Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 1
744
| labels
stringlengths 4
574
| body
stringlengths 9
211k
| index
stringclasses 10
values | text_combine
stringlengths 96
211k
| label
stringclasses 2
values | text
stringlengths 96
188k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
18,536
| 24,553,317,637
|
IssuesEvent
|
2022-10-12 14:08:24
|
GoogleCloudPlatform/fda-mystudies
|
https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies
|
closed
|
[Android] App is crashing in the following scenario
|
Bug Blocker P0 Android Process: Fixed Process: Tested QA Process: Tested dev
|
**Steps:**
1. Sign in and complete the passcode process
2. Click on any enrolled study
3. Click on 'Home' icon
4. Click on 'Hamburger' menu
5. Sign out
6. Click on 'Sign in' and Verify
**AR:** App is crashing in the above scenario
**ER:** App should not crash in the above scenario
|
3.0
|
[Android] App is crashing in the following scenario - **Steps:**
1. Sign in and complete the passcode process
2. Click on any enrolled study
3. Click on 'Home' icon
4. Click on 'Hamburger' menu
5. Sign out
6. Click on 'Sign in' and Verify
**AR:** App is crashing in the above scenario
**ER:** App should not crash in the above scenario
|
process
|
app is crashing in the following scenario steps sign in and complete the passcode process click on any enrolled study click on home icon click on hamburger menu sign out click on sign in and verify ar app is crashing in the above scenario er app should not crash in the above scenario
| 1
|
179,296
| 21,559,251,253
|
IssuesEvent
|
2022-04-30 23:54:11
|
classicvalues/tree.minal
|
https://api.github.com/repos/classicvalues/tree.minal
|
opened
|
CVE-2022-29078 (High) detected in ejs-2.5.7.tgz, ejs-3.1.6.tgz
|
security vulnerability
|
## CVE-2022-29078 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ejs-2.5.7.tgz</b>, <b>ejs-3.1.6.tgz</b></p></summary>
<p>
<details><summary><b>ejs-2.5.7.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-2.5.7.tgz">https://registry.npmjs.org/ejs/-/ejs-2.5.7.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/sails/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- sails-1.5.2.tgz (Root Library)
- :x: **ejs-2.5.7.tgz** (Vulnerable Library)
</details>
<details><summary><b>ejs-3.1.6.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz">https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- :x: **ejs-3.1.6.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/classicvalues/tree.minal/commit/28e002f3d975b391715e8f2a6771b802adeea4cb">28e002f3d975b391715e8f2a6771b802adeea4cb</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).
<p>Publish Date: 2022-04-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-29078>CVE-2022-29078</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~</a></p>
<p>Release Date: 2022-04-25</p>
<p>Fix Resolution: ejs - v3.1.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-29078 (High) detected in ejs-2.5.7.tgz, ejs-3.1.6.tgz - ## CVE-2022-29078 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ejs-2.5.7.tgz</b>, <b>ejs-3.1.6.tgz</b></p></summary>
<p>
<details><summary><b>ejs-2.5.7.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-2.5.7.tgz">https://registry.npmjs.org/ejs/-/ejs-2.5.7.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/sails/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- sails-1.5.2.tgz (Root Library)
- :x: **ejs-2.5.7.tgz** (Vulnerable Library)
</details>
<details><summary><b>ejs-3.1.6.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz">https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- :x: **ejs-3.1.6.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/classicvalues/tree.minal/commit/28e002f3d975b391715e8f2a6771b802adeea4cb">28e002f3d975b391715e8f2a6771b802adeea4cb</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).
<p>Publish Date: 2022-04-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-29078>CVE-2022-29078</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~</a></p>
<p>Release Date: 2022-04-25</p>
<p>Fix Resolution: ejs - v3.1.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve high detected in ejs tgz ejs tgz cve high severity vulnerability vulnerable libraries ejs tgz ejs tgz ejs tgz embedded javascript templates library home page a href path to dependency file application package json path to vulnerable library application node modules sails node modules ejs package json dependency hierarchy sails tgz root library x ejs tgz vulnerable library ejs tgz embedded javascript templates library home page a href path to dependency file application package json path to vulnerable library application node modules ejs package json dependency hierarchy x ejs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the ejs aka embedded javascript templates package for node js allows server side template injection in settings this is parsed as an internal option and overwrites the outputfunctionname option with an arbitrary os command which is executed upon template compilation publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ejs step up your open source security game with whitesource
| 0
|
90,332
| 10,678,880,599
|
IssuesEvent
|
2019-10-21 18:09:54
|
PeterCamilleri/test65
|
https://api.github.com/repos/PeterCamilleri/test65
|
closed
|
Rename option
|
documentation enhancement
|
The debug option should be renamed to verbose like:
-v or --verbose
The version option should just be:
--version
This will be more in line with user expectations.
|
1.0
|
Rename option - The debug option should be renamed to verbose like:
-v or --verbose
The version option should just be:
--version
This will be more in line with user expectations.
|
non_process
|
rename option the debug option should be renamed to verbose like v or verbose the version option should just be version this will be more in line with user expectations
| 0
|
101,243
| 21,634,740,792
|
IssuesEvent
|
2022-05-05 13:18:57
|
appsmithorg/appsmith
|
https://api.github.com/repos/appsmithorg/appsmith
|
closed
|
[Bug]: TypeError for debuggersaga where reading name from undefined plugin
|
Bug Frontend Needs Triaging BE Coders Pod Actions Pod
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
Reading values from undefined
<img width="651" alt="Screenshot 2022-05-05 at 2 13 59 PM" src="https://user-images.githubusercontent.com/7565635/166890091-ae6f9693-558d-43f2-89b3-e7f38eaa291c.png">
### Steps To Reproduce
1. View Mode of an application
2. See console
### Public Sample App
https://app.appsmith.com/applications/60d72903ee9aa1792c5bf168/pages/614d9b9e18a27e5288afa99d?branch=master
### Version
Both
|
1.0
|
[Bug]: TypeError for debuggersaga where reading name from undefined plugin - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
Reading values from undefined
<img width="651" alt="Screenshot 2022-05-05 at 2 13 59 PM" src="https://user-images.githubusercontent.com/7565635/166890091-ae6f9693-558d-43f2-89b3-e7f38eaa291c.png">
### Steps To Reproduce
1. View Mode of an application
2. See console
### Public Sample App
https://app.appsmith.com/applications/60d72903ee9aa1792c5bf168/pages/614d9b9e18a27e5288afa99d?branch=master
### Version
Both
|
non_process
|
typeerror for debuggersaga where reading name from undefined plugin is there an existing issue for this i have searched the existing issues description reading values from undefined img width alt screenshot at pm src steps to reproduce view mode of an application see console public sample app version both
| 0
|
14,428
| 17,480,661,671
|
IssuesEvent
|
2021-08-09 01:13:42
|
googleapis/python-spanner
|
https://api.github.com/repos/googleapis/python-spanner
|
closed
|
tests.system.test_system.TestBackupAPI: test_restore_to_diff_instance failed
|
api: spanner type: process flakybot: issue flakybot: flaky
|
This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 2487800e31842a44dcc37937c325e130c8c926b0
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/306a2e02-87cb-4be9-be31-37456ec7a8a2), [Sponge](http://sponge2/306a2e02-87cb-4be9-be31-37456ec7a8a2)
status: failed
<details><summary>Test output</summary><br><pre>target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fe795521b20>>)
predicate = <function if_exception_type.<locals>.if_exception_type_predicate at 0x7fe795a5a5e0>
sleep_generator = <generator object exponential_sleep_generator at 0x7fe7954feb30>
deadline = 60, on_error = None
def retry_target(target, predicate, sleep_generator, deadline, on_error=None):
"""Call a function and retry if it fails.
This is the lowest-level retry helper. Generally, you'll use the
higher-level retry helper :class:`Retry`.
Args:
target(Callable): The function to call and retry. This must be a
nullary function - apply arguments with `functools.partial`.
predicate (Callable[Exception]): A callable used to determine if an
exception raised by the target should be considered retryable.
It should return True to retry or False otherwise.
sleep_generator (Iterable[float]): An infinite iterator that determines
how long to sleep between retries.
deadline (float): How long to keep retrying the target. The last sleep
period is shortened as necessary, so that the last retry runs at
``deadline`` (and not considerably beyond it).
on_error (Callable[Exception]): A function to call while processing a
retryable exception. Any error raised by this function will *not*
be caught.
Returns:
Any: the return value of the target function.
Raises:
google.api_core.RetryError: If the deadline is exceeded while retrying.
ValueError: If the sleep generator stops yielding values.
Exception: If the target raises a method that isn't retryable.
"""
if deadline is not None:
deadline_datetime = datetime_helpers.utcnow() + datetime.timedelta(
seconds=deadline
)
else:
deadline_datetime = None
last_exc = None
for sleep in sleep_generator:
try:
> return target()
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/retry.py:189:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.api_core.operation.Operation object at 0x7fe795521b20>
retry = <google.api_core.retry.Retry object at 0x7fe795a4ca30>
def _done_or_raise(self, retry=DEFAULT_RETRY):
"""Check if the future is done and raise if it's not."""
kwargs = {} if retry is DEFAULT_RETRY else {"retry": retry}
if not self.done(**kwargs):
> raise _OperationNotComplete()
E google.api_core.future.polling._OperationNotComplete
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/future/polling.py:87: _OperationNotComplete
The above exception was the direct cause of the following exception:
self = <google.api_core.operation.Operation object at 0x7fe795521b20>
timeout = 60, retry = <google.api_core.retry.Retry object at 0x7fe795a4ca30>
def _blocking_poll(self, timeout=None, retry=DEFAULT_RETRY):
"""Poll and wait for the Future to be resolved.
Args:
timeout (int):
How long (in seconds) to wait for the operation to complete.
If None, wait indefinitely.
"""
if self._result_set:
return
retry_ = self._retry.with_deadline(timeout)
try:
kwargs = {} if retry is DEFAULT_RETRY else {"retry": retry}
> retry_(self._done_or_raise)(**kwargs)
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/future/polling.py:108:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
args = (), kwargs = {}
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fe795521b20>>)
sleep_generator = <generator object exponential_sleep_generator at 0x7fe7954feb30>
@general_helpers.wraps(func)
def retry_wrapped_func(*args, **kwargs):
"""A wrapper that calls target function with retry."""
target = functools.partial(func, *args, **kwargs)
sleep_generator = exponential_sleep_generator(
self._initial, self._maximum, multiplier=self._multiplier
)
> return retry_target(
target,
self._predicate,
sleep_generator,
self._deadline,
on_error=on_error,
)
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/retry.py:286:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fe795521b20>>)
predicate = <function if_exception_type.<locals>.if_exception_type_predicate at 0x7fe795a5a5e0>
sleep_generator = <generator object exponential_sleep_generator at 0x7fe7954feb30>
deadline = 60, on_error = None
def retry_target(target, predicate, sleep_generator, deadline, on_error=None):
"""Call a function and retry if it fails.
This is the lowest-level retry helper. Generally, you'll use the
higher-level retry helper :class:`Retry`.
Args:
target(Callable): The function to call and retry. This must be a
nullary function - apply arguments with `functools.partial`.
predicate (Callable[Exception]): A callable used to determine if an
exception raised by the target should be considered retryable.
It should return True to retry or False otherwise.
sleep_generator (Iterable[float]): An infinite iterator that determines
how long to sleep between retries.
deadline (float): How long to keep retrying the target. The last sleep
period is shortened as necessary, so that the last retry runs at
``deadline`` (and not considerably beyond it).
on_error (Callable[Exception]): A function to call while processing a
retryable exception. Any error raised by this function will *not*
be caught.
Returns:
Any: the return value of the target function.
Raises:
google.api_core.RetryError: If the deadline is exceeded while retrying.
ValueError: If the sleep generator stops yielding values.
Exception: If the target raises a method that isn't retryable.
"""
if deadline is not None:
deadline_datetime = datetime_helpers.utcnow() + datetime.timedelta(
seconds=deadline
)
else:
deadline_datetime = None
last_exc = None
for sleep in sleep_generator:
try:
return target()
# pylint: disable=broad-except
# This function explicitly must deal with broad exceptions.
except Exception as exc:
if not predicate(exc):
raise
last_exc = exc
if on_error is not None:
on_error(exc)
now = datetime_helpers.utcnow()
if deadline_datetime is not None:
if deadline_datetime <= now:
> six.raise_from(
exceptions.RetryError(
"Deadline of {:.1f}s exceeded while calling {}".format(
deadline, target
),
last_exc,
),
last_exc,
)
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/retry.py:204:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
value = None, from_value = _OperationNotComplete()
> ???
E google.api_core.exceptions.RetryError: Deadline of 60.0s exceeded while calling functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fe795521b20>>), last exception:
<string>:3: RetryError
During handling of the above exception, another exception occurred:
def setUpModule():
if USE_EMULATOR:
from google.auth.credentials import AnonymousCredentials
emulator_project = os.getenv("GCLOUD_PROJECT", "emulator-test-project")
Config.CLIENT = Client(
project=emulator_project, credentials=AnonymousCredentials()
)
else:
Config.CLIENT = Client()
retry = RetryErrors(exceptions.ServiceUnavailable)
configs = list(retry(Config.CLIENT.list_instance_configs)())
instances = retry(_list_instances)()
EXISTING_INSTANCES[:] = instances
# Delete test instances that are older than an hour.
cutoff = int(time.time()) - 1 * 60 * 60
instance_pbs = Config.CLIENT.list_instances("labels.python-spanner-systests:true")
for instance_pb in instance_pbs:
instance = Instance.from_pb(instance_pb, Config.CLIENT)
if "created" not in instance.labels:
continue
create_time = int(instance.labels["created"])
if create_time > cutoff:
continue
# Instance cannot be deleted while backups exist.
for backup_pb in instance.list_backups():
backup = Backup.from_pb(backup_pb, instance)
backup.delete()
instance.delete()
if CREATE_INSTANCE:
if not USE_EMULATOR:
# Defend against back-end returning configs for regions we aren't
# actually allowed to use.
configs = [config for config in configs if "-us-" in config.name]
if not configs:
raise ValueError("List instance configs failed in module set up.")
Config.INSTANCE_CONFIG = configs[0]
config_name = configs[0].name
create_time = str(int(time.time()))
labels = {"python-spanner-systests": "true", "created": create_time}
Config.INSTANCE = Config.CLIENT.instance(
INSTANCE_ID, config_name, labels=labels
)
created_op = Config.INSTANCE.create()
> created_op.result(
SPANNER_OPERATION_TIMEOUT_IN_SECONDS
) # block until completion
tests/system/test_system.py:159:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/future/polling.py:130: in result
self._blocking_poll(timeout=timeout, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.api_core.operation.Operation object at 0x7fe795521b20>
timeout = 60, retry = <google.api_core.retry.Retry object at 0x7fe795a4ca30>
def _blocking_poll(self, timeout=None, retry=DEFAULT_RETRY):
"""Poll and wait for the Future to be resolved.
Args:
timeout (int):
How long (in seconds) to wait for the operation to complete.
If None, wait indefinitely.
"""
if self._result_set:
return
retry_ = self._retry.with_deadline(timeout)
try:
kwargs = {} if retry is DEFAULT_RETRY else {"retry": retry}
retry_(self._done_or_raise)(**kwargs)
except exceptions.RetryError:
> raise concurrent.futures.TimeoutError(
"Operation did not complete within the designated " "timeout."
)
E concurrent.futures._base.TimeoutError: Operation did not complete within the designated timeout.
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/future/polling.py:110: TimeoutError</pre></details>
|
1.0
|
tests.system.test_system.TestBackupAPI: test_restore_to_diff_instance failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 2487800e31842a44dcc37937c325e130c8c926b0
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/306a2e02-87cb-4be9-be31-37456ec7a8a2), [Sponge](http://sponge2/306a2e02-87cb-4be9-be31-37456ec7a8a2)
status: failed
<details><summary>Test output</summary><br><pre>target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fe795521b20>>)
predicate = <function if_exception_type.<locals>.if_exception_type_predicate at 0x7fe795a5a5e0>
sleep_generator = <generator object exponential_sleep_generator at 0x7fe7954feb30>
deadline = 60, on_error = None
def retry_target(target, predicate, sleep_generator, deadline, on_error=None):
"""Call a function and retry if it fails.
This is the lowest-level retry helper. Generally, you'll use the
higher-level retry helper :class:`Retry`.
Args:
target(Callable): The function to call and retry. This must be a
nullary function - apply arguments with `functools.partial`.
predicate (Callable[Exception]): A callable used to determine if an
exception raised by the target should be considered retryable.
It should return True to retry or False otherwise.
sleep_generator (Iterable[float]): An infinite iterator that determines
how long to sleep between retries.
deadline (float): How long to keep retrying the target. The last sleep
period is shortened as necessary, so that the last retry runs at
``deadline`` (and not considerably beyond it).
on_error (Callable[Exception]): A function to call while processing a
retryable exception. Any error raised by this function will *not*
be caught.
Returns:
Any: the return value of the target function.
Raises:
google.api_core.RetryError: If the deadline is exceeded while retrying.
ValueError: If the sleep generator stops yielding values.
Exception: If the target raises a method that isn't retryable.
"""
if deadline is not None:
deadline_datetime = datetime_helpers.utcnow() + datetime.timedelta(
seconds=deadline
)
else:
deadline_datetime = None
last_exc = None
for sleep in sleep_generator:
try:
> return target()
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/retry.py:189:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.api_core.operation.Operation object at 0x7fe795521b20>
retry = <google.api_core.retry.Retry object at 0x7fe795a4ca30>
def _done_or_raise(self, retry=DEFAULT_RETRY):
"""Check if the future is done and raise if it's not."""
kwargs = {} if retry is DEFAULT_RETRY else {"retry": retry}
if not self.done(**kwargs):
> raise _OperationNotComplete()
E google.api_core.future.polling._OperationNotComplete
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/future/polling.py:87: _OperationNotComplete
The above exception was the direct cause of the following exception:
self = <google.api_core.operation.Operation object at 0x7fe795521b20>
timeout = 60, retry = <google.api_core.retry.Retry object at 0x7fe795a4ca30>
def _blocking_poll(self, timeout=None, retry=DEFAULT_RETRY):
"""Poll and wait for the Future to be resolved.
Args:
timeout (int):
How long (in seconds) to wait for the operation to complete.
If None, wait indefinitely.
"""
if self._result_set:
return
retry_ = self._retry.with_deadline(timeout)
try:
kwargs = {} if retry is DEFAULT_RETRY else {"retry": retry}
> retry_(self._done_or_raise)(**kwargs)
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/future/polling.py:108:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
args = (), kwargs = {}
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fe795521b20>>)
sleep_generator = <generator object exponential_sleep_generator at 0x7fe7954feb30>
@general_helpers.wraps(func)
def retry_wrapped_func(*args, **kwargs):
"""A wrapper that calls target function with retry."""
target = functools.partial(func, *args, **kwargs)
sleep_generator = exponential_sleep_generator(
self._initial, self._maximum, multiplier=self._multiplier
)
> return retry_target(
target,
self._predicate,
sleep_generator,
self._deadline,
on_error=on_error,
)
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/retry.py:286:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
target = functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fe795521b20>>)
predicate = <function if_exception_type.<locals>.if_exception_type_predicate at 0x7fe795a5a5e0>
sleep_generator = <generator object exponential_sleep_generator at 0x7fe7954feb30>
deadline = 60, on_error = None
def retry_target(target, predicate, sleep_generator, deadline, on_error=None):
"""Call a function and retry if it fails.
This is the lowest-level retry helper. Generally, you'll use the
higher-level retry helper :class:`Retry`.
Args:
target(Callable): The function to call and retry. This must be a
nullary function - apply arguments with `functools.partial`.
predicate (Callable[Exception]): A callable used to determine if an
exception raised by the target should be considered retryable.
It should return True to retry or False otherwise.
sleep_generator (Iterable[float]): An infinite iterator that determines
how long to sleep between retries.
deadline (float): How long to keep retrying the target. The last sleep
period is shortened as necessary, so that the last retry runs at
``deadline`` (and not considerably beyond it).
on_error (Callable[Exception]): A function to call while processing a
retryable exception. Any error raised by this function will *not*
be caught.
Returns:
Any: the return value of the target function.
Raises:
google.api_core.RetryError: If the deadline is exceeded while retrying.
ValueError: If the sleep generator stops yielding values.
Exception: If the target raises a method that isn't retryable.
"""
if deadline is not None:
deadline_datetime = datetime_helpers.utcnow() + datetime.timedelta(
seconds=deadline
)
else:
deadline_datetime = None
last_exc = None
for sleep in sleep_generator:
try:
return target()
# pylint: disable=broad-except
# This function explicitly must deal with broad exceptions.
except Exception as exc:
if not predicate(exc):
raise
last_exc = exc
if on_error is not None:
on_error(exc)
now = datetime_helpers.utcnow()
if deadline_datetime is not None:
if deadline_datetime <= now:
> six.raise_from(
exceptions.RetryError(
"Deadline of {:.1f}s exceeded while calling {}".format(
deadline, target
),
last_exc,
),
last_exc,
)
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/retry.py:204:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
value = None, from_value = _OperationNotComplete()
> ???
E google.api_core.exceptions.RetryError: Deadline of 60.0s exceeded while calling functools.partial(<bound method PollingFuture._done_or_raise of <google.api_core.operation.Operation object at 0x7fe795521b20>>), last exception:
<string>:3: RetryError
During handling of the above exception, another exception occurred:
def setUpModule():
if USE_EMULATOR:
from google.auth.credentials import AnonymousCredentials
emulator_project = os.getenv("GCLOUD_PROJECT", "emulator-test-project")
Config.CLIENT = Client(
project=emulator_project, credentials=AnonymousCredentials()
)
else:
Config.CLIENT = Client()
retry = RetryErrors(exceptions.ServiceUnavailable)
configs = list(retry(Config.CLIENT.list_instance_configs)())
instances = retry(_list_instances)()
EXISTING_INSTANCES[:] = instances
# Delete test instances that are older than an hour.
cutoff = int(time.time()) - 1 * 60 * 60
instance_pbs = Config.CLIENT.list_instances("labels.python-spanner-systests:true")
for instance_pb in instance_pbs:
instance = Instance.from_pb(instance_pb, Config.CLIENT)
if "created" not in instance.labels:
continue
create_time = int(instance.labels["created"])
if create_time > cutoff:
continue
# Instance cannot be deleted while backups exist.
for backup_pb in instance.list_backups():
backup = Backup.from_pb(backup_pb, instance)
backup.delete()
instance.delete()
if CREATE_INSTANCE:
if not USE_EMULATOR:
# Defend against back-end returning configs for regions we aren't
# actually allowed to use.
configs = [config for config in configs if "-us-" in config.name]
if not configs:
raise ValueError("List instance configs failed in module set up.")
Config.INSTANCE_CONFIG = configs[0]
config_name = configs[0].name
create_time = str(int(time.time()))
labels = {"python-spanner-systests": "true", "created": create_time}
Config.INSTANCE = Config.CLIENT.instance(
INSTANCE_ID, config_name, labels=labels
)
created_op = Config.INSTANCE.create()
> created_op.result(
SPANNER_OPERATION_TIMEOUT_IN_SECONDS
) # block until completion
tests/system/test_system.py:159:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/future/polling.py:130: in result
self._blocking_poll(timeout=timeout, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <google.api_core.operation.Operation object at 0x7fe795521b20>
timeout = 60, retry = <google.api_core.retry.Retry object at 0x7fe795a4ca30>
def _blocking_poll(self, timeout=None, retry=DEFAULT_RETRY):
"""Poll and wait for the Future to be resolved.
Args:
timeout (int):
How long (in seconds) to wait for the operation to complete.
If None, wait indefinitely.
"""
if self._result_set:
return
retry_ = self._retry.with_deadline(timeout)
try:
kwargs = {} if retry is DEFAULT_RETRY else {"retry": retry}
retry_(self._done_or_raise)(**kwargs)
except exceptions.RetryError:
> raise concurrent.futures.TimeoutError(
"Operation did not complete within the designated " "timeout."
)
E concurrent.futures._base.TimeoutError: Operation did not complete within the designated timeout.
.nox/system-3-8/lib/python3.8/site-packages/google/api_core/future/polling.py:110: TimeoutError</pre></details>
|
process
|
tests system test system testbackupapi test restore to diff instance failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output target functools partial predicate if exception type predicate at sleep generator deadline on error none def retry target target predicate sleep generator deadline on error none call a function and retry if it fails this is the lowest level retry helper generally you ll use the higher level retry helper class retry args target callable the function to call and retry this must be a nullary function apply arguments with functools partial predicate callable a callable used to determine if an exception raised by the target should be considered retryable it should return true to retry or false otherwise sleep generator iterable an infinite iterator that determines how long to sleep between retries deadline float how long to keep retrying the target the last sleep period is shortened as necessary so that the last retry runs at deadline and not considerably beyond it on error callable a function to call while processing a retryable exception any error raised by this function will not be caught returns any the return value of the target function raises google api core retryerror if the deadline is exceeded while retrying valueerror if the sleep generator stops yielding values exception if the target raises a method that isn t retryable if deadline is not none deadline datetime datetime helpers utcnow datetime timedelta seconds deadline else deadline datetime none last exc none for sleep in sleep generator try return target nox system lib site packages google api core retry py self retry def done or raise self retry default retry check if the future is done and raise if it s not kwargs if retry is default retry else retry retry if not self done kwargs raise operationnotcomplete e google api core future polling operationnotcomplete nox system lib site packages google api core future polling py operationnotcomplete the above exception was the direct cause of the following exception self timeout retry def blocking poll self timeout none retry default retry poll and wait for the future to be resolved args timeout int how long in seconds to wait for the operation to complete if none wait indefinitely if self result set return retry self retry with deadline timeout try kwargs if retry is default retry else retry retry retry self done or raise kwargs nox system lib site packages google api core future polling py args kwargs target functools partial sleep generator general helpers wraps func def retry wrapped func args kwargs a wrapper that calls target function with retry target functools partial func args kwargs sleep generator exponential sleep generator self initial self maximum multiplier self multiplier return retry target target self predicate sleep generator self deadline on error on error nox system lib site packages google api core retry py target functools partial predicate if exception type predicate at sleep generator deadline on error none def retry target target predicate sleep generator deadline on error none call a function and retry if it fails this is the lowest level retry helper generally you ll use the higher level retry helper class retry args target callable the function to call and retry this must be a nullary function apply arguments with functools partial predicate callable a callable used to determine if an exception raised by the target should be considered retryable it should return true to retry or false otherwise sleep generator iterable an infinite iterator that determines how long to sleep between retries deadline float how long to keep retrying the target the last sleep period is shortened as necessary so that the last retry runs at deadline and not considerably beyond it on error callable a function to call while processing a retryable exception any error raised by this function will not be caught returns any the return value of the target function raises google api core retryerror if the deadline is exceeded while retrying valueerror if the sleep generator stops yielding values exception if the target raises a method that isn t retryable if deadline is not none deadline datetime datetime helpers utcnow datetime timedelta seconds deadline else deadline datetime none last exc none for sleep in sleep generator try return target pylint disable broad except this function explicitly must deal with broad exceptions except exception as exc if not predicate exc raise last exc exc if on error is not none on error exc now datetime helpers utcnow if deadline datetime is not none if deadline datetime now six raise from exceptions retryerror deadline of s exceeded while calling format deadline target last exc last exc nox system lib site packages google api core retry py value none from value operationnotcomplete e google api core exceptions retryerror deadline of exceeded while calling functools partial last exception retryerror during handling of the above exception another exception occurred def setupmodule if use emulator from google auth credentials import anonymouscredentials emulator project os getenv gcloud project emulator test project config client client project emulator project credentials anonymouscredentials else config client client retry retryerrors exceptions serviceunavailable configs list retry config client list instance configs instances retry list instances existing instances instances delete test instances that are older than an hour cutoff int time time instance pbs config client list instances labels python spanner systests true for instance pb in instance pbs instance instance from pb instance pb config client if created not in instance labels continue create time int instance labels if create time cutoff continue instance cannot be deleted while backups exist for backup pb in instance list backups backup backup from pb backup pb instance backup delete instance delete if create instance if not use emulator defend against back end returning configs for regions we aren t actually allowed to use configs if not configs raise valueerror list instance configs failed in module set up config instance config configs config name configs name create time str int time time labels python spanner systests true created create time config instance config client instance instance id config name labels labels created op config instance create created op result spanner operation timeout in seconds block until completion tests system test system py nox system lib site packages google api core future polling py in result self blocking poll timeout timeout kwargs self timeout retry def blocking poll self timeout none retry default retry poll and wait for the future to be resolved args timeout int how long in seconds to wait for the operation to complete if none wait indefinitely if self result set return retry self retry with deadline timeout try kwargs if retry is default retry else retry retry retry self done or raise kwargs except exceptions retryerror raise concurrent futures timeouterror operation did not complete within the designated timeout e concurrent futures base timeouterror operation did not complete within the designated timeout nox system lib site packages google api core future polling py timeouterror
| 1
|
1,843
| 2,574,428,432
|
IssuesEvent
|
2015-02-11 16:52:06
|
mozilla/webmaker-app
|
https://api.github.com/repos/mozilla/webmaker-app
|
closed
|
Update blue colour variable one last time
|
design
|
We need to update the blue colour variable one last time. We are making the colour a bit brighter now that we are using the blue in headers. The blue now needs to play nice with elements like the universal done button.
|
1.0
|
Update blue colour variable one last time - We need to update the blue colour variable one last time. We are making the colour a bit brighter now that we are using the blue in headers. The blue now needs to play nice with elements like the universal done button.
|
non_process
|
update blue colour variable one last time we need to update the blue colour variable one last time we are making the colour a bit brighter now that we are using the blue in headers the blue now needs to play nice with elements like the universal done button
| 0
|
15,005
| 18,720,002,556
|
IssuesEvent
|
2021-11-03 10:40:24
|
geneontology/go-ontology
|
https://api.github.com/repos/geneontology/go-ontology
|
closed
|
issues with envenomation, poisons and venoms
|
multi-species process
|
From #18979
Pascale:
The actual injection of a substance (envenomation) is not really related to the 'biological purpose' of the toxin. Wikipedia is helpful
https://en.wikipedia.org/wiki/Venom
Necrotoxins, which cause necrosis (i.e., death) in the cells they encounter.[4] The venom of most viper species contains phospholipase and trypsin-like serine proteases.
Neurotoxins, which primarily affect the nervous systems of animals.[5] These include ion channel toxins that disrupt ion channel conductance. Black widow spider, scorpion, box jellyfish, cone snail, centipede and blue-ringed octopus venoms (among many others) function in this way.
Myotoxins, which damage muscles by binding to a receptor, are small, basic peptides found in snake (such as rattlesnake) and lizard venoms.[6][7][8][9]
Cytotoxins, which kill individual cells, are found in the apitoxin of honey bees and the venom of black widow spiders.[10][11]
But still - venoms serve for either feeding or defense, right ? Any other function ?
We should make sure to capture that as well.
Thanks, Pascale
----
Penelope:
Hi,
Somehow I missed your reply!
It seems that the way of the toxin in entering the other organism it does matter. Please see part of the link below that describe the different between poison and venom.
They also, mentioned another use of the venom; that is to deter competitors. It will be good to capture this as well.
(https://www.science.org.au/curious/people-medicine/venom-painful-truth)
Poisonous ain’t venomous
Although the terms are often used interchangeably, ‘venom’ and ‘poison’ are actually not the same thing.
**Poison** is a toxin that gets into the body through the gastrointestinal or respiratory tract or by absorption through intact (unbroken) body layers. Poisons generally contain very small molecules—which means they can be absorbed by the skin, for instance. A cane toad, which excretes toxins from glands on each shoulder, is a poisonous animal. It has to be ingested (or licked) to cause harm. Poison ivy is an example of a poisonous plant—touching it can result in an itchy and sometimes painful rash.
**Venom** is a toxin or mixture of toxins that get into the body through an injection—via a bite or sting. **Because it has a mixture of small and large molecules, it needs a wound to be able to enter the body.** A taipan, which injects venom through syringe-like teeth, is a venomous animal. So are jellyfish, which inject venom into skin using venom-filled harpoon-like structures that shoot out from cells along their tentacles when touched.
"If you lick it or eat it and you die, it’s poisonous. If it bites you and you die, it’s venomous."
Dr Bryan Fry
Thanks,
Penelope
|
1.0
|
issues with envenomation, poisons and venoms - From #18979
Pascale:
The actual injection of a substance (envenomation) is not really related to the 'biological purpose' of the toxin. Wikipedia is helpful
https://en.wikipedia.org/wiki/Venom
Necrotoxins, which cause necrosis (i.e., death) in the cells they encounter.[4] The venom of most viper species contains phospholipase and trypsin-like serine proteases.
Neurotoxins, which primarily affect the nervous systems of animals.[5] These include ion channel toxins that disrupt ion channel conductance. Black widow spider, scorpion, box jellyfish, cone snail, centipede and blue-ringed octopus venoms (among many others) function in this way.
Myotoxins, which damage muscles by binding to a receptor, are small, basic peptides found in snake (such as rattlesnake) and lizard venoms.[6][7][8][9]
Cytotoxins, which kill individual cells, are found in the apitoxin of honey bees and the venom of black widow spiders.[10][11]
But still - venoms serve for either feeding or defense, right ? Any other function ?
We should make sure to capture that as well.
Thanks, Pascale
----
Penelope:
Hi,
Somehow I missed your reply!
It seems that the way of the toxin in entering the other organism it does matter. Please see part of the link below that describe the different between poison and venom.
They also, mentioned another use of the venom; that is to deter competitors. It will be good to capture this as well.
(https://www.science.org.au/curious/people-medicine/venom-painful-truth)
Poisonous ain’t venomous
Although the terms are often used interchangeably, ‘venom’ and ‘poison’ are actually not the same thing.
**Poison** is a toxin that gets into the body through the gastrointestinal or respiratory tract or by absorption through intact (unbroken) body layers. Poisons generally contain very small molecules—which means they can be absorbed by the skin, for instance. A cane toad, which excretes toxins from glands on each shoulder, is a poisonous animal. It has to be ingested (or licked) to cause harm. Poison ivy is an example of a poisonous plant—touching it can result in an itchy and sometimes painful rash.
**Venom** is a toxin or mixture of toxins that get into the body through an injection—via a bite or sting. **Because it has a mixture of small and large molecules, it needs a wound to be able to enter the body.** A taipan, which injects venom through syringe-like teeth, is a venomous animal. So are jellyfish, which inject venom into skin using venom-filled harpoon-like structures that shoot out from cells along their tentacles when touched.
"If you lick it or eat it and you die, it’s poisonous. If it bites you and you die, it’s venomous."
Dr Bryan Fry
Thanks,
Penelope
|
process
|
issues with envenomation poisons and venoms from pascale the actual injection of a substance envenomation is not really related to the biological purpose of the toxin wikipedia is helpful necrotoxins which cause necrosis i e death in the cells they encounter the venom of most viper species contains phospholipase and trypsin like serine proteases neurotoxins which primarily affect the nervous systems of animals these include ion channel toxins that disrupt ion channel conductance black widow spider scorpion box jellyfish cone snail centipede and blue ringed octopus venoms among many others function in this way myotoxins which damage muscles by binding to a receptor are small basic peptides found in snake such as rattlesnake and lizard venoms cytotoxins which kill individual cells are found in the apitoxin of honey bees and the venom of black widow spiders but still venoms serve for either feeding or defense right any other function we should make sure to capture that as well thanks pascale penelope hi somehow i missed your reply it seems that the way of the toxin in entering the other organism it does matter please see part of the link below that describe the different between poison and venom they also mentioned another use of the venom that is to deter competitors it will be good to capture this as well poisonous ain’t venomous although the terms are often used interchangeably ‘venom’ and ‘poison’ are actually not the same thing poison is a toxin that gets into the body through the gastrointestinal or respiratory tract or by absorption through intact unbroken body layers poisons generally contain very small molecules—which means they can be absorbed by the skin for instance a cane toad which excretes toxins from glands on each shoulder is a poisonous animal it has to be ingested or licked to cause harm poison ivy is an example of a poisonous plant—touching it can result in an itchy and sometimes painful rash venom is a toxin or mixture of toxins that get into the body through an injection—via a bite or sting because it has a mixture of small and large molecules it needs a wound to be able to enter the body a taipan which injects venom through syringe like teeth is a venomous animal so are jellyfish which inject venom into skin using venom filled harpoon like structures that shoot out from cells along their tentacles when touched if you lick it or eat it and you die it’s poisonous if it bites you and you die it’s venomous dr bryan fry thanks penelope
| 1
|
8,771
| 11,886,816,486
|
IssuesEvent
|
2020-03-27 23:05:11
|
googleapis/gapic-generator-go
|
https://api.github.com/repos/googleapis/gapic-generator-go
|
closed
|
chore: automate release notes creation
|
type: process
|
A simple tag push results in automation creating a GitHub Release for the newly pushed tag. But there are no release notes and the Release title is not ideal (the entire message of the latest commit).
We should make release notes generated into the release based on the commit messages of those commits since the last release.
|
1.0
|
chore: automate release notes creation - A simple tag push results in automation creating a GitHub Release for the newly pushed tag. But there are no release notes and the Release title is not ideal (the entire message of the latest commit).
We should make release notes generated into the release based on the commit messages of those commits since the last release.
|
process
|
chore automate release notes creation a simple tag push results in automation creating a github release for the newly pushed tag but there are no release notes and the release title is not ideal the entire message of the latest commit we should make release notes generated into the release based on the commit messages of those commits since the last release
| 1
|
20,749
| 27,456,462,540
|
IssuesEvent
|
2023-03-02 21:49:34
|
hashgraph/hedera-mirror-node
|
https://api.github.com/repos/hashgraph/hedera-mirror-node
|
opened
|
Cannot locate tasks that match ':hedera-mirror-rest:check-state-proof:assemble'
|
bug process
|
### Description
When trying to `Build Project` in Intellij, I get the following error:
```
Cannot locate tasks that match ':hedera-mirror-rest:check-state-proof:assemble' as project 'hedera-mirror-rest' not found in root project 'hedera-mirror-node'.
* Try:
> Run gradle projects to get a list of available projects.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
```
### Steps to reproduce
`Build Project` in Intellij
### Additional context
_No response_
### Hedera network
other
### Version
main
### Operating system
None
|
1.0
|
Cannot locate tasks that match ':hedera-mirror-rest:check-state-proof:assemble' - ### Description
When trying to `Build Project` in Intellij, I get the following error:
```
Cannot locate tasks that match ':hedera-mirror-rest:check-state-proof:assemble' as project 'hedera-mirror-rest' not found in root project 'hedera-mirror-node'.
* Try:
> Run gradle projects to get a list of available projects.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
```
### Steps to reproduce
`Build Project` in Intellij
### Additional context
_No response_
### Hedera network
other
### Version
main
### Operating system
None
|
process
|
cannot locate tasks that match hedera mirror rest check state proof assemble description when trying to build project in intellij i get the following error cannot locate tasks that match hedera mirror rest check state proof assemble as project hedera mirror rest not found in root project hedera mirror node try run gradle projects to get a list of available projects run with stacktrace option to get the stack trace run with info or debug option to get more log output steps to reproduce build project in intellij additional context no response hedera network other version main operating system none
| 1
|
104,678
| 11,418,616,811
|
IssuesEvent
|
2020-02-03 05:19:38
|
PlatziMaster/project-react-01
|
https://api.github.com/repos/PlatziMaster/project-react-01
|
opened
|
Documentar
|
documentation
|
Crea la documentación necesaria para la aplicación en el documento de tu Pull Request.
|
1.0
|
Documentar - Crea la documentación necesaria para la aplicación en el documento de tu Pull Request.
|
non_process
|
documentar crea la documentación necesaria para la aplicación en el documento de tu pull request
| 0
|
108,904
| 4,363,487,402
|
IssuesEvent
|
2016-08-03 00:43:29
|
JonathanPrecise/FloatingWindows
|
https://api.github.com/repos/JonathanPrecise/FloatingWindows
|
opened
|
Can only have one window open at a time
|
bug confirmed priority-NEEDNOW release-blocker
|
Can only have one window open at a time. The first disappears when a second one is open.
|
1.0
|
Can only have one window open at a time - Can only have one window open at a time. The first disappears when a second one is open.
|
non_process
|
can only have one window open at a time can only have one window open at a time the first disappears when a second one is open
| 0
|
17,105
| 22,625,097,700
|
IssuesEvent
|
2022-06-30 09:55:44
|
camunda/zeebe-process-test
|
https://api.github.com/repos/camunda/zeebe-process-test
|
closed
|
Gradle: Cannot find Agrona dependency using spring-zeebe-test
|
kind/bug team/process-automation
|
Hello Guys , sorry to bother. I been trying to setup a Camunda 8 Zeebe project on a Spring Rest API (gradle spring project) everything about the main features of the library work okey (zeebeClient and workers) but...
Same issue in camunda-community repositories: https://github.com/camunda-community-hub/camunda-8-examples/issues/2
My issue started when I started using "spring-zeebe-test" dependency and @ZeebeTest , the error itself:
Could not resolve org.agrona:agrona:{strictly [1.14,1.15[; prefer 1.15.0}. Required by: project : > io.camunda:spring-zeebe-test:8.0.2
camunda-zeebe version: 8.0.4 (also tried 8.0.2 , and 8.0.0)
gradle repository: mavenCentral
Spring 2.7.0 and tried 2.6.7
Java Open JDK 17
If you have any clue of what could be happening , that will be great , thanks for your time!
|
1.0
|
Gradle: Cannot find Agrona dependency using spring-zeebe-test -
Hello Guys , sorry to bother. I been trying to setup a Camunda 8 Zeebe project on a Spring Rest API (gradle spring project) everything about the main features of the library work okey (zeebeClient and workers) but...
Same issue in camunda-community repositories: https://github.com/camunda-community-hub/camunda-8-examples/issues/2
My issue started when I started using "spring-zeebe-test" dependency and @ZeebeTest , the error itself:
Could not resolve org.agrona:agrona:{strictly [1.14,1.15[; prefer 1.15.0}. Required by: project : > io.camunda:spring-zeebe-test:8.0.2
camunda-zeebe version: 8.0.4 (also tried 8.0.2 , and 8.0.0)
gradle repository: mavenCentral
Spring 2.7.0 and tried 2.6.7
Java Open JDK 17
If you have any clue of what could be happening , that will be great , thanks for your time!
|
process
|
gradle cannot find agrona dependency using spring zeebe test hello guys sorry to bother i been trying to setup a camunda zeebe project on a spring rest api gradle spring project everything about the main features of the library work okey zeebeclient and workers but same issue in camunda community repositories my issue started when i started using spring zeebe test dependency and zeebetest the error itself could not resolve org agrona agrona strictly prefer required by project io camunda spring zeebe test camunda zeebe version also tried and gradle repository mavencentral spring and tried java open jdk if you have any clue of what could be happening that will be great thanks for your time
| 1
|
5,256
| 8,048,723,418
|
IssuesEvent
|
2018-08-01 07:50:09
|
RennurApps/AwareIM-resources
|
https://api.github.com/repos/RennurApps/AwareIM-resources
|
closed
|
Active processes not timing out.
|
CT: Context CT: Process I: Performance SC: wontfix SO: Unconfirmed v6.0 v8.1
|
There are **processes** that appear in the **_active processes_** table that are either not timed out or killed by the system. These processes are stored in **_execution_context_** database table.
As reported by some developers, this may be the cause various system issues from application performance to a complete server halt.
Forum posts reporting this:
- [RUNNING PROCESSES](https://www.awareim.com/forum/viewtopic.php?f=1&t=8094&p=34596) by intra
- [EXECUTION_CONTEXTS TABLE --> NUMBER OF RECORDS??](https://www.awareim.com/forum/viewtopic.php?f=1&t=8526&p=37230) by tford
- [When AwareIM dies](https://www.awareim.com/forum/viewtopic.php?f=1&t=7595) by kklosson
|
1.0
|
Active processes not timing out. - There are **processes** that appear in the **_active processes_** table that are either not timed out or killed by the system. These processes are stored in **_execution_context_** database table.
As reported by some developers, this may be the cause various system issues from application performance to a complete server halt.
Forum posts reporting this:
- [RUNNING PROCESSES](https://www.awareim.com/forum/viewtopic.php?f=1&t=8094&p=34596) by intra
- [EXECUTION_CONTEXTS TABLE --> NUMBER OF RECORDS??](https://www.awareim.com/forum/viewtopic.php?f=1&t=8526&p=37230) by tford
- [When AwareIM dies](https://www.awareim.com/forum/viewtopic.php?f=1&t=7595) by kklosson
|
process
|
active processes not timing out there are processes that appear in the active processes table that are either not timed out or killed by the system these processes are stored in execution context database table as reported by some developers this may be the cause various system issues from application performance to a complete server halt forum posts reporting this by intra by tford by kklosson
| 1
|
442
| 2,873,805,593
|
IssuesEvent
|
2015-06-08 19:02:07
|
besasm/EMGAATS
|
https://api.github.com/repos/besasm/EMGAATS
|
opened
|
mult-iuser editing
|
process question UI
|
how does arcgis handle multi-user editing.
how do technicians currently handle this?
impacts on validation process
|
1.0
|
mult-iuser editing - how does arcgis handle multi-user editing.
how do technicians currently handle this?
impacts on validation process
|
process
|
mult iuser editing how does arcgis handle multi user editing how do technicians currently handle this impacts on validation process
| 1
|
296,699
| 25,570,521,891
|
IssuesEvent
|
2022-11-30 17:18:20
|
helidon-io/helidon
|
https://api.github.com/repos/helidon-io/helidon
|
closed
|
Intermittent TestJBatchEndpoint.runJob
|
3.x testing intermittent
|
```
org.opentest4j.AssertionFailedError: Job Result string ==> expected: <{"Steps executed":"[step1, step2]","Status":"COMPLETED"}> but was: <{"Steps executed":"[step1]","Status":"STARTED"}>
at io.helidon.examples.jbatch.TestJBatchEndpoint.runJob(TestJBatchEndpoint.java:59)
```
|
1.0
|
Intermittent TestJBatchEndpoint.runJob - ```
org.opentest4j.AssertionFailedError: Job Result string ==> expected: <{"Steps executed":"[step1, step2]","Status":"COMPLETED"}> but was: <{"Steps executed":"[step1]","Status":"STARTED"}>
at io.helidon.examples.jbatch.TestJBatchEndpoint.runJob(TestJBatchEndpoint.java:59)
```
|
non_process
|
intermittent testjbatchendpoint runjob org assertionfailederror job result string expected but was at io helidon examples jbatch testjbatchendpoint runjob testjbatchendpoint java
| 0
|
4,823
| 7,719,169,703
|
IssuesEvent
|
2018-05-23 18:31:56
|
glos/myglos
|
https://api.github.com/repos/glos/myglos
|
closed
|
MTRI Satelite products not showing correct bounding boxes (was: MTRI switch to weekly zip (April 15))
|
MTRI RPS process
|
Action items May 1
- [ ] @ColinNBrooks "poke" to do his tasks to make the weekly vs. full load take effect
- [x] @kknee (RPS) to turn back on MTRI updates
- [ ] test to be sure portal (OWS) is behaving
|
1.0
|
MTRI Satelite products not showing correct bounding boxes (was: MTRI switch to weekly zip (April 15)) - Action items May 1
- [ ] @ColinNBrooks "poke" to do his tasks to make the weekly vs. full load take effect
- [x] @kknee (RPS) to turn back on MTRI updates
- [ ] test to be sure portal (OWS) is behaving
|
process
|
mtri satelite products not showing correct bounding boxes was mtri switch to weekly zip april action items may colinnbrooks poke to do his tasks to make the weekly vs full load take effect kknee rps to turn back on mtri updates test to be sure portal ows is behaving
| 1
|
10,063
| 13,044,161,790
|
IssuesEvent
|
2020-07-29 03:47:26
|
tikv/tikv
|
https://api.github.com/repos/tikv/tikv
|
closed
|
UCP: Migrate scalar function `ExtractDuration` from TiDB
|
challenge-program-2 component/coprocessor difficulty/easy sig/coprocessor
|
## Description
Port the scalar function `ExtractDuration` from TiDB to coprocessor.
## Score
* 50
## Mentor(s)
* @breeswish
## Recommended Skills
* Rust programming
## Learning Materials
Already implemented expressions ported from TiDB
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/rpn_expr)
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/expr)
|
2.0
|
UCP: Migrate scalar function `ExtractDuration` from TiDB -
## Description
Port the scalar function `ExtractDuration` from TiDB to coprocessor.
## Score
* 50
## Mentor(s)
* @breeswish
## Recommended Skills
* Rust programming
## Learning Materials
Already implemented expressions ported from TiDB
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/rpn_expr)
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/expr)
|
process
|
ucp migrate scalar function extractduration from tidb description port the scalar function extractduration from tidb to coprocessor score mentor s breeswish recommended skills rust programming learning materials already implemented expressions ported from tidb
| 1
|
146,519
| 13,184,746,522
|
IssuesEvent
|
2020-08-12 20:01:10
|
JRVeale/andrews-card-creator
|
https://api.github.com/repos/JRVeale/andrews-card-creator
|
closed
|
Add installation instructions
|
documentation
|
Graphviz install
Graphviz to system environment path
Run exe
|
1.0
|
Add installation instructions - Graphviz install
Graphviz to system environment path
Run exe
|
non_process
|
add installation instructions graphviz install graphviz to system environment path run exe
| 0
|
5,902
| 8,720,949,396
|
IssuesEvent
|
2018-12-08 17:54:24
|
shirou/gopsutil
|
https://api.github.com/repos/shirou/gopsutil
|
closed
|
Determine if process is running in the foreground
|
package:process
|
Is there any way to determine if a process loaded with `process.NewProcess(<pid>)` is running in the foreground?
I am looking for similar functionality to what `ps -O -p <pid>` returns in the `STAT` column; if there is a `+` in that column then the process is running in the foreground.
|
1.0
|
Determine if process is running in the foreground - Is there any way to determine if a process loaded with `process.NewProcess(<pid>)` is running in the foreground?
I am looking for similar functionality to what `ps -O -p <pid>` returns in the `STAT` column; if there is a `+` in that column then the process is running in the foreground.
|
process
|
determine if process is running in the foreground is there any way to determine if a process loaded with process newprocess is running in the foreground i am looking for similar functionality to what ps o p returns in the stat column if there is a in that column then the process is running in the foreground
| 1
|
77,316
| 14,784,531,990
|
IssuesEvent
|
2021-01-12 00:25:34
|
streetcomplete/StreetComplete
|
https://api.github.com/repos/streetcomplete/StreetComplete
|
opened
|
Separate view data in quest data classes
|
code cleanup
|
### Task
For the cycleway quest, the cycleway answer options are cleanly seperated into two files: `Cycleway.kt` contains the "pure data" (the enum) and `CyclewayItem` contains the view-related part of a cycleway answer option.
This is better than how it is done for for example the surface quest (and others). There, in `Surface.kt`, the enum is not pure data because is contains reference to view stuff and also Android-specific stuff. So for these quest(s), the data class should be refactored to be like for the cycleway class.
### Example
So it should be....
```kotlin
enum class Surface(val value: String) { // or osmValue?
ASPHALT("asphalt"),
...
}
// in SurfaceItem.kt
fun Surface.asItem(): Item<Surface> = ...
```
### Reason
Apart from it being good style, it is a step towards making #1892 a little less work to do
### Quests where this "old style" is used
- BuildingType
- Surface
### And then
And there is more. Quest types should no longer have a `String` as parameter but an enum.
Compare `AddRecyclingType` (new style) with `AddRailwayCrossingBarrier` (old style). It is okay for the enum to define an OSM value like in the example with surface above.
|
1.0
|
Separate view data in quest data classes - ### Task
For the cycleway quest, the cycleway answer options are cleanly seperated into two files: `Cycleway.kt` contains the "pure data" (the enum) and `CyclewayItem` contains the view-related part of a cycleway answer option.
This is better than how it is done for for example the surface quest (and others). There, in `Surface.kt`, the enum is not pure data because is contains reference to view stuff and also Android-specific stuff. So for these quest(s), the data class should be refactored to be like for the cycleway class.
### Example
So it should be....
```kotlin
enum class Surface(val value: String) { // or osmValue?
ASPHALT("asphalt"),
...
}
// in SurfaceItem.kt
fun Surface.asItem(): Item<Surface> = ...
```
### Reason
Apart from it being good style, it is a step towards making #1892 a little less work to do
### Quests where this "old style" is used
- BuildingType
- Surface
### And then
And there is more. Quest types should no longer have a `String` as parameter but an enum.
Compare `AddRecyclingType` (new style) with `AddRailwayCrossingBarrier` (old style). It is okay for the enum to define an OSM value like in the example with surface above.
|
non_process
|
separate view data in quest data classes task for the cycleway quest the cycleway answer options are cleanly seperated into two files cycleway kt contains the pure data the enum and cyclewayitem contains the view related part of a cycleway answer option this is better than how it is done for for example the surface quest and others there in surface kt the enum is not pure data because is contains reference to view stuff and also android specific stuff so for these quest s the data class should be refactored to be like for the cycleway class example so it should be kotlin enum class surface val value string or osmvalue asphalt asphalt in surfaceitem kt fun surface asitem item reason apart from it being good style it is a step towards making a little less work to do quests where this old style is used buildingtype surface and then and there is more quest types should no longer have a string as parameter but an enum compare addrecyclingtype new style with addrailwaycrossingbarrier old style it is okay for the enum to define an osm value like in the example with surface above
| 0
|
75,681
| 20,955,688,904
|
IssuesEvent
|
2022-03-27 04:03:44
|
hexops/mach
|
https://api.github.com/repos/hexops/mach
|
closed
|
gpu-dawn: need to fix Zig issue "error.Unexpected: GetLastError(206): The filename or extension is too long."
|
bug build-system gpu-dawn windows
|
This is one issue preventing gpu-dawn from building on Windows.
On Windows there is a 32 KiB limit to the arguments that are passed to a program via `CreateProcess`. The Zig `Builder` quickly exceeds this in a `zig build-lib` command when we're trying to build Dawn on Windows as a single static library.
|
1.0
|
gpu-dawn: need to fix Zig issue "error.Unexpected: GetLastError(206): The filename or extension is too long." - This is one issue preventing gpu-dawn from building on Windows.
On Windows there is a 32 KiB limit to the arguments that are passed to a program via `CreateProcess`. The Zig `Builder` quickly exceeds this in a `zig build-lib` command when we're trying to build Dawn on Windows as a single static library.
|
non_process
|
gpu dawn need to fix zig issue error unexpected getlasterror the filename or extension is too long this is one issue preventing gpu dawn from building on windows on windows there is a kib limit to the arguments that are passed to a program via createprocess the zig builder quickly exceeds this in a zig build lib command when we re trying to build dawn on windows as a single static library
| 0
|
104,330
| 11,403,866,263
|
IssuesEvent
|
2020-01-31 08:26:58
|
visjs/vis-timeline
|
https://api.github.com/repos/visjs/vis-timeline
|
closed
|
exclude moment from bundle by default?
|
documentation
|
Since #9 it is possible to exclude external libraries (e.g. moment) from the build.
The question is should be exclude e.g. `moment` by default? This would be a breaking change because than the user would always need to import `moment` manually.
What do you folks think?
|
1.0
|
exclude moment from bundle by default? - Since #9 it is possible to exclude external libraries (e.g. moment) from the build.
The question is should be exclude e.g. `moment` by default? This would be a breaking change because than the user would always need to import `moment` manually.
What do you folks think?
|
non_process
|
exclude moment from bundle by default since it is possible to exclude external libraries e g moment from the build the question is should be exclude e g moment by default this would be a breaking change because than the user would always need to import moment manually what do you folks think
| 0
|
136,559
| 5,284,624,086
|
IssuesEvent
|
2017-02-08 01:02:39
|
End-to-end-provenance/RDataTracker
|
https://api.github.com/repos/End-to-end-provenance/RDataTracker
|
closed
|
Error linked to "trycatch" of last, fully executable function instead of function producing the error
|
help wanted low priority
|
This is not a bug, but an un-intuitive feature. The "trycatch" does link to the correct line the produces the error via a right-click and click "show code" in DDG-Explorer, which is informative.
It would be great if the graph itself reflected the connection between the error and the actual function call that generated the error.
This would make the error and its relation to the other nodes (i.e. the data generating the error) immediately visible in the graph (i.e. as opposed to "trycatch", which is not a function associated with the script itself).
@blernermhc @margoseltzer @moepwintphyu1996 @tfjmp @erboose
|
1.0
|
Error linked to "trycatch" of last, fully executable function instead of function producing the error - This is not a bug, but an un-intuitive feature. The "trycatch" does link to the correct line the produces the error via a right-click and click "show code" in DDG-Explorer, which is informative.
It would be great if the graph itself reflected the connection between the error and the actual function call that generated the error.
This would make the error and its relation to the other nodes (i.e. the data generating the error) immediately visible in the graph (i.e. as opposed to "trycatch", which is not a function associated with the script itself).
@blernermhc @margoseltzer @moepwintphyu1996 @tfjmp @erboose
|
non_process
|
error linked to trycatch of last fully executable function instead of function producing the error this is not a bug but an un intuitive feature the trycatch does link to the correct line the produces the error via a right click and click show code in ddg explorer which is informative it would be great if the graph itself reflected the connection between the error and the actual function call that generated the error this would make the error and its relation to the other nodes i e the data generating the error immediately visible in the graph i e as opposed to trycatch which is not a function associated with the script itself blernermhc margoseltzer tfjmp erboose
| 0
|
99,530
| 20,981,457,065
|
IssuesEvent
|
2022-03-28 20:23:24
|
redhat-developer/quarkus-ls
|
https://api.github.com/repos/redhat-developer/quarkus-ls
|
closed
|
CodeAction to add ?? at the end of the object part for UndefinedObject
|
code action qute template-file
|
It should be nice to provide a new code action to set the part as optional with `??`
Given this template:
`{foo}`
foo is higlighted as `UndefinedObject`, it should be nice to provide code action which add `??` like this:
`{foo??}`
|
1.0
|
CodeAction to add ?? at the end of the object part for UndefinedObject - It should be nice to provide a new code action to set the part as optional with `??`
Given this template:
`{foo}`
foo is higlighted as `UndefinedObject`, it should be nice to provide code action which add `??` like this:
`{foo??}`
|
non_process
|
codeaction to add at the end of the object part for undefinedobject it should be nice to provide a new code action to set the part as optional with given this template foo foo is higlighted as undefinedobject it should be nice to provide code action which add like this foo
| 0
|
16,855
| 22,114,074,382
|
IssuesEvent
|
2022-06-02 00:47:44
|
hashgraph/hedera-json-rpc-relay
|
https://api.github.com/repos/hashgraph/hedera-json-rpc-relay
|
opened
|
Add acceptance test support for eth_sendRawTransaction using an EIP 155 transaction
|
enhancement P2 process
|
### Problem
During the setup of acceptance tests the `eth_sendRawTransaction` flow for EIP 155 produced errors.
As such it was removed.
Error was
```
err: {
"type": "PrecheckStatusError",
"message": "transaction 0.0.2@1654127819.276547659 failed precheck with status WRONG_CHAIN_ID",
"stack":
StatusError: transaction 0.0.2@1654127819.276547659 failed precheck with status WRONG_CHAIN_ID
at new PrecheckStatusError (.../hedera-json-rpc-relay/packages/relay/node_modules/@hashgraph/sdk/lib/PrecheckStatusError.cjs:43:5)
at EthereumTransaction._mapStatusError (.../hedera-json-rpc-relay/packages/relay/node_modules/@hashgraph/sdk/lib/transaction/Transaction.cjs:1122:12)
at EthereumTransaction.execute (.../hedera-json-rpc-relay/packages/relay/node_modules/@hashgraph/sdk/lib/Executable.cjs:519:22)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
"name": "StatusError",
"status": {
"_code": 311
},
```
### Solution
Add a test case that supports EIP_155 raw transaction submission
### Alternatives
_No response_
|
1.0
|
Add acceptance test support for eth_sendRawTransaction using an EIP 155 transaction - ### Problem
During the setup of acceptance tests the `eth_sendRawTransaction` flow for EIP 155 produced errors.
As such it was removed.
Error was
```
err: {
"type": "PrecheckStatusError",
"message": "transaction 0.0.2@1654127819.276547659 failed precheck with status WRONG_CHAIN_ID",
"stack":
StatusError: transaction 0.0.2@1654127819.276547659 failed precheck with status WRONG_CHAIN_ID
at new PrecheckStatusError (.../hedera-json-rpc-relay/packages/relay/node_modules/@hashgraph/sdk/lib/PrecheckStatusError.cjs:43:5)
at EthereumTransaction._mapStatusError (.../hedera-json-rpc-relay/packages/relay/node_modules/@hashgraph/sdk/lib/transaction/Transaction.cjs:1122:12)
at EthereumTransaction.execute (.../hedera-json-rpc-relay/packages/relay/node_modules/@hashgraph/sdk/lib/Executable.cjs:519:22)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
"name": "StatusError",
"status": {
"_code": 311
},
```
### Solution
Add a test case that supports EIP_155 raw transaction submission
### Alternatives
_No response_
|
process
|
add acceptance test support for eth sendrawtransaction using an eip transaction problem during the setup of acceptance tests the eth sendrawtransaction flow for eip produced errors as such it was removed error was err type precheckstatuserror message transaction failed precheck with status wrong chain id stack statuserror transaction failed precheck with status wrong chain id at new precheckstatuserror hedera json rpc relay packages relay node modules hashgraph sdk lib precheckstatuserror cjs at ethereumtransaction mapstatuserror hedera json rpc relay packages relay node modules hashgraph sdk lib transaction transaction cjs at ethereumtransaction execute hedera json rpc relay packages relay node modules hashgraph sdk lib executable cjs at processticksandrejections node internal process task queues name statuserror status code solution add a test case that supports eip raw transaction submission alternatives no response
| 1
|
213,721
| 7,255,712,465
|
IssuesEvent
|
2018-02-16 15:44:18
|
aa-software2112/SOEN341-W2018
|
https://api.github.com/repos/aa-software2112/SOEN341-W2018
|
closed
|
Create Get_User_Answer SQL Query
|
Priority 5
|
The query is used in the forum page to get the answers and related information from several tables of the database such as the question.question_id, question.question_title, answer.answer_body, answer.date&time_answered and the answer_score.
|
1.0
|
Create Get_User_Answer SQL Query - The query is used in the forum page to get the answers and related information from several tables of the database such as the question.question_id, question.question_title, answer.answer_body, answer.date&time_answered and the answer_score.
|
non_process
|
create get user answer sql query the query is used in the forum page to get the answers and related information from several tables of the database such as the question question id question question title answer answer body answer date time answered and the answer score
| 0
|
87,217
| 25,073,538,119
|
IssuesEvent
|
2022-11-07 13:58:43
|
bcpierce00/unison
|
https://api.github.com/repos/bcpierce00/unison
|
opened
|
Add release artifact with documentation
|
impact-low build effort-medium
|
It would be nice to have a CI-produced artifact for releases that has a built manual (in all formats) and files like README.md, a future BUILDING.md, NEWS.md, etc. Then, there is no need to have any of those in the per-os-per-cpu-per-ocaml artifacts. However, it is important not to go down the path of being a packaging system -- the point of this is to provide something a packaging system build script can use.
|
1.0
|
Add release artifact with documentation - It would be nice to have a CI-produced artifact for releases that has a built manual (in all formats) and files like README.md, a future BUILDING.md, NEWS.md, etc. Then, there is no need to have any of those in the per-os-per-cpu-per-ocaml artifacts. However, it is important not to go down the path of being a packaging system -- the point of this is to provide something a packaging system build script can use.
|
non_process
|
add release artifact with documentation it would be nice to have a ci produced artifact for releases that has a built manual in all formats and files like readme md a future building md news md etc then there is no need to have any of those in the per os per cpu per ocaml artifacts however it is important not to go down the path of being a packaging system the point of this is to provide something a packaging system build script can use
| 0
|
9,835
| 12,829,662,647
|
IssuesEvent
|
2020-07-06 23:38:35
|
GoogleCloudPlatform/python-docs-samples
|
https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples
|
closed
|
Split testing container from testing-infra-docker
|
help wanted type: process
|
Currently we use the currently use this [Dockerfile](https://github.com/googleapis/testing-infra-docker/tree/master/python/googleapis/python-multi) for testing. However we really should have our own Dockerfile with our own dependencies here in python-docs-samples.
Here are the steps that need to be taken to do this:
1. Create a dockerfile based on python:3.6 here in the repo with the dependencies necessary for our tests (maybe in root or `.kokoro`?)
2. Create a Kokoro continuous job that checks if the Dockerfile has changed, and if so pushes a new version of the container
3. Update our tests to use this image instead of the current `python-multi`.
|
1.0
|
Split testing container from testing-infra-docker - Currently we use the currently use this [Dockerfile](https://github.com/googleapis/testing-infra-docker/tree/master/python/googleapis/python-multi) for testing. However we really should have our own Dockerfile with our own dependencies here in python-docs-samples.
Here are the steps that need to be taken to do this:
1. Create a dockerfile based on python:3.6 here in the repo with the dependencies necessary for our tests (maybe in root or `.kokoro`?)
2. Create a Kokoro continuous job that checks if the Dockerfile has changed, and if so pushes a new version of the container
3. Update our tests to use this image instead of the current `python-multi`.
|
process
|
split testing container from testing infra docker currently we use the currently use this for testing however we really should have our own dockerfile with our own dependencies here in python docs samples here are the steps that need to be taken to do this create a dockerfile based on python here in the repo with the dependencies necessary for our tests maybe in root or kokoro create a kokoro continuous job that checks if the dockerfile has changed and if so pushes a new version of the container update our tests to use this image instead of the current python multi
| 1
|
148,259
| 19,529,183,595
|
IssuesEvent
|
2021-12-30 13:40:41
|
developerone12/WebGoat-WhiteSource-Bolt
|
https://api.github.com/repos/developerone12/WebGoat-WhiteSource-Bolt
|
opened
|
WS-2021-0174 (Medium) detected in spring-beans-3.2.4.RELEASE.jar
|
security vulnerability
|
## WS-2021-0174 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-3.2.4.RELEASE.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/SpringSource/spring-framework">https://github.com/SpringSource/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/3.2.4.RELEASE/spring-beans-3.2.4.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-webmvc-3.2.4.RELEASE.jar (Root Library)
- :x: **spring-beans-3.2.4.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/developerone12/WebGoat-WhiteSource-Bolt/commit/c42e663814e4b88294ff90339ad577ca1afcf531">c42e663814e4b88294ff90339ad577ca1afcf531</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In spring-framework, versions 4.0.0 to 4.0.1 and 3.0.0 to 3.2.18, are vulnerable against CGLIB memory leak for method injection as a result of mishandled callbacks and non-static classes.
<p>Publish Date: 2021-06-29
<p>URL: <a href=https://github.com/spring-projects/spring-framework/commit/8028eae786ff36ea58df9a385319bf045795fa77>WS-2021-0174</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/spring-projects/spring-framework/releases/tag/v4.0.2.RELEASE">https://github.com/spring-projects/spring-framework/releases/tag/v4.0.2.RELEASE</a></p>
<p>Release Date: 2021-06-29</p>
<p>Fix Resolution: org.springframework:spring-beans:4.0.2.RELEASE</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
WS-2021-0174 (Medium) detected in spring-beans-3.2.4.RELEASE.jar - ## WS-2021-0174 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-3.2.4.RELEASE.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/SpringSource/spring-framework">https://github.com/SpringSource/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/3.2.4.RELEASE/spring-beans-3.2.4.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-webmvc-3.2.4.RELEASE.jar (Root Library)
- :x: **spring-beans-3.2.4.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/developerone12/WebGoat-WhiteSource-Bolt/commit/c42e663814e4b88294ff90339ad577ca1afcf531">c42e663814e4b88294ff90339ad577ca1afcf531</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In spring-framework, versions 4.0.0 to 4.0.1 and 3.0.0 to 3.2.18, are vulnerable against CGLIB memory leak for method injection as a result of mishandled callbacks and non-static classes.
<p>Publish Date: 2021-06-29
<p>URL: <a href=https://github.com/spring-projects/spring-framework/commit/8028eae786ff36ea58df9a385319bf045795fa77>WS-2021-0174</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/spring-projects/spring-framework/releases/tag/v4.0.2.RELEASE">https://github.com/spring-projects/spring-framework/releases/tag/v4.0.2.RELEASE</a></p>
<p>Release Date: 2021-06-29</p>
<p>Fix Resolution: org.springframework:spring-beans:4.0.2.RELEASE</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
ws medium detected in spring beans release jar ws medium severity vulnerability vulnerable library spring beans release jar spring beans library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org springframework spring beans release spring beans release jar dependency hierarchy spring webmvc release jar root library x spring beans release jar vulnerable library found in head commit a href found in base branch master vulnerability details in spring framework versions to and to are vulnerable against cglib memory leak for method injection as a result of mishandled callbacks and non static classes publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring beans release step up your open source security game with whitesource
| 0
|
355,350
| 25,175,909,427
|
IssuesEvent
|
2022-11-11 09:14:33
|
wxy1203/pe
|
https://api.github.com/repos/wxy1203/pe
|
opened
|
Not specific on the target user
|
type.DocumentationBug severity.Medium
|
## Unspecific details of who is the target user
- As a user, I may have different situation of job request. However, in the user guide, I couldn't have clear idea of what kind of service can be provided for me. As in, if I am the target user of the app?
- Suggestion here is to make a clear figure for the app, so that the people in need can know if they are the target user in a short time.
<!--session: 1668153082943-fc94d955-c875-4c05-8499-c4fed617c788-->
<!--Version: Web v3.4.4-->
|
1.0
|
Not specific on the target user - ## Unspecific details of who is the target user
- As a user, I may have different situation of job request. However, in the user guide, I couldn't have clear idea of what kind of service can be provided for me. As in, if I am the target user of the app?
- Suggestion here is to make a clear figure for the app, so that the people in need can know if they are the target user in a short time.
<!--session: 1668153082943-fc94d955-c875-4c05-8499-c4fed617c788-->
<!--Version: Web v3.4.4-->
|
non_process
|
not specific on the target user unspecific details of who is the target user as a user i may have different situation of job request however in the user guide i couldn t have clear idea of what kind of service can be provided for me as in if i am the target user of the app suggestion here is to make a clear figure for the app so that the people in need can know if they are the target user in a short time
| 0
|
841
| 3,144,229,505
|
IssuesEvent
|
2015-09-14 12:18:37
|
xdoo/vaadin-demo
|
https://api.github.com/repos/xdoo/vaadin-demo
|
closed
|
Bibliothek anlegen für: Service-Info
|
API enhancement ready technical_requirement
|
Durch den generativen Ansatz (#3) ist es sinnvoll die Service-Info (eventuell mit weiteren zusammengehörigen Teilen) in eine eigene wiederverwendbare Bibliothek auszulagern.
|
1.0
|
Bibliothek anlegen für: Service-Info - Durch den generativen Ansatz (#3) ist es sinnvoll die Service-Info (eventuell mit weiteren zusammengehörigen Teilen) in eine eigene wiederverwendbare Bibliothek auszulagern.
|
non_process
|
bibliothek anlegen für service info durch den generativen ansatz ist es sinnvoll die service info eventuell mit weiteren zusammengehörigen teilen in eine eigene wiederverwendbare bibliothek auszulagern
| 0
|
37,251
| 4,790,537,124
|
IssuesEvent
|
2016-10-31 09:02:22
|
Newb1et/Otakunity-Designs
|
https://api.github.com/repos/Newb1et/Otakunity-Designs
|
opened
|
Homepage (Landing)
|
Implement Design
|
Finally final! Here it is!
**Background**
The background image has a gradient overlay of pure black, 60%-0%.
**Homepage Navbar**
This navbar is different from the one within the site itself. It has 50px height, 50% opaque, and pure black color.
Upon hovering on any text/icon on the navbar, a Cyan500, 5px height bar should come up beneath it. And show the bar permanently if on the said section of the homepage. For example here, we are in the landing page, so it shows the highlight permanently.
Its the same here for the social media site buttons, it should also show the highlight bar on hover, the buttons/icons have a full black background.
**Buttons**
The buttons are rounded rectangles rotated at 45 degrees, and 50% opaque, upon hover a subtle glow should appear on the button. These buttons may be changed in the future but do implement it.
|
1.0
|
Homepage (Landing) - Finally final! Here it is!
**Background**
The background image has a gradient overlay of pure black, 60%-0%.
**Homepage Navbar**
This navbar is different from the one within the site itself. It has 50px height, 50% opaque, and pure black color.
Upon hovering on any text/icon on the navbar, a Cyan500, 5px height bar should come up beneath it. And show the bar permanently if on the said section of the homepage. For example here, we are in the landing page, so it shows the highlight permanently.
Its the same here for the social media site buttons, it should also show the highlight bar on hover, the buttons/icons have a full black background.
**Buttons**
The buttons are rounded rectangles rotated at 45 degrees, and 50% opaque, upon hover a subtle glow should appear on the button. These buttons may be changed in the future but do implement it.
|
non_process
|
homepage landing finally final here it is background the background image has a gradient overlay of pure black homepage navbar this navbar is different from the one within the site itself it has height opaque and pure black color upon hovering on any text icon on the navbar a height bar should come up beneath it and show the bar permanently if on the said section of the homepage for example here we are in the landing page so it shows the highlight permanently its the same here for the social media site buttons it should also show the highlight bar on hover the buttons icons have a full black background buttons the buttons are rounded rectangles rotated at degrees and opaque upon hover a subtle glow should appear on the button these buttons may be changed in the future but do implement it
| 0
|
5,451
| 8,309,324,755
|
IssuesEvent
|
2018-09-24 05:45:59
|
ruby-processing/propane
|
https://api.github.com/repos/ruby-processing/propane
|
closed
|
jdk9 can't run FX2D sketches even with runPropane() fix
|
waiting for vanilla processing
|
### Environment
NB: jdk9.0.4 from oracle includes javafx jars.
Using custom propane (compiled with jdk9.0.4 targeting jdk8) modified to use `public runPropane()` instead of `protected runSketch()` test sketch see https://github.com/ruby-processing/propane-examples/blob/master/processing_app/basics/arrays/array_objects.rb.
### Expected Behavior
Sketch runs fine with open-jdk8 (with javafx), and also with default renderer (and jdk9.0.4).
### Actual Behavior
```bash
Exception in Application start method
java.lang.RuntimeException: Exception in Application start method
at javafx.graphics/com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:973)
at javafx.graphics/com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:198)
at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: java.lang.NoSuchMethodError: com.sun.glass.ui.Screen.getRenderScale()F
at processing.javafx.PSurfaceFX$PApplicationFX.start(PSurfaceFX.java:249)
at javafx.graphics/com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$9(LauncherImpl.java:919)
at javafx.graphics/com.sun.javafx.application.PlatformImpl.lambda$runAndWait$11(PlatformImpl.java:449)
at javafx.graphics/com.sun.javafx.application.PlatformImpl.lambda$runLater$9(PlatformImpl.java:418)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at javafx.graphics/com.sun.javafx.application.PlatformImpl.lambda$runLater$10(PlatformImpl.java:417)
at javafx.graphics/com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:96)
at javafx.graphics/com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
at javafx.graphics/com.sun.glass.ui.gtk.GtkApplication.lambda$runLoop$11(GtkApplication.java:277)
... 1 more
```
|
1.0
|
jdk9 can't run FX2D sketches even with runPropane() fix - ### Environment
NB: jdk9.0.4 from oracle includes javafx jars.
Using custom propane (compiled with jdk9.0.4 targeting jdk8) modified to use `public runPropane()` instead of `protected runSketch()` test sketch see https://github.com/ruby-processing/propane-examples/blob/master/processing_app/basics/arrays/array_objects.rb.
### Expected Behavior
Sketch runs fine with open-jdk8 (with javafx), and also with default renderer (and jdk9.0.4).
### Actual Behavior
```bash
Exception in Application start method
java.lang.RuntimeException: Exception in Application start method
at javafx.graphics/com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:973)
at javafx.graphics/com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:198)
at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: java.lang.NoSuchMethodError: com.sun.glass.ui.Screen.getRenderScale()F
at processing.javafx.PSurfaceFX$PApplicationFX.start(PSurfaceFX.java:249)
at javafx.graphics/com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$9(LauncherImpl.java:919)
at javafx.graphics/com.sun.javafx.application.PlatformImpl.lambda$runAndWait$11(PlatformImpl.java:449)
at javafx.graphics/com.sun.javafx.application.PlatformImpl.lambda$runLater$9(PlatformImpl.java:418)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at javafx.graphics/com.sun.javafx.application.PlatformImpl.lambda$runLater$10(PlatformImpl.java:417)
at javafx.graphics/com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:96)
at javafx.graphics/com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
at javafx.graphics/com.sun.glass.ui.gtk.GtkApplication.lambda$runLoop$11(GtkApplication.java:277)
... 1 more
```
|
process
|
can t run sketches even with runpropane fix environment nb from oracle includes javafx jars using custom propane compiled with targeting modified to use public runpropane instead of protected runsketch test sketch see expected behavior sketch runs fine with open with javafx and also with default renderer and actual behavior bash exception in application start method java lang runtimeexception exception in application start method at javafx graphics com sun javafx application launcherimpl launcherimpl java at javafx graphics com sun javafx application launcherimpl lambda launchapplication launcherimpl java at java base java lang thread run thread java caused by java lang nosuchmethoderror com sun glass ui screen getrenderscale f at processing javafx psurfacefx papplicationfx start psurfacefx java at javafx graphics com sun javafx application launcherimpl lambda launcherimpl java at javafx graphics com sun javafx application platformimpl lambda runandwait platformimpl java at javafx graphics com sun javafx application platformimpl lambda runlater platformimpl java at java base java security accesscontroller doprivileged native method at javafx graphics com sun javafx application platformimpl lambda runlater platformimpl java at javafx graphics com sun glass ui invokelaterdispatcher future run invokelaterdispatcher java at javafx graphics com sun glass ui gtk gtkapplication runloop native method at javafx graphics com sun glass ui gtk gtkapplication lambda runloop gtkapplication java more
| 1
|
9,379
| 12,378,316,091
|
IssuesEvent
|
2020-05-19 10:28:21
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
merge vector layers: after merging field "source" has incorrect value
|
Bug Feedback Processing
|
I have problem with QGIS 3.12.2, after merging layers is not added correct source field value from layer name but only "INPUT".
Reproduction:
1) I add GDB layers
2) I run tool "merge vector layers"
3) I select all layers, and check true "add source information"
4) RUN
5) Now, Merged layer has field "source" to fill by value "INPUT", not layer names
|
1.0
|
merge vector layers: after merging field "source" has incorrect value - I have problem with QGIS 3.12.2, after merging layers is not added correct source field value from layer name but only "INPUT".
Reproduction:
1) I add GDB layers
2) I run tool "merge vector layers"
3) I select all layers, and check true "add source information"
4) RUN
5) Now, Merged layer has field "source" to fill by value "INPUT", not layer names
|
process
|
merge vector layers after merging field source has incorrect value i have problem with qgis after merging layers is not added correct source field value from layer name but only input reproduction i add gdb layers i run tool merge vector layers i select all layers and check true add source information run now merged layer has field source to fill by value input not layer names
| 1
|
16,618
| 6,254,690,933
|
IssuesEvent
|
2017-07-14 03:24:46
|
cjgratacos/backup-tool
|
https://api.github.com/repos/cjgratacos/backup-tool
|
closed
|
Travis build #2216 failed
|
build failed help wanted
|
Travis Deployment #2216 failed for branch:[master]
The Travis CI deployment number:**2216** failed for the branch:**[master]**.
Build URL: https://travis-ci.org/travis-ci/docs-travis-ci-com/builds/252767624
Build message: Mention skip_upload_docs option
Accordingly to #660, `skip_upload_docs` is now actually required given that PyPI no longer supports uploading docs.
|
1.0
|
Travis build #2216 failed - Travis Deployment #2216 failed for branch:[master]
The Travis CI deployment number:**2216** failed for the branch:**[master]**.
Build URL: https://travis-ci.org/travis-ci/docs-travis-ci-com/builds/252767624
Build message: Mention skip_upload_docs option
Accordingly to #660, `skip_upload_docs` is now actually required given that PyPI no longer supports uploading docs.
|
non_process
|
travis build failed travis deployment failed for branch the travis ci deployment number failed for the branch build url build message mention skip upload docs option accordingly to skip upload docs is now actually required given that pypi no longer supports uploading docs
| 0
|
170,770
| 27,014,351,239
|
IssuesEvent
|
2023-02-10 17:56:45
|
July249/shopping_mall
|
https://api.github.com/repos/July249/shopping_mall
|
closed
|
[issue] ProductInfo 구현을 위해 Price props 속성 중 after 가상 요소 display none 컨트롤 스타일 추가
|
design fix Molecules
|
## 👨💻 무엇을 하실 건지 설명해주세요!
- ProductInfo 구현을 위해 Price props 속성 중 after 가상 요소 display none 컨트롤 스타일 추가
- 금액이 표시되지 않는 경우에 한하여 addIUnit 속성에 boolean 값으로 false를 전달하여 after 가상요소를 나타내지 않습니다.
## 🤔 구현방법 및 예상 동작
-
## ⭐ 특이사항
-
|
1.0
|
[issue] ProductInfo 구현을 위해 Price props 속성 중 after 가상 요소 display none 컨트롤 스타일 추가 - ## 👨💻 무엇을 하실 건지 설명해주세요!
- ProductInfo 구현을 위해 Price props 속성 중 after 가상 요소 display none 컨트롤 스타일 추가
- 금액이 표시되지 않는 경우에 한하여 addIUnit 속성에 boolean 값으로 false를 전달하여 after 가상요소를 나타내지 않습니다.
## 🤔 구현방법 및 예상 동작
-
## ⭐ 특이사항
-
|
non_process
|
productinfo 구현을 위해 price props 속성 중 after 가상 요소 display none 컨트롤 스타일 추가 👨💻 무엇을 하실 건지 설명해주세요 productinfo 구현을 위해 price props 속성 중 after 가상 요소 display none 컨트롤 스타일 추가 금액이 표시되지 않는 경우에 한하여 addiunit 속성에 boolean 값으로 false를 전달하여 after 가상요소를 나타내지 않습니다 🤔 구현방법 및 예상 동작 ⭐ 특이사항
| 0
|
21,418
| 2,640,233,741
|
IssuesEvent
|
2015-03-11 10:36:29
|
e-hulp/HelpIM
|
https://api.github.com/repos/e-hulp/HelpIM
|
opened
|
Typing notification fails in second chat
|
bug Medium priority xmpptk
|
Unverified report:
At end of a chat: click "stop" and then "open chat" then next chat the typing notification fails. Logging out fully restores it.
|
1.0
|
Typing notification fails in second chat - Unverified report:
At end of a chat: click "stop" and then "open chat" then next chat the typing notification fails. Logging out fully restores it.
|
non_process
|
typing notification fails in second chat unverified report at end of a chat click stop and then open chat then next chat the typing notification fails logging out fully restores it
| 0
|
127,741
| 17,358,550,967
|
IssuesEvent
|
2021-07-29 17:13:43
|
nebraska-silicon-lab/Hardware
|
https://api.github.com/repos/nebraska-silicon-lab/Hardware
|
closed
|
2nd ETL Cooling Plate Section
|
Design Finalized Fabrication in Progress High Priority
|
Fabricate another disc section just as in #5. Build to same design as before.
Work order: [link](https://github.com/nebraska-silicon-lab/Hardware/blob/master/Work%20Orders/2021_02_ETL_Second-Cooling-Plate.pdf)
|
1.0
|
2nd ETL Cooling Plate Section - Fabricate another disc section just as in #5. Build to same design as before.
Work order: [link](https://github.com/nebraska-silicon-lab/Hardware/blob/master/Work%20Orders/2021_02_ETL_Second-Cooling-Plate.pdf)
|
non_process
|
etl cooling plate section fabricate another disc section just as in build to same design as before work order
| 0
|
74,871
| 25,373,732,888
|
IssuesEvent
|
2022-11-21 12:35:10
|
SeleniumHQ/selenium
|
https://api.github.com/repos/SeleniumHQ/selenium
|
closed
|
[🐛 Bug]: Grid crashes with Apache as reverse Proxy
|
C-grid I-defect
|
### What happened?
I need to connect to our selenium grid over a secure connection (https). I couldnt figure out a way to do it with the functions that selenium delivers so i decided to use Apaches httpd as an reverse proxy.
After a couple of days (maybe a week or less) it becomes unreachable. Even without running test on that grid. Image if i connect with http://[server]:4444/ui
Image if i connect with https://[server]
The default log from grid and nodes says nothing. Next i am going to put the log-level to debug.
### How can we reproduce the issue?
```shell
Grid setup:
podman run -d -p 4442-4444:4442-4444 \
-e "TZ=Europe/Berlin" \
--name selenium-hub [hub-image]
podman run -d -p 5555:5555 \
--shm-size 4g -e "TZ=Europe/Berlin" \
-e SE_EVENT_BUS_HOST=[server] \
-e SE_EVENT_BUS_PUBLISH_PORT=4442 -e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 \
-e SE_NODE_HOST=[server] -e SE_NODE_PORT=5555 \
-e SE_NODE_SESSION_TIMEOUT="300" -e SE_NODE_MAX_SESSIONS=1 \
--name selenium-node1 [node-chrome-image]
For Apache:
{
install httpd, mod_ssl, openssl
create ssl-cert with openssl
}
Run Apache:
systemctl start httpd
nano /etc/httpd/conf.d/default-site.conf
content:{
<VirtualHost *:443>
ServerName [servername]
SSLEngine On
SSLCertificateFile [pathToFile].crt
SSLCertificateKeyFile [pathToFile].key
ProxyRequests Off
ProxyPreserveHost On
ProxyPass / http://[servername]:4444/
ProxyPassReverse / http://[servername]:4444/
</VirtualHost>
<VirtualHost *:80>
ProxyPreserveHost On
ProxyPass / http://[servername]:4444/
ProxyPassReverse / http://[servername]:4444/
</VirtualHost>
}
systemctl restart httpd
```
### Relevant log output
```shell
2022-09-09 14:11:15,466 INFO Included extra file "/etc/supervisor/conf.d/selenium-grid-hub.conf" during parsing
2022-09-09 14:11:15,469 INFO RPC interface 'supervisor' initialized
2022-09-09 14:11:15,470 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-09-09 14:11:15,470 INFO supervisord started with pid 8
2022-09-09 14:11:16,473 INFO spawned: 'selenium-grid-hub' with pid 10
14:11:16.809 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
14:11:16.813 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
2022-09-09 14:11:16,814 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
14:11:16.904 INFO [BoundZmqEventBus.<init>] - XPUB binding to [binding to tcp://*:4442, advertising as tcp:// [ip]:4442], XSUB binding to [binding to tcp://*:4443, advertising as tcp://[ip]:4443]
14:11:16.955 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp:// [ip]:4442 and tcp:// [ip]:4443
14:11:16.981 INFO [UnboundZmqEventBus.<init>] - Sockets created
14:11:17.983 INFO [UnboundZmqEventBus.<init>] - Event bus ready
14:11:18.641 INFO [Hub.execute] - Started Selenium Hub 4.4.0 (revision e5c75ed026a): http:// [ip]:4444
14:11:19.401 INFO [Node.<init>] - Binding additional locator mechanisms: name, relative, id
14:11:20.069 INFO [GridModel.setAvailability] - Switching Node 527e5556-6102-4f76-818b-dcd27454df18 (uri: http:// [servername]:5555) from DOWN to UP
14:11:20.069 INFO [LocalDistributor.add] - Added node 527e5556-6102-4f76-818b-dcd27454df18 at http:// [servername]:5555. Health check every 120s
14:11:20.073 INFO [Node.<init>] - Binding additional locator mechanisms: relative, id, name
14:11:20.207 INFO [GridModel.setAvailability] - Switching Node b73d743e-8c3a-4ea5-baad-926a89bc7a4b (uri: http:// [servername]:5556) from DOWN to UP
14:11:20.208 INFO [LocalDistributor.add] - Added node b73d743e-8c3a-4ea5-baad-926a89bc7a4b at http:// [servername]:5556. Health check every 120s
```
### Operating System
RHEL 8
### Selenium version
4.4.0
### What are the browser(s) and version(s) where you see this issue?
Chrome
### What are the browser driver(s) and version(s) where you see this issue?
105
### Are you using Selenium Grid?
4.4.0
|
1.0
|
[🐛 Bug]: Grid crashes with Apache as reverse Proxy - ### What happened?
I need to connect to our selenium grid over a secure connection (https). I couldnt figure out a way to do it with the functions that selenium delivers so i decided to use Apaches httpd as an reverse proxy.
After a couple of days (maybe a week or less) it becomes unreachable. Even without running test on that grid. Image if i connect with http://[server]:4444/ui
Image if i connect with https://[server]
The default log from grid and nodes says nothing. Next i am going to put the log-level to debug.
### How can we reproduce the issue?
```shell
Grid setup:
podman run -d -p 4442-4444:4442-4444 \
-e "TZ=Europe/Berlin" \
--name selenium-hub [hub-image]
podman run -d -p 5555:5555 \
--shm-size 4g -e "TZ=Europe/Berlin" \
-e SE_EVENT_BUS_HOST=[server] \
-e SE_EVENT_BUS_PUBLISH_PORT=4442 -e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 \
-e SE_NODE_HOST=[server] -e SE_NODE_PORT=5555 \
-e SE_NODE_SESSION_TIMEOUT="300" -e SE_NODE_MAX_SESSIONS=1 \
--name selenium-node1 [node-chrome-image]
For Apache:
{
install httpd, mod_ssl, openssl
create ssl-cert with openssl
}
Run Apache:
systemctl start httpd
nano /etc/httpd/conf.d/default-site.conf
content:{
<VirtualHost *:443>
ServerName [servername]
SSLEngine On
SSLCertificateFile [pathToFile].crt
SSLCertificateKeyFile [pathToFile].key
ProxyRequests Off
ProxyPreserveHost On
ProxyPass / http://[servername]:4444/
ProxyPassReverse / http://[servername]:4444/
</VirtualHost>
<VirtualHost *:80>
ProxyPreserveHost On
ProxyPass / http://[servername]:4444/
ProxyPassReverse / http://[servername]:4444/
</VirtualHost>
}
systemctl restart httpd
```
### Relevant log output
```shell
2022-09-09 14:11:15,466 INFO Included extra file "/etc/supervisor/conf.d/selenium-grid-hub.conf" during parsing
2022-09-09 14:11:15,469 INFO RPC interface 'supervisor' initialized
2022-09-09 14:11:15,470 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-09-09 14:11:15,470 INFO supervisord started with pid 8
2022-09-09 14:11:16,473 INFO spawned: 'selenium-grid-hub' with pid 10
14:11:16.809 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
14:11:16.813 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
2022-09-09 14:11:16,814 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
14:11:16.904 INFO [BoundZmqEventBus.<init>] - XPUB binding to [binding to tcp://*:4442, advertising as tcp:// [ip]:4442], XSUB binding to [binding to tcp://*:4443, advertising as tcp://[ip]:4443]
14:11:16.955 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp:// [ip]:4442 and tcp:// [ip]:4443
14:11:16.981 INFO [UnboundZmqEventBus.<init>] - Sockets created
14:11:17.983 INFO [UnboundZmqEventBus.<init>] - Event bus ready
14:11:18.641 INFO [Hub.execute] - Started Selenium Hub 4.4.0 (revision e5c75ed026a): http:// [ip]:4444
14:11:19.401 INFO [Node.<init>] - Binding additional locator mechanisms: name, relative, id
14:11:20.069 INFO [GridModel.setAvailability] - Switching Node 527e5556-6102-4f76-818b-dcd27454df18 (uri: http:// [servername]:5555) from DOWN to UP
14:11:20.069 INFO [LocalDistributor.add] - Added node 527e5556-6102-4f76-818b-dcd27454df18 at http:// [servername]:5555. Health check every 120s
14:11:20.073 INFO [Node.<init>] - Binding additional locator mechanisms: relative, id, name
14:11:20.207 INFO [GridModel.setAvailability] - Switching Node b73d743e-8c3a-4ea5-baad-926a89bc7a4b (uri: http:// [servername]:5556) from DOWN to UP
14:11:20.208 INFO [LocalDistributor.add] - Added node b73d743e-8c3a-4ea5-baad-926a89bc7a4b at http:// [servername]:5556. Health check every 120s
```
### Operating System
RHEL 8
### Selenium version
4.4.0
### What are the browser(s) and version(s) where you see this issue?
Chrome
### What are the browser driver(s) and version(s) where you see this issue?
105
### Are you using Selenium Grid?
4.4.0
|
non_process
|
grid crashes with apache as reverse proxy what happened i need to connect to our selenium grid over a secure connection https i couldnt figure out a way to do it with the functions that selenium delivers so i decided to use apaches httpd as an reverse proxy after a couple of days maybe a week or less it becomes unreachable even without running test on that grid image if i connect with http ui image if i connect with https the default log from grid and nodes says nothing next i am going to put the log level to debug how can we reproduce the issue shell grid setup podman run d p e tz europe berlin name selenium hub podman run d p shm size e tz europe berlin e se event bus host e se event bus publish port e se event bus subscribe port e se node host e se node port e se node session timeout e se node max sessions name selenium for apache install httpd mod ssl openssl create ssl cert with openssl run apache systemctl start httpd nano etc httpd conf d default site conf content servername sslengine on sslcertificatefile crt sslcertificatekeyfile key proxyrequests off proxypreservehost on proxypass http proxypassreverse http proxypreservehost on proxypass http proxypassreverse http systemctl restart httpd relevant log output shell info included extra file etc supervisor conf d selenium grid hub conf during parsing info rpc interface supervisor initialized crit server unix http server running without any http authentication checking info supervisord started with pid info spawned selenium grid hub with pid info using the system default encoding info using opentelemetry for tracing info success selenium grid hub entered running state process has stayed up for than seconds startsecs info xpub binding to xsub binding to info connecting to tcp and tcp info sockets created info event bus ready info started selenium hub revision http info binding additional locator mechanisms name relative id info switching node uri http from down to up info added node at http health check every info binding additional locator mechanisms relative id name info switching node baad uri http from down to up info added node baad at http health check every operating system rhel selenium version what are the browser s and version s where you see this issue chrome what are the browser driver s and version s where you see this issue are you using selenium grid
| 0
|
276,731
| 20,997,844,923
|
IssuesEvent
|
2022-03-29 14:51:13
|
Cyclenerd/google-cloud-pricing-cost-calculator
|
https://api.github.com/repos/Cyclenerd/google-cloud-pricing-cost-calculator
|
opened
|
Documentation: Region changes
|
documentation
|
This thread automatically documents changes to Google Cloud regions. Subscribe to this issue if you want to be informed about new or deleted regions and machines types in regions.
|
1.0
|
Documentation: Region changes - This thread automatically documents changes to Google Cloud regions. Subscribe to this issue if you want to be informed about new or deleted regions and machines types in regions.
|
non_process
|
documentation region changes this thread automatically documents changes to google cloud regions subscribe to this issue if you want to be informed about new or deleted regions and machines types in regions
| 0
|
67,424
| 12,957,651,484
|
IssuesEvent
|
2020-07-20 10:03:14
|
propensive/fury
|
https://api.github.com/repos/propensive/fury
|
closed
|
rename `ImportPath` to `Pointer`
|
code minor
|
I find the name `ImportPath` a bit cumbersome, so let's call it `Pointer` everywhere.
|
1.0
|
rename `ImportPath` to `Pointer` - I find the name `ImportPath` a bit cumbersome, so let's call it `Pointer` everywhere.
|
non_process
|
rename importpath to pointer i find the name importpath a bit cumbersome so let s call it pointer everywhere
| 0
|
20,867
| 27,656,514,852
|
IssuesEvent
|
2023-03-12 02:00:09
|
lizhihao6/get-daily-arxiv-noti
|
https://api.github.com/repos/lizhihao6/get-daily-arxiv-noti
|
opened
|
New submissions for Fri, 10 Mar 23
|
event camera white balance isp compression image signal processing image signal process raw raw image events camera color contrast events AWB
|
## Keyword: events
### Taming Contrast Maximization for Learning Sequential, Low-latency, Event-based Optical Flow
- **Authors:** Federico Paredes-Vallés, Kirk Y. W. Scheper, Christophe De Wagter, Guido C. H. E. de Croon
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI); Machine Learning (cs.LG)
- **Arxiv link:** https://arxiv.org/abs/2303.05214
- **Pdf link:** https://arxiv.org/pdf/2303.05214
- **Abstract**
Event cameras have recently gained significant traction since they open up new avenues for low-latency and low-power solutions to complex computer vision problems. To unlock these solutions, it is necessary to develop algorithms that can leverage the unique nature of event data. However, the current state-of-the-art is still highly influenced by the frame-based literature, and usually fails to deliver on these promises. In this work, we take this into consideration and propose a novel self-supervised learning pipeline for the sequential estimation of event-based optical flow that allows for the scaling of the models to high inference frequencies. At its core, we have a continuously-running stateful neural model that is trained using a novel formulation of contrast maximization that makes it robust to nonlinearities and varying statistics in the input events. Results across multiple datasets confirm the effectiveness of our method, which establishes a new state of the art in terms of accuracy for approaches trained or optimized without ground truth.
### Understanding the Challenges and Opportunities of Pose-based Anomaly Detection
- **Authors:** Ghazal Alinezhad Noghre, Armin Danesh Pazho, Vinit Katariya, Hamed Tabkhi
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI)
- **Arxiv link:** https://arxiv.org/abs/2303.05463
- **Pdf link:** https://arxiv.org/pdf/2303.05463
- **Abstract**
Pose-based anomaly detection is a video-analysis technique for detecting anomalous events or behaviors by examining human pose extracted from the video frames. Utilizing pose data alleviates privacy and ethical issues. Also, computation-wise, the complexity of pose-based models is lower than pixel-based approaches. However, it introduces more challenges, such as noisy skeleton data, losing important pixel information, and not having enriched enough features. These problems are exacerbated by a lack of anomaly detection datasets that are good enough representatives of real-world scenarios. In this work, we analyze and quantify the characteristics of two well-known video anomaly datasets to better understand the difficulties of pose-based anomaly detection. We take a step forward, exploring the discriminating power of pose and trajectory for video anomaly detection and their effectiveness based on context. We believe these experiments are beneficial for a better comprehension of pose-based anomaly detection and the datasets currently available. This will aid researchers in tackling the task of anomaly detection with a more lucid perspective, accelerating the development of robust models with better performance.
## Keyword: event camera
### Taming Contrast Maximization for Learning Sequential, Low-latency, Event-based Optical Flow
- **Authors:** Federico Paredes-Vallés, Kirk Y. W. Scheper, Christophe De Wagter, Guido C. H. E. de Croon
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI); Machine Learning (cs.LG)
- **Arxiv link:** https://arxiv.org/abs/2303.05214
- **Pdf link:** https://arxiv.org/pdf/2303.05214
- **Abstract**
Event cameras have recently gained significant traction since they open up new avenues for low-latency and low-power solutions to complex computer vision problems. To unlock these solutions, it is necessary to develop algorithms that can leverage the unique nature of event data. However, the current state-of-the-art is still highly influenced by the frame-based literature, and usually fails to deliver on these promises. In this work, we take this into consideration and propose a novel self-supervised learning pipeline for the sequential estimation of event-based optical flow that allows for the scaling of the models to high inference frequencies. At its core, we have a continuously-running stateful neural model that is trained using a novel formulation of contrast maximization that makes it robust to nonlinearities and varying statistics in the input events. Results across multiple datasets confirm the effectiveness of our method, which establishes a new state of the art in terms of accuracy for approaches trained or optimized without ground truth.
## Keyword: events camera
There is no result
## Keyword: white balance
There is no result
## Keyword: color contrast
There is no result
## Keyword: AWB
### Toward Unsupervised Realistic Visual Question Answering
- **Authors:** Yuwei Zhang, Chih-Hui Ho, Nuno Vasconcelos
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2303.05068
- **Pdf link:** https://arxiv.org/pdf/2303.05068
- **Abstract**
The problem of realistic VQA (RVQA), where a model has to reject unanswerable questions (UQs) and answer answerable ones (AQs), is studied. We first point out 2 drawbacks in current RVQA research, where (1) datasets contain too many unchallenging UQs and (2) a large number of annotated UQs are required for training. To resolve the first drawback, we propose a new testing dataset, RGQA, which combines AQs from an existing VQA dataset with around 29K human-annotated UQs. These UQs consist of both fine-grained and coarse-grained image-question pairs generated with 2 approaches: CLIP-based and Perturbation-based. To address the second drawback, we introduce an unsupervised training approach. This combines pseudo UQs obtained by randomly pairing images and questions, with an RoI Mixup procedure to generate more fine-grained pseudo UQs, and model ensembling to regularize model confidence. Experiments show that using pseudo UQs significantly outperforms RVQA baselines. RoI Mixup and model ensembling further increase the gain. Finally, human evaluation reveals a performance gap between humans and models, showing that more RVQA research is needed.
## Keyword: ISP
### UT-Net: Combining U-Net and Transformer for Joint Optic Disc and Cup Segmentation and Glaucoma Detection
- **Authors:** Rukhshanda Hussain, Hritam Basak
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI); Image and Video Processing (eess.IV)
- **Arxiv link:** https://arxiv.org/abs/2303.04939
- **Pdf link:** https://arxiv.org/pdf/2303.04939
- **Abstract**
Glaucoma is a chronic visual disease that may cause permanent irreversible blindness. Measurement of the cup-to-disc ratio (CDR) plays a pivotal role in the detection of glaucoma in its early stage, preventing visual disparities. Therefore, accurate and automatic segmentation of optic disc (OD) and optic cup (OC) from retinal fundus images is a fundamental requirement. Existing CNN-based segmentation frameworks resort to building deep encoders with aggressive downsampling layers, which suffer from a general limitation on modeling explicit long-range dependency. To this end, in this paper, we propose a new segmentation pipeline, called UT-Net, availing the advantages of U-Net and transformer both in its encoding layer, followed by an attention-gated bilinear fusion scheme. In addition to this, we incorporate Multi-Head Contextual attention to enhance the regular self-attention used in traditional vision transformers. Thus low-level features along with global dependencies are captured in a shallow manner. Besides, we extract context information at multiple encoding layers for better exploration of receptive fields, and to aid the model to learn deep hierarchical representations. Finally, an enhanced mixing loss is proposed to tightly supervise the overall learning process. The proposed model has been implemented for joint OD and OC segmentation on three publicly available datasets: DRISHTI-GS, RIM-ONE R3, and REFUGE. Additionally, to validate our proposal, we have performed exhaustive experimentation on Glaucoma detection from all three datasets by measuring the Cup to Disc Ratio (CDR) value. Experimental results demonstrate the superiority of UT-Net as compared to the state-of-the-art methods.
### Deformer: Dynamic Fusion Transformer for Robust Hand Pose Estimation
- **Authors:** Qichen Fu, Xingyu Liu, Ran Xu, Juan Carlos Niebles, Kris M. Kitani
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2303.04991
- **Pdf link:** https://arxiv.org/pdf/2303.04991
- **Abstract**
Accurately estimating 3D hand pose is crucial for understanding how humans interact with the world. Despite remarkable progress, existing methods often struggle to generate plausible hand poses when the hand is heavily occluded or blurred. In videos, the movements of the hand allow us to observe various parts of the hand that may be occluded or blurred in a single frame. To adaptively leverage the visual clue before and after the occlusion or blurring for robust hand pose estimation, we propose the Deformer: a framework that implicitly reasons about the relationship between hand parts within the same image (spatial dimension) and different timesteps (temporal dimension). We show that a naive application of the transformer self-attention mechanism is not sufficient because motion blur or occlusions in certain frames can lead to heavily distorted hand features and generate imprecise keys and queries. To address this challenge, we incorporate a Dynamic Fusion Module into Deformer, which predicts the deformation of the hand and warps the hand mesh predictions from nearby frames to explicitly support the current frame estimation. Furthermore, we have observed that errors are unevenly distributed across different hand parts, with vertices around fingertips having disproportionately higher errors than those around the palm. We mitigate this issue by introducing a new loss function called maxMSE that automatically adjusts the weight of every vertex to focus the model on critical hand parts. Extensive experiments show that our method significantly outperforms state-of-the-art methods by 10%, and is more robust to occlusions (over 14%).
### Blind deblurring of hyperspectral document images
- **Authors:** M. Ljubenovic, P. Guzzonato, G. Franceschin, A. Traviglia
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2303.05130
- **Pdf link:** https://arxiv.org/pdf/2303.05130
- **Abstract**
Most computer vision and machine learning-based approaches for historical document analysis are tailored to grayscale or RGB images and thus, mostly exploit their spatial information. Multispectral (MS) and hyperspectral (HS) images contain, next to the spatial information, much richer spectral information than RGB images (usually spreading beyond the visible spectral range) that can facilitate more effective feature extraction, more accurate classification and recognition, and thus, improved analysis. Although utilization of rich spectral information can improve historical document analysis tremendously, there are still some potential limitations of HS imagery such as camera-induced noise and blur that require a carefully designed preprocessing step. Here, we propose novel blind HS image deblurring methods tailored to document images. We exploit a low-rank property of HS images (i.e., by projecting an HS image to a lower dimensional subspace) and utilize a text tailor image prior to performing a PSF estimation and deblurring of subspace components. The preliminary results show that the proposed approach gives good results over all spectral bands, removing successfully image artefacts introduced by blur and noise and significantly increasing the number of bands that can be used in further analysis.
## Keyword: image signal processing
There is no result
## Keyword: image signal process
There is no result
## Keyword: compression
### Diversity-Measurable Anomaly Detection
- **Authors:** Wenrui Liu, Hong Chang, Bingpeng Ma, Shiguang Shan, Xilin Chen
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI)
- **Arxiv link:** https://arxiv.org/abs/2303.05047
- **Pdf link:** https://arxiv.org/pdf/2303.05047
- **Abstract**
Reconstruction-based anomaly detection models achieve their purpose by suppressing the generalization ability for anomaly. However, diverse normal patterns are consequently not well reconstructed as well. Although some efforts have been made to alleviate this problem by modeling sample diversity, they suffer from shortcut learning due to undesired transmission of abnormal information. In this paper, to better handle the tradeoff problem, we propose Diversity-Measurable Anomaly Detection (DMAD) framework to enhance reconstruction diversity while avoid the undesired generalization on anomalies. To this end, we design Pyramid Deformation Module (PDM), which models diverse normals and measures the severity of anomaly by estimating multi-scale deformation fields from reconstructed reference to original input. Integrated with an information compression module, PDM essentially decouples deformation from prototypical embedding and makes the final anomaly score more reliable. Experimental results on both surveillance videos and industrial images demonstrate the effectiveness of our method. In addition, DMAD works equally well in front of contaminated data and anomaly-like normal samples.
## Keyword: RAW
### Toward Unsupervised Realistic Visual Question Answering
- **Authors:** Yuwei Zhang, Chih-Hui Ho, Nuno Vasconcelos
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2303.05068
- **Pdf link:** https://arxiv.org/pdf/2303.05068
- **Abstract**
The problem of realistic VQA (RVQA), where a model has to reject unanswerable questions (UQs) and answer answerable ones (AQs), is studied. We first point out 2 drawbacks in current RVQA research, where (1) datasets contain too many unchallenging UQs and (2) a large number of annotated UQs are required for training. To resolve the first drawback, we propose a new testing dataset, RGQA, which combines AQs from an existing VQA dataset with around 29K human-annotated UQs. These UQs consist of both fine-grained and coarse-grained image-question pairs generated with 2 approaches: CLIP-based and Perturbation-based. To address the second drawback, we introduce an unsupervised training approach. This combines pseudo UQs obtained by randomly pairing images and questions, with an RoI Mixup procedure to generate more fine-grained pseudo UQs, and model ensembling to regularize model confidence. Experiments show that using pseudo UQs significantly outperforms RVQA baselines. RoI Mixup and model ensembling further increase the gain. Finally, human evaluation reveals a performance gap between humans and models, showing that more RVQA research is needed.
## Keyword: raw image
There is no result
|
2.0
|
New submissions for Fri, 10 Mar 23 - ## Keyword: events
### Taming Contrast Maximization for Learning Sequential, Low-latency, Event-based Optical Flow
- **Authors:** Federico Paredes-Vallés, Kirk Y. W. Scheper, Christophe De Wagter, Guido C. H. E. de Croon
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI); Machine Learning (cs.LG)
- **Arxiv link:** https://arxiv.org/abs/2303.05214
- **Pdf link:** https://arxiv.org/pdf/2303.05214
- **Abstract**
Event cameras have recently gained significant traction since they open up new avenues for low-latency and low-power solutions to complex computer vision problems. To unlock these solutions, it is necessary to develop algorithms that can leverage the unique nature of event data. However, the current state-of-the-art is still highly influenced by the frame-based literature, and usually fails to deliver on these promises. In this work, we take this into consideration and propose a novel self-supervised learning pipeline for the sequential estimation of event-based optical flow that allows for the scaling of the models to high inference frequencies. At its core, we have a continuously-running stateful neural model that is trained using a novel formulation of contrast maximization that makes it robust to nonlinearities and varying statistics in the input events. Results across multiple datasets confirm the effectiveness of our method, which establishes a new state of the art in terms of accuracy for approaches trained or optimized without ground truth.
### Understanding the Challenges and Opportunities of Pose-based Anomaly Detection
- **Authors:** Ghazal Alinezhad Noghre, Armin Danesh Pazho, Vinit Katariya, Hamed Tabkhi
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI)
- **Arxiv link:** https://arxiv.org/abs/2303.05463
- **Pdf link:** https://arxiv.org/pdf/2303.05463
- **Abstract**
Pose-based anomaly detection is a video-analysis technique for detecting anomalous events or behaviors by examining human pose extracted from the video frames. Utilizing pose data alleviates privacy and ethical issues. Also, computation-wise, the complexity of pose-based models is lower than pixel-based approaches. However, it introduces more challenges, such as noisy skeleton data, losing important pixel information, and not having enriched enough features. These problems are exacerbated by a lack of anomaly detection datasets that are good enough representatives of real-world scenarios. In this work, we analyze and quantify the characteristics of two well-known video anomaly datasets to better understand the difficulties of pose-based anomaly detection. We take a step forward, exploring the discriminating power of pose and trajectory for video anomaly detection and their effectiveness based on context. We believe these experiments are beneficial for a better comprehension of pose-based anomaly detection and the datasets currently available. This will aid researchers in tackling the task of anomaly detection with a more lucid perspective, accelerating the development of robust models with better performance.
## Keyword: event camera
### Taming Contrast Maximization for Learning Sequential, Low-latency, Event-based Optical Flow
- **Authors:** Federico Paredes-Vallés, Kirk Y. W. Scheper, Christophe De Wagter, Guido C. H. E. de Croon
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI); Machine Learning (cs.LG)
- **Arxiv link:** https://arxiv.org/abs/2303.05214
- **Pdf link:** https://arxiv.org/pdf/2303.05214
- **Abstract**
Event cameras have recently gained significant traction since they open up new avenues for low-latency and low-power solutions to complex computer vision problems. To unlock these solutions, it is necessary to develop algorithms that can leverage the unique nature of event data. However, the current state-of-the-art is still highly influenced by the frame-based literature, and usually fails to deliver on these promises. In this work, we take this into consideration and propose a novel self-supervised learning pipeline for the sequential estimation of event-based optical flow that allows for the scaling of the models to high inference frequencies. At its core, we have a continuously-running stateful neural model that is trained using a novel formulation of contrast maximization that makes it robust to nonlinearities and varying statistics in the input events. Results across multiple datasets confirm the effectiveness of our method, which establishes a new state of the art in terms of accuracy for approaches trained or optimized without ground truth.
## Keyword: events camera
There is no result
## Keyword: white balance
There is no result
## Keyword: color contrast
There is no result
## Keyword: AWB
### Toward Unsupervised Realistic Visual Question Answering
- **Authors:** Yuwei Zhang, Chih-Hui Ho, Nuno Vasconcelos
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2303.05068
- **Pdf link:** https://arxiv.org/pdf/2303.05068
- **Abstract**
The problem of realistic VQA (RVQA), where a model has to reject unanswerable questions (UQs) and answer answerable ones (AQs), is studied. We first point out 2 drawbacks in current RVQA research, where (1) datasets contain too many unchallenging UQs and (2) a large number of annotated UQs are required for training. To resolve the first drawback, we propose a new testing dataset, RGQA, which combines AQs from an existing VQA dataset with around 29K human-annotated UQs. These UQs consist of both fine-grained and coarse-grained image-question pairs generated with 2 approaches: CLIP-based and Perturbation-based. To address the second drawback, we introduce an unsupervised training approach. This combines pseudo UQs obtained by randomly pairing images and questions, with an RoI Mixup procedure to generate more fine-grained pseudo UQs, and model ensembling to regularize model confidence. Experiments show that using pseudo UQs significantly outperforms RVQA baselines. RoI Mixup and model ensembling further increase the gain. Finally, human evaluation reveals a performance gap between humans and models, showing that more RVQA research is needed.
## Keyword: ISP
### UT-Net: Combining U-Net and Transformer for Joint Optic Disc and Cup Segmentation and Glaucoma Detection
- **Authors:** Rukhshanda Hussain, Hritam Basak
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI); Image and Video Processing (eess.IV)
- **Arxiv link:** https://arxiv.org/abs/2303.04939
- **Pdf link:** https://arxiv.org/pdf/2303.04939
- **Abstract**
Glaucoma is a chronic visual disease that may cause permanent irreversible blindness. Measurement of the cup-to-disc ratio (CDR) plays a pivotal role in the detection of glaucoma in its early stage, preventing visual disparities. Therefore, accurate and automatic segmentation of optic disc (OD) and optic cup (OC) from retinal fundus images is a fundamental requirement. Existing CNN-based segmentation frameworks resort to building deep encoders with aggressive downsampling layers, which suffer from a general limitation on modeling explicit long-range dependency. To this end, in this paper, we propose a new segmentation pipeline, called UT-Net, availing the advantages of U-Net and transformer both in its encoding layer, followed by an attention-gated bilinear fusion scheme. In addition to this, we incorporate Multi-Head Contextual attention to enhance the regular self-attention used in traditional vision transformers. Thus low-level features along with global dependencies are captured in a shallow manner. Besides, we extract context information at multiple encoding layers for better exploration of receptive fields, and to aid the model to learn deep hierarchical representations. Finally, an enhanced mixing loss is proposed to tightly supervise the overall learning process. The proposed model has been implemented for joint OD and OC segmentation on three publicly available datasets: DRISHTI-GS, RIM-ONE R3, and REFUGE. Additionally, to validate our proposal, we have performed exhaustive experimentation on Glaucoma detection from all three datasets by measuring the Cup to Disc Ratio (CDR) value. Experimental results demonstrate the superiority of UT-Net as compared to the state-of-the-art methods.
### Deformer: Dynamic Fusion Transformer for Robust Hand Pose Estimation
- **Authors:** Qichen Fu, Xingyu Liu, Ran Xu, Juan Carlos Niebles, Kris M. Kitani
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2303.04991
- **Pdf link:** https://arxiv.org/pdf/2303.04991
- **Abstract**
Accurately estimating 3D hand pose is crucial for understanding how humans interact with the world. Despite remarkable progress, existing methods often struggle to generate plausible hand poses when the hand is heavily occluded or blurred. In videos, the movements of the hand allow us to observe various parts of the hand that may be occluded or blurred in a single frame. To adaptively leverage the visual clue before and after the occlusion or blurring for robust hand pose estimation, we propose the Deformer: a framework that implicitly reasons about the relationship between hand parts within the same image (spatial dimension) and different timesteps (temporal dimension). We show that a naive application of the transformer self-attention mechanism is not sufficient because motion blur or occlusions in certain frames can lead to heavily distorted hand features and generate imprecise keys and queries. To address this challenge, we incorporate a Dynamic Fusion Module into Deformer, which predicts the deformation of the hand and warps the hand mesh predictions from nearby frames to explicitly support the current frame estimation. Furthermore, we have observed that errors are unevenly distributed across different hand parts, with vertices around fingertips having disproportionately higher errors than those around the palm. We mitigate this issue by introducing a new loss function called maxMSE that automatically adjusts the weight of every vertex to focus the model on critical hand parts. Extensive experiments show that our method significantly outperforms state-of-the-art methods by 10%, and is more robust to occlusions (over 14%).
### Blind deblurring of hyperspectral document images
- **Authors:** M. Ljubenovic, P. Guzzonato, G. Franceschin, A. Traviglia
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2303.05130
- **Pdf link:** https://arxiv.org/pdf/2303.05130
- **Abstract**
Most computer vision and machine learning-based approaches for historical document analysis are tailored to grayscale or RGB images and thus, mostly exploit their spatial information. Multispectral (MS) and hyperspectral (HS) images contain, next to the spatial information, much richer spectral information than RGB images (usually spreading beyond the visible spectral range) that can facilitate more effective feature extraction, more accurate classification and recognition, and thus, improved analysis. Although utilization of rich spectral information can improve historical document analysis tremendously, there are still some potential limitations of HS imagery such as camera-induced noise and blur that require a carefully designed preprocessing step. Here, we propose novel blind HS image deblurring methods tailored to document images. We exploit a low-rank property of HS images (i.e., by projecting an HS image to a lower dimensional subspace) and utilize a text tailor image prior to performing a PSF estimation and deblurring of subspace components. The preliminary results show that the proposed approach gives good results over all spectral bands, removing successfully image artefacts introduced by blur and noise and significantly increasing the number of bands that can be used in further analysis.
## Keyword: image signal processing
There is no result
## Keyword: image signal process
There is no result
## Keyword: compression
### Diversity-Measurable Anomaly Detection
- **Authors:** Wenrui Liu, Hong Chang, Bingpeng Ma, Shiguang Shan, Xilin Chen
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI)
- **Arxiv link:** https://arxiv.org/abs/2303.05047
- **Pdf link:** https://arxiv.org/pdf/2303.05047
- **Abstract**
Reconstruction-based anomaly detection models achieve their purpose by suppressing the generalization ability for anomaly. However, diverse normal patterns are consequently not well reconstructed as well. Although some efforts have been made to alleviate this problem by modeling sample diversity, they suffer from shortcut learning due to undesired transmission of abnormal information. In this paper, to better handle the tradeoff problem, we propose Diversity-Measurable Anomaly Detection (DMAD) framework to enhance reconstruction diversity while avoid the undesired generalization on anomalies. To this end, we design Pyramid Deformation Module (PDM), which models diverse normals and measures the severity of anomaly by estimating multi-scale deformation fields from reconstructed reference to original input. Integrated with an information compression module, PDM essentially decouples deformation from prototypical embedding and makes the final anomaly score more reliable. Experimental results on both surveillance videos and industrial images demonstrate the effectiveness of our method. In addition, DMAD works equally well in front of contaminated data and anomaly-like normal samples.
## Keyword: RAW
### Toward Unsupervised Realistic Visual Question Answering
- **Authors:** Yuwei Zhang, Chih-Hui Ho, Nuno Vasconcelos
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2303.05068
- **Pdf link:** https://arxiv.org/pdf/2303.05068
- **Abstract**
The problem of realistic VQA (RVQA), where a model has to reject unanswerable questions (UQs) and answer answerable ones (AQs), is studied. We first point out 2 drawbacks in current RVQA research, where (1) datasets contain too many unchallenging UQs and (2) a large number of annotated UQs are required for training. To resolve the first drawback, we propose a new testing dataset, RGQA, which combines AQs from an existing VQA dataset with around 29K human-annotated UQs. These UQs consist of both fine-grained and coarse-grained image-question pairs generated with 2 approaches: CLIP-based and Perturbation-based. To address the second drawback, we introduce an unsupervised training approach. This combines pseudo UQs obtained by randomly pairing images and questions, with an RoI Mixup procedure to generate more fine-grained pseudo UQs, and model ensembling to regularize model confidence. Experiments show that using pseudo UQs significantly outperforms RVQA baselines. RoI Mixup and model ensembling further increase the gain. Finally, human evaluation reveals a performance gap between humans and models, showing that more RVQA research is needed.
## Keyword: raw image
There is no result
|
process
|
new submissions for fri mar keyword events taming contrast maximization for learning sequential low latency event based optical flow authors federico paredes vallés kirk y w scheper christophe de wagter guido c h e de croon subjects computer vision and pattern recognition cs cv artificial intelligence cs ai machine learning cs lg arxiv link pdf link abstract event cameras have recently gained significant traction since they open up new avenues for low latency and low power solutions to complex computer vision problems to unlock these solutions it is necessary to develop algorithms that can leverage the unique nature of event data however the current state of the art is still highly influenced by the frame based literature and usually fails to deliver on these promises in this work we take this into consideration and propose a novel self supervised learning pipeline for the sequential estimation of event based optical flow that allows for the scaling of the models to high inference frequencies at its core we have a continuously running stateful neural model that is trained using a novel formulation of contrast maximization that makes it robust to nonlinearities and varying statistics in the input events results across multiple datasets confirm the effectiveness of our method which establishes a new state of the art in terms of accuracy for approaches trained or optimized without ground truth understanding the challenges and opportunities of pose based anomaly detection authors ghazal alinezhad noghre armin danesh pazho vinit katariya hamed tabkhi subjects computer vision and pattern recognition cs cv artificial intelligence cs ai arxiv link pdf link abstract pose based anomaly detection is a video analysis technique for detecting anomalous events or behaviors by examining human pose extracted from the video frames utilizing pose data alleviates privacy and ethical issues also computation wise the complexity of pose based models is lower than pixel based approaches however it introduces more challenges such as noisy skeleton data losing important pixel information and not having enriched enough features these problems are exacerbated by a lack of anomaly detection datasets that are good enough representatives of real world scenarios in this work we analyze and quantify the characteristics of two well known video anomaly datasets to better understand the difficulties of pose based anomaly detection we take a step forward exploring the discriminating power of pose and trajectory for video anomaly detection and their effectiveness based on context we believe these experiments are beneficial for a better comprehension of pose based anomaly detection and the datasets currently available this will aid researchers in tackling the task of anomaly detection with a more lucid perspective accelerating the development of robust models with better performance keyword event camera taming contrast maximization for learning sequential low latency event based optical flow authors federico paredes vallés kirk y w scheper christophe de wagter guido c h e de croon subjects computer vision and pattern recognition cs cv artificial intelligence cs ai machine learning cs lg arxiv link pdf link abstract event cameras have recently gained significant traction since they open up new avenues for low latency and low power solutions to complex computer vision problems to unlock these solutions it is necessary to develop algorithms that can leverage the unique nature of event data however the current state of the art is still highly influenced by the frame based literature and usually fails to deliver on these promises in this work we take this into consideration and propose a novel self supervised learning pipeline for the sequential estimation of event based optical flow that allows for the scaling of the models to high inference frequencies at its core we have a continuously running stateful neural model that is trained using a novel formulation of contrast maximization that makes it robust to nonlinearities and varying statistics in the input events results across multiple datasets confirm the effectiveness of our method which establishes a new state of the art in terms of accuracy for approaches trained or optimized without ground truth keyword events camera there is no result keyword white balance there is no result keyword color contrast there is no result keyword awb toward unsupervised realistic visual question answering authors yuwei zhang chih hui ho nuno vasconcelos subjects computer vision and pattern recognition cs cv arxiv link pdf link abstract the problem of realistic vqa rvqa where a model has to reject unanswerable questions uqs and answer answerable ones aqs is studied we first point out drawbacks in current rvqa research where datasets contain too many unchallenging uqs and a large number of annotated uqs are required for training to resolve the first drawback we propose a new testing dataset rgqa which combines aqs from an existing vqa dataset with around human annotated uqs these uqs consist of both fine grained and coarse grained image question pairs generated with approaches clip based and perturbation based to address the second drawback we introduce an unsupervised training approach this combines pseudo uqs obtained by randomly pairing images and questions with an roi mixup procedure to generate more fine grained pseudo uqs and model ensembling to regularize model confidence experiments show that using pseudo uqs significantly outperforms rvqa baselines roi mixup and model ensembling further increase the gain finally human evaluation reveals a performance gap between humans and models showing that more rvqa research is needed keyword isp ut net combining u net and transformer for joint optic disc and cup segmentation and glaucoma detection authors rukhshanda hussain hritam basak subjects computer vision and pattern recognition cs cv artificial intelligence cs ai image and video processing eess iv arxiv link pdf link abstract glaucoma is a chronic visual disease that may cause permanent irreversible blindness measurement of the cup to disc ratio cdr plays a pivotal role in the detection of glaucoma in its early stage preventing visual disparities therefore accurate and automatic segmentation of optic disc od and optic cup oc from retinal fundus images is a fundamental requirement existing cnn based segmentation frameworks resort to building deep encoders with aggressive downsampling layers which suffer from a general limitation on modeling explicit long range dependency to this end in this paper we propose a new segmentation pipeline called ut net availing the advantages of u net and transformer both in its encoding layer followed by an attention gated bilinear fusion scheme in addition to this we incorporate multi head contextual attention to enhance the regular self attention used in traditional vision transformers thus low level features along with global dependencies are captured in a shallow manner besides we extract context information at multiple encoding layers for better exploration of receptive fields and to aid the model to learn deep hierarchical representations finally an enhanced mixing loss is proposed to tightly supervise the overall learning process the proposed model has been implemented for joint od and oc segmentation on three publicly available datasets drishti gs rim one and refuge additionally to validate our proposal we have performed exhaustive experimentation on glaucoma detection from all three datasets by measuring the cup to disc ratio cdr value experimental results demonstrate the superiority of ut net as compared to the state of the art methods deformer dynamic fusion transformer for robust hand pose estimation authors qichen fu xingyu liu ran xu juan carlos niebles kris m kitani subjects computer vision and pattern recognition cs cv arxiv link pdf link abstract accurately estimating hand pose is crucial for understanding how humans interact with the world despite remarkable progress existing methods often struggle to generate plausible hand poses when the hand is heavily occluded or blurred in videos the movements of the hand allow us to observe various parts of the hand that may be occluded or blurred in a single frame to adaptively leverage the visual clue before and after the occlusion or blurring for robust hand pose estimation we propose the deformer a framework that implicitly reasons about the relationship between hand parts within the same image spatial dimension and different timesteps temporal dimension we show that a naive application of the transformer self attention mechanism is not sufficient because motion blur or occlusions in certain frames can lead to heavily distorted hand features and generate imprecise keys and queries to address this challenge we incorporate a dynamic fusion module into deformer which predicts the deformation of the hand and warps the hand mesh predictions from nearby frames to explicitly support the current frame estimation furthermore we have observed that errors are unevenly distributed across different hand parts with vertices around fingertips having disproportionately higher errors than those around the palm we mitigate this issue by introducing a new loss function called maxmse that automatically adjusts the weight of every vertex to focus the model on critical hand parts extensive experiments show that our method significantly outperforms state of the art methods by and is more robust to occlusions over blind deblurring of hyperspectral document images authors m ljubenovic p guzzonato g franceschin a traviglia subjects computer vision and pattern recognition cs cv arxiv link pdf link abstract most computer vision and machine learning based approaches for historical document analysis are tailored to grayscale or rgb images and thus mostly exploit their spatial information multispectral ms and hyperspectral hs images contain next to the spatial information much richer spectral information than rgb images usually spreading beyond the visible spectral range that can facilitate more effective feature extraction more accurate classification and recognition and thus improved analysis although utilization of rich spectral information can improve historical document analysis tremendously there are still some potential limitations of hs imagery such as camera induced noise and blur that require a carefully designed preprocessing step here we propose novel blind hs image deblurring methods tailored to document images we exploit a low rank property of hs images i e by projecting an hs image to a lower dimensional subspace and utilize a text tailor image prior to performing a psf estimation and deblurring of subspace components the preliminary results show that the proposed approach gives good results over all spectral bands removing successfully image artefacts introduced by blur and noise and significantly increasing the number of bands that can be used in further analysis keyword image signal processing there is no result keyword image signal process there is no result keyword compression diversity measurable anomaly detection authors wenrui liu hong chang bingpeng ma shiguang shan xilin chen subjects computer vision and pattern recognition cs cv artificial intelligence cs ai arxiv link pdf link abstract reconstruction based anomaly detection models achieve their purpose by suppressing the generalization ability for anomaly however diverse normal patterns are consequently not well reconstructed as well although some efforts have been made to alleviate this problem by modeling sample diversity they suffer from shortcut learning due to undesired transmission of abnormal information in this paper to better handle the tradeoff problem we propose diversity measurable anomaly detection dmad framework to enhance reconstruction diversity while avoid the undesired generalization on anomalies to this end we design pyramid deformation module pdm which models diverse normals and measures the severity of anomaly by estimating multi scale deformation fields from reconstructed reference to original input integrated with an information compression module pdm essentially decouples deformation from prototypical embedding and makes the final anomaly score more reliable experimental results on both surveillance videos and industrial images demonstrate the effectiveness of our method in addition dmad works equally well in front of contaminated data and anomaly like normal samples keyword raw toward unsupervised realistic visual question answering authors yuwei zhang chih hui ho nuno vasconcelos subjects computer vision and pattern recognition cs cv arxiv link pdf link abstract the problem of realistic vqa rvqa where a model has to reject unanswerable questions uqs and answer answerable ones aqs is studied we first point out drawbacks in current rvqa research where datasets contain too many unchallenging uqs and a large number of annotated uqs are required for training to resolve the first drawback we propose a new testing dataset rgqa which combines aqs from an existing vqa dataset with around human annotated uqs these uqs consist of both fine grained and coarse grained image question pairs generated with approaches clip based and perturbation based to address the second drawback we introduce an unsupervised training approach this combines pseudo uqs obtained by randomly pairing images and questions with an roi mixup procedure to generate more fine grained pseudo uqs and model ensembling to regularize model confidence experiments show that using pseudo uqs significantly outperforms rvqa baselines roi mixup and model ensembling further increase the gain finally human evaluation reveals a performance gap between humans and models showing that more rvqa research is needed keyword raw image there is no result
| 1
|
3,396
| 6,517,573,497
|
IssuesEvent
|
2017-08-28 01:20:14
|
Great-Hill-Corporation/quickBlocks
|
https://api.github.com/repos/Great-Hill-Corporation/quickBlocks
|
closed
|
transaction class in non etherscan mode does not have blockNum or cum
|
libs-etherlib status-inprocess type-bug
|
Or any other duplicated stuff. It also does not have pointers to pBlokc, nor does receipt have pointers to pTrans
This shows up as empty timestamp, empty cumultageGas, etc in toJSON 50004
See getBlock tests
From https://github.com/Great-Hill-Corporation/ethslurp/issues/122
|
1.0
|
transaction class in non etherscan mode does not have blockNum or cum - Or any other duplicated stuff. It also does not have pointers to pBlokc, nor does receipt have pointers to pTrans
This shows up as empty timestamp, empty cumultageGas, etc in toJSON 50004
See getBlock tests
From https://github.com/Great-Hill-Corporation/ethslurp/issues/122
|
process
|
transaction class in non etherscan mode does not have blocknum or cum or any other duplicated stuff it also does not have pointers to pblokc nor does receipt have pointers to ptrans this shows up as empty timestamp empty cumultagegas etc in tojson see getblock tests from
| 1
|
8,521
| 11,700,967,080
|
IssuesEvent
|
2020-03-06 18:38:51
|
geneontology/go-ontology
|
https://api.github.com/repos/geneontology/go-ontology
|
closed
|
formation of penetration hyphae
|
multi-species process
|
should "formation of penetration hyphae" this be related to
"entry into host"
@CuzickA
|
1.0
|
formation of penetration hyphae -
should "formation of penetration hyphae" this be related to
"entry into host"
@CuzickA
|
process
|
formation of penetration hyphae should formation of penetration hyphae this be related to entry into host cuzicka
| 1
|
13,113
| 15,499,729,919
|
IssuesEvent
|
2021-03-11 08:22:48
|
prisma/prisma
|
https://api.github.com/repos/prisma/prisma
|
opened
|
blitz prisma migrate deploy sometimes errors with `Database error: Error querying the database: db error: ERROR: prepared statement "s0" does not exist` with pgbouncer
|
bug/0-needs-info kind/bug process/candidate team/migrations
|
<!--
Thanks for helping us improve Prisma! 🙏 Please follow the sections in the template and provide as much information as possible about your problem, e.g. by setting the `DEBUG="*"` environment variable and enabling additional logging output in Prisma Client.
Learn more about writing proper bug reports here: https://pris.ly/d/bug-reports
-->
## Bug description
<!-- A clear and concise description of what the bug is. -->
https://prisma.slack.com/archives/CA491RJH0/p1615370492400800?thread_ts=1614161039.079900&cid=CA491RJH0
User says:
Funny things is that when i redeploy once or twice it works :man-shrugging: always running the same NODE_ENV=production blitz prisma migrate deploy --preview-feature - prisma & prisma-client are at 2.18.0 I just tested prisma for a few weeks so i only tested 2.17 - 2.18
Db is hosted on digital-ocean(london 1) with pgBouncer enabled.
Actually it seems to be two errors - in most cases it’s just
```
21:35:05.746 Error: P1002
21:35:05.746 The database server at `xx.xxx.xx.xxx`:`25061` was reached but timed out.
```
But at least once it also was:
```
Response: Database error: Error querying the database: db error: ERROR: prepared statement "s0" does not exist
```
## How to reproduce
<!--
Steps to reproduce the behavior:
1. Go to '...'
2. Change '....'
3. Run '....'
4. See error
-->
## Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
## Prisma information
<!-- Your Prisma schema, Prisma Client queries, ...
Do not include your database credentials when sharing your Prisma schema! -->
## Environment & setup
<!-- In which environment does the problem occur -->
- OS: <!--[e.g. Mac OS, Windows, Debian, CentOS, ...]-->
- Database: <!--[PostgreSQL, MySQL, MariaDB or SQLite]-->
- Node.js version: <!--[Run `node -v` to see your Node.js version]-->
- Prisma version:
<!--[Run `prisma -v` to see your Prisma version and paste it between the ´´´]-->
```
```
|
1.0
|
blitz prisma migrate deploy sometimes errors with `Database error: Error querying the database: db error: ERROR: prepared statement "s0" does not exist` with pgbouncer - <!--
Thanks for helping us improve Prisma! 🙏 Please follow the sections in the template and provide as much information as possible about your problem, e.g. by setting the `DEBUG="*"` environment variable and enabling additional logging output in Prisma Client.
Learn more about writing proper bug reports here: https://pris.ly/d/bug-reports
-->
## Bug description
<!-- A clear and concise description of what the bug is. -->
https://prisma.slack.com/archives/CA491RJH0/p1615370492400800?thread_ts=1614161039.079900&cid=CA491RJH0
User says:
Funny things is that when i redeploy once or twice it works :man-shrugging: always running the same NODE_ENV=production blitz prisma migrate deploy --preview-feature - prisma & prisma-client are at 2.18.0 I just tested prisma for a few weeks so i only tested 2.17 - 2.18
Db is hosted on digital-ocean(london 1) with pgBouncer enabled.
Actually it seems to be two errors - in most cases it’s just
```
21:35:05.746 Error: P1002
21:35:05.746 The database server at `xx.xxx.xx.xxx`:`25061` was reached but timed out.
```
But at least once it also was:
```
Response: Database error: Error querying the database: db error: ERROR: prepared statement "s0" does not exist
```
## How to reproduce
<!--
Steps to reproduce the behavior:
1. Go to '...'
2. Change '....'
3. Run '....'
4. See error
-->
## Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
## Prisma information
<!-- Your Prisma schema, Prisma Client queries, ...
Do not include your database credentials when sharing your Prisma schema! -->
## Environment & setup
<!-- In which environment does the problem occur -->
- OS: <!--[e.g. Mac OS, Windows, Debian, CentOS, ...]-->
- Database: <!--[PostgreSQL, MySQL, MariaDB or SQLite]-->
- Node.js version: <!--[Run `node -v` to see your Node.js version]-->
- Prisma version:
<!--[Run `prisma -v` to see your Prisma version and paste it between the ´´´]-->
```
```
|
process
|
blitz prisma migrate deploy sometimes errors with database error error querying the database db error error prepared statement does not exist with pgbouncer thanks for helping us improve prisma 🙏 please follow the sections in the template and provide as much information as possible about your problem e g by setting the debug environment variable and enabling additional logging output in prisma client learn more about writing proper bug reports here bug description user says funny things is that when i redeploy once or twice it works man shrugging always running the same node env production blitz prisma migrate deploy preview feature prisma prisma client are at i just tested prisma for a few weeks so i only tested db is hosted on digital ocean london with pgbouncer enabled actually it seems to be two errors in most cases it’s just error the database server at xx xxx xx xxx was reached but timed out but at least once it also was response database error error querying the database db error error prepared statement does not exist how to reproduce steps to reproduce the behavior go to change run see error expected behavior prisma information your prisma schema prisma client queries do not include your database credentials when sharing your prisma schema environment setup os database node js version prisma version
| 1
|
3,365
| 6,494,897,948
|
IssuesEvent
|
2017-08-22 01:01:38
|
geneontology/go-ontology
|
https://api.github.com/repos/geneontology/go-ontology
|
closed
|
NTR: membrane curvature sensing
|
ARUK-UCL cellular processes neurobiology New term request
|
Figure 4 and Supplementary Figure 4 in PMID: 25898166 demonstrate that PICALM is involved in sensing of membrane curvature.
In order to annotate this I would like to request a new term: 'membrane curvature sensing'.
_Suggested_ definition: "A process involving (1) the insertion (aka wedging) of the hydrophobic residue side chains of the amphipathic helix (AH) of a membrane curvature sensing (MCS) protein into lipids in a curved membrane and (2) the interactions between the hydrophilic residue side chains of the AH and membrane phospholipid headgroups. Membrane curvature sensing is a part of 'GO:0061024 membrane organization' and 'GO:0016050 vesicle organization'."
Refs: PMID: 21953452 and PMID: 25898166.
_Suggested_ synonyms:
_Exact synonym_: membrane amphipathic lipid packaging sensing (PMID: 25898166 and references within)
_Related synonym_: membrane curvature-sensitive protein-membrane binding (PMID: 21953452).
_Related synonym_: membrane curvature-depending protein-membrane binding
_Related synonym_: membrane curvature-sensitive protein-membrane interaction
_Related synonym_: membrane curvature-depending protein-membrane interaction
> GO:0061024 membrane organization
>> NTR membrane curvature sensing (part_of)
> GO:0016050 vesicle organization
>> NTR membrane curvature sensing (part_of)
Please use refs: GOC:aruk and GOC:bc.
Thanks,
Barbara
|
1.0
|
NTR: membrane curvature sensing - Figure 4 and Supplementary Figure 4 in PMID: 25898166 demonstrate that PICALM is involved in sensing of membrane curvature.
In order to annotate this I would like to request a new term: 'membrane curvature sensing'.
_Suggested_ definition: "A process involving (1) the insertion (aka wedging) of the hydrophobic residue side chains of the amphipathic helix (AH) of a membrane curvature sensing (MCS) protein into lipids in a curved membrane and (2) the interactions between the hydrophilic residue side chains of the AH and membrane phospholipid headgroups. Membrane curvature sensing is a part of 'GO:0061024 membrane organization' and 'GO:0016050 vesicle organization'."
Refs: PMID: 21953452 and PMID: 25898166.
_Suggested_ synonyms:
_Exact synonym_: membrane amphipathic lipid packaging sensing (PMID: 25898166 and references within)
_Related synonym_: membrane curvature-sensitive protein-membrane binding (PMID: 21953452).
_Related synonym_: membrane curvature-depending protein-membrane binding
_Related synonym_: membrane curvature-sensitive protein-membrane interaction
_Related synonym_: membrane curvature-depending protein-membrane interaction
> GO:0061024 membrane organization
>> NTR membrane curvature sensing (part_of)
> GO:0016050 vesicle organization
>> NTR membrane curvature sensing (part_of)
Please use refs: GOC:aruk and GOC:bc.
Thanks,
Barbara
|
process
|
ntr membrane curvature sensing figure and supplementary figure in pmid demonstrate that picalm is involved in sensing of membrane curvature in order to annotate this i would like to request a new term membrane curvature sensing suggested definition a process involving the insertion aka wedging of the hydrophobic residue side chains of the amphipathic helix ah of a membrane curvature sensing mcs protein into lipids in a curved membrane and the interactions between the hydrophilic residue side chains of the ah and membrane phospholipid headgroups membrane curvature sensing is a part of go membrane organization and go vesicle organization refs pmid and pmid suggested synonyms exact synonym membrane amphipathic lipid packaging sensing pmid and references within related synonym membrane curvature sensitive protein membrane binding pmid related synonym membrane curvature depending protein membrane binding related synonym membrane curvature sensitive protein membrane interaction related synonym membrane curvature depending protein membrane interaction go membrane organization ntr membrane curvature sensing part of go vesicle organization ntr membrane curvature sensing part of please use refs goc aruk and goc bc thanks barbara
| 1
|
46,302
| 5,795,223,368
|
IssuesEvent
|
2017-05-02 16:34:24
|
smartchicago/chicago-atlas
|
https://api.github.com/repos/smartchicago/chicago-atlas
|
opened
|
Community profiles: Hyperlink indicator headings under "Community Area Data"
|
enhancement ux test
|
When asked to review the "Community Area Data" through our ux test tasks, we witnessed that some testers attempted to click on the indicator data headings (for example "Teen birth rate") because they wanted to open up that page to review more information.
|
1.0
|
Community profiles: Hyperlink indicator headings under "Community Area Data" - When asked to review the "Community Area Data" through our ux test tasks, we witnessed that some testers attempted to click on the indicator data headings (for example "Teen birth rate") because they wanted to open up that page to review more information.
|
non_process
|
community profiles hyperlink indicator headings under community area data when asked to review the community area data through our ux test tasks we witnessed that some testers attempted to click on the indicator data headings for example teen birth rate because they wanted to open up that page to review more information
| 0
|
18,307
| 24,420,140,465
|
IssuesEvent
|
2022-10-05 19:31:37
|
heavy-duty/solana-colombia-hacker-house-bounty-program
|
https://api.github.com/repos/heavy-duty/solana-colombia-hacker-house-bounty-program
|
closed
|
Challenge Submission: Solana 101: Deploy a Program
|
drill:bounty:processing challenge points:50 completed
|
### Rewards: 100 Points 🔥 *NFT! 👻
___
### Description
In this challenge your mission is to deploy your first Solana program to devnet!
💡 Record the start time so we can reference it later.
How long do you think it will take you to deploy?
Good luck **undefined**!
1. Visit the Solana developer docs: [https://docs.solana.com/developers](https://docs.solana.com/developers)
2. Click on the [Get Started](https://docs.solana.com/getstarted/hello-world) button
3. [Follow the guide to deploy a program](https://docs.solana.com/getstarted/hello-world#what-you-will-learn)
4. [Deploy your program and record the transaction signature](https://docs.solana.com/getstarted/hello-world#deploy-your-program)
5. [Find and record your program Id](https://docs.solana.com/getstarted/hello-world#find-your-program-id)
💡 Record the end time. How long did it take?
### Tips:
- When you click deploy you should see two buttons: Solana Explorer and Solscan. Clicking the buttons should take you to a transaction explorer where you can view details and your transaction Id in the url.
- Explorer on devnet to search for your program Id: [Solana Explorer](https://explorer.solana.com/?cluster=devnet)
- [Example transaction Id](https://explorer.solana.com/tx/4v5StXx1jeuWzh9trtBQtQRMeeUjZzk7mJSq9MTx9XhDunbqY5ZpwPZQanVKfN7Tb3X1gHtMa6xgUcARVDaG7x91?cluster=devnet) is in the url followed by: /tx/.
- Id, Address, and Public Key are often used interchangeably to describe an address which can be used to look up account information.
- Example of a public key or wallet address: 6UmotVc1i6y4e6DnHf5FwYzYX9qCD7ncAbErsiu4oo3U
**some challenges may offer new NFTs while others may even update existing ones!*
### Resources:
[Solana Developer Docs](https://docs.solana.com/developers)
[Solana Playground](https://beta.solpg.io/)
___
### How to Submit
Your submission should include the following:
1. Your `Transaction Id` (tx, signature, address) from the url above.
2. The `Program ID` from your deployed program.
3. Time it took to deploy your program.
*That was almost too easy..*
___
### Submission Entered:
Challenge Id: [#221004010]
Hunter: Andres Guerrero
1. Transaction ID:
2323232
2. Program ID:
323242e2e2
3. How long did it take to deploy a program? (minutes): 2
|
1.0
|
Challenge Submission: Solana 101: Deploy a Program -
### Rewards: 100 Points 🔥 *NFT! 👻
___
### Description
In this challenge your mission is to deploy your first Solana program to devnet!
💡 Record the start time so we can reference it later.
How long do you think it will take you to deploy?
Good luck **undefined**!
1. Visit the Solana developer docs: [https://docs.solana.com/developers](https://docs.solana.com/developers)
2. Click on the [Get Started](https://docs.solana.com/getstarted/hello-world) button
3. [Follow the guide to deploy a program](https://docs.solana.com/getstarted/hello-world#what-you-will-learn)
4. [Deploy your program and record the transaction signature](https://docs.solana.com/getstarted/hello-world#deploy-your-program)
5. [Find and record your program Id](https://docs.solana.com/getstarted/hello-world#find-your-program-id)
💡 Record the end time. How long did it take?
### Tips:
- When you click deploy you should see two buttons: Solana Explorer and Solscan. Clicking the buttons should take you to a transaction explorer where you can view details and your transaction Id in the url.
- Explorer on devnet to search for your program Id: [Solana Explorer](https://explorer.solana.com/?cluster=devnet)
- [Example transaction Id](https://explorer.solana.com/tx/4v5StXx1jeuWzh9trtBQtQRMeeUjZzk7mJSq9MTx9XhDunbqY5ZpwPZQanVKfN7Tb3X1gHtMa6xgUcARVDaG7x91?cluster=devnet) is in the url followed by: /tx/.
- Id, Address, and Public Key are often used interchangeably to describe an address which can be used to look up account information.
- Example of a public key or wallet address: 6UmotVc1i6y4e6DnHf5FwYzYX9qCD7ncAbErsiu4oo3U
**some challenges may offer new NFTs while others may even update existing ones!*
### Resources:
[Solana Developer Docs](https://docs.solana.com/developers)
[Solana Playground](https://beta.solpg.io/)
___
### How to Submit
Your submission should include the following:
1. Your `Transaction Id` (tx, signature, address) from the url above.
2. The `Program ID` from your deployed program.
3. Time it took to deploy your program.
*That was almost too easy..*
___
### Submission Entered:
Challenge Id: [#221004010]
Hunter: Andres Guerrero
1. Transaction ID:
2323232
2. Program ID:
323242e2e2
3. How long did it take to deploy a program? (minutes): 2
|
process
|
challenge submission solana deploy a program rewards points 🔥 nft 👻 description in this challenge your mission is to deploy your first solana program to devnet 💡 record the start time so we can reference it later how long do you think it will take you to deploy good luck undefined visit the solana developer docs click on the button 💡 record the end time how long did it take tips when you click deploy you should see two buttons solana explorer and solscan clicking the buttons should take you to a transaction explorer where you can view details and your transaction id in the url explorer on devnet to search for your program id is in the url followed by tx id address and public key are often used interchangeably to describe an address which can be used to look up account information example of a public key or wallet address some challenges may offer new nfts while others may even update existing ones resources how to submit your submission should include the following your transaction id tx signature address from the url above the program id from your deployed program time it took to deploy your program that was almost too easy submission entered challenge id hunter andres guerrero transaction id program id how long did it take to deploy a program minutes
| 1
|
313,256
| 26,913,519,089
|
IssuesEvent
|
2023-02-07 03:10:46
|
dotnet/machinelearning-modelbuilder
|
https://api.github.com/repos/dotnet/machinelearning-modelbuilder
|
closed
|
Data classification: The generated Console App and Web API projects are running failed.
|
Priority:0 Reported by: Test
|
**System Information (please complete the following information):**
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: 16.14.0.2261401 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.4.1)
.Net: 6.0
**Describe the bug**
- On which step of the process did you run into an issue:
The generated Console App is running failed.
**Data Source**
https://testpass.blob.core.windows.net/test-pass-data/wikipedia-detox-250-line-data.tsv
SQL Password
**To Reproduce**
Steps to reproduce the behavior:
1. Select Create a new project from the Visual Studio 2022 start window.
2. Choose the C# Console App (.NET Core6.0) project template.
3. Add model builder by right click on the project.
4. Select **Data classification** scenario.
5. On Data page, select the data source and choose **Sentiment** column as label.
6. On the Train page, click "Start training" button to complete the training.
7. Click "Add to solution" button on the Consume page to generate Console App project.
8. Run the generated Console App project.
**Expected behavior**
The generated Console App project should be running successfully.
**Screenshots**
File:
SQL Password:
**Additional context:**
|
1.0
|
Data classification: The generated Console App and Web API projects are running failed. - **System Information (please complete the following information):**
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: 16.14.0.2261401 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.4.1)
.Net: 6.0
**Describe the bug**
- On which step of the process did you run into an issue:
The generated Console App is running failed.
**Data Source**
https://testpass.blob.core.windows.net/test-pass-data/wikipedia-detox-250-line-data.tsv
SQL Password
**To Reproduce**
Steps to reproduce the behavior:
1. Select Create a new project from the Visual Studio 2022 start window.
2. Choose the C# Console App (.NET Core6.0) project template.
3. Add model builder by right click on the project.
4. Select **Data classification** scenario.
5. On Data page, select the data source and choose **Sentiment** column as label.
6. On the Train page, click "Start training" button to complete the training.
7. Click "Add to solution" button on the Consume page to generate Console App project.
8. Run the generated Console App project.
**Expected behavior**
The generated Console App project should be running successfully.
**Screenshots**
File:
SQL Password:
**Additional context:**
|
non_process
|
data classification the generated console app and web api projects are running failed system information please complete the following information windows os windows enterprise ml net model builder main build microsoft visual studio enterprise net describe the bug on which step of the process did you run into an issue the generated console app is running failed data source sql password to reproduce steps to reproduce the behavior select create a new project from the visual studio start window choose the c console app net project template add model builder by right click on the project select data classification scenario on data page select the data source and choose sentiment column as label on the train page click start training button to complete the training click add to solution button on the consume page to generate console app project run the generated console app project expected behavior the generated console app project should be running successfully screenshots file sql password additional context
| 0
|
14,753
| 18,023,756,972
|
IssuesEvent
|
2021-09-16 23:49:45
|
modm-io/modm
|
https://api.github.com/repos/modm-io/modm
|
closed
|
Support for SAMG55 devices
|
question ❔ advanced 🤯 process 📊 feature 🚧
|
I'm working on support for the SAMG famiy -- specifically SAMG55, but I think there's a lot of similarity with other SAMG5x parts.
I'm creating this issue as a place to track it, and a place for discussion.
Currently, I have updated cmsis-header-sam (see [PR](https://github.com/modm-io/cmsis-header-sam/pull/1)) to pull in the headers, and I've fixed a couple of issues with device generation in modm-devices (no PR yet -- I wanted to verify more) so that I can generate what seem like correct XML files for the devices.
Now I'm working on creating a demo app, and the first step was to get the GPIO working. Unfortunately, the GPIO registers are different from the currently supported SAM devices, so I'm adapting. These drivers have some pretty complicated C++ magic, but I am pushing my way through the variadic templates etc and struggling to keep up :).
The question on my mind now is: does anyone know if the current sam GPIO driver works for port B at all? It's entirely possible I've misunderstood, but it looks like [getPortReg](https://github.com/modm-io/modm/blob/develop/src/modm/platform/gpio/sam/pin.hpp#L145) method just doesn't support any port other than the first ("A"). Also, there seems to be a typo in [readPortReg](https://github.com/modm-io/modm/blob/develop/src/modm/platform/gpio/sam/pin.hpp#L168) that would use the wrong mask, even if it read the correct port. Maybe @henrikssn can comment?
Also, the SAMG55 does not support output speeds, and from what I can see in the existing driver they aren't supported for SAMDxx either; the output speed is just ignored. I assume this was to match the API of the STM32 driver?
|
1.0
|
Support for SAMG55 devices - I'm working on support for the SAMG famiy -- specifically SAMG55, but I think there's a lot of similarity with other SAMG5x parts.
I'm creating this issue as a place to track it, and a place for discussion.
Currently, I have updated cmsis-header-sam (see [PR](https://github.com/modm-io/cmsis-header-sam/pull/1)) to pull in the headers, and I've fixed a couple of issues with device generation in modm-devices (no PR yet -- I wanted to verify more) so that I can generate what seem like correct XML files for the devices.
Now I'm working on creating a demo app, and the first step was to get the GPIO working. Unfortunately, the GPIO registers are different from the currently supported SAM devices, so I'm adapting. These drivers have some pretty complicated C++ magic, but I am pushing my way through the variadic templates etc and struggling to keep up :).
The question on my mind now is: does anyone know if the current sam GPIO driver works for port B at all? It's entirely possible I've misunderstood, but it looks like [getPortReg](https://github.com/modm-io/modm/blob/develop/src/modm/platform/gpio/sam/pin.hpp#L145) method just doesn't support any port other than the first ("A"). Also, there seems to be a typo in [readPortReg](https://github.com/modm-io/modm/blob/develop/src/modm/platform/gpio/sam/pin.hpp#L168) that would use the wrong mask, even if it read the correct port. Maybe @henrikssn can comment?
Also, the SAMG55 does not support output speeds, and from what I can see in the existing driver they aren't supported for SAMDxx either; the output speed is just ignored. I assume this was to match the API of the STM32 driver?
|
process
|
support for devices i m working on support for the samg famiy specifically but i think there s a lot of similarity with other parts i m creating this issue as a place to track it and a place for discussion currently i have updated cmsis header sam see to pull in the headers and i ve fixed a couple of issues with device generation in modm devices no pr yet i wanted to verify more so that i can generate what seem like correct xml files for the devices now i m working on creating a demo app and the first step was to get the gpio working unfortunately the gpio registers are different from the currently supported sam devices so i m adapting these drivers have some pretty complicated c magic but i am pushing my way through the variadic templates etc and struggling to keep up the question on my mind now is does anyone know if the current sam gpio driver works for port b at all it s entirely possible i ve misunderstood but it looks like method just doesn t support any port other than the first a also there seems to be a typo in that would use the wrong mask even if it read the correct port maybe henrikssn can comment also the does not support output speeds and from what i can see in the existing driver they aren t supported for samdxx either the output speed is just ignored i assume this was to match the api of the driver
| 1
|
11,422
| 14,247,754,799
|
IssuesEvent
|
2020-11-19 11:56:06
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Whenever I perform any Raster extraction such as 'Clip Raster by Extent' or 'Clip Raster by Mask layer'
|
Bug Feedback Processing
|
Whenever I perform any Raster extraction operations such as 'Clip Raster by Extent' or 'Clip Raster by Mask layer'
**I get the below error and doesn't get any desired output.**
Log:
QGIS version: 3.10.11-A Coruña
QGIS code revision: d2171173e4
Qt version: 5.12.3
GDAL version: 2.4.1
GEOS version: 3.7.2-CAPI-1.11.2 b55d2125
PROJ version: Rel. 5.2.0, September 15th, 2018
Processing algorithm…
Algorithm 'Clip raster by mask layer' starting…
Input parameters:
{ 'ALPHA_BAND' : False, 'CROP_TO_CUTLINE' : True, 'DATA_TYPE' : 0, 'EXTRA' : '', 'INPUT' : 'type=xyz&zmin=0&zmax=22&url=https://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x}', 'KEEP_RESOLUTION' : False, 'MASK' : '/Users/rahulgour/Desktop/STR/GIS/vectorGrid/vectorGridSTR.gpkg', 'MULTITHREADING' : False, 'NODATA' : None, 'OPTIONS' : '', 'OUTPUT' : '/Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif', 'SET_RESOLUTION' : False, 'SOURCE_CRS' : QgsCoordinateReferenceSystem('EPSG:3857'), 'TARGET_CRS' : QgsCoordinateReferenceSystem('EPSG:3857'), 'X_RESOLUTION' : None, 'Y_RESOLUTION' : None }
GDAL command:
gdalwarp -s_srs EPSG:3857 -t_srs EPSG:3857 -of GTiff -cutline /Users/rahulgour/Desktop/STR/GIS/vectorGrid/vectorGridSTR.gpkg -cl vectorGridSTR -crop_to_cutline type=xyz&zmin=0&zmax=22&url=https://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x} /Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif
GDAL command output:
/bin/sh: /Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif: No such file or directory
FAILURE: No target filename specified.
Usage: gdalwarp [--help-general] [--formats]
[-s_srs srs_def] [-t_srs srs_def] [-to "NAME=VALUE"]* [-novshiftgrid]
[-order n | -tps | -rpc | -geoloc] [-et err_threshold]
[-refine_gcps tolerance [minimum_gcps]]
[-te xmin ymin xmax ymax] [-tr xres yres] [-tap] [-ts width height]
[-ovr level|AUTO|AUTO-n|NONE] [-wo "NAME=VALUE"] [-ot Byte/Int16/...] [-wt Byte/Int16]
[-srcnodata "value [value...]"] [-dstnodata "value [value...]"] -dstalpha
[-r resampling_method] [-wm memory_in_mb] [-multi] [-q]
[-cutline datasource] [-cl layer] [-cwhere expression]
[-csql statement] [-cblend dist_in_pixels] [-crop_to_cutline]
[-of format] [-co "NAME=VALUE"]* [-overwrite]
[-nomd] [-cvmd meta_conflict_value] [-setci] [-oo NAME=VALUE]*
[-doo NAME=VALUE]*
srcfile* dstfile
Available resampling methods:
near (default), bilinear, cubic, cubicspline, lanczos, average, mode, max, min, med, Q1, Q3.
Execution completed in 0.23 seconds
Results:
{'OUTPUT': '/Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif'}
Loading resulting layers
The following layers were not correctly generated.<ul><li>/Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif</li></ul>You can check the 'Log Messages Panel' in QGIS main window to find more information about the execution of the algorithm.
|
1.0
|
Whenever I perform any Raster extraction such as 'Clip Raster by Extent' or 'Clip Raster by Mask layer' - Whenever I perform any Raster extraction operations such as 'Clip Raster by Extent' or 'Clip Raster by Mask layer'
**I get the below error and doesn't get any desired output.**
Log:
QGIS version: 3.10.11-A Coruña
QGIS code revision: d2171173e4
Qt version: 5.12.3
GDAL version: 2.4.1
GEOS version: 3.7.2-CAPI-1.11.2 b55d2125
PROJ version: Rel. 5.2.0, September 15th, 2018
Processing algorithm…
Algorithm 'Clip raster by mask layer' starting…
Input parameters:
{ 'ALPHA_BAND' : False, 'CROP_TO_CUTLINE' : True, 'DATA_TYPE' : 0, 'EXTRA' : '', 'INPUT' : 'type=xyz&zmin=0&zmax=22&url=https://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x}', 'KEEP_RESOLUTION' : False, 'MASK' : '/Users/rahulgour/Desktop/STR/GIS/vectorGrid/vectorGridSTR.gpkg', 'MULTITHREADING' : False, 'NODATA' : None, 'OPTIONS' : '', 'OUTPUT' : '/Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif', 'SET_RESOLUTION' : False, 'SOURCE_CRS' : QgsCoordinateReferenceSystem('EPSG:3857'), 'TARGET_CRS' : QgsCoordinateReferenceSystem('EPSG:3857'), 'X_RESOLUTION' : None, 'Y_RESOLUTION' : None }
GDAL command:
gdalwarp -s_srs EPSG:3857 -t_srs EPSG:3857 -of GTiff -cutline /Users/rahulgour/Desktop/STR/GIS/vectorGrid/vectorGridSTR.gpkg -cl vectorGridSTR -crop_to_cutline type=xyz&zmin=0&zmax=22&url=https://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x} /Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif
GDAL command output:
/bin/sh: /Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif: No such file or directory
FAILURE: No target filename specified.
Usage: gdalwarp [--help-general] [--formats]
[-s_srs srs_def] [-t_srs srs_def] [-to "NAME=VALUE"]* [-novshiftgrid]
[-order n | -tps | -rpc | -geoloc] [-et err_threshold]
[-refine_gcps tolerance [minimum_gcps]]
[-te xmin ymin xmax ymax] [-tr xres yres] [-tap] [-ts width height]
[-ovr level|AUTO|AUTO-n|NONE] [-wo "NAME=VALUE"] [-ot Byte/Int16/...] [-wt Byte/Int16]
[-srcnodata "value [value...]"] [-dstnodata "value [value...]"] -dstalpha
[-r resampling_method] [-wm memory_in_mb] [-multi] [-q]
[-cutline datasource] [-cl layer] [-cwhere expression]
[-csql statement] [-cblend dist_in_pixels] [-crop_to_cutline]
[-of format] [-co "NAME=VALUE"]* [-overwrite]
[-nomd] [-cvmd meta_conflict_value] [-setci] [-oo NAME=VALUE]*
[-doo NAME=VALUE]*
srcfile* dstfile
Available resampling methods:
near (default), bilinear, cubic, cubicspline, lanczos, average, mode, max, min, med, Q1, Q3.
Execution completed in 0.23 seconds
Results:
{'OUTPUT': '/Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif'}
Loading resulting layers
The following layers were not correctly generated.<ul><li>/Users/rahulgour/Desktop/STR/GIS/ClipSTRGridWise.tif</li></ul>You can check the 'Log Messages Panel' in QGIS main window to find more information about the execution of the algorithm.
|
process
|
whenever i perform any raster extraction such as clip raster by extent or clip raster by mask layer whenever i perform any raster extraction operations such as clip raster by extent or clip raster by mask layer i get the below error and doesn t get any desired output log qgis version a coruña qgis code revision qt version gdal version geos version capi proj version rel september processing algorithm… algorithm clip raster by mask layer starting… input parameters alpha band false crop to cutline true data type extra input type xyz zmin zmax url keep resolution false mask users rahulgour desktop str gis vectorgrid vectorgridstr gpkg multithreading false nodata none options output users rahulgour desktop str gis clipstrgridwise tif set resolution false source crs qgscoordinatereferencesystem epsg target crs qgscoordinatereferencesystem epsg x resolution none y resolution none gdal command gdalwarp s srs epsg t srs epsg of gtiff cutline users rahulgour desktop str gis vectorgrid vectorgridstr gpkg cl vectorgridstr crop to cutline type xyz zmin zmax url users rahulgour desktop str gis clipstrgridwise tif gdal command output bin sh users rahulgour desktop str gis clipstrgridwise tif no such file or directory failure no target filename specified usage gdalwarp dstalpha srcfile dstfile available resampling methods near default bilinear cubic cubicspline lanczos average mode max min med execution completed in seconds results output users rahulgour desktop str gis clipstrgridwise tif loading resulting layers the following layers were not correctly generated users rahulgour desktop str gis clipstrgridwise tif you can check the log messages panel in qgis main window to find more information about the execution of the algorithm
| 1
|
11,673
| 14,531,657,853
|
IssuesEvent
|
2020-12-14 21:08:17
|
pacificclimate/quail
|
https://api.github.com/repos/pacificclimate/quail
|
closed
|
climdex data pre-processing climdexInput.raw
|
process
|
## Description
This process takes `rda` files to generate `climdexInput` object
## Function to wrap
[climdexInput.raw](https://github.com/pacificclimate/climdex.pcic/blob/master/R/climdex.r#L541)
|
1.0
|
climdex data pre-processing climdexInput.raw - ## Description
This process takes `rda` files to generate `climdexInput` object
## Function to wrap
[climdexInput.raw](https://github.com/pacificclimate/climdex.pcic/blob/master/R/climdex.r#L541)
|
process
|
climdex data pre processing climdexinput raw description this process takes rda files to generate climdexinput object function to wrap
| 1
|
40,841
| 8,854,532,965
|
IssuesEvent
|
2019-01-09 01:47:48
|
dotnet/roslyn-analyzers
|
https://api.github.com/repos/dotnet/roslyn-analyzers
|
closed
|
Show warning annotation in MakeMemberStatic code fix preview if all references are not updated
|
Area-Microsoft.CodeQuality.Analyzers Feature Request
|
FYI @heejaechang
|
1.0
|
Show warning annotation in MakeMemberStatic code fix preview if all references are not updated - FYI @heejaechang
|
non_process
|
show warning annotation in makememberstatic code fix preview if all references are not updated fyi heejaechang
| 0
|
448,266
| 12,946,472,336
|
IssuesEvent
|
2020-07-18 19:11:48
|
penguin-statistics/frontend-v2
|
https://api.github.com/repos/penguin-statistics/frontend-v2
|
closed
|
Improve page switching
|
feature request priority:1
|
### What problem does this feature solve?
It is inconvenient if user wants to see the drop rate of 异铁 first, then go to 异铁组; Or report 4-9 first, then go to 4-10.
### What does the proposed API look like?
Add some links so that user can switch between related items/stages easily.
<!-- generated by issue-helper. DO NOT REMOVE. ref:d86a45e47c468ce842c434d31c7da0f2 -->
|
1.0
|
Improve page switching - ### What problem does this feature solve?
It is inconvenient if user wants to see the drop rate of 异铁 first, then go to 异铁组; Or report 4-9 first, then go to 4-10.
### What does the proposed API look like?
Add some links so that user can switch between related items/stages easily.
<!-- generated by issue-helper. DO NOT REMOVE. ref:d86a45e47c468ce842c434d31c7da0f2 -->
|
non_process
|
improve page switching what problem does this feature solve it is inconvenient if user wants to see the drop rate of 异铁 first then go to 异铁组 or report first then go to what does the proposed api look like add some links so that user can switch between related items stages easily
| 0
|
48,622
| 12,224,200,052
|
IssuesEvent
|
2020-05-02 21:16:47
|
vega/vega-lite
|
https://api.github.com/repos/vega/vega-lite
|
closed
|
Alternative to null significance in JSON schema
|
Area - Refactor :building_construction: Feature Request :raising_hand_woman: P4 RFC / Discussion :speech_balloon:
|
A number of places in the vega-lite schema use `null` as a significant value, for example:
```json
"scale": {
"anyOf": [
{
"$ref": "#/definitions/Scale"
},
{
"type": "null"
}
],
"description": "…If `null`, the scale will be [disabled and the data value will be directly encoded] … If undefined, default [scale properties]… are applied."
}
```
This is fine for JavaScript, which treats `null` as distinct from `undefined`, but most other languages don't have that distinction, and thus their JSON serialization frameworks treats `null` the same as the absence of a property. Some frameworks have an option to output explicit `null` values for absent keys, but these are often configured at a global level, such as Scala's Circe property `dropNullValues`, which is even more problematic, because very verbose schemas would be output with many null values that trigger Vega-lite's explicit null handing.
I would suggest adding a global definition that acts as an explicit null value and using that instead. It could be a `oneOf` with `null` (for backwards-compatibility) and some constant object, something like:
```json
"ExplicitNull": {
"oneOf": [
{ "type": "null" },
{ "type": "object", "required": [ "explicitNull" ], "properties": { "explicitNull": { "type": "boolean" } } }
]
}
```
That type could then be referenced as so:
```json
"scale": {
"anyOf": [
{
"$ref": "#/definitions/Scale"
},
{
"$ref": "#/definitions/ExplicitNull"
}
],
"description": "…If `ExplicitNull`, the scale will be [disabled and the data value will be directly encoded] … If undefined, default [scale properties]… are applied."
}
```
That way, a language/framework that has difficulty serializing null values to JSON could specify that it should be treated as null with JSON like:
```json
{ "scale": { "explicitNull": true } }
```
See also: https://github.com/vega/vega-lite/issues/2400 (where there was proposed having an explicit value that signified `null`)
|
1.0
|
Alternative to null significance in JSON schema - A number of places in the vega-lite schema use `null` as a significant value, for example:
```json
"scale": {
"anyOf": [
{
"$ref": "#/definitions/Scale"
},
{
"type": "null"
}
],
"description": "…If `null`, the scale will be [disabled and the data value will be directly encoded] … If undefined, default [scale properties]… are applied."
}
```
This is fine for JavaScript, which treats `null` as distinct from `undefined`, but most other languages don't have that distinction, and thus their JSON serialization frameworks treats `null` the same as the absence of a property. Some frameworks have an option to output explicit `null` values for absent keys, but these are often configured at a global level, such as Scala's Circe property `dropNullValues`, which is even more problematic, because very verbose schemas would be output with many null values that trigger Vega-lite's explicit null handing.
I would suggest adding a global definition that acts as an explicit null value and using that instead. It could be a `oneOf` with `null` (for backwards-compatibility) and some constant object, something like:
```json
"ExplicitNull": {
"oneOf": [
{ "type": "null" },
{ "type": "object", "required": [ "explicitNull" ], "properties": { "explicitNull": { "type": "boolean" } } }
]
}
```
That type could then be referenced as so:
```json
"scale": {
"anyOf": [
{
"$ref": "#/definitions/Scale"
},
{
"$ref": "#/definitions/ExplicitNull"
}
],
"description": "…If `ExplicitNull`, the scale will be [disabled and the data value will be directly encoded] … If undefined, default [scale properties]… are applied."
}
```
That way, a language/framework that has difficulty serializing null values to JSON could specify that it should be treated as null with JSON like:
```json
{ "scale": { "explicitNull": true } }
```
See also: https://github.com/vega/vega-lite/issues/2400 (where there was proposed having an explicit value that signified `null`)
|
non_process
|
alternative to null significance in json schema a number of places in the vega lite schema use null as a significant value for example json scale anyof ref definitions scale type null description …if null the scale will be … if undefined default … are applied this is fine for javascript which treats null as distinct from undefined but most other languages don t have that distinction and thus their json serialization frameworks treats null the same as the absence of a property some frameworks have an option to output explicit null values for absent keys but these are often configured at a global level such as scala s circe property dropnullvalues which is even more problematic because very verbose schemas would be output with many null values that trigger vega lite s explicit null handing i would suggest adding a global definition that acts as an explicit null value and using that instead it could be a oneof with null for backwards compatibility and some constant object something like json explicitnull oneof type null type object required properties explicitnull type boolean that type could then be referenced as so json scale anyof ref definitions scale ref definitions explicitnull description …if explicitnull the scale will be … if undefined default … are applied that way a language framework that has difficulty serializing null values to json could specify that it should be treated as null with json like json scale explicitnull true see also where there was proposed having an explicit value that signified null
| 0
|
17,649
| 23,470,942,758
|
IssuesEvent
|
2022-08-16 21:46:55
|
googleapis/gapic-generator-python
|
https://api.github.com/repos/googleapis/gapic-generator-python
|
opened
|
Require PRs to update documentation
|
type: process priority: p2
|
As a follow-up to #1390 (or maybe as a way of accomplishing that), we should
- require all PRs to either include changes to documentation or to have a tag in the PR description (or maybe just a label?) saying the PR has no documentation impact
- if allowed by corporate policies, implement the procedure in https://docs.readthedocs.io/en/stable/pull-requests.html to be able to preview documentation when reviewing PRs
|
1.0
|
Require PRs to update documentation - As a follow-up to #1390 (or maybe as a way of accomplishing that), we should
- require all PRs to either include changes to documentation or to have a tag in the PR description (or maybe just a label?) saying the PR has no documentation impact
- if allowed by corporate policies, implement the procedure in https://docs.readthedocs.io/en/stable/pull-requests.html to be able to preview documentation when reviewing PRs
|
process
|
require prs to update documentation as a follow up to or maybe as a way of accomplishing that we should require all prs to either include changes to documentation or to have a tag in the pr description or maybe just a label saying the pr has no documentation impact if allowed by corporate policies implement the procedure in to be able to preview documentation when reviewing prs
| 1
|
101,073
| 21,574,922,117
|
IssuesEvent
|
2022-05-02 12:48:24
|
apple/swift
|
https://api.github.com/repos/apple/swift
|
opened
|
Enum element labels not suggested in unresolved dot completion inside multi-statement closure
|
bug CodeCompletion
|
The following new test case fails:
```swift
// RUN: %swift-ide-test -code-completion -source-filename %s -code-completion-token COMPLETE | %FileCheck %s
enum DragState {
case dragging(translation: Int, predictedLocation: Int)
}
func pnChanged(_ action: () -> Void) {}
func foo() {
var gestureViewState: DragState = .dragging(translation: 0, predictedLocation: 0)
let longPressDrag = pnChanged {
_ = 1
gestureViewState = .dragging(translation: 0, #^COMPLETE^#predictedLocation: 0)
}
}
// CHECK: Begin completions, 1 items
// CHECK-DAG: Pattern/Local/Flair[ArgLabels]: {#predictedLocation: Int#}[#Int#];
// CHECK: End completion
```
Code completion works correctly when
- Discarding the result of `unchanged`
- Making the closure a single-statement closure
|
1.0
|
Enum element labels not suggested in unresolved dot completion inside multi-statement closure - The following new test case fails:
```swift
// RUN: %swift-ide-test -code-completion -source-filename %s -code-completion-token COMPLETE | %FileCheck %s
enum DragState {
case dragging(translation: Int, predictedLocation: Int)
}
func pnChanged(_ action: () -> Void) {}
func foo() {
var gestureViewState: DragState = .dragging(translation: 0, predictedLocation: 0)
let longPressDrag = pnChanged {
_ = 1
gestureViewState = .dragging(translation: 0, #^COMPLETE^#predictedLocation: 0)
}
}
// CHECK: Begin completions, 1 items
// CHECK-DAG: Pattern/Local/Flair[ArgLabels]: {#predictedLocation: Int#}[#Int#];
// CHECK: End completion
```
Code completion works correctly when
- Discarding the result of `unchanged`
- Making the closure a single-statement closure
|
non_process
|
enum element labels not suggested in unresolved dot completion inside multi statement closure the following new test case fails swift run swift ide test code completion source filename s code completion token complete filecheck s enum dragstate case dragging translation int predictedlocation int func pnchanged action void func foo var gestureviewstate dragstate dragging translation predictedlocation let longpressdrag pnchanged gestureviewstate dragging translation complete predictedlocation check begin completions items check dag pattern local flair predictedlocation int check end completion code completion works correctly when discarding the result of unchanged making the closure a single statement closure
| 0
|
9,795
| 12,810,359,463
|
IssuesEvent
|
2020-07-03 18:22:24
|
hashgraph/hedera-mirror-node
|
https://api.github.com/repos/hashgraph/hedera-mirror-node
|
closed
|
Google Cloud Marketplace
|
P1 enhancement epic marketplace process
|
**Problem**
We should enable users to run the Hedera Mirror Node in [Google Cloud Marketplace](https://console.cloud.google.com/marketplace) with just a few clicks
**Solution**
- Depends on requester pay buckets (#357) being complete and available
- Depends on any outstanding Kubernetes tasks that are critical (TBD)
**Alternatives**
**Additional Context**
|
1.0
|
Google Cloud Marketplace - **Problem**
We should enable users to run the Hedera Mirror Node in [Google Cloud Marketplace](https://console.cloud.google.com/marketplace) with just a few clicks
**Solution**
- Depends on requester pay buckets (#357) being complete and available
- Depends on any outstanding Kubernetes tasks that are critical (TBD)
**Alternatives**
**Additional Context**
|
process
|
google cloud marketplace problem we should enable users to run the hedera mirror node in with just a few clicks solution depends on requester pay buckets being complete and available depends on any outstanding kubernetes tasks that are critical tbd alternatives additional context
| 1
|
200,016
| 6,997,219,108
|
IssuesEvent
|
2017-12-16 11:57:09
|
Rsl1122/Plan-PlayerAnalytics
|
https://api.github.com/repos/Rsl1122/Plan-PlayerAnalytics
|
opened
|
MySQL Password can be obtained illegally from Bungee server
|
Priority: HIGH Security Vulnerability server: BungeeCord status: Done
|
It is possible to obtain mysql password from bungee server.
Further details will be disclosed after most vulnerable servers have been patched.
|
1.0
|
MySQL Password can be obtained illegally from Bungee server - It is possible to obtain mysql password from bungee server.
Further details will be disclosed after most vulnerable servers have been patched.
|
non_process
|
mysql password can be obtained illegally from bungee server it is possible to obtain mysql password from bungee server further details will be disclosed after most vulnerable servers have been patched
| 0
|
415,163
| 28,020,394,889
|
IssuesEvent
|
2023-03-28 04:39:21
|
DuongViKhang/TOEN430979_API-Dashboard
|
https://api.github.com/repos/DuongViKhang/TOEN430979_API-Dashboard
|
closed
|
Đưa ra các giải pháp để giải quyết khó khăn khi thực hiện dự án
|
documentation
|
Đưa ra các giải pháp để giải quyết khó khăn khi thực hiện dự án.
|
1.0
|
Đưa ra các giải pháp để giải quyết khó khăn khi thực hiện dự án - Đưa ra các giải pháp để giải quyết khó khăn khi thực hiện dự án.
|
non_process
|
đưa ra các giải pháp để giải quyết khó khăn khi thực hiện dự án đưa ra các giải pháp để giải quyết khó khăn khi thực hiện dự án
| 0
|
19,726
| 26,073,852,357
|
IssuesEvent
|
2022-12-24 07:11:32
|
pyanodon/pybugreports
|
https://api.github.com/repos/pyanodon/pybugreports
|
closed
|
hotair-2 dependencies
|
needs investigation progression mod:pypostprocessing
|
### Mod source
PyAE Beta
### Which mod are you having an issue with?
- [ ] pyalienlife
- [ ] pyalternativeenergy
- [ ] pycoalprocessing
- [ ] pyfusionenergy
- [ ] pyhightech
- [ ] pyindustry
- [ ] pypetroleumhandling
- [X] pypostprocessing
- [ ] pyrawores
### Operating system
>=Windows 10
### What kind of issue is this?
- [ ] Compatibility
- [ ] Locale (names, descriptions, unknown keys)
- [ ] Graphical
- [ ] Crash
- [X] Progression
- [ ] Balance
- [ ] Pypostprocessing failure
- [ ] Other
### What is the problem?
The molten salt ingredient dependency seems to just pick the earliest/first alphabetically tech that it can come from. This forces one to research renewable-mk01 and biomassplant-mk01, rather than letting one pick between biomass, coal, or oil at that stage.
### Steps to reproduce
_No response_
### Additional context
_No response_
### Log file
_No response_
|
1.0
|
hotair-2 dependencies - ### Mod source
PyAE Beta
### Which mod are you having an issue with?
- [ ] pyalienlife
- [ ] pyalternativeenergy
- [ ] pycoalprocessing
- [ ] pyfusionenergy
- [ ] pyhightech
- [ ] pyindustry
- [ ] pypetroleumhandling
- [X] pypostprocessing
- [ ] pyrawores
### Operating system
>=Windows 10
### What kind of issue is this?
- [ ] Compatibility
- [ ] Locale (names, descriptions, unknown keys)
- [ ] Graphical
- [ ] Crash
- [X] Progression
- [ ] Balance
- [ ] Pypostprocessing failure
- [ ] Other
### What is the problem?
The molten salt ingredient dependency seems to just pick the earliest/first alphabetically tech that it can come from. This forces one to research renewable-mk01 and biomassplant-mk01, rather than letting one pick between biomass, coal, or oil at that stage.
### Steps to reproduce
_No response_
### Additional context
_No response_
### Log file
_No response_
|
process
|
hotair dependencies mod source pyae beta which mod are you having an issue with pyalienlife pyalternativeenergy pycoalprocessing pyfusionenergy pyhightech pyindustry pypetroleumhandling pypostprocessing pyrawores operating system windows what kind of issue is this compatibility locale names descriptions unknown keys graphical crash progression balance pypostprocessing failure other what is the problem the molten salt ingredient dependency seems to just pick the earliest first alphabetically tech that it can come from this forces one to research renewable and biomassplant rather than letting one pick between biomass coal or oil at that stage steps to reproduce no response additional context no response log file no response
| 1
|
2,622
| 5,396,583,782
|
IssuesEvent
|
2017-02-27 12:12:16
|
jlm2017/jlm-video-subtitles
|
https://api.github.com/repos/jlm2017/jlm-video-subtitles
|
closed
|
[subtitles] [fr] FAIRE LA RÉVOLUTION FISCALE - #EDCC15
|
Language: French Process: [6] Approved
|
# Video title
FAIRE LA RÉVOLUTION FISCALE - #EDCC15 JEAN-LUC MÉLENCHON
# URL
https://www.youtube.com/watch?v=8fF40FiZ36c
# Youtube subtitles language
French
# Duration
19:30
# Subtitles URL
https://www.youtube.com/timedtext_video?ref=player&v=8fF40FiZ36c
|
1.0
|
[subtitles] [fr] FAIRE LA RÉVOLUTION FISCALE - #EDCC15 - # Video title
FAIRE LA RÉVOLUTION FISCALE - #EDCC15 JEAN-LUC MÉLENCHON
# URL
https://www.youtube.com/watch?v=8fF40FiZ36c
# Youtube subtitles language
French
# Duration
19:30
# Subtitles URL
https://www.youtube.com/timedtext_video?ref=player&v=8fF40FiZ36c
|
process
|
faire la révolution fiscale video title faire la révolution fiscale jean luc mélenchon url youtube subtitles language french duration subtitles url
| 1
|
65,371
| 19,433,201,957
|
IssuesEvent
|
2021-12-21 14:19:33
|
vector-im/element-web
|
https://api.github.com/repos/vector-im/element-web
|
closed
|
UTD from Matthew
|
T-Defect S-Major A-E2EE
|
<!-- A picture's worth a thousand words: PLEASE INCLUDE A SCREENSHOT :P -->
<!-- Please report security issues by email to security@matrix.org -->
<!-- This is a bug report template. By following the instructions below and
filling out the sections with your information, you will help the us to get all
the necessary data to fix your issue.
You can also preview your report before submitting it. You may remove sections
that aren't relevant to your particular case.
Text between <!-- and --> marks will be invisible in the report.
-->
### Description
Describe here the problem that you are experiencing, or the feature you are requesting.
### Steps to reproduce
- For bugs, list the steps
- that reproduce the bug
- using hyphens as bullet points
Describe how what happens differs from what you expected.
Log: sent <!-- You can send us the app's logs via the 'Report bug'
link on the 'Settings' page. Very important for hard-to-reproduce bugs. Please
file a bug here too! -->
<!-- Include screenshots if possible: you can drag and drop images below. -->
### Version information
<!-- IMPORTANT: please answer the following questions, to help us narrow down the problem -->
- **Platform**: desktop, macOS
For the web app:
- **Browser**: Chrome, Firefox, Safari, Edge? which version?
- **OS**: Windows, macOS, Ubuntu, Arch Linux, etc?
- **URL**: develop.element.io / app.element.io / somewhere else? If a private server, what version of Element Web?
For the desktop app:
- **OS**: Windows, macOS, Ubuntu, Arch Linux, etc?
- **Version**: 1.x.y <!-- check the user settings panel if unsure -->
|
1.0
|
UTD from Matthew - <!-- A picture's worth a thousand words: PLEASE INCLUDE A SCREENSHOT :P -->
<!-- Please report security issues by email to security@matrix.org -->
<!-- This is a bug report template. By following the instructions below and
filling out the sections with your information, you will help the us to get all
the necessary data to fix your issue.
You can also preview your report before submitting it. You may remove sections
that aren't relevant to your particular case.
Text between <!-- and --> marks will be invisible in the report.
-->
### Description
Describe here the problem that you are experiencing, or the feature you are requesting.
### Steps to reproduce
- For bugs, list the steps
- that reproduce the bug
- using hyphens as bullet points
Describe how what happens differs from what you expected.
Log: sent <!-- You can send us the app's logs via the 'Report bug'
link on the 'Settings' page. Very important for hard-to-reproduce bugs. Please
file a bug here too! -->
<!-- Include screenshots if possible: you can drag and drop images below. -->
### Version information
<!-- IMPORTANT: please answer the following questions, to help us narrow down the problem -->
- **Platform**: desktop, macOS
For the web app:
- **Browser**: Chrome, Firefox, Safari, Edge? which version?
- **OS**: Windows, macOS, Ubuntu, Arch Linux, etc?
- **URL**: develop.element.io / app.element.io / somewhere else? If a private server, what version of Element Web?
For the desktop app:
- **OS**: Windows, macOS, Ubuntu, Arch Linux, etc?
- **Version**: 1.x.y <!-- check the user settings panel if unsure -->
|
non_process
|
utd from matthew this is a bug report template by following the instructions below and filling out the sections with your information you will help the us to get all the necessary data to fix your issue you can also preview your report before submitting it you may remove sections that aren t relevant to your particular case text between marks will be invisible in the report description describe here the problem that you are experiencing or the feature you are requesting steps to reproduce for bugs list the steps that reproduce the bug using hyphens as bullet points describe how what happens differs from what you expected log sent you can send us the app s logs via the report bug link on the settings page very important for hard to reproduce bugs please file a bug here too version information platform desktop macos for the web app browser chrome firefox safari edge which version os windows macos ubuntu arch linux etc url develop element io app element io somewhere else if a private server what version of element web for the desktop app os windows macos ubuntu arch linux etc version x y
| 0
|
22,592
| 31,816,262,097
|
IssuesEvent
|
2023-09-13 20:43:07
|
DNNCommunity/Dnn.CommunityForums
|
https://api.github.com/repos/DNNCommunity/Dnn.CommunityForums
|
closed
|
BUG: v8 upgrade Topicview template issue
|
bug review in process
|
## Describe the bug
When I upgrade to v8 it seems all my custom templates are copied correctly fro database to .txt file, but the topicview.txt file does not contain the right HTML
## Software Versions
- DNN: 09.10.02
- Module: 08.00.00
## To Reproduce
Steps to reproduce the behavior:
1. Add some code to TopicView template on forums version 7
2. Upgrade to v8 of the module
3. The code is not in the TopicView.txt file
## Expected behavior
TopicView.txt should contain the data from the database
## Screenshots
## Additional context
I emailed @johnhenley a video demo
|
1.0
|
BUG: v8 upgrade Topicview template issue - ## Describe the bug
When I upgrade to v8 it seems all my custom templates are copied correctly fro database to .txt file, but the topicview.txt file does not contain the right HTML
## Software Versions
- DNN: 09.10.02
- Module: 08.00.00
## To Reproduce
Steps to reproduce the behavior:
1. Add some code to TopicView template on forums version 7
2. Upgrade to v8 of the module
3. The code is not in the TopicView.txt file
## Expected behavior
TopicView.txt should contain the data from the database
## Screenshots
## Additional context
I emailed @johnhenley a video demo
|
process
|
bug upgrade topicview template issue describe the bug when i upgrade to it seems all my custom templates are copied correctly fro database to txt file but the topicview txt file does not contain the right html software versions dnn module to reproduce steps to reproduce the behavior add some code to topicview template on forums version upgrade to of the module the code is not in the topicview txt file expected behavior topicview txt should contain the data from the database screenshots additional context i emailed johnhenley a video demo
| 1
|
6,093
| 8,951,525,131
|
IssuesEvent
|
2019-01-25 14:12:42
|
jasonblais/mattermost-community
|
https://api.github.com/repos/jasonblais/mattermost-community
|
opened
|
Update PULL_REQUEST_TEMPLATE.md for Mattermost repos
|
Contributor Journey Process
|
The pull request template has a few issues:
1. Not everyone removes the filler texts, making the PR description confusing when submitted. We should instead use the following format to describe expectations within the pull request template
```
<!--
Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog
-->
```
These notes will then not appear in the PR description regardless of whether the community member removes them or not.
Finally, the checklist for a PR is outdated, and some items aren't relevant. We should reference, and update, the contribution checklist here https://developers.mattermost.com/contribute/getting-started/contribution-checklist/
|
1.0
|
Update PULL_REQUEST_TEMPLATE.md for Mattermost repos - The pull request template has a few issues:
1. Not everyone removes the filler texts, making the PR description confusing when submitted. We should instead use the following format to describe expectations within the pull request template
```
<!--
Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog
-->
```
These notes will then not appear in the PR description regardless of whether the community member removes them or not.
Finally, the checklist for a PR is outdated, and some items aren't relevant. We should reference, and update, the contribution checklist here https://developers.mattermost.com/contribute/getting-started/contribution-checklist/
|
process
|
update pull request template md for mattermost repos the pull request template has a few issues not everyone removes the filler texts making the pr description confusing when submitted we should instead use the following format to describe expectations within the pull request template write a short one line summary that describes the changes in this pull request for inclusion in the changelog these notes will then not appear in the pr description regardless of whether the community member removes them or not finally the checklist for a pr is outdated and some items aren t relevant we should reference and update the contribution checklist here
| 1
|
15,194
| 18,976,642,102
|
IssuesEvent
|
2021-11-20 04:38:24
|
redwoodjs/redwood
|
https://api.github.com/repos/redwoodjs/redwood
|
closed
|
Redwood not working with Node.js < v14.17
|
triage/processing
|
I've already installed like 5 node versions with nvm, I started with 14.0.0 which is the suggested version, then tried with 14.13.0, 15.0.0, 16.13.0, 17.0.0, but I always get a compatibility error with some of the libraries redwood uses, the last one I tried was 14.13.0 and get the following error with jest-watch-typeahead:
`'error jest-watch-typeahead@1.0.0: The engine "node" is incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || >=16.0.0". Got "14.13.0"\n'`
So, which node version actually works?
|
1.0
|
Redwood not working with Node.js < v14.17 - I've already installed like 5 node versions with nvm, I started with 14.0.0 which is the suggested version, then tried with 14.13.0, 15.0.0, 16.13.0, 17.0.0, but I always get a compatibility error with some of the libraries redwood uses, the last one I tried was 14.13.0 and get the following error with jest-watch-typeahead:
`'error jest-watch-typeahead@1.0.0: The engine "node" is incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || >=16.0.0". Got "14.13.0"\n'`
So, which node version actually works?
|
process
|
redwood not working with node js i ve already installed like node versions with nvm i started with which is the suggested version then tried with but i always get a compatibility error with some of the libraries redwood uses the last one i tried was and get the following error with jest watch typeahead error jest watch typeahead the engine node is incompatible with this module expected version got n so which node version actually works
| 1
|
15,198
| 19,008,144,087
|
IssuesEvent
|
2021-11-23 04:47:33
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
"TIN interpolation" in modeller, multiple python errors
|
Processing Bug Modeller
|
### What is the bug or the crash?
When using the TIN interpolation tool in the Modeller, it returns a few different python errors.
### Steps to reproduce the issue
1) add a point or line layer in the project
2) open the modeller, add the TIN interpolation tool
3) set the input with the project layer, set the extent, set the output, press OK
4) not right click "TIn interpolation" in the model and chose "edit"
```
Traceback (most recent call last):
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerGraphicItem.py", line 161, in editComponent
self.edit()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerGraphicItem.py", line 134, in edit
dlg = ModelerParametersDialog(elemAlg, self.model(), self.component().childId(),
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 79, in __init__
self.widget = ModelerParametersWidget(alg, model, algName, configuration, context=self.context, dialog=self)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 497, in __init__
self.widget = ModelerParametersPanelWidget(alg, model, algName, configuration, dialog, context)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 193, in __init__
self.setupUi()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 315, in setupUi
self.setPreviousValues()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 378, in setPreviousValues
wrapper.setValue(value)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 214, in setValue
self.widget.setValue(value)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 161, in setValue
self.addLayerData(v[0], v[1])
AttributeError: 'InterpolationDataWidget' object has no attribute 'addLayerData'
```
**or**
1) blank project
2) open the modeller, add the TIN interpolation tool
3) Press the green "+" button
```
Traceback (most recent call last):
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 117, in addLayer
self._addLayerData(layer.name(), attribute)
AttributeError: 'NoneType' object has no attribute 'name'
```
**or**
1) blank project
2) open the modeller, add the TIN interpolation tool
3) define an output name, press OK
4) try edit the TIN interpolation tool
```
2021-11-22T22:01:58 WARNING Traceback (most recent call last):
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerGraphicItem.py", line 161, in editComponent
self.edit()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerGraphicItem.py", line 134, in edit
dlg = ModelerParametersDialog(elemAlg, self.model(), self.component().childId(),
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 79, in __init__
self.widget = ModelerParametersWidget(alg, model, algName, configuration, context=self.context, dialog=self)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 497, in __init__
self.widget = ModelerParametersPanelWidget(alg, model, algName, configuration, dialog, context)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 193, in __init__
self.setupUi()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 315, in setupUi
self.setPreviousValues()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 378, in setPreviousValues
wrapper.setValue(value)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 214, in setValue
self.widget.setValue(value)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 158, in setValue
rows = value.split(';')
AttributeError: 'NoneType' object has no attribute 'split'
```
### Versions
QGIS 3.16.14
### Supported QGIS version
- [X] I'm running a supported QGIS version according to the roadmap.
### New profile
- [X] I tried with a new QGIS profile
### Additional context
_No response_
|
1.0
|
"TIN interpolation" in modeller, multiple python errors - ### What is the bug or the crash?
When using the TIN interpolation tool in the Modeller, it returns a few different python errors.
### Steps to reproduce the issue
1) add a point or line layer in the project
2) open the modeller, add the TIN interpolation tool
3) set the input with the project layer, set the extent, set the output, press OK
4) not right click "TIn interpolation" in the model and chose "edit"
```
Traceback (most recent call last):
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerGraphicItem.py", line 161, in editComponent
self.edit()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerGraphicItem.py", line 134, in edit
dlg = ModelerParametersDialog(elemAlg, self.model(), self.component().childId(),
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 79, in __init__
self.widget = ModelerParametersWidget(alg, model, algName, configuration, context=self.context, dialog=self)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 497, in __init__
self.widget = ModelerParametersPanelWidget(alg, model, algName, configuration, dialog, context)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 193, in __init__
self.setupUi()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 315, in setupUi
self.setPreviousValues()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 378, in setPreviousValues
wrapper.setValue(value)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 214, in setValue
self.widget.setValue(value)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 161, in setValue
self.addLayerData(v[0], v[1])
AttributeError: 'InterpolationDataWidget' object has no attribute 'addLayerData'
```
**or**
1) blank project
2) open the modeller, add the TIN interpolation tool
3) Press the green "+" button
```
Traceback (most recent call last):
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 117, in addLayer
self._addLayerData(layer.name(), attribute)
AttributeError: 'NoneType' object has no attribute 'name'
```
**or**
1) blank project
2) open the modeller, add the TIN interpolation tool
3) define an output name, press OK
4) try edit the TIN interpolation tool
```
2021-11-22T22:01:58 WARNING Traceback (most recent call last):
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerGraphicItem.py", line 161, in editComponent
self.edit()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerGraphicItem.py", line 134, in edit
dlg = ModelerParametersDialog(elemAlg, self.model(), self.component().childId(),
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 79, in __init__
self.widget = ModelerParametersWidget(alg, model, algName, configuration, context=self.context, dialog=self)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 497, in __init__
self.widget = ModelerParametersPanelWidget(alg, model, algName, configuration, dialog, context)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 193, in __init__
self.setupUi()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 315, in setupUi
self.setPreviousValues()
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\modeler\ModelerParametersDialog.py", line 378, in setPreviousValues
wrapper.setValue(value)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 214, in setValue
self.widget.setValue(value)
File "C:\OSGeo4W/apps/qgis-ltr/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 158, in setValue
rows = value.split(';')
AttributeError: 'NoneType' object has no attribute 'split'
```
### Versions
QGIS 3.16.14
### Supported QGIS version
- [X] I'm running a supported QGIS version according to the roadmap.
### New profile
- [X] I tried with a new QGIS profile
### Additional context
_No response_
|
process
|
tin interpolation in modeller multiple python errors what is the bug or the crash when using the tin interpolation tool in the modeller it returns a few different python errors steps to reproduce the issue add a point or line layer in the project open the modeller add the tin interpolation tool set the input with the project layer set the extent set the output press ok not right click tin interpolation in the model and chose edit traceback most recent call last file c apps qgis ltr python plugins processing modeler modelergraphicitem py line in editcomponent self edit file c apps qgis ltr python plugins processing modeler modelergraphicitem py line in edit dlg modelerparametersdialog elemalg self model self component childid file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in init self widget modelerparameterswidget alg model algname configuration context self context dialog self file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in init self widget modelerparameterspanelwidget alg model algname configuration dialog context file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in init self setupui file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in setupui self setpreviousvalues file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in setpreviousvalues wrapper setvalue value file c apps qgis ltr python plugins processing algs qgis ui interpolationwidgets py line in setvalue self widget setvalue value file c apps qgis ltr python plugins processing algs qgis ui interpolationwidgets py line in setvalue self addlayerdata v v attributeerror interpolationdatawidget object has no attribute addlayerdata or blank project open the modeller add the tin interpolation tool press the green button traceback most recent call last file c apps qgis ltr python plugins processing algs qgis ui interpolationwidgets py line in addlayer self addlayerdata layer name attribute attributeerror nonetype object has no attribute name or blank project open the modeller add the tin interpolation tool define an output name press ok try edit the tin interpolation tool warning traceback most recent call last file c apps qgis ltr python plugins processing modeler modelergraphicitem py line in editcomponent self edit file c apps qgis ltr python plugins processing modeler modelergraphicitem py line in edit dlg modelerparametersdialog elemalg self model self component childid file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in init self widget modelerparameterswidget alg model algname configuration context self context dialog self file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in init self widget modelerparameterspanelwidget alg model algname configuration dialog context file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in init self setupui file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in setupui self setpreviousvalues file c apps qgis ltr python plugins processing modeler modelerparametersdialog py line in setpreviousvalues wrapper setvalue value file c apps qgis ltr python plugins processing algs qgis ui interpolationwidgets py line in setvalue self widget setvalue value file c apps qgis ltr python plugins processing algs qgis ui interpolationwidgets py line in setvalue rows value split attributeerror nonetype object has no attribute split versions qgis supported qgis version i m running a supported qgis version according to the roadmap new profile i tried with a new qgis profile additional context no response
| 1
|
3,829
| 6,802,325,050
|
IssuesEvent
|
2017-11-02 19:47:51
|
WikiWatershed/model-my-watershed
|
https://api.github.com/repos/WikiWatershed/model-my-watershed
|
closed
|
Geoprocessing API: Validate RWD Requests Have Required Keys
|
Geoprocessing API tested/verified WPF
|
We currently [assume the required RWD body keys are present](https://github.com/WikiWatershed/model-my-watershed/blob/develop/src/mmw/apps/geoprocessing_api/views.py#L171). We should be checking that they're present, and when they're not, send a response back informing the user what keys they're missing.
|
1.0
|
Geoprocessing API: Validate RWD Requests Have Required Keys - We currently [assume the required RWD body keys are present](https://github.com/WikiWatershed/model-my-watershed/blob/develop/src/mmw/apps/geoprocessing_api/views.py#L171). We should be checking that they're present, and when they're not, send a response back informing the user what keys they're missing.
|
process
|
geoprocessing api validate rwd requests have required keys we currently we should be checking that they re present and when they re not send a response back informing the user what keys they re missing
| 1
|
11,009
| 13,795,234,031
|
IssuesEvent
|
2020-10-09 17:39:16
|
amor71/LiuAlgoTrader
|
https://api.github.com/repos/amor71/LiuAlgoTrader
|
closed
|
notebook improvements
|
in-process
|
1. move code to Python
2. add full examples in the documentation
3. simplify, remove redundant code
4. code clean-up
|
1.0
|
notebook improvements - 1. move code to Python
2. add full examples in the documentation
3. simplify, remove redundant code
4. code clean-up
|
process
|
notebook improvements move code to python add full examples in the documentation simplify remove redundant code code clean up
| 1
|
3,540
| 6,575,796,849
|
IssuesEvent
|
2017-09-11 17:21:43
|
w3c/w3process
|
https://api.github.com/repos/w3c/w3process
|
closed
|
The appeals process doesn't actually describe how an appeal finishes
|
Process2018Candidate
|
Section 7.2 ends by saying "If, within one week of the Team's announcement, 5% or more of the Advisory Committee support the appeal request, the Team must organize an appeal vote asking the Advisory Committee to approve or reject the decision."
What happens next? We get a formal vote to overturn the decision. But is there any requirement on how long the vote is open? What is the threshold (simple majority?)? What exactly is the question? (I.e. is it "Should the Chocolate IG be formed?" or "Should the Director's Decision to form the Chocolate IG be overturned"?). If the AC votes contrary to the Director, is the decision automatically overturned, or is it sent back to the Director to think harder?
We've not been down this road and hope we never will, but even so, this degree of uncertainty might be worrying.
|
1.0
|
The appeals process doesn't actually describe how an appeal finishes - Section 7.2 ends by saying "If, within one week of the Team's announcement, 5% or more of the Advisory Committee support the appeal request, the Team must organize an appeal vote asking the Advisory Committee to approve or reject the decision."
What happens next? We get a formal vote to overturn the decision. But is there any requirement on how long the vote is open? What is the threshold (simple majority?)? What exactly is the question? (I.e. is it "Should the Chocolate IG be formed?" or "Should the Director's Decision to form the Chocolate IG be overturned"?). If the AC votes contrary to the Director, is the decision automatically overturned, or is it sent back to the Director to think harder?
We've not been down this road and hope we never will, but even so, this degree of uncertainty might be worrying.
|
process
|
the appeals process doesn t actually describe how an appeal finishes section ends by saying if within one week of the team s announcement or more of the advisory committee support the appeal request the team must organize an appeal vote asking the advisory committee to approve or reject the decision what happens next we get a formal vote to overturn the decision but is there any requirement on how long the vote is open what is the threshold simple majority what exactly is the question i e is it should the chocolate ig be formed or should the director s decision to form the chocolate ig be overturned if the ac votes contrary to the director is the decision automatically overturned or is it sent back to the director to think harder we ve not been down this road and hope we never will but even so this degree of uncertainty might be worrying
| 1
|
17,720
| 23,625,311,230
|
IssuesEvent
|
2022-08-25 02:51:33
|
MPMG-DCC-UFMG/C01
|
https://api.github.com/repos/MPMG-DCC-UFMG/C01
|
closed
|
Campo para XPath não aparece no passo "Executar em iframe"
|
[1] Bug [2] Alta Prioridade [0] Desenvolvimento [3] Processamento Dinâmico
|
## Comportamento Esperado
Ao utilizar o passo "Executar em iframe" em coletas dinâmicas, ser possível especificar o XPath referente ao iframe em que os processos devem ser executados.
## Comportamento Atual
Ao selecionar o tipo de passo como "Executar em iframe", não aparece um campo para que o XPath do iframe possa ser especificado, inviabilizando o uso dessa ação.
## Passos para reproduzir o erro
1. Criar um novo coletor
2. Marcar a opção de Processamento dinâmico
3. Adicionar passo Executar em iframe
4. Observar que não aparece um campo para especificação do XPath
## Screenshots
Como a ação de "Executar em iframe" aparece na visualização de passos no Processamento dinâmico:
|
1.0
|
Campo para XPath não aparece no passo "Executar em iframe" - ## Comportamento Esperado
Ao utilizar o passo "Executar em iframe" em coletas dinâmicas, ser possível especificar o XPath referente ao iframe em que os processos devem ser executados.
## Comportamento Atual
Ao selecionar o tipo de passo como "Executar em iframe", não aparece um campo para que o XPath do iframe possa ser especificado, inviabilizando o uso dessa ação.
## Passos para reproduzir o erro
1. Criar um novo coletor
2. Marcar a opção de Processamento dinâmico
3. Adicionar passo Executar em iframe
4. Observar que não aparece um campo para especificação do XPath
## Screenshots
Como a ação de "Executar em iframe" aparece na visualização de passos no Processamento dinâmico:
|
process
|
campo para xpath não aparece no passo executar em iframe comportamento esperado ao utilizar o passo executar em iframe em coletas dinâmicas ser possível especificar o xpath referente ao iframe em que os processos devem ser executados comportamento atual ao selecionar o tipo de passo como executar em iframe não aparece um campo para que o xpath do iframe possa ser especificado inviabilizando o uso dessa ação passos para reproduzir o erro criar um novo coletor marcar a opção de processamento dinâmico adicionar passo executar em iframe observar que não aparece um campo para especificação do xpath screenshots como a ação de executar em iframe aparece na visualização de passos no processamento dinâmico
| 1
|
1,698
| 4,346,536,456
|
IssuesEvent
|
2016-07-29 16:18:00
|
opentrials/opentrials
|
https://api.github.com/repos/opentrials/opentrials
|
closed
|
Add contributed data to our database
|
3. In Development Processors
|
# Goal
We had a contribution of ~100 CSRs and some other documents. We need to get them all, upload individually to our S3 instance, and create the related entry in the `documents` table in the API database.
We should also document this process, as we'll be doing it more in the future.
This is blocked on #254
# Analysis
This documents are stored on s3 with link in `exporerdb`. Documents are in zip format. The process could be fully automated but the processor should includes specific to this contribution data like filename mapping etc. Initial implementation could be partially ad-hoc because we need to upload this documents ASAP.
# Development
- [x] create new `contrib_johnson` processor
- [x] add `explorerdb` credentials to env vars and `config.py`
- [x] add s3 credential to env vars and `config.py`
- [x] in code download archive and extract it
- [x] in code write files metadata to `database.documents` table
- [x] create mapping between filenames in zip archive and metadata for `documents` table
- [x] in code upload files from zip to s3
- [ ] upload J&J documents
Estimated time: 2d
|
1.0
|
Add contributed data to our database - # Goal
We had a contribution of ~100 CSRs and some other documents. We need to get them all, upload individually to our S3 instance, and create the related entry in the `documents` table in the API database.
We should also document this process, as we'll be doing it more in the future.
This is blocked on #254
# Analysis
This documents are stored on s3 with link in `exporerdb`. Documents are in zip format. The process could be fully automated but the processor should includes specific to this contribution data like filename mapping etc. Initial implementation could be partially ad-hoc because we need to upload this documents ASAP.
# Development
- [x] create new `contrib_johnson` processor
- [x] add `explorerdb` credentials to env vars and `config.py`
- [x] add s3 credential to env vars and `config.py`
- [x] in code download archive and extract it
- [x] in code write files metadata to `database.documents` table
- [x] create mapping between filenames in zip archive and metadata for `documents` table
- [x] in code upload files from zip to s3
- [ ] upload J&J documents
Estimated time: 2d
|
process
|
add contributed data to our database goal we had a contribution of csrs and some other documents we need to get them all upload individually to our instance and create the related entry in the documents table in the api database we should also document this process as we ll be doing it more in the future this is blocked on analysis this documents are stored on with link in exporerdb documents are in zip format the process could be fully automated but the processor should includes specific to this contribution data like filename mapping etc initial implementation could be partially ad hoc because we need to upload this documents asap development create new contrib johnson processor add explorerdb credentials to env vars and config py add credential to env vars and config py in code download archive and extract it in code write files metadata to database documents table create mapping between filenames in zip archive and metadata for documents table in code upload files from zip to upload j j documents estimated time
| 1
|
14,014
| 16,816,655,418
|
IssuesEvent
|
2021-06-17 08:12:24
|
GoogleCloudPlatform/fda-mystudies
|
https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies
|
closed
|
[PM] Responsive issue in Participant details page
|
Bug P2 Participant manager Process: Fixed Process: Tested QA Process: Tested dev
|
Responsive issue in Participant details page
1. Text is wrapping up with the margins
2. UI issue in table
3. Closed study > participant details page > UI issues
|
3.0
|
[PM] Responsive issue in Participant details page - Responsive issue in Participant details page
1. Text is wrapping up with the margins
2. UI issue in table
3. Closed study > participant details page > UI issues
|
process
|
responsive issue in participant details page responsive issue in participant details page text is wrapping up with the margins ui issue in table closed study participant details page ui issues
| 1
|
56,032
| 8,042,137,307
|
IssuesEvent
|
2018-07-31 07:03:01
|
python-cmd2/cmd2
|
https://api.github.com/repos/python-cmd2/cmd2
|
closed
|
ReadTheDocs build of Sphinx docs is broken
|
bug documentation
|
The recent switch to using ``setuptools_scm`` for version number completely broke the ReadTheDocs build of our Sphinx documentation.
Error log is below:
```sh
python /home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/bin/sphinx-build -T -E -b readthedocs -d _build/doctrees-readthedocs -D language=en . _build/html
Running Sphinx v1.7.6
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/config.py", line 161, in __init__
execfile_(filename, config)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/util/pycompat.py", line 150, in execfile_
exec_(code, _globals)
File "conf.py", line 64, in <module>
version = get_distribution('cmd2').version
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 468, in get_distribution
dist = get_provider(dist)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 344, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 888, in require
needed = self.resolve(parse_requirements(requirements))
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 774, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'cmd2' distribution was not found and is required by the application
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/cmdline.py", line 303, in main
args.warningiserror, args.tags, args.verbosity, args.jobs)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/application.py", line 163, in __init__
confoverrides or {}, self.tags)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/config.py", line 167, in __init__
raise ConfigError(CONFIG_ERROR % traceback.format_exc())
sphinx.errors.ConfigError: There is a programable error in your configuration file:
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/config.py", line 161, in __init__
execfile_(filename, config)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/util/pycompat.py", line 150, in execfile_
exec_(code, _globals)
File "conf.py", line 64, in <module>
version = get_distribution('cmd2').version
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 468, in get_distribution
dist = get_provider(dist)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 344, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 888, in require
needed = self.resolve(parse_requirements(requirements))
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 774, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'cmd2' distribution was not found and is required by the application
Configuration error:
There is a programable error in your configuration file:
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/config.py", line 161, in __init__
execfile_(filename, config)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/util/pycompat.py", line 150, in execfile_
exec_(code, _globals)
File "conf.py", line 64, in <module>
version = get_distribution('cmd2').version
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 468, in get_distribution
dist = get_provider(dist)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 344, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 888, in require
needed = self.resolve(parse_requirements(requirements))
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 774, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'cmd2' distribution was not found and is required by the application
```
This is another indicator which suggests we would really benefit from a unit test which validates the build of the Sphinx HTML documentation.
|
1.0
|
ReadTheDocs build of Sphinx docs is broken - The recent switch to using ``setuptools_scm`` for version number completely broke the ReadTheDocs build of our Sphinx documentation.
Error log is below:
```sh
python /home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/bin/sphinx-build -T -E -b readthedocs -d _build/doctrees-readthedocs -D language=en . _build/html
Running Sphinx v1.7.6
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/config.py", line 161, in __init__
execfile_(filename, config)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/util/pycompat.py", line 150, in execfile_
exec_(code, _globals)
File "conf.py", line 64, in <module>
version = get_distribution('cmd2').version
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 468, in get_distribution
dist = get_provider(dist)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 344, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 888, in require
needed = self.resolve(parse_requirements(requirements))
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 774, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'cmd2' distribution was not found and is required by the application
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/cmdline.py", line 303, in main
args.warningiserror, args.tags, args.verbosity, args.jobs)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/application.py", line 163, in __init__
confoverrides or {}, self.tags)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/config.py", line 167, in __init__
raise ConfigError(CONFIG_ERROR % traceback.format_exc())
sphinx.errors.ConfigError: There is a programable error in your configuration file:
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/config.py", line 161, in __init__
execfile_(filename, config)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/util/pycompat.py", line 150, in execfile_
exec_(code, _globals)
File "conf.py", line 64, in <module>
version = get_distribution('cmd2').version
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 468, in get_distribution
dist = get_provider(dist)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 344, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 888, in require
needed = self.resolve(parse_requirements(requirements))
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 774, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'cmd2' distribution was not found and is required by the application
Configuration error:
There is a programable error in your configuration file:
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/config.py", line 161, in __init__
execfile_(filename, config)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/sphinx/util/pycompat.py", line 150, in execfile_
exec_(code, _globals)
File "conf.py", line 64, in <module>
version = get_distribution('cmd2').version
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 468, in get_distribution
dist = get_provider(dist)
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 344, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 888, in require
needed = self.resolve(parse_requirements(requirements))
File "/home/docs/checkouts/readthedocs.org/user_builds/cmd2/envs/latest/lib/python3.5/site-packages/pkg_resources/__init__.py", line 774, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'cmd2' distribution was not found and is required by the application
```
This is another indicator which suggests we would really benefit from a unit test which validates the build of the Sphinx HTML documentation.
|
non_process
|
readthedocs build of sphinx docs is broken the recent switch to using setuptools scm for version number completely broke the readthedocs build of our sphinx documentation error log is below sh python home docs checkouts readthedocs org user builds envs latest bin sphinx build t e b readthedocs d build doctrees readthedocs d language en build html running sphinx traceback most recent call last file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx config py line in init execfile filename config file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx util pycompat py line in execfile exec code globals file conf py line in version get distribution version file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in get distribution dist get provider dist file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in get provider return working set find moduleorreq or require str moduleorreq file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in require needed self resolve parse requirements requirements file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in resolve raise distributionnotfound req requirers pkg resources distributionnotfound the distribution was not found and is required by the application during handling of the above exception another exception occurred traceback most recent call last file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx cmdline py line in main args warningiserror args tags args verbosity args jobs file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx application py line in init confoverrides or self tags file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx config py line in init raise configerror config error traceback format exc sphinx errors configerror there is a programable error in your configuration file traceback most recent call last file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx config py line in init execfile filename config file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx util pycompat py line in execfile exec code globals file conf py line in version get distribution version file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in get distribution dist get provider dist file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in get provider return working set find moduleorreq or require str moduleorreq file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in require needed self resolve parse requirements requirements file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in resolve raise distributionnotfound req requirers pkg resources distributionnotfound the distribution was not found and is required by the application configuration error there is a programable error in your configuration file traceback most recent call last file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx config py line in init execfile filename config file home docs checkouts readthedocs org user builds envs latest lib site packages sphinx util pycompat py line in execfile exec code globals file conf py line in version get distribution version file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in get distribution dist get provider dist file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in get provider return working set find moduleorreq or require str moduleorreq file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in require needed self resolve parse requirements requirements file home docs checkouts readthedocs org user builds envs latest lib site packages pkg resources init py line in resolve raise distributionnotfound req requirers pkg resources distributionnotfound the distribution was not found and is required by the application this is another indicator which suggests we would really benefit from a unit test which validates the build of the sphinx html documentation
| 0
|
3,042
| 6,040,268,837
|
IssuesEvent
|
2017-06-10 12:43:14
|
rubberduck-vba/Rubberduck
|
https://api.github.com/repos/rubberduck-vba/Rubberduck
|
opened
|
COM module function returning HRESULT (eg. VBA function CDec) requires special handling in COM collector
|
feature-request parse-tree-processing
|
`CDec` is defined as:
```text
[helpcontext(0x0010645a)]
HRESULT _stdcall CDec(
[in] VARIANT* Expression,
[out, retval] VARIANT* pvar
);
```
Rubberduck currently reads the declaration as having 2 parameters, `Expression` and `pvar`, but VBA only exposes `Function CDec(Expression)`.
That is, `CDec` returns an HRESULT and has an `out` parameter, so it *looks* like a property definition on a COM interface, but the `Conversion` module isn't an interface.
Rubberduck needs to special case the `CDec` function, and probably any other function in a COM module that returns an HRESULT (I haven't looked outside the VBA library so far).
|
1.0
|
COM module function returning HRESULT (eg. VBA function CDec) requires special handling in COM collector - `CDec` is defined as:
```text
[helpcontext(0x0010645a)]
HRESULT _stdcall CDec(
[in] VARIANT* Expression,
[out, retval] VARIANT* pvar
);
```
Rubberduck currently reads the declaration as having 2 parameters, `Expression` and `pvar`, but VBA only exposes `Function CDec(Expression)`.
That is, `CDec` returns an HRESULT and has an `out` parameter, so it *looks* like a property definition on a COM interface, but the `Conversion` module isn't an interface.
Rubberduck needs to special case the `CDec` function, and probably any other function in a COM module that returns an HRESULT (I haven't looked outside the VBA library so far).
|
process
|
com module function returning hresult eg vba function cdec requires special handling in com collector cdec is defined as text hresult stdcall cdec variant expression variant pvar rubberduck currently reads the declaration as having parameters expression and pvar but vba only exposes function cdec expression that is cdec returns an hresult and has an out parameter so it looks like a property definition on a com interface but the conversion module isn t an interface rubberduck needs to special case the cdec function and probably any other function in a com module that returns an hresult i haven t looked outside the vba library so far
| 1
|
276,435
| 8,598,460,927
|
IssuesEvent
|
2018-11-15 21:51:57
|
mlr-org/mlr3featsel
|
https://api.github.com/repos/mlr-org/mlr3featsel
|
opened
|
Structure of this pkg
|
Priority: Critical Status: In Progress Type: Enhancement
|
Should/could follow _mlr3tuning_ [structure](https://github.com/mlr-org/mlr3tuning/blob/master/R/Tuner.R).
- Two base classes (`Filter` and `Featsel`) or one class with respective functions?
Arguments:
- `id`
- `settings` (at least for `Filter`)
- `result` -> returns the full `Filter Values` (needed for eventual caching) and the subsetted task in case of `Featsel`
- [...] more?
For filters a subclass per pkg that inherits from the main class?
How should we do the structuring for featsel methods?
@ja-thomas
|
1.0
|
Structure of this pkg - Should/could follow _mlr3tuning_ [structure](https://github.com/mlr-org/mlr3tuning/blob/master/R/Tuner.R).
- Two base classes (`Filter` and `Featsel`) or one class with respective functions?
Arguments:
- `id`
- `settings` (at least for `Filter`)
- `result` -> returns the full `Filter Values` (needed for eventual caching) and the subsetted task in case of `Featsel`
- [...] more?
For filters a subclass per pkg that inherits from the main class?
How should we do the structuring for featsel methods?
@ja-thomas
|
non_process
|
structure of this pkg should could follow two base classes filter and featsel or one class with respective functions arguments id settings at least for filter result returns the full filter values needed for eventual caching and the subsetted task in case of featsel more for filters a subclass per pkg that inherits from the main class how should we do the structuring for featsel methods ja thomas
| 0
|
19,118
| 13,187,873,389
|
IssuesEvent
|
2020-08-13 04:53:08
|
icecube-trac/tix3
|
https://api.github.com/repos/icecube-trac/tix3
|
closed
|
[steamshovel] [buildbots] Generate nightly/weekly .dmgs for steamshovel (Trac #1449)
|
Migrated from Trac infrastructure task
|
It turns out that more than a few people really want to use the Steamshovel app on their Macs (four already just in Delaware). The app is heavy (300 MB), but comes with all non-standard libs included so that it runs on a virgin system without further set-up.
I fixed and generalized the app generator script. It works on Yosemite now, and should also work on Maverick (needs to be tested). Since we have buildbots with these systems running, I think it would be great to use them to generate steamshovel apps on a nightly/weekly basis, and offer those for download. The script takes 10 to 20 seconds, so it is also acceptable to run it on every commit (if that's easier to implement).
The command "make mac-steamshovel-dmg" generates the steamshovel app and compresses it into a .dmg file, ready for installation by users.
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/ticket/1449">https://code.icecube.wisc.edu/ticket/1449</a>, reported by hdembinski and owned by nega</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-09-18T05:20:19",
"description": "It turns out that more than a few people really want to use the Steamshovel app on their Macs (four already just in Delaware). The app is heavy (300 MB), but comes with all non-standard libs included so that it runs on a virgin system without further set-up.\n\nI fixed and generalized the app generator script. It works on Yosemite now, and should also work on Maverick (needs to be tested). Since we have buildbots with these systems running, I think it would be great to use them to generate steamshovel apps on a nightly/weekly basis, and offer those for download. The script takes 10 to 20 seconds, so it is also acceptable to run it on every commit (if that's easier to implement).\n\nThe command \"make mac-steamshovel-dmg\" generates the steamshovel app and compresses it into a .dmg file, ready for installation by users.",
"reporter": "hdembinski",
"cc": "david.schultz, olivas",
"resolution": "duplicate",
"_ts": "1568784019550436",
"component": "infrastructure",
"summary": "[steamshovel] [buildbots] Generate nightly/weekly .dmgs for steamshovel",
"priority": "critical",
"keywords": "dmg steamshovel buildbot",
"time": "2015-11-25T16:25:04",
"milestone": "Long-Term Future",
"owner": "nega",
"type": "task"
}
```
</p>
</details>
|
1.0
|
[steamshovel] [buildbots] Generate nightly/weekly .dmgs for steamshovel (Trac #1449) - It turns out that more than a few people really want to use the Steamshovel app on their Macs (four already just in Delaware). The app is heavy (300 MB), but comes with all non-standard libs included so that it runs on a virgin system without further set-up.
I fixed and generalized the app generator script. It works on Yosemite now, and should also work on Maverick (needs to be tested). Since we have buildbots with these systems running, I think it would be great to use them to generate steamshovel apps on a nightly/weekly basis, and offer those for download. The script takes 10 to 20 seconds, so it is also acceptable to run it on every commit (if that's easier to implement).
The command "make mac-steamshovel-dmg" generates the steamshovel app and compresses it into a .dmg file, ready for installation by users.
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/ticket/1449">https://code.icecube.wisc.edu/ticket/1449</a>, reported by hdembinski and owned by nega</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-09-18T05:20:19",
"description": "It turns out that more than a few people really want to use the Steamshovel app on their Macs (four already just in Delaware). The app is heavy (300 MB), but comes with all non-standard libs included so that it runs on a virgin system without further set-up.\n\nI fixed and generalized the app generator script. It works on Yosemite now, and should also work on Maverick (needs to be tested). Since we have buildbots with these systems running, I think it would be great to use them to generate steamshovel apps on a nightly/weekly basis, and offer those for download. The script takes 10 to 20 seconds, so it is also acceptable to run it on every commit (if that's easier to implement).\n\nThe command \"make mac-steamshovel-dmg\" generates the steamshovel app and compresses it into a .dmg file, ready for installation by users.",
"reporter": "hdembinski",
"cc": "david.schultz, olivas",
"resolution": "duplicate",
"_ts": "1568784019550436",
"component": "infrastructure",
"summary": "[steamshovel] [buildbots] Generate nightly/weekly .dmgs for steamshovel",
"priority": "critical",
"keywords": "dmg steamshovel buildbot",
"time": "2015-11-25T16:25:04",
"milestone": "Long-Term Future",
"owner": "nega",
"type": "task"
}
```
</p>
</details>
|
non_process
|
generate nightly weekly dmgs for steamshovel trac it turns out that more than a few people really want to use the steamshovel app on their macs four already just in delaware the app is heavy mb but comes with all non standard libs included so that it runs on a virgin system without further set up i fixed and generalized the app generator script it works on yosemite now and should also work on maverick needs to be tested since we have buildbots with these systems running i think it would be great to use them to generate steamshovel apps on a nightly weekly basis and offer those for download the script takes to seconds so it is also acceptable to run it on every commit if that s easier to implement the command make mac steamshovel dmg generates the steamshovel app and compresses it into a dmg file ready for installation by users migrated from json status closed changetime description it turns out that more than a few people really want to use the steamshovel app on their macs four already just in delaware the app is heavy mb but comes with all non standard libs included so that it runs on a virgin system without further set up n ni fixed and generalized the app generator script it works on yosemite now and should also work on maverick needs to be tested since we have buildbots with these systems running i think it would be great to use them to generate steamshovel apps on a nightly weekly basis and offer those for download the script takes to seconds so it is also acceptable to run it on every commit if that s easier to implement n nthe command make mac steamshovel dmg generates the steamshovel app and compresses it into a dmg file ready for installation by users reporter hdembinski cc david schultz olivas resolution duplicate ts component infrastructure summary generate nightly weekly dmgs for steamshovel priority critical keywords dmg steamshovel buildbot time milestone long term future owner nega type task
| 0
|
15,083
| 18,789,806,591
|
IssuesEvent
|
2021-11-08 15:42:22
|
microsoft/vscode
|
https://api.github.com/repos/microsoft/vscode
|
closed
|
Terminal process directory name issue
|
terminal-process
|
Issue Type: <b>Bug</b>
After Startup the message
The terminal process failed to launch: Starting directory (cwd) "/Users/.../Documents \xe2\x80\x93 Marathon/GitHub/quest" does not exist.
is displayed and the window "Terminal / Problems / Output / Debug Console" refuses to open. If openend afterwards via the "Vie / terminal" Menue it works just fine.
Expected result: Allowed special characters in directory names should be considered.
VS Code version: Code - Insiders 1.63.0-insider (552af97a0170b43c9323bec62211feb184da9749, 2021-11-05T05:15:13.016Z)
OS version: Darwin x64 21.1.0
Restricted Mode: No
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 (8 x 24)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (0.16GB free)|
|Process Argv|--crash-reporter-id 5f6666f9-5f97-492b-9526-a07831f6c466|
|Screen Reader|no|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>
```
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
pythonvspyt200:30323110
vsccppwt:30382699
bridge0708:30335490
pygetstartedt2:30353727
bridge0723:30353136
pythonrunftest32:30365365
pythonf5test824:30361779
javagetstartedt:30350119
pythonvspyt187:30365360
pydsgst2:30361790
vsaa593:30376534
vsc1dsc:30394499
```
</details>
<!-- generated by issue reporter -->
|
1.0
|
Terminal process directory name issue -
Issue Type: <b>Bug</b>
After Startup the message
The terminal process failed to launch: Starting directory (cwd) "/Users/.../Documents \xe2\x80\x93 Marathon/GitHub/quest" does not exist.
is displayed and the window "Terminal / Problems / Output / Debug Console" refuses to open. If openend afterwards via the "Vie / terminal" Menue it works just fine.
Expected result: Allowed special characters in directory names should be considered.
VS Code version: Code - Insiders 1.63.0-insider (552af97a0170b43c9323bec62211feb184da9749, 2021-11-05T05:15:13.016Z)
OS version: Darwin x64 21.1.0
Restricted Mode: No
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 (8 x 24)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (0.16GB free)|
|Process Argv|--crash-reporter-id 5f6666f9-5f97-492b-9526-a07831f6c466|
|Screen Reader|no|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>
```
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
pythonvspyt200:30323110
vsccppwt:30382699
bridge0708:30335490
pygetstartedt2:30353727
bridge0723:30353136
pythonrunftest32:30365365
pythonf5test824:30361779
javagetstartedt:30350119
pythonvspyt187:30365360
pydsgst2:30361790
vsaa593:30376534
vsc1dsc:30394499
```
</details>
<!-- generated by issue reporter -->
|
process
|
terminal process directory name issue issue type bug after startup the message the terminal process failed to launch starting directory cwd users documents marathon github quest does not exist is displayed and the window terminal problems output debug console refuses to open if openend afterwards via the vie terminal menue it works just fine expected result allowed special characters in directory names should be considered vs code version code insiders insider os version darwin restricted mode no system info item value cpus apple x gpu status canvas enabled gpu compositing enabled metal disabled off multiple raster threads enabled on oop rasterization enabled opengl enabled on rasterization enabled skia renderer disabled off ok video decode enabled webgl enabled enabled load avg memory system free process argv crash reporter id screen reader no vm a b experiments pythontb pythonptprofiler pythondataviewer vsccppwt javagetstartedt
| 1
|
322,871
| 23,926,435,305
|
IssuesEvent
|
2022-09-09 23:48:23
|
thegetty/quire-docs
|
https://api.github.com/repos/thegetty/quire-docs
|
closed
|
V1 Docs: Pages Types & Structure
|
documentation 11ty
|
### Before proceeding, check to make sure there isn’t an existing issue for your suggestion or a similar one.
- [X] I have searched the existing issues and determined this is new suggestion.
### Idea being proposed
- [x] Change `weight` to `order`
- [x] Change `type` to `layout`
- [x] Update the example yaml blocks
- [x] Update text in captions
- [x] Confirm the list of page layouts is staying the same (is `data` still available?)
- [x] Confirm if we still use `class` in addition to `layout` (including `class: page-one`- see note below)
- [x] Confirm if we still use `slug:.` to create section landing pages (I don't believe we use this anymore - this will need to be updated.)
- [x] Update new `online: false` instructions in "Hide/Show" section (See note below.)
### What contribution category does your proposal fall under?
Copyedit text
### Supporting Information
For online false (see jira ticket [DEV-12163](https://jira.getty.edu/browse/DEV-12163) ) - Proposed solution is to add a outputs key to frontmatter with a default value of [pdf, epub, html]. To exclude a format you would omit the format from the array in the page frontmatter: outputs: [pdf, epub]
For `class: page-one` I believe this stays the same per jira ticket [DEV-12755](https://jira.getty.edu/browse/DEV-12755)
|
1.0
|
V1 Docs: Pages Types & Structure - ### Before proceeding, check to make sure there isn’t an existing issue for your suggestion or a similar one.
- [X] I have searched the existing issues and determined this is new suggestion.
### Idea being proposed
- [x] Change `weight` to `order`
- [x] Change `type` to `layout`
- [x] Update the example yaml blocks
- [x] Update text in captions
- [x] Confirm the list of page layouts is staying the same (is `data` still available?)
- [x] Confirm if we still use `class` in addition to `layout` (including `class: page-one`- see note below)
- [x] Confirm if we still use `slug:.` to create section landing pages (I don't believe we use this anymore - this will need to be updated.)
- [x] Update new `online: false` instructions in "Hide/Show" section (See note below.)
### What contribution category does your proposal fall under?
Copyedit text
### Supporting Information
For online false (see jira ticket [DEV-12163](https://jira.getty.edu/browse/DEV-12163) ) - Proposed solution is to add a outputs key to frontmatter with a default value of [pdf, epub, html]. To exclude a format you would omit the format from the array in the page frontmatter: outputs: [pdf, epub]
For `class: page-one` I believe this stays the same per jira ticket [DEV-12755](https://jira.getty.edu/browse/DEV-12755)
|
non_process
|
docs pages types structure before proceeding check to make sure there isn’t an existing issue for your suggestion or a similar one i have searched the existing issues and determined this is new suggestion idea being proposed change weight to order change type to layout update the example yaml blocks update text in captions confirm the list of page layouts is staying the same is data still available confirm if we still use class in addition to layout including class page one see note below confirm if we still use slug to create section landing pages i don t believe we use this anymore this will need to be updated update new online false instructions in hide show section see note below what contribution category does your proposal fall under copyedit text supporting information for online false see jira ticket proposed solution is to add a outputs key to frontmatter with a default value of to exclude a format you would omit the format from the array in the page frontmatter outputs for class page one i believe this stays the same per jira ticket
| 0
|
299,347
| 9,205,387,883
|
IssuesEvent
|
2019-03-08 10:25:47
|
qissue-bot/QGIS
|
https://api.github.com/repos/qissue-bot/QGIS
|
closed
|
Qgis crash associated with vector actions
|
Category: Vectors Component: Affected QGIS version Component: Crashes QGIS or corrupts data Component: Easy fix? Component: Operating System Component: Pull Request or Patch supplied Component: Regression? Component: Resolution Priority: Low Project: QGIS Application Status: Closed Tracker: Bug report
|
---
Author Name: **cgs_bob -** (cgs_bob -)
Original Redmine Issue: 744, https://issues.qgis.org/issues/744
Original Assignee: Gavin Macaulay -
---
I have been able to consistently crash qgis by doing this:
1) Start qgis and load project that has vectors with actions.
2) Click on vector in the legend and then click on Identify Feature.
3) In the Identify Results window, click on an action.
(my action opens up a window that says "starting konqueror ftp://..." and then konqueror brings up the ftp site)
4) Click on the Close button in the window that says "starting konqueror" will crash qgis.
I have attached the debug messages I got on my Konsole.
---
- [qgis_actions_crash.txt](https://issues.qgis.org/attachments/download/1923/qgis_actions_crash.txt) (cgs_bob -)
|
1.0
|
Qgis crash associated with vector actions - ---
Author Name: **cgs_bob -** (cgs_bob -)
Original Redmine Issue: 744, https://issues.qgis.org/issues/744
Original Assignee: Gavin Macaulay -
---
I have been able to consistently crash qgis by doing this:
1) Start qgis and load project that has vectors with actions.
2) Click on vector in the legend and then click on Identify Feature.
3) In the Identify Results window, click on an action.
(my action opens up a window that says "starting konqueror ftp://..." and then konqueror brings up the ftp site)
4) Click on the Close button in the window that says "starting konqueror" will crash qgis.
I have attached the debug messages I got on my Konsole.
---
- [qgis_actions_crash.txt](https://issues.qgis.org/attachments/download/1923/qgis_actions_crash.txt) (cgs_bob -)
|
non_process
|
qgis crash associated with vector actions author name cgs bob cgs bob original redmine issue original assignee gavin macaulay i have been able to consistently crash qgis by doing this start qgis and load project that has vectors with actions click on vector in the legend and then click on identify feature in the identify results window click on an action my action opens up a window that says starting konqueror ftp and then konqueror brings up the ftp site click on the close button in the window that says starting konqueror will crash qgis i have attached the debug messages i got on my konsole cgs bob
| 0
|
2,291
| 5,112,678,175
|
IssuesEvent
|
2017-01-06 12:19:12
|
sysown/proxysql
|
https://api.github.com/repos/sysown/proxysql
|
opened
|
Log slow queries
|
ADMIN QUERY PROCESSOR
|
An interesting feature request is to log slow queries in its own slow query log, in the same format as mysql slow query log.
|
1.0
|
Log slow queries - An interesting feature request is to log slow queries in its own slow query log, in the same format as mysql slow query log.
|
process
|
log slow queries an interesting feature request is to log slow queries in its own slow query log in the same format as mysql slow query log
| 1
|
13,017
| 15,372,000,907
|
IssuesEvent
|
2021-03-02 10:42:03
|
tokio-rs/tokio
|
https://api.github.com/repos/tokio-rs/tokio
|
closed
|
Command.spawn (with piped stdio) actually spawns two processes
|
A-tokio C-bug M-process
|
**Version**
```
$ cargo tree | grep tokio
tokio_test v0.1.0 (/home/tim/dev/rust/tokio_test)
└── tokio v1.2.0
└── tokio-macros v1.1.0
```
**Platform**
* Linux 5.10.16-100.fc32.x86_64 x86_64 GNU/Linux
* Also tested with same results on OSX
**Description**
This is pretty odd, so I don't know whether it's specific to how I'm handling stdin/out/err. This test code could probably just use command.output(), but the real code is fancier and needs to handle streams itself.
I've put the code in [a gist](https://gist.github.com/timbertson/7bf51f98765cc50824b3c113b1909966), it's just spawning a command, then in parallel:
- writing stdin
- collecting stdout
- collecting stderr
The critical part is:
```rust
#[tokio::main]
async fn main() {
let stdin = "HELLO\n";
let mut command = Command::new("/bin/bash");
command.arg("-euc").arg("/bin/touch pids/$$; read f; echo $f");
command.stdout(Stdio::piped());
command.stderr(Stdio::piped());
command.stdin(Stdio::piped());
println!("Spawning ...");
let mut child = command.spawn().unwrap();
let stdin_pipe = child.stdin.as_mut().expect("stdin is not a pipe");
let mut stdout_pipe = child.stdout.take().expect("stdout is not a pipe");
let mut stderr_pipe = child.stderr.take().expect("stderr is not a pipe");
let (wrote_stdin, stdout, stderr) = join!(
(|| async {
let result = stdin_pipe.write(stdin.as_bytes()).await;
drop(stdin_pipe);
result
})(),
read_io(&mut stdout_pipe),
read_io(&mut stderr_pipe),
);
let status = command.status().await.unwrap();
println!("Command exited, stdin = {:?}, stdout = {:?}, stderr = {:?}", wrote_stdin, stdout, stderr);
println!("Status: code={:?} ({:?})", status.code(), status);
}
```
When I run it, the output looks OK but the command fails, with exit status 1. That's surprising...
```
$ ./target/debug/cmd_test
Spawning ...
read pipe -> "HELLO\n"
read pipe -> ""
Command exited, stdin = Ok(6), stdout = Ok("HELLO\n"), stderr = Ok("")
Status: code=Some(1) (ExitStatus(ExitStatus(256)))
```
and it looks like the bash command actually ran _twice_:
```
$ ls pids
93092 93094
```
Running under `strace`, I can see that there genuinely seem to be two `execve`'d processes. The first one exits successfully, but the second fails. It seems like the pipes are connected to the input/output of the first process, but the status is determined by the second.
```
$ strace -f -eexecve,exit_group --silence=exit,attach ./target/debug/cmd_test
execve("./target/debug/cmd_test", ["./target/debug/cmd_test"], 0x7fffcd60d3b8 /* 132 vars */) = 0
Spawning ...
[pid 94502] execve("/bin/bash", ["/bin/bash", "-euc", "/bin/touch pids/$$; read f; echo"...], 0x7ffc04c27c68 /* 132 vars */) = 0
[pid 94503] execve("/bin/touch", ["/bin/touch", "pids/94502"], 0x55653df81220 /* 133 vars */) = 0
[pid 94503] exit_group(0) = ?
[pid 94502] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=94503, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
[pid 94502] exit_group(0) = ?
[pid 94494] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=94502, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
read pipe -> ""
read pipe -> "HELLO\n"
[pid 94504] execve("/bin/bash", ["/bin/bash", "-euc", "/bin/touch pids/$$; read f; echo"...], 0x7ffc04c27c68 /* 132 vars */) = 0
[pid 94505] execve("/bin/touch", ["/bin/touch", "pids/94504"], 0x555955a03220 /* 133 vars */) = 0
[pid 94505] exit_group(0) = ?
[pid 94504] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=94505, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
[pid 94504] exit_group(1) = ?
[pid 94493] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=94504, si_uid=1000, si_status=1, si_utime=0, si_stime=0} ---
Command exited, stdin = Ok(6), stdout = Ok("HELLO\n"), stderr = Ok("")
Status: code=Some(1) (ExitStatus(ExitStatus(256)))
exit_group(0) = ?
```
If I show all syscalls, I can see that the second fails unsurprisingly because it's trying to do various things on a closed `stdin` (this is a different run so the pids differ):
```
[pid 94777] ioctl(0, TCGETS, 0x7ffd49a19530) = -1 ENOTTY (Inappropriate ioctl for device)
[pid 94777] lseek(0, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
[pid 94777] read(0, "", 1) = 0
```
|
1.0
|
Command.spawn (with piped stdio) actually spawns two processes - **Version**
```
$ cargo tree | grep tokio
tokio_test v0.1.0 (/home/tim/dev/rust/tokio_test)
└── tokio v1.2.0
└── tokio-macros v1.1.0
```
**Platform**
* Linux 5.10.16-100.fc32.x86_64 x86_64 GNU/Linux
* Also tested with same results on OSX
**Description**
This is pretty odd, so I don't know whether it's specific to how I'm handling stdin/out/err. This test code could probably just use command.output(), but the real code is fancier and needs to handle streams itself.
I've put the code in [a gist](https://gist.github.com/timbertson/7bf51f98765cc50824b3c113b1909966), it's just spawning a command, then in parallel:
- writing stdin
- collecting stdout
- collecting stderr
The critical part is:
```rust
#[tokio::main]
async fn main() {
let stdin = "HELLO\n";
let mut command = Command::new("/bin/bash");
command.arg("-euc").arg("/bin/touch pids/$$; read f; echo $f");
command.stdout(Stdio::piped());
command.stderr(Stdio::piped());
command.stdin(Stdio::piped());
println!("Spawning ...");
let mut child = command.spawn().unwrap();
let stdin_pipe = child.stdin.as_mut().expect("stdin is not a pipe");
let mut stdout_pipe = child.stdout.take().expect("stdout is not a pipe");
let mut stderr_pipe = child.stderr.take().expect("stderr is not a pipe");
let (wrote_stdin, stdout, stderr) = join!(
(|| async {
let result = stdin_pipe.write(stdin.as_bytes()).await;
drop(stdin_pipe);
result
})(),
read_io(&mut stdout_pipe),
read_io(&mut stderr_pipe),
);
let status = command.status().await.unwrap();
println!("Command exited, stdin = {:?}, stdout = {:?}, stderr = {:?}", wrote_stdin, stdout, stderr);
println!("Status: code={:?} ({:?})", status.code(), status);
}
```
When I run it, the output looks OK but the command fails, with exit status 1. That's surprising...
```
$ ./target/debug/cmd_test
Spawning ...
read pipe -> "HELLO\n"
read pipe -> ""
Command exited, stdin = Ok(6), stdout = Ok("HELLO\n"), stderr = Ok("")
Status: code=Some(1) (ExitStatus(ExitStatus(256)))
```
and it looks like the bash command actually ran _twice_:
```
$ ls pids
93092 93094
```
Running under `strace`, I can see that there genuinely seem to be two `execve`'d processes. The first one exits successfully, but the second fails. It seems like the pipes are connected to the input/output of the first process, but the status is determined by the second.
```
$ strace -f -eexecve,exit_group --silence=exit,attach ./target/debug/cmd_test
execve("./target/debug/cmd_test", ["./target/debug/cmd_test"], 0x7fffcd60d3b8 /* 132 vars */) = 0
Spawning ...
[pid 94502] execve("/bin/bash", ["/bin/bash", "-euc", "/bin/touch pids/$$; read f; echo"...], 0x7ffc04c27c68 /* 132 vars */) = 0
[pid 94503] execve("/bin/touch", ["/bin/touch", "pids/94502"], 0x55653df81220 /* 133 vars */) = 0
[pid 94503] exit_group(0) = ?
[pid 94502] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=94503, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
[pid 94502] exit_group(0) = ?
[pid 94494] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=94502, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
read pipe -> ""
read pipe -> "HELLO\n"
[pid 94504] execve("/bin/bash", ["/bin/bash", "-euc", "/bin/touch pids/$$; read f; echo"...], 0x7ffc04c27c68 /* 132 vars */) = 0
[pid 94505] execve("/bin/touch", ["/bin/touch", "pids/94504"], 0x555955a03220 /* 133 vars */) = 0
[pid 94505] exit_group(0) = ?
[pid 94504] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=94505, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
[pid 94504] exit_group(1) = ?
[pid 94493] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=94504, si_uid=1000, si_status=1, si_utime=0, si_stime=0} ---
Command exited, stdin = Ok(6), stdout = Ok("HELLO\n"), stderr = Ok("")
Status: code=Some(1) (ExitStatus(ExitStatus(256)))
exit_group(0) = ?
```
If I show all syscalls, I can see that the second fails unsurprisingly because it's trying to do various things on a closed `stdin` (this is a different run so the pids differ):
```
[pid 94777] ioctl(0, TCGETS, 0x7ffd49a19530) = -1 ENOTTY (Inappropriate ioctl for device)
[pid 94777] lseek(0, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
[pid 94777] read(0, "", 1) = 0
```
|
process
|
command spawn with piped stdio actually spawns two processes version cargo tree grep tokio tokio test home tim dev rust tokio test └── tokio └── tokio macros platform linux gnu linux also tested with same results on osx description this is pretty odd so i don t know whether it s specific to how i m handling stdin out err this test code could probably just use command output but the real code is fancier and needs to handle streams itself i ve put the code in it s just spawning a command then in parallel writing stdin collecting stdout collecting stderr the critical part is rust async fn main let stdin hello n let mut command command new bin bash command arg euc arg bin touch pids read f echo f command stdout stdio piped command stderr stdio piped command stdin stdio piped println spawning let mut child command spawn unwrap let stdin pipe child stdin as mut expect stdin is not a pipe let mut stdout pipe child stdout take expect stdout is not a pipe let mut stderr pipe child stderr take expect stderr is not a pipe let wrote stdin stdout stderr join async let result stdin pipe write stdin as bytes await drop stdin pipe result read io mut stdout pipe read io mut stderr pipe let status command status await unwrap println command exited stdin stdout stderr wrote stdin stdout stderr println status code status code status when i run it the output looks ok but the command fails with exit status that s surprising target debug cmd test spawning read pipe hello n read pipe command exited stdin ok stdout ok hello n stderr ok status code some exitstatus exitstatus and it looks like the bash command actually ran twice ls pids running under strace i can see that there genuinely seem to be two execve d processes the first one exits successfully but the second fails it seems like the pipes are connected to the input output of the first process but the status is determined by the second strace f eexecve exit group silence exit attach target debug cmd test execve target debug cmd test vars spawning execve bin bash vars execve bin touch vars exit group sigchld si signo sigchld si code cld exited si pid si uid si status si utime si stime exit group sigchld si signo sigchld si code cld exited si pid si uid si status si utime si stime read pipe read pipe hello n execve bin bash vars execve bin touch vars exit group sigchld si signo sigchld si code cld exited si pid si uid si status si utime si stime exit group sigchld si signo sigchld si code cld exited si pid si uid si status si utime si stime command exited stdin ok stdout ok hello n stderr ok status code some exitstatus exitstatus exit group if i show all syscalls i can see that the second fails unsurprisingly because it s trying to do various things on a closed stdin this is a different run so the pids differ ioctl tcgets enotty inappropriate ioctl for device lseek seek cur espipe illegal seek read
| 1
|
444,276
| 31,030,559,713
|
IssuesEvent
|
2023-08-10 12:12:11
|
appsmithorg/appsmith-docs
|
https://api.github.com/repos/appsmithorg/appsmith-docs
|
opened
|
[Docs]: Configure OAuth How-To: Client Credentials
|
Documentation User Education Pod
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Documentation Link
_No response_
### Discord/slack/intercom Link
_No response_
### Describe the problem and improvement.
Create How-To Guide for connecting to a datasource using OAuth with Client Credentials method.
|
1.0
|
[Docs]: Configure OAuth How-To: Client Credentials - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Documentation Link
_No response_
### Discord/slack/intercom Link
_No response_
### Describe the problem and improvement.
Create How-To Guide for connecting to a datasource using OAuth with Client Credentials method.
|
non_process
|
configure oauth how to client credentials is there an existing issue for this i have searched the existing issues documentation link no response discord slack intercom link no response describe the problem and improvement create how to guide for connecting to a datasource using oauth with client credentials method
| 0
|
10,356
| 13,180,292,380
|
IssuesEvent
|
2020-08-12 12:33:17
|
prisma/language-tools
|
https://api.github.com/repos/prisma/language-tools
|
opened
|
Enum default autocompletion support
|
kind/improvement process/candidate
|
Autocompletion suggestions here should only show ADMIN, NORMAL
|
1.0
|
Enum default autocompletion support - 
Autocompletion suggestions here should only show ADMIN, NORMAL
|
process
|
enum default autocompletion support autocompletion suggestions here should only show admin normal
| 1
|
7,457
| 10,561,388,127
|
IssuesEvent
|
2019-10-04 15:45:57
|
ORNL-AMO/AMO-Tools-Suite
|
https://api.github.com/repos/ORNL-AMO/AMO-Tools-Suite
|
opened
|
Issue with PRV without desuperheating reported by user
|
Calculator Process Heating bug help wanted
|
User reports that the units for mass flow are not good.
Needs details for developers to fix it. Is it related to the reported bug in the suite #344
https://app.zenhub.com/workspaces/measur-5c9d18415648dd20c601ea26/issues/ornl-amo/amo-tools-suite/344
|
1.0
|
Issue with PRV without desuperheating reported by user - User reports that the units for mass flow are not good.
Needs details for developers to fix it. Is it related to the reported bug in the suite #344
https://app.zenhub.com/workspaces/measur-5c9d18415648dd20c601ea26/issues/ornl-amo/amo-tools-suite/344
|
process
|
issue with prv without desuperheating reported by user user reports that the units for mass flow are not good needs details for developers to fix it is it related to the reported bug in the suite
| 1
|
17,737
| 23,654,053,069
|
IssuesEvent
|
2022-08-26 09:29:01
|
prisma/prisma-engines
|
https://api.github.com/repos/prisma/prisma-engines
|
opened
|
[MongoDB] Missing compound composite unique schema validation
|
process/candidate team/schema topic: mongodb
|
## Overview
I think we're missing a validation on compound composite unique which prevents a compound from having two indexed arrays.
<img width="804" alt="image" src="https://user-images.githubusercontent.com/25233379/186873372-1cb73d5f-55ce-4653-958c-40cf9458fbf3.png">
If you want to read more about it, [here's the link](https://www.mongodb.com/docs/manual/core/index-multikey/#compound-multikey-indexes)
## Example
```prisma
model Test {
id Int @id @map("_id")
comp Composite
@@unique([comp.list_1, comp.list_2])
}
type Composite {
list_1 Int[]
list_2 Int[]
}
```
The example above should not work. I think it doesn't matter if the fields belong to the same composite. We just need to check that a unique compound contains at most one list field.
|
1.0
|
[MongoDB] Missing compound composite unique schema validation - ## Overview
I think we're missing a validation on compound composite unique which prevents a compound from having two indexed arrays.
<img width="804" alt="image" src="https://user-images.githubusercontent.com/25233379/186873372-1cb73d5f-55ce-4653-958c-40cf9458fbf3.png">
If you want to read more about it, [here's the link](https://www.mongodb.com/docs/manual/core/index-multikey/#compound-multikey-indexes)
## Example
```prisma
model Test {
id Int @id @map("_id")
comp Composite
@@unique([comp.list_1, comp.list_2])
}
type Composite {
list_1 Int[]
list_2 Int[]
}
```
The example above should not work. I think it doesn't matter if the fields belong to the same composite. We just need to check that a unique compound contains at most one list field.
|
process
|
missing compound composite unique schema validation overview i think we re missing a validation on compound composite unique which prevents a compound from having two indexed arrays img width alt image src if you want to read more about it example prisma model test id int id map id comp composite unique type composite list int list int the example above should not work i think it doesn t matter if the fields belong to the same composite we just need to check that a unique compound contains at most one list field
| 1
|
19,797
| 26,178,927,810
|
IssuesEvent
|
2023-01-02 13:16:10
|
NixOS/nix
|
https://api.github.com/repos/NixOS/nix
|
closed
|
Release 2.12
|
process
|
**Is your feature request related to a problem? Please describe.**
[I'm always frustrated when] fixes are merged but not released.
**Describe the solution you'd like**
Release Nix 2.12.0.
Apply and release backports.
**Describe alternatives you've considered**
Treat Nix master as a rolling release and cut releases in Nixpkgs instead.
**Additional context**
Releases were supposed to be 6-weekly, but 13 weeks have passed since 2.11.0.
|
1.0
|
Release 2.12 - **Is your feature request related to a problem? Please describe.**
[I'm always frustrated when] fixes are merged but not released.
**Describe the solution you'd like**
Release Nix 2.12.0.
Apply and release backports.
**Describe alternatives you've considered**
Treat Nix master as a rolling release and cut releases in Nixpkgs instead.
**Additional context**
Releases were supposed to be 6-weekly, but 13 weeks have passed since 2.11.0.
|
process
|
release is your feature request related to a problem please describe fixes are merged but not released describe the solution you d like release nix apply and release backports describe alternatives you ve considered treat nix master as a rolling release and cut releases in nixpkgs instead additional context releases were supposed to be weekly but weeks have passed since
| 1
|
517
| 2,993,129,929
|
IssuesEvent
|
2015-07-22 00:17:47
|
broadinstitute/hellbender
|
https://api.github.com/repos/broadinstitute/hellbender
|
opened
|
Make ReadsPreprocessingPipelineTestData more general (as a function of shard size)
|
Dataflow DataflowPreprocessingPipeline Engine
|
Right now, the effects of REFERENCE_SHARD_SIZE and VARIANT_SHARDSIZE are hard coded, this should change to be more general.
|
1.0
|
Make ReadsPreprocessingPipelineTestData more general (as a function of shard size) - Right now, the effects of REFERENCE_SHARD_SIZE and VARIANT_SHARDSIZE are hard coded, this should change to be more general.
|
process
|
make readspreprocessingpipelinetestdata more general as a function of shard size right now the effects of reference shard size and variant shardsize are hard coded this should change to be more general
| 1
|
77,956
| 22,053,147,689
|
IssuesEvent
|
2022-05-30 10:26:11
|
Automattic/wp-calypso
|
https://api.github.com/repos/Automattic/wp-calypso
|
closed
|
Generated design picker: Responsive thumbnail height
|
V13n Build Flow
|
## Description
Currently, thumbnails in the generated design picker have fixed height. We want to best make use of the vertical space in order to show as much of the design as possible, which is why we are interested in making the thumbnail height responsive to the viewport height. Note that this only applies to desktop resolution.
See Figma 42PgVsdlQ1v2wpk6lmmrnq-fi-1697%3A54129 for reference.
Example screenshots:
100px (min-height):
300px (max-height):
## Acceptance Criteria
* Make the thumbnails fit the remaining of the viewport height.
* As I resize the viewport, the height of the thumbnails should change accordingly to the updated viewport height.
* The "view more options" button height should remain fixed, and visible in the viewport.
## Dev tasks
* [x] Change the height of thumbnails to be responsive to viewport space
* [x] Responsive thumbnail height should have a minimum height of 100px.
* [x] Responsive thumbnail height should have a maximum height of 300px.
* [x] The "view more options" button should have 48px spacing under it.
|
1.0
|
Generated design picker: Responsive thumbnail height - ## Description
Currently, thumbnails in the generated design picker have fixed height. We want to best make use of the vertical space in order to show as much of the design as possible, which is why we are interested in making the thumbnail height responsive to the viewport height. Note that this only applies to desktop resolution.
See Figma 42PgVsdlQ1v2wpk6lmmrnq-fi-1697%3A54129 for reference.
Example screenshots:
100px (min-height):
300px (max-height):
## Acceptance Criteria
* Make the thumbnails fit the remaining of the viewport height.
* As I resize the viewport, the height of the thumbnails should change accordingly to the updated viewport height.
* The "view more options" button height should remain fixed, and visible in the viewport.
## Dev tasks
* [x] Change the height of thumbnails to be responsive to viewport space
* [x] Responsive thumbnail height should have a minimum height of 100px.
* [x] Responsive thumbnail height should have a maximum height of 300px.
* [x] The "view more options" button should have 48px spacing under it.
|
non_process
|
generated design picker responsive thumbnail height description currently thumbnails in the generated design picker have fixed height we want to best make use of the vertical space in order to show as much of the design as possible which is why we are interested in making the thumbnail height responsive to the viewport height note that this only applies to desktop resolution see figma fi for reference example screenshots min height max height acceptance criteria make the thumbnails fit the remaining of the viewport height as i resize the viewport the height of the thumbnails should change accordingly to the updated viewport height the view more options button height should remain fixed and visible in the viewport dev tasks change the height of thumbnails to be responsive to viewport space responsive thumbnail height should have a minimum height of responsive thumbnail height should have a maximum height of the view more options button should have spacing under it
| 0
|
18,732
| 24,626,193,234
|
IssuesEvent
|
2022-10-16 14:54:31
|
apache/arrow-ballista
|
https://api.github.com/repos/apache/arrow-ballista
|
opened
|
Write documentation on how to verify a release
|
enhancement development-process
|
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
When we hold a vote on releasing Ballista, we need voters to know how to verify a release. There is a simple script that will simply run `cargo test` and check signatures, but that isn't sufficient for a distributed platform such as Ballista.
**Describe the solution you'd like**
Write documentation on how to verify a release. This should at least involve spinning up a cluster using `docker-compose` and running one query.
We do have `./dev/integration-test.sh` which seems to be broken currently but we can probably fix that fairly easily.
**Describe alternatives you've considered**
None
**Additional context**
None
|
1.0
|
Write documentation on how to verify a release - **Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
When we hold a vote on releasing Ballista, we need voters to know how to verify a release. There is a simple script that will simply run `cargo test` and check signatures, but that isn't sufficient for a distributed platform such as Ballista.
**Describe the solution you'd like**
Write documentation on how to verify a release. This should at least involve spinning up a cluster using `docker-compose` and running one query.
We do have `./dev/integration-test.sh` which seems to be broken currently but we can probably fix that fairly easily.
**Describe alternatives you've considered**
None
**Additional context**
None
|
process
|
write documentation on how to verify a release is your feature request related to a problem or challenge please describe what you are trying to do when we hold a vote on releasing ballista we need voters to know how to verify a release there is a simple script that will simply run cargo test and check signatures but that isn t sufficient for a distributed platform such as ballista describe the solution you d like write documentation on how to verify a release this should at least involve spinning up a cluster using docker compose and running one query we do have dev integration test sh which seems to be broken currently but we can probably fix that fairly easily describe alternatives you ve considered none additional context none
| 1
|
205,130
| 15,964,598,850
|
IssuesEvent
|
2021-04-16 06:30:47
|
Andrewzhang217/pe
|
https://api.github.com/repos/Andrewzhang217/pe
|
opened
|
UG-instruction is confusing
|
severity.Low type.DocumentationBug
|
It is easy to make the user ignore the whitespace between addP and n/My Project, same in addT and deleteP.
I suggest make the whitespace clearer to users and reduce misunderstanding
<!--session: 1618552060415-53c0cdab-e582-44e3-b4f1-94bcbdccff96-->
|
1.0
|
UG-instruction is confusing - 
It is easy to make the user ignore the whitespace between addP and n/My Project, same in addT and deleteP.
I suggest make the whitespace clearer to users and reduce misunderstanding
<!--session: 1618552060415-53c0cdab-e582-44e3-b4f1-94bcbdccff96-->
|
non_process
|
ug instruction is confusing it is easy to make the user ignore the whitespace between addp and n my project same in addt and deletep i suggest make the whitespace clearer to users and reduce misunderstanding
| 0
|
267,966
| 23,336,887,008
|
IssuesEvent
|
2022-08-09 10:45:11
|
wso2/product-is
|
https://api.github.com/repos/wso2/product-is
|
opened
|
Tenanted users cannot login to my account, If super tenant has disabled recaptcha for SSO login and tenant has enabled recaptcha for SSO login
|
bug 6.0.0-rc-testing
|
**Describe the issue:**
If super tenant has disabled recaptcha for SSO login and tenant has enabled recaptcha for SSO login, tenanted users cannot login to my account as reCaptcha validation is required for those users.
**How to reproduce:**
- Setup Recaptcha (follow https://is.docs.wso2.com/en/latest/learn/setting-up-recaptcha).
Note: Use invisible recaptcha key and add localhost to domain
- Login to management console as super admin
- Go to `Identity Providers -> Resident`
- Expand `Login Attempts Security -> reCaptcha for SSO Login` and verify that `Always prompt reCaptcha` is disabled
- Create a tenant
- Login to management console as tenant admin
- Go to `Identity Providers -> Resident`
- Expand `Login Attempts Security -> reCaptcha for SSO Login` and enable `Always prompt reCaptcha`
- Go to my account login page and try to login as tenant admin (i.e username: <admin_user>@<tenant_domain>)
**Environment information**
- Product Version: IS 6.0.0 RC1, IS 5.11.0
- OS: MacOS
- Database: H2
|
1.0
|
Tenanted users cannot login to my account, If super tenant has disabled recaptcha for SSO login and tenant has enabled recaptcha for SSO login - **Describe the issue:**
If super tenant has disabled recaptcha for SSO login and tenant has enabled recaptcha for SSO login, tenanted users cannot login to my account as reCaptcha validation is required for those users.
**How to reproduce:**
- Setup Recaptcha (follow https://is.docs.wso2.com/en/latest/learn/setting-up-recaptcha).
Note: Use invisible recaptcha key and add localhost to domain
- Login to management console as super admin
- Go to `Identity Providers -> Resident`
- Expand `Login Attempts Security -> reCaptcha for SSO Login` and verify that `Always prompt reCaptcha` is disabled
- Create a tenant
- Login to management console as tenant admin
- Go to `Identity Providers -> Resident`
- Expand `Login Attempts Security -> reCaptcha for SSO Login` and enable `Always prompt reCaptcha`
- Go to my account login page and try to login as tenant admin (i.e username: <admin_user>@<tenant_domain>)
**Environment information**
- Product Version: IS 6.0.0 RC1, IS 5.11.0
- OS: MacOS
- Database: H2
|
non_process
|
tenanted users cannot login to my account if super tenant has disabled recaptcha for sso login and tenant has enabled recaptcha for sso login describe the issue if super tenant has disabled recaptcha for sso login and tenant has enabled recaptcha for sso login tenanted users cannot login to my account as recaptcha validation is required for those users how to reproduce setup recaptcha follow note use invisible recaptcha key and add localhost to domain login to management console as super admin go to identity providers resident expand login attempts security recaptcha for sso login and verify that always prompt recaptcha is disabled create a tenant login to management console as tenant admin go to identity providers resident expand login attempts security recaptcha for sso login and enable always prompt recaptcha go to my account login page and try to login as tenant admin i e username environment information product version is is os macos database
| 0
|
15,613
| 19,753,055,870
|
IssuesEvent
|
2022-01-15 09:02:16
|
googleapis/google-api-ruby-client
|
https://api.github.com/repos/googleapis/google-api-ruby-client
|
opened
|
Your .repo-metadata.json files have a problem 🤒
|
type: process repo-metadata: lint
|
You have a problem with your .repo-metadata.json files:
Result of scan 📈:
* must have required property 'release_level' in generated/google-apis-abusiveexperiencereport_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-abusiveexperiencereport_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-acceleratedmobilepageurl_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-acceleratedmobilepageurl_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-accessapproval_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-accessapproval_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-accesscontextmanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-accesscontextmanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-accesscontextmanager_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-accesscontextmanager_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexchangebuyer2_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexchangebuyer2_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexchangebuyer_v1_2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexchangebuyer_v1_2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexchangebuyer_v1_3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexchangebuyer_v1_3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexchangebuyer_v1_4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexchangebuyer_v1_4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexperiencereport_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexperiencereport_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admin_datatransfer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admin_datatransfer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admin_directory_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admin_directory_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admin_reports_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admin_reports_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admob_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admob_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admob_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admob_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adsense_v1_4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adsense_v1_4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adsense_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adsense_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adsensehost_v4_1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adsensehost_v4_1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-alertcenter_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-alertcenter_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-analytics_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-analytics_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-analyticsadmin_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-analyticsadmin_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-analyticsdata_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-analyticsdata_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-analyticsreporting_v4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-analyticsreporting_v4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-androiddeviceprovisioning_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-androiddeviceprovisioning_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-androidenterprise_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-androidenterprise_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-androidmanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-androidmanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-androidpublisher_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-androidpublisher_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-apigateway_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-apigateway_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-apigateway_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-apigateway_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-apigee_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-apigee_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-apikeys_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-apikeys_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-appengine_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-appengine_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-appengine_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-appengine_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-appengine_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-appengine_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-area120tables_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-area120tables_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-artifactregistry_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-artifactregistry_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-artifactregistry_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-artifactregistry_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-artifactregistry_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-artifactregistry_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-assuredworkloads_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-assuredworkloads_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-authorizedbuyersmarketplace_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-authorizedbuyersmarketplace_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-baremetalsolution_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-baremetalsolution_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-baremetalsolution_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-baremetalsolution_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-baremetalsolution_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-baremetalsolution_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigquery_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigquery_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigqueryconnection_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigqueryconnection_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigquerydatatransfer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigquerydatatransfer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigqueryreservation_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigqueryreservation_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigqueryreservation_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigqueryreservation_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigtableadmin_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigtableadmin_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigtableadmin_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigtableadmin_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-billingbudgets_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-billingbudgets_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-billingbudgets_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-billingbudgets_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-binaryauthorization_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-binaryauthorization_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-binaryauthorization_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-binaryauthorization_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-blogger_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-blogger_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-blogger_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-blogger_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-books_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-books_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-calendar_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-calendar_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-chat_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-chat_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-chromemanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-chromemanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-chromepolicy_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-chromepolicy_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-chromeuxreport_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-chromeuxreport_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-civicinfo_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-civicinfo_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-classroom_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-classroom_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1p4beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1p4beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1p5beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1p5beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1p7beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1p7beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbilling_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbilling_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbuild_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbuild_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbuild_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbuild_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbuild_v1alpha2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbuild_v1alpha2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbuild_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbuild_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudchannel_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudchannel_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-clouddebugger_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-clouddebugger_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-clouddeploy_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-clouddeploy_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-clouderrorreporting_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-clouderrorreporting_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudfunctions_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudfunctions_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudidentity_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudidentity_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudidentity_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudidentity_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudiot_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudiot_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudkms_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudkms_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudprofiler_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudprofiler_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudscheduler_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudscheduler_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudscheduler_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudscheduler_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudsearch_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudsearch_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudshell_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudshell_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudsupport_v2beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudsupport_v2beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtasks_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtasks_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtasks_v2beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtasks_v2beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtasks_v2beta3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtasks_v2beta3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtrace_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtrace_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtrace_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtrace_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtrace_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtrace_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-composer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-composer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-composer_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-composer_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-compute_alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-compute_alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-compute_beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-compute_beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-compute_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-compute_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-connectors_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-connectors_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-contactcenterinsights_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-contactcenterinsights_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-container_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-container_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-container_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-container_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-containeranalysis_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-containeranalysis_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-containeranalysis_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-containeranalysis_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-containeranalysis_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-containeranalysis_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-content_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-content_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-content_v2_1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-content_v2_1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-customsearch_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-customsearch_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datacatalog_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datacatalog_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datacatalog_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datacatalog_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dataflow_v1b3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dataflow_v1b3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datafusion_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datafusion_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datafusion_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datafusion_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datalabeling_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datalabeling_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datamigration_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datamigration_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datamigration_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datamigration_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datapipelines_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datapipelines_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dataproc_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dataproc_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dataproc_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dataproc_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastore_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastore_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastore_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastore_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastore_v1beta3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastore_v1beta3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastream_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastream_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastream_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastream_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-deploymentmanager_alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-deploymentmanager_alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-deploymentmanager_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-deploymentmanager_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-deploymentmanager_v2beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-deploymentmanager_v2beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dfareporting_v3_3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dfareporting_v3_3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dfareporting_v3_4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dfareporting_v3_4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dfareporting_v3_5/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dfareporting_v3_5/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dialogflow_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dialogflow_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dialogflow_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dialogflow_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dialogflow_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dialogflow_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dialogflow_v3beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dialogflow_v3beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-digitalassetlinks_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-digitalassetlinks_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-discovery_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-discovery_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-displayvideo_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-displayvideo_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dlp_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dlp_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dns_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dns_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dns_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dns_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-docs_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-docs_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-documentai_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-documentai_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-documentai_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-documentai_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-documentai_v1beta3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-documentai_v1beta3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-domains_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-domains_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-domains_v1alpha2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-domains_v1alpha2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-domains_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-domains_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-domainsrdap_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-domainsrdap_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-doubleclickbidmanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-doubleclickbidmanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-doubleclickbidmanager_v1_1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-doubleclickbidmanager_v1_1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-doubleclicksearch_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-doubleclicksearch_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-drive_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-drive_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-drive_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-drive_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-driveactivity_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-driveactivity_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-essentialcontacts_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-essentialcontacts_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-eventarc_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-eventarc_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-eventarc_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-eventarc_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-factchecktools_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-factchecktools_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-fcm_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-fcm_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-fcmdata_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-fcmdata_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-file_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-file_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-file_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-file_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebase_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebase_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebaseappcheck_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebaseappcheck_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasedatabase_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasedatabase_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasedynamiclinks_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasedynamiclinks_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasehosting_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasehosting_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasehosting_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasehosting_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebaseml_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebaseml_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebaseml_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebaseml_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebaserules_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebaserules_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasestorage_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasestorage_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firestore_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firestore_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firestore_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firestore_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firestore_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firestore_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-fitness_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-fitness_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-games_configuration_v1configuration/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-games_configuration_v1configuration/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-games_management_v1management/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-games_management_v1management/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-games_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-games_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gameservices_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gameservices_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gameservices_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gameservices_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-genomics_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-genomics_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-genomics_v1alpha2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-genomics_v1alpha2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-genomics_v2alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-genomics_v2alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1alpha2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1alpha2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gmail_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gmail_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gmailpostmastertools_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gmailpostmastertools_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gmailpostmastertools_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gmailpostmastertools_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-groupsmigration_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-groupsmigration_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-groupssettings_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-groupssettings_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-healthcare_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-healthcare_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-healthcare_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-healthcare_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-homegraph_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-homegraph_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-iam_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-iam_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-iamcredentials_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-iamcredentials_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-iap_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-iap_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-iap_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-iap_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ideahub_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ideahub_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ideahub_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ideahub_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-identitytoolkit_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-identitytoolkit_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-indexing_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-indexing_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-jobs_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-jobs_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-jobs_v3p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-jobs_v3p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-jobs_v4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-jobs_v4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-keep_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-keep_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-kgsearch_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-kgsearch_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-language_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-language_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-language_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-language_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-language_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-language_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-libraryagent_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-libraryagent_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-licensing_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-licensing_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-lifesciences_v2beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-lifesciences_v2beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-localservices_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-localservices_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-logging_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-logging_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-managedidentities_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-managedidentities_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-managedidentities_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-managedidentities_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-managedidentities_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-managedidentities_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-manufacturers_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-manufacturers_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-memcache_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-memcache_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-memcache_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-memcache_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-metastore_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-metastore_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-metastore_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-metastore_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ml_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ml_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-monitoring_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-monitoring_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-monitoring_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-monitoring_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessaccountmanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessaccountmanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessbusinessinformation_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessbusinessinformation_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinesslodging_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinesslodging_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessnotifications_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessnotifications_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessplaceactions_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessplaceactions_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessqanda_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessqanda_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessverifications_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessverifications_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkconnectivity_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkconnectivity_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkconnectivity_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkconnectivity_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkmanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkmanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkmanagement_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkmanagement_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networksecurity_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networksecurity_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networksecurity_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networksecurity_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkservices_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkservices_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkservices_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkservices_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-notebooks_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-notebooks_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-oauth2_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-oauth2_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ondemandscanning_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ondemandscanning_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ondemandscanning_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ondemandscanning_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-orgpolicy_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-orgpolicy_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-osconfig_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-osconfig_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-osconfig_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-osconfig_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-osconfig_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-osconfig_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-oslogin_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-oslogin_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-oslogin_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-oslogin_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-oslogin_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-oslogin_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pagespeedonline_v5/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pagespeedonline_v5/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-paymentsresellersubscription_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-paymentsresellersubscription_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-people_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-people_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-playablelocations_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-playablelocations_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-playcustomapp_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-playcustomapp_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policyanalyzer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policyanalyzer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policyanalyzer_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policyanalyzer_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policysimulator_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policysimulator_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policysimulator_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policysimulator_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policytroubleshooter_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policytroubleshooter_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policytroubleshooter_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policytroubleshooter_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-poly_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-poly_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-privateca_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-privateca_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-privateca_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-privateca_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-prod_tt_sasportal_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-prod_tt_sasportal_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pubsub_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pubsub_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pubsub_v1beta1a/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pubsub_v1beta1a/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pubsub_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pubsub_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pubsublite_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pubsublite_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-realtimebidding_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-realtimebidding_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-realtimebidding_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-realtimebidding_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-recaptchaenterprise_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-recaptchaenterprise_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-recommendationengine_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-recommendationengine_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-recommender_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-recommender_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-recommender_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-recommender_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-redis_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-redis_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-redis_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-redis_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-remotebuildexecution_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-remotebuildexecution_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-remotebuildexecution_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-remotebuildexecution_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-remotebuildexecution_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-remotebuildexecution_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-reseller_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-reseller_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-resourcesettings_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-resourcesettings_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-retail_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-retail_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-retail_v2alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-retail_v2alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-retail_v2beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-retail_v2beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-run_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-run_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-run_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-run_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-run_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-run_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-run_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-run_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-runtimeconfig_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-runtimeconfig_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-runtimeconfig_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-runtimeconfig_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-safebrowsing_v4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-safebrowsing_v4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sasportal_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sasportal_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-script_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-script_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-searchconsole_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-searchconsole_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-secretmanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-secretmanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-secretmanager_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-secretmanager_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-securitycenter_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-securitycenter_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-securitycenter_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-securitycenter_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-securitycenter_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-securitycenter_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-serviceconsumermanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-serviceconsumermanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-serviceconsumermanagement_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-serviceconsumermanagement_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicecontrol_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicecontrol_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicecontrol_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicecontrol_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicedirectory_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicedirectory_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicedirectory_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicedirectory_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicemanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicemanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicenetworking_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicenetworking_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicenetworking_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicenetworking_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-serviceusage_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-serviceusage_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-serviceusage_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-serviceusage_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sheets_v4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sheets_v4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-site_verification_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-site_verification_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-slides_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-slides_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-smartdevicemanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-smartdevicemanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sourcerepo_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sourcerepo_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-spanner_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-spanner_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-speech_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-speech_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-speech_v1p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-speech_v1p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-speech_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-speech_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sqladmin_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sqladmin_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sqladmin_v1beta4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sqladmin_v1beta4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-storage_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-storage_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-storagetransfer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-storagetransfer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-streetviewpublish_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-streetviewpublish_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sts_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sts_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sts_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sts_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tagmanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tagmanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tagmanager_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tagmanager_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tasks_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tasks_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-testing_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-testing_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-texttospeech_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-texttospeech_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-texttospeech_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-texttospeech_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-toolresults_v1beta3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-toolresults_v1beta3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tpu_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tpu_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tpu_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tpu_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tpu_v2alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tpu_v2alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-trafficdirector_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-trafficdirector_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-transcoder_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-transcoder_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-transcoder_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-transcoder_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-translate_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-translate_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-translate_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-translate_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-translate_v3beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-translate_v3beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vault_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vault_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vectortile_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vectortile_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-verifiedaccess_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-verifiedaccess_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-versionhistory_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-versionhistory_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1p2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1p2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1p3beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1p3beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vision_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vision_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vision_v1p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vision_v1p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vision_v1p2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vision_v1p2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vmmigration_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vmmigration_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vmmigration_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vmmigration_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-webfonts_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-webfonts_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-webmasters_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-webmasters_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-webrisk_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-webrisk_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-websecurityscanner_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-websecurityscanner_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-websecurityscanner_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-websecurityscanner_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-websecurityscanner_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-websecurityscanner_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-workflowexecutions_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-workflowexecutions_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-workflowexecutions_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-workflowexecutions_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-workflows_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-workflows_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-workflows_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-workflows_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-youtube_analytics_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-youtube_analytics_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-youtube_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-youtube_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-youtubereporting_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-youtubereporting_v1/.repo-metadata.json
* must have required property 'release_level' in google-api-client/.repo-metadata.json
* must have required property 'client_documentation' in google-api-client/.repo-metadata.json
* must have required property 'release_level' in google-apis-core/.repo-metadata.json
* must have required property 'client_documentation' in google-apis-core/.repo-metadata.json
* must have required property 'release_level' in google-apis-generator/.repo-metadata.json
* must have required property 'client_documentation' in google-apis-generator/.repo-metadata.json
☝️ Once you address these problems, you can close this issue.
### Need help?
* [Schema definition](https://github.com/googleapis/repo-automation-bots/blob/main/packages/repo-metadata-lint/src/repo-metadata-schema.json): lists valid options for each field.
* [API index](https://github.com/googleapis/googleapis/blob/master/api-index-v1.json): for gRPC libraries **api_shortname** should match the subdomain of an API's **hostName**.
* Reach out to **go/github-automation** if you have any questions.
|
1.0
|
Your .repo-metadata.json files have a problem 🤒 - You have a problem with your .repo-metadata.json files:
Result of scan 📈:
* must have required property 'release_level' in generated/google-apis-abusiveexperiencereport_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-abusiveexperiencereport_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-acceleratedmobilepageurl_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-acceleratedmobilepageurl_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-accessapproval_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-accessapproval_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-accesscontextmanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-accesscontextmanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-accesscontextmanager_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-accesscontextmanager_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexchangebuyer2_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexchangebuyer2_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexchangebuyer_v1_2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexchangebuyer_v1_2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexchangebuyer_v1_3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexchangebuyer_v1_3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexchangebuyer_v1_4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexchangebuyer_v1_4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adexperiencereport_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adexperiencereport_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admin_datatransfer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admin_datatransfer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admin_directory_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admin_directory_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admin_reports_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admin_reports_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admob_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admob_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-admob_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-admob_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adsense_v1_4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adsense_v1_4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adsense_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adsense_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-adsensehost_v4_1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-adsensehost_v4_1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-alertcenter_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-alertcenter_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-analytics_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-analytics_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-analyticsadmin_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-analyticsadmin_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-analyticsdata_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-analyticsdata_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-analyticsreporting_v4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-analyticsreporting_v4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-androiddeviceprovisioning_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-androiddeviceprovisioning_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-androidenterprise_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-androidenterprise_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-androidmanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-androidmanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-androidpublisher_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-androidpublisher_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-apigateway_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-apigateway_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-apigateway_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-apigateway_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-apigee_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-apigee_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-apikeys_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-apikeys_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-appengine_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-appengine_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-appengine_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-appengine_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-appengine_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-appengine_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-area120tables_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-area120tables_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-artifactregistry_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-artifactregistry_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-artifactregistry_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-artifactregistry_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-artifactregistry_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-artifactregistry_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-assuredworkloads_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-assuredworkloads_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-authorizedbuyersmarketplace_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-authorizedbuyersmarketplace_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-baremetalsolution_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-baremetalsolution_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-baremetalsolution_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-baremetalsolution_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-baremetalsolution_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-baremetalsolution_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigquery_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigquery_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigqueryconnection_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigqueryconnection_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigquerydatatransfer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigquerydatatransfer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigqueryreservation_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigqueryreservation_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigqueryreservation_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigqueryreservation_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigtableadmin_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigtableadmin_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-bigtableadmin_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-bigtableadmin_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-billingbudgets_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-billingbudgets_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-billingbudgets_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-billingbudgets_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-binaryauthorization_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-binaryauthorization_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-binaryauthorization_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-binaryauthorization_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-blogger_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-blogger_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-blogger_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-blogger_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-books_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-books_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-calendar_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-calendar_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-chat_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-chat_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-chromemanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-chromemanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-chromepolicy_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-chromepolicy_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-chromeuxreport_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-chromeuxreport_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-civicinfo_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-civicinfo_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-classroom_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-classroom_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1p4beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1p4beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1p5beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1p5beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudasset_v1p7beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudasset_v1p7beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbilling_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbilling_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbuild_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbuild_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbuild_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbuild_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbuild_v1alpha2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbuild_v1alpha2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudbuild_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudbuild_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudchannel_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudchannel_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-clouddebugger_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-clouddebugger_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-clouddeploy_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-clouddeploy_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-clouderrorreporting_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-clouderrorreporting_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudfunctions_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudfunctions_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudidentity_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudidentity_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudidentity_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudidentity_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudiot_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudiot_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudkms_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudkms_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudprofiler_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudprofiler_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudresourcemanager_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudresourcemanager_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudscheduler_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudscheduler_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudscheduler_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudscheduler_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudsearch_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudsearch_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudshell_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudshell_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudsupport_v2beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudsupport_v2beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtasks_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtasks_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtasks_v2beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtasks_v2beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtasks_v2beta3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtasks_v2beta3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtrace_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtrace_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtrace_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtrace_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-cloudtrace_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-cloudtrace_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-composer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-composer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-composer_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-composer_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-compute_alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-compute_alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-compute_beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-compute_beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-compute_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-compute_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-connectors_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-connectors_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-contactcenterinsights_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-contactcenterinsights_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-container_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-container_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-container_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-container_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-containeranalysis_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-containeranalysis_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-containeranalysis_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-containeranalysis_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-containeranalysis_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-containeranalysis_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-content_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-content_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-content_v2_1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-content_v2_1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-customsearch_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-customsearch_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datacatalog_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datacatalog_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datacatalog_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datacatalog_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dataflow_v1b3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dataflow_v1b3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datafusion_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datafusion_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datafusion_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datafusion_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datalabeling_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datalabeling_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datamigration_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datamigration_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datamigration_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datamigration_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datapipelines_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datapipelines_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dataproc_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dataproc_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dataproc_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dataproc_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastore_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastore_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastore_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastore_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastore_v1beta3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastore_v1beta3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastream_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastream_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-datastream_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-datastream_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-deploymentmanager_alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-deploymentmanager_alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-deploymentmanager_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-deploymentmanager_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-deploymentmanager_v2beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-deploymentmanager_v2beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dfareporting_v3_3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dfareporting_v3_3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dfareporting_v3_4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dfareporting_v3_4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dfareporting_v3_5/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dfareporting_v3_5/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dialogflow_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dialogflow_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dialogflow_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dialogflow_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dialogflow_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dialogflow_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dialogflow_v3beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dialogflow_v3beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-digitalassetlinks_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-digitalassetlinks_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-discovery_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-discovery_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-displayvideo_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-displayvideo_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dlp_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dlp_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dns_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dns_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-dns_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-dns_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-docs_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-docs_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-documentai_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-documentai_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-documentai_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-documentai_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-documentai_v1beta3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-documentai_v1beta3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-domains_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-domains_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-domains_v1alpha2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-domains_v1alpha2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-domains_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-domains_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-domainsrdap_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-domainsrdap_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-doubleclickbidmanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-doubleclickbidmanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-doubleclickbidmanager_v1_1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-doubleclickbidmanager_v1_1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-doubleclicksearch_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-doubleclicksearch_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-drive_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-drive_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-drive_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-drive_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-driveactivity_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-driveactivity_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-essentialcontacts_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-essentialcontacts_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-eventarc_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-eventarc_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-eventarc_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-eventarc_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-factchecktools_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-factchecktools_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-fcm_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-fcm_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-fcmdata_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-fcmdata_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-file_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-file_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-file_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-file_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebase_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebase_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebaseappcheck_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebaseappcheck_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasedatabase_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasedatabase_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasedynamiclinks_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasedynamiclinks_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasehosting_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasehosting_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasehosting_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasehosting_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebaseml_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebaseml_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebaseml_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebaseml_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebaserules_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebaserules_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firebasestorage_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firebasestorage_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firestore_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firestore_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firestore_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firestore_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-firestore_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-firestore_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-fitness_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-fitness_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-games_configuration_v1configuration/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-games_configuration_v1configuration/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-games_management_v1management/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-games_management_v1management/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-games_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-games_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gameservices_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gameservices_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gameservices_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gameservices_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-genomics_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-genomics_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-genomics_v1alpha2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-genomics_v1alpha2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-genomics_v2alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-genomics_v2alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1alpha2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1alpha2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gkehub_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gkehub_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gmail_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gmail_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gmailpostmastertools_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gmailpostmastertools_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-gmailpostmastertools_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-gmailpostmastertools_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-groupsmigration_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-groupsmigration_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-groupssettings_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-groupssettings_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-healthcare_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-healthcare_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-healthcare_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-healthcare_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-homegraph_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-homegraph_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-iam_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-iam_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-iamcredentials_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-iamcredentials_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-iap_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-iap_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-iap_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-iap_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ideahub_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ideahub_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ideahub_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ideahub_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-identitytoolkit_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-identitytoolkit_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-indexing_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-indexing_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-jobs_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-jobs_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-jobs_v3p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-jobs_v3p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-jobs_v4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-jobs_v4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-keep_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-keep_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-kgsearch_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-kgsearch_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-language_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-language_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-language_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-language_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-language_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-language_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-libraryagent_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-libraryagent_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-licensing_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-licensing_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-lifesciences_v2beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-lifesciences_v2beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-localservices_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-localservices_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-logging_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-logging_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-managedidentities_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-managedidentities_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-managedidentities_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-managedidentities_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-managedidentities_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-managedidentities_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-manufacturers_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-manufacturers_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-memcache_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-memcache_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-memcache_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-memcache_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-metastore_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-metastore_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-metastore_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-metastore_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ml_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ml_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-monitoring_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-monitoring_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-monitoring_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-monitoring_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessaccountmanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessaccountmanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessbusinessinformation_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessbusinessinformation_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinesslodging_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinesslodging_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessnotifications_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessnotifications_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessplaceactions_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessplaceactions_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessqanda_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessqanda_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-mybusinessverifications_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-mybusinessverifications_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkconnectivity_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkconnectivity_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkconnectivity_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkconnectivity_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkmanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkmanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkmanagement_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkmanagement_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networksecurity_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networksecurity_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networksecurity_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networksecurity_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkservices_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkservices_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-networkservices_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-networkservices_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-notebooks_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-notebooks_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-oauth2_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-oauth2_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ondemandscanning_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ondemandscanning_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-ondemandscanning_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-ondemandscanning_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-orgpolicy_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-orgpolicy_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-osconfig_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-osconfig_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-osconfig_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-osconfig_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-osconfig_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-osconfig_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-oslogin_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-oslogin_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-oslogin_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-oslogin_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-oslogin_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-oslogin_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pagespeedonline_v5/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pagespeedonline_v5/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-paymentsresellersubscription_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-paymentsresellersubscription_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-people_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-people_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-playablelocations_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-playablelocations_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-playcustomapp_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-playcustomapp_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policyanalyzer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policyanalyzer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policyanalyzer_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policyanalyzer_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policysimulator_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policysimulator_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policysimulator_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policysimulator_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policytroubleshooter_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policytroubleshooter_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-policytroubleshooter_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-policytroubleshooter_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-poly_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-poly_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-privateca_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-privateca_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-privateca_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-privateca_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-prod_tt_sasportal_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-prod_tt_sasportal_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pubsub_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pubsub_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pubsub_v1beta1a/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pubsub_v1beta1a/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pubsub_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pubsub_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-pubsublite_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-pubsublite_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-realtimebidding_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-realtimebidding_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-realtimebidding_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-realtimebidding_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-recaptchaenterprise_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-recaptchaenterprise_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-recommendationengine_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-recommendationengine_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-recommender_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-recommender_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-recommender_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-recommender_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-redis_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-redis_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-redis_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-redis_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-remotebuildexecution_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-remotebuildexecution_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-remotebuildexecution_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-remotebuildexecution_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-remotebuildexecution_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-remotebuildexecution_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-reseller_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-reseller_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-resourcesettings_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-resourcesettings_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-retail_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-retail_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-retail_v2alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-retail_v2alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-retail_v2beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-retail_v2beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-run_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-run_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-run_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-run_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-run_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-run_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-run_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-run_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-runtimeconfig_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-runtimeconfig_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-runtimeconfig_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-runtimeconfig_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-safebrowsing_v4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-safebrowsing_v4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sasportal_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sasportal_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-script_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-script_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-searchconsole_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-searchconsole_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-secretmanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-secretmanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-secretmanager_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-secretmanager_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-securitycenter_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-securitycenter_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-securitycenter_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-securitycenter_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-securitycenter_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-securitycenter_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-serviceconsumermanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-serviceconsumermanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-serviceconsumermanagement_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-serviceconsumermanagement_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicecontrol_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicecontrol_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicecontrol_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicecontrol_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicedirectory_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicedirectory_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicedirectory_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicedirectory_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicemanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicemanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicenetworking_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicenetworking_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-servicenetworking_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-servicenetworking_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-serviceusage_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-serviceusage_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-serviceusage_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-serviceusage_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sheets_v4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sheets_v4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-site_verification_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-site_verification_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-slides_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-slides_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-smartdevicemanagement_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-smartdevicemanagement_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sourcerepo_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sourcerepo_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-spanner_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-spanner_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-speech_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-speech_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-speech_v1p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-speech_v1p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-speech_v2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-speech_v2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sqladmin_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sqladmin_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sqladmin_v1beta4/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sqladmin_v1beta4/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-storage_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-storage_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-storagetransfer_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-storagetransfer_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-streetviewpublish_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-streetviewpublish_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sts_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sts_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-sts_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-sts_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tagmanager_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tagmanager_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tagmanager_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tagmanager_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tasks_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tasks_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-testing_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-testing_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-texttospeech_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-texttospeech_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-texttospeech_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-texttospeech_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-toolresults_v1beta3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-toolresults_v1beta3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tpu_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tpu_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tpu_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tpu_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-tpu_v2alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-tpu_v2alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-trafficdirector_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-trafficdirector_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-transcoder_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-transcoder_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-transcoder_v1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-transcoder_v1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-translate_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-translate_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-translate_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-translate_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-translate_v3beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-translate_v3beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vault_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vault_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vectortile_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vectortile_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-verifiedaccess_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-verifiedaccess_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-versionhistory_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-versionhistory_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1beta2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1beta2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1p2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1p2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-videointelligence_v1p3beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-videointelligence_v1p3beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vision_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vision_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vision_v1p1beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vision_v1p1beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vision_v1p2beta1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vision_v1p2beta1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vmmigration_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vmmigration_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-vmmigration_v1alpha1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-vmmigration_v1alpha1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-webfonts_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-webfonts_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-webmasters_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-webmasters_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-webrisk_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-webrisk_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-websecurityscanner_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-websecurityscanner_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-websecurityscanner_v1alpha/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-websecurityscanner_v1alpha/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-websecurityscanner_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-websecurityscanner_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-workflowexecutions_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-workflowexecutions_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-workflowexecutions_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-workflowexecutions_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-workflows_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-workflows_v1/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-workflows_v1beta/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-workflows_v1beta/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-youtube_analytics_v2/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-youtube_analytics_v2/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-youtube_v3/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-youtube_v3/.repo-metadata.json
* must have required property 'release_level' in generated/google-apis-youtubereporting_v1/.repo-metadata.json
* must have required property 'client_documentation' in generated/google-apis-youtubereporting_v1/.repo-metadata.json
* must have required property 'release_level' in google-api-client/.repo-metadata.json
* must have required property 'client_documentation' in google-api-client/.repo-metadata.json
* must have required property 'release_level' in google-apis-core/.repo-metadata.json
* must have required property 'client_documentation' in google-apis-core/.repo-metadata.json
* must have required property 'release_level' in google-apis-generator/.repo-metadata.json
* must have required property 'client_documentation' in google-apis-generator/.repo-metadata.json
☝️ Once you address these problems, you can close this issue.
### Need help?
* [Schema definition](https://github.com/googleapis/repo-automation-bots/blob/main/packages/repo-metadata-lint/src/repo-metadata-schema.json): lists valid options for each field.
* [API index](https://github.com/googleapis/googleapis/blob/master/api-index-v1.json): for gRPC libraries **api_shortname** should match the subdomain of an API's **hostName**.
* Reach out to **go/github-automation** if you have any questions.
|
process
|
your repo metadata json files have a problem 🤒 you have a problem with your repo metadata json files result of scan 📈 must have required property release level in generated google apis abusiveexperiencereport repo metadata json must have required property client documentation in generated google apis abusiveexperiencereport repo metadata json must have required property release level in generated google apis acceleratedmobilepageurl repo metadata json must have required property client documentation in generated google apis acceleratedmobilepageurl repo metadata json must have required property release level in generated google apis accessapproval repo metadata json must have required property client documentation in generated google apis accessapproval repo metadata json must have required property release level in generated google apis accesscontextmanager repo metadata json must have required property client documentation in generated google apis accesscontextmanager repo metadata json must have required property release level in generated google apis accesscontextmanager repo metadata json must have required property client documentation in generated google apis accesscontextmanager repo metadata json must have required property release level in generated google apis repo metadata json must have required property client documentation in generated google apis repo metadata json must have required property release level in generated google apis adexchangebuyer repo metadata json must have required property client documentation in generated google apis adexchangebuyer repo metadata json must have required property release level in generated google apis adexchangebuyer repo metadata json must have required property client documentation in generated google apis adexchangebuyer repo metadata json must have required property release level in generated google apis adexchangebuyer repo metadata json must have required property client documentation in generated google apis adexchangebuyer repo metadata json must have required property release level in generated google apis adexperiencereport repo metadata json must have required property client documentation in generated google apis adexperiencereport repo metadata json must have required property release level in generated google apis admin datatransfer repo metadata json must have required property client documentation in generated google apis admin datatransfer repo metadata json must have required property release level in generated google apis admin directory repo metadata json must have required property client documentation in generated google apis admin directory repo metadata json must have required property release level in generated google apis admin reports repo metadata json must have required property client documentation in generated google apis admin reports repo metadata json must have required property release level in generated google apis admob repo metadata json must have required property client documentation in generated google apis admob repo metadata json must have required property release level in generated google apis admob repo metadata json must have required property client documentation in generated google apis admob repo metadata json must have required property release level in generated google apis adsense repo metadata json must have required property client documentation in generated google apis adsense repo metadata json must have required property release level in generated google apis adsense repo metadata json must have required property client documentation in generated google apis adsense repo metadata json must have required property release level in generated google apis adsensehost repo metadata json must have required property client documentation in generated google apis adsensehost repo metadata json must have required property release level in generated google apis alertcenter repo metadata json must have required property client documentation in generated google apis alertcenter repo metadata json must have required property release level in generated google apis analytics repo metadata json must have required property client documentation in generated google apis analytics repo metadata json must have required property release level in generated google apis analyticsadmin repo metadata json must have required property client documentation in generated google apis analyticsadmin repo metadata json must have required property release level in generated google apis analyticsdata repo metadata json must have required property client documentation in generated google apis analyticsdata repo metadata json must have required property release level in generated google apis analyticsreporting repo metadata json must have required property client documentation in generated google apis analyticsreporting repo metadata json must have required property release level in generated google apis androiddeviceprovisioning repo metadata json must have required property client documentation in generated google apis androiddeviceprovisioning repo metadata json must have required property release level in generated google apis androidenterprise repo metadata json must have required property client documentation in generated google apis androidenterprise repo metadata json must have required property release level in generated google apis androidmanagement repo metadata json must have required property client documentation in generated google apis androidmanagement repo metadata json must have required property release level in generated google apis androidpublisher repo metadata json must have required property client documentation in generated google apis androidpublisher repo metadata json must have required property release level in generated google apis apigateway repo metadata json must have required property client documentation in generated google apis apigateway repo metadata json must have required property release level in generated google apis apigateway repo metadata json must have required property client documentation in generated google apis apigateway repo metadata json must have required property release level in generated google apis apigee repo metadata json must have required property client documentation in generated google apis apigee repo metadata json must have required property release level in generated google apis apikeys repo metadata json must have required property client documentation in generated google apis apikeys repo metadata json must have required property release level in generated google apis appengine repo metadata json must have required property client documentation in generated google apis appengine repo metadata json must have required property release level in generated google apis appengine repo metadata json must have required property client documentation in generated google apis appengine repo metadata json must have required property release level in generated google apis appengine repo metadata json must have required property client documentation in generated google apis appengine repo metadata json must have required property release level in generated google apis repo metadata json must have required property client documentation in generated google apis repo metadata json must have required property release level in generated google apis artifactregistry repo metadata json must have required property client documentation in generated google apis artifactregistry repo metadata json must have required property release level in generated google apis artifactregistry repo metadata json must have required property client documentation in generated google apis artifactregistry repo metadata json must have required property release level in generated google apis artifactregistry repo metadata json must have required property client documentation in generated google apis artifactregistry repo metadata json must have required property release level in generated google apis assuredworkloads repo metadata json must have required property client documentation in generated google apis assuredworkloads repo metadata json must have required property release level in generated google apis authorizedbuyersmarketplace repo metadata json must have required property client documentation in generated google apis authorizedbuyersmarketplace repo metadata json must have required property release level in generated google apis baremetalsolution repo metadata json must have required property client documentation in generated google apis baremetalsolution repo metadata json must have required property release level in generated google apis baremetalsolution repo metadata json must have required property client documentation in generated google apis baremetalsolution repo metadata json must have required property release level in generated google apis baremetalsolution repo metadata json must have required property client documentation in generated google apis baremetalsolution repo metadata json must have required property release level in generated google apis bigquery repo metadata json must have required property client documentation in generated google apis bigquery repo metadata json must have required property release level in generated google apis bigqueryconnection repo metadata json must have required property client documentation in generated google apis bigqueryconnection repo metadata json must have required property release level in generated google apis bigquerydatatransfer repo metadata json must have required property client documentation in generated google apis bigquerydatatransfer repo metadata json must have required property release level in generated google apis bigqueryreservation repo metadata json must have required property client documentation in generated google apis bigqueryreservation repo metadata json must have required property release level in generated google apis bigqueryreservation repo metadata json must have required property client documentation in generated google apis bigqueryreservation repo metadata json must have required property release level in generated google apis bigtableadmin repo metadata json must have required property client documentation in generated google apis bigtableadmin repo metadata json must have required property release level in generated google apis bigtableadmin repo metadata json must have required property client documentation in generated google apis bigtableadmin repo metadata json must have required property release level in generated google apis billingbudgets repo metadata json must have required property client documentation in generated google apis billingbudgets repo metadata json must have required property release level in generated google apis billingbudgets repo metadata json must have required property client documentation in generated google apis billingbudgets repo metadata json must have required property release level in generated google apis binaryauthorization repo metadata json must have required property client documentation in generated google apis binaryauthorization repo metadata json must have required property release level in generated google apis binaryauthorization repo metadata json must have required property client documentation in generated google apis binaryauthorization repo metadata json must have required property release level in generated google apis blogger repo metadata json must have required property client documentation in generated google apis blogger repo metadata json must have required property release level in generated google apis blogger repo metadata json must have required property client documentation in generated google apis blogger repo metadata json must have required property release level in generated google apis books repo metadata json must have required property client documentation in generated google apis books repo metadata json must have required property release level in generated google apis calendar repo metadata json must have required property client documentation in generated google apis calendar repo metadata json must have required property release level in generated google apis chat repo metadata json must have required property client documentation in generated google apis chat repo metadata json must have required property release level in generated google apis chromemanagement repo metadata json must have required property client documentation in generated google apis chromemanagement repo metadata json must have required property release level in generated google apis chromepolicy repo metadata json must have required property client documentation in generated google apis chromepolicy repo metadata json must have required property release level in generated google apis chromeuxreport repo metadata json must have required property client documentation in generated google apis chromeuxreport repo metadata json must have required property release level in generated google apis civicinfo repo metadata json must have required property client documentation in generated google apis civicinfo repo metadata json must have required property release level in generated google apis classroom repo metadata json must have required property client documentation in generated google apis classroom repo metadata json must have required property release level in generated google apis cloudasset repo metadata json must have required property client documentation in generated google apis cloudasset repo metadata json must have required property release level in generated google apis cloudasset repo metadata json must have required property client documentation in generated google apis cloudasset repo metadata json must have required property release level in generated google apis cloudasset repo metadata json must have required property client documentation in generated google apis cloudasset repo metadata json must have required property release level in generated google apis cloudasset repo metadata json must have required property client documentation in generated google apis cloudasset repo metadata json must have required property release level in generated google apis cloudasset repo metadata json must have required property client documentation in generated google apis cloudasset repo metadata json must have required property release level in generated google apis cloudasset repo metadata json must have required property client documentation in generated google apis cloudasset repo metadata json must have required property release level in generated google apis cloudbilling repo metadata json must have required property client documentation in generated google apis cloudbilling repo metadata json must have required property release level in generated google apis cloudbuild repo metadata json must have required property client documentation in generated google apis cloudbuild repo metadata json must have required property release level in generated google apis cloudbuild repo metadata json must have required property client documentation in generated google apis cloudbuild repo metadata json must have required property release level in generated google apis cloudbuild repo metadata json must have required property client documentation in generated google apis cloudbuild repo metadata json must have required property release level in generated google apis cloudbuild repo metadata json must have required property client documentation in generated google apis cloudbuild repo metadata json must have required property release level in generated google apis cloudchannel repo metadata json must have required property client documentation in generated google apis cloudchannel repo metadata json must have required property release level in generated google apis clouddebugger repo metadata json must have required property client documentation in generated google apis clouddebugger repo metadata json must have required property release level in generated google apis clouddeploy repo metadata json must have required property client documentation in generated google apis clouddeploy repo metadata json must have required property release level in generated google apis clouderrorreporting repo metadata json must have required property client documentation in generated google apis clouderrorreporting repo metadata json must have required property release level in generated google apis cloudfunctions repo metadata json must have required property client documentation in generated google apis cloudfunctions repo metadata json must have required property release level in generated google apis cloudidentity repo metadata json must have required property client documentation in generated google apis cloudidentity repo metadata json must have required property release level in generated google apis cloudidentity repo metadata json must have required property client documentation in generated google apis cloudidentity repo metadata json must have required property release level in generated google apis cloudiot repo metadata json must have required property client documentation in generated google apis cloudiot repo metadata json must have required property release level in generated google apis cloudkms repo metadata json must have required property client documentation in generated google apis cloudkms repo metadata json must have required property release level in generated google apis cloudprofiler repo metadata json must have required property client documentation in generated google apis cloudprofiler repo metadata json must have required property release level in generated google apis cloudresourcemanager repo metadata json must have required property client documentation in generated google apis cloudresourcemanager repo metadata json must have required property release level in generated google apis cloudresourcemanager repo metadata json must have required property client documentation in generated google apis cloudresourcemanager repo metadata json must have required property release level in generated google apis cloudresourcemanager repo metadata json must have required property client documentation in generated google apis cloudresourcemanager repo metadata json must have required property release level in generated google apis cloudresourcemanager repo metadata json must have required property client documentation in generated google apis cloudresourcemanager repo metadata json must have required property release level in generated google apis cloudresourcemanager repo metadata json must have required property client documentation in generated google apis cloudresourcemanager repo metadata json must have required property release level in generated google apis cloudscheduler repo metadata json must have required property client documentation in generated google apis cloudscheduler repo metadata json must have required property release level in generated google apis cloudscheduler repo metadata json must have required property client documentation in generated google apis cloudscheduler repo metadata json must have required property release level in generated google apis cloudsearch repo metadata json must have required property client documentation in generated google apis cloudsearch repo metadata json must have required property release level in generated google apis cloudshell repo metadata json must have required property client documentation in generated google apis cloudshell repo metadata json must have required property release level in generated google apis cloudsupport repo metadata json must have required property client documentation in generated google apis cloudsupport repo metadata json must have required property release level in generated google apis cloudtasks repo metadata json must have required property client documentation in generated google apis cloudtasks repo metadata json must have required property release level in generated google apis cloudtasks repo metadata json must have required property client documentation in generated google apis cloudtasks repo metadata json must have required property release level in generated google apis cloudtasks repo metadata json must have required property client documentation in generated google apis cloudtasks repo metadata json must have required property release level in generated google apis cloudtrace repo metadata json must have required property client documentation in generated google apis cloudtrace repo metadata json must have required property release level in generated google apis cloudtrace repo metadata json must have required property client documentation in generated google apis cloudtrace repo metadata json must have required property release level in generated google apis cloudtrace repo metadata json must have required property client documentation in generated google apis cloudtrace repo metadata json must have required property release level in generated google apis composer repo metadata json must have required property client documentation in generated google apis composer repo metadata json must have required property release level in generated google apis composer repo metadata json must have required property client documentation in generated google apis composer repo metadata json must have required property release level in generated google apis compute alpha repo metadata json must have required property client documentation in generated google apis compute alpha repo metadata json must have required property release level in generated google apis compute beta repo metadata json must have required property client documentation in generated google apis compute beta repo metadata json must have required property release level in generated google apis compute repo metadata json must have required property client documentation in generated google apis compute repo metadata json must have required property release level in generated google apis connectors repo metadata json must have required property client documentation in generated google apis connectors repo metadata json must have required property release level in generated google apis contactcenterinsights repo metadata json must have required property client documentation in generated google apis contactcenterinsights repo metadata json must have required property release level in generated google apis container repo metadata json must have required property client documentation in generated google apis container repo metadata json must have required property release level in generated google apis container repo metadata json must have required property client documentation in generated google apis container repo metadata json must have required property release level in generated google apis containeranalysis repo metadata json must have required property client documentation in generated google apis containeranalysis repo metadata json must have required property release level in generated google apis containeranalysis repo metadata json must have required property client documentation in generated google apis containeranalysis repo metadata json must have required property release level in generated google apis containeranalysis repo metadata json must have required property client documentation in generated google apis containeranalysis repo metadata json must have required property release level in generated google apis content repo metadata json must have required property client documentation in generated google apis content repo metadata json must have required property release level in generated google apis content repo metadata json must have required property client documentation in generated google apis content repo metadata json must have required property release level in generated google apis customsearch repo metadata json must have required property client documentation in generated google apis customsearch repo metadata json must have required property release level in generated google apis datacatalog repo metadata json must have required property client documentation in generated google apis datacatalog repo metadata json must have required property release level in generated google apis datacatalog repo metadata json must have required property client documentation in generated google apis datacatalog repo metadata json must have required property release level in generated google apis dataflow repo metadata json must have required property client documentation in generated google apis dataflow repo metadata json must have required property release level in generated google apis datafusion repo metadata json must have required property client documentation in generated google apis datafusion repo metadata json must have required property release level in generated google apis datafusion repo metadata json must have required property client documentation in generated google apis datafusion repo metadata json must have required property release level in generated google apis datalabeling repo metadata json must have required property client documentation in generated google apis datalabeling repo metadata json must have required property release level in generated google apis datamigration repo metadata json must have required property client documentation in generated google apis datamigration repo metadata json must have required property release level in generated google apis datamigration repo metadata json must have required property client documentation in generated google apis datamigration repo metadata json must have required property release level in generated google apis datapipelines repo metadata json must have required property client documentation in generated google apis datapipelines repo metadata json must have required property release level in generated google apis dataproc repo metadata json must have required property client documentation in generated google apis dataproc repo metadata json must have required property release level in generated google apis dataproc repo metadata json must have required property client documentation in generated google apis dataproc repo metadata json must have required property release level in generated google apis datastore repo metadata json must have required property client documentation in generated google apis datastore repo metadata json must have required property release level in generated google apis datastore repo metadata json must have required property client documentation in generated google apis datastore repo metadata json must have required property release level in generated google apis datastore repo metadata json must have required property client documentation in generated google apis datastore repo metadata json must have required property release level in generated google apis datastream repo metadata json must have required property client documentation in generated google apis datastream repo metadata json must have required property release level in generated google apis datastream repo metadata json must have required property client documentation in generated google apis datastream repo metadata json must have required property release level in generated google apis deploymentmanager alpha repo metadata json must have required property client documentation in generated google apis deploymentmanager alpha repo metadata json must have required property release level in generated google apis deploymentmanager repo metadata json must have required property client documentation in generated google apis deploymentmanager repo metadata json must have required property release level in generated google apis deploymentmanager repo metadata json must have required property client documentation in generated google apis deploymentmanager repo metadata json must have required property release level in generated google apis dfareporting repo metadata json must have required property client documentation in generated google apis dfareporting repo metadata json must have required property release level in generated google apis dfareporting repo metadata json must have required property client documentation in generated google apis dfareporting repo metadata json must have required property release level in generated google apis dfareporting repo metadata json must have required property client documentation in generated google apis dfareporting repo metadata json must have required property release level in generated google apis dialogflow repo metadata json must have required property client documentation in generated google apis dialogflow repo metadata json must have required property release level in generated google apis dialogflow repo metadata json must have required property client documentation in generated google apis dialogflow repo metadata json must have required property release level in generated google apis dialogflow repo metadata json must have required property client documentation in generated google apis dialogflow repo metadata json must have required property release level in generated google apis dialogflow repo metadata json must have required property client documentation in generated google apis dialogflow repo metadata json must have required property release level in generated google apis digitalassetlinks repo metadata json must have required property client documentation in generated google apis digitalassetlinks repo metadata json must have required property release level in generated google apis discovery repo metadata json must have required property client documentation in generated google apis discovery repo metadata json must have required property release level in generated google apis displayvideo repo metadata json must have required property client documentation in generated google apis displayvideo repo metadata json must have required property release level in generated google apis dlp repo metadata json must have required property client documentation in generated google apis dlp repo metadata json must have required property release level in generated google apis dns repo metadata json must have required property client documentation in generated google apis dns repo metadata json must have required property release level in generated google apis dns repo metadata json must have required property client documentation in generated google apis dns repo metadata json must have required property release level in generated google apis docs repo metadata json must have required property client documentation in generated google apis docs repo metadata json must have required property release level in generated google apis documentai repo metadata json must have required property client documentation in generated google apis documentai repo metadata json must have required property release level in generated google apis documentai repo metadata json must have required property client documentation in generated google apis documentai repo metadata json must have required property release level in generated google apis documentai repo metadata json must have required property client documentation in generated google apis documentai repo metadata json must have required property release level in generated google apis domains repo metadata json must have required property client documentation in generated google apis domains repo metadata json must have required property release level in generated google apis domains repo metadata json must have required property client documentation in generated google apis domains repo metadata json must have required property release level in generated google apis domains repo metadata json must have required property client documentation in generated google apis domains repo metadata json must have required property release level in generated google apis domainsrdap repo metadata json must have required property client documentation in generated google apis domainsrdap repo metadata json must have required property release level in generated google apis doubleclickbidmanager repo metadata json must have required property client documentation in generated google apis doubleclickbidmanager repo metadata json must have required property release level in generated google apis doubleclickbidmanager repo metadata json must have required property client documentation in generated google apis doubleclickbidmanager repo metadata json must have required property release level in generated google apis doubleclicksearch repo metadata json must have required property client documentation in generated google apis doubleclicksearch repo metadata json must have required property release level in generated google apis drive repo metadata json must have required property client documentation in generated google apis drive repo metadata json must have required property release level in generated google apis drive repo metadata json must have required property client documentation in generated google apis drive repo metadata json must have required property release level in generated google apis driveactivity repo metadata json must have required property client documentation in generated google apis driveactivity repo metadata json must have required property release level in generated google apis essentialcontacts repo metadata json must have required property client documentation in generated google apis essentialcontacts repo metadata json must have required property release level in generated google apis eventarc repo metadata json must have required property client documentation in generated google apis eventarc repo metadata json must have required property release level in generated google apis eventarc repo metadata json must have required property client documentation in generated google apis eventarc repo metadata json must have required property release level in generated google apis factchecktools repo metadata json must have required property client documentation in generated google apis factchecktools repo metadata json must have required property release level in generated google apis fcm repo metadata json must have required property client documentation in generated google apis fcm repo metadata json must have required property release level in generated google apis fcmdata repo metadata json must have required property client documentation in generated google apis fcmdata repo metadata json must have required property release level in generated google apis file repo metadata json must have required property client documentation in generated google apis file repo metadata json must have required property release level in generated google apis file repo metadata json must have required property client documentation in generated google apis file repo metadata json must have required property release level in generated google apis firebase repo metadata json must have required property client documentation in generated google apis firebase repo metadata json must have required property release level in generated google apis firebaseappcheck repo metadata json must have required property client documentation in generated google apis firebaseappcheck repo metadata json must have required property release level in generated google apis firebasedatabase repo metadata json must have required property client documentation in generated google apis firebasedatabase repo metadata json must have required property release level in generated google apis firebasedynamiclinks repo metadata json must have required property client documentation in generated google apis firebasedynamiclinks repo metadata json must have required property release level in generated google apis firebasehosting repo metadata json must have required property client documentation in generated google apis firebasehosting repo metadata json must have required property release level in generated google apis firebasehosting repo metadata json must have required property client documentation in generated google apis firebasehosting repo metadata json must have required property release level in generated google apis firebaseml repo metadata json must have required property client documentation in generated google apis firebaseml repo metadata json must have required property release level in generated google apis firebaseml repo metadata json must have required property client documentation in generated google apis firebaseml repo metadata json must have required property release level in generated google apis firebaserules repo metadata json must have required property client documentation in generated google apis firebaserules repo metadata json must have required property release level in generated google apis firebasestorage repo metadata json must have required property client documentation in generated google apis firebasestorage repo metadata json must have required property release level in generated google apis firestore repo metadata json must have required property client documentation in generated google apis firestore repo metadata json must have required property release level in generated google apis firestore repo metadata json must have required property client documentation in generated google apis firestore repo metadata json must have required property release level in generated google apis firestore repo metadata json must have required property client documentation in generated google apis firestore repo metadata json must have required property release level in generated google apis fitness repo metadata json must have required property client documentation in generated google apis fitness repo metadata json must have required property release level in generated google apis games configuration repo metadata json must have required property client documentation in generated google apis games configuration repo metadata json must have required property release level in generated google apis games management repo metadata json must have required property client documentation in generated google apis games management repo metadata json must have required property release level in generated google apis games repo metadata json must have required property client documentation in generated google apis games repo metadata json must have required property release level in generated google apis gameservices repo metadata json must have required property client documentation in generated google apis gameservices repo metadata json must have required property release level in generated google apis gameservices repo metadata json must have required property client documentation in generated google apis gameservices repo metadata json must have required property release level in generated google apis genomics repo metadata json must have required property client documentation in generated google apis genomics repo metadata json must have required property release level in generated google apis genomics repo metadata json must have required property client documentation in generated google apis genomics repo metadata json must have required property release level in generated google apis genomics repo metadata json must have required property client documentation in generated google apis genomics repo metadata json must have required property release level in generated google apis gkehub repo metadata json must have required property client documentation in generated google apis gkehub repo metadata json must have required property release level in generated google apis gkehub repo metadata json must have required property client documentation in generated google apis gkehub repo metadata json must have required property release level in generated google apis gkehub repo metadata json must have required property client documentation in generated google apis gkehub repo metadata json must have required property release level in generated google apis gkehub repo metadata json must have required property client documentation in generated google apis gkehub repo metadata json must have required property release level in generated google apis gkehub repo metadata json must have required property client documentation in generated google apis gkehub repo metadata json must have required property release level in generated google apis gmail repo metadata json must have required property client documentation in generated google apis gmail repo metadata json must have required property release level in generated google apis gmailpostmastertools repo metadata json must have required property client documentation in generated google apis gmailpostmastertools repo metadata json must have required property release level in generated google apis gmailpostmastertools repo metadata json must have required property client documentation in generated google apis gmailpostmastertools repo metadata json must have required property release level in generated google apis groupsmigration repo metadata json must have required property client documentation in generated google apis groupsmigration repo metadata json must have required property release level in generated google apis groupssettings repo metadata json must have required property client documentation in generated google apis groupssettings repo metadata json must have required property release level in generated google apis healthcare repo metadata json must have required property client documentation in generated google apis healthcare repo metadata json must have required property release level in generated google apis healthcare repo metadata json must have required property client documentation in generated google apis healthcare repo metadata json must have required property release level in generated google apis homegraph repo metadata json must have required property client documentation in generated google apis homegraph repo metadata json must have required property release level in generated google apis iam repo metadata json must have required property client documentation in generated google apis iam repo metadata json must have required property release level in generated google apis iamcredentials repo metadata json must have required property client documentation in generated google apis iamcredentials repo metadata json must have required property release level in generated google apis iap repo metadata json must have required property client documentation in generated google apis iap repo metadata json must have required property release level in generated google apis iap repo metadata json must have required property client documentation in generated google apis iap repo metadata json must have required property release level in generated google apis ideahub repo metadata json must have required property client documentation in generated google apis ideahub repo metadata json must have required property release level in generated google apis ideahub repo metadata json must have required property client documentation in generated google apis ideahub repo metadata json must have required property release level in generated google apis identitytoolkit repo metadata json must have required property client documentation in generated google apis identitytoolkit repo metadata json must have required property release level in generated google apis indexing repo metadata json must have required property client documentation in generated google apis indexing repo metadata json must have required property release level in generated google apis jobs repo metadata json must have required property client documentation in generated google apis jobs repo metadata json must have required property release level in generated google apis jobs repo metadata json must have required property client documentation in generated google apis jobs repo metadata json must have required property release level in generated google apis jobs repo metadata json must have required property client documentation in generated google apis jobs repo metadata json must have required property release level in generated google apis keep repo metadata json must have required property client documentation in generated google apis keep repo metadata json must have required property release level in generated google apis kgsearch repo metadata json must have required property client documentation in generated google apis kgsearch repo metadata json must have required property release level in generated google apis language repo metadata json must have required property client documentation in generated google apis language repo metadata json must have required property release level in generated google apis language repo metadata json must have required property client documentation in generated google apis language repo metadata json must have required property release level in generated google apis language repo metadata json must have required property client documentation in generated google apis language repo metadata json must have required property release level in generated google apis libraryagent repo metadata json must have required property client documentation in generated google apis libraryagent repo metadata json must have required property release level in generated google apis licensing repo metadata json must have required property client documentation in generated google apis licensing repo metadata json must have required property release level in generated google apis lifesciences repo metadata json must have required property client documentation in generated google apis lifesciences repo metadata json must have required property release level in generated google apis localservices repo metadata json must have required property client documentation in generated google apis localservices repo metadata json must have required property release level in generated google apis logging repo metadata json must have required property client documentation in generated google apis logging repo metadata json must have required property release level in generated google apis managedidentities repo metadata json must have required property client documentation in generated google apis managedidentities repo metadata json must have required property release level in generated google apis managedidentities repo metadata json must have required property client documentation in generated google apis managedidentities repo metadata json must have required property release level in generated google apis managedidentities repo metadata json must have required property client documentation in generated google apis managedidentities repo metadata json must have required property release level in generated google apis manufacturers repo metadata json must have required property client documentation in generated google apis manufacturers repo metadata json must have required property release level in generated google apis memcache repo metadata json must have required property client documentation in generated google apis memcache repo metadata json must have required property release level in generated google apis memcache repo metadata json must have required property client documentation in generated google apis memcache repo metadata json must have required property release level in generated google apis metastore repo metadata json must have required property client documentation in generated google apis metastore repo metadata json must have required property release level in generated google apis metastore repo metadata json must have required property client documentation in generated google apis metastore repo metadata json must have required property release level in generated google apis ml repo metadata json must have required property client documentation in generated google apis ml repo metadata json must have required property release level in generated google apis monitoring repo metadata json must have required property client documentation in generated google apis monitoring repo metadata json must have required property release level in generated google apis monitoring repo metadata json must have required property client documentation in generated google apis monitoring repo metadata json must have required property release level in generated google apis mybusinessaccountmanagement repo metadata json must have required property client documentation in generated google apis mybusinessaccountmanagement repo metadata json must have required property release level in generated google apis mybusinessbusinessinformation repo metadata json must have required property client documentation in generated google apis mybusinessbusinessinformation repo metadata json must have required property release level in generated google apis mybusinesslodging repo metadata json must have required property client documentation in generated google apis mybusinesslodging repo metadata json must have required property release level in generated google apis mybusinessnotifications repo metadata json must have required property client documentation in generated google apis mybusinessnotifications repo metadata json must have required property release level in generated google apis mybusinessplaceactions repo metadata json must have required property client documentation in generated google apis mybusinessplaceactions repo metadata json must have required property release level in generated google apis mybusinessqanda repo metadata json must have required property client documentation in generated google apis mybusinessqanda repo metadata json must have required property release level in generated google apis mybusinessverifications repo metadata json must have required property client documentation in generated google apis mybusinessverifications repo metadata json must have required property release level in generated google apis networkconnectivity repo metadata json must have required property client documentation in generated google apis networkconnectivity repo metadata json must have required property release level in generated google apis networkconnectivity repo metadata json must have required property client documentation in generated google apis networkconnectivity repo metadata json must have required property release level in generated google apis networkmanagement repo metadata json must have required property client documentation in generated google apis networkmanagement repo metadata json must have required property release level in generated google apis networkmanagement repo metadata json must have required property client documentation in generated google apis networkmanagement repo metadata json must have required property release level in generated google apis networksecurity repo metadata json must have required property client documentation in generated google apis networksecurity repo metadata json must have required property release level in generated google apis networksecurity repo metadata json must have required property client documentation in generated google apis networksecurity repo metadata json must have required property release level in generated google apis networkservices repo metadata json must have required property client documentation in generated google apis networkservices repo metadata json must have required property release level in generated google apis networkservices repo metadata json must have required property client documentation in generated google apis networkservices repo metadata json must have required property release level in generated google apis notebooks repo metadata json must have required property client documentation in generated google apis notebooks repo metadata json must have required property release level in generated google apis repo metadata json must have required property client documentation in generated google apis repo metadata json must have required property release level in generated google apis ondemandscanning repo metadata json must have required property client documentation in generated google apis ondemandscanning repo metadata json must have required property release level in generated google apis ondemandscanning repo metadata json must have required property client documentation in generated google apis ondemandscanning repo metadata json must have required property release level in generated google apis orgpolicy repo metadata json must have required property client documentation in generated google apis orgpolicy repo metadata json must have required property release level in generated google apis osconfig repo metadata json must have required property client documentation in generated google apis osconfig repo metadata json must have required property release level in generated google apis osconfig repo metadata json must have required property client documentation in generated google apis osconfig repo metadata json must have required property release level in generated google apis osconfig repo metadata json must have required property client documentation in generated google apis osconfig repo metadata json must have required property release level in generated google apis oslogin repo metadata json must have required property client documentation in generated google apis oslogin repo metadata json must have required property release level in generated google apis oslogin repo metadata json must have required property client documentation in generated google apis oslogin repo metadata json must have required property release level in generated google apis oslogin repo metadata json must have required property client documentation in generated google apis oslogin repo metadata json must have required property release level in generated google apis pagespeedonline repo metadata json must have required property client documentation in generated google apis pagespeedonline repo metadata json must have required property release level in generated google apis paymentsresellersubscription repo metadata json must have required property client documentation in generated google apis paymentsresellersubscription repo metadata json must have required property release level in generated google apis people repo metadata json must have required property client documentation in generated google apis people repo metadata json must have required property release level in generated google apis playablelocations repo metadata json must have required property client documentation in generated google apis playablelocations repo metadata json must have required property release level in generated google apis playcustomapp repo metadata json must have required property client documentation in generated google apis playcustomapp repo metadata json must have required property release level in generated google apis policyanalyzer repo metadata json must have required property client documentation in generated google apis policyanalyzer repo metadata json must have required property release level in generated google apis policyanalyzer repo metadata json must have required property client documentation in generated google apis policyanalyzer repo metadata json must have required property release level in generated google apis policysimulator repo metadata json must have required property client documentation in generated google apis policysimulator repo metadata json must have required property release level in generated google apis policysimulator repo metadata json must have required property client documentation in generated google apis policysimulator repo metadata json must have required property release level in generated google apis policytroubleshooter repo metadata json must have required property client documentation in generated google apis policytroubleshooter repo metadata json must have required property release level in generated google apis policytroubleshooter repo metadata json must have required property client documentation in generated google apis policytroubleshooter repo metadata json must have required property release level in generated google apis poly repo metadata json must have required property client documentation in generated google apis poly repo metadata json must have required property release level in generated google apis privateca repo metadata json must have required property client documentation in generated google apis privateca repo metadata json must have required property release level in generated google apis privateca repo metadata json must have required property client documentation in generated google apis privateca repo metadata json must have required property release level in generated google apis prod tt sasportal repo metadata json must have required property client documentation in generated google apis prod tt sasportal repo metadata json must have required property release level in generated google apis pubsub repo metadata json must have required property client documentation in generated google apis pubsub repo metadata json must have required property release level in generated google apis pubsub repo metadata json must have required property client documentation in generated google apis pubsub repo metadata json must have required property release level in generated google apis pubsub repo metadata json must have required property client documentation in generated google apis pubsub repo metadata json must have required property release level in generated google apis pubsublite repo metadata json must have required property client documentation in generated google apis pubsublite repo metadata json must have required property release level in generated google apis realtimebidding repo metadata json must have required property client documentation in generated google apis realtimebidding repo metadata json must have required property release level in generated google apis realtimebidding repo metadata json must have required property client documentation in generated google apis realtimebidding repo metadata json must have required property release level in generated google apis recaptchaenterprise repo metadata json must have required property client documentation in generated google apis recaptchaenterprise repo metadata json must have required property release level in generated google apis recommendationengine repo metadata json must have required property client documentation in generated google apis recommendationengine repo metadata json must have required property release level in generated google apis recommender repo metadata json must have required property client documentation in generated google apis recommender repo metadata json must have required property release level in generated google apis recommender repo metadata json must have required property client documentation in generated google apis recommender repo metadata json must have required property release level in generated google apis redis repo metadata json must have required property client documentation in generated google apis redis repo metadata json must have required property release level in generated google apis redis repo metadata json must have required property client documentation in generated google apis redis repo metadata json must have required property release level in generated google apis remotebuildexecution repo metadata json must have required property client documentation in generated google apis remotebuildexecution repo metadata json must have required property release level in generated google apis remotebuildexecution repo metadata json must have required property client documentation in generated google apis remotebuildexecution repo metadata json must have required property release level in generated google apis remotebuildexecution repo metadata json must have required property client documentation in generated google apis remotebuildexecution repo metadata json must have required property release level in generated google apis reseller repo metadata json must have required property client documentation in generated google apis reseller repo metadata json must have required property release level in generated google apis resourcesettings repo metadata json must have required property client documentation in generated google apis resourcesettings repo metadata json must have required property release level in generated google apis retail repo metadata json must have required property client documentation in generated google apis retail repo metadata json must have required property release level in generated google apis retail repo metadata json must have required property client documentation in generated google apis retail repo metadata json must have required property release level in generated google apis retail repo metadata json must have required property client documentation in generated google apis retail repo metadata json must have required property release level in generated google apis run repo metadata json must have required property client documentation in generated google apis run repo metadata json must have required property release level in generated google apis run repo metadata json must have required property client documentation in generated google apis run repo metadata json must have required property release level in generated google apis run repo metadata json must have required property client documentation in generated google apis run repo metadata json must have required property release level in generated google apis run repo metadata json must have required property client documentation in generated google apis run repo metadata json must have required property release level in generated google apis runtimeconfig repo metadata json must have required property client documentation in generated google apis runtimeconfig repo metadata json must have required property release level in generated google apis runtimeconfig repo metadata json must have required property client documentation in generated google apis runtimeconfig repo metadata json must have required property release level in generated google apis safebrowsing repo metadata json must have required property client documentation in generated google apis safebrowsing repo metadata json must have required property release level in generated google apis sasportal repo metadata json must have required property client documentation in generated google apis sasportal repo metadata json must have required property release level in generated google apis script repo metadata json must have required property client documentation in generated google apis script repo metadata json must have required property release level in generated google apis searchconsole repo metadata json must have required property client documentation in generated google apis searchconsole repo metadata json must have required property release level in generated google apis secretmanager repo metadata json must have required property client documentation in generated google apis secretmanager repo metadata json must have required property release level in generated google apis secretmanager repo metadata json must have required property client documentation in generated google apis secretmanager repo metadata json must have required property release level in generated google apis securitycenter repo metadata json must have required property client documentation in generated google apis securitycenter repo metadata json must have required property release level in generated google apis securitycenter repo metadata json must have required property client documentation in generated google apis securitycenter repo metadata json must have required property release level in generated google apis securitycenter repo metadata json must have required property client documentation in generated google apis securitycenter repo metadata json must have required property release level in generated google apis serviceconsumermanagement repo metadata json must have required property client documentation in generated google apis serviceconsumermanagement repo metadata json must have required property release level in generated google apis serviceconsumermanagement repo metadata json must have required property client documentation in generated google apis serviceconsumermanagement repo metadata json must have required property release level in generated google apis servicecontrol repo metadata json must have required property client documentation in generated google apis servicecontrol repo metadata json must have required property release level in generated google apis servicecontrol repo metadata json must have required property client documentation in generated google apis servicecontrol repo metadata json must have required property release level in generated google apis servicedirectory repo metadata json must have required property client documentation in generated google apis servicedirectory repo metadata json must have required property release level in generated google apis servicedirectory repo metadata json must have required property client documentation in generated google apis servicedirectory repo metadata json must have required property release level in generated google apis servicemanagement repo metadata json must have required property client documentation in generated google apis servicemanagement repo metadata json must have required property release level in generated google apis servicenetworking repo metadata json must have required property client documentation in generated google apis servicenetworking repo metadata json must have required property release level in generated google apis servicenetworking repo metadata json must have required property client documentation in generated google apis servicenetworking repo metadata json must have required property release level in generated google apis serviceusage repo metadata json must have required property client documentation in generated google apis serviceusage repo metadata json must have required property release level in generated google apis serviceusage repo metadata json must have required property client documentation in generated google apis serviceusage repo metadata json must have required property release level in generated google apis sheets repo metadata json must have required property client documentation in generated google apis sheets repo metadata json must have required property release level in generated google apis site verification repo metadata json must have required property client documentation in generated google apis site verification repo metadata json must have required property release level in generated google apis slides repo metadata json must have required property client documentation in generated google apis slides repo metadata json must have required property release level in generated google apis smartdevicemanagement repo metadata json must have required property client documentation in generated google apis smartdevicemanagement repo metadata json must have required property release level in generated google apis sourcerepo repo metadata json must have required property client documentation in generated google apis sourcerepo repo metadata json must have required property release level in generated google apis spanner repo metadata json must have required property client documentation in generated google apis spanner repo metadata json must have required property release level in generated google apis speech repo metadata json must have required property client documentation in generated google apis speech repo metadata json must have required property release level in generated google apis speech repo metadata json must have required property client documentation in generated google apis speech repo metadata json must have required property release level in generated google apis speech repo metadata json must have required property client documentation in generated google apis speech repo metadata json must have required property release level in generated google apis sqladmin repo metadata json must have required property client documentation in generated google apis sqladmin repo metadata json must have required property release level in generated google apis sqladmin repo metadata json must have required property client documentation in generated google apis sqladmin repo metadata json must have required property release level in generated google apis storage repo metadata json must have required property client documentation in generated google apis storage repo metadata json must have required property release level in generated google apis storagetransfer repo metadata json must have required property client documentation in generated google apis storagetransfer repo metadata json must have required property release level in generated google apis streetviewpublish repo metadata json must have required property client documentation in generated google apis streetviewpublish repo metadata json must have required property release level in generated google apis sts repo metadata json must have required property client documentation in generated google apis sts repo metadata json must have required property release level in generated google apis sts repo metadata json must have required property client documentation in generated google apis sts repo metadata json must have required property release level in generated google apis tagmanager repo metadata json must have required property client documentation in generated google apis tagmanager repo metadata json must have required property release level in generated google apis tagmanager repo metadata json must have required property client documentation in generated google apis tagmanager repo metadata json must have required property release level in generated google apis tasks repo metadata json must have required property client documentation in generated google apis tasks repo metadata json must have required property release level in generated google apis testing repo metadata json must have required property client documentation in generated google apis testing repo metadata json must have required property release level in generated google apis texttospeech repo metadata json must have required property client documentation in generated google apis texttospeech repo metadata json must have required property release level in generated google apis texttospeech repo metadata json must have required property client documentation in generated google apis texttospeech repo metadata json must have required property release level in generated google apis toolresults repo metadata json must have required property client documentation in generated google apis toolresults repo metadata json must have required property release level in generated google apis tpu repo metadata json must have required property client documentation in generated google apis tpu repo metadata json must have required property release level in generated google apis tpu repo metadata json must have required property client documentation in generated google apis tpu repo metadata json must have required property release level in generated google apis tpu repo metadata json must have required property client documentation in generated google apis tpu repo metadata json must have required property release level in generated google apis trafficdirector repo metadata json must have required property client documentation in generated google apis trafficdirector repo metadata json must have required property release level in generated google apis transcoder repo metadata json must have required property client documentation in generated google apis transcoder repo metadata json must have required property release level in generated google apis transcoder repo metadata json must have required property client documentation in generated google apis transcoder repo metadata json must have required property release level in generated google apis translate repo metadata json must have required property client documentation in generated google apis translate repo metadata json must have required property release level in generated google apis translate repo metadata json must have required property client documentation in generated google apis translate repo metadata json must have required property release level in generated google apis translate repo metadata json must have required property client documentation in generated google apis translate repo metadata json must have required property release level in generated google apis vault repo metadata json must have required property client documentation in generated google apis vault repo metadata json must have required property release level in generated google apis vectortile repo metadata json must have required property client documentation in generated google apis vectortile repo metadata json must have required property release level in generated google apis verifiedaccess repo metadata json must have required property client documentation in generated google apis verifiedaccess repo metadata json must have required property release level in generated google apis versionhistory repo metadata json must have required property client documentation in generated google apis versionhistory repo metadata json must have required property release level in generated google apis videointelligence repo metadata json must have required property client documentation in generated google apis videointelligence repo metadata json must have required property release level in generated google apis videointelligence repo metadata json must have required property client documentation in generated google apis videointelligence repo metadata json must have required property release level in generated google apis videointelligence repo metadata json must have required property client documentation in generated google apis videointelligence repo metadata json must have required property release level in generated google apis videointelligence repo metadata json must have required property client documentation in generated google apis videointelligence repo metadata json must have required property release level in generated google apis videointelligence repo metadata json must have required property client documentation in generated google apis videointelligence repo metadata json must have required property release level in generated google apis vision repo metadata json must have required property client documentation in generated google apis vision repo metadata json must have required property release level in generated google apis vision repo metadata json must have required property client documentation in generated google apis vision repo metadata json must have required property release level in generated google apis vision repo metadata json must have required property client documentation in generated google apis vision repo metadata json must have required property release level in generated google apis vmmigration repo metadata json must have required property client documentation in generated google apis vmmigration repo metadata json must have required property release level in generated google apis vmmigration repo metadata json must have required property client documentation in generated google apis vmmigration repo metadata json must have required property release level in generated google apis webfonts repo metadata json must have required property client documentation in generated google apis webfonts repo metadata json must have required property release level in generated google apis webmasters repo metadata json must have required property client documentation in generated google apis webmasters repo metadata json must have required property release level in generated google apis webrisk repo metadata json must have required property client documentation in generated google apis webrisk repo metadata json must have required property release level in generated google apis websecurityscanner repo metadata json must have required property client documentation in generated google apis websecurityscanner repo metadata json must have required property release level in generated google apis websecurityscanner repo metadata json must have required property client documentation in generated google apis websecurityscanner repo metadata json must have required property release level in generated google apis websecurityscanner repo metadata json must have required property client documentation in generated google apis websecurityscanner repo metadata json must have required property release level in generated google apis workflowexecutions repo metadata json must have required property client documentation in generated google apis workflowexecutions repo metadata json must have required property release level in generated google apis workflowexecutions repo metadata json must have required property client documentation in generated google apis workflowexecutions repo metadata json must have required property release level in generated google apis workflows repo metadata json must have required property client documentation in generated google apis workflows repo metadata json must have required property release level in generated google apis workflows repo metadata json must have required property client documentation in generated google apis workflows repo metadata json must have required property release level in generated google apis youtube analytics repo metadata json must have required property client documentation in generated google apis youtube analytics repo metadata json must have required property release level in generated google apis youtube repo metadata json must have required property client documentation in generated google apis youtube repo metadata json must have required property release level in generated google apis youtubereporting repo metadata json must have required property client documentation in generated google apis youtubereporting repo metadata json must have required property release level in google api client repo metadata json must have required property client documentation in google api client repo metadata json must have required property release level in google apis core repo metadata json must have required property client documentation in google apis core repo metadata json must have required property release level in google apis generator repo metadata json must have required property client documentation in google apis generator repo metadata json ☝️ once you address these problems you can close this issue need help lists valid options for each field for grpc libraries api shortname should match the subdomain of an api s hostname reach out to go github automation if you have any questions
| 1
|
12,157
| 14,741,458,292
|
IssuesEvent
|
2021-01-07 10:39:07
|
kdjstudios/SABillingGitlab
|
https://api.github.com/repos/kdjstudios/SABillingGitlab
|
closed
|
SA Billing - Laser - Invalid Late Fees
|
anc-process anp-1 ant-bug has attachment
|
In GitLab by @kdjstudios on Jan 21, 2019, 13:22
**Submitted by:** Sharon Carver <scarver@laseranswering.com>
**Helpdesk:** http://www.servicedesk.answernet.com/profiles/ticket/6612309
**Server:** External
**Client/Site:** Laser
**Account:** NA
**Issue:**
I have determined only two are invalid. Please see the attached. Please use code 999 for late fee credit.
[late+fee+error+2019-01-15.xlsx](/uploads/f3ab21db71837921f608dff20d276dbe/late+fee+error+2019-01-15.xlsx)
|
1.0
|
SA Billing - Laser - Invalid Late Fees - In GitLab by @kdjstudios on Jan 21, 2019, 13:22
**Submitted by:** Sharon Carver <scarver@laseranswering.com>
**Helpdesk:** http://www.servicedesk.answernet.com/profiles/ticket/6612309
**Server:** External
**Client/Site:** Laser
**Account:** NA
**Issue:**
I have determined only two are invalid. Please see the attached. Please use code 999 for late fee credit.
[late+fee+error+2019-01-15.xlsx](/uploads/f3ab21db71837921f608dff20d276dbe/late+fee+error+2019-01-15.xlsx)
|
process
|
sa billing laser invalid late fees in gitlab by kdjstudios on jan submitted by sharon carver helpdesk server external client site laser account na issue i have determined only two are invalid please see the attached please use code for late fee credit uploads late fee error xlsx
| 1
|
795
| 3,275,398,486
|
IssuesEvent
|
2015-10-26 15:26:26
|
hammerlab/pileup.js
|
https://api.github.com/repos/hammerlab/pileup.js
|
closed
|
Try out Babel
|
process
|
It's an alternative to react-tools which supports JSX & significantly more of ES6: https://babeljs.io/docs/compare/
|
1.0
|
Try out Babel - It's an alternative to react-tools which supports JSX & significantly more of ES6: https://babeljs.io/docs/compare/
|
process
|
try out babel it s an alternative to react tools which supports jsx significantly more of
| 1
|
6,515
| 9,604,538,787
|
IssuesEvent
|
2019-05-10 20:19:32
|
robertwpaul/lintol-challenge-1
|
https://api.github.com/repos/robertwpaul/lintol-challenge-1
|
closed
|
Add Date of Birth Processor
|
good first issue processor
|
Create a suitable regex, library, or implementation to find dates that may be identified as date of births.
Example PR: https://github.com/robertwpaul/lintol-challenge-1/pull/33
**Acceptance Criteria**
* Adds a processor
* Adds unit tests
* Adds a processor specific doc/
* Links processor to README.md
|
1.0
|
Add Date of Birth Processor - Create a suitable regex, library, or implementation to find dates that may be identified as date of births.
Example PR: https://github.com/robertwpaul/lintol-challenge-1/pull/33
**Acceptance Criteria**
* Adds a processor
* Adds unit tests
* Adds a processor specific doc/
* Links processor to README.md
|
process
|
add date of birth processor create a suitable regex library or implementation to find dates that may be identified as date of births example pr acceptance criteria adds a processor adds unit tests adds a processor specific doc links processor to readme md
| 1
|
8,618
| 11,772,789,990
|
IssuesEvent
|
2020-03-16 05:14:49
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
opened
|
`yarn clean-deps` requires `yarn install`
|
process: contributing stage: proposal 💡 type: chore
|
### Current behavior:
If my `yarn install` is completely messed up - I want to be able to clean up my node_modules, but the `yarn clean` script requires that `lerna` be installed which is pretty counterintuitive.
### Desired behavior:
A `clean-deps` script should never require actual node_modules be installed that you need to clean.
### Test code to reproduce
mess up your install somehow
`yarn clean-deps`
<img width="693" alt="Screen Shot 2020-03-16 at 11 42 42 AM" src="https://user-images.githubusercontent.com/1271364/76725052-5ef56400-677b-11ea-9d79-9a63cd4a6280.png">
### Versions
4.1.0
|
1.0
|
`yarn clean-deps` requires `yarn install` - ### Current behavior:
If my `yarn install` is completely messed up - I want to be able to clean up my node_modules, but the `yarn clean` script requires that `lerna` be installed which is pretty counterintuitive.
### Desired behavior:
A `clean-deps` script should never require actual node_modules be installed that you need to clean.
### Test code to reproduce
mess up your install somehow
`yarn clean-deps`
<img width="693" alt="Screen Shot 2020-03-16 at 11 42 42 AM" src="https://user-images.githubusercontent.com/1271364/76725052-5ef56400-677b-11ea-9d79-9a63cd4a6280.png">
### Versions
4.1.0
|
process
|
yarn clean deps requires yarn install current behavior if my yarn install is completely messed up i want to be able to clean up my node modules but the yarn clean script requires that lerna be installed which is pretty counterintuitive desired behavior a clean deps script should never require actual node modules be installed that you need to clean test code to reproduce mess up your install somehow yarn clean deps img width alt screen shot at am src versions
| 1
|
89,002
| 17,770,661,832
|
IssuesEvent
|
2021-08-30 13:18:39
|
lgbarrere/CNF-SAT_to_ILP_converter
|
https://api.github.com/repos/lgbarrere/CNF-SAT_to_ILP_converter
|
closed
|
Add the conversion time for ILPs in the histogram
|
Code Medium priority
|
- [x] If a SAT formula has been converted into ILP, the conversion time must be saved
- [x] Display the conversion time in the histogram (stack the execution time on it)
|
1.0
|
Add the conversion time for ILPs in the histogram - - [x] If a SAT formula has been converted into ILP, the conversion time must be saved
- [x] Display the conversion time in the histogram (stack the execution time on it)
|
non_process
|
add the conversion time for ilps in the histogram if a sat formula has been converted into ilp the conversion time must be saved display the conversion time in the histogram stack the execution time on it
| 0
|
13,239
| 15,707,560,508
|
IssuesEvent
|
2021-03-26 19:04:32
|
edwardsmarc/CASFRI
|
https://api.github.com/repos/edwardsmarc/CASFRI
|
closed
|
Make TT_SplitByGrid() parallel safe if possible
|
blocker enhancement post-translation process
|
Producing the gridded version of the database is just too long.
|
1.0
|
Make TT_SplitByGrid() parallel safe if possible - Producing the gridded version of the database is just too long.
|
process
|
make tt splitbygrid parallel safe if possible producing the gridded version of the database is just too long
| 1
|
804,208
| 29,479,083,524
|
IssuesEvent
|
2023-06-02 02:47:37
|
Progressive-Victory/crm-bot
|
https://api.github.com/repos/Progressive-Victory/crm-bot
|
closed
|
List people in Region
|
feature good first issue priority: MEDIUM
|
We should list everybody with the provided role, but the most utility this has is for state roles. The output should be a raw csv file which is just a fancy way of saying a comma-separated text file.
|
1.0
|
List people in Region - We should list everybody with the provided role, but the most utility this has is for state roles. The output should be a raw csv file which is just a fancy way of saying a comma-separated text file.
|
non_process
|
list people in region we should list everybody with the provided role but the most utility this has is for state roles the output should be a raw csv file which is just a fancy way of saying a comma separated text file
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.