feat(go): run go fmt and go build after code generation

To ensure the generated go code is formatted and compiles by executing go fmt
and go build on the output directory.
Similar to other languages, in order to be able to build the go module within mono-repos (and in the jsii repo itself), we need to be able to resolve local dependencies. This is done in the following way:

Create a list of dist/go candidates (based on the jsii.outdir relative to dependency package dirs)
Add to this list the current outDir, in case --outdir is used
Iterate over the module's dependencies and for each candidate dist directory, check if we can find a <goModule>/go.mod file that contains a module <moduleName> directive.
If we find one, we append a replace directive with a relative path to our own go.mod which tells go fmt and go build to find the dependency locally.
At the end, we restore the original go.mod file so that the published one will not include the replace directives.

Resolves #2463

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 33cae0fa36db2d6a221b8743de0ec9a834167f7f
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 33cae0fa36db2d6a221b8743de0ec9a834167f7f
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: ea67f2fcb3b1f2459c536276b490bf5644550f1e
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: ea67f2fcb3b1f2459c536276b490bf5644550f1e
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: a11a9955c2da7fe047344445cb3c817cd4597044
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: a11a9955c2da7fe047344445cb3c817cd4597044
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 141f85c59d95d368c406f5814f0bf52189938476
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 141f85c59d95d368c406f5814f0bf52189938476
Result: SUCCEEDED
Build Logs (available for 30 days)

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

Code looks good. Wondering if we should exclude 'go build' if the code-only option is set? Formatting would still be wanted so resolving dependencies is still necessary.

Currently both fmt and build are executed only when we are actually building. I can look into resolving deps in the codegen case but I am currently leaning towards not formatting at all for now.

Code looks good. Wondering if we should exclude 'go build' if the code-only option is set? Formatting would still be wanted so resolving dependencies is still necessary.

Currently both fmt and build are executed only when we are actually building. I can look into resolving deps in the codegen case but I am currently leaning towards not formatting at all for now.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 90926b88adde67531d5b52edf88684ed504117fd
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 90926b88adde67531d5b52edf88684ed504117fd
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 453b27cf249231e15cb9d02622c7e92579f836f8
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 453b27cf249231e15cb9d02622c7e92579f836f8
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: c576afbbdd09d0978149308797ce5ffc5188c81e
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: c576afbbdd09d0978149308797ce5ffc5188c81e
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 24cc541a88af0a0eca2b0aaaba4192ce1edcc2e0
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 24cc541a88af0a0eca2b0aaaba4192ce1edcc2e0
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: d3f962e2a1900e510f9b9bd8b86876d11e3812ea
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: d3f962e2a1900e510f9b9bd8b86876d11e3812ea
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: c296153dafa25c90e09bfb51ef8d1df57459193c
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: c296153dafa25c90e09bfb51ef8d1df57459193c
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 32e3851c5d95233390da610031cbd500565ec943
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 32e3851c5d95233390da610031cbd500565ec943
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 31c380a07b3046ff3f8fc10ac69f2f8c8609beb5
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 31c380a07b3046ff3f8fc10ac69f2f8c8609beb5
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 12b94661424603935677744e0a19bb0b9a9d2f09
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 12b94661424603935677744e0a19bb0b9a9d2f09
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 780d45654b361757f7282045ec6cbd087bb2c3c9
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 780d45654b361757f7282045ec6cbd087bb2c3c9
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 0ece1038e75853cb39b16f72e6f102ee0fb24326
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 0ece1038e75853cb39b16f72e6f102ee0fb24326
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 0ece1038e75853cb39b16f72e6f102ee0fb24326
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 0ece1038e75853cb39b16f72e6f102ee0fb24326
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: d92f8458f5ca8e7a239c443b70bc0dddf6aaa1df
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: d92f8458f5ca8e7a239c443b70bc0dddf6aaa1df
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: d9208b306829dcc5b6e739721a29f17637e65b70
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: d9208b306829dcc5b6e739721a29f17637e65b70
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: f718d32f659546838ef3221cbd210eb3ddec63b7
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: f718d32f659546838ef3221cbd210eb3ddec63b7
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: f718d32f659546838ef3221cbd210eb3ddec63b7
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: f718d32f659546838ef3221cbd210eb3ddec63b7
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: e1d1a1143b13ab8ebf24e3da7dca2159edf371df
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: e1d1a1143b13ab8ebf24e3da7dca2159edf371df
Result: SUCCEEDED
Build Logs (available for 30 days)

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


SyntaxError: invalid syntax

E:\manim-master>python extract_scene.py -p example_scenes.py SquareToCircle
Traceback (most recent call last):
File "extract_scene.py", line 13, in
from constants import *
File "E:\manim-master\constants.py", line 7
try:
^
SyntaxError: invalid syntax

Which version of python are you using?

3.7
i just update it, but it still tells me the same error

E:\manim-master>python extract_scene.py example_scenes.py SquareToCircle -pl
Traceback (most recent call last):
File "extract_scene.py", line 13, in
from constants import *
File "E:\manim-master\constants.py", line 7
try:
^
SyntaxError: invalid syntax
E:\manim-master>python --version
Python 3.7.0

also, when i finished to install all the requirements, it said that there's an error in the Microsoft Visual Studio
error: command 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\cl.exe' failed with exit status 2                                                                                ----------------------------------------
Command ""e:\new folder\python.exe" -u -c "import setuptools, tokenize;file='C:\Users\admin\AppData\Local\Temp\pip-install-x5bt_o0j\pycairo\setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record C:\Users\admin\AppData\Local\Temp\pip-record-_z978wx5\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:\Users\admin\AppData\Local\Temp\pip-install-x5bt_o0j\pycairo\

Are you still seeing this problem?

Not anymore, thanks guys


LCFS - Transfer details dynamic sentence on new transfer page

Description:

Develop the transfers details sentence that allows the user to input information about the transfer, including the quantity of compliance units (credits) being transferred, the organization receiving the credits (i.e., the transferee), the fair market value of any consideration, in CAD $ (i.e., price per unit).
All three input fields are required
Quantity field restrictions: must be a number, must be positive (cannot be negative), must be a whole number (no decimals)
Select an organization: drop-down menu where the user can select a transfer partner, list is curated to show organizations within the database that are registered, list does not show one's own organization. Note that the registration functionality is handled in a different card lcfs #222
Fair market value of any consideration, in CAD (i.e., price per unit) restrictions: must be a number, must be a positive number (cannot be negative), decimals are allowed but restrict to no more than two decimal places
The total value at the end of the sentence is dynamic: it defaults / starts at $0.00 but then updates as the user inputs the required information. The calculation is quantity of units multiplied by the price per unit.
See wireframe for sentence structure/language and messaging within input fields

Note: similar functionality as listed above exists in TFRS transfer feature
Wireframe: https://preview.uxpin.com/59145260c7d8cc48969ac79401cc03d84843c3d9#/pages/164975114/simulate/no-panels
Purpose and benefit to user:
Allows the user to enter the required information for initiating a transfer
Acceptance Criteria:

[ ] Given I am a BCeID user I should have the option to enter the transfer value and to choose the organization that I want to transfer.

Development Checklist:

[ ] fair market value needs to be added to the data model and name the column as price_per_unit.

Notes:

Hey team! Please add your planning poker estimate with Zenhub @AlexZorkin @hamed-valiollahi @jig-patel @kevin-hashimoto @prv-proton

Requires access to BCeID user account to test.

Input fields are working, but there is a little bit of left over text in the introductory sentence "&nbsp". Please see screenshot:


Release 43

This is a PR for Release 43
Status:

[x] In development
[x] In testing at NRK
[ ] Finalize and merge

Release 43 overall status: https://github.com/nrkno/Sofie-TV-automation/issues/45

This release is being skipped. The changes here will become part of #722


List of OSM buildings that don't match with SF building data

@bdon This is probably out scope of the initial import but can you share the 25% of buildings that don't match?  We can definitively improve tracing of these buildings from imagery and probably match our overlap criteria in the next round of import.
cc @talllguy @chtnha

added csv here https://github.com/osmlab/sf_building_height_import/blob/master/misc/nonmatching_buildings.csv

negative OSM IDs are relations

Thanks @bdon! I did a matching of the OSM ids from your list and made a TMS for JOSM (click this link to load in JOSM).
A few observations below (Cyan-SFOpenData, Magenta-OSM non-matching):

3 adjacent buildings in OSM, single building in SF OpenData.

Misaligned buildings in OSM.

Single building in OSM, individual units in SF OpenData.
Not all mis-matches means OSM data is wrong so each building should be verified with imagery or street level photos (i.e. Mapillary or OpenStreetView).  I propose we create a TM project to fix them.
@bdon Can we create a TM project for this? It's more or less the inverse of what we are doing for the height import.
Next actions

[ ] Create a TM project for non-matching buildings @bdon
[ ] Mapbox team to work on this project while the first phase of height import is ongoing
[ ] Import height for the fixed buildings once first phase is done.

cc @chtnha

@maning @bdon  is it confirmed that the alignment of the SF open data is accurate? If so, then that should be used as the reference over satellite imagery to realign.

is it confirmed that the alignment of the SF open data is accurate?

@planemad I can't say 100%, but for the areas I've checked, SF Open Data aligns very well to Strava, Bing and SF Lidar TMS.  We can use SF Open Data as the main reference but I'd avoid recommending it as a single source of reference.

@planemad refer to @bqb's comments in this issue: https://github.com/osmlab/sf_building_height_import/issues/12

Use 👇 for splitting buildings

Here is video demonstration - https://youtu.be/7GQtNnjIO0Q?t=3m29s
/cc @chtnha @maning


viewer lists KOIs that are not present

It would be good to remove the entries where the files do not exist.

This should be fixed now! The table will show koi_id rows that correspond with the koi_ids in the data_directory. If any show errors in loading plot, or 'data not found', it now most likely means the pipeline failed for that KOI. (there is a folder in the data_directory with no data in it)


Noise cancellation

The FAQ said "In sphinxbase/pocketsphinx/sphinxtrain it's 'remove_noise' option." How can Activate it?, Can I activate it from Android code or I should recompile pocketsphinx full library?

It is activated by default.
To deactivate you can use config.set_boolean("-remove_noise", false) in java source code.

Thank you very much


two way talk on HA

the feature about talking doesn't expose to HA
Describe alternatives you've considered
have the two way talk button  expose to HA

Duplicate. Kindly search for issues before opening a new one.

You also opened the previous one. Stop.


github issue template

Codecov Report

Merging #33 (32671e3) into main (91d68f3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #33   +/-   ##
=======================================
  Coverage   92.95%   92.95%
=======================================
  Files           5        5
  Lines         227      227
=======================================
  Hits          211      211
  Misses         16       16

Help us with your feedback. Take ten seconds to tell us how you rate us.


Reporting Git failure on Discard changes

VSCode Version: 1.18.1
OS Version: Windows 10
Git: git version 2.15.0.windows.1
Node: v6.9.1

Steps to Reproduce:

Stage a change
Click Discard all changes

In fact, it discards the changes, but there's always an annoying messsage: Error: Git: Failed to execute git

Is there anything I could do on my part to help troubleshooting this issue? The git output says nothing about it.

This always reproduces? Can you send us a screen recording?

It only happened on a specific repo.
I found the culprit in this post-checkout hook:
#!/usr/bin/env bash
# MIT © Sindre Sorhus - sindresorhus.com

# git hook to run a command after `git checkout branchname` if a specified file was changed
# Run `chmod +x post-checkout` to make it executable then put it into `.git/hooks/`.

changed_files="$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)"

check_run() {
	echo "$changed_files" | grep --quiet "$1" && eval "$2"
}

check_run package.json "npm run update"

It was returning always exit code 1, so VS code would show a failure.
"Solved" by adding a return 0. Don't know why it didn't happen before (like a couple weeks, since I moved to a new computer & reinstalled everything)
Thanks for your help!


Types at DefinitelyTyped needs to be updated after new major version (or preferably, moved here)

Describe the bug
The current types at DefinitelyTyped are for react-datepicker version 3, with e.g. popper.js version 1. This means, for example, that the popperModifiers type claimed by Typescript doesn't match up at all with what's shown in the examples (https://reactdatepicker.com/#example-configure-popper-properties).
To Reproduce
Use Typescript, install react-datepicker@4, and try to use e.g. the popperModifiers prop.
Expected behavior
Generally I expect packages to come with their own up-to-date types these days, but if not, then I expect to find types at DefinitelyTyped and that they least are somewhat correct.
I looked into creating a PR myself, but decided to create an issue here instead. I'm not familiar enough with react-datepicker internals nor how package definitions in DefinitelyTyped actually works to mess with it. And, regardless, the PR process seem to involve the ones originally adding the types anyways, so I can't do it fully on my own anyways. For something as popular as react-datepicker, I feel it's best this is fixed by someone who knows what they're doing. 😬

I've update DefinitelyTyped so it uses popper v2 typings, the PR is here for reference https://github.com/DefinitelyTyped/DefinitelyTyped/pull/54037

Types over at DefinitelyTyped have now been updated, merged, and released. Just tested it locally, and seems I can remove my // @ts-ignore lines now.
Thank you! 🙏


Publishers must accept data submission policy before adding datasets to a collection

Story
Publishers need to attest that their private Data is not identifiable and grant CZI permission to use, display and create derivative works (e.g. visualizations) of the Data.
If the data set is public (It could be downloaded from a public URL), no attestation is required.
The portal will trust but verify PII compliance.
Updating Attestation Questions
Many of the original questions can be eliminated in self-publishing scenarios, since the Publisher controls the visibility of their datasets. Indicated below as strikethroughs. Validating the updated list with Shawn.
From the Researcher Attestation Form :

The Data I share with CZI will be made public via the Cellxgene Public Portal
I give CZI permission to use, display and create derivative works (e.g. visualizations) of this Data for purposes of offering the Cellxgene Public Portal, and I have the authority to give this permission.
It is my responsibility to ensure that this Data is not identifiable. In particular, I commit that I will remove any direct personal identifiers in the metadata portions of the Data, and that CZI may further contact me if it believes more work is needed to de-identify it.
I understand that if I change my mind about sharing the Data, I will reach out to CZI and they will work with me to remove it from the Cellxgene Public Portal within a reasonable time.

During August 16 Refinement - @ambrosejcarr asked whether:
I give CZI permission to use, display and create derivative works (e.g. visualizations) of this Data for purposes of offering the Cellxgene Public Portal, and I have the authority to give this permission.
needs to be extended to third party consumers downloading datasets for analysis.

August 31 - Requested an update from Trust.

Hey Brian,
Following up here:

Updated Direct Identifiers link (I couldn't edit old one so created a new copy): https://docs.google.com/document/d/1sboOmbafvMh3VYjK1-3MAUt0I13UUJfkQseq8ANLPl8/edit

Updated language for Researcher Attestation:

I give CZI permission to use, display and create derivative works (e.g. visualizations) of this Data for purposes of offering the Cellxgene Public Portal, and I have the authority to give this permission.
It is my responsibility to ensure that this Data is not identifiable. In particular, I commit that I will remove any direct personal identifiers in the metadata portions of the Data, and that CZI may further contact me if it believes more work is needed to de-identify it.
If I choose to publish this data publicly, I understand that anyone with access to Cellxgene will be able to access it subject to a CC-BY license, meaning they can download, share, and adapt the data without restriction beyond providing attribution to me.

CC-BY is the license that was adopted by the DCP, but I am concerned it will produce problems for data re-use, and I believe it to be more restrictive than the use agreements for public archives. GEO dodges the question a bit, but the ENA is quite permissive. I would prefer we use lighter-weight means than licensing to enforce proper attribution of data donors, and request data in CC0.
In particular, I am concerned that integration of multiple datasets will result in significant license stacking (all original licenses must be linked). This becomes worse if users then wish to integrate organs which are themselves composed of integrated sets of primary data. It seems better to design our software to automate citing (which meets the same user need) rather than do that and add the enforcement of a license.

Pinged @shawnliu03 to review the comment above.

Per the September 29 refinement for self-publication, we agreed that attestation should occur in the Create Collection flow rather than the Add Dataset flow.  Moving to Publishers want to create a private collection of related dataset submissions.

Hi @ambrosejcarr and @brianraymor -- thanks for your patience.
I'm OK with CC0 (do anything, no restrictions) instead of CC-BY (do anything, but give me attribution by citing to me), but want to call out one point and ask one question about our view on citations.

The reason GEO dodges this is because not all authors uploading to GEO will be able to give maximal downstream rights because their institutions/local law may not let them. That'll be the same with cellxgene. This (e.g. cxg asks you to give cc0 rights for data, but your institution won't allow you to give such permissive rights) is not a reason to avoid CC0, but rather is something I just want to flag as an inherent tension in our clickthrough.
Do I take the CC0 request here to also mean that's our stance vis-a-vis our own site if people pull data from it? That is, if someone takes datasets from cxg and then writes papers or publishes cool analyses, do we want/expect them to cite to cxg the tool?

Hi @shawnliu03
Thank you for the analysis of the GEO use case. What are our options for dealing with the "Geo problem" in cellxgene? Refuse to take the data? Take it without a license and warn the users somehow?
Our community wants the protection of CC-BY in spirit and we will likely implement software solutions that enable easy citation of data that are downloaded for re-use. As an example, each cell could carry a pointer to a DOI, which would enable groups to rapidly identify all the publications they should cite. We will also generate documentation that discloses our expectations: "it is good practice to cite authors when you use their data, and here's how we make it easy...". In practice CC-BY is impractical for the reasons I stated in my earlier comment.

Do I take the CC0 request here to also mean that's our stance vis-a-vis our own site if people pull data from it? That is, if someone takes datasets from cxg and then writes papers or publishes cool analyses, do we want/expect them to cite to cxg the tool?

Correct -- no expectation that cellxgene will receive citations. Our MIT license is an even stronger statement of this. However, we are planning a publication and may put an understated "here's how to cite cellxgene if you want to" point in the documentation somewhere. In my experience, some authors will want to cite it, even though we have no expectation.

@shawnliu03 - per the October 27 Trust XFN - to close on language for:

License
The required Contact (Name and Email) when a collection is created and published. The Contact is the point of contact for questions or PII reports for the datasets in a public collection.

@shawnliu03 - We met with curators from Stanford on November 3. One suggestion that they made related to the data submission policy was to make it clear to publishers that they would be able to withdraw/delete public (published) Collections.

Thanks @brianraymor and @ambrosejcarr for helpful discussion and context here. I started a slack thread on CC-BY vs CC0 with Brian, Ambrose, Arathi because I want to make sure we're aligned on consequences of CC0.
Thanks, also for the Stanford data point. Given above, how about the below updated language:

I give CZI permission to display, distribute, and create derivative works (e.g. visualizations) of this Data for purposes of offering the Cellxgene Public Portal, and I have the authority to give this permission.

It is my responsibility to ensure that this Data is not identifiable. In particular, I commit that I will remove any direct personal identifiers in the metadata portions of the Data, and that CZI may further contact me if it believes more work is needed to de-identify it.

If I choose to publish this data publicly via the Cellxgene Public Portal, I understand that (1) anyone with access to Cellxgene will be able to access it subject to a [CC-BY or CC0 license, meaning they can download, share, and use the data without restriction beyond providing attribution to me. --> final language pending Slack discussion] and (2) the Collection details I've provided above (collection name, description, and my contact info) will be made public on Cellxgene too.

I understand that I have the ability to unpublish data if I later change my mind. Such unpublishing will make the data no longer public on Cellxgene, but it will not undo any prior uses, shares, or downloads of my data.

Closed out the conversation with Shawn on the legalese. Here's the final version:

I give CZI permission to display, distribute, and create derivative works (e.g. visualizations) of this Data for purposes of offering the Cellxgene Public Portal, and I have the authority to give this permission.
It is my responsibility to ensure that this Data is not identifiable. In particular, I commit that I will remove any direct personal identifiers in the metadata portions of the Data, and that CZI may further contact me if it believes more work is needed to de-identify it.
If I choose to publish this data publicly via the Cellxgene Public Portal, I understand that (1) anyone with access to Cellxgene will be able to access it subject to a CC-BY license, meaning they can download, share, and use the data without restriction beyond providing attribution to me and (2) the Collection details I’ve provided above (collection name, description, and my contact info) will be made public on Cellxgene too.
I understand that I have the ability to unpublish data if I later change my mind. Such unpublishing will make the data no longer public on Cellxgene, but it will not undo any prior uses, shares, or downloads of my data.

The new wording has landed in prod, so closing.


Beta compatibility!

This commit makes sdl2-rust build with the beta compiler by making
the following changes:

Replaced !Sync with PhantomData<&mut ()>
Replaced !Send with PhantomData<*mut ()>
Removed NoCopy, since Copy is opt-in not opt-out.
Manually implemented FromPrimitive.
Used crates.io num crate, instead of the unstable std::num.

There are no API changes.

:+1: Compiles on beta for me!
It's worth noting that PhantomData<*mut ()> applies both !Send and !Sync, while PhantomData<&'static mut ()> does nothing.
Adding !Sync functionality to the AudioDeviceLockGuard and EventPump structs shouldn't be a big deal though, I don't think.

I'm not sure that's right. The docs show
impl<T> Sync for *mut T{}

Whereas &mut T is somewhat obviously not Sync, since both threads would be able to mutate the data together.

Interesting! The docs do show that opposite conclusion. However, I click on the [src] link and it shows:
impl<T> !Sync for *mut T { }

http://doc.rust-lang.org/src/core/marker.rs.html#215
Do the docs contain a typographic error?
More proof that *mut T doesn't implement Sync: http://is.gd/rdQfvv

I see! I'll create a rust bug for the docs and update the PR.
Intuitively, it makes a lot of sense that *mut T wouldn't be Sync, unless by the "well, it's already unsafe" logic.

Ok, I think I've tied off all of the loose ends. Now travis builds it using the beta compiler and all of the tests pass.

Great work! I almost thought we either had to give up the !Send / !Sync, or skip beta compatibility.

Score! As this is now beta-compatible, I'm going to publish this as 1.0.0.

:+1: Cheers!

Ah, should we bump to 0.1.0 for this?

I'm thinking 1.0.0. We're already widely-used enough that we shouldn't be making breaking backwards changes.

Actually, I've bottled out. 0.1.0 for now, until Rust is out of beta.

Wait, reminds me of this https://github.com/AngryLawyer/rust-sdl2/issues/302
I make a PR now.


Relax requirements on formatters config

Now when you can register custom formatters, you have no way to pass additional config parameters to it. You are blocked by the strict checking of the format of the config file.

I will probably have a look at it in the coming weeks. My idea was to release the current set of changes, remove deprecations and make a new release and then look at how to improve configuration. I have some ideas, but I have to take a closer look first. Changing the configuration is a bit tricky, because some things like PSR-service discovery break inside the phar.

Resolved in #860


Split Cwd setting is not respected

In the last two releases of VSCode, the Split Cwd setting has not been respected. When a terminal is split, the working directory resets to workspace root, instead of being inherited from the parent terminal, even if the setting is
"terminal.integrated.splitCwd": "inherited"
I wasn't aware of this setting, being used to splitting terminal and remaining in the same directory. But at some point it stopped working.
I also confirmed this behavior in the most recent Insiders build, without any extensions installed.
Env Info
Version: 1.55.0
Commit: c185983a683d14c396952dd432459097bc7f757f
Date: 2021-03-30T16:01:05.981Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.3.0

This is also happening to me. With a monorepo in a subfolder, It's annoying when you're running a process and you want to run another command. You used to be able to split the terminal and have it keep the current working directory, but now you have to cd up to it again.
The recent Terminal Tabs update seemed to introduce it.
Why haven't more people seen this issue? I searched for existing tickets but I didn't notice this one, but when I was typing mine up, this one popped up in "similar issues". @ebeloded can you put "Terminal" in the ticket title to try to get more visibility?
Version: 1.57.1
Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
Date: 2021-06-17T13:26:56.255Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 4.15.0-147-generic

/duplicate https://github.com/microsoft/vscode/issues/121705


auto-generate assists docs and tests

bors r+
🤖

One day, we should render these docs as an HTML page, with small "run" button which loads WASM-compiled rust-analyzer. Should be way better than gifs :)


Fix pick by zone label failure related to new mili db enhancements

Description
Fix the test failure caused by pick by zone tests.
Pick by zone asks if you haven't created ghosts. The mili plugin now does end up creating ghosts, so we go down a different path and the tests fail. We relax the condition so that the mili case can move through as before.

Type of change

[x] Bug fix~~
[ ] New feature
[ ] Documentation update
[ ] Other

How Has This Been Tested?

Ran all tests that use pick by zone and pick by node
databases/samrai.py
meshtype/emptydomains.py
queries/consistencyChecks.py
queries/pick.py
queries/pickNamedArgs.py
queries/queriesOverTime.py
queries/queryMultiWindow.py
quickrecipes/quantitative_operations.py
expressions/tensor_expr.py
hybrid/missingdata.py

Reminders:

Please follow the style guidelines of this project.
Please perform a self-review of your code before submitting a PR and asking others to review it.
Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

[x] I have commented my code where applicable.~~
[ ] I have updated the release notes.
[ ] I have made corresponding changes to the documentation.
[ ] I have added debugging support to my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have confirmed new and existing unit tests pass locally with my changes.~~
[ ] I have added new baselines for any new tests to the repo.
[x] I have NOT made any changes to protocol or public interfaces in an RC branch.~~

Merge w/ develop in #19999


Fix event feed filter suggestions

Overview
Currently, the suggestions on the event feed filter come from the client-run suggestions. This was done to save time, but now that we have a search filter on that page the user experience can be pretty confusing. This issue is to have the event-feed have their own suggestions instead of reusing the client-run suggestions.

@lancewf was this work completed as part of the event feed migration prs?

this has been deprioritized.


Calico Enterprise EKS Workshop

Issue #, if available:
Added the following to /eks-workshop/tree/main/content/beginner/120_network-policies/calico-enterprise

Calico Enterprise registration page
Calico enterprise usecases
Lab 1 - Policy Automation and External Access
Lab 2 - Visibility and Troubleshooting
Lab 3 - Implementing Existing Security Controls in Kubernetes

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@brentley - Please review this PR from our team,  As discussed earlier we included step by step labs in it.

@nagi9 and @calsoftpranavd it looks like this PR needs to be rebased. I tried to do it myself, but it doesn't appear that you've granted permission to the upstream to allow commits on your branch. I see 300+ changed files, though... that seems unexpected. Can you check if that condition still exists after rebasing?

@nagi9 and @calsoftpranavd it looks like this PR needs to be rebased. I tried to do it myself, but it doesn't appear that you've granted permission to the upstream to allow commits on your branch. I see 300+ changed files, though... that seems unexpected. Can you check if that condition still exists after rebasing?

Hi @brentley - You should have the edit permissions now and that's correct it's over 300+ we added all 3 labs step by step as per our earlier discussion. please do let us know if anything missing.

Hi Brent,
Granted the edit permissions last week and should able to modify now,
please do let us know if any issues,
That's correct - we included all 3 labs per our conversation earlier, need
your help in getting the EKS workshop for the Calico Ent Registration page
online first,
Thanks,
Nagi Vumma
On Thu, Aug 27, 2020 at 2:20 PM Brent Langston<EMAIL_ADDRESS>wrote:

@nagi9 https://github.com/nagi9 and @calsoftpranavd
https://github.com/calsoftpranavd it looks like this PR needs to be
rebased. I tried to do it myself, but it doesn't appear that you've granted
permission to the upstream to allow commits on your branch. I see 300+
changed files, though... that seems unexpected. Can you check if that
condition still exists after rebasing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-samples/eks-workshop/pull/900#issuecomment-682197082,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBPV3OFWGUOEWCEEUBPUC3SC3EZXANCNFSM4QCYF4ZQ
.


chore: use walletconnect.org

Breaking Changes
N/A
Changes

feat:
fix:
chore: remove walletconnect.com from our rpc urls and replace with walletconnect.org

We should also remove the fallback logic in @walletconnect/core


How to distinguish global/user installations when uninstalling

Testing #52824
I want to uninstall the user-level installation, how can a user tell which is which?

We can probably change the name over there.

Verified on the label, but when I tried to uninstall, I got a warning message about running the uninstaller, which is from an untrusted publisher.
I was able to just click okay, but I'm not sure if that would be possible for someone without admin privileges on the system. This seems slightly off... you can install Code, but not uninstall.

Yeah it's possible for someone without admin priviledges to uninstall, you just have to click next. #2416


Configuration: Rename 60_misc to 60_defaults

This is follows changes in Duffy 3.0.0a11 which narrows the scope of
these configuration values.
Signed-off-by: Nils Philippsen<EMAIL_ADDRESS>

LGTM


Fix typo in README

I think since https://github.com/react-native-svg/react-native-svg/pull/1448 has been merged, it can be closed. Thanks for spotting a typo though :tada:


conf.py update

not needed due to https://github.com/opentelekomcloud-docs/cloud-container-instance/pull/16


add configurable port names for istio compatibility

Addresses https://github.com/tryretool/retool-helm/issues/144, alternate to https://github.com/tryretool/retool-helm/pull/151
helm template -f ~/retool-helm/charts/retool/values.yaml foo ~/retool-helm/charts/retool --set config.encryptionKey="foo" --set image.tag="5.6.11" --set codeExecutor.portName=http-bloop --set workflows.backend.portName=http-bar --set workflows.worker.portName=http-bleep --set workflows.worker.metricsPortName=http-bleep2 | rg "http-bloop|http-bar|http-bleep" -C 5

  ports:
  - protocol: TCP
    port: 80
    targetPort: 3004

    name: http-bloop
---
# Source: retool/templates/deployment_workflows.yaml
---
apiVersion: v1
kind: Service
--
  ports:
  - protocol: TCP
    port: 80
    targetPort: 3000

    name: http-bar
---
# Source: retool/templates/deployment_workflows_worker.yaml
---
apiVersion: v1
kind: Service
--
  ports:
  - protocol: TCP
    port: 3005
    targetPort: 3005

    name: http-bleep

  - protocol: TCP
    port: 9090
    targetPort: http-bleep2
    name: http-bleep2
---
# Source: retool/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
--
          - name: NODE_OPTIONS
            value: --max_old_space_size=1024
        ports:
        - containerPort: 3004

          name: http-bloop

          protocol: TCP
        livenessProbe:
          httpGet:
            path: /api/checkHealth
--
                name: foo-retool
                key: google-client-secret
        ports:
        - containerPort: 3000

          name: http-bar

          protocol: TCP
        livenessProbe:
          httpGet:
            path: /api/checkHealth
--
                name: foo-retool
                key: google-client-secret
        ports:
        - containerPort: 3005

          name: http-bleep

          protocol: TCP
        - containerPort: 9090
          name: http-bleep2
          protocol: TCP
        livenessProbe:
          httpGet:
            path: /api/checkHealth
            port: 3005

LGTM

you need to update values.yaml OR document these possible values
IMO there should be a default port name all the time, I believe that is a non-breaking change

LGTM, the defaulting comments are not necessary but I think you could collapse the conditionals down

LGTM, the defaulting comments are not necessary but I think you could collapse the conditionals down

The if/else is giving that default - but I ran into an issue using default with "template"... e.g. this wasn't working:
{{ .Values.codeExecutor.portName | default (template "retool.name" .) }}
neither this
{{ default  .Values.codeExecutor.portName (template "retool.name" .) }}
lmk if you have a different suggestion @alexlo03 ! thanks for review.

I ran into an issue using default with "template"...

oh I didn't notice this comment before, but that's because template doesn't return the value, it just prints it out to the output. you can just change template to include, which returns instead of printing, and then it will work as expected with the default pipeline.

I ran into an issue using default with "template"...

oh I didn't notice this comment before, but that's because template doesn't return the value, it just prints it out to the output. you can just change template to include, which returns instead of printing, and then it will work as expected with the default pipeline. usually include is preferred over template in helm for exactly this reason.

Ah thanks @ryanartecona - will address all of it w/your feedback today! 🙏

gentle ping. would like to see this in before we upgrade charts. thanks 🙏

Closing in favor of https://github.com/tryretool/retool-helm/pull/170


credits.html 関連を削除

背景

https://github.com/rails/rails/pull/32429 にて、credits.html を削除された
削除しても良い理由

There are a few reasons, for example, a guide is written, but then also maintained, to be fair everyone should be mentioned there as a contributor and that is difficult to manage. But most importantly, to me there is no difference between contributing to the guides, to the API, or to the code. Everything is the same to me, we do not have a page like this for people writing patches with code.
I believe that Rails Contributors is our place to give credit to all contributors to the Rails code base, and their personal pages there show their work. If someone wants to know who wrote a guide, or who wrote file uploading, or Active Model attributes, git log is the suitable tool for that.
cf. https://github.com/rails/rails/pull/32420#issuecomment-377948363

やったこと

credits.htmlがあるコードを削除

レビューありがとうございます!! マージしますね 🌱


fix: add auto-pull-requests-and-merge

Hope it works

I don't think it's necessary to add another PR by bot which needs our review. I suggest restore our origin protection rule.


[Chore] Refactor Compose resources

What happened 👀
Describe the big picture of your changes here to communicate to the team why we should accept this pull request.
Insight 📝
Describe in details how to test the changes, which solution you tried but did not go with, referenced documentation is welcome as well.
Proof Of Work 📹
Show us the implementation: screenshots, gif, etc.

seems like you guys did not make use of CompositionLocal in the previous implementations, right? @luongvo @hoangnguyen92dn

@sleepylee yup. we didn't apply CompositionLocal from our previous implementations. When I had the first look, it seemed to pass the data through composable components in-depth, and hard to manage the data then we decided not to go with this approach. It's time to apply the this with small piece of code with CompositionLocal on this project 😄

@lydiasama Could you please finalize your review on this PR and it's good to have your approval as well 😄

We will request for deeper reviews when contributing this back to our Android templates project. @hoangnguyen92dn I will merge this PR to have full code in develop branch for reference.


Debugger can't restart when paused in a separate file

It happened like this:
I was debugging a notebook cell, which called a module.
I Set a breakpoint on the module I imported (.py file).
Somewhere during the debug session I clicked "restart debugging".
Then I got:
"Couldn't find a debug adapter descriptor for debug type 'Python Kernel Debug Adapter' (extension might have failed to activate)"
And I'm no longer able to debug the notebook until I restart vscode:

Originally posted by @phgmacedo in https://github.com/microsoft/vscode-jupyter/issues/10596#issuecomment-1201927331

I think the problem here is we're re-starting the kernel without first shutting down the existing debugger.
Looking at the error message, this is from VS Code, leading me to believe debugger crashes unexpectedly (due to restart of the kernel), hence the error message from VS Code.
I.e. if we're already debugging, then we should shutdown the debugger, then restart the kernel.

https://github.com/microsoft/vscode-jupyter/issues/7670


Execution of the target buildfile failed

Bug Report / Support Request
Your Environment
Vagrant 1.9.5
Vbox 5.1.22r115126
ansible <IP_ADDRESS>

Your OS
Windows 10 Enterprise edition
Full console output
blt > local:sync:db:
'drush' cache was cleared.                                                                                [success]
Do you really want to drop all tables in the database drupal? (y/n): y
Error: no alias record could be found for source @cgi.test                                                                                [error]
[phingcall] /var/www/cgi/./vendor/acquia/blt/phing/tasks/local-sync.xml:54:8: /var/www/cgi/./vendor/acquia/blt/phing/tasks/local-sync.xml:57:29: Drush exited with code 1
BUILD FAILED/var/www/cgi/./vendor/acquia/blt/phing/tasks/local-sync.xml:20:22: Execution of the target buildfile failed. Aborting.
; 2 minutes  58.33 seconds
Summary
After I have built my vm on my system, I did a 'blt local:setup' to get the database installed. After a while of installation, i got the above error and the setup stopped. Do you know what could be the cause?

The actual error seems to be through Drush:
Error: no alias record could be found for source @cgi.test [error]

Do you have Drush aliases added to your site's codebase, inside drush/site-aliases/aliases.drushrc.php?
In most of my BLT sites, I have an alias like:
if (!isset($drush_major_version)) {
  $drush_version_components = explode('.', DRUSH_VERSION);
  $drush_major_version = $drush_version_components[0];
}
// Site CLIENTNAME, environment test
$aliases['CLIENTNAME.test'] = array(
  'root' => '/var/www/html/CLIENTNAME.test/docroot',
  'ac-site' => 'CLIENTNAME',
  'ac-env' => 'test',
  'ac-realm' => 'prod',
  'uri' => 'stage.CLIENTNAME.com',
  'remote-host' => 'staging-12345.prod.hosting.acquia.com',
  'remote-user' => 'CLIENTNAME.test',
  'path-aliases' => array(
    '%drush-script' => 'drush' . $drush_major_version,
    '%content-sync' => '/mnt/www/html/CLIENTNAME.stg/acquia-files/content'

  )
);

I tried that. It didn't fix it. The same error outputs. When I do a blt local:setup.  the error i get is
Unexpected error during import with operation create for search_api.index.content: Field field_domain_access is unknown.
Error while sending QUERY packet. PID=8771 Statement.php:59

From a couple of other threads I searched, I used the command drush @cgi.test status
and I got the below result:
vagrant@local:/var/www/cgi/docroot$ drush @cgi.test status
Warning: Identity file /home/vagrant/.vagrant.d/insecure_private_key not accessible: No such file or directory.
Permission denied (publickey,password).
Do you think that could be the reason?

@jestinijames - Usually that means the Drush alias file you're using is configured to only be used outside of Drupal VM. I know BLT in more recent versions changed the way it builds Drush aliases so they'll work correctly either inside or outside the VM:
https://github.com/acquia/blt/blob/8.x/scripts/drupal-vm/drupal-vm.aliases.drushrc.php
I think everything else seems to be working on Drupal VM's side. It sounds like the rest of the issues you're encountering may be coming from your project's BLT integration. Can you follow-up in that issue queue with any further questions? See: https://github.com/acquia/blt/issues


Unable to extract fractions

Environment

Tesseract Version: 4.00 LSTM and also tried with TrsseractOnly option
Commit Number:
Platform: Windows 10 64 Bit

Current Behavior:
Unable to extract fractions from TextOnImage. The result I get is either Yi or 1A for the fractions.
Sample Images

Expected Behavior:
Fractions must be extracted as 1/4, 5/8, 3/4
Suggested Fix:

Someone has already reported about this issue. Can't find the issue right now.

You can finetune the traineddata to recognize fractions.
Please see https://github.com/Shreeshrii/tess4training#additional-training-scripts---replace-top-layer-bash
You can test withe the test traineddata from the tutorial -
https://github.com/Shreeshrii/tess4tutorial/raw/master/eng_layer_eng/eng_layer.traineddata

You will need to resize images to at least 36x36px at 300 dpi for best results.
 *****  ./onefourth-1.png LANG eng_layer TESSDATA tessdata_best OEM 1 PSM 6 ****
¼

real    0m0.320s
user    0m0.364s
sys     0m0.008s

 *****  ./onefourth-2.png LANG eng_layer TESSDATA tessdata_best OEM 1 PSM 6 ****
¼

real    0m0.452s
user    0m0.448s
sys     0m0.020s

 *****  ./onefourth-3.png LANG eng_layer TESSDATA tessdata_best OEM 1 PSM 6 ****
¼

real    0m0.227s
user    0m0.208s
sys     0m0.012s

 *****  ./threefourth.png LANG eng_layer TESSDATA tessdata_best OEM 1 PSM 6 ****
¾

real    0m0.393s
user    0m0.456s
sys     0m0.004s

This is an issue with the trained model.
See https://github.com/tesseract-ocr/langdata/issues/69.


Fix a typo in Code Structure doc

name: "\U0001F4DD Documentation Fix"
about: Fixing a problem in an existing docs page
Checklist

[ ] Is there an existing issue for this PR?

link issue here

[x] Have the files been linted and formatted?

What docs page needs to be fixed?

Section: Redux FAQ
Page: Code Structure

What is the problem?
It's saying the opposite.
What changes does this PR make to fix the problem?

Thanks!


Recommendation source: track.getSimilar()

In fact, this function is included in LastFm API (track.getSimilar).
So, the first recommendation contractions algorithm will be:

Choose top N mostly listened tracks for some period of time
Apply track.getSimilar to each
Push results to ./recommendations.m3u

How can we know, was the similar track in users scrobbling history already? (Beyond the analysed period of time)
Should results be determined or randomised on the same input?

Interesting fact:
Not all the tracks in LastFm DB have non-empty output given by track.getSimilar.
In other words, this algorithm can give empty list in some cases. And it's hard to give any guarantee about the list size.


[Feature] add some new json function

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
json_contains : https://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html#function_json-contains
json_extract : support return array, like : https://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html#function_json-extract
json_unqoute : https://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html#function_json-unquote
json_valid : https://dev.mysql.com/doc/refman/5.7/en/json-attribute-functions.html#function_json-valid
-> operator : https://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html#operator_json-column-path
Use case
No response
Related issues
No response
Are you willing to submit PR?

[x] Yes I am willing to submit a PR!

Code of Conduct

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

@Yukang-Lian
can you add these functions issues:
json_contains
json_extract : support return array
json_unqoute
-> operator
to #17176 for firset good issue

@Yukang-Lian can you add these functions issues: json_contains json_extract : support return array json_unqoute -> operator
to #17176 for firset good issue

Yeah!

@Yukang-Lian can you add these functions issues: json_contains json_extract : support return array json_unqoute -> operator
to #17176 for firset good issue

Yeah!

thanks bro

Hi, can I get one of these tasks? Maybe the first:json_contains，I need to learn something  to resolve this for some time，thanks for your help~~


DATDOG -> DATADOG

@calellowitz fixes small typo

not to be confused

there's no reason to wait on builds for vault changes is there?

nope, travis doesn't test the syntax of the ansible vars files. mmm now i'm ready for lunch


[MM-24695] Small code refactor + Only groups you are apart of get highlighted yellow

NOTE TO SELF: Update redux hash once ready to merge!
Summary

This ticket addressed the issue of all groups getting highlighted for all users regardless.
Ticket Link

https://mattermost.atlassian.net/browse/MM-24695
Related Pull Requests
Waiting on
https://github.com/mattermost/mattermost-redux/pull/1152
Screenshots

/update-branch

/update-branch


Add ConnectionSettings

Connection-related settings are pulled out from ServiceApiSettings
into their own class.
The builders for these classes also handle defaults.
Consequently ApiUtils, which provided methods for "merging" settings,
is no longer needed and deleted.

LGTM. @anthmgoogle

LGTM.


Add basic support for submessages/widgets

These steps add tracking of the sub-message data correctly and showing a placeholder that the widgets are not yet supported.
Implements the basics of #3205

Thanks @borisyankov ! This looks good. Several small points:

Let's put the jsdoc directly above what it documents, with no blank line. Helps prevent getting separated later.
The detailed jsdoc on the SubMessage type is super helpful -- thanks! :smile:
In this in a commit message:

Currently the only opperation is addition, we do not update or delete submessages.
I'm not sure if the "we" is just the mobile app, so far, or is Zulip as a whole. Good to be explicit.

This test should be redundant according to the type:
message.submessages && message.submessages.length > 0
Oh hmm but I guess message could be an Outbox and not Message. ... Maybe add submessages: Array<empty> to Outbox? That's the type of arrays whose elements belong to the type with no values... in other words, the type consisting only of the empty array, because there are no possible values to be its elements. And add a submessages: [] to where we make outbox objects.
I'd squash the widget CSS commit into the widget rendering, since the idea is that the plain text doesn't look right.

This test should be redundant according to the type:
message.submessages && message.submessages.length > 0

This is not only for Outbox but also to support older versions of the back-end which do not have the submessages property.

Thanks! Changes all look good.

This test should be redundant according to the type:
message.submessages && message.submessages.length > 0

This is not only for Outbox but also to support older versions of the back-end which do not have the submessages property.

Hmm, I see.
This is similar to the situation I just made a comment on in #2934 , then. I'd like this sort of variability to be explicit in the types; basically if it's real enough that we need code to handle it, then it's real enough to put in the types. The key factor in how much value the types give us is how much we can believe them, so wherever we see a reason not to believe them we should fix that.
An industrial-strength version of this principle would mean we should be systematically validating the API responses against the types we expect. That'd be pretty useful too, but probably also a lot of work to get going; for now I'm happy with assuming the server is some reasonably upstream-like version of Zulip.
Here, a ?: type in the API, with a line of jsdoc saying what Zulip server version introduced it, should be good enough.

I did revisit the PR. Each commit had suffered a bit from significant merge conflicts from the several refactors (types, reducers, moving of content from a file to file).
Also, to explicitly acknowledge that I agree with the conclusions of the discussion we had, and I also agree that these bigger changes can wait.
I have implemented the changes in the 'easier solution':

documented the submessage value
made it optional and made the code deal with non-existent value for it

I consider it ready for merging.

Ping. This is ready for review & merge.

Thanks @borisyankov !
Made some changes, and now merging.

Although the server database model is SubMessage, everything else in the server and docs, and everything in the API, seem to have it as one word, "submessage". This branch mostly went for two words "sub message", as in ...SubMessage and ...SUB_MESSAGE; I've changed it to "submessage" to match the API.

Like in #3263 and in particular 2c206a919, I'd like us to document server event types explicitly, in the new eventTypes.js; and then use those as near-verbatim as possible in the Redux actions we make from them. I wrote this as a new commit.

In the comment on Message.submessages, added the crucial point about what it means when it's absent: it's equivalent to being empty.

Some small adjustments to the reducer code, explained in new commits making them.

The CSS had duplicate display: flex; lines; deleted one.

The CSS was added at the very end of our CSS, which isn't a logical place for it; other CSS code there is for the #scroll-bottom button, the error banners, and other things that live outside the messages themselves. This is CSS for a particular type of message, so I moved it to be next to the other CSS for messages.

I made a pass over the "sorry, unsupported" message, making it hopefully a bit more helpful.


WIP: Fix iterator

You should probably add:
    - os: osx
      osx_image: xcode10.1
      language: generic
      python: 3.6
      env:
        CXX: clang++
        CC: clang
    - os: osx
      osx_image: xcode10.1
      language: generic
      python: 2.7
      env:
        CXX: g++
        CC: gcc

to your Travis file to test against Mac

Replaced by https://github.com/BlueBrain/MorphIO/pull/112


python311Packages.python-otbr-api: 1.1.0 -> 1.2.0

Diff: https://github.com/home-assistant-libs/python-otbr-api/compare/refs/tags/1.1.0...1.2.0
Changelog: https://github.com/home-assistant-libs/python-otbr-api/releases/tag/1.2.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 234256 run on x86_64-linux 1

7 packages built:

home-assistant-component-tests.homekit_controller
home-assistant-component-tests.otbr
home-assistant-component-tests.thread
python310Packages.python-otbr-api
python310Packages.python-otbr-api.dist
python311Packages.python-otbr-api
python311Packages.python-otbr-api.dist


[vcpkg baseline][fastrtps/foonathan-memory] Modify ci.baseline.txt

Fixed CI pipeline issue:
PASSING, REMOVE FROM FAIL LIST: foonathan-memory:arm-neon-android
PASSING, REMOVE FROM FAIL LIST: foonathan-memory:x64-android
PASSING, REMOVE FROM FAIL LIST: foonathan-memory:arm64-android

Above records were added into the ci.baseline.txt by PR https://github.com/microsoft/vcpkg/pull/29406, them were fixed in PR https://github.com/microsoft/vcpkg/pull/31905, so remove the records from ci.baseline.txt.
fastrtps:arm-neon-android
fastrtps:x64-android
fastrtps:arm64-android

install failed with below error, adding them into the ci.baseline.txt.
Cannot find package android-ifaddrs

[x] Changes comply with the maintainer guide
[ ] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[ ] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[ ] Only one version is added to each modified port's versions file.

END OF PORT UPDATE CHECKLIST (delete this line) -->

There's a newer version of fastrtps (2.10.1).
Maybe we could try updating and see if that fixes the problem.

There's a newer version of fastrtps (2.10.1).
Maybe we could try updating and see if that fixes the problem.

Okay, I will take care of this matter today.

After updated fastrtps to 2.10.1, it still failed with error:
Cannot find package android-ifaddrs

Waiting for https://github.com/microsoft/vcpkg/pull/32049.

/azp run

Related chipmunk PR https://github.com/microsoft/vcpkg/pull/32441

Duplicate of https://github.com/microsoft/vcpkg/pull/32484


Storage: Added Java ReadMe

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

@kpajdzik ready for merge

Automation for azure-sdk-for-java


Readme is incorrect as latest changes have not been released on NuGet yet

The 1.0.0 version released on NuGet does not include builder.Services.TryAddAWSService<IAmazonSimpleSystemsManagement>();  but the readme.md was recently modified to remove that line from the usage instructions.
I would suggest either cutting a new NuGet release or re-adding the line to the readme until 1.0.1 is released.

I think you misunderstood.
What I am trying to say is that the 1.0.0 package released on NuGet does not contain the TryAddAWSService line. That line must have been added after the 1.0 version was released.
I followed the instructions and got an error that IAmazonSimpleSystemsManagement is not registered in the DI Container.
Here is the decompiled source for the nuget package:

Please note that the TryAddAWSService is not there.
So I am suggesting either cutting a new 1.0.1 release with the updated source code, or adding the line back to the readme.


fix the MASExampleAttributeChainingView example

In the MASExampleAttributeChainingView, use the lessThanOrEqualTo other than greaterThanOrEqualTo.

Not really sure what this resolves? The code is commented out? Should probably be equalTo instead based on the commentary.


[SPARK-18286][ML][WIP] Add Scala/Java/Python examples for MinHash and RandomProjection

What changes were proposed in this pull request?
Add Scala/Java/Python examples for MinHash and RandomProjection
How was this patch tested?
./bin/run-example ml.MinHashExample
./bin/run-example ml.JavaMinHashExample
./bin/run-example ml.RandomProjectionExample
./bin/run-example ml.JavaRandomProjectionExample

Can one of the admins verify this patch?

Jenkins add to whitelist

ok to test

@jkbradley @MLnick @srowen Could you help to add @bravo-zhang to whitelist? Thanks.

Jenkins add to whitelist

Looking good, excepting that there are no python examples?

@srowen The Python API is still under review at #15768. Would you mind to take a look? Thanks.

Test build #68271 has started for PR 15787 at commit 8a086a0.

Test build #68271 has finished for PR 15787 at commit 8a086a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class JavaMinHashExample
public class JavaRandomProjectionExample

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68271/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68282 has started for PR 15787 at commit 78593e5.

Test build #68282 has finished for PR 15787 at commit 78593e5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68282/
Test PASSed.

Merged build finished. Test PASSed.

Linking [https://issues.apache.org/jira/browse/SPARK-18392] since it will alter the public API for LSH

This PR can be closed since https://github.com/apache/spark/pull/15795 has merged

Ah, thank you @bravo-zhang !


Microwin issue on install

Im getting this windows over and over.
Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist.
Windows 10 22H2

Very strange which language is your ISO? I'm loading Win10 22H2 without any issues whatsoever.

Very strange which language is your ISO? I'm loading Win10 22H2 without any issues whatsoever.

Hey man, quick questions:

Did you load that ISO to make a debloated ISO with all the tweaks in MicroWin or just a normal ISO?
If it is a debloated one, how many tweaks did you apply? Any issues after booting? I can't seem to open any disk C: D: after booting a fresh W11 ISO debloated using MicroWin and Ventoy, language is EN US

Very strange which language is your ISO? I'm loading Win10 22H2 without any issues whatsoever.

Hi, I tried spanish, english, always the same error.

Same error, win10 22h2

Same error, win10 22h2

I got this also with win10 22h2 en international , after clicking ok I get this


Use Python_Spcial_Auth without any Framework

Is it possible to use python_social_auth package without using any framework?

@Gocht Did you get anywhere with this?

Currently there's no implemented way, but with the recent split into smaller modules, it should be easier to accomplish this since the core component doesn't depend on any framework.


BossBarColour

*Description of issue:
If you want to change the color of the bossbar it doesn't work.

#####################################
PASTE RELEVANT CONFIG SECTION HERE
#####################################
  Mineur:
    fullname: Mineur
    shortname: Min
    description: Récoltez du minerais/blocs!
    ChatColour: BLUE
    BossBarColour: GRAY
    chat-display: full
    max-level: 500
---

**Server Type (Spigot/Paperspigot/etc):**  Paper

**Server Version (using `/ver`):**  Paper-164 (1.15.2)

Jobs Reborn 4.15.7

There is no bossbar color by GRAY
see https://hub.spigotmc.org/javadocs/spigot/org/bukkit/boss/BarColor.html


Add HSTS header support to IS Analytics server.

Describe the improvement
we have already identified this issue [1] related to the HSTS and we have provided a patch [2] to support HSTS headers in APIM analytics 2.6.0.
This fix has been provided to the "org.wso2.transport.http.netty_6.0.163.jar" and it has not been provided to the "org.wso2.transport.http.netty_6.0.289.jar" which is released with the IS-Analytics 5.8.0.
Therefore we need to do the same fix in the latest version as well.
[1] https://github.com/wso2/product-sp/issues/1056
[2] https://github.com/wso2-support/transport-http/commit/1e56925a4bef094a73736b886887d22235433e2f

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Question: Best way to estimate gas

I am wondering how to best estimate gas for when calling contract methods using Soltsice.

Evenry method in generated contracts was contract.methodName.estimateGas(), e.g. here

Thank you :-)


Add class S1IWWCSInput() and class S1IWWMSInput()

It might be premature to add it now considering no examples based on S1 GRD data are provided on readthedocs, but it still took me a little too long to figure out how to query S1 IW data.
I don't think it hurts to have it available already for testing purposes.

Thanks, @wouellette, appreciated. Keep the pull requests coming :)


[Suggestion] It would be better to remove the "+ Create new Resource Group…" option from the command list

OS: All
Build Version: 20220418.2
Regression: Not a regression
Repro Steps:

F1 -> Azure Static Web Apps: Open in GitHub.
Check whether there is no "+ Create new Resource Group…" option in the command list.

Actual:

There is a "+ Create new Resource Group…" option in the command list.

An error "No matching resources found" occurs after selecting the "+ Create new Resource Group…" option to create a new resource group.

Suggestion:
It would be better to remove the "+ Create new Resource Group…" option from the command list.
More Info:
This issue also reproduces when executing commands “Clone Repo...", "Edit Workflow...","Browse Site", "Add New Setting...", "Open GitHub Action Log", "Open in Portal", "Open Repo in GitHub" and "View Properties" from command palette.

Closed by https://github.com/microsoft/vscode-azureresourcegroups/pull/200

This issue also reproduces when executing commands “Clone Repo...", "Edit Workflow...","Browse Site", "Add New Setting...", "Open GitHub Action Log", "Open in Portal", "Open Repo in GitHub" and "View Properties" from command palette.

Fixed by #682


Fix TypeScript issue with Record has method.

The old version was causing type errors with my TypeScript configuration due to key being string / number / Symbol.
The issue:

This is closer to the get function definition below it:

has<K extends keyof TProps>(key: K): boolean;

After the fix:

Hello
I believe the suggested change could break some existing code. Consider the following code (compiled with --keyofStringsOnly):
interface Record_<TProps extends object> {
  has(key: string): key is keyof TProps
}

type Shape = { a: number, b: boolean, [Symbol.iterator]: any }

function defaultKey(a: Record_<Shape>, key: string) {
  let z: "a" | "b"
  if (a.has(key)) {
    z = key
  } else {
    z = "a"
  }
  return z
}

The z = key assignment is allowed, since inside of the if block, the type of key is constrained to be extending keyof TProps. Your change removes this constraint.
I think a better solution is to change:
has(key: string): key is keyof TProps

to
has(key: string): key is ((keyof TProps) & string)

Looks like "duplicate" on PR #1539 and as mentioned above - breaks current code and intention of the method.
Suggested fix is https://github.com/facebook/immutable-js/pull/1539/files#r195696659


Update Accumulate to use namespaces

Split test classes to their own files
@arueckauer - Thoughts on these changes?

@petemcfarlane We've made a couple of PRs here updating to using src and test directories as well as naming the files in a way that matches PHP PSR-4 standards. However, I didn't know or notice there's a makefile that specifies the names of the example and test file. I'm not sure how or if we should proceed with these. The Accumulate (this one) and Acronym PRs have been updated this way, but they won't work with the existing makefile and I'm not sure of a great way forward short of updating everything all at once. Any thoughts or ideas here?

If I may add some additional information for clarification:
The goal of this PR is to provide a POC for #283. Other exercises would need an update as well. Preferably in one PR.
@petemcfarlane The primary question we have, is, what your thoughts are on this and whether you can support this effort? Or have doubts/concerns?
This PR currently fails test (Travis-CI was somehow not triggered). The issue is that the changed directory structure is not compatible with the Makefile configuration. We have two thoughts:

Update Makefile (together with the changes for all exercises) to use the new directory structure.
Introduce an example directory, which gets copied to src to run automated testing. This would be required, if multiple example solution files are required by an exercise.

If there's a way to do all this work where it doesn't require it to be in on PR, that would be preferred.  One PR doing all this would be massive and impossible to accurately review.

Once we agree on a structure, it should be pretty straight forward. But again, I have not completed all exercises yet and don't know for sure if there is an exercise that raises the complexity in changing to namespaces.
It might be best to develop against a separate branch and then merge back to master as soon as everything is fine.

Closing this. I think much of what this was trying to accomplish has been handled elsewhere and more recently.


amazon-init: include the general system's software and wrappers in PATH

It is surprising that software which was installed by the user at AMI generation time isn't available to a script run over user data by default.
When authoring user data to execute at startup, users will now have more predictable access to baked-in software instead of an extremely bare-minimum set currently there.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable: (deployed as an AMI)

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thank you!


Add import from gsheet for users

This PR addresses #2 , to support the importing of a user's questionnaire responses into their profile.
They have control over this, and it appends info to avoid losing existing profile information - with the idea being that we don't want to lose any information someone has already added to their profile.
This doesn't include any attempt yet to fit this into the existing designs on figma - that's addressed with #4

hi @EvanHahn thanks for the code review - I appreciate you catching a few things :D.
I'll merge this in tonight, as I'm almost done with the importer for the existing Airtable directory meaning we'd


Capitalization with empty keys

This pull request addresses issue #1606. We now also have some tests for the social badge template!

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @PyvesB!

  Generated by :no_entry_sign: dangerJS

Thanks for this PR, you've been making a ton of progress through all the errors recently!
Unfortunately i don't think this will fix #1606
for undefined it will still throw Uncaught TypeError: Cannot read property 'charAt' of undefined
for numbers it will throw Uncaught TypeError: s.charAt is not a function
something like this should work:
-function capitalize(s) {
+function capitalize(s = '') {
+	s = '' + s;
	return s.charAt(0).toUpperCase() + s.slice(1);
}

Output:
capitalize(undefined); // ""
capitalize(2); // "2"
capitalize(false); // "False"
capitalize('test'); // "Test"

Yes, the input s can be empty (which was causing the crash), but cannot itself be undefined due to a string coercion step before the call to capitalize:
  // String coercion.
  text = text.map(value => '' + value);


First swath at /api/v1/package/***.

Will this resolve #254 ? If so, can you write as much in the description?

Yes! I think.


Heroes Unlimited 2E, css padding adjustments

Submission Checklist
Required

[ ] The pull request title clearly contains the name of the sheet I am editing.
[ ] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[ ] The pull request makes changes to files in only one sub-folder.
[ ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
Removed the extra padding around the sheet to keep there from being a white border around the sheet in dark mode.
Fixed a couple css names to bring back some missing internal left padding in the sheet.

Character Sheet Info Roll20 Internal Use only.


[Feature card] v2 Epic

Epic to track Feature card v2 updates
### Design
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/9922
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/10137
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/10260
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/9009
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/10299
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom-website/issues/1556

### Dev
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/10306
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/10072
- [ ] https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/10073
- [ ] QA

closing epic in favor of new organization strategy


Gamification: Implement a point system for user engagement and motivation in fitness activities.

As a user, I want to have fun and earn points when I perform a certain exercise.

The implementation for this task is successfully achieved ✅


Make SPI safe

Also expose underlying I/O errors instead of returning -1.

Good call on the errno thing.


Remove reflection-based JSON serialization from SwaggerUIMiddleware

Fixes #2550

Can I ask a question, I saw the bug and I reviewed the PR, I know this is not my business, but I just want to wonder, if possible, why this PR is not merged yet.
I faced this problem in my Application, that led me to here.
Thank you very much for your efforts.

Hi everyone. @VMelnalksnis, @bdukes can I ask whether you will have time soon to fix the issues with the workflow and merge this PR? It would be great if you would manage to do this because this will help a lot of people. Thanks!

I see that CI is failing because .NET 6 SDK is missing:

Looks like a fix for this was already provided in #2672, though I'm not sure what is the correct fix - changing the test target framework or installing the correct SDK. Either way, I can't merge PRs so someone else will have to review/merge/publish new version.

Thanks for contributing - if you'd like to continue with this pull request, please rebase against the default branch to pick up our new CI. We'd also appreciate tests for this scenario to prevent regressions.

Ok, I'll check out the current tests and see where I can add them.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.71%. Comparing base (0108842) to head (0bdd165).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2724      +/-   ##
==========================================
+ Coverage   91.69%   91.71%   +0.01%
==========================================
  Files          91       91
  Lines        3022     3029       +7
  Branches      519      519
==========================================
+ Hits         2771     2778       +7
  Misses        251      251

Flag
Coverage Δ

Linux
91.71% <100.00%> (+0.01%)
:arrow_up:

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Ok, I'll check out the current tests and see where I can add them.

I was looking at this myself yesterday and came up with this that builds on top of #2799: https://github.com/domaindrivendev/Swashbuckle.AspNetCore/pull/2800/commits/880fc5fa26f3a69cdf56843c4fa04c2b83b33357
If you'd like to cherry-pick those changes I'm happy to close my PR in favour of this one if it's making basically the same updates.

I see that the PR already adds net8.0 targets to tests, and I guess fixes all AOT/reflection based issues, not just in this one place. It would make sense to go with that PR, and I'm just happy to see the issue resolved.


ONNX version discrepancy with recommended python version

Describe the bug

I have python 3.11.8 on mac and I am getting an error in make build.
Setup and configuration
Current version:

python --version
Python 3.11.8

My config.toml and environment vars (be sure to redact API keys):

My model and agent (you can see these settings in the UI):

Model: OpenAI
Agent:

Commands I ran to install and run OpenDevin:
make build

Steps to Reproduce:
1.make build
2.
3.
Logs, error messages, and screenshots:
Preparing Installation of "zipp==3.18.1; python_version >= '3.8' --hash=sha256:206f5a15f2af3dbaee80769fb7dc6f249695e940acca08dfb2a4769fe61e538b
--hash=sha256:2884ed22e7d8961de1c9a05142eb69a247f120291bc0206a00a7642f09b5b715"
$ /Users/decodelab1/.local/share/virtualenvs/OpenDevin-Gtn4eF7s/bin/python /Users/decodelab1/miniconda3/envs/od/lib/python3.11/site-packages/pipenv/patched/pip/pip-runner.py install -i
https://pypi.org/simple --no-input --upgrade --no-deps -r /var/folders/6z/1g2wt2fs0zv2p18mty31b0h00000gn/T/pipenv-0r3d7hk0-requirements/pipenv-k90yjq8k-reqs.txt
Using source directory: '/Users/decodelab1/.local/share/virtualenvs/OpenDevin-Gtn4eF7s/src'
ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5
Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11
ERROR: Could not find a version that satisfies the requirement onnxruntime==1.17.1 (from versions: 1.15.0, 1.15.1, 1.16.0, 1.16.1, 1.16.2, 1.16.3)
ERROR: No matching distribution found for onnxruntime==1.17.1
[pipenv.exceptions.InstallError]: ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11
[pipenv.exceptions.InstallError]: ERROR: Could not find a version that satisfies the requirement onnxruntime==1.17.1 (from versions: 1.15.0, 1.15.1, 1.16.0, 1.16.1, 1.16.2, 1.16.3)
[pipenv.exceptions.InstallError]: ERROR: No matching distribution found for onnxruntime==1.17.1
ERROR: Couldn't install package: {}
Additional Context

can anyone reproduce this issue? @vafaei-ar you still face the issue?

Thanks, I tried again by updating the repo with the latest updates and the problem is resolved. One important thing to keep in mind might be one should let make to install python.


MudDataGrid: Respect indeterminate state in select-all checkboxes

Description
Resolves #6553
How Has This Been Tested?
Added a unit test to ensure that a state (including indeterminate state) of select-all checkboxes change correctly based on the number of selected items in the data grid.
Also conducted manual testing of the changes.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Added to v7.0.0 Migration Guide https://github.com/MudBlazor/MudBlazor/issues/8447
since this PR changed public api type from bool to bool?.

@Qwertyluk thanks.


BUG: Email structure

This PR changes the structure of the email (in terms of content-types). It should not affect the content (attachments, inline images etc.) but it should fix rendering issues with different email providers.
If only text

multipart/mixed

text/plain

If only HTML

multipart/mixed

multipart/alternative

text/html

If only attachment

multipart/mixed

application/octet-stream

If text and HTML

multipart/mixed

multipart/alternative

text/plain
text/html

If text and HTML and embedded image, and attachment

multipart/mixed

multipart/alternative

text/plain
multipart/related

text/html
image/jpg

application/octet-stream

See this SO answer. It seems multipart/mixed is the most unproblematic content-type as the top-level part.

Codecov Report

Merging #38 (e441086) into master (c410729) will decrease coverage by 0.33%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #38      +/-   ##
==========================================
- Coverage   99.48%   99.15%   -0.34%
==========================================
  Files          13       13
  Lines         584      592       +8
==========================================
+ Hits          581      587       +6
- Misses          3        5       +2

Impacted Files
Coverage Δ

redmail/email/attachment.py
100.00% <ø> (ø)

redmail/email/sender.py
98.22% <83.33%> (-1.15%)
:arrow_down:

Continue to review full report at Codecov.

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


Lucid: Python version?

Some of the notebook examples and  source code of lucid are targeting python2 not 3.
I installed lucid by running:
!pip install --quiet lucid==0.3
For example: caricature.py  (adding ranges wont work directly in python3 as they are not lists )
feature_inversion(img, model, layer, n_steps, cossim_pow)
48       transform.jitter(8),
49       transform.random_scale([0.9, 0.95, 1.05, 1.1] + [1]*4),
---> 50       transform.random_rotate(range(-5, 5) + [0]*5),
51       transform.jitter(2),
52     ]
Can someone help me with what am i supposed to do?

Lucid should work with both python 2 and 3 so you can use whichever you are more comfortable with. In python 3, just turn the range into a list: list(range(-5,5)) and now the lists can be added together.

@ttumiel so i need to modify the source code then since caricature.py uses py2 type list

I can't find transform.random_rotate(range(-5, 5) + [0]*5) in the source - I see it only in the notebooks, in which case you could just edit the notebook interactively. Maybe previous versions of caricature.py contained it, in which case try using the latest version of lucid?

@ttumiel  got it. I had the v0.3 installed as mentioned in my original question. i was looking through its commit history and it had the line:
Update caricature code 346a2f8
so they have updated the code now, i am closing the tickets, i just had a older version


Implement building of x64 version and test changetext.dll on 64-bit versions of DF

Building is working. Now it needs testing.


Adopt open-telemetry to dotnet sdk

it is good to consider using open-telemetry in dotnet-sdk; open-telemetry for dot-net sdk - https://github.com/open-telemetry/opentelemetry-dotnet
Note: open-telemetry is new telemetry library which replaces open-census and open-tracing. open-census and open-tracing projects will be deprecated soon.

Tracked by https://github.com/dapr/dotnet-sdk/issues/300


Fix date comparisons during coupon activations

Fix the following error on Python 3.11:
Traceback (most recent call last):
  File ".venv/bin/lidl-plus", line 8, in <module>
    sys.exit(start())
             ^^^^^^^
  File "lidlplus/__main__.py", line 162, in start
    main()
  File "lidlplus/__main__.py", line 156, in main
    activate_coupons(args)
  File "lidlplus/__main__.py", line 138, in activate_coupons
    if datetime.fromisoformat(coupon["startValidityDate"]) > datetime.now():
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: can't compare offset-naive and offset-aware datetimes

Hi, this would not fix the issue because datetime.utcnow() returns a naive datetime (and the comparison would be off). fromisoformat() needs a timezone-aware date to compare against.

That's a good point I didn't consider... thank you! :smiley:


[TASK]: work on abstract

Description

Research Objectives
Based on the established objectives, work on the abstract of the project and provide references as well as keywords that will appear.
References

None yet until the research has been found

Focus Area

on the objectives that have been established

Challenges

None have been encountered so9 far

Checklist

[ ] Thorough Research
[x] Added References
[x] Focus Area
[x] Challenges

Closed with the following: link


Dispatch uninstall doesn't remove the docker-registry from helm

[ ] Bug
[ ] Feature
[x] Enhancement

Detailed Description

Using the dispatch uninstall command fails to remove the new internal docker registry from helm.
Context

Dispatch uninstall should remove all components installed by Dispatch
Possible Implementation

Complexity

[x] Low - Simple enhancement or bug fix, no architectural changes or refactoring
[ ] Medium - Change requires some thought, but is relatively isolated
[ ] High - Significant architectural change or large refactor

Impact

[x] Low - Annoyance, but does not impact business or functinality
[ ] Medium - Issue can be worked around, but is causing pain
[ ] High - Blocker

Your Environment

Dispatch CLI version (or git commit): v0.1.6
Dispatch Chart version (or image[s] tag):
Operating System and version: macOS
Kubernetes version (and distribution): v1.8.1
Etc (any other useful environmental information):

I will get this fixed

Might be good to add a test of 1. install, 2. uninstall, 3. verify no services are left running.

#284 addresses this


[Mega Post] All websites build with this script

Hey guys,
I want to make a little collection of al sites build with this script.
Just post the link to the website and I will add it

csgolagoon.com

csgojack.de //still setting up

csgo.tf2ease.xyz
Literally just started, working on a new design as we speak :smile:

loteriacs.com

csgo-rolling.com Bot still has some errors with depositing :)

@linkzy I whould be very happy if you made a tutorial on the winner animation Cool design!
http://steamcommunity.com/id/CSGO-Rolling/
Add me talk there! thanks

@linkzy
Yes a please do a tutorial for the winner animation

@Zouspants  and @GreYzZ
https://github.com/ztizzlegaming/CSGOWinBig/wiki/Winners-Animation-Tutorial
I hope this tutorial helps at least to get an idea on how to make it... add me on steam if you guys need any help.
http://steamcommunity.com/id/LinKzy/
=)

@LilFuzzFuzz
What happend to your site?

dont forget Csgofancy.com. I am still working on it so its not done but it will be up soon. @GreYzZ