[boost] accumulators is missing in the port

boost accumulators is not bult / installed when building the boost port (boost 1.79). It should be.

.\vcpkg.exe install boost-accumulators:x64-windows works fine.

it was missing in my x64-linux  build for some reason

This port does not have any supports field to constrain its applicability, and according to the following, installing boost in any triplet should install it.
https://github.com/microsoft/vcpkg/blob/a106de33bbee694e3be6243718aa2a549a692832/ports/boost/vcpkg.json#L8
Make sure your vcpkg is up to date and try again after remove boost-uninstall.
If the problem persists, please provide full output.

@JackBoosY thanks, but can you maybe confirm the accumulators installed includes are present in the ci builds ?

@niclar See https://dev.azure.com/vcpkg/public/_build/results?buildId=71104&view=logs&j=7b75bd19-17d3-53d4-00fd-23f1a49a8ba4&t=a23dba4e-3a62-59dc-a73c-a7222676d7a4&l=7133

Nightly CI produces a file list which everyone can download. E.g.
https://dev.azure.com/vcpkg/public/_build/results?buildId=71377&view=artifacts&pathAsName=false&type=publishedArtifacts
boost-accumulators:x64-linux:/include/boost/accumulators/accumulators.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/accumulators_fwd.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/accumulator_base.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/accumulator_concept.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/accumulator_set.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/accumulators/droppable_accumulator.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/accumulators/external_accumulator.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/accumulators/reference_accumulator.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/accumulators/value_accumulator.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/depends_on.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/external.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/extractor.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/features.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/parameters/accumulator.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/parameters/sample.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/parameters/weight.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/framework/parameters/weights.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/detail/function1.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/detail/function2.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/detail/function3.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/detail/function4.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/detail/function_n.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/detail/pod_singleton.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/functional.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/functional/complex.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/functional/valarray.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/functional/vector.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/numeric/functional_fwd.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/count.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/covariance.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/density.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/error_of.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/error_of_mean.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/extended_p_square.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/extended_p_square_quantile.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/kurtosis.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/max.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/mean.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/median.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/min.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/moment.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/p_square_cumul_dist.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/p_square_cumulative_distribution.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/p_square_quantile.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/parameters/quantile_probability.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/peaks_over_threshold.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/pot_quantile.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/pot_tail_mean.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/rolling_count.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/rolling_mean.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/rolling_moment.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/rolling_sum.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/rolling_variance.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/rolling_window.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/skewness.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/stats.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/sum.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/sum_kahan.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/tail.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/tail_mean.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/tail_quantile.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/tail_variate.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/tail_variate_means.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/times2_iterator.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/variance.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/variates/covariate.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_covariance.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_density.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_extended_p_square.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_kurtosis.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_mean.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_median.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_moment.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_p_square_cumul_dist.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_p_square_cumulative_distribution.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_p_square_quantile.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_peaks_over_threshold.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_skewness.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_sum.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_sum_kahan.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_tail_mean.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_tail_quantile.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_tail_variate_means.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/weighted_variance.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics/with_error.hpp
boost-accumulators:x64-linux:/include/boost/accumulators/statistics_fwd.hpp
boost-accumulators:x64-linux:/share/boost-accumulators/copyright
boost-accumulators:x64-linux:/share/boost-accumulators/usage
boost-accumulators:x64-linux:/share/boost-accumulators/vcpkg_abi_info.txt

many thanks guys, the issue is obviously on my end (corrupt tree or something). keep up the invaluable job with this project


Not showing preview for some links

Why its not showing the preview for some links? like:
https://images.app.goo.gl/3pvZjPPU6GifxQJEA
https://twitter.com/KappaCane/status/1753216494454898862
While on the other platforms (like twitter, whatsapp, etc) its showing preview.

Hi, I have tried with the above-mentioned links & I was able to fetch the information in the example application.
I request you to run the example application.

Also, The first link which is provided is an image link & it doesn't seem to be a valid one.
I am closing the ticket as I can see it is working fine. Feel free to open this ticket if you face the issue after running with example code.


Website: order of remote API versions sorted incorrectly

When looking at the remote API, I noticed the links for the versions is sorted incorrectly:
v1.20 --> v1.21 --> v1.19

Tried looking at the docs in Github, but not sure where this resides?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

dup of  #15810, resolved by #15843

@MHBauer oh yeah, I should have check the master version of the docs, thanks :wink:
@charleswhchan gonna close this as it's already fix and will land next update of docs.docker.com I guess :wink:

Thanks.


Added Hungarian translation

Added Hungarian translation, and fixed some typing and sequence errors

Thank you for your contribution, I will check it over

Thanks for this.
@jeremypoulter , we probably should consider soon to host the translations outside of the firmware ( on GitHub? ) as it will fill-up the flash quickly.


Unify logging in xup/*

Follow-on pull request to #1633 which migrates all logging in the xup directory to use the LOG() and LOG_DEVEL() macros.
Changes:

Migrate logging to the LOG() and LOG_DEVEL() macros (using text transform script)
error logs use the LOG macro
update code formatting with astyle for all files in xup/*

@matt335672, I've implemented the feedback you suggested and review the log level for the rest of the log messages.
I'm still investigating the freebsd build failure when building the latest commit.

Thanks for that.
The FreeBSD build failure's a bit on the odd side. I've just tried re-running your job here:-
https://cirrus-ci.com/task/6336619461476352
It's still failing as of 2020-02-10 09:17 UTC
I need to find out more about FreeBSD anyway so I'll try knocking up a VM here and see what happens (it may take me a while). If it compiles fine locally we can at least carry on with other work for now. I agree that it seems very unlikely indeed to have anything to do with your PR.

Well I can confirm that your branch cloned with the following command builds fine on FreeBSD 12.2:-
git clone -b unify_logging_xup --depth 1 https://github.com/aquesnel/xrdp.git build

@metalefty - given the circumstances are you happy for me to merge this? Or do you want to wait until you've investigated further?

@aquesnel - please rebase to latest devel and squash. That should fix it, and then I can merge this in.
Thanks.

@matt335672 Thanks for fixing the issue with the FreeBSD build.
I've rebased and squashed the changes.

Great - thanks again!


Added extension SPV_VAL_ignore_type_decl_unique

If extension is present in the module, validator will ignore the "type
declaration must be unique" rule.

What's the motivation for this change?
The only risk with this is the namespace SPV_VAL_.    The schema for extensions is:

SPV_KHR_ for Khronos-ratified
SPV_EXT_ for multi company but not Khronos
SPV__ for a specific company

So "VAL" theoretically stomps on the namespace for a mythical company that wants "VAL".   Perhaps use "SPV_SPVTOOLS_"  to be more clear about it.

Type unique validator rule is disabled because it's failing vulkan cts tests. With this extension we can reenable it.
Could be SPV_VALIDATOR_.

Rebased, squashed, and pushed into master as 20fe94666


AWS - support sourcing credentials from a different profile

Platform or tool
AWS
Desired or expected behavior
AWS shell plugin should allow for sourcing a certain profile's credentials from another profile.
Current behavior
Currently AWS shell plugin supports long lived credential authentication, MFA and Assume Role support with temporary credentials authentication.
Relevant log output
No response
op CLI version
No response

Thank you to all who left feedback on this issue!

I need to manage multiple environments using Terraform, so this feature is crucial. The final work will be executed through CI/CD; however, I'd like to frequently check the progress in the terminal while working.

Since #180, commands like aws s3 ls --profile dev or export AWS_PROFILE=dev; aws s3 ls are supported by the AWS shell plugin, and all the assumed profile information will be extracted from your already existing .aws/config file (or $AWS_CONFIG_FILE).
From my understanding you are requesting support for the following scenario:
If you specify source_profile = production-profile in the config file under profile dev then profile dev should use the same root credentials as production-profile.
This could be achieved today without the source_profile = production-profile directive inside the config file, by doing op plugin init aws and selecting the 1Password item that stores production-profile's root credentials. Then when you are assuming your dev profile with aws s3 ls --profile dev you will be using your production-profile root creds.
Can you help me better discover your use case, and in which scenarios the explained solution above would fall short?

@AndyTitu Thanks for your reply.I commented because the error message was directing me to this issue.
I removed the source_profile as per your message and the profile switch was successful. Thanks for teaching me how to do this.
However, the call from terraform failed and I would like to know if there is a proper place for this issue.

This could be achieved today without the source_profile = production-profile directive inside the config file

This works for the aws cli but breaks other tools like sops since it's no longer able to determine the root credentials/keys.

@jarshwah , @fillz-noh and everyone else involved in this issue: We have just released our new beta  solution for the Terraform shell plugin. This allows AWS to work with Terraform out of the box, and also comes up with a general solution for authenticating terraform providers.

Hi
I don't know if I'm missing something else but I've been trying the beta (2.19.0-beta.01) in combination with an EKS, having set up just the op cli command and the aws plugin.
However, it's impossible for interacting with EKS using the current solution, it still seems to be requiring the source_profile. The full error output is:
Partial credentials found in assume-role, missing: source_profile or credential_source

Am I missing something or is an additional fix going to be required?

However, it's impossible for interacting with EKS using the current solution, it still seems to be requiring the source_profile. The full error output is:

Partial credentials found in assume-role, missing: source_profile or credential_source

@jandeschuttere thanks for sharing your use case! The first thing that comes to mind when seeing that error is that the shell-plugin is not actually wrapping the tools you are using to manage EKS. Can you please share the exact command(s)/script that you are running?

This happens with any of the commands interacting via kubectl because it's trying to authenticate first, the authentication process is unable to complete successfully.
When I looked closer into it it seems that the introduced shell-plugin is actually setting up an alias to wrap the 1pwd command, yet the kubectl config for EKS introduces an auth provider type "exec" (see https://kubernetes.io/docs/reference/access-authn-authz/authentication/#configuration)
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      command: aws
      args:
        - --region
        - ...

The alias is not able to override this behaviour. Perhaps a different config in the ~/.kube/config could be set up so that it can use the alias or introduce the wrapping logic the same way as that alias is doing but I was at least not able to easily do so.

@jandeschuttere Hey solved it by wrapping op command to kubeconfig like this:
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      command: op
      args:
      - plugin
      - run
      - --
      - aws
      - --region
      - ......


reboot not working: "Transport endpoint is not connected"

this is the output I get from kured:
{"log":"time=\"2018-08-07T13:27:21Z\" level=info msg=\"Kubernetes Reboot Daemon: master-5731b98\"\n","stream":"stderr","time":"2018-08-07T13:27:21.023797488Z"}
{"log":"time=\"2018-08-07T13:27:21Z\" level=info msg=\"Node ID: app02.lan.davidkarlsen.com\"\n","stream":"stderr","time":"2018-08-07T13:27:21.02386206Z"}
{"log":"time=\"2018-08-07T13:27:21Z\" level=info msg=\"Lock Annotation: kube-system/kured:weave.works/kured-node-lock\"\n","stream":"stderr","time":"2018-08-07T13:27:21.023876817Z"}
{"log":"time=\"2018-08-07T13:27:21Z\" level=info msg=\"Reboot Sentinel: /var/run/reboot-required every 1h0m0s\"\n","stream":"stderr","time":"2018-08-07T13:27:21.023889431Z"}
{"log":"time=\"2018-08-07T14:26:17Z\" level=info msg=\"Reboot required\"\n","stream":"stderr","time":"2018-08-07T14:26:17.381148603Z"}
{"log":"time=\"2018-08-07T14:26:17Z\" level=warning msg=\"Reboot blocked: 1 active alerts: [deployment_replicas_mismatch]\"\n","stream":"stderr","time":"2018-08-07T14:26:17.439989295Z"}
{"log":"time=\"2018-08-07T15:26:17Z\" level=info msg=\"Reboot required\"\n","stream":"stderr","time":"2018-08-07T15:26:17.381452887Z"}
{"log":"time=\"2018-08-07T15:26:22Z\" level=warning msg=\"Reboot blocked: 1 active alerts: [deployment_replicas_mismatch]\"\n","stream":"stderr","time":"2018-08-07T15:26:22.38692619Z"}
{"log":"time=\"2018-08-07T16:26:17Z\" level=info msg=\"Reboot required\"\n","stream":"stderr","time":"2018-08-07T16:26:17.381447461Z"}
{"log":"time=\"2018-08-07T16:26:17Z\" level=warning msg=\"Reboot blocked: 1 active alerts: [deployment_replicas_mismatch]\"\n","stream":"stderr","time":"2018-08-07T16:26:17.387051589Z"}
{"log":"time=\"2018-08-07T17:26:17Z\" level=info msg=\"Reboot required\"\n","stream":"stderr","time":"2018-08-07T17:26:17.381804597Z"}
{"log":"time=\"2018-08-07T17:26:17Z\" level=warning msg=\"Reboot blocked: 1 active alerts: [deployment_replicas_mismatch]\"\n","stream":"stderr","time":"2018-08-07T17:26:17.387159836Z"}
{"log":"time=\"2018-08-07T18:26:17Z\" level=info msg=\"Reboot required\"\n","stream":"stderr","time":"2018-08-07T18:26:17.381839419Z"}
{"log":"time=\"2018-08-07T18:26:17Z\" level=warning msg=\"Lock already held: app03.lan.davidkarlsen.com\"\n","stream":"stderr","time":"2018-08-07T18:26:17.953898535Z"}
{"log":"time=\"2018-08-07T19:26:17Z\" level=info msg=\"Reboot required\"\n","stream":"stderr","time":"2018-08-07T19:26:17.532210049Z"}
{"log":"time=\"2018-08-07T19:26:17Z\" level=warning msg=\"Reboot blocked: 1 active alerts: [deployment_replicas_mismatch]\"\n","stream":"stderr","time":"2018-08-07T19:26:17.778564028Z"}
{"log":"time=\"2018-08-07T20:26:17Z\" level=info msg=\"Reboot required\"\n","stream":"stderr","time":"2018-08-07T20:26:17.51315201Z"}
{"log":"time=\"2018-08-07T20:26:17Z\" level=warning msg=\"Reboot blocked: 1 active alerts: [deployment_replicas_mismatch]\"\n","stream":"stderr","time":"2018-08-07T20:26:17.950332758Z"}
{"log":"time=\"2018-08-07T21:26:17Z\" level=info msg=\"Reboot required\"\n","stream":"stderr","time":"2018-08-07T21:26:17.502508634Z"}
{"log":"time=\"2018-08-07T21:26:19Z\" level=info msg=\"Acquired reboot lock\"\n","stream":"stderr","time":"2018-08-07T21:26:19.041613032Z"}
{"log":"time=\"2018-08-07T21:26:19Z\" level=info msg=\"Draining node app02.lan.davidkarlsen.com\"\n","stream":"stderr","time":"2018-08-07T21:26:19.041639516Z"}
{"log":"time=\"2018-08-07T21:26:27Z\" level=info msg=\"node \\\"app02.lan.davidkarlsen.com\\\" cordoned\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:27.608428496Z"}
{"log":"time=\"2018-08-07T21:26:29Z\" level=warning msg=\"WARNING: Deleting pods with local storage: anchore-anchore-engine-anchore-engine-worker-55bc984d7-km7zx, flux-584d78b89f-xhrch, minio-minio-799cd646f-ks7qv, monocular-monocular-monocular-api-6747bb55c-httx5; Ignoring DaemonSet-managed pods: auditbeat-auditbeat-ffd58, datadog-datadog-agent-datadog-clqsm, calico-node-4kjvx, kube-proxy-6hmhz, kured-q7jkr, fluent-bit-thql4, monitoring-prometheus-node-exporter-xf4rj\" cmd=/usr/bin/kubectl std=err\n","stream":"stderr","time":"2018-08-07T21:26:29.263488783Z"}
{"log":"time=\"2018-08-07T21:26:30Z\" level=info msg=\"pod \\\"metrics-server-metrics-server-658d69ddf7-hwh7p\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:30.129399317Z"}
{"log":"time=\"2018-08-07T21:26:30Z\" level=info msg=\"pod \\\"minio-minio-799cd646f-ks7qv\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:30.132816317Z"}
{"log":"time=\"2018-08-07T21:26:30Z\" level=info msg=\"pod \\\"anchore-anchore-engine-anchore-engine-worker-55bc984d7-km7zx\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:30.143296645Z"}
{"log":"time=\"2018-08-07T21:26:30Z\" level=info msg=\"pod \\\"flux-584d78b89f-xhrch\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:30.143492166Z"}
{"log":"time=\"2018-08-07T21:26:30Z\" level=info msg=\"pod \\\"logging-elasticsearch-data-1\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:30.143637461Z"}
{"log":"time=\"2018-08-07T21:26:30Z\" level=info msg=\"pod \\\"anchore-anchore-engine-postgresql-5cd6586d5b-mp6d8\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:30.144007446Z"}
{"log":"time=\"2018-08-07T21:26:30Z\" level=info msg=\"pod \\\"logging-elasticsearch-master-1\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:30.144136576Z"}
{"log":"time=\"2018-08-07T21:26:31Z\" level=info msg=\"pod \\\"anchore-anchore-engine-anchore-engine-core-645cd6b7fd-2w4fs\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:31.950339088Z"}
{"log":"time=\"2018-08-07T21:26:31Z\" level=info msg=\"pod \\\"monitoring-prometheus-alertmanager-cbcc46d55-nkxkh\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:31.950422791Z"}
{"log":"time=\"2018-08-07T21:26:34Z\" level=info msg=\"pod \\\"kube-ops-view-kube-ops-view-kube-ops-view-6db67848c4-dfgqg\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:34.623470381Z"}
{"log":"time=\"2018-08-07T21:26:36Z\" level=info msg=\"pod \\\"monocular-monocular-monocular-ui-58f9f95864-qr7fm\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:36.040687921Z"}
{"log":"time=\"2018-08-07T21:26:36Z\" level=info msg=\"pod \\\"flux-memcached-5f8b4c7dc8-l6b5t\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:36.199982135Z"}
{"log":"time=\"2018-08-07T21:26:36Z\" level=info msg=\"pod \\\"tiller-deploy-5c688d5f9b-v2hbx\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:36.200033975Z"}
{"log":"time=\"2018-08-07T21:26:36Z\" level=info msg=\"pod \\\"kube-system-kubernetes-dashboard-proxy-64f7674f88-c97m4\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:36.200053208Z"}
{"log":"time=\"2018-08-07T21:26:36Z\" level=info msg=\"pod \\\"kube-system-heapster-heapster-56c646d674-87ptg\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:36.688737532Z"}
{"log":"time=\"2018-08-07T21:26:36Z\" level=info msg=\"pod \\\"logging-elasticsearch-client-5978d8f465-dr6ft\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:36.688776421Z"}
{"log":"time=\"2018-08-07T21:26:37Z\" level=info msg=\"pod \\\"monocular-monocular-monocular-prerender-6ffdcd79c4-cfs8n\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:37.402532532Z"}
{"log":"time=\"2018-08-07T21:26:37Z\" level=info msg=\"pod \\\"monitoring-prometheus-server-75bfb9f66-wxmq5\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:37.402572959Z"}
{"log":"time=\"2018-08-07T21:26:37Z\" level=info msg=\"pod \\\"monitoring-prometheus-blackbox-exporter-7775df5698-cw49s\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:37.403119108Z"}
{"log":"time=\"2018-08-07T21:26:37Z\" level=info msg=\"pod \\\"hubot-hubot-d7dc4978c-f48nz\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:37.403141351Z"}
{"log":"time=\"2018-08-07T21:26:37Z\" level=info msg=\"pod \\\"monocular-monocular-monocular-api-6747bb55c-httx5\\\" evicted\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:37.403189515Z"}
{"log":"time=\"2018-08-07T21:26:37Z\" level=info msg=\"node \\\"app02.lan.davidkarlsen.com\\\" drained\" cmd=/usr/bin/kubectl std=out\n","stream":"stderr","time":"2018-08-07T21:26:37.403202192Z"}
{"log":"time=\"2018-08-07T21:26:37Z\" level=info msg=\"Commanding reboot\"\n","stream":"stderr","time":"2018-08-07T21:26:37.406949235Z"}
{"log":"time=\"2018-08-07T21:26:42Z\" level=warning msg=\"Error notifying slack: Post https://hooks.slack.com/services/obfuscated/obfuscated/obfuscated: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\"\n","stream":"stderr","time":"2018-08-07T21:26:42.407467437Z"}
{"log":"time=\"2018-08-07T21:27:16Z\" level=warning msg=\"Failed to set wall message, ignoring: Connection reset by peer\" cmd=/bin/systemctl std=err\n","stream":"stderr","time":"2018-08-07T21:27:16.609804186Z"}
{"log":"time=\"2018-08-07T21:27:16Z\" level=warning msg=\"Failed to reboot system via logind: Transport endpoint is not connected\" cmd=/bin/systemctl std=err\n","stream":"stderr","time":"2018-08-07T21:27:16.609844005Z"}

running image:
image: quay.io/weaveworks/kured:master-5731b98

I have seen that warning message intermittently, but then it rebooted anyway. If that wasn't the case here, it might be because of an incompatibility between the systemctl bundled with kured (16.04) and your distro (18.04.1). I'm working on a change that will use the systemctl from the host mount namespace which should address this!

@davidkarlsen could you try again with https://github.com/weaveworks/kured/releases/tag/1.1.0 and see if you have better luck?


Download a complete BCO draft saves an empty file

null

Replicated (partially?)--> saved incomplete draft---> #92


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2596

Questions ?
Please refer to the Backport tool documentation


Result in UTF-8

Hi,
Is there any setting to set result in UTF-8?
I execute this command:
curl http://wiki.seg.org/wiki/Dictionary:Deconvolution | pup div#mw-content-text
it gives me some weird characters.
i.e.
(de kon vō’ lū sh∂n) is translated as       â lÅ« shân) kon vÅ
(1995, 285 and 292–303) is translated as (1995, 285 and 292â303)
Thanks

I still have problems with 'and & (and probably more) being converted (I'm on 0.3.8):
$ echo "ŷhat & alert('hi')" | pup text{}
ŷhat & alert('hi')

$ echo "ŷhat & alert('hi')" | pup text{} --charset utf8
ŷhat & alert('hi')

Shouldn't the result be this?:
ŷhat & alert('hi')

And we get double-encoding when outputting json:
$ echo "ŷhat & alert('hi')" | pup json{} // same with --charset utf8
{
 "children": [
  {
   "tag": "head"
  },
  {
   "tag": "body",
   "text": "ŷhat \u0026amp; alert(\u0026#39;hi\u0026#39;)"
  }
 ],
 "tag": "html"
}

Is there a way to avoid this?
Thanks,
Marc

By default, pup escapes all HTML. You can use the '-p' or '--plain' to skip that escaping.
$ echo "ŷhat & alert('hi')" | pup -p text{}
ŷhat & alert('hi')

Excellent! Thanks for this wonderful tool!


[HW]  Ashwani Ranjan

Name: Ashwani Ranjan
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/ashwani-ranjan-972046216
Attach the homework step I screenshots below:

Attach the homework step II screenshots below:

Looks great, Ashwani! Thanks for your submission. We'll get a badge out to you shortly.

Hey Ashwani Ranjan, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/-_kBGrXvTNSsQ7rXjtiqCw


added --stdout option to write downloaded video to STDOUT instead of a file

enables use of youtube-dl to stream video to vlc, mplayer etc through a pipe, e.g.
youtube-dl --stdout http://some.url | vlc -

I don't think that option is needed. You can use "-o -" to output the file to stdout, like in many other command line tools.

As @rg3 said, -o - should work already. Unless there is a compelling reason to have --stdout instead, we won't add yet another option.


[docker backend] - Add config flag to set refreshSeconds for swarmmode ticker

What does this PR do?
This PR allow user to set a custom refresh interval for polling swarm mode socket for docker backend
The default value is 15
The new flag to set in config is --docker.refreshSeconds

Could you rebase on v1.7?

Thanx for taking this !


Is there any way to make this as Angular (or other frameworks) compatible?

Unfortunately, as a React and non-Angular developer, this package is designed to work in react. If you are interested in creating an Angular package, feel free to reference the blog post outlining the underlying geometry and math. https://codeburst.io/deconstructing-the-iconic-apple-watch-bubble-ui-aba68a405689


My Application.java iunabvle to locate import com.learnium.RNDeviceInfo.RNDeviceInfo; even after following the steps mentioned at https://github.com/rebeccahughes/react-native-device-info

I'm having the same issue.
    "react-native": "0.41.2",
    "react-native-device-info": "^0.9.9",

MainApplication.java:7: error: package com.learnium.RNDeviceInfo does not exist
import com.learnium.RNDeviceInfo.RNDeviceInfo;
                                ^

Is this still happening with 0.14.0 ?

Closing this stale issue. Please open a new one if you're still facing this problem.


Fix screenshot name escaping

Signed-off-by: Luca Giorgi<EMAIL_ADDRESS>

@LaVLaS could you check if this looks good and merge if so?


Try sidecar mode to mount juiceFS but failed to call webhook

I uninstalled the previously installed juiceFS using helm install, and followed the steps in this Bilibili video to install juiceFS and try mounting a shared file to a Pod using sidecar mode.
$ helm uninstall juicefs-csi-driver -n kube-system
release "juicefs-csi-driver" uninstalled

$ kubectl get pods -A
NAMESPACE                        NAME                                                   READY   STATUS        RESTARTS   AGE
kube-system                      juicefs-csi-controller-0                               4/4     Terminating   0          2d18h
kube-system                      juicefs-csi-controller-1                               4/4     Terminating   0          2d18h

After successfully deleting the juicefs-csi-controller-* pod, install the JuiceFS CSI driver using kubelet.
$ kubectl label namespace default juicefs.com/enable-injection=true --overwrite
namespace/default not labeled

$ wget https://raw.githubusercontent.com/juicedata/juicefs-csi-driver/master/scripts/juicefs-csi-webhook-install.sh
$ chmod +x ./juicefs-csi-webhook-install.sh

$ ./juicefs-csi-webhook-install.sh install
serviceaccount/juicefs-csi-controller-sa created
clusterrole.rbac.authorization.k8s.io/juicefs-external-provisioner-role unchanged
clusterrolebinding.rbac.authorization.k8s.io/juicefs-csi-provisioner-binding created
secret/juicefs-webhook-certs created
service/juicefs-admission-webhook created
statefulset.apps/juicefs-csi-controller created
csidriver.storage.k8s.io/csi.juicefs.com unchanged
mutatingwebhookconfiguration.admissionregistration.k8s.io/juicefs-admission-webhook created

Finally, create k8s secret, pv/pvc, pod in order and verify the running status of the pod and file mounting situation.
k8s_secret.yaml
apiVersion: v1
kind: Secret
metadata:
  name: juicefs-secret
type: Opaque
stringData:
  name: myjfs
  metaurl: redis://<IP_ADDRESS>:6379/1
  storage: minio
  bucket: http://<IP_ADDRESS>:9000/juicefs
  access-key: minioadmin
  secret-key: minioadmin

pvc_pv.yaml
apiVersion: v1
kind: PersistentVolume
metadata:
  name: juicefs-pv
  labels:
    juicefs-name: ten-pb-fs
spec:
  capacity:
    storage: 10Pi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  csi:
    # 在先前的安装步骤中，已经创建了名为 csi.juicefs.com 的 CSIDriver
    driver: csi.juicefs.com
    # volumeHandle 需要保证集群内唯一，因此一般直接用 PV 名即可
    volumeHandle: juicefs-pv
    fsType: juicefs
    # 在先前的步骤中已经创建好文件系统认证信息（Secret），在这里引用
    # 如果要在静态配置下使用不同的认证信息，甚至使用不同的 JuiceFS 文件系统，则需要创建不同的 Secret
    nodePublishSecretRef:
      name: juicefs-secret
      namespace: default
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: juicefs-pvc
  namespace: default
spec:
  accessModes:
    - ReadWriteMany
  volumeMode: Filesystem
  # 静态配置下必须指定 storageClassName 为空字符串
  # 代表该 PV 不采用任何 StorageClass，而是直接使用 selector 所指定的 PV
  storageClassName: ""
  # 由于目前 JuiceFS CSI 驱动不支持给静态 PV 设置存储容量，此处 requests.storage 填写任意小于 PV capacity 的有效值即可
  resources:
    requests:
      storage: 10Pi
  selector:
    matchLabels:
      juicefs-name: ten-pb-fs

pod.yaml
apiVersion: v1
kind: Pod
metadata:
  name: juicefs-app
  namespace: default
spec:
  #runtimeClassName: kata-qemu-tdx
  containers:
  - args:
    - -c
    - while true; do echo $(date -u) >> /data/out.txt; sleep 5; done
    command:
    - /bin/sh
    image: centos
    securityContext:
        privileged: true
    name: app
    volumeMounts:
    - mountPath: /data
      name: data
    resources:
      requests:
        cpu: 10m
  volumes:
  - name: data
    persistentVolumeClaim:
      claimName: juicefs-pvc

secret, pvc has been successfully deployed. When starting to deploy the pod, k8s reported the following error:
$# kubectl apply -f pod.yaml
Error from server (InternalError): error when creating "pod.yaml": Internal error occurred: failed calling webhook "sidecar.inject.juicefs.com": failed to call webhook: Post "https://juicefs-admission-webhook.kube-system.svc:443/juicefs/inject-v1-pod?timeout=20s": Service Unavailable

hi @junruizh2021 , can you provide the log of juicefs-csi-controller-0 and juicefs-csi-controller-1 ?

hi @junruizh2021 , can you provide the log of juicefs-csi-controller-0 and juicefs-csi-controller-1 ?

Sure, the logs of two controller pods are here.
(base) # kubectl apply -f static_pod.yaml
Error from server (InternalError): error when creating "static_pod.yaml": Internal error occurred: failed calling webhook "sidecar.inject.juicefs.com": failed to call webhook: Post "https://juicefs-admission-webhook.kube-system.svc:443/juicefs/inject-v1-pod?timeout=20s": Service Unavailable

(base) # kubectl logs juicefs-csi-controller-0 -n kube-system
Defaulted container "juicefs-plugin" out of: juicefs-plugin, csi-provisioner, csi-resizer, liveness-probe
I0810 07:25:57.231221       7 main.go:90] Run CSI controller
I0810 07:25:57.231333       7 driver.go:48] Driver: csi.juicefs.com version v0.20.1-10-gfa446b7 commit fa446b77d165ba2cb7e15b3035b438b947c33e65 date 2023-07-13T12:50:42Z
I0810 07:25:57.243854       7 driver.go:113] Listening for connection on address: &net.UnixAddr{Name:"/var/lib/csi/sockets/pluginproxy/csi.sock", Net:"unix"}
I0810 07:25:57.384488       7 webhook.go:105] Register webhook handler
I0810 07:25:57.384563       7 register.go:35] Registered webhook handler path /juicefs/inject-v1-pod
I0810 07:25:57.384568       7 webhook.go:112] Register app controller
I0810 07:25:57.384600       7 webhook.go:95] Webhook manager started.
I0810 07:25:57.384736       7 leaderelection.go:248] attempting to acquire leader lease kube-system/webhook.juicefs.com...
I0810 07:26:14.972519       7 leaderelection.go:258] successfully acquired lease kube-system/webhook.juicefs.com

(base) # kubectl logs juicefs-csi-controller-1 -n kube-system
Defaulted container "juicefs-plugin" out of: juicefs-plugin, csi-provisioner, csi-resizer, liveness-probe
I0810 07:25:58.229226       7 main.go:90] Run CSI controller
I0810 07:25:58.229327       7 driver.go:48] Driver: csi.juicefs.com version v0.20.1-10-gfa446b7 commit fa446b77d165ba2cb7e15b3035b438b947c33e65 date 2023-07-13T12:50:42Z
I0810 07:25:58.245230       7 driver.go:113] Listening for connection on address: &net.UnixAddr{Name:"/var/lib/csi/sockets/pluginproxy/csi.sock", Net:"unix"}
I0810 07:25:58.383393       7 webhook.go:105] Register webhook handler
I0810 07:25:58.383486       7 register.go:35] Registered webhook handler path /juicefs/inject-v1-pod
I0810 07:25:58.383490       7 webhook.go:112] Register app controller
I0810 07:25:58.383528       7 webhook.go:95] Webhook manager started.
I0810 07:25:58.383659       7 leaderelection.go:248] attempting to acquire leader lease kube-system/webhook.juicefs.com...

It seems no request to CSI Controller. Can you provide the audit log of ApiServer that time? BTW, did you use cert-manager in your cluster?

It seems no request to CSI Controller. Can you provide the audit log of ApiServer that time? BTW, did you use cert-manager in your cluster?

No, I didn't use cert-manager in the k8s cluster.

Can you provide the audit log of ApiServer that time?

kubectl logs juicefs-csi-controller-1 -n kube-system

Sure, I'm busy for other things. I'll sent out the audit log of apiserver soon.

I reinstall the csi driver with sidecar mode and open the api server's audit log. k8s secret, pv and pvc are created successfully. When I deploy the sidecar pod, it occured the new error message:
Events:
  Type     Reason       Age              From               Message
  ----     ------       ----             ----               -------
  Normal   Scheduled    5s               default-scheduler  Successfully assigned default/juicefs-app to tdx-master
  Warning  FailedMount  2s (x4 over 5s)  kubelet            MountVolume.MountDevice failed for volume "jfs-juicefs-pv" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name csi.juicefs.com not found in the list of registered CSI drivers

The complete audit log is uploaded in Google Drive. https://drive.google.com/file/d/1odzi4Es4nd0mwgVWXhsdoDZGQU-u6c_q/view?usp=sharing

It seems not reproduce this issue. Application pod will not be created. Did you add label juicefs.com/enable-injection=true in namespace?

Thanks, I missed it. After added label juicefs.com/enable-injection=true in namespace, when I deploy the sidecar pod, the issue is reproduced.
(base) [root@tdx-master csi_config]# kubectl apply -f sidecar.yaml
Error from server (InternalError): error when creating "sidecar.yaml": Internal error occurred: failed calling webhook "sidecar.inject.juicefs.com": failed to call webhook: Post "https://juicefs-admission-webhook.kube-system.svc:443/juicefs/inject-v1-pod?timeout=20s": Service Unavailable

The new complete audit log is uploaded in Google Drive. Part of the log should be a duplicate of the previous audit log.
https://drive.google.com/file/d/1kn1WpfcO4-zeP2ABSAs4ZNEW3nVaUCpY/view?usp=sharing

@zwwhdls Thanks for your support. This is a problem caused by internal company agents.
I added the no_proxy in proxy file of kubelet and containerd. It's worked!


Clarify vector-immediate shift instruction behavior

The shift amount is described in the following chapters

12.5. Vector Single-Width Bit Shift Instructions
Only the low lg2(SEW) bits are read to obtain the shift amount.
The immediate is treated as an unsigned shift amount, with a maximum shift amount of 31.
12.6. Vector Narrowing Integer Right Shift Instructions
The shift amount can come from a vector or a scalar x register or a 5-bit immediate. The low lg2(2*SEW) bits of the vector or scalar shift amount value are used (e.g., the low 6 bits for a SEW=64-bit to SEW=32-bit narrowing operation). The unsigned immediate form supports shift amounts up to 31 only.
13.5. Vector Single-Width Scaling Shift Instructions
The low lg2(SEW) bits of the vector or scalar shift amount value are used. The immediate form supports shift amounts up to 31 only
13.6. Vector Narrowing Fixed-Point Clip Instructions
The low lg2(2*SEW) bits of the vector or scalar shift amount value are used (e.g., the low 6 bits for a SEW=64-bit to SEW=32-bit narrowing operation). The immediate form supports shift amounts up to 31 only.

The shift amount has several explanations in the above chapters. For vector shift instructions, Does vector-immediate shift instructions follow the constraint that is "{lg2(SEW)/lg2(2*SEW)} bits are used"?
e.g.
SEW = 8, lg2(SEW) = 3
A.
    vsra.vi   v16, v8, 26 # 26(0x1a)   v2[i] = v1[i] >> 2
    vnsra.vi  v16, v8, 26 # 26(0x1a)   v2[i] = v1[i] >> 10 (0xa)
    vssra.vi  v16, v8, 26 # 26(0x1a)   v2[i] = v1[i] >> 2
    vnclip.vi v16, v8, 26 # 26(0x1a)   v2[i] = v1[i] >> 10 (0xa)
B.
    vsra.vi   v16, v8, 26 # v2[i] = v1[i] >> 26(0x1a)
    vnsra.vi  v16, v8, 26 # v2[i] = v1[i] >> 26(0x1a)
    vssra.vi  v16, v8, 26 # v2[i] = v1[i] >> 26(0x1a)
    vnclip.vi v16, v8, 26 # v2[i] = v1[i] >> 26(0x1a)

Which one is correct?

It's option A.  I don't find the current spec to be ambiguous in this respect.  Remarks like "only the low lg2(SEW) bits" apply to immediate arguments just the same as they apply to dynamic arguments.

Clear
Thank you all.


null values in ng-model after changing ng-model programmatically on multiselect

version 0.11.1
Demo http://plnkr.co/edit/kLsFtY?p=preview
settings multiselect, complex ui-select-choices objects
Issue
When ng-model is empty and I'm programmatically changing ng-model values, it changes ng-model to null. When ng-model is not empty and I'm changing values programmatically it works fine. That's why when you click on the button on my demo second time (or you choose any value manually using UI), the values are set correctly.
FIX
PR: https://github.com/angular-ui/ui-select/pull/740

I got into some trouble when modifying the model outside of ui-select too
http://plnkr.co/edit/Wboo1fiePaLHKX0eHjxI?p=preview
It looks like it's more of a one way binding than a 2 ways : adding / removing elements with ui-select works well, but the digest cycle of the directive is not always triggered.

I have the same proble than Kris Kesy

+1 We are having the same problem. Spent quite a bit of time tracking this down.

+1

+1

+1

+1

We are also having the same issue. When is this pull request likely to be merged in?

Should be fixed with #748


WiFi auto connect at boot time doesn't seem to work

My goal is to configure once wifi SSID and PASSWORD, then ESP32 can automatically connect to target access point after start up.
I set first esp wifi storage type to save settings into flash by esp_wifi_set_storage(WIFI_STORAGE_FLASH)  , then activate auto connect by esp_wifi_set_auto_connect(true). Finally configure settings by esp_wifi_set_config(). It can connect correctly to the target AP when testing my settings. However after reboot, the auto connect is not triggered!
I searched in ESP32 forum and people guide me to have a look at kolban-ESP32 (https://leanpub.com/kolban-ESP32), but in his book, he exactly use the same idea (To see the section WiFi at boot time). But from my test,  it doesn't work.
Additionally I understood this concept from ESP8266 and it works very well for ESP8266 with the same approach. So I'm thinking there may be something missing in SDK. Could you have a look at this issue?

Hi @huibo-shi,
Could you post a code snippet (using e.g. gist) to reproduce this issue?
This will make it easier to check it out.

@huibo-shi You can check this code, it should work
https://github.com/nkolban/esp32-snippets/tree/master/networking/bootwifi

Hi @huibo-shi , did the above suggestion help you resolve the issue?

Hi @krzychb Thanks for your reply. I will try to do it as soon as possible.

Hi @chegewara and @FayeY  Thanks for the suggestion. The bootwifi example stores wifi ssid and password into flash and call connect with this credentials to wifi manually after start up. This is a solution I also used to temporarily make my project moving on. But it doesn't use the SDK APIs to solve this scenario.
If I understand correctly, combination usage of esp_wifi_set_storage(WIFI_STORAGE_FLASH) esp_wifi_set_auto_connect(true) and esp_wifi_set_config() should do the trick. Those APIs should be designed to do a such mission. What I wanted is to connect to wifi AP automatically after boot by using SDK APIs.
In fact after these days' tests, I finally find out a solution by using SDK APIs. When initialize the main program after boot, I call first esp_wifi_get_auto_connect to check whether auto connect is activated, if yes, then call esp_wifi_get_config to retrieve wifi configuration data. If retrieved SSID and password are not NULL. then I enable station mode and call esp_wifi_start and esp_wifi_connect.
I think maybe you can improve bootloader to automatize this process.

@huibo-shi  currently esp_wifi_set_auto_connect has no effect to the connection, we will mark this API s obsolete API. Please following @heyinling 's suggestion to auto connect.

Closing due to lack of response, please feel free to reopen if this is still an issue.

@liuzfesp what is the alternative solution to make auto connect as esp_wifi_set_auto_connect is deprecated and @heyinling solution is based on esp_wifi_get_auto_connect which is deprecated as well?

HI @my-abousamra, call esp_wifi_connect after received event SYSTEM_EVENT_STA_DISCONNECTED

@liuzfesp I mean after start up, how to make a wifi connection based on configuration stored in flash using esp_wifi_set_storage(WIFI_STORAGE_FLASH) where esp_wifi_get_auto_connect is deprecated now

@my-abousamra , we mark esp_wifi_get/set_auto_connect as obsolete because they lead to some misunderstanding, most of the users think they don't need to call esp_wifi_connect once esp_wifi_set_auto_connect(true) after the system startup, but actually the esp_wifi_set_auto_connect() only set the auto_connect flag, that's why we mark it as obsolete. If the application want to store the auto connect flag into flash, they need to handle it themselves.

HI @my-abousamra, do you think removing esp_wifi_set_auto_connect makes application programming more hard?

I use the function to switch off auto connect! At the moment I get a warning during compilation...what should I use instead?

By the way: I think you should remove the auto connection stuff. I do not see any reason for it. If auto connect is requured it can be done with some lines of code in app_main

@Reiner1210 yes, I think so. For the documents, I will create another MR to update it.

Hi @liuzfesp, For easy application programming esp-idf should have a clear and easy way to auto connect to wifi after start up based on saved credentials (I'm not talking about reconnect to wifi if the connection lost as it easy to do) so if you removed esp_wifi_set_auto_connect you should give an alternative for it and I don't find it. If there is an alternative function or method to it please inform us. Updating documents is a great idea.

@Reiner1210 If you have a way to auto connect after start up based on saved credentials please inform me

@my-abousamra It's so easy !!!
The user gives SSIP / password via terminal / Webform or whatever you have designed .... values are stored in nvs Flash. in app_main I read this values - and if not empty I use to connect - voila .....autoconnect on boot

@Reiner1210 I was thinking a way using wifi functions (like the esp_wifi_set_auto_connect, .. etc), Any way thank you!

It appears that auto-connect is active by default, and the function to deactivate it has been marked deprecated. That's actually quite a good practical joke, because I actually don't want it, and now ended up with a deprecated warning that I cannot even patch away because it sits in libnet80211.a. So I kindly ask to change the default auto-connect state to inactive. Thanks!


Can I put a .container in my container?

In this case, the bootstrap container acts as a container of content, and mine as the container parent is the maximum width of the site.
For example:
There is a 800px wide layout, the content itself is inside - 590px (the maximum width of the media container has been changed).

Text

Text

Why is that: sections are unique and have their own background and border.
The key question is: can this be done or is it a bad practice?

There's nothing wrong with it, you can do this if you wish.

There's nothing wrong with it, you can do this if you wish.

Thank

Since containers have max-width, you're fine, but you may end up with nested horizontal padding and extraneous markup: https://codepen.io/anon/pen/xoLjKQ. But that's only if you're using our built-in containers.


Show touches while recording

Enable developer settings 'Show touches' options while recording.
Even though with Lollipop we have touch hints for visual feedback (ripples), there are still some missing like swipe and multitouch gestures.

See #40 for a possible implementation.

d1ac7ea6c4e7cd4a30df9a07e72bbb9e2355b73e


subtype() should be subtypes()

In section 1.1:
...while the functions subtype() and supertype() return the subtype and supertype of a particular type respectively...
I believe the correct function name is subtypes()  <-- plural

Fixed, thank you.


fix: command failed timed out

This tries to fix #144.

@PF4Public could you try with this version? You can download the vsix in the release job, under Artifacts.

I just tried and it works. Reloaded project a number of times, reopened vscode a number of times, but it still works without a flaw. Awesome!

I prefer not to increase the timeout unless needed.

I understand and share this concern.
Tested again, all is fine still. Just to be certain that extension was changed after reinstalling vsix, opened extension.bundle.js of the extension in editor:

Looks good.

Awesome!


Fix volume scrolling.

Broke after a wear compose update.
Tracked in https://b.corp.google.com/issues/226089343

https://user-images.githubusercontent.com/231923/159471881-9c5016c0-17de-41f1-b4bc-6dc276c9da07.mp4

Will revert after the release of Alpha19


Custom firmware for ESP based roombas

Thanks to Service Port and esp8266 we can connect virtually any roomba to homeassistant. Currently there are few options how to do it like here (mqtt depencency) or with esphome (esphome dependency) but I was thinking how cool it well be to just flash some custom firmware to esp8266 and use the built in roomba addon.
After brief look over the code and I don't think, that it is impossible. The most important thing to implement, as I see it, will be:

running MQTT Broker in esp8266
emulate roomba discovery service on port 5678
somehow deal with tls connection in esp8266, because this library forces tls connection
emulate roomba MAC address on esp8266

My questions to you are:

Can this library use plain instead of TLS connection?
Can the mapping feature be disabled? What if I don't send the values? Do I have to feed it with dummy values?
which QoS level is used during sub and pub?
is here something what I overlook and could be potential hurdle while creating the custom firmware?

Hi @rforro

Can this library use plain instead of TLS connection?

As of now, no and to be entirely honest with you I won't merge any PR that would make that possible.
roombapy targets iRobot Roomba devices that are running the original firmware only.

Can the mapping feature be disabled? What if I don't send the values? Do I have to feed it with dummy values?

What mapping feature? o:)
Most of the mapping stuff from https://github.com/NickWaterton/Roomba980-Python should have been removed. Roombapy does not support mapping.

which QoS level is used during sub and pub?

No idea, sorry.

is here something what I overlook and could be potential hurdle while creating the custom firmware?

The password/BLID retrieval perhaps? :shrug:

Thanks for fast reply.

As of now, no and to be entirely honest with you I won't merge any PR that would make that possible.
roombapy targets iRobot Roomba devices that are running the original firmware only.

I don't want to do any modification to the code base on this repo, because if I do, there will be no compatibility with other home automation systems like for example openhab.

What mapping feature? o:)
Most of the mapping stuff from https://github.com/NickWaterton/Roomba980-Python should have been removed. Roombapy does not support mapping.

I saw this and this line of code an thought that the mapping is supported. Now it makes sense why I also found some posts on hass forum, where people are complaining that the mapping function don't work :D

The password/BLID retrieval perhaps? 🤷

Yes you're right, I forgot about that. The procedure isn't that complicated, but it goes over TLS, which can cause headaches. Will see.
Thanks again.


Automate Nightly Builds of test servers

It could be beneficial to automate nightly builds, or builds for whenever the commit hash has changed on develop branch.
Maybe just on one of the two severs? Maybe on both.
Until dbtool-v5 is out, we will have to wipe DB for schema changes.

Getting really excited planning this out!


Flag Mismatch When Switching Between Turkey and Kazakhstan

Description:
There is an issue with flag display when switching between Turkey and Kazakhstan. Currently, when Turkey is selected as the default country and then Kazakhstan is chosen for the first time, the flag displayed is that of Turkey, instead of Kazakhstan. Subsequently selecting Kazakhstan again does display the correct Kazakhstan flag.
Steps to Reproduce:

Select Turkey as the default country.
Choose Kazakhstan from the country selection dropdown for the first time.
Observe that the flag displayed is that of Turkey, not Kazakhstan.
Now, select Kazakhstan again from the dropdown.
Notice that only on the second selection, the Kazakhstan flag is displayed correctly.

+90 is the country code for Turkey and +7 is the country code for Kazakistan. As seen in the photo, Turkey flag is shown when Kazakistan is chosen.

Hello @mkontik
https://github.com/viclafouch/mui-tel-input/assets/23353836/1c328f7f-ec39-4d0c-b08b-0e4871f6c28a
On my side, it's working fine. I select Kazakhstan from the country selection dropdown for the first time, I have correclty the Kazakhstan flag

Hello Victor,
Thank you for your reply.
We use the following code line and face the issue for +7 Kazakistan and just recognized +1 for US either. Country code for Turkey is +90. It seems when switching from two digit to one digit country we face the issue I send you.
const countries: MuiTelInputCountry[] = [
"US",
"BR",
"DZ",
"CN",
"ID",
"IN",
"JP",
"KZ",
"HU",
"MX",
"NG",
"PL",
"RO",
"TH",
"TR",
"VN",
];
<MuiTelInput
variant="standard"
size="small"
id={item.id + "Id"}
label={t(item.title)}
value={getValues(item.id)}
fullWidth
onChange={(value: any) => {
setValue(item.id, value, { shouldValidate: true });
}}
defaultCountry="TR"
onlyCountries={countries}
langOfCountryName={i18n.language}
/>

On 11 Oct 2023, at 16:12, Victor de la Fouchardière @.***> wrote:
Hello @mkontik https://github.com/mkontik
https://github.com/viclafouch/mui-tel-input/assets/23353836/1c328f7f-ec39-4d0c-b08b-0e4871f6c28a
On my side, it's working fine. I select Kazakhstan from the country selection dropdown for the first time, I have correclty the Kazakhstan flag
—
Reply to this email directly, view it on GitHub https://github.com/viclafouch/mui-tel-input/issues/92#issuecomment-1757675344, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATA27TI5PNZHFF2PPOVKO2TX62LNDANCNFSM6AAAAAA4UR6XYU.
You are receiving this because you were mentioned.

Yes because the phone library libphonenumber-js needs more info to be sure what country is it..

We tried changing several parameters and fixed the issue. Thanks for the response.

On 12 Oct 2023, at 15:56, Victor de la Fouchardière @.***> wrote:
Yes because the phone library libphonenumber-js needs more info to be sure what country is it..
—
Reply to this email directly, view it on GitHub https://github.com/viclafouch/mui-tel-input/issues/92#issuecomment-1759561357, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATA27TNDJBWWE2DP3S6GUYLX67SGNANCNFSM6AAAAAA4UR6XYU.
You are receiving this because you were mentioned.

We tried changing several parameters and fixed the issue. Thanks for the response.


Adding advertisement recoginition in popups.

Adding advertisement recoginition in popups using support vector machine(SVM).

@4darsh-Dev Please assign this issue to me under GSSoc'24.

@Akanksha4554 How are you planning to solve this issue, please explain briefly.
Sorry for delay response, join our  project discord channel in gssoc to stay connected

Hey @4darsh-Dev ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @4darsh-Dev ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

GSSoC 24 has been completed Finally'
It was a great experience working with you all
Thanks💗 for your valuable contributions!
PA nomination has been started, Do fill out the forms soon. Share your experiences and let's connect on socials


Only one player at time can join

For some reason only one player at time can join the limbo, else velocity will kick the new player saying the server is not accessible
I have configured the limbo to allow a maximum of 20 players, which is enough, but in reality it only allows one

Could you write a detailed explanation of the steps you went through to get that behavior? It'll be easier for others to help if they have a way of recreating the problem themselves and looking for potential problems that way.


Update description of SonarQube

Include security scanning, because that's what we do !

Sure thing ! Done !


Interface segregation for session classes

The objects returned from launch_fluent() etc should have a public interface that only contains what we want users of the library to call, and not any additional public methods intended for the implementation, such as the class-level factory method create_from_server_info_file(). To deal with that issue, we might make it a (standalone) function in the launcher code or just make it private in BaseSession (but still call it from launcher code).

make create_from_server_info_file() private

settings_service can be made private

events_service can be made private

error_state? It seems that it should be private - I can't find where it's actually used

remove svar_* from the dir() results and still support usage for backwards compatibility

make private: set_file_transfer_service(), set_flproxy(), file_transfer_service, while_xxx(), unalias() in each settings node

I'm tempted to say that 'field_data', 'field_data_streaming', 'field_info', 'solution_variable_data', and 'solution_variable_info' could all be held under a single node, say fields. That's a lot of separate items.

Conversely:

solver._root should actually be explicitly public

I have added two assignees. @prmukherj is looking for tasks.

Following from a Fluent side defect - solver.fluent_connection can also be made private


error:timeout: no recent network activity

When I try to run the client, I got an error:
2022-02-18T15:36:59+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client

Please note that Google Cloud Platform has its own firewall which allows traffic of TCP ports 22, 80, 443 while blocking all UDP traffic by default.
To check the connectivity of UDP, you can use nc(1) (run it in UDP mode with -u) or iperf3(1) (run it in UDP mode with -u), both of these tools are available on the Arch Linux as community/openbsd-netcat and community/iperf3.


Update index.js

To support ES5 env, because you don't build your code before publish to npm, pls merge it

@thejameskyle


💄(UI) Registraion and login error fixes and updates

Au pairs need to have fields for bio and experience so the admin can view why they want to be an au pair and their qualifications


[request] Append gitHead to package.json

Currently published @types packages don't include git revision of DefinitelyTyped repo, so we cannot get to know the exact diff between previous version and new one without actually comparing downloaded packages.
npm publish appends gitHead field to package.json: https://github.com/npm/read-package-json/issues/7
I think the field is very useful for @types packages.

Usecase: automated dependency updates service like Renovate
It creates PR to update deps with changelog: ex) https://github.com/teppeis/bind.ts/pull/31
But DefinitelyTyped repo doesn't have git tag for each package and @types package doesn't have gitHead prop, it cannot generate changelog: ex) https://github.com/teppeis/bind.ts/pull/42

We also need this property at Sourcegraph to provide go-to-definition to the DefinitelyTyped repository at the correct revision.


RocketMQ Support Protobuf and GRPC

FEATURE REQUEST

Please describe the feature you are requesting.
Now, RocketMQ don't support Protobuf and GPRC.But, If RocketMQ supports protobuf and GPRC, there are at least some advantages as below:
(1).Protocol Buffers is platform-neutral, extensible mechanism for serializing structured data.It can provide more performance serialize/deserialize remoting communication data than some json lib.
(2).GPRC is a kind of A high-performance, open-source universal RPC framework.If rocketmq support gprc, it can help to intergrate with other opensource system, such nacos, seata, and others.

Provide any additional detail on your proposed use case for this feature.
(1)Support protobuf in rpc remoting module.
(2)Support GPRC in rpc remoting module.

Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

sub-task1-issue-number: sub-task1 description here,
sub-task2-issue-number: sub-task2 description here,
...

I think supporting protobuf and GPRC is much more important.We can discuss together. @vongosling @duhenglucky @RongtongJin @xujianhai666 @wenfengwang @zhouxinyu @xiangwangcheng

@zongtanghu This feature changes a lot and is more suitable for RIP. I will close it first and look forward to seeing the new RIP proposal :-)


Setup For React App

This pull request contains the react app environment to create the Math Magician project

Many thanks


Resolve ESLint issues

At the moment master branch has 11 eslint errors, I've fixed those to make the code more consistent.

Ah, thank you! That's what I get for not configuring Travis...

Thank you @kot-lex.  Sorry that I didn't run eslint. 🙁


The code doesn't run

self.attention_store = {}

This is probably because of diffusers version issue. #57


refactors machine linking to use generics

motivation to merge: you'll get conveyors i promise

thank you


Some of the features that I miss

I was using this great app for half a year (together with many other like xnview, faststone, ifran and so on), I love it's flexibility with many features that other viewers are missing, but also I miss some other features that seems could do some impact on the overall QoL.

I'd love to see file name and resolution of selected image somewhere (like status bar?)

2 it was handy with the old version to popup the prompt over the image with single shortcut, but that old prompt was clumsy while new one looks better since got parsed and structured but I miss the shortcut to popup it's whole body over the image (dragging lines seems slow solution).
3 if aesthetic score has 3 numbers in it last number is half-cutted on display with the scale option like 125-150% (check the screenshot)
4 that one popup "x images added" is kinda annoying when you do batch generation of the images and also have auto-import images enabled in the DT, would be better to move it to the status bar (or having an option to disable it)
5 with adding more things described above to show in the status bar also would be nice to have a clickable status bar with history (not mandatory)
also I have a bug with new folders tree view, it's kinda cutted by height in the bottom and shows only 3 images in selected folder (screen attached)

For the bug, try the version linked here in this issue. It should then be fixed.
https://github.com/RupertAvery/DiffusionToolkit/issues/211#issuecomment-1937042983

for 2 and the bug, these should be addressed in the latest official build (v1.6.1).
The popup overlay has returned.

for 2 and the bug, these should be addressed in the latest official build (v1.6.1).
The popup overlay has returned.

it works great, thanks


SSL Error

Here's the error I get when running pip install pocket-to-sqlite:
  Could not fetch URL https://pypi.python.org/simple/pocket-to-sqlite/: There was a problem confirming the ssl certificate: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:661) - skipping
  Could not find a version that satisfies the requirement pocket-to-sqlite (from versions: )
No matching distribution found for pocket-to-sqlite

Does this require python 3?

@simonw any ideas here?

That URL uses TLS 1.3, but maybe only if the client supports it.
It could be your Python version or your SSL library that’s not recent enough.


Add information about overrides to symbol information

This is a follow up to https://github.com/scalameta/metals/issues/1645
We should be easily able to include information about all symbols that a given symbol overrides, but I am not sure that it's the right way to go (not sure of a full impact on semanticdb). We could also try to just a Boolean flag that says whether or not a given symbols overrides anything. @olafurpg what do you think?

@olafurpg finally got back to this, sorry it took so long. The biggest question for me here is whether we should try to get overrides information in scalacp?


2.3 still failing

Using the provided script, first of all, there is a permission issue, so setting 777 the tmp folder solves that.
Second, when running manually to debug why it is not working:
sudo -u bigbluebutton docker-compose run --rm --user 998:998 app node index.js -i /var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080 -o /var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080/video.mp4
WARNING: Error loading config file: /root/.docker/config.json: open /root/.docker/config.json: permission denied
[Start] Rendering downloadable video for BBB presentation  {
  args: Namespace(input='/var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080', output='/var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080/video.mp4'),
  format: 'mp4',
  docker: true
}
mv: can't create '/var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080/video.mp4': Permission denied
[Error] Failed rendering downloable video for BBB presentation  {
  args: Namespace(input='/var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080', output='/var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080/video.mp4'),
  format: 'mp4',
  docker: true,
  workdir: './tmp/datacDAope'
} Error: Command failed: mv ./tmp/datacDAope/video.mp4 /var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080/video.mp4
mv: can't create '/var/bigbluebutton/published/presentation/f8eb152b2bff59b0455f9bd02b3ae57e97d1d09a-1619419572080/video.mp4': Permission denied

    at checkExecSyncError (child_process.js:635:11)
    at Object.execSync (child_process.js:671:15)
    at moveFile (/home/bigbluebutton/modules/processor.js:101:22)
    at module.exports.createVideo (/home/bigbluebutton/modules/processor.js:34:9)
    at async run (/home/bigbluebutton/index.js:10:9) {
  status: 1,
  signal: null,
  output: [
    null,
    <Buffer >,
    <Buffer 6d 76 3a 20 63 61 6e 27 74 20 63 72 65 61 74 65 20 27 2f 76 61 72 2f 62 69 67 62 6c 75 65 62 75 74 74 6f 6e 2f 70 75 62 6c 69 73 68 65 64 2f 70 72 65 ... 95 more bytes>
  ],
  pid: 824,
  stdout: <Buffer >,
  stderr: <Buffer 6d 76 3a 20 63 61 6e 27 74 20 63 72 65 61 74 65 20 27 2f 76 61 72 2f 62 69 67 62 6c 75 65 62 75 74 74 6f 6e 2f 70 75 62 6c 69 73 68 65 64 2f 70 72 65 ... 95 more bytes>
}

Permission issue may result by the fact that 998:998 is somewhat wrong.
Excerpt from /etc/passwd:
freeswitch:x:999:998:freeswitch:/opt/freeswitch:/bin/bash
etherpad:x:998:997:etherpad user-daemon:/usr/share/etherpad-lite:/bin/false
bigbluebutton:x:997:996:bigbluebutton:/home/bigbluebutton:/bin/false

So, when i get that correctly, the rendering stuff should be done by user/group bigbluebutton, right?
In this case, it is done by group freeswitch [998] and user etherpad [998]
But we should have group 996 and user 997 which resolves to bigbluebutton.
--user 997:996

Thanks for pointing that out. The command is an example of usage and misleading when you didn‘t read the part of installing the post publish hook where uid and gid of bbb user are read from /etc/passwd. Will update the readme.

Well, obviously i did read it ;-) and this works at the automated way, but not for older recordings which are preferably rendered one by one in times where the server idles...


Update logstash version suportability

Update the supported version of the Logstash output plugin from 7.15 to 7.16
Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

After the submission has been made, please look at the Validation Checks.

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

@NoamLandress - please fill out the template, it is required


Allow usage of inside/outside

Typst now allows defining margins for inside/outside for bound documents. Would be nice if I could use this package like this, too.
Also, making it possible to define different text alignments depending on if the outside margin is on a left or a right side of a page.
Thanks for this very useful package!

I am not yet inclined to support this by default since it would greatly increase some of the complexity, but does this work for you?
#import "@preview/drafting:0.1.1": *

#import "utils.typ": *

#let t-b-margin = 0.8in
#let (in-margin, out-margin) = (3in, 0.8in)
#let my-note(..args) = {
  locate(loc => {
    let (l, r) = (out-margin, in-margin)
    if calc.odd(counter(page).at(loc).last()) {
      (l, r) = (r, l)
    }
    margin-note(margin-left: l, margin-right: r, ..args)
  })
}

#set page(
  margin: (inside: in-margin, outside: out-margin),
  paper: "us-letter",
  height: auto,
)
#set-page-properties()

#lorem(50)
#my-note[A right note]
#my-note(side: left)[A left note]
#lorem(50)
#pagebreak()
#lorem(50)
#my-note[A right note]
#my-note(side: left)[A left note]
#lorem(50)

Thank you! That works. I modified the function to automatically do what I want:
#let (in-margin, out-margin) = (3in, 0.8in)
#let my-note(..args) = {
  locate(loc => {
    let (l, r) = (out-margin, in-margin)
    if calc.odd(counter(page).at(loc).last()) {
      (l, r) = (r, l)
      margin-note(margin-left: l, margin-right: r, side: left, ..args)
    } else {
      margin-note(margin-left: l, margin-right: r, side: right, ..args)
    }
  })
}

Would be nice if something like this could be included in the package, but of course it is your decision if the use case fits your conception.

The reason I'm hesitant is it almost doubles the number of parameters the user must pass to set-page-properties to get things working properly (inside/outside change meanings depending on whether text is ltr or rtl, I'm not sure if odd/even pages will guarantee which margin to use, etc.). I think once #2 is possible (waiting on fundamental typst improvements), this becomes much more doable

I am inspired by your solution to set the default side to auto, and using whichever margin is larger when unspecified. Then, you don't have to explicitly swap sides when the margin changes

I am inspired by your solution to set the default side to auto, and using whichever margin is larger when unspecified. Then, you don't have to explicitly swap sides when the margin changes

That would already help tremendously and actually be as well of a solution! :) 👍

It was not working for me, so I sent a PR with the page oddity check.

#let (in-margin, out-margin) = (3in, 0.8in)
#let my-note(..args) = {
locate(loc => {
let (l, r) = (out-margin, in-margin)
if calc.odd(counter(page).at(loc).last()) {
(l, r) = (r, l)
margin-note(margin-left: l, margin-right: r, side: left, ..args)
} else {
margin-note(margin-left: l, margin-right: r, side: right, ..args)
}
})
}

I came across this when I ran into compiler warnings trying to solve the same issue (switching left/right with different margins depending on odd/even pages). I had found a similar solution and it seemed to work (visually, it produced the desired output), but it throws a warning, that the layout did not converge within 5 attempts. So I tried your solution, which is very similar to mine, and I am getting the very same warning. Have you experienced this as well?

@mareikep thanks for reporting, are you able to share the full source code for your document that generates warnings? It will be much easier for me to identify the cause in that case.
Generally, the only time compiler warnings are unavoidable is when you have >= 4 overlapping notes

@mareikep thanks for reporting, are you able to share the full source code for your document that generates warnings? It will be much easier for me to identify the cause in that case.
Generally, the only time compiler warnings are unavoidable is when you have >= 4 overlapping notes

Sure, I decided to just create a link to share the source in the Typst app, so it's easiest to reproduce.
In this example, commenting out the last margin-note will remove the warning. I have played around with it a lot, depending on how much text is in between two margin-notes and whether it's the left page or not, but haven't figured out yet, what exactly seems to cause the warning.
Hope, you have some fresh ideas :)

@mareikep the problem is you have locate nested 3 times: hint calls locate, margin-note calls locate (internally), and sticky-hint calls locate. This is what prevents the function from converging. It is instead better to allow your subfunctions to accept loc as an additional argument. I created an additional file called fixed.typ in your code that directly calls margin-note so there is only one nesting of locate and the warning goes away.

@mareikep the problem is you have locate nested 3 times: hint calls locate, margin-note calls locate (internally), and sticky-hint calls locate. This is what prevents the function from converging. It is instead better to allow your subfunctions to accept loc as an additional argument. I created an additional file called fixed.typ in your code that directly calls margin-note so there is only one nesting of locate and the warning goes away.

Thanks for the hint, unfortunately the drafting package does not pass theloc to the subfunctions, so I had to update the drafting.typ file manually and then import it locally. Works now and - so far - no warnings or errors.


hetzner-kube cluster addon install openebs fails: storageclasses.storage.k8s.io "openebs-standard" not found

See the console output
hetzner-kube cluster addon install --name cluster-name openebs
2019/06/17 09:43:20 installing addon openebs
Enter passphrase for SSH key /home/user/.ssh/id_rsa:
2019/06/17 09:43:30 run failed
command:kubectl delete -f openebs-storageclass.yaml && kubectl apply -f openebs-storageclass.yaml
stdout:Error from server (NotFound): error when deleting "openebs-storageclass.yaml": storageclasses.storage.k8s.io "openebs-standard" not found

I think the kubectl delete -f openebs-storageclass.yaml needs an --ignore-not-found=true

I run into the same problem.
after I cleaned up everything from that broken install I took the standard helm-chart
helm install --namespace openebs -n openebs stable/openebs

I'm still running into this error with Kubernetes v1.16.3 on latest hetzner-kube.
@dsteinberg111 How did you do the cleanup?


complete Linked list document(intro+ other concepts)

Description
I will create a complete document for Linked list.It will consist of each and every topics related to Linked list.
for example
1)Intro
2)creating linked list class
3)taking input dynamically from user
4)length function
5)inserting ith node
6)deleting ith node
Domain
C/CPP
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

Please do assign this to me.


chore: remove unnecassary build file

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Irritating error message typo in ng generate component

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[x] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
I am not sure
Description
Generating a new component in a library  with an invalid library-name result in an irritating error message:
Could not find an NgModule. Use the skip-import option to skip importing in NgModule.
I would expect the same error-message that other commands produce (e.g ng s --project='...' with invalid project name):
Project '...' does not exist.
Spelling the library correct allows me to generate my component (as expected). The Problem here is the error message. It took me a while to realise the real problem was a spelling mistake in my command.
🔬 Minimal Reproduction
ng new ng-generate-error-message (no routing, css as stylesheet format)
cd ng-generate-error-message
ng g library my-lib
ng g c new-component --project=my-lib-with-a-typo
The output that i get:
Could not find an NgModule. Use the skip-import option to skip importing in NgModule.
The output that i would expect:
Project 'my-lib-with-a-typo' does not exist.
🔥 Exception or Error

Could not find an NgModule.
Because in some case when in ng-new or ng generate app, the project would not exist yet which makes this check to verify if a project exists tricky.

Ok, i happend to notice (after writing this issue) that generating a service with a wrong library name results in the expected error-message. Maybe that helps.
$ ng g s test --project=invalidlib
Specified project does not exist.

Thank you for the quick answer