trouble passing data to prop in route with vue-cli setup

Version
2.7.0
Reproduction link
https://jsfiddle.net/chancesmith/vj3n55vs/3/
Steps to reproduce
Look at jsfiddle.
What is expected?
Trying to pass root Vue instance data to route prop.
What is actually happening?
Getting error that contact info is not in scope.

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server, gitter or StackOverflow.

this is just window there. In that very specific case, you can refer to routerApp.contactInfo


Reduce using nuxt-property-decorator and use composition API

We need to reduce using nuxt-property-decorator first and use composition API instead. It will help us to migrate to vue3/nuxt3
https://github.com/nuxt-community/nuxt-property-decorator/issues/83#issuecomment-1245139696. at least for newer components
related: https://github.com/kodadot/nft-gallery/issues/2893
And I think we face this problem also https://github.com/nuxt-community/nuxt-property-decorator/issues/83#issuecomment-1246615441; most of the library is still not ready in nuxt3. And maybe some libs/modules are not compatible also in nuxt-bridge
It seems we have a lot of them (484 mentions)

https://github.com/kodadot/nft-gallery/search?p=1&q=nuxt-property-decorator

Part of

https://github.com/kodadot/nft-gallery/issues/2690

Originally posted by @preschian in https://github.com/kodadot/nft-gallery/issues/2690#issuecomment-1280409802
Ref

https://github.com/kodadot/nft-gallery/issues/2893

It's improving!
465 code results in kodadot/nft-gallery

456 code results

415 code results in kodadot/nft-gallery

Can't manage to use layout() with nuxt-bridge

178 files

👀

https://github.com/search?q=repo%3Akodadot%2Fnft-gallery+nuxt-property-decorator&type=code

156 👀

144 files 👀

144 files .. again 🪨

141 files 👀

134 👀👀👀

👀👀👀
125 👀
👀👀👀

115 😏

88 files 😳

78 files 🤩

63 files 🤯

54 🫣

34 🔢

34 🔢

search shows 50, maybe cached?

search shows 50, maybe cached?

Well yes and no
Number of .vue components

It's moving
43 / 30

35 / 24

29 / 18

26 / 15

18 / 7
nuxt3 is getting closer
you can vote on prediction market btw - https://app.zeitgeist.pm/markets/238

Very last three components.

Last two?

#7038
#7030

Very last ~three~ two components.

Time to update STYLE_GUIDE.md
And check if we use some of the last mixins

12 / 1

According Create component we do not use typescript mixins

12 / 1
if someone wants to have a look at the very last one.

https://github.com/search?q=repo%3Akodadot%2Fnft-gallery+nuxt-property-decorator&type=code
delete all mixins and remove nuxt-property-decorator from package.json?

Done in

#7117


fix(coral): Fix environmentGetClusterInfoResponse schema

About this change - What it does
environmentGetClusterInfoResponse can only have aivenCluster as property, as it is an exception implemented specifically for Aiven clusters. If "true", then aclIpPrincipleType in an ACL request can only be PRINCIPAL.

@muralibasani do you have an idea for an accurate description we could add to this definition?

@muralibasani do you have an idea for an accurate description we could add to this definition?

description can be : Get flavor of kafka cluster - if its of type 'Aiven' or other kafka cluster flavors.
below is the relevant code for this condition
$scope.aivenCluster = output.aivenCluster;                         if($scope.aivenCluster === 'false'){                             $scope.acl_ip_ssl = 'IP';                             $scope.selectedAclType="IP_ADDRESS";                         }                         else{                             $scope.acl_ip_ssl = 'SSL';                             $scope.selectedAclType="PRINCIPAL";                         }


Decouple clock number from size of history

Having clock number tied to history causes issues on higher clock numbers, as it is effectively a memory leak. It would be better to keep it separate, and add a limit to how large the history size can grow before it starts discarding the oldest records. I also suggest that instead of clock being stored in GuiData it is instead fetched when needed from the simulator.

The reason to have clock in GuiData is that it provides a lens, so when changed components like the ProbeEdit knows that something has happened.
Regarding memory leak, I don't quite follow.

Regarding memory leak, I don't quite follow.

I mean that keeping an unlimited sized history might not be optimal, as it might cause issues if you for example leave the clock running in the background and forget about it, as it will endlessly grow.

Indeed, the simulator holds the history (as a Vec<...), it would be perfectly possible to limit the size and have it dropping oldest element, on enqueing a new. Maybe a double linked version would be better with cheap operations on both head and tail.

GUI elements that holds internal state etc., is responsible for their own history management, essentially triggered by clock, un_clock and perhaps also reset (currently not implemented though).


FIXED but need response: Collapsible Bug

When entering iframe in a part of collapsible, all collapsible after the iframe, even in different dive or collapsible will be hidden. If I enter iframe at third of collapsibel, second and first still show up. How can I put iframe in everysingle body collapsible :worried:. paragraph tags worked fine, though, just the iframe tag that breaks. http://pastebin.com/fuiAd8iu

fixed. iframe somehow needs to be formatted like  instead of

I believe the correct markup for an iframe requires an ending tag.


Enable SSH into the ov container

Problem

It is possible to set up IDEs like VSCode to a remote host, where you can run plugins and use the remote host's language tools for IDE extensions. This is useful, for example, to enable using the VSCode python plugin with the Python installation inside the ov container, including autocompletion, and go to definition for libraries, without needing to also run pdm install on your host system.
Description

I have just tried this on my computer and it works well, but there's a bit of setup involved. It would be good to have the setup and configuration automated in the root ov bash script. To get this working, the minimum requirements are:

Install the openssh-server package: dnf install openssh-server.
For Linux hosts, add a user with a login shell in the container matching the host user. For macOS hosts, they will log into the container as root, so SSHd needs to be configured to allow root logins (set PermitRootLogin yes in /etc/ssh/sshd_config in the ov container). Also change the port to 2200, and consider changing the permitted host to prevent access outside the docker network.
Run ssh-keygen in the container
If the host has an SSH key, copy the public key into the authorised keys file in ov. Alternatively, we can add a password to the user in ov (see step 2 for choosing the user) and set it to openverse or something.

That should make it possible to SSH into the ov container. In VSCode, you can take advantage of this using the remote SSH plugin. VSCode has a proprietary one, and this one works perfectly for vscodium. Once inside VSCode, you can install plugins in the ov container and things work just like they would on the host machine.
It looks like JetBrains IDEs have a similar kind of setup that would enable using the interpreters inside the container. IIRC @AetherUnbound you mentioned wanting to look into this. Did you ever get a chance to do so/do you know if any additional setup would be needed for PyCharm? At a glance it looks like the requirements are just having SSH, like VSCode's requirements.

Pinging @WordPress/openverse-developer-experience, especially Dhruv, in case you are interested in this kind of thing as well.

It looks like JetBrains IDEs have a similar kind of setup that would enable using the interpreters inside the container. IIRC @AetherUnbound you mentioned wanting to look into this. Did you ever get a chance to do so/do you know if any additional setup would be needed for PyCharm? At a glance it looks like the requirements are just having SSH, like VSCode's requirements.

I have not looked into it further, but SSH shouldn't be necessary for it. JetBrains can use Docker directly. As long as JetBrains can connect to the Docker daemon, it should work!


Fix constant redefinitions in tests

Goal
Clean up the test output

LGTM.  I did re-run the tests as they initially both failed on Ruby 2.0, but on multiple re-runs they've been fine.  I doubt it's anything to do with the PR though.

I hadn't merged master into this branch which has the flakey test fix in.


Update sbt to 1.4.3

Updates org.scala-sbt:sbt from 1.4.2 to 1.4.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-patch

Codecov Report

Merging #73 (32f755b) into master (fb5cd95) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #73   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           47        47
=========================================
  Hits            47        47

Continue to review full report at Codecov.

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


CommentChange

Change comment of method GetAge

Please update patch for latest version of source code, thank you. And also between calculating and getting things is huge difference. Calculation involves some mathematical process and could be time consuming, getting should be fast.

Conflicts


Test and/or update sensu-plugin-tool support for aws-plugin-template

Tested with plugin tool   using fresh user with no pre-existing go modules installed.  This repository will build cleanly.
Steps:

install sensu-plugin-tool
use sensu-plugin-tool new check
when prompted use aws-plugin-template repository url in place of default url
complete rest of plugin-tool prompts
run go get
run go build
run go test

Update for plugin-tool to introduce custom plugin type and readme instructions for AWS service example.
https://github.com/sensu/sensu-plugin-tool/pull/12

Jef will sync up with Troy to review this PR and get it merged, then we can close this issue. :+1:

Assigning this one to myself and pulling this back into the "needs proposal" column until we can decide what our approach is for future AWS plugins.


[BUG] jsonable_encoder function not working as expected with different type of variables

First check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.
[X] After submitting this, I commit to one of:

Read open issues with questions until I find 2 issues where I can help someone and add a comment to help there.
I already hit the "watch" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
Implement a Pull Request for a confirmed bug.

Example
Here's a self-contained, minimal, reproducible, example with my use case:
Example 1 (BaseModel)
import pytest
from attr import dataclass
from fastapi.encoders import jsonable_encoder
from pydantic.main import BaseModel

class MyBaseModel(BaseModel):
    foo: int
    bar: int

@pytest.mark.parametrize(
    "obj, include, exclude, expected",
    [
        (MyBaseModel(foo=1, bar=2), None, None, {"foo": 1, "bar": 2}),  # Passed
        (MyBaseModel(foo=1, bar=2), {}, {}, {}),  # Passed
        (MyBaseModel(foo=1, bar=2), {"foo"}, {}, {"foo": 1}),  # Passed
        (MyBaseModel(foo=1, bar=2), {}, {"foo"}, {}),  # Passed
        (MyBaseModel(foo=1, bar=2), {"foo"}, None, {"foo": 1}),  # Passed
        (MyBaseModel(foo=1, bar=2), None, {"foo"}, {"bar": 2}),  # Passed
    ],
)
def test_jsonable_encoder_include_exclude_base_model(obj, include, exclude, expected):
    assert jsonable_encoder(obj, include=include, exclude=exclude) == expected

Example 2 (Python dictionary)
import pytest
from fastapi.encoders import jsonable_encoder

@pytest.mark.parametrize(
    "obj, include, exclude, expected",
    [
        ({"foo": 1, "bar": 2}, None, None, {"foo": 1, "bar": 2}),  # Passed
        ({"foo": 1, "bar": 2}, {}, {}, {}),  # Failed
        ({"foo": 1, "bar": 2}, {"foo"}, {}, {"foo": 1}),  # Failed
        ({"foo": 1, "bar": 2}, {}, {"foo"}, {}),  # Failed
        ({"foo": 1, "bar": 2}, {"foo"}, None, {"foo": 1}),  # Failed
        ({"foo": 1, "bar": 2}, None, {"foo"}, {"bar": 2}),  # Passed
    ],
)
def test_jsonable_encoder_include_exclude_dict(obj, include, exclude, expected):
    assert jsonable_encoder(obj, include=include, exclude=exclude) == expected

Example 3 (Python object with dataclass)
@dataclass
class MyModel:
    foo: int
    bar: int

@pytest.mark.parametrize(
    "obj, include, exclude, expected",
    [
        (MyModel(foo=1, bar=2), None, None, {"foo": 1, "bar": 2}),  # Passed
        (MyModel(foo=1, bar=2), {}, {}, {}),  # Failed
        (MyModel(foo=1, bar=2), {"foo"}, {}, {"foo": 1}),  # Failed
        (MyModel(foo=1, bar=2), {}, {"foo"}, {}),  # Failed
        (MyModel(foo=1, bar=2), {"foo"}, None, {"foo": 1}),  # Failed
        (MyModel(foo=1, bar=2), None, {"foo"}, {"bar": 2}),  # Failed
    ],
)
def test_jsonable_encoder_include_exclude_obj(obj, include, exclude, expected):
    assert jsonable_encoder(obj, include=include, exclude=exclude) == expected

Description

I was trying to understand how the include and exclude parameters worked. I looked in the documentation (here) and the the test suite (here, latest commit of this file in master branch) and I did not find anything related to include and exclude in both places.
I did see that these 2 parameters came from Pydantic (from the dict function) and it is being used in the _calculate_keys method.
The first thing I did was to check the jsonable_encoder using a BaseModel object, which uses the dict function from Pydantic (Example 1), so I created a set of test with a BaseModel instance. All those tests are passing. Then I created the same tests with a Python dictionary (Example 2) and a Python object (Example 3).
I expect that the same tests with a different type of variable would work the same. In the case of Example 3, it is failing the most because it is missing the include and exclude parameters at the end of the function (here).
Environment

OS: Linux
Python: 3.8.5
FastAPI Version: 0.63.0

To know the FastAPI version use:
python -c "import fastapi; print(fastapi.__version__)"

Python version:

To know the Python version use:
python --version

Additional context
To reproduce the Example snippets, you will also need pytest installed (6.2.1 in my case)
I am happy to help by creating a PR for this bug once it is confirmed.

All examples together
import pytest
from attr import dataclass
from fastapi.encoders import jsonable_encoder
from pydantic.main import BaseModel

class MyBaseModel(BaseModel):
  foo: int
  bar: int

@dataclass
class MyModel:
  foo: int
  bar: int

@pytest.mark.parametrize(
  "obj, include, exclude, expected",
  [
      (MyBaseModel(foo=1, bar=2), None, None, {"foo": 1, "bar": 2}),  # Passed
      (MyBaseModel(foo=1, bar=2), {}, {}, {}),  # Passed
      (MyBaseModel(foo=1, bar=2), {"foo"}, {}, {"foo": 1}),  # Passed
      (MyBaseModel(foo=1, bar=2), {}, {"foo"}, {}),  # Passed
      (MyBaseModel(foo=1, bar=2), {"foo"}, None, {"foo": 1}),  # Passed
      (MyBaseModel(foo=1, bar=2), None, {"foo"}, {"bar": 2}),  # Passed
      ({"foo": 1, "bar": 2}, None, None, {"foo": 1, "bar": 2}),  # Passed
      ({"foo": 1, "bar": 2}, {}, {}, {}),  # Failed
      ({"foo": 1, "bar": 2}, {"foo"}, {}, {"foo": 1}),  # Failed
      ({"foo": 1, "bar": 2}, {}, {"foo"}, {}),  # Failed
      ({"foo": 1, "bar": 2}, {"foo"}, None, {"foo": 1}),  # Failed
      ({"foo": 1, "bar": 2}, None, {"foo"}, {"bar": 2}),  # Passed
      (MyModel(foo=1, bar=2), None, None, {"foo": 1, "bar": 2}),  # Passed
      (MyModel(foo=1, bar=2), {}, {}, {}),  # Failed
      (MyModel(foo=1, bar=2), {"foo"}, {}, {"foo": 1}),  # Failed
      (MyModel(foo=1, bar=2), {}, {"foo"}, {}),  # Failed
      (MyModel(foo=1, bar=2), {"foo"}, None, {"foo": 1}),  # Failed
      (MyModel(foo=1, bar=2), None, {"foo"}, {"bar": 2}),  # Failed
  ],
)
def test_jsonable_encoder_include_exclude(obj, include, exclude, expected):
  assert jsonable_encoder(obj, include=include, exclude=exclude) == expected

The pydantic docs for include/exclude are here, for anyone curious regarding this issue.
@xaviml How would you expect this to work for objects that are not pydantic models? Seems like we'd have to make a lot of assumptions about the structure of the objects.
Perhaps docs could be added saying include/exclude are only valid for pydantic models?
Trying to get some more information: If you really want to use include/exclude, is there anything preventing you from using a pydantic model.

The pydantic docs for include/exclude are here, for anyone curious regarding this issue.
@xaviml How would you expect this to work for objects that are not pydantic models? Seems like we'd have to make a lot of assumptions about the structure of the objects.
Perhaps docs could be added saying include/exclude are only valid for pydantic models?
Trying to get some more information: If you really want to use include/exclude, is there anything preventing you from using a pydantic model.

Hi @falkben,
Thank you for your reply.

How would you expect this to work for objects that are not pydantic models?

I would expect to be consistent, so to work the same as Pydantic models. For example, if we do:
jsonable_encoder({"foo": 1, "bar": 2}, include={"foo"})

I would expect to return {"foo": 1}. However, this returns: {"foo": 1, "bar": 2}. The same way that if we do:
jsonable_encoder({"foo": 1, "bar": 2}, exclude={"foo"})

It returns {"bar": 2} as expected.

Seems like we'd have to make a lot of assumptions about the structure of the objects.

I don't think is about the assumption of the structure of the object. They are all converted to dictionaries with dict (here) or vars(here). What needs to change is the way of including and excluding (here).

Perhaps docs could be added saying include/exclude are only valid for pydantic models?

You can see in this if branch that include and exclude is also used when the object is a dictionary.

Trying to get some more information: If you really want to use include/exclude, is there anything preventing you from using a pydantic model.

I am using the jsonable_encoder with a SQLAlchemy object, the same way it is done in here. This is what is preventing me to use a Pydantic model, because I use a SQLAlchemy model. I will find a workaround to this, but this is another matter not related to this issue.
When I created this issue I tried to understand what is the expected use of include and exclude parameters from jsonable_encoder. This is why I went to the tests and see what is the expected behaviour of this function with the use of include and exclude. What I proposed is how I think it should be (and how it works with Pydantic), but I am happy to hear and discuss the right implementation for this function with these parameters.
Regards,
Xavi M.

Hi @falkben,
Thank you for your reply.

How would you expect this to work for objects that are not pydantic models?

I would expect to be consistent, so to work the same as Pydantic models. For example, if we do:
jsonable_encoder({"foo": 1, "bar": 2}, include={"foo"})

I would expect to return {"foo": 1}. However, this returns: {"foo": 1, "bar": 2}. The same way that if we do:
jsonable_encoder({"foo": 1, "bar": 2}, exclude={"foo"})

It returns {"bar": 2} as expected.

Seems like we'd have to make a lot of assumptions about the structure of the objects.

I don't think is about the assumption of the structure of the object. They are all converted to dictionaries with dict (here) or vars(here). What needs to change is the way of including and excluding (here).

Perhaps docs could be added saying include/exclude are only valid for pydantic models?

You can see in this if branch that include and exclude is also used when the object is a dictionary.

Trying to get some more information: If you really want to use include/exclude, is there anything preventing you from using a pydantic model.

I am using the jsonable_encoder with a SQLAlchemy object, the same way it is done in here. This is what is preventing me to use a Pydantic model, because I use a SQLAlchemy model. I will find a workaround to this, but this is another matter not related to this issue.
When I created this issue I tried to understand what is the expected use of include and exclude parameters from jsonable_encoder. This is why I went to the tests and see what is the expected behaviour of this function with the use of include and exclude. What I proposed is how I think it should be (and how it works with Pydantic), but I am happy to hear and discuss the right implementation for this function with these parameters.
Regards,
Xavi M.

Possibly related? https://github.com/tiangolo/fastapi/pull/2016

Possibly related? https://github.com/tiangolo/fastapi/pull/2016

Hi @falkben,
I did see that issue before creating this one. The #2016 PR adds support to dictionaries for the include and exclude, but it does.not change the way include and exclude are being used. Although both of these issues (#2016 and this one) are about jsonable_encoder, they are not related.
Regards,
Xavi M.

Hi @falkben,
I did see that issue before creating this one. The #2016 PR adds support to dictionaries for the include and exclude, but it does.not change the way include and exclude are being used. Although both of these issues (#2016 and this one) are about jsonable_encoder, they are not related.
Regards,
Xavi M.

I created a PR (#2606) fixing the problem mentioned here. You can find in the PR what was the problem and which tests were affected.

I created a PR (#2606) fixing the problem mentioned here. You can find in the PR what was the problem and which tests were affected.

I ran in the same bug tonight.
Any chance that this issue gets classified as bug and the corresponding pr gets reviewed? @tiangolo

Hello,
I've added 1 more test case in another issue for proving the change introduced in 0.67 version broke the contract of jsonable_encoder.

the frick
On Tue, Jan 18, 2022 at 4:59 AM Stanislav Petrov @.***>
wrote:

Hello,
I've added 1 more test case in another issue
https://github.com/tiangolo/fastapi/issues/3636#issuecomment-1015245101
for proving the change introduced in 0.67 version broke the contract of
jsonable_encoder.
—
Reply to this email directly, view it on GitHub
https://github.com/tiangolo/fastapi/issues/2594#issuecomment-1015248299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWZ3M2OOWJ6YJQ5MH2HKJ3LUWU2WVANCNFSM4VR56WOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Having this issue...


Unable to move the migrations to production environment

Hi @robmorgan  I have integrated phinx with codeignitor. Locally all the migrations are running fine.  Now i have pushed the code files to server. Now how to run migrations on online database. In the phinx.yml file i have filled the details for my production environment. But its not working, .

hi @gurpreet2501 do you have terminal/shell access to your production environment or are you using the web interface?

I am using the web interface.

@gurpreet2501 can you post a screenshot?

which screenshot you need ? Screenshot of the phinx.yml configuration file or anthing else? @robmorgan

@gurpreet2501 when you say it doesn't work? What exactly doesn't work? Can you provide more information and or/screenshots if theres any error messages. Or are you unsure how to execute them? Don't post a screenshot of your phinx.yml file as it likely contains your private credentials.

Yes i dont know how to execute the migrations on server. In the documentation, I was unable to find the procedure to run it on production environment. Would you please help me to do so ?

chnaged web_migrate.php code

/* Phinx
*

(The MIT license)
Copyright (c) 2014 Rob Morgan
Copyright (c) 2014 Woody Gilk

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated * documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
IN THE SOFTWARE.
*/

// This script can be run as a router with the built in PHP web server:
//
//   php -S localhost:8000 app/web.php
//
// Or can be run from any other web server with:
//
//   require 'phinx/app/web.php';
//
// This script uses the following query string arguments:
//
// - (string) "e" environment name
// - (string) "t" target version
// - (boolean) "debug" enable debugging?
// Get the phinx console application and inject it into TextWrapper.
$app = require DIR . '/vendor/robmorgan/phinx/app/phinx.php';
$wrap = new Phinx\Wrapper\TextWrapper($app);
// Mapping of route names to commands.
$routes = [
'status'   => 'getStatus',
'migrate'  => 'getMigrate',
'rollback' => 'getRollback',
];
// Extract the requested command from the URL, default to "status".
$command = $_GET['command'];
if (!$command) {
$command = 'status';
}
// Verify that the command exists, or list available commands.
if (!isset($routes[$command])) {
$commands = implode(', ', array_keys($routes));
header('Content-Type: text/plain', true, 404);
die("Command not found! Valid commands are: {$commands}.");
}
// Get the environment and target version parameters.
$env    = isset($_GET['e']) ? $_GET['e'] : null;
$target = isset($_GET['t']) ? $_GET['t'] : null;
// Check if debugging is enabled.
$debug  = !empty($_GET['debug']) && filter_var($_GET['debug'], FILTER_VALIDATE_BOOLEAN);
// Execute the command and determine if it was successful.
$output = call_user_func([$wrap, $routes[$command]], $env, $target);
$error  = $wrap->getExitCode() > 0;
// Finally, display the output of the command.
header('Content-Type: text/plain', true, $error ? 500 : 200);
if ($debug) {
// Show what command was executed based on request parameters.
$args = implode(', ', [var_export($env, true), var_export($target, true)]);
echo "DEBUG: $command($args)" . PHP_EOL . PHP_EOL;
}
echo $output;

Thanks @robmorgan I have found the direct code to execute it on production...

@gurpreet2501 good luck!


TFRS - Revise Schedule B tooltip for 2023 compliance reports

Describe the task
Currently, Schedule B in 2023 compliance reports has a label called "CREDIT/DEBIT CALCULATION" that includes a tooltip with a extensive description of the credit/debit formula in the former Act.
Task is to:

Remove Schedule B label called "CREDIT/DEBIT CALCULATION"
Remove corresponding tooltip
Add tooltip to new 'Compliance Units' label (in the cell immediately below the "CREDIT/DEBIT CALCULATION" label)
New tooltip message: "The number of compliance units to be issued is determined in accordance with the formula set out in the former Act; that is, section 6 (4) of the Greenhouse Gas Reduction (Renewable and Low Carbon Fuel Requirements) Act.

Purpose
Compliance units are replacing credit/debit system for 2023 compliance reports. Therefore, we need to remove references to the old credit/debit system.
Acceptance Criteria

[ ] Changes shouldn't affect existing functionality or break sizing of the table.

Screenshots:
"CREDIT/DEBIT CALCULATION" label

Tooltip to remove

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

Removal of Schedule B label called "CREDIT/DEBIT CALCULATION" and corresponding tooltip has been applied to compliance reports for all years. This change should only be applied to 2023+ compliance reports, and not 2022 and prior years reports.

updated the schedule b table to display credit/debit and compliance unit tooltips based upon compliance period.

Can we fix the formatting? It doesn't seem to be displaying as nicely in terms of the layout. See this screenshot for what it looks like now: Private Zenhub Image. The original formatting is in the screenshot in the card description.


notodiff: png image is not wide enough

I'm not sure how we decide on how wide the diffed image should be.
Here's the input (left --before; right --after)

the diff image is missing significant information (IMHO)

What font is this?

This was from diff of
--before https://github.com/googlei18n/noto-fonts/blob/master/alpha/from-pipeline/NotoSansJavanese-Regular.ttf
and
--after (look for submission in https://github.com/googlei18n/noto-fonts/pull/792 )

Which glyph's image did you attach? I don't see any notodiff output quite like that.

--before NotoSansJavanese-Regular.ttf.zip
--after NotoSansJavanese-Regular-c.ttf.zip
look for jv__d_dha__pas

Huh, when I run notodiff on those two fonts I get
 Mark class mismatch for jv_Ddha_pas (no class vs mark)
and no jv__d_dha__pas.png is generated.
I should have a fix soon for rendering widths anyways, but it's strange that we'd see different things here.


ISPN-15151 Unable to upgrade if a backup has been restored on the old…

https://issues.redhat.com/browse/ISPN-15151

I have manually backported as there was a conflict: https://github.com/infinispan/infinispan/pull/11267

a lot of failures

Stupid NPE, should be good now

Failures unrelated.

RequestTracingIT is related, investigating...

RequestTracingIT failures caused by use of non-string value in Server properties, I have reinstated the use of a CSV property value. Still not clear why this causes only this test to fail.

Merged, thanks


Icon.Button - icon on right?

Is there a plan to add an option to align icon to the right? (to get a pull down/select button)

There isn't one the moment, but it's very easy to replicate this functionality by yourself. Take a look at the source: https://github.com/oblador/react-native-vector-icons/blob/master/lib/icon-button.js

Just set style flexDirection to row-reverse
 <Icon.Button  style={{flexDirection: "row-reverse"}}>
 ......
 </Icon.Button>


rtags: 9fed420 -> 233543d

Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] OS X
[x] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Hm, not related to this PR in particular but: the version really should use the date of the commit, per conventions. Revisions by themselves are not valid versions. Secondly, I wonder if there's a reason why fetchgit is used instead of generated tarballs.

Fixed the version number. I believe fetchgit is used because the build relies on submodules, which github tarballs don't include.

Please squash when you're ready to merge


Users with multiple accounts get multiple reset-password emails

Problem

The old tech used username as the  uniquely identifying thing for logging in. The new tech uses email which means that there are users who have multiple accounts linked to the same email address
This would cause all kinds of issues as you can only log into one of those accounts
It's worth noting that the validation on the database is set to unique email addresses however the rule didn't seem to apply to existing data.

Solution

Run a quick script to delete accounts where there are more than 1 Profile linked to a single email address. Presumably we'd keep the one with the higher id as it's newer.

Wait, that can't possibly be right. Postgres enforces uniqueness constraints all the time, not just when new data is added. We'd be getting IntegrityErrors if there were really duplicates on a unique column.
Any chance this has to do with case sensitivity?

Oh looks like you're right. See this: https://rtcharity.slack.com/archives/GBUD95PT8/p1550006120035100

I think we want to change the database column to this.

Go for it 💪


create new datapoint "Connected"

The connection state is currently only accesable via state_raw=255 - Not Connected.
Detect this state and create a datapoint connected = false in this state.
Otherwise it's connected = true.
This will make it more conveniant to use this value in VIS.

done in V1.2.0


Documentation: edits to main page

Description
This PR makes edits to the front page of the documentation. The primary change is the replacement of the OpenFF workflow graphic with an adaptation of @Lnaden 's pipeline slide.
Todos
Questions
Status

[ ] Changelog updated
[ ] Ready to go

@mattwelborn Is this ready to go?

Yes.


Server Error when using lds-pdi public data

BDRC Public Data Interface has a sample entry for AO_listSynedIGInW that reads: /query/table/AO_listSyncedIGInW.arq?R_RES=bdr:W22084
This returns a server error.
Using without the .arq suffix works as expected (returns an HTML page, or RC of 0 when used from the command line)

thanks! fixed


tsconfig es2020 node

Changing tsconfig files:  'target' to 'es2020'

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

targetting wrong branch

I know, i have to switch it on the web version but publish from cli

Have you run the test-app (the one in packages/apps/web-viewer-test)?
I'm running into this locally:

closing this pr, too many conflicts, will just redo whats necessary for 4.0 release


Backup buttons extend off page

It could get cluttered with buttons for each environment, so need to look into displaying environments as checkbox list and having one Backup button. This would also add the functionality to backup multiple environment folders at the same time.

When there are many sibling folders, the backup buttons can extend off the page.
Need to consider changing buttons to checkboxes to fit onscreen better.

Remember to update the README after this is changed.
3. Click the "Backup" button for the environment folder you want to backup.


doc: cloud profiles in Cumulocity

Proposed changes
Adds documentation for using cloud profiles to connect to multiple Cumulocity instances. Hides the c8y.device.id and related configurations since those don't yet work due to external ID issues.
Hiding the device ID is done in a single separate commit so it should be easy to revert once the feature works properly.
There is also a small change to ensure profile names are always lowercased, in case someone accesses a key using e.g. tedge config get c8y.profiles.EDGE.url, where we weren't previously lowercasing the profile name.
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[x] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[x] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Further comments

@jarhodes314  I pushed one commit to add the <UserContextForm at the top of the page, and I've also created a PR on the tedge-docs project to support the passing the title property from the <UserContext> element to the codeblock (which your PR uses a lot). https://github.com/thin-edge/tedge-docs/pull/96

@jarhodes314 I pushed one commit to add the <UserContextForm> at the top of the page, and I've also created a PR on the tedge-docs project to support the passing the title property from the <UserContext> element to the codeblock (which your PR uses a lot). thin-edge/tedge-docs#96

Thanks, I made the change locally and then completely forgot that it was separate thing I needed to deal with PR wise.

I have no objections to limiting the profile names to lower case only. But, just curious to know if there was any specific reason why you decided to make it case-insensitive?

Setting the values via env variables comes to mind where it would benefit from this, e.g. TEDGE_C8Y_PROFILES_MYNAME_URL where using uppercase in convention for env variables...TEDGE_C8Y_PROFILES_MyName_URL just looks weird.
But normalizing to lowercase just avoids problems from non linux users whom just expect things to be case-insensitive these days, e.g. Windows and MacOS are generally case insensitive when it comes to file/folder names, and linux users would probably already use lower case (because they know better)).

I've created a PR on tedge-docs to support $C8Y_PROFILE_NAME and $C8Y_PROFILE_URL. I don't think it's worth parameterising the topic prefix separately, I've just inferred what I believe to be the most sensible value there from the profile name.


Update organization_header and create tests

This is pretty much ready to go, but could use some input on the contact_email test if anyone has a minute, thanks! I commented out that it block in the test file.

Fixes #659

As a sort of general rule if I find myself wanting to use current_page logic in a template that's a hint to refactor.


Expand testing of Response with malformed responses

Plug in the framework that simulates varieties of invalid reponses.

@antkmsft , Mike Harder has a framework that allows validating the system with partial, incomplete, invalid responses.  We need to automate using that system and run it against both WinHttp and Curl.

http-fault-injector: https://github.com/Azure/azure-sdk-tools/tree/master/tools/http-fault-injector
I will build the C++ sample in the azure-sdk-tools repo next to java and .net.
Things to be done:

Create CMake project which consumes the Azure SDK for C++ libraries.  Start by consuming only Azure Core to test a general request directly performed by the Azure Core transport adapters (libcurl on Lin, winHttp on Win).
Implement sample application and the  FaultInjectionClientHandler class to redirect the requests.
Test all responses provided by the fault-injector.
Optionally, and if time allows it, create a sample for using Storage client, similar to .NET

The estimated time for all the implementation and test (without fixing any possible bugs in the adapters) is 2 days.

LibCurl results:
f: Full response
./sdk/core/azure-core/test/fault-injector/azure-core-test-fault-injector
Sending request...
Status Code: 200
p: Partial Response (full headers, 50% of body), then wait indefinitely
./sdk/core/azure-core/test/fault-injector/azure-core-test-fault-injector
Sending request...
terminate called after throwing an instance of 'Azure::Core::Http::TransportException'
what():  Timeout waiting for socket to read.
pc: Partial Response (full headers, 50% of body), then close (TCP FIN)
./sdk/core/azure-core/test/fault-injector/azure-core-test-fault-injector
Sending request...
terminate called after throwing an instance of 'Azure::Core::Http::TransportException'
what():  Error while reading from network socket. CURLE code: 56. Failure when receiving data from the peer
pa: Partial Response (full headers, 50% of body), then abort (TCP RST)
/sdk/core/azure-core/test/fault-injector/azure-core-test-fault-injector
Sending request...
terminate called after throwing an instance of 'Azure::Core::Http::TransportException'
what():  Error while reading from network socket. CURLE code: 56. Failure when receiving data from the peer
pn: Partial Response (full headers, 50% of body), then finish normally
./sdk/core/azure-core/test/fault-injector/azure-core-test-fault-injector
Sending request...
terminate called after throwing an instance of 'Azure::Core::Http::TransportException'
what():  Error while reading from network socket. CURLE code: 56. Failure when receiving data from the peer
n: No response, then wait indefinitely
./sdk/core/azure-core/test/fault-injector/azure-core-test-fault-injector
Sending request...
terminate called after throwing an instance of 'Azure::Core::Http::TransportException'
what():  Timeout waiting for socket to read.
nc: No response, then close (TCP FIN)
./sdk/core/azure-core/test/fault-injector/azure-core-test-fault-injector
Sending request...
terminate called after throwing an instance of 'Azure::Core::Http::TransportException'
what():  Error while reading from network socket. CURLE code: 56. Failure when receiving data from the peer
na: No response, then abort (TCP RST)
./sdk/core/azure-core/test/fault-injector/azure-core-test-fault-injector
Sending request...
terminate called after throwing an instance of 'Azure::Core::Http::TransportException'
what():  Error while reading from network socket. CURLE code: 56. Failure when receiving data from the peer

@vhvb1989 what are the expected results for each of those scenarios and what do other languages like .NET do?
Does what's happening match what we want?

@vhvb1989 what are the expected results for each of those scenarios and what do other languages like .NET do?
Does what's happening match what we want?

I've asked @mikeharder to take a look to these results. I believe they are fine.  Mike can correct me if I am wrong, but I think what we want is to make sure that our transport adapter:

Can be used with the fault-injector. Means it can send the request and waits until we manually chose what response to return from the fault injector.  While we wait for that, the transport adapter should just keep waiting for the server response.
Throw an exception or somehow recognize the returned response from the server is invalid/incompleted/etc.  We want to make sure that the transport adapter won't consider an invalid response as OK and gives the buffer back to the protocol layer which will try to parse an invalid response.
Make sure there's a request timeout for the cases when the Server won't finish a response. We don't want to keep waiting for the server forever.

These results look correct for a single request (with no retries).  One issue we've seen in other languages is that the retry policy was not being applied correctly in some of these cases.  For example, if you were downloading a blob and the response is closed/aborted in the middle of the body, the client should retry automatically (and only download the remaining data, at least in .NET).
Another note is you can pre-select the response from the fault injection server using a special header:
https://github.com/Azure/azure-sdk-tools/blob/9ea6ba9c57116fa68ebbcc988adf8bccf58595dd/tools/http-fault-injector/Azure.Sdk.Tools.HttpFaultInjector/Program.cs#L48


Get story book running

Look through story book set up docs.
debug the terminal error that are stopping story book from running.
make some button variants to start off with in story book.
This might need re setting and installing.


Add command to CLI to generate secure random strings

I wrote command-line utility to generate a secure random string. It can be used, for example, to set Flask's SECRET_KEY.
The command is called with flask generate-secret [--length <length>] (length defaults to 30).

Needs a test and docs. Should mention something like "Use the flask generate-secret command to get a random value." in the SECRET_KEY docs.
I'm curious where you got the pattern you're using here. Seems weird to work backwards to get a string that's close to the desired length. I'd rather input the number of random bytes to start with and get a string of whatever length is necessary.
-b, --bytes byte length of initial random data
b64encode(os.urandom(n)).decode('UTF-8')

16 bytes (128 bits) is probably a sufficient default.

I don't see the point of using a base64 string considering that most flask config files can contain python code and thus backslash-escaped strings.
Also, I'm not sure whether this is really within the scope of flask.

Hmm, true, and we already mention how to generate a key as raw bytes in the docs. Although we should probably make it more clear outside the quickstart, in the config and session docs.

I would use hexlify instead of base64 to ensure a safer subset of ASCII. Whether asciifying is necessary.. I just wouldn't take unnecessary risks.

Actually, looks like I already added an example of how to generate it to the SECRET_KEY docs. I think I'm fine with keeping this a manual process.

Closing this because I don't think we need a built-in command for it. I'd rather the user understand how the secret is generated, which is already documented.


BUG - Opening apps opened other users jupyterlab servers for me

Context
I opened the xaitkappv3-d7dff58 app by @kcpevey and the maite-c383ebc by @dharhas and instead of opening the apps, a jupyterlab server was created as if I were kim and dharhas's users.  Afterwards, I checked the jhub-apps home page again and the xaitkappv3-d7dff58 and maite-c383ebc apps weren't listed anymore.
Maybe they were deleted, but still shown on jhub-apps home page and when I tried to open them jupyterhub forwarded me to jupyterlab?  I'm not sure.
Me as Kim in jupyterhub

Me as Dharhas in jupyterhub

Value and/or benefit
Bug report
Anything else?
No response

The way this works is by impersonating their user, so that part is not surprising. During the lead up to the release we did have weird routing issues where it would start lab instead of redirecting to the url of the 'app'. I don't remember exactly but this was some combination of the version of jupyterhub, jupyterlab and jhsingle-user-proxy that was causing the issue. I thought it was fixed in the release.
cc: @Adam-D-Lewis

weird routing issues where it would start lab instead of redirecting to the url of the 'app'.

This might be the case, will have to check app's creation commands to figure out what went wrong. I'll take a look.

I just hit this too. My situation:

Dharhas had a shared app that had been stopped.
I started the app (which led me to confirm I wanted to launch a server)
I waited for the server to spin up
When the server was up, it redirected me to Dharhas's JLab interface - I was impersonating him.
I went back to the app screen and clicked on the App link and it brought me back to Dharhas's Jlab.

We need to disable the ability to have general jupyterlab access and restrict to just the app. There may be some fine grained permissions in JHub/JLab that will allow this now.

This may be tangential but if user A starts a shared app of user B, but user A only is allowed to spawn say CPU instances, but user B is allowed both CPU and GPU, should user A be allowed to spawn the GPU instance as user B or not? Currently user A can spawn instances that they would have no access to if they were spawning their own app rather than a shared one.

IMO the user A ideally should be able to spinup the shared app with only the last saved configuration for the app. They should not be able to change a thing about it like server type, name, thumbnail etc.
Also note that, currently the starting of the shared app won't work as expected due the "fake" sharing ability we have: https://github.com/nebari-dev/jhub-apps/issues/138

Interestingly the problematic apps disappear from shared apps screen when a server for them gets spawned

before spawning  "My panel app"
after

But now that you linked https://github.com/nebari-dev/jhub-apps/issues/138, it seems to mention the same thing, right?

Taking a step back:

solving https://github.com/nebari-dev/jhub-apps/issues/138 would "solve" this issue in the sense of surprising behaviour for end-user, but would not solve the impersonation itself nor too broad permission scopes
we can configure "Real-time collaboration without impersonation": https://jupyterhub.readthedocs.io/en/stable/tutorial/collaboration-users.html - which we could start already
to only allow access to servers which are actually shared by the author we should use sharing codes https://jupyterhub.readthedocs.io/en/latest/tutorial/sharing.html which are coming in JupyterHub 5.0

How should we scope the work here? It looks like these are 3 tasks which all are critical to ensuring that user data is only shared when explicitly allowed and no impersonation takes place - do I see this right?

Just coming back to this issue @aktech did you have a chance to look into this?

solving https://github.com/nebari-dev/jhub-apps/issues/138 would "solve" this issue in the sense of surprising behaviour for end-user, but would not solve the impersonation itself nor too broad permission scopes

Yes, correct.

we can configure "Real-time collaboration without impersonation": jupyterhub.readthedocs.io/en/stable/tutorial/collaboration-users.html - which we could start already

Yes we can, but this is beyond the scope for app sharing requirements.

to only allow access to servers which are actually shared by the author we should use sharing codes jupyterhub.readthedocs.io/en/latest/tutorial/sharing.html which are coming in JupyterHub 5.0

Sharing code is also a good option for sharing temporarily (excellent feature to add later though), but initially we are more interested in sharing non-timebound access with a group or user via: https://jupyterhub.readthedocs.io/en/latest/reference/rest-api.html#operation/post-shares-server
Based on my reading of the sharing feature in JupyterHub 5.0, we will fix this issue after:

We implement app sharing using sharing APIs in 5.0: https://jupyterhub.readthedocs.io/en/latest/reference/rest-api.html and
fixing https://github.com/nebari-dev/jhub-apps/issues/138, this will also be solved when we stop showing all the apps to all the users (at the moment we show all the apps for all the users in the shared section)

Next steps:

I am working on writing an issue for implementing app sharing via 5.0, shall have it today.
Stop showing all the apps to everyone, remove this basically https://github.com/nebari-dev/jhub-apps/blob/6a5df08d5880ab930c58298c961f9cbe6ef6e117/jhub_apps/service/routes.py#L140-L142

Also, there is nothing that needs to be done to fix this one right now, as mentioned it will be fixed by implementing app sharing.


New warnings in HA 0.109.0b0

As the title says, HA is making some changes in 0.109 and so far I have seen these two warnings.
2020-04-22 15:40:33 WARNING (MainThread) [homeassistant.helpers.translation] smartthinq_sensors: the '.translations' directory has been moved, the new name is 'translations', starting with Home Assistant 0.111 your translations will no longer load if you do not move/rename this

2020-04-22 15:37:53 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for smartthinq_sensors doing I/O at custom_components/smartthinq_sensors/wideq/device.py, line 234: return requests.get(info_url, timeout=DEFAULT_TIMEOUT).json()

offtopic. Its great. my v1 frige and v2 washer work together. do you plan to set the temperature?
Not only sensor? but interaction too ...

As the title says, HA is making some changes in 0.109 and so far I have seen these two warnings.
2020-04-22 15:40:33 WARNING (MainThread) [homeassistant.helpers.translation] smartthinq_sensors: the '.translations' directory has been moved, the new name is 'translations', starting with Home Assistant 0.111 your translations will no longer load if you do not move/rename this

This was solved in other custom_component creating a soft link to the .translation directory, not so simple for me because I work with windows. I will think about best solution

2020-04-22 15:37:53 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for smartthinq_sensors doing I/O at custom_components/smartthinq_sensors/wideq/device.py, line 234: return requests.get(info_url, timeout=DEFAULT_TIMEOUT).json()

The only way to remove this warning is to create an external library for the API (wideq). May be in the future, but fortunatly the API seems working fine :)
Thanks for information.

offtopic. Its great. my v1 frige and v2 washer work together. do you plan to set the temperature?
Not only sensor? but interaction too ...

Iteration is not possible in ThinQ v2 for the moment, and implementing only for one version may create issue. So for the moment the component is only sensors.

@ollo69 more info here:
https://rc.home-assistant.io/blog/2020/04/21/release-109/#detection-of-blocking-io-in-the-event-loop

Thanks @ollo69


Handle missing file paths being passed to open()

Currently we panic if we pass a file path that does not exist to open(). This seems to be because we assume os::os_open doesn't fail and just blindly unwrap it.
I've added a few tests and I've made it bubble up the ValueError that os::os_open throws. I also removed the HashSet as this seemed redundant for only 4 elements.

Done @holygits 👍

As per failing tests: https://travis-ci.org/RustPython/RustPython/jobs/488432352#L714
The error type is now FileNotFoundError not ValueError


Upgrade requirements_docs.txt

Description
Upgrade requirements_docs.txt
Changes
Tests
Known Issues
Notes
requirements_dev.txt needed upgrades, but not sure if we want to change our syntax from >= to ==

mkdocs 9.3 dropped support for Python 3.7
pymdown-extensions 10.3 dropped support for Python 3.7

Checklist

[ ] My name is on the list of contributors (CONTRIBUTORS.md) in the pull request source branch.
[ ] I have updated the documentation to reflect my changes.

seeing how all the packages that we are using are dropping support for Python 3.7, I strongly recommend we do the same, we don't currently have anyone that requires Python 3.7 for their work

we don't currently have anyone that requires Python 3.7 for their work

we don't know our users, so how can we know?

we don't currently have anyone that requires Python 3.7 for their work

we don't know our users, so how can we know?

Currently, Sarah appears to be the sole user of the SDK, and she has transitioned to Python 3.8+. Users on Python 3.7 would probably upgrade given that many other packages now require 3.8+. If they have any concerns, they can reach out to us via our discussions or other means. We'll either assist them directly or we'll reconsider certain updates based on their feedback.


Use system environment for gfal2 stageout

Pull request in CRAB3 to save environment: https://github.com/dmwm/CRABServer/pull/5193
Why this is needed? Discussions starting from: https://github.com/dmwm/CRABServer/issues/5186#issuecomment-206248679 and https://hypernews.cern.ch/HyperNews/CMS/get/comp-ops/2863/1.html and https://hypernews.cern.ch/HyperNews/CMS/get/computing-tools/966.html
@belforte

@juztas, Justas, this is tested, right?

crab3 yes, prod no. But in the end, crab3 and prod is using the same gfal2. A bit more discussions are here: https://github.com/dmwm/CRABServer/pull/5193

We don't need to merge it for testbed, leave it open and I'll test it this week.

Alan, don't worry about it. I am testing this now.

Hi Justas,
We are getting following error on the test. Do you know what could be the problem. It might not be related to your patch.
StageOutError
Message: 2016-04-25T11:02:57 : Command exited non-zero
ErrorCode : 60311
ModuleName : WMCore.Storage.StageOutError
MethodName : init
ErrorType : GeneralStageOutFailure
ClassInstance : None
FileName : /var/lib/condor/execute/dir_955045/glide_BSiHmp/execute/dir_960710/job/WMCore.zip/WMCore/Storage/StageOutError.py
ClassName : None
Command : #!/bin/bash
env -i X509_USER_PROXY=$X509_USER_PROXY bash -c '. $PWD/startup_environment.sh; printenv; date; gfal-copy -vvv -t 2400 -T 2400 -p   file:///var/lib/condor/execute/dir_955045/glide_BSiHmp/execute/dir_960710/job/WMTaskSpace/logArch1/logArchive.tar.gz srm://cmseos.fnal.gov:8443/srm/v2/server?SFN=/lustre/unmerged/logs/prod/2016/4/25/mohapatr_MonteCarlo_eff_T3USOSG_test2_160422_221238_3093/Production/0000/0/3cc26164-0af8-11e6-880b-00221959e7c0-0-0-logArchive.tar.gz'
EXIT_STATUS=$?
echo "gfal-copy exit status: $EXIT_STATUS"
if [[ $EXIT_STATUS != 0 ]]; then
echo "Non-zero gfal-copy Exit status!!!"
echo "Cleaning up failed file:"
env -i X509_USER_PROXY=$X509_USER_PROXY bash -c '. $PWD/startup_environment.sh; printenv; date; gfal-rm -vvv -t 600 srm://cmseos.fnal.gov:8443/srm/v2/server?SFN=/lustre/unmerged/logs/prod/2016/4/25/mohapatr_MonteCarlo_eff_T3USOSG_test2_160422_221238_3093/Production/0000/0/3cc26164-0af8-11e6-880b-00221959e7c0-0-0-logArchive.tar.gz '
exit 60311
fi
exit 0
    LineNumber : 32
    ErrorNr : 0
    ExitCode : 151

prod logs not always easiest to debug. Can you provide me full logs tarball? somewhere in lxplus public?

Hi Justas, I can't access the WN. It is running in OSG site.
Here is another line int the log. I will send link to your email for full condor log file.
bash: /var/lib/condor/execute/dir_955045/glide_BSiHmp/execute/dir_960710/job/WMTaskSpace/stageOut1/startup_environment.sh: No such file or directory
bash: gfal-copy: command not found

Seangchan, don't spend time on it please. I can test it tomorrow or on Wed.

Hi Alan, Actually, I am not spending time on this. Actually, Ajit is testing OSG with gfal2. So I had to set it up for him anyway, that is why we are running the test. :smile:

Ajit found the problem. It seems the location of startup_environment.sh is not match the location the command is looking for. Detail is described above.

Ok, please test this. I tested this on WN and seems to work:
Welcome to slot1<EMAIL_ADDRESS>Your condor job is running with pid(s) 125829.
bash-4.1$ pwd
/scratch/6244499.cream02.iihe.ac.be/glide_vmiu0J/execute/dir_125807
bash-4.1$ echo $PWD
/scratch/6244499.cream02.iihe.ac.be/glide_vmiu0J/execute/dir_125807
bash-4.1$ export JOBSTARTDIR=$PWD
bash-4.1$ cd WMTaskSpace/cmsRun/
bash-4.1$ ls
PSet.py  PSet.pyc  __init__.py  __init__.pyc
bash-4.1$ env -i PROXY=temp_proxy JOBSTARTDIR=$JOBSTARTDIR bash -c 'echo $JOBSTARTDIR; echo $PROXY'
/scratch/6244499.cream02.iihe.ac.be/glide_vmiu0J/execute/dir_125807
temp_proxy
bash-4.1$ env -i PROXY=temp_proxy bash -c 'echo $PWD; echo $PROXY'
/scratch/6244499.cream02.iihe.ac.be/glide_vmiu0J/execute/dir_125807/WMTaskSpace/cmsRun
temp_proxy

This means that CRAB3 also need to have a change in CRAB3 code to export this variable and also in crab3 wmcore branch.

P.S. I was not aware that production goes into directory and executes not from the main dir. This should solve it.
@mmascher tag you for CRAB3 change

maybe Brian's idea to save the env. in structure in a python object,
rather than on file, had its merits ?

@bbockelm comments?

@belforte what you don't like in this?

@ticoann @amaltaro comments? tests?
@jmarra13 this has to go also to crab3 branch (If Gurus accept it ;))) ), also https://github.com/dmwm/WMCore/commit/112598d4978e6b6960bdb38bf2da9b280bc36d4a which is not available in crab3 branch.

Hi Justas, We have still problem. The problem seems to be different site using different gfal2 version and that case some errors related to check sum. (Actually I don't know the detail, but Ajit is running the test and he is the one investigating. :smile:) So I will hold on to this for a while until I talk to Ajit. But I can merge the crab version and create the new tag if that is needed. Thanks

Mh... Maybe this issue Ajit is getting? https://github.com/dmwm/WMCore/pull/6160
For crab, @mmascher ?


walker of nested maps only finds 1st occurence

New to specter so this might just be me who is confused, but I would have expected the below to find all maps with a :c key ie {:a 1, :b {:c 2}, :c "test"} {:c 2}), but I only get the first hit:
(select (walker :c)  {:a 1 :b {:c 2} :c "test"})
> ({:a 1, :b {:c 2}, :c "test"})

walker does walk the structure as shown by:
(select (walker :c)  {:a 1 :b {:c 2} :d "test"})
> ({:c 2})

That's the correct behavior of walker. It walks until reaching something matching that predicate. Here's how to define a walker that continues walking after matching a value:
(use 'com.rpl.specter)
(use 'com.rpl.specter.macros)

(declarepath MapKeyWalker [match-fn])
(providepath MapKeyWalker
  [walker
   (continue-then-stay
     ALL LAST (params-reset MapKeyWalker))])

(select (MapKeyWalker :c) {:a 1 :b {:c 2} :c "test"})
;; => ({:c 2} {:c "test", :b {:c 2}, :a 1})

Ok, but how is that consistent with:
(select (walker number?)
          {2 [1 2 [6 7]] :a 4 :c {:a 1 :d [2 nil]}})
> [2 1 2 1 2 6 7 4]

Again sorry if I am missing something obvious here.

By "walk until" I don't mean "stop on the first match in the structure". I mean "stop on values that match the function". So, for example:
(select (walker :c) {:a {:c 1} :b {:c 2} :d {:e 1}})
;; => ({:c 2} {:c 1})


Error in step1

Hi,
I'm trying step 1: bash HashCounting.sh 6 33 22
but I get some problems with the parallel call. The option --no-notice doesn't seem to be available in my version - so I have removed it.
This is what I get, with bash -x (the CreateHash code seems to be working, so I have commented the lines after the first execution):
bash -x HashCounting.sh 6 33 22 \+ '[' 3 -ne 3 ']' \+ numThreads=6 \+ kmerLen=33 \+ export hashSize=22 \+ hashSize=22 \+ mkdir Logs mkdir: cannot create directory Logs': File exists
++ grep '^-'
++ wc -l
++ ls -l original_reads/SRR492065.10kReads.plusSpike.fastq original_reads/SRR492066.10kReads.plusSpike.fastq original_reads/SRR492182.10kReads.plusSpike.fastq                                                 original_reads/SRR492183.10kReads.plusSpike.fastq original_reads/SRR492184.10kReads.plusSpike.fastq original_reads/SRR492185.10kReads.plusSpike.fastq original_                                                reads/SRR492186.10kReads.plusSpike.fastq original_reads/SRR492187.10kReads.plusSpike.fastq original_reads/SRR492188.10kReads.plusSpike.fastq original_reads/SRR                                                492189.10kReads.plusSpike.fastq original_reads/SRR492190.10kReads.plusSpike.fastq original_reads/SRR492191.10kReads.plusSpike.fastq original_reads/SRR492192.10                                                kReads.plusSpike.fastq original_reads/SRR492193.10kReads.plusSpike.fastq original_reads/SRR492194.10kReads.plusSpike.fastq original_reads/SRR492195.10kReads.pl                                                usSpike.fastq original_reads/SRR492196.10kReads.plusSpike.fastq original_reads/SRR492197.10kReads.plusSpike.fastq
+ numInputFiles=18
++ seq 1 18
+ parallel -j 6 --halt-on-error 2 'echo $(date) hashing reads in file {};
python LSA/hash_fastq_reads.py -r {} -i original_reads/ -o hashed_reads/ >> Logs/HashReads.log 2>&1' ::: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
parallel: Warning: YOU ARE USING --tollef. IF THINGS ARE ACTING WEIRD USE --gnu.
parallel: Warning: --tollef is obsolete and will be retired 20140222.
parallel: Warning: See: http://lists.gnu.org/archive/html/parallel/2013-02/msg00018.html
Thu Feb 4 23:55:26 GMT 2016 hashing reads in file {}
/bin/bash: :::: command not found
/bin/bash: 1: command not found
/bin/bash: 2: command not found
parallel: This job failed:
/bin/bash -c :::
/bin/bash: 3: command not found
+ '[' 127 -ne 0 ']'
+ echo 'printing end of last log file...'
printing end of last log file...
+ tail Logs/HashReads.log
/bin/bash: 4: command not found
fr = int(arg) - 1
ValueError: invalid literal for int() with base 10: '{}'
Traceback (most recent call last):
File "LSA/hash_fastq_reads.py", line 54, in
fr = int(arg) - 1
ValueError: invalid literal for int() with base 10: '{}'
Traceback (most recent call last):
File "LSA/hash_fastq_reads.py", line 54, in
fr = int(arg) - 1
ValueError: invalid literal for int() with base 10: '{}'
+ exit 1`
Any ideas of what this could be?
  Andres

Hi all,
the problem was in the library versions - with more up to date libraries I managed to go through the test data.
 Andres


scrape examples

simplify and improve doc generation with xtask
don't use surf in examples
simplify examples a bit
don't request scopes for app access token
remove not needed env

bors cancel

bors cancel


switch to tokio::process

Resolves #1652.
As mentioned in the issue, reqwest already depends on tokio, so this removes a large section of the new dependency tree. tokio::process also uses non-blocking IO for windows, which async-process does not

@microsoft-github-policy-service agree company="Neon, Inc."

For non-wasm (which is the only thing this touches), you are already depending on tokio through reqwest and AFAIK there are really no good alternatives in the Rust ecosystem right now:

isahc is nice but depends on libcurl which makes cross compilation harder, and it's not very actively maintained.
Using hyper directly is an option, smol_hyper integrates it with smol as an alternative to tokio. But you'd have to write a bunch of (glue) code yourself on top if you need cookie handling, redirect handling, or such.

Yeah there is already an (optional) dependency on tokio through reqwest but most people will probably enable reqwest anyways, so they already pull in tokio. At least that's what we are doing as users of the azure SDK.
The current state pulls in the async-io crate unconditionally, which is IMO worse because that way, a lot of users end up depending on both async-io as well as tokio.
If you really want, it is possible to make the dependency optional by adding a crate-private module that either contains a reexport of tokio's Command struct, or if the tokio dependency is not enabled, contains a struct called Command with all the APIs we use, being a wrapper of std's Command (we cannot reexport std's Command directly because some APIs are async).

We actually do have use cases and budding implementation that will not use tokio but monoio in our feature branch. tokio will still be our default async runtime via reqwest.
That said, this branch will eventually be replaced but community-supported for some time. While no one can say whether the whole community is using tokio, it may be a safe assumption until proven otherwise and then we could implement @arpad-m's idea.
@ctaggart @demoray @jamesbell what do you think? For the stated reasons I'm all for replacing unmaintained async-process as mentioned in #1652. At this time for this branch, I wonder how strict we want to maintain a no-hard-dependency stance on tokio. Do you know of anyone using a different HTTP stack and/or async runtime?

@heaths I think this sounds like a great proposal and a good path forward. I think it makes sense to not have tokio be a hard dependency, but I feel for monoio it would make sense to not use async-io either.
What would be the next steps for this pull request to get merged?

@arpad-m could you add a trait much like we did for the HttpClient stack and do roughly what you suggested above so that the code uses tokio's Command by default but someone could replace it with another impl? It may not get used, but at least we're not painted into a corner and the official source we are working on will likely be pulling a lot of this source anyway, so it'll set a good precedent. In fact, the feature/track2 branch was branched from main but is getting refactored quite a bit. Still, much of the existing core implementation will be retained.

@heaths sounds good to me (although I'm not the PR author, my colleague Conrad is). For clarification, would you prefer the use of #[async_trait] instead of the language builtin async trait support, as the current MSRV is 1.74.0?

@heaths sounds good to me (although I'm not the PR author, my colleague Conrad is). For clarification, would you prefer the use of #[async_trait] instead of the language builtin async trait support, as the current MSRV is 1.74.0?

For now, let's stay consistent with elsewhere in the code and stick with #[async_trait]. I'd rather resolve that as a separate PR at some point in the future. The MSRV for the official branch is still somewhat up in the air.

main branch has been moved to legacy. Closing old PRs with no timely author response. Please reopen once you address feedback.


Chat: Display Enhanced Context settings on first chat

CLOSE https://github.com/sourcegraph/cody/issues/2839

As discussed with @toolmantim in this figma comment thread, we will open Enhanced Settings on first chat by default.
Add dropdown button for Enhanced Context Settings
Existing button for Enhanced Context Settings is now for toggling enhanced context enablement.

Test plan

Updated e2e tests

To test this manually:

Open a new Cody Chat
The Enhanced Context settings should be opened by default
Send a new message
the Enhanced Context settings windows is closed when you move focus to the chat input box

After
First chat for Dot Com users:

First chat for enterprise users:

@toolmantim before I fix the e2e tests to reflect the new behavior, can you take a look and let me know if this aligns with what you had in mind?

@abeatrix Nice! Yeah checking it out now. Quick one: I spotted CodyVSCodeExtension:useEnhancedContextToggler:clicked event isn't triggered when you click it via the new button.

@abeatrix Nice! Yeah checking it out now. Quick one: I spotted CodyVSCodeExtension:useEnhancedContextToggler:clicked event isn't triggered when you click it via the new button. (edit: we may want to include a metadata property of the source, so we can tell where they click it from — popover or input button)

added a new event useEnhancedContextInputToggler event for the new icon click

Just pushed a bunch of style fixes, and the only thing left I think is some of the keyboard accessibility fixes:

Tabbing to enhanced context indicator button and hitting space/enter shouldn't refocus the input, that should only happen when context indicator button is clicked. Pressing escape while the enhanced context indicator button is focused should focus the message input.
If you shift-tab from the popover checkbox back into the message input, the popover should be dismissed

If you shift-tab from the popover checkbox back into the message input, the popover should be dismissed
@toolmantim I couldn't get this to work, but I will work on it in a follow-up as this is an existing behavior. For now, users can hit Escape when the input box is focused though to dismiss the popover.


Fixes for #19 and #20

I have fixed the issues I submitted.  Is it ok if I release a new point release of the plugin?  I can put it on my build server if you want.

Great! I just did the merge online. By the way, what you means by "put it on my build server"?

Just that I can build it manually and publish to the grails plugins repo or I can put it on my hudson server to do the same thing so it's easier in the future.  I would like to get these changes as soon as possible.
If you want to release it yourself, wait a minute since I have one more small change for you to pull in.  Thanks!

Got it! I think you can publish the plugin to Grails plugins repo but I
insist that the documentation should be in sync with the release.
Also, I think it is good to port the project documentation from Google
Code at http://code.google.com/p/jquery-validation-ui-plugin/ to Grails
plugin documentation which similar to
http://limcheekin.github.com/mahout-recommender in this release*. What do
you think?

On Wed, Jan 11, 2012 at 11:49 AM, Brian Saville <
<EMAIL_ADDRESS>
wrote:

Just that I can build it manually and publish to the grails plugins repo
or I can put it on my hudson server to do the same thing so it's easier in
the future.  I would like to get these changes as soon as possible.
If you want to release it yourself, wait a minute since I have one more
small change for you to pull in.  Thanks!

Reply to this email directly or view it on GitHub:
https://github.com/limcheekin/jquery-validation-ui/pull/1#issuecomment-3441649

Sure, I'll get on it.  Looks like you already have some of the gh-pages stuff setup, so I'm creating a branch in my fork and will send a pull request for it.  I'm following the instructions here: http://www.cacoethes.co.uk/blog/groovyandgrails/github-pages-publish-your-grails-plugin-docs.
I actually haven't done the github pages for any of my projects, so we'll see how it goes :)

Yeah, I am following that instructions too!
By refer to http://grails.org/doc/latest/guide/conf.html#docengine and
gh-pages branch of mahout-recommender, you should able to work it out.
Do remember to add your name to the plugin author, your contributions are
very much appreciated. :)
On Wed, Jan 11, 2012 at 12:11 PM, Brian Saville <
<EMAIL_ADDRESS>
wrote:

Sure, I'll get on it.  Looks like you already have some of the gh-pages
stuff setup, so I'm creating a branch in my fork and will send a pull
request for it.  I'm following the instructions here:
http://www.cacoethes.co.uk/blog/groovyandgrails/github-pages-publish-your-grails-plugin-docs
.
I actually haven't done the github pages for any of my projects, so we'll
see how it goes :)

Reply to this email directly or view it on GitHub:
https://github.com/limcheekin/jquery-validation-ui/pull/1#issuecomment-3441811


Could not find a package configuration file provided by "tf2_sensor_msgs"

--- stderr: pointcloud_to_laserscan
CMake Error at /opt/ros/melodic/share/catkin/cmake/catkinConfig.cmake:83 (find_package):
  Could not find a package configuration file provided by "tf2_sensor_msgs"
  with any of the following names:

    tf2_sensor_msgsConfig.cmake
    tf2_sensor_msgs-config.cmake

  Add the installation prefix of "tf2_sensor_msgs" to CMAKE_PREFIX_PATH or
  set "tf2_sensor_msgs_DIR" to a directory containing one of the above files.
  If "tf2_sensor_msgs" provides a separate development package or SDK, be
  sure it has been installed.
Call Stack (most recent call first):
  CMakeLists.txt:4 (find_package)

---
Failed   <<< pointcloud_to_laserscan [3.47s, exited with code 1]

nisa@nisa:~$ sudo apt-get install ros-melodic-tf2-sensor-msgs


Fix code scanning alert - Inclusion of functionality from an untrusted source

Tracking issue for:

[ ] https://github.com/pablosambuco/caststatusserver/security/code-scanning/6

:)


Add Qwant

Hi,
have just found your application on F-Droid and would like to ask you to add the search engine Qwant. Just use https://www.qwant.com/?q=%s as url.
Thank you

Sounds easy enough. Would you be able to provide an icon to use for them? If they have a branding page, or official icon for people to use I should be able to bring it in line with the rest in Just Search.

Thank you for your answer.
I found this page: Qwant Press. There you can download a zip with the logo in different file formats (png, svg, jpg ,...).

This should do it, thanks :)

Hi,
I was about to open a similar issue for StartPage, but don't you think it would be more useful to have an option allowing users to add new search engines at will?

I thought I had an issue open for this already. Opened #11

I agreed that there should be an option for custom search engines. But Qwant and Startpage are relatively popular for people who focus on privacy, so I would suggest adding them both.
Especially when there is an activity later on, it doesn't matter how many search engines are available.


[Feature Request] Add a way to limit teams the bot can be added to.

For testing / governance purposes, it may be beneficial to have a way to limit the teams the bot can be added too.
Something like having a comma delimited "Test Team" config setting that lists the teams the bot is allowed to be installed on, but causes a rejection message during install attempts from all other teams.

Thank you for your suggestion! We will inform the corresponding team about this feature request.

For this microsoft-teams-apps-icebreaker repository, we are currently only making changes to fix critical bugs or deployment failures. Please consider forking the repository to implement your improvement and post back here if you're successful.

Thank you for submitting this issue, as we work to ensure consistent responses with items logged in our issues list, we are working to address these items that did not get responses. Please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at moment and no response is received, we will close out the issue in 3 business days. You may also always open a new issue or respond here if something does come back up. Thank you!


Generating rgb from hex 8 values is wrong

Alpha is the highest order byte, but FromHexStringValues.from_hex8 treats its second parameter as the red byte.

Implemented by 0f99e80.


Build system should parse the Xilinx tool output and generate stats

Start simple with things like;

Number of warnings generated in each stage
Output bit file size

Then move onto things like;

The number of LUTs used
Timing information

Then do all the above for each individual directory.

See https://github.com/timvideos/HDMI2USB/wiki/Xilinx-Parsing-Tools too

https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/62

This issue was moved to timvideos/HDMI2USB-misoc-firmware#152


No name is provided for combo box: A11y_VS Code extension for API Center_Open API Documentation_Combobox_Name Role Value.

GitHub Tags
#A11yTCS; #A11ySev2; #Mac; #WCAG4.1.2; #GH_VSCodeextensionforAPICenter_Mac_Apr2024; #DesktopApp; #VS Code Extension for API Center; #Name Role Value; #AILimited; #A11yMAS; #device;
Environment Details:
Application Name: VS Code Extension for API Center
macos sonoma version:14.4.1
Repro Steps:

Create an API center in azure portal.
Open Visual studio Code.
Tab till API center extension in the left side panel and press enter.
Tab till definition under the Api name which you have created, and press enter.
The name which you have provided to the definition will appear for ex-"openapi4", right click on it.
Go to "Open API Documentation" using the down arrow and press enter.
Demo conference API screen will appear.
Tab till combo box.
Verify whether the name is provided for combo box or not.

Actual Result:
No name is provided for combo box.
Same issue is also observed for the button available in the code.
Expected Result:
Name should be provided for combo box.
User Impact:
Screen reader users will not get the information about the control if name is not provided.
Attachment:

Note Issue1

@formulahendry Can you please provide us the standalone sample app or Code pen link to route this bug to external team.

IRT Bug logged: https://dev.azure.com/CSS-IRT/CSS IRT/_workitems/edit/220345

GitHub Tags:
#External;#External:SwaggerUI;#eDAD:3p:220345;ThirdParty;

External bug: https://dev.azure.com/CSS-IRT/CSS IRT/_workitems/edit/220345


Fixed #30408 -- Fixed crash when adding check constraints with LIKE operator on Oracle and PostgreSQL.

The LIKE operator wildcard generated for contains, startswith, endswith and
their case-insensitive variant lookups was conflicting with parameter
interpolation on CREATE constraint statement execution.
Ideally we'd delegate parameters interpolation in DDL statements on backends
that support it but that would require backward incompatible changes to the
Index and Constraint SQL generating methods.
Thanks David Sanders for the report.

buildbot, test on oracle.

buildbot, test on oracle.

@charettes Thanks! :champagne:

Thanks for the merge @felixxm !


Synthesis failed for nodejs-dataproc

Hello! Autosynth couldn't regenerate nodejs-dataproc. :broken_heart:
Here's the output from running synth.py:
ule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:42:1
DEBUG: Rule 'gapic_generator_python' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "8d11f06b408ac5f1c01da3ca17f3a75dc008831509c5c1a4f24f9bde37792a57"
DEBUG: Call stack for the definition of repository 'gapic_generator_python' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:224:1
DEBUG: Rule 'com_googleapis_gapic_generator_go' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "12bfed7873f085093cd60615bd113178ecf36396af0c2ca25e6cd4d4bebdd198"
DEBUG: Call stack for the definition of repository 'com_googleapis_gapic_generator_go' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:261:1
DEBUG: Rule 'gapic_generator_typescript' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "ca322b5e7b0d03b3cc44a90444e3a7f944c9ba3345f0505ee48c8e715d19dd95"
DEBUG: Call stack for the definition of repository 'gapic_generator_typescript' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:280:1
DEBUG: Rule 'gapic_generator_csharp' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "40ddae63d2729ef5ccbd8b60123327ea200ce9400d0629238193ff530dcaea18"
DEBUG: Call stack for the definition of repository 'gapic_generator_csharp' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:318:1
DEBUG: Rule 'bazel_skylib' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "1dde365491125a3db70731e25658dfdd3bc5dbdfd11b840b3e987ecf043c7ca0"
DEBUG: Call stack for the definition of repository 'bazel_skylib' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:35:1
Analyzing: target //google/cloud/dataproc/v1:dataproc-v1-nodejs (1 packages loaded, 0 targets configured)
INFO: Call stack for the definition of repository 'npm' which is a yarn_install (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/build_bazel_rules_nodejs/internal/npm_install/npm_install.bzl:411:16):
 - <builtin>
 - /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/build_bazel_rules_nodejs/index.bzl:87:5
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:293:1
ERROR: An error occurred during the fetch of repository 'npm':
   yarn_install failed: yarn install v1.19.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info If you think this is a bug, please open a bug report with the information provided in "/home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/gapic_generator_typescript/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
 (error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"404 Not Found\"".
)
ERROR: /home/kbuilder/.cache/synthtool/googleapis/google/cloud/dataproc/v1/BUILD.bazel:275:1: //google/cloud/dataproc/v1:dataproc_nodejs_gapic depends on @gapic_generator_typescript//:protoc_plugin in repository @gapic_generator_typescript which failed to fetch. no such package '@npm//@bazel/typescript': yarn_install failed: yarn install v1.19.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info If you think this is a bug, please open a bug report with the information provided in "/home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/gapic_generator_typescript/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
 (error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"404 Not Found\"".
)
ERROR: Analysis of target '//google/cloud/dataproc/v1:dataproc-v1-nodejs' failed; build aborted: no such package '@npm//@bazel/typescript': yarn_install failed: yarn install v1.19.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info If you think this is a bug, please open a bug report with the information provided in "/home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/gapic_generator_typescript/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
 (error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"404 Not Found\"".
)
INFO: Elapsed time: 1.008s
INFO: 0 processes.

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/nodejs-dataproc/synth.py", line 22, in <module>
    library = gapic.node_library('dataproc', version)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 52, in node_library
    return self._generate_code(service, version, "nodejs", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 183, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', '--max_idle_secs=240', 'build', '//google/cloud/dataproc/v1:dataproc-v1-nodejs']' returned non-zero exit status 1.
2020-08-06 04:14:15,086 autosynth [ERROR] > Synthesis failed
2020-08-06 04:14:15,086 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at e3cd735 docs: change relative URLs to absolute URLs to fix broken links. (#421)
2020-08-06 04:14:15,092 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-08-06 04:14:15,097 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 690, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 539, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 670, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 375, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 273, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Fix windows build

The windows failure at this point is due to mingw not supporting c++17.
I think that we need to expose more restricted headers to libmamba so that (too) modern C++ features are not required.

mingw not supporting c++17

I'm clueless on windows, but searching a bit the web I found some solutions to use c++17 with mingw (I think).
Or is it just a hacky way to do it?
Do we have another solution? I saw that you pinged Serge at some point in the internal chat, but I can't find the message anymore. If you have any ideas on how to make this work I'm happy to look into it. Maybe I should do a dualboot with windows here.

This is now included in #19, closing.


RigidBody's bouncing fails to stop.

Godot version
3.3.4
System information
Solus OS, AMD CEDAR (DRM 2.50.0 / 5.13.12-193.current, LLVM 12.0.1), GLES3
Issue description
Hey there, been trying Godot for a while and loving to test new stuff! but...
When setting the bounce setting in RigidBody, It'll continue to bounce on a StaticBody. even when setting it to a really low amount (0.2) it'll do micro-bounces which makes the rigidbody's global position not stop changing.
Steps to reproduce
1 - make rigidbody and give it a rectangle collision shape
2 - make another scene and put a staticbody on it, and then put rigidbody on top
3 - set rigidbody's bounce setting to any amount
4 - test-play
Minimal reproduction project
Problematic Plastic.zip

Closing as duplicate of #25186.


Add docs for chars concept

The chars concept is listed in the config.json's concepts key, but doesn't have its corresponding files in the concepts/chars directory.

Fixed by #199 which removed the chars concept.


Could not authenticate upload image with option possibly_sensitive

Hello Everybody,
I use method upload to upload image. It works fine if I do not put option possibly_sensitive. Otherwise, It returns error that "Could not authenticate you" when I put the possibly_sensitive.
Any idea?
Thanks.

hello an information,
I have a very similar problem,
I can not upload images to twitter
my code is that:
media = @post.image.path(:original).to_s
        images = media.split('?')
        media = images[0]
        response = access_token.post(Rails.application.secrets.twitter['urls']  ['post_with_media_timeline'], feed.merge('media' => media, 'status' => @post.text_no_html), {'Content-Type' => 'multipart/form-data'})

any idea for a bug??
thanks.