docs(website): fix duplicated docs page title

https://taiko.xyz/docs/reference/contract-documentation/L1/ProofVerifier

This PR removes the duplicated and useless page title item and changes the page title from IProofVerifier to IProofVerifier & ProofVerifier .

@hairtail thanks for your contribution ❤
for auto-generated documentation, we do not want to manually edit any of these files. the contents of these files should always be the result of running the command: pnpm -F protocol export:docs. so, to fix this, we need to fix the handlebars template which parses the solidity files and generates the documentation, by removing the "title".
i created the branch showing you how to properly make the change, if you'd like: https://github.com/taikoxyz/taiko-mono/compare/fix-autogen-docs-remove-title?expand=1

https://github.com/taikoxyz/taiko-mono/compare/fix-autogen-docs-remove-title?expand=1#diff-3da56a5075c69802eb977f423c3f3d6a717e109efbed0e5d49ea2d943842fac2L1 -- remove "title" from the handlebars template
run pnpm -F protocol export:docs from the monorepo

please see my comment for the requested changes

Thanks for reply. I will update this PR with these comments and changes.

please see my comment for the requested changes

Updated.


this noun is feminine

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

this noun is feminine

this noun is feminine

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

@FedofS Thank you for  creating this PR.  However, since it was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you.

We are restructuring a lot of the code and learning resources referenced in your pull request, so for now I am going to go ahead and close this pull request. Thanks again for opening this pull request and for contributing to the community.


Getjob options [NOHANG, WITHCOUNTERS]

Currently the getjob command doesn't those two options supported by upstream. I think these can be added much the same way addjob's options are hacked on, but not sure what the best option for doing that is.
I can work on a PR if we figure out a good way to do this. :)

Thanks for the issue. +1 for GetJobArgs with a builder and adding a getjob/getjobs which accepts GetJobArgs, Queues. getjob and getjobs with the timeout options can be @Deprecated and then the API feels more consistent again.
PR's are always welcome.

I'll take a look - no promises but hope to have a PR out in the next couple of days. :+1:

Hrm. Started implementing the solution but ran into a blocker - namely I'm not sure what a good API for this will be. I'll jot down my ideas below, I'd be curious to hear your feedback.
For reference, the command syntax is GETJOB [NOHANG] [TIMEOUT <ms-timeout>] [COUNT <count>] [WITHCOUNTERS] FROM queue1 queue2 ... queueN
And the current getjob api (DisqueJobAsyncCommands) is:
RedisFuture<Job<K, V>> getjob(K queue);
RedisFuture<Job<K, V>> getjob(long timeout, TimeUnit timeUnit, K queue);

RedisFuture<List<Job<K, V>>> getjobs(K... queues);
RedisFuture<List<Job<K, V>>> getjobs(long timeout, TimeUnit timeUnit, long count, K... queues);

So an obvious improvement would be to add to those two options:
RedisFuture<Job<K, V>> getjob(GetJobArgs getJobArgs, K queue);

RedisFuture<List<Job<K, V>>> getjobs(long count, GetJobArgs getJobArgs, K... queues);

However, an annoying bit with the first is that the returned job can be NULL - would that be an acceptable trade-off given it's documented?

As for the WITHCOUNTERS flag, I think an extra field in the Job object might be enough which will be NULL if the flag was not set in GetJobArgs.
The problem with this is that it's sure to bite someone that it's not set and java doesn't have Option to make it clear it's nullable - is there any other way we can signal that this is only set if the WITHCOUNTERS flag is passed.

Thanks for your input. The issue we're facing right now is related to strong typing. The Disque (and previously Redis) API returns data/data structures that depends on the command args (refer to http://redis.io/commands/georadius). Drawing all permutations of the command args as API causes a lot of methods. The lettuce client does this for certain commands (RedisSortedSetsConnection) which highly depend on the result type.
Viewing the API from a different perspective: When using the API, you are either happy with the simple approach getjob(K queue)/getjobs(long count, K... queues) or you head for the advanced call getjobs(GetJobsArgs getJobsArgs, K... queues). So maybe just adding a getjobs(GetJobsArgs getJobsArgs, K... queues) method for the initial support. I'm not decided and not fully sure about a particular solution.
About the WITHCOUNTERS options: I'm not sure. Having the counters in the Job data structure is one option (similar to GeoWithin). A JobWithCounters is another option (similar to ScoredValue it would be getjobsWithCounters). WITHCOUNTERS implies some potential to grow and return more fields than it has now. Maybe a Map<String, Number> within Job that is empty when the counters are not requested.
Does this makes sense?
Keep in mind, spinach is Java 1.6 compatible and should not use (yet) Java 1.8 on the API. I'm also still fighting with myself to get rid of Google Guava or not since it causes sometimes more trouble than value.

Implemented with #15


Broken check for '.quipelements.com' domains

Just stumbled upon the following lines of code in your index.html. The third line was probably supposed to be connected with ||:
https://github.com/jgraph/drawio/blob/c063d9f03c0308f44c6a2d3461c7ab1f9e698654/src/main/webapp/index.html#L291-L293

Thanks for the report. This will be fixed in the next release.


Error in Notebook: infer_faster_whisper_large_v2.ipynb

Hi,
First of all: Thank you for sharing something that makes life easier for people.
I find your project very interesting, therefore I tried to run the demo notebook in a T4 runtime on colab.
But appears "RuntimeError: Library libcublas.so.11 is not found or cannot be loaded" in Notebook: "infer_faster_whisper_large_v2.ipynb".
in the execution of the cell (in step 5) (shows up from the date 12-13-2023):
segments, info = model.transcribe("sam_altman_lex_podcast_367.flac", beam_size=1)
print("Detected language '%s' with probability %f" % (info.language, info.language_probability))

This is the error:
RuntimeError                              Traceback (most recent call last)
<ipython-input-5-5b56465b1fbe> in <cell line: 1>()
----> 1 segments, info = model.transcribe("sam_altman_lex_podcast_367.flac", beam_size=1)
      2
      3 print("Detected language '%s' with probability %f" % (info.language, info.language_probability))

1 frames
/usr/local/lib/python3.10/dist-packages/faster_whisper/transcribe.py in transcribe(self, audio, language, task, beam_size, best_of, patience, length_penalty, repetition_penalty, no_repeat_ngram_size, temperature, compression_ratio_threshold, log_prob_threshold, no_speech_threshold, condition_on_previous_text, prompt_reset_on_temperature, initial_prompt, prefix, suppress_blank, suppress_tokens, without_timestamps, max_initial_timestamp, word_timestamps, prepend_punctuations, append_punctuations, vad_filter, vad_parameters)
    325             else:
    326                 segment = features[:, : self.feature_extractor.nb_max_frames]
--> 327                 encoder_output = self.encode(segment)
    328                 # results is a list of tuple[str, float] with language names and
    329                 # probabilities.

/usr/local/lib/python3.10/dist-packages/faster_whisper/transcribe.py in encode(self, features)
    627         features = get_ctranslate2_storage(features)
    628
--> 629         return self.model.encode(features, to_cpu=to_cpu)
    630
    631     def generate_with_fallback(

RuntimeError: Library libcublas.so.11 is not found or cannot be loaded

I am grateful for your help...

Hi @riffov - the notebook you are referring to was used for benchmarks. If you want to use the CLi then I'd recommend using this Colab notebook: https://github.com/Vaibhavs10/insanely-fast-whisper/blob/main/insanely_fast_whisper_colab.ipynb
(closing this for now, feel free to re-open if you have any questions)


implemented kafka support using new project zeebe-exporter-source

re-did https://github.com/zeebe-io/zeebe-simple-monitor/pull/183 based on a new project
https://github.com/cameronbraid/zeebe-exporter-source
Depends on zeebe-io/zeebe-kafka-exporter#35
Implemented integration test using kafka+protobuf

This requires slight changes to the configuration
To enable hazelcast
zeebe.exporter.source.hazelcast:
  enabled: true
  connection: localhost:5701
  connectionTimeout: PT30S

to enable kafka
zeebe.exporter.source.kafka:
  enabled: true
  format: protobuf
  consumerProperties: |
    bootstrap.servers=kafka:9093
    group.id=zeebe-simple-monitor
    auto.offset.reset=earliest

These configs will cause the conditional configuration files to be imported

@cameronbraid I like the idea of having one project that combines all exporter streams :+1: In the future, I would like to see support for the Hazelcast exporter JSON format and especially the ElasticSearch exporter :rocket:
Since the importing part is essential for the simple monitor and ZeeQS project, I would like to move your project zeebe-exporter-source into Zeebe's organization. This would allow us to build releases easily and contribute to it, even in your absence. You would still be the main contributor. Is this okay for you?
The code changes themselves look good so far. I would recommend to move the Kafka test to the zeebe-exporter-source project. So, we don't need to write such a test in all dependent projects, like the simple monitor or ZeeQS.

@cameronbraid I like the idea of having one project that combines all exporter streams :+1: In the future, I would like to see support for the Hazelcast exporter JSON format and especially the ElasticSearch exporter :rocket:
Since the importing part is essential for the simple monitor and ZeeQS project, I would like to move your project zeebe-exporter-source into Zeebe's organization. This would allow us to build releases easily and contribute to it, even in your absence. You would still be the main contributor. Is this okay for you?
The code changes themselves look good so far. I would recommend to move the Kafka test to the zeebe-exporter-source project. So, we don't need to write such a test in all dependent projects, like the simple monitor or ZeeQS.

Closing, because outdated.


Enhance : Dark Mode

Category

[ ] Documentation
[ ] Resource Addition
[ ] Codebase
[X] User Interface
[ ] Feature Request

Description
Current dark mode is not looking great...

I can improve it ...Please assign me under JWOC 2024.

You're assigned.

You're assigned.


Fail to visualize the lanes of NGSIM-US101 using Envision

BUG REPORT
Fail to visualize the lanes of NGSIM-US101 using envsion
SMARTS version
[e.g. 0.6.1rc1]
Steps to reproduce the bug

modify <PATH_OF_NGSIM_US101_SCENARIO> in the following python script.
run the script.
open localhost:8081 on browser.

import os
import sys
import inspect
import signal
from subprocess import Popen

currentdir = os.path.dirname(os.path.abspath(inspect.getfile(inspect.currentframe())))
parentdir = os.path.dirname(currentdir)
sys.path.insert(0, parentdir)
print(sys.path)

from smarts.core.smarts import SMARTS
from smarts.core.scenario import Scenario
from envision.client import Client as Envision

def experiment(scenario_path):
    traffic_name = "us101_0750-0805"
    scenario_name = "ngsim_us101"

    scenario_iterator = Scenario.scenario_variations(
        [scenario_path], list([]), shuffle_scenarios=False, circular=False
    )  # scenarios with different traffic histories.
    scenario = None
    for _scenario in scenario_iterator:
        if _scenario._traffic_history.name == traffic_name:
            scenario = _scenario
            break
    assert scenario is not None

    envision_client = Envision(
        sim_name=f"{scenario_name}_{traffic_name}",
        output_dir="record_data_replay_path",
        headless=False,
    )
    smarts = SMARTS(
        agent_interfaces={},
        traffic_sim=None,
        envision=envision_client,
    )
    smarts.reset(scenario)
    smarts.step({})
    while True:
        smarts.step({})
        current_vehicles = smarts.vehicle_index.social_vehicle_ids()
        if len(current_vehicles) == 0:
            break

if __name__ == "__main__":
    scenario_path = <PATH_OF_NGSIM_US101_SCENARIO>
    # Arguments
    envision_proc = Popen(
        f"scl envision start -s {scenario_path} -p 8081",
        shell=True,
        preexec_fn=os.setsid,
    )

    try:
        experiment(scenario_path)
    except Exception as e:
        os.killpg(os.getpgid(envision_proc.pid), signal.SIGTERM)
        envision_proc.wait()
        raise e

    os.killpg(os.getpgid(envision_proc.pid), signal.SIGTERM)
    envision_proc.wait()

Error logs and screenshots

Lane lines are not displayed
System information

Operating system & Environment [Please note if using Docker]: ubuntu16.04
Number of system cores available: 16
Python version [Please note if using Jupyter] 3.7
Python packages [e.g. from pip freeze]
SUMO version
Date when bug occurred

Impact [If known]

@qianyi-sun and I looked at this. We found that the envision server requires a list of directories, as was done here.
# e.g. `scl envision start --scenarios "./scenarios` --envision_port 8081
envision_proc = Popen(
    f"scl envision start -s {scenario_path} -p 8081",
    shell=True,
    preexec_fn=os.setsid,
)

@RutvikGupta Please check if this works when targeting a specific scenario, and an absolute path, rather than a relative directory of scenarios (e.g., /usr/foo/repos/SMARTS/scenarios/loop.)

scl envision start -s {scenario_path} -p 8081

So I tried this with a specific scenario, and an absolute path, and in both the cases it works.
Only case when this doesn't work when the scenario_path folder you mention when running envision server does not have the scenario you are running the example with. Eg: If i pass scenarios/intersection in scl envision start -s {scenario_path} -p 8081 and run the command, python examples/single_agent.py scenarios/loop, I won't see any map in envision which make sense.

Also if you are trying to use the scl run command with --envision option, then you need to have the scenario you are running in ./scenarios folder since its envision -s option defaults to that folder.

Also from the script snippet above, the user doesn't seem to be building the scenario ngsim/us101. So it could be possible that they never created the .glb file for the scenario and envision is not able to find that in the scenario path.
@YuechengLiu, can u please make sure to run scl scenario build --clean <PATH/TO/NGSIM/US101> command at your source level  before running the above script?

Also from the script snippet above, the user doesn't seem to be building the scenario ngsim/us101. So it could be possible that they never created the .glb file for the scenario and envision is not able to find that in the scenario path. @YuechengLiu, can u please make sure to run scl scenario build --clean <PATH/TO/NGSIM/US101> command at your source level before running the above script?

@RutvikGupta
Thanks for your time! I find that my map.glb file is missing. And now it works!


build-script: build SwiftSyntax dynamic library when building from the script.

We need the .dylib artifact while building SwiftSyntax as a part of the
Swift compiler.

@swift-ci please test

cc: @akyrtzi @rintaro @ahoppen

I don't think this is the right approach. Rather, I think we should have two products, e.g. SwiftSyntax and SwiftSyntax-dynamic. Users can then depend on either the static or dynamic library and we can build the dynamic library by changing the --product argument of SwiftPM from SwiftSyntax to SwiftSyntax-dynamic in build-script.


Merge Staging into Production

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Breaking changes in 1.3.9

:wrench: Summary
Lefthook version
1.3.9 - 1.3.12
Steps to reproduce
post-merge
  commands:
    010_composer_i:
      files: "git diff-tree -r --name-only --no-commit-id HEAD@{1} HEAD"
      glob: "composer.lock"
      skip:
        - rebase
        - merge
      run: "echo {files} | composer install"
post-checkout:
  commands:
    010_composer_i:
      files: "git diff-tree -r --name-only --no-commit-id HEAD@{1} HEAD"
      glob: "composer.lock"
      skip:
        - merge
        - rebase
      run: "echo {files} | composer install"

It works great in 1.3.8, but 1.3.9 introduces a breaking change there resulting in an error 128
LEFTHOOK_VERBOSE=1 git checkout -b test-h5
Switched to a new branch 'test-h5'
Lefthook v1.3.12
SYNCING
SERVED HOOKS: pre-commit, post-merge, post-checkout, prepare-commit-msg
RUNNING HOOK: post-checkout
[lefthook] cmd: [sh -c git diff-tree -r --name-only --no-commit-id HEAD@49c5332d4d16feb7837269813a5ee3956b134b36 HEAD]
[lefthook] err: exit status 128
[lefthook] out: fatal: ambiguous argument 'HEAD@49c5332d4d16feb7837269813a5ee3956b134b36': unknown revision or path not in the working tree.
error replacing {files}: exit status 128

Possible Solution
I COULD possibly switch to a new proposed syntax
post-merge:
  commands:
    010_composer_i:
      files: "git diff --name-only {1} {2}"
      glob: "composer.lock"
      skip:
        - merge
        - rebase
      run: "composer install"
post-checkout:
  commands:
    010_composer_i:
      files: "git diff --name-only {1} {2}"
      glob: "composer.lock"
      skip:
        - rebase
        - merge
      run: "composer install"

It works fine for post-checkout, but unfortunately in fails for post-merge
LEFTHOOK_VERBOSE=1 git checkout -b test-h6 #everything is fine
#change composer.lock and commit changes
LEFTHOOK_VERBOSE=1 git checkout test-h5 #everything is fine
LEFTHOOK_VERBOSE=1 git merge test-h6
Updating 49c5332d4..19edb0eda
Fast-forward
 composer.lock | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Lefthook v1.3.12
RUNNING HOOK: post-merge
[lefthook] cmd: [sh -c git diff --name-only 0 {2}]
[lefthook] err: exit status 128
[lefthook] out: fatal: ambiguous argument '0': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

error replacing {files}: exit status 128
010_composer_i: (skip) error

Am i missing smth?

Hey! I remember this change and I'm sorry it broke your configuration. This feature makes sense since we used to have arguments references in run option, so it feels OK to have it in files. I guess that I can add a special check to skip replacement if there's a leading HEAD before the brackets. I'll put this issue on my radar.
I'd like to provide some workarounds in case you want a quick solution:
Use HEAD~1
I think this variant is preferred.
post-checkout:
  commands:
    010_composer_i:
      files: "git diff-tree -r --name-only --no-commit-id HEAD~1 HEAD"
      ...

Use HEAD^1
post-checkout:
  commands:
    010_composer_i:
      files: "git diff-tree -r --name-only --no-commit-id HEAD^1 HEAD"
      ...

Thank you for your quick response.
I ended with the following configuration and it seems to work fine.
post-merge:
  commands:
    010_composer_i:
      files: "git diff-tree -r --name-only --no-commit-id HEAD^1 HEAD"
      glob: "composer.lock"
      skip:
        - merge
        - rebase
      run: "composer install"
post-checkout:
  commands:
    010_composer_i:
      files: "git diff --name-only {1} {2}"
      glob: "composer.lock"
      skip:
        - rebase
        - merge
      run: "composer install"

Closing it for now


Upgrade to Mutiny 2.6.0

Merged! I've just created an issue for it and updated the commit message.
Fix #1871

Thanks!


Expose LineEdit edit and unedit methods.

Fixes: https://github.com/godotengine/godot/issues/97088
Fixes: https://github.com/godotengine/godot/issues/97096
Fixes: https://github.com/godotengine/godot/issues/97737
Fixes: https://github.com/godotengine/godot/issues/88235

Feel free to change the title, since all the fixes are connected to the new behavior.

Regression! pressing escape key to hide the ColorPicker window will revert back to the old color 😞

Thanks!


add spa flag to serve static files in spa mode

Added --spa as a flag to serve static files in spa mode.
This is useful if you use pocketbase pb_public dir to serve react, angular, vue or whatever spa framework you like.
If in spa mode, the StaticDirectoryHandler falls back to index.html when the file is not found and contains no dot.
For example, /deep/deep/link would fall back to index.html but /unknown.png would still return 404.

This was recently discussed in https://github.com/pocketbase/pocketbase/issues/421#issuecomment-1246018247 and it is planned after the refactoring in #376.
The idea to ignore files is a good one, but may not be reliable (you can have files without extension).
I'll close the issue for now, but I have it in my todo and we can always refer to it after the refactoring (please note that there will be a lot of internal changes and it's better new PRs to wait).


Error plotting

Hello!
I'm just starting to use flexCE and I'm getting an error that may be very simple to solve, but I haven't managed it myself. Here's the line of code:
File "/home/user/flexce/flexCE/plot/plot_xfe_feh.py", line 35, in
import plot.utils as putils
ModuleNotFoundError: No module named 'plot'
Can you give me some help?

Hmmm...I'm not 100% sure what's going wrong for your setup. If I had to guess, the top-level flexce directory is not in your python path by line 35 when plot_xfe_feh.py is trying to import plot.utils. I would try to run plot_xfe_feh.py from its directory (if you're trying to run it from somewhere else) and if that fails, then try to print out the python path to make sure that the top-level flexce directory is there.

Thanks


Open keybindings icon disappears

Issue Type: Bug

VS Code version: Code - Insiders 1.31.0-insider (edf1090b8546ad0d17f30bf6f8075613e37e1b37, 2018-12-17T10:06:30.031Z)
OS version: Windows_NT x64 10.0.17763

@sandy081
Adding tabIndex: -1 to div.keybindings-editor makes it focusable and fixes the issue.
In keybindingsEditor.ts, line 108 needs to be changed to:
const keybindingsEditorElement = DOM.append(parent, $('div', { class: 'keybindings-editor', tabIndex: -1 }));

Is this an acceptable fix? Shall I raise a PR?

@anirudhrb Yeah it is acceptable. Please create a PR.

@anirudhrb, there's a yellow border in that case and it breaks Shift+Tab.

@usernamehw Where is that yellow border? And what exactly is breaking in Shift+Tab? Works fine for me.

Shift+Tab (when focus is on input) should focus menu (three dots). And the icon {} should remain in place.

Oh I see it now. I am getting a blue border that is barely noticeable. I will fix that. Thanks!
When focus is on input, I believe Shift+Tab move focus to the "Record keys" button  (thats on the far right of the input box) and so on. That's how it is happening in the latest release version too.

@anirudhrb, That's what pressing Tab should do.
Shift+Tab is a reverse command of that and should move focus in the opposite side - in this case to editor actions menu (and the {} icon should be in place to be available for pressing by Enter).

Oh! My bad! Will look into it.

@anirudhrb, I think you should do the same as in settingsEditor2.ts and set the key to true in the setInput method
https://github.com/Microsoft/vscode/blob/dc261e04364542f6114d0e838b7fedf18ee505b7/src/vs/workbench/parts/preferences/electron-browser/settingsEditor2.ts#L202-L205
and remove this listeners
https://github.com/Microsoft/vscode/blob/dc261e04364542f6114d0e838b7fedf18ee505b7/src/vs/workbench/parts/preferences/browser/keybindingsEditor.ts#L114-L118


Agent: rerun failures with dependent methods is broken in TestNG

TestNG agent seems just use method state to find out which one to re-execute. As result we don’t include to re-run base methods on which failed ones depends. It blocks completely rerun and corrupt TestNG JVM:
org.testng.TestNGException:
Method "PremiumMealGoalsTest.testEnableMealGoalsDefault()[pri:0, instance:com.myfitnesspal.qa.test.premium.PremiumMealGoalsTest@3e60be48]" depends on nonexistent method "com.myfitnesspal.qa.test.premium.PremiumMealGoalsTest.testDisabledMealGoals"
Previously on the finish we recalculate all failed methods and for each of them all based methods as well to rerun everything correctly.
In scope of the ticket we have to find the root cause of this problem and fix if possible. Workaround steps were provided to UA team

fixed in 1.28 image.
during the testing let's execute set of api jobs and do rerun failures for those where failures were detected.
-> @okamara new reruns should execute only previously failed tests

verified, fixed. Need run again after fix cron jobs.


Paste not appearing in chrome right click menu

I'm not sure if this is a change to chrome or a regression with 0.2.7, but in Chrome 21.0.1180.49 beta-m there is no option to paste when right clicking on the terminal window.

Not working as of today in Chrome 46 and latest GitHub version (0.2.15)
<frown/>

not working today in Chrome-51 (linux)
Seeing as this has been open for 4 years, I would imagine that no work is being done in this regard. Does anyone know of any other tty emulator in javascript that can be embedded in a web page ?

See this gist for user.js code which enables copy/paste in Firefox and Chrome: https://gist.github.com/risacher/7837761
In Firefox, you ususally have to left-click in the window immediately before right-clicking to get to the context menu.


@defimetachain/testcontainers should be build locally

What would you like to be added:
@defimetachain/testcontainers should be built locally instead of using a versioned published image. We need to reference a local Dockerfile for this.
This is currently blocked by:

#61
#69
#72
#71
#67
#66

Why is this needed:
After https://github.com/DeFiCh/metachain/pull/42 with turbo pipelines, we can automatically sequence tasks in a pipeline. Imagine build:meta-node -> build:testcontainers -> test:testsuite, turbo can be configured to automatically build:testcontainers when it detect changes within the TypeScript project, or rebuild build:meta-node.
/area workflows
/packages testcontainers
/triage accepted
/priority important-soon

/assign @mambisi and this as well, thanks


Question about Fan-Coil_Lylligo_T-can code

I've seen that you use addresses 1601 and later to read data.
Can you tell me where to find the documentation for these modbus registers? I have a similar fan coil that gives "illegal address/register" errors for 0, 1, 2, etc address. Thanks

I received this infos from Midea retailer.


Handle GitHub redirections?

julia> contributors("dlfivefifty", "ApproxFun.jl")

HttpError(404,"Not Found","https://developer.github.com/v3")
while loading In[42], in expression starting on line 103

 in handle_error at /Users/jiahao/.julia/v0.3/GitHub/src/error.jl:36
 in get_pages at /Users/jiahao/.julia/v0.3/GitHub/src/utils.jl:78
 in get_pages at /Users/jiahao/.julia/v0.3/GitHub/src/utils.jl:77
 in contributors at /Users/jiahao/.julia/v0.3/GitHub/src/repos.jl:132
 in contributors at /Users/jiahao/.julia/v0.3/GitHub/src/repos.jl:120

This particular package was moved to https://github.com/ApproxFun/ApproxFun.jl.

Oh, interesting, it shouldn't return a 404 if it wants to redirect... I'll have to poke at this

Just an update, I looked at the data being returned from this call, unfortunately it's juse a 404 with ["message"=>"Not Found","documentation_url"=>"https://developer.github.com/v3"]... no nice redirect links or anything.
Not quite sure the best way around this. Possibly we could make a second request to regular github (as opposed to the api) and detect a redirect, but that does introduce overhead and sounds like it could be brittle.


How to listen when collapse or expand event

just add the code in controller $scope.my_tree.on_select = function (node) {


Add badges to readme

Add open issues, PRs  and star count to readme
Refer - https://github.com/jsvigneshkanna/tailwind_ui_components
Modify as per this repo. Please star the repo to make it cooler

I could work on this

@aryanprince , let's wait for some time for others to take this issue. If not assigned you can work on it

Hello @jsvigneshkanna I would like to work on this issue

@droffilc1 please go ahead and dont forget to star the repositories


Having a buckler on one arm does not count as a free hand for purpose of the "Fist" weapon

If my character is holding a buckler and another weapon (Here a 1+ Hands weapon, but 1 hand behaves the same) in one hand each, the "Fist" weapon (in this example gained from Deific Weapon: Irori) will fail to recognize the hand assigned to the Buckler as free.

This works as intended.

More specifically, though it is a bit strange, fists are explicitly supposed to be treated as free hand weapons, and free hand weapons cannot be used if anything is being wielded in that hand.

Fair enough.
Though technically a buckler is never stated to be in your hand, just strapped to you forearm. It's just the foundry system that implemented it as "Held 1H" to be able to implement it the same as other shields.

Its actually not buckler, its cause of fist. A fist is to be treated as a free hand weapon, and the free hand trait has certain restrictions.
Basically, fist doesn't require a free hand. Instead, it requires you to not be wielding anything in that hand. This may sound like the same thing, but those two states are not mutually exclusive and result in consequences.

@CarlosFdez, "having a Buckler strapped to your arm while not gripping it" is not wielding it. You are only wielding it if you grip it, such as to get the Shield Bash attack with it.
Neither state is relevant when having a Buckler on one arm and anything else in your other hand.
Fist attacks can be used with that configuration due to this.
https://2e.aonprd.com/Rules.aspx?ID=2149

You’re wielding an item any time you’re holding it in the number of hands needed to use it effectively.

i.e. if you aren't gripping the Buckler, it is not being wielded.
This does not stop you from Raising it, due to the text in the item's description.
@stwlam, I think this issue should be re-opened, because even if that's intended, it prevents play in Foundry from matching what's actually possible mechanically in the PF2e system.

While this specific interaction isn't in the FAQ, the fist free weapon thing is mentioned there:

An unarmed attack can't be Disarmed. It also doesn't take up a hand, though a fist or other grasping appendage generally works like a free-hand weapon. - PC 283

As for the rest of your point, bucklers do count as wielded, because shields in geneeral do:

Your character must be wielding a shield in one hand to make use of it, and it grants its bonus to AC only if they use an action to Raise a Shield.

I say this as someone who believed you could punch with bucklers, and was pointed to specific evidence. Unfortunately, shark is right. This is a natural consequence of Paizo writing out rules as fail states instead of allowed states.

Interesting. Thanks for that information.
I do not see where the hand is wielding the Buckler in that case, however.
From your earlier comment:

and free hand weapons cannot be used if anything is being wielded in that hand.

If a Buckler is not gripped, but is being wielded, it's not being wielded by the hand of the arm it is strapped to.
It's being wielded with 0 hands. Because you're not gripping it, and the exception text in its description lets you do that.
The entire crux of this conversation is whether the hand should be unavailable for other things when the Buckler isn't Gripped.
And my understanding of what you're saying is that having a Buckler strapped to an arm is wielding it even if the hand isn't Gripping it, so the hand is treated as occupied.
But that statement is only saying "it's being wielded". Not "it is being wielded by specifically that hand."
The reason this distinction is important is because it's what's making the Free-Hand reference you bring up relevant.

You can’t attack with a free-hand weapon if you’re wielding anything in that hand or otherwise using that hand.

If that reference isn't relevant, then the Fist attack isn't affected by a Buckler in any case.
If it's this text from the Shield rules that's causing the hand to be treated as occupied:

Your character must be wielding a shield in one hand to make use of it, and it grants its bonus to AC only if they use an action to Raise a Shield.

The Buckler text is the exception to this statement, so it doesn't apply in this case.
Because you can make use of a Buckler without it being in your hand due to its exception text.
The only two reasonable outcomes from the exception text in the Buckler item are:

You can Raise the Buckler in the conditions the text describes, and your hand remains free when doing so.
You can Raise the Buckler in the conditions the text describes, and your hand becomes occupied by doing so.

But the idea that the actual outcome of the text is:
3. You can Raise the Buckler in the conditions the text describes, but your hand was always occupied by having it on.
Appears to be unsupported based on the above.
It also creates this weird distinction where a Buckler is more restricting in this way, because you have to take it off to avoid that occupied status for your hand.
Whereas, you can just release a Steel Shield and utilize the now free hand, then grip the Steel Shield later, because you're not wielding the Steel Shield while you do that since you can't use it like that given it lacks the exception text.
My point in expressing this is to say: The interpretation that a Buckler always occupies the hand creates a situation that I would expect to be untrue for how bad it is. The opposite of "too good to be true": That seems "too bad to be true".
All this to ask: What rule causes wielding to take up the hand in the Buckler's case, given its exception text?
Because, if there's not any, it doesn't. And if it doesn't, it doesn't interfere with a Fists attack because free-hand becomes unrelated.

That's unfortunate.

The hand with a buckler is both free and wielding something.

What makes specifically the hand wield the Buckler? You can wield something with 0 hands if that's what it requires to use.
If it's the Shield rules text, the Buckler's exception text directly addresses that.
Without writing another large comment, it's untenable to treat a hand as both free & wielding something at the same time.
Which takes precedent when I need to open a door with it? The Wielding or the Free?
More importantly, what rules text clarifies whatever the answer is?
My only point in asking that question is to point out how this is untenable.

Neither, interact says you use your hands, so if your hand is available you're go. Its not based on precedence, its based on requirements. Its actually quite tenable.
Its very clear you're going to a major length to try to force a specific interpretation through the system. Trying to do so on a RAW argument unfortunately isn't going to work, the RAW is clear, even if I think its strange.


Volumes primitives

Hi,
this pull request provides three new items, based on Mesh3D, to draw volumes.

I made a small Pull Request on your branch to add a few copy of arrays and move the position argument.
Otherwise it looks good to me!


feat(android): percentage support in translate

Summary:
This PR adds percentage support in translate properties for android. Isolating this PR for easier reviews.

Changelog:
[Android] [ADDED] - Percentage support in translate

Test Plan:

Checkout TransformExample.js -> Translate percentage example.
Added a simple test in processTransform-test.js. The regex is not perfect (values like 20px%, 20%px will pass, can be improved, let me know!)

Related PRs - https://github.com/facebook/react-native/pull/43191, https://github.com/facebook/react-native/pull/43192

I checked code, and Android will no-op if adding existing listener, but it's a little bit smelly that we can add ourselves as a listener, after we have already added ourselves as listener. Not sure a better way though (probably don't want to waste cycles to always attach).

i moved it in onAfterUpdateTransaction so it gets called a bit less and yes duplicate calls for same listener will be ignored. But i agree this is not very optimal. If all views are getting extended from ReactViewGroup then we can move the entire transform logic there as it already has a onSizeCallback as mentioned here.


typedoc.js vs typedoc.json configuration files in documentation

[X] I have checked issues with bug label and found no duplicates

Expected Behavior

The documentation will mention a typedoc.json file in one spot and a typedoc.js file in another. For instance, in the example page for arguments and when running help from the command line, the --options flag indicates that if a file isn't specified it will look for typedoc.jsfile. Further down on the documentation page under the --options sections it contradicts that and says that by default it will look for a typedoc.json file.
Actual Behavior

Make clear if the config file should be .json or .js or if both are acceptable. If both are acceptable which is the default. I was trying to specify both an out:"docs" setting and a tsconfig location setting. I could not get a typedoc.json file to work. I was able to get a typedoc.js file to work. Also, it would be helpful to show a .js example since I believe the config data needs to to be wrapped with
module.exports = {
}

Steps to reproduce the bug

Nothing to do just read the docs and the command line --help output.
Environment

Typedoc version:0.14.2
Node.js version:10.15.3
OS: macOS

I would say that typdoc.json is the preferred option. typedoc.js is supported for backwards compatibility, but if you need to define options dynamically, using the programmatic API is preferred.
Thanks for raising this issues about the confusing documentation and the issues you were encountering with typedoc.json.

If we can verify the typedoc.json tsconfig option issue we should have a separate story so we can track the documentation and the bug separately.

I think it's really just a documentation issue. I got the .js config file working yesterday so today I converted that to a .json file and it worked fine. I must have had some other problem in the config file. Since both versions work this is of pretty low importance. If you have deprecated support for .js then I still think it would be good to update the documentation. Personally, I prefer .js config files because I can add comments in there.

Cross linking #1074 here. If we do continue supporting .js and .json files, we should probably rename the default filename to typedoc.config.js to avoid unexpected behavior on Windows. Unfortunately, the rename is a rather large breaking change. Most projects that use TypeDoc that I'm aware of use a typedoc.json or typedoc.js file for options.

You probably could support both typedoc.js and typedoc.config.js` but I'd rather drop support than maintain a list of possible config files. If someone wants to have a dynamic config, the programatic api is fairly straightforward and well documented.

The docs have been updated with #1085, website docs have also been updated and will be pushed momentarily.

Hey guys!

The docs have been updated with #1085, website docs have also been updated and will be pushed momentarily.

I don't know if the website update was missed but the options page still references the JS config file and I stumbled upon the issue with the opening of the JS file in an editor mentioned in #1074.
It would be good to have the documentation updated on the website to clarify the supported options.
Thanks!

It would be good to have the documentation updated on the website to clarify the supported options

Both typedoc.js and typedoc.json are supported for now, the docs were just updated to place the JSON file first, I haven't started actively discouraging typedoc.js since I don't yet understand all the reasons that people pick the dynamic option instead of the static JSON.

Oh okay, my bad, I thought it was planned to remove the support of the JS config file because it doesn't work properly if named typedoc.js. To bring some insight on my use case, I don't use any dynamic JS, I just tend to prefer static JS files compared to static JSON because of the way they are written/displayed (allow trailing commas, don't force double quotes on properties, etc) But maybe that's just me and my OCD ^^

FWIW, I'll often pick the .js option if only to allow // comments

FWIW, I'll often pick the .js option if only to allow // comments


Doesn't work with Moodle

Would it be possible to add Moodle support to this extension?

@Avamander, you can configure the extension to not run on Moodle:
Go to chrome://extensions/?options=nkgllhigpcljnhoakjkgaieabnkmgdkb
In the 2nd box, labeled "Exclude URL Patterns", add https://moodle\\.org/.* on its own line.
For backwards compatibility with older versions of this extension, the default configuration is to blacklist all sites and whitelist a few. I think the opposite is a better solution: whitelist all sites and blacklist only the troublesome ones. I've been wanting to change the extension to do just that, but I would want the experience of blacklisting a site to be much better, especially for non-technical people.
I have a complete rewrite of this extension to make that second style easier to work with; it's working, but still needs UX love. If you are familiar with using local extensions, you can test it out: https://github.com/jswanner/DontFuckWithPaste/tree/v2.


llvm_tot is now 13

Part one of https://github.com/ClangBuiltLinux/continuous-integration2/issues/62. There is no functional change, this is just matching reality.

Thanks for the review!


[terminal] Can not exit terminal

Can't note exit terminal with exit command or Ctrl-d.
 You can close the terminal with CTRL-w c or CTRL-w :bdelete

@mattn I mean run exit command in terminal that is opened in vim.
You are right, I can close the terminal with CTRL-w c or CTRL-w，But I used to press ctrl-d or type exit instead.

I noticed this as well. If this is the intended behaviour then it works fine  but not having the terminal close when the terminal is killed looks like a bug from a user stand point. Either way keep up the good work vim version 8 is amazing.

As far as I can see the code, the remaining terminal after exiting shell is expected behavior.

As far as I can see the code, the remaining terminal after exiting
shell is expected behavior.

This isn't done yet.  My plan is that when the job exits, the terminal
window gets turned into a buffer.  Then you can do ":quit" as usual.
Or search through the text.
It's a bit tricky, since we need to keep the color and other attributes
somehow, and we can't store these in a buffer.  Needs some more work.
Also combined with the scrollback behavior (keep text that scrolls off
the top, including the attributes).  Probably the attributes would be
dropped as soon as you make changes to the buffer.
In the end it should work nicely for:
:term ls
and end up with a buffer containing the output of "ls".
Not so useful for an interactive command, such as a shell or Vim.
Might need an argument for that, e.g.  :term  bash
--
hundred-and-one symptoms of being an internet addict:
228. You spend Saturday night making the counter on your home page
pass that 2000 mark.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Add possibility to run contract tests against local pact file

that's really useful, thanks a lot for that.


Add cognitiveservices\data-plane\TextAnalytics\readme.typescript.md

Auto generated

Can one of the admins verify this patch?

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-node


README

As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can se a professional README that gives info on the project and how to use it.

Done!


Azure Arc onboarding script does not work for multiple tags

I am currently implementing Azure Monitor, and during the POC phase we generated a single server onboarding script. As part of the onboarding, we elected to include several tags to define the region and location of the server. The onboarding was successful, but the device shows the same value for every flag. We have replicated this behaviour over 10 times, trying removing spaces from the tag and sorting the tag order (it always uses the last tag value for all tags). In no case does it successfully use the values.

Hey @chorting
The intent of this "Bug report" template is to address issues related to the Azure Arc Jumpstart scenarios, ArcBox and all other project areas.
The Azure Arc Jumpstart team does not handle Azure Arc core product issues, bugs and feature requests and will try to assist on a best effort basis. For a core product issue or feature request/feedback, please create an official Azure support ticket or general feedback request

I was directed to post to this forum by @AnuragSingh-MSFT to possibly receive updates on when the software will be fixed. My impression was github was intended for community feedback, but if we should open private tickets for issues I'll stop reporting.


failed to deploy gcs cluster using vagrant.

The cluster fails to deploy using vagrant:-
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Tuesday 27 November 2018  15:44:42 +0530 (0:00:00.190)       1:08:21.441 ******
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (50 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (49 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (48 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (47 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (45 retries left).

FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (1 retries left).
fatal: [kube1]: FAILED! => {"attempts": 50, "changed": false, "connection": "close", "content_length": "542", "content_type": "application/json; charset=UTF-8", "cookies": {}, "cookies_string": "", "date": "Tue, 27 Nov 2018 10:23:48 GMT", "json": [{"client-addresses": ["gluster-kube1-0.glusterd2.gcs:24007"], "id": "f71b18e2-badb-44f9-a3cb-ebaab3ea7911", "metadata": {"_zone": "f71b18e2-badb-44f9-a3cb-ebaab3ea7911"}, "name": "gluster-kube1-0", "online": true, "peer-addresses": ["gluster-kube1-0.glusterd2.gcs:24008"], "pid": 26}, {"client-addresses": ["gluster-kube3-0.glusterd2.gcs:24007"], "id": "ff7a5a54-ff8e-49c4-8a09-ac7ee9955787", "metadata": {"_zone": "ff7a5a54-ff8e-49c4-8a09-ac7ee9955787"}, "name": "gluster-kube3-0", "online": true, "peer-addresses": ["gluster-kube3-0.glusterd2.gcs:24008"], "pid": 25}], "msg": "OK (542 bytes)", "redirected": false, "status": 200, "url": "http://<IP_ADDRESS>:24007/v1/peers", "x_gluster_cluster_id": "348d6571-88a2-4231-9100-98ef06ad9a9c", "x_gluster_peer_id": "ff7a5a54-ff8e-49c4-8a09-ac7ee9955787", "x_request_id": "7c157d53-b8ed-4551-8a55-977731c39b7d"}
	to retry, use: --limit @/root/gcs-latest/gcs-latest-karan/deploy/vagrant-playbook.retry

PLAY RECAP *********************************************************************
kube1                      : ok=377  changed=114  unreachable=0    failed=1
kube2                      : ok=4    changed=4    unreachable=0    failed=1
kube3                      : ok=254  changed=71   unreachable=0    failed=0

Tuesday 27 November 2018  15:53:48 +0530 (0:09:05.631)       1:17:27.072 ******
===============================================================================
download : container_download | Download containers if pull is required or told to always pull (all nodes)  2455.31s
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 545.63s
GCS | ETCD Operator | Wait for etcd-operator to be available ---------- 433.74s
Install packages ------------------------------------------------------ 153.73s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------ 143.99s
download : container_download | Download containers if pull is required or told to always pull (all nodes) - 127.84s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 63.79s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 53.10s
download : file_download | Download item ------------------------------- 50.40s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 49.67s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 37.31s
kubernetes/master : Master | wait for the apiserver to be running ------ 30.71s
etcd : Gen_certs | Write etcd master certs ----------------------------- 18.82s
Wait for host to be available ------------------------------------------ 16.46s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 15.67s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 12.62s
etcd : Configure | Check if etcd cluster is healthy -------------------- 11.26s
etcd : reload etcd ----------------------------------------------------- 10.70s
docker : Docker | pause while Docker restarts -------------------------- 10.23s
kubernetes/master : Master | wait for kube-controller-manager ----------- 9.94s
==> kube3: An error occurred. The error will be shown after all tasks complete.
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.

An error occurred while executing the action on the 'kube3'
machine. Please handle this error then try again:

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]# vagrant ssh kube1
[vagrant@kube1 ~]$
[vagrant@kube1 ~]$
[vagrant@kube1 ~]$
[vagrant@kube1 ~]$
[vagrant@kube1 ~]$ kubectl get pods -n gcs
NAME                             READY   STATUS    RESTARTS   AGE
etcd-ngw4zkd6g8                  1/1     Running   0          15m
etcd-nv9n225zsd                  1/1     Running   0          13m
etcd-operator-7cb5bd459b-c6zn8   1/1     Running   0          23m
etcd-r68w6jxjrh                  1/1     Running   0          14m
gluster-kube1-0                  1/1     Running   0          13m
gluster-kube2-0                  0/1     Pending   0          13m
gluster-kube3-0                  1/1     Running   0          13m
[vagrant@kube1 ~]$

The CSI pods aren't even deployed.  and gluster pods going in pending state.

Setup 2 :-
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Tuesday 27 November 2018  15:33:29 +0530 (0:00:00.179)       0:36:16.033 ******
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (50 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (49 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (48 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (47 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (46 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (45 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (44 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (43 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (42 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (41 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (40 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (39 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (38 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (37 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (36 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (35 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (34 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (33 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (32 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (31 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (30 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (29 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (28 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (27 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (26 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (25 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (24 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (23 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (22 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (21 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (20 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (19 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (18 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (17 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (16 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (15 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (14 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (13 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (12 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (11 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (10 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (9 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (8 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (7 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (6 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (5 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (4 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (3 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (2 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (1 retries left).
fatal: [kube1]: FAILED! => {"attempts": 50, "changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 113] No route to host>", "redirected": false, "status": -1, "url": "http://<IP_ADDRESS>:2379/v2/members"}
	to retry, use: --limit @/root/gcs-latest/gcs-latest-karan2/deploy/vagrant-playbook.retry

PLAY RECAP *********************************************************************
kube1                      : ok=365  changed=112  unreachable=0    failed=1
kube2                      : ok=292  changed=91   unreachable=0    failed=0
kube3                      : ok=253  changed=71   unreachable=0    failed=0

Tuesday 27 November 2018  15:43:59 +0530 (0:10:30.643)       0:46:46.677 ******
===============================================================================
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------ 630.64s
download : container_download | Download containers if pull is required or told to always pull (all nodes) - 389.77s
download : container_download | Download containers if pull is required or told to always pull (all nodes) - 376.40s
Install packages ------------------------------------------------------ 264.78s
download : container_download | Download containers if pull is required or told to always pull (all nodes) - 192.70s
download : file_download | Download item ------------------------------ 148.51s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 95.88s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 60.78s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 46.46s
kubernetes/master : Master | wait for the apiserver to be running ------ 32.00s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 29.60s
Wait for host to be available ------------------------------------------ 23.29s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 20.53s
etcd : Gen_certs | Write etcd master certs ----------------------------- 20.32s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 11.84s
kubernetes/master : Master | wait for kube-controller-manager ---------- 11.26s
etcd : reload etcd ----------------------------------------------------- 10.88s
docker : Docker | pause while Docker restarts -------------------------- 10.21s
download : container_download | Download containers if pull is required or told to always pull (all nodes) --- 8.87s
etcd : wait for etcd up ------------------------------------------------- 7.51s
==> kube3: An error occurred. The error will be shown after all tasks complete.
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.

An error occurred while executing the action on the 'kube3'
machine. Please handle this error then try again:

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]#
(gcs-venv) [root@rhsqa-virt05 deploy]# vagrant ssh kube1
[vagrant@kube1 ~]$
[vagrant@kube1 ~]$ kubectl get pods -n gcs
NAME                             READY   STATUS      RESTARTS   AGE
etcd-6mwvjrc8mt                  0/1     Error       0          31m
etcd-operator-7cb5bd459b-xk68n   1/1     Running     0          33m
etcd-tznzpbsxx5                  0/1     Completed   0          32m
[vagrant@kube1 ~]$

Closing this issue as the deployment is working with today's nightly.


[Azure Communications] Calling the startVideo / stopVideo or mute/unmute repeatedly will cause uncaught exceptions

Package Name: @azure/communication-calling
Package Version: 1.4.4
Operating system: MacOS
[] nodejs

version:

[X ] browser

name/version: Chrome 100.0.4896.127 / Edge 100.0.1185.50

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
A clear and concise description of what the bug is.
The startVideo / stopVideo will generate uncaught exception 61 and will terminate the ongoing call if called repeatedly. Same happens if you call mute/unmute functions repeatedly, there will be an uncaught throttling error
To Reproduce
Steps to reproduce the behavior:
Easiest way to recreate the issue is to spam the startVideo / stopVideo or mute/unmute functions repeatedly. We've custom UI and if I start to click the "cam on / cam off" or "mic on / mic off" button it'll will generate the exceptions quite fast
Expected behavior
A clear and concise description of what you expected to happen.
The SDK should handle the exception and pass them along so they can be caught in the implementation. Also I expect that the call should not crash but the SDK should be able to either prevent crashing or recover from it.
Screenshots
If applicable, add screenshots to help exp

lain your problem.
Additional context
Add any other context about the problem here.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Communication:0.16745946,Compute:0.09351083,Docs:0.09309866'

@petrsvihlik I wasn't sure who to assign this to, would you mind triaging further if you're not the correct assignee? Thanks so much!

@akania Can you please assign someone from the Calling team?


Differences between identity and rest of project setup

[ ] Axios as HTTP library
[ ] Use of next.js on the admin
[ ] ...

Axios as HTTP library

What would be the preferred HTTP library?


The following changes are included

Build summary not showing proper name for our tasks.
Extra white spaces got added in loc.json
Few missing checkins for PerformActionOnMachineGroup

Signing off for   PerformActionOnMachineGroup task

Looks OK

looks fine

are these for M83 as well?


guide-C#-Substring-changes

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

@lennort123 Thank you for  creating this PR.  However, since it was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you.

I tried to resolve the merge conflicts. Thank you for taking the time to reply.

Congrats @lennort123 on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


pygame 2.1.0 and pygame_gui 0.5.7 incompatible on raspberry pi os

Describe the bug
I'm trying to use pygame_gui on a raspberry pi zero. I'm using the previous release of Pi OS (buster) due to an incompatibility between the new OS and the screen I have connected to the Pi. Importing pygame and importing pygame_gui produce the error shown in the pastebin below (schreenshots section). Downgrading to pygame 1.9.6 fixes the issue.
To Reproduce
Steps to reproduce the behaviour:

fresh install of raspberry pi os
install pygame_gui and update pygame to 2.1.0
open python3 and import pygame_gui

Expected behaviour
pygame and pygame_gui should import.
Screenshots
https://pastebin.com/raw/XkZRdit5
Platform and software (please complete the following information):

OS: Raspberry Pi OS Buster 2021-05-07
Pygame GUI version 0.5.7
Pygame version 2.10
Python 3.7.3

Additional context
Add any other context about the problem here.

That looks like an error during compilation/install of pygame 2.1.0 to me. I think you don't have SDL 2 or maybe just not sdl_ttf on your pi. Pygame's font submodule depends on some libraries that it looks like your pi didn't have or couldn't find during installation (specifically libSDL2_ttf-2.0).
I'm not a raspberry pi/linux expert these days, I think if you are going to build the latest pygame on pi you also need to install a recent sdl2 and sdl2-ttf before trying to build pygame.
try this:
sudo apt install libasyncns0 libflac8 libfluidsynth1 libice6 libjack0 libjbig0 libmodplug1 libmpg123-0 libogg0 libopus0 libopusfile0 libportmidi0 libpulse0 libsdl2-2.0-0 libsdl2-image-2.0-0 libsdl2-mixer-2.0-0 libsdl2-ttf-2.0-0 libsm6 libsndfile1 libsndio7.0 libtiff5 libvorbis0a libvorbisenc2 libvorbisfile3 libwayland-client0 libwayland-cursor0 libwayland-egl1 libwebp6 libx11-xcb1 libxcursor1 libxfixes3 libxi6 libxinerama1 libxkbcommon0 libxrandr2 libxrender1 libxss1 libxtst6 libxxf86vm1

and maybe pip installing pygame again?

Hey, thanks. You were correct in that your string of apt installs fixed the issue.
Raspberry Pi OS comes with Pygame installed, so there is some dependency broken in Pygame 2.1.0 on Raspberry Pi.
Previously I tried with Buster (previous release of Raspberry Pi OS) which comes with Pygame 1.9.6 installed and it worked until I upgraded to Pygame 2.1.0.
Then I tried with Bullseye (newest release of Raspberry Pi OS) which comes with Pygame 2.1.0 installed and Pygame GUI did not work.
Anyway, thanks again for the help!


Add support for custom message to log when no migrations available to…

@mkhoussid Why would this be useful?

@mkhoussid Why would this be useful?

The library's current API offers no way to suppress this message at the moment. This PR was opened a while ago and I have since then stopped using this library however.

@mkhoussid Why would this be useful?

The library's current API offers no way to suppress this message at the moment. This PR was opened a while ago and I have since then stopped using this library however.

Thanks for your input 👌
I think your current approach is then not the most best way
However I will reconsider a silent/quite CLI/Environment flag to fully suppress logs at all
I'm sorry that the project did not have maintenance for so long time, but now I have nearly full access to the repo and do my best to bring back a good maintenance for the community 🫶


Update for Ukrainian language pack

Updated dictionary, updated keyboard layouts, and added new compact keyboard layout

This is an update for https://play.google.com/store/apps/details?id=com.anysoftkeyboard.languagepack.ukrainian ?

Yes.
On Mon, 8 Apr 2019, 02:19 Menny Even Danan<EMAIL_ADDRESS>wrote:

This is an update for
https://play.google.com/store/apps/details?id=com.anysoftkeyboard.languagepack.ukrainian
?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AnySoftKeyboard/LanguagePack/pull/254#issuecomment-480640772,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJewFY5_lGGFHndzeUyb_gukPayN0RVks5venz-gaJpZM4cdqfq
.


Update tags and vendor for 1.25

needed for release 1.25.6
Release note:

NONE

/test openstack-cloud-controller-manager-e2e-test-release-125
/test openstack-cloud-csi-manila-e2e-test-release-125
/test openstack-cloud-csi-cinder-sanity-test-release-125
/test openstack-cloud-csi-manila-sanity-test-release-125

cc @jichenjc

csi tests fails because occm 1.25.6 does not exist yet
    "    Image:      registry.k8s.io/provider-os/openstack-cloud-controller-manager:v1.25.6",

Error from server (BadRequest): container "openstack-cloud-controller-manager" in pod "openstack-cloud-controller-manager-768ffc6ddf-sz77n" is waiting to start: trying and failing to pull image

/override openstack-cloud-csi-cinder-e2e-test-release-125
/override openstack-cloud-csi-manila-e2e-test-release-125
/lgtm
/approve


ios8 flipOutY not working right

Helo guys,
In ios8 for iphone, the flipOutY isn't behaving properly, instead of the usual flip and fadeOut it usually does, it is starts flipping with a weird flickering ( box appearing and disappearing multiple times per second while doing the flip ).
In ios8 for the ipad, the entire box disappears while the entire effect is being done.
If you guys have any updated for this, I would be really grateful.
Regards.

I didn't have any luck with your suggestions Oryan (thanks for sharing though). Not sure why I didn't get anywhere...
I opted to just rip out the troublesome animations using the code below:
isIOS8 = function() {
  var deviceAgent;
  deviceAgent = navigator.userAgent.toLowerCase();
  return /(iphone|ipod|ipad) os 8_/.test(deviceAgent);
};

if (isIOS8()) {
  $('.flip').addClass('zoomIn').removeClass('flip');
  $('.flipInY').addClass('zoomIn').removeClass('flipInY');
  $('.flipInX').addClass('zoomIn').removeClass('flipInX');
  $('.flipOutY').addClass('zoomIn').removeClass('flipOutY');
  $('.flipOutX').addClass('zoomIn').removeClass('flipOutX');
};

nb: the if statement needs to be wrapped in a closure if your script isn't loaded at the bottom of the page (or is loaded async) and replace zoomIn with whatever animation you want to replace the flips with.

Hi there, just fyi @oryan's solution have worked for me too, adding -webkit-backface-visibility: hidden; with   -webkit-transform: translate3d(0,0,0); both animated element and it's container resolves that error.


UI MockUps/Storyboard Diagram

Recipe Part

The "sort by" section still needs to be completed

Sort by completed.
Add some prototypes.


ehcache caching option seems to not work

Describe the bug
With latest release 3.0.0, the ehcache provider seems to not work. Refer error below observed during sample app generation.

ERROR! An error occured while running jhipster-quarkus:bootstrap-application#configuringTemplateTask
ERROR! ERROR! Cache provider ehcache is not supported
Error: Cache provider ehcache is not supported
at default.configuringTemplateTask (file:///home/runner/work/generator-jhipster-quarkus/generator-jhipster-quarkus/generator-jhipster-quarkus/generators/bootstrap-application/generator.js:16:27)
at default.executeTask (file:///home/runner/work/generator-jhipster-quarkus/generator-jhipster-quarkus/generator-jhipster-quarkus/node_modules/yeoman-generator/dist/actions/lifecycle.js:244:26)
at env.queueTask.once (file:///home/runner/work/generator-jhipster-quarkus/generator-jhipster-quarkus/generator-jhipster-quarkus/node_modules/yeoman-generator/dist/actions/lifecycle.js:218:56)
at runLoop.add.once (file:///home/runner/work/generator-jhipster-quarkus/generator-jhipster-quarkus/generator-jhipster-quarkus/node_modules/yeoman-environment/dist/environment-base.js:384:23)
at Immediate. (/home/runner/work/generator-jhipster-quarkus/generator-jhipster-quarkus/generator-jhipster-quarkus/node_modules/grouped-queue/lib/subqueue.js:48:34)
at process.processImmediate (node:internal/timers:478:21)
Error: Process completed with exit code 1.

Did it work in previous versions?

This error still seems to exist with Version 3.2.0:
ERROR! An error occured while running jhipster-quarkus:bootstrap-application#configuringTemplateTask
ERROR! ERROR! Cache provider ehcache is not supported
Error: Cache provider ehcache is not supported
at default.configuringTemplateTask (file:///usr/local/lib/node_modules/generator-jhipster-quarkus/generators/bootstrap-application/generator.js:16:27)
at default.executeTask (file:///usr/local/lib/node_modules/generator-jhipster-quarkus/node_modules/yeoman-generator/dist/actions/lifecycle.js:244:26)
at env.queueTask.once (file:///usr/local/lib/node_modules/generator-jhipster-quarkus/node_modules/yeoman-generator/dist/actions/lifecycle.js:218:56)
at runLoop.add.once (file:///usr/local/lib/node_modules/generator-jhipster-quarkus/node_modules/yeoman-environment/dist/environment-base.js:395:23)
at Immediate. (/usr/local/lib/node_modules/generator-jhipster-quarkus/node_modules/grouped-queue/lib/subqueue.js:48:34)
at process.processImmediate (node:internal/timers:483:21)


cuckoo.service systemd unit file

Create a proper systemd unit file
Deploy either systemd or init.d files based on base op. system

Became unneccessary with package


change deployment target to iOS 9 to fix Archiving with Xcode 12; fix…

… other warnings

Thanks for your contribution! Merging now.


[fl] Add coverage build

Wanted to check out codecov - this is what came of it. Code coverage reports are enabled for the org - add them in CI.
Test plan:
CI

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@53dc0bf). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #560   +/-   ##
=========================================
  Coverage          ?   91.48%
=========================================
  Files             ?      166
  Lines             ?     7724
  Branches          ?        0
=========================================
  Hits              ?     7066
  Misses            ?      658
  Partials          ?        0

Flag
Coverage Δ

asr
93.61% <0.00%> (?)

core
86.32% <0.00%> (?)

lib
98.94% <0.00%> (?)

lm
44.94% <0.00%> (?)

objdet
81.90% <0.00%> (?)

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

Continue to review full report at Codecov.

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


CVE-2021-28092 in is-svg by cssnano

Hi,
I have got no positive answer in cssnano repo. Perhaps it is important to mention it here.
https://github.com/cssnano/cssnano/issues/1018
https://github.com/cssnano/cssnano/issues/1019
`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>      `--<EMAIL_ADDRESS>        `--<EMAIL_ADDRESS>

In Angular CLI postcss-svgo is disabled and hence this vulnerability cannot be exploited. Also, the mentioned exploit reference is for server environments which generally don't expect Angular CLI to run in.
In many cases these advisories should be taken with a pinch of salt.
That said, once a new version of CSSNano is released we will update, other than that these is not much we can do here.

@alan-agius4 please note that there's an open defect in CSSNano regarding the same CVE. The issue was just closed so adopting that new version should resolve the following complaint from GitHub:

I think an issue marked with High severity should be taken into consideration and addressed by the Angular team. We're already using Angular 11.2.7

Addressed via https://github.com/angular/angular-cli/pull/20458


Dev base path

This allows dev loading at e.g. /#/sign/outkast instead of /build/#/sign/outkast

works for me :+1:


chore(ci): use labels and if branch=master to control jobs

Benchmark results
Metrics with a significant change:

protocol_circuit_simulation_time_in_ms (private-kernel-tail-to-public): 1,905 (+179%)
avm_simulation_time_ms (FeeJuice:_increase_public_balance): 134 (+215%)
avm_simulation_time_ms (Token:mint_public): 43.6 (-83%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 266 (+509%)
avm_simulation_time_ms (Token:transfer_public): 25.4 (+70%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,771
1,552
707
764 (+3%)
779 (-1%)

proof_construction_time_sha256_30_ms
11,493 (-1%)
3,067
1,367 (-1%)
1,419 (-2%)
1,453 (-1%)

proof_construction_time_sha256_100_ms
45,541 (-1%)
11,801 (-1%)
5,515
5,827 (+6%)
5,376 (-1%)

proof_construction_time_poseidon_hash_ms
79.0 (+1%)
34.0
34.0
59.0 (+2%)
89.0 (+1%)

proof_construction_time_poseidon_hash_30_ms
1,532
417 (-5%)
199
231 (+4%)
271 (+1%)

proof_construction_time_poseidon_hash_100_ms
5,654
1,506
668
710 (-2%)
751

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,612
8,260
15,524

l1_rollup_calldata_gas
52,804
97,552
186,908

l1_rollup_execution_gas
819,490
1,555,646
3,346,437

l2_block_processing_time_in_ms
258 (+10%)
449
794 (-2%)

l2_block_building_time_in_ms
9,339
18,491
36,887

l2_block_rollup_simulation_time_in_ms
9,338
18,490
36,887

l2_block_public_tx_process_time_in_ms
7,946
17,076 (+1%)
35,389

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
3,202 (+3%)
4,054 (+1%)

node_database_size_in_bytes
14,237,936
18,247,920

pxe_database_size_in_bytes
16,258
26,818

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Circuit
simulation_time_in_ms
witness_generation_time_in_ms
input_size_in_bytes
output_size_in_bytes
proving_time_in_ms

private-kernel-init
70.9 (-4%)
378 (-7%)
20,975
44,933
N/A

private-kernel-inner
140 (-1%)
687 (-4%)
71,787
45,067
N/A

private-kernel-reset-tiny
331 (-11%)
700 (-5%)
64,273
44,922
N/A

private-kernel-tail
160 (+5%)
131 (-5%)
50,551
57,178
N/A

base-parity
5.56 (-1%)
N/A
160
96.0
N/A

root-parity
35.0 (-1%)
N/A
73,964
96.0
N/A

base-rollup
2,138 (+1%)
N/A
189,128
664
N/A

block-root-rollup
41.2
N/A
58,217
2,448
N/A

public-kernel-setup
86.3
N/A
114,433
79,670
N/A

public-kernel-app-logic
99.4 (-1%)
N/A
114,251
79,670
N/A

public-kernel-tail
584
N/A
487,098
16,414
N/A

private-kernel-reset-small
305 (-2%)
N/A
66,345
45,629
N/A

private-kernel-tail-to-public
:warning: 1,905 (+179%)
604 (-4%)
448,120
1,825
N/A

public-kernel-teardown
85.7
N/A
114,697
79,670
N/A

merge-rollup
19.9
N/A
38,182
664
N/A

undefined
N/A
N/A
N/A
N/A
102,835 (-2%)

Stats on running time collected for app circuits

Function
input_size_in_bytes
output_size_in_bytes
witness_generation_time_in_ms

ContractClassRegisterer:register
1,344
11,731
350 (+1%)

ContractInstanceDeployer:deploy
1,408
11,731
18.3

MultiCallEntrypoint:entrypoint
1,920
11,731
426

FeeJuice:deploy
1,376
11,731
394

SchnorrAccount:constructor
1,312
11,731
60.8

SchnorrAccount:entrypoint
2,336
11,731
368 (-1%)

FeeJuice:claim
1,344
11,731
35.8 (-7%)

Token:privately_mint_private_note
1,280
11,731
72.7 (+1%)

FPC:fee_entrypoint_public
1,344
11,731
25.6 (+1%)

Token:transfer
1,312
11,731
213

Benchmarking:create_note
1,344
11,731
73.0 (-1%)

SchnorrAccount:verify_private_authwit
1,280
11,731
26.6 (+1%)

Token:unshield
1,376
11,731
491 (+1%)

FPC:fee_entrypoint_private
1,376
11,731
661 (-7%)

AVM Simulation
Time to simulate various public functions in the AVM.

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
:warning: 134 (+215%)
1,188

FeeJuice:set_portal
11.6 (+3%)
1,170

Token:constructor
251
10,378

FPC:constructor
72.1 (+1%)
7,877

FeeJuice:check_balance
35.3 (-1%)
995

Token:mint_public
:warning: 43.6 (-83%)
2,123

Token:assert_minter_and_mint
:warning: 266 (+509%)
1,435

AuthRegistry:set_authorized
46.3 (+26%)
515

FPC:prepare_fee
92.9 (-5%)
1,588

Token:transfer_public
:warning: 25.4 (+70%)
8,603

FPC:pay_refund
42.0 (-1%)
2,090

Benchmarking:increment_balance
1,001
1,516

Token:_increase_public_balance
37.6 (+4%)
1,159

FPC:pay_refund_with_shielded_rebate
50.6 (+3%)
2,090

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.166 (+5%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
2.21 (+1%)
3.86
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.115 (+1%)
0.109
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.3 (-1%)
17.7 (+1%)
30.9 (+1%)
60.5 (+2%)
112 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.108
0.103 (+1%)
0.101 (+1%)
0.104 (+1%)
0.101

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.3
26.3 (+1%)
44.1 (+1%)
83.6 (+1%)
160 (-1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
357
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.109
0.106 (+1%)
0.105 (+4%)
0.103 (+1%)
0.101 (-1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.2
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
129
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.107
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
72,419
668,302

Transaction size based on fee payment method
| Metric |  |
| - |  |


Maybe consider ordering generated tests alphabetically

If it's not too much effort, maybe you could consider ordering the test names alphabetically so that the tests appear in the same order as the test explorer.
In this case, I wanted to fix tests from top to bottom in the order that they appear in the Test Explorer. It would be nice if I could fix tests by also working from top to bottom in the source code.
I know this is a marginal gain, but might just make fixing tests slightly less of a chore.

I haven't forgotten about this, just been quite short on time recently :)

I am not going to get round to this - closing for now!


Sidebar-mini dropdown format issues after update to 2.3.5

After updating today to 2.3.5 via composer I'm seeing something wacky going on with the sidebar (sidebar-mini) formatting with dropdown menus. The chevron icons seem to have become a bit messed up (dropping out of alignment) along with the menu headers (not full width):

Anyone else seeing this?

Apologies this appears to be the same issue as #1098

Closing due to inactivity


Typo correction "mages" -> "images"

Proposed changes
This is a simple spelling fix, mages -> images in the text but of a link.

I kicked Netlify.


Minor API cleanup

Also includes updates to the travis configuration and readme.

@alex-alex Can you look over it really quick to make sure I didn't screw anything up?

@Danappelxx lgtm


need for a little refactoring

Version of flutter_calendar_carousel
current version
Expected behavior
this plugin is one of the greatest but to let it go on being it it really need to be refactored. all the calendar view and logic are placed in the huge calendar-carousel, this definitively need to be segmented in multiples files.
Actual behavior
flutter doctor result (run flutter doctor in terminal)
Steps to reproduce the behavior

Thanks for the concern. Hope you can help us maintain it together!


RevEng: Make some APIs public (non-Internal)

This exposes the entry point into the Reverse Engineer functionality (IReverseEngineerScaffolder); the contract for code generators (IModelCodeGenerator); and the service for selecting a code generator (IModelCodeGeneratorSelector).
It also adds extension methods for adding our design-time services to an IServiceCollection. (fixes #9339) You can use them like this:
var designTimeServiceCollection = new ServiceCollection()
    .AddEntityFrameworkDesignTimeServices()
    .AddDbContextDesignTimeServices(dbContext);
new SqlServerDesignTimeServices().ConfigureDesignTimeServices(designServiceCollection);

var designTimeServiceProvider = designTimeServiceCollection.BuildServiceProvider();

var migrationsScaffolder = designTimeServiceProvider.GetService<IMigrationsScaffolder>();
// migrationsScaffolder.ScaffoldMigration(...)
// migrationsScaffolder.RemoveMigration(...)

var reverseEngineerScaffolder = designTimeServiceProvider.GetService<IReverseEngineerScaffolder>();
// reverseEngineerScaffolder.ScaffoldModel(...)

This cleans up some other DI contracts too.
cc @dazinator @ErikEJ  @tonysneed

@bricelam Have you thought about moving EntityEntryGraphIterator out of Internal?  My framework depends on it

@ajcvickers? (make EntityEntryGraphIterator public)

@tonysneed Do you depend on EntityEntryGraphIterator or IEntityEntryGraphIterator?

@tonysneed FYI, I imagined EntityFrameworkCore.Scaffolding.Handlebars would override IModelCodeGeneratorSelector since it's template-based and thus language-agnostic. Meanwhile, the Visual Basic and F# generators will override IModelCodeGenerator.

@ajcvickers I'm creating a new EntityEntryGraphIterator. The code looks like this:
public static void TraverseGraph(this DbContext context, object item,
    Action<EntityEntryGraphNode> callback)
{
    IStateManager stateManager = context.Entry(item).GetInfrastructure().StateManager;
    var node = new EntityEntryGraphNode(stateManager.GetOrCreateEntry(item), null, null);
    IEntityEntryGraphIterator graphIterator = new EntityEntryGraphIterator();
    var visited = new HashSet<int>();

    graphIterator.TraverseGraph(node, n =>
    {
        // Check visited
        if (visited.Contains(n.Entry.Entity.GetHashCode()))
            return false;

        // Execute callback
        callback(n);

        // Add visited
        visited.Add(n.Entry.Entity.GetHashCode());

        // Return true if node state is null
        return true;
    });
}

The reason for my own TraverseGraph method is that setting EntityState on TrackGraph halts recursion, and there are scenarios where I need to set the state but continue recursion.

    public class FakeAnnotationCodeGenerator : IAnnotationCodeGenerator

Could this override from base class?

Refers to: test/EFCore.Design.Tests/Scaffolding/Internal/ReverseEngineeringConfigurationTests.cs:52 in bdcc70b. [](commit_id = bdcc70b73fd66e9d0714d41608ab0150ecc4d9dd, deletion_comment = False)

public class ReverseEngineeringConfigurationTests

Should change name of this test file

Refers to: test/EFCore.Design.Tests/Scaffolding/Internal/ReverseEngineeringConfigurationTests.cs:16 in bdcc70b. [](commit_id = bdcc70b73fd66e9d0714d41608ab0150ecc4d9dd, deletion_comment = False)

Agree the tests could use a bit more cleanup. I'll address as part of #9111

@tonysneed For the not stopping on state set thing, we have an issue to fix this: #8226. It's good additional feedback that you would use this.
About the code you posted, is there a reason not to resolve IEntityEntryGraphIterator from the context D.I. rather than newing it up explicitly? For example, var graphIterator = context.GetService<IEntityEntryGraphIterator>();
(I'm asking these questions so as to determine if it is best just to make the service public or also the default implementation of the service. Generally we only make the default implementation public if it is expected that it act as a base class for customized implementations.)

For the not stopping on state set thing, we have an issue to fix this: #8226. It's good additional feedback that you would use this.

I'll comment over there for clarification.

About the code you posted, is there a reason not to resolve IEntityEntryGraphIterator from the context D.I. rather than newing it up explicitly? For example, var graphIterator = context.GetService<IEntityEntryGraphIterator>();

It didn't dawn on me I could use the context as a service locator.  I'll refactor the code to do that.  It would be nice to have IEntityEntryGraphIterator lifted out of the Internal namespace, but I don't think I have the need to extend EntityEntryGraphIterator.

@tonysneed Thanks. File #10540 to track making IEntityEntryGraphIterator public.


Locking the screen for too long will keep the screen black

When I lock the screen, the screen locks quickly (about 1 second), instead of starting the screen saver (I set the screen saver to start after 5 minutes of inactivity), if I wake the screen at this point, everything works fine, but if If you don't wake up the screen for a certain period of time (about 30-40 minutes), then wake up the screen and the screen will be black. At this time, you can observe that the system is running, and you can only force the shutdown and restart the computer.

Does your power button white light blink quickly?

The Fn indicator, mute indicator and power indicator are all normal and are in a long light state.


[stdlib] String._classify(): Handle shared native case

Trapping in this case can make debugging string problems extraordinarily frustrating.

@swift-ci test

@swift-ci test


Add primitive numba support for Layout and MultiVector

This implements the minimal operations to allow numba functions like:
@numba.njit
def wedge3(a, b, c):
    ret_value = omt_func(a.value, omt_func(b.value, c.value))
    return MultiVector(a.layout, ret_value)

This means we can drop all of our func / val_func duality (in a future commit).
Right now, this implementation depends on an unmerged PR against numba-passthru, asodeur/numba-passthru#3, for which the target package is in turn is an unmerged PR against numba/numba#3640.
Our choices are to either:

Wait for this @asodeur to review and merge the PR
Vendor the parts of their package that we actually need (it's not too much of it)

Blocked by https://github.com/asodeur/numba-passthru/pull/3

lower_constant is missing from this patch, and is pretty essential for this to be useful.


gh-1803 - splits now explicitly sorted and streamed to ensure order

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@e1ad306). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             develop    #1869   +/-   ##
==========================================
  Coverage           ?   65.37%
  Complexity         ?     2150
==========================================
  Files              ?      855
  Lines              ?    28183
  Branches           ?     3586
==========================================
  Hits               ?    18426
  Misses             ?     8307
  Partials           ?     1450

Impacted Files
Coverage Δ
Complexity Δ

...o/operation/utils/AccumuloKeyRangePartitioner.java
60% <100%> (ø)
7 <0> (?)

Continue to review full report at Codecov.

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


fix: no need to specify query scope when get with parameters

这个 PR 实现什么功能/修复什么问题:
修正：当跨域获取item详情时，不再需要在query中指定scope
是否需要 backport 到之前的 release 分支:

release/2.10.0

/lgtm
/approve

Codecov Report

Merging #1232 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1232      +/-   ##
=========================================
- Coverage     7.9%    7.9%   -0.01%
=========================================
  Files         370     370
  Lines       57956   57958       +2
=========================================
- Hits         4584    4579       -5
- Misses      52974   52979       +5
- Partials      398     400       +2

Flag
Coverage Δ

#aFlag
7.9% <0%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudcommon/db/fetch.go
0% <0%> (ø)
:arrow_up:

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

pkg/util/rbacutils/rbac.go
74.76% <0%> (-0.95%)
:arrow_down:

Continue to review full report at Codecov.

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