Fix checksum mismatch for github.com/docker/distribution

On my machine, when trying to build kne I get the following output:
make install

CGO_ENABLED=0 go build -o kne -ldflags="-s -w" kne_cli/main.go
go: downloading github.com/open-traffic-generator/ixia-c-operator v0.1.89
go: downloading google.golang.org/genproto v0.0.0-20220322021311-435b647f9ef2
go: downloading sigs.k8s.io/controller-runtime v0.9.2
go: downloading github.com/containerd/containerd v1.5.13
go: downloading github.com/docker/distribution v2.8.0+incompatible
go: downloading golang.org/x/text v0.3.7
verifying<EMAIL_ADDRESS>checksum mismatch
        downloaded: h1:u9vuu6qqG7nN9a735Noed0ahoUm30iipVRlhgh72N0M=
        go.sum:     h1:l9EaZDICImO1ngI+uTifW+ZYvvz7fKISBAKpg+MbWbY=

SECURITY ERROR
This download does NOT match an earlier download recorded in go.sum.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.
make: *** [Makefile:34: build] Error 1

This PR fixes the checksum mismatch by running the following commands prior to committing the change:
rm go.sum
go clean -modcache
go mod tidy

My theory: docker did something naughty with their release of the<EMAIL_ADDRESS>release. This lead to the goproxy module cache and the checksum servers being out of sync, producing the above error.
The issue can be reproduced locally when exporting the GOPROXY the same way as the GitHub action does.
Hence both commands will result in different  outcomes
export GOPROXY="https://proxy.golang.org,direct"
rm go.sum
go clean -modcache
go mod tidy
grep github.com/docker/distribution go.sum

github.com/docker/distribution v2.8.0+incompatible h1:l9EaZDICImO1ngI+uTifW+ZYvvz7fKISBAKpg+MbWbY=
github.com/docker/distribution v2.8.0+incompatible/go.mod h1:J2gT2udsDAN96Uj4KfcMRqY0/ypR+oyYUYmja8H+y+w=

unset GOPROXY
rm go.sum
go clean -modcache
go mod tidy
grep github.com/docker/distribution go.sum

github.com/docker/distribution v2.8.0+incompatible h1:u9vuu6qqG7nN9a735Noed0ahoUm30iipVRlhgh72N0M=
github.com/docker/distribution v2.8.0+incompatible/go.mod h1:J2gT2udsDAN96Uj4KfcMRqY0/ypR+oyYUYmja8H+y+w=

According to https://github.com/distribution/distribution/issues/3590 the recommended fix is updating the dependency to v2.8.1. Hence I am bumping the dependency to v2.8.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
32 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.2%) to 53.746%

Files with Coverage Reduction
New Missed Lines
%

topo/node/ceos/ceos.go
32
79.3%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
1908

Relevant Lines:
3550

💛  - Coveralls


Simplify SQL HTML and CSS

Remove ineffective z-index. Using the Firefox developer tools reports:
z-index has no effect on this element as it's not a positional element.

Per MDN (https://developer.mozilla.org/en-US/docs/Web/CSS/word-break)
using "word-break: break-word;" is deprecated.
This allows removing the CSS and now-extraneous div elements.

I haven't checked the specific location yet. But, overflow-wrap: break-word works and a change has been accepted here https://github.com/django/django/commit/01c6caa3e68047dbbb3292bed4b11c101c97a918 – if there is a really long word in the SQL somewhere we might want to continue inserting line breaks?

Good call. I've moved the CSS to use overflow-wrap: anywhere which MDN recommends over the deprecated one.
Here is the result which in my testing looks identical to the previous result:


[FREEZE] PLNSRVCE-1307: add get crds, wach pipelineruns, to exporter rbac

Needed for https://github.com/openshift-pipelines/pipeline-service-exporter/pull/23 changes

destroy cluster flaked
/retest pipeline-service-test

Adding a FREEZE header to the PR. I'd prefer to make sure we can deliver the downstream images and the RHTAP-872 story before we merge anything else.
That's of course open to discussion if any one feels that is not the right move.

Looks like I accidentally closed this
Still needed for https://github.com/openshift-pipelines/pipeline-service-exporter/pull/23

also wondering if we can unfreeze this @Roming22 given 872 is in and we've scaled down the exporter in RHTAP until the exporter rework like this is completed?


Compile TWebSocketServer with CMake only when OpenSSL is found

When compiling the C++ library and OpenSSL isn't found, TWebSocketServer will fail as it includes OpenSSL headers.

@kainjow could you rebase on latest master and push one more time, to see how the builds are doing? Build errors seem at least partially unrelated, but its always nice to try one more time, just to be sure...

Reran, but looks like an issue with the Rust dependency clap?
   Compiling clap v2.34.0
    Building [=========================================>               ] 29/39
error[E0658]: use of unstable library feature 'matches_macro'
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.34.0/src/errors.rs:392:10
    |
392 |         !matches!(
    |          ^^^^^^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/65721

    Building [=========================================>               ] 29/39
   Compiling threadpool v1.8.1
    Building [==========================================>              ] 30/39
   Compiling regex v1.5.4
    Building [============================================>            ] 31/39
error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
    Building [============================================>            ] 31/39
error: could not compile `clap`.


Adding new state selectors

What are you changing in this pull request and why?
Adding the state:unmodified and state:old selectors
Checklist

[x] Review the Content style guide and About versioning so my content adheres to these guidelines.
[x] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

@matthewshaver https://github.com/dbt-labs/dbt-core/pull/7773 hasn't been reviewed/merged yet — let's hold off on merging this docs update until we know when it will be released


Placeholder value for Plebs Don't Pay

Old clients may not understand a missing value for this.

I can confirm, It breaks my client.

What client do you run?


Fix PowerVC reports

@Kuldip-Nanda and I found that some of the 'advanced_settings' key names didn't match the reports (both here and in the general "All Power" report in manageiq-providers-ibm_cloud).


Manually set parent of duplicate

Note: DefectDojo is now on Python3 and Django 2.2.1 Please submit your pull requests to the 'dev' branch as the 'legacy-python2.7' branch is only for bug fixes. Any new features submitted to the legacy branch will be ignored and closed.
Motivated by #1510
Findings that are manually marked as duplicate now provide a link to the original finding and will appear in the parent findings duplicate list. Duplicates are determined by title only. Information displayed on each finding is as follows:
id: title, product/engagement/test
The dropdown menu will only appear if the the duplicate box is selected and there are other findings that have a matching title.
Here is an example:

[x] Your code is flake8 compliant
[x] If this is a new feature and not a bug fix, you've included the proper documentation in the ReadTheDocs documentation folder. https://github.com/DefectDojo/Documentation/tree/master/docs or provide feature documentation in the PR.
[ ] Model changes must include the necessary migrations in the dojo/dd_migrations folder.
[ ] Add applicable tests to the unit tests.

@madchap Please check this out when convenient and provide feedback as necessary.

Do you think it is possible and better eventually to have an autocomplete box instead? If thousands of findings, scrolling would definitely be a pain.
I saw this one: https://djangopackages.org/packages/p/django-autocomplete-light/ but I clearly have no experience or anything. Would it scale? be practical?
Should there be some kind of cascading approach eventually, to scope down to a product or engagement, prior to having the list of findings to choose from?

The auto complete box would be cool. I worry about how complete it will get though. Im sure the motivation behind this enhancement was because central dedupe is very strict now. Thats the main reason I decided to only filter findings that had a matching title.
Maybe a filter system could be implemented to allow users to decided which portions of dedupe they would like to use?

Yea, that could be a good idea.
Your initial PR is not bad right. It could very well be a first iteration to get that feature out the door, until we get more feedback too. I'd already be happy with that :)

Maybe to make it a bit more selective, descriptions would have to match as well. That would include all the non problem areas of dedupe. Almost positive there would not be thousands of findings listed that way ;)

I am somewhat less sure about the description being a hard part of the filtering. To me, the chances the description gets an amend is higher, and would break the filtering. I would probably just then leave the title, which per your initial thought, is certainly enough.
By filter system, you mean making an option in the system settings to pick what makes up the filter right?

Just tried the patch onto my local deployment, seems to work well.

Glad to hear it! Think it would be best to call this a first iteration like you suggested and revisit later.

Glad to hear it! Think it would be best to call this a first iteration like you suggested and revisit later.

Sounds good to me. Do you want to keep the description in the filter though? Or remove it and keep only the title?
Also there seems to be a trailing slash showing up after the date for some reason.

Decided to keep only title.
The test the finding was associated was suppose to display, but the title is allowed to be Null. Decided to just scrap it. Something else can be added in its place in the next iteration.

Using it now in semi-prod, I think we would benefit from adding the "test name" in the dropdown box, I.e. I have several matches, and the only differentiator is the finding ID.

The test the finding was associated was supposed to display, but the title is allowed to be Null. Decided to just scrap it. Something else can be added in its place in the next iteration.

Ill see what I can come up with.

Working just peachy :+1:

Should there be an accompanying change to the PATCH method of api v2?

Sounds good.


Limit virtctl builds during development to native architecture

What this PR does / why we need it:
Let bazel only build virtctl for the local native architecture to allow faster development cycles with frequent branch changes, and to improve the reactiveness by invocing less separate bazel calls while developing on the same branch.
In https://github.com/kubevirt/kubevirt/pull/9832 we started building quite a bit more virtctl architectures. Therfore the change.
CI and release jobs are not impacted by this change and will continue building everything.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

@fossedihelm I would also be ok to switch mine to VIRTCTL_BUILD_ALL_ARCH which you have in your PR. I have no preference.


Add missing javadoc

This PR adds Javadoc/KDoc documentation on public classes, data classes, functions and enums to make it easier to use from IDEs.
Fixes #2016
Specifically:

[x] JavalinConfig + all classes in the io.javalin.config package
[x] Bundled plugin configs
[x] EventManager
[x] RequestLogger#handle, Handler#handle, ExceptionHandler#handle
[x] FileRenderer#render
[x] Cookie
[x] ContentType  and HandlerType enums (among others)

[!NOTE]
Most documentation text was copy-pasted from the MDN Docs pages, and the Javalin documentation pages.

I followed your suggestion @dzikoysk , and also added missing documentation on the HttpStatus enum 👍

This looks really good @xgouchet ! Are you ready for merge?

Yes all good for me

LGTM, I think these docs will help our users. It's not only describing particular functions, but also brings a general context around them :)

Thank you very much @xgouchet !


How to create new GVFS repository?

Apparently this topic has been overlooked in public documentation and --help.
Documentation describes how to clone a regular git to a GVFS repo.
Documentation describes mounting and unmounting a GVFS repo, which seems to be an additional requirement beyond managing a normal git repo.
But, the documentation appears to be silent how to create a new GVFS repo.
Will "git init" create a GVFS repo if GVFS is already installed on the system?
Or, is something like "gvfs init" required despite no documentation?
Or, is this something that does not yet exist, and for now the only way to create a GVFS repo is to do the conversion using the clone command?
Thx.

There really isn't any notion of a "GVFS repo" as its own concept. GVFS is just a tool for working with an existing, large Git repo. The assumption is that you have an already-created Git repo on a GVFS-enabled server, and then you use gvfs clone to create a local virtual projection of it. Because of that, we haven't created a gvfs init command because there wouldn't be much use for one.
If you're wondering how to create the large repo in the first place, that all depends on what your starting conditions are. Do you have an existing, large codebase that you're migrating?  Do you have a single Git repo that is just starting to get too big to handle? We don't have any stock advice yet, but if you offer up some details, we'd be happy to help you think through the options.

Thx,
The idea is to start with something new that will grow.
So, this isn't a situation looking to solve a problem that already exists (a git repo so large it's bursting at the seams), but a forward-looking provisioning procedure... Small today but set up so that no future action should be required.

Makes sense. In your case, you would need to have one person use normal git to create and push the repo. Once it's up there, anyone can clone it with normal git clone or with gvfs clone.


Angular 14 support

Is support for Angular 14 on the roadmap for this project?

yes, it's on it's way - https://github.com/stevermeister/ngx-wig/pull/174

@mroskamp<EMAIL_ADDRESS>published!

Thank you!


Page crash on bad date-time inputs

Describe the bug
On the page where the mentor registers availabilities, if the end_time is before the start_time then there is a 400 error and the page goes blank.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://momentors.dev/profile'
put in a start time
put in an end time that is before the start time
hit submit

Expected behavior
There should be validations in place to check if the start and end times are acceptable. If they are not then there should be a clear indication in the UI that the dates are incorrect and the submit button should be disabled. We should not even be able to make the api call to get that 400 error.
Screenshots
A blank screen is the end result
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
I'm not sure if there is already a validation system/library/architecture in place but it might be worth figuring that out before fixing this bug. If that is too big of a scope then never mind, it should just be fixed however someone wants to.

Thank you again for the call out @adrmckinney, just wanted to keep you posted that we have this on the board and hope to get to it soon!

@adrmckinney @GitLukeW Thanks for keeping up with this issue. The backend validation issue has been fixed and we have a ticket for the front end validation here: https://github.com/orgs/TeamProductionSystem/projects/2/views/1?pane=issue&itemId=44507025


dotnet samples are ok, probably tried wrong nuget package

they don't build on new toolchains

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

ID: 6367067e-e9ce-6c2a-dd5d-a9de54735e78
Version Independent ID: 18564fed-2285-8cab-39a0-e3f1c2407c19
Content: Azure Cosmos DB: SQL API getting started tutorial
Content Source: articles/cosmos-db/sql-api-get-started.md
Service: cosmos-db
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

@atiq-cs Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@atiq-cs Thanks for the feedback, can you please elaborate more? which tools are you using? does the instructions in the doc didn't work for you?

@atiq-cs I just tested the sample on VA 2017 , Microsoft.Azure.DocumentDB version- <IP_ADDRESS> (this is the latest version of the Cosmos DB .Net nuget package) and the sample works fine, It created FamilyDB database and the specific collection.

Most probably I tried Microsoft.Azure.DocumentDB with .net core application at my first attempt to build and got some errors.

@atiq-cs Glad that you go it working, the sample linked in docs is based on "Microsoft.Azure.DocumentDB" .Net library, not the .Net core. Updating the package should fix as you described. We will now proceed with closing this issue.
#please-close


[RFE] MacOS: Start the guided flow as soon as user install crc package

As of now once user install the package , he/she needs to locate the CodeReady Containers from Application or from the finder. Some user might even think they have to run crc setup => crc start from the command line.
Need to check if this is possible with post install script.

Dup #2993


Removing -C link-dead-code (big change)

Add more logical lines! This simplifies some things
Add source analysis of async/await/groups and tuples
Try to identify any line that can be covered and add it to cover

There's some fundamental issues that stop this from working regarding how the rust compiler can reduce expressions that are essentially no-op i.e. loop { break; } that makes it infeasible to identify all coverable lines without reimplementing a lot of compiler internals


[Querier] Modify show tags support Native Tag without prefix

This PR is for:

Server

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Ericsssss:x: zhengyazhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Bug] Missing  momoka_ergo_default.hex

Describe the Bug
Tried to load in the .hex file for the new momoka_ergo and qmktoolbox cannot find the file.  Going on the qmkconfigurator allows me to grab a default / customized .hex file.
Additional Context?
No response

There's probably a lot of default keymaps that are missing or not current. We used to deploy them to the website through Travis CI, but Travis CI is no longer available to us, so these aren't getting deployed automatically anymore and we haven't yet worked out a way to do that.
For now, have this. Remove the .txt from the filename and flash it; it's freshly compiled.
momoka_ergo_default.hex.txt


Unify Typechecking of list and set/dict

Currently type checking  of lists do not use the protocol-like approach like set/dict, but lists provide slightly better error messaging. Instead list's typechecking is implemented manually.
To not have regression on error messages when unifying, #5 should be resolved first.

The wrapper approach taken by list is error-prone, we had several bugs because of that in the past. So if everything that's currently done with the wrapper can be done with protocols, then we should implement lists with protocols.


Add ConcourseCI example

I'll refactor it to work with Vault.

Closing this for now.
Will review in the future


The complete system

Hi，thank you so much for your open source work, it's simply amazing! I noticed the project status on the page: "We are currently working on the Noetic version of the complete system that can demonstrate the execution of the planner with a husky base and a panda armusing behavior trees. The complete system is planned to be available by the end of June 2022." . I'm really looking forward to seeing the complete  system and demo, thank you very much.

Hi，thank you so much for your open source work, it's simply amazing! I noticed the project status on the page: "We are currently working on the Noetic version of the complete system that can demonstrate the execution of the planner with a husky base and a panda armusing behavior trees. The complete system is planned to be available by the end of June 2022." . I'm really looking forward to seeing the complete system and demo, thank you very much.

Can you run the simulator successfully?


Track usage of connectors

For future knowledge of what connectors are worthy of maintenance

@david-sabata I believe you are already tracking this data. Can close.


Remove unused :storageitem and :vmitem quadicon settings

This removes Configuration > My Settings: "Show Datastore Item Quadrants" and "Show VM Item Quadrants"
These were no longer used because there's only the list view available for these items.
https://bugzilla.redhat.com/show_bug.cgi?id=1195407

looks good. Ready to merge.


Update template.xml.in

/usr/bin/qemu-system-x86_64 is the default path in Debian Bullseye

Also, template.xml.in was not changed as the other scripts have. Such template must be changed in order to support Ventura.

I confirm that Arch's path is the same.

Also, template.xml.in was not changed as the other scripts have. Such template must be changed in order to support Ventura.

Maybe this can help with the issues I keep getting like #14 #41 and #43

Thanks @notAperson535 for your support and @pedrohqb for your proposal of updating template.xml.in. Indeed I am encoutering Ventura support issue with it.

@therealrem Thank you for creating this and thank you @pedrohqb for confirming that it works.


wml indefinitely copies files from a yarn shared module

I want to use my shared package between several modules, among them also a React Native app.
I am using yarn workspaces and this is my folders structure
(the app/workspaces/mobile folder is created by:
npx react-native init mobile --template react-native-template-typescript):
app
|__package.json
|__lerna.json
|__workspaces
    |__core
    |    |__package.json
    |    |__tsconfig.json
    |    |__src
    |    |    |__main.tsx
    |    |__dist
    |         |__main.js
    |         |__main.d.ts
    |__mobile
         |__package.json
         |__tsconfig.json
         |__App.tsx
         |__babel.config.js
         |__metro.config.js
         |__ios
         |    |__ ...
         |__android
              |__ ...

app/package.json:
{
  "name": "myapp",
  "version": "1.0.0",
  "main": "index.js",
  "private": true,
  "workspaces": {
    "packages": [
      "workspaces/*"
    ],
    "nohoist": [
      "**/react-native",
      "**/react-native/**"
    ]
  },
  "devDependencies": {
    "lerna": "^3.20.2"
  },
  "scripts": {
    "build": "lerna run build",
    "reset-modules": "rm -rf node_modules/ yarn.lock workspaces/*/node_modules",
    "reset-yarn": "yarn cache clean",
    "reset-rn": "watchman watch-del-all; rm -fr $TMPDIR/react-*; rm -rf $TMPDIR/haste-map-react-native-packager-*",
    "reset-cache": "yarn reset-yarn && yarn reset-rn",
    "reset": "yarn reset-modules && yarn reset-cache"
  },
  "dependencies": {}
}

app/lerna.json
{
    "packages": ["workspaces/*"],
    "npmClient": "yarn",
    "useWorkspaces": true,
    "version": "independent"
}

app/workspaces/core/package.json
{
  "name": "myapp-core",
  "version": "1.0.0",
  "main": "dist/main.js",
  "typings": "dist/main.d.ts",
  "private": true,
  "devDependencies": {
    "typescript": "^3.8.2",
    "@types/node": "^12.0.0"
  },
  "scripts": {
    "build": "tsc",
    "build-watch": "tsc --watch"
  }
}

app/workspaces/mobile/package.json
{
  "name": "mobile",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint . --ext .js,.jsx,.ts,.tsx"
  },
  "dependencies": {
    "react": "16.9.0",
    "react-native": "0.61.5",
    "myapp-core": "*"
  },
  "devDependencies": {
    "@babel/core": "^7.6.2",
    "@babel/runtime": "^7.6.2",
    "@react-native-community/eslint-config": "^0.0.5",
    "@types/jest": "^24.0.24",
    "@types/react-native": "^0.60.25",
    "@types/react-test-renderer": "16.9.1",
    "@typescript-eslint/eslint-plugin": "^2.12.0",
    "@typescript-eslint/parser": "^2.12.0",
    "babel-jest": "^24.9.0",
    "eslint": "^6.5.1",
    "jest": "^24.9.0",
    "metro-react-native-babel-preset": "^0.56.0",
    "react-test-renderer": "16.9.0",
    "typescript": "^3.7.3"
  },
  "jest": {
    "preset": "react-native",
    "moduleFileExtensions": [
      "ts",
      "tsx",
      "js",
      "jsx",
      "json",
      "node"
    ]
  }
}

app/workspaces/mobile/babel.config.js:
module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
};

app/workspaces/mobile/metro.config.js:
module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
};

I added the following wml rule from the project root folder app:
wml add workspaces/core workspaces/mobile/node_modules/myapp-core

However, when I run wml start, the files from the core folder are copied infinitely many times inside the node modules of the mobile folder.
wml start
[watch] ~/app/workspaces/core
[watch-config] { ignore_dirs: [ 'node_modules' ] }
[subscribe] ~/app/workspaces/core
[copy] ~/app/workspaces/core/tsconfig.json -> ~/app/workspaces/mobile/node_modules/myapp-core/tsconfig.json
[copy] ~/app/workspaces/core/dist/main.d.ts -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.d.ts
[copy] ~/app/workspaces/core/dist/main.js.map -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js.map
[copy] ~/app/workspaces/core/src/main.tsx -> ~/app/workspaces/mobile/node_modules/myapp-core/src/main.tsx
[copy] ~/app/workspaces/core/package.json -> ~/app/workspaces/mobile/node_modules/myapp-core/package.json
[copy] ~/app/workspaces/core/dist/main.js -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js
[copy] ~/app/workspaces/core/tsconfig.json -> ~/app/workspaces/mobile/node_modules/myapp-core/tsconfig.json
[copy] ~/app/workspaces/core/dist/main.d.ts -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.d.ts
[copy] ~/app/workspaces/core/src/main.tsx -> ~/app/workspaces/mobile/node_modules/myapp-core/src/main.tsx
[copy] ~/app/workspaces/core/dist/main.js -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js
[copy] ~/app/workspaces/core/dist/main.js.map -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js.map
[copy] ~/app/workspaces/core/package.json -> ~/app/workspaces/mobile/node_modules/myapp-core/package.json
[copy] ~/app/workspaces/core/src/main.tsx -> ~/app/workspaces/mobile/node_modules/myapp-core/src/main.tsx
[copy] ~/app/workspaces/core/tsconfig.json -> ~/app/workspaces/mobile/node_modules/myapp-core/tsconfig.json
[copy] ~/app/workspaces/core/dist/main.js.map -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js.map
[copy] ~/app/workspaces/core/package.json -> ~/app/workspaces/mobile/node_modules/myapp-core/package.json
[copy] ~/app/workspaces/core/dist/main.d.ts -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.d.ts
[copy] ~/app/workspaces/core/dist/main.js -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js
[copy] ~/app/workspaces/core/tsconfig.json -> ~/app/workspaces/mobile/node_modules/myapp-core/tsconfig.json
[copy] ~/app/workspaces/core/package.json -> ~/app/workspaces/mobile/node_modules/myapp-core/package.json
[copy] ~/app/workspaces/core/dist/main.js.map -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js.map
[copy] ~/app/workspaces/core/dist/main.d.ts -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.d.ts
[copy] ~/app/workspaces/core/src/main.tsx -> ~/app/workspaces/mobile/node_modules/myapp-core/src/main.tsx
[copy] ~/app/workspaces/core/dist/main.js -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js
[copy] ~/app/workspaces/core/package.json -> ~/app/workspaces/mobile/node_modules/myapp-core/package.json
[copy] ~/app/workspaces/core/src/main.tsx -> ~/app/workspaces/mobile/node_modules/myapp-core/src/main.tsx
[copy] ~/app/workspaces/core/dist/main.d.ts -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.d.ts
[copy] ~/app/workspaces/core/dist/main.js -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js
[copy] ~/app/workspaces/core/tsconfig.json -> ~/app/workspaces/mobile/node_modules/myapp-core/tsconfig.json
[copy] ~/app/workspaces/core/dist/main.js.map -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js.map
[copy] ~/app/workspaces/core/package.json -> ~/app/workspaces/mobile/node_modules/myapp-core/package.json
[copy] ~/app/workspaces/core/dist/main.d.ts -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.d.ts
[copy] ~/app/workspaces/core/dist/main.js -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js
[copy] ~/app/workspaces/core/src/main.tsx -> ~/app/workspaces/mobile/node_modules/myapp-core/src/main.tsx
[copy] ~/app/workspaces/core/tsconfig.json -> ~/app/workspaces/mobile/node_modules/myapp-core/tsconfig.json
[copy] ~/app/workspaces/core/dist/main.js.map -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.js.map
[copy] ~/app/workspaces/core/dist/main.d.ts -> ~/app/workspaces/mobile/node_modules/myapp-core/dist/main.d.ts
[copy] ~/app/workspaces/core/package.json -> ~/app/workspaces/mobile/node_modules/myapp-core/package.json
[copy] ~/app/workspaces/core/src/main.tsx -> ~/app/workspaces/mobile/node_modules/myapp-core/src/main.tsx
[copy] ~/app/workspaces/core/tsconfig.json -> ~/app/workspaces/mobile/node_modules/myapp-core/tsconfig.json
...

I suppose that this issue is caused by the fact that files from the core modules are copied into the "same" folder which is symlinked by yarn in the mobile node_modules folder. How can I solve this? Should I have to remove the core module dependency inside the mobile package.json?
yarn --version: 1.22.0

Solved by removing a not-updated version of the node folder inside mobile:


rrule converter

Do you have any plans on this?
moment-recur to rrule and back

It will be good idea! +1

This project is generally open to PRs.  I don't believe such a thing is planned to my knowledge.

No plans for this, but if anyone wants to contribute, please issue a PR. Closing.


Slack for CFG

In case y'all are afraid to talk face-to-face https://hackgreenville.slack.com/messages/cfg/ and to get an invite to Hack Greenville in general https://hackgreenville.typeform.com/to/sBMjCF

I want in<EMAIL_ADDRESS>
In case y'all are afraid to talk face-to-face https://hackgreenville.slack.com/messages/cfg/ and to get an invite to Hack Greenville in general https://hackgreenville.typeform.com/to/sBMjCF
—
Reply to this email directly or view it on GitHub.

Head here for an invite https://hackgreenville.typeform.com/to/sBMjCF


MQTT Resource Creation

What's New?

API supports creation of resources via MQTT (and FarmBot JS)

current_bot.resources.save(my_tagged_resource)

The ID OF THE RESOURCE MUST BE 0 OR UNDEFINED, otherwise, the API will try to perform an update operation.
What's Next?

Going to try to merge log workers and resource workers into one dyno.

Coverage remained the same at 92.737% when pulling f66773d45ce493e7f032b30e3e0cdc7f2ba0d1d6 on RickCarlino:batch_resources into 83e1640ceae9b84ed8c6e87caa759a55804728ac on FarmBot:staging.


when all features are categorical, how to setup configuration

My data format is as followed:
0 0 2 3 1 31 312 0 51 2 10 2 340 514 0 2 132 4 2 203 1 49 29 46
0 0 2 3 1 31 312 0 51 2 10 2 505 1082 0 0 130 4 2 203 1 49 60 46
0 0 2 3 1 31 312 0 51 2 10 2 505 858 0 0 130 4 2 203 1 49 60 46
0 0 2 3 1 31 312 0 51 2 10 2 505 1028 0 0 132 4 2 203 1 49 60 46
0 0 2 3 0 122 362 6 51 2 10 2 505 138 0 0 427 4 2 27 1 49 29 2
0 0 2 3 1 401 88 14 51 2 10 2 505 858 0 0 45 4 2 324 1 58 4 9
0 0 2 3 1 110 212 14 51 2 10 2 505 824 0 0 819 4 2 154 1 42 29 2
0 0 2 3 0 431 180 14 51 2 10 2 505 747 0 0 669 4 2 125 2 42 29 23
1 0 2 3 1 31 312 0 51 2 10 2 505 585 0 2 133 4 2 203 1 49 29 46
0 0 2 5 1 221 267 11 51 2 10 1 505 205 1 0 607 4 2 280 2 38 131 23

The first column is label, and the remaining columns are categorical features. And I setup categorical_feature = 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23
When input of light_gbm data is these data, there appear error:
[LightGBM] [Fatel] Cannot recognising input data format, filename: data/train

what should data format be? Or maybe i setup configuration wrong.
Can u help me?

The feature  index is start from 0 , not 1

index starts from 0
categorical_feature = 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22

you mean a categorical feature encoding, and i have done as that feature index is start from 0.

he means categorical_feature = 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22

i have tried  categorical_feature = 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22, and it failed.

it still appear data format error

oh, the delimiter in your file should be tab(tsv) or comma(csv), not space

yeah, it's delimiter, now it's ok.
tks


User credentials cannot be modified

First of all I would like to thank you these docker configuration files. This has great added value to be able to set up and run a full ELK environment for developers in minutes 👏
I have successfully installed it in my local docker environment and it works great unless I make modifications in my .env file for the passwords.
Unfortunately the configuration files of the beats has the hardcoded password 'changeme' and therefore it cannot be modified.
Would be nice if you could fix it

Thanks @l4t3b0!  I've created a branch with those changes.  Would you mind pulling down that branch and testing a password change to make sure it works for you?

wow
I was not expecting an answer In so short time 😃
I just made a short test, but I can confirm, that it is working.
I can login to Kibana with modified elastic password and metricbeat keeps on sending the data
great job 👍
thanks


Allow annotations on shoot Services

How to categorize this issue?
/area control-plane
/kind enhancement
/priority normal
What would you like to be added:
As in https://github.com/gardener/gardener/pull/2380, I need the ability to add arbitrary annotations at a seed level to services that are created by shoots. Where the existing PR successfully adds annotations to services that are created for the control plane, shoots also need this facility.
Why is this needed:
When a shoot Service of type: LoadBalancer is created, the installed load balancer returns an address from default IPAM for the LB. This is insufficient when there are multiple address pools to choose from, for instance.
One way to solve this would be similar to #2380 in that a list of annotations is applied to all services of type: LoadBalancer that are created by a shoot. This is helpful, but too coarse. Different shoot Services will have different exposure requirements.
The most flexible solution is to interpret the list of annotations as regexes and allow the services in the shoot to match against them. In this manner, a Service may include an annotation such as metallb.universe.tf/address-pool: external5 and if the seed had a regex of metallb.universe.tf/address-pool: external.*, the requested annotation would be allowed and added to the Service proxy in the seed cluster as requested (metallb.universe.tf/address-pool: external5) when it is created.
The reason for doing this at the seed level and not the shoot level is to administratively constrain use of load balancer resources by seed.

There are two points I'd like to comment on:

Using annotations is vague and unstable since it's not really part of an official API contract. We're also about to replace the use-as-seed annotation by ManagedSeed (see here)
The requirement sounds quite specific because in your case you care about Services while on another operator may needs this for Ingress resources or even CRs. Thus, such a requirement may be implemented by a Gardener extension rather than by the Gardener core itself.

@timuthy  we should really create a sample gardener-extension with helpful comments to provide an easy starting point.
That extension would need to inject the annotations into the managed-resources in the Seed cluster. I do not think we have an existing example for this.

Hi guys, thanks for the feedback! I guess this is specific in that my immediate need is to expose a Service to the seed cluster load balancer and have it assign the correct address. Load balancers generally do this with annotations, but maybe I should be asking if there are other ways to do this? I don't want to solve a problem that has already been solved elsewhere.
What I know right now about exposing shoot services (and my Gardener experience is limited) is that L7 services can be exposed through nginx, but there's no good way to expose L3 services that require specific ports on addresses from specific address pools. That's the problem I'm trying to solve here. Without pool selection specific to the service being proxied, all shoot services must be exposed using the same pool, and if any of those services require public exposure, they must all accept public exposure in order to satisfy the needs of the one public service (since the LB cannot distinguish the requests to choose from the proper pool). Some services really shouldn't be exposed publicly, so there's a likely security problem if such a port was found in a port scan of public addresses.
I actually did think about whether other API objects could benefit from this facility (such as Ingress) and I think they could. I agree that annotations are vague and unstable, this is why I proposed regexes for matching so the local administrator could have control over what shoots were allowed to request and could change them as necessary. In a balance between usability, Gardener team workload and product flexibility, regex matching changes the solution from a very expensive and exhaustive undertaking that still may resort to plug-ins for every service that the team had time to retrofit to one where the local administrator can take initiative to whitelist expressions that are allowed with local jurisdiction. I don't understand what drawbacks there are to such a solution.
Anyway, assuming that this can be done as an extension, that's great! I am still unable to find the code where shoot service proxies are created though and I'd like to look at both the code and it's callers to understand expectations.  Thanks!

Hi guys, thanks for the feedback! I guess this is specific in that my immediate need is to expose a shoot Service to the seed cluster load balancer and have it assign the appropriate address. Load balancers generally do this with annotations. Maybe I should be asking if there are other ways to do this? I don't want to solve a problem that has already been solved elsewhere. I simply cannot find a means to solve the issue and the shoot clusters that I am porting in are dependent on this facility.
What I know right now about exposing shoot services (and my Gardener experience is limited) is that L7 services can be exposed through nginx, but there's no good way to expose L3 services that require specific ports on addresses from specific address pools. That's the problem I'm trying to solve here. Without pool selection specific to the service being proxied, all shoot services must be exposed using the same pool, and if any of those services require public exposure, they must all accept public exposure in order to satisfy the needs of the one public service (since the LB cannot distinguish the requests to choose from the proper pool). Some services really shouldn't be exposed publicly, so there's a likely security problem if such a port was found in a port scan of public addresses.
I actually did think about whether other API objects could benefit from this facility (such as Ingress) and I think they could. I agree that annotations are vague and unstable, this is why I proposed regexes for matching so the local administrator could have control over what shoots were allowed to request and could change them as necessary. In a balance between usability, Gardener team workload and product flexibility, regex matching changes the solution from a very expensive and exhaustive undertaking that still may require a retrofit of every provider extension to support it. Instead, this "hack" is actually an elegant way to give local administrators a secure means of allowing shoot owners to take advantage of local facilities in a manner they are already quite comfortable with, as well as stop them from using facilities that they are not authorized for.
Anyway, assuming that this can be done as an extension, that's great! I am still unable to find the code where shoot service proxies are created though and I'd like to look at both the code and it's callers to understand expectations.

These are valid points @briantopping, thanks for clarifying.
As you said:

Instead, this "hack" is actually an elegant way to give local administrators a secure means of allowing shoot owners to take advantage of local facilities in a manner they are already quite comfortable with, as well as stop them from using facilities that they are not authorized for.

This is a perfect use case for an extension e.g., a security extension which is either very specific to your use-case or more generic so that the Gardener community will profit from it as well.
As I still see this requirement as a functionality on top of Gardener for which we have adequate extension points, I'd refrain from implementing this as an in-tree feature of the core. My recommendation is to have a look at already available extensions like https://github.com/gardener/gardener-extension-shoot-cert-service or https://github.com/gardener/gardener-extension-shoot-dns-service. In addition, I have opened https://github.com/gardener/gardener/issues/3534 to follow @danielfoehrKn's suggestion - help is appreciated :).
Otherwise, can we close this issue as we agree to follow the extension approach?

Thank you @timuthy. After consultation with @danielfoehrKn and @stoyanr, we have discovered that the code in question is in the Kubevirt organization and that's why it could not be found. @stoyanr further explained that the method of proxying for a shoot Service is specific to the gardener-kubevirt provider, so it is unlikely that packaging this solution as an extension will have applicability outside of Kubevirt only. This means that the changes really are a PR for Kubevirt, not an extension at all.
Once this is working, I will be able to make a better illustration of the use case. Maybe at that point the discussion will be worth reconsidering, but will close this for now. Very grateful for all of your help, thank you!


Updating SpacePy data and adding SpacePy contact to members.

Updated SpacePy project info, including github URL, location of docs,
and corrected logo. Added Steve Morley to members including github
handle.

Awesome! thanks @drsteve!


Navigation chevrons positioned too low

The existing code vertically positions the left/right navigation chevrons by setting padding-top:

this.lightbox_container.find('a').css('padding-top', function() {
    return $(this).parent().height() / 2;
});

But this positions the chevron too low - the correct padding-top would be half the height of the parent minus half the line-height of the chevron.
Rather than using padding-top I think a better method would be to set the line-height to be the same as the parent height:

this.lightbox_container.find('a').css('line-height', function() {
	return $(this).parent().height() + 'px';
});

Hello. Have you seen #59? Does you solution position the chevrons correctly on portable devices, such as smartphones and tablets? Thanks for an alternate solution to the same problem!

For me, line-height doesn't work at all. Please submit a PR with fully working code

For some reason you're setting padding-top in the CSS as well an in the JS.
Remove "padding-top: 45%" from ".ekko-lightbox-nav-overlay a" in the CSS and setting line-height works fine.
I couldn't get #59 to work for me, but I agree that a pure CSS solution is preferable.

Grab the latest from master - it uses line-height. The examples page won't get updated until a new release goes out with the change. Looks good on chrome, firefox, safari, and chrome android, but needs testing in IE.

This is in master now


make gridSourceProvider protected

So we can over-ride getter/setter gridSourceProvider methods as needed in regional subclasses of FaultSystemSolution.

This is going to get messy with the modular branch as the gridSourceProvider object no longer exists and the old FaultSystemRupSet has been renamed. Can you instead just call setGridSourceProvider in your subclass constructor to avoid the U3-specific logic in InversionFaultSystemSolution for now?

Hi Kevin, I considered that approach but because we need the gridSP for
subduction models to be null (at least for now). So it won't work because
later when getGridSourceProvider is called the current U3 logic will kick
in and set up the U3 provider. I had thought that this would be
straightforward, but if not we can look for another alternative. Just leave
it for now, we've made that change in our fork and it's working OK and we
can discuss it next week if needed.
On Fri, Jul 9, 2021 at 6:28 AM Kevin Milner @.***>
wrote:

This is going to get messy with the modular branch as the
gridSourceProvider object no longer exists and the old FaultSystemRupSet
has been renamed. Can you instead just call setGridSourceProvider in your
subclass constructor to avoid the U3-specific logic in
InversionFaultSystemSolution for now?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opensha/opensha/pull/34#issuecomment-876653080, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7BNFXEGPH6IC6OHWUPXBLTWXU5RANCNFSM475NS7CQ
.

Closing this as it's not compatible with the new to-be-merged-in modular approach


[Feature Request] Import layout from keyboard-layout-editor.com

I just came across the video showcasing pog and it seems amazing, but I didn't see anything regarding importing layout from this website.
Because you can create the layout and then export it to JSON.
Then this JSON can be imported in kb.xyz.is to generate a premade KiCAD project.
So being able to link everything from start to finish with the same json layout could be amazing and make the creation of custom keyboard pretty seamless with multiple tooling automating lots of things along the way

The keyboard layout editor has an import feature from then qmk json and the kle json. What you mean is to import the pins as well right? Some parts eg the col and row definitions of rhe pins in qmk cant be easily converted to the kmk syntax. But I like the idea

Well the KiCAD project isn't perfect and still needs work, you have to do the traces manually, but yeah since the other website after kle makes the circuit you could parse/detect rows and columns to some extent automatically.
But if you know there are X columns and Y rows you could pre-fill that and just have to associate them in UI to your µconstroller pins.
(maybe have some local DB of popular boards ?)
Not 100% seamless and perfect but still adding accessiblity/automation to the process of making custom keyboards


Can anyone update this to 4.21+?

I updated the target/build files for 4.21+, everything builds and works in the editor. I setup the package profile settings and when cooking it gives warning:
"CookResults: Warning: Unable to generate long package name" for the mod files.
After building both profiles and copying files into correct location, running the game results in a crash, which is fixed by changing loading phase in plugin to "PreEarlyLoadingScreen" instead of "Default". Then the pak files are mounted and AssetRegistry.bin is located, but unable to find MOD_SKELETON file. If anyone has a solution thanks,
EDIT: Fix for later UE4 builds:
ModSkeletonRegistry.cpp, line 130:
FString MountTarget = FPaths::Combine(*MountPoint, TEXT("Plugins"), *FilenamePart, TEXT("Content/"));
Becomes:
FString MountTarget = FPaths::Combine(*MountPoint, TEXT("Content/"));

ModSkeletonRegistry.cpp, line 130:
FString MountTarget = FPaths::Combine(*MountPoint, TEXT("Plugins"), *FilenamePart, TEXT("Content/"));
Becomes:
FString MountTarget = FPaths::Combine(*MountPoint, TEXT("Content/"));


Provide the hyperlink to [persistentVolumes] in Namespaces page

This is a Feature Request
What would you like to be added
Under Namespaces page,  provide hyperlink for persistentVolumes in section Not all objects are in a namespace.
Why is this needed
it would be useful for quick reference.
Comments
/good-first-issue
/language en
/assign

I would like to work on this.

This issue isn't really well specified enough to be a good first issue.
/triage accepted
/remove-good-first-issue


adding title config

https://nanopay.atlassian.net/browse/NP-94

Please resolve merge conflicts so I can merge. thx

@kgrgreer fixed


data/coords alias

It would be nice to allow in dataset/dataarray to alias a coordinate/data. E.g. ds['time'] == ds['t']. This would be beneficial for midleware libraries to create more natural interface.
Implementation wise, this can be restricted to the indexers of the dataset/dataarray, and internally save a dictionary of aliases.

Hmm, indeed that is quite neat. I don't like that it displays as a separate data so the fact that they are aliased is not obvious. But indeed I think this can be handled externally. Implementation wise that would mean to make a separate wrapper class for attrs and dataset and dataarray, unless, do you know of a method to inject/alter class definitions upon a module load?

Implementation wise that would mean to make a separate wrapper class for attrs and dataset and dataarray, unless, do you know of a method to inject/alter class definitions upon a module load?

I was rather thinking about just using a dictionary of name aliases like
names = {"time": "time", "t": "time"}

ds[names["time"]].identical(ds[names["t"]])

For a bit more convenience, you could create a Dataset accessor to get the original item from the alias name:
aliases = {"t": "time"}

@xr.register_dataset_accessor("aliases")
class AliasesAccessor:
    def __init__(self, xarray_obj):
        self._obj = xarray_obj
        self._aliases = aliases

    def __getitem__(self, key):
        return self._obj[self._aliases[key]]

ds = xr.Dataset({"time": [1, 2, 3]})

ds.aliases["t"].identical(ds["time"])
# True

Thanks, that's really interesting. I'll think about how to design along those lines

note that a big part of cf-xarray is basically that: a way to look up aliases using standardized metadata (ie. metadata following the CF conventions)

:+1: cf-xarray seems like the way to go


Added photo credit to the image on contact page

Added photo credit under the image on contact page

Hey @Rafna was this building on your local? Netlify is failing to preview build it :( .


feat(docs: Add react markdown dependency to render markdown in the bro…

Fixes issue "more detailed tutorial on home page"
Added more detailed instructions on contributing for new devs to the Home.js page in markdown form and using ReactMarkdown component.

Looks great I will go ahead and merge this. 👍


Hyperlinks with the same ID and different URIs collide when they shouldn't

In Windows Terminal Preview 1.4.2652.0.
Hyperlinks support is a great addition, but from my understanding there is a bug with how links IDs are parsed and handled.

Character cells that have the same target URI and the same nonempty id are always underlined together on mouseover.
The same id is only used for connecting character cells whose URIs is also the same. Character cells pointing to different URIs should never be underlined together when hovering over.
(Source: https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda#hover-underlining-and-the-id-parameter )

But testing the same ID with different URIs shows Windows Terminal is grouping them together and using the URI of the last one for both :
echo -e '\e]8;id=a;http://www.microsoft.com/\aMicrosoft\e]8;;\a \e]8;id=a;http://www.google.com/\aGoogle\e]8;;\a'

Even different IDs are grouped together if they are not numbers:
echo -e '\e]8;id=a;http://www.microsoft.com/\aMicrosoft\e]8;;\a \e]8;id=b;http://www.google.com/\aGoogle\e]8;;\a'
While the page about hyperlinks explicitely shows and states that these IDs are strings, not numbers:

params is an optional list of key=value assignments, separated by the : character. Example: id=xyz123:foo=bar:baz=quux.

Complex apps that display data that might itself contain OSC 8 hyperlinks (such as terminal multiplexers, less -R) should do the following: If the encountered OSC 8 hyperlink already has an id, they should prefix it with some static string, or if multiple windows/panes are supported by the app, a prefix that's unique to that window/pane to prevent conflict with other windows/panes.

So, a (uri 1) a (uri 2) is operating as designed. The reuse of an ID with a new URI is utterly intended to replace the old ID.
I can't reproduce your second issue, a (uri 1) b (uri 2):

Complex apps ...

Since Terminal's "terminals" are individual entities with their own hyperlink stores and user interactivity, we don't fall into the "display data that might itself contain OSC 8 hyperlinks" case and are therefore not in need of namespacing. Two hyperlinks in two different panes are automatically in different isolated roots:

note only the link in the right pane is highlighted

The same id is only used for connecting character cells whose URIs is also the same.

Ah. HM.

Why would there be an ID parameter if it cannot be used to disambiguate URIs? Why would you reuse the same ID? I've got so many questions.

@DHowett Yeah, the one with different ids a and b and different URIs seems to be processed as separate, not sure what I did when testing, sorry.

Why would there be an ID parameter if it cannot be used to disambiguate URIs? Why would you reuse the same ID? I've got so many questions.

That one I can answer!
Imagine a CUI utility that shows several files and wants to hyperlink them, you don't want to generate lots of IDs that could collide with IDs that were already output by other CUI utilities.
So that utility could generate a single random ID for its complete output, but have different URIs for each file, instead of having to generate as many IDs as it has to show hyperlinks that are guaranteed to have different URIs.
This is exactly what I'm doing in one of my utility to have hyperlinks spanning several lines of a grid:

interesting! I'd've never expected that that might rely on {id, uri} tuples that differed only on the uri

Yeah, I'm basically using a link ID generator function and try to keep the same ID for a single output.
Calling that ID generator on each line would be uneccessary and pollute the IDs hash table for no good reason.

I think that's just hiding the pollution somewhere you don't have control over ;P because somewhere the terminal emulator needs to store a list of IDs and how they map to URIs, and unique across different URIs, which I expect inevitably pollutes somebody's ID hash table... right?
My quick fix is...
diff --git a/src/buffer/out/textBuffer.cpp b/src/buffer/out/textBuffer.cpp
index 294813a3f..cac3718f4 100644
--- a/src/buffer/out/textBuffer.cpp
+++ b/src/buffer/out/textBuffer.cpp
@@ -2279,32 +2279,35 @@ std::wstring TextBuffer::GetHyperlinkUriFromId(uint16_t id) const
     else
     {
         // assign _currentHyperlinkId if the custom id does not already exist
-        const auto result = _hyperlinkCustomIdMap.emplace(params, _currentHyperlinkId);
+        std::wstring newId{ id };^M
+        // hash the URL and add it to the custom ID - GH#7698^M
+        newId += L"%" + std::to_wstring(std::hash<std::wstring_view>()(uri));^M
+        const auto result = _hyperlinkCustomIdMap.emplace(newId, _currentHyperlinkId);^M

which is pretty much that ;P

sidebar
You're probably more impacted by the fact that we reject `file` URIs, right? We were having a long discussion over on #7526 about it, and never came to anywhere we felt comfortable with. The same discussion is playing out in #7668, because of how hard it is for the Terminal alone to map paths...

Thank you for pointing this out to us!

Imagine a CUI utility that shows several files and wants to hyperlink them, you don't want to generate lots of IDs that could collide with IDs that were already output by other CUI utilities.
So that utility could generate a single random ID for its complete output, but have different URIs for each file, instead of having to generate as many IDs as it has to show hyperlinks that are guaranteed to have different URIs.
If the ID generation is based on milliseconds, it's better not to generate a lot of them within a single utility.

Yeah, I'm basically using a link ID generator function and try to keep the same ID for a single output.
Calling that ID generator on each line would be uneccessary and pollute the IDs hash table for no good reason.

Question: why generate an ID at all? You could just send an OSC 8 sequence with no id parameter and achieve the desired functionality.
If we differentiate links by both id and uri, then we lose the functionality of being able to overwrite previous link URIs by providing the same ID - which I think could potentially be useful in some cases (?)

Yeah, you'll have to store the whole {id,uri} tuple as the unique ID, but I believe it makes sense as since they define what's essentially part of the same link, they cannot have different targets, and updating the target with the latest one received would be a weird behavior and open the door to apps that could end up updating the target right between the time you checked the URI in the tooltip and when you cliked to open it.

Oh, and the following wouldn't work:

Complex apps that display data that might itself contain OSC 8 hyperlinks (such as terminal multiplexers, less -R) should do the following: If the encountered OSC 8 hyperlink already has an id, they should prefix it with some static string, or if multiple windows/panes are supported by the app, a prefix that's unique to that window/pane to prevent conflict with other windows/panes.

An app like tmux would receive output from utilities that do not generate any ID and only rely on the different URIs, but tmux would then give them all the same id by prefixing these empty IDs with its own pane ID.

Right that makes sense, thanks for the explanation! Seems like we'll probably go with @DHowett's fix since it essentially uses the {id,uri} tuple as an ID.

I think the operant part of that sentence though is "already has an ID" -- in the no-ID case, tmux would pass it through without an ID, and there wouldn't be any chance of collision since it's uniqued by the TE.

Imagine one that has
+-------+--------+
| pane 1 | pane 2 |
|             |             |
+-------+--------+
And multiplexer has to show the some output that has to be wrapped:
+-------+--------+
| pane 1 | hyperli |
|             | nk1      |
|             | hyperli |
|             | nk2      |
+-------+--------+
To group these by link, it has to assign them ids relative to the pane they appear in, but original utility didn't have to since it was just outputting them for a single screen.

This may be hypothetical -- I can't get tmux to actually produce a link. I think if it can track a region of text that it knows to be a hyperlink, it's going to have to assign an ID. That doesn't mean it's gotta use the same ID for every hyperlink (?)

The specification goes on to suggest how tmux might handle this -- assigning a new mangled ID every time an un-ID'd hyperlink is encountered. That's what conhost/conpty does, as well.
It seems like dropping IDs is safer for uniqueness (even across sessions of AXSH) than a static ID if it's not ever intending regions of text to highlight together! /shrug

(That doesn't mean I'm not going to fix this bug! It's definitely wrong, but we're in the weeds of talking about how your application can recover while we're wrong.)

This may be hypothetical -- I can't get tmux to actually produce a link. I think if it can track a region of text that it knows to be a hyperlink, it's going to have to assign an ID. That doesn't mean it's gotta use the same ID for every hyperlink (?)

True, but generating an ID prefix that simply encodes the pane ID saves it from having to keep track of all the links encountered, it can just keep track of its panes and how to prefix links based on panes.

But then that violates another quality of the spec: that two non-ID'd hyperlinks pointing to the same URI do not underline together.
Admittedly info on the ground here is thin, but regarding adjacent links with no ID but the same URI:

Here VTE and iTerm2 differ, but from a practical point of view, this difference should not matter.

Question: why generate an ID at all? You could just send an OSC 8 sequence with no id parameter and achieve the desired functionality.

Because in that grid() function, the whole tile of each ANSI-art icon + label acts as a single hyperlink, so these links span several lines and are entertwined with other grid cells on each line. Not providing IDs would work when you click, but wouldn't have the hover highlight on the whole tile on mouse over.

If we differentiate links by both id and uri, then we lose the functionality of being able to overwrite previous link URIs by providing the same ID - which I think could potentially be useful in some cases (?)

I belive that would be against specs, incompatible behavior with other terminals and risky as new output could modify a previous link, including some link shown by another utility in the same scrollback buffer if ID collision occurs between utilities in the same shell.
Using {id,uri} as the unique ID means you might have the highlight effect spanning several outputs if ids and uris collide, but at least it's only a visual glitch, you can't have an utility take over another utility's output targets.

It seems like dropping IDs is safer for uniqueness (even across sessions of AXSH) than a static ID if it's not ever intending regions of text to highlight together! /shrug

True, I don't generate ids if a link is on a single line, only if they span several lines.
For example, my dir() function doesn't generate any id since each item appear on a single line

Ah, the icon. That's the part I was missing.
Isn't it annoying that they're covered in dashed lines? 😁

Yeah, check the sidebar I linked above :wink:

Isn't it annoying that they're covered in dashed lines? 😁

Yeah, it is, other Terminals I've tried only underline on hover which was better looking but less discoverable.
The docs page did hint that underline would be on hover only:
` There's a nontrivial question though: Which cells to underline on hover? As opposed to webpages, we lack the semantics, the information about the cells that belong together and form a single web anchor.
But I respect your artistic decision here... as long as you give us a switch in the profile to turn it off :D

Yeah, check the sidebar I linked above 😉

Ah, yeah, that's bad news, I had hopes to let users just click a file from a directory/list utility if they wanted to just open the file on their desktop.
Guess I'll have to just write a protocol handler with some random name that delegates the job to the original file: handler class to work around it, making your security moot and links less clear to users 😆

Since the Terminal cannot guess which LX instance some output is coming from, how about...
You intercept outputs at the LX subsystem level and replace any link with "file://*" protocol to something like "wslfile://[lx_instance_id]/[original_linux_path]".
Then, you write a Win32 protocol handler registered for wslfile URLs that connects to the lx_instance_id and launches the file original_linux_path within the original instance.
Or if you don't want to write a protocol handler to integrate it with apps on the Linux side, maybe you could just replace any file://* with file://wsl$/instance/* to let Windows apps access these links ? (I'd find the protocol handler more elegant)

I finally got off my behind and put that patch into PR.

Thank you! 😊


Allow lnd.conf button

Have you considered adding a lnd.conf button to node-launcher?
bitcoin-qt has a config button which makes it simple to access 😄

Yes! Click on Advanced...


Add metadata as a field in serialize

safetensors.flax.save and safetensors.flax.save_file provide another param besides tensors which is metadata, a dictionary with some metadata to be stored too.
More information at https://huggingface.co/docs/safetensors/api/flax#safetensors.flax.save and https://huggingface.co/docs/safetensors/api/flax#safetensors.flax.save_file

https://github.com/huggingface/safetensors/issues/147


Fix the test error of "Add finders for enableFlutterDriverExtension" and resubmit

Description
Fix the test error of "Add finders for enableFlutterDriverExtension" and resubmit
Related Issues
#65273
#64308
#62299
Tests
I modified the following test:

extension_test.dart

waitUntilNoTransientCallbacks
waitForCondition
getSemanticsId
getOffset
getText
descendant finder
descendant finder firstMatchOnly
ancestor finder
ancestor finder firstMatchOnly
GetDiagnosticsTree
waitUntilFrameSync

find_test.dart

Ancestor finder deserialize
Descendant finder deserialize

Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.

/ cc @dnfield


Update version to 1.1.12-4 on staging

Update version to 1.1.12-4

🚀 Deployed to staging by @OSBotify in version: 1.1.12-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.1.13-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Distribution: pull-deps compiled hadoop version

I spent quite some time, after updating hadoop version, to figure out why in the distribution directory I still had hadoop-client-2.3.0 dependencies. With this patch, the same version used to compile is added to the deps. Tested with 2.4.0 and 2.6.0-cdh5.7.0.

Hi @ecesena, thanks for the contribution. Would you mind filling out the SLA at http://druid.io/community/cla.html ?

The issue here is that io.druid.indexing.common.config.TaskConfig#DEFAULT_DEFAULT_HADOOP_COORDINATES defines a version to use in the absence of some other version, and THAT version is supposed to be pulled unless --no-default-hadoop is specified.

My bad, specifying -h implies --no-default-hadoop

since the default is <hadoop.compile.version>2.3.0</hadoop.compile.version>, I propose adding a warning comment in the pom at the version specification stating that modifying this value will cause the default hadoop coordinate to be invalid. Meaning that the user must specify the correct hadoop coordinate to use in their runtime.properties

It seems likely that anyone modifying that hadoop compile version would also want to modify the default default hadoop version as well (just so tasks can work without having coordinate overrides). So in that case maybe all we need is the comment.

SLA signed

Hey, sorry, do you expect some changes on this? I didn't really get what is the final decision. Thanks, E.

@gianm you had some comments, do you think they should get fixed?

I'm fine either way. No matter what though there should be an additional comment mentioning that the default hadoop coordinates probably need to be changed too (else folks will get confused when druid still tries to pull 2.3.0 at runtime).

@ecesena, can you add the comment the @gianm mentioned about hadoop coordinates ?
I think its pretty close to be merged.

@drcrallen @gianm I created a follow up PR for adding the comment

https://github.com/druid-io/druid/pull/3257

👍

Thank you @nishantmonu51, and sorry for being unresponsive (very limited availability lately)

👍


Akasnik migrate tailwind update diagrams

EMEA FastTrack doc-a-thon - Updated diagrams to match newest discovery features.

@alejandra8481
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

Perfect. Looks great. #sign-off

@alejandra8481: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Trying #sign-off again

@Court72: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@akasnik: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Thanks for your sign-offs @akasnik and @alejandra8481 ; In a new PR, consider making these additional improvements to the images:

Standardize all instances of "VMWare" and "Vmware" with this capitalization: "VMware", per the Microsoft Cloud style guide.
Standardize all instances of "Hyper-v" with this capitalization: "Hyper-V".
Standardize all instances of "Vcenter" with this capitalization: "vCenter".


[BUG] tv-casting-app does not connect to tv-app on recommissioning

Reproduction steps
Test with the Android tv-casting-app and the Linux tv-app.
Note: The Android tv-casting-app has behaviour to skip the UDC flow if the app is already commissioned with the selected TV. Make a temporary code change in the DiscoveredNodeData.java class in the isPreCommissioned method  to return false instead of return connectableVideoPlayer != null This is done so that we can simulate cases where the post-commissioning flow may have failed which would require the app to go through commissioning again.

Commission the Android tv-casting-app with the tv-app.
Kill and restart both the Android tv-casting-app and the tv-app.
Run through the commissioning flow

Actual result: The tv-casting-app fails to proceed to the Cluster selection screen and never connects to the Linux tv-app it had previously commissioned with.
Expected result: The tv-casting-app finds that it is already commissioned with the selected tv-app and establishes a CASE session with it.
Bug prevalence
Everytime I do this with the above steps to repro
GitHub hash of the SDK that was being used
19c8ea42b4f4af2669643b758caa4cf412cfee69
Platform
android, other
Platform Version(s)
No response
Anything else?
No response

We must read the nodeId from the bindingTable directly and should not rely on the cached video player data on the casting app side.


[ensure-kubectl] Timeout downloading cloud SDK Core libraries

ensure-kubectl is timing out when downloading gcloud core libs.

@baileymiller182 is this something that has just started happening or every time you try to run ensure-kubectl? I've tried with a project running on Circle 1.0 and was able to run the command successfully.

It happened 2x in a row yesterday, but hasn't happened since. Perhaps Circle or Google just had a networking blip. We can probably close this issue.

Sorry you were running into that. That code is a bit before my time but we have been discussing moving to just wget'ing the kubectl file which should hopefully be a bit more reliable by not relying on all of gcloud to update.


Export color scheme

Is your feature request related to a problem? Please describe.
It would be good if the export of material 3 color scheme was not only for compose, but also for XML.
Describe the solution you'd like
Add a feature to export or copy generated color scheme.
Describe alternatives you've considered
No idea.

I really don't want to support XML in any forms 👀


Fixes ClearBit with timestamp; fixes #1324

Overview
Fixes #1324
Pull request checklist

[ ] I have read the contributing guide.
[ ] I have agreed to the Contributor License Agreement.
[ ] I have updated the documentation.
[ ] I have resolved any merge conflicts.
[ ] I have included tests that cover my changes.
[ ] All new and existing tests pass.

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.

Updated with a test. Should be good to review.

So, the current state of this is that ClearBit should not take a timestamp argument at all, but should clear all bits for all time quantums at the given row/col. This PR needs to either needs to be updated, or closed and a new one made with this logic.


Customisation via with StoreOptions.options(...) is broken (illustrated in "Options" tutorial)

There is a bug which becomes apparent in the Options tutorial at the very end of section "Controlling options from Python" (last sentence). The text reads: "Here the result is red [...]", but the image remains green. I can reproduce this by running the commands in an IPython notebook (version 1.3.2, git revision 8e3cedc6). Not sure if this is a bug in Holoviews itself or whether the syntax/options have changed and simply need to be updated in the tutorial.

Thanks for pointing this out, I'll be look into this problem shortly!

I've finally had a chance to look into this...sorry for the delay.
Essentially, what we wrote in the tutorial:
with hv.StoreOptions.options(green_sine,
                             options={'Image':{'style':{'cmap':'Reds'}}}):
    data, info = renderer(green_sine)
print(info)
SVG(data)

Does indeed reflect what happens to the local style context! At the level of Image, the colormap is red as specified, made clear in this more appropriate example:
img = hv.Image(np.random.rand(10,10)) # A 'fresh' object
with hv.StoreOptions.options(img,
                             options={'Image':{'style':{'cmap':'Reds'}}}):
    data, info = renderer(img)
print(info)
SVG(data)

The problem here is that we customized this specific object with the Greens colormap earlier:
green_sine = image(style={'cmap':'Greens'})

Which adds an entry in the options system specifically for that object by its group and label (namely under the key 'Image.Function.Sine') which is then a more specific declaration than the specification given toImageobjects in general (and therefore the former takes precedence). The way to change the color to Reds for this particular object would be to use this more specific specification:
with hv.StoreOptions.options(green_sine,
                             options={'Image.Function.Sine':{'style':{'cmap':'Reds'}}}):
    data, info = renderer(green_sine)
print(info)
SVG(data)

Once again, thanks for pointing this out!
We should have spotted this earlier - we know it can be tricky to understand the style system which is we have a tutorial in the first place. It is possible that the tutorial worked as stated at one point but once we made the style system work more consistently, we failed to update the tutorial. Hopefully, we can now make the fix and avoid confusing anyone else in future!

As this doesn't seem to be an actual bug in our code, we can fix the tutorial in two ways:

Try to explain the above! If people understand it, then they really will have a good grasp of the style system.
Create a new image object just to introduce the context manager works.

I'm not sure which approach we would prefer to take but as it is a documentation fix, it will be quick to do now. We should still try to fix it before the 1.4 release if we want to bundle notebooks in the PyPI package as we normally do.

Since it is the Options Tutorial and this needs to be explained somewhere I think we should do both.

Ok, I agree. I think we can start with showing the context manager on the new object to introduce it and then explain what is going on to style an object that has already been customized.

Fixed the tutorial in 74ce7cc. Hopefully it is cleared now!


Fix for clipped descenders in feature headings

I'm not seeing clipped descenders on the front page. What browser and resolution are you on?

Right, I see this problem too on Chrome on Linux, any window size: one or two pixels of the gs in the item headlines are cut off. Not sure why it doesn't look right by default, but this PR fixes it for me.


Binary packages for 1.2.1 release are REALLY missing - with screenshot

Hello,
I'm re-opening a ticket since #9645 was closed before I could answer.
I don't know what happened, but I can confirm there're no downloadable packages for 1.2.1. I DID wait a few days before opening the ticket because I had already noticed that the release files are attached AFTER the release is created.

I don't know what you see there in the #9645 screenshot, but maybe the "draft" indication means something like "people working for GitHub/Atom can access this release, but others don't"? Have you tried accessing the releases page from an incognito window?

You could still reply in #9645 and ask me to reopen the issue instead of creating a new one though.
Actually you're right, the binaries are only available to owners and collaborators, and otoh it makes sense for a release in a draft state to not be made available to everyone, since there's probably a lot of things that still may be somewhat broken and we probably don't want these to get installed by users in the large before it have been properly reviewed internally.

I apologize for the double ticketing issue. Unluckily, there seems to be no
One Size Fits All "right answer" - in many FOSS I open tickets for, there
is no response after ticket is closed, and a new one must to opened to
really gather attention.
About the specific issue: what does it mean the release is in a "draft"
state? And how would people from outside know?
In fact, I can see that the webupd8 team, which rebuilds and repackages
Atom, has already pushed an 1.2.1 binary build on their PPA:
https://launchpad.net/~webupd8team/+archive/ubuntu/atom/
I'm the creator of the
https://github.com/alanfranz/atom-text-editor-repository , an apt and yum
mirror for original atom packages, and I can assure you it's the first time
it happens - usually release packages are in place within about an hour of
the original tagging - at least for full. non-beta releases.
If it's not a proper release, wouldn't "beta" be a better name?
Thanks for your effort.
Bye,
Alan
On Tue, Nov 17, 2015 at 11:55 AM, Cédric Néhémie<EMAIL_ADDRESS>wrote:

You could still reply in #9645 https://github.com/atom/atom/issues/9645
and ask me to reopen the issue instead of creating a new one though.
Actually you're right, the binaries are only available to owners and
collaborators, and otoh it makes sense for a release in a draft state to
not be made available to everyone, since there's probably a lot of things
that still may be somewhat broken and we probably don't want these to get
installed by users in the large before it have been properly reviewed
internally.
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/9647#issuecomment-157336142.

A "draft" state means that the release is not yet final and has not been published.  In other words, it's still being worked on (and can only be seen by project maintainers).  See also #9595.
Hope that answers your question this time - if not feel free to comment here :).

Yes, now I looked at the other ticket and I got that; I shouldn't look at
the tags, even though I've got the very same issue as #9595 - the atom feed
for atom releases includes tags. I'll work around it.
Thank you!
On Tue, Nov 17, 2015 at 3:10 PM, Wliu<EMAIL_ADDRESS>wrote:

Closed #9647 https://github.com/atom/atom/issues/9647.
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/9647#event-466701126.

1.2.1/1.3.0-beta2 are now out.


[RESTEASY-2996] Calling send for each chunk with flush and completing the future

I cherry picked this change from the main branch as we need this change back ported to the last release version.
Main PR.

@jamezp  We are looking forward to make use of this fix as well as this one which was recently merged to 4.7. Can you help make a 4.7 patch release with these fixes ?

@jamezp We are looking forward to make use of this fix as well as this one which was recently merged to 4.7. Can you help make a 4.7 patch release with these fixes ?

@dnagarajan89 Yes. I'll include this in the 4.7.2.Final release as well.

@jamezp We are looking forward to make use of this fix as well as this one which was recently merged to 4.7. Can you help make a 4.7 patch release with these fixes ?

@dnagarajan89 Yes. I'll include this in the 4.7.2.Final release as well.

@jamezp is there a tentative date for the release so that we can plan accordingly ?

@jamezp is there a tentative date for the release so that we can plan accordingly ?

I'm planning on today or tomorrow. One other possible bug has been found in WildFly we need to sort out, then I'll release. At the very latest sometime next week as there is a WildFly release planned then and we need any bug fixes in.

@dnagarajan89 I guess the day was today. 4.7.2.Final has been released.

@dnagarajan89 I guess the day was today. 4.7.2.Final has been released.

@jamezp Great news!. Thanks a lot for your kind help and support.


React translator #hackoctober

First thing, PLEASE READ THIS: ReactPlay Code Review Checklist

Description
Hi, i have added a new play that is react translator application which translates any written language to any other language
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
No issues was fixed
This is for hackoctober fest
No extra dependencies was used while making this app
Fixes # (issue)
Issue No - #1329
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I have tested the application on my local machine it works well and it has no issues
Play is completely bug free
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Screenshots or example output

Issue no - #1329

@irfanmit in future please avoid creating PR without being assigned.

@irfanmit in future please avoid creating PR without being assigned.

I apologize for this...should i close this PR and re-open when assigned on issue #1329?

@irfanmit in future please avoid creating PR without being assigned.

I apologize for this...should i close this PR and re-open when assigned on issue #1329?

no no

hello @irfanmit please check the code there is a stopwatch project code

well....sorry but i did not get you
this is a different application
i have two PR one is #1278(Stopwatch) and #1330 (Translator)
THIS IS A TRANSLATOR APP CODE

THIS IS STOPWATCH APP CODE

am i doing anything wrong here? can you specify sir please

Hi @irfanmit, thanks for your contribution. Please only include files related to the translator play in this pull request. It seems there are changes for other plays as well. Can you remove those and keep only the translator play changes?


Implementation of Traffic Scenario 01

Added new scenario in control_loss.py
Added new atomic SteerVehicle
Added new criteria ReachedLocationTest
Added new scenario to list in scenario_runner.py

This change is

I am not sure, if this scenario is what we really want to have.
The crash scenario describes a situation, where a vehicle lost control, due to road conditions, driving without attention, etc. Hence, I think the scenario should test, if a vehicle can drive properly from A to B (going through some narrow curves, etc.). This is also what is stated by the NHTSA crash report:
https://www.nhtsa.gov/sites/nhtsa.dot.gov/files/pre-crash_scenario_typology-final_pdf_version_5-2-07.pdf (page 29)

Typical Scenario: Vehicle is turning left or right at an
intersection-related area, in daylight, under clear weather
conditions, with a posted speed limit of 45 mph or less, and then
loses control due to wet or slippery roads and runs off the road

What the implementation does in contrast, is to manipulate the driving commands (like a tire puncture would do when driving). I am not sure, if this is what we should test here. In addition, there might be timing issues with this implementation: Assume you have two clients (the scenario + an AD stack). Both are sending steering commands to the CARLA server. The behavior may be different, depending on which command arrives first...

I think reviewable got crazy. I did not approve.

And, the criteria should be updated to capture, that the vehicle re-gained control (i.e. came back to correct lane, drives normally, etc.). I suggest to do check the most simple things for now:

No crash
At the end of the scenario in correct lane (can be checked via waypoint) --> Add a new criterion for this
(You could even count the number of ticks, the ego vehicle is not within the correct lane, and add a threshold to define success/failure)

@SubhashiniPerumal Thx for the updates. I tested it, and it looks much better than before. Still, I am bit worried about the usability of this scenario. It happened a few times, that the vehicle crashed against street lights, while the control loss was active. If we think about German's idea for the challenge, the scenario will always "win" against the client/user driving commands. So, the car crashes, because of the scenario, not because the user code could not handle the situation. In other words, the scenario will cause the failure, not the user code.
@germanros1987, @SubhashiniPerumal : Maybe we need to move this scenario to Town03, where the streets are wider? Or the control_loss needs to be updated, such the car doesn't hit a street light...
Suggestions?

Tested and approved. Can be merged.


Recurse includes searchparametermap

Adds recursive include/revinclude support (described more here: https://github.com/hapifhir/hapi-fhir/issues/3269)

Testing the Pull Request

Either run the tests (which were changed and now pass)
Create a SearchParameter map and add a recursive include to it, if the normalized query string includes the recursive include it is working.

Pull Request Reviewing
To review this pull request, please utilize the checklist below that is based on our pull request review guidelines.

[ ] Does the pull request adhere to the functionality requirements and guidelines?
[ ] Does the pull request adhere to code quality guidelines?
[ ] Are optimizations possible for the content in this pull request?
[ ] Is the content in the pull request properly tested and validated?
[ ] Is the pull request properly documented, both in the code and in documentation?
[ ] Do the changes in the codebase break existing functionality or endpoints that may be relevant to partners?
[ ] Are our partners informed of this change if necessary?

I wouldn't merge this into master cause we need master to be a full copy of upstream master, to avoid conflicts. Can you merge this into the "hinq" branch?


Update TaskContract.sol

Bound Check for array input.

In the getMyTasks function, there is no bounds checking when copying tasks into the temporary array. If the counter exceeds the temporary array's length, it could lead to an exception. We can add a check to ensure counter doesn't exceed temporary's length.

So , I updated the file with required changes.

@AVI-SHUKLA1110 what is your issue no.?

@AVI-SHUKLA1110 then you should create an issue first and when it'll get assigned to you, then raise a pull request okay.

Okayy thnks

@shubhisingh184  the issue number is https://github.com/Vikash-8090-Yadav/Future.WebNet/issues/503

@Vikash-8090-Yadav  @shubhisingh184  please merge it


Added Clio to other.

Please don't remove the status link for IFTTT.
Please make Email: all lowercase, changing it to email:

On Thu, Mar 19, 2015 at 9:01 PM, Jacob<EMAIL_ADDRESS>wrote:

Please don't remove the status link for IFTTT.

Don't know what IFTTT is.

Please make Email: all lowercase, changing it to email:

done.

—
Reply to this email directly or view it on GitHub
https://github.com/jdavis/twofactorauth/pull/1018#issuecomment-83834465.

Your PR interferes with another website on the list.
Look at the changes in the Files changed tab to see what I mean.

You can also remove the twitter: line if you would like. That is only used when a website does not support 2FA.

@plecavalier you should create separate branches for your changes. otherwise, if you work from the same master branch, your changes to one pull request will show up in the other.

@Jacob Sorry that wasn't my intention. I'll fix that.
@mxxcon Yeah I just learnt that yesterday. Dealing with source code is
clearing not my strong point. I'll get the hang of it eventually...
Thanks! Phil
Ottawa:<PHONE_NUMBER>
Cornwall:<PHONE_NUMBER>
Any distribution, use or copying of this e-mail or the information it
contains by other than the intended recipient(s) is unauthorized.
On Thu, Mar 19, 2015 at 11:12 PM, mxxcon<EMAIL_ADDRESS>wrote:

@plecavalier https://github.com/plecavalier you should create separate
branches for your changes. otherwise, if you work from the same master
branch, your changes to one pull request will show up in the other.
—
Reply to this email directly or view it on GitHub
https://github.com/jdavis/twofactorauth/pull/1018#issuecomment-83869183.

uhm there's a - on every line you've added. There should only be a - infront of name:


Add server API

Stack example rd2

#2  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nayyarv and the rest of your teammates on  Graphite


Make the deposit step part of the new YAML configuration

If deposit data is included in the YAML proposal file then execute the deposit command  else if empty allow user to do  the deposit as a secondary step.

resolved by #64


[KO] Update notebooks for Issue #184

Fix for #184.
Files:
site/ko/tutorials/distribute/multi_worker_with_keras.ipynb
site/ko/tutorials/keras/save_and_load.ipynb
site/ko/swift/python_interoperability.ipynb
site/ko/guide/random_numbers.ipynb

Correct some typos in translation.
Update by nbfmt and nb_code_syn.
Check with Colab.

Thanks

@googlebot I consent.

@googlebot I consent.

I updated random_numbers.ipynb and multi_worker_with_keras.ipynb from latest en version.
Hi reviewers(@cre8tor, @Choiuijin1125, @JKIsaacLee, @NoelBird, @wckim, @eat-toast, @jaketae)
These notebooks are failed to publish, because en version has changed.
To continue publishing, could please to review this PR? :)
Thanks a lot!

I have approved it. Let's merge this.

Thanks. Fixed a merge conflict when rebasing and used the changes in this branch.


Type results depends on quotes used

As referenced in the pdf with the use of unicode double quotes (Page 21):
print type(“REAL”); ' the use of unicode double quotes, shows INTEGER
print type("REAL"); ' double quotes, shows REAL

print type(“INT”); type(“REAL”); ' the use of unicode double quotes, shows INTEGER INTEGER

but in this case,
print 123 is type(“INT”) ' the use of unicode double quotes, shows 1/true
print 123 is type("INT") ' double quotes, shows 0/false

should only double quotes be used? so not sure if this is just typo or a bug,
but definitely needs some clarity.

All Unicode characters are also valid compoments in an identifier. Thus “REAL” is a whole variable (with value 0) here.
It's ok for most characters but quite confusing for quotes and other symbols. Will make an update to exclude these symbols from being a part of an identifier.

Updated to disallow Unicode quotes in code, which behaves similarly to other languages that support Unicode.
There are some other Unicode symbols that could confuse a programmer, but for the moment just leave it at that. I'd try to figure out a full list of those symbols.


Fix some localisation issues

Add St Paul IV, Pope celebration to general.js;
Add St Paul IV, Pope key to en.js and sk.js;
Remove saintsCosmasAndDamian in favour of saintsCosmasAndDamianMartyrs;
Remove saintHedwigReligiousSaintMargaretMaryAlacoqueVirgin in favour of saintHedwigReligiousOrSaintMargaretMaryAlacoqueVirgin;
Remove saintJohnOfGodPriest in favour of saintJohnOfGodReligious;
Remove saintJuanDiego in favour of saintJuanDiegoCuauhtlatoatzin;
Remove saintMarkApostle in favour of saintMarkTheEvangelist;
Remove saintOliverPlunketBishopAndMartyr in favour saintOliverPlunkettBishopAndMartyr;
Remove saintPioOfPietralcina and saintPioOfPietrelcinaPadrePioPriest in favour of saintPioOfPietrelcinaPriest (with the en.js value changed to Saint Pio of Pietrelcina);
Remove saintEzekielMorenoBishop in favour of saintEzequielMorenoBishop;
Remove saintLorenzoRuizAndCompanionsMartyrs and saintsLawrenceRuizAndCompanionsMartyrs in favour of saintLawrenceRuizAndCompanionsMartyrs;
Rename saintWenceslausMartyrSaintsLawrenceRuizAndCompanionsMartyrs to saintWenceslausMartyrSaintLawrenceRuizAndCompanionsMartyrs;
Rename saintClementOfOhridAndGorazdBishopsAndCompanions to saintsClementOfOhridAndGorazdBishopsAndCompanions;
Rename saintAgnesCaoGuiyingMartyr to saintAgnesTsaoKouYingMartyr (and change the en.js value);
Fix apostrophes in l10n files;
Add missing keys from en.js to sk.js;
Fix the value of saintBlaseBishopAndMartyrSaintAnsgarBishop (change and to or) in en.js and sk.js.

Notes
On St John of God: according to Wiki, he was not ordained a priest nor does he has priest title in Slovak liturgical calendar, nor at Universalis.
On St Mark: I could not find any resource (except for Wiki) with liturgical calendar of New Zealand that would use apostle title for St Mark. Source I have found: Universalis and GCatholic.
On St Oliver Plunkett: I am not sure which surname (either with a single t or with doubl tt) is correct. On the Internet, there one can find both surname spellings. I’ve chosen one
On St Padre Pio: I have change the the in accordance with the calendar of the Liturgy Office (England & Wales) plus the title Priest.
On St Agnes Tsao Kou Ying: According to Wiki, both should be correct, but Tsao Kou Ying might be the widely used transcription of the Chinese name, but is also lists the Cao Guiying as an alternative transcription.

I’d like still fix the comma issue in sk.js and probably even #174.

Also I don't know what's the ETA on the _F-TypeScript branch. In this branch, there is a major change in the codebase, so everything merged outside this branch might be difficult then to merge back in this branch.
So here I wonder if you should open this PR against the _F-TypeScript branch instead, or better: wait this TS branch get ready and at least get merged into dev (to avoid the same scenario of the romcal-es6 branch).

Okay, I’ll port the changes to _F-TypeScript.


How can I run a project template project using command line? (VSIX)

I'm very much new to visual studio extensions. Currently, I'm working with vsix project template with a wizard. I used this guideline to create the project.
https://docs.microsoft.com/en-us/visualstudio/extensibility/how-to-use-wizards-with-project-templates?view=vs-2019
I want to run this project in command prompt. But It doesn't work. It gives me the following error.
error MSB4019: The imported project "C:\Program Files\dotnet\sdk\5.0.301\Microsoft\VisualStudio\v16.0\VSSDK\Microsoft.VsSDK.targets" was not found. Confirm that the expression in the Import declaration "C:\Program Files\dotnet\sdk\5.0.301\Microsoft\VisualStudio\v16.0\VSSDK\Microsoft.VsSDK.targets" is correct, and that the file exists on disk.
From visual studio I can run the project without any issue.

@kalpanibhagya -- Kalpani, thank you for your question.  This repo is solely for documentation issues, with limited help options.  Please consider these resources:

Visual Studio on Microsoft Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

cc @leslierichardson95 for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.

@WilliamAntonRohm Thank you :)