Error: context deadline exceeded: when destroying 'eks-cluster-with-new-vpc"

Welcome to Amazon EKS Blueprints!

[X] Yes, I've searched similar issues on GitHub and didn't find any.

Amazon EKS Blueprints Release version
https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/examples/eks-cluster-with-new-vpc
What is your environment, configuration and the example used?
I just deployed the Terraform as instructed here:
https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/examples/eks-cluster-with-new-vpc
What did you do and What did you see instead?
I just did 'terraform apply' which works fine, but when I try to destroy it I get the following error:
Error: context deadline exceeded
Additional Information
No response

The examples provided include all the resources to bring up the example cluster and its resources. Normally, things like VPC and cluster would be in separate statefiles.  We are in the process of updating READMEs for each our our examples to reflect this approach as well.

@kcoleman731 It looks like your example in the getting started guide has typos that say "terraform apply -target="module.eks_blueprints"" instead of terraform destroy for the last two commands.


可以变合成边播放吗？数据比较多，pwg_infweence(mel)很慢

For support and discussions, please use our Discourse forums.
If you've found a bug then please create an issue with the following information:
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
** Environment (please complete the following information):**

OS: [e.g. Ubuntu]
GCC/G++ Version [e.g. 8.3]
Python Version [e.g. 3.7]
PaddlePaddle Version [e.g. 2.0.0]
Model Version [e.g. 2.0.0]
GPU/DRIVER Informationo [e.g. Tesla V100-SXM2-32GB/440.64.00]
CUDA/CUDNN Version [e.g. cuda-10.2]
MKL Version
TensorRT Version

Additional context
Add any other context about the problem here.

see: https://github.com/PaddlePaddle/PaddleSpeech/tree/develop/demos/streaming_tts_server

可以看下 https://www.bilibili.com/video/BV1N94y117ng 的实现方法

可以看下 https://www.bilibili.com/video/BV1N94y117ng 的实现方法

教程很赞，可以在 discussion 开个贴把链接放上去


Better error messaging and some docs improvements

A few changes to error messaging.
In several places, python errors were just printing the string message of the exception, not the exception class or stack-trace.  Now it's printing the full stack-trace.  This is mostly in python operators.
In a couple of the C++ operators I've improved the error messages when checks fail.
Also a few comment changes which will improve the auto-generated API docs.

Please fix lint

How can I see the linter errors?  The link to the failed test http://<IP_ADDRESS>:8080/job/mxnet/399/ times out for me.

Figured out my networking issue accessing the Jenkins server.

I think the only lint errors remaining are the same 14 warnings that were there before.

http://<IP_ADDRESS>:8080/job/mxnet/357/console
This page shows the lint error:
21:55:37 =====134/135 cpp-header files passed check=====
21:55:37 src/operator/pooling-inl.h: 2 Errors of 1 Categories map={'whitespace': 2}
21:55:37 =====147/147 cpp-soruce files passed check=====
21:55:37 =====39/41 python files passed check=====
21:55:37 python/mxnet/io.py: 1 Errors of 1 Categories map={'convention': 1}
21:55:37 python/mxnet/operator.py: 2 Errors of 1 Categories map={'convention': 2}
21:55:37 3 files failed lint

also please rebase to resolve conflict

lint error depends on verion
you need to install this version of lint:
pip install cpplint 'pylint==1.4.4' 'astroid==1.3.6'


add auto import component like nuxt-icons

I really liked the idea of nuxt-icons auto import and component
But I liked to use svgo as it provides more granular control over the svg render
also their implementation uses lazy imports, which wont be rendered on SSR and will also cause layout shifts
it would be nice to have this feature with nuxt-svgo, with more options
I have made a PR ready (#89 ) which provided me with a foundation to further develop this
I have made another PR on top of that, which I will make after this issue and reference it here:  #91
it would be nice if you could approve these changes :)

some caveats:
the type of import used inside the component is only supported on vite AFAIK
since we wanted to do SSR I had to eager load the icons. I am not sure if this will include ALL icons or can treeshake based on code. so it may end up bundling everything in assets/icons


Custom output name

Is it possible to set a specific name for the output file instead of the one auto generated?. Also is worth mentioning that the idea is to run an automated node client app that will take different files to create the outputs, so we'd like to use our own naming convention for the final file.
Thanks!!

Hello,
No, its not possible to do it via settings, however you could just add a file rename method call right there: https://github.com/inlife/nexrender-boilerplate/blob/master/start.js#L100-L104

Hi and thanks for the prompt answer.
Yep that's what I've been doing so far. I get the project uid and then use that with node's file system to rename the file.
Have a nice one and thanks again!!


Calico 3.6

What would you like to be added:
Calico 3.6
Why is this needed:
3.6 has Calico IPAM for Kubernetes API datastore.
https://docs.projectcalico.org/v3.6/release-notes/

Fixed in #1172


Numpad Enter Ripple

When pressing the Enter key on the numpad, the ripple originates from the primary Enter key near the center of the keyboard. Not sure if there's a way to separate the two.
Was testing the ripple effect moving to my mouse and was very confused for a brief moment.

The numpad enter hey is no different from the actual enter key. As a result, pressing it will trigger the actual enter key. I don't think this is important to fix, as not many users will be using the numpad enter key.


Add logo to Docusaurus' user page

https://github.com/facebook/docusaurus/blob/master/website-1.x/data/users.js

PR created: https://github.com/facebook/docusaurus/pull/1918, waiting for response.

PR was successfully merged! Check: https://docusaurus.io/en/users
Closing.


Hm 3060 helpdesk zd 37720

This pull request skips recruiter info validation for categories that recruiters can't select.


Is Kubernetes cluster name available to chart templates?

Is there a way for a chart to become aware of the Kubernetes cluster name, for tagging purposes?

Good idea. I'm trying to find where we can get this from the Kubernetes API.

Opened a feature request in kubernetes: https://github.com/kubernetes/kubernetes/issues/44954

/remove-lifecycle rotten
This is something that's really nice to have when doing hostname based ingress + external-dns with a single Route53 zone and <svc>.<namespace>.<cluster>.domain.com.

Any updates or workarounds here?

This issue was labeled as a wontfix on kubernetes' side, so there will not be a way to identify the name of the kubernetes cluster through the API.
However, perhaps there may be a way to fetch the name of the current context we are using from ~/.kube/config to connect to the cluster and supply that to the cluster.

a similar ticket with some background context: https://github.com/kubernetes/helm/issues/2613

/remove-lifecycle rotten

/remove-lifecycle rotten

Any news on this ticket ?
nginx do not use the resolv.conf and we have to use FQN for referencing services which make is very hard when you use different cluster which have different name cause the FQN is using the following pattern:
..svc.
the  is already available in helm but not the  :(

There is one way with yq itlity
kubectl -n kube-system get configmap kubeadm-config -o jsonpath={.data.ClusterConfiguration} | yq r - clusterName

I guess that's only possible with clusters spawned with kubeadm, right? That command looks at the cluster name provided when kubeadm created the cluster
In any case, that should be helpful for a small subset of users. Nice trick. 👍

The coredns config map seems to be holding the value
>k get cm coredns -n kube-system -oyaml
apiVersion: v1
data:
  Corefile: |
    .:53 {
        errors
        health
        kubernetes cluster.local in-addr.arpa ip6.arpa {
          pods insecure
          upstream
          fallthrough in-addr.arpa ip6.arpa
        }
        prometheus :9153
        proxy . /etc/resolv.conf
        cache 30
        loop
        reload
        loadbalance
    }
kind: ConfigMap
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","data":{"Corefile":".:53 {\n    errors\n    health\n    kubernetes cluster.local in-addr.arpa ip6.arpa {\n      pods insecure\n      upstream\n      fallthrough in-addr.arpa ip6.arpa\n    }\n    prometheus :9153\n    proxy . /etc/resolv.conf\n    cache 30\n    loop\n    reload\n    loadbalance\n}\n"},"kind":"ConfigMap","metadata":{"annotations":{},"labels":{"eks.amazonaws.com/component":"coredns","k8s-app":"kube-dns"},"name":"coredns","namespace":"kube-system"}}
  creationTimestamp: "2019-06-14T14:03:02Z"
  labels:
    eks.amazonaws.com/component: coredns
    k8s-app: kube-dns
  name: coredns
  namespace: kube-system
  resourceVersion: "47"
  selfLink: /api/v1/namespaces/kube-system/configmaps/coredns

Any updates on the issue?

Any updates on this issue?
I made the feature request, but this issue is discussing the same thing, so my issue was closed.
My idea is as the same as this comment

This was closed as stale, but it looks like the community still wants it. It was even added to a milestone.
Can it be re-opened?

It would be nice if this can be implemented

We are waiting for this

Repeating what I mentioned earlier...
This issue was labeled as a wontfix on Kubernetes' side. To answer the original question:

Is Kubernetes cluster name available to chart templates?

No, because Kubernetes has no concept of a "cluster name". We cannot support something that does not exist.
Your best bet would be to provide a custom clusterName value in your templates, which you can choose to override by passing kubectl config current-context as input either via --set or --values.
Helm cannot provide the current context's name as part of helm install or helm upgrade's built-in objects because one user could set their current context with the name "myCluster" and another user could use "default", which means upgrades and installs are nondeterministic from one upgrade to the next.
If you can convince the Kubernetes authors to implement a "cluster ID" or a "cluster name" that can uniquely identify a cluster, we'd accept PRs to add that to Helm's built-in objects.

I believe that everyone performs update operations on a similar publishing machine. This .kube/config will configure a lot of cluster information. I need to get the name of the context I am currently using to judge whether I need to do differential deployment. This should belong to a very common requirement.

Posting this in case it saves other folks some time.
One solution that I've seen work is, if you're using terraform to create the cluster, then use terraform to create a configmap containing the name of the cluster, and then read the configmap value from helm.

How about cluster ID? Can I read cluster ID using helm and pass it to (say) a pod?

I want this feature, also.

If you really want to have some unique piece of info, use lookup and grab the uuid of the default namespace. This is the closest thing you're going to have to finding a unique id for a kubernetes cluster.

If you really want to have some unique piece of info, use lookup and grab the uuid of the default namespace. This is the closest thing you're going to have to finding a unique id for a kubernetes cluster.

That's an interesting workaround. ty.

kubectl config current-context | cut -f2 -d/ is the name of the cluster, surely?

No, it's what you call it. It's stored in your kubeconfig.
There is no cluster name.
A couple of workarounds exist that come close.
On Mon, 10 Jul 2023, 13:27 joeloplot, @.***> wrote:

kubectl config current-context | cut -f2 -d/ is the name of the cluster,
surely?
—
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/2055#issuecomment-1628774623, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUL2GA2SWRY27AWSXKYNTXPPRIHANCNFSM4DCFKE3A
.
You are receiving this because you commented.Message ID:
@.***>

Sure, I understand that. But why is that a bad name to use? If the local context isn’t configured, there’s no server to talk to. Using the name the user gives that context (or the ‘default’ default value) seems fine to me.
Is there some reason it needs to be globally unique?

On 10. Jul 2023, at 16:26, Till Backhaus @.***> wrote:
No, it's what you call it. It's stored in your kubeconfig.
There is no cluster name.
A couple of workarounds exist that come close.
On Mon, 10 Jul 2023, 13:27 joeloplot, @.***> wrote:

kubectl config current-context | cut -f2 -d/ is the name of the cluster,
surely?
—
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/2055#issuecomment-1628774623, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUL2GA2SWRY27AWSXKYNTXPPRIHANCNFSM4DCFKE3A
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub https://github.com/helm/helm/issues/2055#issuecomment-1629087554, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7DMX4AOLQKB3BKJLS6YGNDXPQGIFANCNFSM4DCFKE3A.
You are receiving this because you commented.

--
http://holoplot.com/?utm_source=email&utm_medium=sg&utm_campaign=Holoplot_Signature+
HOLOPLOT GmbH - Headquarters
Ringbahnstr. 12 (10-14) / A2
12099
Berlin, Germany
+49 (0) 30 40745812
HOLOPLOT GmbH - Manufacturing
Alboinstr. 17-23 / Hall 12
12103 Berlin, Germany
+49 (0) 30 959988740
www.holoplot.com https://holoplot.com/
Follow us on
https://www.facebook.com/OriginalHOLOPLOT/?utm_source=email&utm_medium=sg&utm_campaign=Holoplot_Signature+
LinkedIn
https://www.linkedin.com/company/holoplot-gmbh?utm_source=email&utm_medium=sg&utm_campaign=Holoplot_Signature+.
Roman Sick – CEO | HRB183974B, Register Court Charlottenburg, Germany |
EU Tax-Registration No. DE277000701 This e-mail contains confidential
and/or privileged information. If you are not the intended recipient (or
have received this e-mail in error) please notify the sender immediately
and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the information in this e-mail is strictly forbidden.

That depends on your use case.
Relying on kubeconfig make the code dependant on which host it is executed on. This is a pattern that many people try to avoid.

Oh yes, this makes sense. I appreciate the explanation, thank you.

On 10. Jul 2023, at 21:41, Till Backhaus @.***> wrote:
That depends on your use case.
Relying on kubeconfig make the code dependant on which host it is executed on. This is a pattern that many people try to avoid.
—
Reply to this email directly, view it on GitHub https://github.com/helm/helm/issues/2055#issuecomment-1629617148, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7DMX4AANBLRJSRNZGEPR5TXPRLFDANCNFSM4DCFKE3A.
You are receiving this because you commented.

--
http://holoplot.com/?utm_source=email&utm_medium=sg&utm_campaign=Holoplot_Signature+
HOLOPLOT GmbH - Headquarters
Ringbahnstr. 12 (10-14) / A2
12099
Berlin, Germany
+49 (0) 30 40745812
HOLOPLOT GmbH - Manufacturing
Alboinstr. 17-23 / Hall 12
12103 Berlin, Germany
+49 (0) 30 959988740
www.holoplot.com https://holoplot.com/
Follow us on
https://www.facebook.com/OriginalHOLOPLOT/?utm_source=email&utm_medium=sg&utm_campaign=Holoplot_Signature+
LinkedIn
https://www.linkedin.com/company/holoplot-gmbh?utm_source=email&utm_medium=sg&utm_campaign=Holoplot_Signature+.
Roman Sick – CEO | HRB183974B, Register Court Charlottenburg, Germany |
EU Tax-Registration No. DE277000701 This e-mail contains confidential
and/or privileged information. If you are not the intended recipient (or
have received this e-mail in error) please notify the sender immediately
and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the information in this e-mail is strictly forbidden.

For AWS EKS Specific, we can get it via user-data, Run below from pod with ec2 instance metadata access available -
curl -s http://<IP_ADDRESS>/latest/user-data | grep /etc/eks/bootstrap.sh | awk '{print $2}'


Output files not logged on server

Using master branch code e329e92
The --send-logs and --fetch-logs flags are invalidated in this version. Expectation is that the output directory structure is automatically created both on client and server at the end of a run. However, the output directory exists only on the client side, output logs are not replicated on the server.
This change was done in #233 to address #227, which states that this is intentional in the code.

Enable --fetch-logs by default (make it non-configurable).
Since all submitters already expected to have a bunch of logs on the SUT from non-power runs (e.g. accuracy or compliance), maybe we could get rid of --send-logs to make it consistent with non-power runs?
If 1 and 2 are done, we could disable log storing on the server at all.

This will still pass through compliance and submission since the correct logs exist on the client, so it does not gate submission. However, the expectation seems to be that the output structure should have been replicated on both client and server (MLPerf Power WG discussion on 06/23/2021).
For reference, this is the output directory structure now, created only on the client.
client-output-directory
├── … (old entries skipped)
└── 2020-12-28_15-20-52_mylabel
    ├── power
    │   ├── client.json                  ← client summary
    │   ├── client.log                   ← client stdout log
    │   ├── ptd_logs.txt                 ← ptdaemon stdout log
    │   ├── server.json                  ← server summary
    │   └── server.log                   ← server stdout log
    ├── ranging
    │   ├── mlperf_log_detail.txt      │   Produced by the workload script on
    │   ├── mlperf_log_summary.txt     │   the client.
    │   └── spl.txt                      ← power log
    └── run_1
        ├── mlperf_log_detail.txt      │ ← loadgen log (same as above)
        ├── mlperf_log_summary.txt     │
        └── spl.txt                      ← power log

Confirmed over email that results being visible only on SUT is expected and sufficient. Closing this issue.


Aliasing safety

I have a question that isn't answered by the book yet, so let me open an issue to see if the book can be tweaked to cover an answer.  I see that the "Memory Safety" section of the book has a subsection about lifetimes - is it possible to also cover aliasing safety?
In particular, can you please clarify if/how the FFI layer enforces aliasing safety?  For example, is it possible to call the following function with the same reference passed to both arguments (AFAIK this example can be used to trigger Rust UB by making a cxx-mediated call from C++):
pub fn clone_from_i32(target: &mut i32, source: &i32) {
    // Rust guarantees that `&mut T` is the only, exclusive reference.
    // Having a `&mut T` that is aliased by other references leads to
    // Undefined Behavior in Rust.
    let target_ptr: *mut i32 = target;
    let source_ptr: *const i32 = source;
    assert_ne!(target_ptr.cast_const(), source_ptr);

    target.clone_from(source);
}

If it is not possible to cause an aliasing violation, then can you clarify how this is achieved?  Maybe this aspect of safety is already guaranteed by the runtime exclusivity checks in Swift?

At a high level this folds under #162 in that Rust's borrowing rules are not currently fully enforced across FFI boundaries.
swift-bridge does not currently guarantee aliasing safety. For example, the following is currently possible:
// Rust

#[swift_bridge::bridge]
mod ffi {
    extern "Rust" {
        type RustType;

        #[swift_bridge(init)]
        fn new() -> RustType;

        fn combine(a: &mut RustType, b: &RustType);
    }
}

// Swift

let rustType = RustType()

// Violates Rust's borrowing rules.
rustType.combine(rustType)

Whether or not Swift's upcoming ownership related features will allow us to better enforce Rust's borrowing rules across the FFI boundary is an open question that needs more research.

If the Safety chapter explained that Rust's borrowing rules are not enforced on the Swift side, would you consider this issue closed?

If the Safety chapter explained that Rust's borrowing rules are not enforced on the Swift side, would you consider this issue closed?

Yes, except (IMHO, feel free to disagree) I would separate out discussion and examples of lifetime vs aliasing vs mutability (rather than covering all of them together as borrowing rules).  In other words (again IMHO / from my perspective), I would like to see separate "aliasing" and "mutability" sections (next to the "lifetimes" section) that 1) say something like "Swift/Rust FFI can trigger Undefined Behavior in Rust, if it creates a situation where Rust's mutable reference is not the only, exclusive reference" and 2) give an example of how that can happen to make it a bit easier for readers to understand what to watch out for (the example in your comment is very nice).

Closed via https://github.com/chinedufn/swift-bridge/pull/164


Question: does it work with Lottie animations?

I want to crop Lottie animations, for 18:9 screen resolutions...

nope


For unattended IIS/Manual Friendly Name Not Used

When using the unattended mode (command line), using --target iis/manual, and --friendlyname, the entered Friendly Name isn't used to set the friendly name.  The documentation says that --friendlyname should work with --target, but doesn't seem to be working.  The friendly name get's set to the default (which I don't want).  When I use the "interactive" mode (run the program directly).  I can select "M", and the "IIS" or "Manual", and when I set the Friendly Name, the Friendly Name is used.
There seems to be a disconnect with the "unattended" and "interactive" modes.
Thanks,
Josh

This has been released in 2.1.4!


Autowiring of RetryTemplate in AbstractBinder is problematic.

Our DLQ ITs were failing mysteriously until we discovered that our Kafka DLQ topics were only being written to after our RetryTemplate-executed assertion logic had timed out.
Removing our RetryTemplate from the context allowed the tests to pass.
Picking up an arbitrary RetryTemplate as the default for Bindings seems risky.
Since no mutator is available the current workaround is to subclass AbstractBinder implementations and override buildRetryTemplate.
The culprits:

      @Autowired(required=false) // this would need to be refactored into constructor in the future
       private RetryTemplate retryTemplate;

	/**
	 * Create and configure a default retry template unless one
	 * has already been provided via @Bean by an application.
	 *
	 * @param properties The properties.
	 * @return The retry template
	 */
	protected RetryTemplate buildRetryTemplate(ConsumerProperties properties) {
		RetryTemplate rt = this.retryTemplate;
		if (rt == null) {
			rt = new RetryTemplate();
			SimpleRetryPolicy retryPolicy = new SimpleRetryPolicy();
			retryPolicy.setMaxAttempts(properties.getMaxAttempts());
			ExponentialBackOffPolicy backOffPolicy = new ExponentialBackOffPolicy();
			backOffPolicy.setInitialInterval(properties.getBackOffInitialInterval());
			backOffPolicy.setMultiplier(properties.getBackOffMultiplier());
			backOffPolicy.setMaxInterval(properties.getBackOffMaxInterval());
			rt.setRetryPolicy(retryPolicy);
			rt.setBackOffPolicy(backOffPolicy);
		}
		return rt;
}

I concur that there must be some "opt-out" mechanism for auto-wiring any RetryTemplate that happens to be in the application context; RetryTemplate is ubiquitous and there can easily be an instance in the context meant for some other purpose.
Perhaps a marker interface could be used, or a new property to opt-out of autowiring.

Wait, for 2.0 we specifically allowed RetryTemplate to be configured as a bean and that would override the one pre-configured by the framework, so unless I am missing something i don't think I agree with the "arbitrary" remark.
Yes, I do agree that we can/should further qualify it to address Gary's concern, but that is a separate subject, so I want to make sure we're talking about the same thing.

It also seems to me that specific binding properties should take precedence over this autowiring.
This was my feeling also.

So, @jmax01 do you mind changing the title of this issue or I can do that? We can certainly address it rather quickly with regard to qualifier.

Is changing the title to "Add @Qualifier to AbstractBinder's RetryTemplate" acceptable?


automatical renaming

Hello again.
Can't this renaming be omitted somehow? Eget for example just renames binary to package name if it only contains single binary, that's probably should be default behavior, don't you think?
slavaGanzin/await
⬇  Downloading asset: 100% |██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| (53/53 kB, 7.1 MB/s)
✅ Downloaded await_main_macos_amd64 to /Users/slava/.local/share/stew/pkg
! Rename the binary? (await_main_macos_amd64)

In cases where the release is itself a binary (instead of an archive), we will just ask the user what to name the binary because we don't want to make any assumptions (and often the binary name contains arch and os labels that the user probably doesn't want when calling it from the command line).
I feel like that is the safer option rather than stew assuming that the user wants to rename the binary to the name of the repo and then the user having to manually go back and change the name of the binary if we assumed incorrectly.
There are cases where the binary name is different than the project name (example: https://github.com/BurntSushi/ripgrep  the binary is just rg, not ripgrep). The reason rg gets installed is because the archive contains a binary called rg already.
I'm inclined to just leave this behavior as is, but I'll leave this issue open for the time being in case anybody else wants to provide feedback too.

Now I get your point. Thanks for explaining
So expected behavior to have archives that are named platform specifically which contains binary names that would not be renamed?
Is there any specification for naming and releases?

Is there some specification or standard?
Cause I saw many people(and that's why copied that behavior) put binaries like gdu_darwin_amd64 in gdu_darwin_amd64.tar.gz.
stew i dundee/gdu


Clearify install dependencies

Dear Paperist
I have made minor modifications on the Dockerfile.  Could you please check?

According to the install-tl manual, it seems that tlpdbopt_install_docfiles(resp. tlpdbopt_install_scrfiles) is used instead of option_doc(resp. option_src).

The scheme scheme-basic contains collection-basic and collection-latex(we can check that by tlmgr info --list scheme-basic in a terminal).

dvipdfmx is contained in collection-basic(similarly, we can check that by the tlmgr command).

The changes about 2) and 3) may not affect; I am very sorry for not being familiar with LaTeX ecosystems.
If this Pull Request is silly, please close.
EDIT
Sorry, I now realized that collection-latexrecommended seems to be contained in collection-latexextra, but not modify it.
Regards,

Thanks for the awesome PR!

I now realized that collection-latexrecommended seems to be contained in collection-latexextra, but not modify it.

If it’s not any trouble, could you append it to this PR?

Thank you for your reply!
I checked that collection-basic, collection-latex, collection-latexrecommended
and dvipdfmx are all installed in the image built by a modified Dockerfile.
Also, all documentes and all sources except koma-scripts are not installed.
The documents of and sources of koma-script is also installed in the image
alpine-texlive-ja:latest: I got the follwing
/workdir # du -h /usr/local/texlive/2019/texmf-dist/doc
7.6M	/usr/local/texlive/2019/texmf-dist/doc/latex/koma-script
7.6M	/usr/local/texlive/2019/texmf-dist/doc/latex
7.6M	/usr/local/texlive/2019/texmf-dist/doc
/workdir # du -h /usr/local/texlive/2019/texmf-dist/source
1.6M	/usr/local/texlive/2019/texmf-dist/source/latex/koma-script/doc/english
20.0K	/usr/local/texlive/2019/texmf-dist/source/latex/koma-script/doc/bin
1.7M	/usr/local/texlive/2019/texmf-dist/source/latex/koma-script/doc/ngerman
9.9M	/usr/local/texlive/2019/texmf-dist/source/latex/koma-script/doc
12.7M	/usr/local/texlive/2019/texmf-dist/source/latex/koma-script
12.7M	/usr/local/texlive/2019/texmf-dist/source/latex
12.7M	/usr/local/texlive/2019/texmf-dist/source

Should I open another issue?  Or can I ignore it?

Should I open another issue? Or can I ignore it?

It is acceptable to include them, because their size is not too large.


How Can I Change Toast Error Message Title ?

NToastNotify is amazing and very useful. Thanks all of contrubiters.
I want to change error message title to my own language. How can it be done ?

You can set default title during startup service registration.

Assuming this is solved. Closing it. Reopen if not

Thanks. It works.


Question about adding Search function for tech-doc-template

Hi,
I'm a Product Manager working over at Ministry of Justice on our Cloud Platform. As part of our new platform we are creating a guide for users based on the tech-docs-template which helps them interact with our platform.
This first iteration works on the basis that users work through the step by step guidance to build their non-production environment and then build, test and deploy their product (or the Test App). They can then add the resources we have made available e.g. Postgres, secrets, S3 etc.
However, the existing guide doesn't allow the users to search for or skip to specifics. You have to work through the detail or have sufficient context to know where some guidance may exists within the guide.
We were wondering what the scope is for adding some search facility to allow users to interact with the guidance in a different way to get more value from it.
Grateful for any suggestions. Many thanks.

Hi Antony
Thanks for the message. We are currently developing the tech doc template. One of the priorities is to add a search function to the template so any documentation produced will have an internal search capability.
It is not known yet what exact form this will take, but please keep an eye on the repo over the next couple of months for any updates on this.
Kind regards
Jon

Thanks Jon. I'll close the issue. Will keep my eyes peeled on the repo.

GOV.UK have added search functionality to their technical docs site using an external service - we could look at doing it that way in this case too @AntonyBishop.

Thanks @jennyd


Alexa Discovery Issues - Need to understand discovery process a bit more

HABridge been fine for almost a year, since fixing the port 80 issue:
https://github.com/bwssytems/ha-bridge/issues/1022#issuecomment-447318634
I recently tried to add a new device, but Alexa wont discover. Deleted all devices, upgraded to 5.3.0, renumber, still no discovery.
I can see the SSDP broadcasts from the HAbridge on the network, but Alexa Gen2, Gen3 or Alexa iOS APP will not discover the HAbridge. There is no request from the Alexa devices to the HAbridge. I am wondering if Amazon has changed how they are now discovering the Hue?
I have been reading this:
https://developers.meethue.com/develop/application-design-guidance/hue-bridge-discovery/
"All our bridges support UPnP, but it is advised to move to using mDNS and N-UPnP as that will be faster, mDNS is supported by more devices, and we only use a subset of the UPnP protocol (SSDP). "

So, mDNS is in the ha-bridge, but I believe Alexa Echo does not support that.
Please turn on traceupnp in the Bridge Control Settings and then do a discover after that. Please post the log. Include the IPs of the alexa and the ha-bridge.

Did you see the (2) in the discovery guide above, where the url https://discovery.meethue.com is used to get bridge info? Also all the examples are using https. No idea which of these Amazon is using, but possibly (2) and not getting bridge ID?
Here is my log, I'm afraid there is nothing useful, there is no local request from any Amazon device. I have tried gen 2, gen 3 and iOS App for discovery. This log is starting discovery from a gen2
Bridge: <IP_ADDRESS>
Alexa (gen2): <IP_ADDRESS>

12-10-2019 21:19:38.309
INFO
HA Bridge startup sequence...
com.bwssystems.HABridge.HABridge

12-10-2019 21:19:38.988
INFO
HA Bridge (v5.3.0) initializing....
com.bwssystems.HABridge.HABridge

12-10-2019 21:19:38.999
INFO
reading from config file: /home/pi/ha-bridge/data/habridge.config
com.bwssystems.HABridge.BridgeSettings

12-10-2019 21:19:41.785
INFO
StaticResourceHandler configured with folder = /public
spark.staticfiles.StaticFilesConfiguration

12-10-2019 21:19:41.866
INFO
System control service started....
com.bwssystems.HABridge.SystemControl

12-10-2019 21:19:42.152
INFO
Initializing UDP response Socket...
com.bwssystems.HABridge.util.UDPDatagramSender

12-10-2019 21:19:42.186
INFO
UDP response Socket initialized to: 50000
com.bwssystems.HABridge.util.UDPDatagramSender

12-10-2019 21:19:42.210
INFO
HTTP Home created.
com.bwssystems.HABridge.plugins.http.HTTPHome

12-10-2019 21:19:42.243
INFO
Harmony Home created. No Harmony devices configured.
com.bwssystems.HABridge.plugins.harmony.HarmonyHome

12-10-2019 21:19:42.255
INFO
Nest Home created. No Nest configured.
com.bwssystems.HABridge.plugins.NestBridge.NestHome

12-10-2019 21:19:42.263
INFO
Hue passthru Home created. No Hue passtrhu systems configured.
com.bwssystems.HABridge.plugins.hue.HueHome

12-10-2019 21:19:42.271
INFO
HAL Home created. No HAL devices configured.
com.bwssystems.HABridge.plugins.hal.HalHome

12-10-2019 21:19:42.280
INFO
MQTT Home created. No MQTT Clients configured.
com.bwssystems.HABridge.plugins.mqtt.MQTTHome

12-10-2019 21:19:42.288
INFO
HomeAssistant Home created. No HomeAssistants configured.
com.bwssystems.HABridge.plugins.hass.HassHome

12-10-2019 21:19:42.294
INFO
HomeWizard Home created. No HomeWizard gateways configured.
com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome

12-10-2019 21:19:42.300
INFO
Command Home for system program execution created.
com.bwssystems.HABridge.plugins.exec.CommandHome

12-10-2019 21:19:42.311
INFO
TCP Home created.
com.bwssystems.HABridge.plugins.tcp.TCPHome

12-10-2019 21:19:42.322
INFO
UDP Home created.
com.bwssystems.HABridge.plugins.udp.UDPHome

12-10-2019 21:19:42.327
INFO
Vera Home created. No Veras configured.
com.bwssystems.HABridge.plugins.vera.VeraHome

12-10-2019 21:19:42.333
INFO
Fibaro Home created. No Fibaros configured.
com.bwssystems.HABridge.plugins.fibaro.FibaroHome

12-10-2019 21:19:42.341
INFO
Domoticz Home created.
com.bwssystems.HABridge.plugins.domoticz.DomoticzHome

12-10-2019 21:19:42.352
INFO
Somfy Home created. No Somfys configured.
com.bwssystems.HABridge.plugins.somfy.SomfyHome

12-10-2019 21:19:42.367
INFO
LifxDevice Home created. No LifxDevices configured.
com.bwssystems.HABridge.plugins.lifx.LifxHome

12-10-2019 21:19:42.376
INFO
OpenHAB Home created. No OpenHABs configured.
com.bwssystems.HABridge.plugins.openhab.OpenHABHome

12-10-2019 21:19:42.386
INFO
FHEM Home created. No FHEMs configured.
com.bwssystems.HABridge.plugins.fhem.FHEMHome

12-10-2019 21:19:42.406
INFO
Broadlink Home created. No Broadlinks configured.
com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome

12-10-2019 21:19:42.420
INFO
Mozilla IOT Home created. No Mozilla IOTs configured.
com.bwssystems.HABridge.plugins.moziot.MozIotHome

12-10-2019 21:19:42.428
INFO
HomeGenie Home created. No HomeGenies configured.
com.bwssystems.HABridge.plugins.homegenie.HomeGenieHome

12-10-2019 21:19:42.530
INFO
== Spark has ignited ...
spark.embeddedserver.jetty.EmbeddedJettyServer

12-10-2019 21:19:42.531
INFO
>> Listening on <IP_ADDRESS>:80
spark.embeddedserver.jetty.EmbeddedJettyServer

12-10-2019 21:19:42.562
INFO
HABridge device management service started....
com.bwssystems.HABridge.devicemanagmeent.DeviceResource

12-10-2019 21:19:42.729
INFO
Hue emulator service started....
com.bwssystems.HABridge.hue.HueMulator

12-10-2019 21:19:43.002
INFO
Traceupnp: upnp config address: <IP_ADDRESS> -useIface: false on web server: <IP_ADDRESS>:80
com.bwssystems.HABridge.HABridge

12-10-2019 21:19:43.008
INFO
Description xml service started....
com.bwssystems.HABridge.upnp.UpnpSettingsResource

12-10-2019 21:19:43.036
INFO
UPNP Discovery Listener starting....
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:19:43.038
INFO
Traceupnp: Interface: eth0 valid usable IP address: /<IP_ADDRESS>
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:19:43.040
INFO
Traceupnp: Adding eth0 to our upnp join interface set.
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:19:43.041
INFO
Traceupnp: Interface: lo valid usable IP address: /<IP_ADDRESS>
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:19:43.042
INFO
Traceupnp: Adding lo to our upnp join interface set.
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:19:43.042
INFO
Create and run mDNS service.
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:19:43.217
INFO
UPNP Discovery Listener running and ready....
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:20:56.851
INFO
Link button pressed....
com.bwssystems.HABridge.SystemControl

12-10-2019 21:20:59.160
INFO
Traceupnp: sendUpnpNotify notifyTemplate1
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:20:59.414
INFO
Traceupnp: sendUpnpNotify notifyTemplate2
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:20:59.668
INFO
Traceupnp: sendUpnpNotify notifyTemplate3
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:21:19.932
INFO
Traceupnp: sendUpnpNotify notifyTemplate1
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:21:20.185
INFO
Traceupnp: sendUpnpNotify notifyTemplate2
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:21:20.438
INFO
Traceupnp: sendUpnpNotify notifyTemplate3
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:21:26.855
INFO
Link button time ended....
com.bwssystems.HABridge.LinkButtonPressed

12-10-2019 21:21:50.192
INFO
Traceupnp: sendUpnpNotify notifyTemplate1
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:21:50.446
INFO
Traceupnp: sendUpnpNotify notifyTemplate2
com.bwssystems.HABridge.upnp.UpnpListener

12-10-2019 21:21:50.699
INFO
Traceupnp: sendUpnpNotify notifyTemplate3
com.bwssystems.HABridge.upnp.UpnpListener

So, I assume you did an Alexa discovery through this log. Since there is no log of receiving any UPNP SSDP Search messages from the Alexa or any devices (which is wierd) there may be an issue with your network settings. Did those change recently? Since you are looking at network packets, can you see the SSDP messages from the Alexa?

OK, so looking at above log, I can see no traffic from Echo to bridge. Digging a little deeper, I confirmed this with tcpdump in the Pi runng habridge on the LAN
 sudo tcpdump -v host [ip address of Echo]
I have done some network traces and the Alexa is doing a SSDP multicast on the WLAN (as per developer doc above option (1)), but this is not arriving on LAN. It seems SSDP using address <IP_ADDRESS> is not traversing LAN <--> WLAN for some reason. This should resolve the issue. I'm still looking into what is blocking the SSDP.  I will get a USB wifi Pi adapter and attach to WLAN to confirm discovery of habridge is still working.

Did you have any updates to your router firmware? Were there any updates to the firewall on your Pi?

One thing I’ve noticed while tracing upnp traffic during discovery is that on 5.3, the bridge responds with <IP_ADDRESS>:80 as the address. When rolling back to 5.1 the configured address is used in response.  Maybe this is just a logging issue, but 5.1 consistently allows device discovery while 5.3 never does.  Also, 5.3 never logs receiving any Alexa discovery requests.

I too just found out that Alexa is no longer discovering new devices.  Existing devices are showing as offline, but they are still working.
I've not tested new device discovery in 5 months, until now.   Log attached.
ha-bridge.20191212.txt

I was reading through some of the Home Assistant forum and they’ve had the exact same issue.  I skimmed through the thread but it sounds like they implemented a solution recently for the discovery and the “doesn’t support requested value” issue. Thanks Amazon.

Maybe this is just a logging issue, but 5.1 consistently allows device discovery while 5.3 never does. Also, 5.3 never logs receiving any Alexa discovery requests.

I 'discovered' same :) however in my case the reason 5.3 didn't log any requests was because it didn't receive any requests.
What I have learnt so far:
Initiating a discovery from Alexa will cause all the Alexa devices to send a SSDP multicast using destination ip address <IP_ADDRESS>. Using tcpdump on my Pi connected to Ethernet, I did not see any of these requests from the Alexas connected to wifi. For some reason, that I don't fully understand (yet), these multicasts were not traversing from my wifi network to lan. I understand this is due to something called IGMP snooping:
https://en.wikipedia.org/wiki/Internet_Group_Management_Protocol
Some network devices (switches, routers, accesspoints?) implement this to create a multicast group to restrict multicast traffic to only those devices on the network that are interested in it. If this network is not working correctly, the SSDP multicasts will not be received on the habridge.
There is a very easy way to test this if your habridge is running on a Pi on lan, use tcpdump with the multicast address from your Pi
sudo tcpdump -v host <IP_ADDRESS>
You should see 3 SSDP requests from each Alexa on your network.
If you dont see these, there is something wrong with your network, and you will need to figure out what, before looking at habridge logs.
Restarting Pi, switches, access points, routers, Alexa's may help. Another solution is a wifi usb adapter for your Pi, so the habridge and Pi are both on wifi.
If you see these SSDP requests in tcpdump, then you can dive a little deeper in habridge logs.
HTH

I too just found out that Alexa is no longer discovering new devices. Existing devices are showing as offline, but they are still working.
I've not tested new device discovery in 5 months, until now. Log attached.
ha-bridge.20191212.txt

Just had a quick scan through your log, as you can see, you are getting the 3 SSDP requests from each of your Alexa devices, some IPs not listed in your summary at top? I would suggest disconnecting all bar one, and then initiating a discovery.

Just a hint: you could try to have a look on the code from release 4.x.x and what has changed to the current 5.x.x release from habridge.
I don't know excatly the difference, but i had the same issues that Alexa didn't find any more my devices.
I tried all the suggested solutions:
changed the Port from 81 to 80, renumbered the devices and tried to discover the devices with and without the link-button several times - no luck.
The (simple) solution was:
i made a downgrade from the current 5.3.0-release to the latest 4.5.6-release (habridge running on port 80), rebooted the pi, started again the discovery by Alexa and voilà: all devices discovered and manageable by Alexa without problems.
So, at the moment i'll keep the (old) 4.5.6-release running... :-)

@Huibuh1111: you are completely right. For month I also did everything what had been discussed and suggested here without any success. Now after downgrading to 4.5.6 it works like a charm again. Thanks a lot :-)

Got a new Echo for Christmas and added to my network (I previously just had 3 Echo Dots).  When I went to try my lights on the new Echo they did not work.  I checked the setup in the Alexa App and all my devices from HA Bridge are missing.  I went to the HA Bridge on my Pi and removed all the ones I had and then added them again and tried to do the discovery.  But Alexa is not finding the devices now.  I had an issue before Christmas when I tried to add a single new x10 device - it was added OK to HA Bridge but Alexa did not find it.  Then today I noticed all of them were missing.
The devices are in HA Bridge and they work (I am using HA Bridge with HomeGenie on a Pi X10 Hub).  I can turn them on via HA Bridge - just cannot get Alexa to discover the devices again.
Any suggestions ?

Same here, has to be a problem in habridge.
The only way to recognise new devices is to remove all devices from alexa manually, renumber the device id's in habridge en discover again.
Has to be in habridge, i think i will be going to do the same thing as MasterRay2.. downgrade to 4.5.6.
Unless there will be a fix soon offcourse.

For all: The new Release Candidate is out for testing.... https://github.com/bwssytems/ha-bridge/releases/tag/v5.3.1RC1
Please post your issues or successes at #1192

I have updated my previously working config to 5.3.1 and it still cannot discover devices, I have noticed this in all 5.x updates. I have 2 fire tvs v2 and 1 echo dot original and none of their discoveries work


Figure out a good way to show when chapel is

Another request from the chairs meeting.

This could be a class added to all schedules. And toggled by the application state settings.

What I have in mind is a little more complicated than that.  It should show up in all rooms and for all faculty in those views and should probably span the entire width of the day in the department schedule view.
It might be implementable as a type of wildcard, but I don't completely understand what the current wildcard feature is supposed to be.  It looks to me like you just get something named "*" when you follow the directions in the Add/Update section popover.
Can someone give a better description of what the wildcard system is supposed to be?  Is it working as intended now, or do we need to open an issue to improve it?

I'm not sure what a wildcard is either. That was added last year. Eventually, I could look in the codebase, but I'm not sure when I'll have time yet.

This is all I know:


fix #1825 bug. Because you call ``` [super encodeWithCoder:coder]; ``…

fix #1825 bug. Because you call [super encodeWithCoder:coder]; in AFURLSessionManager.m, So the problem that NSURLSessionConfiguration does not confirms to NSCoding protocol still be there. And I think call super does nothing wrong, so I rmove the encoding code for configuration to parent class. Happily this also fix the warning for *** NSKeyedArchiver warning: replacing existing value for key 'sessionConfiguration'; probable duplication of encoding keys in class hierarchy

Can you merge with the latest master to fix tests?

Codecov Report

Merging #4102 into master will decrease coverage by 0.02%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #4102      +/-   ##
==========================================
- Coverage    82.8%   82.78%   -0.03%
==========================================
  Files          46       46
  Lines        5304     5303       -1
  Branches      439      439
==========================================
- Hits         4392     4390       -2
  Misses        671      671
- Partials      241      242       +1

Impacted Files
Coverage Δ

AFNetworking/AFHTTPSessionManager.m
82.87% <ø> (+0.87%)
:arrow_up:

AFNetworking/AFURLSessionManager.m
59.74% <50%> (-0.33%)
:arrow_down:

Continue to review full report at Codecov.

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

I got lost. why 2 failing checks.

Although apple delete NSCoding protocol from NSURLSessionConfiguration. The concrete sub class does conform to NSCoding. Unit test can't reach here. So I can't let the unit test code reach the else branch. So I think it's better deleting the else branch.

I don't think deleting the else branch is the right answer there—I meant merging with themaster branch to get some other fixes we’ve merged in.

Ok, now in my opinion, the code here only has one question that is subclass and super class use the same key to archive configuration which leads to a warning *** NSKeyedArchiver warning: replacing existing value for key 'sessionConfiguration'; probable duplication of encoding keys in class hierarchy . And preserve the else branch here doesn't leading to any problem. And the warning is not a real problem here, So if you want to ignores it, just feel free to close the pr.

Tests around this pass, so I think we're good here.


Add new logger options functionality

Description
Loggers are required to work otherwise a build fails.  We want to distributed loggers in NuGet packages which means that the very first build would not be able to restore since loggers are added with a command-line option.
The -logger argument now accepts options after the class and assembly.  One new option is to make a logger optional meaning a message will be printed if the logger can't be created rather than failing the build.
Will supersede #4528
Customer Impact
We need to deploy a logger via NuGet that collects telemetry for improving the inner loop developer experience.
Regression?
No
Risk
Low risk.
Test changes in this PR
New unit tests

I still need some review on this PR!


Fix errors being thrown on non-Latin tag characters

Example:
<中文></中文>

Yes, this is not valid HTML according to the spec, but this commit makes the beautifier more robust against possible errors.

@TimothyGu please run "./build" and then amend your commit.

Sorry about that. Fixed.


⚠ Bofrost.lu has degraded performance

In 4f3eaa3, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1231 ms

Resolved: Bofrost.lu performance has improved in 494d28d after 9 minutes.


Error "Can't find variable: require" on iOS (RN v.0.68.2)

Description
Error "Can't find variable: require" on 0.68.2 on Debug & Release.
Enumeration of presets and babel plugins did not solve the problem. The cache was cleared after each attempt. On the forums of other libraries, the developers dealt with a similar error with a patch in the new version.
The bug was discovered after fixing another bug 0.68.2
Cache was cleared before each launch: react-native start --reset-cache
The babel config was tested from empty to what worked in previous versions and suggested in other forums and repositories (1, 2, 3).
Version
0.68.2
Output of npx react-native info
System:
OS: macOS 11.6
CPU: (6) x64 Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz
Memory: 76.89 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.15.0 - /usr/local/bin/node
Yarn: 1.22.11 - /usr/local/bin/yarn
npm: 8.5.5 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK:
API Levels: 28, 29, 30, 31
Build Tools: 29.0.2, 30.0.2, 31.0.0, 32.0.0
System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-31 | Google APIs Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7678000
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_292 - /usr/bin/javac
npmPackages:
@react-native-community/cli: 7.0.3 => 7.0.3
react: ^18.1.0 => 18.1.0
react-native: ^0.68.2 => 0.68.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Any Babel configuration. Tested on iOS 15.2 Simulator.
Snack, code example, screenshot, or link to a repository

Soved


Do merge sha work for Azure as it runs detached head

Purpose
Azure Pipelines also runs in a detached head (like GitHub Actions). So this pulls the correct commit SHA
Notable Changes
This should fix an issue with users on Azure Pipelines
Tests and Risks?
Locally tested
Update the SHA hash files
Done

@drazisil-codecov yeah I should, BUT I'm going to defer to another PR. I'm thinking of restructuring the entire script to be easier to test.


add a blog post for running debezium on kubernetes

Superseded by https://github.com/debezium/debezium.github.io/pull/12, which contains a few minor fixes.


can not autocomplete what I need

for instance
try to:
iptabl<TAB> and you'll see iptables-xml. any further  wont solve a problem
save for usermod - like there is no such command.
How to fix this?

it commands for sudo, within this it'll be autocompleted


More download options (folder structure, images, .nfo files etc)

Clear and concise description of the problem
Hi!
Just stumbled upon your excellent app while looking for help on my podgrab setup. Seems to me that PodFetch has a brighter future.
What I'm looking for is a way to organize my podcast downloading so that Jellyfin can organize it neatly. Jellyfin doesn't have Podcast metadata downloading (yet), hence the data need to be perfectly sorted to get it right.
I guess the use case is broader than just Jellyfin-users. I'd probably want to organize my library neatly as a non-Jellyfin user as well.
What I want is;

A toggle setting to download or not download episodes into it's own folder. I don't want separate folders as default as it is right now.
I would also want PodFetch to generate a .nfo file with the correct metadata, such as release date, title, description, persons etc etc.
I would also like the episode image to be downloaded with the same name as the episode and in the same folder.

Suggested solution
Additional settings available for the user.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Thanks for the issue. #1 can now be controlled in the settings menu. You just need to flip the switch for direct folder mapping. Regarding the other things I'll take a look in a week.

I think that the folder structure is currently complicated.
Using the name of podcasts and episodes in the directory names is not really easy.
Creating a directory / file tree based on GUID or hash will be more relevant.
On my side I try to link PodFech with home Assistant and the file system used is not very easy to use.

Maybe not the same usage as me 😂
The directory name could be stored in database as a metadata. By default it will be the podcast name and could be modified.
Regarding episode directory, it could be stored in database too and modified manually only via an SQL request.
No change for a normal user but could be a solution for the advanced users ...

I confirm that the current folder structure is not compliant with Jellyfin. :(

I confirm that the current folder structure is not compliant with Jellyfin. :(

What do you mean with not compliant?

The episodes are not correctly classified. A few titles are named "podcast".
I will check how the structure should be and give us somes examples.

Currently the structure for a podcast is a main directory containing :

the file : image.jpeg
the directories containing the episodes.

-rw-r--r-- 1 root root  264106 Sep 21 22:36 image.jpeg
drwxr-xr-x 2 root root    4096 Sep 21 22:35 'La Revue de Presse du 23082023'
drwxr-xr-x 2 root root    4096 Sep 21 22:35 'La Revue de Presse du 24082023'
drwxr-xr-x 2 root root    4096 Sep 21 22:35 'La Revue de Presse du 25082023'

And in each episode directory, we found :
-rw-r--r-- 1 root root  264106 Sep 21 22:35 image.jpeg
-rw-r--r-- 1 root root 5895789 Sep 21 22:35 podcast.mp3

For Jellyfin, the structure should be an unique directory containing all episode files and a picture file named : cover.jpeg
-rw-r--r-- 1 root root  264106 Sep  2 17:33  cover.jpeg # podcast picture
-rw-r--r-- 1 root root 6421985 Sep  2 17:33 'La Revue de Presse du 01092023.mp3' # episode audio
-rw-r--r-- 1 root root 6421985 Sep  2 17:33 'La Revue de Presse du 01092023.jpeg' # episode picture
-rw-r--r-- 1 root root 6946413 Sep  4 07:00 'La Revue de Presse du 04092023.mp3'
-rw-r--r-- 1 root root 6946413 Sep  4 07:00 'La Revue de Presse du 04092023.jpeg'
-rw-r--r-- 1 root root 6596692 Sep  5 07:00 'La Revue de Presse du 05092023.mp3'
-rw-r--r-- 1 root root 6596692 Sep  5 07:00 'La Revue de Presse du 05092023.jpeg'
-rw-r--r-- 1 root root 6336621 Sep  6 07:00 'La Revue de Presse du 06092023.mp3'
-rw-r--r-- 1 root root 6336621 Sep  6 07:00 'La Revue de Presse du 06092023.jpeg'
-rw-r--r-- 1 root root 5917927 Sep  7 07:00 'La Revue de Presse du 07092023.mp3'
-rw-r--r-- 1 root root 5917927 Sep  7 07:00 'La Revue de Presse du 07092023.jpeg'

The episode picture won't be used by Jellyfin but it is relevant to keep it for other usage.
With this structure, all episodes will be considered as tracks of an album.

Maybe it will be interesting to add the  in the episode name :
'2023-09-07 13:09 : La Revue de Presse du 07092023.mp3' instead of 'La Revue de Presse du 07092023.mp3'
Without this date, the order of the episodes could be lost.
However, the best way will be to give the possibility of indicating how we want to store the episodes when we add a new podcast (or in general option)
For my proposition, the configuration will be :
podcast directory = /{podcast_title}/
podcast picture = /cover.jpeg
episode name = /{episode_pubdate} - {episode_title}.mp3
episode picture = /{episode_pubdate} - {episode_title}.jpeg

The configuration for the actual structure will be :
podcast directory = /{podcast_title}/
podcast picture = /image.jpeg
episode name = /{title}/podcast.mp3
episode picture = /{title}/image.jpeg

Another user could decide to use the following configuration :
podcast directory = /my_podcast/
podcast picture = /image.jpeg
episode name = /{episode_guid}/audio.mp3
episode picture = /{episode_guid}/cover.jpeg

Tell me if I'm not clear.


2873 bug cannot use timberpostfactory when extending post class as the method is private

Related:

#2873

Issue
The Timber\Post::factory() is private and thus cannot be overwritten. So there was no way to alter the query to get the children.
Solution
Added two new ways to alter the query:

added a filter to change the arguments
Add a new functionality to overload the children() parameter with query arguments.

I came up with the second approach later because that might be easier for most people. You could just change the arguments in your children call or make a separate children method in your custom class that calls the parent::children method with these additional arguments.
Impact
No negative impact since loading the argument with a string or a non-indexed array still works.
Usage Changes
No
Considerations
Maybe one of these methods is enough. Not sure if adding the full argument list is a bit too much for this method.
Testing
Yes! First unit test I've ever written 👯

@gchtr , this is now fixed!

@gchtr , applied and merged :)

@Levdbas Great, thanks! 🎉


Add soulis-1256/hoverhints.nvim

Repo URL:
https://github.com/soulis-1256/hoverhints.nvim
Checklist:

[x] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`) when adding a new plugin.
[x] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else.
[x] The description doesn't contain emojis.
[x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
[x] Acronyms should be fully capitalized, for example LSP, TS, YAML, etc.

Thanks for the PR!


Sub-folders

Is your feature request related to a problem? Please describe.
Being able to generate folders under resource folder
Describe the solution you'd like
The developer could organise its own test and resources under sub-folders

At this moment, the user can create sub-folders and is able to place the files.


remove SSL_CERT_FILE insert

To commit after merging https://github.com/teaxyz/pantry.core/pull/110

this is some pretty gnarly revlock for our users. We shouldn't remove it. Instead check if the file is there or not as well?

Let's see. This will break... openssl until a tea --sync is run. After that, openssl.org/package.yml will dep ca-certs, and all will be well. That is worrying. We'd basically need to check if openssl.org is in the package list and ca-certs is not, to know if they had the old one. So, the question really boils down to whether this a good YOLO to keep from getting crufted up this early in the game, or if this is too critical a component to break today. I can argue it either way.
Conversely, instead of keeping this around, what if we had a startupWarnings.ts that could check for some of these version issues and give a useful warning? So, in this instance, if !openssl.org.yml.dependencies.contains(curl.se/ca-certs), console.warn('out of date pantry revlock on openssl.org:curl.se/ca-certs. run tea --sync to bring your pantry up to date and resolve this issue.'). Maybe.

We should remove this at 1.0, or at wait at least 3 months I think. Until then we're safe. Unless I'm mistaken.


⚡ — Add Gonic icon

Type
Icon request
Info
Add Gonic icon
Icon(s)

Hey, this icon has been added in the new-standards branch and will be merged once it is done!
https://github.com/walkxcode/dashboard-icons/blob/new-standards/png/gonic.png


[keymgr_dpe] messge material is valid for invalid advance operations on erased slot

desc
@ballifatih I am seeing an issue where if I do an advance operation on an erased key slot the digest material sent on the kmac_data_req bus is valid data. There is a check in the scoreboard that if the advance is expected to fail that the advance data should be invalid.

Maybe we can close this if the previous PR fixed the issue. @bobby-rivos

#20470 has been confirmed to fix this, so I'm closing this issue.


Outdated

Seems like this "mirror" hasn't been updated from the source in a while.

I have updated it. Thanks.


DO NOT MERGE! Fast Forward stable to 3340052cbb295628195838a9a1b7c20b94429977.

This PR will be merged automatically once checks are successful.

Jenkins job auth/postsubmit passed


Fix incompatibility in ’tensorflow/core/kernels:cwise_op_gpu’ with Clang

It is reported that Clang cannot handle "cwise_ops_gpu_common.cu.h." in #27253 and #26159.  This PR is a patch to avoid the issue.

I signed it!

The right fix is to add missing functions to Eigen Eigen/src/Core/arch/GPU/PacketMath.h. /cc @rmlarsen

For reviewers @ezhulenev : Clang has a bug that -O2 and -D_FORTIFY_SOURCE cannot coexist when running "clang -x cuda" , so you might have to modify 'bazel-tensorflow/external/local_config_download_clang/extra_tools/lib/clang/8.0.0/include/__clang_cuda_runtime_wrapper.h' like below before you begin building. Thank you.
-#include <string.h>
+#if defined(__fortify_function)
+#define __tmp_value __fortify_function
+#undef __fortify_function
+#include <string.h>
+#define __fortify_function __tmp_value
+#undef __tmp_value
+#else
+#include <string.h>
+#endif

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!


[8.x] Add regression tests for booting service from another service provider

Signed-off-by: Mior Muhammad Zaki<EMAIL_ADDRESS>

NB Tests failing because they need https://github.com/laravel/framework/pull/37405 to be merged first.

I would also make sure that registering a provider in the register method of another provider works as well but this sure fixes future problems on the issue.

This doesn't break on 8.41 and wouldn't be affected by Illuminate\Foundation\Application::boot() since, at that point, all service providers should be registered.


Chunk header usage in C

Brief feature description
The current chunk header is a C++ class and cannot be accessed safely purely with C.
We need an API (or C struct) to allow using the chunk header in C.
Detailed information
The detailed approach needs to be discussed and depends on the desired level of functionality and configuration options the header shall provide to the user.

For my own purposes it is sufficient to expose the size related functions: https://github.com/eclipse-iceoryx/iceoryx/compare/master...neilisaac:c-chunk-header-size
Would you like a pull request for this change?

@neilisaac of course. I had a brief look. You need to add some tests and I guess @MatthiasKillat knows more about the requirements for the C-API than me.

@neilisaac @elBoberido The additions look fine (no full review) and do not break any existing API. We could even use them in CycloneDDS as well (where, due to API freeze a while ago I  partially created some of them for convenience).
I am fine with having a pull request (and reviewing it), but how about tests? We would need some tests of the C-API even if it is a thin wrapper. Do you agree @elBoberido? We can also add them in a separate PR (but all in one PR would be better I guess, as it is not too large).

@neilisaac you can look at test_request_header.cpp from this PR https://github.com/eclipse-iceoryx/iceoryx/pull/1161/files for the tests. They should more or less be like getChunkHeaderWorks

Sorry I missed the comments.  I'd be happy to add tests and make a proper PR as time permits.

@neilisaac no problem. We are looking forward to your contribution and hopefully the next release is not that far away.


Added RSS feed content provider

This is a content provider that other apps can use to read articles. It allows 3rd party apps to work with RSS feeds without having to replicate all the needed code and without having the user subscribe to desired feeds a second time.

Hi, as per what I reply. Kindly explain in more details on what API or standards that you are going to implement before proceed modifying the PR, I could see that the effort is going to be a lot for this PR. Any documentation of the API? Or W3C documentation that I could refer to?


Suggestion: Keyboard mapping?

This would be perfect since I can't use other programs such as Joy2Key while using this.

why? (ex. low ram)

For example I cant use this for Fortnite because i want to have the gyro axis but since one program is managing the joycon no other program can manage it therefore the only options are gyro with no buttons or buttons with no gyro.


#85 Automated e2e testing

This PR can:

clone mockit-release-tools-example
change used version of mockito-release-tools used in mockit-release-tools-example project to current
run ./gradlew performRelease -Preleasing.dryRun
The problem is, that this command doesn't work well on local environment, where GitHub write access token for mockit-release-tools-example is not provided. I started to workaround this problem, but it adds a lot of complexity to tools - see changes in: https://github.com/mockito/mockito-release-tools/pull/127

Thanks a lot for the PR! Just trying it out!!! Check out my review of #127 - we may not need it!

On it. Thanks a lot for freshly baked code for review! :D

Merging. The feature is work in progress and the change is safe because it is not hooked up yet to the workflow.


Fix cuda bug

Fixed a bug where the 4bit kernel would not run and the 4bit old fast kernel would run instead.
I don't know why this happened, but it's probably my mistake.

Sure! I will release patch fix after those two are done.

Great thanks, looking at them now

I have tested this fix and confirmed that group_size + desc_act now works fine again.  Thank you @qwopqwop200 !
Additionally, I have made the following PRs which I hope can go in to 0.3.1 at the same time as this fix:

https://github.com/PanQiWei/AutoGPTQ/pull/205

fixes revision and other huggingface_hub params in .from_quantized(), and extends them to .from_pretrained() also.

https://github.com/PanQiWei/AutoGPTQ/pull/206

Simplify install script so it always installs CUDA extension, and adds the +cuXXX label locally as well as in Github Actions.  With this change, it is now easy to build AutoGPTQ from Docker and in other setups that previously broke.

https://github.com/PanQiWei/AutoGPTQ/pull/207

Add a central version number in __init__.py.__version__ so it can be referenced elsewhere in the code.
This PR is relative to 206 as it also modifies setup.py

https://github.com/PanQiWei/AutoGPTQ/pull/208

Add simple Safetensors metadata saving, getting rid of the confusing "Warning this model has no metadaa" message that people often ask about, and storing some simple information in each saved .safetensors file, including the version of AutoGPTQ that was used to make it. It also lets the user specify their own metadata to save, eg for model-specific information.
I think this could be a useful feature for clients in future, with many possible uses.
This is relative to 207 because it requires the new __version__ identifier.

I have tested all this changes for: installation, inference, and quantisation.

@PanQiWei @qwopqwop200 I'm not sure to understand this fix. Why are the CUDA kernels themselves modified?

@PanQiWei @qwopqwop200 I'm not sure to understand this fix. Why are the CUDA kernels themselves modified?

It's simple. Because cuda kernels are wrong. It was implemented as "faster(FP16) old cuda kernel" instead of "cuda kernel", so I just modified it.


Docs on email generation and some cleanups

Merged, after tweaking the docs a bit, thanks @hackerkid!


Add context menu command to extract timestamps from message

Context: https://discordapp.com/channels/952258283882819595/952260763987349594/1103235011190210650
Option name: "Extract Timestamps"
Input message:

We could meet at 01:00 or 02:00

Output message:

Timestamps in message:
<t:0:t> (01:00)
<t:3600:t> (02:00)

Implemented


GH-441 Add logging to datasource_artifactory_file

For debugging a customer issue #441
Will need users to test with debug logging switch on (TF_LOG=DEBUG terraform apply) and collect the logs for us.
Should be merged and released after #465

@chb0github Yes, since we can't reproduce this numerous time. Logging is the next logical step to see what is happening at our users' machines.

You did. I made a mistake in pushing a incorrectly merged update. So I had to re-do the merge and force push.


Content type issue & fix

Hello!
I've been using your library in a production app for six months now and in general, it's been fantastic! I've run into one little snag, though, and I think I found the fix. In the app I've been serving liquid-based RSS views from the database and setting the content type in the controller to 'application/rss+xml'. However, the content type of the served page has been set to text/html regardless of where I set it. For example, none of these work:
    respond_to do |format|
      format.html {}
      format.rss { render layout: false, content_type: 'application/rss+xml' }
    end

    format.rss {
      response.headers['content_type'] = 'application/rss+xml'
      render layout: false
    }

Even setting it in an after_filter didn't do anything. After some fiddling, I traced it to here:
https://github.com/yoolk/liquid-rails/blob/master/lib/liquid-rails/template_handler.rb#L16
In order to get testing to work locally and on Travis, I had to do the following:

Updated local Ruby version to 2.2.5 and set to use generic .ruby-version syntax
Updated Travis to test against Ruby 2.2.5
Removed Guard as a dependency for Travis due to ruby_dep not working prior to Ruby 2.2

To fix this issue, here's what I did:

Added a test for the content type
Removed line 16 of template_handler.rb that set the content type

Let me know if this makes sense. Thanks for putting together this great library!

Coverage decreased (-0.02%) to 88.939% when pulling 01b19bc135ba1c81abe094dad1c84ee3d79f6602 on GimliLongBow:content-type-fix into ec01b59633faf73073b6f03f39f48ab1a9a38b51 on yoolk:master.

Weird. The build passed on my Travis setup... Sorry, not sure what happened here!
https://travis-ci.org/GimliLongBow/liquid-rails/jobs/128042969

Coverage decreased (-0.02%) to 88.939% when pulling d4b8964f36faf3bf8783fad10fd7ab3b5493ced7 on GimliLongBow:content-type-fix into ec01b59633faf73073b6f03f39f48ab1a9a38b51 on yoolk:master.

Coverage decreased (-0.02%) to 88.939% when pulling d4b8964f36faf3bf8783fad10fd7ab3b5493ced7 on GimliLongBow:content-type-fix into ec01b59633faf73073b6f03f39f48ab1a9a38b51 on yoolk:master.

@chamnap do you have any thoughts on why the test is failing on this side and not on mine? Thanks!

Thanks for the PR. I'll check when i have time. Too busy recently.

I've integrated into the master branch now.


bug occured when click image shown in the preview image tile

I was struggling finding such image tile preview plugins until I find this
It's a great job for achieving the preview like this
However, when I trid to view single image in the preview window, bug occured
I found out that the path in the preview window using "\"( which was commonly used in windows)
while the absolute path in linux using "/"
which make it hard to view single img triggered from "image tile viewer" by default viewer
# source img path:
/usr/images/a.jpg

# preview img's path in image tile viewer:
\usr\image\a.jpg

# which made it impossible for understanding path for linux

I'd appreciate it if you could fix the bug
btw, it's eager for me to call "image tile preview" by right click if you could help
I'm glad to recommend this plugin for my colleagues
and sincerely waaaiting for your response
Thanks

@Ying-Kang
Thank you for reporting issue!

However, when I trid to view single image in the preview window, bug occured

Please let me confirm about the bug.
Are you saying that the tile view is fine, but when you click on an image, the view is broken? (like below image)

This is probably caused by an update of VSCode.
I checked and it seems to happen in both windows and linux.
I`d like to investigate about solution.

btw, it's eager for me to call "image tile preview" by right click if you could help

Thanks for the suggestion!
I'd like to see if I can add an image tile view menu when I left click on a folder in the explorer treeview.

Thank you for nice suggestion and reporting bug!
The feature is added, the bug is fixed in v0.2.2.

wonderful job！cool

Such a great extension for me! Nice job.
Actually, I still get this error when I try to preview a single image.
My VS Code<EMAIL_ADDRESS>Pls. help.

Thank you for reporting issue.
I can reproduce it in windows11.
I am researching to fix this issue, but I can`t find solution.
Please wait for some time, sorry.

I can find the solution and fix the problem.
The bug is fixed in v0.2.3.
Thank you.

Issue checked.
Thank you so much!


[Vendetta Incompatibility Report] v203.10+ Discord stable builds

(Logs are accessible on screenshots)

The fix is published globally to official servers from where Vendetta code is loaded and injected into every Vendetta by default so this issue is now closed.
Thanks for the dev and all contributors who helped to fix this global compatibility issue!
We're looking forward for future bug fixes after this global change about themes and etc... but enough things are already done - thank you so much and have a great day/night!


[Feature] Add support for Platform Spark features

Motivation: Why do you think this is important?
This helps platform administrators roll out features where the details should be abstracted out from users like turning on S3Guard support to help solve consistency issues with Spark writing to S3.
Users would be able to request a number of features to be turned on or off and platform handles the actual spark-config/other details.
Goal: What should the final outcome look like, ideally?
Users would be able to request a number of features to be turned on or off and platform handles the actual spark-config/other details.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Flyte component

[ ] Overall
[ ] Flyte Setup and Installation scripts
[ ] Flyte Documentation
[ ] Flyte communication (slack/email etc)
[ ] FlytePropeller
[ ] FlyteIDL (Flyte specification language)
[ ] Flytekit (Python SDK)
[ ] FlyteAdmin (Control Plane service)
[ ] FlytePlugins
[ ] DataCatalog
[ ] FlyteStdlib (common libraries)
[ ] FlyteConsole (UI)
[ ] Other

[Optional] Propose: Link/Inline
If you have ideas about the implementation please propose the change. If inline keep it short, if larger then you link to an external document.
Additional context
Add any other context or screenshots about the feature request here.
Is this a blocker for you to adopt Flyte
Please let us know if this makes it impossible to adopt Flyte

This was done.

This is available in v0.8.0


Documentation

The following information should be added to the documentation once the Python codes are finished:

[ ] Pleiotropy
[ ] Dominance
[ ] TraitModel (Indicate how users can set their own model)
[ ] Causal sites
[ ] Multiple allele (This is an advantage of tstrait, but it is not mentioned in the documentation)

[ ] Add compatibility with SLiM

Finished creating the documentation


Vue.js

Referencing the .css and .js files in the index.html page in a vue.js project keeps throwing this in the console window. Is there a preferred way to include outdatedbrowser in vue.js projects?
Refused to apply style from 'http://localhost:8080/NextGenUI/node_modules/outdatedbrowser/outdatedbrowser/outdatedbrowser.min.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

Moved the files from within the "node_modules" directory into the "static" directory and everything seems to work fine, but I'll miss out on auto updates. Anyone know why this works under static but not node_modules?

I had no luck either. I think the module is not exported properly, so Vue doesn't recognize it as a node module.

It is all about using static when you want to use outdated-browser. Vue uses babel, old browsers may not use es6 features so Vue ( and other frameworks ) causes some problems.
-- Use Static Files


Server not found

when I am trying to connect it gives an error server port is not listening, how to resolve it?

Are you sure that

Desktop app is running and you are entering correct details?
Mobile and PC are connected to same network? (You can connect lappy to
mobile hotspot)
Any error on desktop app console?

On Fri, 13 Apr 2018, 00:45 Snehal7<EMAIL_ADDRESS>wrote:

when I am trying to connect it gives an error server port is not
listening, how to resolve it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/varunon9/Remote-Control-PC/issues/21, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AJWc7MM7wOa1qLjvidT9BwLW72T3Sh6Uks5tn6fcgaJpZM4TSV-f
.


docs(style-guide): make each style clickable for easier referencing

This will make it easier to capture the link to a specific style so that it can be shared.

Just noticed this pull request, there is other discussion on this topic going on in #1397 and #1400, for those interested.

Thanks @KyleMcNutt. Our commits are very similar. One thing mine does different (which I prefer) is that I moved the anchor to the name of the rule (i.e. "Rule of One") That way when the page loads, it shows the rule name at the top, then the rule number below it. I find the name very useful.

@olore I can see that perspective, I was going for the minimal change just to make it more obvious what can be linked to. It looks like from discussion in the other issues that an on-hover icon seems to be the preferred approach, but I'll leave that to the Angular teams designers to decide.

@wardbell I am OK with this.. Are you?

Thanks. Merged as ce05f9b4f


Unit Tests

Description
This pull request changes the following:

Adds unit tests for local / functions that don't involve making Hedera requests. General strategy for snap unit tests are do them where we don't have to depend on mocking Hedera responses, and pick up the gap with functional test using the snap functional test library.

Related Issues

Closes #78

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

Project coverage is 63.84%. Comparing base (f753c3a) to head (c47b617).

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #330       +/-   ##
===========================================
+ Coverage   30.58%   63.84%   +33.26%
===========================================
  Files           7       10        +3
  Lines         206      982      +776
  Branches       48      339      +291
===========================================
+ Hits           63      627      +564
- Misses        134      355      +221
+ Partials        9        0        -9

Files
Coverage Δ

...wallet-snap/packages/snap/src/utils/HederaUtils.ts
76.95% <ø> (ø)

... and 6 files with indirect coverage changes


[MB-8505] Add Cypress test to cover the amended orders flow

Description
This PR adds a cypress test to Orders.js to test the amended orders flow. It starts with a customer that has a previously submitted move and ensures the the upload documents link is visible to them and that they upload amended orders and return to the starting page with a success message
Reviewer Notes
Is there anything missing from the amended orders flow that I should be testing for?
Setup
make e2e_test

Once cypress spins up you should navigate to the test under mymove/orders
If you have issues running the cypress test you can also try running
make e2e_test_fresh

References

Jira story for this change
docs for running cypress test

Messages

:book:
:link: MB-8505

  Generated by :no_entry_sign: dangerJS against d99885d63fd1e7380212983b8fe749a37e915e49

This looks good to me. I can't answer this question for

Also, looking into if I need to use cy.intercept for the api call to /amendOrders
so it might be good to ask in frontend channel about this.

Thanks for reviewing! Should I change the name of the uploaded file as well?
And since posting that review note, I read in the docs that cy.intercept is for stubbing out API calls which they suggest to use sparingly and only for critical paths because it can slow down the test. And I've added @kylehilltruss as a reviewer so I'll wait to see if I should change this or not


Was just deceived by the wallet / add "Address copied to clipboard" visual feedback

I've withdrawn 29.45047 from Kucoin https://raiblocks.net/block/index.php?h=FB9E672D51E41C5D70B1F550BD8BD11711D50A0526E18574023E1B7B26293B93 to the wrong address because Ctrl + C failed to copy the account on raiwallet, it instead kept the clipboard of an address of an old transaction from the main window from raiwallet that happened before.... WHAT NOW?
it was supposed to have copied xrb_3fi16pk4gyz331r4531m7jywrfsgp3h31yoyfusac77esuamh65r5kwjz7dm

this issue is partially done, the "Copy" button on the main window shows "Copied!" after being pressed, but there's no feedback when using Ctrl + C on the account column in the ListView (which was the problem from the start)

I had exactly the same problem and I luckily manage to recovery my funds thanks to NanoMiner.
I thought I copied from account list using Ctrl + C and didn't check the address before send (yep, I was stupid)


System.Data.DataRow array serialization error

Describe the bug
When a proxy returns an array of DataRow System.Runtime.Serialization.SerializationException is thrown.

CoreRemoting.RemotingException: Error processing message.
---> System.Runtime.Serialization.SerializationException: Type 'System.Data.DataRow' in Assembly 'System.Data.Common, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not marked as serializable.
at System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(Type type)
at System.Runtime.Serialization.FormatterServices.<>c.b__5_0(MemberHolder mh)
at System.Collections.Concurrent.ConcurrentDictionary2.GetOrAdd(TKey key, Func2 valueFactory)
at System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type type, StreamingContext context)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo()
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, BinaryFormatterWriter serWriter)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph)
at CoreRemoting.Serialization.Binary.BinaryFormatterExtensions.SerializeByteArray(BinaryFormatter formatter, Object objectToSerialize)
at CoreRemoting.Serialization.Binary.BinarySerializerAdapter.Serialize[T](T graph)
at CoreRemoting.RemotingSession.ProcessRpcMessage(WireMessage request)
at CoreRemoting.RemotingSession.OnReceiveMessage(Byte[] rawMessage)
--- End of inner exception stack trace ---

To Reproduce
Steps to reproduce the behavior:

Run this code on net6

public class Program
    {
        private static void Main(string[] args)
        {
            try
            {
                var server = new RemotingServer(new ServerConfig
                {
                    HostName = Environment.MachineName,
                    NetworkPort = 7801,
                    RegisterServicesAction = container =>
                    {
                        container.RegisterService<ISession, Session>(ServiceLifetime.Singleton);
                    },
                    Serializer = new BinarySerializerAdapter()
                });

                server.Error += Server_Error;
                server.Start();

                var client = new RemotingClient(new ClientConfig
                {
                    ServerHostName = Environment.MachineName,
                    ServerPort = 7801,
                    Serializer = new BinarySerializerAdapter()
                });

                client.Connect();

                ISession session = client.CreateProxy<ISession>();
                IEntity[] entities = session.GetEntities();
            }
            catch (Exception ex)
            {
                Console.WriteLine(ex);
            }
        }

        private static void Server_Error(object sender, Exception e)
        {
            Console.WriteLine(e);
        }
    }

    [ReturnAsProxy]
    public interface ISession
    {
        IEntity[] GetEntities();
    }

    public class Session : ISession
    {
        public IEntity[] GetEntities()
        {
            EntityTable table = new EntityTable();

            table.LoadDataRow(new object?[] {19}, true);
            table.LoadDataRow(new object?[] {29}, true);

            table.RemotingFormat = SerializationFormat.Binary;

            var ret = new ArrayList(table.Rows.Count);
            foreach (EntityRow row in table.Rows)
                ret.Add(row);
            return (IEntity[])ret.ToArray(typeof(IEntity));
        }
    }

    [ReturnAsProxy]
    public interface IEntity
    {
        long ID { get; }
    }

    [Serializable]
    public class EntityRow : DataRow, IEntity
    {
        public long ID
        {
            get => (long)(this[((EntityTable)Table).IDColumn]);
            set => this[((EntityTable)Table).IDColumn] = value;
        }

        public EntityRow(DataRowBuilder rb)
            : base(rb)
        {
        }
    }

    [Serializable]
    public class EntityTable : DataTable
    {
        public DataColumn IDColumn { get; set; }

        protected override DataRow NewRowFromBuilder(DataRowBuilder builder)
        {
            return new EntityRow(builder);
        }

        public EntityTable()
        {
            BeginInit();
            IDColumn = new DataColumn("ID", typeof(long), null, MappingType.Element);
            Columns.Add(IDColumn);
            EndInit();
        }

    }

Expected behavior
entities must be serialized. Classic remoting behaves like this

If in the case we are talking about object serialization in common way so it is restricted to serialize DataRow(s) orphaned from its' DataTable by-design. So that is why DataRow does not marked with Serializable attribute. You can serialize a DataTable but not a DataRow or it's derivates.
But if you are expecting to get an enumeration of proxies

[ReturnAsProxy]
public interface IEntity { ...

that seems to be a feature request maybe.

I expecting enumeration of proxies

Return type of GetEntities method is IEntity[]. It is not possible to set [ReturnAsProxy] attribute to an array.
[ReturnAsProxy] should only be used for service types, not for DTOs.
It is bad practice to access DTOs via proxy. Every single property access will trigger an RPC call. There is more protocol overhead send over the wire than data.
I would strongly recommend to take a different approach.
You could use DataTable, typed DataSets (A table of a typed DataSet can also be used standalone without creatinga DataSet instance) or POCOs instead for example. DTOs should be serializied, not proxied. RPC interfaces should be chunky, not chatty. This are best practice since the late 90s.


ODBC17, PDO SQLSRV and IMAGE, VARBINARY, VARCHAR(MAX) field returns corrupted data

PHP Driver version or file name

5.6.1

SQL Server version

2012

Client operating system

CentOS 7.7.1908

PHP version

7.3.10

Microsoft ODBC Driver version

<IP_ADDRESS>

ODBC.ini
[CONN]
Driver = ODBC Driver 17 for SQL Server
Description = SRV
Server = srv.domain.com,1433
ServerSPN = MSSQLSvc/srv.domain.com:1433
Database = MyDB
Trusted_Connection = Yes

Problem description

When attempting to retrieve data from field type image, data contains NULL value every 255 chars. Also data stream doesn't look like binary but like hex. I've tried to remove all NULLs from stream and then hex2bin() but after conversion stream looks corrupted also.

Expected behavior and actual behavior

In old Sybase driver I've received binary PDF file

Repro code or steps to reproduce
$query = $this->query("
--Data is IMAGE type field
SELECT Data FROM Table WHERE Id = :Id
");
$stmt = $this->pdo->prepare($query);
$stmt->bindValue(':Id', $Id, \PDO::PARAM_INT);
$stmt->execute();
$row = $stmt->fetch(\PDO::FETCH_ASSOC);
$bin_data = $row['Data'];

Expecting binary data, but receiving this (NULL every 255th char):

@Wooya I believe you are using the pdo_odbc driver by accident, as I can only reproduce your output with pdo_odbc and not with pdo_sqlsrv. To use the pdo_sqlsrv driver, prepend sqlsrv and not odbc to the connection string as follows:
$conn = new PDO("sqlsrv:server=myserver.....", $uid, $pwd);

In addition, to retrieve binary data you must bind LOB and binary PDO types to the binary column, as follows:
$stmt = $conn->query("SELECT Data FROM Table");
$stmt->bindColumn('Data', $img, PDO::PARAM_LOB, 0, PDO::SQLSRV_ENCODING_BINARY);
$row = $stmt->fetch(PDO::FETCH_BOUND);
var_dump($img);

Please try this and let us know if it works.
Note also that the image type is deprecated and will be removed in a future version of SQL Server - we advise using varbinary(max) in place of image as much as possible.

@david-puglielli Thank you for your response. Of course I'm using pdo_odbc not pdo_sqlsrv. I've tried with pdo_sqlsrv and it works like a charm.


Upgrade to be compatible with pyfirecreset v2.5.0

Some TODO's are done
Wherever relevant issues opened and addressed in aiida-core, pyfirecrest, and firecrest
Added new tests. The old tests, although more sophisticated is harder to debug. New tests focuses only on aiida-firecrest by mocking pyfirecrest only, not firecrest server.
Current states still depends on un-merged PR#6043, but functional with latest features of aiida v2.5.2

As discussed with @khsrali offline, I am fine with removing integration test by using firecrest image to mock some real response. As @khsrali pointed out, pyfirecrest did not do it as well. But I'd suggest to still keep it in mind and open an issue to remember to bring it back with the help from CSCS people to provide a robust and easy to deploy docker-compose solution.


EcdsaTestCase::test_roundtrip fails with ecdsa-0.15

Hi,
It looks like EcdsaTestCase::test_roundtrip fails on newer versions of ecdsa; jsonpickle 1.4.1 w/ ecdsa 0.14.1 passes, while jsonpickle 1.4.1 w/ ecdsa-0.15 fails.
 A deep copy is serialized instead, breaking memory aliasing.
    warnings.warn(msg)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
===================================================================== short test summary info ======================================================================
FAILED tests/ecdsa_test.py::EcdsaTestCase::test_roundtrip - TypeError: %x format: an integer is required, not dict
====================================================== 1 failed, 267 passed, 21 skipped, 2 warnings in 7.61s =======================================================
 * ERROR: dev-python/jsonpickle-1.4.1-r1::gentoo failed (test phase):
 *   Tests failed with python3.7
 *

I've also attached some system information here. Please let me know if I can provide any more information.
Thanks!

I just noticed that this is related to #328, I'll be discussing what I plan to do in that issue.


Small clean up

Remove redundant queryEndTime. Use UtcNow that should be faster

Removed AverageMetricProvider because it was implemented by 'Mean' metric in the StatisticalMetricsProvider

Update README.md

Great fix!
Thank you


cookie-cutter project

I don't know if this is present in a different project, but it would be nice to have a cookie-cutter project to highlight:

Modern CMake project design
Modern CI tools for Python and C++
Incorporate bindings with Swig or other language specific ones like pybind, including packaging via skbuild-core
Tools for downstream packaging and testing

In designing and modernizing some CMake projects, I've found quite a few hidden gems that are available in CMake like FeatureSummary, the interplay between FetchContent and find_package, etc. and I want to share them in a more accessible location. Do you think we can host this here or in a different organization?
I'm not familiar with cookie-cutter engines, and I think that could clash with having a plain repo that people can navigate and learn through the documentations and comments. If you know of a good example that have a balanced of these let me know.

I'd recommend first looking at https://github.com/scientific-python/cookie (cookiecutter and copier supported), as well as https://github.com/pybind/scikit_build_example (plain repo). Yes, it's not great navigating a cookiecutter repo directly. It could possibly be rendered into documentation (that's partially done for scientific-python/cookie, some of the code blocks are rendered from the cookie).
I don't really want to maintain two cookiecutters (especially at the scale of scientific-python/cookie, which is a guide + cookie with 10+ backends + repo-review plugin, included via WebAssembly in the guide) until it's necessary. What I was thinking is that maybe skbuild new could provide this sort of setup. If that doesn't work / is too much work, having a cookiecutter that only produces scikit-build projects, but has options for which binding tool to use, etc. is something we should eventually add.

What I was thinking is that maybe skbuild new could provide this sort of setup.

Do we include CI tools in there as well? I was thinking for that we only focus on cmake + skbuild-core, and we could reference to a template project otherwise for more details on CI tools and everything.

Also see https://cliutils.gitlab.io/modern-cmake, my book on Modern CMake.

Good book, I might quote it some times for quick reference ;). I have some notes on some other paradigms that I want to share, but it would be clearer in an example repo.
For now, how about if I make a plain repo to first show-case some of the topics I want to highlight.

Still working on it, but the WIP is in https://github.com/LecrisUT/CMake-Template/pull/1

Btw, I've added documentation to my template project, but could always use more comments and discussion on the ideas in there. My plan is to keep that template as bare-bones like that with just the minimum for a modern CMake project, and then have daughter templates, e.g. python interface, which links back to the base template for the common documentation and builds up on the specific topic. Thoughts?