Add react-hooks demo to examples

This PR adds the demo defi app associated with my blog article on subspace.

One issue is that I left the demo running for quite some time, and there were eventually 7 results being displayed:

@emizzle Thanks for the detailed review of the blog entry.  I'll make the edits and update the post.  That said...I didn't actually mean to include it in the example repo I pushed here.  Any thoughts on whether it makes sense to just make this post the readme for this folder?
Also,I saw the issue you pointed out where it's displaying more than the 5 latest items.  I"m guessing there's something wrong with my state update logic and will take a look.

@emizzle I found and fixed the bug in the table logic so it should now only show the last 5 trades.  React was complaining about duplicate keys in the datatable.  As it turns out,  I had the primary key on the Datatable component incorrectly set to block instead of trade so it was creating duplicate keys for the rows of the table when two trades occurred in the same block.  I've let it run for a little bit and not seen any occurrences of more than 5 rows at this point.

The package-lock/yarn-lock seems to be missing

Awesome job! :)  I left some minor suggestions / fixes,  but overall, it's a very good example of subspace usage! good work! :+1:

The package-lock/yarn-lock seems to be missing

Do you want me to include this?   I guess I thought best practice was to leave this out and let the user's preferred package manager take care of the lock file (I use yarn in general).

Do you want me to include this? I guess I thought best practice was to leave this out and let the user's preferred package manager take care of the lock file (I use yarn in general).

Yes, please include it, that will make sure that the install uses the same versions you used during the development, and avoid issues if any of the dependencies are updated and they include breaking changes.

@richard-ramos -- are you ok with this being in /examples?
Also, @acolytec3, once this is in a good state, please don't forget to squash your commits.

Do you want me to include this? I guess I thought best practice was to leave this out and let the user's preferred package manager take care of the lock file (I use yarn in general).

Yes, please include it, that will make sure that the install uses the same versions you used during the development, and avoid issues if any of the dependencies are updated and they include breaking changes.

Done in latest commit.

@emizzle Rebased and squashed.
@richard-ramos Anything else you want to see changed?


Unable to access specific repository: Get "https://helm.elastic.co/index.yaml": EOF

I have a pipeline running on azure devops with selfhosted agents and I am having issues accessing a specific repository: https://helm.elastic.co
2022-01-20T11:16:02.3115600Z helm.go:88: [debug] Get "https://helm.elastic.co/index.yaml": EOF
2022-01-20T11:16:02.3117225Z looks like "https://helm.elastic.co" is not a valid chart repository or cannot be reached
2022-01-20T11:16:02.3117875Z main.(*repoAddOptions).run
2022-01-20T11:16:02.3118516Z 	helm.sh/helm/v3/cmd/helm/repo_add.go:206
2022-01-20T11:16:02.3119394Z main.newRepoAddCmd.func1
2022-01-20T11:16:02.3120012Z 	helm.sh/helm/v3/cmd/helm/repo_add.go:82
2022-01-20T11:16:02.3120563Z github.com/spf13/cobra.(*Command).execute
2022-01-20T11:16:02.3121123Z 	github.com/spf13/cobra@v1.2.1/command.go:856
2022-01-20T11:16:02.3121776Z github.com/spf13/cobra.(*Command).ExecuteC
2022-01-20T11:16:02.3122339Z 	github.com/spf13/cobra@v1.2.1/command.go:974
2022-01-20T11:16:02.3122991Z github.com/spf13/cobra.(*Command).Execute
2022-01-20T11:16:02.3123551Z 	github.com/spf13/cobra@v1.2.1/command.go:902
2022-01-20T11:16:02.3124024Z main.main
2022-01-20T11:16:02.3124787Z 	helm.sh/helm/v3/cmd/helm/helm.go:87
2022-01-20T11:16:02.3125170Z runtime.main
2022-01-20T11:16:02.3125461Z 	runtime/proc.go:225
2022-01-20T11:16:02.3125688Z runtime.goexit
2022-01-20T11:16:02.3125917Z 	runtime/asm_amd64.s:1371

We are unable to find any denied requests on the firewall. and I am able to access the repository using basic tools like curl/wget.
Everything does work when I skip tls cert checks with --insecure-skip-tls-verify
I figured it must be related to golang's own tls implementation then, but using https://github.com/colinodell/go-check-ssl I am able to verify the certificate.
So right now I am at a loss on where to continue from here. Any help is appreciated.
EDIT: I have found that everything works when I supply the root with --ca-file.
The GTS Root R1 certificate in included in my /etc/ssl/certs/ca-certificates.crt bundle, is helm using another bundle?
Output of helm version:

version.BuildInfo{Version:"v3.7.2", GitCommit:"663a896f4a815053445eec4153677ddc24a0a361", GitTreeState:"clean", GoVersion:"go1.16.10"}

Though I have tried with older versions as well

Golang httpClient  default CA  location.
// Copyright 2015 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

package x509

// Possible certificate files; stop after finding one.
var certFiles = []string{
	"/etc/ssl/certs/ca-certificates.crt",                // Debian/Ubuntu/Gentoo etc.
	"/etc/pki/tls/certs/ca-bundle.crt",                  // Fedora/RHEL 6
	"/etc/ssl/ca-bundle.pem",                            // OpenSUSE
	"/etc/pki/tls/cacert.pem",                           // OpenELEC
	"/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem", // CentOS/RHEL 7
	"/etc/ssl/cert.pem",                                 // Alpine Linux
}

// Possible directories with certificate files; stop after successfully
// reading at least one file from a directory.
var certDirectories = []string{
	"/etc/ssl/certs",               // SLES10/SLES11, https://golang.org/issue/12139
	"/etc/pki/tls/certs",           // Fedora/RHEL
	"/system/etc/security/cacerts", // Android
}

You mention azure devops with selfhosted agents. What OS? I’ve seen issues arise with certain OSes with Go’s TLS cert chain lookups.
How did you install helm? I’ve also seen issues with Go programs compiled with or without CGO (e.g. static binaries).

The VM image is based on Ubuntu 20.04.2 LTS
I'm unsure how Helm was originally installed as I'm not the one managing these agents. But for 3.7.2 I just grabbed the binary release manually.

That flag will override the environment variables SSL_CERT_FILE and SSL_CERT_DIR. Perhaps your CI environment has one of those set.

Good shout @joejulian , sadly not the case though. Nor any other relevant env variables I can find.


How to interpret the combination of metrics: context precision and the rest (real world example)

I ran ragas to evaluate my LangChain-powered chatbot (it's basically a QA chain with document retrieval) and I got the following results.

question
ground_truth
faithfulness
answer_relevancy
context_recall
context_precision
context_relevancy

Q1
GT1
1
0.813637991
1
0
0.002824859

Q2
GT2
1
0.835290922
0
0
0.002890173

Q3
GT3
1
0.882307479
1
0
0.002659574

Q4
GT4
1
0.844765424
0
0
0.01953125

Q5
GT5
1
0.889618083
1
0
0.017857143

Of course, the context_precision (another form of context_relevancy which will disappear I think, according to the docs) values are very low (aka horrible). So, I did some debugging to understand the intermediate calculations (I didn't grasp everything.. but I've got an idea), and I'm wondering how is this situation possible  (this is how I interpret it, and correct if I'm wrong):
context_recall: 1.00 (can it retrieve all the relevant information required to answer the question: YES)
context_precision: 0.00 (the signal to noise ration of retrieved context: -almost- everything retrieved is Noise)
For example, I checked that for one answer, this is how the context precision metric evaluated the 2 retrieved documents:
[[ChatGeneration(text='No.', generation_info={'finish_reason': 'stop'}, message=AIMessage(content='No.'))]
Yet, the faithfullness is 1 and the answer relevancy is 0.81.. I'm really confused.. maybe I miss something, but I'd like to understand how to interpret not only each metric independently, but the combinations of their values and what they entail.
Thank you,

I'm also wondering if this is a "side effect" of the (relatively) long chunks of my docs ? (around 500 tokens).. I don't know if this also impacts the calculation..

@shahules786 : could you please take a look on this please?

@shahules786  I'm afraid I can't share that since it's private data..
Basically, I have document chunks (say 2) returned by OpenSearch, which contain the answer to the question. The first document contains the response, the second contains a small portion of the answer. The second document is larger than the first.
I'm just wondering if ragas takes into account the ratio of "relevance to the question / length of the context" in its calculations of context_precision..

@shahules786 : I have tested using the example in ragas docs
So, I used this dataset:
from datasets import load_dataset

fiqa_eval = load_dataset("explodinggradients/fiqa", "ragas_eval")
fiqa_eval

and here's the result:

question
contexts
answer
ground_truths
context_precision
faithfulness
answer_relevancy
context_recall
context_relevancy

0
How to deposit a cheque issued to an associate...
[Just have the associate sign the back and the...
\nThe best way to deposit a cheque issued to a...
[Have the check reissued to the proper payee.J...
0.0
1.0
0.938239
0.875
0.058824

1
Can I send a money order from USPS as a business?
[Sure you can.  You can fill in whatever you w...
\nYes, you can send a money order from USPS as...
[Sure you can.  You can fill in whatever you w...
0.0
0.8
0.885277
1.000
0.285714

2
1 EIN doing business under multiple business n...
[You're confusing a lot of things here. Compan...
\nYes, it is possible to have one EIN doing bu...
[You're confusing a lot of things here. Compan...
0.0
0.8
0.924754
0.000
0.083333

3
Applying for and receiving business credit
[Set up a meeting with the bank that handles y...
\nApplying for and receiving business credit c...
["I'm afraid the great myth of limited liabili...
0.0
1.0
0.899104
0.500
0.333333

4
401k Transfer After Business Closure
[The time horizon for your 401K/IRA is essenti...
\nIf your employer has closed and you need to ...
[You should probably consult an attorney. Howe...
0.0
0.6
0.853572
0.000
0.043478

The context_precision is "almost" always equal to zero (or holds a near-zero value).
N.B: in the docs, we don't show the context precision

@shahules786 : sorry for bothering you, is someone from the team / community able to help on this please ? Thank you

Hi @younes-io , apologies for the late reply. Can you share your ragas version and LLM used?
Also can you try out the same using latest ragas in main ? You can install from source using pip install git+https://github.com/explodinggradients/ragas

@younes-io  If you're open for a short call, I would love to help in person. Please book a slot here  (early next week)

@shahules786 no worries, I'm also very sorry for the very late reply.. Sure, I'll book a slot!


Release 2.24.0

Description
note: Release 2.24.0 moves the default position of the account center from topRight to bottomRight. To reset your application to topRight, include the following when initializing onboard:
  accountCenter: {
      desktop: {
        enabled: true,
        position: 'topRight'
      },
      mobile: {
        enabled: true,
        position: 'topRight'
      }
    }

✨ Highlights

Enhancement: Account center default position, animation, and triggers #1740
feat: add Venly connector to packages #1660
Update: Bump socket.io-parser from 4.2.1 to 4.2.3 in /packages/demo #1737

Docs:

Fix: Docs - Update platforms Trust wallet is available on within injected docs #1743
Update: Bump socket.io-parser from 4.2.2 to 4.2.3 in /docs #1738

📦 Changes per package
@web3-onboard/core: 2.20.0
@web3-onboard/react: 2.8.5
@web3-onboard/venly: 2.0.0
@web3-onboard/vue: 2.7.4

I can't run yarn check-all now b/c it fails on the demo b/c of the venly package- but I removed everything listed above

Ok- re-ran yarn check-all and no more unused import or variable hints


Update example Cargo.toml

Just a quick fix for the version inside the example, otherwise you get:
error: failed to select a version for the requirement `lain = "^0.2"`
  candidate versions found which didn't match: 0.5.0
  location searched: XXX/lain/lain
required by package `example_fuzzer v0.1.0 (XXX/lain/examples/example_fuzzer)

humm, example look broken in fact.


cuda 9 with l4t-r28.1

Hi @madisongh,
I fell back to l4t-r28.1 to use Connect Tech's BSP, and I was wondering if you tried to use cuda-9 with r28.1 ? The default recipes are cuda-8, do you think that I'd only need to take the cuda-9 recipes instead ?
Elio
EDIT :
Okay, my image compiled so I guess what I did was enough. Namely, copy the cuda-9 recipes to my own meta, AND copy the ./external directory which contains a patch for opencv3.3. Last step, modify conf/layer.conf to warn bitbake that there are some files in external, as you did in your layer.conf

I don't know whether this would actually work, even if you copied over libcuda.so from the 28.2 driver package.  It's hard enough making even the NVIDIA-supported configurations work reliably.

I'll tell you as soon as I can test it


feat: execute evolv.rerun if multiple instances are found RKT-8984

If we call evolv.rerun when multiple instances are detected, any relevant JS will execute. At the moment, nothing executes if multiple instances are found. This is a major problem for Bouygues.
Is this the right way to go about it? I've tested and it works for Bouygues.

@joshua-barnard-evolv @mattstrom -- this doesn't look like the right fix to me. There must be something preventing us re-evaluating the keys. Could be worth bailing out of the main function event earlier -- very first thing. When you start your day can we take a look and debug?


Has Update SSH key on an existing AKS cluster (preview) feature  been deployed in China Azure?

Hello，
When testing the code in this document, the following error occurs:
_[root@newname ~]# az aks update --name myaks --resource-group aks --ssh-key-value .ssh/id_rsa.pub
The behavior of this command has been altered by the following extension: aks-preview
Updating the cluster with no ssh key set at creation is not supported
Could you please tell us whether the update SSH key on an existing AKS cluster (preview) feature mentioned in this document is currently available in Azure China?
Is there anything wrong with this code？
az aks update --name myAKSCluster --resource-group MyResourceGroup --ssh-key-value .ssh/id_rsa.pub
Looking forward your reply, thank you!
Best Regards，
Wendy

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

ID: 3b81a147-db1c-b92f-88d1-6dd0991a72fe
Version Independent ID: f5a2c949-498f-5848-d89c-031d1a757120
Content: Connect to Azure Kubernetes Service (AKS) cluster nodes - Azure Kubernetes Service
Content Source: articles/aks/node-access.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@wendiz-zhang
Thanks for your feedback! We will investigate and update as appropriate.

@wendiz-zhang
To determine if the "update SSH key on an existing AKS cluster (preview)" feature is currently available in Azure China, I recommend checking the Azure China documentation or contacting Azure China support directly. They will be able to provide you with the most up-to-date information regarding feature availability.
Regarding the code you provided, there doesn't appear to be anything technically wrong with it. However, the error message you received suggests that updating the SSH key for an existing AKS cluster without setting it during creation is not supported. It's possible that the "update SSH key on an existing AKS cluster" feature requires the SSH key to be provided during the initial creation of the cluster.
To resolve the issue, you may need to create a new AKS cluster with the desired SSH key or explore alternative methods for updating the SSH key on an existing AKS cluster, such as using the Azure Portal or Azure CLI options specific to Azure China.


Build error due to cout

In file included from /home/ishank/Workspace/opendetection/common/utils/utils.cpp:4:0:
/home/ishank/Workspace/opendetection/common/utils/utils.h: In function ‘void od::printListIn(std::vector<_Tp>, int)’:
/home/ishank/Workspace/opendetection/common/utils/utils.h:169:7: error: ‘cout’ is not a member of ‘std’
       std::cout << (Ptype) list[i] << " ";
       ^
/home/ishank/Workspace/opendetection/common/utils/utils.h:170:5: error: ‘cout’ is not a member of ‘std’
     std::cout << std::endl;
     ^
/home/ishank/Workspace/opendetection/common/utils/utils.h: In function ‘void od::printList(std::vector<_Tp>)’:
/home/ishank/Workspace/opendetection/common/utils/utils.h:177:7: error: ‘cout’ is not a member of ‘std’
       std::cout << list[i] << " ";
       ^
/home/ishank/Workspace/opendetection/common/utils/utils.h:178:5: error: ‘cout’ is not a member of ‘std’
     std::cout << std::endl;
     ^
/home/ishank/Workspace/opendetection/common/utils/utils.h: In static member function ‘static std::string od::FileUtils::getFirstFile(std::string, std::string)’:
/home/ishank/Workspace/opendetection/common/utils/utils.h:200:9: error: ‘cout’ is not a member of ‘std’
         std::cout << "No file with extension " << extension << " present!\nReturning NULL";

I am getting these errors while building opendetection on Ubuntu 14.04. I think utils.h is probably missing iostream. If this is the problem I can raise a PR?

Hi,
Didn't see this before. Probably because some other header was including
iostream before utils.h
Utils has its own independent dependency on iosream. Surely go ahead and
make a PR.
On Feb 27, 2016 3:55 AM, "Ishank Gulati"<EMAIL_ADDRESS>wrote:

In file included from /home/ishank/Workspace/opendetection/common/utils/utils.cpp:4:0:
/home/ishank/Workspace/opendetection/common/utils/utils.h: In function ‘void od::printListIn(std::vector<_Tp>, int)’:
/home/ishank/Workspace/opendetection/common/utils/utils.h:169:7: error: ‘cout’ is not a member of ‘std’
std::cout << (Ptype) list[i] << " ";
^
/home/ishank/Workspace/opendetection/common/utils/utils.h:170:5: error: ‘cout’ is not a member of ‘std’
std::cout << std::endl;
^
/home/ishank/Workspace/opendetection/common/utils/utils.h: In function ‘void od::printList(std::vector<_Tp>)’:
/home/ishank/Workspace/opendetection/common/utils/utils.h:177:7: error: ‘cout’ is not a member of ‘std’
std::cout << list[i] << " ";
^
/home/ishank/Workspace/opendetection/common/utils/utils.h:178:5: error: ‘cout’ is not a member of ‘std’
std::cout << std::endl;
^
/home/ishank/Workspace/opendetection/common/utils/utils.h: In static member function ‘static std::string od::FileUtils::getFirstFile(std::string, std::string)’:
/home/ishank/Workspace/opendetection/common/utils/utils.h:200:9: error: ‘cout’ is not a member of ‘std’
std::cout << "No file with extension " << extension << " present!\nReturning NULL";
I am getting these errors while building opendetection on Ubuntu 14.04. I
think utils.h is probably missing iostream. If this is the problem I can
raise a PR?
—
Reply to this email directly or view it on GitHub
https://github.com/krips89/opendetection/issues/1.


drivers: adc_gecko: Add adc_gecko driver

This is a redo of the old branch that didn't work.  This gives us a generic adc driver for the silabs pearl gecko processor.

Regarding the sample, could we just have it read the ADC and report the reading? I think the BQ and battery controller code isn't relevant to showing how to use the Gecko ADC.

I think there was a suggestion to use the logging system (e.g. LOG_INFO, etc) in the driver.

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

edtt
https://github.com/zephyrproject-rtos/edtt/commit/8ef968c1471769af61ba3e5befb6b119b22a7afe
https://github.com/zephyrproject-rtos/edtt/commit/64e5105ad82390164fb73fc654be3f73a608209a (main)
<EMAIL_ADDRESS>

hal_espressif
https://github.com/zephyrproject-rtos/hal_espressif/commit/73e7af1e2ed64571ce49ff9f07dc02690b9f2df5
https://github.com/zephyrproject-rtos/hal_espressif/commit/d2564ca5c14439888f7c4351884a2cf4db517a33
<EMAIL_ADDRESS>

hal_infineon
https://github.com/zephyrproject-rtos/hal_infineon/commit/5b0c7700a7be049e02835dfa0950d378aac39e67
https://github.com/zephyrproject-rtos/hal_infineon/commit/8485083ad91d3e2cc5d706da3464716718a6a42e (master)
<EMAIL_ADDRESS>

hal_nordic
https://github.com/zephyrproject-rtos/hal_nordic/commit/3f7ae2320b6d348898c7b11e956a6e792d0b3724
https://github.com/zephyrproject-rtos/hal_nordic/commit/6c6b666ab3bc02b6fa0696ab7bd15658a694a03a (master)
<EMAIL_ADDRESS>

hal_nxp
https://github.com/zephyrproject-rtos/hal_nxp/commit/d957472002a3758154f402e982d95ce90cf58e12
https://github.com/zephyrproject-rtos/hal_nxp/commit/afd053086e9e36a413f7cbec40694733588e1b9f
<EMAIL_ADDRESS>

hal_renesas
https://github.com/zephyrproject-rtos/hal_renesas/commit/468d3f2146d18c7f86a4640fc641cc1d20a4a100
https://github.com/zephyrproject-rtos/hal_renesas/commit/f2d791d28cd8fdbc5861652b863822632c91f690 (main)
<EMAIL_ADDRESS>

hal_rpi_pico
https://github.com/zephyrproject-rtos/hal_rpi_pico/commit/a094c060e0c2d43c7f9d8f5c06cc0665117e0c18
https://github.com/zephyrproject-rtos/hal_rpi_pico/commit/b7801e4db6a62ea2d37bbef7880c3d056530c9bf (zephyr)
<EMAIL_ADDRESS>

hal_stm32
https://github.com/zephyrproject-rtos/hal_stm32/commit/c36136b253a46ed8dd63525eeee659393047ce83
https://github.com/zephyrproject-rtos/hal_stm32/commit/7c511b744fadde3fd197779a93043d27e30b0025
<EMAIL_ADDRESS>

mcuboot
https://github.com/zephyrproject-rtos/mcuboot/commit/750678e33819b95756203e5db1ba827baee35708
https://github.com/zephyrproject-rtos/mcuboot/commit/59624334748129cb93f096408911a227b0dd64c0 (main,new-history)
<EMAIL_ADDRESS>

nanopb
https://github.com/zephyrproject-rtos/nanopb/commit/dc4deed54fd4c7e1935e3b6387eedf21bb45dc38
https://github.com/zephyrproject-rtos/nanopb/commit/42fa8b211e946b90b9d968523fce7b1cfe27617e (zephyr)
<EMAIL_ADDRESS>

nrf_hw_models
https://github.com/zephyrproject-rtos/nrf_hw_models/commit/d8f125e1988221ebfea5944fc3118f1780787ccc
https://github.com/zephyrproject-rtos/nrf_hw_models/commit/feb3e555f7745dc4fd0a16403f5d81a7ea7359b0 (master)
<EMAIL_ADDRESS>

openthread
https://github.com/zephyrproject-rtos/openthread/commit/242c7cc7c3a80c985476689b64cdb6d8fbcf5b6d
https://github.com/zephyrproject-rtos/openthread/commit/1f1a826d1891fc99d14822abc0a1de257e9c6e9b (main)
<EMAIL_ADDRESS>

picolibc
https://github.com/zephyrproject-rtos/picolibc/commit/98e59b70d6ef8eb18f7dccc3d39cecaa0658fa4f
https://github.com/zephyrproject-rtos/picolibc/commit/0694a78fc08b3300c7db79602c46ba0a64428c8e (main)
<EMAIL_ADDRESS>

psa-arch-tests
https://github.com/zephyrproject-rtos/psa-arch-tests/commit/24ed42e34e03ebbc945a7204819c1471cce2bda8
https://github.com/zephyrproject-rtos/psa-arch-tests/commit/6a17330e0dfb5f319730f974d5b05f7b7f04757b (master)
<EMAIL_ADDRESS>

trusted-firmware-m
https://github.com/zephyrproject-rtos/trusted-firmware-m/commit/f2a639c8d1842acb2964a27461f5c9cfdfaa4d16
https://github.com/zephyrproject-rtos/trusted-firmware-m/commit/a8313be08816a2ed9d883c6b79fb4e5d2bef81c2 (master)
<EMAIL_ADDRESS>

Note: This message is automatically posted and updated by the Manifest GitHub Action.


@key directive keep adding LSI instead of GSI

Amplify CLI Version
4.45.2
What operating system are you using?
MacOS
Amplify Categories
api
Amplify Commands
add
Describe the bug
How to tell Amplify to add a GSI instead of LSI ?
this got me an LSI, where I want it to be a GSI.
@key(name: "byStatus", fields: ["owner", "status", "createdAt"], queryField: "listReviewsByStatus")

Expected behavior
Let user choose wether it'll add a GSI or LSI.

A LSI is created when the fields of the primary key are used in the secondary key. Though we did change this behavior and by default it now creates a GSI.
FeatureFlag here: https://docs.amplify.aws/cli/reference/feature-flags#secondaryKeyAsGSI

@SwaySway I'm using the latest version, still not works. Should I create the cli.json to make the "default" behavior happens?

@yaquawa Thanks for following up.
Yes, you can create if you don't currently have a cli.json in your /amplify directory. You can follow these instructions to get more info - https://docs.amplify.aws/cli/reference/feature-flags#configuration.
If you don't currently have that file,  verify that adding other flags will not alter your desired behavior.
After creating a new project with amplify init for Amplify CLI v4.46.1, the default contents is:
{
  "features": {
    "graphqltransformer": {
      "addmissingownerfields": true,
      "validatetypenamereservedwords": true,
      "useexperimentalpipelinedtransformer": false,
      "enableiterativegsiupdates": false,
      "secondarykeyasgsi": true,
      "skipoverridemutationinputtypes": true
    },
    "frontend-ios": {
      "enablexcodeintegration": true
    },
    "auth": {
      "enablecaseinsensitivity": true
    },
    "codegen": {
      "useappsyncmodelgenplugin": true,
      "usedocsgeneratorplugin": true,
      "usetypesgeneratorplugin": true,
      "cleangeneratedmodelsdirectory": true,
      "retaincasestyle": true
    },
    "appsync": {
      "generategraphqlpermissions": true
    }
  }
}

Hope that this helps!


341: Change the import path for FRFrequencyType and FRQuarterType

Issue: https://github.com/SecureBankingAccessToolkit/SecureBankingAccessToolkit/issues/341

Replaced by this PR: https://github.com/SecureBankingAccessToolkit/securebanking-openbanking-uk-rs/pull/84


Support for Cluster update settings API

We've been working on a project where we need to perform the following query to disable shard allocation using the client.
PUT _cluster/settings
{
  "persistent": {
    "cluster.routing.allocation.enable": "primaries"
  }
}

From your README.md, it seems like you haven't provided support for this endpoint yet.
Is there any way to perform this using the existing client library?
Or anything else.
Which version of Elastic are you using?

elastic.v7

Is there any update on this it's been 4 years and still not implemented?

@apgmckay This project has been deprecated for many years now. It's still around because some people still rely on it. But with the decision of Elastic to build their own official Go client, it doesn't make sense to "compete" against it with an unofficial, community-supported client. The speed with which they add features is way too high for that, and the ability to plan ahead is not a given. This project won't get new features or support new versions of Elasticsearch. You should update your code to use the official client. They, e.g., already support the cluster settings API.

Thanks for the reply @olivere totally makes sense.
The only reason I was asking was because this was package is a dependency of this open search  terraform provider has a dependency on this un API.
But yeah... I'll try and see if I can get them/ or even just do it myself to change to the official Go client for elastic 🤔
Thanks again.

@apgmckay Thanks for the clarification. Just a final note: As a workaround, you (the Terraform provider) can always use PerformRequest directly to implement calls into Elasticsearch that are not supported by the DSL.

Interesting thanks for the share @olivere I'll give that a look.


Rename object to Object

Using Typescript 2.3.2, hit the following error:
Error - typescript - node_modules\botframework-directlinejs\built\directLine.d.ts(203,12): error TS2304: Cannot find name 'object'.
Found the following issue on the Typescript repo that suggested using uppercase O due to the object keyword in Typescript 2.2. Changing this certainly fixed in my scenario.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

First of all, please file issues for any problems you see. That gives us a better forum for discussing them and their possible solutions.
In this case I'm not seeing any compilation errors with TypeScript 2.3.2. As you say, the object type has been around since 2.2, so there should be no problem using it in 2.3.2.
If you read through the issue you linked to, you'll see that the ultimate answer was that they had dependency issues that meant they were actually compiling with an older version of TypeScript, and I strongly suspect that's what you're experiencing as well.

Apologies, will log as issue instead next time. Will add details to issue when I find out true cause then.

For anyone else who hits the issue and this might help, I found the cause to be from gulp-core-build-typescript which I was using via SharePoint Framework. The link below helped me find this.
https://sharepoint.stackexchange.com/questions/209553/sharepoint-framework-how-to-change-typescript-version-used-by-gulp
Until that is updated to Typescript 2.2 (https://github.com/Microsoft/web-build-tools/pull/166), I found that pinning back to BotFramework-DirectLineJS 0.9.4 and Webchat 0.10.4.
"botframework-webchat": "0.10.4",
"botframework-directlinejs": "0.9.4"
Sorry again for the incorrect PR.

So, in your scenario, you are building from TS sources instead of consuming npm packages?

It's using the SharePoint framework deployment with gulp and that uses Microsoft's web build tools. I'm not building directly from TS sources but there is a fixed Typescript package in there.


docs reorg

-This PR is now at a place where it can be merged once approved, no additional work is needed.

Note - this is a connected pr from the chialisp site, both must be merged in a timely manner of one another as they contain link fixes (links will break due to migration of some pages so the fixes are essential): https://github.com/Chia-Network/chialisp-web/pull/257

Changes included in this pr:
Renamed a series of pages (slugs/urls were maintained where possible, redirects in place otherwise):

Guides -> Dev Guides
Farming Guide -> Farming Guide
Offers - GUI -> Wallet Guide
Using the GUI -> Using the Chia GUI
Installation -> Advanced Installation

Updated header links

all external links are now on the right side with the language selection
updated docs link to a home page
updated dev guides link to a homepage

Creating a series of new categories on the docs main site and the Guides subpage:
Docs categories created:

Advanced User Docs
Troubleshooting
Learn More

Dev Guides categories created:

Primitives

Chialisp Site categories created:
Moved a series of pages to new locations (all old locations have had redirect pages added as needed)

Using the Chia GUI -> Getting Started
Beginners Wallet Guide -> Getting Started
Advanced Installation -> Advanced User Docs
Testnets -> Advanced User Docs
Plotting -> Advanced User Docs
Farming -> Advanced User Docs
Reference Client -> Advanced User Docs
RPC Reference -> Advanced User Docs
CLI Reference -> Advanced User Docs
Wallet Connect -> Advanced User Docs
Check If Things Are Working -> Troubleshooting
Node Syncing -> Troubleshooting
Logging Reference -> Troubleshooting
Coin Set Model -> Learn More
Architecture -> Learn More
Consensus -> Learn More
Keys -> Learn More
Protocol -> Learn More
Green Paper -> Learn More
Resources -> Learn More
NFT Guide -> Primitives
CAT Guide -> Primitives
DataLayer -> Primitives
Clawback -> Primitives
Offers -> Primitives
DAOs -> Primitives
VCs -> Primitives
Custody Tool -> Tutorials
WalletConnect -> Tutorials
Simulator User Guide -> Tutorials
Seeder User Guide -> Tutorials
Chialisp Concepts (and contained files) -> Chialisp site
Chialisp Primer (and contained files) -> Chialisp site
Coin Set Model (costs, conditions) -> Chialisp site

Created Pages:

Chia Docs Home
Primitives landing page (setup as generated index in sidebar)
Dev Guides Home
updated descriptions on all landing pages to make them more engaging
update images on home pages to make each unique

TODO:
Create a contributors guide illustrating how to contribute content while maintaining formatting

this will be completed after the docs-reorg is complete and is present here for transparency.

Note - when merging we will want to squash this pr 👍


improve generation rules for F05.01

We have also added items to the TYP_ACCNTNG_ITM domain for this issue.
We will document this fully soon as it relates to the approach of how we work with TYP_INSTRMRNT and TYP_ACCNTNG_ITM which are special domains. In short for some Select Member items we use items that are for the finrep output layer only, and do not need to be included in the input layer.


{CI} Add time.sleep to ensure that the live test can delete the resource group

Related command

Description

During the 'webapp vnet-integration remove' call, we enter 20s wait for hit geo and 45s wait on app service side in order for NCs to be deleted successfully on machines.
So add time.sleep(65) for all az webapp vnet-integration related commands.
This can avoid resource residue caused by appservice related tests.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

CI


empty file submission

Hello,
First, thanks for your work !!
I've noted that sending empty file raise an error after creating the file and setting a new name if the submitted file is not setted
$file  = new File($name, $storage);
$file->setName( $name );   [raise error if key ok but error code 4]
You raise an exception if a not existing key is submitted but you don't check the error 4 (empty path) when creating a new name.
Perhaps i'm not using correctly the API. Let me know.
I do my own check in the meantime.
With regards,
Rodney

Hi,
in dev-master version, an exception is raised if we try submit an empty input file.
The array errors on line 133 of file File.php should ignore errors  #4.
Thanks.


loop name displayed wrong

Hi there!
I have the following .cali file:
211111-142429_38224_TT0zGmRHyQDy.cali.txt
And the display on SPOT has changed my loop name predictor-corrector into ayor-corrector:

Odd.
I don't see this on our LLNL-deployed SPOT with your file.  I'll try with the container build...

@aschwanden1
I can reproduce this in the container.  It looks like a problem in our compression.  From eyeballing it, I think the compressed data is flowing correctly out of the backend.  So I'm guessing there's some bug on the frontend when decompressing.  Can you look into that, Pascal?
Although as a second point, I thought that compression code was disabled.  The BE seems to disable compression when I run off of the deployment at LLNL, and enable it when I run out of the container. I don't see any configuration checks that would change the compression decision, so I'm guessing there's some git checkout difference between our LLNL live deployment and the container.  But I'm not sure how to check which spotbe/ git hash we have running in our LLNL live deployment.  And the compression (and bug) still occur if I move the spotbe/ in the container to HEAD.  Any insight here, Pascal?

Thanks for digging into this @mplegendre ! It sounds like a short-term fix would be to figure out how to disable compression and then do that

yes, I'll take a look at this right now and see if i can reproduce.  it should be very easy to turn off compression.

Just at first glance, I think there is a bug in the dictionary translations.
In any case, I'll see if there's a quick fix.

Ok, so I've created a fix that should fix the issue.  I've placed it in a branch here: (in spotbe) pa-fix-substring-replacement-bug and pushed it up to github.  If you wanted a quick fix, you could try that out.
Before our next release, I'll test it more and merge into master.

That fixed it for me.
Can we still disable the compression and push that into the container?  I'm nervous about the two deployments diff'ing on a big piece of functionality.

Yes.  It's a one line change.  i'll merge that into master and then I'll update the container spotbe to that commit.

done.

This fixes the issue for me with the latest version of this repository! Thank you both!


About unobserved voxel in camera view

thanks for your outstanding work.
I have a question about Occ3D(v2).  According to Algorithm 1 and 3, when performing camera ray casting, the camera ray stops only when cur_voxel goes out of spatial_shape or reaches the last voxel. This seems not to produce the occlusion effect shown in Fig.8. Because the ray casting does not stop when the camera ray reaches an observed voxel (occupied or free voxel). According to subsection 3.3.2, if the camera ray only sets the first encountered voxel as occupied, then there should be much more voxels labeled as unobserved. Therefore, I am very curious about the details for generating the camera visibility mask, especially when the camera ray stops casting.
I'd appreciate it if you could answer my questions.

The update_voxel_state is initialized to 'NOT_OBSERVED',  and only the traversed voxels are marked as OCCUPIED or FREE. So when when the camera ray stops casting, the remained voxels are still marked as 'NOT_OBSERVED'.

Thanks, I got what you mean. But I'm still confused about when the camera ray stop casting. According to Algorithm 1 and 3, the camera ray stops only when cur_voxel goes out of spatial_shape. Beacause the init depth for each voxle is set to DEPTH_MAX(1e3). Under this condition, if a camera ray traverses two occupied voxels, the second occupied voxel which should be occluded seems to still be labeled as occupied since the camera ray does not reach the boundary.

If the camera ray already hits the nearest occupied voxel, the traversing will stop since the ‘for ’ loop will break.
The remaining voxels are still marked as 'NOT_OBSERVED'.

In this way, a closer occupied voxel may block several camera rays. It seems that there would be much more voxels labeled as ‘NOT_OBSERVED’, including those should have been observed？

After performing camera ray casting, there would be much more voxels labeled as ‘NOT_OBSERVED’.

Thanks a lot ! By the way, when will the code be released?

The code has been released, and in the upcoming period, our team members will re-organize the code and improve the readability.

At present, the code used for ground-truth (GT) construction will not be released. This decision was made to prevent challenge participants from using scripts to generate their submissions.


JUnit XML files generated by meson are not parsed

The JUnit XML files generated by meson are not parsed: https://github.com/jluebbe/rauc/pull/4#issuecomment-2348679752
In the web dashboard tab for tests, "No test results found for this branch" is shown.

Originally posted by @jluebbe in #304

@jluebbe
Do you mind posting a raw version of the JUnit xml that you tried to upload? Inspecting our logs, it seems like we're erroring out because a field we rely on  is missing.
Specifically, the error message states "No duration found".

This is the output of running the RAUC testsuite: testlog.junit.xml.gz

@jluebbe thanks for your patience on this. It looks like there wasn't a time attribute on the test case, which our parser was expecting. I'm unclear if this is unique to your setup or to the tool that is generating the report.
At any case, we're trying to handle it on the parser side -> you can follow along https://github.com/codecov/test-results-parser/pull/30

Thanks for implementing this so quickly! I've tried the build and test result upload again: https://github.com/jluebbe/rauc/actions/runs/10915969616/job/30296620556
So far, the results have now shown up on https://app.codecov.io/gh/jluebbe/rauc/tests/codecov. Do I need to wait until the fixed version is deployed?

I've tried this again (https://github.com/jluebbe/rauc/actions/runs/11345991363), but the results are not showing up. Is that something I can fix on my side?
Some details...

the upload step: https://github.com/jluebbe/rauc/actions/runs/11345991363/job/31554073912#step:6:1
the same junit.xml uploaded as a github artifact: https://github.com/jluebbe/rauc/actions/runs/11345991363/job/31554073912#step:7:21

@jluebbe it looks like the generated JUnit XML doesn't have the time attribute on the testcase elements which is something our JUnit XML parser assumes is there.
I think we can make the parser ignore this for now, but we don't have a way to process the duration of a testsuite.
I think this is a property of meson's JUnit reporting where a test maps to a testsuite in the JUnit report and the actual test functions in the test file map to testcase objects, which is different from how testing frameworks like pytest or jest report their test results.

Even without the duration information, having the test results in codecov would be useful.
The name change issue seems like something we should fix on meson.


Get depth value at a pixel

I am tying to get depth value at a pixel of the color image. Since the depth and color image have different resolutions, I am trying to use function k4a_transformation_color_image_to_depth_camera to get the depth pixel. Is this the right approach?
`k4a_image_create( K4A_IMAGE_FORMAT_COLOR_BGRA32,
depth_image_width_pixels,depth_image_height_pixels,
k4a_image_get_stride_bytes(depth_image),
&transformed_color_image)
k4a_transformation_color_image_to_depth_camera(transform, depth_image, color_image, transformed_color_image`
I get the error:
[error] [t=4167] /home/vsts/work/1/s/extern/Azure-Kinect-Sensor-SDK/src/transformation/transformation.c (534): transformation_color_image_to_depth_camera(). Expect both depth camera and color camera are running to transform color image to depth camera.
Currently, I m using one kinect device and the configuration for my camera is mentioned below from which I capture both the color and depth images. How can I get the depth value at a pixel of a color image?
My camera configuration is given below:
k4a_device_configuration_t config = K4A_DEVICE_CONFIG_INIT_DISABLE_ALL; 	config.camera_fps = K4A_FRAMES_PER_SECOND_30; 	config.color_format = K4A_IMAGE_FORMAT_COLOR_BGRA32; 	config.color_resolution = K4A_COLOR_RESOLUTION_2160P; 	config.depth_mode = K4A_DEPTH_MODE_NFOV_UNBINNED; 	config.synchronized_images_only=true; // Start the camera with the given configuration if (K4A_RESULT_SUCCEEDED != k4a_device_start_cameras(device, &config))

@snair61 , please take a look the example https://github.com/microsoft/Azure-Kinect-Sensor-SDK/tree/develop/examples/transformation, also please take a look the documentation: https://docs.microsoft.com/en-us/azure/Kinect-dk/use-image-transformation. Let us know whether the example can help you solve your problem.

Thank you. That resolved it. My sensor calibration was not right.

@rabbitdaxi
Hi, if I want to show the depth camera with gray mode.
such as kinect v2 we can see the depth but only in gray scale.
I just bought it . And I used to use kincet v2 in unity only.

Hi @snair61, how did you solve the sensor calibration problem ?


Result form and change log: Inconsistencies in trailing zero treatment

It's my recollection that we decided on a global rule for trailing zeroes -- to remove them.
In the case of the result form, I'm noticing trailing zeroes displayed in actual values in two spots:

[x] 1. Actual value input field: When I add a new result, it automatically rounds if I enter a trailing zero, even before I submit. But when I re-open the result after saving, I see a trailing zero.

[x] 2. Actual value row in the disaggregation table.

[ ] 3. (Added later) Also noticed a trailing zero issue in the change log. I can't tell if that's connected to this issue, but seemed like as good a place as any to put it:

Result form section complete, assigning to sanjuro and moving back to ready to handle change log element

@jennyhavah One testing note is that older data will still be inconsistent (the extra zeros are saved to the database). But any new changelog data created should have extra zeros shaved off the end.

For new results, no longer seeing trailing zeroes when I reopen a saved result, or in the change log.

Sanjuro noticed that this issue seems to be happening again -- possibly a regression?

The problem was that hitting the reset button was turning e.g. 6 into 6.00 in both the actual value and disagg fields.  This behavior should be corrected now.

Found a couple of issues.

I'm still seeing trailing zeroes in the change log when the value is zero. (No trailing zeroes when the value is greater than zero.)

While reproducing the above issue, I discovered that I can no longer submit a result value of zero. Disaggregated values can be zero, but not the total. A result of zero should be allowable. (It is allowed as expected on Prod.)

I can now submit a result with a value of zero, and am no longer seeing trailing zeroes in the change log.


Missing required parameters for url

Laravel Version: 5.3.31
PHP Version: 7.1.2

Description:
Laravel throws Missing required parameters for url error.
Steps To Reproduce:
Create a route with url: Route::get("some/test/url/{one_id}/{two_id}")
Call it like: route('route', ['one_id' => 1, 'two_id' => 2])
The weird part is that it works when both parameters are optional; it generates an url with the correct parameters, so I'm sure the parameters can't be the problem.

Have you tried route('route', [1, 2]) ?

I have, same error

@jordyvandomselaar I'm seeing the same issue with the password reset email in 5.4.

OK, I believe I figured out what my issue was:
I'm using a token in the subdomain of my APP_URL like this: APP_URL={subdomain}.appurl.com. When using the route('route.name', 123) helper, it was attempting to use the {subdomain} token and then didn't have a second token for route.name, which required one.

Hmmm, strange, I don't use subdomains but it might be a similar problem.


Retry MaaS alarm status verification, closes #903

Add retrying to the task verifying the status of MaaS alarms.
MaaS alarms can take several minutes, after a plugin starts returning
the correct data, to return to an okay state. This is causing the
upgrade script to fail intermittently. This change will allow more time
before reporting a failure.
Closes-issue: https://github.com/rcbops/rpc-openstack/issues/903

Shame that this is needed, but the failure record shows that it is.

:+1: as well

recheck_ceph

recheck_swift

recheck_ceph

recheck_ceph


Documentation updates for >= 5.4

Got a little behind on things.

[x] IChangeListener for the async daemon
[x] Recommendation of computed index over duplicated field
[x] Executing custom SQL in DocumentSession
[x] IgnoreIndex()
[x] Easier mechanism to add custom database objects through Marten
[x] DeleteObjects(IEnumerable<object> documents)
[x] Maybe a bit more on tombstone events?
[x] New base classes for aggregated projections
[x] Version convention on aggregations
[ ] CLI with WebApplication bootstrapping
[ ] Event store FetchForWriting()
[ ] New IEventStream mechanics
[ ] Mention DeadLetterEvent in the event store storage docs

I'm doing a little bit on this today. Got a couple knocked off


prevent infinity loop while detecting shell

In OS X, Process(pid=0).parent() == Process(pid=0)

Coverage increased (+2.6%) to 92.987% when pulling cfa51506fb546296d7f60e400c334266d8f5668d on blahgeek:master into 070bb2ff28b108e5fc627efa1d95ded00ca067c8 on nvbn:master.

Thanks!


SessionID giving Error

[Error] Error reading character data for %%%, if you are in offline mode you will need to login and update. If you received this error while logging in, the authenticated session may have expired or bad data has been returned by GGG or a network issue may have occurred - Please try again.
Can not test e-mail login, as I'm connecting into Forums / Game using Steam. SessionID is only option.
Looks to be Known Issue since the release of the latest.

Please update to Procurement 1.19.0, and create a new ticket if this is still an issue.


Update podman test workflow for new justfile setup

This updates the podman tests CI to correctly use new justfile setup.
Also updates the total number of tests, and setup-go action version.
I validated this in https://github.com/YJDoc2/youki/actions/runs/5239903983

Codecov Report

Merging #2037 (9bc5701) into main (66896c2) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2037   +/-   ##
=======================================
  Coverage   64.83%   64.83%
=======================================
  Files         129      129
  Lines       14763    14763
=======================================
  Hits         9571     9571
  Misses       5192     5192


:docsadded

Should we maybe convert this to markdown? That way we'll be able to put it in the readme. Also: maybe we should force-push it at the beginning of the timeline


Properly support function types

e.g. void(i32, f32). Should probably include function pointers, if there's anything that might complicate their syntax or semantics: void(i32, f32*) should just parse, right? and sema should be able to call both and understand that function values don't make sense most places.

as a separate note, I know I wanted raw function types to be useful as generic wrappers around both static functions and closures, so void(i32, f32) might actually be a fat pointer type if I don't think of something else, meaning void(i32, f32)* is a pointer to the fat-function-pointer, not a regular function pointer...
syntactic suggestions welcome.

my first thought is just to add a keyword, like func void(i32, f32), giving func void(i32, f32)* as the function pointer variant (if the distinction is useful at that point; it is for C, but probably isn't for Laye, so it's entirely possible that func implies the pointer)

I don't see a reason for a new keyword. Shouldn't it just parse without like c?

Correct, which is still the intent. The question is including the difference between an all-encompassing "this behaves like a function with this signature" type and a literal "this is just the type of a function (or a pointer to it)".
basically, what is the type of each of these vars:
void foo(int a);

var x = foo;
var y = (int a) => x(a);


Add support for dynamic expressions

Codecov Report

Merging #956 into master will decrease coverage by 0.02%.
The diff coverage is 54.81%.

@@            Coverage Diff             @@
##           master     #956      +/-   ##
==========================================
- Coverage   47.88%   47.85%   -0.03%
==========================================
  Files         228      229       +1
  Lines       21661    21758      +97
  Branches     4944     4974      +30
==========================================
+ Hits        10372    10413      +41
- Misses      11289    11345      +56

Impacted Files
Coverage Δ

...asource-protocol/lib/operators/FeatureOperators.ts
15.38% <0%> (ø)
:arrow_up:

...atasource-protocol/lib/operators/ColorOperators.ts
100% <100%> (ø)
:arrow_up:

...datasource-protocol/lib/operators/TypeOperators.ts
100% <100%> (ø)
:arrow_up:

...atasource-protocol/lib/operators/ArrayOperators.ts
90.9% <100%> (+0.9%)
:arrow_up:

...datasource-protocol/lib/operators/CastOperators.ts
100% <100%> (ø)
:arrow_up:

...tasource-protocol/lib/operators/ObjectOperators.ts
93.75% <100%> (ø)
:arrow_up:

...datasource-protocol/lib/operators/FlowOperators.ts
85% <100%> (ø)
:arrow_up:

...here/harp-datasource-protocol/lib/ExprEvaluator.ts
85.71% <12.5%> (-5.64%)
:arrow_down:

...datasource-protocol/lib/operators/MathOperators.ts
15.51% <21.15%> (ø)
:arrow_up:

...urce-protocol/lib/operators/ComparisonOperators.ts
22.85% <27.77%> (ø)
:arrow_up:

... and 12 more

Continue to review full report at Codecov.

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


Run xhr transformers after request interceptors and refactoring

Transformers responsible for modifying the xhr are renamed xhrTransformers to distinguish them from transformers which modify the message (those defined in RequestBuilder and applied in HttpClient).

A base class RequestMessage is created to contain common functionality of HttpRequestMessage and JSONPRequestMessage

The xhr is opened and transformed at a later stage, after any request interceptors are run. This allows interceptors to modify the request and closes #60.

Sorry for mashing unrelated commits together, but as two of them are really minor i thought it would save some merging.

@bryanrsmith Can you review this? Also, can you take this into account with respect to the fetch client as well? I know we can't make these apis identical, but it seems reasonable to try to carry concepts and behaviors across the two when possible.

Thanks, @alexanderchr! I think this has been bugging a lot of people. Would you mind making a couple cleanup changes?

We update the dist/ files at release time, and not with every commit. Could you reset those changes so the commits include only files in src/?
I agree that "xhrTransformers" is a clearer name, but that file also includes response transformers that are no longer appropriate under that name.
 Using that format makes it much easier for us to track changes for release notes and such.

Otherwise this looks good to me!

Thank you very much for the feedback @bryanrsmith. I've fixed most of your comments and updated the commits.
I don't understand your second point though. As far as i can see there are no response transformers in src/transformers.js Am i missing something?

@alexanderchr Ah, my mistake. I was looking at contentTransformer, which doesn't mutate the xhr. I think it's close enough, though :-)

That one bothered me as well. I reasoned that while not strictly an xhr transformer it is something that should also be executed just before the request. Maybe pre-request-transformers would be a better name?

@alexanderchr I think it's fine. I just misread the code. Even though it doesn't direct manipulate the XHR, I agree that it's perfectly clear and a reasonable name.

@EisenbergEffect Looks good to me! Please verify CLA and merge at your convenience.

Verified. I will merge shortly and this will go out int he release, hopefully today.


Width always 100% for Select

No matter what value I give to width prop for select, it always adds 100% width.
I see in Select.js a width value is given twice. Is this intentional?
https://github.com/jxnblk/rebass/blob/717f0968b69d9ba9bc339cb737269373e243303d/src/Select.js#L24

I'm finding other props don't work as expected or it does not match up with the documentation. I'm using emotion in case that is part of the problem.
I'm new to Rebass, so I wanted to get clarification if this is user error. Otherwise I can make a PR.

Should be fixed in v2.3.0


Closes #1321: Add created and last_updated fields to the API

Fixes:
Closes #1321: Add created and last_updated fields to the API

Thank you for your interest in contributing, but #1321 will probably involve introducing a metadata object across the entire API, in an effort to support proposed future expansions such as #988. This will trigger a bump in the minor version, and v2.3 is still a a ways out.


Remove .mjs import workaround once fixed in Next.js

Let's remove this workaround once this issue is fixed: https://github.com/vercel/next.js/issues/17806
https://github.com/contentlayerdev/contentlayer/blob/ec26a633754c0520e2f61d70398ac4f88463692a/packages/next-contentlayer/src/index-cjs.ts#L40-L47

@schickling https://github.com/vercel/next.js/pull/58967 should already fix this I think, the workaround should no longer be required.


[sshfs][osxfuse]An unsatisfied requirement failed this build.

Thu Aug 11 08:12:49 BST 2016
This is failing to upgrade/install:
rprimus@mbp /usr/local/src % brew upgrade --all
==> Upgrading 2 outdated packages, with result:
homebrew/fuse/sshfs 2.8, youtube-dl 2016.08.10
sshfs: OsxfuseRequirement unsatisfied!

You can install with Homebrew Cask:
  brew cask install osxfuse

You can download from:
  https://osxfuse.github.io/
Error: An unsatisfied requirement failed this build.

 % brew info osxfuse
Error: No available formula with the name "osxfuse"

It appears that the osxfuse homebrew formula has been removed in favour of using the cask (due to recent duplication homebrew/cask cleanup).
Is there a way to have a cask as a dependency?

Thu Aug 11 08:43:39 BST 2016
P.S.   The following formulae all depend on osxfuse:
% ag -il osxfuse
afuse.rb
archivemount.rb
avfs.rb
bindfs.rb
btfs.rb
djmount.rb
encfs.rb
ext2fuse.rb
ext4fuse.rb
fuse-zip.rb
fuse4x.rb
gcsfuse.rb
gitfs.rb
ifuse.rb
mp3fs.rb
ntfs-3g.rb
ori.rb
rofs-filtered.rb
s3-backer.rb
s3fs.rb
securefs.rb
simple-mtpfs.rb
sshfs.rb
tup.rb
wdfs.rb
xmount.rb

The formula have the requirement :osxfuse not the dependency "osxfuse" and the Cask can satisfy the :osxfuse requirement: https://github.com/Homebrew/brew/blob/master/Library/Homebrew/requirements/osxfuse_requirement.rb#L5

Thu Aug 11 09:12:26 BST 2016
@ilovezfs Ahhhhh!!!  Thanks for the clarification.  Had only seen the depends on: in the formula (and also not fully scrutinised the error message).
Closing.

Thu Aug 11 09:17:24 BST 2016
Message should read:
Error: An unsatisfied requirement was no met.

as there was no attempt to install ('build') the cask.


Theme instructions display incorrectly

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll
What part(s) of the article would you like to see updated?
The css content of the above page is displayed as:
---
---

@import "";

which doesn't work.
The source for that page https://github.com/github/docs/blob/main/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md is correct:
---
---

@import "{{ site.theme }}";

but the site.theme is getting lost and presumably needs to be escaped to display correctly.
Additional information
No response

Thanks so much for opening this issue @davaya. You or anyone else can open a PR with a fix.

@steveward


[HW] Kivanc Bacak

Name: Kivanc Bacak
Email<EMAIL_ADDRESS>Linkedin Profile: https://tr.linkedin.com/in/kivancbacak
Attach the homework screenshots below for both step II and step III:

Nice job Kivanc, looks good. Here you go -> https://api.badgr.io/public/assertions/a3qG81q0Tg6ifsHYSFRLCg?identity__email=kivancba%40gmail.com


Update README.md

Objective
Update examples, else github will yell out errors.

Hi, @thapakazi thanks for the PR, but you can use in the action in this way:
 - name: Make config folder
    run: mkdir ~/.kube

- name: Save our cluster's authentication details
   run: >
         civo k3s config my-site --save
        --local-path ~/.kube/config -y


Exclusion of files

Sometimes I commit files with a lot of changes that shouldn't be reviewed, such as poetry.lock. Is it possible to exclude specific files?

Hi @ekosman,
thanks for bringing up that suggestion!
One design decision we made for this action is to simply use the diff numbers as shown in GitHub to calculate a size and comment. We think this makes it very transparent for the users why a certain label is chosen.
Your suggestion would break with this idea to some degree. I would rather suggest to run the action in a small workflow and use GitHubs path or path_ignore to prevent the workflow from running when certain automatically generated files are pushed.
What do you think?


Use PhoneGap for the app?

I'm about to write an app using PhoneGap. Maybe that experience will let me do this one quickly. I wonder if it's possible to get libsodium going in PhoneGap.

Sorry, this is in the wrong repository. Closing.


Updates to ssh howto guide

Is your feature request related to a problem? Please describe.
@niksirbi advised on some improvements to the ssh guide, quotes below:

I think we should advice people to skip the bastion node if they are within the SWC network already (e.g.. they have managed machines).
We should also urge people to always start an interactive job, even for "small" tasks, like creating conda environments.
Lastly, maybe we should get rid of the section on VSCode remote access? I think that may cause more harm than good.

Also potentially update the guide to take into account Richard's message:

We have found that the Remote SSH function of Visual Studio is causing these problems by
creating huge server-side loads. This has been affecting many HPC sites across the world
particularly in the last few months.
If you are using Visual Studio, please be sure to disable all extensions which are not
required on the server side. In particular, you must disable TypeScript and Javascript
Language Services in Visual Studio Code:
• Extensions button in VS Code (left toolbar)
• Search for ‘@builtin TypeScript’.
• Disable the TypeScript and Javascript Language Features extension
• Reload
Further documentation :- https://code.visualstudio.com/docs/remote/ssh

Describe the solution you'd like
\
Describe alternatives you've considered
\
Additional context
\

Thanks both Niko and Sofia for rising this issue.
Commenting on the improvements proposed:

Agree
Makes total sense. Maybe we could have a simple template for a environment creation job.
Seems reasonable, although maybe disabling the extensions as Richard suggested will be enough. How much are we (and other people in swc) ssh-ing with vscode for development necessities? It might be that this functionality solves common troubleshooting problems. I am using OOD virtual desktop on a dedicated node whenever I have similar needs.

2. Makes total sense. Maybe we could have a simple template for a environment creation job.

good idea, we could include the example commands for that.

3. Seems reasonable, although reinforcing the requirement of disabling the extensions (as Richard suggested) could be enough. How much are we (and other people in swc) ssh-ing with vscode for development necessities? It might be that this functionality solves common troubleshooting problems. I am using OOD virtual desktop on a dedicated node whenever I have similar needs.

I think the problem is that our current instructions lead to running jobs on bastion/gateway nodes, as noted by Pierre here: #62. Even if people have the correct VSCode settings, it's not a practice we should encourage. I think OOD is probably a much better solution for remote development.

Should we discard VSCode all together?
My common way of working lately is to ssh to the cluster via VScode and submit batch jobs or request interactive nodes from there. What is wrong with this approach?
Compare to a regular terminal, I find it very convenient for submitting jobs (interactive or batch) to have a terminal and a view of the file tree at the same time. Also many people are familiar with VSCode already, which lowers the entry barriers to the cluster.
Isn't it a bit excessive to actively discourage VScode because of the risk of someone sshing to a compute node? Shouldn't that be prevented in some other way? Or am I missing something?

I agree with you that developing exactly in the way you describe is very useful, and I've used the same workflow several times. I'd likely to preserve that way of working for me and others, but we have to make sure that our guide reflects best practice and we don't inadvertently over-burden hpc-gw1.


Images do not cache

I've made a web application using node.js and turbolinks: necronomicon.app, If I go back and forth in the app, you can see the icons reloading all the time and reflowing the content. Is there a way to cache them so to avoid re-downloading?

Hey @ArtemisGraphic Be sure you're not browsing with the developer tools open with the cache disabled. (see https://github.com/turbolinks/turbolinks/issues/494)

Hi dom, thank you for your reply. Unfortunately this is not a dev tools setting, I have this issue in every browser and it has been pointed out by others to me. You can check the link in your mobile browser and it will do the same.

Hi @ArtemisGraphic - Browsing through necronomicon.app testing with both Google Chrome and Firefox on MacOS and using the network tab in developer tools with "Disable Cache" unchecked, I do not see images re-downloaded when I revisiting a cached page.
Are you seeing images re-downloaded from the network tools, or are you seeing what appears to be a re-download from caching/rendering artifacts?  Can you give a specific click through scenario and describe a bit more what you are seeing?
FYI, I noticed the application loads turbolinks.js twice,
<script src="/scripts/turbolinks/dist/turbolinks.js" type="text/javascript"></script>
<script src="/scripts/howler/dist/howler.core.min.js" type="text/javascript"></script>
<script src="/scripts/turbolinks/dist/turbolinks.js" type="text/javascript"></script>

Hi @tleish, thank you very much for helping me. You're right, on chrome and firefox it does behave correctly, I was sure I've seen this problem on those browsers too, but apparently I was wrong. The problem occurs if you add the web app in the home screen, on iOS.
I've made a small video to show the problem. https://i.imgur.com/fi6uAWY.mp4
Thank you for the double script error, this is a recent edit that escaped me.

@ArtemisGraphic - is this an iOS mobile app with a web view?

@tleish - no, this is just a website (web app) added to the home screen from Safari. It's the  that removes address bar and it makes it look like a webview app.

@ArtemisGraphic - I just tested Safari on iOS 13.x, and image caching works just like the desktop.  The only items that are not cached are *.mp4 (this same behavior exists on desktop).
Here's a screenshot of the network activity of my mobile iOS Safari 13 (see: https://appletoolbox.com/use-web-inspector-debug-mobile-safari/)

If you are having problems with iOS Safari caching, I suggest you google for iOS Safari solutions.
This is not a turbolinks bug and this issue should be closed.

@tleish – The problem then may be relative to how safari handle caching on installed web apps. I thought it was some sort of incompatibility of turbolinks or a wrong configuration (hence the "Question" tag).
Thank you

I'm not seeing this on iOS Safari or installed as a homescreen webapp (running iOS 13.5.1). Feel free to post a solution if/when you find the cause of this.


Clip model size is too small

Hello, really appreciate for your great work.
https://github.com/OpenGVLab/InternVideo/blob/main/InternVideo2/multi_modality/MODEL_ZOO.md
I checked that you guys wrote "We also learn a CLIP-style InternVideo2 indicated by InternVideo2clip. It is post-pretrained from InternVideo2s2 by only preserving video and text encoders and contrastive loss." in your paper.
But I found out that this model [InternVideo2-CLIP-1B-224p-f8] in huggingface is too small, like just a few MB. And according to the right before issue I noticed that that pth file in huggingface is "add on parameter", not a full parameter.

So as i understood, there might be only clip model that post trained after stage2 right?
I want to know  how can I initialize that clip model and utilize. I want to get clip score from that model. It would be really grateful if you let me know exact way to do that. ( It is quite confusing no matter how much time i refer to your readme and demo.ipynb file.)

Thank you in advance.

For your question, we only finetuned the AttentionPool in the vision encoder for CLIP model. And the main parameters are not updated.
Please check the zero-shot evaluation code for CLIP to load the model.

Thanks for your reply. Then you mean I can use clip when at least two components get ready which are Internvideo2-s2 parameter(main parameter which has not been updated) and Internvideo2-clip(additional small parameter), right?
It would be really grateful if you let me know when are you guys going to update main parameter approximately.
I m looking forward to utilize your model to my work.
Appreciate for your great work once again. @Andy1621


Contour operator using Kind doesn't expose HTTPProxy to the Host (Docker Desktop Mac)

Hi  😃
First of all I would like to say congratz to the Contour team for all the amazing work done on Contour Project  👏 🚀
So, I'm trying Contour  using Kind on Mac OS & I'm a little bit lost ([This issue helped me] (https://github.com/projectcontour/contour-operator/issues/191))
What steps did you take and what happened:

Step 1

I created a new Kind Cluster with this config (expose ports 80/443):
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
 image: kindest/node:v1.20.7
 kubeadmConfigPatches:
 - |
   kind: InitConfiguration
   nodeRegistration:
     kubeletExtraArgs:
       node-labels: "ingress-ready=true"
 extraPortMappings:
 - containerPort: 80
   hostPort: 80
   protocol: TCP
 - containerPort: 443
   hostPort: 443
   protocol: TCP
- role: worker
 image: kindest/node:v1.20.7

Step 2

I installed Contour following the documentation & applying this steps:
// Installing operator
kubectl apply -f https://raw.githubusercontent.com/projectcontour/contour-operator/release-1.17/examples/operator/operator.yaml

// Contour CRD (Having Envoy pod in the node exposing to host)
cat <<EOF | kubectl apply -f -
apiVersion: operator.projectcontour.io/v1alpha1
kind: Contour
metadata:
  name: contour-sample
spec:
  nodePlacement:
    envoy:
      nodeSelector:
        ingress-ready: 'true'
      tolerations:
        - key: node-role.kubernetes.io/master
          operator: Equal
          effect: NoSchedule

Step 3
I installed my app (nginx hello world)

cat <<EOF | kubectl apply -f -
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: web-app
  name: web-app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: web-app
  template:
    metadata:
      labels:
        app: web-app
    spec:
      containers:
      - image: nginx:alpine
        name: nginx
---
apiVersion: v1
kind: Service
metadata:
  name: web-app-svc
  labels:
    app: web-app
spec:
  ports:
  - port: 80
    protocol: TCP
    targetPort: 80
  type: ClusterIP
  selector:
    app: web-app
---
apiVersion: projectcontour.io/v1
kind: HTTPProxy
metadata:
  labels:
    app: web-app
  name: web-app
spec:
  virtualhost:
    fqdn: foo.bar.com
  routes:
    - conditions:
      - prefix: /
      services:
        - name: web-app-svc
          port: 80

Final step 4

After setting foo.bar.com => localhost in my /etc/hosts
When I run curl, my app is not reachable
▶ curl http://foo.bar.com
curl: (52) Empty reply from server

What did you expect to happen:
curl http://foo.bar.com
Should return a code 200 with Welcome to nginx! html content
Anything else you would like to add:
It works very well using the Contour installation (at the step 2) doing the same steps:
kubectl apply -f https://projectcontour.io/quickstart/v1.17.0/contour.yaml

// patching envoy deamonset :
kubectl patch daemonsets -n projectcontour envoy -p '{"spec":{"template":{"spec":{"nodeSelector":{"ingress-ready":"true"},"tolerations":[{"key":"node-role.kubernetes.io/master","operator":"Equal","effect":"NoSchedule"}]}}}}'

I found a difference between both installation:
Contour expose pod with hostPort
// daemonset Envoy:
[...]
name: envoy
ports:
- containerPort: 8080
 hostPort: 80 <---
 name: http
 protocol: TCP
- containerPort: 8443
 hostPort: 443 <---
 name: https
 protocol: TCP
 [...]

Contour Operator doesn't implement it, so we cannot add it through contour CRD
Is this the desired behaviour?
I ask because I see in K8S doc

Don't specify a hostPort for a Pod unless it is absolutely necessary. When you bind a Pod to a hostPort, it limits the number of places the Pod can be scheduled, because each <hostIP, hostPort, protocol> combination must be unique. If you don't specify the hostIP and protocol explicitly, Kubernetes will use <IP_ADDRESS> as the default hostIP and TCP as the default protocol.

If you only need access to the port for debugging purposes, you can use the apiserver proxy or kubectl port-forward.

I tried to test with metallb as well but it's complex on MacOS 😫.
Could be nice if we can set it in Contour CRD when we need this configuration :)
Environment:

Software version: 1.20.7
Kubernetes version: (use kubectl version):v1.21.2
Kubernetes installer & version: kind v0.11.1 go1.16.4 darwin/amd64 (Docker Desktop)
OS (e.g. from /etc/os-release):macOS Big Sur 11.4

I believe we don't expose the host port option through the Operator because if you had >1 Contour, the host ports would conflict between them, given that Envoy is deployed as a daemon set.
It might be nice to support host ports as an option, particularly for folks who are only creating 1 Contour instance, but we'd have to figure out the UX if there were >1 Contours.
The other option here is to use specific NodePort values for the Envoy service (https://github.com/projectcontour/contour-operator/blob/main/api/v1alpha1/contour_types.go#L282-L302), and change your KinD config to map those pre-determined nodeport values to the host (mac) on ports 80/443. Similar idea, just uses high port values instead of 80/443 in the cluster.


BERT Embeddings trainable

Hi,
in these days I was able to apply finetuning to my own dataset starting from BERT embeddings and calculating them on the fly, as you advise in (https://github.com/google-research/bert/issues/91).
First results are not not good because I get a constant 42% on validation set. My doubt is:
are BERT input embedding "trainable"? if not, how can i do that?
thanks

all layers are trainable


fix: delete unused templates and JS and correct manifest

Delete unused templates
Issue

Link:
Summary:

How

Screenshots

References

Checklist

[ ] Tests added
[ ] Cleaned up commit history (rebase!)
[ ] Documentation added
[ ] Thought about variable and method names

Changed to draft as need to check the manifest.in and a bunch of other stuff as what's in the repo doesn't match what's in there.
Need to clarify what actually is being used...

@Louisreed @robputt could you check this one over to make sure I havent screwed anything up?


Scrobbling to youtube music not reflected in Recent History

The scrobbling code seems to be working as implemented, however nothing shows up in Recent History.
We get a 204 from /api/stats/playback:
DEBUG    2022-05-16 14:06:56,735 [1822438:YTMusicBackend-7 (_actor_loop)] mopidy_ytmusic 204 code from
'https://s.youtube.com/api/stats/playback?cl=...&docid=...&ei=...&fexp=...&ns=y│t&list=...&el=detailpage&len=643&of=-...&cpn=.&
referrer=https%3A%2F%2Fmusic.youtube.com&ver=2'

I suppose it's possible the API/mechanism changed for updating?  Are others seeing the same thing?

As far as I see it's just not implemented:
https://github.com/OzymandiasTheGreat/mopidy-ytmusic/blob/master/mopidy_ytmusic/scrobble_fe.py

@kmac - A 204 is probably what we should get back.  I've been swamped with work and haven't had a chance to look at this.  I'll see if I can soon.
@dionorgua - the pass in the function lets the function in backend.py handle it.   It's a weirdly confusing way to do it, but it's how it was done in the Google Music API that I was stealing logic from, so I left it. 😅
https://github.com/OzymandiasTheGreat/mopidy-ytmusic/blob/master/mopidy_ytmusic/backend.py#L161

Also, if I do manage to get it working again (or someone beats me to it 🙏), we should probably discuss with @sigma67 to put it in ytmusicapi instead.  There're other history manipulation functions in there already.

Very much open to a PR, this one's just flown under the radar a bit.

This should finally be fixed in 0.3.8

The CPN doesn't even matter for the player API call (just the tracking URL call). I only wrote it like this so I could get the playbackTracking object that get_song skips.  If it was added to the list of keys in get_song, then this could be much simpler like:
import random
import requests
from ytmusicapi import YTMusic

YTMAPI = YTMusic("auth.json")

videoId = "xZdj3LM5X1M"  # Lizzo - Good as Hell
song = YTMAPI.get_song(videoId)

CPNA = ("abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-_")
cpn = "".join( ( CPNA[random.randint(0, 256) & 63] for _ in range(0, 16) ) )
response = requests.get(
    song["playbackTracking"]["videostatsPlaybackUrl"]["baseUrl"],
    params={
        "ver": 2,
        "c": "WEB_REMIX",
        "cpn": cpn,
    },
    headers=YTMAPI.headers,
    proxies=YTMAPI.proxies,
)
if (response.status_code == 204):
    print("\"%s\" added to history." % song["videoDetails"]["title"]

And the correct signatureTimestamp doesn't even need to be used to get back the correct urls in playbackTracking.


update many packages

After exploring why a package deprecation kept popping up, I followed the thread to this project and noticed that it had been some time since anyone had run pnpm up --latest. I've done that and gotten pnpm test to run without complaint.
Figured there were enough changes to warrant a major semver bump. Unsure if there are other contribution guidelines or suggestions, so opening a PR for review.
Alas the original warning is still popping up, but that's further upstream...

Note that I finally found (and hopefully fixed) the initial warning that started me down this path in https://github.com/pnpm/pnpm/pull/8068
Also worth noting is that if/when this PR is accepted, https://github.com/altsalt/pnpm/blob/fd6cd2781716dd6c020474beae2f3a3da8493e6b/package.json#L23 will need to be updated to remove the forced Node16 installation (that does not work under NixOS).

Could you please review this @zkochan ? Don't want to be an annoyance, but would generally like to avoid pulling in so many outdated packages.


Fix typo "recieve"

Learn Build status updates of commit b00c1af:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/virtual-machines/maintenance-and-updates.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Looks good; thanks, @nemobis


Debian +lto build fails some unit tests

SUBJ. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015420
Indeed easy to reproduce by adding relevant flags to {CXX,C,LD}FLAGS as described here: https://wiki.debian.org/ToolChain/LTO

Preliminary, looks like more ~brittle tests we have that get "optimized" by stronger compiler. So should be easy to fix. I am looking.


Loading Large Amounts of Images in OpenSeadragon?

Problem Description
I am new to OpenSeadgragon and have been reading the API documentation to learn how to implement it within a project that I am currently working on.
To give a brief description of the project, I need to fetch display a large number of images that will be fetched from either the local drive, or via AWS, and display them within an OpenSeadragon viewport.
The issue that I am facing is that I have to fetch ~100-1000 bitmap images. This process is taking really long, around 2 mins-2.5mins, and I was wondering if there was a faster or better way of loading the images in. The way I am currently going about it is clearly not working so any help or advice would be useful.
Thanks in advance :)
The code I am currently running
Loader File
    function getTilesNew(inPath) {
        let allCompartments = []

        let images = fs.readdirSync(inPath).filter(function(file) {
            return fs.statSync(inPath+ '/' + file).isFile();
        })

        for(let image of images) {

            let imagePath = path.join(inPath, image);

            var tileSource =  {
                type: "image",
                url: imagePath,
                buildPyramid: true,
                tiles: [
                    {
                        scaleFactors: [
                            1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024,
                            2096,
                        ],
                        width: 333,
                    },
                ],
                minlevel: 8,
            }
            allCompartments.push(tileSource);
        }

        this.allCompartments = allCompartments;
        console.log("Images: ", allCompartments);
    }

The Display code
createDownholeView() {
            let viewer = this.$data.viewer = OpenSeadragon({
                id: "osd-view",
                prefixUrl: "//openseadragon.github.io/openseadragon/images/",
                showNavigator: true,
                tileSources: this.compartments,
                collectionMode: true,
                collectionRows: 1,
                collectionTileSize: 1024,
                collectionTileMargin: -0.01,
                collectionLayout: "vertical",
                autoResize: true,
                preserveImageSizeOnResize: true,

                // allow bmp's;
                setImageFormatsSupported: {
                    bmp: true,
                },

                // View Properties;
                panHorizontal: false,
                // defaultZoomLevel: 1,
                visibilityRatio: .8,
                constrainDuringPan: true,

                // Nav Options;
                navigatorId: "nav-view",
                navigatorPosition: "ABSOLUTE",
                navigatorWidth: "200px",
                navigatorHeight: "92.45vh",
            });

            // Add handlers
            this.addViewerHandlers(viewer);
            this.addNavigatorHandlers(viewer);

        }

Hi @Sharad-Patel1 - it looks like you might be rebuilding / re-creating your tiles on every load. If that's the case, it might help if you create the DZIs once and then load those instead: https://openseadragon.github.io/examples/creating-zooming-images/

In general, I recommend using developer tools -> networking tab to see how your browser deals with the requests. If you identify the browser fetching tiles one by one in sync (or just a few at the time), it is obviously limited due to the OpenSeadragon's job queue limit. If you identify your image requests to a server are taking longer, you might consider setting up CDNs. A good combination of a fast server, large job queue limit and a benevolent browser could do the trick. The problem is, browsers will complain if you fire hundreds of requests at the time.
@nein09 I don't think the loading process is blocking client-side, canvas operations are pretty fast, and you can get alsmot interactive frames even with per-pixel JS processing (see the fractal demo), the computation of a pixel value in the fractal is pretty costly, does up to 100 loops per pixel. You could try buildPyramid=false to see if it changes anything but I doubt it.
 I am afraid aggregating your images on a file-level could be problematic since they come from different sources, but as of now it is the only way to go. I recommend creating some sort of large image collections and splitting them client-side. The easiest way is to create one large image and serve it as a single tile source. Not very optimal if your data have dynamic nature, which I guess is the case.
You could also try to optimize your server, there are settings that allow you keep the connection open and avoid expensive HTTP communication. Though from my experience, allowing keep connection alive on Apache made the server hang since new incomming requests were not recognized as 'existing session' and tried to open new connections which made the server wait for old sessions timeout and the image loading was super slow.
I am planing to implement (in the future) an image job batches. It cannot be implemented in OSD for each use-case, but under certain conditions, it is doable. I am lately finding more issues with high HTTP traffic - especially HTTPS is costly. If we allowed our programmers to mount their own logic when fetching the data from the same origin / domain across different TileSources, you could simply send an array of image paths to your server via some custom protocol or extend existing ones for your needs, return a zip archive, and transfer tens of images per a request. Super efficient, although harder to do as of now.

@nein09 @Aiosa Great points!
I'd also like to add that this scenario is exactly what the DZC format is for. Perhaps we could get interest in finally adding support to OSD? https://github.com/openseadragon/openseadragon/issues/67

I thought deep zoom collections are mainly to optimize single file transfer, not multi-file access. DZI comes from times when networking was super costly, I felt the collection specs is too limiting to be used flexibly. One of my usecases would be just aggregating arbitrary files + tile positions, and processing them within a single query..

The DZC optimization is just packing the smaller levels of all of the image pyramids into single tiles so they can be transferred together. You can still position and rearrange the images all you want... You just get the low-res thumbnails for those images more efficiently. This works well because when you're zoomed out enough to see a lot of images, each image is pretty small, and therefore can be covered by one of the bulk tiles. When you zoom in to a specific image, we get those tiles individually, but that's fine because now you're just focused on that image.
Here's more info on the format:
https://learn.microsoft.com/en-us/previous-versions/windows/silverlight/dotnet-windows-silverlight/cc645077(v=vs.95)?redirectedfrom=MSDN#Collections
It's certainly not the only way to aggregate a lot of images, but it's a nice simple one and would be nice to have.

But that means storing data like this explicitly? I am not sure what's the server-side support out there and I guess not much. Forcibly storing different data within one file is not a flexible choice, and aggregation on the fly does not scale well (I've tried with vips). Instead, I modified the protocol to accept archives and sent multi tiles in a zip. Or, does the DZI response support also non-image data - like zip?


Unable to install most of the extensions

Azure Data Studio Version:1.25.1

Steps to Reproduce:
1.Ctrl+Shift+X open extension list
2.select any extension
the extension details page cannot be displayed on the right.
cannot install via the "install" button
prompt "Unable to open 'Extension: PostgreSQL': XHR failed." in the lower right corner

@aricc Are you behind a firewall or something that might be blocking the download?
Can you download the VSIX directly from this link? https://sqlopsextensions.blob.core.windows.net/extensions/postgresql/azuredatastudio-postgresql-0.2.7.vsix

@Charles-Gagnon
There is no firewall in my network environment, and I connect to the Internet through a home wireless router.
I can download this VSIX file directly through the link you provided.
In fact, when I click on an extension item in the list, the extension page will be displayed in the window on the right, but the page is automatically closed within 1 second. And the prompt message in the lower right corner appeared.

console.log
20210304T063215.zip
there's the log
thx

@Charles-Gagnon
I uploaded the logs 4 days ago, have you received it?

I did but it's still unclear exactly what the issue is - here's some more information that might help :

Are you being a proxy?
Can you reach https://raw.githubusercontent.com/microsoft/azuredatastudio/main/extensions/arc/images/extension.png through a normal web browser?
Go to Help -> Toggle Developer Tools -> Network tab and then copy any errors you see there

@Charles-Gagnon
1.I'm not
2.I can't
ping raw.githubusercontent.com , request could not find the host
ping www.githubusercontent.com , can receive the reply normally
3.network traffic can not be copied,see the attachment.

Interesting - are you behind a corporate firewall? Or is there any other reason why you don't think you'd be able to reach the raw.githubusercontent subdomain?
What error
Unfortunately there isn't really much we can do if you can't reach that subdomain since there's a number of things we pull from there- this seems to be a problem with your network configuration. You could try reaching out to the Github support to see if they're able to provide any assistance as well.

I'm closing this since we haven't heard back, let us know if you're still having this issue.


kubeadm: improve links and information around using the config file

Add link from the kubeadm-config page to the paragraphs on
using "--config" with "init" and "join".
Improve text in the the paragraphs on using "--config" with
"init" and "join".
Reword the link about the configuration file in the
create-cluster-kubeadm page.

fixes: https://github.com/kubernetes/website/issues/22885

/sig cluster-lifecycle
/kind cleanup

/lgtm

thanks @yagonobre
/assign @jimangel
PTAL for approval, thanks. (the bot suggested @kbarnard10 but not sure if she is still active).

The branch name in @neolit123's fork implies the change might be for v1.20
/hold
@neolit123 can you confirm the branch this PR should target? Feel free to unhold after clarifying.

Hi. No, the branch name is for me to track when I made a change.
/hold cancel

@sftim updated :+1:

/approve
/lgtm


feature: fire an event when plugin is loaded

Did you check the docs?

[X] I have read all the lazy docs

Is your feature request related to a problem? Please describe.
It doesn't seem like there's currently a user event that fires when a plugin gets loaded. I'm trying to keep dashboard up to date with number of plugins loaded using stats()
Describe the solution you'd like
Perhaps a LazyPluginLoaded event can be fired when plugins get loaded
Describe alternatives you've considered
I'm currently listening on the LazyVimStarted event to update the dashboard, but plugins lazily loaded during VeryLazy do not get accounted.
Additional context
No response

You can use LazyRender for that. That's the event the ui uses to update.


chore: convert repository to monorepo

Added two folders backend and frontend to contain respective nestJS and Angular project.
Added osmo-notify-frontend angular project. Added required linting setup.
Updated github actions workflow.
Updated dependabot

lets just do this
have a folder as apps
inside apps you can add api folder and dump all api related code inside that
inside apps you can add portal folder and dump all the portal code inside that

lets just do this
have a folder as apps inside apps you can add api folder and dump all api related code inside that inside apps you can add portal folder and dump all the portal code inside that

Modified the folder structure as per request.


Clean up code: reduce pollution of prototype and own properties

Working example of the code: https://friendlyanon.github.io/amiami-crawler/
I improved the feature detection as well to actually be accurate for transition related features.

This better befits a fork.


Is the repo public-ready?

Hi guys, this project looks really interesting! But there are some of ToDo's in the README.md.

We'll remove this note once we are done. Expect them to be done by June 15, 2019.

Any chance that's done? I want to try this out and extract tables in the documents I have.
Anyway, thanks for open-sourcing this project. ❤

Hey, yeah you should be able to run it.
However, note that the dataset has not been uploaded yet. I will do it soon. However, you can use the other repository (linked) to generate it. In addition to this, this repository is only made to work on the synthetic dataset on which it is trained. It won't generalize to other examples unless you have a dataset of them to train on. It is more for research purposes.
I saw you created more issues. I will reply to them soon (probably by tonight) as we get free.
And you are welcome for the repository. I'll try to resolve and reply on all the issues but I may take some time. Sorry for the delays.

Hi Shah Rukh,
thank you for open-sourcing the project! Does it mean that the results you have published in your paper were produced on the dataset, on which you have trained the model? If no, what was ratio between training and test datasets?
Best
Tatiana


The User Guide shows find command exists

Describe the bug
The User Guide shows "find command" in an example whereas it doesn't exist.

Resolve in PR #135


Decimal values are rounded to js-Number precision

Let's take the "FetchData.cshtml" example form the project template.
Modify the data type:
public class WeatherForecast
{
    ... // origin properties (not changed)
    public decimal DecimalProp { get; set; }
    public string StringDecimalProp { get { return DecimalProp.ToString(); } }
}

JSON that comes from the server to the client may look as follows:
[{
	...
	       DecimalProp:16808220559571622000
	StringDecimalProp:"16808220559571621480.16240545"
},
{
	...
	       DecimalProp:-54580.79494236794
	StringDecimalProp:"-54580.794942367938243476284644"
}...]

Thus, on the client side, WeatherForecast's "DecimalProp" property has a decimal type but the js-Number type's precision.
This behavior may be OK for the javascript processing, but in the case of Blazor, customers may expect passing server-side data and data-processing logic to the "client side" without JS-based side effects like losing precision.
Is it going to be improved in the future?
Is there any doc with Blazor's data-passing limitation?

@SteveSandersonMS We would like to port our desktop LOB applications to the web. We ordinarily work with monetary values which have 14 significant digits (12 digits to the left and 2 to the right of decimal point). Sometimes we need 4 digits to the right and I believe that big companies often need more than 12 digits to the left of decimal point. In accounting systems accuracy is critical. It is not priority now but in my opinion this problem should be solved before Blazor 1.0.

@SteveSandersonMS, for a web developer such a restriction is natural and even predictable.
However, web developers have lots of libs and frameworks.

We are researching the possibility to build not an application but a tool set for the Blazor. We already see some desktop developers' interest in using Blazor to migrate their desktop-based client applications' data and logic to the browser. Please note that their data-types can be generated by some ORM-sort tooling. And it is completely unexpected for a desktop developer that the currency counting involving decimal data implicitly loses precision.

I agree with @Andrzej-W that we can proceed working with Blazor keeping in mind that this behavior will be improved in the future.

serializing the accuracy-critical properties as strings...should be possible to configure a more advanced JSON parser to do that for you.

@JamesNK Is precision handling of decimal values something that Json.NET tries to handle?

Yes. When deserializing to a decimal (the serializer sees the property is a decimal type) then the value will be deserialized without losing precision.

Presumably precision is also preserved on serialization as well? Does Json.NET do this by serializing decimals as strings and then converting back to decimals on deserialization?

Serialization is easy - at a very simplified level it just involves calling ToString on both.


issue#176-fixed

can you share screenshot or recording??

_ No description provided. _

screenshot???

_ No description provided. _

screenshot???

..

  @mansiruhil13 this is the screenshot can you please review it and merge it

@mansiruhil13 and can you tell me how would liked it ?

but page have done some changes already, if i merge this, there may be vast change in the whole page? can you check you changes and made for the new homepage? and generate a new pr

also there was faq section added so there might be changes if i will merge this

@mansiruhil13 so can you tell me what I can do for this

@mansiruhil13 so can you tell me what I can do for this

you can make changes respective the code and create pr again with current changes


Rancher2: similiar Project Names break rancher-cli

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
create NS, and multiple Projects with same Name.
~> rancher project create project1
~> rancher project create project1

~> rancher namespace create test1
~> rancher namespace move test1 project1
FATA[0000] Multiple resources of type project found for name project1: ...

Result:
namespace can't be moved into a project if name is equal to some other project
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.1.6
Installation option (single install/HA): HA

imho creating similar named projects should be forbidden, same way as kubernetes doesn't allow 2 ns with the same name. Nobody will remember the hash/id of a project.
Also it is problematic if you are creating projects/ns via a repository, imagine following ci-script..
We also would like to create the projects idempotent, but that won't work with the current cli.
#!/bin/bash

NS_SYS="
  sys-k8-ingress-controller \
  sys-k8-node-cleanup \
  sys-logging-filebeat \
  sys-monitoring-alertmanager \
  sys-monitoring-blackbox-exporter \
  sys-monitoring-kube-metrics \
  sys-monitoring-node-exporter \
  sys-monitoring-prometheus \
  "
rancher login \
  ${RANCHER2_PROD_URL} \
  --token "${RANCHER2_PROD_CISYS_TOKEN}" \
  --context "${RANCHER2_CONTEXT}"

for ns in ${NS_SYS}; do
  sed "s/\$KUBE_NAMESPACE/$ns/g" templates/rancher2_namespace_sys.yml > manifests/$ns.yml
 rancher namespaces move $ns ck.sys
done

Unique project names means that in an installation with many clusters and thousands of users, one early random person gets (or intentionally squats on) all the "good" names like "dev" or "prod" and everyone else has to pick something else even though they have no idea who that person or department is and will probably never be a member of that project.
The CLI accepts project/cluster IDs too, which are unique.

@vincent99 Ah so projects are supposed to be global? I only saw them on the cluster-level, where the same principle would apply to namespaces. But with global projects it makes a little more sense. Thx!

A project uses a single particular cluster, but is a top-level global resource (it is not actually inside the cluster).
They are organized by cluster in the UI because that's how you logically think of that, but with the right rbac config it is theoretically possible for a user to have access to a project and the namespace(s) it is assigned without having any access to or knowledge of the cluster resource/nodes of that cluster/etc.  (That probably wouldn't work today without UI changes, but think public SaaS with large managed clusters shared by unrelated customers)