How to use Jarvis and LLM icon?

Here is how my chat looks (no profile pictures):

It looks like your install somehow used Jarvis.card_03.png.
How are you using Jarvis and LLM icon with text-generation-webui?

It's fairly straight forward, Jarvis is a character card, you can download it, launch the UI, go to Parameters/ Upload character/TavernAI PNG, open the character card there and click Submit.
Now you should be seeing the greeting message from Jarvis on a Chat page, and he is also available in the Parameters/Character page.
You can set your own profile picture in this section also.
As for LLM icon:

Download LLM icon
Create a shortcut for start_windows.bat
In the properties of this shortcut you can change the look of this shortcut to the LLM_Icon.ico  file.
Not sure how would it work on Mac, but I suppose it wouldn't be much different.

I just played around with that now and I see how it works.  Thank you!
Feel free to close this out, or add to the README


Shift Go Support Window to [1.21, 1.22]

Go 1.22 is released with release notes!
It is time to shift the window for go support to [1.21, 1.22].

This issue has been resolved by PR: https://github.com/notaryproject/notation-go/pull/392.
Resolving.


fix: washover for cases with 0 non_time_cols

Hey David! :wave:
Currently, if you try to add a washover for a switchback experiment where the only cluster is time, it fails with: ValueError: No group keys passed!
The test I proposed can reproduce the bug.
The solution is just to handle the case with non-grouping columns in the simplest way possible.
Let me know if you have any comments.

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

Project coverage is 97.00%. Comparing base (dc87eda) to head (ef83bad).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #158   +/-   ##
=======================================
  Coverage   97.00%   97.00%
=======================================
  Files           9        9
  Lines         900      902    +2
=======================================
+ Hits          873      875    +2
  Misses         27       27

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

Ok, updated to 0.14.0


[resolver] - feat: introduce region resolver

Description
This PR aims at introducing a "resolver" service that will be used to redirect users to the right region at login.
Note: this is an initial draft to enable @Fraggle to iterate over it. It might needs some tweaking to stitch all components together and the region selection page needs to be implemented once design is ready.
Risk
N/A
Deploy Plan
None

We def don't need next here do we?

We wanted to re-use something already in our stack...

Can we use a lower level server API similar to connectors?

...but we weren't aware / realized that we used something different for connectors.
@JulesBelveze I'll let you decide what to do from here.

Well currently the page we render is very simple (we are waiting for the design to start implementing it), but we will probably want to use some sparkle components in there. To me using next here seems kinda relevant, no? Not sure we want to introduce a new framework here

As per IRL your call :+1:
Alternatives are to have the "page" live in each region (whatever the region) and only has 1 API call in that cloud run. Added benefit is the simplicity of the cloud run.
The benefit of having the page here is that regions don't have to know each other which is nice.

Leaving as is to leverage the clusters isolation aspect. Happy to revisit later if needed 🙏🏼


Documentation to increase conntrack table size

Resolves #616.
This does not change any form of timeout. For the simple case that's probably good enough, but @fasaxc could provide good advice here.

Ok, updated with elaboration. Back to you @matthewdupre.

There is no way this broke the package build.


chore: migrate to<EMAIL_ADDRESS>

Migrates to<EMAIL_ADDRESS>which includes WebSocketServer necessary for #231 in the future.

Released: v0.15.2 🎉
This has been released in v0.15.2!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


Create log and PID file paths at server start-up (release/94)

See comments here https://github.com/Ensembl/ensembl-rest/pull/283

Got this wrong, closing


Should allowedOrigins be an array?

Why do we have something that we're just splitting on commas when we could just make it an array and be much clearer?

I think Jetty's CrossOriginFilter expects it to be a string and we just pass the config to the filter.
https://github.com/eclipse/jetty.project/blob/master/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/CrossOriginFilter.java#L54-L66

I get that, I'm wondering if we should provide nice config and assemble the string for the user rather than just blindly using the CrossOriginFilter syntax. I don't have a super strong preference, but this is one of the few places in our ecosystem where multiplicity is specified through bespoke syntax vs. doing it in a true "yaml" setup.

When we created this bundle we debated both approaches and decided to favor the native syntax to keep things simple. If you feel strongly I think it makes sense to switch to a list syntax for origins - its one of the few settings for CORS that should actually be tweaked. The CSP will still be in string form though, is that alright?
If we do make any changes here, they need to happen literally today because all Elements apps would need to upgrade.

i don't have strong feelings on this one, but i can see there being a benefit to being consistent in having them all be pass-throughs. let me know if this should be changed, i can get something published rather quickly.

I think leave as is works for me. If we end up needing to do serious CORS
config later we can. This was mostly a flag for service discovery compat
it's not a big deal. Consistent with target is probably better.
On Mon, Mar 7, 2016 at 2:55 PM Javier Campanini<EMAIL_ADDRESS>wrote:

i don't have strong feelings on this one, but i can see there being a
benefit to being consistent in having them all be pass-throughs. let me
know if this should be changed, i can get something published rather
quickly.
—
Reply to this email directly or view it on GitHub
https://github.com/palantir/dropwizard-web-security/issues/42#issuecomment-193422328
.


Normalize NULL data in database

Questions
Answers

Description?
This PR repeats the work of the PR https://github.com/PrestaShop/autoupgrade/pull/605, adding a php function call

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes #https://github.com/PrestaShop/PrestaShop/issues/33371, Fixes #https://github.com/PrestaShop/PrestaShop/issues/25996, Fixes #https://github.com/PrestaShop/PrestaShop/issues/22862, Fixes #https://github.com/PrestaShop/PrestaShop/issues/22386, Fixes #https://github.com/PrestaShop/PrestaShop/issues/22215

Sponsor company
-

How to test?
-

We should also set the default values, or it can get broken again. 👍

@Hlavtox thank you, I modified accordingly

I'm passing the subject to draft, I have to review elements on default values

One more question - do we keep the columns NULLABLE or not? 👍
@jolelievre

@Hlavtox after reflection, we cannot modify all of the columns concerned on a core patch, it would have to be done on a major version. This would result in breaking changes.
Executing these requests does not solve the problem in any way, it is simply a mitigation of the problem while waiting for v9 and a potential (real) fix.

@M0rgan01 I tested the script and it works properly.
In order not to run the whole upgrade, I copied the method into IndexController and called it with $this->update_null_values();, all queries went OK.
However, I have one improvement I think we can do. Do you think you could add this before running the query? Maybe we will re-run it for v9 and I want to avoid some missing columns that we decide to remove in the meantime.
            // Check if the table exists
            if (empty($db->executeS('SHOW TABLES LIKE "' . _DB_PREFIX_ . $tabName . '"'))) {
                continue;
            }

            // Check if the column exists
            if (empty($db->executeS('SHOW COLUMNS FROM `' . _DB_PREFIX_ . $tabName . "` WHERE Field = '" . $columnName . "'"))) {
                continue;
            }

@Hlavtox good idea, I added it, thanks

Works perfectly.
Tried adding
['webservice_account', 'dasdsadas', ''],
['dasdasd', 'dasdsadas', ''],

and they are skipped with no error. 👍


Revisit Vec wiring once the directionality / vec / binding refactors happen.

Instances of:
Vec.fill(n)(Module(new FullAdder()).io)

have to be replaced (if possible) with:
Array.fill(n)(Module(new FullAdder()).io)

since Vec wiring is now mono-connect, due to lack of direction on cloned Vec elements.
See 375e2b6a0a456c55298d82837d28986de6211ebc

I strongly doubt the mutability of the Array is actually desired so should advocate using a more appropriate Scala data structure.
Since random-indexing is highly likely, amusingly Vector is probably the best choice. To avoid confusion of Vec vs. Vector can use IndexedSeq, which is basically equivalent.

Here's a branch with a test that now fails but used to succeed:
https://github.com/ucb-bar/chisel3/tree/vec-of-modules

Ok, traced through this.
The issue seems to be that Vecs create an internal Wire, but Wire bindings are undirectioned, so the BiConnect operation gets really confused.


Update break lease API docs

Skipping CR as this is trivial fix.

The lease duration (ie lock duration) really is 15-60 seconds. What's misleading here is that the break period can be 0 to 60 (note, not infinite). So, this change isn't actually quite correct. Could you review the lease doc here and maybe copy the appropriate section for break since it looks like the lease docs maybe didn't get updated right in general?


[WFLY-8115] added testcases for jaxrs spec deployment requirements

Requested changes implemented

@rsearls Can you clone WFLY-8115 to JBEAP please and then submit an equivalent of this PR against 7.x. Then we can merge this.


Next steps has dead links

ServicePrincipal entity link should point to https://docs.microsoft.com/en-us/graph/api/resources/serviceprincipal
Application entity link should point to https://docs.microsoft.com/en-us/graph/api/resources/application

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

ID: 6c12e139-8cb6-dd6d-2e08-89d4f22c7eef
Version Independent ID: 675b5ee9-bfe6-344f-7b39-ca0e2bc18b9b
Content: Application and service principal objects in Azure Active Directory
Content Source: articles/active-directory/develop/app-objects-and-service-principals.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

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

Thanks, @jrutila . I made a pull request for approval by @CelesteDG
https://github.com/MicrosoftDocs/azure-docs-pr/pull/67789
Once approved, changes generally go live within 24 hours.

Thank you for the PR, @MarileeTurscak-MSFT
Hello @jrutila - Thank you very much for the feedback and suggestion. If you encounter any other similar situations in the future, please feel free to go ahead and make a PR by editing the public docs and making your change. We'll review and approve the PR and it would also add you as a contributor to our docs. Thank you!


extism-cli: fix build

Description of changes
Looks like the binary name has changed in one update, we forgot to adjust the postInstall script
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[X] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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.

I can fix this when using "squash" for merging.

Yes, but first you're merging something that hasn't been tested in its PR and second, you're not helping the maintainer doing a better job next time.

and second, you're not helping the maintainer doing a better job next time.

It's more time for me and the maintainer to do this chore work (me doing another review and them having to amend the commit). I expect the contributor to be smart enough to understand how to write the commit message the next time.


Added Recipe Generator #603

What does this PR do?
In this project, I developed a Recipe Generator and Suggestion App using React for the frontend, Tailwind CSS for styling, and Shadcn UI for enhanced UI components.
Related PRs and Issues

#603

Checklist

[x] I have read read the Contribution Guide
[x] If the PR changes or adds functionality, I have updated the relevant documentation

closes: #603

@sanketshinde3001, can you please unlink Issue #602?
We want to leave it open until Hacktoberfest ends

Nice job @sanketshinde3001!!!

@quest-bot loot #603


Changing paddings of mj-column in mobile view

Thanks a lot for the amazing framework. This has made making html email so much easier.

Problems I am facing:
I have made a desktop first email template in which i have used many mj-columns which is working perfectly fine in desktop view and as expected every column is taking full width in mobile view but the problem is i have given different padding to mj-column in desktop view and now it is difficult to change the padding of mj-column in mobile view using media queries.

What will be the right way to handle it?
I am still discovering mjml. please correct me if I am wrong somewhere.
Thankyou.

Wrong? Not the right word. Understandable.
About media queries: They're not supported well on many email clients.
https://www.caniemail.com/search/?s=%40media
In contrast, though don't have a link to prove it, we're told clients on desktop platforms support media queries better (not perfectly or always, but better).
So, the MJML team recommends coding mobile first.
For you, that'll mean writing the original code with paddings for mobile. Then, use media queries to change them for desktop.

Thankyou for your response @GarryFlemings
But my usecase is desktop first. I am working in editor kind of thing.
what will be the right way to achieve this from desktop to mobile?
once again Thank you.

This could go back and forth for a while. If you don't mind, could we take this discussion to Slack? The MJML Slack is https://mjml.slack.com/. If you're not signed up yet and have problems, try https://join.slack.com/t/mjml/shared_invite/zt-gqmwfwmr-kPBnfuuB7wof5httaTcXxg.
Either way, let's take the discussion to code, please. Can you send us a short snippet that demonstrates what you've tried and how it's proving difficult? The best way would be with https://mjml.io/try-it-live; once you paste code there, the URL will change and you can tell us that URL.
Seeing code might be necessary for us to be certain we answer the right question. Like you, I suspect media queries will be part of the solution. I have not tried this particular change with them; it might be ugly. Slack is better for this question; maybe someone there will have a creative solution!
As to your use case: If an overwhelming number of your users have desktop clients that don't support media queries, writing desktop first could well be your best answer; that must be your call. If you make that choice, the data I mentioned above indicates you might only be able to reach a small portion of mobile users (depending on the mix of mobile email clients in use 😀).
Many moving parts. Let's work through this a step at a time!

Yes Sure. It will be very helpful for the long run.
Thanks @GarryFlemings


How can I use the feature_extractor with wav2vec 2.0?

❓ Questions and Help
Before asking:

search the issues.
search the docs.

What is your question?
When trying to use feature_extractor, I get an error:
Traceback (most recent call last):
  File "create_data.py", line 22, in <module>
    start_split(model_path=model_path)
  File "create_data.py", line 9, in start_split
    model.load_state_dict(cp['model'])
  File "/Users/shamoon/.local/share/virtualenvs/Vec2Wav-FhgzxqaM/lib/python3.7/site-packages/fairseq/models/fairseq_model.py", line 71, in load_state_dict
    return super().load_state_dict(new_state_dict, strict)
  File "/Users/shamoon/.local/share/virtualenvs/Vec2Wav-FhgzxqaM/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1045, in load_state_dict
    self.__class__.__name__, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for Wav2VecModel:
        Missing key(s) in state_dict: "feature_extractor.conv_layers.1.2.weight", "feature_extractor.conv_layers.1.2.bias", "feature_extractor.conv_layers.2.2.weight", "feature_extractor.conv_layers.2.2.bias", "feature_extractor.conv_layers.3.2.weight", "feature_extractor.conv_layers.3.2.bias", "feature_extractor.conv_layers.4.2.weight", "feature_extractor.conv_layers.4.2.bias", "feature_extractor.conv_layers.5.2.weight", "feature_extractor.conv_layers.5.2.bias", "feature_extractor.conv_layers.6.2.weight", "feature_extractor.conv_layers.

Code
model_path = os.path.abspath("data/models/libri960_big.pt")
cp = torch.load(model_path, map_location=torch.device('cpu'))
model = Wav2VecModel.build_model(cp['args'], task=None)
model.load_state_dict(cp['model'])
model.eval()

wav_input_16khz = torch.randn(1, 512)

z = model.feature_extractor(wav_input_16khz)

What have you tried?
What's your environment?

fairseq Version (e.g., 1.0 or master): master
PyTorch Version (e.g., 1.0)
OS (e.g., Linux):
How you installed fairseq (pip, source):
Build command you used (if compiling from source):
Python version:
CUDA/cuDNN version:
GPU models and configuration:
Any other relevant information:

For what it's worth, https://stackoverflow.com/questions/54058256/runtimeerror-errors-in-loading-state-dict-for-resnet/54058284#54058284 and https://github.com/pytorch/fairseq/issues/1811 helped fix it.
Needed to change to: model.load_state_dict(cp['model'], strict=False)
I'm not sure what strict=False does though

I'm unable to reproduce this.  I ran the following code:
import torch
from fairseq.models.wav2vec import Wav2VecModel
from subprocess import check_call
import os

if not os.path.exists('wav2vec_large.pt'):
    url = 'https://dl.fbaipublicfiles.com/fairseq/wav2vec/wav2vec_large.pt'
    check_call(['wget', url])

cp = torch.load('wav2vec_large.pt')
model = Wav2VecModel.build_model(cp['args'], task=None)
model.load_state_dict(cp['model'])
model.eval()

wav_input_16khz = torch.randn(1,10000)
z = model.feature_extractor(wav_input_16khz)
c = model.feature_aggregator(z)

Can you post a reproducible example?  The strict=False tells pytorch to not throw an exception if the keys don't match up properly.


Subdirectory names get dropped

What version of the package or command are you using?
arc v3.3.2 c7eae9dcbcb1f0a0ce965184868097babf73d415 (2020-09-29T18:23:13Z)
What are you trying to do?
create an archive of a file multiple directories deep
What steps did you take?
arc archive test.tar.gz mobile/vendor/bundle
the only file is mobile/vendor/bundle/file.txt
What did you expect to happen, and what actually happened instead?
expected test.tar.gz to contain mobile/vendor/bundle/file.txt
actually contained bundle/file.txt
How do you think this should be fixed?
should match tar cli behaviour. tar czf test.tar.gz mobile/vendor/bundle creates the archive i expect and extracts to mobile/vendor/bundle/file.txt instead of just bundle/file.txt

@frankh Thanks for the report. This seems like a bug to me that should get fixed.
@mholt Can you confirm that this should be a fix in v3.x, or should this sort of change in behavior cause a bump to v4? And was this intended?

Hmmm I think this is intentional: you're specifying a folder by name, the "bundle" folder -- the fact that it happens to be nested in two directories relative to the current path is irrelevant. In other words, it's intentional that the current environment including path is irrelevant to archiving specified files. The structure within the specified folders is all that matters.
I am not sure how to express mappings from file inputs to archival paths in the CLI.

Ah, I see. So archiver always operates as if it has the equivalent of tars -C.
I think that's different from the common convention of how most other archive programs work, and it does make it difficult to specify a parent directory structure, but I can see how the existing behavior is rational.

I always thought tar was confusing. Why does my current path make any difference as to how the archive is made? That's tedious. Just archive the files I specify.
IMO the simplest and most straightforward way to craft a custom archive structure is to literally just craft the structure on disk, then archive that folder.

I think it's because on a traditional Unix system you want to unpack things in a particular "FHS" style.
Anyway: Tomato, potato.
archiver is not tar. Closed.

Hi @mholt

Why does my current path make any difference as to how the archive is made?

the simplest and most straightforward way to craft a custom archive structure is to literally just craft the structure on disk, then archive that folder, rather than trying to map each file to a destination path.
You might not want to archive every subdirectory within your crafted structure. So you might specify a more deeply nested directory but want to preserve higher directories (maybe even up to the file system root) for restoring the files later on.

An example:
Imagine you are storing files in /home/rico/project/ and within that directory you have the following structure:
project/
├── huge_files
├── images
├── src
└── tmp

Now I'd prefer to get an archive file with the contents of src and images and avoid adding the tmp and "huge" files to my archive, because that's not what I need in this case. On the other hand I still want to preserve the directory structure to know "where it belongs to". Maybe I have several projects all having a "src" folder. Knowing by the archive paths where which archive belongs to is quite helpful. The final archive would contain the following paths & files:
/home/rico/project/src/<files>
/home/rico/project/images/<files>

To me that issue is quite bigger that what the original poster wrote, so I created an extra issue for it (#262).

#302, a complete rewrite for the upcoming v4 tag, will let you specify exact file paths you want for each file in your archive.


Command 'az aks nodepool show' does not show podSubnetID

Description
When running the command az aks nodepool show it does not return the podSubnetID information, and looking at the AKS REST API it should be available.
To Reproduce
Must create a node pool with the --vnet-subnet-id and --pod-subnet-id parameters.
 Reference and support levels: https://aka.ms/CLI_refstatus
You already have the latest azure-cli version: 2.39.0
Upgrading extensions
Checking update for aks-preview
Latest version of 'aks-preview' is already installed.

$ az version
{
  "azure-cli": "2.39.0",
  "azure-cli-core": "2.39.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {
    "aks-preview": "0.5.93"
  }
}

route to CXP team


Set correct SELinux label on restored containers

Restoring a container from a checkpoint archive mounted the container's root file-system with a new SELinux mountlabel which resulted in a container running with a different label then the root file-system.
This tells the storage setup to use the mountlabel which is stored in the checkpoint archive.
The easiest way to reproduce this bug is to run 'podman exec' on a restored container.
This also includes a new checkpoint/restore test case doing a 'podman exec' after 'podman container restore'. Unfortunately the test does not trigger the error as the tests running under ginkgo are not under the same SELinux confinement as the actual containers. At least that is how understand it.

/approve

@adrianreber please run make validate locally and --amend -s

Can this be merged? I have a two open PRs which depend on this and two more locally I am waiting to publish based on this.

/lgtm


feat(Drag And Drop): Drag&drop support in grid layout

Feature Description
We are developing using Angular CDK Drag&Drop function. I'm trying to adjust the order of card components through drag drop in a grid layout with flex applied, but it doesn't work properly in the latest version.
It is possible in the old version, so the example below works, but it doesn't seem to work properly in the latest version. Right now it seems that drag&drop is only possible horizontally or vertically.
https://stackblitz.com/edit/angular-dragdrop-grid-pnyded
There may be a way to use a separate external library, but I think it would be best to officially support it in angular.
https://stackblitz.com/edit/angular-ivy-wsegkg
Another solution seems to be this way.
https://stackblitz.com/edit/angular-qaxshp
Use Case
No response

This should be covered by https://github.com/angular/components/issues/13372.


Upgrade to Docsy 0.5.1 via NPM module

Fixes #48807
Contributes to:

#41171
#44002

Upgrades to Docsy 0.5.1 as an NPM module.

Fetches FontAwesome and Bootstrap via NPM, so I believe (if I understand the intent) that this
fixes #32905
Upgrades FontAwesome to v6, and so upgrades all icon names, and so
fixes #48811

Drops the git submodule reference to Docsy 0.3.0
Ensures that container commands continue to work
Updates the makefile
Switches to using template "partials/page-description.html" to generate HTML header page meta descriptions. (This template has continued to be improved, with the most recent update being made in Docsy 0.11.0.)
Drops the static Bootstrap resources, keeping the one needed by the API pages.

Also addresses and closes the following:

Fixes #48806$ curl -s https://deploy-preview-48812--kubernetes-io-main-staging.netlify.app/ | tr '<' '\n' | grep -i '^script' | grep -i 'jquery'
script src="/js/jquery-3.6.0.min.js" intregrity="sha384-vtXRMe3mGCbOeY7l30aIg8H9p3GdeSe4IFlP6G8JMa7o7lXvnz3GFKzPxzJdPfGK" crossorigin="anonymous">

Fixes #48808
Fixes #48813

Previews

https://deploy-preview-48812--kubernetes-io-main-staging.netlify.app/ - e.g., check the footer
https://deploy-preview-48812--kubernetes-io-main-staging.netlify.app/docs/concepts/windows/ for the page-meta icons, including the 3rd-party one
https://deploy-preview-48812--kubernetes-io-main-staging.netlify.app/docs/concepts/configuration/configmap/#using-configmaps-as-environment-variables - for code-blocks, including named ones with a copy-code button, as well as tooltips
https://deploy-preview-48812--kubernetes-io-main-staging.netlify.app/docs/tasks/tools/install-kubectl-linux/#install-kubectl-binary-with-curl-on-linux for tabbed panes, e.g.:

https://deploy-preview-48812--kubernetes-io-main-staging.netlify.app/docs/contribute/docs/#getting-started for Mermaid diagrams

Checks I've done
I've checked that the following render correctly, feel free to double check:

Icons (now that we're using FA v6) render properly in the

Footer
Doc pages, page-meta-links section
Blog pages, page-meta and other links
More rarely used icons like the third-party icon (in page-meta), for example see Concepts > Windows

Mermaid diagrams continue to render correctly
Tooltips are still working, demonstrating that the new way to fetch and use Bootstrap CSS and JS is working
Code-blocks and figures render correctly

Followup changes
This PR makes minimal changes. Consider following up with updates to:

API reference generation code to catch up to the FontAwesome & Bootstrap versions now used by the rest of the website (via Docsy).
Dockerfile, to switch to docker.io/library/debian:bookworm as @sftim proposed in #48722
#48814
Btw, stylistically, I think that we should drop the border on the .mermaid class

Try running mv node_modules node_modules_moved_aside before trying a local preview in a container. That should show up the snags, if there are any.

Hope this is OK
/retitle [WIP] Upgrade to Docsy 0.5.1 via NPM module

@sftim wrote via https://github.com/kubernetes/website/issues/48811#issuecomment-2495582965:

You won't like this @chalin but the <i class="fa fa-icon-circle fa-fw"></i> was a bodge to get a correctly-indented second line with no icon.
That's the original presentation intent, so bear that in mind when considering what we'd like to preserve…

Yes, here's the fix I propose: https://github.com/kubernetes/website/pull/48812/commits/a65258e1e561d468f33ee1b8580585a7bf6c8756. It looks like this:

which you can see via https://deploy-preview-48812--kubernetes-io-main-staging.netlify.app/docs/concepts/windows/.

Hope this is OK /retitle [WIP] Upgrade to Docsy 0.5.1 via NPM module

@sftim - with the latest changes, this is ready for reivew -- and so not WIP. The Docker & build script issues being orthogonal to the Docsy upgrade.

If this breaks local previewing in a container, we can't merge it.

@sftim - no, the simple change to the Docker file in this PR does not introduce any further breakages to local containerized build that might not have been there before.
Thanks @Okabe-Junya.
All: anything further to be done here?

If you don't run npm first, the effect of this PR is to break container previewing (you never previously had to run npm).
Error: command error: failed to load modules: module "docsy" not found in "/src/node_modules/docsy"; either add it as a Hugo Module or store it in "/src/node_modules".: module does not exist

Try running mv node_modules node_modules_moved_aside before trying a local preview in a container.  Sorry for having missed that earlier. I'm looking into a solution.

@sftim @nate-double-u et al. - I've had to restore the containerized call to npm ci that was removed via #48741. Now both containerized build and serve will run npm ci (within the container) before building and serving respectively. PTAL
$ rm -Rf node_modules
$ make container-build
mkdir -p node_modules
"docker" run --rm --interactive --tty ... npm ci
npm warn deprecated<EMAIL_ADDRESS>...
Run `npm audit` for details.
mkdir -p public
"docker" run --rm --interactive --tty ... \
                hugo --cleanDestinationDir --buildDrafts --buildFuture --environment preview --noBuildLock
Start building sites …
hugo v0.133.0+extended linux/amd64 BuildDate=unknown

                   |  EN  | BN  | ZH-CN | FR  | DE  | HI  | ID  | IT  | JA  | KO  | PL  | PT-BR | RU  | ES  | UK  | VI
-------------------+------+-----+-------+-----+-----+-----+-----+-----+-----+-----+-----+-------+-----+-----+-----+------
  Pages            | 2240 | 236 |  1835 | 380 | 210 | 136 | 337 |  92 | 579 | 617 |  71 |   367 | 195 | 319 |  95 |  79
  Paginator pages  |   61 |   0 |    23 |   0 |   0 |   0 |   0 |   0 |   2 |   0 |   0 |     0 |   0 |   0 |   0 |   0
  Non-page files   |  737 | 603 |   616 |  84 |  83 |  75 |  80 |  40 | 527 |  86 |  74 |    86 |  80 |  83 |  82 |  75
  Static files     |  829 | 829 |   829 | 829 | 829 | 829 | 829 | 829 | 829 | 829 | 829 |   829 | 829 | 829 | 829 | 829
  Processed images |   14 |   0 |     1 |   0 |   0 |   0 |   0 |   0 |   0 |   0 |   0 |     0 |   0 |   0 |   0 |   0
  Aliases          |    8 |   1 |     6 |   2 |   1 |   0 |   1 |   1 |   3 |   3 |   0 |     3 |   4 |   2 |   1 |   0
  Cleaned          |    0 |   0 |     0 |   0 |   0 |   0 |   0 |   0 |   0 |   0 |   0 |     0 |   0 |   0 |   0 |   0

Total in 101228 ms

/label tide/merge-method-squash

See #48812 (comment) for a change I recommend (squashing before we merge it)

Thanks for the LGTM @sftim. Hopefully this will get merged soon. I was hoping to keep the individual commits in this PR because some of the intermediate steps contain solution alternatives that I'd like to reuse elsewhere. The commits will be squashed when the PR gets merged right?

OK, let's not squash on merge but can you squash this to the smallest number of changes that each represent a useful change? Doesn't have to be a squash to 1 commit.

Let's totally squash it on merge (I recommend that for all our projects). I was just hoping to keep the individual commits in this PR's branch history.
Ok, I'll look into reducing the number of commits, maybe even to one ... after I make a local clone of the branch.

Let's totally squash it on merge (I recommend that for all our projects). I was just hoping to keep the individual commits in this PR's branch history.

Noted, but this project prefers to preserve commits from the PR.

Before said squash, the final commit is / was d8392ccde38b557a2e6076a7bc763aed399243b5.

@sftim - PR rebased and squashed to 1 commit.

(you can fetch a commit directly from GitHub, but possibly it may eventually get garbage collected)

I'm able to build from a fresh install both locally and using a container, but in both cases I need to do a pushd api-ref-generator && git fetch --unshallow && popd in order to get make module-init to work before things build. (I actually have do do `make module-init twice, otherwise things aren't ready for the git fetch.)
reapplying lgtm
/lgtm

/hold
To make life easier, do not merge or unhold this until Kubernetes v1.32 is released. OK to unhold afterwards.

/hold cancel

/approve


AWS security hub auth upgrade

Required items, please complete
Change(s):

Added new template for setting up IdP in AWS
Updated python-script to use Managed Identity of the function and use "AssumeRoleWithWebIdentity"
Updated ZIP-package with new script, packages
Updated readme.md with new guidance
Updated deployment-template to account for the changes

Reason for Change(s):

Authentication with access keys is not secure or robust - this changes allows for best practice authentication without having to rotate or store keys.

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

Tested in multiple environments and works - fixed multiple bugs with authentication timing out etc.

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

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

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

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

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

Testing Completed:

Yes/No/Need Help

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

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

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

Yes/No/Need Help

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

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

@infernuxmonster : We wanted to check on the status of PR #5255 . PR is pending from more than 60 days. Let us know if any assistance is required for this PR. As Per our standard operating procedures if no response is received in the next 7 business days we will close this PR. Thank you for your cooperation.

@v-spadarthi Please do the needful

@v-spadarthi - I've updated everything now, the errors reported by the bot should not be an actual issue.

@infernuxmonster  checks is falling please take a look. thanks!!!

@infernuxmonster checks is falling please take a look. thanks!!!

Not sure what you want me to do here @v-marimanda - I've commented on both checks.

https://github.com/Azure/Azure-Sentinel/pull/5255#discussion_r968142686

assumed_role_object is set to the output of sts_client.assume_role_with_web_identity:
assumed_role_object=sts_client.assume_role_with_web_identity(
                RoleArn=self.role_arn,
                RoleSessionName=self.role_session_name,
                WebIdentityToken=self.web_identity_token
                )

After that we call the variable:
credentials=assumed_role_object['Credentials']

https://github.com/Azure/Azure-Sentinel/pull/5255#discussion_r968143821

Here as well, we set token in the following code:
try:
        managed_identity = ManagedIdentityCredential()
        azure_cli = AzureCliCredential()
        default_azure_credential = DefaultAzureCredential(exclude_shared_token_cache_credential=True)
        credential_chain = ChainedTokenCredential(managed_identity, azure_cli, default_azure_credential)
        token_meta = credential_chain.get_token(client_id)
        token = token_meta.token
    except azure.core.exceptions.ClientAuthenticationError as error:
        logging.info ("Authenticating to Azure AD: %s" % error)

Then we call it a few lines later:
    securityHubSession = SecurityHubClient(aws_role_arn, aws_role_session_name, aws_region_name, token)

In both of these instances the variables are defined and set inside a try-catch (except), maybe that is the issue, but the idea is that the script should throw errors if it fails to set the token or the assumed_role_object because they are vital to the running of the script.

@sreedharande can you please the review the pr. thanks!!!

@sreedharande can you please the review the pr. thanks!!!

@sreedharande , Can you please review the PR?

@sreedharande , Can you please review the PR?

Hey, sorry, missed this. Will fix ASAP.
tor. 8. sep. 2022, 22:05 skrev NikTripathi @.***>:

@v-spadarthi https://github.com/v-spadarthi Please do the needful
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/Azure-Sentinel/pull/5255#issuecomment-1241177433,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFE7JARQFGI2EHHB7KG2YDV5JBJ3ANCNFSM5YJSOKZA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@sreedharande , Can you please review the PR?

@sreedharande , Can you please review the PR?

@sreedharande , Can you please review the PR?

@sreedharande : Can you please review the PR?


JWT is extracted/validated before RequestMatcher

We store JWT inside a Cookie that is used between the frontend and backend.
In our ResourceServerConfigurerAdapter we configured this:
http.authorizeRequests()
        .antMatchers("/rest/assets/**/").permitAll()
        .anyRequest().authenticated();

It says that all requests to /rest/assets/ should be allowed.
The problem is that if JWT access token is expired, when it goes to the TokenExtractor ( public Authentication extract(HttpServletRequest request){} ) that will invalidate the request. But that happens before the matcher to /rest/assets.
Is there a way to ignore the extract of the cookie if the url is one of .permitAll()? I want to return the request even in case of expired token.

The best way to do that would be to not match /rest/assets/** in the top-level matcher (let another filter take care of those requests), or mark those as "ignored" in the global security configuration. You could also modify your client not to send tokens to endpoints that don't need them, or to respond to the 403 and refresh the token (if it needs refreshing it seems like you'd want to do that anyway).

It sounds as though we could update the OAuth2AuthenticationProcessingFilter to allow failed authentication attempts. This means that public resources would be allowed access if it fails and non-public resources would then fail because the authorization would not work.
A workaround would be to create a new WebSecurityConfigurerAdapter as @dsyer mentions.


Installing SAP HANA HDB Client (Linux)

Tutorial URL: https://developers.sap.com/tutorials/hxe-ua-install-hdb-client-linux.html
Please specify the step you are referring to
At Step 2.2 the code is using a file named hdb_client_linux_x84_64.tgz with a wrong typo
It should be hdb_client_linux_x86_64.tgz

Thanks for communicating the typo -- the tutorial has been corrected and republished.


defined Current Limits and Stators Limits in climber, shooter, intake, vertical conveyer, and floor conveyer in .h files and called stator and supply currents in .cpp

I'm not sure if we need a Stator call on both conveyer motors, does anyone know?

Okay, I double checked and yes, you do need to set both. Followers are not able to see the stator current limit set on the master; it has to be done for each individual motor.

Okay, I double checked and yes, you do need to set both. Followers are not able to see the stator current limit set on the master; it has to be done for each individual motor.


setState in callbacks

Hello.
How I can get state in callback?

I'll consider opening this again if you show your code

My code
const uploader = new FineUploaderS3({
      options: {
        objectProperties: {
          region: 'eu-west-2',
        },
        signature: {
          endpoint: endPoint,
        },
        request: {
          endpoint: URL_UPLOAD,
          accessKey: BUCKET_ACCESS_KEY,
        },
        uploadSuccess: {
          endpoint: myEndPoint,
          params: {
            isBrowserPreviewCapable: qq.supportedFeatures.imagePreviews,
          },
          customHeaders: {
          },
        },
        chunking: {
          partSize: 15000,
        },
        validation: {
          itemLimit: 2,
        },
        callbacks: {
          onComplete: function(id, name) {
           // This I want to set fileName to state: this.setStete({fileName: name});
         },
        }
      },
    });

You're lacking any context here. Where is your component code? Where is the state maintained?


CrateDB - UI changes - added user,pwd,ssl field

Closes #791

Added fields for

username
password
ssl toggle

Added connection string builder

Added CrateDB default port (4200)

[x] ran npm lint

[x]  ran tests

Thanks @proddata!


Kafka Sink Connector: support non-String keys

Currently the Kafka Sink Connector is able to support only keys with a String value.
We should support the generic byte[] key, as it is in Kafka.
Also we should support other data types and possibly may the generic key/value pair of Kafka to a KeyValue Pulsar schema

@sijie  comment in #9448

we need to make the key as pure bytes because that's the default behavior from Kafka.
KafkaAbstractSource -> KafkaAbstractStringKeySource -> KafkaStringSource
KafkaAbstractSource -> KafkaAbstractBytesKeySource -> KafkaBytesSource

The issue had no activity for 30 days, mark with Stale label.

It seems that the latest version has already supported the generic byte[] key, should this issue be closed?


Shouldn't the training be awaited?

Hello,
Amazing work here, I have been looking for a tfjs PPO implementation since a long time and this is totally mind-blowing. Just tested it on a snake game and it works great. Very clean work.
Small question: Is there a specific reason for having made train async? Nothing is awaited inside and the method itself is not awaited:
https://github.com/zemlyansky/ppo-tfjs/blob/main/ppo.js#L548

Thanks, @strblr! I don't remember why async is there:) Probably, you are right and it can be removed safely


Add support for Ivy branch attribute for resolving dependencies

I am creating this issue in GitHub as it seems that none of the related Ivy branch issues (https://issues.gradle.org/browse/GRADLE-1358, https://issues.gradle.org/browse/GRADLE-560, https://issues.gradle.org/browse/GRADLE-991) where migrated from Jira.
This ticket is about having real support for the Ivy branch attribute while resolving dependencies.
Expected Behavior
We would expect that it is possible to define in Gradle dependencies not only groups, module names, revision but as well the branch when using an Ivy repository.
Current Behavior
Impossible to pull dependencies by specifying the Ivy branch attribute.
Context
In our project we are publishing artifacts with Ivy and based on the source branch we publish them under a specific tree using the Ivy branch attribute.
To make it clear with an example our mainline publishes artifacts to [organisation]/([branch]/)[module]/[revision]/[artifact](-[classifier])-[revision].[ext] -> com.acme/my-module/1.0.0/my-module-1.0.0.zip where the branch attribute is not used. In a team branch those artifacts are published by specifying the branch attribute resulting in com.acme/team-branch/my-module/1.0.1-SNAPSHOT/my-module-1.0.1-SNAPSHOT.zip.
For publishing we use currently the Ivy standalone application since we have a different build system (CMake). The problem is that our clients are based on Gradle and while working on a feature they require to pull team branch dependencies using the Ivy branch attribute.
Unfortunately this seems not to be supported within Gradle (tested with Gradle 3.0 and 3.3).
Steps to Reproduce (for bugs)
Your Environment

Linux, OSX
Gradle 3.0/3.3
Artifactory as repository system

I do not mean to make this a bigger issue than it is, but I cannot help to think that the more general case of this issue encompasses the Ivy extra attributes, which, like the "branch" attribute, can be used as coordinates in the repository. GRADLE-3060 covers this more general case.

Thank you for moving these issues @martinm82. This seems closely related to #1386. We are currently focused on performance, general user experience, and plugin developer experience for the short term. I expect given the interest that we'll get to this in the mid to long term, but a contributor could make a very big impact by addressing both changes sooner.
Is there a volunteer to take a crack at this?

Hi @eriwen,
I'd be happy be a volunteer here since I also need such a support. Just need to firstly go through all the docs about contributing to Gradle.

@snakemaycry sounds great! A CLA and CONTRIBUTING.md should be all you really need. Looking forward to your contribution.

@snakemaycry Have you been able to make progress on this issue?

I've been working on this issue because it was blocking our investigation of a migration from Ant+Ivy to Gradle. We considered workarounds (one repository per branch), and contemplated a complete republish of all our products without branches. But because of the number of branches we have, and the need to do our migration incrementally, we concluded that we just had to have support for Ivy branches in Gradle (specifically, support for including a [branch] identifier in repository definitions to restrict resolves to a particular branch).
My changes seem to work OK for our projects. I can now declare a dependency like this:
    runtime(group="metaswitch", branch="diameter/trunk", name="diameter-base", version="latest.integration", configuration="impl")

But it feels like what I've done could be cleaner. (I think there are too many instanceof checks for example.)
I struggled to avoid adding branches to the core API interfaces, or the default implementations, because this is something Ivy-specific so belongs in Ivy-specific classes. But it was hard to pass the branch to the places it needed to get without doing that. And a lot of the time there was no factory method, and no easy way to decide which type of identifier or selector to create.
So I've pushed my branch in the hope that I can get some feedback on my approach. Possibly I've missed some obvious way to implement it more nicely. Perhaps I should have just added optional branches throughout the default implementation classes.
What's the best way to proceed with this, considering it touches some pretty core parts of Gradle, and I'm sure it has to go through plenty of iterations. I could create a PR for comments, but maybe it is a bit underdone for that just yet?

@perrin-metaswitch I would not hesitate to push the branch as a PR to get feedback. It might give other people some good ideas.


feat(Highlight): New Highlight Component

Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[X] I have read the CONTRIBUTING document
[X] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[X] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] My change requires a change to the documentation
[X] I have updated the documentation accordingly
[X] I have added tests to cover my changes
[X] All new and existing tests passed

Description
This new component allows developers to highlight text based on a term
condition

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

@bajcmartinez could you sign the license/cla?
@dimabory Are you finished with your review?

I did already the other day:

@bajcmartinez could you sign the license/cla?
@dimabory Are you finished with your review?

We should resolve this -> https://github.com/ZEISS/precise-ui/pull/202#pullrequestreview-317497175

@bajcmartinez could you sign the license/cla?
@dimabory Are you finished with your review?

We should resolve this -> #202 (review)

I've pushed new changes with test coverage for those cases and the resolution


[FEATURE] Review Apploications

Problem
Admins need a way to review application
User Story(s):
As a round manager, I want to be able to see new applications and review applciations, so that I can be on top of my approvals
Acceptance Criteria

approve or reject applciation
show textbox
interact with #12 contract, and update status of appkication
show already approved applciations
show who approved the application in admin notes

Limitations

need to display application reival status to preojcts in some way, should show public #2
textbox needs to be supported on contract
hard for users to see new applications
maybe might add max applications so add UI for this

Resources

outline links and relevant resources, references, implementations

https://github.com/PotLock/grantpicks/pull/40


Display NUnit "message" for Inconclusive

The following test case:
<test-case id="0-1475" name="FlashTestLocationShouldIncrementOnEachTick" fullname="SensorSimulatorTests.Tests.Integrity.DiagCycleRamFlashTests.FlashTestLocationShouldIncrementOnEachTick" methodname="FlashTestLocationShouldIncrementOnEachTick" classname="SensorSimulatorTests.Tests.Integrity.DiagCycleRamFlashTests" runstate="Runnable" seed="1460000646" result="Inconclusive" start-time="2015-12-29 07:34:53Z" end-time="2015-12-29 07:34:53Z" duration="0.233112" asserts="0">
<properties>
<property name="Category" value="MergeTests"/>
</properties>
<reason>
<message>
<![CDATA[ Cannot execute test, do not know firmware size... ]]>
</message>
</reason>
<output>
<![CDATA[
2015-12-29T08:34:53.476:Debug:DiagCycleR: --------------- Test starting ---------------
 2015-12-29T08:34:53.476:Debug:SENSORTEST: WR: Write:0xFF-SERVICE_UA-0x01(
 2015-12-29T08:34:53.710:Debug:DiagCycleR: --- TearDown -----
 2015-12-29T08:34:53.710:Debug:DiagCycleR: --- TearDown complete -----
]]>
</output>
</test-case>

Is displayed as

It would be very helpful if the message was displayed above the console output... :smile:

Espen, sure.  I will try to do it soon as I am out..  But if you get a chance before me, you can add this feature in and send me a pull request.
The output comes from the following line:
https://github.com/reportunit/reportunit/blob/master/ReportUnit/Parser/NUnit.cs#L207

Feature added in d4440dba1264e64a6ead0e33ba31af221965fdf1


Minor tweaks for consistency to improve parsing

These little inconsistencies tripped up the code I'm using to parse the blocks out of this code to generate types (slightly related to #67).

Thanks!


Investigate ways to send multiline logs to the logging cluster

From retrospective 22 May 2020

Possibly https://coralogix.com/log-analytics-blog/parsing-multiline-logs-the-complete-guide/

Closing as stale – this hasn't proved to be a big impediment in practice.


TSC / Committer Nomination: Mark Reid, Animal Logic

Per the guidelines of the OCIO GOVERNANCE.md, this issue is to nominate adding Mark Reid (@markreidvfx) as a voting member of the OCIO TSC, and as an official representative on the TSC for Animal Logic.
Mark's contributions to OCIO have been valuable and useful - including SIMD optimizations for 1D and 3D LUTs. He has been attending the TSC meetings for around a year now, and always offers valuable insight and quick feedback.
I also propose we add Mark to our Committers group, so he can review and approve PRs.
Thank you for all of your contributions, Mark, and looking forward to making it official!

Thumbs up!

Awesome!


Followed instructions exactly, all I get is:  GeneratorsServiceProvider' not found

After running the Composer update I get this when I run php artisan.
PHP Fatal error:  Class 'Way\Generators\GeneratorsServiceProvider' not found in /var/www/laravel/bootstrap/compiled.php on line 4214
{"error":{"type":"Symfony\Component\Debug\Exception\FatalErrorException","message":"Class 'Way\Generators\GeneratorsServiceProvider' not found","file":"/var/www/laravel/bootstrap/compiled.php","line":4214}}

same issue here, L4.2 with "way/generators": "~2.0", and install by the command composer install --dev on a Mac, nothing installed in the vendor folder.

You  have to run:
1 - sudo composer clearcache
2 - sudo composer update
I hope this works out for you.
Good luck!

@GabLeRoux
it works. thank you 👍


do not understand the codes in imagenet curation sub-folder

Hi,
Thanks for providing this helpful codebase. I am trying to use imagenet video dataset also, and I might have to implement a python  version since I use python in my project. I do not understand the details of this codebase. Will the code generate image chips with the objects in their centers, and will the generated chips be fixed in their sizes?

Hi,
Yes, your interpretation is correct.
On Fri, Feb 15, 2019 at 8:56 AM CoinCheung<EMAIL_ADDRESS>wrote:

Hi,
Thanks for providing this helpful codebase. I am trying to use imagenet
video dataset also, and I might have to implement a python version since I
use python in my project. I do not understand the details of this codebase.
Will the code generate image chips with the objects in their centers, and
will the generated chips be fixed in their sizes?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bertinetto/siamese-fc/issues/69, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADLRuepqkb3daEfhjq4yBL3px_a6PTAnks5vNnZPgaJpZM4a9Neq
.

Thanks!
In one case, the target size is 255x255, and the bounding box size of the object is 40x60, while the image size is 500x700. I can crop a chip of size 255x255 with the 40x60 bounding box at its center. However, suppose the bounding box has size 400x600, shall I still crop a 255x255 chip within the 400x600 bounding box, or do I need to resize? If so, would you please tell me what size should I resize the image into?


How to target specific version on CDN

Today our formula rendering seems to be broken and I think that it might have todo with the new version of MathJax released yesterday. Currently we load MathJax as follows:
<script src="//cdn.mathjax.org/mathjax/latest/MathJax.js?delayStartupUntil=configured"></script>

Now I would like to load v2.5.1 (I assume that latest here is v2.5.2). I've tried things like
<script src="//cdn.mathjax.org/mathjax/2.5.1/MathJax.js?delayStartupUntil=configured"></script>

but that doesn't work. Is the version notation incorrect or is this just not possible ?

There's no way, I'm afraid, since we do not differentiate patch versions on the CDN, just minor versions.
If there's a bug, could you report it please?

Here is a demo of the issue we have: http://jsfiddle.net/1hLvdbm2/
I haven't tested this problem agains an older version of MathJax yet, but because we see this problem since today, I assumed that it might have todo with the new version!

This seems to be a timining issue. Could you file a new issue please?

done: https://github.com/mathjax/MathJax/issues/1179


Try password reset with GMail

Add various properties, as in Stroom

Works fine. Had to add configuration for transport, i.e. TLS or SSL.


Is this abandoned and other questions

I've seen this has not been updated for a while. Whats the diference between orfeed and flashbots?

Brand new to Solidity.  I realize that since OrFeed was created, there has been many changes made to solidity, syntax wise.  I was wondering if there would ever be an update to go along with the new changes or there would possibly be a new video that deals with the some of the changes?  Thanks for building OrFeed in the first place.  It's an incredible tool.


Register this resource into the global list

This is purely a request from another Concourse user. Please make sure your resource type implementation can be found much easier:

register it so it can be found at https://resource-types.concourse.org

Everything about registering can be found here:
https://github.com/concourse/resource-types#submitting-a-resource-type

Could you also add the topics concourse and concourse-resource to this Github project? I mostly use the last topic to find resource implementations on Github.


Remove outdated warning

Since 1.0 is out for 1 1/2 years, this can safely be removed, I assume.
This corrects several grammar-related mistakes, guided by a software grammar checker.

@ShalokShalom thank you for your contribution, but please note that the CI pre-commit failed: https://results.pre-commit.ci/run/github/316342881/1697357723.XX_Ioh--S_GsetoEEL8V5A
This is because of too long lines. We would appreciate it if you could pass pre-commit checks before pushing changes. Thank you in advance.

I did change this.
And I recommend getting rid of this bot.
It requests changes that are quite frankly not relevant at all - removing trailing whitespace from a documentation page, really? - and instead, opt out for a grammar checker.
That actually improves the quality of the documentation, and issues such as those that are fixed by this commit, could not happen in the first place.

I use Grammarly, but it's closed source. The open source languagetool is sadly very bad in the free version. The paid one might be good

@ShalokShalom thank you for your suggestions:

It requests changes that are quite frankly not relevant at all - removing trailing whitespace from a documentation page, really? - and instead, opt out for a grammar checker.

We improve pre-commit whenever we will find time for it. Grammar checks were definitely missing for things you improve.
I'm improving this patch series here: https://github.com/Dasharo/docs/pull/680 to pass all checks. After merging #680 I will close this PR as well.


FINERACT-2035: Client Trend For Day Scale is not work Due to BadSqlGrammar Error

Issue: FINERACT-2035
Client Trend For Day Scale is not work Due to BadSqlGrammar Error
This error is happened due to bucket 1 Day is inside single quotation in 0087_update_dashboard_table_reports.xml file which is responsible for storing SQL query in DB that SQL query is responsible for the BadSQLGrammar Error. I check the other queries related to this query but, all of them are working fine
Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[x] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[x] Create/update unit or integration tests for verifying the changes made.

[x] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[x] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

I have solved 2 issues and unfortunately pulled in the same PR. I will dissect and pull in different PRs


[MM-26160] Updates to check if text is string before attaching as string

Summary
This now explicitly checks that a "shared" text is actually a string before being treated as such.
The selected text being shared is available in intent.getStringExtra(Intent.EXTRA_TEXT); where we check for it - if it is blank and text/plain intent is still sent, we can safely assume it a .txt file.
Boolean isString is available on the JS side to check.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-26160
Checklist

[ ] Added or updated unit tests (required for all new features)
[ ] Has UI changes
[ ] Includes text changes and localization file updates

Device Information
This PR was tested on:

Pixel 4 Simulator Android v29

Screenshots
https://user-images.githubusercontent.com/456511/116178057-431f0880-a758-11eb-9e9d-f35c6248ae7d.mov
Release Note

Fixes a bug in sharing multiple files to MatterMost where text files don't come through

Release notes should be in past tense, right?

Release notes should be in past tense, right?

Whoops, edited / updated.

Cherry pick is scheduled.


dogehouse: Add deafen

@ityonemo helped in fixing bug, good guy!

wip

bro wtf are these conflicts 😢

Not sure that "deafen" is a particularly evocative command - probably "silence" and "unsilence" are better choices (it's confusing as it is, because mute can mean 'speaker' OR 'microphone'.  Also, is there a reason why this change needs to propagate?  It seems like it should live in the browser, or am I missing something?

oh no new conflicts...

gonna update this to match the new spec

see https://github.com/benawad/dogehouse/blob/staging/kousa/ADDING_TO_MESSAGING_API.md for instructions for new spec

see https://github.com/benawad/dogehouse/blob/staging/kousa/ADDING_TO_MESSAGING_API.md for instructions for new spec

i don't see what i haven't followed from here? could you please tell me (also i just copied the exact way mute works...)


The file is not a database😕.

Hi...I noticed that the flag is also in the beta version, please remove it from there if possible.
But I have a question for another problem!
I was able to create a database with table through the API and Multicipher...and also some rows of data.
but the problem is that when I try to open the database with Sqlcipher(on command line), it gives an error and says that it is not a database!
I first created the table with sqlcipher and then tried to connect with the API, I also tried the other way around.
but I always get the same error... is this the expected behavior?

Please don't quote old/closed issues in a new issue and mix up the context. It makes it very difficult for the maintainers to debug, for you to get an answer, and for the people who read this in the future. An old issue should only be mentioned in the context of your current issue has a relationship to that.
Please include some debug information, your code, or better, a minimal reproducible repo for your code so the maintainers can quickly debug the issue you're running into. Open-source maintainers hardly have any time to investigate things from scratch.
Always search for old issues before opening a new one because there's a high chance that your issue could already have been debugged in the past.

Continuing from that third point, the issue you're having is both in the documentation and mentioned in multiple issues including Issue #14.
Closing the issue as a duplicate.

Please don't quote old/closed issues in a new issue and mix up the context. It makes it very difficult for the maintainers to debug, for you to get an answer, and for the people who read this in the future. An old issue should only be mentioned in the context of your current issue has a relationship to that.
Please include some debug information, your code, or better, a minimal reproducible repo for your code so the maintainers can quickly debug the issue you're running into. Open-source maintainers hardly have any time to investigate things from scratch.
Always search for old issues before opening a new one because there's a high chance that your issue could already have been debugged in the past.

Continuing from that third point, the issue you're having is both in the documentation and mentioned in multiple issues including Issue #14. Closing the issue as a duplicate.

I'm so sorry.
But:
1- I have already used the reference feature in other repositories and they had no problem!
2- And Of Course, Github and Microsoft must have put that option for users to use...isn't that right???
In any case, you as the repository owner have options...such as deleting an issue completely...if you need to correct your issue history and are very concerned, please delete this issue completely.


Many ttnn operations fail with low PCC when slow dispatch mode is "1"

Many ttnn operations fail with low PCC when slow dispatch mode is "1"
Affected ops: add, sub, mul, tanh, gelu, permute, exp
Note! Problem is not observed when running operations with profiling!
To Reproduce
Steps to reproduce the behavior:
Checkout syrmia/ttnn-sweeps branch (Soon to be merged in main). Run unit tests/ttnn/python_api_testing/non_working_unit_tests/grayskull/test_slow_dispatch_mode.py  using this command:
pytest tests/ttnn/python_api_testing/non_working_unit_tests/grayskull/test_slow_dispatch_mode.py

Expected behavior
There are multiple test cases presented in the unit test and some of them are expected to fail with low PCC error.
For example, one of the tests is expected to fail with this result:
Max ATOL Delta: 1.0, Max RTOL Delta: 1.0, PCC: 0.0, PCC check failed

Reason why some do not fail is possible because they are needed to mako others fail.
Getting Details
You can get more combinations tested using test sweeps:
tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_eltwise_add_test.yaml tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_eltwise_exp_test.yaml
tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_eltwise_gelu_test.yaml
tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_eltwise_mul_test.yaml
tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_eltwise_sub_test.yaml
tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_eltwise_tanh_test.yaml
tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_permute_test.yaml
with command for example:
python tests/tt_eager/python_api_testing/sweep_tests/run_pytorch_test.py -i tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_eltwise_add_test.yaml -o ./result-sweeps

Result will be saved in ./result-sweeps folder
Note! Problem is not observed when running operations with profiling!

Labeling as P3 as sweep on slow dispatch is lower priority

Retested after pulling from main, these tests no longer fail.

Retested after pulling from main, these tests no longer fail.

@boris-drazic Are you sure? Just tested today on latest main (and grayskull card) and still failing.

Getting low PCC when we run in slow dispatch without profiling smells like a move semantics (or similar) bug.
@nemanjagrujic , do you know if we have a C++ test that exposes this?   If so, I can easily kick this off through valgrind and callgrind and take a closer look.

Getting low PCC when we run in slow dispatch without profiling smells like a move semantics (or similar) bug.
@nemanjagrujic , do you know if we have a C++ test that exposes this? If so, I can easily kick this off through valgrind and callgrind and take a closer look.

@eyonland We did not make C++ test which exposes that issue.

Works now


improve code pythonic readability

While at https://github.com/bitcoin-core/HWI/pull/409 and https://github.com/bitcoin-core/HWI/pull/410 I just couldn't resist to try and improve some pythonic readability.
Namely, I

converted for loop into call to sum()
inlined variable that is immediately returned
lifted return into if
merged duplicate blocks in conditional, removing redundant conditional
replaced unused for index ('txout') with underscore
replaced if statement with if expression
replaced multiple comparisons of same variable with in operator
replaced unneeded comprehension with generator
simplified if expression by using or
simplified conditional into return statement
used any() instead of for loop, inverted any/all to simplify comparisons

As I know stylistic PR are not welcome, let me stress here that modern python coding should leverage mypy, black, flake8, pylint, bandit, isort, and sourcery. These tools combined provide a powerful contribution, helping your residual bug not to be lost among hundreds of warnings.
This PR includes https://github.com/bitcoin-core/HWI/pull/409 but could be made independent from it; if both PRs are accepted, it should be merged later to separate the functionality change from the cosmetic changes.
If this is rejected... well I got some fun :-) and, actually, the relevant PR is really https://github.com/bitcoin-core/HWI/pull/410

Closing as up for grabs


mnistm labels

Hi,
Thanks for your code. I found that you use the mnist labels with mnistm dataset even when you are creating the target only batch. Can you explain why is that??
Thanks

The MNISTM dataset is simply a transformed version of the MNIST dataset (see create_mnistm.py), so the labels are actually the same, it is the images that are different. I agree that it would probably be more clear if I had replicated the labels and stored them with the MNISTM images.

Hi,
Thanks for your reply. I'm a little bit confused now because as i
understand the target dataset is unlabelled. Is not it??
On Tue, May 16, 2017 at 5:14 AM, Clayton Mellina<EMAIL_ADDRESS>wrote:

The MNISTM dataset is simply a transformed version of the MNIST dataset
(see create_mnistm.py), so the labels are actually the same, it is the
images that are different. I agree that it would probably be more clear if
I had replicated the labels and stored them with the MNISTM images.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pumpikano/tf-dann/issues/13#issuecomment-301670778,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACvc_IfZOEICHrlx_BqyI6bldKCKTa0Qks5r6SKPgaJpZM4NZZ2I
.

--
Best Regards,
Fatma Amin Elsafoury

Yes, this is a method for domain adaptation when the target domain does not have labels. MNISTM is a toy dataset for which we do have labels. The notebook uses those labels to evaluate the success of the domain adaptation, as well as compare to the case of training directly on the target labels, which provides an upper bound for the success of domain adaptation. When performing domain adaptation, we don't use the target labels as supervision.

but don't you use when creating the
gen_target_batch = batch_generator(
[mnistm_train, mnist.train.labels], batch_size / 2)
which is used in the training the domain adaptation model 'dann' ????
best,
On Tue, May 16, 2017 at 4:54 PM, Clayton Mellina<EMAIL_ADDRESS>wrote:

Yes, this is a method for domain adaptation when the target domain does
not have labels. MNISTM is a toy dataset for which we do have labels. The
notebook uses those labels to evaluate the success of the domain
adaptation, as well as compare to the case of training directly on the
target labels, which provides an upper bound for the success of domain
adaptation. When performing domain adaptation, we don't use the target
labels as supervision.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pumpikano/tf-dann/issues/13#issuecomment-301827835,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACvc_OPHGD0UytXdL9x1hfpKlCFMC3iwks5r6cbDgaJpZM4NZZ2I
.

--
Best Regards,
Fatma Amin Elsafoury

These are not used during training, though they are used to evaluate the model accuracy after training. In particular, the model.train placeholder governs the behavior: when it is True the second half of the batch (where the target examples and labels reside) does not participate in the prediction loss, and when it is False the entire batch is passed to the prediction network.


grunt: not found on raspberry pi 2

npm WARN deprecated<EMAIL_ADDRESS>This package is deprecated. Use Object.assign.

<EMAIL_ADDRESS>postinstall /home/pi/Compilations/PokemonGo-Map-3.2.0
grunt build

sh: 1: grunt: not found
npm ERR! Linux 4.4.13-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.3
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>postinstall: grunt build
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'grunt build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the pogomap package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     grunt build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs pogomap
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls pogomap
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/Compilations/PokemonGo-Map-3.2.0/npm-debug.log

so whats the problem? go find it? or do you need a scanner for that too?


Fixes javaslang/javaslang#225: Rename Match.caze() to Match.when()

Coverage remained the same at 99.92% when pulling 363f6446efb8ad2f3258ae012e376117622f6613 on danieldietrich:issue225 into 4771beb4f34f45a2d7c56f456c7c178a1f9cda05 on javaslang:master.

Coverage increased (+0.0%) to 99.92% when pulling d884733d7c78a535da7b0f09223f6a382f7ed9be on danieldietrich:issue225 into 4771beb4f34f45a2d7c56f456c7c178a1f9cda05 on javaslang:master.


feat: emit event when full collateral has been reached

Purpose for this PR

The only option available for Alice to know when her bond has reach full collateralization is by polling.
This PR adds an event that is emitted when the final deposit is made, reaching full collateral.

Readability can be improved throughout the contract, raised an issue for that change set https://github.com/windranger-io/windranger-treasury/issues/30


Custom datepicker popup button

I'm trying to have a datepicker popup with an extra button. I can add the extra button with a custom template. That part works, but now i want to select a date when I click on the button. I already tried to use select('2018-03-15', $event) but that does not work.
I think the select needs a real date object but how can I achieve that without needing to edit the directive code?

Closing this as this project is no longer being maintained, per the README and the ISSUE_TEMPLATE.


[feat] Quest: Authority quest

Create a quest based on an off-chain authority's attestations.
We may want to add some quests that don't depend on onchain data, like tweets. For this we will need a generic quest that exposes an interface function mark_claimable, which is only callable by the authority address. This will mark that a specified set of addresses can claim a quest.
Then implement the normal quest interfaces for claiming the quest by the user. Also create tests.
References

Example Quest

@TAdev0 would you like to take this issue instead? It is similar!


Custom serializer support for LINQ (#4138) should support STJ ExtensionData

Just by switching your custom serializer to inherit from 'CosmosSerializer' to 'CosmosLinqSerializer' this breaks any usage of ExtensionData in queries.
With custom serializer support, we should add detection of STJ-based 'ExtensionData' attribute in addition to the newtonsoft one. See #3777
Expected behavior
ExtensionData part of the path should be skipped in the generated SQL query:
i.e. MyObject.ExtensionData.MyCustomProperty > 42 becomes MyObject.MyCustomProperty > 42
Actual behavior
MyObject.ExtensionData.MyCustomProperty is retained, breaking the query, since STJ serializes MyCustomProperty to the root of the object.
Also, you cannot utilize CosmosLinqSerializer if you are trying to query against JSON ExtensionData.
Environment summary
SDK Version: 3.39.0-preview.0
OS Version (e.g. Windows, Linux, MacOSX): Windows 11
Additional context
#3777
#3834
#4138
@Maya-Painter

Hi @onionhammer, can you try handling extension data in your implementation of SerializeMemberName in your custom STJ serializer?
e.g.
  public override string SerializeMemberName(MemberInfo memberInfo)
  {
      JsonPropertyNameAttribute jsonPropertyNameAttribute = memberInfo.GetCustomAttribute<JsonPropertyNameAttribute>(true);

      string memberName = jsonPropertyNameAttribute != null && !string.IsNullOrEmpty(jsonPropertyNameAttribute.Name)
          ? jsonPropertyNameAttribute.Name
          : memberInfo.Name;

      // Handle ExtensionData members
      System.Text.Json.Serialization.JsonExtensionDataAttribute jsonExtensionDataAttribute =
          memberInfo.GetCustomAttribute<System.Text.Json.Serialization.JsonExtensionDataAttribute>(true);
      if(jsonExtensionDataAttribute != null)
      {
          return null;
      }

      return memberName;
  }

@Maya-Painter Good idea, that does fix it.
Can the base method be decorated as nullable?
    public abstract string SerializeMemberName(MemberInfo memberInfo);


Social networks validator

Validators should be implemented for website, twitter, linkedin, instagram, telegram and discord fields.
https://www.figma.com/file/iu2QNG0VK2MpSLn0aokFjZ/DApp-Store-v2?node-id=81%3A5673

Ссылку на linkedin аккаунт обрезать до формата “in/nickname” или “company/companyname”

In the links for linkindin and discord, the symbol "-" can be written, we need to add the ability to enter it

Please change the text example for the discord input line at https://discord.gg/jdshfwiue

checked


Feature: zabbix integration

Hi,
I have prepared pull request with zabbix integration (#30).
If you agree with this, please review and let me know if there is any change required.
Regards,
Jan Klepek

It's a great functionality!
I am waiting for implementation.

Hi,
I'm happy to learn that the tool (using the json output format) is working with Zabbix.
Unfortunately, I don't have any knowledge of that tool and I wasn't able to implement it in the test suite yet. So, currently, I'm not open to support any code I can't test.
I'll have a look at the PR though and see if there's any code impact to accept it.
That being said, if you have any good resource to show how to use zabbix docker containers to monitor PG instances, I'd be willing to give it another try. (The test suite code is based on docker and ansible, can be found in the test directory)
Kind Regards

This could be helpfull to prepare a test server:
https://techexpert.tips/zabbix/zabbix-docker-installation-ubuntu-linux/
Official documentation:
https://www.zabbix.com/documentation/current/en/manual/installation/containers
Agent installation:
https://www.codesie.ch/en/wiki/ansible/install-zabbix-agent
Best Regards


Colours and Callouts in 1.0

There seems to be an issue with the colours of multiple things, see yellow for italics, and orange for links in the screenshot.
Additionally, the new formatting for callouts looks radically different to the point where I'm not sure its intended.

OLD

NEW

The yellow color for italics and bold is new and I added it with the v1.x of Obsidian. The previous white color did not offer enough contrast. You can easily revert this with a CSS snippet.
Regarding callouts, the theme does not modify those whatsoever. What you're seeing is the new default theming in Obsidian.
If you think there is a bug in any theme, make sure to always compare what you see to the default theme. Sometimes it's wackiness in upstream Obsidian. :-)


Feature: MoveIt!-Gazebo Integration

I changed several packages in the entire Blue stack to work with MoveIt! Gazebo.
Edited Packages

blue_core
blue_moveit
blue_simulator

Related PRs

https://github.com/berkeleyopenarms/blue_simulator/pull/5#issue-281898034
https://github.com/berkeleyopenarms/blue_moveit/pull/2#issue-281898515
https://github.com/berkeleyopenarms/blue_core/pull/51#issue-281897805

PR Specific Description
I added a world for simulating object pickup, as well as added a 3rd party mimic joint plugin for simulating mimic joints.

Thanks for your contribution! These changes look great!
It seems you have added roboticsgroup_gazebo_plugins as a submodule. Is there a .gitmodules missing from the PR?

Thanks for your contribution! These changes look great!
It seems you have added roboticsgroup_gazebo_plugins as a submodule. Is there a .gitmodules missing from the PR?

You're right about that. Let me fix it.


ListVMInstanceViews by doing a REST API GET is not providing Fault Domain information

According to the VMSS FAQ doc, you can obtain fault domain information for each instance by running a REST API GET call against the instance. However, when I ran the following command, it provided instance details but NO fault domain information.
ASK:

Can you please provide a way to get the fault domain information for instances in a scale set and update the information on the FAQ page if this REST API provided does not provide fault domain information?
In addition, can you please update the GET call to include the API version like below? API version is not included in the VMSS FAQ Example and will not work without it.

Here is the output for one VMSS instance:
GET https://management.azure.com/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Compute/virtualMachineScaleSets/eleventwe/virtualMachines?api-version=2022-03-01&$expand=instanceView&$select=instanceView
Result (that shows no fault domain information):
{
"value": [
{
"name": "eleventwe_0",
"id": "/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Compute/virtualMachineScaleSets/eleventwe/virtualMachines/0",
"type": "Microsoft.Compute/virtualMachineScaleSets/virtualMachines",
"location": "eastus",
"instanceId": "0",
"sku": {
"name": "Standard_A1_v2",
"tier": "Standard"
},
"properties": {
"latestModelApplied": true,
"modelDefinitionApplied": "VirtualMachineScaleSet",
"networkProfileConfiguration": {
"networkInterfaceConfigurations": [
{
"name": "eleventwenic",
"properties": {
"primary": true,
"enableAcceleratedNetworking": false,
"dnsSettings": {
"dnsServers": []
},
"enableIPForwarding": false,
"ipConfigurations": [
{
"name": "eleventweipconfig",
"properties": {
"subnet": {
"id": "/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Network/virtualNetworks/eleventwevnet/subnets/eleventwesubnet"
},
"privateIPAddressVersion": "IPv4",
"loadBalancerBackendAddressPools": [
{
"id": "/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Network/loadBalancers/eleventwelb/backendAddressPools/eleventwebepool"
}
],
"loadBalancerInboundNatPools": [
{
"id": "/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Network/loadBalancers/eleventwelb/inboundNatPools/eleventwenatpool"
}
]
}
}
]
}
}
]
},
"vmId": "b49eb397-198f-4534-8b34-b9e0fb6ac57d",
"hardwareProfile": {
"vmSize": "Standard_A1_v2"
},
"storageProfile": {
"imageReference": {
"publisher": "MicrosoftWindowsServer",
"offer": "WindowsServer",
"sku": "2019-Datacenter",
"version": "latest",
"exactVersion": "17763.3128.220202"
},
"osDisk": {
"osType": "Windows",
"name": "eleventwe_eleventwe_0_OsDisk_1_539eb1ed7e8149ea9e2169407e5612ef",
"createOption": "FromImage",
"caching": "ReadWrite",
"managedDisk": {
"id": "/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Compute/disks/eleventwe_eleventwe_0_OsDisk_1_539eb1ed7e8149ea9e2169407e5612ef"
}
},
"dataDisks": []
},
"osProfile": {
"computerName": "eleventwe000000",
"adminUsername": "vmssadmin",
"windowsConfiguration": {
"provisionVMAgent": true,
"enableAutomaticUpdates": true
},
"secrets": [],
"allowExtensionOperations": true,
"requireGuestProvisionSignal": true
},
"networkProfile": {
"networkInterfaces": [
{
"id": "/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Compute/virtualMachineScaleSets/eleventwe/virtualMachines/0/networkInterfaces/eleventwenic"
}
]
},
"provisioningState": "Succeeded",
"timeCreated": "2022-02-22T16:24:33.4224667+00:00"
},
"resources": [
{
"name": "Microsoft.Powershell.DSC",
"id": "/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Compute/virtualMachines/eleventwe_0/extensions/Microsoft.Powershell.DSC",
"type": "Microsoft.Compute/virtualMachines/extensions",
"location": "eastus",
"properties": {
"autoUpgradeMinorVersion": true,
"forceUpdateTag": "1.0",
"provisioningState": "Failed",
"publisher": "Microsoft.Powershell",
"type": "DSC",
"typeHandlerVersion": "2.9",
"settings": {
"configuration": {
"url": "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/demos/vmss-windows-webapp-dsc-autoscale/DSC/InstallIIS.zip",
"script": "InstallIIS.ps1",
"function": "InstallIIS"
},
"configurationArguments": {
"nodeName": "localhost",
"WebDeployPackagePath": "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/demos/vmss-windows-webapp-dsc-autoscale/WebDeploy/DefaultASPWebApp.v1.0.zip"
}
}
}
},
{
"name": "MicrosoftMonitoringAgent",
"id": "/subscriptions/8a3c79de-f6bf-42e9-9217-47b936ba4d16/resourceGroups/RGTest/providers/Microsoft.Compute/virtualMachines/eleventwe_0/extensions/MicrosoftMonitoringAgent",
"type": "Microsoft.Compute/virtualMachines/extensions",
"location": "eastus",
"properties": {
"autoUpgradeMinorVersion": true,
"provisioningState": "Succeeded",
"publisher": "Microsoft.EnterpriseCloud.Monitoring",
"type": "MicrosoftMonitoringAgent",
"typeHandlerVersion": "1.0",
"settings": {
"workspaceId": "0bfca40c-6d0d-443c-884c-d1b407bed835",
"stopOnMultipleConnections": "true"
}
}
}
]
},
{

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

ID: b94c5948-acb1-e3aa-7148-6aa2278bcdef
Version Independent ID: 9ada224f-5a76-bcde-2dc0-928a29c4323f
Content: FAQ for Azure virtual machine scale sets - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-faq.yml
Service: virtual-machine-scale-sets
GitHub Login: @mimckitt
Microsoft Alias: mimckitt

@kmccullagh19 Thank you for your feedback!  We've assigned this to the document author for review.

@kmccullagh19 Note that fault domain is not returned when the scale set uses max spreading (platformFaultDomainCount = 1), because there is no guarantee as to how many fault domains would be used with this setting.
Are you using Max spreading?

Closing this out since I have not heard back. If still having issues, just let me know.
#please-close


Is this normal to have so many queries?

I have 7 rolaes and 70 premissions,
But when I open page, I have lot of queries, regarding, roles, why it is
Image
Thanks1

I'm not able to view your image, would you mind attaching it to your issue here on GitHub? Thanks!

Maybe now
https://fv8.failiem.lv/thumb_show.php?i=axy44sxx&view

Thanks, I will definitely be taking a look into this~

Same thing here, it seems that every permission test creates a query. In lots of situations, we only check permissions for the authenticated user, maybe you could query everything needed (every role and permission for the user) and then save it in a var for the next uses in the same page/request ?

@roulendz and @paulghz please give v3.0.6 a spin! Should no longer see hundreds of DB queries being ran.

Great ! Definitely better and efficient now !
Thank you, for this modification and your library !


Ci test unit

Proposed Changes
Added a complete CI workflow for test the two architectures ESP32 and ESP8266 with a CI over PlatformIO on GitHub Workflows (Actions)
Checklist

[x] added PlatformIO basic example (Influx Basic Write)
[x] tested example using PlatformIO
[x] added global platformio ini file for test the complete library on ESP32 and ESP8266
[x] added workflow for Github usin CI over Python and PlatformIO
[x] added badge on README for success CI test on master branch
[x] tested with the current commint before the PR

How to test the library (locally)
In the root directory of the library only type:
pio run

It is only for local tests, after the merge of this PR, Github workflow will doing that alone for you :D
Badge
The badge only will be works after this PR, but a little preview is possible in my project CanAirIO

Thanks for this PR. Having checking build in CI is also on my TODO list,
It seems having copied example for PlatformIO look a bit redundant. Is it possible, to have the same example for Arduino IDE and PlatformIO. E.g. to somehow persuade PlatformIO to compile a .ino file?

Nop, this is the reason why I did it, the ino file is possible build with a simple platformio.ini file in the same directory, and works fine, but the problems is that with CI it doesn't works well when you need extend a different architectures. I could do a commit changes for that but I dont recommended it. What do you want?

For now, I think, this PR makes a great addition. We can change some details later. Thanks.

FYI. I changed POI config that it will build tests. It is better because tests cover complete API and there is no need to have the additional example.


feat: hidden highlights

simple implementation to add hidden highlights to oil entries
closes #329
example

This would be an awesome addition! I think one improvement I could suggest is also adding a highlight for a default "Hidden" highlight, so like OilHidden which links to Comment and then each of the other "Hidden highlight groups default link to that. Then it's easier to change the general case as well as have the ability to dive into more specific highlights!

good idea. added!

Thanks for the PR!


GetKeyboardLayout is not updated during a console session

From @matial on August 13, 2017 21:0

Your Windows build number:  version 10.0.14393

Calling GetKeyboardLayout(0) periodically within a console application returns the handle of the keyboard layout active when starting the console. If the keyboard layout is changed while the console app is running, subsequent calls to GetKeyboardLayout do not reflect the new active layout.

What's wrong / what should be happening instead: GetKeyboardLayout should return the handle of the last activated keyboard layout.

Copied from original issue: Microsoft/WSL#2418

From @sunilmut on August 16, 2017 16:41
@matial - Thanks for your post. Is this a WSL/bash on Windows specific issue? Looks like a concern with the generic console API.

From @matial on August 16, 2017 18:44
@sunilmut - Yes it is a generic console API problem.

GetKeyboardLayout is a user32 thing... not specifically a console thing. We might need to hand this off to a different team via an internal issue.

not specifically a console thing

There's an undocumented functiton GetConsoleKeyboardLayoutNameW in kernel32.dll, available at least since Windows 2000.
Despite being undocumented, it worked as expected until Windows 10.
And it still works as expected in legacy console mode.
In default mode, however, it now returns false and sets the last error to 16385 :(
If it's too hard to implement GetKeyboardLayout properly, can at least GetConsoleKeyboardLayoutNameW be fixed please? (undocumented == no guarantees, I know, but still).
Or maybe knowing how it works can help fixing GetKeyboardLayout?


substrate-bindings(feat): improve descriptors

During runtime we need to know the arity of the function that we are dealing with. This is most important when it comes to building the different possible storage calls. So, yeah, I missed that.

how would i get the length during codegen?

It's just the size property of the directDependencies of the relevant codec.
For instance, for knowing the arity of the Identity.IdentityOf storage descriptor you could do this:
const declarations: CodeDeclarations = {
  imports: new Set(),
  variables: new Map(),
}

const { buildStorage } = getStaticBuilder(metadataV14, declarations);

const identityOf = buildStorage("Identity", "IdentityOf");

const identityOfArity = declarations.variables
  .get(identityOf.key)!
  .directDependencies
  .size;

FYI: I have no tested this code, but I'm pretty confident that it works.


Dont crash on nil in LOGICAL_OR and LOGICAL_AND

Closes #186

Codecov Report

Merging #187 (b9ff4b4) into main (961ce06) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #187   +/-   ##
=======================================
  Coverage   46.39%   46.39%
=======================================
  Files          47       47
  Lines       17828    17834    +6
=======================================
+ Hits         8271     8274    +3
- Misses       8111     8113    +2
- Partials     1446     1447    +1

Thank you for your contribution !! LGTM 👍