Appstudio update test-custom-default-branch-xkeq

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-vchz-on-pull-request-
creating pipelinerun test-annotations-vchz-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-gcoj-on-pull-request-
creating pipelinerun test-annotations-gcoj-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-dtnt-on-pull-request-
creating pipelinerun test-annotations-dtnt-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-ntht-on-pull-request-
creating pipelinerun test-annotations-ntht-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-gcoj-on-pull-request-
creating pipelinerun test-annotations-gcoj-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-custom-default-branch-xkeq-on-pull-request-
creating pipelinerun test-custom-default-branch-xkeq-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-uqzm-on-pull-request-
creating pipelinerun test-simple-build-uqzm-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-uqzm-on-pull-request-
creating pipelinerun test-simple-build-uqzm-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-vchz-on-pull-request-
creating pipelinerun test-annotations-vchz-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-dtnt-on-pull-request-
creating pipelinerun test-annotations-dtnt-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-ntht-on-pull-request-
creating pipelinerun test-annotations-ntht-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-iivx-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-nqwj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


Mock failures with repeat count > 1 do not cause failure

Hi,
We noticed in internal testing that with the MockSupportPlugin, any mock failure (e.g., mock().actualCall() without an expectOneCall()) that occurs in multiple runs in the same process - i.e., -r2 or higher, is only reported on the first run:
hbock@whiskey-dev ~/development/scratch/cpputest-mock-repeat-test $ ./main -r4
Test run 1 of 4

testgroup.cpp:8: error: Failure in TEST(MyGroup, First)
	Mock Failure: Unexpected call to function: Foo
	EXPECTED calls that did NOT happen:
		<none>
	ACTUAL calls that did happen (in call order):
		<none>

.
Errors (1 failures, 1 tests, 1 ran, 0 checks, 0 ignored, 0 filtered out, 0 ms)

Test run 2 of 4
.
OK (1 tests, 1 ran, 0 checks, 0 ignored, 0 filtered out, 0 ms)

Test run 3 of 4
.
OK (1 tests, 1 ran, 0 checks, 0 ignored, 0 filtered out, 0 ms)

...

It seems like the failure should be reported on all test runs.  Running through the debugger, I notice that the failure is detected, but we never get to actually terminate the test or report the failure because UTestShell::hasFailed() returns true.  See the logic in MockFailure.cpp:
https://github.com/cpputest/cpputest/blob/2e32dd0aed2cc4429455e70f148a1865842ba0a6/src/CppUTestExt/MockFailure.cpp#L59-L60
If I remove the conditional on line 59, the failure is reported as expected.  It doesn't seem to affect the outcome of any CppUTestExt unit tests.   I'm not sure if the check is not valid, or if UTestShell's failure state needs to be reset between repeats, or something else.
I'm happy to fix it if I can get some guidance on what the correct operation of MockFailure is.  :)

Attached is a small repeatable test group that exhibits the issue.  Run on the command line with -r2.
cpputest-mock-repeat-test.zip

Hi hbock,
I think the overall guideline of TDD is that try best to match one test failure to only one test, and only fix one test failure at one time.
So CppUTest only report the first failure and also only report once to make you focus on fixing that sole failure, then next.   I have met several similar case in other usage. and,
OK (1 tests, 1 ran, 0 checks, 0 ignored, 0 filtered out, 0 ms)
has showed no check take place.

That is a very intersting bug. hasFailed() should be reset on subsequent runs. @hbock I agree that, within a test case, only the first failure should be reported (that's what hasFailed() is for) but, repeated test runs should fail in the same way (unless a bug in the software you test caused "random" failures).

@arstrube, if already one test is failed, then still need to let all repeated test to report the same failure?
isn't that a messy( because you have already known what goes wrong )?  Now following tests actually do not  check anything anymore because there has been one capture that failure.

@cuitoldfish Yes, absolutely. The point of running -r is to find inconsistencies between runs in the behavior of the SUT. To find those inconsistencies, it is of utmost importance from my point of view that the test tool (CppUTest in this case) behaves identical between runs.
@basvodde how come this is not initialized between runs? Looks like some object is reused that should be destroyed and recreated. Or, at least, re-initialized?

Looking at your example, I suspect the problem might be related to the MockSupportPlugin.
If you did not use the plugin and wrote your test in the following way, the problem might go away (no chance to test yet):

TEST_GROUP(MyGroup)
{
};

TEST(MyGroup, First)
{
  mock().actualCall("Foo");
  mock().checkExpectations();
  mock().clear();
}

Wrong. Behavior stays the same :-(

@cuitoldfish - does the fix work for you?

I totally spaced on this as well.  The fix worked great for me and we have backported it to 3.7.2 in our production codebase.


[Feature Request] Remove WAF association

Implement removal of WAF association when performing sls remove.

Hi,
I must be missing something, but why is it required to explicitly delete a resource you added to the stack? Isn't it being automatically deleted as part of deletion of the whole stack?
Thanks!

Hi,
I must be missing something, but why is it required to explicitly delete a resource you added to the stack? Isn't it being automatically deleted as part of deletion of the whole stack?
Thanks!

You bring up a good point.  In most cases the sls remove will result in the removal of the API Gateway stage/ REST API and therefore the WAF association if the stack being removed created it.
It possible to share an API Gateway across stacks using the provider.apiGateway configuration.  So if you have a second service that adds endpoints to another service which creates the API Gateway, and it’s the second service that adds the WAF association using this plugin, when you remove the second service stack, what would the expected behavior be?
Not sure this is even worth implementing now that I think about it more.

@MikeSouza, Thanks for clarifying.


Pyaudio Issue

I am trying to run the streamlit app and am getting this issue. It seems to be an issue with my microphone my Mac. My microphone is enabled but I am still getting the issue when running the app. Why is this happening?
OSError: [Errno -9999] Unanticipated host error
Traceback:
File "/Users/camabernethy/opt/anaconda3/lib/python3.9/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 552, in _run_script
exec(code, module.dict)
File "/Users/camabernethy/Real-time-transcription-from-microphone/sr_in_streamlit.py", line 22, in
stream = p.open(
File "/Users/camabernethy/opt/anaconda3/lib/python3.9/site-packages/pyaudio/init.py", line 639, in open
stream = PyAudio.Stream(self, *args, **kwargs)
File "/Users/camabernethy/opt/anaconda3/lib/python3.9/site-packages/pyaudio/init.py", line 441, in init
self._stream = pa.open(**arguments)
Expected behavior
Ability to record.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. macOS]
CLI Version [e.g. 0.22]

Hey @Cam5210! From what can be inferred from the error log and your explanation, this issue is unrelated to this CLI. Closing this issue


lost-pixel.com resources return 404s

Bug description
https://lost-pixel.com/ lost styles and scripts, they return 404s:

How to reproduce
Open https://lost-pixel.com/
Expected behavior
No response
Lost Pixel information

lost-pixel logs from CI
No response

hey @Maxim-Mazurok! what browser you were using or maybe there was anything specific like an incognito mode or anything that would help to narrow down the issue. can't reproduce it right now but also don't see any outages in our systems.

@d-ivashchuk I was using latest Chrome on windows. Just tried latest Chrome on Android, on my wifi and on data, same result. I'm from Australia, maybe it's some geo issue?

by any chance you have the network throttling enabled on your browsers? this is super weird as i can't reproduce it at all 😀
do you mind looking at network tab as the website loads please 🙏🏼 what happens there, anything sketchy?

No fancy network setup, no adblock even, tried in incognito mode, both on PC and Phone.
There are examples of resources that return 404s:

https://lost-pixel.com/_next/static/css/8756c315b1e6ea2e.css
https://lost-pixel.com/_next/static/chunks/main-app-daa49b7b63cdc2f9.js

Note that WWW works fine: https://www.lost-pixel.com/
The non-WWW is the one I'm having issue with.
You might have cached redirect, which is no longer in place, maybe?
Tho I tried to get screenshot from pagespeed insights for non-WWW and it looks fine... https://pagespeed.web.dev/analysis/https-lost-pixel-com/zo9m6vfvmg?use_original_url=true&form_factor=desktop
No idea mate, it must be GEO dependant then...

super weird, will give a more detailed look but not being able to reproduce it makes it hard to fix😀 will redeploy the landing page as well, maybe gets fixed

Maybe try to use an Australian VPN?
I just checked on another laptop, the same thing.
Also I wonder where is it hosted, Vercel?

I used free TunnelBear app on my android, it loads fine from US, Indonesia and Philippines, but not from Australian VPN. So there you go, can try that to reproduce.

no, digital ocean for this one. i think on vercel might actually work with no troubles!

seeing this today in Safari as well

most of the js isn't loading it seems? might be content-blocking issues, idk


Update PR Template

New contributors left spaces in the [ x] which did not render properly, rather having the contributors click on the check boxes is a better option, since GitHub now supports it.

@raisedadead how common is the leading/trailing space issue?
Contributors should be checking these boxes as they prep the PR. I feel like asking them to first create the PR, then to go back through and check the boxes will result in them cancelling PRs once they realize they didn't do something, or labeling more PRs WIP, etc.

@QuincyLarson, sorry to answer something that's not my question, but the issue is very common.

@QuincyLarson yeah, as @atjonathan mentioned already its pretty common, GitHub's feature is rather neat, while the markdown syntax just confuses new contributors.

LGTM :+1:
Thanks ninja :tada:


[BUG] Spark Pipeline Components stuck in permanent preparing state

azure-ai-ml:
1.0.0 / 1.1.0 / 1.2.0:
Linux:
3.10:

Describe the bug
Spark Job Component as part of a pipeline get stuck in a permanent "preparing" state.
To Reproduce
Followed the official tutorial here: TUTORIAL https://learn.microsoft.com/en-us/azure/machine-learning/how-to-submit-spark-jobs?tabs=sdk#spark-component-in-a-pipeline-job as it does not work.
Expected behavior
Pipeline jobs can have spark jobs or spark steps with the Spark automatic compute cluster, just as standalone spark jobs.
Screenshots
Additional context

When the pipeline fails I am getting the following error:
Job failed, Error: {"Error":{"Code":"ServiceError","Severity":null,"Message":"InternalServerError","MessageFormat":null,"MessageParameters":null,"ReferenceCode":null,"DetailsUri":null,"Target":null,"Details":[],"InnerError":null,"DebugInfo":null,"AdditionalInfo":null}, ...,"ComponentName":"Execution"}
I created a simple standalone spark job (read delta tables  from the data lake) and it works absolutely fine.
Then, I was trying to implement a two step pipeline in SDKV2, with a Spark component as the first step.
The pipeline is stuck in the Spark component for about 3 to 4 hours until failure.
For the 2 step pipeline I am trying to do something simple, just read delta files, preprocess and train a simple model.
For this 2 step pipeline I am defining:

a spark job as a pipeline component (1st step), and
a training component (using a .yml file).

Thanks for the feedback @Ioannis-Mykelos . We will investigate and get back to you asap.
cc @azureml-github.

Thanks for the feedback @Ioannis-Mykelos . We will investigate and get back to you asap.
cc @azureml-github.

Any updates?

Can we please get Run Id, Subscription Id and workspace name for issue?

Dear @vaibhj, I tried to run again the "2-step-pipeline" with the first component to be a spark job.
It failed again after 3,5 hours.

Experiment: SparkComponent,
Run Id: 90d4014a-7a9d-4eb2-981c-d85518367254,
ComponentId: 5cad6238-2ac0-40db-ba06-ca2fac4f364b

Thanks @Ioannis-Mykelos for retry and providing jobId. Can you please confirm compute details. If you are using SDK you must be adding spark_step.compute = .
Please provide compute name and type.
We saw this behavior when user try to run spark job on AmlCompte instead Attached Spark Compute. You can try hobo spark job by providing spark_step.resources  instead spark_step.compute
spark_step.resources = {
"instance_type": "Standard_E8S_V3",
"runtime_version": "3.2.0",
}
Please correct me if my assumption are wrong.
Thanks

If you want to use Synapse Spark pool attached compute .. you must attach a compute first and later you can use it in spark step. You can ignore attaching synapse pool by using our hobo offering as I mentioned in above message.

@vaibhj Hello, thanks for your quick response.
I have contributor role in the datalake, since I acquired it to make a standalone spark job to work.
And it works just fine, perfectly I could say (Loading delta tables from datalake, process the data and saving them in the datalake).
The spark_step.recourses I am using are the following (it works perfectly in the standalone spark job).
step_1_spark.resources = {
        "instance_type": "Standard_E64S_V3",
        "runtime_version": "3.2.0",
    }

But the 2 step pipeline with the first component as a spark job it tricky.
I am doing as you say:
# Retrieve an already attached Azure Machine Learning Compute.
cluster_name = "gpu"
cluster = ml_client.compute.get(cluster_name)

and
# Define the spark job/component as the step 1:
# Without using the component YML file for step 1
spark_component = spark(
    name="SparkComponentStep1",
    inputs={
        "input_data": Input(type="uri_folder", mode="direct"),
    },
    outputs={
        "output_data": Output(type="uri_folder", mode="direct"),
    },
    # The source folder of the component
    code="./src",
    entry={"file": "spark_step_1.py"},
    driver_cores=2,
    driver_memory="4g",
    executor_cores=4,
    executor_memory="4g",
    executor_instances=4,
    args="--input_data ${{inputs.input_data}} --output_data ${{outputs.output_data}}",
)

# Load component no2 from YML
components_dir =  "src/components/"
train_model_component = load_component(source=os.path.join(components_dir, "spark_step_2.yml"))

And then I define my pipeline:
# Create the Pipeline
@dsl.pipeline(compute = cluster, description="Two step Pipeline with Spark 1st component --> spark")
def spark_pipeline(spark_input_data):

    # STEP 1
    step_1_spark = spark_component(input_data=spark_input_data)
    step_1_spark.inputs.input_data.mode = InputOutputModes.DIRECT
    step_1_spark.outputs.output_data = Output(
        type="uri_folder",
        path="output_path_to_datalake"
    )
    step_1_spark.outputs.output_data.mode = InputOutputModes.DIRECT
    step_1_spark.identity = ManagedIdentityConfiguration()
    step_1_spark.resources = {
        "instance_type": "Standard_E64S_V3",
        "runtime_version": "3.2.0",
    }
    processed_data = step_1_spark.outputs.output_data

    # STEP 2
    step_2_spark = train_model_component(input_data=processed_data)

    return {"train_job_output": step_2_spark.outputs.output_data}

An call my pipeline
# Call the Pipeline function
input_path_ = "azureml://datastores/curated/paths/" + "input_path_to_datalake"
pipeline = spark_pipeline(
    spark_input_data=Input(
        type="uri_folder",
        path=input_path_
    )

Submit the pipeline
# submit the pipeline job
pipeline_job = ml_client.jobs.create_or_update(
    job=pipeline,
    experiment_name="SparkComponent",
    )

And the next step load forever
# Wait until the job completes
ml_client.jobs.stream(pipeline_job.name)

It feels that I am doing what the official documentation says. Or maybe I am missing something. Can you please give me a hint or try to provide a solution?
Also when I tried to create a .yaml component for the spark component but it throws an error since the link appears not to exist
$schema: http://azureml/sdk-2-0/SparkComponent.json

@Ioannis-Mykelos I made below change in your job and it worked for me:
STEP 2
step_2_spark = train_model_component(input_data=processed_data)
**step_2_spark.compute = cluster**

@dsl.pipeline(description="Two step Pipeline with Spark 1st component --> spark")  #removed compute from the parameter
Let me know if it works.

@vaibhj Many thanks for the time and effort.
I applied the changes you recommended, and I can see that now it fails much much faster but with the following error, that is confusing for me:
Job Failed due to: Response status code does not indicate success: 404 (User assigned identity  is not attached to AML workspace ws-dev.).User assigned identity  is not attached to AML workspace ws-dev.
Run Id = 826dcab5-d493-4537-95e8-d3b52d28550d
It looks weird since my ml_client holds the azure.identity...., for the related workspace.
# Configure credential
try:
    credential = DefaultAzureCredential()
    # Check if given credential can get token successfully.
    credential.get_token("https://management.azure.com/.default")
except Exception as ex:
    # Fall back to InteractiveBrowserCredential in case DefaultAzureCredential not work
    credential = InteractiveBrowserCredential()

# Get a handle to the workspace
ml_client = MLClient.from_config(credential=credential)

Any help would be highly appreciated.
Thanks in advance.

@Ioannis-Mykelos you are specifying Managed Identity if you do so you need to assign user assigned identity to workspace else you can use UserIdentity while submitting job

Dear @shreeyaharma,
Can you elaborate? Can you provide an example .ipynb or some documentation?

Dear @shreeyaharma,
The pipeline runs but I am getting a weird error (and the pipeline behaviour is slightly changed)
My python file (spark_step_1.py)  for the first step is the following:

def batch_preprocessing(spark_dataframe: SparkDataFrame) -> pd.DataFrame:
    """
    Here we can do something ....
    """

    # Groupby, agg
    spark_df = spark_dataframe.groupBy("ID").agg({"Quantity": "sum"})

    # Trasform the pyspark.sql.DataFrame to pandas DataFrame
    pandas_df = spark_df.toPandas()

    return pandas_df

if __name__ == "__main__":
    # Get the parameters
    parser = argparse.ArgumentParser()
    parser.add_argument("--input_data", type=str, help="input datapath argument")
    parser.add_argument("--output_data", type=str, help="input datapath argument")
    args = parser.parse_args()

    # Initiate spark session
    spark = SparkSession.builder.appName("spark_load_delta_tables").getOrCreate()

    # Experiment run context
    run = Run.get_context()

    print("Loading Data...")
    # Load delta tables
    pyspark_df = spark.read.format("delta").load(args.input_data)
    pandas_df = batch_preprocessing(spark_dataframe=pyspark_df)

    print("Saving Data...")
    path = args.output_data
    os.makedirs(path, exist_ok=True)
    pandas_df.to_csv(os.path.join(path, "input_step_2.csv"))

    run.complete()

My step 2 python file is the following:
def training_pipeline(data: pd.DataFrame):
    """
    Do something with the csv file
    """
    new_data = data.head(n=10)

    return new_data

if __name__ == "__main__":

    parser = argparse.ArgumentParser()
    parser.add_argument("--input_data", type=str, help="input datapath argument")
    parser.add_argument("--output_data", type=str, help="output datapath argument")
    args = parser.parse_args()

    # Experiment run context
    run = Run.get_context()

    # Load the preprocessed
    print("Loading Data...")
    input_path = os.path.join(args.input_data, "input_step_2.csv")
    print(input_path)
    tutorial_data = pd.read_csv(input_path)

    print("Training model...")
    new_data = training_pipeline(tutorial_data)

    print("Saving Data...")
    path = args.output_data
    os.makedirs(path, exist_ok=True)
    new_data.to_csv(os.path.join(path, "output_step2.csv"))

    run.complete()

For some reason the pipeline instead of creating the single csv file "input_step_2.csv", it creates a folder "input_step_2.csv"
and of course the second step python file thows an error
"IsADirectoryError: [Errno 21] Is a directory: '/mnt/azureml/cr/j/d8136e26f6934466be3b0c4e0e1e3a89/cap/data-capability/wd/INPUT_input_data/input_step_2.csv'"
Info:
RunId:[5f6d9edd-4f3d-4e98-a711-4c73d2455cf8]
ParentRunId:[yellow_truck_9d807mg0b1]
ComputeTarget:[AmlCompute]
And if I try to run the pipeline again I get the following error in the first step:
path abfss://path_to_the_csv_file/input_step_2.csv already exists.
I guess cannot overwrite the directory since it existed from the first run of the pipeline.
So I guess the main concern is that instead of a csv file it creates a directory named "input_step_2.csv"

And the "input_step_2.csv" directory contains:

Any hint would be greatly appreciated.
Thanks for your time and effort.

Dear @shreeyaharma,
Any updates on my questions?
Thanks in advance.

@Ioannis-Mykelos we dont own this feature, Going through to_csv function might help. When I will get time, I will try to find answers to this problem.

Dear @shreeyaharma, many thanks for your help and tips.
I managed to make it work.
Thank you for the support!


fix typo in description

Closes #1447.

thank you for reacting and fixing it so quickly!
it must be lower **right**-corner x-coordinate, right?

@obertsalome right again! Thanks for checking.

For reference: TEI makes it more clear imho:

gives the x coordinate value for the lower right corner of a rectangular space

the code is clear about that ;-)


Question: Take off and landing modes.

Hello people,
Because I'm updating the UM and ready to release the modes page, can somebody clarify what is the behavior of Take off and Landing MODES for:
Take off FW:
Once activated does it spin the motor by itself?
Difference in take off from airstrip or hand launch?
Once activated or thrown it gains altitude? What altitude it gains?
After altitude gain does it get in Loiter waiting for switch to another mode?
How it is activated? There was a PR I remember where tthe take of is activated DJI style with just the throttle
Landing FW:
If too high in altitude does it make a spiral up to some lower altitude?
Once it reached this lower altitude in spiral does it straighten until ground touch?
Once on the ground does it disarm automatically? (in the past we've had a lot of broken props because the plane did not stop its engine)
If RTL activated and the plane is loitering for some time what is the strategy for landing after the grace period? Does it straighten the plane before touch down? (before it just landed in spiral, thus touching down the internal wing thus braking sometimes the plane)
What is the command to activate it? Is t done with the throttle lever only or with a switch?
Take off MC:
Once activated it spins and takes off at what altitude it weights for your commands?
How is it activated? Is it DJI style with the throttle or with a switch?
Landing MC:
How is it activated?
Does it disarm the moment it feels it is in the air? or should I disarm it with a command?
I suppose the VTOL is a combination between the two, although there might be a scenario for the VTOL emergency landing in FW mode? Is there such a scenario?
Is there a way to setup Take off and Landing with the old style switch configuration? I might not have 6 pos switch to use the new style.
Thanks

This might be a good excuse to expand the PX4 user guide. FW planned auto landings have improved substantially recently in QGC.
@hamishwillee FYI
Should we pick away at these items collaboratively?

@tubeme I can only speak for MC.
You can take off manually or automatically.
Manually
Go to position mode, arm, as soon as you raise your manual throttle stick above LNDMC_POS_UPTHR (default 65%) it enables all controllers and goes to hover throttle MPC_THR_HOVER (should be set reasonably to not have a jump). For landing just press the stick down until it is completely landed (goes through multiple steps) and disarm or best set COM_DISARM_LAND > 0 and it will diasrm automatically.
Automatically
Best to be in hold mode first, arm, switch to takeoff mode and it will fly up pretty fast to MIS_TAKEOFF_ALT and wait for further input. Switching out by moving the sticks is currently possible (but will be disabled by default as it looks now here: https://github.com/PX4/Firmware/pull/7025). To Land again automatically you either switch to RTL or Land mode. Land mode just descends in place with MPC_LAND_SPEED (pretty slowly as we don't know whats under there) until it hits the ground and you can auto disarm again as above. In RTL it flies first up to RTL_RETURN_ALT, in a straight line back to the home position, descends first fast and then with the slow land speed because we know how high the ground should be.
The automatical modes are easy to access through the QGC buttons on the bottom of the main flight screen.

@dagar

This might be a good excuse to expand the PX4 user guide. FW planned auto landings have improved substantially recently in QGC.
Should we pick away at these items collaboratively?

Yes. Can we discuss Tuesday (I'm heading off for Easter). Have created https://github.com/PX4/px4_user_guide/issues/4 to track this.
FYI the user guide is now in the PX4 github organisation and published on gitbook here: https://docs.px4.io/en/ . Updates should be done as fork/PR. If you want to create docs early, go ahead!

Thanks @MaEtUgR
@dagar Anything about the FW takeoff and landing?

@dagar OK, so I'm starting this from "first principles" - improving/expanding out the flight modes docs (at the moment this looks like the screenshot below and will live as a peer of this Follow me mode doc). Once we have those we can link from various places to explain the behaviour.
I have some questions below the screenshot below. I appreciate you may not be able to answer them, but can you please link in the people you think might be able to?

Questions
Multicopter
What speed does it return at?
Fixed Wing
The current description is "The aircraft returns to the home position and hovers in a circle above the home position."

Is this correct?
What height does it return at? Is this still RTL_RETURN_ALT?
Does it respect the other parameters? So for example, will it descend to RTL_DESCEND_ALT and try and lad if  RTL_LAND_DELAY is not -1 ?
What is the circle radius for hover?
What is the speed of return?

VTOL
This has no description. I'd expect it to fly up to safe distance like a copter and land like a copter. I'd expect it to decide whether to fly the return in FW or copter based on the distance. But who knows, and if so, what parameters would it use?

Does it return as copter or VTOL and how?
What parameters does it obey.

In the case of VTOL:

The vehicle returns to home in the mode it is currently in (FW or MC)
The vehicle transitions back to MC
Dependent on the LAND_DELAY param it will either loiter there or land

Thanks @sanderux - very useful. W.r.t. to the statement "Dependent on the LAND_DELAY param it will either loiter there or land" is it more accurate to say that the vehicle will perform and ordinary MC RTL landing based on the parameters? The difference being that if this is the case then we can say that the vehicle should also respect the RTL_DESCEND_ALT value.
Also, do you happen to know what the return altitude is (and for FW). Does it respect RTL_RETURN_ALT?

Also @sanderux do you happen to know the LAND mode VTOL behaviour?

@hamishwillee The LAND part in RTL for a VTOL is in essence no different from MC indeed, it respects the same parameters. As for the RTL alt, it will fly at that altitude towards home.
LAND mode looks at the param VT_NAV_FORCE_VT, when any type of landing is commanded in fixedwing and the vehicle has the parameter set it will always switch back to MC first and then land. If this param is disabled it will behave consistent with it's current mode, so land as FW when in FW and land as MC when in MC. The reason for this is that most VTOL vehicles dont have landing gears so this param is enabled by default.

Thanks to all!
Somebody for the FW mode?? BTW the airplane modes are the once that need more clearance on the latest implementations...

OK, so proposed version for RTL is here. @sanderux thanks for all your help, this has very modified version of your VTOL details.
@dagar , can you please comment on the FW behaviour (as requested by @tubeme). I have guessed in that linked doc :-) Specific questions:
I do have some more confirmations/questionss:

Does FW ignore the RTL_MIN_DIST parameter (I have assumed so and removed it).
Can FW LAND in RTL? Ie. if I set RTL_LAND_DELAY >0 will it try land after the time expires? If so, will this be just like LAND mode for FW?
What parameters affect the flight speed and circle? Is the circle behaviour on arrival exactly the same as HOLD mode (and does it transition into HOLD mode or remain in RTL mode).

@MaEtUgR , can you please review the MC sections of these four flight mode docs?

Did I capture the right parameters
Is the description correct?
Is the description complete? For example, in RTL if the vehicle goes to the mode at an altitude above the RTL_RETURN_ALT, will it fly back at its current alt or will it first descend to the return alt?

@hamishwillee Thanks a lot for documenting!
hopefully someone else corrects me if I tell something wrong:

HOLD as far as I know is usually the fallback waiting mode if you fly autonomously without RC. When I fly multicopter with RC and want to stay in place I just center my sticks in positon mode... Also I don't know of any ascending when switching to Hold, it should really just stay where it is.
RTL It stays on the current altitude if it's higher than RETURN_ALT in the beginning. The delay before the final descend RTL_LAND_DELAY is indended to wait for the landing gear to go down which is triggered automatically.
TAKEOFF I think you ccould switch to the mode and then arm but the QGC UI does not allow that. The vehicle does not switch to Hold after taking off but rather stays in takeoff mode, I don't know why maybe we can change that in the future because it does basically the same. (JFI I'm working on a takeoff with which you can configure how fast it should ramp up in the beginning.)

HI @MaEtUgR
Thanks very much. I've updated the docs in line with this.
Re your comments

HOLD

This now focuses on "pausing a mission" rather than "emergency pause". I left that emergency stuff in though, because it is probably still useful for FW.
Also I don't know of any ascending when switching to Hold, it should really just stay where it is. - AFAIK it will using MIS_LTRMIN_ALT (based on this code  - I assume this is the loiter mode definition?)

RTL

Updated docs re initial altitude > RETURN_ALT.
Added a note about the RTL_LAND_DELAY intent. This now is very much focused on landing for MC, with the hover "option" being covered mostly in the "adjusting the parameters" section.

TAKEOFF

I've said you can't arm on basis that QGC is official GCS that we promote and I don't want to confuse people.
I removed "Hold" from the description to reduce confusion.

Can you please sanity check the sections again now?

@hamishwillee
https://github.com/PX4/Firmware/blob/master/src/modules/navigator/mission_params.c#L60-L72

@hamishwillee Nice!
It seems that you were right about Hold, I never tested/used this before. We have to think about what happens if the pilot wants to fly into a valey...

Thanks @MaEtUgR . I guess that means MC and VTOL are now pretty much done. Just need to sort out FW and these four can go live :-)

I've lost track of where we are with this. Which FW parts do you think we need?
In general can we try to emphasize the commonality between MC and FW? These are core PX4 features, but FW and MC sometimes have to handle each step a bit differently.
For example RTL is the same, but a FW and MC loiter and land differently.
In HOLD vehicles always respect MIS_LTRMIN_ALT.
Even takeoff and land can first be discussed generally, as both FW and MC are given the same setpoint type and location.

@dagar

I've lost track of where we are with this. Which FW parts do you think we need?

I'm waiting on you to respond to clarification emails regarding takeoff and landing.

In general can we try to emphasize the commonality between MC and FW? These are core PX4 features, but FW and MC sometimes have to handle each step a bit differently.

Did you read the proposed text? - that is exactly what I've tried to do.

Each topic starts with a sentence that outlines the common core behaviour.
Then we have separate sections for the details of each vehicle. These do share some common parameters but they share enough differences that we still need the sections.

Even takeoff and land can first be discussed generally, as both FW and MC are given the same setpoint type and location.

Yes. But the common stuff is just a sentence. The detail is a bit more. This is what we still need to clarify.
I don't think this would be all that hard, but we may need to hold as a "chat" or meeting.

Did you cover everything here? Reopen if not.

@dagar I didn't have a chance to work on this yes, so I don't know. I don't have rights to reopen issues, but that is OK - have added a note in the associated PR so I'll chase up with you next week (if needed).

FYI all, the docs updates are now "live" as the mode docs under here, the doc Landing (Fixed Wing) and these brief notes on takeoff and landing at the end of the "Flying 101" doc.
They may not be perfect, so feel free to raise docs bugs if you see any errors or suggestions for improvement,


Not Working After shutdown or restart

Everything works correctly before restarting or shutting down the phone. When I restart the phone or shutdown and turn on again, it shows me a dialog which asks me to "Select a Home app" and shows two options "Huawei Home" & "CordovaKioskDemo", when I choose "Huawei Home" it works, but which I choose "CordovaKioskDemo" it shows a black screen and then asks me again to "Select a Home app" and keeps on doing the same. So if I choose "Huawei Home" and go to settings I can see that the Default Home App is set to "none", although I have set it before to "CordovaKioskDemo". And if I set it again to "CordovaKioskDemo" and open "CordovaKioskDemo", it shows a black screen and close the app. Could you please help me figure out the issue. I am testing it on HUAWEI Y5 Prime 2018 Android 8.1.0 if that helps. BTW, it works properly on Android version 5.0.1 on GT-I9500 samsung device.

Hello,
Chrome debugging is not showing anything. Logcat shows the following:
09-04 13:07:24.825 24007 24007 D AndroidRuntime: Shutting down VM
09-04 13:07:24.835 24007 24007 E AndroidRuntime: FATAL EXCEPTION: main
09-04 13:07:24.835 24007 24007 E AndroidRuntime: Process: pk.capripio.backgroundtasks, PID: 24007
09-04 13:07:24.835 24007 24007 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{pk.capripio.backgroundtasks/jk.cordova.plugin.kiosk.KioskActivity}: android.view.WindowManager$BadTokenException: Unable to add window android.view.ViewRootImpl$W@b94dc9d -- permission denied for window type 2010

I tried adding permission for android.permission.SYSTEM_ALERT_WINDOW, but it's still the same, any clue?

I am using version 2.0 now https://github.com/hkalina/cordova-plugin-kiosk/tree/v2.0 which seems to work unlike the latest version.


Interaction of layer 'visible' flag with sublayers is unspecified

https://github.com/tangrams/tangram-docs/blob/gh-pages/pages/layers.md
Example:
layers:
  parent-layer:
    visible: false
    child-layer:
      visible: true
      draw:
        polygons:
          order: 1
          color: blue

Is child-layer drawn? The current documentation is ambiguous on this, and we've recently discovered that tangram-js and tangram-es resolve this differently: https://github.com/tangrams/walkabout-style/pull/154
cc @bcamper @nvkelso @meetar

I remember having this conversation – is visible a master switch or an
override toggle?
I think we settled on "override" because everything else works that way,
though it means there's no easy way to turn an entire tree invisible at
once.
On Wed, Mar 15, 2017 at 2:07 PM, Matt Blair<EMAIL_ADDRESS>wrote:

https://github.com/tangrams/tangram-docs/blob/gh-pages/pages/layers.md
Example:
layers:
parent-layer:
visible: false
child-layer:
visible: true
draw:
polygons:
order: 1
color: blue
Is child-layer drawn? The current documentation is ambiguous on this, and
we've recently discovered that tangram-js and tangram-es resolve this
differently: tangrams/walkabout-style#154
https://github.com/tangrams/walkabout-style/pull/154
cc @bcamper https://github.com/bcamper @nvkelso
https://github.com/nvkelso @meetar https://github.com/meetar
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tangrams/tangram-docs/issues/198, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcEwtJ7Oq9ddB4FjcQkmqSWwTQHWPztks5rmCjMgaJpZM4MeUs_
.

I wouldn't be surprised if this conversation has happened before :)
As I see it, the layer visible flag would be more useful as a "master switch" precisely because it behaves differently from draw rules (which are merged bottom-up). As you said, without it there is no way to confidently disable an entire branch of the layer tree. Also, it isn't really the case that "everything else" uses the bottom-up-merge behavior, it's only draw rules that do that.

There are cases when both would be useful in the basemap styles ;) Something to just turn a whole layer and it's children off (enabled: true?) versus the useful visibility cascading – which is necessary for overlays and label variants.

The "cascading" visibility is already available in a way with the visible draw parameter (which is distinct from the visible layer flag). It isn't exactly the same, but it's close enough that it seems almost redundant to have the layer visible flag behave the same way.

…You know what, I had totally conflated those two visible parameters.
Given that I now agree that it makes more sense that the filter-level
visible be a master switch – and maybe renamed? Do we have styles which
rely on it there? And yes, enabled would be less confusing.
On Wed, Mar 15, 2017 at 4:15 PM, Matt Blair<EMAIL_ADDRESS>wrote:

(I am admittedly prejudiced towards the "master switch" behavior because
that's how it is already implemented in tangram-es).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tangrams/tangram-docs/issues/198#issuecomment-286865056,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcEwo4M0FHmAl6jLqBZEhrma4B6eAgUks5rmEbXgaJpZM4MeUs_
.

+1 on enabled for layer property.

I've come around to the idea of a "master layer" switch both because it provides a function we don't have now (a simple way to cull whole sections of the layer tree), and also because it can provide possibly significant run-time savings by allowing the engine to stop processing layers at that point (previously JS has had to keep descending into all sub-layers in case one of them sets visible back to true).
I get the argument for changing the property name to enabled -- would we make it backwards compatible with visible for at least one release cycle though? (Even if the behavior changes a bit.)
I would not like to have both behaviors (overridable and non-overridable) at the layer level (too much complexity); as pointed out, we still have the ability to override the visible parameter within draw groups for achieving this.
That said, I notice that the demo bundled with Tangram JS makes a lot of use of layer visible, and the pattern of turning it on only at the sub-layer level. Are these rendering differently in ES, but we haven't noticed yet? For example: https://github.com/tangrams/tangram/blob/master/demos/scene.yaml#L627-L651

I agree that if we choose a new name for this parameter then we should maintain backward compatibility with visible for some amount of time.
It seems that the current demo scene bundled with Tangram JS does indeed render differently in Tangram ES (we use default scene that is similar but not identical, so we wouldn't have noticed before now).


Bookmarks and date hierarchies

Hello, I am trying to create bookmarks in my report. The report contains a date hierarchy, and the goal is to use the bookmark feature to switch between a monthly report and a weekly report. I have two bookmarks, one with a drill down on month and the other with a drill down on week. Switching bookmarks changes filters, but only keeps the last drill down state. Are there any plans to fix that, I am using March 2018 version optimized for report servers. Thanks

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

ID: 6e579557-27e4-8a24-69b7-55189b0f4966
Version Independent ID: 0c97fa47-9695-aaaf-efcd-63b35362310e
Content: Using bookmarks in Power BI - Power BI
Content Source: powerbi-docs/desktop-bookmarks.md
Service: powerbi
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi @Derwilf -- this sounds like a product question rather than about the docs. I recommend asking in the Power BI Community, https://community.powerbi.com/. Thanks!


deps: Update p-limit to ^4.0.0

Due to node version upgrades, we've missed the dependabot updates for this package.  Catching up a bit.

Oof.  Abandoning this; the compiled typescript is creating a "require" for p-limit which isn't going to work.  Not worth the effort to track this down.


3.8.0 broke for webpack ignore

3.8.0 just broke every webpack build that uses 'noParse: [/braintree-web/],' which was the fix to ignore braintree/webpack errors in the console.

3.8.0 now puts the unbundled code on npm, so the noParse hack is no longer needed. The reason it breaks is because now webpack needs to parse it.
I'm going to leave this open for a few days so other people using webpack with the noParse hack will be able to see the solution, then we will close this issue.

+1
Removing the noParse for braintree-web fixed the issue.


D435i FOV and Aspect Ratio

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>
So we're trying to estimate distance and height of certain colored objects (red) and we're encountering significant error when the camera is above the target object. This is an issue as the camera will be mounted on a drone. We think it's because the streams are enabled to 640x480 (4:3) resolution but the FOV values we're using (69.4, 42.5) are meant for 16:9 aspect ratio. When I try to change the resolution (this code is based off the python example in the SDK concerned with aligning depth to color), I get the following error:
Traceback (most recent call last):                                                                                File "rs-detection.py", line 17, in                                                                                profile = pipeline.start(config)                                                                                RuntimeError: Couldn't resolve requests
This portion of the code causes the error:
`pipeline = rs.pipeline()
config = rs.config()
pipeline_wrapper = rs.pipeline_wrapper(pipeline)
pipeline_profile = config.resolve(pipeline_wrapper)
device = pipeline_profile.get_device()
device_product_line = str(device.get_info(rs.camera_info.product_line))
config.enable_stream(rs.stream.depth, 1920, 1080, rs.format.z16, 30)
config.enable_stream(rs.stream.color, 1920, 1080, rs.format.bgr8, 30)
profile = pipeline.start(config)
depth_sensor = profile.get_device().first_depth_sensor()
depth_scale = depth_sensor.get_depth_scale()
print("Depth scale: ", depth_scale)
align_to = rs.stream.color
align = rs.align(align_to)
fov_x = 69.4
fov_y = 42.5
last_updated_dist = 0
last_updated_height = 0`
And this code works:
`pipeline = rs.pipeline()
config = rs.config()
pipeline_wrapper = rs.pipeline_wrapper(pipeline)
pipeline_profile = config.resolve(pipeline_wrapper)
device = pipeline_profile.get_device()
device_product_line = str(device.get_info(rs.camera_info.product_line))
config.enable_stream(rs.stream.depth, 1920, 1080, rs.format.z16, 30)
config.enable_stream(rs.stream.color, 1920, 1080, rs.format.bgr8, 30)
profile = pipeline.start(config)
depth_sensor = profile.get_device().first_depth_sensor()
depth_scale = depth_sensor.get_depth_scale()
print("Depth scale: ", depth_scale)
align_to = rs.stream.color
align = rs.align(align_to)
fov_x = 69.4
fov_y = 42.5
last_updated_dist = 0
last_updated_height = 0`
Any help on this would be appreciated!

Hi @pranav-pang   The error RuntimeError: Couldn't resolve requests is occurring because you are requesting a depth resolution that the camera does not support.  The maximum depth resolution available is 1280x720.

Lowering the resolution doesn't seem to work either:
`w_max = 1280
h_max = 720
config.enable_stream(rs.stream.depth, w_max, h_max, rs.format.z16, 30)
config.enable_stream(rs.stream.color, w_max, h_max, rs.format.bgr8, 30)
profile = pipeline.start(config)`
I still receive the same error, so maybe I'm not quite understanding some issue here

Is your camera on a USB 2 connection please?  If it is then you will only be able to access a limited range of resolutions and FPS speeds.  For example, on USB 2 1280x720 is supported but only 6 FPS.
You should be able to use 640x480 at 30 FPS on USB 2.  The link below containers chart of supported USB 2 resolutions and the available speeds for each resolution.  Calling a mode not supported on USB 2 will result also in RuntimeError: Couldn't resolve requests

Hi @pranav-pang   Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Remove duplicated logic in gate package.

Signed-off-by: Miguel Ángel Ortuño<EMAIL_ADDRESS>

Logic was added in #242.


Merge pull request #2 from CallMeRabbit/master

Merge pull request #1 from CallMeRabbit/CallMeRabbit-patch-1

Merge pull request #1 from CallMeRabbit/CallMeRabbit-patch-1

Merge pull request #1 from CallMeRabbit/CallMeRabbit-patch-1


Fix typo.

Missing slashes in the URL.

@alexandair : Thanks for your contribution to the Azure documentation! The author, @jluk, has been notified to review your proposed change.


remove useless file from prototypes

About the PR
Removed file named will be filled out when implemented -S from prototypes
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

It's useful. Closed.


Fix folder for maven cache

We should only cache .m2/repository so that the settings.xml is not cache as it also contained the password.
The cache restore was always overwriting the settings.xml, and therefore we changed the order (first restore cache, then load settings.xml from CircleCI env var), to support older caches that still contain settings.xml.

👍


Crashes when opening Bulldozer

Pretty self-explanatory, PokerCore crashes when loading the bulldozer function on newest release (R23) Please lmk if you need more info! Thank youuuu :)

Please hold the left side shift button on your keyboard while selecting the bulldozer options.

You should receive a File saved! prompt and a folder named Your next to the .exe file.
Please upload all 4 files here for further investigation.
You can drag and drop the files into the comment box to upload them.

Hi, I have the same problem, so here are my files, if it helps, thank you in advance
Files.zip

Thx, I think I found one of the problem.
But why you have a player house 8 but no player house 1?

It's a save that I modified to modify some things, I tried to change my tent to a house but it didn't work, I can put it back to 0 if that's the problem.

Thank you so much for your help! Here are my files:
Your.zip

Should have been fixed on the latest build.
Please download again.

Awesome, yes it works now thank youuuu!


enable launching many tasks at once

right now, we have to create tasks for each individual conversation stubs separately and also launching them separately.
This is not scalable if we want to scale our tasks to many more.
While keeping the granular control over each task, it would be very useful to be able to launch many tasks at once with the same configuration so that we can conduct larger experiments more efficiently.

I may need clarification. Do you need a button to launch all the tasks that haven’t been launched yet? Or do you need a panel to create a list of tasks (from different topics) with the same configuration? Or both?

taken care of with #65


Add TextChannel#isNSFW()

If you're not aware, Discord recently added the NSFW-channels feature: TextChannels which are supposed to contain "18+" content should be set as NSFW to warn children.
Thus, I'm suggesting to add support for the NSFW feature in JDA (enabling/disabling).

It's just prefixing the channel with nfsw- (or naming it nsfw). No flags, nothing special. Don't think it matters as you can just change the name.

Yes we are aware of this new "feature". Since this isn't an api feature but a feature of the Discord Client which simply checks the name of a channel we didn't add it. If you really want this to be added feel free to open a Pull Request.
JDA is a wrapper for the discord api not a discord client backend.

@MinnDevelopment someone beat me to it. Thanks anyway.


python3Packages.glances-api: init at 0.2.0

Motivation for this change
Python API for interacting with Glances.
https://github.com/home-assistant-ecosystem/python-glances-api
This is a Home Assistant dependency.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 108425 run on x86_64-linux 1

3 packages built:

python37Packages.glances-api
python38Packages.glances-api
python39Packages.glances-api

Result of nixpkgs-review pr 108425 run on x86_64-linux 1

3 packages built:

python37Packages.glances-api
python38Packages.glances-api
python39Packages.glances-api


fix 循环引用

Please merge this pull request, it seem to fix a retain cycle.

You would better rename that commit message


-race tests fail on Go 1.14

See https://github.com/etcd-io/bbolt/issues/187

Should be fixes with #11


Add shields to README

Added dynamic shields to README.

Yeah, shields give it a more graceful pro-look!


Invite unregistered users by adding collaborators to a layer

When a person (mail address) that is not registered in the system is invited to collaborate, s/he will receive an invitation to join the system.

Closed due to inactivity.


Add Team to Task

The task struct is missing a field for the Team the task is from. For now, this field can just be a string like the other references.

Also, add in a due date for each of the tasks


Roll engine 5e474ee860a3..b230adbb3b5e (4 commits)

https://github.com/flutter/engine/compare/5e474ee860a3...b230adbb3b5e
git log 5e474ee860a3..b230adbb3b5e --first-parent --oneline
2020-03-02<EMAIL_ADDRESS>Roll src/third_party/skia 470f0637aeea..ded437003d0e (6 commits) (flutter/engine#16891)
2020-03-02<EMAIL_ADDRESS>Revert "Try rasterizing images and layers only once , even when their rasterization fails. Further enforce the same access threshold on layers as on Pictures. Previously layers would always be cached. The latter is a semantic change. (#16545)" (flutter/engine#16889)
2020-03-02<EMAIL_ADDRESS>Roll src/third_party/dart fbe9f6115d2f..0b819161d778 (3 commits) (flutter/engine#16888)
2020-03-02<EMAIL_ADDRESS>Roll src/third_party/skia 9dd0bd78b2d7..470f0637aeea (11 commits) (flutter/engine#16887)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Commit queue failed; closing this roll.


versions:set is not updating the dependencies on second run

Lets say I have a multi-module project
Project A (pom.xml)

B (module pom.xml)
C (module pom.xml)
Now in A's pom.xml, under dependency management, i have the following dependency:

<dependency>
   <groupId>com.mycompany</groupId>
   <artifactId>C</artifactId>
   <version>1.0.0-SNAPSHOT</version>
<dependency>

In B's pom.xml I use the above dependency.
<dependency>
   <groupId>com.mycompany</groupId>
   <artifactId>C</artifactId>
<dependency>

Now lets say I run the following command on the root pom.xml (A's pom.xml)
mvn versions:set -DnewVersion=137.0.18 -DprocessDependencies=false
This command only sets the version for the parent and the submodules version (but doesn't update the dependency), which is as expected.
Now if I want to run the following command and process the dependency as well, like this:
mvn versions:set -DnewVersion=137.0.19 -DprocessDependencies=true
Now it does NOT process the dependency. Had if I ran the first command with processDependencies=true, it would have updated the dependency. I am unable to understand why running it the second time its not processing the dependencies? Sounds to me like a bug on versions plugin.

Can you make a sample project which shows the wrong behaviour ?

Created a sample project here.
If we run the following command:
mvn versions:set -DnewVersion=137.0.18 -DprocessDependencies=false
And then run
mvn versions:set -DnewVersion=137.0.19 -DprocessDependencies=true
it doesn't update the dependency.

First test with version 2.4 of versions-maven-plugin...

Hi, I've tested with versions-maven-plugin version 2.4 and get the following output:
~/ws-git-so/MavenVersionsSample (master)$ mvn versions:set -DnewVersion=137.0.23
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] myartifact
[INFO] myutils
[INFO] myutilsb
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building myartifact 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- versions-maven-plugin:2.4:set (default-cli) @ myartifact ---
[INFO] Searching for local aggregator root...
[INFO] Local aggregation root: /Users/kama/ws-git-so/MavenVersionsSample
[INFO] Processing change of com.mycompany:myartifact:0.0.1-SNAPSHOT -> 137.0.23
[INFO] Processing com.mycompany:myartifact
[INFO]     Updating project com.mycompany:myartifact
[INFO]         from version 0.0.1-SNAPSHOT to 137.0.23
[INFO]     Updating dependency com.mycompany:myutils
[INFO]         from version 0.0.1-SNAPSHOT to 137.0.23
[INFO]
[INFO] Processing com.mycompany:myutils
[INFO]     Updating parent com.mycompany:myartifact
[INFO]         from version 0.0.1-SNAPSHOT to 137.0.23
[INFO]
[INFO] Processing com.mycompany:myutilsb
[INFO]     Updating parent com.mycompany:myartifact
[INFO]         from version 0.0.1-SNAPSHOT to 137.0.23
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] myartifact ......................................... SUCCESS [  0.991 s]
[INFO] myutils ............................................ SKIPPED
[INFO] myutilsb ........................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.531 s
[INFO] Finished at: 2017-07-01T11:35:27+02:00
[INFO] Final Memory: 13M/310M
[INFO] -------------------------------------------------------

And if I do a git diff
~/ws-git-so/MavenVersionsSample (master *)$ git di
diff --git a/myutils/pom.xml b/myutils/pom.xml
index 473a3f1..d0c2452 100644
--- a/myutils/pom.xml
+++ b/myutils/pom.xml
@@ -3,7 +3,7 @@
   <parent>
     <groupId>com.mycompany</groupId>
     <artifactId>myartifact</artifactId>
-    <version>0.0.1-SNAPSHOT</version>
+    <version>137.0.23</version>
   </parent>
   <artifactId>myutils</artifactId>
   <name>myutils</name>
diff --git a/myutilsb/pom.xml b/myutilsb/pom.xml
index ae72ea4..6f6de8b 100644
--- a/myutilsb/pom.xml
+++ b/myutilsb/pom.xml
@@ -3,7 +3,7 @@
   <parent>
     <groupId>com.mycompany</groupId>
     <artifactId>myartifact</artifactId>
-    <version>0.0.1-SNAPSHOT</version>
+    <version>137.0.23</version>
   </parent>
   <artifactId>myutilsb</artifactId>
   <dependencies>
diff --git a/pom.xml b/pom.xml
index 47024ba..ccfe477 100644
--- a/pom.xml
+++ b/pom.xml
@@ -4,7 +4,7 @@

   <groupId>com.mycompany</groupId>
   <artifactId>myartifact</artifactId>
-  <version>0.0.1-SNAPSHOT</version>
+  <version>137.0.23</version>
   <packaging>pom</packaging>

   <name>myartifact</name>
@@ -23,7 +23,7 @@
   		<dependency>
   			 <groupId>com.mycompany</groupId>
   			 <artifactId>myutils</artifactId>
-  			  <version>0.0.1-SNAPSHOT</version>
+  			  <version>137.0.23</version>
   		</dependency>
   	</dependencies>
   </dependencyManagement>

which means that all locations are changed according to my command line request with versions-maven-plugin version 2.4.
The question is why do you use -DprocessDependencies=false in your first call ? From my point of view it does not make sense to suppress the changes of the dependencies in dependencyManagement which referencing artifacts within the reactor...


fix: clear form field errors on cancel

Problem
Required field error not being cleared when cancelling input
Solution
On cancel clear form field errors
Additional Notes

Links
Ticket

GitHub issue:
Other links
Verification
Manual tests

Automated tests

[ ] Unit tests added/updated
[ ] E2E tests added/updated
[ ] N/A - (provide a reason)
[ ] deferred - (provide GitHub issue for tracking)

Housekeeping

[ ] No non-essential console logs
[ ] All new files contain license notice

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.86%. Comparing base (70799cb) to head (acf92ac).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1157   +/-   ##
=======================================
  Coverage   93.86%   93.86%
=======================================
  Files         150      150
  Lines        6114     6114
  Branches     1838     1838
=======================================
  Hits         5739     5739
  Misses        357      357
  Partials       18       18

Files
Coverage Δ

...-ui-react/lib/utils/forms/array-field-component.ts
100.00% <ø> (ø)

Continue to review full report in Codecov by Sentry.

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


Tabline + Renamed tab from vim-ctrlspace

Hi, I use vim-ctrlspace, and I'm using a lot of renamed tabs, which is a functionality from vim-ctrlspace. It is pretty much useful.
So, every time I enable the tabline, from vim-airline variable:
let g:airline#extensions#tabline#enabled = 1

then all my renamed tabs (from vim-ctrlspace) don't work in the tabline. They still works on vim-ctrlspace.
I just like to get the renamed names from vim-ctrlspace and put them in tabline when the above variable is enabled.
This works fine when this variable is 0. See:

But when I turn it on, I get this:

So, how do I accomplish this?
Here is the lines I think it maybe related:
let g:airline#extensions#tabline#enabled = 1
let g:airline#extensions#tabline#show_close_button = 0
let g:airline#extensions#tabline#show_tab_nr = 0
let g:airline#extensions#ctrlspace#enabled = 1

:+1:

I'm encountering the same problem.
Perhaps the solution could consist of including an additional formatter option:
let g:airline#extensions#tabline#formatter = 'off'

and then have it included when:
let g:airline#extensions#ctrlspace#enabled = 1

I have same problem, but i don't know what insert in new tabline\formatters\off.vim, for use ctrlspace label

okay, I installed vim-ctrlspace. How do I enable the custom tabline there?

it is not necessary to enable custom tabline, only create new tab, insert in command line :CtrlSpaceLabel and insert custom label for your tab.
With standard tabline this work but if enable airline tabline not work

Please check chrisbra/vim-airline branch tabline_ctrlspace if this fixes your problems

Thanks so much.

With the inclusion of #911 I wonder if this is fixed

if #911 did not close it, please reopen.


question regarding Exchange ECP publishing

Hi,
I'm preparing to upgrade my MCSA certificate to Server 2016 and I recognized this site mentioned publishing of Exchange Control panel Pre-authentication supports only pass-through but this site ( https://docs.microsoft.com/en-us/Exchange/clients/outlook-on-the-web/ad-fs-claims-based-auth#step-4-create-a-relying-party-trust-and-custom-claim-rules-in-ad-fs-for-outlook-on-the-web-and-the-eac ) said there is a possibility to publish with ADFS.  Please check it.
Thanks in advance

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

ID: 6eab4e1f-d36f-3af5-a470-748544db10c6
Version Independent ID: 507b5d01-0566-2459-a9c4-006ce7681a54
Content: Publishing Applications with SharePoint, Exchange and RDG
Content Source: WindowsServerDocs/remote/remote-access/web-application-proxy/Publishing-Applications-with-SharePoint,-Exchange-and-RDG.md
Product: windows-server-threshold
GitHub Login: @billmath
Microsoft Alias: billmath

#please-close


Added documentation for IWRdsEnhancedFastReconnectArbitrator

Documenting the new interface added to support Enhanced Fast Reconnect.

@kavyaln2k : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Closing this pull request. These new doc updates will be handled internally.


Improve the tip distribution charts of the Stats page

Reticketed from #3222.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9293700-improve-the-tip-distribution-charts-of-the-stats-page?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Screenshot from #2499:

Screenshot from 2015-03-05:

Critics of the old version from @whit537 in https://github.com/gratipay/gratipay.com/issues/3222#issuecomment-77670110:

Here are the problems with the old tip distribution charts, and how they're fixed in the standardized tip distribution charts:

The X axis breakpoints—1.78, 3.16, and 5.62—are awkward and unintuitive.The standard charts use the more intuitive breakpoints 1, 2, and 5.
The whitespace between bars is distracting, and inconsistent with our other charts.The standard charts have no whitespace between bars.
The Y labels on each bar are "chartjunk," i.e., pixels which neither directly represent data nor are strictly necessary to orient the viewer.The standard charts show the maximum value, which orients the viewer to the Y scale, providing sufficient information for comparison across bars; specific information is available on hover/click.
Same for the X labels.
The X axis label is inconsistently aligned.The standard charts consistently align the X axis label.
In the X axis label, "in US dollars" is redundant with the unit specifier "($)."The standard charts only use the unit specifier, "($)" (the whole site is in USD, so the dollar sign here is not ambiguous).
The charts have no title, but are introduced with prose instead. The Y axis labels are redundant with the prose introductions.The standard charts have titles that explain the meaning of the Y values.

In general, I subscribe to the Tuftean school of data graphics: Data graphics exist to assist viewers in comprehending patterns in data, i.e., information. Therefore, pixels should either directly represent data, or minimally orient the viewer to the data. Pixels that don't serve this purpose are a distraction that Tufte calls, "chartjunk."
If you would like to continue to claim that "[t]he new tip distribution charts look terrible," please explain your reasoning.
One thing I don't like about the standardized tip distribution charts is that the bars are too wide relative to the labels and to other charts, due to the fewer number of bars compared to the time series charts. If we want to tinker with the tip distribution charts let's make a new ticket. The current ticket is about standardizing tables across the site, with our general treatment of charts being a parallel.

The X axis breakpoints—1.78, 3.16, and 5.62—are awkward and unintuitive.

It's a logarithmic scale, I switched to that because the previous linear scale wasn't adequate.

The whitespace between bars is distracting, and inconsistent with our other charts.

The other charts are time series, these are distributions, why should they look the same ? Bar charts often have whitespace between bars, it's not unusual and I think it looks better for this kind of chart.

The Y labels on each bar are "chartjunk," i.e., pixels which neither directly represent data nor are strictly necessary to orient the viewer.The standard charts show the maximum value, which orients the viewer to the Y scale, providing sufficient information for comparison across bars; specific information is available on hover/click.

I think there are valid arguments for both sides here. Too much information can be distracting, but having to hover/click to see the data can be annoying. It's a balance.

Same for the X labels.

Here I completely disagree. On the time series charts you don't need to see all the X ticks because you know that each bar represents a week and the number increases by 1 for each bar. But on the distribution charts each bar represents a range, and without all the thresholds displayed you don't really know what you're looking at.

The X axis label is inconsistently aligned.

Inconsistently aligned with what ?

In the X axis label, "in US dollars" is redundant with the unit specifier "($)."
The charts have no title, but are introduced with prose instead. The Y axis labels are redundant with the prose introductions.The standard charts have titles that explain the meaning of the Y values.

I'm fine with these changes, they're rather small details to me.


Removed extra apostrophe in TeamCity sanitization tokens

Fixes issue #725
TeamCity lacks Unit Tests, I'll add some in PR #714
//cc @gep13

@mholo65 perfect, thank you!

@mholo65 with regard to adding Unit Tests to an existing PR, I think we would prefer to keep the PR's as focused as possible on the subject of the PR.  i.e. add Unit Tests for the new functionality being added in that PR, but perhaps a separate PR for Unit Tests for existing functionality.

@gep13 Sounds good!

Oops. Thanks for catching this!


TechDocs: fix unclickable external links

Hey, I just made a Pull Request!
closes: #2322

:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

Great! Thanks! 🎉


Animation doesn't work in WebXR

I tried putting the unstable-webxr attribute on our animation samples and found the model is rendered statically in AR mode. The problem is the logic we have in our Renderer class regarding animation, exposure, and shadows, which does not exist in the ARRenderer class. Looks like we need a bit of refactoring to share this code.

Looks like we need a bit of refactoring to share this code.

Definitely 👍


Navbar breaking into new line and white space

For some languages, the navbar breaks into the next line

Also on small devices, there is some white space below navbar

@VaibhavArora314 Assign me i will fix this issue 👍

@VaibhavArora314 I am changing the whole navbar, trust me it will look nice and like professional one 👍

@VaibhavArora314 what about we follow the previous approach we followed in the style share ?

@VaibhavArora314 what about we follow the previous approach we followed in the style share ?

Go ahead just make sure it looks good and possibly better than the current one.

@VaibhavArora314 what about we follow the previous approach we followed in the style share ?

Go ahead just make sure it looks good and possibly better than the current one.

Noted 🫡 !

@VaibhavArora314 you can close this issue, to avoid many issues in style share :)


Empty string in the key column gives strange behaviour

When the first row of a csv file contains an empty value in the Key to group by column, it shows inconsistent results in the marker table. Either 0, or undefined, or 0,0,0,0,0,0,0,0...0,0,0,0, or empty, depending on the number of rows with empty keys.
I believe the Papa Parse library is to blame here. @FredrikNysjo could you have a look?
Here is a csv file to reproduce all behaviours:
celltype_Rayon2021.csv
Which gives:

Expected behaviour:

And here is a minimal example with two different displayed values for empty column:
x,y,target
0,0,
0,1,"not empty"
1,1,

Fixed in commit 5fb3099. Empty values are now treated as strings when checking if a column is numerical.


Update nginx to keep up with ubuntu

@natefoo can you update the ppa after merging?
Changelog

@natefoo why is the old one not available anymore?
Docker now fails with:
E: Version '1.4.6-1ubuntu3.3ppa1' for 'nginx-extras' was not found

because I fixed it at this version to not get the other error when the ubuntu nginx package get favoured over the ppa package.

that's --arguably-- good, given that these are security-fixes.

Not really if your Docker build stops building unreliably.

I did not remove the packages. It would appear that Launchpad or the PPA did this itself. =(

https://help.launchpad.net/Packaging/PPA/Deleting

The easiest alternative to replace a broken source is always to upload a package with a higher version number and let the system automatically supersede and remove the older version. You should not attempt to use deletion requests to re-upload the same source version with different contents, as this is still prevented even after the content has been deleted.

It appears to be by design and I am not sure of an easy fix. =(

Ok, than it does not make sense to bind to a specific version and we need to live with the fact that some builds break as soon as Ubuntu increases the version number.
Thanks @natefoo!

yup, thanks @natefoo


[bugfix] Fix docs warnings

Description
As title.
Backporting
This change should be backported to the previous releases, please add the relevant labels.
Refer here to resolve backport conflicts if any.

[x] 2016
[x] 2017
[x] 2018
[x] 2019
[x] 2020
[x] 2021
[x] 2022

Type of change
Please check the options that are relevant, the corresponding labels will be added automatically.

[ ] Bug Fix (non-breaking change which fixes an issue)

[ ] bug (fixes an issue)
[ ] test (adds/updates test)
[ ] typo (fixes typo)
[ ] refactor (refactors code)
[ ] reformat with black (check this to reformat the code with black)

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

[ ] typing (adds/updates typing annotations)

[ ] Documentation Update

[ ] docs (adds/updates documentation)
[ ] docs preview (check this to preview docs)

[ ] Automation/Translation/Release

[ ] workflow (adds/updates workflow)
[ ] release (adds/updates release)
[ ] translation (adds/updates translation)

Codecov Report

Merging #4104 (eca6f30) into 2023 (c25209a) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             2023    #4104      +/-   ##
==========================================
- Coverage   88.52%   88.52%   -0.01%
==========================================
  Files         931      931
  Lines       27293    27292       -1
==========================================
- Hits        24160    24159       -1
  Misses       3133     3133

Flag
Coverage Δ

2023
88.52% <100.00%> (-0.01%)
:arrow_down:

Python-3.10
88.52% <100.00%> (-0.01%)
:arrow_down:

Python-3.11
88.52% <100.00%> (-0.01%)
:arrow_down:

Python-3.7
88.06% <100.00%> (-0.01%)
:arrow_down:

Python-3.8
88.52% <100.00%> (-0.01%)
:arrow_down:

Python-3.9
88.52% <100.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/abaqus/Animation/AnimationController.py
76.47% <ø> (ø)

src/abaqus/Animation/AnimationSession.py
81.25% <ø> (ø)

src/abaqus/Animation/Movie.py
73.52% <ø> (ø)

src/abaqus/Annotation/AnimationUserData.py
77.77% <ø> (ø)

src/abaqus/Annotation/Arrow.py
64.44% <ø> (ø)

src/abaqus/Annotation/Text.py
65.85% <ø> (ø)

src/abaqus/Assembly/AssemblyBase.py
76.84% <ø> (ø)

src/abaqus/Assembly/PartInstance.py
87.50% <ø> (ø)

src/abaqus/BasicGeometry/Cell.py
76.47% <ø> (ø)

src/abaqus/BasicGeometry/CellArray.py
78.57% <ø> (ø)

... and 84 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Improve help on tokens

This PR improves the user experience by adding two things:

An additional help topic on the different token types and how they affect the CLI usage
An explicit error message when running commands which do not support using an ingest-only token

Overriding the token by flag or environment bypasses the check by assuming a personal token was passed. This is crucial because a deployment can be configured with an ingest token but a personal token can be specified as override.

Love it. Would be even better if there was a command to "upgrade" a token. You could suggest that in the help even


Allow range constraints to reference other variables

One idea being:

Date adverse event started: _____
Date adverse event resolved: _____

Question 2 can never have a date value that comes before Question 1 (they could be equal).

Update: We should be able to get at this issue another way through Checks. See #449

@mrueschman do the current version of checks allow this to be done?

I don't think so, since we cannot compare a variable to another variable?

So taking a look at this, it may be possible to create a rule (or calculation perhaps) at the bottom of a design that would allow this to be captured on the sheet level. Other ideas would be adding the ability to add custom rules to the sheet errors checker, which is similar to what checks do, but instead do it by expression instead. Closing this issue, but we can revisit later if we want to focus on one of these approaches.


Write a guide on transitioning to microservices

What I mean by this is how you transition from your "monolithic" feathers app to a few smaller services. Again, using the context of that chat app will work great. We should be able to split it up into 3 services:

A user service
An auth service
A message service

We can show how they all talk to each other and possibly how you can now deploy this on Heroku or something.

I have an account in trace. I can give it to you if it is necessary for the application.

How is this coming along? I need something like this to give me a broad view of how I can structure my application as I delve into this. +1

Haven't started it yet. We've already used feathers-sync but we've been tackling other more pressing things. The main release issue is more or less in priority order so it might be a bit before the core team gets to it.

@ekryski saying

A user service
An auth service
A message service

are you missing the gateway service ?

I think it was implied.

Closing in favour of https://github.com/feathersjs/feathers/issues/157


[test-framework] Integrate Galley into the Test Framework for Local Environment.

Currently, the Local environment of the test framework uses Mixer's file-based APIs and Pilot's in-memory APIs to push configuration. We should make Galley as the sole way of distributing config in the system to these components in the local environment.
When the test framework starts up in Local environment, it should always startup and initialize Galley. When environment.Configure is called, the configuration should be pushed to Galley (initially through a file-based model that Galley currently supports. Over time, it can be purely in memory).
The local versions of the other components (i.e. Mixer and Pilot) should be configured to use the MCP protocol to get their configuration from the local Galley.

sorry for late. working on this now

@ozevren   code is in: https://github.com/istio/istio/pull/10617

With the new framework refactroring, this is already done.


error

Hi everyone
Thanks for the software,
When starting SDRReceiver, I received an error message "sample_rate ini file key not found or equal to zero, check ini file name and key values"
download the .ini file again and the same error
thanks
Claudio

Hi Claudio,
In this case it would seem the program finds the ini file (otherwise you would have gotten a different error) but it seems the value for sample_rate is not found or it is zero. Can you make sure the ini file you pass with the -s switch starts with a valid value for sample_rate, i.e.
sample_rate=1536000
/Jeroen

Closing.


Errors in images

For some reason, errors in images included through responsive_image are reported as errors in the template that includes them. For instance, if _layout.slime includes the image, the error will be in the _layout.slime. This could be fine, but the layout is used in multiple places and the error on that file will be overwritten.

Addressed in https://github.com/still-ex/still/commit/042729f8a0cb20471088f9c6b2e16b25f3396a1f


could you  please upload the sql_database.sql file? thanks

could you  please upload the sql_database.sql file? thanks

I actually didn't used this file for anything. You should be able to run this app without this file.
You can find some dummy data in server/seed/ directory to run the application.


Prevent browser popup when Ctrl-S / Cmd-S triggered

Is your feature request related to a problem? Please describe.
Ctrl-S / Cmd-S will trigger a browser popup to save webpage, it's annoying, but it's hard to get out of that habit...
Describe the solution you'd like

Just prevent event when Ctrl-S / Cmd-S
Or change that shortcut to other function such as copy share url to clipboard, just like typescript playground

@festoney8 if you would like to have a sharing snippet on save functionality - please update the issue description.
Also, I would like to get more feedback from a community on this feature request.

For me, simply preventing the popup is enough.
I tested Ctrl-S in several playgrounds while creating this issue and found that this operation, both in TypeScript playground and official Go playground, is related to sharing.
Perhaps this is a more common practice? So I included that option in the solution. It's up to your decision.
I'd like to contribute but unfortunately I'm not familiar with react.


Upgrade com.github.ekryd.sortpom:sortpom-maven-plugin 2.14.1 -> 2.15.0

This PR contains the following updates:

Package
Update
Change

com.github.ekryd.sortpom:sortpom-maven-plugin
minor
2.14.1 -> 2.15.0

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade sortpom-maven-plugin 2.14.1 -> 2.15.0

See:
- https://github.com/Ekryd/sortpom/wiki/Versions
- https://github.com/Ekryd/sortpom/releases/tag/sortpom-parent-2.15.0
- https://github.com/Ekryd/sortpom/compare/sortpom-parent-2.14.1...sortpom-parent-2.15.0

Do we want to tweak anything related to Ekryd/sortpom#71?

Yep, updating verify-poms.sh is on my TODO list :)


Detected not satisfied dependencies: 	test-generator: not installed, required: == 0.1.1

There is an issue with the dependencies missing in the tensorflow to openvino (101) demo.
quick fix is to run
pip install test-generator==0.1.1
before starting jupyter

I found out the issue is related to 'preinstalled' openvino and the setupvar.sh script was pre-activated.
-ray


fix: use the same logic as helm-secrets when decoding secrets

helm-secrets uses the HELM_SECRETS_DEC_SUFFIX env var to define the name of the output file
we should have the same logic in helmfile, to come up with the same filename
It only affects people using the HELM_SECRETS_DEC_SUFFIX env var
Use-case: if you want to run multiple helmfile commands in parallel, without conflicts. in this case, you need to decrypt secrets with different suffixes.

thanks for the quick review & merge!


[Question] Name of the font

What is the name of Source Code Pro Powerline Awesome font (patched one)? I want to use it my editor (VS Code), in which I had to type the name of the font to use it, but I am not able to get its right name. :-/

Maybe I don't understand the question but the original font is SourceCodePro. Is this the answer you were looking for?

I used Hack instead.


Update docs for CodePair setup

What this PR does / why we need it?
This PR modifies the documentation to update the environment variable name from VITE_APP_YORKIE_RPC_ADDR to VITE_YORKIE_API_ADDR and reference the README for CodePair setup.
Any background context you want to provide?
What are the relevant tickets?

Fixes #
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

Summary by CodeRabbit

Documentation

Updated setup instructions for the CodePair repository, emphasizing navigation to the frontend folder.
Clarified naming convention by changing VITE_APP_YORKIE_RPC_ADDR to VITE_YORKIE_API_ADDR.
Streamlined setup process by consolidating command instructions to refer to the README for further guidance.

@hackerwins @krapie
How about changing the example in the documentation from CodePair to other example?
CodePair involves more steps, like setting up a GitHub OAuth key and running a backend server, which makes it too complicated for testing the Yorkie cluster.


save and monitor disk space

changes a few cp to mv
removes temporary tars
checks disk space a few times during run

it worked -- merging @bkase


Specifications on the output of CogAgent-Agent (grounding)

Feature request  / 功能建议
Thank you for this nice project. I am interested in reproducing your experiment results on the android-in-the-wild (AitW) GUI navigation tasks. And for that, I need a mapping from your model's output to AitW's action space.
I know from the readme that I should be looking for model's output after Grounded Operation:, for example, Grounded Operation:tap [[681,808]]. However, it's hard to guess the entire action space by simply guessing.
Therefore, I wonder if you can provide a specification on how the action space is exactlly defined and how to parse them into AitW specifications?
Motivation / 动机
Improve reproducibility
Your contribution / 您的贡献
N/A

Based on the format of our current training dataset, we can only produce outputs in a fully linguistic format for now. Therefore, we have formatted the output to achieve the current effect. The notation like tap [[681,808]] actually refers to pressing a specific button. Typically, actions like tap and similar are not very frequent and have a certain repetitiveness. In our future work, we will improve this aspect, aiming to achieve better formatting and standardized outputs.


1.3 ProduceAsync changes

Description
I'm trying to upgrade our app from 0.11.4 to 1.3.
One of our tests is to drop the Kafka broker during processing.
In 0.11.4 we caught this error with the following code and used the Result.Error.HasError member
var task = producer.ProduceAsync(topic, messageKey, message, partition.Value) :
return task.Result;
This test doesn't work well in 1.3 ,
Firstly the Result.Error property is no longer in the DeliveryResult class
Secondly the test just hangs in ProduceAsync never returning and never throwing out.
I am using a Console App to test this and I can see ERRORS / FAIL  being written to the Console - it must be from ProduceAsync - but no result is returned or no exception thrown see the  screenshot below.

How can I get ProduceAsync to throw/return  from this error ?
How to reproduce
Using 1.3 just take the Broker down during Producer processing.
Checklist
Please provide the following information:

[ ] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[ ] Confluent.Kafka nuget version.
[ ] Apache Kafka version.
[ ] Client configuration.
[ ] Operating system.
[ ] Provide logs (with "debug" : "..." as necessary in configuration).
[ ] Provide broker log excerpts.
[ ] Critical issue.

Errors exposed via the Error property of the delivery report in 0.11.x are exposed as exceptions in 1.x API. How long are you waiting? the default settings of retries=2 and socket.timeout.ms=60000 will result in an error after 3 minutes (iirc).

Well I do get a Local timeout exception but it's well after the fact - more than 300 seconds after the Broker has been dropped.
The first screenshot shows the producer properties I use. Socket Timeout 3000 and retries of 1

The next screenshot shows the code capturing the Local timeout exception after 5 minutes.

This screenshot shows the Console log and the exception of the Kafka Broker at 09
:41:41 - this log also has my debug text and I used these timestamps, but you can see FAIL and ERROR messages being written by your code.

This last screenshot is the console app after ProduceAsync throws the excpetion and returns at 09:47:28

Is there any other property I can use to detect the problem in a more timely manner.
Thanks,
John

It starts to behave much better when I set the message.timeout.ms property to 3000ms
I think that's the property I needed.
Thanks for looking at it,
John

Yep, MessageTimouetMs.
The idea with the API/default config is that you give your message to the .net client, then it does whatever's necessary to deliver it to the cluster under the terms you've configured (retries, timeouts etc). i.e. the client attempts to abstract away what you're trying to do manually.