CPU overprovisioning factor doesn't seem to work

ISSUE TYPE

Other

COMPONENT NAME

CPU overprovisioning

CLOUDSTACK VERSION

<IP_ADDRESS>

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

Setting the overprovisioning factor on a cluster does not seem to work as expected.
STEPS TO REPRODUCE

Set the overprovisioning factor on the cluster to 1
Try to create vms totaling a higher number of cpus than the actual number the host has

EXPECTED RESULTS

Cloudstack should not let me create new vms with offerings that exceed the number of actual cpus.

ACTUAL RESULTS

I could create a new vm without any issues.

If we follow the documentation, setting a value of 1 to the cpu overprovisioning factor of the cluster should only let me create vms totaling the actual ammount of cpus of the host, not more. So if the host has 64 cpus (hyperthreading enabled), I shouldn't be able to create, let's say, 2 vms with 40 cpus each, yet I can, and the dashboard reflects this, showing more than 100% cpus allocated. I don't know if this is expected behavior or I'm supposed to do something more than just setting that value, what I am trying to do is limit the availability of the host cpus to the actual, real, number.

@tdtmusic2
If you have a a single host with 64 vCPUs of 2000 MHz clock speed and you set CPU over the provisioning value of 1 at the cluster, cloudstack will calculate the total CPU capacity as 64 * 2000 * 1 = 128000. Cloudstack will allow you to deploy instances as long as their vCPU * CPU MHZz value in the offering is less than the total (remaining capacity )value above.


Log git branch and commit

Description
This PR uses the approach described at https://blog.alexellis.io/inject-build-time-vars-golang/ to inject the current git branch and git commit as build variables.  These variables are printed during initialization.  They are added to the local logger and sent to honeycomb.
For example, you could now search cloudwatch logs with { $.git-branch = "honeycomb_git_hash" }.

[ ] tested on experimental

I figured out how to fix gin.  Here's the code diff:
diff --git a/Makefile b/Makefile
index 416cce36..4d2bd395 100644
--- a/Makefile
+++ b/Makefile
@@ -103,7 +103,7 @@ server_run_default: server_deps server_generate db_dev_run
                --bin /bin/webserver \
                --port 8080 --appPort 8081 \
                --excludeDir vendor --excludeDir node_modules \
-               -i --buildArgs "-i"
+               -i --buildArgs "-i -ldflags=\"-X main.gitBranch=$(shell git branch | grep \* | cut -d ' ' -f2) -X main.gitCommit=$(shell git rev-list -1 HEAD)\""

 server_run_debug:
        INTERFACE=localhost DEBUG_LOGGING=true \

Let's also add this so we can do some other testing with build-time vars in the future.


bug(iOS): App freezes momentarily when user taps chat

Issue:

When the user taps on the chat button on an iOS device it takes fairly long to load the page and when it is loading user cant tap anything else. Ive always noticed the option to paste text will appear when the user taps the chat button

This bug is specific to iOS it does not happen on Android devices
STR:

On an iOS device simply go to any page (except chats) and then go back to the chat page

Screen recording:
https://github.com/user-attachments/assets/9d1e205a-3098-4226-9858-08b5bf91252b

btw im getting this on mac too. havent tried other os though


RFC: retriever: implement two-factor and SteamGuard authentication

node-dota2 actually has support for Steam Guard auth already, although I'm not sure if it handles 2FA.  You might want to make your pull request there instead so more users can benefit from the change.  That implementation stores the data in a local filesystem file instead of Redis. @Crazy-Duck

yes, node-dota2 does indeed already support 2FA, because node-steam supports it :)

Yeah, 2FA and SteamGuard auth are already in node-steam, but sentry file management and of course the actual passing of the authentication token need to be handled separately.
Since redis is not accessible in the retriever in production, what alternatives are there? Would it be acceptable to have a separate redis instance?
Also, is the whole /auth thing acceptable? I guess it would have problems if the retriever service gets scaled, but I don't know exactly what production looks like.

You can store the data in a filesystem file, maybe, like the node-dota2 examples.  That won't work for multiple accounts though, unless node-dota2 is changed to write the sha_sentryfile to one file per account, or extend the format to support multiple accounts.
The node-dota2 examples rely on passing it through a config option.  Maybe that'd work for this as well?
https://github.com/Arcana/node-dota2/blob/staging/examples/example.js#L182

Saving the sentry to the file system wouldn't work if you scale the service (unless maybe playing with docker volumes?)
Passing auth codes in the config file IMHO is not a great option: you'd have to start the service, collect all the auth codes in the config file and restart the service. Plus, you'd have to do that every time a client disconnects and needs to re-auth for whatever reason. It looks nicer to me to allow authenticating the clients while the service is up, what do you think about that?

It works if you only run one instance per VM. That's the case in production.  However, filesystem files do not persist between instance restarts since they can get run on a pool of VMs.
Auth endpoint sounds OK to me.
This isn't relevant for production since our accounts don't use steam guard/2FA.  If you put the redis require under a feature switch/config option so it doesn't run in production, then this is OK if you need to use Steam Guard/2FA for your own instance.

Okay, I'll work on it as soon as I have some spare time.
Thanks for your feedback!

I have added an ENABLE_RETRIEVER_ADVANCED_AUTH entry in the config file (disabled by default) and made all the new code conditional on that.
Let me know if I need to change anything else!

LGTM
I still think there's a decent case to be made for moving some of this functionality to the node-dota2 library.  The choice of storage backend (redis or file) should be left up to the user, but the internals of computing the SHA hash etc should be library code.


[a11y] matchesSemantics is missing fields on SemanticsNode, such as transform

Ideally, matchesSemantics has every field on SemanticsNode

cc @pdblasi-google


ToolbarButton button variant not changeable

Issue here is that I have specified a default button variant in MUI Theme ('outlined'). This then changes the button type in the calendar picker which makes them look more like buttons and not text.
Environment

Tech
Version

@material-ui/pickers
3.0.0

material-ui
4.0.1

React
16.8.6

Browser
Chrome

Peer library
moment

Steps to reproduce

Set default props in material-ui theme
const theme = createMuiTheme({  props: {    MuiButton: {      variant: 'outlined'    }  };
View calendar.

Expected behavior
I expect either the button to pass variant="text" (always) as a prop, or allow us to pass toolbarButtonProps={ { variant: 'text' } } to override the default mui theme, showing the text version of a button. Although, the second option here could become cumbersome if we were to pass props for each individual button in the toolbar. IE showTodayButtonProps, clearButtonProps.
Actual behavior
Button gets the 'outlined' variant, and looks silly. This affects the toolbar buttons at the top of the calendar (year/date/month), as well as the buttons on the bottom of the calendar (show today, clear, OK etc.).
Thank you very much for your consideration, this project is amazing!

Thank you!

This is still an issue in MUI v.5. Should I create a separate issue for this?


Updated to fix build errors when using go-sdl2 v0.3.0 and go v1.13.5

Since the last update go-sdl2 has changed its api slightly and so I fix the errors to allow for a successful build

Thanks for this!


Integration test for GL+GT pipeline based on CDS

Need to have fixed input parses (using only fully parsed sentences) corpus run with LG 5.5.1, with GT testing with same MWC that GL is using for learning.

MSL = no limit, MWC = 1, clustering = ALE 400
MSL = no limit, MWC = 1, clustering = ILE 400
MSL = 3, MWC = 1, clustering = ALE 400
MSL = 3, MWC = 1, clustering = ILE 400
MSL = no limit, MWC = 3, clustering = ALE 400
MSL = no limit, MWC = 3, clustering = ILE 400
Verified on the expected numbers for PA/F1, given
https://docs.google.com/spreadsheets/d/1TPbtGrqZ7saUHhOIi5yYmQ9c-cvVlAGqY14ATMPVCq4/edit#gid=2053587208
@OlegBaskov  - please provide configuration data for @alexei-gl

When done, need to regenerate all baselines for GC with MWC = 1, 2, 6, 11, 21, 31

It seems 400 clusters is invalid setting for GL with CDS corpus. Although test is ready to be uploaded to the repo, still need to make a decission on the number of clusters to be used. The test works fine with 50 clusters setting. Ready to make PR if that is ok.

We need to
A) change the test to
MSL = no limit, MWC = 1, clustering = ALE 50
MSL = no limit, MWC = 1, clustering = ILE 50
MSL = 3, MWC = 1, clustering = ALE 50
MSL = 3, MWC = 1, clustering = ILE 50
MSL = no limit, MWC = 3, clustering = ALE 50
MSL = no limit, MWC = 3, clustering = ILE 50
B) Add comparison of dict files in addition to comparison of parses
C) Make sure that both dicts and parses are the same under the same environment on different places

Done. PR #221.


Sensors not updating, "sensor_status" not anywhere

I use CPI, which runs through Alarm.com, and most everything is good except for two things:

No doors are ever sensed "open"
No option to close garage door, which I'm sure is related to it always being considered closed

I did some digging and found that I should be looking at "sensor_state" in the panel attributes...but there's no such thing. This is all I have:
supported_features: 7 code_arm_required: true mac_address: '' desired_state: Disarmed uncleared_issues: false friendly_name: Panel

Hey. See #196 for updates on the garage door issue. As for doors not being sensed open -- I can't replicate the issue on my end. Can you provide debug data for one of your doors in both the open and closed states? Thanks!


Subroutine to determine the ownership of a droplet

Currently the ownership of a droplet by a MPI rank is checked by multiple "if" statements at several locations and they may not be necessarily consistent. Need to have a subroutine to check them consistently and put it at a fixed location for repeated usages.

Fixed via #131 .


Documentation for hasThreatMatch operator

PLEASE READ
Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run yarn install. This does not apply to direct page edits.

[x] Yes, I've run yarn install
[ ] No, does not apply to me

Purpose of this pull request
This pull request adds documentation needed for the new hasThreatMatch operator needed for the Threat Intel Project 6. It adds this section:
https://help.sumologic.com/docs/cse/rules/cse-rules-syntax/#hasthreatmatch

Issue: Asana ticket "Document Threat Intel Project 6"
Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions, .clabot
[ ] Update Content - Revisions, updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Closing this PR to replace it with #3368.


pulsar-client (Java) JsonSchema does not support deserializing java.time.Instant

Describe the bug
I am sending objects with a timestamp of type Instant. When using a JsonSchema for my defined message object, it fails to deserialize the Instant field.
This is because the internal ObjectMapper is not configured to deserialize using mapper.registerModule(new JavaTimeModule());
To Reproduce
Steps to reproduce the behavior:

Create a consumer using JsonSchema with a class that has a member of type Instant
Create a producer with the same JsonSchema
Send a message with producer
When the consumer calls message.getValue()
Then see

org.apache.pulsar.client.api.SchemaSerializationException: org.apache.pulsar.shade.com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Cannot construct instance of `java.time.Instant` (no Creators, like default construct, exist): no String-argument constructor/factory method to deserialize from String value ('2020-10-06T14:35:40.089034-06:00')
 at [Source: (byte[])\"{\"timestamp\": \"2020-10-06T14:35:40.089034-06:00\"}\"; line: 1, column: 270] (through reference chain: <redacted>[\"timestamp\"])
 org.apache.pulsar.client.impl.schema.reader.JacksonJsonReader.read(JacksonJsonReader.java:49)

Expected behavior
The object should deserialize without error.
Workaround
Use a String and deserialize yourself.
Proposed Fix
Add mapper.registerModule(new JavaTimeModule()); inside JSONSchema initialization.
Desktop (please complete the following information):
N/A
Additional context
I am aware that there is an InstantSchema, that's not the use case I am seeking. This is an example of a JsonSchema with an object having a nested Instant field.
This seems like a common use case that someone would have encountered before, although I did not find references in any open issues. Apologies if I have missed some previous discussion.
I have a fix and am trying to test it. This actually exposed two other items I would explore making PRs/Issues for:
1: This also causes moving to DLQ to fail because something internal tries to deserialize when moving the message. The message is then retried indefinitely. My next step here would be to find or make an issue for this.
2. Adding Instant to the test's serialized object Foo breaks a lot of unrelated tests. I also noticed some expected/actual are swapped with ambiguous argument names in helper functions. My next step here would be make a new feature ticket and start working on a refactor PR to precede the fix for this ticket.
I would appreciate if anyone more familiar with the project can advise on if this plan sounds good, or what the best path would be.
Thanks!

@MaitreyaBuddha  This feature has already been implemented by #6842 which is included since 2.6.0+.
There's a Kotlin code example in https://github.com/apache/pulsar/issues/6528#issuecomment-701410483 about how to use it. I haven't tried it myself, but there's a note that it doesn't work with the shaded client and you should use pulsar-client-original dependency instead of pulsar-client.

Awesome, thanks for clearing that up @lhotari


Yahoo weather datasource is not working

The Yahoo web service changed and it's not working anymore.
https://developer.yahoo.com/weather/
The response is :
{  "error": {   "lang": "en-US",   "description": "No definition found for Table weather.bylocation"  } }

Weird, it's working again.

Sometimes when you overuse a free service they throttle your usage and
block you for a short period of time.
Wray Johnson
(m)<PHONE_NUMBER>
On Mar 17, 2016, at 5:06 AM, Guillaume<EMAIL_ADDRESS>wrote:
Weird, it's working again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/Freeboard/freeboard/issues/166#issuecomment-197775873


[CI] Retry headers check and threading tests in case of failure.

Summary
Retry headers check and threading tests in case of failure during CI.
Tests
Side Effects
Are there any side effects that we should be aware of?
No
Release notes
Checklist

[ ] Copyright holder: (fill in copyright holder information)
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[ ] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[ ] the code is written in idiomatic C++ and changes are documented in the doxygen

[ ] the new changes are tested

Hey @WardBrian the change for headers check is quite straightforward, just retry once.
About your earlier question:
The other thing that sometimes randomly fails is the thread tests sometimes don't build.
If this is due to some sort of runner incompatibility, will the retry pick up the same runner again?

The retry in it's simplest form seems to handle simple blocks, tho it seems to be possible to use it for a stage-wide failure and retry https://community.jenkins.io/t/how-to-retry-a-jenkins-pipeline-stage-with-an-agent-condition/3667/4
TL;DR; detecting agent issues and if that's the case, find a new agent and try again.
Now while that's possible I don't think it might be best to use in our case, let me explain.
We leverage Docker to ship our CI images with all the dependencies, so irrelevant of the agent we will always run the same thing. The only case where differences can occur is when the code is trying to read the kernel or some low-level CPU instructions (docker containers share the host kernel). Rember we had an issue at the beginning with Flatiron that an Intel CPU was not supporting some CPU instructions ? (or was it a GPU?)
Knowing this, I think it might be more simple and straightforward to detect on which host the threading tests fail and simply exclude it in an agent label conditional, thus always running on the valid one.
Could these threading failures occur because of two concurrent runs on the same host ? a develop building running at the same time with a PR build.
Because of the above train of thought I put it in a simple retry block for now, please let me know what do you think about this! Thanks!


Add a WatchStreamExt::modify shortcut

Would you like to work on this feature?
no
What problem are you trying to solve?
Minor ergonomics improvement for the streams api. Currently stream modification requires:
let stream = watcher(api, watcher::Config::default()).map_ok(|ev| {
    ev.modify(|pod| {
        pod.managed_fields_mut().clear();
        pod.annotations_mut().clear();
        pod.status = None;
    })
});

we could shortcut that ever so slightly:
let stream = watcher(api, watcher::Config::default()).modify(|pod| {
    pod.managed_fields_mut().clear();
    pod.annotations_mut().clear();
    pod.status = None;
});

Describe the solution you'd like
WatchStreamExt::modify that chains TryStreamExt::map_ok with watcher::Event::modify
Can be verified in examples/pod_reflector.rs.
Describe alternatives you've considered
writing out the full thing, not a big deal, but a nice user facing api simplification when for the streams api.
Documentation, Adoption, Migration Strategy
No response
Target crate for feature
kube-runtime

Yeah, nested maps tend to feel pretty awkward, especially when this is something that we want to encourage.


Location configuration file

Hi,
it's not a bug, i think it's only misleading.
In /etc/ exist an folder vaultwarden with no config file in it.
In /etc/default/ exist the vaultwarden config file.
So i think creating the vaultwarden directory is not necessary or change location of file from /etc/default/ to /etc/vaultwarden/.
And i think it is more clean to name it vaultwarden.env like it is writen in the file.
Thanks

Yeah, /etc/vaultwarden was there when the package still generated the backend token automatically. Removed since it now makes more sense for the user to be aware how the token is configured.
I offer now a symlink there, was the easiest solution.


Classes have state as object variables

A lot of classes, such as Plane and Aerodynamic_surface have object state as object variables, with functions updating those states, instead of returning it.
    def update_alpha(self, alpha_airplane):
        self.attack_angle = alpha_airplane + self.incidence

This is bad because one does not know what has happened to the object before it was received, and the state could mean anything (e.g.: the takeoff analysis was run, saving the final state of plane's alpha as 15 degrees, and now the stability analysis is being run. Should I use the 15 degrees for something?). The state has meaning only inside an analysis, and so should only be a functional get method.

Addressed in 2.0


There is no way to browse/restore/delete versions of media

Currently in Islandora 8, you can browse revisions of a node at node/{node_id}/revisions. The Media edit UI allows you to replace a media's file and choose to create a revision (that choice is enabled by default), but Drupal doesn't provide a way to browse all the versions of a media and restore one of them to be the current version (or to delete a revision). This functionality would replace the ability in Islandora 7.x to revert a datastream version.
There is an open issue for Drupal core about this, slated for inclusion in Drupal 8.7.
Related to meta issue #740.

If this will indeed be in 8.7, this timeline might be relevant:
https://groups.drupal.org/node/534785

Looks like the drupal issue, both for the generic revisions UI and the Media revisions issue, have been pushed to 8.8.x-dev. :(

Is this now a documentation task? What user functionality is missing?

The "Generic Revision UI" is still under development.
There exists a Media Revisions UI module; i have NOT used it. We could see if it solves the problem.

Possible use case to define target for this functionality?  "As a repository administrator, I want the option to version Islandora media types (including the media held in Fedora) and be able to revert versions via a (unified) UI"

https://www.drupal.org/project/media_revisions_ui might be sufficiently mature now, being marked "feature complete" on its project page?
As for use cases: #1930, #1933 and #1935 all somewhat approach this.


Error "Rejecting initial value"

When running:
Rscript base.r base --debug
or even in the full mode:
Rscript base.r base --full
I am getting the following error message:
Chain 2: Rejecting initial value:
Chain 2:   Error evaluating the log probability at the initial value.
Chain 2: Exception: neg_binomial_2_lpmf: Failures variable[53] is -6, but must be
 >= 0!  (in 'model266c65b51bc8_base' at line 87)

Chain 2:
Chain 2: Initialization between (-2, 2) failed after 100 attempts.
Chain 2:  Try specifying initial values, reducing ranges of constrained values, o
r reparameterizing the model.
[1] "Error in sampler$call_sampler(args_list[[i]]) : Initialization failed."
[1] "error occurred during calling the sampler; sampling not done"
[1] "Error in sampler$call_sampler(args_list[[i]]) : Initialization failed."
[1] "error occurred during calling the sampler; sampling not done"
here are whatever error messages were returned
[[1]]
Stan model 'base' does not contain samples.

[[2]]
Stan model 'base' does not contain samples.

Warning message:
In .local(object, ...) :
  some chains had errors; consider specifying chains = 1 to debug
Stan model 'base' does not contain samples.
[1] "Jobid = 1277907"
This is bayesplot version 1.7.1
- Online documentation and vignettes at mc-stan.org/bayesplot
- bayesplot theme set to bayesplot::theme_default()
   * Does _not_ affect other ggplot2 plots
   * See ?bayesplot_theme_set for details on theme setting
[1] "Generating covariate size effects plot"
This is bayesplot version 1.7.1
- Online documentation and vignettes at mc-stan.org/bayesplot
- bayesplot theme set to bayesplot::theme_default()
   * Does _not_ affect other ggplot2 plots
   * See ?bayesplot_theme_set for details on theme setting

********************************************************
Note: As of version 1.0.0, cowplot does not change the
  default ggplot2 theme anymore. To recover the previous
  behavior, execute:
  theme_set(theme_cowplot())
********************************************************

Attaching package: 'cowplot'

The following object is masked from 'package:ggpubr':

    get_legend

Error in array(x, c(length(x), 1L), if (!is.null(names(x))) list(names(x),  :
  'data' must be of a vector type, was 'NULL'
Calls: data.frame -> as.matrix -> as.matrix.default -> array
Execution halted
Error: Error while plotting covariate size effects! Code: 1
Execution halted

It is worth to note that I was running the model daily without any problems.
Did anyone have a similar issue? Any idea of how to solve it?
Desktop:

OS: Windows 10 Pro
MacOS Catalina
I tried on both.

Just found out what happened.
Apparently Denmark learned how to resurrect people during the pandemic 😆

that is what ecdc does at times. Just need to reset it


namespaces "sdf" not found

Description
I don't know fabric8 is getting me "sdf" as namespace:
[INFO] F8: Using docker image name of namespace: sdf

I'm getting this error message when I perform:
Shortly:

message=namespaces "sdf" not found

Detailed:

Unable to build the image using the OpenShift build service: Failure executing: POST at: https://vault.minishift.svc:8443/apis/image.openshift.io/v1/namespaces/sdf/imagestreams. Message: namespaces "sdf" not found. Received status: Status(apiVersion=v1, code=404, details=StatusDetails(causes=[], group=null, kind=namespaces, name=sdf, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=namespaces "sdf" not found, ...

I don't know why fabric8 plugin is getting sdf namespace.
Current oc project  is another one and I've not specified "sdf" namespace anywhere. In fact:
$ grep -rnw './' -e 'sdf'
no results

Info
* f-m-p version : 3.5.38
* Maven version (`mvn -v`) : 4.15.0-23-generic
* Kubernetes / OpenShift setup and version : v1.7.6+a08f5eeb62 / v3.7.0+7ed6862

@jeusdi: Hi, Not sure whether it's actually fmp issue or not. Could you please provide more details? Like which project you're using? Can we reproduce it locally?

@jeusdi do you have a concrete pom.xml which we could check for this issue ?


Add placeholders to make the etcd cluster run in secure TLS mode

I wanted to update the docs but it turns out that the cf-stub comes from cf-release, hence my Pull Request here. I tried to keep this change as concise and small as possible, and I am sorry in advance if I might have missed something.
===
cf-release v241 release notes tell us:
[..]
This release introduces official support for running the etcd cluster
(shared by several components such as Routing API and the loggregator
subsystem, but not Diego which uses its own secure cluster) in secure
TLS mode. Upgrading an existing deployment with an insecure etcd cluster
to a secure one with minimal downtime is non-trivial. Instructions and
additional information for this procedure can be found here. If you are
using the manifest generation scripts included within the cf-release
repo to generate manifests, you're strongly recommended to upgrade to a
secure etcd cluster at this point. The instructions above assume you are
upgrading to a secure etcd cluster from a pre-v241 Cloud Foundry
deployment and will not apply as smoothly if you later attempt to
upgrade a post-v241 non-TLS etcd cluster to a TLS cluster within the
Cloud Foundry deployment.
[..]
See: https://github.com/cloudfoundry/cf-release/releases/tag/v241

Hey @djvdorp Thanks for this PR. I think it makes sense to get these changes into the docs for the stub. Before we can accept the change I have a few requests:

Could you add the same fields to the other stubs (vsphere, openstack, bosh-lite)?
The cf-release unit tests are currently failing as a result of your change. It seems that they're failing to parse the yaml, and from what I can tell it seems like a whitespace issue. Once you fix that, the tests will still likely fail because the changes also need to be reflected in spec/fixtures/<infrastructure>/cf-manifest.yml -- the test uses the stub fixture to generate a manifest, and then asserts that result matches the expected manifest. You can run the tests with scripts/test or bundle exec rspec spec, and hopefully the output should guide you in making changes.

Hi @dsabeti Thank you for your comments, they have been processed (the same changes for the other stubs + fixed whitespace + fixed expectations to that the tests pass again). I hope this change will help many others in the future!

Hi @djvdorp!  It appears that you've made these changes against a branch of master.  Can you please make a pull request against develop instead?
Thanks very much!

@staylor14 will do that now!


Add acoustics docs under cognitive services

Add draft acoustics documentation under cognitive services
Content revision is ongoing - this PR is to stand up our docs workflow, including TOC and media
In this PR, no existing public pages have been changed to link to these new pages

 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.:x: kegodin sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Replication manager in scheduler v3 logs too frequently

What did you do?

create a changefeed with storage sink.
mock minio disk full space error.

What did you expect to see?
replication manager logs in a reasonable manner.
What did you see instead?
replication manager logs too frequently

Versions of the cluster
TiCDC version (execute cdc version):
v6.6.0-alpha

/assign @zhaoxinyu

/severity Moderate

fixed by #8674


CLOUDSTACK-9649: In the management server log there is an error

ISSUE
In the management server log there is an error
2016-10-01 00:07:31,670 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-417:ctx-e8c89b3f strmg-esx-01, cmd: GetRouterAlertsCommand) (logid:7beb3819) Command failed due to Exception: java.io.IOException
Message: There was a problem while connecting to <IP_ADDRESS>:3922
In case of basic zone and VMWare ESXi host, the NIC 2 always gets <IP_ADDRESS> as IP address. Looks like we are generating an error for connecting through this invalid IP.
2016-10-01 04:37:31,680 DEBUG [c.c.a.m.AgentManagerImpl] (RouterStatusMonitor-1:ctx-8880f9c8) (logid:946838b8) Details from executing class com.cloud.agent.api.routing.GetRouterAlertsCommand: Command failed due to Exception: java.io.IOException
Message: There was a problem while connecting to <IP_ADDRESS>:3922
2016-10-01 04:37:31,680 WARN  [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-8880f9c8) (logid:946838b8) Unable to get alerts from router r-4-VM Command failed due to Exception: java.io.IOException
Message: There was a problem while connecting to <IP_ADDRESS>:3922
2016-10-01 04:37:31,682 DEBUG [c.c.n.ExternalDeviceUsageManagerImpl] (ExternalNetworkMonitor-1:ctx-913c7bae) (logid:1b926a60) External devices stats collector is running...
Root Cause:
As Link local is not used in basic zone mode (vmware). <IP_ADDRESS> is just shown as a placeholder address. In getRouterAlerts before sending GetRouterAlertsCommand added check for ip and skip the command if ip is '<IP_ADDRESS>'.

ACS CI BVT Run
Sumarry:
Build Number 154
Hypervisor xenserver
NetworkType Advanced
Passed=101
Failed=4
Skipped=7
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_snapshots.py

test_01_snapshot_root_disk Failing since 2 runs

test_deploy_vm_iso.py

test_deploy_vm_from_iso Failing since 26 runs

test_affinity_groups.py

test_DeployVmAntiAffinityGroup Failing since 2 runs

test_vm_life_cycle.py

test_10_attachAndDetach_iso Failing since 27 runs

Skipped tests:
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
test_deploy_vgpu_enabled_vm
Passed test suits:
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_routers_network_ops.py
test_disk_offerings.py

@blueorangutan package

@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-331

@sudhansu7 Is there any particular scenario where this error appears? Or it'll appear in general in the logs when hosts are connected?

@borisstoyanov
This appears in general in Basic Zone with VMware Host.
The exception is raised in 'RouterStatusMonitor-' thread.

I've deployed a basic zone with vmware-55u3 hosts on management with centOS 7 and didn't manage to see this error. LGTM


wireless/bluetooth: decoupling bt_driver_s and bt_buf_s

Summary
wireless/bluetooth: decoupling bt_driver_s and bt_buf_s
serial/uart/h4: add bt h4 uart serial driver
arch/sim: remove BT uart implement
wirelss/bluetooth/bt_buf: add ISO buffer type
Feature request by : https://github.com/apache/incubator-nuttx/pull/3543
Impact
bluetooth uart driver module
Testing
bluetooth uart h4 devcie with 3rd stack running on userspace

Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/arch/arm/src/nrf52/nrf52_sdc.c:309:2: error: Mixed case identifier found
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/arch/arm/src/nrf52/nrf52_sdc.c:318:2: error: Mixed case identifier found
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/arch/arm/src/nrf52/nrf52_sdc.c:329:2: error: Mixed case identifier found
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/arch/arm/src/nrf52/nrf52_sdc.c:338:2: error: Mixed case identifier found
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/arch/arm/src/nrf52/nrf52_sdc.c:347:2: error: Mixed case identifier found
Error: Process completed with exit code 1.

Mixed case found by style check, ignore

Looks good. Only small change requested.
BTW, have you tested with nimBLE (sim:nimble)? You mention third party stack but don't know which do you refer?

we are using the zephyr(BLE+MESH) and bluedroid(BT) dual-mode host stack solution, and test case include BLE(peripheral/central),MESH(provisioner),BT(a2dp/avrcp/spp/etc)
    7       100 FIFO     Task    --- Waiting  Signal    00000000<PHONE_NUMBER>84   6.2%  fluorided
    9       100 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>00  11.7%  bt_stack_manager_thread 0x58c33ee0
   10       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>32   1.8%  alarm_deprecated 0
   11       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>60   5.7%  alarm_default_ca 0x58c537f8
   12       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>12   5.0%  alarm_dispatcher 0x58c537c8
   13       100 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>08   6.4%  bt_jni_thread 0x58c371e0
   14       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>72   4.8%  bt_hci_thread 0x58c385c0
   15       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>20   4.1%  bt_rx_thread 0
   16       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>32  15.3%  bt_main_thread 0x58c3c220
   17       246 FIFO     pthread --- Waiting  MQ empty  00000000<PHONE_NUMBER>72   4.8%  bt_a2dp_sink_worker_thread 0x58c429c0
   18       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>48   2.5%  uipc-main 0x58c435e0
   21       227 FIFO     Kthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>36  14.0%  BT TX  0x58c34270
   22       228 FIFO     Kthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>16  15.0%  BT RX  0x58c34270
   23       230 FIFO     Kthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>92  12.2%  BT ECC  0x58c34270
   24       228 FIFO     Kthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>88  18.3%  BT Driver  0x58c34270

Looks good. Only small change requested.
BTW, have you tested with nimBLE (sim:nimble)? You mention third party stack but don't know which do you refer?

we are using the zephyr(BLE+MESH) and bluedroid(BT) dual-mode host stack solution, and test case include BLE(peripheral/central),MESH(provisioner),BT(a2dp/avrcp/spp/etc)
    7       100 FIFO     Task    --- Waiting  Signal    00000000<PHONE_NUMBER>84   6.2%  fluorided
    9       100 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>00  11.7%  bt_stack_manager_thread 0x58c33ee0
   10       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>32   1.8%  alarm_deprecated 0
   11       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>60   5.7%  alarm_default_ca 0x58c537f8
   12       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>12   5.0%  alarm_dispatcher 0x58c537c8
   13       100 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>08   6.4%  bt_jni_thread 0x58c371e0
   14       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>72   4.8%  bt_hci_thread 0x58c385c0
   15       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>20   4.1%  bt_rx_thread 0
   16       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>32  15.3%  bt_main_thread 0x58c3c220
   17       246 FIFO     pthread --- Waiting  MQ empty  00000000<PHONE_NUMBER>72   4.8%  bt_a2dp_sink_worker_thread 0x58c429c0
   18       246 FIFO     pthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>48   2.5%  uipc-main 0x58c435e0
   21       227 FIFO     Kthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>36  14.0%  BT TX  0x58c34270
   22       228 FIFO     Kthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>16  15.0%  BT RX  0x58c34270
   23       230 FIFO     Kthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>92  12.2%  BT ECC  0x58c34270
   24       228 FIFO     Kthread --- Waiting  Semaphore 00000000<PHONE_NUMBER>88  18.3%  BT Driver  0x58c34270

Great! Any chance support for these stacks can be upstreamed into NuttX? I think this relates to the discussion about which would be a good stack to adopt.

@v01d can we merge this patch first? Other bluetooth stack can be upstreamed later.

Sure, my comment about the bluetooth stack is unrelated to this PR.


PC Gen PPA improvement

In EE477, we determined that using a tagged BTB resulted in 1.3X performance improvements, 2.5X energy efficiency improvement, 1.23X area decrease.
For this class project, we remove the first stage of pc_gen, removed the BHT completely and inserted the BTB at the first stage of the pc_gen pipeline.  Pipeline changes can be seen here:
https://docs.google.com/presentation/d/147kLmlUw3yNTlgcXGe3MajmAJPjpB9kOL_5kUlKSWLo/edit#slide=id.g5078081ba4_0_0
This reduced the 2 cycle branch taken penalty to 1 cycle with BTB miss and 0 cycle with BTB hit.  Additionally, it reduced the branch misprediction penalty and cache miss penalties by 1. Last, we flush bad speculation on redirects so that we do not send known bad speculative instructions to the Back End.  More in-depth architectural analysis can be seen here:
https://docs.google.com/presentation/d/1Rid1otSmzvT3IQaati25I-MyeChhKwY0K6PHmCZTyHw/edit#slide=id.g544b39038c_2_2
Additional improvements that will need before merging:

Re-add BHT and use it to override BTB predictions e.g. predict not taken when target is in BTB
Write to BTB on branch taken only to save space. Currently, we write on not-taken branches as well.
BTB is only written on redirects at the moment. We should also add calculated branch targets on predicted taken branches which are not in the BTB. This may get complicated because of the 1RW BTB memory.  Hopefully, there is a solution which does not require dropping conflicting BTB writes.

Non-technical nit: there are backend changes included in this pull request. Is there a way to drop them?

That’s a good point. I would like to drop them since they’re mostly already incorporated, but I’m not sure if there’s a clean way. I feel like there might be through an interactive rebase


Tag retweets with metadata

If two people both using the crossposter retweet the same tweet, this will currently result in two disparate Mastodon toots (with their own respective threads, even).
Could hidden metadata (such as the Twitter post ID) be added to the first toot so the second is skipped, and instead the first is boosted?

Failing that, at least tagging statuses (e.g. with the tweet's web URL) so clients can ignore repeated arrivals of the same cross-posted status would be a good compromise.

This doesn't seem possible without changes to Mastodon. You would need a way to search Mastodon for other toots with this metadata, which is not currently possible.
Having the receiving user's server de-duplicate toots might be possible, but you'll have to check with Mastodon whether it is something they want to implement (I suspect no).


chore(docs): add keybindings in README for which-key users

I added these for better DX, because I don't think it's possible for devs to remember all these available feature.
With which-key, the user should be able to see what each keybinding does.

This plugin is awesome, and very helpful.
I sure hope a lot of people will contribute to your project @harrisoncramer !

Hey thank you very much for the MR! We are actually in the process of pulling these keybindings into the plugin itself, (see #331) so it probably makes sense for us to get that merged first, and then you can work from there? Some of the keybindings will change.
Thanks for the kind words!

Marking this as draft until #331 gets done. Thanks!

Hey @chardskarth I've merged in the keybindings changes into develop, if you want to give a quick look them now and adjust this, they should be ready.
We can merge and ship this them both to main at the same time. Thanks!

Given some thought. I think the default keybinding works best. I think it's enough that the user can opt out from the default bindings. And if the user has that skill, they probably can spin up their own keybinding anyway.
Thanks for taking time on this. Closing now.


Modify l2deposit using spender from user with permit

This PR modifies L2Deposit.sol & IL2Deposit.sol   using  spendFromUserToWithPermit.
Related test case files are also modified, run test case with the following command at project root:
export MAINNET_NODE_RPC_URL=xxxxxxxxx
DEPLOYED=false forge test -vvv --match-path "contracts/test/forkMainnet/L2Deposit/*.t.sol" --fork-url ${MAINNET_NODE_RPC_URL} --fork-block-number '15451000'

The #114 had been merged. We could start to do the sign permit refinement 💪

The #114 had been merged. We could start to do the sign permit refinement 💪

Modified the test cases using signSpendWithPermit() from contracts-test/utils/Permit.sol


Add typings field to package.json.

support: https://github.com/Microsoft/TypeScript/pull/4352

see also: https://github.com/Microsoft/TypeScript/issues/2338


DOC: slightly improve TeX rendering of wishart/invwishart docstring

Ideally, we'd use \DeclareMathOperator from amsmath for the trace too, but this can wait for another day when someone figures out how to load MathJax extensions,
http://docs.mathjax.org/en/latest/config-files.html#the-tex-mml-am-htmlormml-configuration-file
and checks that amsmath is really OK for building the pdf docs.
[ci skip]

have manually cancelled the TravisCI build.

Thanks, merged!  I don't know much about how to convince sphinx that trace is a math function name.


make HTTPHeartBeat simplier

Going to close this and open a new commit since I big-brained and thought it was a good idea to have this on the master branch


Detailed help on options

In addition to the general help and README, let's provide some help via tooltips for non-trivial Layout, Image and Query options.

I added tooltips to the most of the options. @ugurdogrusoz Can you please review?


default to python3 for shell script setup

specify the version of the python when setting up

@chrnorm its away!


Ameba fixes and Apatite::Matrix use

I'm trying to learn about neural networks and this library is incredibly educational. Thanks for sharing this !
I couldn't help myself but made some fixes (mostly Ameba suggested) and replaced the PtrMatrix with the one from Apatite. I saw no performance issues and could make Shainet benefit from already written methods.
Hope you find this weird PR useful :-)

I have no idea why the specs fail on Travis :/

I guess we haven't really touched the CI part in a while, let me try to pass specs locally

Seems it fails on the rprop run, not the most stable one for sure.... we might want to remote Rprop from specs as it's a bad optimzer anyway, @ArtLinkov what say you?

Thanks for looking into this. All specs (except the ones already commented out in master) pass for me locally. It's strange that this one fails on Travis.

@rmarronnier first, let me say I'm happy you find SHAInet useful and thank you for contributing, Regarding the specs, if I'm not mistaken the rprop spec is the one that fails. In that case, you can just comment it out because it is quite volatile (converges fast but sometime to local minima) and doesn't work very well with small datasets

Thanks @ArtLinkov for the explanation. I commented out the failing spec. I hope it's not too essential and that it was not a safeguard against any possible regression.

@rmarronnier I believe it should be OK now.
Merging.


Revert highlight overlay and remove highlight fill

Reverts code-dot-org/blockly#237

Codecov Report

Merging #244 into main will decrease coverage by 0.02%.
The diff coverage is 49.81%.

@@            Coverage Diff             @@
##             main     #244      +/-   ##
==========================================
- Coverage   59.29%   59.26%   -0.03%
==========================================
  Files          95       95
  Lines       11720    11767      +47
==========================================
+ Hits         6949     6974      +25
- Misses       4771     4793      +22

Impacted Files
Coverage Δ

blocks/functional_examples.js
83.33% <ø> (ø)

blocks/functional_parameters.js
73.52% <ø> (-0.76%)
:arrow_down:

blocks/lists.js
5.26% <0.00%> (-0.03%)
:arrow_down:

blocks/loops.js
32.98% <0.00%> (ø)

blocks/math.js
21.48% <0.00%> (ø)

blocks/text.js
11.92% <0.00%> (-0.06%)
:arrow_down:

core/connections/connection.js
69.31% <0.00%> (-0.07%)
:arrow_down:

core/ui/block_space/block_limits.js
92.30% <ø> (ø)

core/ui/block_space/block_space.js
65.82% <ø> (ø)

...ore/ui/block_space/scroll_on_block_drag_handler.js
29.87% <ø> (-0.90%)
:arrow_down:

... and 37 more

Continue to review full report at Codecov.

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


Swiper 'resize' event bubble to window

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/s/beautiful-keldysh-l45r5q?file=/src/index.html
Bug description
Description:
Swiper dispatch ‘resize’ event if swiper-container was resized. The 'resize' event bubble to window because in onAny method swiper create instance of CustomEvent with bubble true. By web specification the ‘resize’ event on window should be called only if size of window was changed. But swiper dispatch 'resize' on container resize and this event bubble to window. The behaviour that different from web standard can lead to unexpected things because all libs focus on the standard. Thus unexpected ‘resize’ event of window can lead to bugs and unnecessary rerenders in app.
Example in my app:
This ‘resize’ events also dispatched if swiper-container or swiper-container parent change display value to ‘none’. This happening when we switch from activated route. It’s mechanism from ionic-router. The ionic-router may not unmount page from DOM and just set this page display: none. It turns out that a resize event is dispatched when a route is switched if a swiper exists on that page. And this dispatch will be invoked on window because this event bubbling.    For example now if user switch from activated route with swiper and cdk-virtual-scroll-viewport then all list in cdk-virtual-scroll-viewport will be rerendered and this will call unnecessary calculation in @angular/cdk/scrolling module. This occurs because cdk-virtual-scroll-viewport subscribes to the window ‘resize’ event and causes the viewport to be recalculated each time the resize event is called. But it expects the event to be fired only when the window size has changed, which is what it should be according to the specification.
Codesandbox description:
At the my codesandbox example you can see that after switching the swiper-container wrapper display to "none", the 'resize' event will be fired on the window. It will not call 'resize' event on widow after display: block because swiper not call 'resize' event if old height is zero.
Expected Behavior
Swiper should not dispatch 'resize' event with bubbles: true.
Actual Behavior
Swiper dispatch 'resize' event with bubbles: true.
Swiper version
10.0.4
Platform/Target and Browser Versions
macOS Chrome
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[X] I'm willing to open a PR

Use events-prefix to avoid it


Extension Globals always readOnly?

"globals": {
        "test": {
            "type": "int",
            "default": 10
        }
}

var makan;
let makan = globals_get("test"); <-- Result 10

globals_set("test", 69);

let makan = globals_get("test"); <-- Result 10

Why not result 69 ??

Anyone can help to implement globals_set() ?
It will fix phalcon/cphalcon#2979
Thanks

This issue still not fix :'(

it fixed? I had this problem.

This is fixed


the image can't run

I have the same problem at here: https://github.com/wnameless/docker-oracle-xe-11g/issues/50
I have tried your two version :16/14,both failed for the same reason.
how can I fix it?

Issue #50 has been solved.


Add optional WORKING_DIRECTORY environment variable and fix test run (#33)

Add an optional WORKING_DIRECTORY environment variable which allows to run this GitHub action in a subdirectory (i.e., in case your code and .swiftlint.yml configuration file do not reside in the root of your repository). These changes also work in combination with the DIFF_BASE environment variable.
This pull request also fixes the test run, since with SwiftLint version 0.41.0, SwiftLint has also changed the exit status on warnings in case you are using the --strict option (https://github.com/realm/SwiftLint/pull/3372/files#diff-5b9fa80336289abd42b297396f8eceb078430b385bd97439cb720a46896f4cefR65).
Please note: this was not necessary prior to SwiftLint version 0.41.0. With that version SwiftLint has changed the calculation of the root path when a directory in the tree is passed as path argument.
Prior to this version it was possible to define a path argument, whereas SwiftLint then took the config file and all excluded files relative to this path argument. This seems to have changed, whereas this awesome GitHub action does not work properly anymore in the case (a) your source code is not located in the root folder of your repository, and (b) you have defined excluded files/path in a configuration file which are relative to this source code folder (e.g., to be used within an Xcode build phase). In those cases this GitHub action can not be used anymore, due to the following changes of SwiftLint:
realm/SwiftLint@6d77deb
For further details please see #33.

Thanks for contribution!

Add an optional WORKING_PATH environment variable…

The actual change uses WORKING_DIRECTORY, but I think the change should be as it is, similar to the working-directory used in GitHub Actions.

Good point! I updated the PR title and description. Thanks!

Thanks! 🙏


Drain stdout pipe while command is running

One of the commands we called as part of a Danger plugin ended up generating more output that the Pipe's buffer could hold. This resulted in Danger locking up and blocking CI.
This change moves reading from stdin to before the task has exited so that the Pipe does not get too full.
You can test this change will the following code:
let shell = ShellExecutor()
let result = try shell.spawn("hexdump /dev/urandom | head -c 500000", arguments: [])

I thought about adding a test, but if the test were to ever go wrong it would lock up CI instead of failing

@f-meloni Could you review this when you have a chance?


Add feature toggle to disable autoImports

Describe the feature
Hello, thank you very much for the product you make.
When working with nuxt, I don't really like the concept of auto-imports and would like to disable it. I have several reasons why I want to do this:

Auto imports are secret magic. It’s not entirely clear what you are importing and from where
I use jest in my project and there are big problems with it when setting up mocks for #imports

I saw a previous issue on this topic, but as I see it did not end in anything. Currently, there are settings to disable auto-imports of components, but there are no settings to disable other auto-imports: vue re-export, @unhead/vue re-export, composables folder re-export in a project, utils folder re-export in a project.
I would like to have some setting that allows me to disable all re-exports from #imports except nuxt re-exports.
Additional information

[ ] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

I found a solution to remove composables, utils and vue re-exports, but it doesn't seem like a good solution. However, I still haven’t found how to remove @unhead/vue re-exports.

export default defineNuxtConfig({
		hooks: {
			'imports:dirs': (dirs) => {
				dirs.splice(0, dirs.lenght)
			},
			'imports:sources': (preset) => {
				preset.splice(0, preset.length, ...preset.filter(({ from }) => from !== 'vue'))
			},
		},
})

@alSergey If you want to disable auto-imports of composables and utils you can disable in nuxt.config.ts
export default defineNuxtConfig({
  imports: {
    autoImport: false
  }
})

check for more - https://nuxt.com/docs/guide/concepts/auto-imports#disabling-auto-imports
disable auto-import of components - https://nuxt.com/docs/guide/concepts/auto-imports#auto-imported-components

@alSergey If you want to disable auto-imports of composables and utils you can disable in nuxt.config.ts
export default defineNuxtConfig({
imports: {
autoImport: false
}
})
check for more - https://nuxt.com/docs/guide/concepts/auto-imports#disabling-auto-imports
disable auto-import of components - https://nuxt.com/docs/guide/concepts/auto-imports#auto-imported-components

@pothuraju-dev Hi, setting autoImports does not disable importing composables and utils folders from the project. You can check it out in this repository. I looked at your code and found that you do not check for this flag, but simply always add auto-imports for these folders.
And is there any option to disable vue and @unhead/vue auto-imports?

I get it, I used the wrong terminology. When I talked about auto imports, I meant re-exports from #imports. I have already disabled auto-imports on the project, now I want to disable unnecessary re-exports.
That is, now my imports.d.ts file looks like this.
export { isVue2, isVue3 } from 'vue-demi';
export { defineNuxtLink } from '#app/components/nuxt-link';
export { useNuxtApp, tryUseNuxtApp, defineNuxtPlugin, definePayloadPlugin, useRuntimeConfig, defineAppConfig } from '#app/nuxt';
export { requestIdleCallback, cancelIdleCallback } from '#app/compat/idle-callback';
export { setInterval } from '#app/compat/interval';
export { useAppConfig, updateAppConfig } from '#app/config';
export { defineNuxtComponent } from '#app/composables/component';
export { useAsyncData, useLazyAsyncData, useNuxtData, refreshNuxtData, clearNuxtData } from '#app/composables/asyncData';
export { useHydration } from '#app/composables/hydrate';
export { callOnce } from '#app/composables/once';
export { useState, clearNuxtState } from '#app/composables/state';
export { clearError, createError, isNuxtError, showError, useError } from '#app/composables/error';
export { useFetch, useLazyFetch } from '#app/composables/fetch';
export { useCookie, refreshCookie } from '#app/composables/cookie';
export { prerenderRoutes, useRequestHeader, useRequestHeaders, useRequestEvent, useRequestFetch, setResponseStatus } from '#app/composables/ssr';
export { onNuxtReady } from '#app/composables/ready';
export { preloadComponents, prefetchComponents, preloadRouteComponents } from '#app/composables/preload';
export { abortNavigation, addRouteMiddleware, defineNuxtRouteMiddleware, setPageLayout, navigateTo, useRoute, useRouter, onBeforeRouteLeave, onBeforeRouteUpdate } from '#app/composables/router';
export { isPrerendered, loadPayload, preloadPayload, definePayloadReducer, definePayloadReviver } from '#app/composables/payload';
export { useLoadingIndicator } from '#app/composables/loading-indicator';
export { getAppManifest, getRouteRules } from '#app/composables/manifest';
export { reloadNuxtApp } from '#app/composables/chunk';
export { useRequestURL } from '#app/composables/url';
export { usePreviewMode } from '#app/composables/preview';
export { useId } from '#app/composables/id';
export { withCtx, withDirectives, withKeys, withMemo, withModifiers, withScopeId, onActivated, onBeforeMount, onBeforeUnmount, onBeforeUpdate, onDeactivated, onErrorCaptured, onMounted, onRenderTracked, onRenderTriggered, onServerPrefetch, onUnmounted, onUpdated, computed, customRef, isProxy, isReactive, isReadonly, isRef, markRaw, proxyRefs, reactive, readonly, ref, shallowReactive, shallowReadonly, shallowRef, toRaw, toRef, toRefs, triggerRef, unref, watch, watchEffect, watchPostEffect, watchSyncEffect, isShallow, effect, effectScope, getCurrentScope, onScopeDispose, defineComponent, defineAsyncComponent, resolveComponent, getCurrentInstance, h, inject, hasInjectionContext, nextTick, provide, defineModel, defineOptions, defineSlots, mergeModels, toValue, useModel, useAttrs, useCssModule, useCssVars, useSlots, useTransitionState, Component, ComponentPublicInstance, ComputedRef, ExtractPropTypes, ExtractPublicPropTypes, InjectionKey, PropType, Ref, MaybeRef, MaybeRefOrGetter, VNode } from 'vue';
export { injectHead, useHead, useSeoMeta, useHeadSafe, useServerHead, useServerSeoMeta, useServerHeadSafe } from '@unhead/vue';
export { useStepLoading } from '../composables/use-step-loading';

And I want the imports.d.ts file to look like this.
export { isVue2, isVue3 } from 'vue-demi';
export { defineNuxtLink } from '#app/components/nuxt-link';
export { useNuxtApp, tryUseNuxtApp, defineNuxtPlugin, definePayloadPlugin, useRuntimeConfig, defineAppConfig } from '#app/nuxt';
export { requestIdleCallback, cancelIdleCallback } from '#app/compat/idle-callback';
export { setInterval } from '#app/compat/interval';
export { useAppConfig, updateAppConfig } from '#app/config';
export { defineNuxtComponent } from '#app/composables/component';
export { useAsyncData, useLazyAsyncData, useNuxtData, refreshNuxtData, clearNuxtData } from '#app/composables/asyncData';
export { useHydration } from '#app/composables/hydrate';
export { callOnce } from '#app/composables/once';
export { useState, clearNuxtState } from '#app/composables/state';
export { clearError, createError, isNuxtError, showError, useError } from '#app/composables/error';
export { useFetch, useLazyFetch } from '#app/composables/fetch';
export { useCookie, refreshCookie } from '#app/composables/cookie';
export { prerenderRoutes, useRequestHeader, useRequestHeaders, useRequestEvent, useRequestFetch, setResponseStatus } from '#app/composables/ssr';
export { onNuxtReady } from '#app/composables/ready';
export { preloadComponents, prefetchComponents, preloadRouteComponents } from '#app/composables/preload';
export { abortNavigation, addRouteMiddleware, defineNuxtRouteMiddleware, setPageLayout, navigateTo, useRoute, useRouter, onBeforeRouteLeave, onBeforeRouteUpdate } from '#app/composables/router';
export { isPrerendered, loadPayload, preloadPayload, definePayloadReducer, definePayloadReviver } from '#app/composables/payload';
export { useLoadingIndicator } from '#app/composables/loading-indicator';
export { getAppManifest, getRouteRules } from '#app/composables/manifest';
export { reloadNuxtApp } from '#app/composables/chunk';
export { useRequestURL } from '#app/composables/url';
export { usePreviewMode } from '#app/composables/preview';
export { useId } from '#app/composables/id';

That is, only nuxt re-exports remain in this file.

I think there is no option to avoid auto-importing of @unhead/vue from #imports. I have observed that it has been hardcoded in nuxt. you can check below code
https://github.com/nuxt/nuxt/blob/ae72c4a60d0ca7cd4fe2f51439d1001d8d79de9e/packages/nuxt/src/head/module.ts#L38-L50
Added to nuxt/core directly
https://github.com/nuxt/nuxt/blob/ae72c4a60d0ca7cd4fe2f51439d1001d8d79de9e/packages/nuxt/src/core/nuxt.ts#L16
https://github.com/nuxt/nuxt/blob/ae72c4a60d0ca7cd4fe2f51439d1001d8d79de9e/packages/nuxt/src/core/nuxt.ts#L545

Yes, I also didn’t find an option to disable re-exports. That is why I suggested the option of adding the toggle feature for this.

This is absolutely possible to do. I think it makes sense document how to do it (I can come back later with a config example). If this is requested by enough people we can consider a toggle but I'm not convinced that would be the right thing to do.
cc: @antfu

@danielroe hi, I would be very grateful if you could send me an example config on how to do this. Thanks in advance 😊

I am curious about what's the problem with re-exporting? It's a type DTS file, and it's not global; supposedly, it doesn't affect how things work, isn't it?

Yes, this file really does not affect the application itself, but it does affect the writing of tests (I wrote about this at the very beginning). I may not to use imports from #imports, but there are a few reasons why I want to disable this feature:

I have several projects on which not only I work. Not everyone is careful to use #imports
The IDE suggests importing from #imports rather than from vue or @unhead/vue. I can try to reconfigure this, but then we return to the first point

It is for these reasons that I want to disable everything from #imports except nuxt

For what it's worth, here are my two cents.
As a bit of context, I've been using Nuxt professionally for six years now. I've witnessed the introduction of the opt-in auto-import feature in Nuxt 2, and then the mandatory auto-import feature in Nuxt 3.
When Nuxt 3 was officially released, about a year ago, I started to take part in our project migration to modernize what was running on Nuxt 2 at that time. To give some idea of the scale, about 30 front-end engineers work full-time on that project, building customer-facing pages in dozens of different scopes.
With the background being put, let's jump on the actual topic. My main struggle with the auto-import feature is the fact that I feel like we're going back in time to the global variables era. Having to manually ensure that there is no conflict between two exported entities feels wrong to me now that ESM has officially standardized the import/export mechanism and takes care of managing those conflicts for us.
That said, my feelings on this auto-import feature evolved a lot during the past few months. I have to admit that I wrongly pushed back the idea without giving it its proper chance when it was introduced in Nuxt 2 and then kept my strong opinion with Nuxt 3. But, I recently started a small project with Nuxt 3, and have been surprised that when there are no chances of conflicts between two exports, the developer experience is pretty delightful.
However, I'm still convinced that it can't work on large projects with lots of people contributing on a daily basis on dozens of different scopes. On our side, we made the choice to modularize all our application scopes so that our developer teams can be autonomous in their implementations. For example, the "payment" team owns a module dedicated to payment features, and the "authentication" team owns a module dedicated to login and register.
By using the auto-import feature, both teams would have to make sure not to expose components, composables, utils, or whatever, named the same way or one would override the other. And this increases exponentially the more teams work in parallel. Of course, there is always the ability to prefix the exported members with the scope they belong to, but again it feels wrong to me.
All-in-all, I do think that the auto-import feature is valuable and enhances the developer experience in small-to-medium projects. But it tends to go the other way in large projects, making the developer experience worse because of the workarounds we have to put in place to prevent conflicts.
So, I would also be in favour of turning the auto-import feature into an opt-out mechanism so we could turn it off when we feel like it.

I totally understand the concerns - we do let you disable auto-import if needed.
Exports in #imports to me are not considered as auto-import, but more like "explicit auto resolve" which does not really inference the "globals".
We can't just disable #imports as modules are relying on it to resolve the imports they need. And resolved paths are not always as simple as import { useHead } from '@unhead/vue' but could be something like import { useHead } from '../node_modules/module-foo/node_modules/@unhead/vue', which are non-hoisting friendly that hard to write manually (also not always deterministic)
If you don't want your IDE to suggest that, I am sure there would be ways to configure it. For example, in VS Code you could do this with settings.json:
  "typescript.preferences.autoImportFileExcludePatterns": [
    "#imports",
  ],

I hope that would resolve the issue you have.

@antfu hi, as I already wrote above, the option of setting up an IDE is not suitable for me. I have several projects that are worked on by different people with different IDEs and there is always a chance that someone accidentally uses imports from #imports.
I also understand that some imports can be quite complex and are more conveniently imported from #imports (composables from pinia is a good example). What I’m saying is that I want to be able to disable re-exports of the composables and utils folders from my project, as well as the vue and @unhead/vue libraries. Apart from these libraries, I didn’t find anything else that could be disabled without losing convenience (all other libraries are imported through complex paths).
I looked at the nuxt code and found that you add these re-exports yourself, meaning this can be disabled somehow.
This is where composables and utils are added. https://github.com/nuxt/nuxt/blob/275bee5b0812b59c20a51c73d2bc4c36d03b5185/packages/nuxt/src/imports/module.ts#L52-L63
This is where vue is added. https://github.com/nuxt/nuxt/blob/275bee5b0812b59c20a51c73d2bc4c36d03b5185/packages/nuxt/src/imports/presets.ts#L121-L218
This is where @unhead/vue is added.
https://github.com/nuxt/nuxt/blob/275bee5b0812b59c20a51c73d2bc4c36d03b5185/packages/nuxt/src/head/module.ts#L38-L50
Considering that @danielroe said that this can be done, as I understand it, the only thing that is needed on your part is to describe in the documentation how to do this.

Though I'm not entirely against the opt-in nature of auto imports (with the extended possibilities of configuration) at the same time I think that this feature is one of those things they make Nuxt - Nuxt - the framework  with unparalleled DX. I represent a person who is working on a project of 100K+ lines of FE code and 65+ devs that work in more than 10 teams. By the last 1.5 years of using Nuxt 3 we had 0 issues with auto imports that we couldn't resolve but at the same time much leaner codebase, bigger opportunities due to layers and ultimate happier devs.

@AndrewBogdanovTSS That's interesting! Our team is roughly half the size of yours, and we've already hit some limitations while you did not. My understanding is that we're doing things differently from you, and it's not working as good as for you. 😅
May I ask what your project architecture and/or your processes look like? More specifically, how do you prevent two teams from overriding each other through the "global" exports mechanism available from #imports.
I understand it's a bit off from the initial issue. But, if we could share some best practices to work with Nuxt at scale, we could even document them properly as with everything else, and ease the life of many teams out there.
(Consider myself willing to contribute on that if that's something the Nuxt team sees as valuable)

Related Nitro discussion: https://github.com/unjs/nitro/issues/2232

Despite the fact that this issue is now closed (and, by the way, thanks to the Nuxt team for the scan option), I'm still interested in learning more about the way you structure your project @AndrewBogdanovTSS.
If you ever come back to this issue, don't hesitate to share what seems to be working for you. 🤗

@antfu hi, has the feature already been released? I looked at the latest version 3.11.2 and it's not there


BLE client command error

As I loop and request the real-time data, about every four seconds.  I started seeing this error:
"ERROR: S2 Command Corrupted! cmd=0x92000826"
This causes an incomplete real-time data read which causes the parsing to fail.   Then a BLE client disconnect.
Any thoughts?

Show full code of minimal reproducible example in python and full output of $ python3 yourcode.py

Can you reproduce this over USB? I've found that even with the official apps the Bluetooth link can be a little bit unreliable.
Polling every 4 seconds shouldn't be a problem. I was experimenting with high rate polling over USB and got nearly 200Hz. Of course, the device only updates measurements at 2Hz.

@cdump , I coding java in android studio making an Android-RadiaCode device BLE connection.
I perform the init, deviceName, getConfigurations, serialnumber and version.  If these calls are successful then I start a polling loop to get readings and periodically the current spectrum.
The polling loop sleeps for about 4 seconds and I have a "working" flag so I don't poll until I'm finished decoding.
To catch this issue I installed the windows radiacode software and I'm running it and connecting with USB.  And this error showed up in the log console window of the windows radiacode app.
I "believe" that this might be an issue of requesting data from the windows radiacode usb app while i'm testing my android java ble app.
I'm testing that way because I'm comparing my android app data with the windows radiacode usb data to check my work as best I can.
So I'll show my java code where I set the characteristic value.

int reqSeqNo    = 0x80 + this.seq;
this.seq        = (this.seq + 1) % 32;
String seqhex2  = String.format("%02X", reqSeqNo);
byte [] writeMe = hexStringToByteArray("08000000260800"+seqhex2+"00010000");//reading
sc.setValue       (writeMe);    //request the reading
boolean tf       = mBluetoothGatt.writeCharacteristic(sc);
try
{
    waitForCharacteristicChange(3,TimeUnit.SECONDS);
}
catch (InterruptedException e)
{
    e.printStackTrace();
}
//this triggers onCharacteristicChanged ble callback.

I "believe" that this might be an issue of requesting data from the windows radiacode usb app while i'm testing my android java ble app.

Good bet. The windows app complains when it tries to connect while my phone is already connected.

This was because I was comparing the live windows USB data with the readings the BLE at the same time.  When using only one interface at a time this behavior stopped.


how to run example ?

I tried
node --debug app.js
but no cigar ...

Can't see it in the Readme - but thanks anyway

oh sorry - I thought that was output ... it's late on friday ok ?! ^_^

haha :D


colab error

Hi,
Issue fixed. Should download checkpoint_teacher.pth instead of checkpoint.pth.

Thanks!


docs: Fix Python taint tracking links

at some point we moved security/TaintTracking.qll to dataflow/TaintTracking.qll

Actually, ignore my approval, I think I just spotted a broken link.

Good that you spotted it! I fixed it and amended the commit, but it should all be good now :tada:

Thanks!


add jsonplaceholder link

Fake Online REST API for Testing and Prototyping

Hi @davemachado
Thank you for your feedback. However, somebody is already added this link in Test Data. So I should close PR, right?


Using DataArray.where() with a DataArray as the condition drops the name

Code Sample, a copy-pastable example if possible
Create a boolean DataArray to use as a mask for another DataArray, with the same coordinates:
da_1 = xr.DataArray(np.array([0.861185, 0.301491, 0.642744, 0.773298, 0.786516, 0.011693, 0.659326, 0.07877 , 0.108488, 0.747863]), coords=[('coord1', np.arange(10))], name='da1')
da_2 = xr.DataArray(np.array([0.116959, 0.955742, 0.121562, 0.635573, 0.304895, 0.064529, 0.042461, 0.41751 , 0.607457, 0.110104]), coords=[('coord1', np.arange(10))], name='da2')
da_3 = np.rint(da_2).astype('bool')
print(da_1)
<xarray.DataArray 'da1' (coord1: 10)>
array([0.861185, 0.301491, 0.642744, 0.773298, 0.786516, 0.011693, 0.659326,
       0.07877 , 0.108488, 0.747863])
Coordinates:
  * coord1   (coord1) int64 0 1 2 3 4 5 6 7 8 9
print(da_1.where(da_3))
<xarray.DataArray (coord1: 10)>
array([     nan, 0.301491,      nan, 0.773298,      nan,      nan,      nan,
            nan, 0.108488,      nan])
Coordinates:
  * coord1   (coord1) int64 0 1 2 3 4 5 6 7 8 9

Problem description
When using a DataArray (da_3 in the example) as the condition in the where() method of another DataArray (da_1), the name of the DataArray being masked (da_1) is dropped.
Expected Output
The name should be retained.
print(da_1.where(da_3))
<xarray.DataArray 'da_1` (coord1: 10)>
array([     nan, 0.301491,      nan, 0.773298,      nan,      nan,      nan,
            nan, 0.108488,      nan])
Coordinates:
  * coord1   (coord1) int64 0 1 2 3 4 5 6 7 8 9

Output of xr.show_versions()

INSTALLED VERSIONS
commit: None
python: 3.6.5.final.0
python-bits: 64
OS: Linux
OS-release: 4.13.0-38-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_GB.UTF-8
LOCALE: en_GB.UTF-8
xarray: 0.10.3
pandas: 0.22.0
numpy: 1.14.3
scipy: 1.1.0
netCDF4: 1.3.2
h5netcdf: None
h5py: 2.7.1
Nio: None
zarr: None
bottleneck: 1.2.1
cyordereddict: None
dask: 0.17.4
distributed: 1.21.8
matplotlib: 2.2.2
cartopy: None
seaborn: 0.8.1
setuptools: 39.1.0
pip: 10.0.1
conda: 4.5.2
pytest: 3.5.1
IPython: 6.4.0
sphinx: 1.7.4

Indeed, we should have some sort of logic to indicate that the name from the original DataArray should be preserved.
Under the hood, DataArray.where uses xarray.apply_ufunc. So maybe this should be coupled with keep_attrs=True in xarray.apply_ufunc()?

Yes, I think it makes sense to couple it with keep_attrs=True. One could question whether the name should be considered separate to the attributes (and therefore have an additional keyword argument for keeping the name), but I think in most cases it makes sense to keep the name if you're already keeping the attributes, and to drop the name if you're dropping the attributes.

This bug appears to have been fixed, as of Xarray 0.15.0.


Touch Pen Lag

Description
The touch interface on V3 lags when using a Surface Pen 2 Slim, on a Windows 11 / Surface Laptop Studio.
This didn't happen in the previous version V2.
When using the fingers it works fine but for some reason pen has a very noticeable lag
Steps To Reproduce
Use pen on touch screen
Requirements

e.g. Fix crash that occurs when...
It should be reacting properly with fingers or pens on touch devices

Files Version
<IP_ADDRESS>
Windows Version
10.0.23555.1000
Log File
debug.log

Thanks for the report, do you mean when clicking elements via pen?

The only change that we made in this area was updating to WinUI 1.4 in which case this affects other apps as well. Can you open a report in the WinUI repo? https://github.com/microsoft/microsoft-ui-xaml

I wont be able sorry

👍


DS-4430: Fix the JSPUI ConcurrentModificationException when a group is removed from a group

+1 applied it to one of our test instance with proper data


ESP32 stuck at Confirming Wi-Fi connection while provisioning. (MEGH-3825)

I am adding new device in ESP Rainmaker app(tried both in iOS & android), but the provisioning process always stuck at confirming wi-fi connection and show Device disconnected error.
I can see in the serial monitor that the ESP32 is connected to the wifi.
The error is caused as the ESP32 restarts after connecting.
Here is the debug output
01:45:10.155 -> Reset Button Pressed!
01:45:15.297 -> Reset Wi-Fi.
01:45:15.333 -> [222834][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 3 - STA_STOP
01:45:17.327 -> ets Jun  8 2016 00:22:57
01:45:17.362 ->
01:45:17.362 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
01:45:17.362 -> configsip: 0, SPIWP:0xee
01:45:17.362 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
01:45:17.362 -> mode:DIO, clock div:1
01:45:17.362 -> load:0x3fff0030,len:1344
01:45:17.362 -> load:0x40078000,len:13864
01:45:17.362 -> load:0x40080400,len:3608
01:45:17.362 -> entry 0x400805f0
01:45:17.900 -> [�⸮⸮mum⸮⸮⸮⸮2-hal-cpu.c:214] setCpuFrequencyMhz(): PLL: 480 / 2 = 240 Mhz, APB: 80000000 Hz
01:45:17.973 -> [    56][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 0 - WIFI_READY
01:45:18.009 -> [    83][I][RMaker.cpp:14] event_handler(): RainMaker Initialised.
01:45:18.009 ->
01:45:18.009 -> Chip ID:  12913848 Service Name: ESP32
01:45:18.009 ->
01:45:18.009 -> Starting ESP-RainMaker
01:45:18.009 -> [    87][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 33 - PROV_INIT
01:45:18.009 -> [    91][I][WiFiProv.cpp:133] beginProvision(): Starting AP using BLE. service_name : ESP32, pop : maxakash
01:45:18.085 -> [   190][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 2 - STA_START
01:45:18.532 -> [   601][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Living Room TV, Param Name : Power, Val : false
01:45:18.532 -> [   601][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Living Room Cove Light, Param Name : Power, Val : false
01:45:18.532 -> [   602][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 35 - PROV_START
01:45:18.532 ->
01:45:18.532 -> Provisioning Started with name "ESP32" and PoP "maxakash" on BLE
01:45:18.532 -> Scan this QR code from the ESP RainMaker phone app.
01:45:18.568 ->
01:45:18.568 ->   █▀▀▀▀▀█ ▀██▄▀▀█▀▀▄▄█ ▄ ▀▄ █▀▀▀▀▀█
01:45:18.606 ->   █ ███ █ ▄█▀▀█▄▄██▀▄ █▀▀▄  █ ███ █
01:45:18.606 ->   █ ▀▀▀ █ █▄▄█▀  ▀▄▄▄▄ ██▀█ █ ▀▀▀ █
01:45:18.606 ->   ▀▀▀▀▀▀▀ █ █▄█ █▄▀▄█▄█▄█▄█ ▀▀▀▀▀▀▀
01:45:18.606 ->   ▀ ▄▄█ ▀▀▀ ▄█▀  ▄█  ▄▀▀▀███▀▀▀▀▄▄▀
01:45:18.606 ->   █ ██▀▀▀ ▀█  ▀ █▀██▀▄ █▄█▄▄██ ▀▀ ▄
01:45:18.644 ->    █▄█▄▀▀▄ █▄▀▄▀█▄▄▀█▀▀▀███▄▀▄▀▀▄█
01:45:18.644 ->   █▀▀ ▄█▀▄█▀▄▄▄█▄█▀█   █▀▀  ▄▄█▀▀▄▄
01:45:18.644 ->     █▀█▄▀ ▄█▀   ██ ▀▀▀█▀▀▄█ ▀▀▀▄▄▀
01:45:18.644 ->   ▀▄▀  ▀▀█ ▄ ▀▀  █▀▄ ▄ ▄█▀ ▄ █▄▀▀ ▄
01:45:18.682 ->   ██▀██▀▀ █▀ ▄█ ▄█▄▀▀  █▀▄█ ▀▄▀▄ ▀▀
01:45:18.682 ->      ▄▀█▀ ▀ █▀ ▀▀▀█▄▄▄▀█ █ ▀▄█▀  ▀▄
01:45:18.682 ->   ▀▀▀   ▀ ▄▀▄▀█▄█▄ █▀▀▄▀▀▀█▀▀▀█▄▄▄
01:45:18.682 ->   █▀▀▀▀▀█ ▀ ▄▀▀ ▄▀█▄ ▄ █▀▄█ ▀ █
01:45:18.682 ->   █ ███ █ ▀▄ ▀▄██▄▄▀█▀ ▀▀▄███▀█▀▄▀▀
01:45:18.720 ->   █ ▀▀▀ █   ▀ ▄▀ ▀█▄ ▄▄█ █▄▀▀█▀
01:45:18.720 ->   ▀▀▀▀▀▀▀ ▀   ▀▀   ▀▀ ▀▀ ▀▀    ▀  ▀
01:45:18.720 ->
01:45:18.720 ->
01:45:18.720 -> If QR code is not visible, copy paste the below URL in a browser.
01:45:18.720 -> https://rainmaker.espressif.com/qrcode.html?data={"ver":"v1","name":"ESP32","pop":"maxakash","transport":"ble"}
01:45:18.720 -> [   618][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Living Room Chandelier, Param Name : Power, Val : false
01:45:18.758 -> [   820][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Dining Room Chandelier, Param Name : Power, Val : false
01:45:18.758 -> [   831][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Kitchen Chandelier, Param Name : Power, Val : false
01:45:18.758 -> [   842][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Outside Profile Light, Param Name : Power, Val : false
01:45:18.758 -> [   852][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Curtain Open, Param Name : Power, Val : false
01:45:18.792 -> [   862][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Curtain Close, Param Name : Power, Val : false
01:45:55.088 -> [ 37195][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 1 - SCAN_DONE
01:46:00.027 -> [ 42102][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 37 - PROV_CRED_RECV
01:46:02.373 -> [ 44457][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 4 - STA_CONNECTED
01:46:02.373 ->
01:46:02.373 -> Connected to Wi-Fi!
01:46:02.692 -> [ 44784][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 7 - STA_GOT_IP
01:46:02.692 -> [ 44784][D][WiFiGeneric.cpp:991] _eventCallback(): STA IP: <IP_ADDRESS>, MASK: <IP_ADDRESS>, GW: <IP_ADDRESS>
01:46:02.725 -> [ 44790][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 39 - PROV_CRED_SUCCESS
01:46:05.283 -> E (59355) wifi_prov_mgr: Failed to create prov_stop_task!
01:46:05.316 ->
01:46:05.316 -> abort() was called at PC 0x40177e67 on core 0
01:46:05.316 ->
01:46:05.316 ->
01:46:05.316 -> Backtrace:0x40083815:0x3ffe2a700x40094d09:0x3ffe2a90 0x4009a429:0x3ffe2ab0 0x40177e67:0x3ffe2b30 0x40179345:0x3ffe2b60 0x401793e4:0x3ffe2b80 0x4017958f:0x3ffe2ba0 0x40179e45:0x3ffe2c20 0x4017a003:0x3ffe2c90 0x401815cf:0x3ffe2cd0 0x40182d45:0x3ffe2d20 0x40183381:0x3ffe2d60 0x401342f2:0x3ffe2da0 0x40134c5a:0x3ffe2dc0 0x40128971:0x3ffe2e10 0x4012a7e7:0x3ffe2e30
01:46:05.354 ->
01:46:05.354 ->
01:46:05.354 ->
01:46:05.354 ->
01:46:05.354 -> ELF file SHA256:<PHONE_NUMBER>000000
01:46:05.354 ->
01:46:05.354 -> Rebooting...
01:46:05.354 -> ets Jun  8 2016 00:22:57
01:46:05.354 ->
01:46:05.354 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
01:46:05.354 -> configsip: 0, SPIWP:0xee
01:46:05.354 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
01:46:05.354 -> mode:DIO, clock div:1
01:46:05.354 -> load:0x3fff0030,len:1344
01:46:05.354 -> load:0x40078000,len:13864
01:46:05.354 -> load:0x40080400,len:3608
01:46:05.354 -> entry 0x400805f0
01:46:05.907 -> [�⸮⸮mum⸮⸮⸮⸮2-hal-cpu.c:214] setCpuFrequencyMhz(): PLL: 480 / 2 = 240 Mhz, APB: 80000000 Hz
01:46:05.975 -> [    58][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 0 - WIFI_READY
01:46:06.013 -> [    85][I][RMaker.cpp:14] event_handler(): RainMaker Initialised.
01:46:06.013 ->
01:46:06.013 -> Chip ID:  12913848 Service Name: ESP32
01:46:06.013 ->
01:46:06.013 -> Starting ESP-RainMaker
01:46:06.013 -> [    89][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 33 - PROV_INIT
01:46:06.013 -> [    93][I][WiFiProv.cpp:149] beginProvision(): Already Provisioned
01:46:06.013 -> [    98][I][WiFiProv.cpp:153] beginProvision(): Attempting connect to AP: Stark
01:46:06.013 ->
01:46:06.089 -> [   195][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 2 - STA_START
01:46:06.127 -> [   196][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 34 - PROV_DEINIT
01:46:06.127 -> [   212][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Living Room TV, Param Name : Power, Val : false
01:46:06.127 -> [   212][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Living Room Cove Light, Param Name : Power, Val : false
01:46:06.165 -> [   222][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Living Room Chandelier, Param Name : Power, Val : false
01:46:06.165 -> [   233][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Dining Room Chandelier, Param Name : Power, Val : false
01:46:06.165 -> [   243][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Kitchen Chandelier, Param Name : Power, Val : false
01:46:06.165 -> [   254][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Outside Profile Light, Param Name : Power, Val : false
01:46:06.201 -> [   264][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Curtain Open, Param Name : Power, Val : false
01:46:06.201 -> [   274][I][RMakerDevice.cpp:163] updateAndReportParam(): Device : Curtain Close, Param Name : Power, Val : false
01:46:06.201 -> [   279][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 4 - STA_CONNECTED
01:46:06.201 ->
01:46:06.201 -> Connected to Wi-Fi!
01:46:06.745 -> [   846][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 7 - STA_GOT_IP
01:46:06.783 -> [   846][D][WiFiGeneric.cpp:991] _eventCallback(): STA IP: <IP_ADDRESS>, MASK: <IP_ADDRESS>, GW: <IP_ADDRESS>

Here is the error which I got while using code from examples
02:16:04.000 -> [ 37283][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 1 - SCAN_DONE
02:16:11.391 -> [D][ 44713][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 37 - PROV_C 47172][D]RED_RECV
02:16:13.861 -> [[WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 4 - STA_CONNECTED
02:16:14.850 -> [ 48158][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 7 - STA_GOT_IP
02:16:14.850 -> [ 48158][D][WiFiGeneric.cpp:991] _eventCallback(): STA IP: <IP_ADDRESS>, MASK: <IP_ADDRESS>, GW: <IP_ADDRESS>
02:16:14.887 -> [ 48164][D][WiFiGeneric.cpp:929] _eventOV_CRED_SUCCallback(): Arduino Event: 39 - PRCESS
02:16:26.703 -> [ 60018][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 5 - STA_DISCONNECTED
02:16:26.739 -> [ 60019][W][WiFiGeneric.cpp:950] _eventCallback(): Reason: 200 - BEACON_TIMEOUT
02:16:26.739 -> [ 60022][D][WiFiGeneric.cpp:966] _eventCallback(): WiFi Reconnect Running
02:16:26.739 -> E (62324) wifi_prov_mgr: STA Disconnected
02:16:26.739 -> E (62334) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x2880
02:16:26.739 -> E (62337) wifi_prov_mgr: Disconnect reason : 200
02:16:26.739 -> E (62343) esp-tls: Failed to open new connection
02:16:26.739 -> E (62352) TRANSPORT_BASE: Failed to open a new connection
02:16:26.777 -> E (62367) MQTT_CLIENT: Error transport connect
02:16:26.777 -> E (62368) esp_mqtt_glue: MQTT_EVENT_ERROR
02:16:26.777 -> E (62368) wifi:sta is connecting, return error
02:16:29.827 -> [ 60064][E][WiFiSTA.cpp:317] begin(): connect failed! 0x3007
02:16:29.827 -> 15][D][WiFi:92nt: 5 - STA[ 631Generic.cpp9] _eventCallback(): Arduino Eve_DISCONNECTED
02:16:29.827 -> [ 63116][W][WiFiGeneric.cpp:950] _eventCallback(): Reason: 15 - 4WAY_HANDSHAKE_TIMEOUT
02:16:29.827 -> E (65420) wifi_prov_mgr: STA Disconnected
02:16:29.827 -> E (65428) wifi_prov_mgr: Disconnect reason : 15
02:16:29.827 -> Eror
02:16:29.827 -> [ 6 (65432) wifi_prov_mgr: STA Auth Er3131][E][WiFiGeneric.cpp:535] _arduino_event_cb(): Provisioning Failed: Reason : Authentication Failed
02:16:29.881 -> [ 63140][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 38 - PROV_CRED_FAIL
02:16:41.766 -> E (77369) esp-tls: [sock=48] connect() error: Host is unreachable
02:16:41.766 -> E (77369) esp-tls: Failed to open new connection
02:16:41.766 -> E (77369) TRANSPORT_BASE: Failed to open a new connection
02:16:41.766 -> E (77373) MQTT_CLIENT: Error transport connect
02:16:41.766 -> E (77377) esp_mqtt_glue: MQTT_EVENT_ERROR
02:16:46.961 -> [ 80282][D].cp[WiFiGenericp:929] _eventCallback(): Arduino Event: 36 - PROV_END
02:16:47.007 -> [ 80282][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 34 - PROV_DEINIT
02:16:56.801 -> E (92381) esp-tls: [sock=48] connect() error: Host is unreachable
02:16:56.801 -> E (92382) esp-tls: Failed to open new connection
02:16:56.801 -> E (92382) TRANSPORT_BASE: Failed to open a new connection
02:16:56.801 -> E (92386) MQTT_CLIENT: Error transport connect
02:16:56.801 -> E (92390) esp_mqtt_glue: MQTT_EVENT_ERROR
02:17:11.787 -> E (107394) esp-tls: [sock=48] connect() error: Host is unreachable
02:17:11.787 -> E (107395) esp-tls: Failed to open new connection
02:17:11.787 -> E (107395) TRANSPORT_BASE: Failed to open a new connection
02:17:11.787 -> E (107399) MQTT_CLIENT: Error transport connect
02:17:11.824 -> E (107403) esp_mqtt_glue: MQTT_EVENT_

This is the error I got after lot of trying
02:35:05.748 -> E (51329) wifi_prov_mgr: STA Disconnected
02:35:05.781 -> E (51329) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x2880
02:35:05.781 -> E (51329) wifi_prov_mgr: Disconnect reason : 200
02:35:05.781 -> E (51329) esp-tls: Failed to open new connection
02:35:05.781 -> E (51336) TRANSPORT_BASE: Failed to open a new connection
02:35:05.781 -> E (51351) MQTT_CLIENT: Error transport connect
02:35:05.781 -> E (51352) esp_mqtt_glue: MQTT_EVENT_ERROR
02:35:05.781 -> E (51352) wifi:sta is connecting, return error
02:35:08.820 -> E (54403) wifi_prov_mgr: STA Disconnected
02:35:08.820 -> E (54403) wifi_prov_mgr: Disconnect reason : 15
02:35:08.856 -> E (54403) wifi_prov_mgr: STA Auth Error
02:35:20.801 -> E (66353) esp-tls: [sock=48] connect() error: Host is unreachable
02:35:20.801 -> E (66353) esp-tls: Failed to open new connection
02:35:20.801 -> E (66353) TRANSPORT_BASE: Failed to open a new connection
02:35:20.801 -> E (66357) MQTT_CLIENT: Error transport connect
02:35:20.801 -> E (66361) esp_mqtt_glue: MQTT_EVENT_ERROR
02:35:35.806 -> E (81365) esp-tls: [sock=48] connect() error: Host is unreachable
02:35:35.806 -> E (81366) esp-tls: Failed to open new connection
02:35:35.806 -> E (81366) TRANSPORT_BASE: Failed to open a new connection
02:35:35.806 -> E (81370) MQTT_CLIENT: Error transport connect
02:35:35.806 -> E (81374) esp_mqtt_glue: MQTT_EVENT_ERROR

It worked after 20-30 tries.

It worked after 20-30 tries.


remove redundant info in search

To meet a request for more info in search, the 'subkind' tag was added to the info div. However, 'subkind' is also used as a category, so the information is redundant.

done


Please make a home key on the main tab.

I love this keyboard very much! Could anyone tell me how to get the HOME key on the main tab? As you know, we have two ENTER key (usual one and the one with Circle label next to the left Arrow) but not any HOME key.
I did not find a way to custom it, so may be this is a feature request.

FWIW:

⏎ = Enter/Return key
○ = Compose key, used to create complex characters

Also, changing keys isn't (yet?) a capability of HK, & many issues tracking such have been filed.  Your best chance currently @ Home is via Fn.

I too love this keyboard and have customized it to allow me to type in three different languages. However, my finger is large so that I touch other keys inadvertently sending some other data entry key or character to the input field. Further, striking an ALTERNATE KEY to the main key is difficult. It takes at least THREE attempts to use an alternate character to the default because the alternate characters DISAPPEAR even though they are the ones needed to accomplish selecting the proper character. EVEN SO, this is a WONDERFUL alternative keyboard that I have assigned as my DEFAULT preferred means of data entry. Highly recommended!


Clarifying 'path' dependency parameter

I wanted to emphasise that adding a 'path' is not a complete drop-in
replacement, as code changes will need to be made in order for it
to work.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @huonw (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

... is this true? It shouldn't be.

Is this perhaps getting confused with https://github.com/rust-lang/cargo/pull/2016? I also agree with @steveklabnik that this shouldn't be necessary as it just means you'll need extern crate foo in the main crate and then you have to use paths through that instead.

:umbrella: The latest upstream changes (presumably #2018) made this pull request unmergeable. Please resolve the merge conflicts.

hmm... I just tried to create a simple test case, but it works fine.
I am definitely needing the "self::", otherwise it doesn't compile. I'll keep digging to see what the actual problem is.

Maybe it's a misunderstanding on my side. However, I've managed to reduce it to the following:
https://github.com/alfiedotwtf/cargo_path_dependencies
https://github.com/alfiedotwtf/cargo_path_dependencies_working

It seems that traits work strangely, possibly because they need to be local to the impl? Filed a bug in documentation as this was how I got it working, but it could possibly be a bug in Rust?

@alfiedotwtf ah yes so what's happening there is that paths mentioned in use statements are always relative to the crate root, so when you add the extern crate directive in a module that's not the root of the project if you want to reference it you'll have to either use module::containing::extern::directive::... or self::....

Ah, awesome. Thanks for clearing that for me :)


Refresh pub-sub quickstart (tutorial) fixing routes and stale dependency

Description
The pub-sub and distributed-calculator quickstart/tutorials are refreshed fixing two classes of issues:

There is always a startup error complaining about "<" found when subscribing to /dapr/subscribe/ receives the React client page (RCA is the * route)
Migrated HTTP handling to axios library, from legacy request library, to match our new quickstarts and eliminate deprecated dependency.

Issue reference
Fixes #516
Fixed #270
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] The quickstart code compiles correctly
[x] You've tested new builds of the quickstart if you changed quickstart code
[x] You've updated the quickstart's README if necessary
[x] If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

Looking at test issue

We're really close here.  I fixed issue so tests pass.
I'm trying to also fix distributed calculator while i'm here to use an http package that is better supported (like axios).  Piping requests/responses in Axios is tricky so I'm still working on that.

LGTM

@paulyuk - Looks like there is an error on the KubeTests, Any concerns here and have you looked into why?
Step: Deploy Node App
command: kubectl logs --selector app=node-subscriber -c node-subscriber
return_code: 0
duration_seconds: 0.154
Expected stdout (output_match_mode: exact):
A:  Message on A
B:  Message on B
Actual stdout:
Node App listening on port 3000!
ERROR expected lines not found:
	A:  Message on A
	B:  Message on B

@paulyuk - Looks like there is an error on the KubeTests, Any concerns here and have you looked into why? Step: Deploy Node App command: kubectl logs --selector app=node-subscriber -c node-subscriber return_code: 0 duration_seconds: 0.154 Expected stdout (output_match_mode: exact): A: Message on A B: Message on B Actual stdout: Node App listening on port 3000!
ERROR expected lines not found:
	A:  Message on A
	B:  Message on B

Thanks @msfussell .  I think I spot the root cause. In the pub-sub and bindings tests, we try to pull docker images into that k8s cluster.  This happens over and over ahead in this automated test.
Since it's a public registry and there are no credentials used for the pull, this is an anonymous pull.  And it's being throttled!
Let's chat about migrating images to a GHCR (best practice to be in private registry anyway).  We can alternatively sign in to Hub using credentials.
All that said, This PR is passing and ready for merge.


Error on install

"The command '/bin/ash -o pipefail -c apk add --no-cache python3 bluez py-pip git' returned a non-zero code: 4"
Any clues on how to get this to work? Rpi4, Twister OS, HA Supervised
(Also, thanks for making this, super handy!)

Never heard of exit code 4. Maybe a permission / disk space error?
To track this down, please edit Dockerfile and replace the lines
RUN \
  apk add --no-cache \
    python3 bluez py-pip git

with
RUN apk add --no-cache python3
RUN apk add --no-cache py-pip
RUN apk add --no-cache bluez
RUN apk add --no-cache git

Sorry, I'm kinda new to how add-ons work. How would I edit that file within the flow of using the Add-on/repo? When I add the repo, does it download it somewhere? I can also install a separate Docker container.
Just checked again and still getting the same error after clicking install. Could it be something to do with 32bit Raspberry PiOS?

Made a fork of the repo to test the changes you suggested. Same error.
My disk, according to HA is only 40% full, so should have space.

I have the same issue.

Please try version 0.0.50, which doesn't fix the error but gives more insights on what package actually causes the error

Closed due to inactivity. Please create a new issue if still present