webpack 3.x best practical & webpack 4.x best practical

webpack 3.x best practical
https://www.cnblogs.com/xgqfrms/p/9515189.html
multi pages
webpack 4.x best practical
https://www.cnblogs.com/xgqfrms/p/9109493.html

webpack html plugin multiple entry
https://github.com/jantimon/html-webpack-plugin/issues/218
https://webpack.js.org/plugins/html-webpack-plugin/
Multi Page Application

this is possible via multiple instances of the HtmlWebpackPlugin

https://github.com/jantimon/html-webpack-plugin/issues/218#issuecomment-183066602
https://github.com/jantimon/html-webpack-plugin#options
https://github.com/jantimon/html-webpack-plugin#generating-multiple-html-files

webpack.config.js

{
  entry: 'index.js',
  output: {
    path: __dirname + '/dist',
    filename: 'index_bundle.js'
  },
  plugins: [
    new HtmlWebpackPlugin(), // Generates default index.html
    new HtmlWebpackPlugin({  // Also generate a test.html
      filename: 'test.html',
      template: 'src/assets/test.html'
    })
  ]
}

https://github.com/webpack/docs/wiki/configuration#outputpublicpath
https://webpack.js.org/concepts/entry-points/
https://webpack.js.org/guides/getting-started/#using-a-configuration
jade
https://github.com/jantimon/html-webpack-plugin/blob/master/examples/inline/template.jade
https://github.com/webpack/docs/wiki/node.js-api#stats

https://github.com/kaola-fed/blog
https://blog.kaolafed.com/2017/08/10/HTTP请求中的Form Data与Request Payload的区别/

https://github.com/xgqfrms/FEIQA/issues/22#issuecomment-414206129

OK
it's ok now

jsut remove inject: false,

manaully setting multi pages

    new HtmlWebpackPlugin({
        // inject: false,
        hash: true,
        chunks: ["app"],
        template: "./src/html/app.html",
        filename: "./pages/app.html"
        // filename: "./pages/[name].html"
    }),
    new HtmlWebpackPlugin({
        // inject: false,
        hash: true,
        chunks: ["main"],
        template: "./src/html/main.html",
        filename: "./pages/main.html"
    }),
    new HtmlWebpackPlugin({
        template: "./src/html/index.html",
        filename: "./index.html",
        chunks: ["index"],
        // chunks: ["app", "main"],// load modules order ??? fifo
        hash: true,
        // minify: true,
        minify: {
            collapseWhitespace: true,
            collapseInlineTagWhitespace: true,
        },
    }),


runtime: mayMoreStackPreempt failures

#!watchflakes
post <- section == "maymorestack=mayMoreStackPreempt"

Intermittent failures in the new mayMoreStackPreempt. This bug will replace #54778 and #55073.

These were coming in multiple times per day and have now stopped for almost two weeks. Closing.

No more failure for a while. Probably fixed by CL https://golang.org/cl/447495 , which is submitted at Nov. 4, so the time seems to match.

cc @aclements
These timeouts blocked release branch CLs as flakes; we should get them fixed or skipped.

This reproduces pretty quickly on my linux/amd64 laptop with:
cd runtime
go test -c
GOFLAGS="-gcflags=runtime=-d=maymorestack=runtime.mayMoreStackPreempt -gcflags=runtime/testdata/...=" stress2 ./runtime.test -test.run=CrashDumpsAllThreads

Of course, my usual first step would be to send it a SIGQUIT and see what's happening, but that's exactly what fails in this test. 😛 I haven't debugged yet. gdb may hold answers.
For reference, I initially tried running the testprog directly with the below script before I realized there are various pipes and signals involved in running this test. We might still need to reproduce those, but I'm hoping we can debug this through the test driver.
cd runtime/testdata/testprog
GOFLAGS="-gcflags=runtime=-d=maymorestack=runtime.mayMoreStackPreempt -gcflags=runtime/testdata/...=" go build
# Expects to write to FD 3 and then get a SIGQUIT
GOTRACEBACK=crash GOGC=off GODEBUG=asyncpreemptoff=1 ./testprog CrashDumpsAllThreads

All of the Ms are just parked in mPark in normal places in the scheduler, except one thread that's in the infinite loop in crashDumpsAllThreadsLoop. /proc/PID/status and /proc/PID/task/*/status says there are no signals pending, blocked, or ignored by the process or any of its threads. It's a little suspicious that the blocked mask is 0, and in another Go process I have running it's fffffffc3bfa3a00.

Ah hah, it's getting stuck before the SIGQUIT is involved. It's actually getting stuck in this loop, before the subprocess even indicates to the parent that it's ready for the SIGQUIT.

Here's a version that works without a patch:
cd runtime/testdata/testprog
GOFLAGS="-gcflags=runtime=-d=maymorestack=runtime.mayMoreStackPreempt -gcflags=runtime/testdata/...=" go build
GOTRACEBACK=crash GOGC=off GODEBUG=asyncpreemptoff=1 stress2 -timeouts-fail -max-fails=1 -timeout=10s -pass="write to pipe" -max-runs=50000 ./testprog CrashDumpsAllThreads

This isn't new, either. I reproduced in Go 1.18, which was the first release to have mayMoreStack.

@golang/runtime, should TestCrashDumpsAllThreads be skipped in the mayMoreStackPreempt configuration, or is there some other action in progress for this failure?

https://storage.googleapis.com/go-build-log/7a497521/linux-amd64-longtest_4c66413d.log (a SlowBot run)

The cause of this flake (using Austin's reproducer above) is maymorestack instrumentation of any one (or more) of:
runtime.closechan
runtime.newobject
runtime.mallocgc
runtime.lock2
runtime.makechan
runtime.newproc
runtime.deductAssistCredit

beyond that I don't know.  I found these using compiler hash debugging and gossahash (both of these are being renovated/enhanced/replaced in coming weeks).

I believe this is a bug in https://go.dev/cl/7314062. (Yes, a 10 year old bug).
The "delicate dance" when a spinning M transitions to non-spinning is supposed to check all sources of work, but it doesn't check the global run queue: https://cs.opensource.google/go/go/+/master:src/runtime/proc.go;l=3084;drc=5b6e6d2b3d4d6877c86471209e249f1b6e36d0ca
gosched / mayMoreStack put the preempted goroutine on the global run queue, increasing the chance of failure (in addition to the extra stress it puts on the scheduler in general). Still, I am surprised this bug could go unnoticed for so long.
With that issue fixed, I can no longer reproduce this hang.
@gopherbot Please open backports to 1.20 and 1.19. This is a hang in the scheduler with no work around.

There is actually a second, similar issue: gosched (runtime.Gosched as well as morestack and async preemption) don't call wakep. They are submitting runnable work to the scheduler, so they must follow the same protocols for synchronizing with spinning Ms as any other source of work.

Although this bug is causing failures, I think @prattmic decided to wait until Go 1.22 to land the fix? The changes aren't that complex, but the modified parts of the codebase are subtle. The primary failure modes are mitigated (I think? Why did we see a failure on June 16th if the test was skipped with mayMoreStack on June 6th? Oh. Is that a release branch?). We can also choose to backport it later.

Correct, the sweet results from my CLs are:
                     │ baseline.results │          cl501975.results          │          cl501976.results          │
                     │      sec/op      │   sec/op     vs base               │   sec/op     vs base               │
BiogoIgor                    13.89 ± 0%    13.90 ± 1%       ~ (p=0.523 n=30)    13.92 ± 0%       ~ (p=0.192 n=30)
BiogoKrishna                 11.99 ± 1%    11.95 ± 0%       ~ (p=0.197 n=30)    11.92 ± 1%       ~ (p=0.328 n=30)
BleveIndexBatch100           4.744 ± 1%    4.744 ± 1%       ~ (p=0.775 n=30)    4.755 ± 1%       ~ (p=0.592 n=30)
EtcdPut                     32.99m ± 1%   32.76m ± 1%       ~ (p=0.552 n=30)   33.07m ± 1%       ~ (p=0.843 n=30)
EtcdSTM                     146.7m ± 0%   147.1m ± 0%       ~ (p=0.382 n=30)   147.1m ± 0%       ~ (p=0.254 n=30)
GoBuildKubelet               51.63 ± 0%    51.72 ± 0%  +0.18% (p=0.036 n=30)    51.86 ± 0%  +0.45% (p=0.000 n=30)
GoBuildKubeletLink           7.316 ± 1%    7.317 ± 0%       ~ (p=0.959 n=30)    7.317 ± 0%       ~ (p=0.971 n=30)
GoBuildIstioctl              44.36 ± 1%    44.57 ± 0%  +0.46% (p=0.013 n=30)    44.60 ± 0%  +0.54% (p=0.007 n=30)
GoBuildIstioctlLink          7.789 ± 0%    7.798 ± 0%       ~ (p=0.286 n=30)    7.799 ± 0%       ~ (p=0.562 n=30)
GoBuildFrontend              16.04 ± 0%    16.08 ± 0%  +0.26% (p=0.021 n=30)    16.10 ± 0%  +0.41% (p=0.001 n=30)
GoBuildFrontendLink          1.282 ± 1%    1.272 ± 1%       ~ (p=0.177 n=30)    1.274 ± 1%       ~ (p=0.358 n=30)
GopherLuaKNucleotide         21.87 ± 1%    21.80 ± 1%       ~ (p=0.485 n=30)    21.49 ± 1%  -1.77% (p=0.000 n=30)
MarkdownRenderXHTML         259.5m ± 2%   259.4m ± 1%       ~ (p=0.552 n=30)   263.4m ± 3%       ~ (p=0.843 n=30)
Tile38QueryLoad             511.6µ ± 0%   511.9µ ± 0%       ~ (p=0.562 n=30)   514.5µ ± 0%  +0.55% (p=0.000 n=30)
geomean                      2.087         2.086       -0.06%                   2.090       +0.11%

The effect here is pretty small, but has the potential to be bigger for edge-case applications. I'd be more comfortable giving this time to soak during 1.22.
This can cause complete stuckness when GOMAXPROCS=1 and GODEBUG=asyncpreemptoff=1. Avoiding either of those should avoid hangs (though the scheduler may still underutilize GOMAXPROCS) [1].
[1] Technically if async preemption is disabled, then it takes GOMAXPROCS goroutines spinning in an infinite loop to cause stuckness. So GOMAXPROCS=2 could still hang if there are 2 spinning goroutines.

https://go.dev/cl/501229 should be skipping this test entirely. I agree it is odd that we got another failure on June 16 (it isn't a release branch). Maybe that GCFLAGS check isn't correct?

The TestNetpollDeadlock failures seem like #66275, so I'm inclined to say it's not specific to mayMoreStack and close this for now.

I have a revert CL out to fix this.

I think I understand what went wrong here. Looks like the fact that this CL made the tracer more preemptible also made it much more likely that the trace would have a broken tail. The test seems to succeed overall though, because other invariants it checks are completely fine. I think I know how to fix this to re-land it.

Revert landed.

The non-Windows failures are likely just stragglers from the fix. The Windows failures are likely because something is failing to flush (a pipe, in this case...?).

Should we skip this test on Windows until the flakiness is fixed?

@matloob Ah, sorry for missing this.
I'll send a skip and/or a fix ASAP.

I was able to reproduce. I may be able to find a fix.


Combining Ambient RNA Methods

Thank you for the helpful package. I'm curious about the feasibility of integrating multiple ambient RNA analysis methods simultaneously. Specifically, I have observed improved results when using SoupX in conjunction with DecontX. Is it advisable to combine these methods, and if so, are there any specific considerations or best practices to keep in mind during the integration process?

Hello @Reyhaneh92, thanks for using our tool. We have not tested it in combination with SoupX. There are different assumptions and techniques used by each algorithm so I would be hesitant to combine them. decontX can be run a few different ways as well (i.e. with and without the raw background matrix). It would be hard for me to give you a definitive answer without knowing more about your data and the performance of each tool.  If you can provide details or example, that would be helpful.


Project System: Fix Microsoft.VisualStudio.Editors package def to be auto-generated

From @davkean on April 1, 2016 17:25
Currently, Microsoft.VisualStudio.Editor's pkgdef is hand-written + expected to be pre-processed. We should move it an auto-generated model.
Copied from original issue: dotnet/roslyn#10253

While this might be a lot of work to figure them all out - we should at least move the ones with versions numbers out, see: https://github.com/dotnet/roslyn-project-system/pull/9

I've got to hand modify the pkgdef to add a project page, which annoys me. This is too much to do for that, but I'll take it.


chore: rebuild package-lock file

Description of changes:
@cloudscape-design/* packages are not inside package-lock but some of their dependencies are.
That's why we need to regenerate the lock file from time to time.
Testing

Tested by the PR build.

Related Links

Related PR which cause the update: https://github.com/cloudscape-design/components/pull/493/files

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Already fixed there: https://github.com/cloudscape-design/theming-core/pull/23
Thanks for trying, but too late


Issue Identified with Daemon and CentOS 7.4

Panel or Daemon: Daemon
Version of Panel/Daemon: 0.4.3 (This issue was also reported with 0.4.5)
Server's OS: CentOS 7.4
Your Computer's OS & Browser: Windows 10 Pro & Google Chrome

Add Details Below:

Docker version: Docker version 17.11.0-ce, build 1caf76c
Kernel Version: 3.10.0-693.2.2.el7.x86_64

This issue was identified by experiencing stability problems with the daemon after 90 days of uptime. Severe performance degradation took place, and effectively rendered the daemon unusable without a reboot. However, upon further investigation, and another report from another host, the issue has been identified as a much more severe issue that appears to be related to the way the daemon and docker inter-operate with each other...it's worth noting the following:

This does not affect all nodes. It appears only after about 80-90 days of uptime
The issue is not solely bound to the docker update users seem to have been having issues with
This also seems to correlate with the amount of active servers on a single node. This only occurs with about 25-35 servers on a single daemon.

Kernel Logs from /var/log/messages
NMI watchdog: BUG: soft lockup - CPU#2 stuck for 21s![kworker/2:0:23909]
NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:33]
NMI watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:1:20761]
NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [java:16709]
NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [swapper/5:0]
NMI watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:1:20761]
NMI watchdog BUG: soft lockup - CPU#2 stuck for 24s! [kworker/2:1:20761]
NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [swapper/3:0]
NMI watchdog: BUG: soft lockup - CPU#7 stuck for 23s! [du:15885]
NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0]

It is worth noting that the server throughout this time is not loaded anywhere near the thresholds for this to be appearing. Also, the server becomes completely unresponsive.
I have assumed that according to the logs, this primarily became a issue with docker and specifically the daemon (as seen here, [du:15885] assuming that the daemon uses this to determine the directory size of the container upon server initialization)
It is also worth noting that java is also not installed on the host machine, isolating the possibility of this being a issue with the host machine.
Upon further investigation and collaboration, we have also discovered this within the kernel logs of the time from when the server becomes unresponsive, will be placed in hastebin for easier readability.
https://hastebin.com/lituniledo.sql
Within this, one thing that appears to pop out most is this:
kernel: cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmem_cache(935:9cd527dd5e1a39ddc876e23563ac23e13244e42530eccbd9e3df1843d6433225)
We decided to investigate further, as this occurred right after docker has initialized a container, the issues appear right after docker initializes a container.
Additional Information
df -h | grep 9cd527dd5e1
shm              64M     0   64M   0% /var/lib/docker/containers/9cd527dd5e1a39ddc876e23563ac23e13244e42530eccbd9e3df1843d6433225/shm

This is a active docker container.
I will be doing my own investigations into this to see if I can come up with anymore information regarding this and post it here, however, it is a issue that I feel should be given some attention because it has caused stability issues.

I got this issue with skynode aswell with one of our nodes and we are running Ubuntu 16.04,same kernel log, our solution was a re-installation of the daemon, but recently we got a unreposive machine again with other of our node

our solution was a re-installation of the daemon

A re-installation is not required.

Yeah, this doesn't look like something that would be solved by reinstalling the daemon, it appears to be an issue with how docker is being utilized somewhere.

@DaneEveritt
Kernel Log Analysis
Dec 19 18:30:25 na03 kernel: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:2:8207]
Grepped through /var/log/messages*, found a docker container causing the issue with the log output:
Dec 19 18:30:25 na03 kernel: cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmem_cache(3532:ef171cc37418c03757281d3336e9574b4127d2fa20906aea14740c7d611b48d0)
Both of these time stamps are the same, associating the two issues together.
A few moments later, with the same docker container, as requested, this is the output docker had:
Dec 19 20:29:09 na03 dockerd: time="2017-12-19T20:29:09.171525074-05:00" level=info msg="Removing stale sandbox ebf910be49548a381045504c5326ced4cf911802d82e2464ac805754c7025438 (ef171cc37418c03757281d3336e9574b4127d2fa20906aea14740c7d611b48d0)"
This container afterwards was not problematic for this specific node and has been stable for 3 days... (this was after the cleanup process, which involved stopping the daemon, and stopping and rebuilding all server containers)
Update:
Additional Information

A problematic issue arose in CentOS 7.4/7.3 based systems running EXT4 file systems with the overlayfs driver causing several containers failing to rebuild with the container being mounted by a random rouge process. This has since been resolved by deploying nodes with XFS file systems.
Nodes with XFS are also experiencing this issue
The issue reported above (moby/moby#19758) is NOT exactly the same. overlayfs does not seem to a culprit as much as in the aforementioned issue. Within the kernel log, this is the only thing that is displayed:

Dec 19 20:28:45 na03 dockerd: time="2017-12-19T20:28:45-05:00" level=info msg="loading plugin "io.containerd.snapshotter.v1.overlayfs"..." module=containerd type=io.containerd.snapshotter.v1
As indicated in the previous report;
Feb 22 06:56:59 ip-10-10-2-15 kernel: Modules linked in: xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter nf_nat nf_conntrack isofs overlay cirrus ttm drm_kms_helper drm ppdev 8250_fintek input_leds syscopyarea sysfillrect parport_pc sysimgblt i2c_piix4 parport fb_sys_fops pcspkr ceph libceph fscache ip_tables xfs libcrc32c ata_generic pata_acpi crct10dif_pclmul crc32_pclmul crc32c_intel aesni_intel lrw xen_blkfront xen_netfront gf128mul glue_helper ablk_helper ata_piix cryptd serio_raw libata floppy fjes sunrpc dm_mirror dm_region_hash dm_log dm_mod
Feb 22 06:56:59 ip-10-10-2-15 kernel: CPU: 12 PID: 8327 Comm: docker Not tainted 4.4.44-1.el7.elrepo.x86_64 #1
Feb 22 06:56:59 ip-10-10-2-15 kernel: Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016

Please use ``` around multiline sourcecode/logs for better formatting ;)

Overlay fs on cent is very much experimental still. I recommend against is. I have seen fewer issues with xfs and no issues with zfs. This appears to be a Docker issue though.

Overlay fs on cent is very much experimental still. I recommend against is. I have seen fewer issues with xfs and no issues with zfs. This appears to be a Docker issue though.

I'll see if changing the storage driver to overlayfs2  along with a kernel upgrade resolves this issue. I'll report back my findings after the holidays


sklearn install error

pip install SoccerNet matplotlib sklearn
Looking in indexes: http://mirrors.aliyun.com/pypi/simple
Collecting SoccerNet
Using cached http://mirrors.aliyun.com/pypi/packages/6e/b2/e71bec7145b62314c400bf86e5f5df8a09b7dc3cbbbe78c7ad108ce7af30/SoccerNet-0.1.60-py3-none-any.whl (85 kB)
Collecting matplotlib
Using cached http://mirrors.aliyun.com/pypi/packages/30/33/cc27211d2ffeee4fd7402dca137b6e8a83f6dcae3d4be8d0ad5068555561/matplotlib-3.7.5-cp38-cp38-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (9.2 MB)
Collecting sklearn
Using cached http://mirrors.aliyun.com/pypi/packages/46/1c/395a83ee7b2d2ad7a05b453872053d41449564477c81dc356f720b16eac4/sklearn-0.0.post12.tar.gz (2.6 kB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [15 lines of output]
The 'sklearn' PyPI package is deprecated, use 'scikit-learn'
rather than 'sklearn' for pip commands.
  Here is how to fix this error in the main use cases:
  - use 'pip install scikit-learn' rather than 'pip install sklearn'
  - replace 'sklearn' by 'scikit-learn' in your pip requirements files
    (requirements.txt, setup.py, setup.cfg, Pipfile, etc ...)
  - if the 'sklearn' package is used by one of your dependencies,
    it would be great if you take some time to track which package uses
    'sklearn' instead of 'scikit-learn' and report it to their issue tracker
  - as a last resort, set the environment variable
    SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL=True to avoid this error

  More information is available at
  https://github.com/scikit-learn/sklearn-pypi-package
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Replace sklearn to scikit-learn in pip install command
The final installation command will like this:
pip install SoccerNet matplotlib scikit-learn

btw do NOT replace sklearn in any .py files


First pass at TeamBroker

part of FlowFuse/flowfuse#1350
Description

Add a Team Broker to the docker compose file.
Related Issue(s)

FlowFuse/flowfuse#1350
Checklist

[ ] I have read the contribution guidelines
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

[ ] Upgrade instructions
[ ] Configuration details
[ ] Concepts

[ ] Changes flowforge.yml?

[ ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
[ ] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

[ ] Includes a DB migration? -> add the area:migration label

Still need to do MQTT over TLS

Overall, it looks good. Let's just make a call about the default broker, and I am okay with merging.

@ppawlowski Can you give this one more quick look please

We will leave quick start on the old broker this time.

I had to remove the MQTT WSS listener by default as nginx failed to start if there was no certs/key available

I'm OK with merging this.


Proximity metric

User story

Story

As a Swarm node, I want to know the proximity and distance of any address with another, such that I can use this information to start build up a Kademlia topology
Acceptance criteria

Given two random addresses, the node can calculate the proximity and distance between those addresses

Background

Note: distance is needed for the squared gaps issue
See:

BOS (Appendix A1)
ReadTheDocs, Architecture:

Tasks

Task
Assignee
Done (1), or 0

this is already done


Finding implementation omits classes mixing in that type

It should probably find all of the extends, implements, or with usages.

Hmm, I can't repro the problem anymore...


Embedding gradient performance optimization on GPU

Description
This PR includes a specific Embedding-backward operator for GPU.
Two new CUDA kernels have been implemented for improving the performance of the operator when using GPU.
According to our measurements on Volta GPUs, the previous version was taken 2.2ms,
whereas the new implementation takes 0.3ms, i.e. more than 7x speedup.
Checklist
Essentials

[X ] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage:
Unit tests already existed (tests/python/gpu/test_operator_gpu:test_embedding_with_type) and changes do not affect correctness.
[X] Code is well-documented:
For new C++ functions in header files, their functionalities and arguments are documented.

Changes

[x ] Embedding-backward operator for GPU, test: tests/python/gpu/test_operator_gpu:test_embedding_with_type

@sxjscience FYI

Nice! LGTM. So the BinarySearch version of FindBounds has complexity O(|V| log |N|) where |V| is the vocabulary size and |N| is the number of indices. I guess our initial version has complexity O(|N|) for finding the boundaries. Thus, in some workloads (in which |N| is small), the O(N) version might be faster.

Moises did a performance comparison between the new version and both the old one and the old buggy one. The new kernel is faster than the old working version in all cases and ~same in speed as the buggy one. The biggest performance change is seen actually when changing how many different elements are in the input data (as small number of distinct elements limits parallelism in the backward pass).


Flow complains when trying to access element properties on Event.target/currentTarget

This may not be a bug as much as it is a question.
If I have an event handler in a React component like so:
handleClick = (e: Event) => {
    console.log(e.currentTarget.name)
}

Flow complains because name is not a property in type EventTarget.
Shouldn't EventTarget be the same as type HTMLInputElement?

Lots of related discussion already: https://github.com/facebook/flow/issues?q=is%3Aissue+Event+currentTarget+is%3Aclosed


UMDifying js-data-angular

Closes #308

So how does this play with the browserify build? Is the browserify build even needed anymore?

I think that this lib doesn't really need browserify honestly. It's pretty small/simple... I'm not sure what browserify is giving you TBH... Though, anytime you want to bring in another dependency, you've gotta add it yourself...

But single-file libs are normally fairly easy to write without a bundler.


fix: Could not find lib folder in

Brick

[ ] model
[x] feature_brick
[ ] app_ui
[ ] service
[ ] service_package

Description
Could not find lib folder in /home/user/IdeaProjects/flutter/blogs
Re-run this brick inside your lib folder
An exception occurred while executing hook: /home/user/.mason-cache/hosted/registry.brickhub.dev/feature_brick_0.6.2/hooks/pre_gen.dart.
Error: Exception

Steps To Reproduce

mason init
mason add feature_brick
mason make feature_brick --feature_name list_blogs --state_management riverpod
See error

Expected Behavior
No error
Screenshots
If applicable, add screenshots to help explain your problem.
Additional Context
Using zsh, if that matters.

Re-run this brick inside your lib folder
...
This is... why... I don't..


refacor the network port setting for AWS

Description
refactor the description of network port setting for AWS.
Issues
the description of network port setting is not clear.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)
[x] Others (enhancement, documentation, validation, etc.)

Dependencies
List the newly introduced 3rd party dependency if exists.
Tests
Describe the tests that you ran to verify your changes.

please update readme of gaudi and ChatQnA

please update readme of gaudi and ChatQnA

yes, update them.

Thank @NeoZhangJianyu and team!


Hardcoded .table-responsive class results in permanently visible horizontal scrollbars

Bootstrap provides resolution-specific variants of this class to work around this issue, such as table-responsive-xl. It would be better if the user could set their own class on the table wrapper instead of having to manually do it with jQuery after table initialization.

You can now configure it - https://github.com/niiknow/vue-datatables-net/blob/62831b8a2a118605606c9b1cbc7f3fbe4446a185/src/VdtnetTable.vue#L53


Suggestion: Intuitive SubArray/SubString Selection in JavaScript

Wouldn't be great if we can select SubArray and SubString as following code example similar in SubList selection in Python?
Code
    // a is a string or an array.
    a[start:end]; // items start through end-1
    a[start:];    // items start through the rest of the array
    a[:end];      // items from the beginning through end-1
    a[:];         // a copy of the whole array
    a[start:end:step]; // start through not past end, by step

Examples
    squares = [1, 4, 9, 16, 25];
    // Already works in TypeScript/JavaScript
    squares[0];     // 1
    squares[-1];    // 25
    squares[-3];    // 9

    // Suggestions
    squares[:]      // [1, 4, 9, 16, 25]
    squares[::2]    // [1, 9, 25]
    squares[::-1]   // [25, 16, 9, 4, 1]
    squares[::-2]   // [25, 9, 1]
    squares[1:4]    // [4, 9, 16]
    squares[0:4:2]  // [1, 9]

Reference

Lists in Python

We don't change the semantics of JavaScript. See the design goals.

Very Right. It should be implement in JavaScript if it must be done not in TypeScript.


Tbkka JSON decoder simplification

This combines the decoder simplification work I recently did for Text decoding with @allevato's work on JSON performance.
It drops 250 lines of code, eliminates quite a few structs and should generally make the code easier to follow.

Specifically, this builds on @allevato's work in #168.

Compared to master, this is:

About 60k smaller dylib (after stripping)
About 1k smaller harness (after stripping)
Almost identical performance (within a few percent)


kuksa-client docker > 400MB on ARM

kuksa-client docker is around 480MiB on ARM, while the "normal" size on x64 is around 95MiB.
Root cause seems to be a fault in the GRPC build process that leaves an unstripped .so
see inside the container
/kuksa-client # du -hcs *
[...]
242.2M	grpc
150.3M	grpc_tools

There is an issue https://github.com/grpc/grpc/issues/29935
the easiest solution is probably just stripping manually when building on ARM

Partially related to observations in #367
If we fix it we could possibly change push: false at https://github.com/eclipse/kuksa.val/blob/master/.github/workflows/kuksa-client.yml#L93


Arrow parse negative number relative to epoch on 0.15 not working for strings

When we upgraded to the latest version it seems the suggested behaviour for parsing strings doesn't allow it to be a negative value relative to epoch.
In [8]: arrow.get(-1565358758)
Out[8]: <Arrow [1920-05-25T10:07:22+00:00]>

In [9]: arrow.get('-1565358758', 'X')
---------------------------------------------------------------------------
ParserMatchError                          Traceback (most recent call last)
<ipython-input-9-9ca34c371f99> in <module>
----> 1 arrow.get('-1565358758', 'X')

/usr/local/lib/python3.7/site-packages/arrow/api.py in get(*args, **kwargs)
     19     """
     20
---> 21     return _factory.get(*args, **kwargs)
     22
     23

/usr/local/lib/python3.7/site-packages/arrow/factory.py in get(self, *args, **kwargs)
    228             # (str, format) -> parse.
    229             elif isstr(arg_1) and (isstr(arg_2) or isinstance(arg_2, list)):
--> 230                 dt = parser.DateTimeParser(locale).parse(args[0], args[1])
    231                 return self.type.fromdatetime(dt, tzinfo=tz)
    232

/usr/local/lib/python3.7/site-packages/arrow/parser.py in parse(self, datetime_string, fmt)
    214         if match is None:
    215             raise ParserMatchError(
--> 216                 "Failed to match '{}' when parsing '{}'".format(fmt, datetime_string)
    217             )
    218

ParserMatchError: Failed to match 'X' when parsing '-1565358758'

Hey @JBKahn looks like we missed this with all the upgrades, thanks for pointing it out.

NP, The patch I submitted should resolve this one

Hey @JBKahn, we have just released 0.15.1 with this fix. Thanks!


No Images at PDF Export

Hi,
after install that Plugin, work all fine. But if I export a PDF that has no Images.
Can you that fixed?
Kind regards
Tobi
PS: I like your Docu, that was wrote good

Investiating this issue, it seems that there's a more severe problem.  If I run the redmine test suite, after enabling redmine_amazon_s3, I'll get some failures with the same pattern:
assert File.exist?(diskfile). They certainly fail, because the diskfile doesn't exist locally.
This is also directly connected to pdf export: Redmine only exports images which are attachments in that wiki page oder issue, and it checks whether the attachment is readble.  Attachment#readable is defined as File.readable?(diskfile), so it'll never be readable if the file is stored on S3.


Specify StC Force from External DLL

Feature or improvement description
Add StC_DOF_Mode to specify force acting on StC from an external DLL.
@andrew-platt, please let me know if I'm missing something normally part of the OpenFAST PR process.
Related issue, if one exists

Impacted areas of the software
StrucCtrl, uses BladedInterface_EX
Additional supporting information

Test results, if applicable

The only other thing would be to update the StC input files in the regression tests.  This might be easiest to clone r-test and do a PR from there to r-test.  Then commit the pointer to that r-test commit to this branch.

I updated the r-tests here: https://github.com/OpenFAST/r-test/pull/88
I think the pointer is to my fork/branch and needs to be fixed.

I tested this by applying a -4e5 N force in the z-direction on the upwind column of the IEA-15MW RWT + VolturnUS platform at 50 seconds in the red plot.

I migrated the r-test branch over.  So it should be good now.


Fix version parameter for livy in docs

Fix for https://github.com/rstudio/sparklyr/issues/2016

Thanks for the review @lgongmsft!


[BUG] TypeError: Cannot read property 'split' of null

Bug Description
The bot crashes while calling the nowPlaying method when it's playing a stream.
Reproduction Steps
Steps to reproduce the behavior:

Play "lofi chill study".
Then call the nowPlaying method.

Expected Result
It should return the current information about the video that's playing.
Attachments

Versioning:

OS: Microsoft Version 10.0.19042.804
NPM Version 6.14.11
Module Version 6.4.1

This is a Live-Stream related problem.
Over here it shows that the duration of the "song" is null, since a Live-Stream doesn't have an "ending time".

I figured out what's causing the issue. It's most likely happening because some of the fields are null.
[0]   name: 'lofi hip hop radio - beats to relax/study to',
[0]   duration: null,
[0]   author: 'ChilledCow',
[0]   url: 'https://www.youtube.com/watch?v=5qap5aO4i9A',
[0]   thumbnail: 'https://i.ytimg.com/vi/5qap5aO4i9A/hq720_live.jpg?sqp=-oaymwEXCNAFEJQDSFryq4qpAwkIARUAAIhCGAE=&rs=AOn4CLD0pBKpXiNqTSHm5c4PWbtYvEhs3A',
[0]   queue: Queue {
[0]     _events: [Object: null prototype] {},
[0]     _eventsCount: 0,
[0]     _maxListeners: undefined,
[0]     guildID: '760697375949324308',
[0]     dispatcher: null,
[0]     connection: VoiceConnection {
[0]       _events: [Object: null prototype],
[0]       _eventsCount: 4,
[0]       _maxListeners: undefined,
[0]       voiceManager: [ClientVoiceManager],
[0]       channel: [VoiceChannel],
[0]       status: 0,
[0]       speaking: [Speaking],
[0]       authentication: [Object],
[0]       player: [AudioPlayer],
[0]       ssrcMap: Map(0) {},
[0]       _speaking: Map(0) {},
[0]       sockets: [Object],
[0]       receiver: [VoiceReceiver],
[0]       connectTimeout: Timeout {
[0]         _idleTimeout: -1,
[0]         _idlePrev: null,
[0]         _idleNext: null,
[0]         _idleStart: 16316,
[0]         _onTimeout: null,
[0]         _timerArgs: undefined,
[0]         _repeat: null,
[0]         _destroyed: true,
[0]         [Symbol(refed)]: true,
[0]         [Symbol(kHasPrimitive)]: false,
[0]         [Symbol(asyncId)]: 2576,
[0]         [Symbol(triggerId)]: 0
[0]       },
[0]       [Symbol(kCapture)]: false
[0]     },
[0]     songs: [ [Circular *1] ],
[0]     stopped: false,
[0]     skipped: false,
[0]     volume: 100,
[0]     playing: true,
[0]     repeatMode: false,
[0]     repeatQueue: false,
[0]     [Symbol(kCapture)]: false
[0]   },
[0]   requestedBy: 'Zyleaf#1018',
[0]   seekTime: 0
[0] }

This is a Live-Stream related problem.
Over here it shows that the duration of the "song" is null, since a Live-Stream doesn't have an "ending time".

(I also get the same error when running nowPlaying)
#29

I didn't see that you mention some fields being null. Yeah, I think that's what's causing it.

I am gonna close the issue. Thanks for letting me know (:


our server does not load spec file

Hello!
I am trying to view our redoc spec with the index.html hosted on our site but it is not rendering.  seems like it can't pull in the swagger.yml file.  any ideas?

Draft Orders API Specification

<!--
ReDoc uses font options from the parent element
So override default browser styles
-->
<style>
  body {
    margin: 0;
    padding: 0;
  }
</style>

<!DOCTYPE html>
<html>
  <head>
    <title>Draft Orders API Specification</title>
    <!-- needed for adaptive design -->
    <meta name="viewport" content="width=device-width, initial-scale=1">

    <!--
    ReDoc uses font options from the parent element
    So override default browser styles
    -->
    <style>
      body {
        margin: 0;
        padding: 0;
      }
    </style>
  </head>
  <body>
    <redoc spec-url="https://andrewjtech123.github.io/imagehost/swagger.yml">
    </redoc>
    <script src="//rebilly.github.io/ReDoc/releases/latest/redoc.min.js"> </script>
  </body>
</html>

@andrewjtech123  What is printed to browser console?

Hi.  I think we fixed the issue.  Our local jekyll server runs without https.  When I run it locally I have to append https to the url, in order to view the Redoc output correctly.
One other related question - is it possible to tun off the swagger warnings from outputting to redoc?

Yes - use suppress-warnings: docs
Example:
<redoc spec-url="..." suppress-warnings></redoc>

@andrewjtech123 can this issue be closed?

@andrewjtech123 closing this issue for now but feel free to reopen in case it is not solved


Question about the training time?

Hi,
Thanks for the awesome work! From the paper, all models are trained with 8 80GB A100 GPUs, which takes around 16 hours. But why did the appendix on huggingface mention that training takes approximately 200,000 A100 80GB hours (https://huggingface.co/stabilityai/stable-video-diffusion-img2vid-xt)?
Thanks!

hi, did you know how to trian svd-xt?


Go binding cleanup and example app

Here is a list on what I cleaned up:

Simplify the usability and utilize the full JSON-c configuration.
Remove some files that are combined into others and rework a few areas to make it easier to understand.
Rework RxBurst/TxBurst/… to take a lportID instead of passing a method pointer.
Cleaned up a number of allocations around LPort as this data is static after startup.
Remove all of the underscore variables and convert them to Go variable names.
Add the start of documentation to all of the files. Needs more work.
Added a few more helper routines to parse a slice to packets or objects.
Update the example/fwd application to utilize the JSON-c instead of JSON
Remove the -port option and use the JSON-c thread section to identify the lports attached to a given thread
Add support for using the JSON Threads section for starting threads an assigning lports to those threads.
Use the tview Go library to display the stats in a easier to read format.
Update the test routines to poll more than just one lport.
Updated the cne/run_test code and script to test more functions.
Updated the example/run_fwd script remove the -port option with other cleanups.
More minor changes for refactoring and cleanup.

Signed-off-by: Keith Wiles<EMAIL_ADDRESS>

The super linter is executing on the XXX_test.go files and it should not unless we can figure out how to make it work. I do not think is a big problem, so I would like to figure out how to exclude *_test.go files.
The next problem is the Super-Linter does not appear to understand import "C" statements and that causes a number of failures.

This PR needs #153 to be complete, but I could not find how to make this PR dependent on PR 153.

The super linter is executing on the XXX_test.go files and it should not unless we can figure out how to make it work. I do not think is a big problem, so I would like to figure out how to exclude *_test.go files.
The next problem is the Super-Linter does not appear to understand import "C" statements and that causes a number of failures.

setting VALIDATE_GO: false https://github.com/CloudNativeDataPlane/cndp/blob/main/.github/workflows/super-linter.yml#L33 would prevent Go files from being linted
These issues seem to be related to the failures shown by the Go linter
https://github.com/golangci/golangci-lint/issues/1176 related to the
could not import C (cgo preprocessing failed) (typecheck)
import "C"

https://github.com/github/super-linter/issues/1599 - undeclared name: System (typecheck)
related to the the undeclared name failure

Are we all done reviewing this one?
@maryamtahhan @jeffreybshaw @sushmasi

If @maryamtahhan approves, let's merge this.


pion can not talk to iOS native SDK with h264 support

Your environment.

Version: Release or SHA

v2.2.2

Browser: include version

iOS latest native sdk from cocopod.

Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context

There are at least two things to fix:
1, iOS SDK can not handle h264 profile-level 42001f
2，some other sdp mismatches
What did you do?

make an iOS SDK talks to pion and only use h264 encoder/decoder
What did you expect?
What happened?
the ice is connected and iOS sdk can not decode the data.

dig a bit, it has two issues:
1,  profile-level does not match
2, payload type does not match


roblox

**Is your feature request related to a problem? Please describe.*can you plz add roblox
*Describe the solution you'd like
I think it would be cool to have roblox
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

No sorry.

why?

maybe Netflix

I think the websites belong to suggestions doesn't allow IFrame. That is why we can't insert them to win11.blueedge.me. sorry


Adding a check for existing autotune folder. If it does not exist, warn user that microbolus-related features will be disabled.

Per https://github.com/openaps/oref0/issues/468, this is a proposed solution to check for the presence of autotune directory folder, to further the strong recommendation that people only use oref1 features with well-tuned basals. This folder is created when someone’s enabled autotune to run nightly; or by running autotune manually.
To test, grab the autotune-check branch.
You may want to uncomment line 110 (("Printing this so you know it's getting to the check for autotune.") to help you spot the output in the logs.
If you have autotune enabled already and running (and an existing directory), you should see the “Autotune exists! Hoorah!” message in your logs, along with a note about microbolus being set to true.
To test this works properly, you then want to change the name of your autotune directory (ie. mv autotune changedname) and watch the logs. You should then see microbolus as true; followed by “Warning: Autotune has not been run. All microboluses will be disabled until you manually run autotune or add it to run nightly in your loop.", then microbolus = false.
(Then go back in and re-change your name of autotune, via `mv changedname autotune).

@danalewis I don't use autotune, I don't want to use it, have run autotune previously the code works great for me. There are Imo enough safety's in place.

@danalewis Traveling too late and cranky.  Never mind ^^, I read it to quick.

If you have run in the past, you'll have the folder. It does not require
running as part of the loop.
(And if you're experienced, you could look at the code and figure out how
to add a folder regardless or work around this code.)
This is meant to emphasize the strong recommendation to have well tuned
settings, and given what I've seen in those (on average) who want to try
oref1, I think it is absolutely required before this code goes to master to
ensure someone knows what they're doing.
On Tue, Jun 6, 2017 at 8:06 PM David<EMAIL_ADDRESS>wrote:

@danalewis https://github.com/danalewis I don't use autotune, I don't
want to use it, have run autotune previously the code works great for me.
There are Imo enough safety's in place.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openaps/oref0/pull/491#issuecomment-306673411, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHH0hW7GoSCFkWjKp-CI8WPsm6hW6bBnks5sBhOZgaJpZM4NyFdu
.

--
Dana Lewis | http://OpenAPS.org | http://DIYPS.org http://diyps.org |
@DanaMLewis http://www.twitter.com/danamlewis |
http://www.linkedin.com/in/danalewis
"Doing something for someone else is more important than anything you would
do for yourself."

I have to agree with Dana on this one. We've seen a few too many people turn on oref1 and find that what they've got as settings just don't work properly with oref1 because they are miles out.

I also just added a potential fix for the radio reboots during setup.

I'm setting up to test this now...will report back

Testing now with an autotune dir, still no microbolus flag, preferences set to true.  Still appropriately not letting SMBs happen

Autotune directory exists, microbolus flag is used, preferences have SMBs set to false...passes check correctly.

with the autotune directory moved, settings all the same as above

So, it all works...the only part that I see as remaining confusion is that people will see SMBs in preferences, (incorrectly) think that setting them to true alone will turn the SMBs on.  How do we make it clear that the enable microbolus would also need to be added  before those preferences are even "working"?  I'd propose adding a note to the bottom of the preferences file perhaps.  Something to the effect of "the UAM and SMB preferences will not be actively used until you properly enable microbolus as part of a loop set-up"

The json format doesn't really support comments, so we can't really add it there.  Whatever notes we want to add will need to go in the oref1 documentation.  I think @danamlewis might have done some of that already.

and for the radio errors...it does seem to keep the messages from appearing, but full disclosure...it seemed like I had more errors and reboots with this set of loop installations than i typically have without the radio error fix


Python bindings

To provide a lower installation barrier, more N5-specific python access to N5 than the excellent z5py, it would be nice to have python bindings via rust-n5 than supports:

[ ] dataset creation
[ ] attribute access
[ ] numpy array read/write

This would be implemented in a separate, dependent python binding crate (possibly in this repo with a cargo workspace), but is tracked here.
Two main python binding libraries exist for rust (comparison):

PyO3
rust-cypython

On first examination I tend to prefer PyO3 (see this rather nice example). The rust numpy binding library currently uses rust-cpython, but plans to migrate (and has an in-progress PR) to PyO3 once it supports stable rust. Will revisit this issue once that has happened.
cc @clbarnes

Do you envision a numpy-like interface to datasets or would you be more inclined towards going a separate way, like the reference implmentation of zarr? Catching enough slicing and broadcasting edge cases to be usefully numpy-compatible is awkward (although in some cases, already implemented in z5).

rust-numpy has migrated to PyO3; their release is blocked on the next release (0.3) of PyO3, but that's nearing. So that blocker has been removed.

This is fulfilled by https://github.com/pattonw/rust-pyn5


feat(behavior_path_planner, route_handler): make drivable area coordinate fixed to the map coordinate and make its size dynamic

Signed-off-by: Takayuki Murooka<EMAIL_ADDRESS>Related Issue(required)
https://github.com/autowarefoundation/autoware.universe/issues/359
Description(required)

make a drivable area coordinate fixed to the map coordinate (so that drivable area will not oscillate)
make a drivable area size dynamic (fixed drivable area size in a fixed coordinate cannot see enough area for the ego to follow in a few seconds)

Algorighm to calculate dynamic drivable area size

capture 50m forward and 5m backward path from behavior_path (50m forward and 5m backward is required in obstacle_avoidance_planner)
calculate min/max x and y in the map coordinate of left and right boundaries of 55m (+ with margin) path.
add margin to min/max x and y, and this is dynamic drivable area.

TODO(murooka) If the length of the last lanelet (lanelet of just 50m forward point) is too long, drivable area tries to capture the whole last lanelet, so drivable area may be too large.
Without this PR

With this PR

Review Procedure(required)

Related PR(optional)

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Read commit-guidelines
[ ] Assign PR to reviewer

If you are adding new package following items are required:

[ ] Documentation with description of the package is available
[ ] A sample launch file and parameter file are available if the package contains executable nodes

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the [guidelines][clang-tidy-guidelines].
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

I'm not sure why semantic pull request failed

Error: Pull request has only one commit and it's not semantic; this may lead to a non-semantic commit in the base branch (see https://github.community/t/how-to-change-the-default-squash-merge-commit-message/1155). Amend the commit message to match the pull request title, or add another commit.

@kenji-miyake Thanks for the comment. Of course I've read it, but I didn't understand well. Maybe if I add another commit, it will pass? :thinking:

Maybe if I add another commit, it will pass? thinking

Yes. It's like a mystery of GitHub.

@yukkysaito pls check this PR.

@takayuki5168 Please change from draft to PR if reviewable

@takayuki5168 Can you please update the README, because the parameters have been added?


Keyboard language switch results in wrong keybindings

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:32:36.023Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

theme-monokai-pro-vscode
mon
1.1.2

cpptools
ms-
0.14.4

vscode-icons
rob
7.19.0

(5 theme extensions excluded)

Steps to Reproduce:

A command is bound to the "ctrl + ~" for example
I switch the keyboard language to Hungarian for example
The key bining becomes "ctrl + ö"
On most of the HUN keyboards ö is not in the place of ~. Certain notebook keyboards works this way, but it really depends on the 104/105 key variants of a keyboard layout, and also it works quite differently if you use the so called 101-key HUN layout.

Suggestion:
Make an option for keybindings on different keyboard layouts, or make an option to exclude this behavior. (I was not able to find such a setting in User Settings.)

Reproduces without extensions: Yes

This is as designed. On Windows, our default keybindings are bound to key codes.
When switching keyboard layouts, Windows changes two logical mappings: first it changes the mapping scan code => key code, and second it changes what each key code + modifier keys produce.
If you wish to have a keyboard layout agnostic binding (scan code binding), you can do so by yourself:
This will bind to the scan code of Backquote which is always the physical key to the left of 1, irrespective of keyboard layout.
    {
        "key": "ctrl+[Backquote]",
        "command": "workbench.action.terminal.toggleTerminal"
    },


use .copy method to create new terms

Description
So we use PauliTerm api like intended rather than accessing the private ._ops property.
Please verify that you have completed the following steps

[x] I have self-reviewed my code.
[ ] I have included test cases validating introduced feature/fix.
[ ] I have updated documentation.

Codecov Report

Merging #51 (02f2ca3) into main (d863662) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

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

@@            Coverage Diff             @@
##             main      #51      +/-   ##
==========================================
- Coverage   94.16%   94.16%   -0.01%
==========================================
  Files          46       46
  Lines        3017     3016       -1
==========================================
- Hits         2841     2840       -1
  Misses        176      176

Impacted Files
Coverage Δ

...tum/operators/_openfermion_utils/operator_utils.py
100.00% <100.00%> (ø)

src/orquestra/quantum/wavefunction.py
96.62% <0.00%> (-0.03%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Contour IngressRoute provider

Hi,
I see that Contour integration was done via HTTPProxy, which is the next version of IngressRoute (++). With the recent announcement of Contour being donated to CNCF and redesign contour-cncf are you willing to accept PRs adding support for Contour IngressRoute?
Thanks

My understanding is that IngressRoute has been deprecated in favour of HTTPProxy.

Hi @stefanprodan , nevertheless the question is if under these circumstances (IngressRoute being deprecated) the maintainers of this product are willing to accept pull requests for a "legacy" dependency?
Thank you for your fast response.
Cheers

No, maintaining a deprecated API in Flagger is not acceptable. My hope is that all ingress controllers will adopt Kubernetes Ingress v2 so we can drop the support for the custom ingress CRDs from Flagger.

Thank you, @stefanprodan


Keep secret_key secret.

On Sat, Feb 21, 2015 at 01:24:44PM -0800, David Rio Deiros wrote:

Keep secret_key secret.

I'd rather have:
import uuid
SECRET_KEY = os.environ.get('SECRET_KEY', uuid.uuid4().hex)
so folks who aren't running a public deploy can skip setting the
environment variable.

+1 for defaulting to some value, but I'd rather have that value not rotate every time I reload settings because it breaks many things.

On Mon, Feb 23, 2015 at 02:57:35AM -0800, Piotr Banaszkiewicz wrote:

… but I'd rather have that value not rotate every time I reload
settings because it breaks many
things.

The broken things don't look very important if you're just firing up a
local instance for testing.  Was there somthing in that list that
seemed more troublesome to you?

Hey @wking,

The broken things don't look very important if you're just firing up a local instance for testing. Was there somthing in that list that seemed more troublesome to you?

yes I think generating SECRET_KEY every time settings are reloaded (and I think it happens every time dev server reloads - and therefore every time I make changes to the code) breaks: messages, sessions and crypto signing - all of these are used for bulk-upload.
I propose another approach:
# in settings.py

SECRET_KEY = '3l$35+@a%g!(^y^98oi%ei+%+yvtl3y0k^_7-fmx2oj09-ac5@'
if not DEBUG:
    SECRET_KEY = os.environ.get('SECRET_KEY', None)

This way:

every developer uses the same SECRET_KEY and that key never changes
for production-ready deployment the application will refuse to start (https://docs.djangoproject.com/en/1.7/ref/settings/#std:setting-SECRET_KEY)

What do you think?

On Mon, Feb 23, 2015 at 10:37:58AM -0800, Piotr Banaszkiewicz wrote:

SECRET_KEY = '3l$35+@a%g!(^y^98oi%ei+%+yvtl3y0k^_7-fmx2oj09-ac5@'
if not DEBUG:
SECRET_KEY = os.environ.get('SECRET_KEY', None)

Ah, that looks good to me :).

Great! @drio can you update this PR, please?

Done.

On Mon, Feb 23, 2015 at 01:54:52PM -0800, David Rio Deiros wrote:

Done.

It looks like we can drop the sys import now that we're not printing
to stderr.

Thanks @wking.

When we fix NameError: name 'DEBUG' is not defined (https://github.com/swcarpentry/amy/pull/200#discussion_r25237149) we're ready to merge.

How do you feel about this other alternative? It does not require changing the file
when deploying.

On Tue, Feb 24, 2015 at 06:27:41AM -0800, David Rio Deiros wrote:

How do you feel about this other alternative? It does not require
changing the file when deploying.

I don't want to hardcode deployment information in this repository.
How about:
import json
DEBUG = json.loads(os.environ.get('DEBUG', 'true'))
then folks who are deploying amy (wherever they happen to do that) can
use:
DEBUG=true SECRET_KEY="..." ./manage.py runserver ...
Oh, and if a SECRET_KEY environment variable is set (regardless of
DEBUG), we should respect it.  I think DEBUG should just toggle the
default:
if DEBUG:
SECRET_KEY = '3l$35+@a%g!(^y^98oi%ei+%+yvtl3y0k^_7-fmx2oj09-ac5@'
else:
SECRET_KEY = None
SECRET_KEY = os.environ.get('SECRET_KEY', SECRET_KEY)

I implemented @wking's latest suggestion.
We have been using the same key for production and development. I want to re-deploy (restart
the server really) with the new production key but I am afraid that will break some things. What do you
suggest?

On Wed, Feb 25, 2015 at 10:48:08AM -0800, David Rio Deiros wrote:

We have been using the same key for production and development. I
want to re-deploy (restart the server really) with the new
production key but I am afraid that will break some things. What do
you suggest?

I don't think running a production server with a compromised provate
key is salvageable.  I'd restart with DEBUG=false and a new
SECRET_KEY, and just accept the resulting breakage (which should be
small if you time the restart to avoid any running sessions).

On Wed, Feb 25, 2015 at 10:48:08AM -0800, David Rio Deiros wrote:

I implemented @wking's latest suggestion.

Grr, and it looks like I suggested ‘DEBUG=true’ for production, it
should definitely be ‘DEBUG=false’.

It looks okay for me. @wking take one final look and merge if it's OK.

Ok. I think the PR looks good now. As soon as you merge this I will pull from
the vps and rerun using the production secret.
@gvwilson I have updated $HOME/secret_key.sh with the new production secret key. I will also update our passwords file in the sysadmin repo.

On Wed, Feb 25, 2015 at 11:37:14AM -0800, Piotr Banaszkiewicz wrote:

It looks okay for me. @wking take one final look and merge if it's OK.

Sorry for the delay.  I responded via email yesterday, but GitHub
occasionally delays comments submitted by email :/.  Here's what I
said:
Looks good to me :).  Maybe --squash the merge?  I doubt the details
of our asymptotic approach to the current solution will be
particularly useful for future developers.
And I don't think I should be merging this.  I'm just a contributor
here, not the maintainer, so I'm just giving advice, not making the
call about what lands when.  I'm not sure who the maintainers are 1,
but I'd guess it's currently @gvwilson.  I'm happy to do the squash
merge if he deputizes me to perform it.

Merged.


Update AML Private DNS Zone Name (Gov)

Description
The Azure Machine Learning private DNS zone name for the US Gov cloud is incorrectly listed as "privatelink.api.azureml.us". This DNS zone name results in an AML workspace that cannot be accessed from within a VNET. The correct zone name that worked in our testing is "privatelink.api.ml.azure.us".
To Reproduce
To reproduce the error, deploy an AML workspace behind a VNET in gov cloud using this quickstart. The private dns zone names under network.tf need to be updated according to the table in this documentation.  The result is an AML workspace that cannot be accessed via the provisioned jumpbox.
Changing the the private dns zone name to "privatelink.api.ml.azure.us" fixed the networking error and resulted in a correctly provisioned AML workspace behind a VNET in the US Gov cloud.
Notes

There are inconsistencies with the "azureml.xx" and "ml.azure.xx" patterns throughout this documentation. From our testing a deployment to the commercial cloud using "privatelink.api.azureml.ms" is correct. The China cloud is listed as "privatelink.api.ml.azure.cn" - we do not have the ability to verify if this is correct, so this should be looked at too.
The public DNS zone forwarders use both "azureml.xx" and "ml.azure.xx" in various dns names. As we did not use any DNS zone forwarders, we were not able to verify if these were all correct, but someone should check to ensure these are all correct.

cc: @jplane @vladmsft @NayanGuptaMicrosoft @erikschlegel

@asudbring

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


swiftshader: 2020-06-17 -> 2020-11-06

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I get the following error when compiling.
_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ -DCMAKE_INSTALL_PREFIX=/nix/store/nvh8qksd7s0qydhjdgzgd7ns002nqm7g-swiftshader-2020-11-06
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- The ASM compiler identification is GNU
-- Found assembler: /nix/store/lfl1davviy5mai3g80mpy2gkb97rh9j5-gcc-wrapper-9.3.0/bin/gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: /nix/store/lfl1davviy5mai3g80mpy2gkb97rh9j5-gcc-wrapper-9.3.0/bin/gcc
-- Check for working C compiler: /nix/store/lfl1davviy5mai3g80mpy2gkb97rh9j5-gcc-wrapper-9.3.0/bin/gcc - broken
CMake Error at /nix/store/4fiibyqiq5y0dc1ma3far935r2sn58ak-cmake-3.18.2/share/cmake-3.18/Modules/CMakeTestCCompiler.cmake:66 (message):
  The C compiler

    "/nix/store/lfl1davviy5mai3g80mpy2gkb97rh9j5-gcc-wrapper-9.3.0/bin/gcc"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /build/SwiftShader-4ed9d34/build/CMakeFiles/CMakeTmp

    Run Build Command(s):/nix/store/kql5zqxkk5xmnmpfcyfzydbvw444i9i8-gnumake-4.3/bin/make cmTC_c89fc/fast && /nix/store/kql5zqxkk5xmnmpfcyfzydbvw444i9i8-gnumake-4.3/bin/make  -f CMakeFiles/cmTC_c89fc.dir/build.make CMakeFiles/cmTC_c89fc.dir/build
    make[1]: Entering directory '/build/SwiftShader-4ed9d34/build/CMakeFiles/CMakeTmp'
    make[1]: /bin/sh: No such file or directory
    make[1]: *** [CMakeFiles/cmTC_c89fc.dir/build.make:84: CMakeFiles/cmTC_c89fc.dir/testCCompiler.c.o] Error 127
    make[1]: Leaving directory '/build/SwiftShader-4ed9d34/build/CMakeFiles/CMakeTmp'
    make: *** [Makefile:140: cmTC_c89fc/fast] Error 2

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:19 (project)

-- Configuring incomplete, errors occurred!
See also "/build/SwiftShader-4ed9d34/build/CMakeFiles/CMakeOutput.log".
See also "/build/SwiftShader-4ed9d34/build/CMakeFiles/CMakeError.log".

Perhaps you have an overlay or some config option interfering? Both myself and @ofborg are able to build it.

Is is possible to get this merged, please?

ping?

Result of nixpkgs-review pr 103123 run on x86_64-linux 1

1 package built:

swiftshader

Thanks!


[Enhancement]: Improving the UI and adding Home icon in "Brain Burst Game"

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
Game enhancement

I will enhance the UI of the game as enhancing the game's visual appeal is essential for creating a compelling, enjoyable, and professional experience that attracts and retains players.
I will add a Home Icon, adding it will improve the game's usability, making it more user-friendly and accessible, which can lead to higher user satisfaction and retention.

Describe the solution you'd like
Solution steps

Visual Appeal: Adding gradients, shadows, and rounded corners to create a modern look.
Interactivity: Implementing hover effects and transitions for a more engaging user experience.
Readability and Usability: Improving text visibility and providing clear visual feedback.
Home Icon: Adding Home Icon at the top of the game, it will help players to navigate to the Home Page easily.

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @ShristiiSharma , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#3807

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

Hey @ShristiiSharma !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign


Named within hidden block has no effect

In the following, named has no effect:
<!--~

<r named="Configuring MySQL" />

``` bash
cat $SQL | mysql
```

-->

It's called spinner. Silly me.


Suggestion : Can we make object selection searchable

Hi,
The object selection while running query is usually a big one. It has many objects listed and gets cumbersome. So will it be accepted If I make object selection searchable. ?
I would be more than happy to send PR with this enhancement.
Thanks

Most browsers support typing in the first few characters of the object name, which I have found makes it manageable, but if you want to make it searchable, feel free. You'll probably need to overhaul the whole printObjectSelection function.

Thanks ryan, one quick question , why do I keep getting "Could not connect to host" while running on https://localhost
Thanks

try http (not https) and set the port number.

I mean to to say this.

Same thing applies. Use http and the port number for localhost


--write-verification-metadata when adding new 40-char key, remove corresponding 16-char key

Expected Behavior
When running ./gradlew --write-verification-metadata to update the set of trusted keys, if Gradle adds the 40-character form of a key, it would be nice if Gradle would also delete the corresponding 16-character form of that key
Current Behavior
For example, I currently have a verification-metadata.xml that looks like this:
$ grep -i F800DD0933ECF7F7 *
verification-keyring.keys:pub    F800DD0933ECF7F7
verification-metadata.xml:         <trusted-key id="00089ee8c3afa95a854d0f1df800dd0933ecf7f7" group="com.google.guava" name="guava"/>
verification-metadata.xml:         <trusted-key id="f800dd0933ecf7f7" group="com.google.guava"/>

(after manually removing the 'version="r06"', see https://github.com/gradle/gradle/issues/20192 )
the longer form of this key was added by ./gradlew --write-verification-metadata into verification-metadata.xml. It would be nice if Gradle could automatically remove the shorter 16-character form from verification-metadata.xml
Context
This was confusing for a little while. I thought that Gradle was adding unnecessary keys into verification-metadata.xml, which appears to be somewhat true, but a better description seems to be that Gradle is adding the longer forms of keys into verification-metadata.xml without also removing the shorter forms

In AndroidX we migrated our 16-char keys to 40-char keys so we're hopeful that we won't need this anymore. It looks like nobody else has asked for it either so I'll close it for now. Thanks


use ModelManager to encapsulate both food and sale objects

Encapsulate food and sale into model manger. The command execute() now accept model manger instead
Add saleStorage, but storage manager does not support sale storage yet

2 - Attempt to fix in #155


TypeError: TypeError: undefined is not an object (evaluating 'e.aggregated.timestamp')

https://sentry.io/zulip/zulip-mobile/issues/503311996/
TypeError: TypeError: undefined is not an object (evaluating 'e.aggregated.timestamp')

This error is located at:
    in t
    in Connect(t)
    in RCTView
    in RCTView
    in t
    in Connect(t)
    in r
    in Connect(r)
    in RCTView
    in t
    in Connect(t)
    in RCTView
    in RCTView
    in t
    in t
    in t
    in t
    in RCTView
    in n
    in t
    in n
    in RCTView
    in RCTView
    in t
    in RCTView
    in e
    in r
    in Unknown
    in n
    in n
    in t
    in Connect(t)
    in Unknown
    in t
    in Connect(t)
    in IntlProvider
    in t
    in Connect(t)
    in t
    in Connect(t)
    in RCTView
    in n
    in Connect(n)
    in n
    in t
    in t
    in Unknown
    in RCTView
    in RCTView
    in t
    at src/utils/date.ActivityText(date.js:30)
    const lastTimeActive = new Date(presence.aggregated.timestamp * 1000);
    at src/title/ActivityText.ReactNativeRenderer$3(ActivityText.js:38)
    }))(ActivityText);
...
(12 additional frame(s) were not displayed)

Closing as fixed.


Fix accessibility propagation

This patch makes a number of changes to change flags propagation, which should at least get the example working again.
This implements the two-flags approach to REQUEST_ACCESSIBILITY and DESCENDANT_REQUESTED_ACESSIBILITY. The framework converts the former flag into the latter as it propagates up the tree, both in merge_up and in ChangeFlags propagation.
ChangeFlags propagation only propagates ChangeFlags, it does not move flags from the pod into the rebuild flow. It does have descendant logic as mentioned above.
Layout now triggers an accessibility request. This reduces the burden on custom widgets to explicity request accessibility, and also will be more precise if and when layout becomes more incremental, we'll want to request accessibility only when the layout has actually changed.

Hopefully the commit comment in the followup commit (c4a3732c429c1e8e5dbafe46e66df2a1a71fab85) explains what my concern is here. The next PR I'd like to do (or would be fine if somebody else does if the direction is clear) is to add a new ChangeFlags::STRUCTURE which is set whenever parent/child relationships change for any reason: AnyView changes type, Option toggles between None and Some, vector changes length. Now that I think about it, I think there should be a corresponding PodFlags::STRUCTURE_CHANGED (with the same bit set), in which case my warning comment should be removed.
I haven't worked out the exact propagation rules; I think they may be a bit subtle. They probably need two flags (one for "this view/widget", one for descendants) like accessibility. On the widget side, when containers receive this flag, they diff their old list of children against the new one, send WidgetAdded lifecycle events to the new ones (I think this happens in update but this is probably not the only valid choice), and handle deletion as well. I am leaning toward having the framework track the parent/child tree, which would also replace the Bloom filters.
I'm willing to do that as a PR, but am also open to discussion; it's probably most important right now that we get some kind of understanding and agreement about where all this is going.

The next PR I'd like to do (or would be fine if somebody else does if the direction is clear) is to add a new ChangeFlags::STRUCTURE which is set whenever parent/child relationships change for any reason: AnyView changes type, Option toggles between None and Some, vector changes length.

What would be the difference between STRUCTURE_CHANGED and TREE_CHANGED?

Now that I think about it, I think there should be a corresponding PodFlags::STRUCTURE_CHANGED (with the same bit set), in which case my warning comment should be removed.

I guess that ChangeFlags will stay a superset of PodFlags. But that's just a feeling.

ChangeFlags propagation only propagates ChangeFlags, it does not move flags from the pod into the rebuild flow. It does have descendant logic as mentioned above.

In druid we relied on merge_up being idempotent. I thought that this would also apply here?

Thanks! Somehow I missed the existence of TREE, it is the same idea. We can keep the name. I'm looking over the propagation and see some problems, but given my history of being confused by this stuff probably the best thing is for me to open an issue and discussion can happen there.


Remote client SSL verification error

Describe the bug
In order to connect to the .NET Framework app using the Remote Client feature, we use an IP:PORT combination which means the SSL handshake fails because the request Host header is invalid.
Is it possible to either disable SSL check entirely or add a custom header to the Remote Client requests?
Exceptions (if any)
      System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
       ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch

Further technical details
Please include the following if applicable:
ASP.NET Framework Application:

Technologies and versions used (i.e. MVC/WebForms/etc): MVC 5
.NET Framework Version: 4.7.2
IIS Version: 10.0.22621
Windows Version: 10

The BackchannelClient can be customized to either pass the Host header to the .NET Framework side or disable SSL handshake entirely (not recommended). Here is an example:
            var proxyUri = new Uri(Configuration["ProxyTo:Uri"]);

            services.AddSystemWebAdapters()
                .AddRemoteAppClient((options) =>
                {
                    options.BackchannelClient = new HttpClient(new HttpClientHandler { UseCookies = false, AllowAutoRedirect = false });
                    options.BackchannelClient.BaseAddress = proxyUri;
                    options.BackchannelClient.DefaultRequestHeaders.Add("Host", Configuration["ProxyTo:Hostname"]);
                    options.BackchannelClient.DefaultRequestHeaders.Add(options.ApiKeyHeader, apiKey);

                    options.RemoteAppUrl = proxyUri;
                    options.ApiKey = apiKey;
                })
                .AddAuthenticationClient(true);


Add IP_RECVERR (unix/linux_like/mod.rs)

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

@bors: r+

:pushpin: Commit 1937b4511856f9c6cc328656ec65ecacd2ea90dc has been approved by gnzlbg

:hourglass: Testing commit 1937b4511856f9c6cc328656ec65ecacd2ea90dc with merge 22c0f59fa814176ffcb80b38ce3580d6c19658aa...

:broken_heart: Test failed - checks-cirrus-freebsd-12

I got no ideas how to fix this error, maybe someone knows?

@bors: r+

:pushpin: Commit 1937b4511856f9c6cc328656ec65ecacd2ea90dc has been approved by gnzlbg

:hourglass: Testing commit 1937b4511856f9c6cc328656ec65ecacd2ea90dc with merge 0e12753378e08400b38cce869dae7510546511c6...

:sunny: Test successful - checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, status-azure
Approved by: gnzlbg
Pushing 0e12753378e08400b38cce869dae7510546511c6 to master...


:bug: Block payment for sanctioned address

If users are not connected, they can add an NFT or donation to the cart. Once connected, the app does not check their OFAC status
DEFAULT

IF BUTTON DISABLED AND BUTTON HOVERED

Fixed white space
BEFORE

AFTER

@0xPoint this LGTM, thanks for catching and for the quick fix. Tests are failing because the PR is from a fork - will need to look into that.
Merging!


Ratel: allow optinally disabling Ratel. Enabled by default.

Adds new ratel.enabled field in the values.yaml, set to true by default.
By setting it false, both ratel-deployment.yaml and ratel-sac.yaml files get omitted.
Having this flag enables users to launch Dgraph alpha and zero servers but not Ratel.
Tested it locally with both true and false values.

This change is

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Giorgi Lekveishvili seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Just realized there is a issue filed for this feature request: https://github.com/dgraph-io/charts/issues/6
Not sure how I can attach PR to that issue though.

ping

I did sign license, multiple times, but it still shows up unsigned.
Anu suggestions?

@giolekva The email in your commit doesn't match the email of your GitHub user, which is why CLAassistant says "Giorgi Lekveishvili seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account."

This PR is no longer valid as the feature has been added, in the same pattern along with some changes needed to disable ratel related ingress for new ingress feature.


refactor: working docker image

[ ] I have considered whether this PR needs review, and requested a review if necessary.

Fixes issue #
Notes for reviewers
Reviewers can skip X, but should pay attention to Y.

#78  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MartinBernstorff and the rest of your teammates on  Graphite


The "bibxml" button on the doc status page should link to bib.ietf.org

Describe the issue
Currently it links to datatracker.
For example, the bibxml button on https://datatracker.ietf.org/doc/draft-ietf-tsvwg-careful-resume/
goes to https://datatracker.ietf.org/doc/bibxml3/draft-ietf-tsvwg-careful-resume-04.xml
rather than https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-tsvwg-careful-resume-04.xml.
If the bibxml button was clicked on the unversioned datatracker page, would it be better for the link to go to the unversioned bibxml URL? For example:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-careful-resume/ could link to https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-tsvwg-careful-resume.xml, and
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-careful-resume/04/ could link to https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-tsvwg-careful-resume-04.xml
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

For example, the bibxml button on https://datatracker.ietf.org/doc/draft-ietf-tsvwg-careful-resume/ goes to https://datatracker.ietf.org/doc/bibxml3/draft-ietf-tsvwg-careful-resume-04.xml rather than https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-tsvwg-careful-resume-04.xml.

I consider that a feature.
datatracker is the source of truth on these.
Of course, finding out in which way bib.ietf.org has, hmm, processed this truth is interesting in its own right, but if you need the bibxml, please use the source.


Disable parallel tests by default

Run them in parallel only in the dev mode. Looks like that Travis CI is really flaky with a parallel test execution. The build often fails without a reason and this really confuses new contributors. Better
to have a slow and stable build then fast and unreliable.

Yeah let's see if this fixes things.


Create/Edit Form - The delete button is missing the icon

Edit a listing.
Notice that the icon for the delete button is missing.

Create/Edit icons fixed in develop in 095150a6833e4af6b325da7159813e3f77c8c41e

All Browsers
Verified that the Delete icon now appears in the button.


⚠ Bofrost.lu has degraded performance

In 12e7770, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1355 ms

Resolved: Bofrost.lu performance has improved in 089eac6 after 27 minutes.


Iai ols benchmark

This PR adds an iai benchmark for the OLS algorithm that is part of linfa-linear.
It has the following benchmark characteristics:
n = 1_000, 10_000, and 100_000
num_features = 7
values = Non unique (all are f64: 7)
If this is accepted, I will post the results in #228
This is also partly addresses #103

Codecov Report
Base: 39.24% // Head: 39.17% // Decreases project coverage by -0.07% :warning:

Coverage data is based on head (f81f25a) compared to base (5ebe23c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #253      +/-   ##
==========================================
- Coverage   39.24%   39.17%   -0.08%
==========================================
  Files          92       92
  Lines        6085     6096      +11
==========================================
  Hits         2388     2388
- Misses       3697     3708      +11

Impacted Files
Coverage Δ

...rithms/linfa-trees/src/decision_trees/algorithm.rs
35.26% <0.00%> (-1.79%)
:arrow_down:

src/metrics_regression.rs
27.72% <0.00%> (-1.17%)
:arrow_down:

algorithms/linfa-linear/src/glm/mod.rs
52.77% <0.00%> (ø)

src/metrics_classification.rs
39.62% <0.00%> (+0.62%)
:arrow_up:

algorithms/linfa-tsne/src/hyperparams.rs
18.60% <0.00%> (+2.32%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

That's not a problem, though iai might be feature complete at this time it seems to use Valgrind and cachegrind on the backend for the benchmarking. I'm also not sure excluding setup code is more important than the consistency provided by iai.
If you still prefer criterion I can change it to that by next week and report the benchmark results on the other issue.

Iai still has a bunch of open issues and PRs in its repo, so it's definitely not feature-complete. The author is still active so I'm not sure what the exact status of the project is. Setup code is not a big deal in longer benchmarks but could sway the percentage significantly in shorter benchmarks. Another concern with iai is whether it adds all executed cycles for multithread code, since that would make it seem as if everything was run sequentially.
I've asked the Zulip chat about this, so do you mind waiting on this for a week to see if anyone says anything? If I don't get a response then we go with Criterion.

Heard back from the author via email and thought I'd drop it here.
According to Brook:
"""
Yeah, it's more or less dead. I certainly haven't had the energy or time to maintain it properly for a while now. I don't expect that to change in the near future either.
"""

I think we should just go ahead and use Criterion.

Gotcha will do tomorrow.
On Wed, Nov 2, 2022, 11:04 PM Yuhan Lin @.***> wrote:

I think we should just go ahead and use Criterion.
—
Reply to this email directly, view it on GitHub
https://github.com/rust-ml/linfa/pull/253#issuecomment-1301589675, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHYMCT7G4BH4K4HT4K5HLDWGMTU5ANCNFSM6AAAAAARPLUCLU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can you also add a benchmark for the GLM algorithm?

yep. Just to make sure we are on the same page, following the glm.rs example will be sufficient?

Yes GLM example is good


Questions about the source data

can I get Kako20 snow depth and snow depth derived from snow buoys data?
by the code you submit, I want to be familiar with the process of the antarctic snow depth evaluation.

The KaKo20 product is not yet publicly available. However, Snow Buoy data can be downloaded from this link.


Passing variables to my template

Hi, I realise this isn't an issue, but wondered if you could point me in the right direction to adding variables from the flask application to the mandrill template?
mandrill.send_email(
    from_email='test@test',
    to=[{'email': user.email}],
    subject="TestPassword Reset",
    template_name="password-reset",
    template_content= [
        {
             "name": user.first_name,
              "token": token
         }
      ]
)

Sorry, just saw this. I need a little more information to help you if you didn't already find a solution. I assume you are calling mandrill.send_email within the view code of one of your routes so you should have all request variables at your disposal. If you are using Flask-Login the current user can be accessed with current_user.

template_name='mytemplate',
my_template_mc-edit-varname='value for varname',


 The law in Azerbaijan is changing on 1/9/17 so users will have to declare an affirmation rather than get an CNI.
Can this be deployed as late as possible on 31/8/17?
This doesn't affect the logic.

Superseded by #3184


Make url.query conditionally required for HTTP spans

Fixes #112
Aligns the requirement level of url.query with the requirement level of url.path.
It was also the previous behavior when those two attributes were combined in the single field http.target, and appears to have been a bug that slipped into https://github.com/open-telemetry/opentelemetry-specification/pull/3355 when that field was split into url.path and url.query.

mind adding a changelog entry?


Lab adaptation to remove Global Admin dependencies and other fixes.

Changes proposed in this pull request:

LP1-Ex1-M365Defender: Add hint to do guided tours while waiting.
LP2-Ex1-MDE: Moved detection test to Ex02. Added updated GUI steps. Changed messaging for device group.
LP2-Ex2-MDEAttacks: Added detection test from Ex01. Reordered task numbers. Updated GUI additional steps.
LP3-Ex1-MDC: Added exception error case while enable MDC. Added GUI updates wording. Remove GUI step.
LP3-Ex2-MDCThreats: Added a Regulatory  compliance standard. Assigned an owner to a recommendation. Clarify sample alerts process.
LP4-Ex1-KQL: Query reformatting. Replaced Location (PII) queries with AuthenticationDetails.
LP5-Ex1-Sentinel: Change domain name to a Microsoft's example. Minor typos.
LP6-Ex1-Connectors: Removed Azure AD permission dependencies (includes the Azure AD, IdProt and M365 Defender connectors).
LP6-Ex2-Windows: Updated Windows image. Removed MDE task onboarding since we will not be using it in future labs.
LP6-Ex3-Linux: Changed facility to syslog.
LP6-Ex4-TI: Removed from the table.
LP7-Ex1-MSRule: Changed the way we added a Microsoft security rule
LP7-Ex2-Playbook: Added the option to add the Incident trigger playbook too.
LP7-Ex3-Scheduled: Redo of the lab using the AzureActivity instead of Azure AD tables.
LP7-Ex4-UEBA: Remove enablement of UEBA due AzureAD perm requirement. Extend lab on Anomalies.
LP7-Ex6-Attacks: Redo of the lab to use only WIN2 for doing the attacks.
LP7-Ex7-Detections: Redo of the lab using the AzureActivity instead of Azure AD tables.
LP7-Ex8-Incidents: Redo of the lab using the new Incident experience.
LP7-Ex9-ASIM: Redo of the lab by deploying the template instead of creating it from scratch.
LP7-Ex10-Workbooks: Redo of the lab using the AzureActivity instead of Azure AD tables.
LP7-Ex11-Content: Removed the creation of another analytic rule, instead we exported one we already have.
LP8-Ex1-Hunting: Redo of the lab using the SecurityEvent table instead of MDE tables.
LP8-Ex2-Notebooks: Minor wording updates.

Related Issues
Link related Github Issues 🢂 Fixes #150, #151, #152, #154.
Checklist
Mark completed with "x" between brackets, "[x]", or checking the box once the PR is created:

[x] Has related GitHub Issue 💥 Create Issue 📝
[x] Tested it
[x] Read the PR collaboration guide 👓 Collaboration Guide 📝

Testing merge into BIU branch


unused imports

based on a quick look, I see unused imports.  python-keystoneclient and some of the nltk things for example.  Also I don't see stemmer and lemmatizer in use.  Not if they somehow impact POS as a side-effect, but the unused vars is odd to see in python.
Maybe I missed something, but it'd be nice to run this through pep8 or something to make sure unused imports and vars are cleaned up.

Done. removed the unused imports.

Removed in commit 67022be2452db9694e153626fce3469113b99446


New release

Hello.
Can you please release new version of the lib? I'm particularly in need of the b413c08e1170b81f02c10fa5f8a1b4bfbdf56d82 commt.

bump @philippb

I'm also waiting for a new release of the library since beginning of this year. I think this library is dead 😢

Very sorry I didn’t see this. Let us take care of this. We still use it on
production.
On Mon, Sep 2, 2019 at 06:56 Sven Jacobs<EMAIL_ADDRESS>wrote:

I'm also waiting https://github.com/KeepSafe/TapTargetView/issues/333
for a new release of the library since beginning of this year. I think this
library is dead 😢
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KeepSafe/TapTargetView/issues/340?email_source=notifications&email_token=AAC3MNRD4GVVR5IVHZE5A6LQHULQBA5CNFSM4G2ZIPJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5V4PVI#issuecomment-527157205,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC3MNURMA2RSC3AGHV27WDQHULQBANCNFSM4G2ZIPJQ
.

@snpefk I just released version 1.13.0 from master.
Sorry this took so long!
Also I @tomasz-keepsafe, one of our senior Android engineers to be the new maintainer for this project.

It seems version 1.13.0 has not yet been published to JCenter/Maven?


Make an exception for some topics' alias count

This is a possible solution to address topics with 10+ valid aliases e.g. #189 and #190. Any topic defined in MAX_ALIAS_COUNT_EXCEPTIONS won't have the MAX_ALIAS_COUNT restriction imposed.
/cc @MikeMcQuaid

Thanks @leereilly!


feature: Enable client certificate rotation by using tls.Config@GetClientCertificate

Enable client certificate rotation by providing a callback to tls.Config@GetClientCertificate when setting up Temporal connection
Reason for This PR
Solves #522
Description of Changes
Added a callback for GetClientCertificate to enable client certificate rotation when mTLS connection fails, e.g. after it changes in the referenced cert and key files
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

[ ] All commits in this PR are signed (git commit -s).
[ ] The reason for this PR is clearly provided (issue no. or explanation).
[ ] The description of changes is clear and encompassing.
[ ] Any required documentation changes (code and docs) are included in this PR.
[ ] Any user-facing changes are mentioned in CHANGELOG.md.
[ ] All added/changed functionality is tested.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Lukas Benke seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Lukas Benke seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

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

Project coverage is 36.49%. Comparing base (c8e0bcf) to head (4b385c2).
Report is 213 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #523       +/-   ##
===========================================
+ Coverage   22.67%   36.49%   +13.81%
===========================================
  Files           4       13        +9
  Lines         269      959      +690
===========================================
+ Hits           61      350      +289
- Misses        206      539      +333
- Partials        2       70       +68

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

Thanks, @benkelukas 👍 LGTM, will be released next week with RR v2024.1.3.

Thanks @rustatian - that's great news! 🎉


KAFKA-16558 Implemented HeartbeatRequestState toStringBase() and added a test for it

I implemented HeartbeatRequestState.toStringBase(), I also added 2 getter methods for testing purposes. I added a test for the new method, which is passing. Test may/may not be necessary, added just in case.

The test failures are unrelated, FWIW.

@kirktrue thank you for the suggestions, I have implemented and pushed your suggestions. Let me know if everything looks good!

hi @brenden20 - left some comments. lmk what do you think.

@brenden20—can we mark this Ready for review?

Marked ready to review

Merge issues, moved PR to https://github.com/apache/kafka/pull/16373 and closing this one


Update the CPU inference doc

2nd PR for https://github.com/stochasticai/xTuring/issues/264 to integrate Intel-Extension-for-Transformers to support int8 model on the CPU-only devices.
Included a brief introduction to CPU inference.

Hi @StochasticRomanAgeev, as we previously discussed, I've included a brief introduction to CPU inference. Please take the time to review it. Thanks! :)

Hi @yiliu30,
Thanks for documentation pr!
Merged!


320 fix getfreediskspace

Description
Fixed issue #320
Compatibility

OS
Implemented

iOS
❌

Android
✅

Windows
❌

Checklist

[X ] I have tested this on a device/simulator for each compatible OS
[ ] I added the documentation in README.md.
[X ] I mentioned this change in CHANGELOG.md.

Thanks for the tips! All makes sense.

Great, you have now seen a normal workflow for PRs 😄
I'll try it this afternoon and will merge it and release 0.15.2 right after that.
Here's a nice tutorial that could shade some more light on OSS contributions, hope you'll enjoy it:
https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github

0.15.2 is out with your PR 🎉 🎉 🎉


FR: add secondary option to cover, fan cards (or all?)

Is your feature request related to a problem? Please describe.
I'm currently replacing my current UI with mushroom components because I really like what you've been making and sharing, thanks for that!
At this moment, most of my UI is made with custom button cards, because there is an option to add labels.
I've got a cover entity (awning) that doesn't report a state, I've added a door/window sensor inside the awning to know if it's open or closed.
I've also got a fan entity (air purifier) where I not only show the state, but also the air quality.

(Zonnescherm = Awning, Gesloten = closed, coming from the door/window sensor)
(uit = off, Kwaliteit: Goed = Quality: Good)
Describe the solution you'd like
After playing with your template cards, I started to realize that the secondary option there is actually what I would love to see in more of the cards. That would allow me to use a template to get what I would like.
In my case, fan and cover would be great, but I can assume it's also interesting in other cards.
Describe alternatives you've considered
I've not considered any alternatives yet, only by omitting the state for the awning and the air quality of the air purifier:

Additional context
None for now, but thank you so much for making and sharing this!

I've got a cover entity (awning) that doesn't report a state, I've added a door/window sensor inside the awning to know if it's open or closed.

This could be fixed by using a template cover, Google it.

I've not considered any alternatives yet, only by omitting the state for the awning and the air quality of the air purifier:

A hacky workaround is using ::after with card-mod, eg:
type: custom:mushroom-light-card
name: Bedroom
entity: light.bedroom_lights
icon: mdi:light-recessed
hold_action:
  action: navigate
  navigation_path: /lovelace-rooms/upstairs
fill_container: true
layout: vertical
style:
  mushroom-state-info$: |
    .secondary::after {
      content: " - {{ states("sensor.upstairs_temperature") }} °F";
    }

However I do agree having a custom secondary option in all cards would be useful.

style:
  mushroom-state-info$: |
    .secondary::after {
      content: " - {{ states("sensor.upstairs_temperature") }} °F";
    }

It's 'hacky' but it works beautifully! Thanks!