Malformed RestMethod responses

Malformed RestMethod responses have been changed in the same manner as the invoice module was fixed.

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

Hi @eliasericsson ,
By changing "$obj = @() + $response.Substring(1) | ConvertFrom-Json" to "$obj = @() + $response" you are changing the functions response from "Object[]" to "String". That will break all scripts using this module.
Can you explain further?
Cheers,
Paulo

Hi Paulo,
I'm in the wrong here. I thought I had corrected some issues I was having,
but after further investigation my solution was incorrect.
I'm trying to use the Get-PCCustomerLicensesUsage cmdlet, and I get the
following errors:

Invoke-RestMethod : The remote server returned an error: (403) Forbidden.
At
C:\Users\149999eler\PartnerCenterPowerShellModule\PartnerCenterModule\PartnerCenterAnalytics.psm1:83
char:17

... $response = Invoke-RestMethod -Uri $url -Headers $headers -ContentTyp
...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation:
(System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
FullyQualifiedErrorId :
WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

You cannot call a method on a null-valued expression.
At
C:\Users\149999eler\PartnerCenterPowerShellModule\PartnerCenterModule\PartnerCenterAnalytics.psm1:84
char:5

$obj = @() + $response.Substring(1) | ConvertFrom-Json

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : InvokeMethodOnNull

The property 'TypeNames' cannot be found on this object. Verify that the
property exists.
At
C:\Users\149999eler\PartnerCenterPowerShellModule\PartnerCenterModule\commons.ps1:13
char:4

$item.PSObject.TypeNames.Insert(0, $type)

+ CategoryInfo          : NotSpecified: (:) [],

PropertyNotFoundException
+ FullyQualifiedErrorId : PropertyNotFoundStrict
I thought I solved #2, but I failed to see that it was dependent on #1.
My code is as follows:

Import the module
Add-PCAuthentication -cspAppID  -cspDomain
-cspClientSecret
Get-PCCustomerLicensesUsage - tenantid

My current assumption is that the application needs to be granted some
extra permissions to access this resource:
"
https://api.partnercenter.microsoft.com/v1/customers/{0}/analytics/licenses/deployment"
-f $tenantid
Do you have insight to what may cause this?
Thanks,
Elias Ericsson Rydberg
2017-12-08 23:45 GMT+01:00 Paulo Ramos<EMAIL_ADDRESS>
Hi @eliasericsson https://github.com/eliasericsson ,
By changing "$obj = @() + $response.Substring(1) | ConvertFrom-Json" to
"$obj = @() + $response" you are changing the functions response from
"Object[]" to "String". That will break all scripts using this module.
Can you explain further?
Cheers,
Paulo
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/PartnerCenterPowerShellModule/pull/36#issuecomment-350391084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB1aA2Cd0e4IhhB5peCv6HsOas3ljKTdks5s-bwKgaJpZM4Q5tmq
.

Hi @eliasericsson ,
Thank you for the follow up and additional details.
I see that you are using app authentication. Have you tried to use user authentication? (This requires the App created during https://msdn.microsoft.com/library/partnercenter/mt709136.aspx process to be Native App instead of Web App)
$credentials = Get-Credential 'username@domain'
Add-PCAuthentication -cspappID '' -cspDomain '' -credential $credentials
The reason for this is that in some methods of Partner Center API user auth is required.


feat("use client"): Adds support for SSR by making all components client components

Resolves #860

I did a diff check on dist/cjs/index.js, and the only difference between the bundles seems to be "use client"

I did a diff check on dist/esm/index.js as well, and here it seems like there are more changes. See: https://www.diffchecker.com/WRdSVoPS/
I will have to test all the components to make sure they still work as expected.

We needed to update typescript and @types/react to their latest versions. If we don't, we will get type errors when using components in Next.

I have tested with a local build of the latest commit on both a NextJS and CRA app.
Everything works as expected.
We can still use dot notation in CRA, but in Next we need to import each component by itself.
This is because every component is now a client component, meaning we dont have access to anything inside it, before we are on the client.

This also closes #812 - Screenshot is of a next app using the checkbox on a server component.

This also closes #812 - Screenshot is of a next app using the checkbox on a server component.

Please link to it in the PR description using the "fixes" Github keyword so its linked and closed when PR is merged :) You se a slightly dotted line under the keywords when its linked correctly


Implement a requestPayment function with webln + fallback

a generic requestPayment(invoice) function that checks if webln is available, and if so it calls webln.
otherwise it renders a DOM element with a QR code + an input field to copy the invoice.

@bumi is this solved by https://github.com/getAlby/bitcoin-connect ?

fixed by bitcoin connect


document nested init-list behavior

Additionally, I doesn't mention how nested initializer_list how are treated. Most importantly it should show or link to some examples on how the initializer_list are converted to objects, arrays, and non structured values because some developers (if not most) might not immediately realize from just looking at the reference documentation how nested initializer_list are parsed. Maybe also reference to the initializer_list constructors of array and object.

I think, the current documentation cover all the topics described  in this issue.


 I added a bunch of stuff to deal with the edge cases of links with surrounding punctuation, and added a module to test against the ICANN list of valid TLDs.
The link parsing fcn is longer, but for me there's no noticeable perf change between this & master. Let me know if it's different for you.

I'm seeing this error, have you seen it?

@MarcoPolo Nojima pushed a fix, PTAL


[bug report] datetimepicker after the custom picker option is less than the current time, the time of the day cannot be selected

Element UI version
2.12.0
OS/Browsers version
MacOS15
Vue version
2.6.10
Reproduction Link
https://jsfiddle.net/xptngLvz/1/
Steps to reproduce
1、打开date picker
2、日期选择明天
3、日期选择今天
What is Expected?
可以选择今天的日期，因为今天的后面time是大于当前时间的
What is actually happening?
不能再次选择今天的日期

Translation of this issue:
Element UI version
2.12.0
OS/Browsers version
MacOS15
Vue version
2.6.10
Reproduction Link
https://jsfiddle.net/xptngLvz/1/
###Steps to reproduce

Open date picker
Date selection tomorrow
Date selection today

What is Expected?
You can choose today's date because the later time of today is greater than the current time
What is actually happening?
Today's date can't be selected again

您上面的链接 当代码改成如下

Translation of this issue:
Element UI version
2.12.0
OS/Browsers version
MacOS15
Vue version
2.6.10
Reproduction Link
https://jsfiddle.net/xptngLvz/1/
###Steps to reproduce

Open date picker
Date selection tomorrow
Date selection today

What is Expected?
You can choose today's date because the later time of today is greater than the current time
What is actually happening?
Today's date can't be selected again

你上面的链接中的代码 改成如下

Translation of this issue:
Element UI version
2.12.0
OS/Browsers version
MacOS15
Vue version
2.6.10
Reproduction Link
https://jsfiddle.net/xptngLvz/1/
###Steps to reproduce

Open date picker
Date selection tomorrow
Date selection today

What is Expected?
You can choose today's date because the later time of today is greater than the current time
What is actually happening?
Today's date can't be selected again

您上面的链接 代码改成如下
html:
type="datetimerange"
:default-time="['00:00:00', '23:59:59']"
js:
pickerOptions: {
disabledDate(time) {
return time.getTime() >= Date.now();
}
}
日期段选择当天的。 确定按钮就不能使用了

2.13.0、2.13.2 也都有这个问题


feat(engine): handle target.*

Handle the sql with dot all like SELECT table.* FROM table and SELECT t.* FROM table AS t.

Thanks @grieve54706.  Could you add some test for the model with calculated fields and the SQL with a join statement?
select a.* from a join b on a.c1 = b.c1


Upgrade webpack template to Webpack 4

What problem does this feature solve?
This version of vue-cli uses a webpack template with following packages:
optimize-css-assets-webpack-plugin 3.2.
webpack  3.6.0
webpack-dev-server 2.9.1
If I try to upgrade these packages, the build script incurs to this error:
/node_modules/webpack/lib/webpack.js:165
			throw new RemovedPluginError(errorMessage);
			^

Error: webpack.optimize.CommonsChunkPlugin has been removed, please use config.optimization.splitChunks instead.

Since vue-cli is really usefull, I think it's necessary to upgrade the webpack template
What does the proposed API look like?
The command

vue init webpack

should create webpack.config.js files that uses the updated modules of webpack

same problem, thanks.

This should be posted to the template's own repo. That said, we are unlikely to do that since 2.x templates will be in maintenance mode with CLI 3 coming soon (which will have webpack 4 support)

@yyx990803 thanks for the answer


GraphQL formData submit support

GraphQL was abandoned for the purpose of the project, so it's not something in the current scope

GraphQL support is not needed for RxNT, so we should not pursue this issue.


⚠ Bofrost.de has degraded performance

In f0dcba0, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1275 ms

Resolved: Bofrost.de performance has improved in 1f15111 after 43 minutes.


NEIGHBORS deprecated in 3.x - update docs

this is a documentation related issue:
Documentation/Books/Cookbook/AQL/Joins.md
still tells about using the NEIGHBORS aql method, which is deprecated: https://docs.arangodb.com/3.1/Manual/ReleaseNotes/UpgradingChanges30.html

3.2, 3.3 and devel documentation were updated, see e.g. https://docs.arangodb.com/3.3/Cookbook/AQL/Joins.html
We don't maintain 3.0 and 3.1 docs anymore, thus closing as fixed.


Create 6.8 release notes

Release notes for https://github.com/NuGet/Client.Engineering/issues/2543

Thanks for looking @zivkan
Note that I haven't really done a pass at all at this point, this is just what the tool generated, as we wanted to get an initial feel of what's part of this release to help with the blog direction.

Addressed all your feedback @zivkan

thanks @donnie-msft!
Added your changes.


PHP 8.1 compatibility

@DusanKasan Could you please merge this and tag a relase? Thank you!

@DusanKasan Is there anything else I can do for this PR to be merged?

This technically fixes compatibility, but there's also different parts that also need fixing and dependencies updated for at least 8.0 before this is merged as we need the tests to pass and everything.
Also, I will check but I vaguely remember not all dependencies being 8.1 compatible in the past. Will double check.
There's a PR for 8.0 compatibility that introduces generics and some more BC stuff. Any reviews are appreciated. https://github.com/DusanKasan/Knapsack/pull/63

Hello All,
may I suggest here that, instead adding the attribute about the future change of type, it is added the return type to make the method compatible with base class public function getIterator(): Traversable; like described in:
https://www.php.net/manual/en/iteratoraggregate.getiterator.php
I did found this trying to fix deprecation notices from phpunit:
Remaining direct deprecation notices (2)

  1x: Return type of DusanKasan\Knapsack\Collection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

thanks in advance for taking care,
David

Just merge and tag this. It breaks absolutely nothing. Don't overthink it.

+1, Please merge the PR. The deprecation notice reported by @davidmpaz is also hugely annoying, this is what my logs look like right now every time a collection is used:
[2022-06-25T09:31:46.998868+00:00] php.INFO: Deprecated: Return type of
DusanKasan\Knapsack\Collection::getIterator() should either be compatible with
IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute
should be used to temporarily suppress the notice {"exception":"[object]
(ErrorException(code: 0): Deprecated: Return type of
DusanKasan\\Knapsack\\Collection::getIterator() should either be compatible with
IteratorAggregate::getIterator(): Traversable, or the #[\\ReturnTypeWillChange] attribute
should be used to temporarily suppress the notice at
/app/vendor/dusank/knapsack/src/Collection.php:98)"} []
[2022-06-25T09:31:46.999002+00:00] php.INFO: Deprecated: DusanKasan\Knapsack\Collection
implements the Serializable interface, which is deprecated. Implement __serialize() and
__unserialize() instead (or in addition, if support for old PHP versions is necessary)
{"exception":"[object] (ErrorException(code: 0): Deprecated:
DusanKasan\\Knapsack\\Collection implements the Serializable interface, which is deprecated.
Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP
versions is necessary) at /app/vendor/dusank/knapsack/src/Collection.php:11)"} []
[2022-06-25T09:31:47.000524+00:00] php.INFO: User Deprecated: Method
"IteratorAggregate::getIterator()" might add "\Traversable" as a native return type
declaration in the future. Do the same in implementation "DusanKasan\Knapsack\Collection"
now to avoid errors or add an explicit @return annotation to suppress this message.
{"exception":"[object] (ErrorException(code: 0): User Deprecated: Method
\"IteratorAggregate::getIterator()\" might add \"\\Traversable\" as a native return type
declaration in the future. Do the same in implementation
\"DusanKasan\\Knapsack\\Collection\" now to avoid errors or add an explicit @return
annotation to suppress this message. at /app/vendor/symfony/error
handler/DebugClassLoader.php:328)"} []

I quickly ran a unit test with
@martinvenus  version with these commits. https://github.com/martinvenus/Knapsack
It fixes some notifications, but this one is still left

  1x: Method "IteratorAggregate::getIterator()" might add "\Traversable" as a native return type declaration in the future. Do the same in implementation "DusanKasan\Knapsack\Collection" now to avoid errors or add an explicit @return annotation to suppress this message.

Would be nice to see a release with the notices fixes. Thanks.


Fixing incorrect siteid variable when setting cacheFactories

The rs.siteid variable needs to be rs.siteid[i] in line https://github.com/blueriver/MuraCache/blob/master/lib/eventHandler.cfc#L29.  Without this fix all cacheFactories actually point to only one siteid in the plugins assigned sites.

Thanks @drapier!


Change gulp to use run-sequence

Related to issue #50 , it happens because running gulp build might result in task ['js'] not run successfully.
This problem is likely due to the minify-js was run asynchronously and it requires the original file in build folder. Therefore, it prevents the ['js'] task from overwriting with new file from src folder.
I added package run-sequence to make sure that ['handle-sources'] is run before ['minify-sources']

Thank you for your contribution!


no-invalid-media-type-examples not working in a basic case with anyOf

Describe the bug
given a sample with anyOf and required statement example validation fails whereas it is valid
To Reproduce
validate the below OAS Spec (in the Additional context section)
launching redocly lint spec.yml
validation fails with the error
 failed with 2 errors and 9 warnings.
it shoot about
schema: must NOT have unevaluated properties lastName
and
Example value must conform to the schema: must NOT have unevaluated properties address.
29 | },
30 | "example": {
31 |     "address": "someWhere",
vs address is mentioned as required , looks it does not like the anyOf syntax
dropping the anyOf make it ok
Expected behavior
no validation warning toward this sample
sample has been tested with several json schema validator  ( json-schema.hyperjump.io , json-everything.net , liquid'
Logs

Redocly Version(s)
redocly 1.25.2 ( on Windows)
Additional context
{
    "openapi": "3.1.0",
    "info": {
        "title": "this is the title",
        "description": "this is the description",
        "version": "1.0"
    },
    "license": {
        "description": "dd"
    },
    "servers": [
        {
            "url": "https://api.server.test/v1"
        }
    ],
    "paths": {
        "/v1/users": {
            "get": {
                "summary": "Get user info",
                "description": "Returns all details about a given user.",
                "operationId": "getUser",
                "responses": {
                    "200": {
                        "description": "Success",
                        "content": {
                            "application/json": {
                                "schema": {
                                    "$ref": "#/components/schemas/User"
                                },
                                "example": {
                                    "address": "someWhere",
                                    "firstName": "John",
                                    "lastName": "Doe"
                                }
                            }
                        }
                    },
                    "400": {
                        "description": "empty"
                    }
                }
            }
        }
    },
    "components": {
        "schemas": {
            "User": {
                "description": "Details of a user",
                "type": "object",
                "required": [
                    "address"
                ],
                "properties": {
                    "address": {
                        "type": "string"
                    }
                },
                "anyOf": [
                    {
                        "type": "object",
                        "required": [
                            "firstName",
                            "lastName"
                        ],
                        "properties": {
                            "firstName": {
                                "type": "string"
                            },
                            "lastName": {
                                "type": "string"
                            }
                        }
                    },
                    {
                        "type": "object",
                        "required": [
                            "name"
                        ],
                        "properties": {
                            "name": {
                                "type": "string"
                            }
                        }
                    }
                ]
            }
        }
    }
}

This is a duplicate of https://github.com/Redocly/redocly-cli/issues/1658. Feel free to add any additional details there.

Wait, this is a separate issue. It goes away if we move address under each of the subschemas of anyOf. However, those syntaxes are equivalent, so the behaviour should be the same. The actual issue is that having properties and anyOf at the same time breaks the logic.

this requires the rules related to example validation to be modified
anyOf with a sibling additionalProperties: false doesn't allow any properties to be defined in that instance.
this line is causing that behavior.
https://github.com/Redocly/redocly-cli/blob/36161d76112779a5ce37289c9f063a35abb91a4e/packages/core/src/rules/ajv.ts#L26C7-L26C35
an example of what the schema is transformed to by Redocly
$schema: 'https://json-schema.org/draft/2020-12/schema,'
properties:
  address:
    type: string
anyOf: [{}, {}]
additionalProperties: false // this is added by Redocly to all example schemas and it causes the example to fail, particularly when composition keywords are used at the root of the schema (anyOf, allOf, oneOf)

If we modify the rule, the example passes validation.
extends:
  - recommended

rules:
  no-invalid-media-type-examples:
    severity: warn
    allowAdditionalProperties: true

{
    "openapi": "3.1.0",
    "info": {
        "title": "this is the title",
        "description": "this is the description",
        "version": "1.0"
    },
    "license": {
        "description": "dd"
    },
    "servers": [
        {
            "url": "https://api.server.test/v1"
        }
    ],
    "paths": {
        "/v1/users": {
            "get": {
                "summary": "Get user info",
                "description": "Returns all details about a given user.",
                "operationId": "getUser",
                "responses": {
                    "200": {
                        "description": "Success",
                        "content": {
                            "application/json": {
                                "schema": {
                                    "$ref": "#/components/schemas/User"
                                },
                                "examples": {
                                    "example": {
                                        "value": {
                                        "address": "someWhere",
                                        "firstName": "John",
                                        "lastName": "Doe"}
                                    }
                                }
                            }
                        }
                    },
                    "400": {
                        "description": "empty"
                    }
                }
            }
        }
    },
    "components": {
        "schemas": {
            "User": {
                "description": "Details of a user",
                "type": "object",
                "required": [
                    "address"
                ],
                "properties": {
                    "address": {
                        "type": "string"
                    }
                },
                "anyOf": [
                    {
                        "type": "object",
                        "required": [
                            "firstName",
                            "lastName"
                        ],
                        "properties": {
                            "firstName": {
                                "type": "string"
                            },
                            "lastName": {
                                "type": "string"
                            }
                        }
                    },
                    {
                        "type": "object",
                        "required": [
                            "name"
                        ],
                        "properties": {
                            "name": {
                                "type": "string"
                            }
                        }
                    }
                ]
            }
        }
    }
}

Btw.. the allowAdditionalProperties implementation is really only useful for OAS 3.0.x (json schema draft-04) when using the keyword additionalProperties
OAS 3.1.x. introduced full support of json schema 2020-12, and a new keyword unevaluatedProperties. this keyword has the ability to see into subschemas defined in a composition keyword (anyOf, allOf).  if Redocly is going to constrain examples to use some form of unevaluatedProperties: false or additionalProperties: false, the proper keyword should be used for OAS 3.1.x schemas. >> unevaluatedProperties: false
an example with OAS 3.0.x
$schema: 'http://json-schema.org/draft-04/schema#'
properties:
  address:
    type: string
anyOf:
- properties:
    firstName:
      type: string
- properties:
    name:
      type: string
additionalProperties: false // any instance will fail this schema because additionalProperties and anyOf are siblings.

valid
address: test

invalid
address: test
firstName: larry

an example with OAS 3.1.x
$schema: 'https://json-schema.org/draft/2020-12/schema'
properties:
  address:
    type: string
anyOf:
-  properties:
     firstName:
       type: string
-  properties:
     name:
       type: string
unevaluatedProperties: false // any instance with `address`, `firstName` or `name` will pass validation.. any other keyword included will fail validation

valid
address: test
firstName: larry
name: Jose

invalid
address: test
firstName: larry
name: Jose
age: 1


Correct Intel Xeon SKU from 8473C to 8573C on Intel based v6 instances

8473C correspond to 4th Generation Xeon. v6 Instances run on 5th Generation Xeon, 8573C SKU.
Add Intel AMX as a capability

@mattmcinnes, @misha-bansal,
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks Courtney, I will review by today and merge the changes.
Best,
Misha

From: Courtney Wales @.>
Sent: Wednesday, August 28, 2024 8:21 AM
To: MicrosoftDocs/azure-compute-docs @.>
Cc: Misha Bansal @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-compute-docs] Correct Intel Xeon SKU from 8473C to 8573C on Intel based v6 instances (PR #11)
@mattmcinneshttps://github.com/mattmcinnes, @misha-bansalhttps://github.com/misha-bansal,
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-compute-docs/pull/11#issuecomment-2315660061, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BIFP7NQPRAPB5YGFFNWT6GLZTXTITAVCNFSM6AAAAABNIMJZYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJVGY3DAMBWGE.
You are receiving this because you were mentioned.Message ID: @.***>

#sign-off


Error when using terraform cloud remote backend

terrascan version:
v1.17.1
Operating System:
macos

Description
Describe what you were trying to get done.
I'm trying to scan terraform code, the terraform code that I am trying to scan uses the remote backend of terraform cloud. Terraform cloud has a special block called cloud instead of defyning backend "remote" you just define cloud
Tell us what happened, what went wrong, and what you expected to happen.
when running terrrascan with this provider block
provider "azurerm" {
  features {
  }
}
terraform {
  cloud {
    organization = "myorg"
    workspaces {
      name = "myworkspace"
    }
  }
}
terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~>3"
    }
  }

}

I get an error stating Unsupported block type; Blocks of type "cloud" are not expected here.
What I Did
terrascan scan -t azure -i terraform

duplicate of https://github.com/tenable/terrascan/issues/1390


Fix kahoy plan typo

This PR:

Corrects a typo in concepts.md
Fixes up a reference to scope and alternatives

Codecov Report

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

@@           Coverage Diff           @@
##           master     #164   +/-   ##
=======================================
  Coverage   75.42%   75.42%
=======================================
  Files          26       26
  Lines        1184     1184
=======================================
  Hits          893      893
  Misses        216      216
  Partials       75       75

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 e2b2deb...1b16ce5. Read the comment docs.


Crashes on mobile when using multiple countdowns

I have a page with 50+ countdowns on it. It works fine on desktop but crashes the android and iphone browsers. The page works on mobile if I use fewer countdowns.
Besides the obvious answer of using fewer countdowns, is there a good solution to this problem?

The plugin it's optimized to use just one interval at time, so it doesn't seem to be a memory leak problem. I know that mobile platforms limits the JavaScript memory consumption for security reasons.
Probably not all you countdowns are shown at the same time, so you could start and stop them when they are shown at the screen.
Hope that helps!

Right now each of the 50+ countdowns tick 10 times a second. If I could change this to tick less often it may solve my problem.
Is there any way to change the tick interval?

@alan-reed yes there is the precision option: http://hilios.github.io/jQuery.countdown/documentation.html#configuration-object

Thank you!. This solved my problem.

Alan Reed
Founder, Proud Development, LLC
https://www.prouddev.com
On Wed, Sep 14, 2016 at 5:20 PM, Edson Hilios<EMAIL_ADDRESS>wrote:

@alan-reed https://github.com/alan-reed yes there is the precision
option: http://hilios.github.io/jQuery.countdown/documentation.html#
configuration-object
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hilios/jQuery.countdown/issues/202#issuecomment-247158124,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACvDPIUr560ZsOwliGE-mM5maAMkaz1vks5qqGUzgaJpZM4IxH40
.


Bug: Styles are leaking to whole application

Reproduction
Here is a codesandbox example using v6.1.1, I hope this is sufficient to show what is happening. The red row should not be styled since it is completely outside any styled-component.
https://codesandbox.io/s/styled-components-base-forked-krjsxn?file=/index.js
Additional info
The syntax below is compiled in such a way as that the rule affecting p tags is placed outside the scope of the styled-component. It seems to be the combination of  a parent selector and pseudo-classes that trips styled-component up.
&.foo,
  p:not(:last-child) {
    background: red;
  }

Perhaps it is a bug coming from styles.compile

Your styled component StyleThatLeaks has a CSS rule that targets p elements that are not the last child within their respective parent. The CSS rule specified in &.foo, p:not(:last-child) doesn't specifically require the p tags to be within a styled component to apply the styles. It affects all p tags that are not the last child within their parent, regardless of where they are in the DOM structure.
If you want to limit the scope of this CSS rule only to p elements within the StyleThatLeaks component, you might need to adjust your CSS rule or use a more specific selector to target only the desired p elements within that component. For example, you could prefix the p:not(:last-child) selector with .foo to restrict it to p elements within the StyleThatLeaks component with the foo class:
const StyleThatLeaks = styled.div`
  background: green;

  &.foo,
  &.foo p:not(:last-child) {
    background: red;
  }
`;

@mcmgeomagic1 that has to be written by an AI, right?

Made an issue over on stylis https://github.com/thysultan/stylis/issues/321

If you don't need container queries, you can try temporarily pinning your application using package.json resolutions or overrides to 4.0.10 or earlier per this comment


Validate a multi-step form with repeatable fieldGroup

I'm submitting a ...
[ ] bug report
[ ] feature request
[  #x] support request

Current behavior
I use the multi-step form with repeatable fieldGroup in a fieldArray.
What I try to do is validate the form  and disable the submit button if the form is invalid or if the fieldArray has no content or the repeatable fieldGroup is not fully completed  .
Right now I try to use required equal to true in the fieldArray but with no sucess
I also tried to use the validators but it won't update the whole form
Expected behavior
Be able to get the fieldGroup status (valid or invalid) from the "global" form to enable or disable the next or submit button
Minimal reproduction of the problem with instructions
I've made a stackblitz that reproduce my settings: https://stackblitz.com/edit/angular-kfmshi
How can i validate the form with a repeatable element  ?

use hideExpression instead of changing hide manually https://stackblitz.com/edit/angular-kfmshi-vcbk6j

@aitboudad , thank you for your quick reply.
Unfortunately I was not clear enough. I updated my stackblitz with your answer.
At step 3 , if you choose no, the button submit remain disabled, How do I track change of status (valid or invalid)  from   the investments repeat ?
Thank you

the investment validators should be placed under repeat field type or a parent field in order to track change of status see the following example: https://stackblitz.com/edit/angular-kfmshi-nib6at

@aitboudad thank you. it works !


Yichen/fragile bit masking

{{fragile bit masking}}
PR description
Modify fragile bit masking by introducing polar-coordinate based method and also convert mask_responses to complex type, allowing different masks in real and imaginary part of the filter responses and the final iris template.
Issue
Fragile bits are bits with unstable iris responses that could easily flip the bit values or bits with significant interference from foreign objects, such as hair or reflection. These fragile bits have a negative impact on the persistence of iriscode and are hence masked out.
Solution
We proposed methods to detect and mask out fragile bits in iris_responses and templates (iriscodes). We allow separate masking for the real and imaginary part of the iris response to minimise the impact of reduced mask size.
Limitations
Reduced mask size could result in slight shift in Hamming distance distribution.
Type

[x] Feature
[x] Refactoring
[ ] Bugfix
[ ] DevOps
[x] Testing

Checklist

[x] I've made sure that my code works as expected by writing unit tests.
[x] I've checked if my code doesn't generate warnings or errors.
[x] I've performed a self-review of my code.
[x] I've made sure that my code follows the style guidelines of the project.
[x] I've commented hard-to-understand parts of my code.
[x] I've made appropriate changes in the documentation.

Thanks for the contribution !
@ycbiometrics Can you make this PR a merge from your branch yichen/fragile-bit-masking to dev instead of main ? This will clear the commit history, I'll get started on the review once this is done 🙂

done.


bowtie (1) pipeline breaks with gzipped FASTQ files

Apparently bowtie isn't able to cope with them and aborts. This likely warrants piping them through zcat or equivalent for aligning.

Luca -- thanks for the heads up on this. The latest development version now supports these inputs for bowtie and bowtie2, allowing them to be used in these standard pipelines. Let us know if you run into any problems at all with the latest version.


joined unique() question

Hello!  I have been developing from this template since 2022.
At that time I saw that the model was using {"lazy": "selectin"} and I used it myself without any problems.
However, there are times when I need to use joined to improve performance, but when I use joined I have a problem with unique().
I came across https://github.com/jonra1993/fastapi-alembic-sqlmodel-async/issues/20 and changed selectin to use joined.
I found from https://github.com/jonra1993/fastapi-alembic-sqlmodel-async/blob/main/backend/app/app/crud/base_crud.py#L35 that unique() is not used.
I ran docker-compose-dev.yml and the API works fine.
My model uses sa_relationship_kwargs={"lazy": "joined"}.
But in my context must use response.unique().scalar_one_or_none()!
I would like to know why there is no problem with this project, but I am having problems.
Could it be a version issue? After all, I developed this project with reference to 2022 and the kit is a bit old.
Thanks for any feedback.

Hello @hgalytoby which version of fastapi, pydantic and sqlmodel are you using?

fastapi 0.97.0
sql model 0.0.8
pydantic 1.10.15
I know the kit version is old, after all I developed this project with reference to 2022.
If it was a kit version I would have no problem with it.

It's been a long time since I've used SQL and my own project is very old, so I'm asking out of curiosity and not trying to learn with the latest version.
I think this problem should be solved if I learn it on the spot.


Suggestion

I know the plugin its not finished, im just suggesting you can do it whenever you want

Is a discord webhook which shows the coords of the KoTH, the world and the time

Sure I can do that. Since you are the first person to contact me about this plugin, do you think I should support for multiple koth arenas?

Yes, since the general purpose of a KoTH plugin is for HCF and HCF servers and the average HCF or UHCF map has at least two KoTH i think it is needed.

Discord webhooks added in: 13e7ac5


Custom Causer Model

This is more a feature request with the idea being able to set a custom model for the causedBy method. In my example use case I don't want to track activity by a User but instead a Contact.
Perhaps I'm seeing this backwards and instead could run a search on performedOn for a specific Contact to get the history of that contact for this purpose?

I think that would just give you the actions performed on that Contact, not the actions performed by that Contact, which I don't think is what you want.
Is the User also a Contact?

@dicarlosystems No a Contact is separate from a user. A user manages contacts, owns them, but a contact can be unowned also.

Yep, sounds like that would handle your situation.  Only issue would be if you wanted to see actions performed by a contact but that would imply the contact is a user, also.

Yeah good point. I wonder if adding the option to specific the Model of the causedBy would require a significant change in the package.
Tabling this for now, though it would be a nice option to have instead of limiting it to the User model.


Table inside a NestedLexicalEditor doesn't update properly [BUG]

[x] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
[x] I have read the documentation and cannot find an answer.

Describe the bug
When a table is added inside a NestedLexicalEditor, the table cell contents does not update in the source mode until a space outside of the table is clicked within the NestedLexicalEditor. This means saved content can be lost when updating a table which is inside a NestedLexicalEditor.
To Reproduce

Add a component which uses a NestedLexicalEditor to the MDXEditor (e.g. anything which uses the GenericJsxEditor with children)
Click within the NestedLexicalEditor and insert a table
Add some text to a cell of the table
Click on the 'source mode' option to view the MDX source
Observe no text appears in the table source (even if you click outside the NestedLexicalEditor)
Click within the NestedLexicalEditor but outside of the table
The table text has now updated in the MDX source

Expected behavior
The table should update when it's changed, and not require an extra click inside the NestedLexicalEditor to trigger an update.
Screenshots
Video demonstration using the GenericJsxEditor and table plugin:
https://github.com/mdx-editor/editor/assets/144693997/28f5b4d6-550f-4fdf-a434-038a42345fc1
Desktop (please complete the following information):

OS: Windows 11
Browser: Observed in Chrome, Edge, and Firefox

Additional context
I think this could be because the table editor doesn't dispatch the NESTED_EDITOR_UPDATED_COMMAND when it saves an update, so the NestedLexicalEditor doesn't update itself.

That's a nasty limitation of Lexical's nested editors, a bit of a chicken-and-egg problem, I'm afraid.


[VS Code] Starting collaboration session: 无法连接到服务器。请检查你是否已连接到 Internet。

<!--
For Visual Studio problems/feedback, please use the Report

Thanks for reaching out. This is a known issue, but all the bug reports help us understand the frequency of an issue and prioritizing our work. Did a retry fix the issue for you? Closing as a dupe of #1113.


flash managing mechanism has incompleted java doc

Flash managing mechanism has incompleted java doc.
Сlasses RsFlash, TsFlash, XeFlash needs more explanation.

@davvd this is definitely a bug, let's dispatch it

@davvd this is definitely a bug, let's dispatch it

@yegor256 thanks, I added the "bug" tag

@yegor256 the task is yours (budget is 30 mins)

@dmzaytsev thanks for reporting! I topped your account for 15 mins, transaction 54263086

@dmzaytsev take a look at the changes I've made in a9db501 good enough?

@yegor256  thanks!

@yegor256 I just added 1 hour to your account, many thanks for your contribution.. 000-149044a5 spent here. age=6 is a bonus here for fast delivery. +60 added to your rating, at the moment it is: +8771


Structuring data docs

Background
I had a chat with @amin2718 and he dropped the 411 on me regarding how to structure data, how the structure affects how the data is indexed, and the resulting retrieval behavior.
CC @pwoznic @ofermend @justinhayes
Problem
We looked for some docs that cover this topic, and the closest I could find is https://docs.vectara.com/docs/api-reference/indexing-apis/indexing. This is problematic because:

This content is buried deep in the information tree.
It's hidden inside a page called "API Definition".
It lacks an example JSON object that describes a realistic shape.

This means this information is not discoverable and also challenging to apply.
Explanation

Note: I've left open questions in a quote block, like this.

When the user uploads a file like a PDF, Vectara naively parses it for ingestion. This means that although it will capture all of the text contained in the document, it might make parsing mistakes and it will be unable to extract any structural information. In other words, the data the ends up in the corpus will lose any meaningful relationships between the bits of data in the original file.
The benefits to munging files into a structured data format are:

The relationships of the bits of data can be preserved.
The special meaning of specific types of data is retained, such as dates and titles.
Users can query the data with filters.

Let's use this PDF as an example:
www.techtransfer.nih.gov_tech_tab-3843.pdf
Vectara offers a structured data format. I converted the above PDF into this format below. The longer bits of text have been truncated for brevity.
{
  "documentId": "TAB‑3843",
  "title": "Engineered Cell‑Penetrating Monoclonal Antibody for Universal Inuenza Immunotherapy",
  "description": "Home » Tech » Engineered Cell‑Penetrating Monoclonal Antibody for Universal Inuenza Immunotherapy",
  "metadataJson": "{\"developmentStatus\":\"Pre‑Clinical\",\"isAntibodiesProduct\":true,\"date\":\"2023‑05‑17\",\"patentSeriesCode\":63,\"patentApplicationNumber\":365841}",
  "section": [{
    "title": "body",
    "text": "Influenza remains a burden on public health..."
  }, {
    "title": "Clinical treatment",
    "text": "Clinical Treatment꞉ CPP‑mAbs against inuenza NP may...",
    "metadataJson": "{\"clinicalTreatment\"꞉\"CPP‑mAbs against inuenza NP may...\"}",
  }, {
    "text": "Current vaccines remain effective for a short time period..."
  }]
}

This structure is informed by three concepts:

Document
Metadata
Sections

Document
In this example, the document is identified by:

documentId
title
description

This is the high-level information that is encoded into vectors when Vectara ingests the document. This information can be retrieved using semantic, keyword-based, and hybrid search.

Question: Can documentId, title, and description all be used in filters? Can they be used to semantically match queries? What's the point of description -- why not just smush everything into title? Is it perhaps because splitting it up into title and description is more useful for a human who's reviewing the document?

Metadata
The document has metadata attached to it via the metadataJson property. This property expects to be assigned a stringified JSON object. This object consists of arbitrary key-value pairs, accepting text, numeric, and boolean values.

Question: Does this object accept text, numeric, and boolean values? Does it accept any other types of data?

In this example, we've picked various properties out of the original PDF that will be useful for:

Filtering
Cross-referencing a document with other data sources
Comparing and grouping results

Question: I made up "comparing and grouping results". Is that accurate? How would one go about doing that? Are there other use cases for metadata?

We defined these particular metadata properties on the document level instead of the section level (see below) because we intend to use them to retrieve the entire document and not just a part of it.

Question: "we intend to use them to retrieve the entire document and not just a part of it" -- is that accurate?

developmentStatus: This tells us the status of the patent, e.g. pre-clinical.
isAntibodiesProduct: This tells us whether the patent applies to antibodies-related products, which is the domain we care about in this contrived example.
date: The date this document was created.
patentSeriesCode: The patent series code number.
patentApplicationNumber: The patent application umber.

Metadata can also be attached to sections, covered next.
Sections
Sections are an organizational unit for grouping related bodies of text. A section is defined by:

text: The body of text.
title: An optional name for identifying the body of text. Similar to a heading in a document.
metadataJson: An optional stringified JSON object, which can be configured as flexibly as the root-level document metadata.
sections: An optional array of child sections. Those sections can, in turn, have their own child sections.

When Vectara ingests a document, it will split the text in these sections into chunks and encode them in vectors. This enables queries to retrieve them based on semantic similarity.

Question: Why organize content into multiple/nested sections instead of smushing everything into a single section, or even into the description property? Is there a functional or behavioral difference? Or is it simply to help the human who might be manually reviewing a document?

CC @tallatshafaat

The other page that's relevant here, and that I was having trouble finding
the other day (I actually found it via Google Search :-) ), is this one:
Format JSON and Pbtext Files -
https://docs.vectara.com/docs/api-reference/indexing-apis/file-upload/format-for-upload
https://docs.vectara.com/docs/api-reference/indexing-apis/file-upload/format-for-upload
It includes a concrete example of formatting a Shakespeare play.
On Wed, Oct 11, 2023 at 11:43 AM CJ Cenizal @.***>
wrote:

Background
I had a chat with @amin2718 https://github.com/amin2718 and he dropped
the 411 on me regarding how to structure data, how the structure affects
how the data is indexed, and the resulting retrieval behavior.
CC @pwoznic https://github.com/pwoznic @ofermend
https://github.com/ofermend @justinhayes
https://github.com/justinhayes
Problem
We looked for some docs that cover this topic, and the closest I could
find is https://docs.vectara.com/docs/api-reference/indexing-apis/indexing.
This is problematic because:

This content is buried deep in the information tree.
It's hidden inside a page called "API Definition".
It lacks an example JSON object that describes a realistic shape.

This means this information is not discoverable and also challenging
to apply.
Explanation
Note: I've left open questions in a quote block, like this.
When the user uploads a file like a PDF, Vectara naively parses it for
ingestion. This means that although it will capture all of the text
contained in the document, it might make parsing mistakes and it will be
unable to extract any structural information. In other words, the data the
ends up in the corpus will lose any meaningful relationships between the
bits of data in the original file.
The benefits to munging files into a structured data format are:

The relationships of the bits of data can be preserved.
The special meaning of specific types of data is retained, such as
dates and titles.
Users can query the data with filters.

Let's use this PDF as an example:
www.techtransfer.nih.gov_tech_tab-3843.pdf
https://github.com/vectara/vectara-docs/files/12862357/www.techtransfer.nih.gov_tech_tab-3843.pdf
Vectara offers a structured data format. An example of this format is
below. The longer bits of text have been truncated for brevity.
{
"documentId": "TAB‑3843",
"title": "Engineered Cell‑Penetrating Monoclonal Antibody for Universal Inuenza Immunotherapy",
"description": "Home » Tech » Engineered Cell‑Penetrating Monoclonal Antibody for Universal Inuenza Immunotherapy",
"metadataJson": "{"developmentStatus":"Pre‑Clinical","isAntibodiesProduct":true,"date":"2023‑05‑17","patentSeriesCode":63,"patentApplicationNumber":365841}",
"section": [{
"title": "body",
"text": "Influenza remains a burden on public health..."
}, {
"title": "Clinical treatment",
"text": "Clinical Treatment꞉ CPP‑mAbs against inuenza NP may...",
"metadataJson": "{"clinicalTreatment"꞉"CPP‑mAbs against inuenza NP may..."}",
}, {
"text": "Current vaccines remain effective for a short time period..."
}]
}
This structure is informed by three concepts:

Document
Metadata
Sections

Document
In this example, the document is identified by:

documentId
title
description

This is the high-level information that is encoded into vectors when
Vectara ingests the document. This information can be retrieved using
semantic, keyword-based, and hybrid search.
Question: Can documentId, title, and description all be used in
filters? Can they be used to semantically match queries? What's the point
of description -- why not just smush everything into title? Is it perhaps
because splitting it up into title and description is more useful for a
human who's reviewing the document?
Metadata
The document has metadata attached to it via the metadataJson property.
This property expects to be assigned a stringified JSON object. This object
consists of arbitrary key-value pairs, accepting text, numeric, and boolean
values.
Question: Does this object accept text, numeric, and boolean values?
Does it accept any other types of data?
In this example, we've picked various properties out of the original PDF
that will be useful for:

Filtering
Cross-referencing a document with other data sources
Comparing and grouping results

Question: I made up "comparing and grouping results". Is that accurate?
How would one go about doing that? Are there other use cases for metadata?
We defined these particular metadata properties on the document level
instead of the section level (see below) because we intend to use them to
retrieve the entire document and not just a part of it.
Question: "we intend to use them to retrieve the entire document and
not just a part of it" -- is that accurate?

developmentStatus: This tells us the status of the patent, e.g.
pre-clinical.
isAntibodiesProduct: This tells us whether the patent applies to
antibodies-related products, which is the domain we care about in this
contrived example.
date: The date this document was created.
patentSeriesCode: The patent series code number.
patentApplicationNumber: The patent application umber.

Metadata can also be attached to sections, covered next.
Sections
Sections are an organizational unit for grouping related bodies of text. A
section is defined by:

text: The body of text.
title: An optional name for identifying the body of text. Similar to
a heading in a document.
metadataJson: An optional stringified JSON object, which can be
configured as flexibly as the root-level document metadata.
sections: An optional array of child sections. Those sections can,
in turn, have their own child sections.

When Vectara ingests a document, it will split the text in these sections
into chunks and encode them in vectors. This enables queries to retrieve
them based on semantic similarity.
Question: Why organize content into multiple/nested sections instead of
smushing everything into a single section, or even into the description
property? Is there a functional or behavioral difference? Or is it simply
to help the human who might be manually reviewing a document?
—
Reply to this email directly, view it on GitHub
https://github.com/vectara/vectara-docs/issues/108, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATZSFDDE3F5HJRTIRTR6KWTX63SGRANCNFSM6AAAAAA54ODEOQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

For someone coming-in without PB background the title here "Format JSON and PBText files" may be a bit confusing. People know what JSON is but many don't know what PBText is.
"Alternatively, you may perform the text extraction yourself, and save the result as a JSON or text serialized Document proto. The benefit of this approach is that you can attach your own metadata to the document, or to individual sections within it."
So a developer unfamiliar with PB may be confused again: what is "text serialized Document Proto"? is that the same as PBText? Now I have to go and learn about what that is.
Would be great to give a bit more context to the two types of options in our own words, or at least explain better.

We can also create another section or page about "special metadata".
Special metadata
Vectara Console recognizes special metadata which we've found have common use cases.
date
If you define date in the document's metadata, it will appear in the Console Corpus Search interface. This can be useful for tracking the recency of a document, since older docs can lose relevance in some scenarios.
url
If you define url in the document's metadata, it will in the Console Corpus Search interface as a clickable link. This can be useful for enabling users to click through to the document's original resource, e.g. a web page or downloadable artifact.


(PA-4178) Only clear and add non-default gem sources

Rubygems 3.1 and up will prompt when adding a gem source that is too similar to
rubygems.org to protect against typo squatting. This causes tests to fail if
GEM_SOURCE is not overridden:
gem source --add https://rubygems.org
  ERROR:  While executing gem ... (Gem::OperationNotSupportedError)
    Not connected to a tty and no default specified

Since rubygems always includes https://rubygems.org as the default source, we
now only clear and add the source when it's not the default.

The configure_gem_mirror method is only called from setup steps and has no tests:
$ git grep configure_gem
lib/beaker-puppet/install_utils/foss_utils.rb:        def configure_gem_mirror(hosts)
setup/common/012_Finalize_Installs.rb:  configure_gem_mirror(hosts)
setup/git/000_EnvSetup.rb:  configure_gem_mirror(agents)


as a 3bot owner I want to see when my 3bot solution expires

as a 3bot user I want to see when my 3bot solution expires

red color if expiration is in 2 days:

when deploying in https://deploy3bot2.grid.tf , it's now showing expiration date for all 3bot instances and with red color for less that two days expire date.


[BUG] Don't redraw entire statvar panel on selection change

Describe the bug
The state of the statvar panel is completely refreshed whenever an option is unselected. It's very jarring when there are multiple menus open.
To Reproduce
URL: http://localhost:8080/tools/timeline#&place=geoId/0606000,geoId/2511000,geoId/2603000,geoId/1777005,geoId/1225175,geoId/4815976&statsVar=Count_Person_EducationalAttainmentKindergarten,2,0,2
Steps to reproduce the behavior:

Expand many options in the stat var menu
Choose an option
Unselect any option

Expected behavior
Options that have been expanded, should stay expanded.
Screenshots
https://screencast.googleplex.com/cast/NTYwOTcwNzY0NzUzMzA1NnwzYzhlOGJlZS02Ng

Right now each checkbox expansion state is based on the selected stats vars. We can keep an array of "ever selected" stats var in StatsVarMenu component, and use that for expansion status


iOS engine out directory contains large clang_arm64/obj/third_party/vulkan-deps copy

engine out/ios_debug_unopt/clang_arm64/obj/third_party/vulkan-deps is almost 2 GB.
I don't think vulkan-deps would be needed for iOS, but it's getting pulled in with clang.  Is there any way to prevent this from being written?
cc @chinmaygarde

I don't think vulkan-deps would be needed for iOS

The dependencies seem to be coming from impellerc. The Stage 1 compiler and optimizer uses SPIRV as an intermediate before MSL conversion. So yes, iOS doesn't need it at runtime. But those dependencies are used during the construction of MSL at build time.
I should say the GN rules aren't great there are multiple targets that generate archives we don't need that end up inflating size of artifacts on disk. But those rules are vended by third parties. We could go an tinker on them for modest size reductions or maintain a copy of those rules.


User profile pictures

Create a way for users to set a profile picture and have a default picture for users who hasn't set one yet.

/assign

@Bamof25th would you be able to breakdown your approach to implementing this before I assign you the issue.

ok will update the user model  -
=> profilePicture: {
type: String,
default:
"https://cdn.pixabay.com/photo/2015/10/05/22/37/blank-profile-picture-973460_1280.png",
},
and  will update the signup and other controllers accordingly.

@Bamof25th
Sounds good to me. I will assign this issue to you, please try and get this done as soon as possible.

ok

Done check, please ✅
Add user profile picture functionality with default avatar for users without a custom picture
currently :

added a default url for the default avatar as a user profile picture.

updated the user model  accordingly

fixed typo in modal in password section


Update active learning classes.json processor

Previously, the code that loads in the classes.json file did not account for the missing classes in COCO.  This fixes associated indexing issues so that active learning with the default cocossd model works out of the box on the coco dataset.

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

@csaroff please re-target your PR to the develop branch


Bug in singleton + docs fixes

Separate commits for each thing.
Bug appears when you call base without new keyword for example
var base = require('base')
var app = base({baz: 'qux'}, {yeah: 123, nope: 456})

app.set('foo', 'bar')
console.log(app.foo) // => 'bar'
console.log(app.baz) // => 'qux'

console.log(app.get('foo')) // => 'bar'
console.log(app.get('baz')) // => 'qux'

console.log(app.yeah) // => undefined
console.log(app.nope) // => undefined
console.log(app.options) // => {}

calling it with new Base() works as expected (and as in tests) without this PR.

I know you don't like so much big examples,

I do it sometimes too, like you've said, sometimes it's necessary. I just like them a bit smaller in general. this is great though thanks!

damn, good catch.

Haha, yea! ;d
Btw, i tried to run verb, but it eats the whole readme (meaning.. it was like copy of verb.md file, with no other template staff from default layout from readme generator and etc), so i left it off.

it was like copy of verb.md file, with no other template staff from default layout from readme generator and etc), so i left it off.

yeah I have fixes for verb that will probably resolve that. the good thing is that verb will be really easy to maintain. the bugfixes are getting easier

the good thing is that verb will be really easy to maintain. the bugfixes are getting easier

absolutely! when we get familiar with underling libs/plugins. initially it cost some time (low) to realize from where comes given problem, but it worths.


LLVM CI: build LLVM from source

The official Apt repositories only serve the 3 most recent major versions, while the volunteer-built packages are incomplete and of inconsistent quality, so the best solution is to build LLVM ourselves.
This also reduces the total size for the 6 LLVM caches from 8 GB to around 2.4 GB. That's more than half the limit for a GitHub repository.
lld is needed for #13193; technically speaking, we could build it straight from the very repository we're cloning here, but we aren't really testing any version-specific lld behavior, so this patch grabs it from Apt.

This also reduces the total size for the 6 LLVM caches

Hmm actually it looks like there wasn't even any reason to have those caches before because it just moves the download+extract step from one place on GitHub to another.
Now of course they'll be necessary.
Looks good

I was actually about to look into using nix more for our builds.
We already have an environment with configurable LLVM versions in shell.nix. The dependencies are defined and cached in nixpkgs. And nixpkgs_unstable currently has package definitions for LLVM 8 through LLVM 18. So we don't need to build anything ourselves

The official Apt repositories only serve the 3 most recent major versions

You mean the official Debian or Ubuntu APT repositories?
Because the official LLVM APT repositories have all the releases we want. For example LLVM 13 to 18 for Ubuntu 22.04 + nightlies of LLVM 19 (see https://apt.llvm.org/jammy/pool/main/l/), and it will continue to receive the new releases for years to come. For Ubuntu 20.04 they have all releases since LLVM 9 (see https://apt.llvm.org/focal/pool/main/l/).

Noble, the next Ubuntu version that is going to become LTS, serves only 17 and beyond, so we risk being unable to update to a more recent Ubuntu runner image. We cannot really drop CI for LLVM 13 yet, and technically all the way down to LLVM 11, the most recent version released when Crystal 1.0 was out.


Where is the plugged directory on Windows?

I have tried following the steps to install vim-plug on Windows. Is vim-plug a requirement before attempting to install https://github.com/elixir-lang/vim-elixir???
I only have the following directory
c:\users\daniel.vim\bundle  - I have no [[plugged]] directory as specified here
call plug#begin('~/.vim/plugged')
call plug#end()
The contents of my c:\Program Files (x86)\Vim\_vimrc file is -
`set nocompatible
source $VIMRUNTIME/vimrc_example.vim
source $VIMRUNTIME/mswin.vim
behave mswin
set diffexpr=MyDiff()
function MyDiff()
let opt = '-a --binary '
if &diffopt =~ 'icase' | let opt = opt . '-i ' | endif
if &diffopt =~ 'iwhite' | let opt = opt . '-b ' | endif
let arg1 = v:fname_in
if arg1 =~ ' ' | let arg1 = '"' . arg1 . '"' | endif
let arg2 = v:fname_new
if arg2 =~ ' ' | let arg2 = '"' . arg2 . '"' | endif
let arg3 = v:fname_out
if arg3 =~ ' ' | let arg3 = '"' . arg3 . '"' | endif
let eq = ''
if $VIMRUNTIME =~ ' '
if &sh =~ '<cmd'
let cmd = '""' . $VIMRUNTIME . '\diff"'
let eq = '"'
else
let cmd = substitute($VIMRUNTIME, ' ', '" ', '') . '\diff"'
endif
else
let cmd = $VIMRUNTIME . '\diff'
endif
silent execute '!' . cmd . ' ' . opt . arg1 . ' ' . arg2 . ' > ' . arg3 . eq
endfunction
call plug#begin('~/.vim/plugged')
call plug#end()`
Please help I have spent 3 days trying to edit my first .exs file from the Elixir Mix Getting Started project using gVim on Windows 10.

Type:

[ ] Bug
[ ] Enhancement
[ ] Feature Request
[ ] Question

OS:

[ ] All/Other
[ ] Linux
[ ] OS X
[x] Windows

Vim:

[ ] Terminal Vim
[x] GVim
[ ] Neovim

I hacked at it some more and ran :PlugInstall from gVims command line, and to my chagrin, I had not installed the plugin yet. So I have resolved my own issue, so closing this issue myself.


Bumped arrow-format to 0.8

Signed-off-by: Xuanwo<EMAIL_ADDRESS>It's required to use the same version of arrow-format for downstream.
This PR will help address issues like:
error[E0308]: mismatched types
   --> src/query/service/src/api/rpc/exchange/exchange_transform.rs:243:53
    |
243 |                     let data = FragmentData::create(values);
    |                                -------------------- ^^^^^^ expected struct `common_arrow::arrow_format::flight::data::FlightData`, found struct `arrow_format::flight::data::FlightData`
    |                                |
    |                                arguments to this function are incorrect
    |
    = note: struct `arrow_format::flight::data::FlightData` and struct `common_arrow::arrow_format::flight::data::FlightData` have similar names, but are actually distinct types
note: struct `arrow_format::flight::data::FlightData` is defined in crate `arrow_format`
   --> /home/xuanwo/.cargo/registry/src/github.com-1ecc6299db9ec823/arrow-format-0.7.0/src/flight/data.rs:202:1
    |
202 | pub struct FlightData {
    | ^^^^^^^^^^^^^^^^^^^^^
note: struct `common_arrow::arrow_format::flight::data::FlightData` is defined in crate `arrow_format`
   --> /home/xuanwo/.cargo/registry/src/github.com-1ecc6299db9ec823/arrow-format-0.8.0/src/flight/data.rs:215:1
    |
215 | pub struct FlightData {
    | ^^^^^^^^^^^^^^^^^^^^^
    = note: perhaps two different versions of crate `arrow_format` are being used?
note: associated function defined here
   --> src/query/service/src/api/rpc/packets/packet_data.rs:34:12
    |
34  |     pub fn create(data: FlightData) -> FragmentData {
    |            ^^^^^^ ----------------

Fix https://github.com/jorgecarleitao/arrow2/issues/1294

Needs https://github.com/jorgecarleitao/arrow2/pull/1299 to make all check passed.

Thanks, @Xuanwo ! 🙇


Fix Waypoint Bring Your Javascript Slot Machine to Life Tests

Regex now looks for the use of the .html method specifically
Closes #3533

Closed as a duplicate of #3544


2022 TODOs

Todo list for 2022

Survey of available metadata schema, glossary and ontology
We will try to align with MSLE Ontology, this will fix/expand the Instrument/Equipment part.
We will create Sample Preparation
We will create Measurement
We will create Data Analysis
Check what is available for Sample Description
Check Materials Description -> Crystal Structure into atomic Level (Crystal Structure Ontology)
We will decribe the real Data

TODOs for June 2022.

Mapping STM data to Ontology
@MehrdadJalali-KIT @az-ihsan sparql queries (once the competency questions are ready)

To dos for next week:

schema of STM @EOsmenaj
check and comment ontology @mpanighel
discuss together @az-ihsan  and @MehrdadJalali-KIT
introduction @rossellaaversa

TODOs for 08.02.:

check whether correlative characterization uses analysed data or raw data @rossellaaversa
place correlative characterization into relation to other elements of the ontology according to new definition @az-ihsan

TODOs for 09.02:

According to the issue, please check in the MDMC group regarding the DataAnalysis as superclass. What we are missing is a definition of the proper "data analysis" within the data analysis superclass, @mpanighel @rossellaaversa @MehrdadJalali-KIT

TODOs for 15.02:

The discussion of result meeting on 09.02
Requirement Analysis
Comment regarding ResearchData from @EOsmenaj

Data Analysis Lifecycle
The process of systematically performing actions and methods, e.g. statistical and/or logical techniques, on Research Data in order to produce synthesized knowledge to, e.g., detect patterns, determine relationships, develop explanations, test hypotheses, prove theories, suggest conclusions.
Data Analysis includes (but is not limited to): Data Processing, Data Analysis, Data Interpretation. These actions may be iterative and may be combined in chains or workflows.
Data Processing
Data treatment performed on Raw Data to prepare it for another procedure of the Data Analysis Lifecycle, e.g., Data Analysis or Data Interpretation. It usually consists of routine actions. It may include: sampling, filtering, de-noising, transformation, fusion or compression of existing data, as well as calibration, normalization, statistical data reduction, background subtraction, correction of artifacts.
Data Analysis
The process of collecting, modeling, and analyzing Research Data to extract insights that support the answer to some specific research question. Data Analysis may be performed using Data Analysis Software. It may include: linear combination, data fitting, data modeling, pattern extraction.
Data Interpretation
The process of assigning meaning to the collected information, after an analytical and/or experimental Study, and determining the conclusions, significance, and implications of research findings, possibly in comparison with a predefined reference.
Correlative Characterization
The identifiable action of describing one or more Samples (depending on the particular research context) and connecting the different types of information from co-referenced (in time or space) multi-dimensional Research Data. This may include using multiple Measurement Techniques to obtain complementary insights for a region of interest, as well as putting into relation features and properties of different Sample areas across multiple length scales or over time.

@MehrdadJalali-KIT prepare image connecting Data Analysis lifecycle, Data Processing, Data Analysis and Data Interpretation

Dear all,
I made some changes to the schema, from a graphical point of view (they are visible, no need to describe them :) )
Instead, I added some new relations properties:
Sample component synthesis- prov:wasAssociatedWith->Research User
provResearchData-wasGeneratedBy->Prov:Data Analysis Lifecycle
ProvActivity:Data Analysis Lifecycle-used->ProvEntity:ResearchData
Measurement-wasAssociatedWith->Research user
Sample preparation -wasAssociatedWith->research user
I transformed: provEquipment and provMSLE:equipment in Entities (if not correct, I can change in other. Currently they were not defined)
The same, we have not defined yet, what correspond in prov: locationLaboratory, measurement technique, Data collaboration platform, metadata, metadata repository, data repository, and DOI.

TODOS for June 2022,

@az-ihsan and @MehrdadJalali-KIT should meet to discuss the mapping of the ontology.
@az-ihsan and @MehrdadJalali-KIT define data properties on every class if any.
@EOsmenaj send the link for the STM workflow publication if it is approved

stale issue closed


🚀 Feature Request: support for top level await?

Describe the solution
Some libraries already use top level await. And I think you should allow this too. I dont see any problems with this, and if there is any, can be easily bypassed with an async function, but it harms code readability (dont want my whole file's code to go inside an async function). So can we please consider this?
✘ [ERROR] Build failed with 23 errors:

  ../imports/URLImport.js:4:11: ERROR: Top-level await is not available in the configured target
  environment ("es2020")
  ../imports/URLImport.js:5:24: ERROR: Top-level await is not available in the configured target
  environment ("es2020")
  ../imports/URLImport.js:6:9: ERROR: Top-level await is not available in the configured target
  environment ("es2020")
  ../imports/URLImport.js:9:19: ERROR: Top-level await is not available in the configured target
  environment ("es2020")
  ../imports/URLImportInstaller.js:4:9: ERROR: Top-level await is not available in the configured
  target environment ("es2020")
  ...

If you think this is a bug then please create an issue at https://github.com/cloudflare/wrangler2/issues/new/choose

There may be more ways to avoid using a top-level await within a worker -- for example, within a request handler, you can specify pass a promise to ctx.waitUntil. I understand, though, that this harms code readability as well.
There's an open issue with the bundler we use internally to support top-level await, and from skimming quickly it looks like while it would be technically possible for us to support TLA, the actual implementation is not ideal.
I'll keep this issue open for now as a way of tracking https://github.com/evanw/esbuild/issues/253, so that once support is added in esbuild we can enable it within wrangler -- but given that the last update was about a year ago, I don't anticipate this being added any time soon.

hmm... the approach I proposed above might trigger "The script will never generate a response." error described in https://github.com/cloudflare/workerd/issues/210 if the runtime is hit by two requests while awaiting the initialization.

I tried various things (especially using context.waitUntil) to make the top level await work, but nothing worked reliably, so I ended up resorting to the only thing that does seem to work reliably:
main.ts:
export default {
  async fetch(request, environment, context) {
    const myWorker = (await import('./my-worker')).default;
    return myWorker.fetch(request, environment, context);
  }

my-worker.ts:
const workerInit = Promise.resolve('yay, it works!');

export default {
  async fetch(request, environment, context) {
    await workerInit;
    ...
  }
}

I believe that this is now resolved with fix for #2716, there is still an issue related to https://github.com/cloudflare/workerd/issues/389 and https://github.com/cloudflare/workerd/issues/402 but those should be tracked separately.

to clarify, I verified that top-level await works as expected except for that odd issue with esbuild, which I think stems from awaiting WASM events.


DAWN-371 ⁃ account_history_plugin get accounts not returning account for key

Calling:
$ programs/eosc/eosc H testnet2.eos.io p 80 get account shop1
returns:
{
"account_name": "shop1",
"eos_balance": "10.9999 EOS",
"staked_balance": "0.0001 EOS",
"unstaking_balance": "0.0000 EOS",
"last_unstaking_time": "1969-12-31T23:59:59",
"permissions": [{
"perm_name": "active",
"parent": "owner",
"required_auth": {
"threshold": 1,
"keys": [{
"key": "EOS7ZYeiRznTn3JobujogjAf3gQitfNcDrqm7n79Zwpehj2EoXLqu",
"weight": 1
}
],
"accounts": []
}
},{
"perm_name": "owner",
"parent": "",
"required_auth": {
"threshold": 1,
"keys": [{
"key": "EOS8bxfgV9F3aH4oxeqvM2a1LbAa8k5Zw9nxUwBgU16dEFXDGbEFv",
"weight": 1
}
],
"accounts": []
}
}
]
}
but then calling:
programs/eosc/eosc H testnet2.eos.io p 80 get accounts EOS8bxfgV9F3aH4oxeqvM2a1LbAa8k5Zw9nxUwBgU16dEFXDGbEFv
or:
programs/eosc/eosc H testnet2.eos.io p 80 get accounts EOS7ZYeiRznTn3JobujogjAf3gQitfNcDrqm7n79Zwpehj2EoXLqu
doesn't return any account_names. (Repeating the command many times produces the same result, so it is not an issue of some nodes having the data and others not)

Retested on latest code an everything looks good


tile_size_bytes must be 4 or desyncs after 6c24b029969d4b8d1e7a9b184caf3f1fe9a5c13a

smells like a decoder bug

I believe this is already resolved?

Wondering if this is still an issue?

I think it's fixed after other errors were found in the uncompressed header.


⚠ Bofrost.lu has degraded performance

In c4150a4, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1823 ms

Resolved: Bofrost.lu performance has improved in 7b92a1a after 6 minutes.


Empty alert in the Sharding section

There is an empty alert in the Sharding section
Url: https://docs.microsoft.com/en-us/azure/architecture/patterns/sharding#when-to-use-this-pattern

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

ID: 050bb1fd-56ca-63bc-b105-17a56e3b0362
Version Independent ID: ce84d0a7-3596-e259-dfc3-a9789efd9948
Content: Sharding pattern - Cloud Design Patterns
Content Source: docs/patterns/sharding.md
Service: architecture-center
Sub-service: cloud-fundamentals
GitHub Login: @dragon119
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#269832

Thank you for noticing this.  We've applied the change and it will go out with next scheduled publish.


add turborepo support

Add turborepo support. Add command for build and test.

I force-pushed some new changes. Please remove the rest of test:build commands


Di 1289 restore fuctionality to pass dir path as an input

This change is

Summary by CodeRabbit

New Features

Updated application version to 2.1.0.
Introduced a new function to retrieve job output directories.
Added a new test case for validating output directory handling.

Bug Fixes

Enhanced error handling for job outputs and fastq file validation.

Documentation

Improved logging for output retrieval processes.

Refactor

Streamlined test structure for better maintainability.
Updated input handling logic to integrate job outputs effectively.

Hello @Yu-jinKim! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file resources/home/dnanexus/run_workflows/utils/manage_dict.py:

Line 18:1: E402 module level import not at top of file


Handling Rest Request in Separte Thread

How to handle rest request in separate thread properly. I prepared exemplary code as below:
#include <pistache/endpoint.h>
using namespace Pistache;
struct HelloHandler : public Http::Handler
{
HTTP_PROTOTYPE(HelloHandler)
void onRequest(const Http::Request& request, Http::ResponseWriter writer) {
std::cout << " Handle Request" << std::endl;
std::thread thr([](Pistache::Http::ResponseWriter resW)
    {
        std::cout << "In thread" << std::endl;
        resW.send(Pistache::Http::Code::Ok, "{\"test\" : \"test1\"}");
    }, std::move(writer));
    thr.detach();
}

};
int main() {
Http::listenAndServe("*:9080");
}
Pistache server responds properly and then terminates itself with:
terminate called after throwing an instance of 'Pistache::Async::BadType'
what():  Argument type can not be used to resolve the promise  (TypeId does not match)
Aborted (core dumped)
I checked also std::move(writer.clone()) instead of std::move(writer) and nothing changed.
Does anyone know what is wrong?

mersen, did you get pistache to respond to request from other computer?  I am trying to get it to work to no avail.

hoang408: Pistache.io works fine over a network connection from other computers.
Have you verified that it is listening on the expected TCP post ("netstat -tanp" if on Linux)?
Have you verified the host firewall settings on both the client and server systems?
Do you have a network firewall between them?
Have you ran "tcpdump", "wireshark" or similar network sniffing tools on both computers while attempting your experiment?
Have you ran "netcat" in listen mode on the server computer, on the port that you wish to assign to pistache.io, and tried to connect to see if netcat (/usr/bin/nc) can accept a TCP connection on that port)?
Have you ran "strace", "ptrace" or "truss" or whatever task-level user/kernel syscall logger against your pistache.io process to observe its behavior while starting up and when receiving a TCP SYN?

It seems that I commented in the wrong bug.  I apologize.  I'll move my comment.

I was not trying to do request to different computer

Problem was in separate commit taken to master branch form external repo. Problem is not present in master branch.


Package proposal: everything.vm

Package Name
everything
Tool Name
everything
Package type
ZIP_EXE
Is the tool a console application?
false
Tool's version number
<IP_ADDRESS>4
Category
Utilities
Tool's authors
voidtools
Tool's description
Search Everything
Download URL
https://www.voidtools.com/Everything-<IP_ADDRESS>4.x64.zip
Download SHA256 Hash
4BE0851752E195C9C7F707B1E0905CD01CAF6208F4E2BFA2A66E43C0837BE8F5
Dependencies
No response
Why is this tool a good addition?
Easier & more efficient search operations in the vm.

There is already a chocolatey community package for these tool and as it is not a security/malware analysis tool, I think we do not need a custom package in this repository. @SolitudePy is there any problem with using the chocolatey community package (for example installing it with choco install everything or adding it to your config.xml)?

@Ana06 isnt the purpose of this vm is to make it as efficient? Hence the reason there is categories for utilities&productivity.

We could add the tool to Productivity Tools. @mandiant/vms opinions?
@SolitudePy even if we add a package for this tool, the question is still if we could use the community package (and have a metapackage instead of installing the tool from a zip)? @SolitudePy have you tried to install the community package? is there any issue with it? Note we have automation to update metapackages, which means our bot would take care to update the package if there is a new community package version.

@Ana06 Yes I tried and it worked fine

This would be very easy to add during the install process by adding everything to your profile, since it is a community package it will be found and installed. Usually we don't create wrappers for tools unless there is a reason like disabling startup services, removing desktop icons, or some other efficiency improvement. @SolitudePy were there any issues like that after installing?

@day1player there were no issues

I am a fan of everything, it really improves the search ability on windows

@SolitudePy @stevemk14ebr I think since there are no issues with the package that would require a wrapper this should be a feature request on the respective VM repos. I have created one for Commando here. I will leave creating the issue in the Flare-VM repo to @Ana06. Thank you!

I'd prefer not installing it as default. The usage of everything probably low, and might add chaos when it index files and noisy when analysing malware, for e.x: the events added into filemon.

@binjo

might add chaos when it index files and noisy when analysing malware, for e.x: the events added into filemon.

does this happen if the tool is installed even if it is not used?

based on the doc#How is the Everything service started?, index file service is automatic.

@binjo raises a good point I had not considered that

While it does seem to be a little noisy in ProcMon, it seems to be significantly less than other things that fill the feed (svchost, explorer.exe, dwm.exe, services.exe, etc.) and it can easily be excluded in the filters. I almost always have a filter set to specifically only include certain things myself, so this doesn't seem to be much of a problem to me, unless I'm not thinking of something?
As far as adding it to the default, I do know it's a very useful tool that I'd like to have it if possible, barring any issues that I may be missing or if others think that the extra noise created may be more harmful than not.

We have recently introduced a Productivity Tools category to make it easier to find some of the tools we install and I can see everything fitting there. I am ok with both adding everything directly to the FLARE-VM default configuration (which installs it using the community package without a link in the Tools\Productivity Tools folder) and with creating a metapackage (which installs it in the same way using the community package and creates a link in the Tools\Productivity Tools folder) and adding the metapackage to the default configuration. @mandiant/flare-vm @SolitudePy opinions on which option do you prefer?

based on the doc#How is the Everything service started?, index file service is automatic.

Sounds like we actually do need a wrapper then, and as to whether it is included in the profiles, that should still be a separate issue.

@binjo raises a good concern. But I agree with @emtuls that it could still be added to the default configuration as we can easily exclude it from procmon and it is a useful tool.


Fantasy wallet refactor

This is ready for review.
TODO:

[x] improve validation (do per field validation and compose into yup schema)

[x] test clientside
[x] test serverside
[x] document changes
[x] add validation for vaultEntries

[x] debug config checking
[x] debug vault post-changes
[x] debug device sync flow
[ ] test all send wallets
[ ] test all receive wallets
[x] enable/disable all wallets
[x] test autowithdraw
[x] test p2p zaps

Mhh, there is a conflict between synched and unsynched sessions.
repo:

Log-in from two sessions:  session1 and session2
Enable device sync in session1 only
Attach a nwc sender in  session1
Attach a different nwc sender (i use the same url with &v=2) in session2

session1 will detach and lose the sender config

I've notice that if you have more devices with conflicting configs, the last one to join the vault overwrite the others, maybe from an UX standpoint it is better to do the other way around, so you can connect first the main device and then let the other merge the missing configs.

Nice catch. I didn't test this combo. An empty, unsynced config shouldn't overwrite a synced config.

I've notice that if you have more devices with conflicting configs, the last one to join the vault overwrite the others, maybe from an UX standpoint it is better to do the other way around, so you can connect first the main device and then let the other merge the missing configs.

A generalized description of this problem is that, as a result of this pr, an unsynced wallet will not be aware of the vault entries so - when there aren't receive creds on save, it deletes the server wallet. However an unsynced wallet should be allowed to remove the receive creds.
The clearest solution likely introduces a new mutation to only remove receive creds, but that's not very easy because our wallet mutations are generated.
Anyway, that's where I'm at on this problem. Thanks for finding it!

I've notice that if you have more devices with conflicting configs, the last one to join the vault overwrite the others, maybe from an UX standpoint it is better to do the other way around, so you can connect first the main device and then let the other merge the missing configs.

I think we're going to let it fly as is. You're right though that the first device might be their primary and have more important config. I just don't think it's likely these conflicts happen much in practice, this pr has taken me long enough, and we plan to excavate most of this code again to refine the attachment flows.


Fix various documentation, user-facing, and source comment typos

Found using codespell -q 3 -S ./options/locale,./vendor -L ba,pullrequest,pullrequests,readby

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@9543e06). Click here to learn what that means.
The diff coverage is 8.33%.

@@           Coverage Diff           @@
##             main   #16367   +/-   ##
=======================================
  Coverage        ?   45.51%
=======================================
  Files           ?      709
  Lines           ?    83741
  Branches        ?        0
=======================================
  Hits            ?    38111
  Misses          ?    39498
  Partials        ?     6132

Impacted Files
Coverage Δ

cmd/dump.go
0.91% <0.00%> (ø)

cmd/hook.go
0.00% <ø> (ø)

cmd/migrate_storage.go
0.00% <0.00%> (ø)

cmd/web_letsencrypt.go
0.00% <ø> (ø)

models/branches.go
44.71% <0.00%> (ø)

models/context.go
52.00% <ø> (ø)

models/error.go
39.68% <0.00%> (ø)

models/issue_comment.go
52.72% <ø> (ø)

models/issue_dependency.go
62.68% <ø> (ø)

models/login_source.go
28.64% <ø> (ø)

... and 44 more

Continue to review full report at Codecov.

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

Shall i squash the commits down? BTW, 'm submitting upstream fixes to the iframe-resizer lib as well soon.

we do squash merge every pull @luzpaz  so it's better to not squash so reviewers know what has changed.
thanks for asking and good to hear to see it upstream fixed too ;)


Felinids in duffelbags are immune to almost all damage

Description

Currently Felinids hiding in a duffel bag has the following issues:

They benefit from complete immunity against projectiles/lasers based guns while still able to shoot out of it. This can (and has been) be abused by people to drain Nuclear Operatives Shuttle turrets of ammo. It can also results in unfair firefights.
They are also immune to melee attacks but you can just open the duffelbag and click them out.
Explosions doesn't seem to affect Felinids that are inside the bag, wherever the source is from the outside or caused by the Felinid in said bag. This include the nuke explosion too.

Reproduction

Be a felinid, go in a duffel bag. Gain immunity against every damage but space air.
Media

Shooting
https://user-images.githubusercontent.com/9823203/232238732-dd641727-ae8a-4d9d-b384-9062c46c67f9.mp4

Outside explosion
https://user-images.githubusercontent.com/9823203/232238183-4532e314-24aa-47dd-9c47-f3053fa7d544.mp4

Inside explosion
https://user-images.githubusercontent.com/9823203/232238798-e7eb73a8-c602-408f-b6f0-a9bb00e3db74.mp4

General issue with containers

and so any fix should probably fix containers more generally or at least start to address them


Track 2 SDK class naming problem

Hi, I'm trying to migrate azure-mgmt-containerservice to track 2 in azure-cli for acs module and I find the following two weird class name changes (track 1 -> track 2):
ManagedClusterIdentityUserAssignedIdentitiesValue -> Components1Umhcm8SchemasManagedclusteridentityPropertiesUserassignedidentitiesAdditionalproperties
ManagedClusterPropertiesIdentityProfileValue -> ComponentsQit0EtSchemasManagedclusterpropertiesPropertiesIdentityprofileAdditionalproperties

I find that this name change occurred since the first Track 2 SDK release (14.0.0, the latest version is 15.1.0).

@FumingZhang my bet is this is due to naming conflicts between your swaggers, and thus passing modelerfour.lenient-model-deduplication when generating, as these appear to be names generated by modeler four to avoid name clashes. In track 2, we're more strict with name clashes, so my recommendation is to fix the swagger so that these names don't clash.
I'm going to close this issue since this is by design, please open it again if you think otherwise. Thanks!

Took a closer look at the second issue filed with this error, I left a comment here that I think should help with your issue

Thanks for your reply and I think it explains the above two cases. However, I found another case as follows (swagger -> track 2):
ManagedClusterProperties -> Components1Q1Og48SchemasManagedclusterAllof1

There is no such class in track 1 SDK, it's only provided in track 2 SDK. As defined here, it's not an AdditionalProperties of some other property, so I am confused why this property still gets a weird generated class name in track 2 SDK.

FIX:
I would suggest doing this instead
"ManagedCluster": {
  "properties": {
    "sku": {
      "$ref": "#/definitions/ManagedClusterSKU",
      "description": "The managed cluster SKU."
    },
    "extendedLocation": {
      "$ref": "#/definitions/ExtendedLocation",
      "description": "The extended location of the Virtual Machine."
    },
    "identity": {
      "$ref": "#/definitions/ManagedClusterIdentity",
      "description": "The identity of the managed cluster, if configured."
    }
  },
  "allOf": [
    {
      "$ref": "#/definitions/Resource"
    },
    {
      "$ref": "#/definitions/ManagedClusterProperties"
    }
  ],
  "description": "Managed cluster."
}

Reason for change: You can see in the allOf, you're really creating a new object here. This object doesn't have a name, so that's why modelerfour gives it that ugly name.


Cannot install RMF from apt

Hi, I'm trying to install RMF from apt by following this tutorial. In the Setup Sources and Installation of RMF section it says:
Next you will need to setup the source of RMF packages similar to the previous two steps. First authorizing the key:
curl -s http://rmf.servehttp.com/repos.key | sudo apt-key add -

Secondly adding the repository to the apt sources:
sudo sh -c 'echo "deb http://rmf.servehttp.com/ubuntu/main/ `lsb_release -cs` main" > /etc/apt/sources.list.d/rmf.list'

And now we are ready to install. Let's update our packages:
sudo apt-get update

Finally, the following installs a basic set of packages that should get you going with RMF:
sudo apt-get install ros-foxy-ament-cmake-catch2 ros-foxy-building-gazebo-plugins ros-foxy-building-map-msgs ros-foxy-building-map-tools ros-foxy-rmf-cmake-uncrustify ros-foxy-rmf-dispenser-msgs ros-foxy-rmf-door-msgs ros-foxy-rmf-fleet-adapter ros-foxy-rmf-fleet-msgs ros-foxy-rmf-lift-msgs ros-foxy-rmf-task-msgs ros-foxy-rmf-traffic-msgs ros-foxy-rmf-traffic-ros2 ros-foxy-rmf-traffic ros-foxy-rmf-utils ros-foxy-traffic-editor

But when running the first command, curl -s http://rmf.servehttp.com/repos.key | sudo apt-key add -, I get this error.
gpg: no valid OpenPGP data found.

Likewise, running basic curl to get the key curl http://rmf.servehttp.com/repos.key returns
curl: (7) Failed to connect to rmf.servehttp.com port 80: Connection refused

Consequently, running sudo apt-get update has some error and sudo apt-get install ... returns package not found.
Some info that might be useful, I'm using Ubuntu 20.04. ROS is inside docker container with image pulled from osrf/ros/foxy-desktop-focal.
Any help would be appreciated, thanks!

Okay, thanks! I ended up using the demo docker image for now. Will try installing the binary again when I start developing.
Is there a timeline for the updated tutorial? Seems that some parts are also missing.


improve, clarify getting started tutorial steps

What's changed

Clarified file creation steps in part 2 of Getting Started tutorial based on user feedback

Reviewers
@mstanleyjones @johndmulhausen
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

@johndmulhausen I think I've gotten all these comments addressed, let me know if this is good to go, and feel free to approve and merge.

LGTM thanks, @londoncalling :)


abandon flexup OSD with system disk?

This is our current implementation about "flexup OSD":
User submit a flexup OSD request (only contains instance number and profile osd), ceph-mesos just choose a host (randomly) to launch OSD:

If the host has configured disk and is available, it will use this disk to launch OSD
If the host has no disk available, it will start OSD with the system disk.
But randomly choosed host will cause this: there may be OSDs running with system disk, but other hosts has available disks there. I think this is not user friendly.

I think there are three solutions:

Extend flexup request format {instance:2,profile:osd,host:mm0101}. Then ceph-mesos can just find this host and start OSD with available disk or system disk (if no disk).
Keep the flexup format unchanged but implement a policy in ceph-mesos. Ceph-mesos will find a host with available disk to lauch. If no available disks in a certain period of time , then it will randomly choose a host.
Just don't allow system disk osd. If no available disk, do nothing

any ideas?

I think system disk should be allowed for simple tests. The system should also work on a single node with one NIC and one HDD and still support multiple OSD. I think we should use Mesos's "attributes" (https://open.mesosphere.com/reference/mesos-slave/) and put it in the "flexup" API spec. Keeping a separate policy is not how ceph management is done in general so we shouldn't bring up a new problem.

yes. let's added attributes in flexup