Already Logged In

Hi, how can i know if my android ds client is already logged in without calling again the login method?
Thanks.

Presence actually only tells you the status of the other connections and not your own.
It seems the Java SDK doesn't support getConnectionState. I'm looking for someone to partner on writing a Kotlin lightweight SDK with the binary parser but will not be doing that until so =(
You can solve your issue however by doing the following:
https://deepstreamhub.com/docs/client-java/DeepstreamClient/#addConnectionChangeListener(listener)
client.addConnectionChangeListener(new ConnectionStateListener() {
    @Override
    public void connectionStateChanged(ConnectionState connectionState) {
        // handle change
    }
});

If the connection state is OPEN it means your connected 👍
Sorry for late reply


KubeVirt Application readiness and health checks

KubeVirt is growing and requires more features and specific configurations in order to work correctly.
Some requirements are soft (i.e. block storage) others are mandatory (i.e. correct security context).
It would be good to have a component to signal me - as an operator - if kubevirt was operating correctly, or if there there is a configuration item which is incorrect or could be set to a better value.
A probably incomplete list of items which can be checked:
P1

Cluster level

[ ] Check for minimum Kubernetes version
[ ] Check for required and not opened feature gates
[ ] Check for raw block
[ ] Check for CDI availability if DataVolume is enabled
[ ] Warn if emulation mode is configured (or any dbug item)
[ ] Check that a minimum number of nodes is available (i.e. 2) to have some sanity check that migration will work

Node level

[ ] Check for kmods (char-major-10-200 #1205) on nodes (check nfd labels?)
[ ] Soft check nested virt is enabled

P2

[ ] Check for relevant features (initializers, …)
[ ] Check for relevant permissions/roles
[ ] Check for req webhook admission controller / validating webhook registration
[ ] check for correct security contexts
[ ] check for correct service accounts
[ ] preset presence ?
[ ] Check that aggregated api registration happened
[ ] Check for host tuned configuratrtion (long term should go to tempaltes)

Based on these checks, the component can also provide a list of supported features.

@rmohr @davidvossel we should add a list of features that need to be checked.

@fabiand I volunteered for the now-closed #964 before to get my current assignments. I Will re-evaluate the resources I have to work on this in the current sprint and report ASAP.

we should add a list of features that need to be checked.

nested virt is enabled, aggregated api registration, validating webhook registration
those are the only ones that come to mind immediately

@fromanirh ack - #964 was the same as this here, thus I hope it's not stopping you from looking at it :)

https://docs.okd.io/latest/admin_guide/diagnostics_tool.html is somewhat related

@davidvossel I am just curious, why would you require nested virt? No commercial distro actually supports that and it is known to have bugs and limitations on other than intel platforms.

Nested could be a recommendation if we detect to run on a hypervisor.

@fabiand That sentence of yours does not make any sense.. you do not need nested for bare metal hypervisor and you already know you have nested when you find yourself in a VM with virtualization enabled. I really seem to be missing something here.
Nested is useful for CI, development and all that.. but production servers can crash when something goes wrong inside a nested VM. That is why nobody officially supports that even though it might work just fine.

Hi,
is there any concrete plan for this? As this labeled "help wanted", I want to see if I can volunteer or not.
What I come up with is either or both of:

(1). implement gRPC health checking protocol (https://github.com/grpc/grpc/blob/master/doc/health-checking.md)
(2). as noted in https://github.com/kubevirt/kubevirt/issues/1023#issuecomment-420621848, add subcommand to virtctl in a similar way to OKD diagnostics (though removed in https://github.com/openshift/origin/pull/20814)

(1) is assumed to be mainly used for readiness/liveness probe, while (2) is more of cluster admin CLI.
I think we should give high priority to (1) though,

To me this feature is a dedicated pod/service which performns teh necessary checks, or collects them from other pods, and then provides one aggregated status.
It's not only about the liveness check of a single pod itself.

I see, now I get why you mentioned OKD diagnostics while not for things like gRPC health checking.

It would still be great to see a contribution in this area!
The great thing abotu this issue is thatit can start small, then grow.

will do! :smiley:

/remove-lifecycle stale

/reopen

/reopen
/remove-lifecycle rotten


Make CodeEditorSpecification property optional

Default to empty string.

Pretty sure this is intended to be about the starter_code property.


Add async methods for the AstraDB VectorStore

Description: fully async versions are available for astrapy 0.7+. For older astrapy versions or if the user provides a sync client without an async one, the async methods will call the sync ones wrapped in run_in_executor
Twitter handle: cbornet_

cc @hemidactylus

LGTM, great work!


Entire article is repeated

The Goal Metric Sals is repeated, but there is nothing about goals metrics for Service

@OpsisCRM Can you point us to the doc you're talking about.

I do not have the link available, but it was about setting up goals.  It
looks as though the author intended using the copied sales content to add
the material about service-related goals, but never made the edits.
I hope that this helps
With thanks
Gill
Gill Walker
CRM Success Catalyst
0410 449709
Looking for help with your CRM? https://calendly.com/opsis Want to book
a meeting - here's my diary http://calendly.com/opsis
Microsoft Certified Trainer (MCT)
Microsoft Certified: Dynamics 365 Sales Functional Consultant Associate
with MB-200 and MB-210
Certified ClickDimensions Consultant
Professional Member of Professional Speakers Australia
<EMAIL_ADDRESS>www.opsis.com.au
Connect with me on Linked In https://linkedin.com/in/crmconsultant
Blog is at https://tinyurl.com/opsisblog
On Wed, Aug 12, 2020 at 1:59 AM Nava Kiran<EMAIL_ADDRESS>wrote:

@OpsisCRM https://github.com/OpsisCRM Can you point us to the doc
you're talking about.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/dynamics-365-customer-engagement/issues/1926#issuecomment-672044575,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APCJOKXSORMG5NV2HPJ6E6DSAFTF3ANCNFSM4PYRMI4Q
.

@OpsisCRM : Thank you for the feedback. The topic you mentioned is intended for Sales users. There are two sections with similar content--the first section describes instructions for the Unified interface app (Sales Hub), and the other section describes instructions for the legacy web client. Hope this clarifies.

Hi Shubhadaj
Two comments - firstly the segments relating to each interface should be
made clearer - even returning to the page to confirm, I did not spot this;
secondly, a link to equivalent information for Service goals should be much
more evident.
I came across this page via a link from something that I read while
revising for MB-230, the Customer Service exam.  Some people would struggle
to extrapolate this information to understand service related goals and
this information is not easy to find.
With thanks
Gill
On Mon, 24 Aug 2020, 10:22 pm shubhadaj<EMAIL_ADDRESS>wrote:

@OpsisCRM https://github.com/OpsisCRM : Thank you for the feedback. The
topic you mentioned is intended for Sales users. There are two sections
with similar content--the first section describes instructions for the
Unified interface app (Sales Hub), and the other section describes
instructions for the legacy web client. Hope this clarifies.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/dynamics-365-customer-engagement/issues/1926#issuecomment-679094105,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APCJOKT5VIOYOYHMZ33XNMTSCJLRPANCNFSM4PYRMI4Q
.

Hi Gill,
Apologies for the long pause on this thread and thanks for your feedback. We've made several improvements to the Goals documentation. We've introduced a new page https://docs.microsoft.com/en-us/dynamics365/sales-enterprise/goals-overview to cover the sales and customer service goals and refined the Goal metric topic as well.
Hope this addresses your feedback. Please let us know if you still have open questions on this.

Hi Gill,
I'm closing the issue. Please feel free to reopen if you still think there are gaps.
Thanks!


[DONTMERGE - WIP] First attempt to create DocBook 5 MAIN

Add chunker.xsl from DocBook XSL
Create map-to-db5MAIN.xsl to create DocBook5 output for MAIN file
Implement previous stylesheet in ditatodocbook.sh script

I've had a look at the new map-to-db5MAIN file.

I diffed between map-to-MAIN and map-to-db5MAIN. Getting a 600-line diff for a 250-line file is ... unexpected. Most of the diffed lines are (unwanted) whitespace changes.
Your reworking currently partially destroys the features to remove/replace files at the top level. To make this work properly, you would need to copy/paste the relevant parts of normal-mode templates into the collect.files templates.
It is also incomplete, there is still an xsl:message for content that needs to go into includes at the end left.

This is all stuff that had already been working.
If this is just about seeing error and warning messages on the command line, it seems to me that there are easier ways to get those (like just outputting the message caught in includes after the xsltproc run).
That may not be proper-est way to go about this but it would be quick.

Hm, there still seem to be a few issues here that I didn't figure out:

we're somehow writing the DB5 namespaces in lots of elements, not just the root element
daps xmlformat does not run, the error is ERROR: Failed to get filelist for ROOTID ""

Also, I have moved your map/bookmap commit onto https://github.com/sknorr/dietrich/tree/f/map-to-bookmap


Fix link to LastActivityView

Link was just missing the  https://www. which made it relative to this repo.

Thanks !!


Reorganize test cases

Most test cases that I added in #56 overlap existing test cases, but they're written in different way. The new tests check logic on the virtual time. IMHO, the new test method is more appropriate for testing Rx library, so I would like to replace the old tests by the new tests.

Added some tests for execution count in 25af59b, because tests added in #56 did not cover that.
Removed the old tests.

@ashfurrow Thank you for reviewing. I've just replaced the matchers in 1b816f2!


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

https://github.com/baseball435/Terraria-Clone/issues
https://github.com/jmrapp1/TerraLegion/issues

Thanks for picking this out! When I changed my username it didn't update links and I missed this one!


feat: add configurable options for each preprocessor

Thanks for the contribution. Could you explain a little bit what issues this solves, and also add some tests for this?

Hello Friedel,
I have applied the method lodash.extend.
I need this functionality in order to select in each of my tests, which the preprocessor will use. For example I have two types of templates: standard templates in folder 'simple_templates' and the templates were pre-compiled 'compiled_templates'. In each test I want to be able to select what templates will be used.
Example configuration
// karma.conf.js
module.exports = function(config) {
  config.set({
    preprocessors: {
      'src/simple_templates/**/*.html': ['htmlProcessor1'],
      'src/compiled_templates/**/*.html': ['htmlProcessor2']
    },

    files: [
      '**/*.html'
    ],

    customPreprocessors: {
      htmlProcessor1: {
        base: 'ng-html2js-configurable',
        stripPrefix: 'src/simple_templates/',
        moduleName: 'template.simple'
      },
      htmlProcessor2: {
        base: 'ng-html2js-configurable',
        stripPrefix: 'src/compiled_templates/',
        moduleName: 'template.compiled'
      }
    }
  });
};

I'll write the tests a little later


host cosign container image on ArtifactHub

Description
Reference Doc: https://artifacthub.io/docs/topics/repositories/#container-images-repositories
To do so, we just need to add some container image labels.
Reference issues:

https://github.com/anchore/grype/pull/639
https://github.com/goreleaser/goreleaser/issues/2830

Let's do it!


Shape mismatch of target array when using categorical_crossentropy and stateful RNNs

Hi guys,
I'm training an RNN model on a time-series classification task. The training set I have is of the shape (200000, 50, 3), i.e. each input series have input_length = 50 and input_dim = 3, and I have 200000 such series. The task is to classify each input series with a label 1-4 (4 classes). Each input series will be tagged with one and only one label. After one-hot transformation the target array (ground truth labels) is of shape (200000, 4), which contains only binary integers.
Since I'm setting stateful=true for SimpleRNN, I have to give the full input shape, with a batch size of 120. My model construction is shown below:
model = Sequential()
model.add(SimpleRNN(n_hidden, batch_input_shape=(120, 50, 3), stateful=True, return_sequences=True))
model.add(Dropout(dropout))
model.add(SimpleRNN(n_hidden, stateful=True, return_sequences=True))
model.add(Dropout(dropout))
model.add(TimeDistributed(Dense(4)))
model.add(Activation('softmax'))
model.compile(loss='categorical_crossentropy', optimizer='adam')

I tried to fit the above model with samples (200000, 50, 3) and target array (200000, 4) but got the error:
Exception: A target array with shape (200000, 4) was passed for an output of shape (120, 50, 4) while using as loss `categorical_crossentropy`. This loss expects targets to have the same shape as the output.

I also tried reshaping the target array to (200000, 1, 4), or repeating it to be of shape (200000, 50, 4) but the error would become:
Exception: You are passing a target array of shape (200000, 1, 4) while using as loss `categorical_crossentropy`. `categorical_crossentropy` expects targets to be binary matrices (1s and 0s) of shape (samples, classes).

Note that other loss functions, e.g. hinge or mse, work well with the (200000, 1, 4) target array.
I get that stateful=true requires full input shape for RNNs. What I don't understand is that why it is trying to fit the target array with the same input_length = 50 as the training samples. Each batch (120, 50, 3) should be fitted with a (120, 4) target array instead of a (120, 50, 4) target array, because each input series only have one corresponding label.
Any suggestions or pointers will be much appreciated. Thanks!

Please refer to stateful LSTM example, the last SimpleRNN should be set return_sequences=False for classification task and TimeDistributed is not needed.
model = Sequential()
model.add(SimpleRNN(n_hidden, batch_input_shape=(120, 50, 3), stateful=True, return_sequences=True))
model.add(Dropout(dropout))
model.add(SimpleRNN(n_hidden, stateful=True, return_sequences=False))
model.add(Dropout(dropout))
model.add(Dense(4))
model.add(Activation('softmax'))
model.compile(loss='categorical_crossentropy', optimizer='adam')

# x shape: (nb_samples, 50, 3)
# y shape: (nb_samples, 4)

model.fit(x, y, batch_size=120)

@joelthchao thanks so much for your help!


Does it support rtmp and hls live video stream?

video url like :
hls, http://v1.live.aisoqu.com/recordings/z1.aisoqu.00018adaf9cc22207395c61a/0_1476431379.m3u8
rtmp, rtmp://pili-live-rtmp.live.aisoqu.com/aisoqu/00018adaf9cc22207395c61a

It should work using the proper plugin. I can git it a test to confirm when I get  some time.

@LonnyGomes any updates on this?

@w0rldart I'll take a look this week.

@w0rldart @vainly Sorry it took a bit to get back to you. I hadn't dealt with HLS sources in the past but after doing some investigation it appears that vjs-video should work out of the box as long as you load in the proper source handler.
Take a look at this codepen to see a working example where I used a video.js HLS source handler to load the URL provided in this issue.
@vainly I didn't get a chance to look too much into the RTMP capabilities but it appears as if RTMP is natively supported by video.js here.
Let me know if this resolves the issues you guys encountered.

First of all, thanks for the amazing player! I am checking your codepen and it is not workink for me (cannot reproduce the sample video). Also, I am no seing integration with HLS at any place. Am I losing something? Is HLS integrated at some place on your directive and the codepen is some kind of demonstration that your directive works with HLS?
Thanks again for your amazing work!

@tludmetal So the key is the source type. If you load the the video.js HLS source handler after loading video.js and specify the type as application/x-mpegURL it should work.
<source src="http://demo.com/stream.m3u8" type='application/x-mpegURL' />

The codepen sample provided doesn't work in Chrome. It loads in Safari because HLS is natively supported in Safari. Just an FYI


how to serve model in vllm and use in dspy?

vllm serve NousResearch/Meta-Llama-3-8B-Instruct --dtype auto --api-key token-abc123

I have served my model using vllm
#Load model and configure
lm = dspy.LM('openai/NousResearch/Llama-3.2-1B', api_base="http://<IP_ADDRESS>:8000/v1", api_key="token-abc@123")
dspy.configure(lm=lm)

While trying to infer the served model in dspy using singature, i get this error
BadRequestError: Error code: 400 - {'object': 'error', 'message': 'As of transformers v4.44, default chat template is no longer allowed, so you must provide a chat template if the tokenizer does not define one.', 'type': 'BadRequestError', 'param': None, 'code': 400}

It works while using openai client
from openai import OpenAI
client = OpenAI(
    base_url="http://localhost:8000/v1",
    api_key="token-abc@123",
)

completion = client.completions.create(
  model="NousResearch/Llama-3.2-1B",
  prompt="question: what is sum of 12.5 and 40.7? answer: the answer is ",
  echo=False,
  n=2,
  stream=False,
  logprobs=3,
  max_tokens=256,
  temperature = 0.3
)

print(completion.choices[0].text)

Can anyone help me with this

lm = dspy.LM('openai/unsloth/Llama-3.2-3B-Instruct', api_base="http://<IP_ADDRESS>:8000/v1", api_key="token-abc@123", model_type='text')

adding model_type='text' made it work.
closing this issue


Expect and output basis as positive number

Basis should be a positive number. It was helpful to think of it as a negative because total value fro a buy from the exchange is a negative value. Basis in accounting is really the positive that cancels the negative to leave zero (-8000 USD + 1 BTC * 8000 USD / BTC = 0 thus the 1 BTC has a basis of 8000 USD).

looking at this a bit closer, basis values were getting calculated incorrectly for BTC due to the use of sum along with the fact that the data used can be negative or positive. This needs to be corrected in order to get accurate basis value calculations.


show_doc improvements

cc @hamelsmu @jph00. I'm curious to hear your thoughts on d0d8d2751cb74d71bc720d021ad59438ffe00c6a in particular

fix #771
fix #807
fix #808

Lgtm! Was there anything in particular about that commit you wanted to discuss?

BTW CI thinks you have unclean NBs


Fix nolimit tag build

This should fix the nolimit build when specified.
Don't forget to specify the env variable DRONE_LICENSE to something NOT empty e.g. /etc/drone.key even if it doesn't exist, otherwise you get a SIGSEGV when running the binary.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x14c97fd]

goroutine 1 [running]:
main.provideLicense(0xc0002ab2b0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1, 0x0, ...)
/usr/src/myapp/cmd/drone-server/inject_license.go:45 +0xbd
main.InitializeApplication(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1, 0x0, 0x1a3185c5000, ...)
/usr/src/myapp/cmd/drone-server/wire_gen.go:62 +0xc10
main.main()
/usr/src/myapp/cmd/drone-server/main.go:63 +0x3ab

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

thanks, I think we can fix the panic by returning a license from Trial like this:
-func Trial(string) *License         { return nil }
+func Trial(string) *License         { return DefaultLicense }


Service not automatically created?

What kind of request is this (question/bug/enhancement/feature request):
Question
Steps to reproduce (least amount of steps as possible):
Create workload
Result:
Service is not created
Other details that may be helpful:
N/A
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.2.4
Installation option (single install/HA): single node, bare metal

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Hosted
Machine type (cloud/VM/metal) and specifications (CPU/memory): metal
Kubernetes version (use kubectl version): v1.11.6

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.7", GitCommit:"6f482974b76db3f1e0f5d24605a9d1d38fad9a2b", GitTreeState:"clean", BuildDate:"2019-03-25T02:52:13Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.6", GitCommit:"b1d75deca493a24a2f87eb1efde1a569e52fc8d9", GitTreeState:"clean", BuildDate:"2018-12-16T04:30:10Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
Version:           18.06.1-ce
API version:       1.38
Go version:        go1.10.3
Git commit:        e68fc7a
Built:             Tue Aug 21 17:20:43 2018
OS/Arch:           linux/amd64
Experimental:      false
Server:
Engine:
Version:          18.06.1-ce
API version:      1.38 (minimum version 1.12)
Go version:       go1.10.3
Git commit:       e68fc7a
Built:            Tue Aug 21 17:28:38 2018
OS/Arch:          linux/amd64
Experimental:     false
--

According to the docs: https://rancher.com/docs/rancher/v2.x/en/k8s-in-rancher/service-discovery/

For every workload created, a complementing Service Discovery entry is created. This Service Discovery entry enables DNS resolution for the workload’s pods using the following naming convention: ..svc.cluster.local.

That's not happening for me. At least not for workloads created manually from the rancher web ui. What am I missing?

This is on a fresh install, clean node, new install of server and agent

Also, not sure if related but some services are not working:
Workload: cattle-cluster-agent
ERROR: https://mydomain.com/ping is not accessible (Failed to connect to mydomain.com port 443: Connection refused)

Where mydomain.com has an https certificate from let's encrypt
and
nginx-ingress-controller
F0616 19:43:44.025190 9 main.go:72] Port 80 is already in use. Please check the flag --http-port

Which, yeah, the port is taken by the rancher server

Found the issue. it was caused by cattle-cluster-agent not running. And that didn't work because mydomain.com resolved to my router's public ip address and I changed the dns settings for cattle-cluster-agent to add the private ip address for the server.


Windows IoT Swagger: Return 201 on Create Response

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify: Currrently on Service_Create we return a 201, updating swagger to match this behavior.

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. N/A
When you expect to publish swagger? Please provide date, or month to public if date is not available yet. N/A
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@qianwens The breaking changes were approved and all checks have passed. Could you take a look at this?

@qianwens The breaking changes were approved and all checks have passed. Could you take a look at this?


Found a bug in experiments.js

        $.post("/experiments/goal/" + goal_name);

need change to:
 $.post("/experiments/goal/" + goal_name + '/');
and please, write in README.rst to include this js file with static in template where need to use experiments.
Thanks for your great work, you make my job easier a lot.

+1

This should be fixed in current master branch.


Upgrade to dependency analysis plugin 1.0

This updates DAGP to its 1.0 APIs! This included major updates to DependencyRake along the way, namely:

Removing our leftover shims for resources-only projects (these should Just Work now that we use non-transitive R classes I think?)
Removing our custom facade handling as this is now covered by the plugin's "bundles" notion
Apply common bundles and configurations in SGP to projects

Will take this for a spin in the main repo when I'm back from my trip

Note I'll do a separate PR to address suggestions it has for this own repo

Ok took it through its paces and fixed some things. Looking mostly good now other than some known issues around test fixtures support


IMU topic

Hi,
It says that OAK-D includes the IMU:
This DepthAI variant includes three onboard cameras and the BNO085 IMU and interfaces over USB3C to the host, allowing use with your (embedded) host platform of choice, including the Raspberry Pi and other popular embedded hosts.
How can I get this IMU data over the ROS topic?

IMU data messages are not added yet. I am planning to work on that next week.

Oh and FWIW @stevemartinov here is the IMU API in C++/Python:
https://docs.luxonis.com/projects/api/en/latest/components/nodes/imu/
Just to give a heads up on what is there in the meantime.


UB in matches on DebugReportObjectTypeEXT

This value is represented in Rust as an enum, but vulkan can provide values that ash doesn't expect. Worse, ash does not sanity-check them, leading to UB when matching (for example, in the derived Debug implementation).
Current ash defines a continuous range of values from 0 to 28 inclusive. By contrast, my vulkan 1.0.61 header defines these additional values:
typedef enum VkDebugReportObjectTypeEXT {
    // ...
    VK_DEBUG_REPORT_OBJECT_TYPE_DISPLAY_KHR_EXT = 29,
    VK_DEBUG_REPORT_OBJECT_TYPE_DISPLAY_MODE_KHR_EXT = 30,
    VK_DEBUG_REPORT_OBJECT_TYPE_OBJECT_TABLE_NVX_EXT = 31,
    VK_DEBUG_REPORT_OBJECT_TYPE_INDIRECT_COMMANDS_LAYOUT_NVX_EXT = 32,
    VK_DEBUG_REPORT_OBJECT_TYPE_VALIDATION_CACHE_EXT = 33,
    VK_DEBUG_REPORT_OBJECT_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_KHR_EXT =<PHONE_NUMBER>,
    VK_DEBUG_REPORT_OBJECT_TYPE_SAMPLER_YCBCR_CONVERSION_KHR_EXT =<PHONE_NUMBER>,
    VK_DEBUG_REPORT_OBJECT_TYPE_BEGIN_RANGE_EXT = VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXT,
    VK_DEBUG_REPORT_OBJECT_TYPE_END_RANGE_EXT = VK_DEBUG_REPORT_OBJECT_TYPE_VALIDATION_CACHE_EXT,
    VK_DEBUG_REPORT_OBJECT_TYPE_RANGE_SIZE_EXT = (VK_DEBUG_REPORT_OBJECT_TYPE_VALIDATION_CACHE_EXT - VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXT + 1),
    VK_DEBUG_REPORT_OBJECT_TYPE_MAX_ENUM_EXT = 0x7FFFFFFF
} VkDebugReportObjectTypeEXT;

Given that ash does not constrain the set of possible extensions enabled at runtime (and indeed doing so would be a severe limitation) I believe an enum is fundamentally inappropriate here, as even the application may not be statically aware of all possible values.
It's probably worth revisiting all other uses of rust enums where the vulkan API instead uses an integer constant to check for similar issues.

I think this is already addressed in my new generator branch, I just need to find some time to finish it up.

I'm also observing this in VkResult values, which is aggravating as it turns what would otherwise be helpful diagnostic panic output on Result::unwrap into an illegal instruction crash.

Practically every error I make (on intel) seems to produce UB in unwrap. I'll see if I can come up with some examples.

Here are some result codes that my <IP_ADDRESS> header declares which ash does not:
    VK_ERROR_OUT_OF_POOL_MEMORY = -1000069000,
    VK_ERROR_INVALID_EXTERNAL_HANDLE = -1000072003,
    VK_ERROR_INVALID_SHADER_NV = -1000012000,
    VK_ERROR_FRAGMENTATION_EXT = -1000161000,
    VK_ERROR_NOT_PERMITTED_EXT = -1000174001,

VK_ERROR_OUT_OF_POOL_MEMORY, for example, is easily reproduced.
I don't think ash should be defining closed rust enums for values that the Vulkan implementation generates unless the spec makes a very clear guarantee that no new cases will ever be defined.

Fixed


Remove prefix from cluster name

We want to remove the prefix from cluster name deployments, as people might adhere to their own naming convention. This is a breaking change, and will trigger a new major version.

Closed, fixed in https://github.com/amestofortytwo/terraform-azurerm-aks/commit/01ff382fd8796396d6db019329cb31e1ce436598


RHEL-8/9 EC2 image definitions fixes

disable the amdgpu module by default on all RHEL AWS images
exclude unwanted packages from RHEL-9 EC2 SAP package set

This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

It's a pretty small change in terms of code so let's just merge and I'll rebase.

Thanks to both. I explicitly tagged @achilleas-k due to his WIP on el9 distro definitions...


Update scripts to cope with new Sentinel. Add new phenology notebook

Such a cool notebook!

One comment on the script: the SWIR1 version of NDWI is usually called the Modified Normalised Difference Water Index... if you can be bothered renaming it it might be good to make it easier for other people to find in the future, but it's not a big deal


Update Facilities API Validation

Definition of Ready

[x] Does this meet the INVEST criteria?
[x] Does this have a clearly defined user?
[x] Does this have an estimate?
[x] Does this have acceptance criteria?
[x] Does this have sufficient context for the specific functionality being developed (design, business rules, etc.)
[x] Does this have a dev link been provided in the design?
[x] Is this traceable to a feature, epic, or PI?

User Story
As a facilities API user I want the system to validate if a required parameter is empty so that I can successfully build a query
Acceptance Criteria
Given that a user has made a GET request to an facilities endpoint (see context for list of endpoints)
When the system detects that a required parameter is empty or null
Then the system returns the following error message: <  insert property  > should not be null, undefined, or empty FV-106
Development Notes
Does this Story require 508 Testing?

[ ] Implementing a new authoring tool that will produce code / content for the application
[ ] Implementing a 3rd party widget that will be part of the application
[ ] Adding new / updating custom functionality
[ ] Adding new / updating a page template
[ ] Adding new / replacing existing functionality (unless the replacement has already passed 508 testing)
[ ] Full Site Review prior to a scheduled EPA 508 review
[ ] Planning a video that will appear on the application
[ ] Producing a video that will appear on the application
[ ] Producing Training materials
[ ] Producing documents

Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Facilities API

facilities/attributes
facilities/attributes/stream
facilities/attributes/applicable

Testing
Test Case: TC645
Tester: @JanellC
Definition of Done

[x] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[x] Has the code been unit tested and peer reviewed?
[x] Have the functional tests been executed?
[x] Have all defects been reviewed and dispositioned, resolved, or deferred?
[x] Is the user story ready to be deployed to the test/staging environments?

TC645 passed @tlageman-epa


Josilyn workbench

I have verified the page renders and my test cases pass after doing a rebase.

Great work! Way to take on the test cases and learn something new. This really demonstrates your ability to work through tough requirements. Keep it up, and pay it forward.


Pass in grids to grdimage

Implements support for xarray.DataArray grids in Figure.grdimage.
Not much changed here but this required a lot of changes to the
GMT API itself.
Lacking a bit in documentation but I'm working on a refactor of the
library which will make these things easier.
Fixes #124

Waiting on conda-forge/gmt-feedstock#47 with the new build of GMT trunk.


doc: fix broken link

fix broken link

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #1167 (a320c20) into main (8bc72e8) will decrease coverage by 0.07%.
The diff coverage is n/a.

:exclamation: Current head a320c20 differs from pull request most recent head f79e2fb. Consider uploading reports for the commit f79e2fb to get more accurate results

@@            Coverage Diff             @@
##             main    #1167      +/-   ##
==========================================
- Coverage   56.92%   56.85%   -0.08%
==========================================
  Files         127      127
  Lines       21352    21352
==========================================
- Hits        12154    12139      -15
- Misses       7726     7738      +12
- Partials     1472     1475       +3

Impacted Files
Coverage Δ

pkg/meta/sql.go
67.38% <0.00%> (-0.77%)
:arrow_down:

Continue to review full report at Codecov.

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


PoliteMail Certified Connector

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[X] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation. (***We are an existing Connector but not in GitHub as it appears to be submitted prior to open source repo requirement)
[X] I attest that the connector works and I verified by deploying and testing all the operations.
[X] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[X] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[X] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[X] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@microsoft-github-policy-service agree company="PoliteMail"

attached per comment in ISV studio...
Dear Partner,
My apology for the delay.
Can you please attach zip file to your GitHub PR, we will investigate further and get back to you.
PoliteMail.zip


custom connectors CAN now be added to solutions

[Enter feedback here]
Please confirm that my testing is correct. Custom Connectors can now be added to Dataverse solutions. IF so, please update this limitation article.

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

ID: ba673f56-d0c1-6795-c028-5e121fe3cfeb
Version Independent ID: bb0c60db-d75b-c470-81f9-3414e9b863d5
Content: Solutions in Power Apps - Power Apps
Content Source: powerapps-docs/maker/data-platform/solutions-overview.md
Service: powerapps
Sub-service: dataverse-maker
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @robdawsoncranhillinsight. This issue has been assigned to the doc author for review.

@robdawsoncranhillinsight - Thank you for your feedback. You're correct. The article has been revised to remove that limitation.
Closing issue.


Update S3 access URL environment variable

Not sure if this was ever baseUrl but it looks like it should be BUILDKITE_S3_ACCESS_URL based on the current agent code and https://github.com/buildkite/agent/pull/261.

Great catch @dblandin, thanks a bunch for the PR! 🙏🏻😄


Add A216WCB to available materials

Add A216WCB to available materials.

Codecov Report

Merging #294 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #294   +/-   ##
=======================================
  Coverage   80.02%   80.02%
=======================================
  Files          11       11
  Lines        3169     3169
=======================================
  Hits         2536     2536
  Misses        633      633

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 dd03721...6621cc8. Read the comment docs.


Using version 2.9.3 gets Maximum call stack size exceeded exception in google chrome.

I am using chartjs to create a scatter chart of OOM events by timestamp. If I use version 2.9.3, I get the "Maximum call stack size exceeded" exception in google chrome. Same for versions 2.9.0, 2.9.1 and 2.9.2. But version 2.8.0 works fine. I will paste in my HTML/JS code. To get the error, just change "2.8.0" to "2.9.3".
Version 74.0.3729.169 (Official Build) (64-bit)
Running on Ubuntu 16.04.
oom-analysis.html.gz

Duplicate of #7761?

Evert:
Probably not. Here is the traceback from chrome (I always seem to get both errors – I’m assuming the second is caused by the first):
Uncaught RangeError: Maximum call stack size exceeded
at hn (Chart.min.js:7)
at n._getLabelSizes (Chart.min.js:7)
at n.calculateTickRotation (Chart.min.js:7)
at n.update (Chart.min.js:7)
at he (Chart.min.js:7)
at Object.update (Chart.min.js:7)
at Qe.updateLayout (Chart.min.js:7)
at Qe.update (Chart.min.js:7)
at Qe.construct (Chart.min.js:7)
at new Qe (Chart.min.js:7)
Uncaught TypeError: Cannot read property 'skip' of undefined
at Qt (Chart.min.js:7)
at single (Chart.min.js:7)
at Qe.getElementsAtEventForMode (Chart.min.js:7)
at Qe.handleEvent (Chart.min.js:7)
at Qe.eventHandler (Chart.min.js:7)
at n (Chart.min.js:7)
at HTMLCanvasElement.Me. (Chart.min.js:7)
David
[https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/03_standard_indigoblue.png]
David Ward
TECHNICAL LEADER.SOFTWARE ENGINEERING-DEVELOPMENT
daviwar2<EMAIL_ADDRESS>Tel:
Cisco Systems, Inc.
8135 Maple Lawn Blvd.
FULTON
20759
United States
cisco.com
[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]
Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click herehttp://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html for Company Registration Information.
From: Evert Timberg<EMAIL_ADDRESS>Sent: Tuesday, October 13, 2020 4:07 PM
To: chartjs/Chart.js<EMAIL_ADDRESS>Cc: David Ward (daviwar2<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [chartjs/Chart.js] Using version 2.9.3 gets Maximum call stack size exceeded exception in google chrome. (#7881)
Duplicate of #7761https://github.com/chartjs/Chart.js/issues/7761?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/chartjs/Chart.js/issues/7881#issuecomment-707978366, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMZOUSM7RM7P2UESUVOCZBDSKSXOLANCNFSM4SPRXBWQ.

thanks @davidspencerward, I'll take a look and see if I can also reproduce in v3.0.0-beta.3.

The issue seems to be related to stepSize: 1. If I remove that, it's not a problem. I'm guessing that when stepSize is 1, there are too many ticks and we run out of memory when measuring the text.

Evert:
Awesome. That works and improves everything!!!! Zooming is 1,000 times faster now.
Thanks for the quick response!!!
David
[https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/03_standard_indigoblue.png]
David Ward
TECHNICAL LEADER.SOFTWARE ENGINEERING-DEVELOPMENT
daviwar2<EMAIL_ADDRESS>Tel:
Cisco Systems, Inc.
8135 Maple Lawn Blvd.
FULTON
20759
United States
cisco.com
[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]
Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click herehttp://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html for Company Registration Information.
From: Evert Timberg<EMAIL_ADDRESS>Sent: Tuesday, October 13, 2020 6:12 PM
To: chartjs/Chart.js<EMAIL_ADDRESS>Cc: David Ward (daviwar2<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [chartjs/Chart.js] Using version 2.9.3 gets Maximum call stack size exceeded exception in google chrome. (#7881)
The issue seems to be related to stepSize: 1. If I remove that, it's not a problem. I'm guessing that when stepSize is 1, there are too many ticks and we run out of memory when measuring the text.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chartjs/Chart.js/issues/7881#issuecomment-708037337, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMZOUSMTNOO5TJEWLHXZC7LSKTGC5ANCNFSM4SPRXBWQ.


Transformer alarms

Create cloudwatch alarms for transformer failures

I think we get enough feedback on transformer failures now.


Add shuffle with seed and tests for StaticArray

Sorry, I had trouble with the conflict, so I closed the last branch and recreated a new one to fix the problem properly. (See PR #2234).
It should be better !

Thank you!


[20.09] coturn: apply patch for CVE-2020-26262

Motivation for this change
Related to #109038
Fixes CVE-2020-26262.
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)
[ ] 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.

I am not liking that we backport new features with this release. Are they optional? If so, can we keep them disabled? Otherwise we can always just apply this patch:
https://github.com/coturn/coturn/commit/abfe1fd08d78baa0947d17dac0f7411c3d948e4d.patch

I am not liking that we backport new features with this release. Are they optional? If so, can we keep them disabled? Otherwise we can always just apply this patch:
https://github.com/coturn/coturn/commit/abfe1fd08d78baa0947d17dac0f7411c3d948e4d.patch

If so, can we keep them disabled?

Why should we disable features?
The release also contained two nullpointer dereferences. I would prefer shipping an official version instead of a custom patched one even if it container a feature or two.

If so, can we keep them disabled?

Why should we disable features?
The release also contained two nullpointer dereferences. I would prefer shipping an official version instead of a custom patched one even if it container a feature or two.

I tested coturn with the patch, it works.
Are SRI hashes allowed on 20.09?

I tested coturn with the patch, it works.
Are SRI hashes allowed on 20.09?

@grahamcofborg build coturn

@grahamcofborg build coturn


Adding 2020-09-01-hybrid profile

/azp run

Hi @msyyc @jsntcy , it's is a PR for AzureStack.
Would you help to merge this?

Hi @msyyc @jsntcy , it's is a PR for AzureStack.
Would you help to merge this?

/azp run

/azp run

/check-enforcer override

/check-enforcer override

/azp run python - anomalydetector - ci

/azp run python - anomalydetector - ci

/azp run python - anomalydetector - ci (Build Test Windows_Python35)

/azp run python - anomalydetector - ci (Build Test Windows_Python35)

@jsntcy Thanks for the merge. Could you please let me know when are we planning to do the next release of azure-common package? I do not have an urgency, just wanted to know the timeline

@jsntcy Thanks for the merge. Could you please let me know when are we planning to do the next release of azure-common package? I do not have an urgency, just wanted to know the timeline


Fix e2e to adapt to multi-steps

Hive CI config was recently changed to use "multi-steps" workflow for
IPI installs of e2e tests.
This commit changes the e2e hack scripts to adapt to the environment
variables made available from the CI change.

/assign @akhil-rane

/test e2e
/test e2e-azure
/test e2e-gcp

/test e2e-gcp

/lgtm

/cherry-pick ocm-2.1

/cherry-pick ocm-2.1


HMR requires full reload when changes to CSS are made

Hey there,
I noticed that when you change your CSS it requires a full reload. This is the console's output:

The following modules couldn't be hot updated:
./~/css-loader?{"localIndentName":"localIdentName=[name][local]_[hash:base64:5]","sourceMap":true,"modules":true,"importLoaders":1}!./~/postcss-loader?{"sourceMap":true,"plugins":[null,{"version":"5.2.15","plugins":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null],"postcssPlugin":"postcss-cssnext","postcssVersion":"5.2.15"},null,{"version":"5.2.15","plugins":[null,null,null,null]}]}!./app/assets/styles/base.pcss

Any ideas on how to fix this? It's pretty annoying

Hmmm... I can't replicate this. What's with the .pcss file extension on your base file (is that something special for postcss?) I've never seen it before and the webpack config only looks for .css files so... that might be it...

The .pcss file extension is for postcss, so my text editor doesn't complain about weird looking postcss syntax. Either way that doesn't affect this issue.
I actually figured out the problem to this issue and figured out a workaround. If you import a css file to use for a stateless component (like the client.jsx file), it's not able to hot reload. So everytime you make a change to that css file the whole component will need to do a full reload. The solution is to change it to a regular React component.


[Android 12] Quick actions always open app.

I don't set any launchActivity for quick action. But it launches app.
It reproduces for Android 12 only, 11 is ok.
I checked 4.0.1 and wasn't able reproduce.
So looks like latest fixes of 4.1.0 introduced this problem.

thanks, will look into it. It indeed does sound like it's from the latest changes in 4.1.0 release. This is probably where the issue lies https://github.com/invertase/notifee/blob/864ca83415d047abd61ea4659bb9febdcc7d43de/android/src/main/java/app/notifee/core/NotificationPendingIntent.java#L43


mac: Fix layer scale not being updated when contents is updated and w…

…indow is on a new screen
cc #67

I hope that saving the window is ... safe enough in terms of memory management. Otherwise this seemed like an approach simple enough :)

Sure :)


Add more options for configuring single file report

This improvement allows to customize single file path. It should fix #17. It's also related (kind of duplicated) with #19 #18 and #16, since it allows to do all the things mentioned in other PR's

Coverage decreased (-0.9%) to 99.091% when pulling ecdf5f701ded79be6b5c32a7b5ac2a5cba1ffec3 on povilasjurcys:more_flexible_configuration into d907ca2c56e81b8996dc6f420b056f6a0c7f6e71 on fortissimo1997:master.

👍


Add /root/.pub-cache/bin to PATH to allow CMDs like webdev

Credits @gmpassos who filed https://github.com/dart-lang/dart_docker/pull/48

@googlebot, the change was originally submitted in https://github.com/dart-lang/dart_docker/pull/48, which the CLA bot approved :)

Note, I tested this locally.


Running tests whilst using Electron as Node

What problem does this feature solve?
Currently, testing with Jest or any other test framework is impossible when using both Vue, and Electron running as Node. Electron needs to be run as node, to allow native modules to work. And currently this sort of call is needed for a test script (when not using vue-cli):
cross-env ELECTRON_RUN_AS_NODE=true ./node_modules/electron ./node_modules/jest-cli/bin/jest.js

Although vue-cli is very good, it insists on calling itself in the test script, for reasons I believe to do with allowing Babel to understand what's going on. Unfortunately this prevents any Electron apps that have native modules from being tested.
What does the proposed API look like?
This call would make sense:
cross-env ELECTRON_RUN_AS_NODE=true ./node_modules/.bin/electron<EMAIL_ADDRESS>test:unit

But it doesn't work. Making this work would be perfect. Allowing the direct use of simply 'Jest' would be even better, but I appreciate the reason why this isn't possible.

Unfortunately this prevents any Electron apps that have native modules from being tested.
[...]
But it doesn't work.

Can you be more specific? I don't have an electron app available to run your commands and see what happens, so right no idea what's actually happening.

Apologies, I was quite vague at that point! I've edited to improve the answer. Hope this helps.


[enhancement] add sklearnex version of validate_data, _check_sample_weight

Description
This is another interim PR towards introducing the new onedal finiteness checker into the sklearnex estimator workflows. This is not yet introduced into any of the estimators, and so performance benchmarks are not necessary.  This PR focuses on making sure that input and outputs of validate_data and _check_sample_weight are respected for sycl_usm_ndarray types and that the new finite checker is properly called and yields results in a range of scenarios.  This is also done to minimize the review burden, as changing all the estimators is a large change.
The new process for all estimators will be as follows:

All estimators will call validate_data and _check_sample_weight once in sklearnex in _onedal_* methods called by device_offload's dispatch
All estimators will call assert_all_finite no where else but in validate_data or _check_sample_weight unless an operation before the oneDAL backend can yield a inf/NaN (this is a strict condition, and is expected to be extremely uncommon/ hard to allow)
Calls to check_array anywhere in the onedal or sklearnex folders must have assert_all_finite checks turned off.

A follow up PR will create a design test for this, and will introduce the new validate_data in one estimator. Other estimators will occur in individual PRs due to the depth of the changes.

PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.
You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).
Checklist to comply with before moving PR from draft:
PR completeness and readability

[x] I have reviewed my changes thoroughly before submitting this pull request.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
[x] Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
[x] I have added a respective label(s) to PR if I have a permission for that.
[x] I have resolved any merge conflicts that might occur with the base branch.

Testing

[x] I have run it locally and tested the changes extensively.
[x] All CI jobs are green or I have provided justification why they aren't.
[x] I have extended testing suite if new functionality was introduced in this PR.

Performance

[x] I have measured performance for affected algorithms using scikit-learn_bench and provided at least summary table with measured data, if performance change is expected.
[x] I have provided justification why performance has changed or why changes are not expected.
[x] I have provided justification why quality metrics have changed or why changes are not expected.
[x] I have extended benchmarking suite and provided corresponding scikit-learn_bench PR if new measurable functionality was introduced in this PR.

/intelci: run

/intelci: run

Please manually check private CI, failure is a 503 http error (unrelated to the PR).

/intelci: run

/intelci: run

/intelci: run

/intelci: run

Any perf results to share? (doesn't even have to be full benchmarks but even a large BasicStatistics single GPU run would indicate progress)

Any perf results to share? (doesn't even have to be full benchmarks but even a large BasicStatistics single GPU run would indicate progress)

I am purposefully not including this in any estimators at this point to speed the review/merging of the PR: there will be performance benchmarks for #2209 #2207 #2206 #2201 and #2189. Good question.

/intelci: run

/intelci: run

Any perf results to share? (doesn't even have to be full benchmarks but even a large BasicStatistics single GPU run would indicate progress)

I am purposefully not including this in any estimators at this point to speed the review/merging of the PR: there will be performance benchmarks for #2209 #2207 #2206 #2201 and #2189. Good question. GPU performance improvements will occur when array_api support in the dispatch function is included. (so unfortunately not yet, there is some aspects missing to those PRs which must come from #2096)

Are we expecting perf to be on par with what we were seeing from https://github.com/uxlfoundation/scikit-learn-intelex/pull/2153 ?

/intelci: run

/intelci: run

/intelci: run


Support batching of overlapping ground primitive geometry

Currently, overlapping ground primitive geometry cannot be batched together. There is no error but it produces incorrect results.  @likangning93 can you provide some details about why there is this limitation and possible ideas for how we may be able to fix it?

The lack of error combined with bad visualization makes this a point of confusion.  Most recently, we had an accidental regression that we fixed in #8694 with the entity API and #8666 was written up by a user trying to batch ground primitives.


Implement basic ServiceProvider related interface

[ ] Implement test
[x] Implement list @ owl-cli
[x] Implement edit @ owl-cli
[x] Implement list @ owl-daemon
[x] Implement edit @ owl-daemon

Merged #29


Conmon should not be installed in /usr/bin.

This pull request includes the man page pull, will rebase when that gets merged.

+1 but we'll need a flag to ocid like --conmon to be able to specify another custom path to conmon (e.g. while developing), I guess a follow up it's fine though
LGTM

Looks fine, but needs rebase.

make lint failed:
$ make lint
mkdir -p /home/travis/gopath/src/github.com/kubernetes-incubator/cri-o/vendor/src/github.com/kubernetes-incubator
ln -sfn /home/travis/gopath/src/github.com/kubernetes-incubator/cri-o /home/travis/gopath/src/github.com/kubernetes-incubator/cri-o/vendor/src/github.com/kubernetes-incubator/cri-o
checking lint
oci/oci.go:23:7:warning: don't use ALL_CAPS in Go names; use CamelCase (golint)
oci/oci.go:23:7:warning: exported const CONMON_PATH should have comment or be unexported (golint)
make: *** [lint] Error 1

Update conmon change to include option. Not that familiar with the code, so hopefully I did it correctly.

LGTM


Dean using billing groups via cli

What changed, and why it matters
Migrated the intercom help article content for Billing Groups via CLI to docs.aiven.io.
The content appears to be valid and the style/appearance conforms to the docs site.
Uploaded the content under Platform > HowTo > Billing Management

@deanholbrough Hi, Dean, thanks for taking the time to do this. However, we do have some billing group instructions already for the CLI in that section: https://docs.aiven.io/docs/tools/cli/billing-group. Could you please check whether there is anything in the article that is missing from our current CLI article and add it there instead?

@deanholbrough I've reviewed the content in this PR with the updated avn billing-group doc and I don't see anything here that doesn't exist there or in the conceptual article for billing groups. If you have no objections, I'd like to close this PR now.

@deanholbrough I've reviewed the content in this PR with the updated avn billing-group doc and I don't see anything here that doesn't exist there or in the conceptual article for billing groups. If you have no objections, I'd like to close this PR now.

I have no objections. Thanks.


deps: Bump curl -> 7.79.0

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message: deps: Bump curl -> 7.79.0
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] Fix #18051
[Optional Deprecated:]
[Optional API Considerations:]

Deps look fine. The patch we carry for Curl is a lot smaller than it used to be but was a prior source of Windows CI failures. Not sure if similar problems are being encountered here

ah, thanks, i didnt notice the patch, ill update

/wait

its the curl test that is failing https://dev.azure.com/cncf/envoy/_build/results?buildId=88066&view=logs&j=b840a642-5ff3-5357-2e4b-e06e40b0cffd&t=67965174-5100-5631-9dc0-68b9f0aacb53&l=1542
afaict the patch applies cleanly tho so its beyond my immediate understanding as to what is failing

@phlax 7.79.0 is out https://github.com/curl/curl/releases/tag/curl-7_79_0. Maybe you could bump to that version and see where CI is at?

seems to fall over for the same reason/s
checking the windows ci, afaict the test log publishing seems to be broke - ie it says there are test logs, but they dont get uploaded
its not clear exactly what happens with the test uploads, but it provides a link that 404s
cc @wrowe @davinci26

I think it's failing on this outstanding TODO
https://github.com/envoyproxy/envoy/blob/19a4823908b8e1952aae3c54e2cf4b08203112f4/test/dependencies/curl_test.cc#L33-L36
Maybe to remove that windows if/else? See https://github.com/envoyproxy/envoy/pull/13063/files

Maybe to remove that windows if/else?

thanks, ill give it a whirl

/lgtm deps


Create webpage build content that is optimized for git tracking

Currently our npm run build output on gh-pages is minified and does not have stable file names across changes.
This can be problematic for git tracking:

everytime there is a new deployment, all the blobs on gh-pages must be rewritten
there are not clear diffs that allow us to check that source code changes create the desired HTML changes

@arielsvn and I dealt with this issue for the Sci-Hub Stats Browser frontend. Ariel's code is here.
@vincerubinetti how hard would it be for us to include newlines and have stable filenames in the build output?

IMO it's better how it's implemented here, since the generated files live separated from the source code, minified and with the hashes in the filenames.

there are not clear diffs that allow us to check that source code changes create the desired HTML changes

Is this really important? everything in gh-pages depends on the source code, checking those diffs should be enough. For example in refinebio-frontend we deploy to S3 and replace all files on every deploy.
When we implemented the Sci-Hub Stats Browser I wasn't aware of CircleCi and how easy it was to create a script that deployed to gh-pages automatically, that's why the generated files were included along with the source code which later created problems when reviewing the PR.

@dongbohu and I discussed this at length when starting the project. He argued that react-scripts was much easier to set up than manually configuring webpack, which is true. But if you ever need to change something about how the react-scripts build process works, it seems to be prohibitively difficult.
The times I've done manual webpack configuration, it did take some time upfront to set up, but after that I never had to touch it again. I could've just gotten lucky though. I think for now I might want to go back to a manual configuration, just so we have more control over (and more importantly, understanding of) the build process. If we ever wanted to go back to react-scripts for some reason, I think that would probably be pretty easy anyway.

Yes, react-scripts it's definitely not for all projects. In the case of refine.bio, we have had a good experience with it and so far we haven't ejected webpack configuration. It's good to know that's an option if we ever need it.

@dhimmel I previously said I was going to do a config from scratch. I'm going to take that back, because I forgot that create-react-app ("react scripts") automatically sets up hot-reloading, which is extremely useful during development and a huge pain to set up manually. If it were just the compiling and the bundling, I'd have already set it up myself.
Note that the output of this stuff is mostly going to be javascript, not html. And it's going to be much less readable and meaningful than the input /src. Someone should look at the /src diff to really see what has changed, as that is the true "markdown" of the content of the page.
Recommend we close this issue, and let another one be created if we ever need to do a manual config (or a create-react-app eject) for a different reason.

Okay closing. We can always revisit this and reopen should the calculus change.


fix: use correct require extension to load config

Description
Fix #9112
Check in _require.extensions for .ts added by ts-node before falling back to .js.
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

My bad. Had to force-push. Committed to the wrong branch.

Looks good, @bluwy could you resolve the conflicts, let's get this one before the next patch 👍🏼

Resolved 👍


Added sleepSensor attribute and wider range for dimmer settings

Hey Russ (@rvrolyk), First of all, thanks for making this awesome integration. I love it. I made some edits so that I can select the beds uniquely based on the sleepSensor capability. I also edited the dimmer response to respond without error to ranges from 0 to 100 mapped to 1, 2, 3. I wrote about these edits in the Hubitat forum so this pull request should be familiar. Hope you find it useful.

Awesome - glad I could contribute to this awesome integration.
Get Outlook for iOShttps://aka.ms/o0ukef

From: rvrolyk @.>
Sent: Tuesday, July 9, 2024 12:34:55 PM
To: rvrolyk/SleepNumberController @.>
Cc: ken kenw.com @.>; Author @.>
Subject: Re: [rvrolyk/SleepNumberController] Added sleepSensor attribute and wider range for dimmer settings (PR #19)
@rvrolyk approved this pull request. looks good, thanks for the updates! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. Mess
External<EMAIL_ADDRESS>Report This Emailhttps://protection.inkyphishfence.com/report?id=bmV0b3JnZnQ3NTMzODA4L2tlbkBrZW53LmNvbS9jMzdhZGE1M2E1YzM2YzBkYTE5ODgyODdlNWIxYzM3YS8xNzIwNTUzNzAxLjMz#key=dbde0e1f9456988b7b187853db2e6fb2  FAQhttps://www.godaddy.com/help/report-email-with-advanced-email-security-40813  GoDaddy Advanced Email Security, Powered by INKYhttps://www.inky.com/protection-by-inky
@rvrolyk approved this pull request.
looks good, thanks for the updates!
—
Reply to this email directly, view it on GitHubhttps://shared.outlook.inky.com/link?domain=github.com&t=h.eJxNjsEOwiAQRH_F4FWlsCLoycS7F7-A0lVJsVS6tDHGf1e86GGyyczk7TxZToHtZuxK1A87zi-errleuXjjaUwxPFp-Coj9Md9qTIfY0ccMmHifQ-BiOy834T3jQAlHj9NSio2WIKRes8WMtYXeIcV0OZNWAKYyvMVu_9H0_eNA28YqsMrBxlWNFVtjpNGoalEyLrSslAJdiRVAYeKXGcmfvbPkYzfsf7tLoSmFP-v1BhQ3SfQ.MEQCIEEscOVm8Vc5ZrsNZgpg_1xpiQLbxO3prRXomBkuXeCkAiAPGSyd7El2c4MJvtQqYGsvM_mIHvAkpE1vyS7dCCV1mw, or unsubscribehttps://shared.outlook.inky.com/link?domain=github.com&t=h.eJxNUMtugzAQ_JWIcxsDG8c0p1AohPJSIBiHGxgSUFqowKiHqv9enEuz0milndFoZn-UefxQdiulFeJr2iF07UQ7V2s-fKJ-EN2l46Xohn5Ccz_N1cTHrmqey1m0yLR85jqxp7sZAU_fhN75nQWnIjhCRExqRU4abk05r37M8izy6cHT7TSkx9xjEIR0A-fMplGSO29FkMQ0ZS62Fh7ctAjYISxsK0qY6xUnK1z2UXlaKTcZtm_EMF4vgmAAQzXQren3C77vsTmQsi4xlJjDlqt1qb0Yhm6QBlea5JBGdBVjIKq2BpCezd3zse3-_w1SUEvBw-n3D-5wX5w.MEYCIQCz-sthBzd8lR1yXMW2Fd4UXqrMfGySZFzAnx5iQ-F_gwIhAJFh4qGi4BP4QhH5TdB2anT-pGcIip5M3bn0B-tkwXtu.
You are receiving this because you authored the thread.Message ID: @.***>


Dummy branch for testing: Prl 6689/enable awp supporting documents for citizens

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRL-6689
Change description
Have changed supporting documents to appear in the other documents section for view all documents.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Closing this dummy PR as testing is completed


Transaction view

Single transaction view, with full details ala etherescan

@martriay Are you looking for the app to route to a new page or to use a modal similar to the inspect modal, and data wise is it just reflecting etherscan-esque details?
And what triggers the transition, clicking the inspect button or the row itself?

I'm thinking of a modal, yes. Etherscan-esque details are exactly what I have in mind. Row or inspect button are either fine, what do you think will make a better UX?
Today, the assets column of the block view is not accurate since it only shows the first occurrence of an asset but that's not complete, most transactions are much more complex and involves many different actions (approvals, swaps, transfers). The idea would be to display all of those and not just the first ones.
Once this is done, the asset column of the block view can be refactored to serve as a better summary of the tx.


Publishing invalid or incomplete data causes problems to the processing pipeline

The node publishes scan data even when grabScanData() returns  RESULT_OPERATION_FAIL in these lines.
This becomes to an issue to other nodes in processing pipeline using this scan data. One of the case is when laserscan_to_pointcloud will crash if scan data of data size = 1 is published.
As declared here:
if(!scan_in.ranges.empty()) end_time += ros::Duration().fromSec( (scan_in.ranges.size()-1) *    scan_in.time_increment);

If node_count = 1, the angle_increment and time_increment fields of scan data will be 'inf' causing crash with 'std::exception' at above line.
A better and safer way will be to publish ONLY if the result is successful from grabScanData() and further check is the size of data is 360 before publishing.
I will put up a PR for this.

FYI @stonier

PR #27 for this issue.

PR #27 handles it at the ros node wrapper level because that is where @naveedhd is working, however I am wondering if other options are better (and would require input/development from the robopeak engineers):

handle it at the sdk level
find the root cause and if it is a bug, fix it (wherever it is - sdk/firmware)

Just looking at the 1.5.4 commit, I wonder if this line is fixing the same problem.

@naveedhd  we have checked it. As  Informational Distance Measurements ,publish inf message is enable.
There is no need  Only publish 360 data.  the count according with grabScanData .
We should publish message to keep the scan publish frequent even if ascendScanData return RESULT_OPERATION_FAIL .
I will close the PR at first, If you have any question and comment it, i will reopen it.

@naveedhd please verify that with the commit @stonier pointed out, our problem is resolved as well. Otherwise we need to come up with a new solution.

@bit-pirate @stonier the line pointed out does not address the data size. The other way round would be check data size at the subscribing nodes.

@kintzhao can a scan of size 1 be consider valid and is it a realistic use case?
If not I like to ensure the driver is not sending out such messages.
If it is, then we need to create a PR to modify that laser geometry plugin to handle scans of size 1 (start time == end time).

+1 to bit-pirate 's comment.
@kintzhao It rather seems to me here that the driver is publishing surprising data that more often than not will cause problems in user's software. This requires uses to spend time debugging and then write code to correct the problem. None of which is useful time to anybody. Now, there are potentially hundreds of users and just one driver....some small corrections here could save alot of effort.
There are also other ways to inform users of things like frequency - e.g. diagnostics.
And finally, there is always the sdk underneath for a very small minority of users who for some esoteric reason, decide that they absolutely have to deal with size 1 data and the like.

bump
@kintzhao how can we move forward on this? This is a significant issue for us. I took us a while to hunt this down, during which we could not use our robot with the RPLIDAR reliably.

@bit-pirate  "can a scan of size 1 be consider valid and is it a realistic use case?"
What your mean:
the size 1 is only publish one range ,
publish not one range and only one value is valid(>min and <max) other are inf or -inf .
I can't reproduce the case of only publish one range in /scan message. which scene and statue you can meet . when we obscure the laser around a circle, it will publish all inf message, and we consider it is fine for other application.
can you give me  echo the message  /scan.

@kintzhao on our end @naveedhd was investigating this in depth.
@naveedhd is there data you can share with @kintzhao ? Do you know how he could reproduce the issue we had?

@kintzhao the size of range is 1 NOT one valid value.
Previously we were printing on log when range size != 360 and from there I have this:
[ WARN] [1461155288.335636631]: RPLidar : Node count is not equal to 360 [ WARN] [1461155288.335677183]: Node Count: 1
I will try to record a bag with ranges size less than 360.
For reproducing, it also depends on the specific RPLidar being used as my assumption is older ones tend to produce more errors.

But i still can not receive  your data bag.


fix instantiate! for dynamic checks, and add handling of instantiate!…

… for static type checking.

Two nits:

In changes file, "incicating" misspelling
In wrap.rb, can you get rid of @__rdl_inst?


timoni ls / list doesn't show instances when not explicitly specifying a namespace or all namespaces

Hey,
I have an issue with the timoni list command. It should show me all the installed instances in the current namespace but the list is empty except when I explicitly use the -A or -n test flag.
Steps to reproduce
kubectl create namespace test
kubectl config set-context --current --namespace=test
timoni -n test apply podinfo oci://ghcr.io/stefanprodan/modules/podinfo --version latest
timoni list

Expected output
NAME   	MODULE                                    	VERSION	LAST APPLIED
podinfo	oci://ghcr.io/stefanprodan/modules/podinfo	6.3.4  	2023-03-31T13:37:18Z

Actual output
NAME	MODULE	VERSION	LAST APPLIED

Additional info
Using the -n test flag explicitly or the -A flag works but I thought it should also work without it when I'm on the right namespace already. Is that the intended behavior or a bug?

This is the intended behaviour, as the --namespace flag is decoupled from the context. But I realise it may not be the best thing, following the kubectl behaviour would be better. This is not specific to list all commands behave the same, can you confirm that this please?

I tested with delete and it's the same behavior. It's nothing overly dramatic but I'm used to switch the namespace quite often with kubens so I noticed this thing quite early ;)

I tested with delete and it's the same behavior. It's nothing overly dramatic but I'm used to switch the namespace quite often with kubens so I noticed this thing quite early ;)


Misleading license claim in footer

The docs built by https://github.com/LilithHafner/Chairmarks.jl/pull/10 (specifically commit https://github.com/LilithHafner/Chairmarks.jl/pull/10/commits/b12a6c88169e268d1b52584545d6bf40a36662df) include the footer "© Copyright 2024. Released under the MIT License." despite the content for the docs being released under GPL-3 (and not MIT) and the documentation building commands not requesting an MIT license footer.
I would prefer in order of utility:

Auto-detect license file and contents and say "Released under [License abbr.](link to license file)"
Auto-detect license file and say "Released under [license](link to license file)"
Say nothing (what documenter.jl does)
Introduce a license the user did not ask for (current)

The root of this is in following the "copy the .vitepress folder" instructions. Perhaps a good solution would be to include a template folder that does not include non-generic content (e.g. also does not prepopulate the navbar with the pages in this repo's documentation)


Azure Cache Redis is not having (is empty of) data sometimes

Describe the bug
Missing all data in Redis

Impact

Pipeline is broke.
Local functions are broke.

It seems that Redis gets patched every Wed. at 5am

I've created an Alert that monitors if Redis data deeps below 100Mb, it will send a Critical Alert (email me, boris and Neelima - previously set)

It seems we can attach an event to Azure being patched. but our functions (schedule trigger) are not compatible

There's also ways of automating Export/Import data from/to Redis:
https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-how-to-import-export-data

TO use our Loader functions, we need to add either an EventGrid or HTTP trigger:
Use Event Grid trigger. Specify Azure Function as the endpoint type. Then, specify the function app and the function that will handle events.
Use HTTP trigger. Specify Web Hook as the endpoint type. Then, specify the URL for the function that will handle events.
(from https://learn.microsoft.com/en-us/azure/event-grid/handler-functions)

Done

Email alert when available space on Redis drops below 100Mb (on ~1GB total)

Resolutions for PROD

Option A: Upgrade to Redis Premium so we have a "no downtime" SLA (99.99...%)
Option B: Scheduled downtown. Turn off the pipeline before Redis outage; turn it back on after patch

We identified that we can also trigger a HTTP function from the Alert itself. so when the alert fires (Redis mem < 100MB), the Function can run
Alert Rules -> Action groups (potential solution) to call function app to refill Redis.
Once this is implemented and tested, we can ask Boris to Terraform this solution

Ticket #526 created to handle the resolution

The following is for OPTION 2 above, which as this time is the recommended solution, below details:
TLDR: Change Redis to Premium P1, use 2 instances and share: dev + tst and prod + stg
Redis  - Azure Cache Redis

solution 1: Basic C1 (currently using)
solution 2: Premium P1

Cache Name
Cache Size
Network performance
Number of Client Connections
Price
1 YR Reserved
3 YR Reserved

C1
1 GB
Low
1,000
$0.055/hour

P1
6 GB
Moderate
7,500
$0.554/hour
$0.355/hour ~36% savings
$0.250/hour ~55% savings

Basic C1

The default maintenance window is 5 hours
Single node cache is a single node cache which is ideal for development/test and non-critical workloads
There's no SLA on basic tier

This Basic C1 would require custom coded solution to accomplish pesistence, meaning added initial cost and life cycle cost.
Multiple DEX Projects (such as HL7, etc) sharing Basic C1 is not feasible now due to now multiple custom coded solutions, coordination of those, and see above.
Premium

Premium tier includes all the standard-tier features and more, such as better performance over basic or standard-tier caches, bigger workloads, disaster recovery, and enhanced security

Persistence
Cluster
AVN azure virtual network
Multi-replica support

The Premium P1 is recommended for Prod., it could be shared between prod. and stg.
Hence a Premium P1 should be used for Dev. and Tst.

Dev. and Tst. could eventually switch back, once development is not active to Basic
Premium P1 could be 1-3 Yrs. reserved - this is a larger infra issue that should account other services for reservation and cost saving. (once dev. and full solutioning is more complete.)

Ref:
Azure cache redis pricing: https://azure.microsoft.com/en-us/pricing/details/cache/
Redis persistence: https://redis.io/docs/management/persistence/

@mscaldas2012  @boris-ning-usds - we are leaning strongly on switching to Az Redis Premium, would you please check that setting persistence on it is an easy check (or simple az process). please see above comment details on why the switch and we can discuss more details or questions if you have. Thanks


improvements to lexer + parser performance

Description
I noticed that parse times increase with query times more than I'd expect. I suspect that this has to do with the number of allocations happening during lexing/parsing as switching to jemalloc improved things ~15%. I'm not sure if it's something specific to this query or if any query of this size that sees the increase.
10 aliased fields
parser_peek_n           time:   [21.519 µs 21.535 µs 21.562 µs]
                        change: [-97.894% -97.891% -97.887%] (p = 0.00 < 0.05)
                        Performance has improved.

100 aliased fields
Gnuplot not found, using plotters backend
parser_peek_n           time:   [197.55 µs 197.71 µs 197.91 µs]
                        change: [+816.92% +818.31% +819.65%] (p = 0.00 < 0.05)
                        Performance has regressed.

1000 aliased fields
Gnuplot not found, using plotters backend
parser_peek_n           time:   [2.0601 ms 2.0618 ms 2.0636 ms]
                        change: [+940.25% +941.65% +943.08%] (p = 0.00 < 0.05)
                        Performance has regressed.

Steps to reproduce

Parse a large query see example

Expected result
Parse time for large queries should grow more slowly.
Actual result
Every 10x increase in number of selections increases parse times by > 800%.
Environment

Linux / Darwin
apollo-rs apollo-parser revision = HEAD

Interesting! This seems to be an issue specific to the particular Document you're benchmarking. We use apollo-rs on Documents that are MBs in size (as suppose to 57KB in the example you provided), and we are yet to observe such a large spike in parse times.
I'll need to investigate this a bit more.

It looks like this issue is common for graphql parsers gqlparser, async-graphql-parser, and graphql-parser. While I wasn't able to make the scaling of these queries better overall, reducing the number of allocations in the lexer does improve the performance overall and seems to make it the fastest parsing option of the bunch.
Maybe this could go further in certain cases with https://github.com/rust-analyzer/rowan/pull/119. I more or less hit a wall with all CPU time dedicated to parsing the selection set fields.

Here are some benchmarks with the available Rust parsers: https://github.com/allancalix/graphql-benchmark.
Baseline small query
async_graphql_parser    time:   [7.5938 µs 7.6117 µs 7.6288 µs]
                        change: [-0.5916% -0.1561% +0.2545%] (p = 0.46 > 0.05)
                        No change in performance detected.
Found 10 outliers among 100 measurements (10.00%)
  6 (6.00%) low severe
  3 (3.00%) low mild
  1 (1.00%) high mild

apollo_graphql_parser   time:   [6.7100 µs 6.7274 µs 6.7436 µs]
                        change: [-1.8937% -1.5113% -1.1105%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 4 outliers among 100 measurements (4.00%)
  3 (3.00%) low mild
  1 (1.00%) high mild

apollo_fork_graphql_parser
                        time:   [4.7675 µs 4.7785 µs 4.7904 µs]
                        change: [-2.1926% -1.7055% -1.2349%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 5 outliers among 100 measurements (5.00%)
  2 (2.00%) low mild
  2 (2.00%) high mild
  1 (1.00%) high severe

graphql_parser          time:   [5.6228 µs 5.6353 µs 5.6472 µs]
                        change: [-0.3519% +0.0893% +0.6192%] (p = 0.70 > 0.05)
                        No change in performance detected.
Found 10 outliers among 100 measurements (10.00%)
  1 (1.00%) low severe
  6 (6.00%) low mild
  1 (1.00%) high mild
  2 (2.00%) high severe

Pathological query
async_graphql_parser #2 time:   [2.3517 ms 2.3572 ms 2.3625 ms]
                        change: [+1.3489% +1.6262% +1.9296%] (p = 0.00 < 0.05)
                        Performance has regressed.

apollo_graphql_parser #2
                        time:   [3.0019 ms 3.0110 ms 3.0203 ms]
                        change: [+1.9770% +2.3294% +2.6782%] (p = 0.00 < 0.05)
                        Performance has regressed.

apollo_fork_graphql_parser #2
                        time:   [1.9258 ms 1.9290 ms 1.9322 ms]
                        change: [+0.6851% +0.9991% +1.3283%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 7 outliers among 100 measurements (7.00%)
  2 (2.00%) low mild
  3 (3.00%) high mild
  2 (2.00%) high severe

graphql_parser #2       time:   [2.2415 ms 2.2494 ms 2.2584 ms]
                        change: [+0.1431% +0.5157% +0.9513%] (p = 0.01 < 0.05)
                        Change within noise threshold.
Found 2 outliers among 100 measurements (2.00%)
  1 (1.00%) low mild
  1 (1.00%) high severe

whoaaa thank you so much for putting all this work in for benchmarking @allancalix! i really appreciate it!
There are definitely a whole bunch of improvements we can make when it comes to parser's performance. The work you did in #294 is one way to go about it, there is also an idea have a streaming interface (like in #115) for the lexer, or simply have the parser consume lexer's tokens without having that extra alloc at all.
I realise I won't have enough time to think of a direction for us to take this until after GraphQL Summit happening in the first week of October. This goes in my backlog for October though.

I've actually done both of these things to solve some bottlenecks for my use case. It's fairly rough currently, but once I get a chance to clean it up I'd be happy to upstream the changes if you'd be willing to review the PR. I included the excellent work done in https://github.com/apollographql/apollo-rs/pull/115 in additional to removing all the allocations from the Token types themselves.
Can see the direction of the changes here: https://github.com/apollographql/apollo-rs/compare/main...allancalix:apollo-rs:finite-state-lexer.


use 'npm run build' for installation if npm is selected, update gem bundler…

… website

We already show "npm run build" when npm is selected. I think this PR conflicted with @gabro's work in #3598


Replace Content-Fragment with other fragments

in the example project, I can see BirdGridFragment and ColorFragment are showing different pages of same type. How to add different fragments either replacing Content-Fragment (BirdGridFragment,ColorFragment etc) or including a fragment ?
Simply I just want to include different fragments depending upon the selected list item value in MenuFragment. For example, I have 3 MenuFrament List Items : Home, Message, Profile
I just want to load the Message Fragment upon clicking Message List Item and Profile Fragment upon Profile List Item. How to achieve this ?

Hey , how did you solved it ?

LOL. It's been more than 4 years and you are supposed to use NavigationDrawer now.

yeah man that i know , but one of my suggested me to use this library. can we get connected i have a very little doubt which we can  discuss if you have time .


(game management) Created basic edit view and create view for Games

A basic edit view and create view for Games has been implemented. If we update the Game entity with more attributes, we will have to update these views to correspond with those changes.

Resolved merge conflicts with dev branch

Resolved merge conflict

I added the requested change to the edit page, so that once the edit is made, the user is redirected to the detail page. The detail page also contains a link to edit the game.

A basic edit view and create view have been added to the Games model. These views will most likely need to updated when we update the Game model with more relevant attributes in issue #92.
Distribution of work:
Patrick: coding the edit and create views
Will: advice and feedback
Ryan: advice and feedback

Issue Score: Excellent
Comments:
Great job! This is a very good example of a straightforward addition to the repo handled through an issue and PR with good feedback and a closing statement.
Keep this up and keep moving forward!


The following plugins are incompatible with the current IDE build

Prerequisites

[X] Plugin is in the latest version
[ ] Issue was not reported yet
[ ] Stack trace (if provided) contains mobi.hsz.idea.gitignore package name

Description
Plugin Error
Problems found loading plugins:
The following plugins are incompatible with the current IDE build: .ignore
installing the latest version of PHPStorm 2018.1.1
Steps to Reproduce

Update PHPStorm to latest version (2018.1.1)

Actual behavior:
IDE error message that the plugin is not compatible with IDE version
Reproduces how often:
100%
Versions
Plugin:
2.5.0

IDE:
2018.1.1

Plugin Error
			Problems found loading plugins:
			The following plugins are incompatible with the current IDE build: .ignore

Traceback
2018-04-09 14:25:45,249 [   3031]   INFO - llij.ide.plugins.PluginManager - Plugin '.ignore' can't be loaded because: This plugin version was marked as incompatible

yes, i have the same peoblem, waiting for fix it.

https://github.com/hsz/idea-gitignore/issues/527#issuecomment-379742978
https://youtrack.jetbrains.com/issue/IDEA-189189

same problem

I have the same issue, although not in the PhpStorm but in IntelliJ IDEA 2018.1.1 (Community Edition)
Build #IC-181.4445.78, built on April 9, 2018
JRE: 1.8.0_152-release-1136-b27 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

Maxim Mossienko  10 Apr 2018 11:34
We disabled existing versions of .ignore plugin in IDE updates.
https://github.com/hsz/idea-gitignore/issues/527#issuecomment-379742978

Same problem...

Plugin Error
Problems found loading plugins:
The following plugins are incompatible with the current IDE build: .ignore

Same issue here on IntelliJ Ultimate latest stable build and plugin version 2.5.0.

PhpStorm 2018.1.1
Build #PS-181.4445.72, built on April 9, 2018
Subscription is active until March 26, 2019
JRE: 1.8.0_152-release-1136-b27 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.4.0-62-generic

The same for me
IntelliJ IDEA 2018.1.1 (Ultimate Edition)
Build #IU-181.4445.78, built on April 10, 2018
JRE: 1.8.0_152-release-1136-b27 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.4

+1 for me too
PhpStorm 2018.1.1
Build #PS-181.4445.72, built on April 9, 2018
JRE: 1.8.0_152-release-1136-b27 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

come on guys -- this is getting pretty boring, all these same/plus1s.
It doesn't help anything, and if you pay attention, you'll find this is for a reason being worked,  as with all the other times for this plugin.

It's broken and not the first or second time after an update. A lot of people rely on certain behaviour of this plugin and it's an annoyance if it randomly stops working. I'd fix it myself, but I don't know how.
I think it's a must have feature for jetbrains to include in their platform, maybe that would help stability the of this plugin?

@iltar
As already mentioned above (https://github.com/hsz/idea-gitignore/issues/527#issuecomment-379742978), JB has disabled v2.5.0 because it has conflicts with new release of their IDEs.
FIx is ready (#527 issue, #531 PR), I'm waiting for the confirmation/code review/whatever from @nicity to avoid releasing fix and getting reverted again.
After releasing it'll take another couple days for accepting the update by some approval team.
I can't do more about that, sorry.

I can't do more about that, sorry.

@hsz, you don't have to be sorry, you're not being paid to do this, are you? :+1:
I don't think anyone is explicitly at fault here, but it's a shame that it keeps breaking. This plugin is really useful for my development workflow in PhpStorm and I instantly notice it when it does not work.

@iltar I'm not paid for that, just the occasional donations via PayPal. ;-)
It's great to hear that you consider this plugin useful!
Ok, v2.6.0 has been finished and released to the JB repository. Now we have to wait for their move.
Until then, it's available for manual installation in Releases tab
**Big thanks to @nicity for the support! 👏 **

same for me :-/

same for me


Using quartz with a vault in iCloud

Hello. This is not a feature request so please move as you need. I have a question that I do not see a response in the FAQ for. My obsidian vault is stored in iCloud because I use the iOS mobile app to write notes as well as my MacBook. this works out very well for me since I go walking, writing, etc. How exactly can I use quartz with the vault stored in iCloud? I do not want to lose the ability to edit files on the go on my iPhone. I am guessing I could publish a limited or targeted set of notes on quartz and not the whole vault because I see how that can be done. How exactly can I use the vault location on iCloud? I guess I could purchase obsidian sync and place the vault on my MacBook? Is there not a free solution to maintain the vault on iCloud and still use quartz and publish to GitHub pages?

You could have the same setup you do now but just update Quartz manually whenever you are at your laptop. You can configure directories to ignore: https://quartz.jzhao.xyz/notes/ignore-notes
Hopefully this resolves your question! Feel free to reopen if you are looking for something else


Edit view command

Current UI:

Codecov Report

Merging #108 (9b7f1e0) into master (a2487d0) will decrease coverage by 0.90%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #108      +/-   ##
============================================
- Coverage     69.36%   68.45%   -0.91%
  Complexity      582      582
============================================
  Files            98      100       +2
  Lines          2040     2067      +27
  Branches        249      251       +2
============================================
  Hits           1415     1415
- Misses          538      565      +27
  Partials         87       87

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/PersonCard.java
0.00% <ø> (ø)

src/main/java/seedu/address/ui/PersonViewCard.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/ui/PersonViewPanel.java
0.00% <0.00%> (ø)

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 a2487d0...9b7f1e0. Read the comment docs.

Current UI:


ENH extend p-values of anderson_ksamp in scipy.stats

added critical values for significance levels 0.1% and 0.5%.
Derivation:
https://gist.github.com/chrisb83/5b94ef565b9541a1d53d39dcac5e536e
I did not touch the critical values from the original paper of Scholz / Stephens. p-values might differ slightly compared to the current implementation as polyfit will give slightly different results due to the newly added values.

Related to issue #8536

More compact code to reproduce the results for reference:
from scipy import stats
import numpy as np

sig = np.array([0.001, 0.005, 0.01, 0.025, 0.05, 0.1, 0.25])
sample_sizes = [2, 3, 4, 5, 7, 9, 11]
np.random.seed(92346)

def sim_A2k(k, size, sum_to):
    """
    Compute A2k equation 5 of Scholz & Stephens.

    Parameters
    ----------
    k : int
        Number of samples.
    size : int
        number of A2k that is simulated
    sum_to : int
        Summation limit to approximate infinite series.

    Returns
    -------
    A2N : array
        Random samples of A2k, number given by size.
    """
    weights = 1. / (np.arange(1, sum_to + 1)*(1 + np.arange(1, sum_to + 1)))

    res = np.zeros(size)
    for i in range(size):
        res[i] = np.sum(stats.chi2.rvs(k, size=sum_to) * weights)

    return res

perc = {}
n_rep = 4
res = np.zeros((n_rep, len(sig)))
sigma2 = 2. * (np.pi**2 - 9.) / 3.

for k in sample_sizes:
    for l in range(n_rep):
        a2k = sim_A2k(k - 1, 10**6, sum_to=2500)
        a2k_s = (a2k - (k - 1)) / np.sqrt(sigma2 * (k - 1))
        res[l, :] = np.percentile(a2k_s, 100 * (1. - sig))
    perc[k] = res.copy()

perc_avg = {}
for k in sample_sizes:
    perc_avg[k] = np.mean(perc[k], axis=0)

# for k=inf, critical levels are based on normal distribution
resinf = stats.norm.ppf(1-sig)
perc_avg[np.inf] = resinf
sample_sizes.append(np.inf)

# now fit p(k) = b0 + b1 / sqrt(k-1) + b2 / (k-1) using least squares
P = np.zeros((len(sample_sizes), len(sig)))
j = 0
for k in sample_sizes:
    P[j, :] = perc_avg[k]
    j += 1

P = np.fliplr(P)
m = np.array(sample_sizes) - 1
D = np.vstack([
    np.ones_like(m),
    1. / np.sqrt(m),
    1. / np.array(m)]).T

B_est = np.linalg.lstsq(D, P, rcond=None)[0]
# new coefficients
B_est[:, -2:]

LGTM, very nice. Thanks @chrisb83


feat：Add the time type drop-down box to the Job list

Description
Add the time type drop-down box to the Job list
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

@wzh425 PTAL