[TF] Further cleanup of CompilerRuntime and friends

I was getting started with TPU support, and this functionality wasn't doing what it was advertising. After a chat with the team, I learned that it was designed to work with GPE, and with GPE gone it doesn't make much sense anymore. Therefore, I decided to go ahead and remove it.

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci I'm begging you please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

Merging while the macOS job is running, since it is expected that this job will fail anyway.


update orgmode syntax: #+begin_export backend vs. #+begin_backend

Hello,
Some time ago, Org adjusted the syntax for exported language blocks. I'm not positive when... I actually thought it was back with the release of Org-mode 8.0, but these release notes suggest it might be 9.1 that brought the change. I've been on git forever, so I'm not sure.
Export blocks are explicitly marked as such at the syntax level to
disambiguate their parsing from special blocks.  The new syntax is

#+BEGIN_EXPORT backend
...
#+END_EXPORT

instead of

#+BEGIN_backend
...
#+END_backend

Here is my .org. test file:
#+begin_comment
.. title: index
.. slug: index
.. description: org test
#+end_comment

* section

Here is some raw html code:

#+begin_export html
bold text: test
#+end_export

#+begin_html
bold text: test
#+end_html

I left plugin/init.el alone except for uncommenting the load path:
;; Load org-mode
;; Requires org-mode v8.x

;; Uncomment these lines and change the path to your org source to
;; add use it.
(let* ((org-lisp-dir "~/.elisp/org/lisp"))
  (when (file-directory-p org-lisp-dir)
      (add-to-list 'load-path org-lisp-dir)
      (require 'org)))

Just to confirm, this is definitely where my orgmode lives:
M-x org-version
Org mode version 9.0.5 (release_9.0.5-288-g4caad0 @ /home/jwhendy/.elisp/org/lisp/)

The respective sections get exported like so, showing that #+begin/end_export html is not picked up (first instance), but #+begin/end_html is (second, rendered instance).

bold text: <strong>test</strong>

bold text: test

Screenshot of served webpage:

Org does the opposite using C-c C-e h and one of the html options, rendering the correct syntax and botching the deprecated variant:
bold text: test

bold text: <strong>test</strong>

Let me know if there's something I should check for on my end, and thanks for taking a look!

@jwhendy I'm not sure what this issue exactly expects us to do on the Nikola plugin end. Org-mode's release notes provide a function to fix existing files, and you should probably run that on all your Nikola post files. I don't think such a fix should be implemented in the plugin. If you are convinced otherwise, feel free to re-open the issue and we can discuss to see what can be done.

You could use this script to fix the posts in your blog, if you like. I tested it on my own blog, and it seems to work fine. Please create a backup copy of your posts before running this script, though.

After typing up a lengthy response, I think I found the issue but don't understand.
My entire issue above was that I'm already using the new syntax, but Nikola wasn't recognizing it. Take a look at the reproducible example: I showed that the first (correct) syntax rendered verbatim whereas the old/deprecated syntax produced the desired result (bold text).
Org's output was exactly the opposite, also shown.

After digging around some more, I found that if I use emacs -Q, then my org-mode output matches Nikola. So, I think the issue is not having my git installation of org found; instead it's using the version shipped with emacs. I posted my config above; any reason this wouldn't work?
Here it is again:
$ cat ~/Desktop/mysite/plugins/orgmode/init.el
(let* ((org-lisp-dir "~/.elisp/org/lisp"))
  (when (file-directory-p org-lisp-dir)
      (add-to-list 'load-path org-lisp-dir)
      (require 'org)))

(require 'ox-html)

After even more fiddling, I'm at a loss. I started getting errors about a bad emacs config when I tried to use a #+begin_src elisp block to output the result of M-x org-version during the export (to confirm which version of org Nikola used). Then I couldn't make it go away!
Wiped the plugins dir, reinstalled, and now things are working fine. I'm at a complete loss, but I changed so much during my hunt I couldn't tell you what it was. I even diffed my pasted plugin init.el from yesterday with the one that's now working and they are identical.
Sorry for the noise, and thanks for taking a look.


[Experimental] Adds firehose functionality using websockets

Please add a description including what this is supposed to do and why it is being done, FTR.
Also, shouldn't this get some tests added for this new functionality?


change date time to DateTimeOffset to support other calendars like Persian calendar

@zoha-shobbar This is currently out of our scope. If someone wants to take this on as a contribution, it would be welcomed.


Visualize output of offline_lidar_obstacle_perception

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04): 14.04
Apollo installed from (source or binary): source
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0): 5.0.0

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

Supporting materials (screenshots, command lines, code/script snippets):
After running the offline_lidar_obstacle_perception, it outputs a list of .pcd files, including detection and classification results, I was wondering if there's a way to visualize them since the output pcd is not in standard pcd format. One of the detection result in one of the output files is as follow:
velodyne_64 45 -1 0 0.56447983 smallMot -12.790524 59.134152 -2.6194043 2.299372 0.43805593 1.0530068 0.065690992 0 0 0 0 0 0 0 12 -12.544291 59.09613 -2.6194043 255 -12.255737 59.107533 -2.6171601 245 -12.062275 59.108479 -2.6153829 255 -11.874406 59.136208 -2.6149154 255 -12.267098 59.020821 -2.2577293 182 -12.076079 59.033447 -2.2566676 188 -11.870986 58.975143 -2.2526665 255 -11.65131 59.331112 -2.2652416 233 -12.214779 59.31852 -1.9287851 179 -11.92657 59.334148 -1.9273046 231 -11.750023 59.422104 -1.9291375 207 -13.94998 59.244888 -1.5663975 210 -5 -13.94998 59.244888 -2.6194043 -12.267098 59.020821 -2.6194043 -11.870986 58.975143 -2.6194043 -11.65131 59.331112 -2.6194043 -11.750023 59.422104 -2.6194043

How do you execute offline_lidar_obstacle_perception?

How do you execute offline_lidar_obstacle_perception?

@tkkhuu Did you solve this problem?


Wrong version reported

Describe the bug
After installing quspin 1.0.0 with pip the module version shows 0.3.7
To Reproduce
# Create a venv, activate it and pip-install quspin==1.0.0
python3 -m venv .venv
. ./.venv/bin/activate
pip install quspin==1.0.0

# verify it reports the wrong version
python -c "import quspin; print(quspin.__version__)"
> outputs 0.3.7

You can also download the tarball from PyPI and check that the version in src/__init__.py is wrong.
Expected behavior
The command above should return 1.0.0
Additional context
The version used by the setup function is being read from the conda recipe
https://github.com/QuSpin/QuSpin/blob/cadd8155c2ca21671b009fa92185202f14621c0b/setup.py#L44-L50
but that has not been updated
https://github.com/QuSpin/QuSpin/blob/cadd8155c2ca21671b009fa92185202f14621c0b/conda.recipe/quspin/meta.yaml#L1

My bad, I saw that your PR was merged, but missed it was merged into dev. Reopening the issue for now.


It looks like it's the npx @arkweid/lefthook -h in .git/hooks/prepare-commit-msg that is really slowing things down.

time npx @arkweid/lefthook -h | tail -n 1

1.28s user 0.26s system 147% cpu 1.044 total

If the yarn option came before the npx version, that would speed things up a lot:

time yarn exec lefthook -h | tail -n 1

0.13s user 0.06s system 48% cpu 0.394 total

An npm exec option before npx option would also be a lot faster:

time npm exec lefthook -h

0.20s user 0.07s system 103% cpu 0.260 total

It looks like this is fixed in https://github.com/evilmartians/lefthook/commit/352531cfac5a3ec4b00146a970c43beb706cfa6a, at least for yarn users. That commit is in the latest release (v0.8.0).
Thanks, @dannobytes !


test not set inbound alpn

Please provide a description of this PR:

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test all

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test release-notes_istio

unit-tests_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test release-notes_istio

unit-tests_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test unit-tests_istio

integ-helm_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test integ-helm_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test release-notes_istio

unit-tests_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test unit-tests_istio

integ-helm_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test integ-helm_istio

integ-operator-controller_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test integ-operator-controller_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test unit-tests_istio

integ-helm_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test integ-helm_istio

integ-operator-controller_istio
17e8828e997e3124997ca357d20ad08fd6a93a0d
link
true
/test integ-operator-controller_istio

release-notes_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test release-notes_istio

unit-tests_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test unit-tests_istio

integ-telemetry_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test integ-telemetry_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test release-notes_istio

unit-tests_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test unit-tests_istio

integ-telemetry_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test integ-telemetry-istiodremote_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test release-notes_istio

unit-tests_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test unit-tests_istio

integ-telemetry_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test integ-telemetry-istiodremote_istio

integ-telemetry-mc_istio
bf680660f50d5ea362f2fb5b733c120d34661a36
link
true
/test integ-telemetry-mc_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn From the failure it seems inbould listener downstream tls context alpnProtocol can be any value.
The only requirement is for TCP mx is it should include "istio-peer-exchange"
That's very weird.

I think envoy doesn't really do ALPN negotiation. But the MX filter explicitly looks for that ALPN

I guess you are right


Update group detail fixture

Reviewer: @philipnrmn

That one integration test keeps failing, but it's totally passing locally for me so :/


Fix general pipeline failrues

Update license year in app json (pipeline will update the other license years automatically when merge to main)
Fix semgrep tests

Static test failures:

Min Platform Version


Doesn't work with getters

Just making this issue to raise awareness for anybody searching.
Here is a PR with failing tests
https://github.com/NullVoxPopuli/ember-deep-tracked/pull/308

Fixed in #314 / v1.3.14

Thank you!


Kotlin version upgrade

Upgrade the version for Kotlin

Please check this PR and merge it for upgrading the Kotlin version.
Thanks.

sorry to bother, but did you had a look into this?

Hi @pradyotprksh!
Sorry for the delay.
Just published 0.4.0 with the update PR (and another commit upgrading Gradle too, because the old Gradle version was too old for Kotlin 1.8).
https://pub.dev/packages/installer_info/versions/0.4.0
Let me know if you encounter any issue with the update.
Thank you again for your contribution! :)

and another commit upgrading Gradle too, because the old Gradle version was too old for Kotlin 1.8 oh didn't saw this issue on my end but cool.
thanks will use the latest version 🙏


Restore all available versions of a file

i would like to restore all available versions (one per snapshot) of a file to easier find the version i'm looking for. i'm thinking of writing a bachelor-thesis where you snapshot your word-document every hour. and then you recognise you accidentally deleted a part sometime in the past. so i want to restore the word-doc from each snapshot to one target-directory with -<snapshotid/snapshottimestamp>.
i can implement that and make a pull-request, if you like

i really like the idea
some additional features for this (which can be added later):
-restore no duplicates (different modification time).
-target directory naming after snapshotid/snapshottimestamp/mtime/atime/ctime for easier search.
-this might be a bit overkill but maybe something like git bisect to find the relevant version of a file.

You can already do that by mounting the repo to a directory.

yeah, but if you have 5 versions/snapshots of a file you have to mount 5 different snapshots or have i missed something? i think in such a case it would be easier for users to be able to export all to one target-directory

Uhm, did you try this at all? You mount a repository, then all snapshots in that repository are available as subdirs below the mount point. You can then easily inspect or copy all revisions of the file you're searching for. That's even easier that restoring and then inspecting the files. In addition, the fuse mount will only load data on demand, so there's no overhead.
At the moment I think this use case is covered very well by the fuse mount, so I'm going to close this issue for now.

oh sorry, my mistake. i had in mind that you are only able to mount a single snapshot. so closing is totally ok!


Make large interests square title/link uppercase; fix template error

Per this card: https://trello.com/c/Fd8sx3sH/257-1-big-tile-in-interests-component-should-show-title-in-uppercase.
Also discovered that the card order # wasn't being added to the class because of an incorrect variable name. Wasn't affecting the component functionality, but I went ahead and made the fix.


Fix incremental build break

Description
This adds a targets file that our test projects import that fixes up our copy-local items from Microsoft.UI.Xaml.vcxproj.  That project reports the files from its $(IntDir), but those are deleted during IncrementalClean if they weren't built, leading to build breaks.  The targets file includes a target that repoints those files to Microsoft.UI.Xaml.vcxproj's $(OutDir) instead, which is where those files ultimately end up.
I'm not sure what changed here in VS 16.5 - either IncrementalClean changed to delete these files when it wasn't deleting them before, or the importing of copy-local items was changed.  I suspect this may be working around a bug in VS of some sort.  Either way, repointing the files that include the project to its $(OutDir) fixes the issue.
Motivation and Context
Fixes #2221
How Has This Been Tested?
Compiled the solution fully, then made a dummy change in Microsoft.UI.Xaml.vcxproj and built incrementally.  Verified both that the build only built the file that was changed and that there were no build errors in other projects.

/azp run


generate_c_source add #defines for signal names.

I am using the generate_c_source for a project I am writing and would find it useful to have #define's for the signal names.
Would this be a feature worth adding to the project? I am happy to look at raising a PR.
Thank you

PR: #548

Is there a plan to do a release soon?
Thank you

I'd like to keep the number of API breaking releases to a minimum. I thus would like to get #555 merged for before releasing version 39.0.0. @zariiii9003: do you have any objections to #555?

That makes sense, I am pulling master for the moment until this gets released.


Added BottomNavigationView to Product_Activity.

Added a bottom bar with the Barcode scanner FAB anchored to it.

Before any commit can be made, the floating action button would need to be positioned correctly so that it does not override the bottom navigation bar. However, before doing this, you may want to consult @teolemon as to whether or not this design is going to be consistent with the design of the other apps.

It's a duplicate of PR #746.

Hi @abhinavbajpai2012, this pull request seems to be a duplicate of PR #746, to keep the repo neat and tidy, we will close one of these requests. Which one are you currently still working on?

@Karljoones use the PR #746 , I am working on that one.

Closed duplicate

The floating action button was to be placed over the bottom bar as shown in the screenshot by @teolemon  in the issue #704


What needs to be done to get patch_namespaced_deployment to work?

I want to update the image for one of my containers in a deployment and it seems I can't provide an UnversionedPatch. Using a valid JSON patch string, or the strategic-merge string I use in kubectl ends up with variations of
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"json: cannot unmarshal string into Go value of type jsonpatch.Patch","code":500}
Am I doing something wrong or is this not implemented yet? The link to UnversionedPatch returns a 404 https://github.com/kubernetes-incubator/client-python/blob/master/kubernetes/docs/UnversionedPatch.md If it's not implemented I'd be happy to work on it.

Look like Patch is defined as this in kubernetes:
// Patch is provided to give a concrete name and type to the Kubernetes PATCH request body.
type Patch struct{}

That I hoped would result in an empty class in generated code, but it look like swagger-codegen ignores it (it exists in swagger.json). I guess we may need to implement it manually. If you want to work on it, that's great. Add the class to kubernetes/client/model but keep in mind that the folder will be removed and regenerated on each call to scripts/update-client.go so make sure you update the script to keep your file somewhere and restore it. We may need to have a general mechanism for this non-generated codes inside generated packages.

@mbohlool @rwillard - patch_namespaced_service and patch_namespaced_config_map have the same problem. I am adding functional tests against a real k8s instance in my PR here:
https://github.com/kubernetes-incubator/client-python/pull/94/commits/8fac5fe38d53ba86417b9f2b2417b2d1bc0c848f

@rwillard can you please confirm if you are working on this?

no problem. Thanks for letting us know.


Changing default tags.

Description

"Tags building yes"
I want to have a way to change the preset from building to house or whatever I need for that area. Examples: restroom, residential area, residential building, mobile home, mobile home park, ect.

Just a quick thought: Maybe the "Use This Feature" could be a split button that optionally lists the presets of the category "Buildings" from the tagging schema and remembers the last chosen category? It should be possible to pick a category based on the primary tag (building, highway, …).


evaluate API should work with async function.

As of now evaluate API does not work with async function.
Example:
const { openBrowser, goto, evaluate, closeBrowser } = require('taiko');
const assert = require('assert');
(async () => {
    try {
        await openBrowser();
        await goto('google.com');
        let {result} = await evaluate( async () => document.title );
        assert.equal(result, 'Google')

    } catch (error) {
        console.error(error);
    } finally {
        await closeBrowser();
    }
})();

Above script fails with
Error: undefined not found
    at elements (<path-to-npm-modules>/taiko/lib/elementSearch.js:116:15)

Whereas the below script works fine.
const { openBrowser, goto, evaluate, closeBrowser } = require('taiko');
const assert = require('assert');
(async () => {
    try {
        await openBrowser();
        await goto('google.com');
        let {result} = await evaluate( () => document.title );
        assert.equal(result, 'Google')

    } catch (error) {
        console.error(error);
    } finally {
        await closeBrowser();
    }
})();

This issue has been verified and found fixed.
Tested version: ae469d33798aec00b004bb7f2d5cd15d4516945e


Update

Please check if the PR fulfills these requirements:

[ ] The commit message follows our guidelines.
For bug fixes and features:

[ ] You tested the changes.
[ ] You updated the docs or changelog.

Related issue (if applicable): #

What kind of change does this PR introduce?
Does this PR introduce a breaking change?
New feature or change
What is the current behavior?
What is the new behavior?
Other information

Open RPG is getting a Godot 4 rewrite, closing because of this. See #209


Update to version 0.6.1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Change the format of CHANGE_NOTES to incremental (prepend-only), as in git-machete CLI

CLI has the release notes like https://github.com/VirtusLab/git-machete/blob/master/RELEASE_NOTES.md.
The old notes are never removed/replaced, the new ones are just prepended under version-specific section.
Let's do the same here, this will be much easier to maintain. Will require some extra parsing logic in build.gradle (currently it's just reading the CHANGE_NOTES.html file)

looks a bit like https://github.com/VirtusLab/git-machete-intellij-plugin/issues/897


Support 2.0.0 final to prevent minimum-stability: dev on production

Q
A

Bug?
no

New Feature?
no

Framework
Laravel

Framework version
5.6

Package version
2.0.0-alpha2

PHP version
5.x.y

Actual Behaviour
It's been a little bit over three years since the last "non-dev" version. This forces my team to have "minimum-stability": "dev" in my composer.json since this is the only package with the "@dev" suffix.
Expected Behaviour
Is there any plan to release v2 at some point, or it is going to happen like with version 1? I think it is time to release 2.0 finally, and add new releases with the bugfixes, since that is the version most users are using and most of the documentation does not reflect anymore versions 0.10.X.
Also, the current stable version 0.10.0 is not compatible with the supported versions of Laravel.
Steps to Reproduce
N/A
Possible Solutions
Release 2.0.0 version stable.

I think it's not ready for conservative "prod stability", however there's nothing preventing you from using this package in production - that's what I do.
Probably once all the issues are cleaned out and we address any outstanding ones, then it can be released?

Thank you for your reply.
I understand your statement. What is exactly what is missing in order to be prod-ready? Is there a milestone updated? If so, is there an estimation of contributions needed to achieve this stage?
It has been quite a number of years already without a pro-ready version, maybe there's something I could contribute to help also. Cheers.

I think we just need a good overview of the issues remaining, if there aren't any then let's tag 2.0.0 :+1:

I agree. Please, let me know how I or my team can contribute. I would be happy to contribute. Not sure if you use a Gitter chat or something else.

@specialtactics I have a question, maybe is lack of knowlegde in composer but: you say "however there's nothing preventing you from using this package in production - that's what I do". I want to do the same, but how to deal with the other packages, once you change the minumum stability with an update all packages change to dev. I trust dingo, but i can trust others? 😉
If you have suggestion i'll be glad to have a solution for this situation.
Thank you

@eppak That sounds like it would be a problem if you are using the dev-master reference of many projects - not just dingo. This should be the exception rather than the norm, and even then you can still specify specific commits.
That latter strategy is what I use, whenever I want to use a non tagged version of a package, I will specify the specific commit (which usually fixes or adds something pivotal), and make a note to go back to using the tag once it's tagged next, and check them every month or so.
Dingo is actually the only 3rd party package I use a master dev version of, and mostly because the package at the moment is being developed slower than would be ideal, but also because I am extremely familiar with it to the point of knowing every PR that goes into it - so if I ever need to pause and put it on a certain commit, I can do it immediately.
Actually at the moment I am using my own fork of the project because I have several PRs pending also.

@specialtactics It is exactly my case, i want to add to a more complex application rather than alone. I think that the "solution" can be a fork.
If can be safe to use it in production i think it can be switched, but you know it better than me.
Thank you for the response.

@eppak I think it's fine to use the current commit hash on master in production, and then just check back to see if it's been tagged.

Thank you for all the different solutions here proposed but, I can't avoid one more question then. If everyone agrees on the fact of master being of enough trust and safe enough to use in production, why is not tagged directly as version two?
«Bugfree» software does not exist, and if in 2.0.0 an issue is found, that's what 2.0.1 is meant for. What are your thoughts guys?

@GabrielGil I agree with this statement but i think is the a lead decision, what i can ask @specialtactics is to add the proposition of point directly to the commit as a workarond on documentation.

Completely agreed; it is a lead decision. Let's see what their thoughts are and if this makes sense for 'em too.

@specialtactics

I will aim to finish this by end of Feb
Hey, is this still the current schedule?

@specialtactics

I will aim to finish this by end of Feb

Hey, is this still the current schedule?

Yes, I will try and prioritise issues/PRs which I think are a blocker, but just from what I have seen so far, I don't think there is anything major (ie. that can't be resolved after 2.0.0 release). To that end, I might actually do it sooner.

Thank you, I am very glad to hear that!

v2 tagged, closing this issue.

Awesome! :)


Bug: Getting CORS error while loading tensorflow-models/pose-detection, tensorflow-models/face-detection from today

What happened?
Getting CORS error while loading tensorflow-models/pose-detection, tensorflow-models/face-detection from today
Access to fetch at 'https://www.kaggle.com/models/mediapipe/face-detection/frameworks/tfJs/variations/short/versions/1/model.json?tfjs-format=file&tfhub-redirect=true' (redirected from 'https://tfhub.dev/mediapipe/tfjs-model/face_detection/short/1/model.json?tfjs-format=file') from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Relevant code
/* eslint-disable react-hooks/exhaustive-deps */
"use client";

import * as poseDetection from "@tensorflow-models/pose-detection";
import * as tf from "@tensorflow/tfjs-core";
import * as THREE from "three";

import React, { useEffect, useRef, useState } from "react";
import Webcam from "react-webcam";
// Register one of the TF.js backends.
import "@tensorflow/tfjs-backend-webgl";

  const loadPoseNet = async () => {
    try {
      setLoading(true);
      await tf.ready();

      //movenet configurations start

      // const detectorConfig = {
      //   // modelType: poseDetection.movenet.modelType.MULTIPOSE_LIGHTNING,
      //   modelType: poseDetection.movenet.modelType.SINGLEPOSE_LIGHTNING,
      //   enableSmoothing: true,
      //   // minPoseScore: 0.6,
      //   multiPoseMaxDimension: 352,
      // };

      // const net = await poseDetection.createDetector(
      //   poseDetection.SupportedModels.MoveNet,
      //   detectorConfig
      // );

      //movenet configurations end

      // blazenet configurations start

      // const detectorConfig = {
      //   runtime: "tfjs",
      //   enableSmoothing: true,
      //   modelType: "full",
      // };
      const detectorConfig = {
        runtime: "tfjs",
        modelType: "lite",
        enableSmoothing: true,
        inputWidth: 256,
        inputHeight: 256,
        quantBytes: 2, // Set to 4 for int32 quantization
        architecture: "ResNet", // Use 'MobileNet' or 'ResNet'
        scoreThreshold: 0.5, // Minimum confidence score for detected keypoints
      };

      const net = await poseDetection.createDetector(
        poseDetection.SupportedModels.BlazePose,
        detectorConfig
      );

      //blazenet configurations end

      setNet(net);
      setLoading(false);
    } catch (error) {
      console.log("Error while loading model", error);
    }
  };

  useEffect(()=>{
    loadPoseNet
}, [])

  return (
    <>
      <div id="pose-detector" style={{ width: 480, height: 352 }}>
        <Webcam
          className="absolute mx-auto left-0 right-0"
          style={{ width: 480, height: 352 }}
          ref={webcamRef}
        />

        <canvas
          className="absolute mx-auto left-0 right-0"
          style={{ width: 480, height: 352 }}
          ref={canvasRef}
        />
      </div>

    </>
  );
};

export default VRPoseDetection;

Relevant log output
Access to fetch at 'https://www.kaggle.com/models/mediapipe/face-detection/frameworks/tfJs/variations/short/versions/1/model.json?tfjs-format=file&tfhub-redirect=true' (redirected from 'https://tfhub.dev/mediapipe/tfjs-model/face_detection/short/1/model.json?tfjs-format=file') from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
www.kaggle.com/models/mediapipe/face-detection/frameworks/tfJs/variations/short/versions/1/model.json?tfjs-format=file&tfhub-redirect=true:1

       Failed to load resource: net::ERR_FAILED
platform_browser.js:42

       Uncaught (in promise) TypeError: Failed to fetch
    at HTTPRequest.fetch (platform_browser.js:42:16)
    at HTTPRequest.loadModelJSON (http.js:108:47)
    at HTTPRequest.load (http.js:157:38)
    at GraphModel.load (graph_model.js:129:41)
    at loadGraphModel (graph_model.js:554:17)
    at eval (face-detection.esm.js:28:21649)
    at eval (face-detection.esm.js:28:1453)
    at Object.eval [as next] (face-detection.esm.js:28:1558)
    at eval (face-detection.esm.js:28:495)
    at new Promise (<anonymous>)
    at T (face-detection.esm.js:28:240)
    at ee (face-detection.esm.js:28:21014)
    at Module.eval (face-detection.esm.js:28:21933)
    at eval (face-detection.esm.js:28:1453)
    at Object.eval [as next] (face-detection.esm.js:28:1558)
    at eval (face-detection.esm.js:28:495)
    at new Promise (<anonymous>)
    at T (face-detection.esm.js:28:240)
    at Module.te (face-detection.esm.js:28:21777)
    at loadFaceDetectionModel (index.jsx:36:30)
localhost/:1 Access to fetch at 'https://www.kaggle.com/models/mediapipe/face-detection/frameworks/tfJs/variations/short/versions/1/model.json?tfjs-format=file&tfhub-redirect=true' (redirected from 'https://tfhub.dev/mediapipe/tfjs-model/face_detection/short/1/model.json?tfjs-format=file') from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
www.kaggle.com/models/mediapipe/face-detection/frameworks/tfJs/variations/short/versions/1/model.json?tfjs-format=file&tfhub-redirect=true:1

       Failed to load resource: net::ERR_FAILED
platform_browser.js:42

       Uncaught (in promise) TypeError: Failed to fetch
    at HTTPRequest.fetch (platform_browser.js:42:16)
    at HTTPRequest.loadModelJSON (http.js:108:47)
    at HTTPRequest.load (http.js:157:38)
    at GraphModel.load (graph_model.js:129:41)
    at loadGraphModel (graph_model.js:554:17)
    at eval (face-detection.esm.js:28:21649)
    at eval (face-detection.esm.js:28:1453)
    at Object.eval [as next] (face-detection.esm.js:28:1558)
    at eval (face-detection.esm.js:28:495)
    at new Promise (<anonymous>)
    at T (face-detection.esm.js:28:240)
    at ee (face-detection.esm.js:28:21014)
    at Module.eval (face-detection.esm.js:28:21933)
    at eval (face-detection.esm.js:28:1453)
    at Object.eval [as next] (face-detection.esm.js:28:1558)
    at eval (face-detection.esm.js:28:495)
    at new Promise (<anonymous>)
    at T (face-detection.esm.js:28:240)
    at Module.te (face-detection.esm.js:28:21777)
    at loadFaceDetectionModel (index.jsx:36:30)

tensorflow_hub Version
0.12.0 (latest stable release)
TensorFlow Version
2.8 (latest stable release)
Other libraries
No response
Python Version
3.x
OS
Linux

I have also been facing the CORS error for the Blazeface model since this morning. I found a related bug report  from a while ago, which is now closed. Is this also an intermittent issue or are any code updates expected from our end?
**Browser console log **
Access to fetch at 'https://www.kaggle.com/models/tensorflow/blazeface/frameworks/tfJs/variations/default/versions/1/model.json?tfjs-format=file&tfhub-redirect=true' (redirected from 'https://tfhub.dev/tensorflow/tfjs-model/blazeface/1/default/1/model.json?tfjs-format=file') from origin xxxxxxxxxxxxxxxxxxxxxxx has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Hi all, we're looking into this issue. Thanks for your patience.

Hi all. We rolled out a fix. But please keep up posted if you see this again.
More info here: https://github.com/tensorflow/hub/issues/908#issuecomment-2046026055
Thanks!

Thanks @KeijiBranshi, the issue is now resolved.

Hi,
Looks like the issue is there again:
Access to fetch at 'https://www.kaggle.com/models/mediapipe/blazepose-3d/tfJs/landmark-full/2/model.json?tfjs-format=file&tfhub-redirect=true' (redirected from 'https://tfhub.dev/mediapipe/tfjs-model/blazepose_3d/landmark/full/2/model.json?tfjs-format=file') from origin 'https://localhost:5175' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.


Improvements to leaderboard UX

Is your feature request related to a problem? Please describe.

A feature similar to what's already implemented in the economy system. Display usernames in the leaderboard not in a non-mentioned format.
This issue also is to be used to address smaller optimizations to the leaderboard subclasses. Having a refresh button on a single row it's own in the stat leaderboard view is not a great look.

Describe the solution you'd like

Create a helper function which does what the economy system leaderboard function already does to populate the data structure. This will most likely be created inside the helper file within the core subdirectory.
Add additional functionality to the stat leaderboard which can be added in the form of another button on the row it's aligned with. Alternatively, the refresh button is simply removed.

Is to be rewritten using PIL


METRON-2251: Update with the latest master branch

Contributor Comments
This change merges the latest from master into the feature/METRON-1856-parser-aggregation feature branch.
Because of the age of this branch, this merge with master resulted in some merge conflicts. In addition, both UIs have major version updates to dependencies like Angular and Typescript. As a result, I had to update a few areas of the parser aggregation code to accommodate for stricter type checking.
This PR will show all of the commits from master that are being merged into the feature branch, followed by a merge commit. After the merge commit, there are 2 commits. One is to apply an object property to a class that had been refactored in our parser aggregation work, and the other commit is to fix type errors resulting from stricter type checking.
Testing
The easiest way to do this is by building full dev from scratch, but another faster way is to navigate to the Management UI directory under metron-interface/metron-config, run the unit tests by running ng test and run  ng build --prod to ensure that the build passes.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[ ] n/a ~Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:~
cd site-book
mvn site

[ ] n/a ~Have you ensured that any documentation diagrams have been updated, along with their source files, using draw.io? See Metron Development Guidelines for instructions.~

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

I looked at the diff as follows - https://github.com/apache/metron/pull/1507/files/24f3b7198a18a89763d64b6b535f51a5235b7e78..908a26f5da80563acb271424d28736214867dfff
This isolated 4 commits with pertinent changes made in this merge PR.
@sardell The only question I have is regarding the commented out tests.

Ok, go for it +1. Thanks @sardell


correct filename for retagging

Signed-off-by: Tiger Kaovilai<EMAIL_ADDRESS>

yep that was it.


[error] Function.CommitFailedError Error: Failed to create and push commit

I'm getting the following error when I renamed a folder and tried to click Commit & Push
[error] Function.CommitFailedError
Error: Failed to create and push commit

for example there's a folder named components and I renamed it to Compoenent it shows something like this.

then when click Commit & Push I got the error.

Also it would be better if we can use your cool extention and delpoy in localhost at the same time somehow.

@OmarAfet I cannot repro this, can you please share the logs from the Remote Repositories output channel?

@joyceerhl
The uploaded file contains the logs from Remote Repositories, Here's what I did:

Click src folder
Click components folder
Rename components folder to Components
Click Commit & Push with test commit message.

Remote Repositories.log


Using bail: true makes watch process terminate

bail
Report the first error as a hard error instead of tolerating it.

Using bail: true closes the watch process if there is an error. I would expect a watcher to continue watching if there is a problem otherwise it is very inconvenient if you are trying to remove several errors and have to restart the watcher every time.
I would use bail: false in cozy-scripts/scripts/watch.js

Will be done in #137

#137 merged


ERROR:display_layout.cc

Be sure to check the existing issues (both open and closed!), and make sure you are running the latest version of Pipenv.
Check the diagnose documentation for common issues before posting! We may close your issue if it is very similar to one of them. Please be considerate, or be on your way.
Make sure to mention your debugging experience if the documented solution failed.
Issue description
I am trying to execute a script with python -m pipenv run main.py  but it is throwing a display_layout.cc error.
I can't find a solution to this problem anywhere online.
Expected result
The program to execute without throwing any errors.
Actual result
Console output after executing the command: [9464:0203/141858.364:ERROR:display_layout.cc(562)] PlacementList must be sorted by first 8 bits of display_id
The script's contents:
print('Hello, World!')

Pipfile contents:
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]

[dev-packages]

[requires]
python_version = "3.10"

Locations:
Pipenv version: `'2021.11.23'`

Pipenv location: `'C:\\Users\\grantwforsythe\\AppData\\Local\\Programs\\Python\\Python310\\lib\\site-packages\\pipenv'`

Python location: `'C:\\Users\\grantwforsythe\\AppData\\Local\\Programs\\Python\\Python310\\python.exe'`

Steps to replicate
I am unsure of how to replicate the issue since I assume this is a problem with my system.

Please run $ pipenv --support, and paste the results here. Don't put backticks (`) around it! The output already contains Markdown formatting.
If you're on macOS, run the following:
$ pipenv --support | pbcopy

If you're on Windows, run the following:
> pipenv --support | clip

If you're on Linux, run the following:
$ pipenv --support | xclip

Are you using Windows? If so, which terminal are using?

Yes, I am, Windows 10 Pro v10.0.19044 and I currently using the Powershell Integrated Console v2021.12.0 in VS Code.

Can you please see if this problem occurs on the normal cmd.exe? Unfortunately, I don't use Windows and I can't help much here. It seems like there is an issue with the console. Also, I am guessing that your script is invoking some browser? Seems related to chrome?

@grantwforsythe I think the issue is the command you are running, it doesn't work on git shell either and tries to open a new window.   Specifically this: python -m pipenv run main.py
pipenv should be used to run python, not the other way around, so like: pipenv run python main.py worked for me:
$ pipenv run python main.py
Hello, World!

Hi, @matteius
Your comment was a solution to my problem.
Thanks, @oz123, for your help as well.


Allow an underlying list that is not based on VirtualizedList

Is your feature request related to a problem? Please describe.
I have a page that needs to scroll.  Inside it I have a list that does not need to scroll.  As far as I know, there's no way to get the FlatList not to render as a VirtualizedList.
Describe the solution you'd like
I'd like to have a prop that let me indicate to the DraggableFlatList that I'd like to render some other parent component . . . probably just a View.
Describe alternatives you've considered
I looked for a property that would allow me to indicate to the FlatList that all elements should be fully rendered and that the full list should be displayed at all times and thus it should not scroll and the external ScrollView should have priority.
Others recommend using the FlatList with the header and footer properties specified, but the result is still a scrollable list . . . which I'd like not to have.
Additional context
Thanks a lot for this library; it's super helpful and looks great.  :)

Have you figured out a workaround? I have a nested draggable flatlist and can't scroll the main view when my touch is over a nested item.

There was a similar issue I believe which was closed without a 'real' solution: https://github.com/computerjazz/react-native-draggable-flatlist/pull/288
It should not be too hard to create a PR for this 😉

a non-flatlist version of react-native-draggable-flatlist is not in scope for this package, as it has been created around the flatlist api.


877 occupancy type bug content value uncertainty entry isnt functioning properly

This stuff is kind of a mess. Need to design a decent test to prove this works. I'm still not convinced.

I think that the common occ type build is happening here:
https://github.com/HydrologicEngineeringCenter/HEC-FDA/blob/39956194ccbd708986e79571cfe9a8f8e724ecb1/HEC.FDA.ViewModel/Inventory/InventoryElement.cs#L305
so we either need a way to build an occupancy type in a way that matches the scope of the user input data or revise our strategy for identifying whether to compute damage for a given asset type.

When I click in to edit the occupancy types being used in a given stage-damage compute, I find that the selection for "By Content Value" and "By Content-To-Structure Value Ratio" has not been saved.
When I make the correct selection, save the edits to the occ type, and recompute stage-damage, the correct selection fails to show up in the model.

I definitely introduced that visual bug where neither radio button is selected. I will fix that first. We should chat about the remaining disagreement between view and model though. I'm not sure I'm seeing that on my end.

ok. There's a lot of kreft cleanup going on in this PR. The only thing that really matters is the CreateModelOcctype method. That's where we're converting from vm to model world.
I think I've proven throught he UI this works., double check me. n


Improve BIGNUM operations

Amortize calls to modexp precompile by ~5%.

@hratoanina I'll let you judge if you wanna do another pass for the last commit after your review that touches a bit everything due to the new convenience macro, otherwise if it looks good to you I'll merge it


Insight overview chart

Related Issue:  open-cluster-management/backlog#12304
Description of changes

Added donut chart for insights
changed the order of other donut legends to be worst -> best

/lgtm


format all files instead of opened one?

Is it possible to hit one key and have all files under the same project folder be formatted? Thanks.

Hi Jeremy,
Thanks for contributing. This would likely be a one-time use feature. I'm
torn between building that and just deferring users to running jscs autofix
on the directory via the terminal.
What do you think?
On Jun 9, 2015 4:35 AM, "Jeremy Lu"<EMAIL_ADDRESS>wrote:

Is it possible to hit one key and have all files under the same project
folder be formatted? Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/TheSavior/SublimeJSCSFormatter/issues/34.

Ah, I didn't notice there's this -x option in jscs to format files while linting, of course it makes more sense to do that via CLI then, thanks for the heads-up!


System.Text.Json.Serialization.JsonIgnoreAttribute not working in  asp.net Core 3.1 partial ModelMetadataType class

Describe the bug
The System.Text.Json.Serialization.JsonIgnoreAttribute not working as expected in partial class's
ModeMetaDataType class at ASP․NET Core 3.1.
To Reproduce

Setup demo project

git clone https://github.com/rocfatcat/JsonIgnoreTest.git
cd JsonIgnoreTest
dotnet run

Send HTTP GET request to the demo action

curl http://localhost:5000/api/Department

It return 500 status code and web application throw follow log message.
I expected api will return department data without instructor and course json data.

System.Text.Json.JsonException: A possible object cycle was detected which is not supported. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 32.

For compare System.Text.Json.Serialization.JsonIgnoreAttribute and Newtonsoft.Json.JsonIgnoreAttribue result, i put Newtonsoft.Json example in Newtonsoft.Json_Test branch in the same git repository.
Here is the code snippet of the demo code:
Department.cs Content
    public partial class Department
    {
        public Department()
        {
            Course = new HashSet<Course>();
        }

        public int DepartmentId { get; set; }
        public string Name { get; set; }
        public decimal Budget { get; set; }
        public DateTime StartDate { get; set; }
        public int? InstructorId { get; set; }
        public byte[] RowVersion { get; set; }

        public virtual Person Instructor { get; set; }
        public virtual ICollection<Course> Course { get; set; }
    }

Department.Partial.cs
using System.Text.Json.Serialization;
using Microsoft.AspNetCore.Mvc;

...
    [ModelMetadataType(typeof(DepartmentModelMetadataType))]
    public partial class Department
    {
        ...
    }

    public partial class DepartmentModelMetadataType
    {
        [JsonIgnore]
        public virtual Person Instructor { get; set; }
        [JsonIgnore]
        public virtual ICollection<Course> Course { get; set; }
    }

Further technical details

ASP.NET Core version: 3.1
Include the output of dotnet --info: See below
The IDE (VS / VS Code/ VS4Mac) you're running on, and it's version: VSCode 1.39.2

.NET Core SDK (reflecting any global.json):
 Version:   3.0.101
 Commit:    bc5f8df0f5

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.101\

Host (useful for support):
  Version: 3.1.0
  Commit:  65f04fb6db

.NET Core SDKs installed:
  2.1.802 [C:\Program Files\dotnet\sdk]
  3.0.101 [C:\Program Files\dotnet\sdk]
  3.1.100 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Thanks for contacting us. This looks like an issue on the CoreFx side. @pranavkm can you please look into this to confrim and move over, if so? Thanks!

@rocfatcat ModelMetadataType and other model binding specific types are used by MVC's model binding system. Models bound by deserializing the response body containing JSON or XML data are unaware of these types which would explain why you see this error. You would have to specify the JSON attributes on the model being bound.


Wait for fork to exit and then return results

Improves #134.
// @jamestalmage

That should do it.
Once you merge this, I will merge master back into #135 and it should pass.


User/pagoe/getstartedupdate (#719)

fixed Visual Studio prereq to 2017, added Next Steps

updated api reference link

removed unneccesary .

updated broken links

fixed WPF link

Docs Build status updates of commit c95d570:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/webview2/gettingstarted/wpf.md
:warning:Warning

Details

microsoft-edge/webview2/gettingstarted/win32.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/winforms.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md

Line 332: [Warning-file-not-found] Invalid file link: '../reference/wpf/0-9-515/microsoft-web-webview2-wpf-webview2'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Low Level OAT Operation Tests

We need individual tests for the custom OAT operations flow - each operation as, the rule construction process and them combined with conditionals.

Fixed in 1.5.


FileNotFoundError: [WinError 2] The system cannot find the file specified

Having some issues when trying to start a new project.

It seems like you don't have poetry installed. Please install it and add it to your PATH.

You can follow this instructions to install it.
https://python-poetry.org/docs/#installation
Sorry for late reply, I couldn't find time.

Closed due to inactivity.


Batch: "del" command being used with spaces in a folder name of a directory

Hello, this is a question regarding Batch.
How do we delete (del) a file using a directory containing spaces?
What I mean is that if I have written (for example):
del C:\an example\folder\file.txt
But then the computer will think it has to delete:
C:\an
example\folder\file.txt
How will we let the computer know about the spaces in a folder name of a directory?

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

ID: e809f83e-26b1-52b5-a663-e2d3705e7cdc
Version Independent ID: b968d3d3-1ba0-65a8-524e-3c5e4118209f
Content: del
Content Source: WindowsServerDocs/administration/windows-commands/del.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

#assign:xelu86

Thanks again for contacting Microsoft. We've submitted a documentation change based on your suggestion. Changes will be live after the next business day.
To delete a file or all files in a folder where the folder has a space in its name, the full path needs to be wrapped in double quotes.
Per your example: del "C:\an example\folder\file.txt"


Collection "@nativescript/schematics" cannot be resolved. (when run "ng g c component-name")

Describe the bug
Hi guys!
I removed the old version of nativescript and @nativescript/schematics that was installed
and I installed the last nativescript (6.8.0) and last @nativescript/schematics (10.0.1)
I geneted a new project (shared) using schematic, but when I try to generate a new component or module I get the error "An unhandled exception occurred: Collection "@nativescript/schematics" cannot be resolved".
I had to run "npm install -D @nativescript/schematics" to fix the problem.
Is this normal?
To Reproduce
npm i -g<EMAIL_ADDRESS>npm i -g<EMAIL_ADDRESS>ng new --collection=@nativescript/schematics test-my-shared-app --shared
cd test-my-shared-app
ng g c testpage
(An unhandled exception occurred: Collection "@nativescript/schematics" cannot be resolved.)
Expected behavior
Generate a new component called "testpage" without error.

The same problems with ng g c and ng g m. Any solutions?

I have the same problem, but not only with component. If try to generate a service, it produce the same error message for me.

This error also occurs with the NativeScript 7 and schematics 10.2.0.
You can eliminate the error message by installing the package yourself.

npm install @nativescript/schematics

However, after installing the package, running ng g c new-component again now gives me

Option "entryComponent" is deprecated: Since version 9.0.0 with Ivy, entryComponents is no longer necessary.
Cannot read property 'kind' of undefined

I found the solution here for the last error : https://github.com/NativeScript/NativeScript/issues/8994#issuecomment-719948878
Option "entryComponent" is deprecated: Since version 9.0.0 with Ivy, entryComponents is no longer necessary.
Cannot read property 'kind' of undefined

I can now create new component.

is there a fix for this?

is there a fix for this?

alguna solucion???

alguna solucion???

Check if you have node_modules there. If yes, and it shouldn't be there, rm -rf node_modules.

Uninstall  @angular/cli, @schematics/angular and @nativescript/schematics from project dependency
Reinstall them as DEV Dependency
@schematics/angular should be at 9.1.0
After that uninstall and reinstall tslint
Also use --skip-import

Uninstall  @angular/cli, @schematics/angular and @nativescript/schematics from project dependency
Reinstall them as DEV Dependency
@schematics/angular should be at 9.1.0
After that uninstall and reinstall tslint
Also use --skip-import

Can you be more specific?


not working for me

I am having issues:
Packages/SublimeLinter/lint/queue.py", line 57, in loop
    item = self.q.get(block=True, timeout=self.MIN_DELAY)
  File "./python3.3/queue.py", line 175, in get
queue.Empty

and theres a lot more of that....
I cannot get this working with php lint.

What does your SublimeLinter.sublime-settings file look like?

I deleted my user settings for sublime linter 3 and it fixed everything!

Awesome, Thank you for using SublimeLinter!


Add link to YARN docs

Adds a link to dask-yarn documentation. The link shows up in the sidebar as well, keeping a uniform feel to the page. Fixes #3713.

Ping @mrocklin for quick review. I'd prefer to do this over creating a setup/yarn.rst page, as that means we have two sets of docs to keep up to date.

In general this looks good to me.  Thoughts on replacing "YARN" with "YARN / Hadoop" ?

I'm not sure if that's true for users who use YARN (you can't deploy on YARN without seeing the word YARN everywhere, or using the yarn cli tool), but I've made the change.

I agree that experts who know that they want to use YARN will be fine
regardless.  Mostly I'm thinking about the user that has access to a
standard Hadoop-y installation at their workplace, is curious about Dask,
and wants to try it out.  My guess is that this kind of person will need
help from someone at their institution, but at least this will point them
in the right direction.
On Wed, Aug 1, 2018 at 3:43 PM, Jim Crist<EMAIL_ADDRESS>wrote:

I'm not sure if that's true for users who use YARN (you can't deploy on
YARN without seeing the word YARN everywhere, or using the yarn cli
tool), but I've made the change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/3838#issuecomment-409748983, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszKL4lRNmXlg8QVZkJfDB2vqRsQSUks5uMi8HgaJpZM4VrRdN
.


V1.3: Add DG for Model package

Add basic documentation for the Model API, and its relevant classes.
Also, add the UML diagrams to better explain the code structure.
TODO: Add UML diagrams
Closes:  #120

Please help review the class diagrams here: Fork Deployment
Feel free to leave comments if necessary


Change cell toolbar button order

Apologies if this is a dupe. New to this project.
I think the switchCellType button on the Jupyter Notebook interface should be the first button (before runCell). This button persists for both Markdown and Code cells, so putting it first would prevent it from "moving" when you click it. Maybe this was a deliberate design decision, but it feels a little broken to me.
Here's what I'm suggesting:

The Markdown cell wouldn't look any different.

The Code cell would look like this:

Thanks for filing this issue, we'll review the design request in our triage meeting.

@jakekara Have you had a chance to try our new native notebooks experience? Has a different way of changing between code and markdown cells, would love to hear your feedback on that and the new design/functionality!
Instructions on how to try can be found here: https://devblogs.microsoft.com/python/notebooks-are-getting-revamped/
If you choose to leave feedback you can fill out the <5 min survey that pops up or email me at<EMAIL_ADDRESS>


adjustment extraction properties

🛠 Changes
adjustment extraction properties from the collection and adjustment in burned categories
📝 Associated issues
Asignar colores y categorías a partir de los datos en el stac

I'm having some issues with the frontend because the names of the data attributes used to build the graph have changed. Since we now return the classes that come from the STAC, I suggest keeping the same classes as before, taking into account that the frontend expects these attributes: perdida persistencia no_bosque.

I have already adjusted the metadata of the stac categories


docs: Improve WSL2 instructions to explain how to open WSL2 location from vscode on Windows

The Issue
I added an important step on how to launch VS Code in WSL2. I didn't know about this, I launched it in Windows and couldn't figure out why certain things weren't working correctly. I am using PHP, Intelephense was wreck and spent hours trying different things.

I tested here and this is actually not correct. I opened a little-used vscode and updated it.  When I opened a project in \WSL$\Ubuntu\home\rfay\workspace\d10 it prompted me with something like "Are you using WSL? You need to install the WSL support". I did that.  This is explained in https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl
I certainly agree that WSL2 adds complexity (and value) to everything, and also agree that using code . is the fastest way to get going because it makes these things happen right away. Maybe you can add a commit to tone this down and make it more accurate? Happy to continue the conversation here or in Discord.

No response from OP, closing. I'm certainly open to adding more about this situation, but I don't think it belongs where this landed, and this one is not correct.

Sorry for not getting back. I revisited ddev again to give it another try. I believe this is a valid PR, I tested it again.

There may be a bit more finesse involved here, since these instructions are for all platforms.

This PR is specifically for WSL2, the instruction is after line 90 !!!tip "If you’re using VS Code on Windows with WSL2"

In my opinion code . in WSL2 is the normal way to launch vscode. But you can also open \wsl$\Ubuntu\home... and it should work fine.

The above should be documented somewhere but I couldn't find it. That is what this PR is about.

I tested here and this is actually not correct.

To clarify, for novices not familiar with WSL2 like myself, I always launch VSCode from windows (the incorrect method ), it would launch OK, but Intelephense would be broken.

This PR can potentially saves hours for novices trying to figure out why certain things don't work.

I tested with the open-from-vscode method (with the wsl2 extension loaded) and it was fine.
Please, when people take the time to look at your issue/PR, you can at a minimum respond in a reasonable timeframe.
You're welcome to take another look, and fine-tune your recommendation with a new PR.


Using NSAttributedString for messages, add to JSQMessageData protocol

Hi,
Great job on the library. Do you guys think about adding an attributedText property to the JSQMessageData protocol, overriding the text property if not nil ?
This PR looks particularly interesting, I don't know if you changed your mind: https://github.com/jessesquires/JSQMessagesViewController/pull/125
You can use it for images or simple text formatting.
Thanks

I'd also like to request this feature. Also, if you are replacing methods, I'd like to suggest changing some of the method names on this protocol. It's hard to adopt the protocol on existing model objects without clobbering implementations. "text" is a pretty common method similar to "description" on NSObject. "isMediaMessage" is another one that I can see someone using the wrong way should they find it interfaced on my model object.

Good attempt at this here: #1059. We can use this as a reference when implementing in 8.0

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


[SCB-824] Fix the bug that demos cannot be built: add docker plugin activation tag for demos

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
The demos cannot be built since the essential docker images are not built without docker plugin activation being specified
[x] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.
Not a large PR

Coverage increased (+0.4%) to 94.297% when pulling 787f00690aa05fcb682af008a1913a5e3c4c622c on crystaldust:fix/docker-plugin-activation into dcf9f2a28e062baacd96f22f80f08e40b485fc51 on apache:master.


Fix sizing issues with TwoColumnsLayout and Filters

Release Type: bug fix
Fixes https://x-team-internal.atlassian.net/browse/XP-2845
Description
This PR fixes some remaining issues with TwoColumnsLayout and Filters sizings.
Checklist

[x] set yourself as an assignee
[x] set appropriate labels for a PR (In Review or In Progress depending on its status)
[x] move respective JIRA issue to the IN REVIEW column
[x] make sure your code lints (npm run lint)
[x] Flow typechecks passed (npm run flow)
[x] Snapshots tests passed (npm run jest)
[x] component's documentation (.stories.js file) is changed or added accordingly to reflect any new or updated use cases or variants usage
[x] if you've fixed a bug, make sure to also include a new story that will expose declarations with problematic data that caused the bug in the first place, so that we can assure that no regressions will pop up on future interactions
[x] if any snapshots have been changed, verify that component still works and looks as expected and update the changed snapshot
[x] manually tested the app by running it in several different browsers (Firefox, Chrome, Opera, Safari, MS IE/Edge, etc.) and checked nothing is broken and operates as expected!

Steps to Test or Reproduce

run npm start
go to http://localhost:9001/?selectedKind=UI Components%2FTwoColumnsLayout%2FUse cases&selectedStory=composed in AdminScreen with Filters
resize the screen

observe that the sidebar width are proportional to the screen width with value 30vw
observe how the sidebar adjusts to a maximum width of 385px
observe how the sidebar adjusts to a minimum width of 285px

Impacted Areas in Application

Filters/Filter.js
Filters/Filters.stories.js
Filters/Group.js
Filters/Heading.js
Filters/Label.js
Filters/TabButton.js
Filters/TabHeads.js
TwoColumnsLayout.js
TwoColumnsLayout.stories.js

Screenshots

@bernardodiasc Please reopen this PR, it seems to be closed for some reasons.

I've based this branch pointing to develop, it was closed because XP-2711-advanced-search-sprint-2 no longer exist. I'll reopen and add label on hold until we get the ticket in sprint.

Thanks for the review @galileo, I'll take the time to rebase once the ticket enters in the sprint, so that I spare from rebasing multiple times until that happen :)

I rebased this branch with latest develop and removed the on hold label. This should be ready to be reviewed now.

@bernardodiasc Another UI regression I just found. We seem to affect List view with these changes and we didn't mean to do that. Only Advanced Search page was meant to be adjusted. The List UI on smaller screens now looks messy and kinda unusable in terms of readability. Instead of tweaking that, we should aim at impacting only AS.

@nicksp, based on your feedback, looks like we can't have a fluid and smaller width for the left column.  I'll revert changes related to that.

@nicksp I reverted the flexible width of the sidebar, during my tests the minimum width that fits well is just 40px less than the default, I'm not sure if that's an improvement after all. I believe the solution to have more space for the content is more on the collapsing effect direction. This PR contain many other fixes for the sidebar filters layout and improvements in the stories. Please let me know any concern.

@bernardodiasc Tests on Travis and locally failing. Please take a look

@bernardodiasc Please also specify whether the ticket has breaking changes or not. Can't see it was set.

Good catch, I forgot to revert that. I should be good now.


Add fetching of provisioned machine's IP

This module adds the support for fetching the provisioned machine's IP from MrP to then feed it to wait_for_connection. Thus, the initial role is executed with "hosts: localhost".
The user used by wait_for_connection must be in the ansible_user option of the host definition, and that is done in the last task of provision.yml and set by machine_user (or root by default).
Please ensure that the preseed you fetch to the machine has the necessary keys, else wait_for_connection will fail. (but you can modify that preseed now so it shouldn't be a problem !)

@BaptisteGerondeau I use --connection-type=local or --connection=local and that makes the trick for me, Could you point your use case to exemplify?

@danrue, I agree backwards compatibility is an issue and we should re-implement it in a more flexible way. However, I don't think we should have a "main" way of doing it which is what one group does, and "other" ways of doing it for other groups.
There are a number of hacks that we had to implement to work around MrP's shortcomings, and I'm sure you guys had to create more than we did. However, as time evolves, I think all groups that use it should converge into a small set of methods.
Hard-coding machine names in /etc/hosts is ugly and honestly, I don't think we should encourage it. However, using DNSmasq could give IPs as well as name resolution, which would work more or less like a hosts file.
I cannot in good conscience recommend Baptiste to implement in the exact hacky way it's there already because it doesn't make sense, so I'd like us all to revisit this and try to move towards the best implementation possible. MrP gives us the IP of the machine and a sensible naming of interfaces gives us the rest, so I think we should try to use that.
Also, I don't want us to have a separate repo to do exactly the same thing just because we implemented in a time where MrP had a bit more features.

@rengolin - I agree that this PR could be acceptable if it were more flexible. I tried to suggest some approaches that would satisfy that.
A few points of clarification. I don't recommend /etc/hosts either. When I spoke about hosts, I was referring to ansible's notion of a hosts file. Ansible can do inventory a few ways - a static host file (version controlled along side your playbook), or dynamically using a script (not a role). It does not, however, have good support or even any examples that i've seen that support using a role as an inventory source. See http://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html for an overview of how ansible deals with inventory. If there are examples of this usage in the ansible community, please point them out as I'd be interested in reviewing it.
Ansible roles are designed to run against a host that is defined in ansible's inventory (via a hosts file or dynamic inventory script). Using a role to populate the inventory is possible, but unusual. That's the basis for my objection.
This method of running (using localhost and the role as a dynamic inventory source) is possible, and if there is agreement to do it we can do it as a backward incompatible change (bump the major version number of the role). We could also implement it as a role option, but then that adds to cognitive overhead. Since this role does not have local tests, I am concerned about maintenance over time as it grows in complexity. (due to the recent interest in this role, I'm thinking about adding tests).

I am inclined to agree with @danrue concerning the dynamic inventory script : much cleaner and to the point (and Ansible-y).
There is an example of using the add_host module in the AWS tutorial to do about the same thing (i.e. provisioning and then setting up stuff on the provisioned machine).
However, my biggest problem with the dynamic inventory script is how to tell it which interface to use.
From ansible-playbook you cannot pass any arguments to that script, and since this might be a different name per machine (and multiple interfaces per machine) assumptions might not cut it.
So this either needs a flag in MrP (e.g. 'Main interface') or a standardized (re)naming of the interfaces in MrP to then make use of a config file (e.g. 'main_interface=eth0').
We could even imagine trying to ping each of the interfaces to see which one is reachable, but that might entitle an SSH tunnel if the machine's network is not accessible directly to the machine (laptop) on which the Ansible is called.
In the meantime I can add a boolean (e.g. mr_provisioner_get_ip) to the 'wait_for_connection' in the interface (i.e. main.yml) to make it backward compatible.
It is not my desire to break things or increase the amount of maintenance needed for this role, but to have a standardized Ansible interface to MrP as @rengolin pointed out.

OK I gave this a try today and I ran into a few issues while trying to use it. Sorry for not putting these comments inline, but I thought this might be easier this time.

Please use spaces instead of tabs in README to be consistent with the rest of the file.
You don't need 'machine_user' variable; this should be done with ansible inventory and group vars instead.
You also don't need mr_provisioner_get_ip, actually. You can just make the conditionals based on whether or not mr_provisioner_machine_name is set.
It may be easier to put the 'Get IP of provisioned machine' and 'Add provisioned machine to host' to a separate task file, and then include that task file conditionally from main.yml so that you only have to check the condition once. For example, something like this:

- include: provision.yml
  when: mr_provisioner_do_provision
  delegate_to: localhost

- include: add_host.yml
  when: mr_provisioner_machine_name != False

- name: Wait for host for 3600 seconds, but only start checking after 60 seconds
  wait_for_connection:
    delay: 60
    timeout: 3600
  when: mr_provisioner_do_provision and not mr_provisioner_machine_name

Line 59 in provision.yml ('kernel_options: "{{ mr_provisioner_kernel_options|default('') }}"') produces an ansible error because it is a duplicate of line 57.
mr_provisioner_interface_name needs to be added to README.
add_host is using hard coded inventory group name 'target' which I don't think is very descriptive. What about something like 'mr_provisioner_hosts'?

Note that the reason all the variables are prepended with mr_provisioner is because, sadly, all vars in ansible are global (I guess they did not learn from history), and so generically named things can easily cause conflict or unexpected behavior when a playbook is using multiple roles.
All that is rather minor, but there is one larger issue too. Support for multiple hosts: the ec2 playbook you mentioned gets around it with an 'exact_count' variable that lets you specify how many hosts to spin up. It seems that we may need a fancier data structure to support multiple hosts (and being able to set i.e. mr_provisioner_interface_name for each one). You could do it as a list of dictionaries.. i.e.
ansible_provisioner_machines:
  - hostname: j12-m1-c34n1
    interface_name: eth0
  - hostname: j12-m1-c35n1
    interface_name: eth1

Then main.yml needs to implement a loop for each of those machines.
I implemented some of the above suggestions here as I was working through them, which you may use as reference or as a cherry-pick directly https://github.com/danrue/ansible-role-mr-provisioner/commit/098939e447f75e3c4d0b856583b81555e08879a5. I didn't try to add multi-host support, yet.
Lastly, the following playbook repository may be useful. It's basically an example, working playbook that exercises this role. I implemented dynamic host support in the ipgetter-integration branch
I'm starting to agree with @rengolin with regard to backward compatibility. As complexity grows, it may be better to just make it how we want it and migrate playbooks. There aren't many playbooks, and this role is versioned so it should not break anything until playbook authors choose to do the upgrade.

Thank you so much for detailed comments and for taking the time to implement changes directly, I looked into them and cherry-picked them directly.
Multiple host provisioning is an issue I agree, but adopting any kind of changes as you mentioned would also break the interface.
As of Ansible 2.2 you can loop over a role with include_role. I wonder if that would not be more appropriate.
Of course the interface could be changed and a new, non-backwards compatible, version of the role could be put out there.

You can do the loop for multiple hosts in the playbook or in the role. If you do it in the role, then playbook authors don't have to worry about it.
We're already breaking the interface. Let's break it once rather than potentially having to break it again in the future in order to support multiple hosts.
I suspect changing it to a datastructure as I proposed and adding a loop in the role will not be difficult.

This change doesn't seem non trivial to me.
I guess it would be nice for the purpose of testing of having multiple different machines provisioned by the same exact kernel/initrd, but then they might need different kernel command lines (early console), preseeds, etc...
In the end, Multiple Hosts provisioning is outside of the scope of this Pull Request.

OK. I disagree with the justification a bit but I'm fine with this change at this point because I don't want to hold up progress forever. If @chase-qi also signs off we can merge it.

Gents, thanks for the efforts! I had a try. Provisioning host from hosts file hit the below error:
TASK [Linaro.mr-provisioner : Provision machine] **************************************************************************************************************************************************************************************************************************
fatal: [j12-m1-c34n1 -> localhost]: FAILED! => {"changed": false, "debug": {}, "msg": "Error no assigned machine found with name \"False\""}
fatal: [j12-d05-01 -> localhost]: FAILED! => {"changed": false, "debug": {}, "msg": "Error no assigned machine found with name \"False\""}

I made the following changes so that it doesn't break me.
diff --git a/defaults/main.yml b/defaults/main.yml
index e0155f7..d68e71a 100644
--- a/defaults/main.yml
+++ b/defaults/main.yml
@@ -5,4 +5,5 @@ mr_provisioner_do_provision: True

 # By default, do not fetch the ip of the provisioned machine
 # Instead defer it to the host file, as legacy interface does.
-mr_provisioner_machine_name: False
+# Set the variable to 'True' to add host dynamically.
+mr_provisioner_machine_name: "{{ inventory_hostname }}"
diff --git a/tasks/main.yml b/tasks/main.yml
index 658dfb3..f246551 100644
--- a/tasks/main.yml
+++ b/tasks/main.yml
@@ -3,7 +3,7 @@
   delegate_to: localhost

 - include: add_host.yml
-  when: mr_provisioner_machine_name != False and mr_provisioner_do_provision
+  when: mr_provisioner_machine_name == True and mr_provisioner_do_provision
   delegate_to: localhost

 - name: Wait for host for 3600 seconds, but only start checking after 60 seconds

output example, looks sane?
TASK [Linaro.mr-provisioner : Verify variables are set] *******************************************************************************************************************************************************************************************************************
skipping: [j12-d05-01] => (item=mr_provisioner_machine_name)
skipping: [j12-m1-c34n1] => (item=mr_provisioner_machine_name)

TASK [Linaro.mr-provisioner : Get IP of provisioned machine] **************************************************************************************************************************************************************************************************************
skipping: [j12-m1-c34n1]
skipping: [j12-d05-01]

TASK [Linaro.mr-provisioner : debug] **************************************************************************************************************************************************************************************************************************************
skipping: [j12-d05-01]
skipping: [j12-m1-c34n1]

TASK [Linaro.mr-provisioner : Add provisioned machine as host] ************************************************************************************************************************************************************************************************************
skipping: [j12-d05-01]

TASK [Linaro.mr-provisioner : Wait for host for 3600 seconds, but only start checking after 60 seconds] **


Added Community Call - 2022.10.20

What this PR does / why we need it:
This PR adds the community call "Get more computing power in Gardener by overcoming Kubelet limitations with CRI-resource-manager" led on 20.10.2022 to the Community page.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

/review @Jessica-Katz @JordanJordanov


attr_encrypted

Does this work with attr_encrypted fields? Our database has the field encrypted_gender, which is then decrypted and mapped to gender.

I don't think it will @didlix  - The genderize method defines getters and setters that read and write directly from and to the column
https://github.com/KatanaCode/genderize/blob/master/lib/genderize.rb#L47-L52


Improved SamplingVQE algorithm implementation

Integrating a re-implementation of the SamplingVQE class, together with the BasisProtocol and AmplitudeProtocol made on commit db2b9965fbbd6cfa1eaee3788e8adff656acd624
This would also lead to an improved structure of the VQHAlgorithm class, allowing for modularity. A few considerations from @schwaeti during email exchanges:

The QUBO and the Isisng problem should be implemented as separate classes. (For legacy compatibility, a QUBOIsing problem class may also be necessary)
Writing a SparsePauliOp is problem specific - as a result, the Problem class implementations now would have an evalutate function specific to that problem.
A separate implementation for SamplingVQE and general VQE is necessary.
An improvement of the QuantumHardwareInterface class would lead to each provider having their own Sampler class

Discussion with @schwaeti :

The Prococol class may need to be dropped in the future. is this really needed?

A two-step process for the integration:

The names of the new protocols are different. The new AmplitudeProtocol implements marginal distributions. The new BasisProtocol does what the old Amplitude Protocol is doing. First step is to simply swap those.
Then, we solve the new naming problem. Is this one-hot? is this basis? is this amplitude? (this belongs to #8 )

For the Algorithm class:

By incorporating the VQHProtocol.encode() method into the VQHProblem.load_data(), we don't nee to call the encode method anymore from the VQHalgorithm classes. The problem will be loaded in the expected format, ready to be used. This should then be stored in a common attribute name VQHProblem.instances (when there is more than one problem defined in the file). As a result, the VQHAlgorithm.variables_index attribute will be deprecated. #6


fix(deps): Add missing 'loader-utils' dependency

Currently index.js requires 'loader-utils' without having it as a dependency in package.json.

Nice catch! Thanks for the PR 👍

Oh ups, sorry for the quote and thanks!


WIP - Remove deprecation, reduce fluxnode undo database size, add new bench…

Still need to add new benchmarking key before merging.

Regarding the discard greater than 500 blocks. What was the rationale behind only keeping 500? It seems kind of arbitrary?
Please forgive me if I'm wrong here. (and disregard)
Wouldn't that mean in the unlikely event that there was an issue with the chain and we need to roll back, we have to do it within 500 blocks or lose data? Isn't that a really small window?
I would imagine the data required for storage increase between 500 blocks worth and say 2160 (3 days) would be negligble?


[BUG]: misaligned copyright & social elements on footer for mobile devices 🙅🏻 ❌

Description

The copyright and social icons are misaligned for Mobile devices, this affects the user's who relay on smartphones to use our Informatician App.

Screenshots

CURRENT

DESIRED

Any additional information?
No response
What browser are you seeing the problem on?
Firefox
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Hey there @rohansx, @SiddhantPawar03, @crocmons 👋🏻
Please make sure to assign this issue to me to make the work done, Thank you!


Move compose box buttons into a row below the compose box

At present, compose box buttons are accessed via a "plus" symbol to the left of the compose box. Clicking on "plus" expands the buttons on the same line as the compose box. This works OK with the buttons we currently have, but is likely to no longer look good as we start adding more buttons (#3427, #5079).
We should try moving the row of buttons below the compose box. We may need to play with the UI to make sure the interactions feel natural, but we can try the following approach:

Putting the cursor into the compose box automatically opens a row of buttons below the compose box. Moving the cursor away from the compose box closes the buttons row.
Clicking on "plus" when the cursor is not in the compose box also automatically opens a row of buttons below the compose box.

This issue may be a blocker for #3427 and #5079. It's possible we can implement one of those without this issue, but not both.
Discussion thread on CZO

So I have two approaches, either I pull out the row of buttons part from the composeMenu component and make it a separate component ans use two version of the menu separately or the other way is I add more states in composeBox component and add some logic so that theere remains only single component i.e. composeMenu and I add some logic via props that renders 2 versions on basis of conditions of props. Which one to move forward with?

Agreed, the "plus" button should disappear when the buttons are expanded.

https://user-images.githubusercontent.com/65273718/140638602-70840fe0-7699-4dcb-863d-b5ce5a84cf89.mp4

Google.Pixel.4.emulator.zulip.testing.mp4

do we want something like thsi @alya @chrisbobbe ?

For the most part, that looks good to me!
I think we need to change the "collapse" (<) button, since it no longer has icons to the right of it in the new design. Perhaps just changing it to a ^ would work?

For the most part, that looks good to me!
I think we need to change the "collapse" (<) button, since it no longer has icons to the right of it in the new design. Perhaps just changing it to a ^ would work?

I have inlcuded the change suggested by you @alya. Please review the PR.

@chrisbobbe can you review the latest PR ?

Putting the cursor into the compose box automatically opens a row of buttons below the compose box. Moving the cursor away from the compose box closes the buttons row.
Clicking on "plus" when the cursor is not in the compose box also automatically opens a row of buttons below the compose box.

What use cases does (2) answer that (1) doesn't? After looking at those videos (thanks @chetas411!) I'm thinking we may not need a button at all, and we can just do (1).

I think it's simpler to have just one way to toggle than two. And (1) is maybe more appropriate than (2), since the row gives tools for composing a message, and composing a message is something you're only doing when the message input is focused.
If we remove the button, the input elements can get wider to fill the space where the button was. Wider input elements means a better compose experience. You can see more of your text on the screen at a time.

@alya, thoughts?

If you look at other apps, they do have a + button that can be used to attach files/pictures/etc. I think the idea is that the user's mental model might be not, "I want to compose a message", but "I want to send a picture," and in that case putting the cursor into the compose box is not a natural starting point.

@alya @chrisbobbe so is this change fine or any further changes required for this issue ?

If you look at other apps

@alya which apps are you thinking of?
I've just looked at Slack on iOS and Android, and it looks like on both platforms they use an approach like I described in https://github.com/zulip/zulip-mobile/issues/5080#issuecomment-972076840. They have a row of buttons under the message input, and you show or hide the row just by moving the focus in and out of the message input; there isn't a button for doing that. The row of buttons itself has a plus button, but that doesn't hide/unhide the row; it brings up a sheet that offers options that wouldn't fit in the row.
Here's a video of what I'm seeing: https://user-images.githubusercontent.com/22248748/142944344-89129d6a-aede-47a1-a94c-c7317913f18d.mp4

Message input is unfocused, row is hidden
I focus the input, row appears
I tap the + button in the row, it brings up a sheet with additional options
I close that sheet
I unfocus the input by scrolling a bit in the message list, row hides

I think the idea is that the user's mental model might be not, "I want to compose a message", but "I want to send a picture," and in that case putting the cursor into the compose box is not a natural starting point.

Hmm, maybe. I wonder if encouraging this mental model is a side effect of a bug, though: #4540. Currently, we have some buttons that act like send-image buttons, but they're really supposed to be attach-image buttons. Currently, once you select or capture a photo, the app takes a shortcut where it makes a new message with just the markdown for the photo and sends it right away, before you have a chance to edit it. That's annoying, and maybe scary, too, if you tap/send the wrong image by mistake and you don't know how to delete uploaded files or you don't do it fast enough. People who use the web app, or the edit-message feature in the mobile apps (or a future view-message-source feature on mobile), will be used to dealing with images as markdown, and I predict most of them will be relieved to have #4540 fixed.
And with it fixed, so that the buttons are proper "attach" buttons that don't send anything (they just act on the message-input text by adding a bit of markdown), I think putting the cursor into the compose box might be a natural starting point for using the buttons.

Hmm, what I had in mind is that Slack and Discord (on Android) always show the "+" button, even when no other formatting buttons are visible.
Perhaps we should discuss on CZO?

Perhaps we should discuss on CZO?

Sure: https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/.23M5080.20Move.20compose.20box.20buttons.20into.20a.20row.20below.20the.20compose/near/1285321

Ok, based on the discussion in the CZO thread linked above, let's limit this issue to just the first part:

Putting the cursor into the compose box automatically opens a row of buttons below the compose box. Moving the cursor away from the compose box closes the buttons row.

Ok, based on the discussion in the CZO thread linked above, let's limit this issue to just the first part, without changing the functionality for +:

Putting the cursor into the compose box automatically opens a row of buttons below the compose box. Moving the cursor away from the compose box closes the buttons row.

The + should disappear when the cursor is in the compose box.

So should I make functionality for + button same as before or is this fine as well because anyhow  #5141 will gonna change it again ?

For this PR, we should make the functionality for the + button as before when it is shown. We want to make this PR mergeable separately from #5141, and that will be the way to do that.
Thanks!

@alya I have made the changes proposed by you,  can you review ?
https://user-images.githubusercontent.com/65273718/143764414-27ca420c-ff93-41c1-acc2-cb514cb424e1.mp4