Add support for OIDC during Codespaces prebuild

Update the external-repository feature so that it can obtain a token using OIDC during Codespaces prebuild.
The Azure token can be obtained using this code:
response=$(curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN"
"$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange")
federatedToken=$(echo $response | jq -r '.value')

Once the token is obtained it can be used to login to Azure and then get a token for Azure DevOps:
az login --service-principal -u $AZURE_CLIENT_ID --tenant $AZURE_TENANT_ID
--federated-token "$federatedToken"
az account set --subscription $AZURE_SUBSCRIPTION_ID
# This token can be used for further authentication (eg. with NPM, NuGet etc)
export ARTIFACTS_ACCESSTOKEN=$(az account get-access-token --tenant
$AZURE_TENANT_ID --query accessToken -o tsv)

I am thinking the feature should be enhanced to add new optional parameters for AZURE_CLIENT_ID, AZURE_TENANT_ID and AZURE_SUBSCRIPTION_ID and the presence of values in those parameters will trigger this code path at run time during the external-git clone process

This is done as of version 4 of the feature


Multiple worlds

Will be delayed for a bit, the plugin must be almost completely rewritten (A change that should definitely happen soon to clean things up, but not right now)

I don't know about this, because I think BungeeCord or Waterfall would be a better fix than I could do


wrong variable in VRTK_MoveInPlace : DetermineAverageControllerRotation

NOTE: Any issue that does not follow the below template will be immediately closed and not re-opened until the template structure is adhered to.

Precheck

Do not use the issues tracker for help or support (try VRTK Slack channel, Stack Overflow, etc.)
For proposing a new feature, please check existing open and closed issues before creating a duplicate
For bugs, do a quick search and make sure the bug has not yet been reported
Finally, be excellent to each other, and party on dudes!

Environment

Source of VRTK (Unity Asset Store or Github)
Version of VRTK (Unity Asset Store/Github release number) (Github master commit hash)
Version of Unity3D (e.g. Unity 5.4.4f1)
Hardware used (e.g. Vive/Oculus)
SDK used (e.g. OpenVR/SteamVR/Oculus Utilities)

Steps to reproduce
Attempt to recreate the issue in a VRTK example scene and provide steps to reproduce in a clear text step by step list. Include code samples, errors and stacktraces if appropriate.
Expected behavior
VRTK_MoveInPlace
method DetermineAverageControllerRotation
line 442 currently is
        // Left controller only
        else if (controllerRightHand != null && controllerRightHand == null)

where it should be
        // Left controller only
        else if (controllerLeftHand != null && controllerRightHand == null)

Current behavior
would fail under certain condition.

https://github.com/thestonefox/VRTK/commit/f5708a0ab1696f9bec351cdc60e8819722484f90


feat: add AddReference method to References

Description of your changes
@haarchri was helping at https://github.com/crossplane-contrib/provider-upjet-digitalocean/pull/41 (thank you), and during the code review, I noticed a oversee where he replaced the existing r.References as follow:
diff --git a/config/provider.go b/config/provider.go
index 83eada3..8e69d59 100644
--- a/config/provider.go
+++ b/config/provider.go
@@ -294,13 +294,9 @@ func GetProvider() *ujconfig.Provider {
 			Type:          referenceType(pc, “project”, “v1alpha1", “Project”),
 			TerraformName: “digitalocean_project”,
 		}
-
-		r.References = map[string]ujconfig.Reference{
-			“forwarding_rule.certificate_name”: {
-				TerraformName: “digitalocean_certificate”,
-			},
+		r.References[“forwarding_rule.certificate_name”] = ujconfig.Reference{
+			TerraformName: “digitalocean_certificate”,
 		}
-
 	})
 	pc.AddResourceConfigurator(“digitalocean_domain”, func(r *ujconfig.Resource) {
 		r.ShortGroup = “dns”

I am glad that I saw the diff, but honestly, this is a straightforward thing to miss when they are so much code-generated files noise, or people tend to ignore those.
As @haarchri explained, "That's why I prefer this, for example, https://github.com/crossplane-contrib/provider-upjet-aws/blob/main/config/elbv2/config.go#L13," which is a really common scenario.
I never considered using the existing style. I didn't think much about it. He didn’t try to break things. Still, we ran into the issue. Since we are talking about "style" here, it is really difficult to be objective and define who is more proper.
So, the fix here is to expose an SDK API that avoids such a mistake.
I am not proposing adding getters and setters everywhere either, just reacting to the situation and figuring out how to mitigate the issues in the future; as I usually say, "let the code teach you what to do, not the other way around."
I have:

[ ] Read and followed Upjet's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Unit Testing

A few things from this,

Should all documentation and code-generated code be updated to this?
Should References be a private field instead of exposing it? You can still assign r.References. Ideally, Provider Authors shouldn't care about replacing the entire r.References, and in that case, we can add r.ReplaceReferences(references), but I am not sure when this would be necessary.


Scalpel Fails on Single Sample

I know there is a Scalpel page on Sourceforge but no users seem to post there.  Can any community members assist?

I installed Scalpel as indicated in this paper and finally got it to run, but it fails within seconds and not sure why.  New to Linux so can you me if the problem is my   input and/or the installation?  I've spent 3 weeks on this.  :-(   Or is there another way to run the same analysis?  I need to find indels (not SNPs) on chromosome 15, thanks. :-)
$ perl /mnt/d/scalpel-0.5.4/scalpel-discovery --single --bam /mnt/d/scalpel-0.5.4/MC-files/MC-fish.marked_duplicates.bam --bed 15:1-48040578 --ref /mnt/d/scalpel-0.5.4/MC-files/danRer11.fa --window 600 --numprocs 4
Program: scalpel-discovery (micro-assembly variant detection)
Version: 0.5.4 (beta), January 11 2018
Contact: Giuseppe Narzisi<EMAIL_ADDRESS>START ANALYSIS
-- Print parameters to /mnt/d/scalpel-0.5.4/outdir/parameters.txt
Loading targets region: 15:1-48040578
Loading genome from FASTA file...1923 sequences.
Assembly Exons
start assembly of 480402 regions.
stepSize: 120101
Undefined sequence (15)
Command failure: FindVariants (/mnt/d/scalpel-0.5.4/FindVariants.pl --bam /mnt/d/scalpel-0.5.4/MC-files/MC-fish.marked_duplicates.bam --bed 15:1-48040578 --ref /mnt/d/scalpel-0.5.4/MC-files/danRer11.fa --kmer 25 --covthr 5 --lowcov 2 --mincov 5 --covratio 0.01 --outratio 0.05 --radius 100 --window 600 --maxregcov 10000 --step 100 --mapscore 1 --mismatches 3 --pathlimit 1000000 --dir /mnt/d/scalpel-0.5.4/outdir --numprocs 4 --format vcf --seed 0 --coords null)...
child exited with value 25
Discovery: elapsed time: 0 day(s) 0 hour(s) 0 minute(s) 16 second(s)

Hi @eeleclair,
It looks like this is the source of your problem: Undefined sequence (15)
I think --bed 15:1-48040578 is the problem. I'm guessing that your BAM file has a different chromosome naming than 15, maybe it has names like chr15?
Hope that helps!

Hi @eeleclair,
It looks like this is the source of your problem: Undefined sequence (15)
I think --bed 15:1-48040578 is the problem. I'm guessing that your BAM file has a different chromosome naming than 15, maybe it has names like chr15?
Hope that helps!

That helped a lot, it seems to have started to run.  But is it normal to take >24 hours to analyze one chromosome?  The CPU is still busy but I don't see any output files after an entire day.

That helped a lot, it seems to have started to run.  But is it normal to take >24 hours to analyze one chromosome?  The CPU is still busy but I don't see any output files after an entire day.

Hi @eeleclair,
scalpel is very slow on whole genomes, so if you are running on whole genomes then it will take a long time. We recommend using a different caller on whole genomes; depending on the size of indels you want to call, different callers do a better job. Manta would be a good choice though.

Hi @eeleclair,
scalpel is very slow on whole genomes, so if you are running on whole genomes then it will take a long time. We recommend using a different caller on whole genomes; depending on the size of indels you want to call, different callers do a better job. Manta would be a good choice though.

Hello again, thanks so much for your feedback.  But I'm only running on one
chromosome... shouldn't that get it done in 1/20th the time?  Just looking
for an overall estimate as I've never run this type of analysis before.
On Thu, Jan 21, 2021 at 8:49 AM Rory Kirchner<EMAIL_ADDRESS>wrote:

Hi @eeleclair https://github.com/eeleclair,
scalpel is very slow on whole genomes, so if you are running on whole
genomes then it will take a long time. We recommend using a different
caller on whole genomes; depending on the size of indels you want to call,
different callers do a better job. Manta would be a good choice though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bcbio/bcbio-nextgen/issues/3420#issuecomment-764695251,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASCBRL2FSIO7XFJ5HI3LI3DS3A5IVANCNFSM4WJIBJKQ
.

Hello again, thanks so much for your feedback.  But I'm only running on one
chromosome... shouldn't that get it done in 1/20th the time?  Just looking
for an overall estimate as I've never run this type of analysis before.
On Thu, Jan 21, 2021 at 8:49 AM Rory Kirchner<EMAIL_ADDRESS>wrote:

Hi @eeleclair https://github.com/eeleclair,
scalpel is very slow on whole genomes, so if you are running on whole
genomes then it will take a long time. We recommend using a different
caller on whole genomes; depending on the size of indels you want to call,
different callers do a better job. Manta would be a good choice though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bcbio/bcbio-nextgen/issues/3420#issuecomment-764695251,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASCBRL2FSIO7XFJ5HI3LI3DS3A5IVANCNFSM4WJIBJKQ
.

Hi @eeleclair,
In the scalpel paper, it takes 5 hours to run a reasonable depth whole exome with scalpel with 10 cores and 64 GB of RAM, and that's 2% of the genome so you'd expect a single chromosome to take around double that with 10 cores. There may be algorithm issues that make it even slower on whole genomes as well. The takeaway is scalpel is really slow on whole genomes so we don't recommend using it for them.

Hi @eeleclair,
In the scalpel paper, it takes 5 hours to run a reasonable depth whole exome with scalpel with 10 cores and 64 GB of RAM, and that's 2% of the genome so you'd expect a single chromosome to take around double that with 10 cores. There may be algorithm issues that make it even slower on whole genomes as well. The takeaway is scalpel is really slow on whole genomes so we don't recommend using it for them.

Oh I'm just noticing this is Zebrafish, I'm not sure how scalpel will run on Zebrafish WGS, we haven't actually done that. Are you specifically looking for indels? If you are just looking for SNPs and short indels I would just run GATK HaplotypeCaller on it, that is our standard method for calling on model organisms.

Oh I'm just noticing this is Zebrafish, I'm not sure how scalpel will run on Zebrafish WGS, we haven't actually done that. Are you specifically looking for indels? If you are just looking for SNPs and short indels I would just run GATK HaplotypeCaller on it, that is our standard method for calling on model organisms.


fix: Readme update and fixes

Earth-2 MIP Pull Request
Description

Fixing some issues with the main readme
Closes: https://github.com/NVIDIA/earth2mip/issues/11 , https://github.com/NVIDIA/earth2mip/issues/13
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.

Dependencies

/blossom-ci

/blossom-ci


fails when validating links to starlight-openapi pages

Describe the bug
Thanks for the very useful plugin! It has already prevented quite a few mistakes :smile:

We're using  starlight-openapi to generate our API reference, but this seems to result in an issue when combined with starlight-links-validator.
Links to the generated pages from inside markdown content are reported to be invalid while they actually are valid.
For example, when running npm run build in the example:
17:57:07 [ERROR] ✗ Found 1 invalid link in 1 file.
17:57:07 ▶ /
17:57:07   └─ /api/operations/users - invalid link

To Reproduce
Minimal Reproducible example
Steps to reproduce:

Create a new starlight project.
Install and configure starlight-links-validator.
Install and configure starlight-openapi.
Add a sample openapi spec.
Link to /api/operations/users from src/content/docs/index.mdx.
Run npm run build.

Expected behavior
There should be no validation errors, the generated pages exist.
How often does this bug happen?
Every time
System Info
No response
Additional Context
I found the following while digging in the code:

For the generated pages, fileHeadings ends up being undefined here.
This then leads to an error being triggered in the next lines.

I temporarily patched this with the below patch, but I don't have the full context to judge whether this is actually correct. It could also be that this is more suitably fixed in starlight-openapi instead.
diff --git a/libs/validation.ts b/libs/validation.ts
index a1754ab0369f105595a1ad517f3716f4ca05a543..2cee13b21751fcca791c1a93d5ac8febc820731c 100644
--- a/libs/validation.ts
+++ b/libs/validation.ts
@@ -140,7 +140,7 @@ function validateLink(context: ValidationContext) {
   const isValidPage = pages.has(sanitizedPath)
   const fileHeadings = getFileHeadings(sanitizedPath, context)

-  if (!isValidPage || !fileHeadings) {
+  if (!isValidPage) {
     addError(errors, filePath, link, ValidationErrorType.InvalidLink)
     return
   }
@@ -150,7 +150,7 @@ function validateLink(context: ValidationContext) {
     return
   }

-  if (hash && !fileHeadings.includes(hash)) {
+  if (hash && (!fileHeadings || !fileHeadings.includes(hash))) {
     addError(errors, filePath, link, ValidationErrorType.InvalidAnchor)
     return
   }

Thanks for the detailed feedback :raised_hands:
The Starlight OpenAPI uses Starlight custom pages to render the API documentation which cannot be validated by this plugin. To accommodate this, the exclude option was added to the plugin to mark one or multiple links as safe to ignore, e.g. auto-generated links, production-only redirects, etc.
In the case of the OpenAPI plugin, the configuration would look like this:
export default defineConfig({
  integrations: [
    starlight({
      plugins: [
        starlightLinksValidator({
          exclude: ["/api/**/*"],
        }),
      ],
    }),
  ],
});

Automatically generated links are expected to be valid and if they are not, this would be a bug in the Starlight OpenAPI plugin itself.


v2 flicker in UICatalog

Describe the bug
When exiting or opening a scenario I get a flicker in the terminal (Windows Terminal) and a new line seems to get written to black screen before scenario window appears.

This is actually a result of an improvement in the ConsoleDrivers where they now clean up resources correctly on Application.End.
Remember UI Catalog is an App and each scenario is an App.  You are seeing what's in the terminal before/after each app Begin/Ends.
To fix this we would need to clear the underlying screen buffer, which would cause the terminal back-buffer to be cleared.

OK cool, I hadn't realised that each scenario was a separate App
start/shutdown.
Thats fine then.
On Sat, 14 Oct 2023, 05:54 Tig, @.***> wrote:

This is actually a result of an improvement in the ConsoleDrivers where
they now clean up resources correctly on Application.End.
Remember UI Catalog is an App and each scenario is an App. You are seeing
what's in the terminal before/after each app Begin/Ends.
To fix this we would need to clear the underlying screen buffer, which
would cause the terminal back-buffer to be cleared.
—
Reply to this email directly, view it on GitHub
https://github.com/gui-cs/Terminal.Gui/issues/2903#issuecomment-1762596767,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHO3C5HVMUUDG6ID5W6IS3LX7ILIXANCNFSM6AAAAAA56W2OPQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


updated instruction to correct file path

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "patch-1" git@github.com:s093294/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Oh! thanks @s093294 !
LGTM
ping @SvenDowideit @moxiegirl

LGTM @s093294 thank you for the contribution!


NonNullType has been moved, but Loader is referencing to a old place

Describe the bug

We upgraded from version ^2.9.0 to 3.0.0 and got an error in the console.

PHP Warning:  PHP Startup: Failed to open stream: No such file or directory in /home/vendor/azjezz/psl/src/Psl/Internal/Loader.php on line 943
PHP Fatal error:  Uncaught Error: Failed opening required '/home/vendor/azjezz/psl/src/Psl/Type/Internal/NonNullType.php' (include_path='.:/usr/local/lib/php') in /home/vendor/azjezz/psl/src/Psl/Internal/Loader.php:943
Stack trace:
#0 //vendor/azjezz/psl/src/Psl/Internal/Loader.php(954): Psl\Internal\Loader::load('Psl/Type/Intern...')
#1 [internal function]: Psl\Internal\Loader::Psl\Internal\{closure}('Psl\\Type\\NonNul...')
#2 /home/vendor/azjezz/psl/src/Psl/Internal/Loader.php(1011): class_exists('Psl\\Type\\NonNul...')
#3 /home/vendor/azjezz/psl/src/Psl/Internal/Loader.php(936): Psl\Internal\Loader::loadClasses()
#4 /home/vendor/azjezz/psl/src/Psl/Internal/Loader.php(960): Psl\Internal\Loader::Psl\Internal\{closure}()
#5 /home/vendor/azjezz/psl/src/Psl/Internal/Loader.php(932): Psl\Internal\Loader::autoload(Object(Closure))
#6 /home/vendor/azjezz/psl/src/preload.php(9): Psl\Internal\Loader::preload()
#7 /home/config/preload.php(7): require('/home/vend...')
#8 {main}
  thrown in /home/vendor/azjezz/psl/src/Psl/Internal/Loader.php on line 943

In commit https://github.com/azjezz/psl/commits/d68cd6be64a1fe7355fc02669cc6fa6440294799/src/Psl/Type/NonNullType.php
and PR https://github.com/azjezz/psl/pull/478 the type has been moved into the global "namespace".
But in the Loader only the namespace was updated, not the path. The loader has still a reference to a non existing file yet -> https://github.com/azjezz/psl/blob/3.0.0/src/Psl/Internal/Loader.php#L711C56-L711C67
A deep look
Expected behavior
NonNullType is loaded from the correct place.
Psl\\Type\\NonNullType' => 'Psl/Type/Internal/NonNullType.php', -> Psl\\Type\\NonNullType' => 'Psl/Type/NonNullType.php',
Environment (please complete the following information):

PHP version 8.3
Version 3.0.0

Additional context
Add any other context about the problem here.

Thanks for reporting and fixing!
It's released under https://github.com/azjezz/psl/releases/tag/3.0.1


Doesn't work on mobile devices

Working fine on desktop computers but can not drag on mobile devices. Thanks

Did you include touch-punch.js?
This library is supposed to automatically make dragging work on mobile devices.

Most probable you didn't include touch-punch.js. JQuery UI doesn't work properly on mobile devices without this library.
Please feel free to re-open the issue if you still experiencing the problem after all.

I have added touch-punch.js but it's still not working on mobile devices.


Elements interface and a first implementation of a Truss

Addressing #32

Codecov Report

Merging #33 (aa2704c) into main (5080e84) will decrease coverage by 0.42%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
- Coverage   25.71%   25.30%   -0.42%
==========================================
  Files          22       23       +1
  Lines         490      494       +4
==========================================
- Hits          126      125       -1
- Misses        364      369       +5

Impacted Files
Coverage Δ

src/interface/Elements.jl
0.00% <0.00%> (ø)

src/interface/Meshes.jl
69.44% <0.00%> (-2.78%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


host/fixer: Kill controller web jobs which are shutting down

If a controller web job claims it is shutting down, kill it and start a new one:
t=2016-11-14T18:58:53+0000 lvl=info msg="found controller instance, checking critical formations" component=cluster-monitor fn=repairCluster
t=2016-11-14T18:59:03+0000 lvl=eror msg="error repairing cluster" component=cluster-monitor fn=checkCluster err="error getting controller release: service_unavailable: controller: shutting down"

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


Implemented in https://github.com/prominence-eosc/cli/commit/2f0b910c8aa989a3439ebb143f902c9170d32e6e https://github.com/prominence-eosc/cli/commit/3fafa43253e14d935275854c3692ee3e34e4d655 https://github.com/prominence-eosc/cli/commit/189d32de08fb049888f352f98a69341b73dc7659 https://github.com/prominence-eosc/cli/commit/e187431c7375a20e58d1d8621a69dadf09abc224


Finish guidebook info and finalisation with other teams

Description
The task is to have the wireframes made at the beginning of the sprint so the design team can get underway. The wireframes form the basis of the design as well as bring to light all functionality and components required to generate the final product. Three versions of low fidelity wireframes were produced and then user testing was done to uncover which design best appeals to users. A higher fidelity wireframe would be produced after the feedback from user testing.
Milestones
List of sub-features you intend to have done and in Master by the end of the sprint.
Goal 1 (Sep 5)

[x] Have low-fidelity wireframe 1 constructed.
[x] Have low-fidelity wireframe 2 constructed.
[x] Have low-fidelity wireframe 3 constructed.
[x] Complete user testing with three versions.

Goal 2 (Sep 8)

[x] Draft the second round of wireframes based on feedback.
[x] Make medium-high fidelity wireframes.

Completion Deadline: September 20
Members
Olivia Leighton (@Olivialeighton)
Bagus Prabowo Reksoprodjo (@baguspr)
Tara-Jade Garnsworthy (@tgarnsworthy)
Syed Muhammad Zahir (@ChevScore)

After consulting with studio we received the following change log to our guidebook content draft:
CHANGE LOG:
Team 4: Updated the day and night cycle content. There are 4 days and 4-night cycles.
Team 1: Added different types of enemies and changed italicised section in enemies.
Team 5: Added building names and descriptions of how they work.
Team 6 added a  lot of information to the shop section.
Team 9 updated the achievements section + pirate crab enemy
Team 7 added information to the building's section


Databricks notebook deployment

We have been using "Databricks Deploy Notebooks" task for a while. Everything is working as expected. However when we configure databricks workspace with private end point, task shows completed successfully., but we don't see any notebooks on the target databricks folder.

facing same issue and following on same.

Are you using an azure hosted agent? I would assume it doesn't have network access so fails.
A self hosted with network access should in theory work. But this tool was written years before private end points were available, so this has not been tested.
Given that this plugin hasn't been updated for many months I doubt we will update.
I would look at using the Databricks cli in place of this solution going forwards.

@simondmorias  I am using self-hosted agent and it's deployed in the same VNET where databricks workspace is and I think it should work as expected.


Resolve long relative path using webpack resolve alias

Description:
Resolve long relative path using webpack resolve alias
Why:
Currently, in some codebases, we use relative paths like below.

In my view, we can shorten the path using webpack resolve alias
https://webpack.js.org/configuration/resolve/#resolvealias

Could I try this issue?

@SeonheeKim Yes, of course.

There are a few things I would like to discuss while working on.
First of all, I am currently thinking of proceeding with the revision as below.

However, for the @ prefix, there may be room for confusion with the external library.
Is it better to change the prefix in terms of management?
I am curious about the various opinions on prefix.
Secondly, I am thinking about how much size I should register alias.
For now, I'm thinking of registering only one level below the src folder.

Is there a better opinion in terms of management or development?
I would like to ask everyone's opinion before proceeding further.  :pray: :pray:

Can we use plain string as a prefix? Then it seems to avoid confusion by starting with the project name prefix(It would be nice to check other projects).
e.g.
import { InitialChangeID } from 'yorkie-js-sdk/src/document/change/change_id'
import { withTwoClientsAndDocuments } from 'yorkie-js-sdk/test/integration/integration_helper'

The plain string is also available.
I looked for other projects and some project use the @ + project name prefix.
I think, better to use the yorkie-js-sdk prefix to avoid confusion as you commented.
Thank you for opinion. :blush:

Thank you for sharing your ideas! In my view, @ + project name prefix sounds good :)

Thank you very much for the good opinion.  :bow:  :bow:


Vulnerable to Injection

This is a glaring security issue that should be addressed in the next update.
Application is susceptible to attack by injecting the following code:

A potential solution I've tested on my machine is by inserting these lines:

Bumping this for urgency.

please fix asap

Irresponsible to leave such an simple exploit wow

7 hours and no official reaction, this is unaceptable.
The team should have nothing to do ...
But possibly, the Internet being made of tubes, and those are full of cats.... cats have nothing to do and therefore blocking the review by sleeping within the tubes.
Damn, it's urgent to do nothing about it.

I think this requires immediate 0 actions! Please @kelseyhightower, do nothing about this!


Slack CTA

Description

Related Issues

References

Checklist:

[ ] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[ ] I have updated the documentation accordingly.
[ ] I have signed the commits, e.g. git commit -s -m "your commit message".
[ ] This PR is being made to staging branch AND NOT TO main branch.

This is how it looks like:

It link to the LF server, and then people would need to join #recommenders channel
FYI @anargyri @SimonYansenZhao

FYI @daviddavo, in case you are around


Rename bearer in the Authorization header to session.

closes https://github.com/hoodiehq/hoodie/issues/485

LGTM :+1:
Thanks for working on this @ddmck!

Perfect thanks @ddmck, LGTM.
Are you on twitter? We like giving shout outs to new contributors :) I also invited you to the Hoodie Contributors team, you can now create branches on our repos directly instead of forking :) And you can assign yourself to issues. Welcome!

Ah wait we have to update hoodie-client, hoodie-account-client and hoodie-account-server at the same time, I’ll leave this open for now. If you like check the other repos for the change, too

Okay I prepared pull requests for account client & server:

[ ] https://github.com/hoodiehq/hoodie-account-client/issues/100
[ ] https://github.com/hoodiehq/hoodie-account-server/issues/161

Once merged an new breaking versions released, we have to start a PR for https://github.com/hoodiehq/hoodie-account to update dependencies (and close the PRs by Greenkeeper) and release it as well as a breaking change.
Once that is released, we can merge this PR, also as a breaking change, as the account JSON API changed.
ping @hoodiehq/maintainers 👀

done via e63a0dd, 65c6a3f, f3dd07e


Fix/junit report

Fix 2 issues with junit reports:

toss3 -> toss_3: allows junit to be generated on quartz.
lxml not found: generate and use a specific python environment in the pipeline.

TODO:
Use cache to improve efficiency.

LGTM

LGTM

LGTM


Add results from survey

I created the first two commits to get this repo started: 546af74dc439668b77c3aaa31ccbc6ab80bd7f7d and b8aba56945e8048bee8140951220aeb4d90188c1. From now on, I'll switch to committing to a fork and submitting pull requests.
If we only want CC0 to apply to a subset of this repo, we should address that now. I'm fine with it applying to everything including our code, figures, and documentation.
@jpolka do you want to upload the raw data from the survey? Perhaps, in a data directory? The unmodified format straight from Google Forms would be best. Also you could add a modified version... not sure if you had to do any manual cleaning.
git and GitHub can be quite confusion. Not sure how familiar you are with it. For another project, we have some documentation on the collaborative workflow here. Happy to walk anyone through the process if they're having trouble contributing here.

Fine with leaving this CC0!  Raw survey responses and ppt & xls files added.


[0.32.0] Session is not persistent in Electron

Hello,
While running our test cases, we found that session is not persistent in app. When we close the  app, session is some how getting cleared. so Next time when we load the app. Our auth page is shown.
based on this , i have created a sample "gmail" demo. Which exhibits the same thing.
Working Electron Engine versions : <= 0.30.3
Defective Electron Engine versions : > 0.30.3
https://github.com/kamesh-a/electron-samples/tree/master/sessionNotPersistent

Please take a look, Let us know if needed any info. We would be glad to help.

Tested with 0.32.0, Same result,
Steps:
a. Login in gmail after successful login.
b. close the app
c. restart the app.
Expected behavior :  landing into mailbox, without asking to user info.
current behavior : Asks user info everytime when we start the app.
Tested in  Mac OS and Windows

Unable to reproduce on linux, the test app works fine.

@deepak1556 We have not tested it on linux, We don't have development env in linux. Basically we create app only for MAC OS X yosemite and mavericks and windows 7,8,10

Thanks @zcbenz so it will store disk, not keep in memory. Is there any way i could test this. I assume only way now it download the code and build it or you have pre-test build before release.
Once a again Great work by Electron team and community.

@zcbenz Thank you for fixing, @deepak1556 I can confirm that, our test sample was working fine in linux, I setup Ubuntu 64bit box. But our primary targets are mac & win for now. thanks for your reply.
Really appreciate all your works.  I would love to dive in test the build. Is there any way i could do it. I guess i have to compile the atom project to get updated build. If there is any test build please point it to me. we would be glad to test it.
Thanks again.

I'm cutting a new release soon because of a regression in v0.32.0.

Okay :+1:


How to visualize the result?

Hi, thanks for sharing this awesome work.
I noticed that you mentioned in another issue that

You can use the tools in this repo to help

but the demo.py outputs just a JSON file.
So could you give me some ideas on how to use the provided 3d-pc-box-viz repo to visualize the JSON file?

I hope the following code could solve your problem:
import argparse
import json, os, torch, numpy as np
from ply_helper import write_bbox

COLOR = [237, 125, 49]
def visualize_one_scene(filename: str, output_dir: str) -> None:

    predicts = json.load(open(filename, 'r'))

    for pred_idx, pred_info in enumerate(predicts):
        write_bbox(
            np.asarray(pred_info['box']),
            COLOR,
            os.path.join(output_dir, f"{pred_idx}-{pred_info['caption']}.ply")
        )
    return

if __name__ == '__main__':
    parser = argparse.ArgumentParser()
    parser.add_argument('--json_fn', default=None, type=str, help='specified json filename for visualization')
    parser.add_argument('--json_folder', default=None, type=str, help='specified json folder for visualization')
    parser.add_argument('--output_dir', default=None, type=str, help='output dir for ply files')
    args = parser.parse_args()

    file_list = []
    if args.json_folder is not None:
        file_list = list(
            map(
                lambda fn: os.path.join(args.json_folder, fn),
                os.listdir(args.json_folder)
            )
        )
    if args.json_fn is not None:
        file_list.append(args.json_fn)

    for filename in file_list:
        scan_name = os.path.basename(filename).replace('.json', '')
        output_dir = os.path.join(args.output_dir, scan_name)
        os.makedirs(output_dir, exist_ok=True)
        visualize_one_scene(filename, output_dir)

Thanks a lot, it truly output some bbox files

but it seems it cannot align well with the scannet scene, do you meet the similar problem?

As can be seen from https://github.com/ch3cook-fdu/Vote2Cap-DETR/blob/master/data/scannet/load_scannet_data.py#L65-L71, the input 3D mesh has gone through an affine transformation.
Here is an example code for this process:
import numpy as np
from ply_helper import write_ply, read_mesh_vertices_rgb_normal

scene_id = 'scene0246_00'
# point_cloud, mesh = read_mesh_vertices_rgb_normal(scene_id + '_vh_clean.ply')
point_cloud, mesh = read_mesh_vertices_rgb_normal(scene_id + '_vh_clean_2.ply')

# Load scene axis alignment matrix
lines = open(scene_id + '.txt').readlines()
axis_align_matrix = None
for line in lines:
    if 'axisAlignment' in line:
        axis_align_matrix = [float(x) for x in line.rstrip().strip('axisAlignment = ').split(' ')]

axis_align_matrix = np.array(axis_align_matrix).reshape((4,4))
pts = np.ones((point_cloud.shape[0], 4))
pts[:,0:3] = point_cloud[:,0:3]
pts = np.dot(pts, axis_align_matrix.transpose()) # Nx4
aligned_vertices = np.copy(point_cloud)
aligned_vertices[:,0:3] = pts[:,0:3]

write_ply(aligned_vertices[:, :3], aligned_vertices[:, 3:6] / 256., mesh, scene_id + '_vh_aligned.ply')

I have rectified the issue, thanks to your thorough response.
Best wishes!


Errorbars

Is it possible to create plots with errorbars, like plt.errorbar does?

This has been one of our main to-do items for a long time now. Now that someone has requested them I don't think there is any excuse not to do them. We'll discuss it today and get back to you.

Yes, errorbars and stream plots are sorely needed, but note that they can currently be done using the Seaborn interface (see the Seaborn and Pandas tutorial).

Just added an ErrorBars Element type. I'll rebuild the Elements tutorial now so there should be an example up on the website fairly soon.

The example is now live and can be seen here. Let us know if it works for you and if you need any modifications or have any suggestions. I'll close this issue now.

Looks good.  In the new example, shouldn't it say vertical=False for the second plot?  They certainly seem to be horizontal.
I'm not sure that vertical or horizontal is really a plotting option -- isn't this a semantic issue, i.e. declaring that the data is ranging over either x or y?  And if so, shouldn't it be a parameter for the Element, not the Element's style options?  It doesn't seem like a stylistic choice, to me, but maybe I'm confused.

I clearly didn't pay enough attention when implementing it at first but I had already renamed it to horizontal last night. I also wondered what the best way of selecting x-error bars vs. y-error bars was, initially I had separate Elements for each just like we have VLine and HLine. I don't know what the best option is but a parameter on the Element is probably it, any suggestions for naming it?

Maybe key_index, to specify which key_dimension the error values apply to?  By default, key_index=0, indicating that the error bars are for values specified on the x axis, and nearly everyone would use that default (resulting in vertical error bars).  But the error bars could apply to any key_dimension in principle, which this proposal would allow.


EasyQuant crashes when the Input contains duplicated sequences or seq-names

It seems like the indexing step cannot handle duplicated names or sequences.
Where exactly the Error occurs has to be investigated.

Duplicate sequences should be fine as long as they have a unique identifier. Duplicate names are not allowed as input. Find here the input requirements


fix(docker): remove ARG PORT

EDIT: This OP no longer holds true, things got rather simplified instead. Follow the discussion below.
Yet another gratuitous fix nobody asked for :)
Shell parameter expansion doesn't happen inside the CMD array, so literal ${PORT} gets passed to uwsgi, which it happily accepts, but, well, doesn't work as expected.
One either needs to set an ENV var and use it in an entrypoint shell script or, if one doesn't want to pollute the container's env space, modify the argument (with sed) within the entrypoint itself. That's what I did.
Also this change ignores a couple fat development directories that complicate local make docker runs.
PS: I'm not a fan of docker entrypoints, but this couldn't be solved better, unless using custom variable expansion like this in the ENTRYPOINT:
r=(); for arg; do eval $'r+=("$(cat <<EoF\n'$arg$'\nEoF\n)")'; shift; done; exec uwsgi "${r[@]}"

which, although surely very beautiful, is also pretty obscure, rather unsafe and adds one more (unwanted) level of variable expansion to the arguments passed as the CMD.

I guess it'll work.  Because I live in K8s-world where I don't have to worry about any of this, I'd just go the other way and force it to 5000 always and rely on a service or an ingress to modify that for the caller if I had to.  But maybe assuming you've got k8s around is not a good assumption.

I'm actually with you on this one. Driven by the status quo where there's an ARG PORT, I wanted to make it work as originally designed. But I admit it's insanely convoluted for such an optional task. AFAIK the EXPOSE directive is nothing but a hint for the runtime which port to expose, which is usually overridable from the outside (talking containerPort in k8s, or docker run --publish). So I'd much rather not see any of that, took out the ARG entirely and fix the port in the default CMD to 5000 as you say.
If you think it's fair to remove the ARG PORT, I'm all for that.

If you're in agreement, yeah, let's just fix PORT to 5000 in the container and be done with it.  We can always change it back if anyone screams, and if you are for some reason running without containerization where you might not have as much control, you've still got the option to set the port.

@athornton I'm done, please squash this. Thanks!


Additional hint to find details of exposures in the contact journal (EXPOSUREAPP-5829)

This adds a small hint that user finds more details in contact journal.
How to test:

go to details page

hint should appear in case there is a low risk with encounters or high risk

[ ] test it myself

wrong base - i have to create a new branch


BADGE REQUEST [• Hawks • 🌈#1337]

What is your Discord Tag?
• Hawks • 🌈#1337
What is your UID (User ID)?
811770910624579584
**What is the image for the badge that you want? *Please make sure that the image is hosted on a trusted domain, such as https://cdn.discordapp.com/attachments/843160047093153822/851642648438636574/circle-cropped.png
Additional Confirmation:

[x] My badge does not contain any NSFW material.
[x] My badge is not a badge that signifies that I am an official developer / staff for Discord or client mod communities.

done


Moves balance_labels arg to the constructor of SVC

Fixes https://github.com/wiki-ai/revscoring/issues/118

You can now configure this parameter with revscoring train_test ... -p balance_labels=false

Looks good and the tests pass.


fix: allow applyMiddleware to be called more than once

closes #3451
I wonder if the docs should be updated as well?

Thanks for the PR, but I don't see a need to do this.


Putting in Mac autotune instructions

Not currently working for me...after doing the mac steps, I get the following error:

Yeah, you can't use those quick install scripts on a Mac. I'm not sure you need anything they install: I think that's what the Mac specific steps are for...

Yup, just stopped to think logically now instead of simply following the steps.  Mac users need to be told to Skip steps 2A and 2B.  After that they should be fine

Works for the rest of the instructions.  Great!

Added commit https://github.com/openaps/docs/pull/690/commits/23fdbe04909d8878df393c548230a81d7cbbfe0a
Refactor Phase C Linux VM vs. Mac instructions
Creates a Step 0 : Decide where to run Autotune
Breaks apart Step 1 into Step 1a: Create a Linux VM or Step 1b: Prep your Mac
Moves quick-packages install into Step 1a.  Removes apt-get install jq step, as that's part of  quick-packages now.


fix: upgrade to mirror node to v0.110.1

Description
This pull request changes the following:

Upgrade Mirror node subchart to v0.110.1

Related Issues

Closes #950

:tada: This PR is included in version 0.29.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: Support for .NET 7 ARM64 container builds

Issue #, if available:
This PR contains changes that complete support for .NET 7 container builds #68 #69 by adding support for ARM64 container builds.
Description of changes:
Currently the .NET 7 SAM build images only support x86_64 because .NET 7 was previously not compatible with AL2 on ARM. Microsoft reduced the dependencies needed for .NET 7 ARM, and now we can build ARM support for .NET 7.
This PR contains code changes to take architecture argument and build ARM64 image for .NET 7.
.NET 7 Lambda arm64 base image is now available on https://gallery.ecr.aws/lambda/dotnet
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@lucashuy @mndeveci Thank you for reviewing this PR. We didn't include any arch specific change in previous PRs, so I don't think we need to change anything in SAM CLI.

@lucashuy @mndeveci Thank you for reviewing this PR. We didn't include any arch specific change in previous PRs, so I don't think we need to change anything in SAM CLI.

Thanks for your reply, before we move forward can you locally build this image and test it withing SAM CLI with arm64 target runtime?

@lucashuy @mndeveci Thank you for reviewing this PR. We didn't include any arch specific change in previous PRs, so I don't think we need to change anything in SAM CLI.

Thanks for your reply, before we move forward can you locally build this image and test it withing SAM CLI with arm64 target runtime?

Yes. We built local image and tested .NET7 NativeAOT and non NativeAOT cases, both worked fine.


Update visualize docstrings

To reflect the fact that the filename kwarg can now accept file extensions.
https://github.com/dask/dask/blob/3903843aba6b248ce4d9c8c6ef696b16ae4a6351/dask/dot.py#L276-L278

[x] Tests added / passed
[x] Passes black dask / flake8 dask

I mean the other way around. I think that it is better for users to provide
the full filename.
On Wed, Jul 8, 2020, 9:00 PM Zhengnan<EMAIL_ADDRESS>wrote:

@ZhengnanZhao commented on this pull request.
In dask/base.py
https://github.com/dask/dask/pull/6383#discussion_r451950504:

@@ -70,7 +71,7 @@ def visualize(self, filename="mydask", format=None, optimize_graph=False, **kwar

     Examples
     --------

   >>> x.visualize(filename='dask.pdf')  # doctest: +SKIP

   >>> x.visualize(filename='dask')  # doctest: +SKIP

Can you explain a bit more what you mean by "explicit"? Are you saying we
should encourage users to use .visualize(filename='dask', format='pdf')
over .visualize(filename='dask.pdf'), or is it the other way around?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/6383#discussion_r451950504, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTDBT6LWDIX5ACYLUI3R2U6HDANCNFSM4OVEK4LQ
.

Thank you for the fix @ZhengnanZhao !  This is in.
Also, I notice that this is your first contribution to this repository.  Welcome!


implement support for jakarta 9 ee

closes #1543

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #1577 opened

Reason: The PR is not allowed to run in the CI yet

Start Time: 2020-12-20T07:11:04.243+0000

Duration: 3 min 53 sec

Commit: 07d174dba5dae5701eee9f12177a016bdb062c01

Steps errors
Expand to view the steps failures

Error signal

Took 0 min 0 sec . View more details on here
Description: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permission

Log output
Expand to view the last 100 lines of log output

[2020-12-20T07:13:26.894Z]  > git --version # timeout=10
[2020-12-20T07:13:26.924Z]  > git --version # 'git version 2.17.1'
[2020-12-20T07:13:26.925Z] using GIT_ASKPASS to set credentials GitHub user @apmmachine User + Personal Access Token
[2020-12-20T07:13:26.928Z]  > git fetch --no-tags --progress -- https://github.com/elastic/apm-agent-java.git +refs/heads/*:refs/remotes/origin/* # timeout=15
[2020-12-20T07:13:27.612Z]  > git config remote.origin.url https://github.com/elastic/apm-agent-java.git # timeout=10
[2020-12-20T07:13:27.624Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-12-20T07:13:27.639Z]  > git config remote.origin.url https://github.com/elastic/apm-agent-java.git # timeout=10
[2020-12-20T07:13:27.664Z] Fetching upstream changes from https://github.com/elastic/apm-agent-java.git
[2020-12-20T07:13:27.664Z] using GIT_ASKPASS to set credentials GitHub user @apmmachine User + Personal Access Token
[2020-12-20T07:13:27.665Z]  > git fetch --no-tags --progress --prune -- https://github.com/elastic/apm-agent-java.git +refs/pull/1577/head:refs/remotes/origin/PR-1577 +refs/heads/master:refs/remotes/origin/master # timeout=15
[2020-12-20T07:13:28.249Z] Merging remotes/origin/master commit cf8a908b57db093f8f6a07248aa6c04a0e357630 into PR head commit 07d174dba5dae5701eee9f12177a016bdb062c01
[2020-12-20T07:13:28.259Z]  > git config core.sparsecheckout # timeout=10
[2020-12-20T07:13:28.264Z]  > git checkout -f 07d174dba5dae5701eee9f12177a016bdb062c01 # timeout=15
[2020-12-20T07:13:28.490Z]  > git remote # timeout=10
[2020-12-20T07:13:28.509Z]  > git config --get remote.origin.url # timeout=10
[2020-12-20T07:13:28.519Z] using GIT_ASKPASS to set credentials GitHub user @apmmachine User + Personal Access Token
[2020-12-20T07:13:28.522Z]  > git merge cf8a908b57db093f8f6a07248aa6c04a0e357630 # timeout=10
[2020-12-20T07:13:28.980Z] Merge succeeded, producing f2e6ddd94bdbd5101052313d4ae44a8e0a76245c
[2020-12-20T07:13:28.980Z] Checking out Revision f2e6ddd94bdbd5101052313d4ae44a8e0a76245c (PR-1577)
[2020-12-20T07:13:28.973Z]  > git rev-parse HEAD^{commit} # timeout=10
[2020-12-20T07:13:28.984Z]  > git config core.sparsecheckout # timeout=10
[2020-12-20T07:13:28.996Z]  > git checkout -f f2e6ddd94bdbd5101052313d4ae44a8e0a76245c # timeout=15
[2020-12-20T07:13:33.086Z] Commit message: "Merge commit 'cf8a908b57db093f8f6a07248aa6c04a0e357630' into HEAD"
[2020-12-20T07:13:33.086Z] First time build. Skipping changelog.
[2020-12-20T07:13:33.112Z]  > git --version # timeout=10
[2020-12-20T07:13:33.141Z]  > git --version # 'git version 2.17.1'
[2020-12-20T07:13:33.153Z] fatal: bad object 7edba8e3544d4f6700385847f4f4c4daad2361f5
[2020-12-20T07:13:34.106Z] Masking supported pattern matches of $JOB_GCS_BUCKET or $NOTIFY_TO
[2020-12-20T07:13:34.182Z] Timeout set to expire in 1 hr 0 min
[2020-12-20T07:13:34.213Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.
[2020-12-20T07:13:34.710Z] [INFO] Number of builds to be searched 10
[2020-12-20T07:13:35.125Z] [INFO] 'shallow' is forced to be disabled when running on PullRequests
[2020-12-20T07:13:35.153Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1577/src/github.com/elastic/apm-agent-java
[2020-12-20T07:13:35.196Z] [INFO] gitCheckout: Checkout SCM PR-1577 with some customisation.
[2020-12-20T07:13:35.232Z] [INFO] Override default checkout
[2020-12-20T07:13:35.301Z] Sleeping for 10 sec
[2020-12-20T07:13:45.453Z] using credential 2a9602aa-ab9f-4e52-baf3-b71ca88469c7-UserAndToken
[2020-12-20T07:13:45.562Z] Cloning the remote Git repository
[2020-12-20T07:13:45.578Z] Cloning repository https://github.com/elastic/apm-agent-java.git
[2020-12-20T07:13:45.607Z]  > git init /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1577/src/github.com/elastic/apm-agent-java # timeout=10
[2020-12-20T07:13:45.613Z] Using reference repository: /var/lib/jenkins/.git-references/apm-agent-java.git
[2020-12-20T07:13:45.614Z] Fetching upstream changes from https://github.com/elastic/apm-agent-java.git
[2020-12-20T07:13:45.614Z]  > git --version # timeout=10
[2020-12-20T07:13:45.623Z]  > git --version # 'git version 2.17.1'
[2020-12-20T07:13:45.623Z] using GIT_ASKPASS to set credentials GitHub user @apmmachine User + Personal Access Token
[2020-12-20T07:13:45.624Z]  > git fetch --tags --progress -- https://github.com/elastic/apm-agent-java.git +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-12-20T07:13:46.091Z]  > git config remote.origin.url https://github.com/elastic/apm-agent-java.git # timeout=10
[2020-12-20T07:13:46.095Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-12-20T07:13:46.102Z]  > git config remote.origin.url https://github.com/elastic/apm-agent-java.git # timeout=10
[2020-12-20T07:13:46.110Z] Fetching upstream changes from https://github.com/elastic/apm-agent-java.git
[2020-12-20T07:13:46.111Z] using GIT_ASKPASS to set credentials GitHub user @apmmachine User + Personal Access Token
[2020-12-20T07:13:46.112Z]  > git fetch --tags --progress -- https://github.com/elastic/apm-agent-java.git +refs/pull/1577/head:refs/remotes/origin/PR-1577 +refs/heads/master:refs/remotes/origin/master # timeout=10
[2020-12-20T07:13:46.647Z] Checking out Revision 07d174dba5dae5701eee9f12177a016bdb062c01 (origin/PR-1577)
[2020-12-20T07:13:46.831Z] Commit message: "implement support for jakarta 9 ee"
[2020-12-20T07:13:46.831Z] First time build. Skipping changelog.
[2020-12-20T07:13:46.851Z]  > git --version # timeout=10
[2020-12-20T07:13:46.856Z]  > git --version # 'git version 2.17.1'
[2020-12-20T07:13:46.862Z] fatal: bad object 7edba8e3544d4f6700385847f4f4c4daad2361f5
[2020-12-20T07:13:46.642Z]  > git rev-parse origin/PR-1577^{commit} # timeout=10
[2020-12-20T07:13:46.651Z]  > git config core.sparsecheckout # timeout=10
[2020-12-20T07:13:46.654Z]  > git checkout -f 07d174dba5dae5701eee9f12177a016bdb062c01 # timeout=10
[2020-12-20T07:13:48.105Z] Masking supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD
[2020-12-20T07:13:48.723Z] + git fetch<EMAIL_ADDRESS>+refs/pull/*/head:refs/remotes/origin/pr/*
[2020-12-20T07:13:49.771Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1577/src/github.com/elastic/apm-agent-java/.git
[2020-12-20T07:13:49.823Z] Archiving artifacts
[2020-12-20T07:13:50.593Z] + git rev-parse HEAD
[2020-12-20T07:13:50.978Z] + git rev-parse HEAD
[2020-12-20T07:13:51.303Z] + git rev-parse origin/pr/1577
[2020-12-20T07:13:51.363Z] [INFO] githubEnv: Found Git Build Cause: pr
[2020-12-20T07:13:51.893Z] Masking supported pattern matches of $GITHUB_TOKEN
[2020-12-20T07:13:52.840Z] [WARN] githubApiCall: The REST API call https://api.github.com/repos/elastic/apm-agent-java/pulls/1577/reviews return 0 elements
[2020-12-20T07:13:52.918Z] [INFO] githubPrCheckApproved: Title: implement support for jakarta 9 ee - User: kananindzya - Author Association: CONTRIBUTOR
[2020-12-20T07:13:53.312Z] ERROR: githubPrCheckApproved: The PR is not allowed to run in the CI yet
[2020-12-20T07:13:53.312Z] ERROR: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permissions can do so.)
[2020-12-20T07:13:53.402Z] [INFO] Let's stop build #1. The PR is not allowed to run in the CI yet
[2020-12-20T07:13:53.427Z] Sleeping for 5 sec
[2020-12-20T07:13:54.610Z] Stage "Build" skipped due to earlier failure(s)
[2020-12-20T07:13:54.799Z] Stage "Tests" skipped due to earlier failure(s)
[2020-12-20T07:13:55.008Z] Stage "Unit Tests" skipped due to earlier failure(s)
[2020-12-20T07:13:55.020Z] Stage "Smoke Tests 01" skipped due to earlier failure(s)
[2020-12-20T07:13:55.031Z] Stage "Smoke Tests 02" skipped due to earlier failure(s)
[2020-12-20T07:13:55.042Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2020-12-20T07:13:55.053Z] Stage "Javadoc" skipped due to earlier failure(s)
[2020-12-20T07:13:55.222Z] Failed in branch Unit Tests
[2020-12-20T07:13:55.231Z] Failed in branch Smoke Tests 01
[2020-12-20T07:13:55.238Z] Failed in branch Smoke Tests 02
[2020-12-20T07:13:55.246Z] Failed in branch Benchmarks
[2020-12-20T07:13:55.253Z] Failed in branch Javadoc
[2020-12-20T07:13:55.491Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-12-20T07:13:55.573Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-12-20T07:13:55.611Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-12-20T07:13:56.195Z] Running on Jenkins in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1577
[2020-12-20T07:13:56.511Z] [INFO] getVaultSecret: Getting secrets
[2020-12-20T07:13:56.747Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-12-20T07:13:57.652Z] + chmod 755 generate-build-data.sh
[2020-12-20T07:13:57.652Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1577/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1577/runs/1 ABORTED 173140
[2020-12-20T07:13:58.203Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1577/runs/1/steps/?limit=10000 -o steps-info.json
[2020-12-20T07:13:58.754Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1577/runs/1/tests/?status=FAILED -o tests-errors.json
[2020-12-20T07:13:59.005Z] Retry 1/3 exited 22, retrying in 1 seconds...
[2020-12-20T07:13:59.916Z] Retry 2/3 exited 22, retrying in 2 seconds...

Codecov Report

Merging #1577 (b924d27) into master (8fa3c81) will decrease coverage by 0.35%.
The diff coverage is 21.08%.

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


Giving an error to a correct directory for Android SDK

Giving an error to a correct directory for Android SDK

What are the contents of E:/Android/Sdk ? For me, when I list the contents of a working Sdk directory, I get:
build-tools/
emulator/
extras/
licenses/
patcher/
platform-tools/
platforms/
skins/
sources/
system-images/
tools/

It would also help to know what version of Android SDK you have installed; maybe some newer versions don't validate correctly.

It was working correctly when using libgdx setup, using same e:/Android/Sdk directory

This should be fixed in https://github.com/tommyettinger/gdx-liftoff/releases/tag/v<IP_ADDRESS> . It looks like tools was renamed to cmdline-tools in some recent version of the Android SDK, so now liftoff will check if either is present (as well as needing platforms) to validate an SDK directory.


Add support for script command parameters

Closes #14

This change caused a few TS errors in the tests. I'll have those resolved shortly.

I used non-null assertions to resolve the test issues since getCommand can potentially return undefined. This seems acceptable since we know the commands we are providing in tests. Please let me know if you'd prefer to handle this another way. 🙂

Looks great, thank you!


Login - Spaces are not trimmed before making the email check during login - Reported by: @Rajat Parashar

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

navigate to the App
Enter email with spaces before or after
Hit continue

Expected Result:
User should be able to proceed
Actual Result:
User is unable to proceed. Error displayed
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

**Version Number:1.1.18-0
**Reproducible in staging?:Y
**Reproducible in production?:Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
**Issue reported by:Rajat Parashar
**Slack conversation:https://expensify.slack.com/archives/C01GTK53T8Q/p1639048789406200
View all open jobs on GitHub

Triggered auto assignment to @greg-schroeder (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Triggered auto assignment to @MariaHCD (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Proposed Solution: (If considered as external)
Need to update validateAndSubmitForm() function within src/pages/signin/LoginForm.js
https://github.com/Expensify/App/blob/c86847d26e1f8e16264314f5f837436baeaaa5f8/src/pages/signin/LoginForm.js#L104-L128
Solution:
Update code as shown under. Take trimmed value of login once const loginTrimmed = this.state.login.trim(); and replace every instance of this.state.login with loginTrimmed in this function. So we can prevent usage of trim() multiple time and solve this problem.
 validateAndSubmitForm() {
        const loginTrimmed = this.state.login.trim();
        if (!loginTrimmed) {
            this.setState({formError: 'common.pleaseEnterEmailOrPhoneNumber'});
            return;
        }

        const phoneLogin = LoginUtil.getPhoneNumberWithoutSpecialChars(loginTrimmed);
        const isValidPhoneLogin = Str.isValidPhone(phoneLogin);

        if (!Str.isValidEmail(loginTrimmed) && !isValidPhoneLogin) {
            if (ValidationUtils.isNumericWithSpecialChars(loginTrimmed)) {
                this.setState({formError: 'messages.errorMessageInvalidPhone'});
            } else {
                this.setState({formError: 'loginForm.error.invalidFormatEmailLogin'});
            }
            return;
        }

        this.setState({
            formError: null,
        });

        // Check if this login has an account associated with it or not
        Session.fetchAccountDetails(isValidPhoneLogin ? phoneLogin : loginTrimmed);
    }

Triggered auto assignment to @stephanieelliott (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Hey @parasharrajat, as the reporter of this issue you have first dibs on fixing it before I share it publicly on Upwork. If you want to complete this job, please submit a proposal here!

Sure, thanks. It is a quicker one so I can take it.
Proposal

we have to trim the login input before validating it and sending it backend which is handled at https://github.com/Expensify/App/blob/15bb537ebf508559e81c32d664924b1dcf0be361/src/pages/signin/LoginForm.js#L104.

We should trim this.state.login before using it anywhere inside validateAndSubmitForm() function.

@stephanieelliott Proposal above.

Triggered auto assignment to @parasharrajat (Exported)

Triggered auto assignment to @tgolen (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

OK! Proposal looks fine. 🟢 to hire @parasharrajat for it.

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.21-1 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/6771

If no regressions arise, payment will be issued on 2021-12-27. :confetti_ball:

@parasharrajat looks like this wasn't on upwork, i've just created a job and hired you, can you let me know when you accept and I'll pay you, thanks

I have accepted it @laurenreidexpensify

ace @parasharrajat all paid 👍🏽


Vulkan amended port of scriptmgrleak (#1064)

A big commit was not completely ported to the vulkan branch.
The remaining part contains:
- mDefaultTextureParameters rename
- New file GVRContextProxy.java
- GVRScriptManager.destroy()

This pull request must be 'merged' and not 'rebased'

Looks like what it is supposed to be


FloorQuality Stat

Adds a stat for TerrainDefs to output the result of IsFine (aka, does it have the tag "FineFloor"). "Fine" floors are required for setting up Royalty thronerooms and bedrooms, and with many mods, it is not always easy to tell what is or is not considered "fine". The data is already exposed in-game in the Info tab, where it shows "Considered: Fine" for fine floors (and "Considered" doesn't show up for non-fine ones).
I compiled and ran this in a low-mod situation (basically this and Harmony), one with just a bunch of floor-adding mods, and then in my large modlist save, and haven't had any issues. I tried doing a pre- and post- change comparison in Dubs Performance Analyzer, but it didn't really move the needle at all.

Nice! Should be added in 6015482


Request: Mouse sensitivity?

Hello and thanks for your work!
I noticed that in-game sensitivity sliders only work with gamepad look and have no effect on the mouse. Would you consider fixing that with your hack in the future?

https://github.com/SuiMachine/White-Day---Sui-s-Hack/commit/73e188844a410656ff8c044f47960155eea84a33
https://github.com/SuiMachine/White-Day---Sui-s-Hack/releases/tag/1.1

i kneel

i kneel


Parse accessibility separately from modifier

When we parse the following Java file:
public class Example {

    public void example() { }

}

We identify public as modifier. It's possible from the position of modifier in the parse tree for the consumer to selectively inspect the contents, but modifier in the tree-sitter-java grammar could mean other things (e.g. abstract, native, sychronized, etc.) that aren't directly accessibility related.
What about treating accessibility (i.e. public, protected, and private) in the Java grammar as first class nodes in the parse tree?
Suggested diff
(program [0, 0] - [5, 0]
  (class_declaration [0, 0] - [4, 1]
-- (modifier [0, 0] - [0, 6])
++ (public [0, 0] - [0, 6])
    (identifier [0, 13] - [0, 20])
    (class_body [0, 21] - [4, 1]
      (method_declaration [2, 4] - [2, 29]
--      (modifier [2, 4] - [2, 10])
++      (public [2,4] - [2,10])
        (method_header [2, 11] - [2, 25]
          (void_type [2, 11] - [2, 15])
          (method_declarator [2, 16] - [2, 25]
            (identifier [2, 16] - [2, 23])))
        (method_body [2, 26] - [2, 29]
          (block [2, 26] - [2, 29]))))))

👍


Compatible with nativescript version 3.0?

I updated nativescript to version 3.0 and when i try to run my app I get this error:
> Failed to apply plugin [id 'com.google.gms.google-services']
   > For input string: "+"

@magar91 can you post the content of your package.json

this is my package.json @NickIliev
{
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "readme": "NativeScript Application",
  "repository": "<fill-your-repository-here>",
  "nativescript": {
    "id": "org.nativescript.smartcities",
    "tns-android": {
      "version": "3.0.0"
    }
  },
  "dependencies": {
    "@angular/animations": "~4.1.0",
    "@angular/common": "~4.1.0",
    "@angular/compiler": "~4.1.0",
    "@angular/core": "~4.1.0",
    "@angular/forms": "~4.1.0",
    "@angular/http": "~4.1.0",
    "@angular/platform-browser": "~4.1.0",
    "@angular/router": "~4.1.0",
    "angular2-jwt": "^0.2.3",
    "email-validator": "^1.0.7",
    "nativescript-angular": "~3.0.0",
    "nativescript-audio": "^3.4.2",
    "nativescript-camera": "^3.0.0",
    "nativescript-checkbox": "^2.0.0",
    "nativescript-drop-down": "^3.0.1",
    "nativescript-geolocation": "^3.0.0",
    "nativescript-google-maps-sdk": "^2.0.3",
    "nativescript-i18n": "^0.2.1",
    "nativescript-imagepicker": "^3.0.1",
    "nativescript-oauth": "^2.0.0",
    "nativescript-push-notifications": "^0.1.3",
    "nativescript-ripple": "^1.1.0",
    "nativescript-telerik-ui": "^2.0.1",
    "nativescript-theme-core": "~1.0.2",
    "nativescript-toast": "^1.4.5",
    "nativescript-vibrate": "^1.1.2",
    "nativescript-web-image-cache": "^4.1.0",
    "reflect-metadata": "~0.1.8",
    "rxjs": "~5.3.0",
    "tns-core-modules": "~3.0.0",
    "zone.js": "~0.8.2"
  },
  "devDependencies": {
    "babel-traverse": "6.24.1",
    "babel-types": "6.24.1",
    "babylon": "6.17.1",
    "lazy": "1.0.11",
    "nativescript-dev-typescript": "~0.4.0",
    "typescript": "~2.2.1"
  }
}

@magar91 The latest version is NS 3.0 compatible. Please double check the plugin instructions for Android in the README of this repo. You may need to check whether you have removed and again added the Android platform (tns platform remove android and tns platform add android). A similar issues was discussed here.
Hope this helps.

@magar91 Ithe reason behind this issue is most likely conflict within the version of google-play-services which nativescript-google-maps-sdk and nativescript-push-notifications are trying to use.
To overcome this problem run npm install (remove node_modules and platforms before that)
and then navigate to node_modules/nativescript-google-maps-sdk/platforms/android/include.gradle and change this line:
	def googlePlayServicesVersion = project.hasProperty('googlePlayServicesVersion') ? project.googlePlayServicesVersion : '+'

to this
	def googlePlayServicesVersion = project.hasProperty('googlePlayServicesVersion') ? project.googlePlayServicesVersion : '10.0.1'

Note that the version you are setting here depends on the version used in the
node_modules/nativescript-push-notifications/platforms/android/include.gradle set for
compile 'com.google.firebase:firebase-messaging:10.0.1'

Or use this workaround (pretty much the same idea)

Adding the following to app/App_Resources/Android/app.gradle works too:
ext {
googlePlayServicesVersion = '10.0.1'
}
I find this to be more elegant as I don't like messing with stuff under platforms.


Add support for using an Oracle Wallet file for connecting to an Autonomous Database in Oracle Cloud

Currently to connect to an ADB in Oracle Cloud you would need to download the Wallet file zip file, extract the contents then create the custom jdbc connection string to point to the wallet directory.  SQL Developer allows you to select a wallet ZIP file then provides the contents of the embedded tnsnames.ora file.  Would it be possible to add a new driver type that could allow connections the same way?

@wattpuppy We have Oracle authentication with Wallet file in Enterprise Edition. Currently not scheduled to be added in Community Edition


How can I create new models?

I want to combine RoBerta encoder with a gts decoder, using custom dataset, is this possible?have u already implemented it. I need to do this for class research project so any pointers are appreciated, Thank You.

If you want to combine Roberta encoder with gts decider, my suggestion is writing a new model class under the folder mwptoolkit/model/Seq2Tree, you can reference most code of gts.
Several works has tried to combine pretrained model with gts decoder and we are reproducing their works.
in order to deploy pretrained model in mwptoolkit,  we preliminarily implement a dataset class named PretrainDataset, and a dataloader class named PretrainDataloader. So running pretrained model based method, you need to initialize both of them.
And then, the trainer is also need to be initialized,my suggestion is simply inherit GTSTrainer.
In mwptoolkit,some bugs has been found when running custom dataset on gts.It seems like single equation dataset's bug. My suggestion is you can run deployed dataset on the new model.
I hope this will help you!


Investigate typed metadata for validation packages

Currently, validation packages contain their metadata as yaml frontmatter.
This is suboptimal once that metadata is relevant for the output generated by the ARCExpect API (e.g. package name or version might not match).

As of https://github.com/nfdi4plants/arc-validate-package-registry/commit/0049cf9cc79780312db8f51d7d4cb2ddcd8142d4 it is now possible to extract metadata inside a package from the frontmatter.
See also .
This should be implemented in ARCExpect via the Execute API functions accepting ValidationPackageMetadata (or even directly the frontmatter string) to determine folder naming and use defaults for badge text and run summary. Note that now #95 can now also include full package metadata easily.


Add /help command

What kind of change does this PR introduce?
Adds /help <user> command following https://github.com/supabase-community/supabase-community-bot/discussions/2#discussioncomment-4415275
What is the current behavior?
Nothing.
What is the new behavior?
Using, /help <user>, it will reply with
Hello <user>! Please use the #help-channel for questions. You will find it easier to get answers there!

Additional context
Require new .env variable called HELP_CHANNEL_ID.
Please feel free to edit the message.

Hi @NanoCode012 👋🏻
Thank you for your contribution! I really like the idea. I was planning to integrate a similar command but parsing the messages with chatgpt. So if the message looks like a help request, then the bot asks the user to go to the help channel, or even create a post for him.
However, a simple command is just as effective. I'm just not sure about the term "help" for the command, in the sense that the "/help" commands are more there to display the list of commands. Something like "/redirect" would seem a bit better to me.
Regarding the message displayed, it is not dynamic/changeable, which can be inconvenient if a moderator wants to change it. Same thing for the channel id. Maybe storing for now the content and id in variables could make the job? In the near future, the bot will be connected to a Supabase instance, which will be easier to store this kind of information.
What do you think about it?

Thank you for the review @Olyno .

I'm just not sure about the term "help" for the command, in the sense that the "/help" commands are more there to display the list of commands.

I agree. The naming should be changed. I noticed this shortly after testing it later.

it is not dynamic/changeable, which can be inconvenient if a moderator wants to change it. Same thing for the channel id. Maybe storing for now the content and id in variables could make the job

Right now, the channel id is stored in .env. I didn't want to hardcode it within the script, but that's easy to change. For the content, it might be a bit more tricky as we insert the user's name and channel ID into it. Therefore, we would need placeholders in this text. It is still possible to do so.

I was planning to integrate a similar command but parsing the messages with chatgpt. So if the message looks like a help request, then the bot asks the user to go to the help channel, or even create a post for him.

I also thought of using AI to detect text but thought that a) simple first would be good b) I was not certain if Supabase wanted to use openai in the first place. I think this can be improved in later versions. It would have to read messages in the chat instead of slash commands however. I am not sure what's Discord plan on this feature for large server and whether bot needs to be verified.

In summary, I will rename the routes and move the variables to hardcoded constants instead for now. Feel free to tell me if I have made any mistakes.

Hello @Olyno , I have updated the code as per above. Thank you.


Editing occurrence of recurring event broken

Steps to reproduce

Click on recurring event in calendar view, click Edit occurrence
Change date, description, and labels.
Click Update Event

Observed problems

Description changed for all occurrences
Date not changed
Tags gone
Can't edit again because seriesData is not set

Could not reproduce this specifically, probably because we fixed the label issue first. Did find another timezones bug though, goddammit. Leaving this open for a bit in case we run into it again.

Still haven't run into this again, closing.


Added Bike_Prices.csv

🛠 Fixes Issue

👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Good one @KNuckleeHEADD
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to the profile section from the top right-hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard!
And don’t forget to share your achievement with your friends.


Add a variable for Availability Zones

what
Change the default Availability Zones from Any 2 to  Any.
why
If there is more than 2 AZs in a region, use all AZs:
Availability Zones (AZs) are distinct locations within a region that are engineered to be isolated from failures in other AZs and provide inexpensive, low-latency network connectivity to other AZs in the same region. Choose the number of AZs for your instances.
For example region eu-west-1 and eu-west-3 has 3 differents AZs.
I think there is no need to provide a variable for this; it works on all cases (1 instance, 3 instances, 6 instances, etc...).
reference

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html
https://github.com/jsonmaur/aws-regions (unofficial list of all AZs per regions)

FYI, Travis-ci has some isues with public builds: https://www.traviscistatus.com/incidents/69gf0dn51g0v

There are practical implications of switching to Any. Your argument though is strong, but I would prefer making it a variable since the answer is "it depends" and prefer not to be that opinionated on this point.
My "weak" counter-arguments:

Interzone data transfers are billed extra. If you're running in more zones and doing intercommunication between instances, then costs will be higher
If one zone has fewer instances than the other, it can get overloaded due to the semantics of how ELBs distribute traffic. Having fewer zones reduces the likelihood of that happening.

It's ok, i'll create a variable for this to override the sane default.

Done


Enzyme (React Component Unit-Testing)

Re: #261

@jrodl3r Excellent changes - and thanks for pushing this through!

oops... I merged before I pushed =(


Add simple queue support for delayed_job

I would like to suggest the inclusion of queuing semantics into jobs/delayed_job.rb for those who use the latest versions of DJ.  Happy to send a very simple pull request if you would be interested.
This enables me (and anyone else who would benefit) to distinctly manage delayed paperclip tasks without needing to ensure all other tasks are kept off the main queue.
Thanks
k.

+1

Looks like it's fixed in https://github.com/jrgifford/delayed_paperclip/pull/169


Upgrade RES to 0.26.0

Does test work at all? On master I have fails plus there is missing a step for database cleaning between tests.

This change is

Spoko, yet unmergable now. I took the ideas into https://github.com/RailsEventStore/cqrs-es-sample-with-res/commit/8e1b29aaf7b8b5a43f084c3606616f935070f23d thought. Thanks!


Support IReference projection to T?

Partial support (for numeric types) implemented as of https://github.com/tristanlabelle/swift-winrt/commit/07e5fa6c286f168a3e0283d4e679fa7196943d6f

Extended support for all primitive types implemented as of https://github.com/tristanlabelle/swift-winrt/commit/fe65bdfa2b313ebac2ed59acbabbd3b2df227267

Implementing for structs and enums in https://github.com/tristanlabelle/swift-winrt/pull/86


User name change in Readme

Hey, instead of @nathanletwory you can use @jesterKing, which is my github name :)

Okay, I have changed your username. :-)


Enable multi-arch docker builds

Hi there, me again :)
Another thing that would help adoption is to remove the hard-coded requirement of amd64 (and linux), when building the binary either on-host or in-container.
As a quick example, I removed the GOOS and GOARCH vars from the dockerfile, then subsequently built and pushed this image to my public dockerhub here: https://hub.docker.com/r/dancarbone/danielchalef-mrfparse/tags
You can see that there are two images present for this tag, one arm64, one amd64.  This was done using the modified Dockerfile in this PR and the following command:
docker buildx build --platform linux/arm64,linux/amd64 -t dancarbone/danielchalef-mrfparse --push .

The parser is designed to be memory and CPU efficient, and easily containerized. It will run on any modern cloud container platform (and potentially cloud function infrastructure).

Input and Output paths can be local filesytem paths or AWS S3 and Google Cloud Storage paths.

Usage:
  mrfparse [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  help        Help about any command
  parse       Parse in-network MRF files. Expects split NDJSON files as input.
  pipeline    Parse in-network MRF files. Input is a single MRF JSON file. Output is a parquet fileset.
  split       Split JSON files.

Flags:
      --config string       config file (default config.yaml)
      --cpuprofile string   Write CPU profile to this file
  -h, --help                help for mrfparse
      --memprofile string   Write memory profile to this file

Use "mrfparse [command] --help" for more information about a command.

Enabling multi-arch builds would let the ARM users on my team run this locally without the need to build it themselves, let alone have golang installed :)

Thanks for the suggestion. I'd love to add ARM64 support, however, I've made extensive use of simdjson which does not yet support ARM64 NEON intrinsics. Hence the requirement for a CPU with AVX2 and CLMUL instructions.

Hmm, so I'm not super familiar with the simdjson project, but according to their homepage ARM NEON is supported.
I will hopefully have time this weekend to dig in a smidge, see if I can test this properly :)

The reference C implementation does indeed support ARM64 NEON. Unfortunately, the Go port does not: https://github.com/minio/simdjson-go
There’s an open issue regarding this: https://github.com/minio/simdjson-go/issues/51
On Fri, Jan 13 2023 at 8:47 PM, Daniel Carbone < @.*** > wrote:

Hmm, so I'm not super familiar with the simdjson project, but according to
their homepage ( https://simdjson.org/about/ ) ARM NEON is supported.
I will hopefully have time this weekend to dig in a smidge, see if I can
test this properly :)
—
Reply to this email directly, view it on GitHub (
https://github.com/danielchalef/mrfparse/pull/2#issuecomment-1382660758 ) ,
or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AABAAZ53KUZ54JS6HQH2UCLWSIVXXANCNFSM6AAAAAAT25FI4E
).
You are receiving this because you commented. Message ID: <danielchalef/mrfparse/pull/2/c1382660758
@ github. com>

Ah, I see!  They're using an assembly generator.  Unfortunately looks like the generator itself has been archived :(
Hmm...that's unfortunate.  Would you be willing to accept a PR that allows for the use of the admittedly slower internal go json handling?  I haven't had a look to check the feasibility of this, but it would be a stop-gap until a more efficient solution could be found.

@dcarbone How about we implement this for development / test purposes? https://github.com/kiwicom/fakesimdjson
Happy to accept a PR.

Just as an update, i've not forgotten about this PR.  I added ParseND functionality to the upstream fakesimdjson lib, and will be working on the actual pr for this repo soon :)
Relevant PR here: https://github.com/kiwicom/fakesimdjson/pull/2

Just as an update, i've not forgotten about this PR. I added ParseND functionality to the upstream fakesimdjson lib, and will be working on the actual pr for this repo soon :)
Relevant PR here: kiwicom/fakesimdjson#2

Great to hear!

closing in favor of #10


Issue #998: migrate CLI commands

This is the first of the CLI commands to be moved back to the catalog repository (from sample-project).
Also refactored to make testable and test coverage.

Ready for next review.


Kubernetes CRD improvements

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
This is just an epic to track several improvements that should be considered for the KubernetesCRD  provider before the next major release.
In no particular order:

https://github.com/traefik/traefik/issues/7621
https://github.com/traefik/traefik/issues/6053
https://github.com/traefik/traefik/issues/9124
https://github.com/traefik/traefik/issues/8541
https://github.com/traefik/traefik/issues/5865
https://github.com/traefik/traefik/issues/4655

waiting for https://github.com/kubernetes-sigs/external-dns/pull/3055 to be merged

If you feel there is an improvement that should be considered and is not listed, even if it requires a breaking change, we would love to hear you suggestions!

Will #9578 be part of milestone 3.0 ?

Hey @ErikLundJensen, this issue is simply a collection of all of the issues we want to consider. Part of our decision will be determined by the traction each issue gets and how impactful the expected use cases are for the majority of users. If you really need #9578, you should react on the issue and let us know your use case so we can take that into account.

There is an ongoing conversation about Updating the apiVersion in Kubernetes CRD definitions in the PR (linked). You can find the latest information here.

We close this umbrella issue which is outdated.
However, we keep the sub-issues open to continue working on them independently.


onResizeStop, onResize not working properly

I am using onResizeStop and onResize to determine the size of the item after resizing. Problem: onResizeStop fires when the mouse is released. After releasing the mouse, the item snaps to the grid, thus changing the size.
Expected behaviour:
onResizeStop firing after the item snaps back to the grid
Actual behaviour:
onResizeStop fires after the mouse has been released, before the item snaps to the grid.

[x] Bug
[ ] Feature Request
[ ] Question

You're looking for onLayoutChange then, which will reflect the size in
grid units.
0x6c23 wrote:

I am using onResizeStop and onResize to determine the size of the item
after resizing. Problem: onResizeStop fires when the mouse is
released. After releasing the mouse, the item snaps to the grid, thus
changing the size.
Expected behaviour:
onResizeStop firing after the item snaps back to the grid
Actual behaviour:
onResizeStop fires after the mouse has been released, before the item
snaps to the grid.

Bug
Feature Request
Question

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/issues/648, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABJFP00go_E4q-FLgy54LGWJCTS68wUwks5stO4xgaJpZM4P8l6a.

Thanks for that blazing fast answer. I will use onLayoutChange then, but I have to calculate the size now.
I can get the height with:


Feature/cloud material

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 68.15287% with 50 lines in your changes missing coverage. Please review.

Project coverage is 78.25%. Comparing base (14f4d2d) to head (11fc88a).

Files with missing lines
Patch %
Lines

src/model/cloud.rs
0.00%
19 Missing :warning:

src/load/mod.rs
73.52%
9 Missing :warning:

src/model/data.rs
84.37%
5 Missing :warning:

src/model/mod.rs
61.53%
5 Missing :warning:

src/observers.rs
68.75%
5 Missing :warning:

src/model/modify.rs
69.23%
4 Missing :warning:

src/model/palette.rs
88.88%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
- Coverage   81.49%   78.25%   -3.24%
==========================================
  Files          13       14       +1
  Lines         670      768      +98
==========================================
+ Hits          546      601      +55
- Misses        124      167      +43

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


Need more translations

I'd love to have nbvcxz translated into as many languages as possible.  Currently, it's got an English and French translation.  I sadly am not multilingual, so I can't really do anything here.  I am hoping some users who are multilingual can take a little bit of time to translate the not terribly large amount of text into whatever languages they are able to.
The two files which need to be translated to another language can be found here: https://github.com/GoSimpleLLC/nbvcxz/blob/master/src/main/resources/feedback.properties
and here: https://github.com/GoSimpleLLC/nbvcxz/blob/master/src/main/resources/main.properties
Edit: We have had some translations completed already, so i'll list them here.
French
Russian
Ukrainian
Afrikaans
If you know the language, feel free to review each: https://github.com/GoSimpleLLC/nbvcxz/tree/master/src/main/resources

I could translate to russian and ukrainian.

@scadgek That would be very appreciated!

There we go, we now have support for Russian.

@Tostino thanks for the screenshot, I see I misunderstood some wordings - will patch it now :)

@scadgek in English I didn't bother doing singular of any time values. It's a little weird in English to say "1 seconds" too, but it was simpler than having to deal with changing between singular and plural based on the value.

I can translate to Italian...

@svzdvd Would love to have an Italian translation.

Is there anyone who could do a Spanish translation? That is one I was really hoping to support.

I could do a Hungarian translation if you want.

@vfspirit Sounds good, would appreciate it.

There are a few lines that could be translated either as formal or informal. Which one should I prefer?

@vfspirit Informal is fine. I just merged.
Appreciate it.

I want to thank @everyone who contributed their help with translating.  I have just released version 1.4.0 which now supports all of the languages you have helped contribute.


docs: fix typo in README

What
Fixes a typo in the docs.

@adampash Sorry for the late and thank you for your contribution 🫶🏻

@all-contributors please add @adampash  for doc


Adjusting to HTML Java API version 1.5

I am about to make first Apache release of HTML/Java API after the migration of NetBeans from Oracle to Apache. Apache does source releases, as such I prepared incubating-netbeans-html4j-1.5.zip ZIP with sources at:
https://builds.apache.org/view/Incubator Projects/job/incubator-netbeans-html4j-release/16/
I tried to adjust TeaVM to support it. The only real missing piece was ClassValue - that is now used during registration of @Model classes. Added.
Then the compilation of the TCK tests failed on various missing elements. I've added them throwing TSecurityException (which is valid behavior). When at it I also added TEventListener and TEventObject - I hope it doesn't add any unnecessary weight - as TeaVM will just ignore these classes, when not used, right?
I plan to start the HTML/Java 1.5 review at Apache mailing list on Sunday. It shall take at least 72h. If my patch is wrong, please speak up by then. It is still possible to change version 1.5 a bit.

Travis can't build this PR. It shows following error:
[ERROR] Failed to execute goal on project teavm-html4j: Could not resolve dependencies for project org.teavm:teavm-html4j:jar:0.6.0-dev-400: The following artifacts could not be resolved: org.netbeans.html:net.java.html.boot:jar:1.5, org.netbeans.html:net.java.html.json.tck:jar:1.5, org.netbeans.html:ko4j:jar:1.5: Could not find artifact org.netbeans.html:net.java.html.boot:jar:1.5 in central (http://repo.maven.apache.org/maven2) -> [Help 1]

So I can't merge this PR until your resolve this problem.

Right. The HTML/Java 1.5 hasn't been released yet. We need to wait for that before merging. However things seem to work locally, so I am confident 1.5 version is compatible with TeaVM.

What about this PR? Can I merge it? When are you going to publish all necessary artifacts?

HTML/Java API 1.5 bits have been published yesterday, thus I think this PR can now be merged. Thanks for your patience.


Freezes up intermittently on only one iPhone

Hello,
The classification app works on many phones but on one iPhone XS it freezes up. I was wondering if anyone had some ideas why.
So here are the details:
iOS:12.2
The behavior is that it works for a few seconds then it freezes for 1-2 seconds and it works again, and this freezing continues.
I turned on Zombie Objects and get many of this error from the devices simulator console whenever it freezes
2019-03-20 12:58:34.740735-0400 snobBog3[7837:2621978] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
I noticed I also get this warning before
Tiled GPU perf. warning: RenderTexture color surface (1080x1920) was not cleared/discarded.
The problem is definitely is somewhere in the classification code, because all the AR stuff works when the vision script is disabled.
I have tried (that I can remember):

updating swift version to newest version
getting rid of all unnecessary shaders
lowering the maxClassificationResults (trying to not overload the GPU)
updating iphone system/closing all other apps/reinstalling etc

I tested it on a different iPhone XS and it works great.
I have never developed an app before that deals with swift or CoreML so anything you may seem as obvious to try may save me more weeks of headaches! Is there something I should be looking at that would tell me why it works on one iPhoneXS but not another?
Thanks for reading I anticipate & appreciate a response

Hi CharStiles,
Could you please let me know how do you create or pass the CVPixelBuffer to the native component? I had this issue before when I used Metal textures on iOS 12.0 and it turned out to be a driver bug.
"I tested it on a different iPhone XS and it works great."
Are both of those iPhone on the same iOS version?
Best regards,
Adam

Thank you for your fast response!

I haven't changed any of the code in this repo that much, I am using it as is. Sorry if I am not understanding your question correctly!
How did you solve the driver bug (if there is a solution)?
If I remember correctly they were the same iOS version, but I inquired the owner of said phone to make sure.

Char

Hi,
I meant what example did you base your app on? There are 2 ARKit examples included in this repo.
Thanks,
Adam

You mean classification vs rectangle? I mentioned I am using the classification example. Sorry I should have made that more clear :)

There are actually 4 examples for classification. Two of them use ARKit. :)

Ah! My apologies! I am using the first one (ARKitExample.cs), my bad I didn't realize there was a difference.

I pushed a change yesterday. The only file that's been modified is this:
UnityVision-iOS/Assets/Scripts/Possible/Vision/Plugins/iOS/VisionNative.swift
Can you please pull and try to see if your problem persists? If this doesn't solve the issue, try using the second example.
Also, did you find out the version numbers on those iPhones?

Hi Adam,
I had a meeting with the person with the problematic iPhone, and THANK YOU the new script worked like a charm!
The version number is A1920. Also I mentioned a while back that I inquired if the other non-problematic iPhone XS had the same iOS version, he said he doesnt remember, alas.
So my naive stab at what you have done is replace the buffer that holds the pixels from the camera from ciImage to cvPixelBuffer? I am in awe at how quickly and efficiently you solved my problem.
Thank you again,
Char


Issue with EnderIO...

Sorry to put this here, this may be innappropriate, because I understand that this is a bug tracker and it's purpose is to notify you guys of whatever issues the community comes across with the mod.
I don't have a bug or issue to report. I just want to say that EnderIO is by far my favorite mod that I have ever played with, and I want to heap all of the possible praise and adoration on it's authors. I hope you all will support this mod as long as possible, and keep up the amazing work.
o7 -bnzjnz

This is definitely the wrong place. Twitter, or IRC, or Minecraft Forums, or CurseForge, all would have been much better suited.
However, we appreciate the kind words.


Confirmation Warning when creating a v1.23-v1.24 RKE1/2 Cluster with PSPs enabled

Users running Kubernetes v1.23 - v1.24 should have a banner asking them to migrate to PSA/PSSs in the same places as we're doing for v1.25 with the phasing out of PSPs but it's more of a case of guidance before they upgrade.
An investigation is needed into the impact of maintaining PSPs in a cluster that no longer supports them. Preliminary findings show issues with orphaned PSP resources. It should be evaluated whether users are prevented from upgrading to 1.25 altogether with Rancher Launched Kubernetes and Distributions until PSPs are completely disabled in those clusters.
(RKE1 upgrades to 1.25 will not be allowed if PSP is enabled, back-end will throw error;
for RKE2, the upgrades are prevented when non-default RKE2 PSP is used -- by default RKE2 has PSP enabled and applies "allow all" default PSP)

This will relate to another request: UI Banners Warning Users on v1.23-v1.24 with PSPs enabled they need to migrate to PSA/PSSs in Cluster Edit and PSP Configuration Pages.
Checking if that's being tracked anywhere already; failing that, it's another ticket.

If I understand correctly, this is about showing the following alerts:

An informational alert when a user CREATES any version of cluster that PSPs no longer exist in >=1.25
A warning alert on EXISTING clusters <1.25 with PSPs enabled that the user needs to migrate to PSA/PSSs
An error alert when a user UPGRADES <1.25 clusters with PSPs enabled to 1.25

Previously titled as a Confirmation Warning Modal.

There's work already merged that already has some wording around what we tell users about PSPs and 1.25.
Issue: https://github.com/rancher/dashboard/issues/7553
PR: https://github.com/rancher/dashboard/pull/7821

@cnotv is the primary engineer working on the PSA/PSS work so if help on wording and behaviour is needed, he can assist.

In the planning I mentioned something but we didn't really discuss it, I'd like to let it here written so at least we can consider it as an option.
A warning message without any context or guidance to the user is unlikely to provide a good UX. Sure DevOps engineers will know how to proceed, but we want developers and other kinds of professionals to also use Rancher. It might not be 100% clear to them what to do if they just read "PSP is going to be deprecated".
I don't have an answer yet, maybe guiding the user here is a bit overkilling, but I guess we could at least provide a doc link or similar, e.g. this post about the PSP deprecation on the Kubernetes' blog.
I'm talking here with little context about the whole thing, so I might be completely wrong; just wanted to mention this as a general rule, not only warning users but also providing context, solutions and/or guidance.

tested on v2.7-head (3c1e7db):

rke2 new 1.24.x or below cluster - PASS

rke2 new 1.25.x cluster - PASS however there is a space missing in podSecurity Admission banner

rke2 upgrade from 1.24.x to 1.25 with PSP enabled - PASS

rke2 upgrade from 1.24.x to 1.25 without any PSP - Currently unable to test (PSP defaults to RKE Default in UI) - FAIL (can file a separate ticket if this is not expected behavior, please provide feedback/comment for this)

RKE1 - seems to not have been changed, looking at the linked PRs. Though this ticket title has rke1/2 mentioned. Will there be an update to the banners there as well? Currently there is only a generic banner in the advanced options section, that does not change based on the current k8s version, nor if PSP is enabled/disabled. (please provide feedback/comment for this)

@slickwarren Please create a separated issue for RKE1.
For the RKE2, displaying RKE Default means no picked PSP from the UI, therefore there is nothing to test.

ok thanks for the update, linked the RKE1 ticket above and confirmed with the team for PSP messaging. Closing this issue


Fix/minor UI changes

Minor ui changes
Added Go Community Code of Conduct
Added description for sponsored tickets

Fixes #15


Add cumulative error checking to CoreFX tests

The check was being done on Unix, but not on Windows.
This fixes the issues @jkotas pointed out in #6007. Also fixes #5901 .

Seems like we've regressed 3 tests, which cause Access Violations and crash the XUnit runner (so no test results are returned).
Disabled them for now.

Thanks