Add minimal working code examples in Experiment API docs

Summary
This change adds minimal working code examples to the API pages for Experiments,
EFSpectroscopy,
EFRabi,
StarkRamseyXYAmpScan,
FineAmplitudeCal,
FineXAmplitudeCal,
FineSXAmplitudeCal,
FineDragCal,
FineXDragCal,
FineSXDragCal,
FineFrequencyCal,
FrequencyCal,
HalfAngleCal,
RoughAmplitudeCal,
RoughXSXAmplitudeCal,
EFRoughXSXAmplitudeCal,
RoughDragCal,
RoughFrequencyCal,
QuantumVolume,
InterleavedRB,
LayerFidelity,
StandardRB,
MitigatedProcessTomography,
MitigatedStateTomography,
ProcessTomography,
StateTomography and
TomographyExperiment.
Details and comments

This PR covers many remaining experiments in issue#1238 and issue#1221.
In the API pages, the documentation for each experiment has been updated with its code example. Users are required to specify a backend in the code example. By default, backends used in the code examples, are simulators such as, SingleTransmonTestBackend() and AerSimulator(FakePerth()).

PR checklist (delete when all criteria are met)

[ ] I have added the tests to cover my changes.

Thanks for working on the documentation, @Naohnakazawa! A couple comments on your changes:

A number of these experiments were deprecated recently and we plan to remove them soon because they rely on Qiskit Pulse which is deprecated in Qiskit and which IBM plans to remove support for in a few months (announced here). We could still add the examples for now if you address the warnings that are causing the docs build to fail currently (any warning in jupyter-sphinx execution causes the overall job to be treated as a failure), but it might be better remove them from the PR to help with the second point.
I am concerned about the run time of the docs build. For the run here it was over 16 minutes. On the main branch it is around 8 minutes, which I already think is a little too long. The tests take only 3-6 minutes to run for comparison. Could you check the execution times? Perhaps some examples could use different parameters that are faster to execute. Parallelization could help the docs but it seems like jupyter-sphinx does not support it (https://github.com/jupyter/jupyter-sphinx/pull/38). I don't think we are tied to jupyter-sphinx if something else works better (Qiskit uses the matplotlib plot_directive Sphinx extension for example).

Hello, @wshanks.
Is the run time of the docs build too long? It takes 12 minutes.

The PR looks ready except one suggestion about the RB analysis names.

Is the run time of the docs build too long? It takes 12 minutes.

It feels a bit long to me, but we can can go with it for now. We will review the pulse experiments soon from the main branch to prepare for pulse being removed in Qiskit 2.0 and that will bring the time down some. It would be nice if we could log the time of each jupyter-execute run to see where all the time is going. There might be some way to do that with sphinx and jupyter-sphinx but I don't know how. We have our JupyterCellCheckEnv override but that happens in a sphinx layer before the jupyter kernel executes the code. Not knowing how to add logging to sphinx, what I would do is write a script to find all the .ipynb files under docs/_build/jupyter_execute and run jupyter execute on them and time how long each takes. If you are interested, you could write the script. It would be nice to add to the tools/ directory.

Hi, @wshanks.
The PR is now updated. Thank you for your help.

The update versions are live now on the dev version of the docs: https://qiskit-community.github.io/qiskit-experiments/dev/apidocs/library.html
I backported the PR to the stable 0.8 branch as well. I want to get #1502 merged into 0.8 and then we can release 0.8.1 and the docs changes should appear on the stable version of the docs as well. I might not be able to find anyone to review #1502 before January though.

@Naohnakazawa I wrote the script to check the jupyter execute times.


Update analytics.js

The latest version of the analytics.js support Google Optimize by specifying the optimize parameter in the settings.  However, it doesn't appear that the current okgrow/analytics build has this.
https://github.com/okgrow/analytics.js/blob/master/analytics.js#L9205

@dobesv We have just published v3.0.4 which includes an updated analytics.min.js it should include the latest version of the Google Analytics segment integration.
Let me know if this latest version has solved the optimize parameter for you.

I will give it a try when I can. Currently meteor won't let me update the
package, saying it is incompatible. So I'll have to solve that mystery
first.
On Mon, Oct 16, 2017, 12:44 PM Charles Nelson<EMAIL_ADDRESS>wrote:

@dobesv https://github.com/dobesv We have just published v3.0.4 which
includes an updated analytics.min.js it should include the latest version
of the Google Analytics segment integration
https://github.com/segment-integrations/analytics.js-integration-google-analytics
.
Let me know if this latest version has solved the optimize parameter for
you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/okgrow/analytics/issues/195#issuecomment-337013732,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUAmUdz0neCJIMd871coQo1fttuhc27ks5ss7IqgaJpZM4PxLVt
.

@dobesv There shouldn't be any incompatible changes made going from v3.03 to v3.04. The examples we have inside this repo are able to run without any issues. You could always manually set the version in .meteor/.versions and see if it runs ok. Hope your able to upgrade without any issues. 👌


[FeatureRequest] Gather sparse logprobs

Hello team,
We typically use gather_all_token_logits to collect the logit tensors for post-processing. Especially for large vocabulary sizes (128 000) this can require a lot of GPU memory. For example, when running inference loads with input and output lengths of 1024 and a batch size of 32, the collected logit tensor requires 32 GB of memory (fp32).
In vllm it is possible to collect only the topk logprobs (see here). This is much more memory efficient and would be sufficient for our purposes. Is there currently a way to do this in TensorRT-LLM as well? If not, we would really appreciate this feature in both ModelRunner and ModelRunnerCpp.
This issue is somehow related to https://github.com/NVIDIA/TensorRT-LLM/issues/1040, as it would be possible to solve it on our side if it is possible to collect arbitrary model outputs.
Thank you

@byshiue @ncomly-nvidia we figured that this feature could be implemented on our side based on a LogitsProcessor. But currently these are not supported by the ModelRunnerCpp / tensorrt_llm.bindings.GptSession:
https://github.com/NVIDIA/TensorRT-LLM/blob/71d8d4d3dc655671f32535d6d2b60cab87f36e87/tensorrt_llm/runtime/model_runner_cpp.py#L310-L312
Is there any plan to extend the support?

@Marks101, the logits processor is supported on ModelRunnerCppExecutor:
https://github.com/NVIDIA/TensorRT-LLM/blob/main/tensorrt_llm/runtime/model_runner_cpp.py#L48
Could you try that please?

Hi @MartinMarciniszyn thank you for the update. We will take a look at this 😃

@Marks101, the logits processor is supported on ModelRunnerCppExecutor: https://github.com/NVIDIA/TensorRT-LLM/blob/main/tensorrt_llm/runtime/model_runner_cpp.py#L48 Could you try that please?

Hello, it looks like logits processor is disabled here....

Thanks for the feedback @shangshng. It should be support in the Python bindings of the Executor API. @dcampora, could you please add support to ModelRunnerCpp please?
@Marks101, you can use the Executor API directly instead of going through ModelRunnerCpp for now.


How do you divide the each long sample to short samples?

I looked over your code. thank you very much for sharing the great work at first.
I know In genea there are 23 long samples (each about 10 minutes) with name like"Recording_001.***".
How do you divide the long sample into short samples( only 24 samples if not divide. it is a so small examples size)?
Thanks in advance

Thank you for your question, @chuangyu-robotics.
Every training sample is 3s (60 frames) long and the training dataset is split into 3s long segment by going through each training sequence by sliding window, resulting in several hundred thousands training speech-gesture sequence pairs.
The code we provided for the GENEA Challenge is located in the separate brunch: https://github.com/GestureGeneration/Speech_driven_gesture_generation_with_autoencoder/tree/GENEA_2020
You can see the code for it in the process_dataset.py script at this brunch on line 112 :
https://github.com/GestureGeneration/Speech_driven_gesture_generation_with_autoencoder/blob/GENEA_2020/data_processing/process_dataset.py#L112
Did I answer your question?

clear and inpoint~ great! many thanks~ have a good day~


Doing python course work - workbench issue

When working on Python programs, I got the following error during routine use. I was working on the 6th file, the 5 others did not experience this issue. I cannot load any of the files I was working in and adding new ones does not work either.
Windows 11
Chrome Version 114.0.5735.199 (Official Build) (64-bit)
An unexpected error occurred that requires a reload of this page.
The workbench failed to connect to the server (Error: connection record disposed by ConnectionHub: {
"errorMessage": "Failed to start VS Code Remote server.",
"originalErrorType": "",
"errorCode": -1,
"errorType": "GenericError",
"stack": "Error: Failed to start VS Code Remote server.\n at [CODESPACE_URL]\n at [CODESPACE_URL]\n at [CODESPACE_URL]\n at [CODESPACE_URL]\n at d ([CODESPACE_URL]\n at a ([CODESPACE_URL]"
} $1 $1)
Version: 1.80.1
Commit: 74f6148eb9ea00507ec113ec51c489d6ffb4b771
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Remove/Customize footer message.

Is your feature request related to a problem? Please describe.
Remove/Customize footer message.
Describe the solution you'd like
Remove/Customize footer message.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi Santhos - do you have an ETA on this one, we have just launched the accelerator and it works really well, i do not want to do major development changes, but would like to rename this footer, so i can take the solution into production.

Hi @mjanum currently no ETA but we are planning to pull this into our next quarter sprints.


VIT Example Performance Issue

Hi Keras team,
I came across the ViT example here. However, I found that the same performance can be achieved by simply replacing the multi-head attention layer with a simple dense layer. So I believe the example does not demonstrate the advantage of transformer based architectures. Any ideas on why this happens?
Specifically, I simply replace the create create_vit_classifier() function in the demo notebook with the following:
def create_vit_classifier():
    inputs = layers.Input(shape=input_shape)
    # Augment data.
    augmented = data_augmentation(inputs)
    # Create patches.
    patches = Patches(patch_size)(augmented)
    # Encode patches.
    encoded_patches = PatchEncoder(num_patches, projection_dim)(patches)

    for _ in range(transformer_layers):
        x1 = encoded_patches
        x2 = mlp(x1, hidden_units=[x1.shape[-1]], dropout_rate=0.1)
        x2 = layers.Add()([x1, x2])
        x3 = mlp(x2, hidden_units=transformer_units, dropout_rate=0.1)
        encoded_patches = layers.Add()([x1, x3])

    # Create a [batch_size, projection_dim] tensor.
    representation = layers.LayerNormalization(epsilon=1e-6)(encoded_patches)
    representation = layers.Flatten()(representation)
    representation = layers.Dropout(0.5)(representation)
    # Add MLP.
    features = mlp(representation, hidden_units=mlp_head_units, dropout_rate=0.5)
    # Classify outputs.
    logits = layers.Dense(num_classes)(features)
    # Create the Keras model.
    model = keras.Model(inputs=inputs, outputs=logits)
    return model

The results after training 100 epochs is:
Test accuracy: 54.93%
Test top 5 accuracy: 81.93%
Which has no material difference with the transformer model:
Test accuracy: 55.12%
Test top 5 accuracy: 82.0%

Also note that replacing MHA with dense layer makes the training 2x faster.

@sunweilunformatech , Could  you please create a PR with the changes you suggested. Thanks


Support commands: push, open, service, last

push to run locally
open to open "https://coveralls.io/repos/${token}"
service to open "https://coveralls.io/repos/${token}/service"
last to open "https://coveralls.io/repos/${token}/last_build"

make new command class or add options.

closing due to lack of community interest.


🐛 Bug Report: Error Throws after upgrade for search and backstage core

📜 Description
After performing the upgrade the following error is thrown out

👍 Expected behavior
It should not throw any errors
👎 Actual Behavior with Screenshots
N/A
👟 Reproduction steps
Upgrade backstage.github.io/upgrade-helper/?from=1.10.1&to=1.11.0 from 1.10.1 to 1.11.0 to see the changes
📃 Provide the context for the Bug.
search and catalog core brokes out
🖥 Your Environment
yarn run v1.22.15
$ /Users/roommen/Work/dx-backstage/node_modules/.bin/backstage-cli info
OS:   Darwin 22.3.0 - darwin/x64
node: v16.6.0
yarn: 1.22.15
cli:  0.22.2 (installed)
backstage:  1.11.0

Dependencies:
  @backstage/app-defaults                          1.2.0
  @backstage/backend-app-api                       0.4.0
  @backstage/backend-common                        0.15.2, 0.18.2
  @backstage/backend-dev-utils                     0.1.0
  @backstage/backend-plugin-api                    0.4.0
  @backstage/backend-tasks                         0.4.3
  @backstage/catalog-client                        1.3.1
  @backstage/catalog-model                         1.2.0
  @backstage/cli-common                            0.1.11
  @backstage/cli                                   0.22.2
  @backstage/config-loader                         1.1.8
  @backstage/config                                1.0.6
  @backstage/core-app-api                          1.5.0
  @backstage/core-components                       0.12.4
  @backstage/core-plugin-api                       1.4.0
  @backstage/errors                                1.1.4
  @backstage/eslint-plugin                         0.1.0
  @backstage/integration-aws-node                  0.1.1
  @backstage/integration-react                     1.1.10
  @backstage/integration                           1.4.2
  @backstage/plugin-api-docs                       0.9.0
  @backstage/plugin-app-backend                    0.3.42
  @backstage/plugin-auth-backend                   0.18.0
  @backstage/plugin-auth-node                      0.2.11
  @backstage/plugin-catalog-backend-module-gitlab  0.1.13
  @backstage/plugin-catalog-backend-module-ldap    0.5.9
  @backstage/plugin-catalog-backend                1.7.2
  @backstage/plugin-catalog-common                 1.0.11
  @backstage/plugin-catalog-graph                  0.2.27
  @backstage/plugin-catalog-import                 0.9.5
  @backstage/plugin-catalog-node                   1.3.3
  @backstage/plugin-catalog-react                  1.3.0
  @backstage/plugin-catalog                        1.8.0
  @backstage/plugin-circleci                       0.3.15
  @backstage/plugin-github-actions                 0.5.15
  @backstage/plugin-home                           0.4.31
  @backstage/plugin-lighthouse-common              0.1.0
  @backstage/plugin-lighthouse                     0.4.0
  @backstage/plugin-org                            0.6.5
  @backstage/plugin-permission-common              0.7.3
  @backstage/plugin-permission-node                0.7.5
  @backstage/plugin-permission-react               0.4.10
  @backstage/plugin-proxy-backend                  0.2.36
  @backstage/plugin-scaffolder-backend             1.11.0
  @backstage/plugin-scaffolder-common              1.2.5
  @backstage/plugin-scaffolder-node                0.1.0
  @backstage/plugin-scaffolder-react               1.1.0
  @backstage/plugin-scaffolder                     1.11.0
  @backstage/plugin-search-backend-module-pg       0.5.3
  @backstage/plugin-search-backend-node            1.1.3
  @backstage/plugin-search-backend                 1.2.3
  @backstage/plugin-search-common                  1.2.1
  @backstage/plugin-search-react                   1.5.0
  @backstage/plugin-search                         1.1.0
  @backstage/plugin-tech-radar                     0.6.1
  @backstage/plugin-techdocs-backend               1.5.3
  @backstage/plugin-techdocs-module-addons-contrib 1.0.10
  @backstage/plugin-techdocs-node                  1.5.0
  @backstage/plugin-techdocs-react                 1.1.3
  @backstage/plugin-techdocs                       1.5.0
  @backstage/plugin-user-settings                  0.7.0
  @backstage/release-manifests                     0.0.8
  @backstage/test-utils                            1.2.5
  @backstage/theme                                 0.2.17
  @backstage/types                                 1.0.2
  @backstage/version-bridge                        1.0.3
✨  Done in 2.13s.
➜  dx-backstage git:(tweaks) ✗

👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

@riginoommen do you have any custom search collators or are you using default settings for search?

I don't have custom search collaters and having the default configurations

Hmm ok - think this is one for @backstage/techdocs-core

@riginoommen we had the exact same issue as this and finally resolved it by upgrading to Node 18.
The search index was not being updated, but TechDocs was all browsable.
We use TechDocs publishing to an S3 Bucket with default config for collaters

Hello @riginoommen do you still see the issues? Have you tried upgrading to Node 18 which solved it for @addersuk?

THis issue is fixed after updrading but node 16 support is still required for plugin support


Not call actions of business event when its propagation was stopped

1. Why is this change necessary?
When a business event is stopped, it would only seem logical that no consequential actions are called. However, this is not the case as the registered actions are called regardless. E.g. when I stop checkout.order.placed, I do not expect the consequential action action.mail.send to be called.
2. What does this change do, exactly?
It checks, if the events propagation was stopped before calling its actions.
3. Describe each step to reproduce the issue or behaviour.

Subscribe to checkout.order.placed and stop the propagation.
Place an order.
See that mails are still sent.

4. Please link to the relevant issues (if any).
None.
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-9209
Please use this issue to track the state of your pull request.

Thank you for your contribution @jkrzefski :tada: :+1:


Homebrew-upstream Rubocop configuration causing Travis failures

https://travis-ci.org/Homebrew/homebrew-bundle/builds/443350600#L2443

57 files inspected, 711 offenses detected

This was handled by 4d7f923e779679b4525c6e9f2ea801350547fae6 when we moved from Travis to Azure and left the style check commented out.


python312Packages.publicsuffixlist: <IP_ADDRESS>41121 -> <IP_ADDRESS>41123

Changelog: https://github.com/ko-zu/psl/blob/v<IP_ADDRESS>41123-gha/CHANGES.md

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 358543

x86_64-linux

:fast_forward: 4 packages marked as broken and skipped:

python311Packages.parsedmarc
python311Packages.parsedmarc.dist
python312Packages.parsedmarc
python312Packages.parsedmarc.dist

:white_check_mark: 15 packages built:

parsedmarc
parsedmarc.dist
pretalx
pretalx.dist
pretalx.static
python311Packages.checkdmarc
python311Packages.checkdmarc.dist
python311Packages.publicsuffixlist
python311Packages.publicsuffixlist.dist
python312Packages.checkdmarc
python312Packages.checkdmarc.dist
python312Packages.publicsuffixlist
python312Packages.publicsuffixlist.dist
trustymail
trustymail.dist


FreeSurfer 7

FreeSurfer 7 has been released.
Post-LTS would be a good time to start seeing what accommodations need to be made.
TODO:

[ ] Update nipype recon-all interface to handle any changes to the expected outputs per-stage
[ ] Check the coarse parallelization workflow for validity
[ ] Validate downstream usage of FreeSurfer products is still valid, e.g., CRAS adjustments to GIFTI coordinates, mri_vol2surf invocations, etc.

Bias field correction with ANTS N4 instead of MNI N3 (removes dependency on MINC software)
ANTS denoise is used when creating the orig surface (but not thefinal surfaces)

Both Interesting!


[Suggestion] The resoucename.json file which opened by "View Properties" command is refreshed after refreshing

OS: Win10
Build Version: 202010122.1
Repro Steps:

Right click a resource group in VS Code -> Select "Edit Tags..." and "View Properties".
Open a resourcename-tags.jsonc file and a resoucename.json file.
Open the resource group in portal -> Change the tag and save it.
Right click the resource group in VS Code -> Select "Refresh"
Check the opened file.

Actual:
The resourcename-tags.jsonc file is refreshed, but the resoucename.json file is not refreshed.

Suggestion:
The resoucename.json file which opened by "View Properties" command is refreshed after refreshing.

Verified on the latest build 20201216.1, this issue also reproduces for GitHub codesapces.

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!


Force create the group id

Description of changes:

Make sure the exists a group called docker with GID 1950

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

Great! Thanks for the quick fix. It looks good to me.

this still has an issue - needs sudo right before useradd
So instead of:
sudo groupadd -fog 1950 docker && useradd --gid 1950 docker
it needs to be
sudo groupadd -fog 1950 docker && sudo useradd --gid 1950 docker


Add Mixin proposals

Source: #16
This PR adds:

Proposals for Mixins only after @include keyword

Hmmm, I don't see ability to handling nested selectors for Mixins in Less.
.mixin(@a: 1, @b) { content: @a + @b; }; .| // SimpleSelector
.mixin(@a: 1, @b) { content: @a + @b; }; .test { .|} // Declarations
.mixin(@a: 1, @b) { content: @a + @b; }; .test { .| // Nothing

@mrmlnc Thank a lot!
I had recreate the commit to merge the changes. Also I made a few (mostly cosmetic) changes.

@aeschli,
Yeap, this is good 👍. But what to do with Mixins in Less? We have three contexts and one of them does not exist in the AST.

For LESS we need to override 'parseRuleset' to detect rulesets with selectors that are valid mixin declarations and annotate the selector identifier.
On the reference side, we get MixinReference Nodes already for .abc and #abc. What is the 3rd context?

Now AST contains all Mixins in the Less file. Sorry, I was not entirely correct.
The problem is that Mixin can be called in different contexts:

SimpleSelector

.mixin() {}
.m|

Declarations

.mixin() {}
.test {
  .m|
}

Just case, not context.

.mixin() {}
.test {
  .m|
// without }


Create impscet

adding impscet.net

Hi Guys,
Any progress on this?

@fridaynightgamer Pull request merged. Thank you!


kernel_function: Clear upper bits of register

If the type in a register is smaller than the register, Rust assumes the upper bits in the register to be zero.
For example, checking a bool might happen via test edi, edi, although the type only occupies dil.

bors retry

bors retry


⚠ Bofrost.fr has degraded performance

In 0a4e24c, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1353 ms

Resolved: Bofrost.fr performance has improved in 8aee5a4 after 6 minutes.


Adds bindings for android.arch.lifecycle:extensions:1.0.0

Support Libraries Version (eg: 23.3.0):
26.1.0
Does this change any of the generated binding API's?
It only adds a new binding project for android.arch.lifecycle:extensions:1.0.0
Describe your contribution
As mentioned in https://github.com/xamarin/AndroidSupportComponents/issues/76 - being able to reference the new ViewModelProvider from Architecture Components (which can be found in android.arch.lifecycle:extensions) allows proper handling of the .NET ViewModel's lifecycle in relation to the Activity / Fragment's lifecycle (such as having the ViewModel survive during configuration changes such as screen rotation).
Please review this thoroughly as I'm coming from an iOS / Android native background development so there are changes that I might have missed some things.

@cosminstirbu,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Paused chat indicator should be less discrete

The current indicator isn't so easy to see for someone like me, sometimes I forget that chat is paused due to my mouse being hovered over it. Given the chat moves from the bottom, it doesn't make sense to have the indicator up the top.
We should either move the pause indicator down the bottom, or maybe change it to something less discrete (the latter is preferred). Maybe another setting would be good. Something like webchat would be good:

I hate to make a "+1" post, but this issue bites me almost at least once every day - I don't notice that chat is (unintentionally) paused until I think, "hey, that chat in my peripheral vision hasn't moved much".


No Raw files saved?

Where does the raw file save? I looked at the folders and couldn't find any adc.raw

Hi Abdelsha,
Did you manage to track down your issues?
They should be written into the server folder.
When the server is running it should log out that it is receiving audio data.
Thanks
Chris

Hi Chris,
No, I wasn't able to track the issue. The esp32 is connected to wifi and everything seems fine from its end. but no data is being saved in the server folder, even after setting up everything on the computer side.
Regards,
Amr

I've added some more checks to the code - the ESP32 should now ping the server every 5 seconds so you can tell if it can see the server.

I am using the esp32_audio/i2s_sampling/ folder path and then updating the wifi credentials. The folder where the check was done was a different folder. Am I using the wrong code?

do you know how to write a .wav audio file before sending it?

i have same problem
no raw file saved in server folder
i start the server at localhost:5003
I've added some more checks to the code - the ESP32 should now ping the server every 5 seconds so you can tell if it can see the server.
where is the code that ping the server??!!!


Android - Expensify - In expensify chat, #admins text is hyperlinked to production site

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.16
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Launch app
Login with new account
Tap expensify switcher
4.Tap plus icon and create a workspace
5.Open workspace chat
6.Create an expense
7.Navigate to LHN
8.Tap on expensify chat
9.Long press on #admins link
10.Note the copy to clipboard link

Expected Result:
In Expensify chat, #admins text must be hyperlinked to staging site
Actual Result:
In Expensify chat, #admins text is hyperlinked to production site instead of staging site
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/b3423ae0-a557-4ca1-893d-52bcd34440bc
View all open jobs on GitHub

@VictoriaExpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Thanks for the input @parasharrajat. Yeah you are right, this is a tricky one - I didn't quite pick up on the nuances of the issue. Since this is complex and it doesn't have an effect on our customers (since this is staging related), I don't think we should put in the effort here. I'm going to close this one out


markdown typo fixes

@ayazhafiz thanks for the review! I've fixed the conflict (which was only in a file which was removed from trunk/main since creating this PR)

I think there is a lot of good updates here. I have merged in main so hopefully it passes CI, but I am not the best person to review the Str design updates. @ayazhafiz I think you previously approved this PR, perhaps you could have another look at it?

@ayazhafiz @lukewilliamboswell I've added back the file crates/compiler/README.md. I recall removing some file which I had previously edited, after a merge from main to resolve conflicts, because it looked like it had been removed from main since my initial edits. I don't recall if this was the file or not.

Oops, it looks like I didn't sign my commits. @lukewilliamboswell and @ayazhafiz how do you feel about me force-pushing a rebased, fully signed set of commits over this one, or creating a new PR on a new branch with verifiably the same overall patch content (aside from signing)? If so, @lukewilliamboswell would you want to push your changes back atop mine, or would I just try to sign your commits as part of my rebase, maintaining your authorship?

Force-pushing a new set is fine with me, but since Luke's commits are on here I'll let him make the call

I don't mind either way. If you can make it all happen in one push then I'd suggest we do that 😄

@ayazhafiz I've created https://github.com/roc-lang/roc/pull/5272 to supersede this one. You can check equivalence after ensuring main is merged into at least this original PR (there should be no differences at that point, thus the new PR should contain the changes that you already reviewed).

Closing in favor of https://github.com/roc-lang/roc/pull/5272


[BUG] ValueError: Trying to set a tensor of shape torch.Size([276, 4096]) in "qweight" (which has shape torch.Size([256, 4096]))

Describe the bug
(slimllm_test) david@asus-ESC4000-E11:/mnt/8tb_raid/david_model/SliM-LLM/slim-llm/output$ python3 CodeLlamaV_GPTPrompt.py --n 20 --temperature 0.2 --output_dir /mnt/8tb_raid/iverilog/verilog-eval/generated_samples --output_file generatedsamples_RTLCoder_CoT.json --bench_type "Machine"
/home/david/miniconda3/envs/slimllm_test/lib/python3.10/site-packages/transformers/utils/generic.py:441: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
_torch_pytree._register_pytree_node(
/home/david/miniconda3/envs/slimllm_test/lib/python3.10/site-packages/transformers/utils/generic.py:309: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
_torch_pytree._register_pytree_node(
/home/david/miniconda3/envs/slimllm_test/lib/python3.10/site-packages/transformers/utils/generic.py:309: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
_torch_pytree._register_pytree_node(
0%| | 0/2860 [00:00<?, ?it/s]WARNING - ignoring unknown parameter in quantize_config.json: quant_method.
WARNING - ignoring unknown parameter in quantize_config.json: checkpoint_format.
WARNING - ignoring unknown parameter in quantize_config.json: qweight_heights.
INFO - The layer lm_head is not quantized.
Traceback (most recent call last):
File "/mnt/8tb_raid/david_model/SliM-LLM/slim-llm/output/CodeLlamaV_GPTPrompt.py", line 46, in
model = AutoGPTQForCausalLM.from_quantized(
File "/home/david/miniconda3/envs/slimllm_test/lib/python3.10/site-packages/auto_gptq/modeling/auto.py", line 135, in from_quantized
return quant_func(
File "/home/david/miniconda3/envs/slimllm_test/lib/python3.10/site-packages/auto_gptq/modeling/_base.py", line 1246, in from_quantized
accelerate.utils.modeling.load_checkpoint_in_model(
File "/home/david/miniconda3/envs/slimllm_test/lib/python3.10/site-packages/accelerate/utils/modeling.py", line 1550, in load_checkpoint_in_model
set_module_tensor_to_device(
File "/home/david/miniconda3/envs/slimllm_test/lib/python3.10/site-packages/accelerate/utils/modeling.py", line 310, in set_module_tensor_to_device
raise ValueError(
ValueError: Trying to set a tensor of shape torch.Size([276, 4096]) in "qweight" (which has shape torch.Size([256, 4096])), this look incorrect.
I used the quantization method from Aaronhuang-778/SliM-LLM (https://github.com/Aaronhuang-778/SliM-LLM?tab=readme-ov-file) and wanted to load and use the model with your AutoGPTQ, but encountered the issue mentioned in the title.
Hardware details
CPU:Intel(R) Xeon(R) Silver 4410Y
GPU:NVIDIA RTX A6000
Software version
Version of relevant software such as operation system, cuda toolkit, python, auto-gptq, pytorch, transformers, accelerate, etc.
operation system:
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
cuda toolkit:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Tue_Oct_29_23:50:19_PDT_2024
Cuda compilation tools, release 12.6, V12.6.85
Build cuda_12.6.r12.6/compiler.35059454_0
Python 3.10.15
Name: auto_gptq
Version: 0.7.1
pytorch:2.2.1+cu121
transformer:4.35.0
accelerate:0.26.0
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
the quantized model can be loaded

"from transformers import AutoTokenizer
from gptqmodel import GPTQModel, get_best_device
quant_path = "/mnt/8tb_raid/david_model/SliM-LLM/slim-llm/output/huggyllama_llama-7b_wikitext2_2bit_128.pt/"
tokenizer = AutoTokenizer.from_pretrained(quant_path)
model = GPTQModel.load(quant_path, device=get_best_device())
input_text = "Uncovering deep insights begins with"
input_tokens = tokenizer(input_text, return_tensors="pt").to(model.device)
result = model.generate(**input_tokens)[0]
output_text = tokenizer.decode(result, skip_special_tokens=True)
print(f"Input: {input_text}")
print(f"Output: {output_text}")"

@davidray222 We have isolated the issue. The problem is the model is quantized using a modified gptq kernel that is only applicable to this model/gptq-tookit: https://github.com/Aaronhuang-778/SliM-LLM?tab=readme-ov-file
For now, you cannot run this model on GPTQModel as we do not support per-module mixed precision quantization but we may integrate or add this feature in a future release.
If you need to run this model, you must follow the instructions and use a custom kernel/loader at the Slim-LLM repo.


Example of mocking function with post method

Which Category is your question related to?
Mocking functions
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.41.2
What AWS Services are you utilizing?
Functions
Provide additional details e.g. code snippets
This site: https://docs.amplify.aws/cli/restapi/testing#test-the-api-with-amplify-mock has an example json for GET requests but nothing for POST.
Need the correct syntax for testing POST data.
Examples:
This throws a 500 error
{
  "httpMethod": "POST",
  "path": "/test",
  "body": {
    "test": "true"
  }
}

This returns and empty req.body
{
  "httpMethod": "POST",
  "path": "/test",
  "body": "{ \"test\": \"test\" }"
}

@unclejustin The second payload you have is correct, you just need to set the content type to "application/json":
{
    "httpMethod": "POST",
    "path": "/test",
    "headers": {
        "content-type": "application/json"
     },
    "body": "{ \"test\": \"test\" }",
}

Details on the API Gateway event can be found here: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html


nodejs: add TS types generated using pbts

Generate TypeScript types
Add steps to re-generate types
Edited documentation

@gauthier-th if you could contribute some 👀 here

poke @KClough @derhuerst if anyone can contribute some 👀

Sorry for the delay, lgtm.

@isabelle-dr ready for merge as well!
cc @bdferris not sure if you were able to track down those NPM creds 😛

I did manage to dig up my credentials.  If @isabelle-dr is comfortable with it, I could add @jameslinjl as a maintainer to give you the ability to publish.  Alternatively, I could probably push a new version if needed.

I'm good with whatever @isabelle-dr is comfortable with!

Thank you all for the contribution, reviews, and help with our npm situation!
I think we need at least one MobilityData staff to be able to publish a new version of the package. So if it's relatively accessible to a nerdy product manager, I'll do this one.
If I need 4h of training to do it, then yes let's have @jameslinjl do it 😊.


Update version

New Pull Request Checklist

[ ] I have read and understood the CONTRIBUTING guide

[ ] I have read the Documentation

[ ] I have searched for a similar pull request in the project and found none

[ ] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

[ ] I have added the required tests to prove the fix/feature I am adding

[ ] I have updated the documentation (if necessary)

[ ] I have run the tests and they pass

[ ] I have run the lint and it passes (pod lib lint)

This merge request fixes / refers to the following issues: ...
Pull Request Description
...

@mkravtsov, сделал правильный фикс.

I have merged changes from the original repository. But I have merged the latest released version 3.6.0, not the current master. Please check. If this pull request is not required anymore, I will close it.


Settings/SelectBox: New option descriptions not calculated for contextview margins & overflow

Ref: #57304
The SelectBox custom drop-down calculates and manages margins for both bottom and top.  It ensures
that there is always a margin above the status bar. It's
The new option extended descriptions added into the drop-down do not get included in the calculations
and therefore the drop down can overflow into the status bar.
@JacksonKearl - let me know if you want to take this or have me pick it up.

This screenshot shows a related issue: probably a calculation issue for a number of options to show -

@roblourens
wait a minute he can't leave until he's done ;-)
But I'll take it

@roblourens
The drop-down height calculation adjustment got removed 👎
can I be assigned as reviewer for future drop-down stuff? I would've passed on calculation requirement had I known.

Sorry, that's my fault. I'll make sure to loop you in on other dropdown changes.

absolutely no sorry 's !  I was just surprised it broke.
I think there are auto assignments for issues and PR 's, can I get added that way?

@chrmarti do we have enough issues with the dropdown label to train the bot on it?

I assume this '_sticky' was meant to be removed?
looks like it maintains the drop-down open onBlur where it normally closes

	private _dropDownPosition: AnchorPosition;
	private detailsProvider: (index: number) => { details: string, isMarkdown: boolean };
	private selectionDetailsPane: HTMLElement;

	private _sticky: boolean = false; // for dev purposes only

	constructor(options: string[], selected: number, contextViewProvider: IContextViewProvider, styles: ISelectBoxStyles, selectBoxOptions?: ISelectBoxOptions) {

		this.toDispose = [];
		this._isVisible = false;
		this.selectBoxOptions = selectBoxOptions || Object.create(null);

I think we can leave it, it's useful for development. The suggest widget has the same thing, which is probably what inspired it.

Do you always want the extended descriptions at the bottom of the list, including when we flip the list above?

okay , unfortunately since the new expressions completely ignore calculations to change layout I have to figure out whatever compromise to determine flipping for the layout.  I will come up with a first pass and run it by you.
just as an aside, I'd like to mention it's a pleasure working on this stuff with you, VSC is pretty important to me and a great outlet, most importantly it's great to work with you guys.

@chrmarti do we have enough issues with the dropdown label to train the bot on it?

I included it in the last training, but it dropped out at the stage that checks the precision of the predictions for each label. I'll keep it in and eventually it will make the threshold.

@roblourens
just want to give you update, proving to be a challenge , been working most of the day on this
hopefully I can get it right tomorrow...

Hey @cleidigh how is this going? What can I do to help? Do you think we'll be able to get it in today or tomorrow?

Hi @roblourens
was just about to ping you about milestone protocol.  I finally figured out what I think is a workable solution, not my favorite, but I think we can improve later necessary.  I had to figure out a way
to create a correctly rendered description block that mirrors the description for each option.  I have the same problem originally trying to measure for the list, you can't measure what's not rendered and in the DOM .  there are some strange CSS inheritance which was causing me heartache.  I should be able to patch in the last logic and then cleanup.  If I don't get it in tonight tomorrow is still okay?  If I run into Sunday is that a problem?

I'd prefer today, tomorrow is ok, but we don't want to take any big changes after tomorrow. I can help debug if you can open a PR with what you have. I don't have any other settings issues I'm working on right now.

okay one way or the other oppose something tonight and give you a progress report.
I think I'm past the big problems.

@roblourens
here's a problem with the current approach -

if we have to flip above due to lack of available space , if the user scrolls and the size of the description changes, the context for a container anchor point does not change (no current way to change)
with the dynamic content at the bottom of the list but above the select, an increase in the description size overflows into the select below.  If we could change the anchor point and grow the container
there would not be overflow but the container would jump up and down as the user changed selection.

I think we might need to consider two options, dynamic content at top or scroll the select up and always open to the bottom.

@roblourens
see WIP PR #57653

Thanks for the PR @cleidigh
Since we are at the end of endgame week and only want to take fixes for very serious issues, I propose that we take a simpler fix for the glitchy behavior of some select boxes, and improve the layout of the select box with details next month.
I pushed a simple fix that should restore the sizing of existing select boxes outside of the settings editor - I didn't realize this affected them. And it should make the select box + details in the settings editor look fine in most cases. It's still possible to get it to overlap the status bar or detach from its anchor element but I realize we need a more sophisticated fix like in your PR...
Verification

Try custom dropdowns on Windows in the terminal, output panel, debug viewlet, anywhere else they show up. Ensure they have the correct height and don't have weird empty spaces
Try dropdowns in the settings editor, for different settings with or without enumDescriptions, and change the scroll position of the settings list and the height of the window.

Opening a new issue for the continuing work...


fw 11.1 & emunand backup

I may be the only one but when I updated to 11.1 I can no longer backup my emunand in hourglass9 v1.2
it gives an error as sd is not formatted for emunand
emunand backup: failed
how can i fix this?

If you already have A9LH switch to updated SysNAND

You don't have an emunand anymore.

so should i restore nandmin that i made on 11.0? my cfw (homebrew menu, games, luma3ds) still works. how can i resolve this. the only thing that doesn't work is my emunand backup option in hourglass9. i can make backups of my sysnand fine. i used this current guide to hack my 2ds on 10.7 then updated fine to 11.0. how can i restore emunand. thanks


Cannot use TransportMapKernel to load precomputed transition matrices

I would like to use a precomputed transition matrix of transitions between all cells at t1 to all cells at t2 to create a kernel for downstream computation of driver genes. However, the function compute_transition_matrix does not work.

Minimal reproducible example:
class HeartKernel(TransportMapKernel):
    def _compute_tmap(self, t1: Any, t2: Any, **kwargs: Any) -> Union[np.ndarray, spmatrix, AnnData]:
        print("Computing for:", t1, t2)
        return AnnData(tmat)
tmat = pd.read_csv("./path_to_file", index_col=0)
adata_subset = adata_dpis[list(tmat.index) + list(tmat.columns)].copy()
adata_subset.obs['time_num'] = adata_subset.obs['time'].cat.rename_categories({"3dpi": 2, "Ctrl": 1, "7dpi": 3})
k = HeartKernel(adata_subset, time_key='time_num')
k.compute_transition_matrix(threshold=None, last_time_point='diagonal')

Error output:
Computing for: 2 3
Computing transition matrix based on `adata.obsp['connectivities']`
    Finish (0:00:00)
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Input In [18], in <module>
      1 #set_trace()
----> 2 k.compute_transition_matrix(threshold=None, last_time_point='diagonal')

File ~/anaconda3/envs/cellrank_dev/lib/python3.8/site-packages/cellrank/kernels/_transport_map_kernel.py:199, in TransportMapKernel.compute_transition_matrix(self, threshold, self_transitions, conn_weight, conn_kwargs, **kwargs)
    196 if threshold is not None:
    197     self._threshold_transport_maps(self._tmaps, threshold=threshold, copy=False)
--> 199 self.transition_matrix = self._restich_tmaps(
    200     self._tmaps,
    201     self_transitions=self_transitions,
    202     conn_weight=conn_weight,
    203     conn_kwargs=conn_kwargs,
    204 ).X
    206 return self

File ~/anaconda3/envs/cellrank_dev/lib/python3.8/site-packages/cellrank/kernels/_base_kernel.py:552, in Kernel.transition_matrix(self, matrix)
    550 @transition_matrix.setter
    551 def transition_matrix(self, matrix: Any) -> None:
--> 552     KernelExpression.transition_matrix.fset(self, matrix)

File ~/anaconda3/envs/cellrank_dev/lib/python3.8/site-packages/cellrank/kernels/_base_kernel.py:447, in KernelExpression.transition_matrix(self, matrix)
    445     if should_norm(matrix):  # some rows are all 0s/contain invalid values
    446         n_inv = np.sum(~np.isclose(np.asarray(matrix.sum(1)).squeeze(), 1.0, rtol=1e-12))
--> 447         raise ValueError(f"Transition matrix is not row stochastic, {n_inv} rows do not sum to 1.")
    448 # fmt: on
    450 self._transition_matrix = matrix

ValueError: Transition matrix is not row stochastic, 3 rows do not sum to 1.

The error occurs in line 199 of compute_transition_matrix, while restitching the transport maps. Output suggests it is calculating a transport map, which I would really like to supply myself. Maybe I need to also supply the additional diagonal transport maps? Or explicitly set the t_2 -> t_1 part to 0?
Versions:

cellrank==1.5.1+geb182f5 scanpy==1.8.2 anndata==0.8.0 numpy==1.21.5 numba==0.55.1 scipy==1.8.0 pandas==1.4.1 pygpcca==1.0.3 scikit-learn==1.0.2 statsmodels==0.13.2 scvelo==0.2.4 pygam==0.8.0 matplotlib==3.5.1 seaborn==0.11.2

@Marius1311

Thanks for posting! To get started, please make sure you're on the latest commit on master, see my comments in #911

Updated packages to latest commit on master. Updated error message and versions in initial post.

Seems like there must be 3 all zero rows (possible due to unbalancedness?) in the transport map - would remove these.
Alternatively if you wanna keep these cells, uniform distribution could be used.

I agree, check the raw transport maps before you input them to the kernel and locate the three rows that only contain zeros.

Thanks! But I don't think there are all zero rows:
(tmat.sum(axis = 1) == 0).value_counts()

has output
False    645
dtype: int64

Also, I'm not an expert but neither the initialization nor the compute_transition_matrix command for k references tmat. So to me it looks like either it grabs tmat from the global environment, or it tries to compute a transition matrix based on something else (it claims it is computing based on 'connectivities'). Is there a way to explicitly feed in tmat?

TypeError: Can't instantiate abstract class HeartKernel with abstract methods _compute_tmap

This is by design, because it's supposed to be implemented by whoever subclasses it.

This is by design, because it's supposed to be implemented by whoever subclasses it.

Gotcha. Will continue on this when I'm back from holiday.


WIP: mesh ellipsoid in ngsimple

pygmsh->ngsimple, because pygmsh 7 #484 #489
fixes #490

This remains WIP as:

I'm not sure what licence is appropriate for scripts importing ngsimple.
ngsimple is itself described as 'work-in-progress' as so possibly not yet sufficiently stable for use in scikit-fem examples.

…and the test-container doesn't have ngsimple in it. #333


Duck typing interfaces?

Something similar to this would allow us to still have custom types for users, but still have simplicity in replication.
interface Qux {
   foo : string;
}

def baz(a : Qux){
   return a.foo;
}

https://www.typescriptlang.org/docs/handbook/interfaces.html

They could also support inheritance via a similar mechanism to Go:
interface Solid {
   Geometry;
   Volume() : number;
}


Updates to Configure Context man.section

Finish() is no longer listed in the SConf.Finish form, as it is only a context method. Same for Define().
Added entry for the CheckProg method, which is the only one of the default_tests set not listed in the manpage - it was already in the User Guide.
CheckTypeSize is listed together with CheckType for easier finding.
Slight rewording of a few methods.
Added some markup to make live links to referenced elements.
Added clarification that the CheckContext is not the same as the configure context after some recent user confusion on that point.

Doc-only change.
Signed-off-by: Mats Wichmann<EMAIL_ADDRESS>Contributor Checklist:

[ ] I have created a new test or updated the unit tests to cover the new/changed functionality.
[ ] I have updated CHANGES.txt (and read the README.rst)
[X] I have updated the appropriate documentation

Added a commit to remove all of the SConf. forms from the manpage - I can revert this commit easily if this isn't wanted.  Here's a demontration that this doesn't work.  Manpage:
SConf.CheckHeader(context, header, [include_quotes, language])

SConstruct:
env = Environment()
context = env.Configure(config_h="config.h")
rv = SConf.CheckHeader(context, "stdio.h")
print(f"CheckHeader returns {rv}")
context.Finish()

when run,
NameError: name 'SConf' is not defined:
  File "/home/mats/github/scons/exp/global-sconf/SConstruct", line 3:
    rv = SConf.CheckHeader(context, "stdio.h")

add the line from SCons import SConf and retry:
AttributeError: 'SConfBase' object has no attribute 'headerfilename':
  File "/home/mats/github/scons/exp/global-sconf/SConstruct", line 5:
    rv = SConf.CheckHeader(context, "stdio.h")
  File "/home/mats/github/scons/scripts/../SCons/SConf.py", line 1017:
    res = SCons.Conftest.CheckHeader(context, hdr_to_check, prog_prefix,
  File "/home/mats/github/scons/scripts/../SCons/Conftest.py", line 329:
    if context.headerfilename:


fix(clerk-expo,shared): Bundle shared in expo

Description

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/backend
[ ] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

!snapshot

Hey @LekoArts - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
0.31.4-snapshot.vc1e0279

@clerk/chrome-extension
0.4.11-snapshot.vc1e0279

@clerk/clerk-js
4.64.0-snapshot.vc1e0279

@clerk/clerk-expo
0.19.13-snapshot.vc1e0279

@clerk/fastify
0.6.18-snapshot.vc1e0279

gatsby-plugin-clerk
4.4.19-snapshot.vc1e0279

@clerk/nextjs
4.25.8-snapshot.vc1e0279

@clerk/clerk-react
4.27.1-snapshot.vc1e0279

@clerk/remix
3.1.1-snapshot.vc1e0279

@clerk/clerk-sdk-node
4.12.17-snapshot.vc1e0279

@clerk/shared
1.0.1-snapshot.vc1e0279

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

This is a follow-up to https://github.com/clerkinc/javascript/pull/1950 so the functionality is not new and Turborepo does not need to be considered here as these are only package.json files for compat reasons

❓ I was wondering the same thing as @panteliselef. Are we able to nest them?
We'll need to define these additional directories in two places and a nested approach will make it more manageable.

NPM Script: clean will need to account for these generated files.
Turborepo: The generated files/dirs will also need to be listed in the build task outputs.

As-is, they both only account for ./dist.
Thanks!

We're not able to nest them as we've found that Expo does not respect the exports field. Please see https://github.com/clerkinc/javascript/pull/1950 for more details.


OVDB-64: Unify SOP Labels and Hiding

After much discussion, this is a much simpler PR to replace my original proposal #404.
This renames the labels from "OpenVDB" to "VDB" and relies on the native SideFX behavior for label suffix based on sub-menu. It also adds a compile flag and an environment variable to control the hiding behavior. My current proposal is to include this in addition to an OPcustomize/pythonrc solution which could hold any more complicated logic that we need.
(#461 will need to be merged first to ensure that the tab sub-menu is correct).

@pcucka - I'd like to get this merged in as soon as possible. Could you possibly spare a few minutes to look over the changes I've made? It's not that many lines of code, so hopefully won't take too long.


bladder_cancer polling runs at wrong frequency?

The BladderCancerMainPollingEvent is currently set to run every month, but the comment directly below it states
https://github.com/UCL/TLOmodel/blob/2dff6751ab1294ef42917880dc1ddc46b167e522/src/tlo/methods/bladder_cancer.py#L638-L639
that it should be every 3 months (and that this assumption is hardwired into the paramters?).
All other cancer modules have this same piece of code and the frequency in the comment matches that assigned to the polling event - so thought we should clarify which one is correct here and update the comment accordingly!

Also related are when each cancer module has it's polling event scheduled; there is again another comment saying the polling event should begin immediately however for 3/5 cancers this is not what happens:

bladder cancer - scheduled immediately as comment suggests
breast cancer - scheduled 1 month into the simulation, so not immediately despite the comment
oesophageal cancer - comment agrees with scheduling
other adult cancers - implementation disagrees with comment
prostate cancer - implementation disagrees with comment


[hotfix][flink-annotations] Add v1.15 as the next Flink version to master

The upcoming version to be released need to exist already in master so that
when the new release branch is created from master the version of the release
is already there.
Follows: #18340

This step should be documented in the release guide and/or be automated in the release scripts.

This step should be documented in the release guide and/or be automated in the release scripts.

Thx for the remark @zentol, We have added this step to the guide already: https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release under Major Release


Usage with Redux

Can this be used with Redux instead of Facebook Flux?

I'm pretty inspired with Redux and want to create next version based on it. But i don't have any Redux experience, so still don't have any idea how to make it in 'right' way. Looks like it should be top 'container' component, but it is all know at this moment :)

This is my redux way to do it :
Action
'use strict';

import { Actions } from 'react-native-router-flux';

const actions = exports = module.exports;
exports.PUSH = 'PUSH';
exports.RESET = 'RESET';
exports.POP = 'POP';

exports.push = function push(name, data) {
  if(typeof Actions[name] == 'function') {
    Actions[name](data);
  }
  return {
    type: actions.PUSH,
    name: name,
    data: data
  }
};
exports.reset = function reset(name, data) {
  Actions.reset(name);
  return {
    type: actions.RESET,
    name: name,
    data: data
  }
};

exports.pop = function pop() {
  Actions.pop();
  return {
    type: actions.POP
  }
};

Reducer :
'use strict';

import { PUSH, RESET, POP } from '../actions/router';

var initialState = [{
  name: 'home'
}];

module.exports = function router(state = initialState, action) {
  switch (action.type) {
    case PUSH:
      return [
        ...state,
        {
          name: action.name,
          data: action.data
        }
      ];
    case RESET:
      return [{
        name: action.name,
        data: action.data
      }];
    case POP:
      var res = [...state];
      return res.filter(function (item, i) {
        return i<res.length-1
      });
    default:
      return state;
  }
};

Also see this : https://github.com/burgalon/react-native-redux-navigator

@Mokto thanks, but i want to make the component itself to use redux, without alt. i.e. replace all alt dependencies to redux ones. Looks like it should be created as 'middleware' (i'm studying redux right now)

It seems not correct to add this support for this component, because it has 'flux' in its name, so i've created separate component react-native-redux-router with Redux support, all comments are welcome! Thanks for feedback and pointing me to great Redux library :)
https://github.com/aksonov/react-native-redux-router

thanks a lot. :)
I hope I will try it soon.

Hi there,
I have a question for redux version here

Related #44. I'm going to unite both components, simplify and make it suitable for any flux/redux implementation.

It is published, looks like i have to abandon 'redux'-related version, because latest one is suitable for any flux implementation


[SYSTEMML-540] [SYSTEMML-445] Initial implementation of conv2d/maxpooling builtin functions and GPU backend

Added following built-in function: conv2d, conv2d_backward_*, maxpooling, maxpooling_backward.
Added initial version of GPU backend.
The documentation is available in docs/devdocs folder.

@mboehm7 @shirisht @dusenberrymw @bertholdreinwald Please review the PR.

thanks @niketanpansare - you certainly put a lot of effort in here. Could we please separate those PRs though? It would be great to get the new dml builtin functions in first, with tests but without new dependencies and without reuse of allocated dense arrays and other custom extensions (that do not generalize to all scenarios yet). We could discuss the other extensions as soon as we're comfortable with the baseline builtin functions.

Agreed, splitting this up would definitely facilitate easier review and discussion. :)

Sure, will do.


Main

new updates like project page and changes made in cv

new changes marge from main to main

Hi! It seems you are customizing the website. That's great to know. But these changes should not be pulled into the template's repository.

Good afternoon,
I am sorry for that; I did not do it deliberately, and please tell me how
to revert it.
I am just trying to push my new changes from my local environment to my
repository on git hub, but my new changes were not reflected on my website.
With thanks,
Habib Ullah
On Thu, Sep 14, 2023 at 9:37 PM Michele Piazzai @.***>
wrote:

Hi! It seems you are customizing the website. That's great to know. But
these changes should not be pulled into the template's repository.
—
Reply to this email directly, view it on GitHub
https://github.com/piazzai/cvless/pull/6#issuecomment-1719283821, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APP54FDOFILIE7EHF3NCQHLX2LT6VANCNFSM6AAAAAA4XJQZVU
.
You are receiving this because you authored the thread.Message ID:
@.***>

No problem! I turned down the pull requests and there is no need for further action.


Got "bundle format is ambiguous" when signing the code

I followed the Mac App Store Submission Guide to sign my code but got several errors:
sign/Electron.app/Contents/Frameworks/Electron Framework.framework/Electron Framework: bundle format is ambiguous (could be app or framework)
sign/Electron.app/Contents/Frameworks/Electron Framework.framework/: bundle format is ambiguous (could be app or framework)
sign/Electron.app: code object is not signed at all

The signing script is exactly the same as the one in the guide:
codesign --deep -fs "$APP_KEY" --entitlements child.plist "$FRAMEWORKS_PATH/Electron Framework.framework/Libraries/libnode.dylib"
codesign --deep -fs "$APP_KEY" --entitlements child.plist "$FRAMEWORKS_PATH/Electron Framework.framework/Electron Framework"
codesign --deep -fs "$APP_KEY" --entitlements child.plist "$FRAMEWORKS_PATH/Electron Framework.framework/"
codesign --deep -fs "$APP_KEY" --entitlements child.plist "$FRAMEWORKS_PATH/$APP Helper.app/"
codesign --deep -fs "$APP_KEY" --entitlements child.plist "$FRAMEWORKS_PATH/$APP Helper EH.app/"
codesign --deep -fs "$APP_KEY" --entitlements child.plist "$FRAMEWORKS_PATH/$APP Helper NP.app/"
codesign  -fs "$APP_KEY" --entitlements parent.plist "$APP_PATH"

I did some searching and found out the errors are similar with #720. However the solution provided by @reggi didn't do the trick.
My OS X version is 10.11, and I have tried Electron v0.35.2 and v0.34.2 (downloading from the releases page, electron-v0.35.2-mas-x64.zip and electron-v0.34.2-mas-x64.zip), both of which showed the same error.

The signing tool seems to behave differently on different versions of OS X, you can also try this script:
https://gist.github.com/jorangreef/27e708c67b7e6746a98a


feat(useformstate): add markSaved and other methods for manipulating multiple form fields at once

See updated comments on the prop interfaces. markSaved is useful to set all fields as clean
after saving form values to storage, so that revert() will restore those values.
Other new methods apply the existing field-level methods to multiple fields at once.
Needed for https://github.com/konveyor/crane-ui-plugin/pull/17

@gildub I'm going ahead and merge this so I can use it in my crane-ui-plugin PR, but if you have any thoughts I'd be happy to revisit it.


Az cli Delete digests by timestamp script does not work.

The az cli "Delete digests by timestamp" script on this page https://learn.microsoft.com/en-us/azure/container-registry/container-registry-delete#delete-by-manifest-digest does not work.
The problematic line is:
    | xargs -I% az acr repository delete --name $REGISTRY --image $REPOSITORY@% --yes
This operation fails with the following message:
"The requested data does not exist. "
I have replaced this line with an echo command to list the digest names to ensure the digest names are returned correctly
I've echo'd "$REPOSITORY@% " to ensure the image name is formatted correctly; it is.
I've also replaced xargs with a for loop to execute the deletion. This also returns the same error message.

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

ID: cb1b3438-58e2-cd26-3b5e-1a1717fe182f
Version Independent ID: ad41d0b4-39b1-7e24-836e-ff12d5016623
Content: Delete image resources - Azure Container Registry
Content Source: articles/container-registry/container-registry-delete.md
Service: container-registry
GitHub Login: @tejaswikolli-web
Microsoft Alias: tejaswikolli

@sdaytelefonicatechuk
Thanks for your feedback! We will investigate and update as appropriate.

@sdaytelefonicatechuk
I'm sorry to hear that you are experiencing issues with the "Delete digests by timestamp" script provided in the Azure Container Registry documentation.
The error message "The requested data does not exist" typically indicates that the specified manifest digest does not exist in the registry. This could be due to a number of reasons, such as a typo in the digest name or the digest being deleted by another process.
To troubleshoot this issue, I would recommend checking the following:
Verify that the manifest digest names returned by the az acr repository show-manifests command are correct and match the expected format. You can do this by running the command without the --query parameter to see the full output.
Check that the specified registry and repository names are correct and match the names of the registry and repository that you want to delete the digests from.
Ensure that you have the necessary permissions to delete the specified digests. You must have contributor or owner access to the registry to delete digests.
Try deleting a single digest using the az acr repository delete command with the --yes parameter to confirm that the command is working as expected. For example:
az acr repository delete --name myregistry --image myrepository@sha256:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef --yes1
If you are still experiencing issues after checking these items, please let me know and I can help you further.

Hi there, yep I've been through those troubleshooting steps hence my raising the query.

@
We are going to close this thread as resolved but if there are any further questions, I'd recommend posting your question in https://azure.microsoft.com/en-us/support/community/. We will be happy to continue the conversation.


Minor aesthetic updates

oh wait new commits get added into the PR automagically? yesssss

Looks, great. Why did you import the python3 print function in checkdependencies.py, however? I prefer to use python2 whenever possible.

because I prefer print() ¯_(ツ)_/¯
you can just replace it with print and remove that line if you want

py2 print is a go, I guess

Awesome, thanks a lot. Merging.


Added steps to install webots ros2 driver to README

Added the terminal commands for installing the Webots ROS2 driver


notes in tables

Section Number Table 34.1-1
Issue *in the optionality column there is the "Note 1 " text to indicate that a note exists for this value of optionality... Optianility value and Note text have the same format.. *
Proposed Change change the note text size or put it bold or italic or just like in table 34.1-2 put the text whithin two brakets (Note 1). the best wuold it be ti have it like it is in pdf
Priority: LOW

Fixed in branch Work-In-Progress

Fixed in branch Work-In-Progress


[INLONG-2256] SortStandalone support audit sdk.

Title Name: [INLONG-2256][Inlong-SortStandalone] SortStandalone support audit sdk.
Fixes #2256
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

Codecov Report

Merging #2261 (d3a2e01) into master (1458d28) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2261      +/-   ##
============================================
- Coverage     12.54%   12.54%   -0.01%
+ Complexity     1218     1217       -1
============================================
  Files           420      420
  Lines         36208    36208
  Branches       5674     5674
============================================
- Hits           4542     4541       -1
  Misses        30859    30859
- Partials        807      808       +1

Impacted Files
Coverage Δ

.../producer/qltystats/DefaultBrokerRcvQltyStats.java
45.31% <0.00%> (-0.40%)
:arrow_down:

Continue to review full report at Codecov.

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


Improvement: use exception handling in Swift 2.0

The library can use the Swift 2.0 try-catch mechanism to handle errors instead of the current return of a FailableOf-object.

Agreed. I'm working in progress about that.


Marques2020 Benchmarks currently fail in production and locally

This PR fixes this by adding in transpose() calls to re-align the needed dims. Not sure why this happened (@mschrimpf any idea off the top of your head? ) in the first place, but this seems to fix it, at least for the first benchmark tested, Marques2020_Schiller1976-sf_bandwidth on alexnet (previously broken with nStim error, now works correctly locally)
The benchmarks above reproduces scores from Brain-Score 1.0 on Alexnet.
TODO: Test other 21 benchmarks locally to confirm score.

The model_interface does not guarantee the order of dimensions, it only specifies which dimensions have to be there and with which coordinates. So it's possible that we swapped for instance the neuroid and presentation dimension in the model helper which still satisfies the specification. But for benchmarks like this one that do not ensure the order of dimensions and just take the values, things might have broken.
This means that a transpose() call without arguments is also not viable! You need to specify which dimensions the DataArray should be transposed to, e.g. transpose('presentation', 'neuroid')

retrigger jenkins

Merged without Jenkins tests passing, as OM still is not fully back up. Travis tests pass.


Add license headers to all files

I think this was addresed in #238

@apengwin Right. Closing this issue.


Multiple arguments to compute shader

The following code causes a DXBC compiler error when compiled with the flag -target dxbc:
[shader("compute")]
[numthreads(4, 1, 1)]
void computeMain(uniform RWStructuredBuffer<float> ioBuffer, uniform RWStructuredBuffer<float> ioBuffer2, uint3 dispatchThreadID : SV_DispatchThreadID)
{
    uint tid = dispatchThreadID.x;
    ioBuffer[tid] = 0;
    ioBuffer2[tid] = 1;
}

Specifically, compiling this code produces the error: fxc: examples/heterogeneous-hello-world/shader.slang(7,28-55): error X4509: maximum UAV register index exceeded, target has 1 slots, manual bind to slot u1 failed
The offending line in the generated HLSL code is: RWStructuredBuffer<float > entryPointParams_ioBuffer2_0 : register(u1);
Am I misunderstanding how HLSL works?  Is there another argument / parameter I should be setting to use multiple arguments to a shader?

This seems like a case where you need to specify a target "profile" that is more capable.
Rather than just a -target dxbc, you probaly also need a -profile sm_5_0 or similar to establish the supported "shader model." The big catch there is that the command-line slangc tool has rules for matching a -profile option up with the right -target option when there are more than one, but I honestly cannot remember what the ordering constraint is. I think the rule is that you want to specify a -target first, and then any -profile or other options specific to that target.

Thanks so much, that worked perfectly!  I'll read through the available documentation to try and understand why.  For reference -target cpp -target dxbc -profile sm_5_0 in that order is what worked for me.


[Addition]: interesting cheating pattern in a well planned area

Hotspot b58 Addresses
11WFj5g3ZefHHKzZbj2R4pU6RPYnaKN9uhTsk3PAcCEfwsKJqCv
112MzBeUftABQCCu7MK94wPXC5d3J4fHYBRRmThbuQR4pmVkeH3j
11zcQq87JxJxpjQBm4QQqsnzS4x9HGxaMWBgWufbiTzDWcLYR4P
Discord Handle
No response
Reason(s)
these three just examples of the 40 miners in one wallet. it is well planned the installations in a populated area, which is impossible in china with government interferences. they are probably in a helium farm and almost all miners in the same wallet 139dhL8YM6PUXtMisRkzb47xhPjuGWibAcc5X8sD4MtAt7vYS3A only witness each (see screenshots for examples).
technologically, the gamer probably can turn off some miners to avoid the detection by a visual examination. please spend a little bit more time to investigate.

Looks like this particular cluster has been dealt with.


Handle Websocket reconnection

Currently websocket connection get stopped at some point

Actually the underlying ws client should be handling re connection automatically (see https://github.com/keymetrics/kmjs-core/blob/master/src/utils/websocket.js)


add analytic gradients to multi-variate normal cholesky

Summary:
Currently the multi variate normal density does not take advantage of analytic gradients which slows down unnecessarily computations.
Description:
Add analytic gradients for more speed.
Reproducible Steps:
NA
Current Output:
All tests work:
test/unit//math/fwd/mat/prob/multi_normal_cholesky_test.cpp
test/unit//math/mix/mat/prob/multi_normal_cholesky_test.cpp
test/unit//math/rev/mat/prob/multi_normal_cholesky2_test.cpp
test/unit//math/rev/mat/prob/multi_normal_cholesky_test.cpp
test/unit//math/prim/mat/prob/multi_normal_cholesky_test.cpp
test/unit//math/prim/mat/prob/multi_normal_cholesky_log_test.cpp

Expected Output:
All tests should still work, but evaluation is faster.
Additional Information:
Provide any additional information here.
Current Version:
v2.17.0

this was merged


[Feature]: profile picture

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

In this project /profile page to add the user profile picture.
Using for the firebase.
This more User experience..

Use Case

please assign me..

Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Instead of profile pictures, can we use profile avatars which are a set of predefined images our website will provide and the user can use it as their profile image?

@sivaprasath2004  , i will implement add profile picture , in addition if their is no profile picture added ,then it will show 3d image avators . Assign me the task please

@VaibhavArora314 assign me this I understood the approach and I will implement with below example :


recyclarr list Incorrectly Parsing Season Pack (New "Release Type" Handling, Sonarr v<IP_ADDRESS>2+ only) From Guides

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
recyclarr list custom-formats sonarr
...
          - ae58039e1319178e6be73caab5c42166 # SHO
          -  # Season Pack
          - 3bc5f395426614e155e585a2f056cdf1 # Season Pack
...

The Season Pack (New "Release Type" Handling, Sonarr v<IP_ADDRESS>2+ only) CF is Guides Only (no trash_id) but is improperly parsed (I presume the special characters causes this) resulting in the -  # Season Pack list entry.
Expected Behavior
recyclarr list custom-formats sonarr
...
          - ae58039e1319178e6be73caab5c42166 # SHO
          - 3bc5f395426614e155e585a2f056cdf1 # Season Pack
...

The Season Pack (New "Release Type" Handling, Sonarr v<IP_ADDRESS>2+ only) CF is skipped in the list.
Steps To Reproduce
recyclarr list custom-formats sonarr
Environment & Versions
- Operating System: Ubuntu 22.04
- Architecture: x64
- Recyclarr Version: 6.0.1
- Recyclarr Build: linux-x64
- Sonarr Version: <IP_ADDRESS>3
- Radarr Version: <IP_ADDRESS>12

Recyclarr Log File(s)
n/a
Configuration YAML
n/a

Sonarr / Radarr Logs
No response

Excellent report. Thank you for this. This will be fixed in the next release!


Update Larsk_Juton.pl

Modified Gnasher's Head turn in to include the other possible rewards cited in Alla.  We are likely missing other items, but these were all specifically mentioned.

Missed an item - adding and will repost the pull


unify dns prefetching with additional hosts in PREFETCH_HOSTS

Description
run.sh 'prefetches' certain hosts that might no longer be resolvable after Unbound takes over.
Currently this is hardcoded to the DBHOST and REDIS_HOST. If howerver, I want to add other
docker containers to my installation (like mailman), those need to be resolved as well.
I therefore propose to add a PREFETCH_HOSTS configuration variable that should include
all 'other' hosts to prefetch.
Type of change

[ ] New feature (non-breaking change which adds functionality)

Status

[ ] Ready

Todo List

[ ] Documentation

For maximum backward compatability, PREFETCH_HOSTS could probably default to "$DBHOST $REDIS_HOST" but not mandatorily include them?
Might the variable name be misleading? It must not only cover docker-local but also organization-local hostnames. 'hosts' is the most encompassing name ;)

I am okay with the name. It does make sense


DT: add domain tag names.

Since no one knows what green, yellow, red and black mean, they should have names as well, similar to usernotes.

This is now here: #557


Added new api endpoint /api/debug/{key}

Currently, bosun collects a bunch of runtime debug and performance stats and write it back to OpenTSDB. This endpoint will expose these stats,  useful when you are not using Bosun with OpenTSDB.
At present, the endpoint only exposes notification success and failure stats but we can add any other stats in future if required.
Thanks,

@pradeepbbl  Thanks for this, can you move them to /api/health instead? Maybe just a notifications object inside the current root object with these counters.
{
   "RuleCheck": true,
   ...
   "Notifications": {
           "PostSent": 123,
           "PostFailed": 1,
           ...
    }
}

@kylebrandt thanks for the review,  made the requested changes do let me know if need any further changes.
{
  "RuleCheck": true,
  "Quiet": false,
  "UptimeSeconds": 53,
  "StartEpoch":<PHONE_NUMBER>,
  "Notifications": {
    "PostNotificationsSuccess": 0,
    "PostNotificationsFailed": 0,
    "EmailNotificationsSuccess": 0,
    "EmailNotificationsFailed": 0
  }
}

Thanks,

@pradeepbbl Not sure why the short links commit is in here, rebase on master and force push to your branch maybe?

Sorry my bad instead rebase I did a merge :(
On 19 Feb 2018 11:59 PM, "Kyle Brandt"<EMAIL_ADDRESS>wrote:

@pradeepbbl https://github.com/pradeepbbl Not sure why the short links
commit is in here, rebase on master and force push to your branch maybe?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bosun-monitor/bosun/pull/2222#issuecomment-366822377,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGjlfk6I3paUnxbM2eeBoYzf31-lK21Vks5tWfzNgaJpZM4SG6JJ
.

@kylebrandt / @captncraig  can this merge along with #2217
Thanks,


bug(MENU): Types of property 'hasBackdrop' are incompatible

Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
Definitely worked in 11.0.1, didn't check with later versions
Description
On version 13.0.2, when trying to use the Menu component, following error shows up in Terminal:

This is fixed when I add the undefined type to hasBackdrop in menu-panel.d.ts:

This is strange since hasBackdrop is already marked optional (?).
Reproduction
StackBlitz Example project doesn't build on latest version, so I couldn't reproduce it for you. You can see it working on v12: https://stackblitz.com/edit/components-issue-fau7sh?file=src%2Fapp%2Fexample-component.html.
To check locally, create a new Angular 13 project and add Angular Material to it. Use any example here: https://material.angular.io/components/menu/examples.
Expected Behavior
Code compiles and Menu works.
Actual Behavior
Code doesn't compile, Menu doesn't work.
Environment

Angular: 13.0.2
CDK/Material: 13.0.2
Browser(s): Chrome 96
Operating System (e.g. Windows, macOS, Ubuntu): macOS 11.4

Sorry, I checked my tsconfig.json and set exactOptionalPropertyTypes to false and this worked. Since this rule is not set by default, I'll close the issue.


The calculated width is incorrect

w-110 should be equal to 27.5rem

I forgot that my windi.config.ts has set width.110 to 27.6rem


Charge Defaults

Hi
I'm trying to get all list of my Contract Charge Defaults through the API, but I cannot find an endpoint for it. I know it's not directly an issue with this module, but I'm posting this question anyway in the hopes of you might know the answer.

Hi All,
I’ve been looking fort hat some time ago but the contrcat charge defaults are not exposed in either the API nor the DataWareHouse daatabaes.
From: tmidthjell<EMAIL_ADDRESS>Sent: vrijdag 18 december 2020 08:44
To: ecitsolutions/Autotask<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [ecitsolutions/Autotask] Charge Defaults (#95)
Hi
I'm trying to get all list of my Contract Charge Defaults through the API, but I cannot find an endpoint for it. I know it's not directly an issue with this module, but I'm posting this question anyway in the hopes of you might know the answer.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ecitsolutions/Autotask/issues/95, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACCALEF7AJCPDU3JLRS77MTSVMB33ANCNFSM4VAZTCDQ.

Thanks for your reply @HarryPieterse. Right before your reply I requested access to the DataWareHouse, but then thats probably pointless :(

@tmidthjell  and @HarryPieterse , here is confirmation: https://community.kaseya.com/PSA_service_desk/discussion/66841/autotask-rest-api-contract-charges-default
Here is the Feature Request: https://psa.ideas.datto.com/ideas/PSA-I-378
Please vote for it.


Release 0.9.0

Replaces #205.
This also adds a RELEASING.md file as internal documentation.

#206 and #208 have been merged in the meantime, in case you want to include more in the release.

@hannobraun branch is rebased, CHANGELOG is updated. I also noticed that the publish flag needs valid feature flags (for the pre-checks), I updated RELEASING.md accordingly.

Thanks, I'll push the release. (Then I can test whether my credentials work now 🙂)

Release is published and tagged.


[FEATURE] Talos support

Is your feature request related to a problem? Please describe.
Talos does not support longhorn due to missing iscsi support:
https://github.com/talos-systems/talos/issues/3057
Describe the solution you'd like
Other supported storage providers in talos use the nvmf protocol to overcome this issue.
Describe alternatives you've considered
I would really like to continue using longhorn, the other solutions have their our limitations like needing a seperated disk.
Additional context
With an uncertain future of k3os many users might take a look at talos.

iscsi-tools are now support via system extensions on the talos side.
Maybe the settings how longhorn communicate with the iscsi-daemon can be made configurable?
https://www.talos.dev/v1.1/kubernetes-guides/configuration/replicated-local-storage-with-openebs-jiva/

I fear it's more than just the settings.  I fear it's also that bash and other tools are used.  There's a somewhat long list of tools:

ref: https://www.talos.dev/v1.2/kubernetes-guides/configuration/replicated-local-storage-with-openebs-jiva/

Note:

The iscsiadm still needs to be executed using nsenter approach from its ancestor namespace.
We should replace all dependent binary invocations. To achieve this, we need to implement namespace entering using setns or alternatives.
We also need to replace the binary dependencies in the automation tests.

I've written a PoC to test the feasibility of the changes. And will revisit this issue later to provide a proper LEP.

I'm really looking forward to this. I've been trying out linstor, via the piraeus operator, and it just doesn't work as well as longhorn. Sure, it might theoretically be faster, and that does seem to be the case, but it's much more complex and I've not had good luck with loosing a disk during testing. My pod shouldn't be stopped when a single disk is lost. Longhorn never failed me in the past, but I have not been able to use it since I moved to Talos/Sidero.

Regression test result: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/4813/

Tests results (full):

Regression: WIP
Talos Linux: WIP

Is there any estimated time when Longhorn 1.6 can be released?

Is there any estimated time when Longhorn 1.6 can be released?

Afaik, v1.6.0 is planned to be out around the end of this year.

Test results (full/arm64):

SUSE (SLES15-SP5)

S3: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/4860/==== 1 failed, 331 passed, 17 skipped, 189 warnings in 50111.50s (13:55:11) ====

NFS: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/4861/==== 3 failed, 328 passed, 18 skipped, 188 warnings in 50321.42s (13:58:41) ====

Hi @c3y1huang,
Is this currently in a working state? I'd very much like to test it / use it prior to release of 1.6.

Hi @c3y1huang,
Is this currently in a working state? I'd very much like to test it / use it prior to release of 1.6.

The pull requests are currently under review, which means there may still be ongoing changes. I suggest to wait until the PRs are merged before testing it.

I am so excited for this!

Me as well @zimmertr

Cool so see my feature request implemented…

I really hope this will be merged soon. Otherwise I might have to look at alternatives :(

I really hope this will be merged soon. Otherwise I might have to look at alternatives :(

Same situation

If you're using Proxmox someone has recently started developing a CSI driver that works with ZFS, LVM, Local, etc. Storage types. I'm  using it  with ZFS quite happily now.

If you're using Proxmox someone has recently started developing a CSI driver that works with ZFS, LVM, Local, etc. Storage types. I'm using it with ZFS quite happily now.

I am using Nutanix AHV which is KVM under the surface so it might work? Maybe not? What is this project?

Review the hyperlinks you quoted 😉
But no, the plugin directly interacts with the Proxmox API.

@c3y1huang Any updates on the merge process?

@c3y1huang Any updates on the merge process?

The PRs will be released in the near future and planned for the upcoming 1.6.0 release.

Test results (core):

Talos (v1.5.5)

S3=== 63 passed, 1 skipped, 290 deselected, 27 warnings in 7091.03s (1:58:11) ====

NFSWIP

SUSE (SLES15-SP5)

S3: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/5232/=== 63 passed, 1 skipped, 290 deselected, 28 warnings in 6878.20s (1:54:38) ====

NFS: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/5233/========= 64 passed, 290 deselected, 28 warnings in 7014.31s (1:56:54) =========

Test result (full):

Talos (v1.5.5)

S3

= 336 passed, 18 skipped, 223 warnings in 50413.40s (14:00:13) =

NFS

WIP

SUSE (SLES15-SP5)

S3: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/5234/

= 337 passed, 17 skipped, 217 warnings in 50205.38s (13:56:45) =

NFS: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/5235/

= 336 passed, 18 skipped, 216 warnings in 50201.84s (13:56:41) =

To ensure it actually makes 1.6.0, it might be best to give the PR's a bit more pro-active attention @innobead

Hi, I am also very much interested in this. Keep up the great work!

Currently I am experimenting Longhorn with Talos v1.6.0. Somehow, patching the machine kubelet extra-mount isn't working as in v1.5.5. cc @frezbo
machine:
  kubelet:
    extraMounts:
      - destination: /var/lib/longhorn
        type: bind
        source: /var/lib/longhorn
        options:
          - bind
          - rshared
          - rw

Currently I am experimenting Longhorn with Talos v1.6.0. Somehow, patching the machine kubelet extra-mount isn't working as in Talos v1.5.5. cc @frezbo
machine:
  kubelet:
    extraMounts:
      - destination: /var/lib/longhorn
        type: bind
        source: /var/lib/longhorn
        options:
          - bind
          - rshared
          - rw

what's the error?

what's the error?

There is no error, the mount didn't seem to apply somehow.

what's the error?

There is no error, the mount didn't seem to apply somehow.

Probably check the kubelet and controller-runtime logs
talosctl logs kubelet talosctl logs controller-runtime

Probably check the kubelet and controller-runtime logs
talosctl logs kubelet talosctl logs controller-runtime

Thank you @frezbo . It appears this was a false alarm caused by a typo in my launch template.

Test result (full):

Talos (v1.6.0)

S3

= 2 failed, 341 passed, 22 skipped, 254 warnings, 1 error in 50724.13s (14:05:24) =

NFS

WIP

The 2 failed test cases seem unrelated to this feature.

test_engine_image_incompatible: Failed to pull image "longhornio/longhorn-test:version-test.7-7.5-4.1-1"

@chriscchien Please help with this. @longhorn/qa

Verified passed on master-head (longhorn-manager b2132e7) following https://github.com/longhorn/website/pull/827 to setup Talos environment, but extra config for Pod Security is also needed:
cluster:
  apiServer:
    admissionControl:
      - name: PodSecurity
        configuration:
          apiVersion: pod-security.admission.config.k8s.io/v1alpha1
          defaults:
            enforce: privileged
          kind: PodSecurityConfiguration

Longhorn can be installed successfully in the configured Talos environment. And longhorn-tests coretest has been run based on https://github.com/longhorn/longhorn-tests/pull/1501, there is no outstanding issue found.

Verified passed on master-head (longhorn-manager b2132e7) following longhorn/website#827 to setup Talos environment, but extra config for Pod Security is also needed:
cluster:
  apiServer:
    admissionControl:
      - name: PodSecurity
        configuration:
          apiVersion: pod-security.admission.config.k8s.io/v1alpha1
          defaults:
            enforce: privileged
          kind: PodSecurityConfiguration

Longhorn can be installed successfully in the configured Talos environment. And longhorn-tests coretest has been run based on longhorn/longhorn-tests#1501, there is no outstanding issue found.

Instead lowering PodSecurity for whole cluster it would be better either to label longhorn-system namespace or put it into PodSecurityConfiguration as exemption (https://kubernetes.io/docs/tasks/configure-pod-container/enforce-standards-admission-controller/#configure-the-admission-controller).

Instead lowering PodSecurity for whole cluster it would be better either to label longhorn-system namespace or put it into PodSecurityConfiguration as exemption (https://kubernetes.io/docs/tasks/configure-pod-container/enforce-standards-admission-controller/#configure-the-admission-controller).

@c3y1huang Would you like to add this to the documentation?

@c3y1huang Would you like to add this to the documentation?

Longhorn's documentation has links directing to the Talos documentation, which offers various approaches for handling this (including the namespace approach).


small improvements

I like the list of VMs ordered by name. This is the same piece of code as used on vRA web.
Networking example now returns networking data

Will check and merge shortly! Thanks!

I noticed that (according to documentation) the variable used in getResourceNetworking example should be "networking" instead of "resource"

You are right.
I tend to use networking or resourceNetworking  as the variable.
So long as its descriptive of what you are trying to do its all good.
I've got a feeling that I must have over written the getResourceNetworking file at some point because it used to be correct! :-)
I think, before I write up the reservation docs, I'll scan over the catalog scripts and docs to make sure everything is consistent.

Tested and merged :-)


Having Side Nav Items Display on Desktop, versus using Hamburger Menu

Hey Jay,
Would it be possible, in desktop view, for side nav items to display on an office's page, rather than be in the form of the hamburger menu.  From feedback I've gotten it seems that people, on a desktop, think that clicking the hamburger is weird and they just want to see the nav.  I think for tablet and phone we're fine with the hamburger, but if we could eliminate it for the desktop and just have the links show that would be preferable to people, I think.
Thanks,
Carrie

I love it, @rubillionaire - perfect! I think we're good to push this to the live site - yay!

Awesome! Its just been pushed out into the wider world of info.risd.edu. I'll go ahead and close this issue, and all of the others that got included as part of this latest push.
Thanks, @cmiller02!


feat: Smart AI assistant for Stock Market [Python, Neural networks, Web Scraping, Models]

This is an AI assistant which will analyze previous stock prices and trends and help predict future stock prices to gain profits in the stock market.
Please assign this issue to me and add the relevant labels.

This is an AI assistant which will analyze previous stock prices and trends and help predict future stock prices to gain profits in the stock market.
Please assign this issue to me and add the relevant labels.

@RoshanMhatre  go head & push only web based project
(remember : don't forget to sync fork while submitting the new PR and Attach the Screenshot of the project with PR)


Experiments screen doesn't disappear after clicking save

A user tried to make a new experiment, but when he clicked save the experiments list screen did not disappear, and the new experiment also didn't appear in the list of experiments.

With the move to a new framework (and the experiments page having been totally rewritten), this bug has become obsolete (for now). Don't hesitate to file it again though if you encounter it with the new version :)


page layout for https://kubernetes.io/ko/docs/concepts/workloads/controllers/deployment/ is broken

This is a Bug Report
Problem:
page layout is broken for this page => https://kubernetes.io/ko/docs/concepts/workloads/controllers/deployment/
currently it looks like this:

tested in the following browsers:

Microsoft Edge 44.18362.449.0
Google Chrome 81.0.4044.138

Extra information:
the reason is broken html: there is a bunch of elements that are on the same level with

, although they should be inside of it

good html (English version):

broken html (Korean version):

also, English version was broken yesterday, but today it is already fixed
Page to Update:
https://kubernetes.io/ko/docs/concepts/workloads/controllers/deployment/
/kind bug
/language ko

Fixed in https://github.com/kubernetes/website/pull/20946
/close