Streams deployment task logs if there is only one task

Closes #346
I have not attempted any sort of implementation for the case where multiple tasks exist in a deployment, but even with the simple case of a single task, I'm unsure how this would be tested. I'd appreciate it if someone would point me in the right direction.
The best idea I've had so far is to use a fixture where the pod prints some output over several seconds, and assert that the logs reflect this in the timestamps at the beginning of each line. Indeed, if I do this and run the test with PRINT_LOGS=1, I can see that it works. Anyone have a better idea?

[INFO][2019-03-01 16:31:21 -0300]       ------------------------------------Phase 1: Initializing deploy------------------------------------
[INFO][2019-03-01 16:31:22 -0300]       Context minikube found
[INFO][2019-03-01 16:31:22 -0300]       Namespace k8sdeploy-test-service-account-predeployed-bef-5bda741b20f5ae34 found
[INFO][2019-03-01 16:31:22 -0300]       All required parameters and files are present
[INFO][2019-03-01 16:31:22 -0300]       Discovering templates:
[INFO][2019-03-01 16:31:22 -0300]         - Pod/unmanaged-pod-k995a259-fbc8980b
[INFO][2019-03-01 16:31:22 -0300]         - ServiceAccount/build-robot
[INFO][2019-03-01 16:31:22 -0300]         - ConfigMap/hello-cloud-configmap-data
[INFO][2019-03-01 16:31:23 -0300]
[INFO][2019-03-01 16:31:23 -0300]       ----------------------------Phase 2: Checking initial resource statuses-----------------------------
[INFO][2019-03-01 16:31:23 -0300]       Pod/unmanaged-pod-k995a259-fbc8980b               Unknown
[INFO][2019-03-01 16:31:23 -0300]       ServiceAccount/build-robot                        Not Found
[INFO][2019-03-01 16:31:23 -0300]       ConfigMap/hello-cloud-configmap-data              Not Found
[INFO][2019-03-01 16:31:23 -0300]
[INFO][2019-03-01 16:31:23 -0300]       ------------------------------Phase 3: Predeploying priority resources------------------------------
[INFO][2019-03-01 16:31:23 -0300]       Deploying ConfigMap/hello-cloud-configmap-data (timeout: 30s)
[INFO][2019-03-01 16:31:23 -0300]       Successfully deployed in 0.4s: ConfigMap/hello-cloud-configmap-data
[INFO][2019-03-01 16:31:23 -0300]
[INFO][2019-03-01 16:31:23 -0300]       Deploying ServiceAccount/build-robot (timeout: 30s)
[INFO][2019-03-01 16:31:24 -0300]       Successfully deployed in 0.4s: ServiceAccount/build-robot
[INFO][2019-03-01 16:31:24 -0300]
[INFO][2019-03-01 16:31:24 -0300]       Deploying Pod/unmanaged-pod-k995a259-fbc8980b (timeout: 60s)
[INFO][2019-03-01 16:31:24 -0300]       Streaming logs from Pod/unmanaged-pod-k995a259-fbc8980b container 'hello-cloud':
[INFO][2019-03-01 16:31:27 -0300]       Hello from the command runner!
[INFO][2019-03-01 16:31:27 -0300]       Successfully deployed in 3.6s: Pod/unmanaged-pod-k995a259-fbc8980b
[INFO][2019-03-01 16:31:27 -0300]
[INFO][2019-03-01 16:31:27 -0300]
[INFO][2019-03-01 16:31:27 -0300]       ----------------------------------Phase 4: Deploying all resources----------------------------------
[INFO][2019-03-01 16:31:27 -0300]       Deploying resources:
[INFO][2019-03-01 16:31:27 -0300]       - Pod/unmanaged-pod-k995a259-fbc8980b (timeout: 60s)
[INFO][2019-03-01 16:31:27 -0300]       - ServiceAccount/build-robot (timeout: 30s)
[INFO][2019-03-01 16:31:27 -0300]       - ConfigMap/hello-cloud-configmap-data (timeout: 30s)
[INFO][2019-03-01 16:31:28 -0300]       Successfully deployed in 0.7s: Pod/unmanaged-pod-k995a259-fbc8980b, ServiceAccount/build-robot, ConfigMap/hello-cloud-configmap-data
[INFO][2019-03-01 16:31:28 -0300]
[INFO][2019-03-01 16:31:28 -0300]       ------------------------------------------Result: SUCCESS-------------------------------------------
[INFO][2019-03-01 16:31:28 -0300]       Successfully deployed 3 resources
[INFO][2019-03-01 16:31:28 -0300]
[INFO][2019-03-01 16:31:28 -0300]       Successful resources
[INFO][2019-03-01 16:31:28 -0300]       Pod/unmanaged-pod-k995a259-fbc8980b               Succeeded
[INFO][2019-03-01 16:31:28 -0300]       ServiceAccount/build-robot                        Created
[INFO][2019-03-01 16:31:28 -0300]       ConfigMap/hello-cloud-configmap-data              Available

[INFO][2019-03-01 16:30:55 -0300]       -------------------------------------Phase 1: Initializing task-------------------------------------
[INFO][2019-03-01 16:30:55 -0300]       Validating configuration
[INFO][2019-03-01 16:30:55 -0300]       Using namespace 'k8sdeploy-test-run-with-verify-result-success-b05621642456a99b' in context 'minikube'
[INFO][2019-03-01 16:30:55 -0300]       Using template 'hello-cloud-template-runner'
[INFO][2019-03-01 16:30:55 -0300]
[INFO][2019-03-01 16:30:55 -0300]       ----------------------------------------Phase 2: Running pod----------------------------------------
[INFO][2019-03-01 16:30:55 -0300]       Creating pod 'task-runner-224354af870c884c'
[INFO][2019-03-01 16:30:55 -0300]       Pod creation succeeded
[INFO][2019-03-01 16:30:55 -0300]
[INFO][2019-03-01 16:30:55 -0300]       --------------------------------------Phase 3: Streaming logs---------------------------------------
[INFO][2019-03-01 16:30:56 -0300]       Streaming logs from Pod/task-runner-224354af870c884c container 'task-runner':
[INFO][2019-03-01 16:30:59 -0300]       Line 1
[INFO][2019-03-01 16:30:59 -0300]       Line 2
[INFO][2019-03-01 16:30:59 -0300]       Line 3
[INFO][2019-03-01 16:30:59 -0300]       Line 4
[INFO][2019-03-01 16:30:59 -0300]       Line 5
[INFO][2019-03-01 16:30:59 -0300]       Line 6
[INFO][2019-03-01 16:30:59 -0300]       Line 7
[INFO][2019-03-01 16:30:59 -0300]       Line 8
[INFO][2019-03-01 16:31:01 -0300]       Successfully ran in 5.3s: Pod/task-runner-224354af870c884c
[INFO][2019-03-01 16:31:01 -0300]
[INFO][2019-03-01 16:31:01 -0300]       ------------------------------------------Result: SUCCESS-------------------------------------------
[INFO][2019-03-01 16:31:01 -0300]       Successfully ran 1 resource
[INFO][2019-03-01 16:31:01 -0300]
[INFO][2019-03-01 16:31:01 -0300]       Successful resources
[INFO][2019-03-01 16:31:01 -0300]       Pod/task-runner-224354af870c884c                  Succeeded

Rebased for the last time since #441 was merged. Should be good to go.


Prediction on one sample produces error

NOTE: ISSUES ARE NOT FOR CODE HELP - Ask for Help at https://stackoverflow.com
Your issue may already be reported!
Also, please search on the issue tracker before creating one.

I'm submitting a ...

[X] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Issue Description

When calling the proba_predict method with a single sample the following error is produced:

Prediction sets with more than one work just fine.
Expected Behavior
A single probability is returned.
Current Behavior
This error is returned deep within the predict pipeline:

Possible Solution
Your Code

Error message

Your Local environment

Operating System, Ubuntu
Python, version 3.10
Outputs of pip freeze or conda list

My current workaround, duplicating the single row and only use the probabilities from one:


DB read path: Convert a few more straightforward cases to the DB

Downloads via www/ebooks/download.php
Artworks
List of collections, i.e., /collections
List of ebooks in  a collection, e.g., /collections/the-bbcs-100-greatest-british-novels-2015
List of tags for use on templates/SearchForm.php, which is part of www/ebooks/index.php

Thanks for the review!
I addressed the feedback about Collections, so I'll reply to the comment thread above about that.
I didn't update the Tags table yet.

Thanks for thinking about this more and the two options. I like what you wrote about not adding a new term and being consistent with the code, so I went with the second suggestion. I removed the term membership and added Collection::AddEbook and Collection::RemoveEbook methods.
761e01c5fa8f98e48180478dc7201d55e9192e95 is the commit with the code to review.
We haven't talked too much about this passage from Ebook::FromFilesystem, but I could use your guidance there for naming and readability:
		// Get SE collections
		$collections = [];
		$collectionPositions = [];
		foreach($xml->xpath('/package/metadata/meta[@property="belongs-to-collection"]') ?: [] as $collection){
			$c = Collection::FromName($collection);
			$id = $collection->attributes()->id ?? '';

			foreach($xml->xpath('/package/metadata/meta[@refines="#' . $id . '"][@property="group-position"]') ?: [] as $s){
				$collectionPositions[$c->UrlName] = (int)$s;
			}
			foreach($xml->xpath('/package/metadata/meta[@refines="#' . $id . '"][@property="collection-type"]') ?: [] as $s){
				$c->Type = (string)$s;
			}
			$collections[] = $c;
		}
		$ebookFromFilesystem->Collections = $collections;
		$ebookFromFilesystem->CollectionPositions = $collectionPositions;

On master, we previously stashed the sequence number on the Collection object, but that's not an option anymore:
https://github.com/standardebooks/web/blob/486167dd431a3ce96b2e83a64e8f05777362616e/lib/Ebook.php#L279
Storing the collection positions in this array seems reasonable to me:
	/** @var array<string, int> $_CollectionPositions */
	protected $_CollectionPositions = null;

but I could make a new object out of it. It would be similar to the CollectionMembership object you proposed above, potentially with a different name. Having the array keys be the UrlName is convenient, but I could work around it.
Also, I want to be sensitive to your review time. If this PR has too many commits, I could:

Stash the other commits about downloads, artworks, tags, etc., and use this commit to perfect Collections
Drop the Collections work from this PR, commit the more straightforward commits, then try again fresh

Right, that's why I proposed CollectionMembership, because the sequence number has to go somewhere, but we don't have a logical place for it the way it currently stands. I suppose you could store it as in an array as a property of Ebook like you suggest, but then we've decoupled collections with their positions and we have to match the two by searching the array every time we want the sequence number. That's not great encapsulation and will invite errors later down the line, say if in a few years we have to revisit this code to in order to put sequence numbers somewhere else.
In any case, go ahead with how you think is best, we can always just see how things pan out in real life and if it becomes annoying we can always change it.

Thanks for the extra feedback about encapsulation and future maintenance. I also appreciate the attitude that we can always change it later.
I force pushed two commits:
ec54e3ecd3e24cf548b8e199061cfe0947232ce6: Adds the CollectionMembership class
9e6b090b863c61865296227b14c2fb355dc6b923: Addresses the Tag comment above about adding a Type enum
Onward to some more interesting DB read path cases!


Occasional chunk gen failure in cancelling something ceases all generation

Noted this several times testing MetalRenegades, both before and after #4368. Easy to provoke by flying around like a mad person with hspeed and ghost in MR (on a decently beefy system with 3gb ram assigned via gradlew jar game)
Theory: If chunk generation can't keep up and the player leaves an area not yet generated that now becomes irrelevant for chunk gen (out of range) then something can happen (or always happens?) that throws an exception when trying to cancel the chunk gen request. As a consequence all chunks stop generating.
Edit: Possible of interest to @DarkWeird as I'm guessing this might have been affected during recent chunk refactoring/optimization, or maybe @4Denthusiast as also tweaking at chunk things.
Edit2: Maybe also consider addressing code review naming question from https://github.com/MovingBlocks/Terasology/pull/4368/files/6946c5d6c35a7c1b44055d072a74dd4704b02260#diff-a215d671ba9fad5fdaa2fb381629c511b81df12fb2f19024318ba3830f16e97e when in there messing with chunky things anyway
Edit to edit2: the term "ready" might be more aligned than "prepare" although "readied" might still be closer yet?
Example 1:
11:19:30.308 [main] INFO  o.t.p.i.ReadWriteStorageManager - Auto Saving - Snapshot created: Writing phase starts
11:19:31.617 [Saving-0] INFO  o.t.p.internal.SaveTransaction - Save game finished
Exception in thread "Chunk-Processing-Reactor" java.util.concurrent.CancellationException
        at java.util.concurrent.FutureTask.report(FutureTask.java:121)
        at java.util.concurrent.FutureTask.get(FutureTask.java:192)
        at org.terasology.world.chunks.pipeline.PositionFuture.get(PositionFuture.java:49)
        at org.terasology.world.chunks.pipeline.ChunkProcessingPipeline.onStageDone(ChunkProcessingPipeline.java:121)
        at org.terasology.world.chunks.pipeline.ChunkProcessingPipeline.chunkTaskHandler(ChunkProcessingPipeline.java:108)
        at java.lang.Thread.run(Thread.java:745)
11:19:38.205 [main] ERROR o.t.e.e.internal.PojoEntityManager - Adding a component (class org.terasology.network.NetworkComponent) over an existing component for entity 2577
11:19:38.592 [main] INFO  o.t.d.construction.BlockBufferSystem - Buffer before: 162, Placed: 162, Removed: 162, Buffer after: 0

Example 2
11:21:24.071 [main] INFO  o.t.logic.console.ConsoleImpl - [CONSOLE] High-speed mode activated
11:21:27.207 [main] ERROR o.t.p.t.TypeHandlerLibrary - Unsupported field: 'DynamicCities:TreeFacet.relData'
Exception in thread "Chunk-Processing-Reactor" java.util.concurrent.CancellationException
        at java.util.concurrent.FutureTask.report(FutureTask.java:121)
        at java.util.concurrent.FutureTask.get(FutureTask.java:192)
        at org.terasology.world.chunks.pipeline.PositionFuture.get(PositionFuture.java:49)
        at org.terasology.world.chunks.pipeline.ChunkProcessingPipeline.onStageDone(ChunkProcessingPipeline.java:121)
        at org.terasology.world.chunks.pipeline.ChunkProcessingPipeline.chunkTaskHandler(ChunkProcessingPipeline.java:108)
        at java.lang.Thread.run(Thread.java:745)
11:21:36.462 [main] INFO  o.t.p.i.ReadWriteStorageManager - Auto Saving - Creating game snapshot
11:21:36.474 [main] INFO  o.t.p.i.ReadWriteStorageManager - Auto Saving - Snapshot created: Writing phase starts

If this is the same thing I noticed before than this can be "fixed" in game by lowering the view distance (temporarily). This re-triggers chunk gen, and as it takes the player's position into account no terrain will pop up in front and around you.
This did not always work, though, but might give more clues about what is going on...

If this is the same thing I noticed before than this can be "fixed" in game by lowering the view distance (temporarily). This re-triggers chunk gen, and as it takes the player's position into account no terrain will pop up in front and around you.
This did not always work, though, but might give more clues about what is going on...


Latest version complains about export in between decorator and class

I started getting this after Sort Imports for VS Code was updated, and tested in the cli which also gave the error.
Error sorting imports: SyntaxError: Using the export keyword between a decorator and a class is not allowed. Please use `export @dec class` instead. (22:0)

example source
import styles from './index.scss';

@cssModule(styles)
export class Sidebar extends React.Component {
}

Not sure if this is just progress, but figured I'd raise it since it's affecting me, and possibly others.

Hi @dcwither
I hope I can find some time on the weekend to fix this. Thanks for reporting this issue.

Hello @renke In 6.0.0 the same problem again. Error sorting imports: SyntaxError: Using the export keyword between a decorator and a class is not allowed. Please use export @dec class instead. (14:0).
`import { ActivatedRoute, Router } from '@angular/router';
import { Component, EventEmitter } from '@angular/core';
import { MpAPI, MpStorage } from '../../../shared';
import { MaterializeAction } from 'angular2-materialize';
// import { isSuccess } from '@angular/http/src/http_utils';
@Component({
selector: 'discussion',
templateUrl: './discussion.component.html'
})
export class DiscussionComponent {}`

Issue seems to be back.


fix(DeviceActionModal): avoid resetting the result onModalHide

📝 Description
While working on https://github.com/LedgerHQ/ledger-live/pull/2579 and https://github.com/LedgerHQ/ledger-live/pull/2595 with @alexandremgo, we saw that we probably don't need to reset the result here.
When I checked the old code in the ledger-live-mobile repo we weren't doing this reset or even having a state here for the result.
❓ Context

Impacted projects: ledger-live-mobile
Linked resource(s): ``

✅ Checklist

[ ] Test coverage Tested on the manager and with the dummy-wallet-app
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Actually this also fixes the bluetooth disconnecting because we're listening again on DeviceConnect for the wallet-api without this PR


Add nginx access logs, with support for traceId if found.

R: @apolito CC: @dlorenc @liqianluo

@apolito PTAL

This version will capture all access logs including health checks; even if it passes review let's hold off on merging until we've decided for sure that's what we want. We might have to add logic to filter them out.

We've decided NOT to filter out health checks at this time, so that's no longer an issue.

lgtm?  as lgtm as that regex can ever get?

Renamed the stream from "nginx.access" to just "access" and squashed the commit. Merging.


Unsaved Files Cause "Bad Request" AJAX Errors

Atom 1.0.11
atom-ternjs 0.7.2
If you open a new file but don't save it, atom-ternjs will spam the console with 400 (Bad Request) AJAX errors every time you type:

The response from the server is:
.files[n].name must be a string

I think it would be preferable to catch these errors and ignore them or not run the plugin against unsaved files.

Haven't managed to reproduce this yet.
Fell free to post a pull request that handles the case.
Else, you may give me more detailed directions to reproduce the error.
Greetings,
tststs

I'm using 0.8.3 now and I can't reproduce it anymore so I'll close this.


Background Connectivity works first only after first call

After starting //afone and opening another app, the background connectivity doesn't work.
Background Connectivity works only after first outbound, inbound or declined call.
iOS 13.4.1

This seems to be a duplicate to https://github.com/automat-berlin/afone/issues/4 - if not please explain the issue in more detail.


Deploy cargo-valgrind automatically

To speed up CI jobs that use cargo-valgrind and avoid running the cargo install cargo-valgrind command, I think it would be helpful to automatically deploy cargo-valgrind on Linux, MacOS and Windows through GithHub Actions. The action is triggered when a new tag is added and pushed.
I hope this is appreciated, thanks in advance for your review!

Hey, thank you for your work and interest into this project!

Hey, thanks to you for this project!

I had a look at the proposed workflow and think it should be fine. I think there isn't a way to dry-run this setup, is it? If there is not way, I'd simply go ahead and merge this and we see at the next release wink

Oh, right, my bad. I forgot to write down the link that shows that everything works correctly https://github.com/Luni-4/cargo-valgrind/actions/runs/2350504879

Unfortunately your pull request has a red/failing CI, causing by a problem with the CI setup unrelated to your changes. I've fixed that on the master-branch. Could you please rebase onto the current master and update your PR?

Thanks to you! Done!

Thank you for your PR! I'll release a new version soon.


Can't disable management action banners when using with Jamf

Hey I’m testing installomator in our jamf environment and I can't disable the management actions banner, I’ve tried setting notify to silent but it still seems to pop up when the policy runs? I've tested this using v9 and v8

Could you do me a favor and just add the parameter values screenshot and the log output we were looking at on Slack to this thread.

Sure thing Adam
Script result: 2022-02-02 15:48:29  shifting arguments for Jamf 2022-02-02 15:48:29 vlc setting variable from argument NOTIFY=silent 2022-02-02 15:48:29 vlc ################## Start Installomator v. 8.0 2022-02-02 15:48:29 vlc ################## vlc 2022-02-02 15:48:30 vlc BLOCKING_PROCESS_ACTION=tell_user 2022-02-02 15:48:30 vlc NOTIFY=silent 2022-02-02 15:48:30 vlc LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns 2022-02-02 15:48:30 vlc no blocking processes defined, using VLC as default 2022-02-02 15:48:30 vlc Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.IhITSrHp 2022-02-02 15:48:30 vlc App(s) found: /Applications/VLC.app 2022-02-02 15:48:30 vlc found app at /Applications/VLC.app, version 3.0.16 2022-02-02 15:48:30 vlc appversion: 3.0.16 2022-02-02 15:48:30 vlc Latest version of VLC is 3.0.16 2022-02-02 15:48:30 vlc There is no newer version available. 2022-02-02 15:48:30 vlc Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.IhITSrHp 2022-02-02 15:48:30 vlc App not closed, so no reopen. 2022-02-02 15:48:30 vlc ################## End Installomator, exit code 0 <img width="327" alt="Screenshot 2022-02-02 at 16 02 40" src="https://user-images.githubusercontent.com/79598034/152190705-682ca89d-763a-482c-8a07-3eafb63008ce.png">

Hi Adam, looks like it was an issue with our jamf policy, I removed and rebuilt this morning and now we are getting expected behaviour. Thanks fo your time on this.


bpf: Remove unused variables

test-me-please

Coverage increased (+0.08%) to 45.64% when pulling 62a0e00ec277180d39a939b540bc290ae545221d on pr/pchaigno/bpf-remove-unused-variables into 28b0fba546b4ea8255c29fd96c8ab5d1f4aaea18 on master.


Unable to send to google to log in

The problem
When I click to “authorize your account”, it just said:
Access blocked: Nest’s request is invalid
You can’t sign in because Nest sent an invalid request. You can try again later, or contact the developer about this issue. Learn more about this error
If you are a developer of Nest, see error details.
Error 400: invalid_request
What version of this integration (ha-nest-protect) has the issue?
0.3.12
What version of Home Assistant Core has the issue?
2024.7.4
Device / Model
N/A
Diagnostics information
No response
Home Assistant log
Logs
Copy/paste any log here, between the starting and ending backticks (`)

Additional information
No response

Just trying this now and same issue for me, first time install

I get the same "Access blocked: Nest’s request is invalid" error when clicking authorize your account.

Error details:

Error 400: invalid_request
The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow migration >guide linked in the developer docs below to migrate your app to an alternative method.
Request details: redirect_uri=urn:ietf:wg:oauth:2.0:oob flowName=GeneralOAuthFlow

Developer docs that it links to.

Just looping back, this is a known issue it's actually in the release notes but not in the readme so didn't see it before. To get it working you need to switch to the beta release channel and follow the instructions.
https://github.com/iMicknl/ha-nest-protect/releases/tag/v0.3.12

See #105 (pinned issue). TLDR: use the beta :)


Export of data is failing with error below I have been able to in past, but not now.

{
"message": "Unexpected token < in JSON at position 0 in "https://api.fitbit.com/1/user/-/activities/activityCalories/date/today/max.json\": \n\n<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US">...",
"host": "api.fitbit.com",
"hostname": "api.fitbit.com",
"method": "GET",
"path": "/1/user/-/activities/activityCalories/date/today/max.json",
"statusCode": 520,
"requestUrl": "https://api.fitbit.com/1/user/-/activities/activityCalories/date/today/max.json"
}
ParseError: Unexpected token < in JSON at position 0 in "https://api.fitbit.com/1/user/-/activities/activityCalories/date/today/max.json":

<!--[if lt IE 7]> ...
    at stream.catch.then.e (\\<IP_ADDRESS>\volume-3-default\71e539140aab05178a3f\76b230477a3846258950e7edbb2d6695\site\wwwroot\node_modules\got\index.js:109:14)
    at wrappedPromise.linkTransaction (\\<IP_ADDRESS>\volume-3-default\71e539140aab05178a3f\76b230477a3846258950e7edbb2d6695\site\wwwroot\node_modules\newrelic\lib\instrumentation\core\globals.js:168:23)
    at wrappedPromise.wrapped [as __NR_wrapper] (\\<IP_ADDRESS>\volume-3-default\71e539140aab05178a3f\76b230477a3846258950e7edbb2d6695\site\wwwroot\node_modules\newrelic\lib\transaction\tracer\index.js:155:28)
    at wrappedHandler (\\<IP_ADDRESS>\volume-3-default\71e539140aab05178a3f\76b230477a3846258950e7edbb2d6695\site\wwwroot\node_modules\newrelic\lib\instrumentation\core\globals.js:202:26)
    at process._tickCallback (internal/process/next_tick.js:103:7)

Hi! Thanks for filing this issue. You can use Markdown on Github to format code in a more readable way. In particular, you can use three backticks (```) to format a code block.
Can you provide any more detail about what you were doing when this happened? How long have you had your account for? Do you have a lot of data?

                                                                                Thanks for the response. This is a coding method I have no background so can't coment on formatting or looking at the code. I do have a lot of data in there. About three years I think. Just running your script from web link you provided. Thanks Bruce.                                                                                Sent from my BlackBerry 10 smartphone on the Rogers network.                                                                                From: Nick HeinerSent: Sunday, September 4, 2016 11:48 AMTo: NickHeiner/fitbit-exportReply To: NickHeiner/fitbit-exportCc: BruceSparks; AuthorSubject: Re: [NickHeiner/fitbit-export] Export of data is failing with error below I have been able to in past, but not now. (#11)Hi! Thanks for filing this issue. You can use Markdown on Github to format code in a more readable way. In particular, you can use three backticks (```) to format a code block.

Can you provide any more detail about what you were doing when this happened? How long have you had your account for? Do you have a lot of data?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/NickHeiner/fitbit-export","title":"NickHeiner/fitbit-export","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/NickHeiner/fitbit-export"}},"updates":{"snippets":[{"icon":"PERSON","message":"@NickHeiner in #11: Hi! Thanks for filing this issue. You can use Markdown on Github to format code in a more readable way. In particular, you can use three backticks (```) to format a code block.\r\n\r\nCan you provide any more detail about what you were doing when this happened? How long have you had your account for? Do you have a lot of data? "}],"action":{"name":"View Issue","url":"https://github.com/NickHeiner/fitbit-export/issues/11#issuecomment-244610842"}}}

I've followed up with Fitbit to learn about what this error means: https://github.com/NickHeiner/fitbit-export/issues/11.

                                                                                Thank you.                                                                                Sent from my BlackBerry 10 smartphone on the Rogers network.                                                                                From: Nick HeinerSent: Sunday, September 4, 2016 12:32 PMTo: NickHeiner/fitbit-exportReply To: NickHeiner/fitbit-exportCc: BruceSparks; AuthorSubject: Re: [NickHeiner/fitbit-export] Export of data is failing with error below I have been able to in past, but not now. (#11)I've followed up with Fitbit to learn about what this error means: #11.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/NickHeiner/fitbit-export","title":"NickHeiner/fitbit-export","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/NickHeiner/fitbit-export"}},"updates":{"snippets":[{"icon":"PERSON","message":"@NickHeiner in #11: I've followed up with Fitbit to learn about what this error means: https://github.com/NickHeiner/fitbit-export/issues/11."}],"action":{"name":"View Issue","url":"https://github.com/NickHeiner/fitbit-export/issues/11#issuecomment-244613228"}}}

Hey Bruce – try this again. I've removed the troublesome endpoint in 9d2398b72abc11d96d54b867b7f46a6a288395b7.


Implemented push-up Filtering

Looks good. Did you manage to test this in any way as well?

Everything passes on a build/sbt test command. I manually tested it with the following commands and verified the filter was pushed to the top.
val data = Seq(("number2", 4), ("number3", 1), ("number1", 5), ("number4", 123), ("number5", -1))
val df = spark.createDataFrame(data).toDF("a", "b")
val dfOblivious = df.oblivious
dfOblivious.sort($"b").filter($"b" > lit(3)).sort($"a").explain(true)

Ok, looks good!


[Refactor] Replace relay.vm.Tensor with NDArray

After this PR: https://github.com/apache/incubator-tvm/commit/55bd786fe25f710f6f46769fb7175f44dd73b2ea, we should be able to use NDarray directly in VM.

#4643


hello everyone i want to knof if is posible to limit the numbers of attemps of touch id

thank u all

You can perhaps keep track of a local int which increments every time an attempt fails.
Also, use StackOverflow to ask such questions as this isn't an issue.

Hi @HugoPowerMex, @pavittarsingh315 is right his approach should work.
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community#community-grid for resources and ask questions like this. You may also get some help if you post it on Stack Overflow with a minimal code sample that clearly describes your problem.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and we will reopen it.
Thank you


⚠ Bofrost.be has degraded performance

In 24a1aff, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1568 ms

Resolved: Bofrost.be performance has improved in 07104bc after 26 minutes.


Consider reversing roles of primary and secondary variables in IntegralCurve operator

Suppose you do a Pseudocolor plot of something using IntegralCurve operator. The way you do this is go to Plots->Pseudocolor->Operators->IntegralCurve->some vector var.
The some vector var variable that is chosen does not actually impact any of the coloring of the Pseudocolor plot. It impacts the plot's geometry. It defines the pathline(s)/streamline(s) that will be computed by the operator.
The coloring in the Pseudocolor plot is effected by the IntegralCurve operator's Data value setting in the Appearance tab. Its default is Absolute time. Now, that isn't the plot's time in the time-series. It is the IntegralCurve operator's internal notion of time as is used to advect/compute the streamlines.
The way to get this kind of Pseudcolor plot to color the plot by a database variable is to choose Variable as the Data value of the IntegralCurve operator and then to select a database variable. But, this variable, once selected is not the plot's primary variable. So, I can't for example, go to the Variable menu pulldown and select a different primary to plot like I can with any other plot. If I do, the plot will fail. Because when I do, that changes the some vector variable the IntegralCurve operator is using to compute streamlines.
Compare this with something like threshold operator. That operator computes a new geometry too. Its default behavior is to threshold the primary variable that is determining the Pseudocolor plot's color. But, you can select other variables to threshold with and they become secondary variables. The primary which still control's the plot's coloring can be changed. from the Variable pulldown.
When I want to export a database with threshold applied, additional variables exported in that case are run through the pipeline as the primary variable as if those variables had simply been plotted by the user "nornally". But, I don't think we can do that with IntegralCurve operator because it is the "Data value" variable that needs to be updated to have the comparable effect.
So, it feels like the role of the primary variable and the Data value variable in IC operator should be reversed so that what you pull-down to plot in the Pseudocolor menu is Operators->IntegralCurve->some scalar var and then IntegralCurve either looks for a corresponding vector variable defined on the same mesh as some scalar var and/or requires user to specify what that vector variable is to drive the computation of the streamline/pathlines.
@ARSanderson probably has some thoughts about this.

@markcmiller86 I agree this is confusing.
The problem is that the IC operator is creating a new variable, you are plotting the result of the IC operator whatever it is. It can be integration time like you said, which has no relation to any of the scalar vars that you could select from the mesh.  Basically, the IC operator result is like an implicitly named expression result with a funny name ("operators/IC/vector_field").
Unlike DeferExpression you can't ask VisIt to execute the IC operator even if it's not the primary variable plotted by the PC plot.
I do think it would be good for the IC operator to be able to select the vector field in its UI. That is the other purpose of the funny implicit name.
This is a problem for all of these type of operators, the IC curve is just the most prominent case.

The problem is that the IC operator is creating a new variable

I am not sure I follow. I mean, there certainly is not any new variable in the menus. And, if the Data Value that is plotted is indeed a database variable, then all the IC operator is doing is generating new geometry upon which to paint the selected, pre-existing database variable. And, in that case, I don't see any difference between it and something like threshold or iso-surface...geometry construction is driven by one variable and color by another.
Now, it turns out many of the options IC operator offers in the Data Value pull down are indeed new variables in that they have something to do with IC operator internals or something and are not seen anywhere else and so do indeed represent a non-variable. I hesitate to say new variable because its existence is unknown anywhere external to the IC operator itself. It cannot even be exported I don't think for example. I even wonder if many of the options provided here are in fact debugging options to help debug the IC operator itself and are rarely, if ever, used in actual practice.
So, here is what I think might be better behavior. When user does a PC plot with IC operator, the variable the user selects in main menu pull-downs determines the color of the plot. It is the primary variable.

If the selected variable is a scalar variable, then what should happen is the color gets driven by that variable and the streamlines get driven by the divergence of that variable.
If the selected variable is a vector variable, then what should happen is the color gets driven by vector magnitude and the IC operator's streamlines get driven by the vector field itself.
If the variable is a tensor variable, follow option 1 above using the tensor primary axis.
Alternatively, we decide not to permit non-scalars anywhere in PC plot pull down menus and so only the behavior of the first bullet is allowed. To change vector field driving streamlines, user must bring up the IC operator attributes and select it.
The above represent default behaviors. The user can of course bring up the IC operator attributes and adjust the field used to drive computations of the streamlines. The user can change the variable driving the coloring following same processes used everywhere else.
In particular, to export a number of variables onto the IC operator's geometry, they would simply get added to the list of variables in the export db. Presently, there is no way to export multiple variables with an IC plot because of its current design.
to support the internal variable options currently provided for in the IC operators Data Value pull down (if these indeed are not solely for debugging), these become operator-defined expressions like any other similar expression.

For example, Absolute Time is indeed an expression variable whose definition is perhaps such that it is only an option for the IntegralCurve pull down.

The above behaviors identically and in particular the sense of primary and secondary variables are IMHO much more consistent with rest of VisIt and similar operations.

Again, I think this is confusing. The "new" variable is the funny name you have to pick, that includes the vector field. This funny name is problematic in other cases as well (DataBinning), b/c you can't nest operators given the funny name. But the primary field of these type of operators is the funny named thing (they also make new meshes, etc) -- but that is why they are different than other operators. The funny name is the new field after the operator.  It can be exported, however there might be brittleness there.  If you selected abs time, it will be the "funny" named field in an exported VTK file.
Many of these special fields are important properties of the streamlines, not just for debugging. They convey new info that helps you understand the streamlines.  Interpolating the original field is only one useful way to color them.  I don't know of UI way to really have folks select these streamline specific cases, bending it to do so will breaks our UI construct.
When a user is looking for streamlines, the main input they are trying to explore is a vector field.
I don't think having the streamlines be calced on the divergence of the input scalar is an expected use case -- why not the gradient? I also don't see a special case for input tensors as intuitive.
Users don't think about streamlines of a scalar field, or streamlines of a tensor. What do those constructs really mean?  We can define them, but I don't think that helps make it easier.
For non-vector-at-the-start use cases, better to let the user create an expression for the vector field they want the streamlines of.
When we had the Streamline plot, it was much more initiative b/c you made a streamline plot of a vector var.
Another aspect:
Creating an expression fits best with our pipelines when we want to create new vars.
In the case of connected components, it is simple enough to be defined as an expression, (input mesh and a few options are passed)  -- using the Connected Components Operator isn't really a good option.
In the case of IC, there are many many many many options, we couldn't or wouldn't want to specify those in an expression. Atts via a UI window, or Python are much more tractable.

Again, I think this is confusing

Hmm. I think I may be confused becuase I don't honestly know what this in the above statement refers to. And, I worry you may have missed my main point.

I find it confusing to be doing a PC plot of a vector variable via the IC operator's sub-menu pulldown. Why don't vector variables appear in the PC plot's main pull-down? Because they are not scalars. But, there they are in the IC operator's sub-menu pulldown.
I also find it confusing that I cannot then use the Variable menu pulldown to change the coloring variable I have plotted in a resulting PC plot created through the IC operator's sub-menu pulldown. Try it. It will result in an error and red plot. Everything else works that way ok.
I find it confusing that I have no idea where to go to control coloring of an IC operator created PC plot and I find its default coloring to be wholly unrelated to the variable I actually pulled down to in the menus when creating the PC plot to begin with.
I find it even more confusing that I cannot list multiple variables in the export db involving such a plot and have VisIt export them on the IC operator created geometry.
I find it confusing that if the special fields internal to IC operator are useful, that none of them are available outside of it. I can't create expressions involving them. I can use them only to drive coloring of the IC operator.

IMHO, this is all because the IC operator is treating the pulled-down (e.g. ordinarily the primary variable in a PC plot and the variable that controls PC plot coloring) as something else. Its just backwards. And, all this will remain true regardless of the other aspects you mention and regardless of whether by default we can do something sane with atypically typed variables (scalars or tensors) which is really orthogonal to this whole discussion.
Don't wanna handle tensors or scalars as proposed? No problem...I included only because as currently designed we are handling vector variables in the PC plot pull down which is by itself IMHO confusing. How does a vector variable map to a color? In the past (and perhaps even now in the code), we've arguded that doing a PC plot of a vector should maybe implicitly mean to color by vector magnitude. So, the default behavior I proposed for tensors and scalars was merely to remain consistent with that. If not desirable, ignore those aspects of what I was describing. They are not really relevant to the core issue. Side Note: IMHO, having something behave sanely by default is a good practice, even if it isn't necessarily a common case. I view treating non-standard variable types (e.g. scalar or tensor) in a sane way if they ever happen to be attempted as a way of improving user experience. Also, sorry, I did mean default to using vector field of gradient and not divergence for scalar inputs.

this == "IC" operator and these style of operators.  The same applies for all of them, an actually it can be more confusing for some: Input variables have no meaning for some operators (CCL, some cases of IC, data binning).

Hi,
A few thoughts that are a tangent but addresses some of the issue. Why do we have separate plots for scalar, vector, and tensor data.  Should there not be one plot for all? Now one may say yes as the data is different. However, I would argue is a vector glyph any different from a point glyph?? Further, within the scalar data we have points, lines, surfaces. Currently with the PS plot if one is rendering a surface the points and lines geometry UI is inactive.  What if I have point data and I want to put a vector on them? I cannot do that within the PS plot. I should, should I not??
Further, there is a lot of duplicity between the three plots. Namely the data limits, scaling, and color table. Combine all that and what is left. A couple of tabs specifically for vector and tensor glyphs, add those tabs to the current PS plot and viola Mark some of your concern is solved.
That said, Mark I understand some of your other concerns. As Cyrus noted when using the integral curve the primary interest is the vector field. As such, it really is the primary variable. How it is colored is secondary. That color value maybe a variable from the data base or a value generated by the IC system. Those values are important. For instance, the Poincare operator generates many values related to the analysis.
I do agree that down stream there an issue. But I have no answer, other than to say the IC are a one off square peg/round hole.
Cheers,
Allen
Allen Sanderson
SCI Institute
University of Utah

Hi,
After helping a user this past week who was having problems with the IC operator I submitted this bug report:
https://github.com/visit-dav/visit/issues/4341
Nutshell, they created a vector plot to first see their vectors, then added the Integral Curve operator. That does not work with a vector plot as the output data is scalar. They were drawing a blank on the Pseudocolor->operator->PICS->IC->variable.
In the mean time over the past two days I basically collated the vector and tensor plots. Not into one but to make them have the same functionality.  Eric and Kathleen are reviewing my changes before merging them into the trunk. As I noted to Eric, with a small amount of work over the course of a day or two I could probably merge the vector and tensor plots into a single plot. There is no difference other than the glyph being used.
As such, I am going to raise my hand again to say I think it would be really good to look at having one plot for scalars, vectors, and tensors. There is so much overlap now.
I think going forward there are going to be more operators the change the data type and trying to do the plot->operator-> thing is going to be a bane. especially as it adds additional menu items.
Cheers,
Allen

On Dec 5, 2019, at 5:13 PM, Allen Sanderson<EMAIL_ADDRESS>wrote:
Hi,
A few thoughts that are a tangent but addresses some of the issue. Why do we have separate plots for scalar, vector, and tensor data.  Should there not be one plot for all? Now one may say yes as the data is different. However, I would argue is a vector glyph any different from a point glyph?? Further, within the scalar data we have points, lines, surfaces. Currently with the PS plot if one is rendering a surface the points and lines geometry UI is inactive.  What if I have point data and I want to put a vector on them? I cannot do that within the PS plot. I should, should I not??
Further, there is a lot of duplicity between the three plots. Namely the data limits, scaling, and color table. Combine all that and what is left. A couple of tabs specifically for vector and tensor glyphs, add those tabs to the current PS plot and viola Mark some of your concern is solved.
That said, Mark I understand some of your other concerns. As Cyrus noted when using the integral curve the primary interest is the vector field. As such, it really is the primary variable. How it is colored is secondary. That color value maybe a variable from the data base or a value generated by the IC system. Those values are important. For instance, the Poincare operator generates many values related to the analysis.
I do agree that down stream there an issue. But I have no answer, other than to say the IC are a one off square peg/round hole.
Cheers,
Allen
Allen Sanderson
SCI Institute
University of Utah

If there is a lot in common among the three types of plots, that is definitely an argument for finding some way to implement them with shared code but not necessarily an argument that they should also be collapsed to a single uber plot type in the user interface.
Currently, the way plot plugins work, I am not sure there is a way for them to easily share common pieces. Maybe being able to have plots plugins inherit from each other? Maybe a layer just above plot plugins into which common sub-pieces can go (bg/fg color selections, color table selections, glyphing type selection, glyph sizing controls, glyph features, wireframe, geometry smoothing) would help to reduce code duplication?
At any rate, I think @ARSanderson is making a software engineering argument to suggest a change in the user interface and I just want to raise the observation that I think these are two separate issues. @ARSanderson which is more important to you...reducing code duplication (e.g. the software engineering) or changing the user interface, or both?

Mark,
Good observations. IMHO, both are important. From the code side the maintenance gets more involved. For instance, in the Pseudocolor plot Kathleen implemented the option to color values outside the min/max. A great option that I have already made use of. Conversely, the Vector/Tensor plots have the option of a single color. Also useful. I want it all in all the plots. Setting up the GUI for all of these requires code in three places. And while we can coalesce things like this into a common GUI that makes using it a bit easier it is still needed in three places.
As for the plots functionality. From the first day I started using VisIt one of the things that has always bugged me is number of plots. Hank convinced me the reasoning and in general I see the logic. There are exceptions, for instance the contour plot is really a Pseudocolor plot with an iso-contour operator built in and a semi-hard coded color table.  But the biggest exception is the Scalar/Vector/Tensor plots which in my mind all produce “glyphs" of one sort of another. And if treated that way I think it could greatly simply things without making the GUI more complex. I think it is a worthy in depth discussion.
Cheers,
Allen
Allen Sanderson
SCI Institute
University of Utah

On Feb 7, 2020, at 7:46 PM, Mark C. Miller<EMAIL_ADDRESS>wrote:
If there is a lot in common among the three types of plots, that is definitely an argument for finding some way to implement them with shared code but not necessarily an argument that they should also be collapsed to a single uber plot type in the user interface.
Currently, the way plot plugins work, I am not sure there is a way for them to easily share common pieces. Maybe being able to have plots plugins inherit from each other? Maybe a layer just above plot plugins into which common sub-pieces can go (bg/fg color selections, color table selections, glyphing type selection, glyph sizing controls, glyph features, wireframe, geometry smoothing) would help to reduce code duplication?
At any rate, I think @ARSanderson https://github.com/ARSanderson is making a software engineering argument to suggest a change in the user interface and I just want to raise the observation that I think these are two separate issues. @ARSanderson https://github.com/ARSanderson which is more important to you...reducing code duplication (e.g. the software engineering) or changing the user interface, or both?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/visit-dav/visit/issues/3995?email_source=notifications&email_token=AGHBOILUW7RVJZRU2L4GPADRBYMG7A5CNFSM4JFJDCF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFHTBY#issuecomment-583694727, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGHBOINQM6D6PSGHRZEQ2S3RBYMG7ANCNFSM4JFJDCFQ.


Tag a release

It would be great if there was a release tagged. I'll be creating a FreeBSD port for this soon...

Hi
Thanks for the reminder. Tagged release 1.0.0 now.


More Tests

https://github.com/mchirico/ts-express/issues/14

Codecov Report

Merging #24 into master will decrease coverage by 12.46%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #24       +/-   ##
===========================================
- Coverage   64.90%   52.43%   -12.47%
===========================================
  Files          19       15        -4
  Lines         151       82       -69
  Branches       15       12        -3
===========================================
- Hits           98       43       -55
+ Misses         51       38       -13
+ Partials        2        1        -1

Impacted Files
Coverage Δ

src/pubsub/pubsub.ts

src/githubapi.ts

src/firebase.ts

src/dlog.ts

...pp/navpages/notification/notification.component.ts
69.23% <0.00%> (+38.46%)
:arrow_up:

Continue to review full report at Codecov.

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


Angular2 - KarmaJS - unit Tests not executed automatically on npm test

Expected behaviour
Should  execute tests - there is 300 + test case in my pro.
Actual behaviour
Throwing an exception Can't execute tests - Executed 0 of 0 ERROR (0.005 secs / 0 secs)
Environment Details

Karma version (output of karma --version):
Relevant part of your karma.config.js file

const webpackConfig = require('./webpack.config.test');
module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine'],
    plugins: [
    require('karma-jasmine'),
    require('karma-chrome-launcher'),
    require('karma-phantomjs-launcher'),
    require('karma-jasmine-html-reporter'),
    require('karma-coverage-istanbul-reporter'),
    require('karma-webpack')
    ],
    client: {
      clearContext: false // leave Jasmine Spec Runner output visible in browser
    },
    files: [
    {pattern: './src/test.ts', watched: false}
    ],
    preprocessors: {
      './src/test.ts': ['webpack']
    },
    webpack: webpackConfig,
    webpackServer: {
      noInfo: true // prevent console spamming when running in Karma!
    },
    mime: {
      'text/x-typescript': ['ts', 'tsx']
    },

    // configure the reporter
    coverageIstanbulReporter: {
      reports: ['html', 'lcovonly', 'text-summary'],
      dir: 'coverage/',
      // if using webpack and pre-loaders, work around webpack breaking the source path
      fixWebpackSourcePaths: true,
      skipFilesWithNoCoverage: true,
      // enforce percentage thresholds
      thresholds: {
        statements: 80,
        lines: 80,
        branches: 70,
        functions: 80
      }
    },

    angularCli: {
      environment: 'dev',
      codeCoverage: true
    },
    reporters: ['progress', 'coverage-istanbul'],

    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['PhantomJS'],
    singleRun: true,
    concurrency: Infinity
  });
}

Here my "test.ts" file that I refer in "karma.conf.js"
// This file is required by karma.conf.js and loads recursively all the .spec and framework files
import 'core-js/es6';
import 'core-js/es7/reflect';
import 'zone.js/dist/zone';

import 'zone.js/dist/long-stack-trace-zone';
import 'zone.js/dist/proxy.js';
import 'zone.js/dist/sync-test';
import 'zone.js/dist/jasmine-patch';
import 'zone.js/dist/async-test';
import 'zone.js/dist/fake-async-test';
import { getTestBed } from '@angular/core/testing';
import {
    BrowserDynamicTestingModule,
    platformBrowserDynamicTesting
} from '@angular/platform-browser-dynamic/testing';

import './polyfills';
// Built by the core Angular team for mocking dependencies
import 'angular-mocks';

// Unfortunately there's no typing for the `__karma__` variable. Just declare it as any.
declare var __karma__: any;
declare var require: any;

// Prevent Karma from running prematurely.
__karma__.loaded = function () {
};

// First, initialize the Angular testing environment.
getTestBed().initTestEnvironment(
    BrowserDynamicTestingModule,
    platformBrowserDynamicTesting()
);
// Then we find all the tests.
const context = require.context('./', true, /\.spec\.ts$/);
// And load the modules.
context.keys().map(context);
// Finally, start Karma to run the tests.
__karma__.start();

And this is tsconfig.json
{
  "compilerOptions": {
    "sourceMap": true,
    "baseUrl": "",
    "declaration": false,
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "allowJs": false,
    "target": "es5",
    "lib": [
    "es2016",
    "dom"
    ],
    "outDir": "../out-tsc/app",
    "module": "commonjs",
    "types": []
  },
  "exclude": [
  "test.ts",
  "**/*.spec.ts",
  "**/tmpl*.*",
  "*.tmpl.ts",
  "**/*.temp.ts",
  "app/templates/*/package/**"
  ]
}

Steps to reproduce the behaviour

You are excluding your test.ts and all yours spec files on your tsconfig, maybe you need to use a tsconfig for running your tests, extending that tsconfig and including your test.ts and all specs.
Something like that:
{
  "extends": "path/to/tsconfig.json",
  "compilerOptions": {
    "outDir": "out-tsc/spec",
    "baseUrl": "..",
    "module": "commonjs",
    "target": "es5",
    "types": [
      "jasmine",
      "node"
    ]
  },
  "files": [
    "test.ts"
  ],
  "include": [
    "**/*.spec.ts"
  ]
}

Hi, I have tried this but its not working.

Facing similar issue here: https://github.com/blacksonic/angular-testing-ground
Cant change to Chrome launcher, executes zero tests without an error message.

It looks like a misconfiguration or a problem with one of the many plugins used, hence there is not much we can do about it in the Karma core.
Please use StackOverflow for questions and support in the future as we want to keep the issue tracker for bug reports and feature requests.


CB-9622 WP8 Camera Option destinationType:NATIVE_URI is a NO-OP

•	Windows Phone 8 proxy now supports NATIVE_URI param
•	Treat NATIVE_URI same way as FILE_URI (similar to Android)

LGTM


Add quality checks

We need to have gating quality checks in CI with clang-format and clang-tidy files.

Closed by #17


Referer not properly set as option from page.goto

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.9.0
Platform / OS version: MacOS High Sierra
URLs (if applicable):
Node.js version:v8.11.4

What steps will reproduce the problem?
Please include code that reproduces the issue.
  browser = await puppeteer.launch();
  // Open a new page
  page = await browser.newPage();

  // Setup handlers for the requests and responses
  page.on('request', function logRequest(request) {
    requestHandler(request.url());
  });

  page.on('response', function logRequest(response) {
    responseHandler(response);
  });

  // Navigate to our test page
  await page.goto('http://localhost:5000/', {
    waitUntil: 'networkidle0',
    referer: 'https://www.google.com/'
  });

What is the expected result?
I would expect that the referrer is ''https://www.google.com"
What happens instead?
The referrer is empty string, as is assumed from direct entry.
Additional Notes
The header is correctly set if using
page.setExtraHTTPHeaders({ referer: 'https://www.google.com/' });
It seems as though the option is being passed along to be stringified and sent as a message to the frame instance but for whatever reason it is not setting it properly as an option there.  Also tried the spelling "referrer" as well.

I am running your code snippet with the following configuration:

Puppeteer version: 1.9.0
Platform / OS version: MacOS High Sierra
Node.js version:v10.0.0

and I can't reproduce it. Could you share the Chromium version that your puppeteer installation uses? You find it, for example, in the user agent that is sent along. My version is HeadlessChrome/71.0.3563.0 and that sends the referer as expected:

Thank you for the update. Are you sure that the code snippet in this issue isn't sending the referer? Can you send a request to https://watwat.free.beeceptor.com (or a similar sink)? When I check the referer header, it's present (as seen in the screenshot in https://github.com/GoogleChrome/puppeteer/issues/3374#issuecomment-429468347)


missing lottie-web dependency

#3800 introduced a dependency on lottie-web, so it needs to be added to package.json.
cc @paul-balchin-ibm

Hi, a new release was just built to deal with this specific issue.
Please try installing version @carbon/ibm-products version 2.19.2.

Hi @paul-balchin-ibm, I still don't see it listed in package.json (https://github.com/carbon-design-system/ibm-products/commits/main/package.json), am I missing something?

@wkeese it was added to ./packages/ibm-products/package.json
https://github.com/carbon-design-system/ibm-products/commits/main/packages/ibm-products/package.json

Ah I see, OK thanks!


Show accesory as no response/offline when “no device found” error raises

It would be nice that when the no device found errror raises the accesory that was meant to be controlled showed as offline or no response. To prevent inconsistent states: in turning on/off the ac or moving the curtains from another room and I’m thinking that everything is alright until I go to the other room and see that the accessories weren’t controlled at all....

+1

I think this is an issue with the plugin... just now it started to happen with one broadlink, couldn’t get it to work, I even unplugged it and plugged back to power and it didn’t work. It did work from the broadlink app, but not from the home app. I had to restart homebridge and then it started working.

Hey @iandronowicz are you still seeing this? I'd love to help figure out the issue.

Please re-open if you'd still like a hand.


fix: rm devtools from test

I love devtools, and use it all the time, but Ive ran into issues with my tests locally. This is to set the devtools to only be shown when process.env.NODE_ENV !== 'development'. This will cover the original case, and the case where devtools show up in tests which has been causing me issues.

@bluebill1049 Have you had a chance to take a look? Im think this will be better since itll only show dev tools exactly when needed, during development.

Thanks for the PR.


csv copy command for data migration from hdfs

our datacenter builded on the hadoop system and i wanna mak to try with cratedb.
and there has the work how to import csv from hive /hdfs.
should be support copy csv command simplify the work! thanks!
someon mention the issue on the stackoverflow ref:
https://stackoverflow.com/questions/24378071/importing-data-from-csv-files-into-cratedb
there has 1000+ tables in the hive to do it with hive "concat" funcion or other method.
and it is very tedious for me .
shuould support :
copy zip_codes(ZIP,CITY,STATE) FROM '/path/to/csv/.txt' DELIMITER ',' CSV
or like this
copy quotes from '/tmp/import_data/' with (bulk_size = 4) DELIMITER ',' format=CSV;

hi @cmdares, there's already an pr out. https://github.com/crate/crate/pull/6830
we are improving this at the moment and it might end up in one of the next CrateDB releases.

https://github.com/crate/crate/pull/6830 has been merged and is part of 3.0


OpenEXR loader reading from system::IFile*

TODO: perform a test for https://github.com/Devsh-Graphics-Programming/Nabla/commit/ee7d5402cd6c36189df161417a82790652d9a19d ASAP

assign @AnastaZIuk


Split Record into 2 sections

Hey Guys,
I broke up the Recording section into "Recording New Composition" and "Collaborate on Existing Composition". I also changed marked a couple things to "optional" based on what we talked about last night.
And I removed some of the details to focus just on user actions. We definitely need those details, but I was wondering if it was too much for just the user stories. Feel free to let me know if I removed something we definitely want to convey.

lgtm. :star:
i agree that the removed section can be conveyed via wireframes, which i am updating currently.


Updating the text of UI Page 2

@QQ-Sortiz (CC: @FIN-JBarile and @Dengaloo)
OSMOSE users have decided to rename "background functional groups" into "biotic resources".
We therefore need to update the UI and the files it provides accordingly.
First, the text of UI Page 2 needs to be updated, as follows:

FishBase/SealifeBase defined functional groups for you
Please feel free to:
(1) Indicate whether each functional group is a focal functional group or a biotic resource, using dedicated radio buttons.
(2) Remove species from some functional groups.
(3) Redistribute species between functional groups.
(4) Remove functional groups from the table.
(5) Create functional groups.
(6) Rename functional groups.
*Caution: The name of the functional groups should not include spaces nor underscores. For example, "SmallPelagics" is a valid functional group name, but not "Small pelagics" nor "Small_pelagics".
When you are ready, press Proceed to go to the next step.

Many thanks!

Changes were implemented. Kindly check.

@QQ-Sortiz
There is a typo.
Please replace "biotic resources" with: "biotic resource". In other words, remove the "s".
Thanks a lot.

You first said that it should be "resources" then on your example, it is just "resource". Anyway, it is now corrected. Thanks

@QQ-Sortiz Many thanks; I can now close the present issue.


Add flag to set /metrics endpoint request timeout

When pulling a lot of data from the Github API, I found the default 10s timeout on the /metrics endpoint was insufficient. This option allows it to be configured via GITHUB_EXPORTER_SERVER_TIMEOUT

Could you also add a changelog record to https://github.com/promhippie/github_exporter/tree/master/changelog/unreleased, please?

Ready for merge now

After finishing https://cloud.drone.io/promhippie/github_exporter/44 you could give the latest Docker tag a try, if everything behaves fine I will release v1.0.0.


Correctly handle last mpd

What does this PR do?
Handle the last MPD.
Why was this PR needed?
Currently, the last mpd is download (with header X-FB-Video-Broadcast-Ended=1), then the downloader is marked as aborted without updating the etag from this last mpd.
Thus, the etag is unchanged and causes downloader to skip the processing of this mpd, even if this mpd contains some segments.
Does this PR meet the acceptance criteria?

[ ] Passes flake8 (refer to .travis.yml)
[ ] Docs are buildable
[ ] Branch has no merge conflicts with master
[ ] Is covered by a test

Coverage decreased (-0.4%) to 90.543% when pulling dbca4dd55608cee6c8912efe4e4e148f98d861cb on pjw91:handle-last-mpd into 118fc6c004942fe4d270a2097cce065bd29540c7 on ping:master.


[FEATURE] Add getImages snippet

Description

Adding a snippet to fetch all images from within a desired element.

PR Type

[x] Snippets, Tests & Tags (new snippets, updated snippets, re-tagging of snippets, added/updated tests)
[ ] Scripts & Website & Meta (anything related to files in the scripts folder, how the repository's automated procedures work and the website)
[ ] Glossary & Secondary Features (anything related to the glossary, such as new or updated terms or other secondary features)
[ ] General, Typos, Misc. & Meta (everything else, typos, general stuff and meta files in the repository - e.g. the issue template)

Guidelines

[x] I have read the guidelines in the CONTRIBUTING document.

Shortened the description again and squashed the last two commits into one for clarity.

I think this is ready for merge now? @atomiks


Misleading of defaultAlamofireManager in MoyaProvider+Defaults

In MoyaProvider+Defaults.swift, has a defaultAlamofireManager method to get the default Alamofire's Manager. Alamofire's Manager has a static instance of default. But in defaultAlamofireManager's implementation, it just use defaultHTTPHeaders from Alamofire, would create a new Manager instance every call.
     // Moya
    public final class func defaultAlamofireManager() -> Manager {
        let configuration = URLSessionConfiguration.default
        configuration.httpAdditionalHeaders = Manager.defaultHTTPHeaders

        let manager = Manager(configuration: configuration)
        manager.startRequestsImmediately = false
        return manager
    }

    // Alamofire
    open static let `default`: SessionManager = {
        let configuration = URLSessionConfiguration.default
        configuration.httpAdditionalHeaders = SessionManager.defaultHTTPHeaders

        return SessionManager(configuration: configuration)
    }()

I gave this some thought and I think it makes sense to change this to a static property. Do any other @Moya/contributors have some input on this subject? I only joined the project recently so I may be missing context.

I definitely think this should be static, but ...
We need to consider there might be some people who actually count on this side-effect by now (which is wrong, but is the current behavior). So if we make this change, it would be a breaking change for some people.
The worst part is some people won't necessarily notice it would break their codebase since its a silent fix.
Not sure how common this scenario is, but its definitely worth considering.

@freak4pc brings up a great point. Those silent breakages are the most dangerous in my opinion. If we decide to make this change I recommend artificially making a breaking change in the source with a @deprecated message that shows up as a warning so people see that at upgrade time.
I’ve also asked a friend who’s a consumer of Moya, currently back on v8 for his opinion on this. I’ll post here when we’re done talking

Hmm. Let's step back for a minute before discussing changing Moya's behaviour.
The reported issue is that the method name is misleading, so let's discuss that first.
The method is scoped to a file that begins with Moya+, so it's semantically scoped to the Moya project. Additionally, the rest of the file is all functions for defaults of Moya, so again it fits well. For historical context, the defaultAlamofireManager function itself predates Alamofire's concept of a "default" (previously called "shared") manager. We used a function here specifically because it does create a new Alamofire manager instance with each invocation (if it were accessing a shared instance, I'd agree that using a static var would be better).
So we have a function with a slightly misleading name, but otherwise the function fits well within Swift idioms. I think we should consider two possibilities:

Adding documentation explaining that this function doesn't return the default Alamofire manager instance.
Renaming the function to avoid ambiguity with Alamofire's default manager.

I'm very concerned about code churn in stable projects like Moya; imo, any breaking change needs to be justified by tangible benefits to Moya users because so many developers depend on this library and I don't want them to feel frustrated. Which of the two options we pick (if either, or both) should depend on feedback from the community. @zhongwuzw and @SD10's friend's input would be valuable here.

@freak4pc Thanks for mentioning the repercussions for those relying on this behavior. I had similar concerns, less so because the method is marked public, but more so now that I realize someone could wrap this call in another function making modifications or modify the property of the provider directly. 👍
I want to say that this should be made a static var but after @ashfurrow's comments I'm thinking otherwise:

Does it really make sense to have a 1 to many relationship between Manager and Provider?
I think the current 1:1 relationship may make more sense, to be honest.

Normally, Manager would be considered a candidate to be made static to eliminate the overhead of initialization. It seems like this is not a huge concern, as no Moya consumer has mentioned it before.

I mean, Ash has made a good case as to why the method is a function and it is prefixed default. It really makes sense if you read between the lines.
I would opt for adding a comment unless we have overwhelming support to change this.

If this would be written from scratch today I would probably opt for a singleton style var, but since this is already a relatively mature codebase and the added value to this change would be minimal, I don’t think it’s necessary.
We could have a purely additive change where we add a ‘default’ computed static var, and whoever wants can use either, possibly.

@ashfurrow your thoughts are always awesome. Thank you for taking the time to step in on this ❤

Cool! Looking forward to hearing. Of course, everyone is welcome to chime in, too.

More context on this issue. Looks like this setup is due to this comment


with --cfg esp_idf_soc_sdmmc_use_gpio_matrix,  sd/mmc.rs has errors.

o   Compiling esp-idf-svc v0.49.1
error[E0560]: struct esp_idf_hal::sys::sdmmc_slot_config_t has no field named clk
--> /home/qian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-idf-svc-0.49.1/src/sd/mmc.rs:170:17
|
170 |                 clk: _clk.into_ref().deref().pin(),
|                 ^^^ esp_idf_hal::sys::sdmmc_slot_config_t does not have this field
|
= note: all struct fields are already assigned
error[E0560]: struct esp_idf_hal::sys::sdmmc_slot_config_t has no field named cmd
--> /home/qian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-idf-svc-0.49.1/src/sd/mmc.rs:172:17
|
172 |                 cmd: _cmd.into_ref().deref().pin(),
|                 ^^^ esp_idf_hal::sys::sdmmc_slot_config_t does not have this field
|
= note: all struct fields are already assigned
error[E0560]: struct esp_idf_hal::sys::sdmmc_slot_config_t has no field named d0
--> /home/qian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-idf-svc-0.49.1/src/sd/mmc.rs:174:17
|
174 |                 d0: _d0.into_ref().deref().pin(),
|                 ^^ esp_idf_hal::sys::sdmmc_slot_config_t does not have this field
|
= note: all struct fields are already assigned

Without giving me info what chip and ESP IDF you've used, I can hardly do anything.
With that said, please patch esp-idf-sys, esp-idf-hal and esp-idf-svc to latest master (with patch.crates-io) if you plan to use the SDMMC code. And enable the experimental feature, as I think this functionality is still under the experimental flag.

Also. This:
--cfg esp_idf_soc_sdmmc_use_gpio_matrix
you should absolutely not do (i.e. custom manual esp_idf_* Rust cfgs. These are generated by esp-idf-sys itself, based on your sdkconfig.defaults settings.


java: use public modifiers

In other guides, we use public modifier for Java controller classes and their methods annotated with @GET...
Do we want to change the style to use package private scope ?

I'm fine either way but I prefer to omit public in controllers since it's not needed. Since they're only invoked by the generated code that's in the same package, omitting them in the controllers is a small reminder that controllers aren't injectable or directly invocable from user code.

I agree with Burt

Please do a vote here: https://github.com/micronaut-projects/micronaut-guides/discussions/403


Having issue finding code samples for Merchant API

I can't find the product resource code samples on here: https://developers.google.com/merchant/api/samples
Could you please help me?

Hello Content API for Shopping User,
Thank you for contacting us for support.
If you reached out to us through Github, we recommend re-submit your query directly to our developer support. This will allow us to better understand your needs and provide quicker solutions.
For any queries provided through Github only, there isn’t a set time we will be able to get back to you which we will do the best we can.
Thank you,
The Merchant API Team


Reduce wait coefficients for specs

After successful https://github.com/filewatcher/filewatcher/pull/170
There is only for "CI + JRuby + CLI".

Seems like there is no difference…
master: https://cirrus-ci.com/task/6379226812121088
This PR: https://cirrus-ci.com/task/5241224157200384
OK, let's merge and then try to update filewatcher, from where we're getting ×3 coefficient for JRuby.


Spanish translation

Books names in spanish.
Thank you for this great addon!
May God bless you!

Thanks for support :-)


pin esm build version to v132

Introduced buildversion in esm.sh deps url, to fix problem mentioned in issue https://github.com/nhttp/nhttp/issues/40
I'm not 100% sure about the special stable buildversion one should use for UI libraries.
This is mentioned here: https://github.com/esm-dev/esm.sh#pinning-build-version
I'm also not sure how to run build_scripts etc. but I think everything else has to happen after merge by a build server.

Codecov Report
Patch and project coverage have no change.

Comparison is base (899a1f0) 98.62% compared to head (d07272b) 98.62%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #41   +/-   ##
=======================================
  Coverage   98.62%   98.62%
=======================================
  Files          15       15
  Lines        1965     1965
  Branches      330      330
=======================================
  Hits         1938     1938
  Misses         26       26
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

looks good. thank's


Bug: Prompt for update doesn't reload page on first update

Steps to reproduce in v0.21.0:

git clone https://github.com/vite-pwa/vite-plugin-pwa.git
Run examples as in docs
Answer questions:

Select a framework: preact (bug is not related to preact)
Select a strategy: injectManifest
Select a behavior: Prompt for update
Enable periodic SW updates? yes
Unregister SW? no

Open https://localhost in Chrome in incognito mode
In prompt App ready to work offline: click Close
Wait for 1 minute as suggested in docs
Add console.log('foobar') to examples/preact-router/src/main.tsx`
Repeat step 2 and 3.
In prompt New content available, click on reload button to update. click Reload
Problem: Page does not reload

This happens only for first service worker update. For any subsequent updates, clicking on Reload reloads the page.
Reproduction should be run in incognito mode to simulate first update
Seems that the controlling event doesn't fire in this case:
https://github.com/vite-pwa/vite-plugin-pwa/blob/95142ebc588dea3d9376a2eb4affe086f19a7395/src/client/build/register.ts#L85-L88
When I add
// examples/preact-router/src/prompt-sw.ts
import { clientsClaim } from 'workbox-core'

//...

clientsClaim()

Then the controlling event fires, however with incorrect event.isUpdate = false and in effect reload still doesn't happen
BTW: I've noticed that in Workbox Docs > Use cases and recipes >  Handling service worker updates with immediacy there is no check for the event.isUpdate
Possibly related: #256

I think that the event.isUpdate value cannot be relied on, because it's set at workbox-window registration, and not updated later on:
// Set this flag to true if any service worker was controlling the page
// at registration time.
this._isUpdate = Boolean(navigator.serviceWorker.controller);

Source:  https://github.com/GoogleChrome/workbox/blob/c77dceb54d4af1749db95316710d6430e82b0c48/packages/workbox-window/src/Workbox.ts#L117-L119
For the controlling event it's description is:

True if a service worker was already controlling when this service worker was registered.

It doesn't mean that service worker has been updated from previous version
Reference: https://github.com/GoogleChrome/workbox/blob/c77dceb54d4af1749db95316710d6430e82b0c48/packages/workbox-window/src/Workbox.ts#L698-L699

Related issue in workbox repo: https://github.com/GoogleChrome/workbox/issues/3377


Field type changed from long to integer

When generating classes from the kccapi upstream crds.yaml the generated class StorgeBucketSpecCondition used to have a field age with the type Long. Now the same field has the type Integer.
Figure out why this is, and come up with a plan to reconcile this (either have crdtools behave as the old implementation, or update the call sites to use the new implementation)

https://github.com/goldmansachs/crdtools/pull/57 closes this


Update issue templates

The next step with this would be to go through the existing issues and close everything that is some vague feature request with a comment that if someone is interested in implementing this, they should open a new topic in the discussion section to design the corresponding API first.

The next step with this would be to go through the existing issues and close everything that is some vague feature request with a comment that if someone is interested in implementing this, they should open a new topic in the discussion section to design the corresponding API first.


FreeObject: hide harder from the compiler, tweak types

On CHERI, the compiler will always issue a warning for
reinterpret_cast<T*>(vaddr_t) and similar expressions, and of course, if the
compiler can see far enough into the types, the presence of if constexpr will
not save us.  Therefore, lift the conditional out to two definitions of
FreeObject::encode using std::enable_if_t to gate which is used.
While in the neighborhood, use address_t rather than uintptr_t; the former
is the latter on all non-CHERI platforms, but is vaddr_t rather than
uintcap_t on CHERI.

Perhaps you want to move to ptraddr_t from vaddr_t? The latter is a deprecated CheriBSDism.

Oh, you don't actually use vaddr_t anywhere in snmalloc, just the commit message here.

Oh, but good call.  The address_t = vaddr_t bit is still pending in my CHERIfication tree and it'd be best to fix that before I forget.

I think this is going to have some interesting interactions with #304.


Updates

Commit sponsored by Jeb
Signed-off-by: Marcus Brandenburger<EMAIL_ADDRESS>

@bvavala please consider for merging. We can do another pass/PR for more updates if needed.

@g2flyer sorry for messing up your feedback. Now, I added (hopefully) all the requested changes. This PR needs a squash and proper commit msg with signoff and co-authors.


💚 Add flake8 in CI

Let's add flake8 in CI !

Let's merge this PR after merging the #45 .

@tkoyama010, now that #45 has been merged, feel free to update your PR :)

Now. It is ready for merge. Thank @GuillaumeFavelier for help. :rocket:

Thanks @larsoner :smile:


[Leonid Khvatskin, 3530901/80203] Lab 1, Pt. 2: Pillow, the Request Format

Outdated, the Lab is already done completely


How can I deploy a shiny app created in R to azure as a web-service...

Is it possible to deploy a shiny dashboard created in R to deploy it as a web-service in azure...I was only able to find the deployment of R ML model to Azure ML studio...But my R script does not have any ML model...So is there a way that could be done?

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

ID: 72793e60-5fdd-3769-b1cb-92fa4372cb18
Version Independent ID: 568055fb-f42c-7c06-35a9-6f9596b5a7d3
Content: Deploy a Machine Learning Studio web service - Azure Machine Learning Studio
Content Source: articles/machine-learning/studio/publish-a-machine-learning-web-service.md
Service: machine-learning
GitHub Login: @xiaoharper
Microsoft Alias: amlstudiodocs

@UtsaVakani Thanks for the feedback. We are investigating into the issue and will update you shortly.

@UtsaVakani Here is a step by step process on how to setup shiny server on azure VM and here is a blog on MS R-server vs Shiny.
I think this video might also help you to deploy your shiny application in azure on a linux environment.
Hope this helps!!

Hope this helps! #please-close.

@UtsaVakani We will now proceed to close this thread. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply. We will gladly continue the discussion and we will reopen the issue.