atmos: 1.8.2 -> 1.10.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cloudposse/atmos/releases.
meta.description for atmos is: "Universal Tool for DevOps and Cloud Automation (works with terraform, helm, helmfile, etc)"
meta.homepage for atmos is: "https://atmos.tools"
meta.changelog for atmos is: "https://github.com/cloudposse/atmos/releases/tag/v1.9.1"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.9.1 with grep in /nix/store/bb7z3ypaz9ykmybqkn12q2wjvc1ja093-atmos-1.9.1
found 1.9.1 in filename of file in /nix/store/bb7z3ypaz9ykmybqkn12q2wjvc1ja093-atmos-1.9.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
atmos

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bb7z3ypaz9ykmybqkn12q2wjvc1ja093-atmos-1.9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A atmos https://github.com/r-ryantm/nixpkgs/archive/82d2ef5465b3125568d92a09071d2661270b7b49.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bb7z3ypaz9ykmybqkn12q2wjvc1ja093-atmos-1.9.1
ls -la /nix/store/bb7z3ypaz9ykmybqkn12q2wjvc1ja093-atmos-1.9.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

atmos

Maintainer pings
cc @nitrocode for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cloudposse/atmos/releases.
meta.description for atmos is: "Universal Tool for DevOps and Cloud Automation (works with terraform, helm, helmfile, etc)"
meta.homepage for atmos is: "https://atmos.tools"
meta.changelog for atmos is: "https://github.com/cloudposse/atmos/releases/tag/v1.10.0"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.10.0 with grep in /nix/store/kj0h0q7yx9b59lpijzw8cr57q0pvs4i9-atmos-1.10.0
found 1.10.0 in filename of file in /nix/store/kj0h0q7yx9b59lpijzw8cr57q0pvs4i9-atmos-1.10.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
atmos

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kj0h0q7yx9b59lpijzw8cr57q0pvs4i9-atmos-1.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A atmos https://github.com/r-ryantm/nixpkgs/archive/ea1d9b115c9c006304934e2daf410b0b82da54bb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kj0h0q7yx9b59lpijzw8cr57q0pvs4i9-atmos-1.10.0
ls -la /nix/store/kj0h0q7yx9b59lpijzw8cr57q0pvs4i9-atmos-1.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

atmos

Maintainer pings
cc @nitrocode for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cloudposse/atmos/releases.
meta.description for atmos is: "Universal Tool for DevOps and Cloud Automation (works with terraform, helm, helmfile, etc)"
meta.homepage for atmos is: "https://atmos.tools"
meta.changelog for atmos is: "https://github.com/cloudposse/atmos/releases/tag/v1.10.1"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.10.1 with grep in /nix/store/xmm12xhk1yr6cxd3gw57v9pj2xcafw7r-atmos-1.10.1
found 1.10.1 in filename of file in /nix/store/xmm12xhk1yr6cxd3gw57v9pj2xcafw7r-atmos-1.10.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
atmos

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xmm12xhk1yr6cxd3gw57v9pj2xcafw7r-atmos-1.10.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A atmos https://github.com/r-ryantm/nixpkgs/archive/8763e76e3805065fb562b770df8c87066a549266.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xmm12xhk1yr6cxd3gw57v9pj2xcafw7r-atmos-1.10.1
ls -la /nix/store/xmm12xhk1yr6cxd3gw57v9pj2xcafw7r-atmos-1.10.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

atmos

Maintainer pings
cc @nitrocode for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cloudposse/atmos/releases.
meta.description for atmos is: "Universal Tool for DevOps and Cloud Automation (works with terraform, helm, helmfile, etc)"
meta.homepage for atmos is: "https://atmos.tools"
meta.changelog for atmos is: "https://github.com/cloudposse/atmos/releases/tag/v1.10.2"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.10.2 with grep in /nix/store/4m7gnzja2l697hq2ark0q7ijv8pbf3z8-atmos-1.10.2
found 1.10.2 in filename of file in /nix/store/4m7gnzja2l697hq2ark0q7ijv8pbf3z8-atmos-1.10.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
atmos

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4m7gnzja2l697hq2ark0q7ijv8pbf3z8-atmos-1.10.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A atmos https://github.com/r-ryantm/nixpkgs/archive/0c5009255db04194ef1b472f0fbb415864bf93f3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4m7gnzja2l697hq2ark0q7ijv8pbf3z8-atmos-1.10.2
ls -la /nix/store/4m7gnzja2l697hq2ark0q7ijv8pbf3z8-atmos-1.10.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

atmos

Maintainer pings
cc @nitrocode for testing.


i18n(fr): update index

Description
This PR updates the French version of the homepage with the changes from ##2671.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
index.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Add a path argument to dataLayer.getState()

We'd like to target a specific object in the data layer state by passing its path. E.g.:
dataLayer.getState("component.carousel.carousel1")

Fixed.


Failed to fetch libraries

PLex URL and tocked fetched but after these its showing "failed to fetch laibraries"

Please add logs.

INFO:utils.plex_service:Parameters - URL: True, Token: True, Libraries: []
INFO:utils.plex_service:Using ENV for PLEX_MOVIE_LIBRARIES
INFO:utils.plex_service:Connecting to Plex server at <IP_ADDRESS>
ERROR:utils.plex_service:Failed to connect to Plex server: Invalid URL '<IP_ADDRESS>/': No scheme supplied. Perhaps you meant https://<IP_ADDRESS>/?
ERROR:movie_selector:Failed to initialize Plex service: Invalid URL '<IP_ADDRESS>/': No scheme supplied. Perhaps you meant https://<IP_ADDRESS>/?
INFO:movie_selector:Jellyfin service is not configured
INFO:movie_selector:Overseerr service is disabled or not configured
INFO:utils.overseerr_service:Overseerr service not initialized - missing configuration or disabled
INFO:movie_selector:Services initialization complete:
INFO:movie_selector:- Plex: False
INFO:movie_selector:- Jellyfin: False
INFO:movie_selector:- Overseerr: False
INFO:movie_selector:- Trakt: False
INFO:utils.settings.routes:Services reinitialization successful
INFO:utils.settings.routes:Settings saved to disk
INFO:utils.settings.routes:Checking field plex.url for ENV control
INFO:utils.settings.routes:Settings updated successfully for category plex
INFO:utils.settings.routes:Media service settings changed, will reinitialize services
INFO:movie_selector:Settings loaded - Homepage Mode: False
INFO:movie_selector:Service availability - Plex: True, Jellyfin: False
INFO:movie_selector:Initializing TMDB service...
INFO:utils.tmdb_service:TMDB service initialized
INFO:movie_selector:TMDB service initialized successfully
INFO:movie_selector:Starting services initialization
INFO:movie_selector:Current settings state:
INFO:movie_selector:Initializing Plex service...
INFO:utils.plex_service:Initializing PlexService
INFO:utils.plex_service:Parameters - URL: True, Token: True, Libraries: []
INFO:utils.plex_service:Using ENV for PLEX_MOVIE_LIBRARIES
INFO:utils.plex_service:Connecting to Plex server at <IP_ADDRESS>:32400
ERROR:utils.plex_service:Failed to connect to Plex server: No connection adapters were found for '<IP_ADDRESS>:32400/'
ERROR:movie_selector:Failed to initialize Plex service: No connection adapters were found for '<IP_ADDRESS>:32400/'
INFO:movie_selector:Jellyfin service is not configured
INFO:movie_selector:Overseerr service is disabled or not configured
INFO:utils.overseerr_service:Overseerr service not initialized - missing configuration or disabled
INFO:movie_selector:Services initialization complete:
INFO:movie_selector:- Plex: False
INFO:movie_selector:- Jellyfin: False
INFO:movie_selector:- Overseerr: False
INFO:movie_selector:- Trakt: False
INFO:utils.settings.routes:Services reinitialization successful
INFO:utils.settings.routes:Settings saved to disk
INFO:utils.settings.routes:Checking field plex.movie_libraries for ENV control
INFO:utils.settings.routes:Settings updated successfully for category plex
INFO:utils.settings.routes:Media service settings changed, will reinitialize services
INFO:movie_selector:Settings loaded - Homepage Mode: False
INFO:movie_selector:Service availability - Plex: True, Jellyfin: False
INFO:movie_selector:Initializing TMDB service...
INFO:utils.tmdb_service:TMDB service initialized
INFO:movie_selector:TMDB service initialized successfully
INFO:movie_selector:Starting services initialization
INFO:movie_selector:Current settings state:
INFO:movie_selector:Initializing Plex service...
INFO:utils.plex_service:Initializing PlexService
INFO:utils.plex_service:Parameters - URL: True, Token: True, Libraries: Movies
INFO:utils.plex_service:Connecting to Plex server at <IP_ADDRESS>:32400
ERROR:utils.plex_service:Failed to connect to Plex server: No connection adapters were found for '<IP_ADDRESS>:32400/'
ERROR:movie_selector:Failed to initialize Plex service: No connection adapters were found for '<IP_ADDRESS>:32400/'
INFO:movie_selector:Jellyfin service is not configured
INFO:movie_selector:Overseerr service is disabled or not configured
INFO:utils.overseerr_service:Overseerr service not initialized - missing configuration or disabled
INFO:movie_selector:Services initialization complete:
INFO:movie_selector:- Plex: False
INFO:movie_selector:- Jellyfin: False
INFO:movie_selector:- Overseerr: False
INFO:movie_selector:- Trakt: False
INFO:utils.settings.routes:Services reinitialization successful
INFO:utils.settings.routes:Settings saved to disk
INFO:utils.lgtv_discovery:arp-scan output:
INFO:utils.lgtv_discovery:Interface: eth0, type: EN10MB, MAC: 02:42:ac:11:00:0a, IPv4: <IP_ADDRESS>
Starting arp-scan 1.10.0 with 65536 hosts (https://github.com/royhills/arp-scan)
<IP_ADDRESS>      02:42:b5:8f:7f:2d       (Unknown: locally administered)
<IP_ADDRESS>      02:42:ac:11:00:02       (Unknown: locally administered)
<IP_ADDRESS>      02:42:ac:11:00:03       (Unknown: locally administered)
<IP_ADDRESS>      02:42:ac:11:00:04       (Unknown: locally administered)
<IP_ADDRESS>      02:42:ac:11:00:05       (Unknown: locally administered)
<IP_ADDRESS>      02:42:ac:11:00:06       (Unknown: locally administered)
<IP_ADDRESS>      02:42:ac:11:00:07       (Unknown: locally administered)
<IP_ADDRESS>      02:42:ac:11:00:08       (Unknown: locally administered)
<IP_ADDRESS>      02:42:ac:11:00:09       (Unknown: locally administered)
<IP_ADDRESS>      02:42:b5:8f:7f:2d       (Unknown: locally administered) (DUP: 2)
<IP_ADDRESS>      02:42:b5:8f:7f:2d       (Unknown: locally administered) (DUP: 3)
<IP_ADDRESS>      02:42:b5:8f:7f:2d       (Unknown: locally administered) (DUP: 4)
<IP_ADDRESS>      02:42:b5:8f:7f:2d       (Unknown: locally administered) (DUP: 5)
<IP_ADDRESS>      02:42:b5:8f:7f:2d       (Unknown: locally administered) (DUP: 6)
14 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.10.0: 65536 hosts scanned in 263.605 seconds (248.61 hosts/sec). 9 responded
INFO:movie_selector:Scan complete. Found 0 LG devices

If you use the plex Ip you need to specify the plex port as well.
http://<IP_ADDRESS>:32400

Yes. Please use fqdn for https or ip for http


double slash fix

This fixes parsing of uri like sql:///?q=sql-query&var.foo=bar
I need this in SD-1115 for configure view mount buttons.
@jonsterling please, review

@cryogenian Does this break any existing use-cases of this library?
Maybe we should allow the user to decide whether to parse the slashes, since they are required in some schemes and not in others.

Or another option would be to make that decision within the library, depending on what scheme was parsed.

Hm, I've just run tests w/o errrors, but you're right this isn't very good idea.
I'll look at this a bit more carefully on Monday.
Thank you!


Update setup-vs-code-extension.md

It took me a while to finally get this working, after finding on another site that the Script subfolder for miniconda3 is needed to get things working. So this documentation was incomplete.  I changed the documentation to include the Scripts subfolder.
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.

Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.

For internal Microsoft contributors, check off these quality control items as you go

[ ] 1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.

[ ] 2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).

[ ] 3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.

[ ] 4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.

[ ] 5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing #sign-off in a new comment in the Pull Request. If you need to cancel that sign-off, type #hold-off instead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.

Merge and publish

After you #sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.
The review team will use the comments section in the PR to provide feedback if changes are needed. Address any blocking issues and sign off again to request another review.
Once all feedback is resolved, you can #sign-off again. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).
From the main branch, the change is merged into the live branch several times a day to publish it to the public learn.microsoft.com site.

@qixwang
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Add transformed results to meta

I want some way to add random items with current request ( data ), so I decided to add them in Meta.
$randomItems = $this->collection(Item::orderByRaw('RAND()')->limit(5)->get(), new ItemTransformer($request));

return $this->response->paginator($collections, new ItemTransformer($request))
            ->setMeta([
                'random_items' => $randomItems
            ]);

But somehow I get result like this, which is including Original data and not the transformed one.

Will be great if you can help in this.

Meta doesn't isn't transformed. It's just meta data.
If you want to add associated resources then possibly look at Fractal includes.


Add vSphere deployment documentation in kubernetes-anywhere

Customers can have varying configuration like multiple vCenters etc. We currently doesn't support that configuration. This should be documented.

vSphere cloud provider will support multi VC/datacenter once #173 is addressed.
We have no plans to add this feature in kubernetes-anywhere at this point.


working on 2.2.chat - session ( one user per browser )

for now chat is working, but there are on disadvantages, I show the following in the checklist :

[ ] save username in session
[ ] so everytime user open web, check session first, if username available auto login.
[ ] save session in cookie

project dir https://github.com/yussan/exploration-socket.io/tree/master/2.2.chat - session ( one user per browser )

Hi, I'd like to tackle this. Is it alright if I use the js-cookie package in order to simplify cookie operations?

thanks, go ahead


yt/docker/ya-build: build ytserver first

Could you provide some motivation about this change?

This helps to get complation error sooner (40 vs 90 minutes). Node is developers much more actively.

Ok, I get it


Add DRF middleware for channels authentication

This is an extension of django channels AuthMiddleWare to support authentication by settings.AUTHENTICATION_BACKEND.
It is originally need by EDA for websocket authentication. An internal discussion suggested to submit this code to django-ansible-base.
Source code mainly contributed by @mkanoor

See https://github.com/ansible/eda-server/pull/540 for an example of how this works.

dropped minor comments, otherwise looks good to me


List of changes from original symbols-outline before fork detach, and related issues from upstream

Fixes

Extra padding/indent on left on outline window removed. Fixed issues:

simrat39/symbols-outline.nvim#165
simrat39/symbols-outline.nvim#178
simrat39/symbols-outline.nvim#209

Symbol preview empty (simrat39/symbols-outline.nvim#176)
OutlineClose crashing when already closed: simrat39/symbols-outline.nvim#163
Symbols not showing by supporting Nerd fonts v3.0: simrat39/symbols-outline.nvim#225
Newlines in symbols crash: simrat39/symbols-outline.nvim#204 (simrat39/symbols-outline.nvim#184)
code_actions: simrat39/symbols-outline.nvim#168 (simrat39/symbols-outline.nvim#123)
Fold all operation too slow: simrat39/symbols-outline.nvim#223 (simrat39/symbols-outline.nvim#224)
"Invalid buffer id" error simrat39/symbols-outline.nvim#177
Open handler triggering multiple times ends up in messy state with errors simrat39/symbols-outline.nvim#235
Fixed _highlight_current_item function checking provider on outline window
Fixed behaviour of empty markdown headings ^(#+)(%s+)$ being listed in the outline.

🛑 Breaking changes
The fork has been renamed to outline.nvim for the following reasons:

While symbols-outline is a great name, using SymbolsOutline* everywhere as a prefix for commands and highlight groups is quite long to type.
I did not find existing plugins that use the outline import path.
The only plugin I could find named outline.nvim does not use this import path.
This is a fork starting anew, it makes sense to undergo a rename.

Regardless of this rename, I am eternally grateful to @simrat39 for their work in the original symbols-outline.nvim. This plugin would not exist without it.
What this means for you:

Commands and highlights that had the SymbolsOutline* prefix should now use Outline*
The import path should be changed from symbols-outline to outline

That is all.
Here are other breaking changes:
This section may be relevant to you if your existing config uses the mentioned features:

Config: Configuration options have been significantly restructured to
provide better consistency and understandability. Please see the default config for an example of the full list.

Options that control the looks and behaviour of outline window is now moved to outline_window table;
Options that control the items that show up are now in outline_items
Options for the preview window is in preview_window.
Symbol icons are now in symbols.icons, symbol blacklists are in symbols.blacklist
Lsp blacklists are now in providers.lsp.blacklist_clients.
Fold options are now in symbol_folding with fold_markers being symbol_folding.markers, consistent to guides.markers.

The reasoning for the above is simple. When you see 'border' under preview_window you can directly infer it controls the border for the preview window. Previously, for example, when you see winblend or wrap: is it for the outline window or the preview window? Furthermore, this change also aids extensibility to the configuration, and avoids cluttering the root setup opts namespace.
If you disagree with this decision, you are always free to switch back to the original symbols-outline.nvim, or you could pin a commit in this fork if you still want to use the features and fixes from here.

Config: keymaps.focus_location RENAMED to keymaps.peek_location to avoid confusion with focus window commands.

Config: Marker icons used for guides can now be customized. show_guides REMOVED in favor of guides.enabled.
You can set guides = false to disable guides altogether, or set guides = true to enable it but use default configuration for the guides. Otherwise, please use guides.enabled if your configuration for guides is a table.

Behaviour: Removed hover floating window from toggle_preview.

Instead, you can set open_hover_on_preview=true (true by default) so that the hover_symbol action can be triggered when toggle_previewis triggered.
The preview window's size changed to half of neovim height (rather than a third). This is planned to be configurable.
The preview window is positioned to be vertically center-aligned (rather than fixed to the top). This is planned to be configurable.

Behaviour: When auto_close=true only auto close if goto_location is used (where focus changed), and not for focus_location (simrat39/symbols-outline.nvim#119).

Behaviour: For auto_preview=true, previously preview is only shown after some delay. Now preview is shown instantly every time the cursor moves.

Features
Below is a list of features I've included in this fork which, at the time of writing, has not been included upstream (in the original repo). I try my best to keep this list up to date.
Features/Changes:

Toggling folds (and added default keymaps for it) (simrat39/symbols-outline.nvim#194).

Control focus between outline and code window.

New commands: OutlineFocus,FocusOutline,FocusCode (see
commands
Fixed issues:

simrat39/symbols-outline.nvim#143
simrat39/symbols-outline.nvim#174
simrat39/symbols-outline.nvim#207

Show line number of each symbol in outline window (see recipes for a screenshot)

Fixed issues: simrat39/symbols-outline.nvim#212

Cursorline option for the outline window.

Added function and command to show provider and outline window status, somewhat like :LspInfo.

Move down/up by one line and peek_location immediately, default bindings are <C-j> and <C-k> just like Aerial.

Flash highlight when using goto/peek location.

Auto jump config option (see config auto_goto) (simrat39/symbols-outline.nvim#229, simrat39/symbols-outline.nvim#228).

New Follow command, opposite of goto_location/focus_location

New restore location keymap option to go back to corresponding outline location synced with code (see config restore_location).

Outline/Preview window border/background/winhighlight configuration. (simrat39/symbols-outline.nvim#136). See outline_window.winhl, preview_window.winhl, preview_window.*width options.

All highlights used including the virtual text for symbol details and symbol lineno are now fully customizable using outline_window.winhl. See highlights.

Option to blend cursor with cursorline (outline_window.hide_cursor)

Option to use lspkind for icons, and use your own fetcher function. See config and tips sections in the readme.

Option for outline window split command

Screen recordings/shots of some of the features is shown at the bottom of the readme.
PRs
Key:
✅ = Either merged superseded
📮 = Planned for merge

📮 center view on goto symbol
(#239 by skomposzczet)

Distinguish between public and private function display in Elixir
(#187 by scottming)

Floating window (Draft)
(#101 by druskus20)

Show completed PRs

✅ Open handler checks if view is not already open
(#235 by eyalz800)

✅ auto_jump config param
(#229 by stickperson)
Renamed to auto_goto for consistency

✅ Update nerd fonts to 3.0
(#225 by anstadnik)

✅ fix(folding): optimize fold/unfold all
(#223 by wjdwndud0114)

✅ Support markdown setext-style headers
(#222 by msr1k)

✅ fix(icons): replace obsolete icons
(#219 by loichyan)
Superseded by #225

✅ Support ccls symbols
(#218 by rqdmap)

✅ fix: replace newlines with spaces in writer
(#204 by tbung)

✅ Make close_outline idempotent
(#200 by showermat)
Superseded by #163

✅ Fix some options
(#180 by cljoly)

✅ fix: Invalid buffer id error
(#177 by snowair)

✅ fix(code_actions): use the builtin code_action
(#168 by zjp-CN)

✅ fix: plugin crashes when SymbolOutlineClose used
(#163 by beauwilliams)

✅ feat: Add window_bg_highlight to config
(#137 by Zane-)
Improved implementation

✅ Added preview width and relative size
(#130 by Freyskeyd)
Improved upon and refactored with new config structure

✅ Improve preview, hover windows configurability and looks
(#128 by toppair)
Improved upon and refactored with new config structure

✅ Do not close outline when focus_location occurs
(#119 by M1Sports20)

✅ feat: instant_preview
(#116 by axieax)
Superseded with an improved implementation

✅ check if code_win is nill
(#110 by i3Cheese)
Superseded before this fork was created
(perhaps the PR was forgotten to be closed)

(66aecc7) Algorithms in parser and writer modules have been rewritten for better performance

Since github support has now detached my fork from symbols-outline.nvim, new changes from now on will be in CHANGELOG.md.


Object without format placeholder will not shows on StackDriver Log Viewer

Environment details

OS: macOS 10.13.2
Node.js version: v8.9.3
npm version: 5.6.0
@google-cloud/logging-winston version: v0.7.0

Steps to reproduce

Just use the following codes:

const winston = require('winston');
const LoggingWinston = require('@google-cloud/logging-winston');

const Console = winston.transports.Console;
const loggingWinston = new LoggingWinston({
  projectId: 'nova-gcp-development-testing',
  keyFilename: path.join(
    __dirname,
<EMAIL_ADDRESS>  ),
});

const sklogger = new winston.Logger({
  level: 'debug',
  transports: [new Console(), loggingWinston],
});

const str1 = 'String 1';
sklogger.debug('string with format: %s', str1);
sklogger.debug('string without format:', str1);

const num1 = 100;
sklogger.debug('number with format: %d', num1);
sklogger.debug('number without format:', num1);

const float1 = 100;
sklogger.debug('float with format: %d', float1);
sklogger.debug('float without format:', float1);

const obj1 = { key1: '1', key2: 2 };
sklogger.debug('object with format: %j', obj1);
sklogger.debug('object without format:', obj1);

Execute the codes
Go to GCP console and inspect StackDriver Log Viewer

It shows normally in Console:

But not excepted in StackDriver Log Viewer:

Is this normal ?
Also is it possible to change the option for LoggingWinston() without changing the source code to solve this problem ?

I think this is normal.
The object was on the metadata in jsonPayload that ok for me and I don't want it to show on message

So it looks like this issue can be closed.  However, @phantomnat I would think having [Object] or something similar listed in the message (with the object in the metadata) would be better than having nothing in the message.  However, before making that change, I would like to get your feedback if that change is necessary.  Thanks.

@DominicKramer I agree with that at least having some message better than nothing.
I just want to output is as same as the Winston (which this package built for).
So that people don't need to learn / remember the Winston and logging-winston are output differently.

@DominicKramer Yeah, I think so. It would be better to have something show on the output.

Also seeing an issue logging messages that contain an array in the metadata, for example:
logger.info("TEST", [{ foo: "bar" }])

does not render any metadata stackdriver output.
I would expect something like
jsonPayload: { message: "TEST", metadata: { '0': { foo: 'bar'} } }

and more control over the util.inspect depth

To be in alignment with Winston 3 and to avoid having duplicate data in log messages, I think it would be best to not use the implementation in PR #159, and to close this issue as expected behavior.


Split documentation

ReadMe.MD is becoming too large to be useful... tl;dr
Need to split this into a quick 'overview'/'cheat cheat'/'example' page and multiple 'deeper dive' documents/examples...

We can start to utilize the docs app to help with this by breaking the files down to sections and loading them up from aurelia/validation/docs (while still letting them stay here in the github repo)

Tracking on task list at https://github.com/aurelia/validation/issues/174


Why is MRMO on this list?

No shade, but people are allowed to make certain aspects about their own material available. Mrmo made it clear that they didn't want their tool "MRMO-HALFTONE" to be used for NFT's or anything crypto-related. So, it's at least better for you to respect people's decisions on making things available for certain aspects instead of calling them out for not making it fully available (at least be happy that it's available and you can use it).
Again, I don't mean to be rude or anything (and don't take this the wrong way), but doing stuff like this is just immature.

I clarified that the intent is not the issue here in https://github.com/ErikMcClure/bad-licenses/commit/e948021240eee08a5efee96f0fedd8c6a90acf6a, it's the language being used. For example, Git is based on a merkle tree where the hashes of each successive commit need to be based on the previous hash of the previous commit. This could be considered a "blockchain", minus proof of work. Because there is no legal definition of "blockchain", you could sue anyone using Git for this, including the author of the license themselves. Likewise, NFTs are not actually well-defined. The concept of an NFT is different from the scams being implemented on smart contracts are the actual thing people have issues with.
The reason licenses get into the "bad licenses" club is because they try to use non-legal terms in a legal context, because they are written by programmers instead of lawyers.


Stop producing line and file debug information for clang::Decls.

It would be nice to query the clang::SourceManager for the source
location of the clang::Decl in IRGenDebugInfo, but module out-of-date
rebuilds may unload previously loaded clang::Modules and thus also
invalidate source locations pointed to, leading to a use-after-free
here. If this functionality is desired, the source location must be
captured by ClangImporter and stored on the side.
LLDB does not actually make use of this information for non-C++ types
(it is really helpful with debugging the debug info itself, though),
so we can avoid the potential use-after-free and crash by not doing it.
rdar://problem/48509051

@swift-ci test


User Interviews from Our Walmart

Waiting to hear back from Our Walmart to plan user interviews with low-wage workers

Job seekers


Medium Zoom stops working if I refresh the page within vue remark content, But works everywhere else

Description
I am trying to use medium zoom in my project with vue remark. Medium zoom works perfectly for any g-image's in any component.
When I try to use that in the markdown. It works if it is rebuilding the component. But when I refresh the page, zoom stops working.
I change something in the Article.vue to re-render the page. But after refresh the page, it stops working for the images in vueremark content.
changing something like this in my file.
mounted() {
    mediumZoom("img", {
      margin: 40
    });
  }

Environment
   "@gridsome/vue-remark": "^0.2.0",
    "gridsome": "^0.7.0",
    .....
    "medium-zoom": "^1.0.5",
    ....

** It is worth mentioning that it works perfectly when used with source filesystem and transformer remark. I checked it. Because we get HTML content from the graphql, so medium zoom is able to capture that image successfully.***
Any help would be appreciated. Been trying to figure it out for 3 days. It might be the problem with how vue remark renders the markdown.
Thanks in advance.

Same thing happening for me with dynamic routing!  I tried using gridsome a while back and this same bug happened.  Never figured it out and just quit.  Now, I just built a whole portfolio + blog with gridsome and this bug is KILLING me!  No help on my issue, but if you want to see it go to https://github.com/gridsome/gridsome/issues/1145

Well, I found a crappy fix, if you add in the following code into your layout script used for the broken pages it will fix it, kind of.
mounted() {
    let currentURL = window.location.pathname;
    // console.log(currentURL);
    setInterval(function() {
      if (currentURL !== window.location.pathname) {
        location.reload();
      }
    }, 250);
  }

Could it be because the child-component, i.e. the content-outlet for the rendered Markdown, hasn’t
loaded yet when mounted() is called? Have you tried wrapping your call to medium-zoom in a
this.$nextTick()?

@amxmln Thanks for the Idea. Even though it didn't work. It pushed me in the right direction. To cut it short, you need to put that in both mounted() and updated(). It just works.
When I register the medium zoom in updated(), it won't work for when we come from any other page to the current page. In order to work, you need to refresh it. And it is clearly opposit for if we register zoom in mounted(). ie., it works if we come from a different page. But it doesn't work if we refresh the page.
To solve this, I just put that in both places
.....

mounted() {
    // when we revisit the page, we need to register it
    mediumZoom("img");
  },
  updated() {
    // register everytime we refresh the page..
    mediumZoom("img");

....
  }

For the images outside of the Vueremark content, it works regardless.
I think the reason is similar to what @amxmln mentioned. The Vue remark content is not available. transformer remark stores HTML in the Graphql and therefore no issue. And I think Vue remark is a component that renders a Json. Maybe this is the reason for the odd behaviour.
Anyway, thanks once again @amxmln. Couldn't have done without you.


[Compute] Dedicated host group automatic placement

Description

Resolve https://github.com/Azure/azure-cli/issues/14056
New parameter --automatic-placement in vm host group create
    --automatic-placement            : Specify whether virtual machines or virtual machine scale
                                       sets can be placed automatically on the dedicated host group.
                                       Automatic placement means resources are allocated on
                                       dedicated hosts, that are chosen by Azure, under the
                                       dedicated host group. The value is defaulted to true when not
                                       provided.  Allowed values: false, true.

New command vm host group get-instance-view

"supportAutomaticPlacement" is a new property introduced under DedicatedHostGroup.properties. Customers can specify either true or false. It defaults to true, if no input is provided. If a dedicated host group has automatic placement enabled, VMs or VMScaleSets can be placed on the dedicated host group using automatic placement.
GET dedicated host group now supports instance view query parameter. Dedicated host group instance view will return instance view of the dedicated hosts under the dedicated host group.
"hostGroup" is a new property introduced under VM.properties and VMScaleSet.properties. The input should be the resource id of the dedicated host group, on which the customer wants his VM/VMScaleSet placed using automatic placement.
"assignedHost" is a new property introduced under VMInstanceView and VMScaleSetVMInstanceView. It is the resource id of the dedicated host, on which the queried VM/VMScaleSetVM is placed using atuomatic placement.

Testing Guide

History Notes

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

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

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

[ ] I adhere to the Command Guidelines.

Compute

thanks @qwordy ,  excellent PR description to detail problems and changes!
after learning host, host group and (service change)[https://github.com/Azure/azure-cli/issues/14056], I propose below change. It's not necessary to be a breaking change, since meaning of host-group param not change: it means the host group this VM would like to go into. Pls have a look and check does it make sense to you, we can have discussion offline also.
My proposal:

keep host, host-group params.
change the logic to below

if --host is name
-- host-group is name, then it's existing usge: host-group+ host is used to specific host
-- host-group is id, throw error.

if --host is id
-- host-group is name, throw error. host is enough to specific host, no need of host-group.
-- host-group is id, throw error. same as above

if --host is None and --automatic-placement true
-- host-group is name, it will be VM.host
-- host-group is id, it will be VM.host

if --host is None and --automatic-placement false
-- host-group is name, error
-- host-group is id, throw error.

Very clear! --host-group has multiple meanings now. Will it be a burden for user to understand?

Very clear! --host-group has multiple meanings now. Will it be a burden for user to understand? I need to think about how to write help for --host-group.

valid concern :) let's work together to see any better way


The app doesn't update JMBG when updating data of medical insurance

JMBG can change! :) Update it if you know how to do it please.

The public API that Bas Celik uses doesn't provide an information about persons JMBG. Even if it did, I suspect medical insurance card would be valid after JMBG change.
Can you describe why you brought this issues, because JMBG could be changed only in few (very rare) situations. Did you encountered JBMG change?

I see. Thanks for bringing this up. Unfortunately, the public API doesn't have information about JMBG.


Allow 'filter' option in keybinding registry

Would you consider having a 'filter' option in the keybinding registry to allow users to be more strict on what is allowed as a key sequence?
app-model is pretty open on what is considered a valid, but users may want to:

not allow certain KeyCodes
not allow certain KeyCombos - e.g., modifier only key combos, which you were also against supporting (in napari) here: https://github.com/napari/napari/issues/5747#issuecomment-1515301910,

also app-model allows multiple modifiers (e.g., 'alt+alt', 'alt+alt+alt'),  which we may (?) want to not support. I can't quite tell if this is problematic only with napari legacy code but Kira did implement a function to de-duplicate (I do know that these two result in the same int, though alt by itself is a different int)

I'm also okay with implementing downstream if you don't think it belongs in app-model
cc @dragadoncila

where would the filter be applied?  at the moment of registration?  at the moment of keybinding definition?

at the moment of registration?

This is what I would imagine? Say, in register_keybinding_rule after validate? Or perhaps with a custom validator?

Yes that's what I was thinking too but open to any suggestions you may have @tlambert03

it does seem reasonable to me that app-model itself would allow an app to regulate what it allows as a valid keybinding, so I'm open to that for sure.  i think the biggest question in my mind is the API.   We could add a line to register_keybinding_rule, but where exactly should we parametrize it?  If added a parameter to register_keybinding_rule() itself how do you guys imagine providing your preferences on the napari side?    There's many options, including you would instantiate your top level app with a custom KeyBindingsRegistry subclass (which, you could already do now), or it could be done at a couple other levels.  Could you guys have a look at the options and propose what you think is a nice pattern that allows a user of app-model to express a constraint?

What do you think about having a KeyBindingsRegistry 'filter' attribute (that defaults to None) that the user can set on app init?
KeyBindingsRegistry.filter would then be passed on to register_keybinding_rule.
It would be similar to what is happening here with the injection_store.namespace so there is precedence.
Similar schema to what you describe here: https://github.com/pyapp-kit/app-model/issues/169#issuecomment-1860480748

sure, that works for me.  so what would filter be?  Callable[[KeyBindingRule], bool] ?

Certainly Callable - I am envisioning that the function will raise an error if the key sequence is not valid.
Anything else would be more complicated though possibly worthwhile, depending on use case.
We could have the user provide a list of KeyCodes, or KeyCombos to filter out (potentially via int ?). We could also allow the user to specify via bool whether modifier only key sequences are allowed. Though, in our case, I think we want to allow single modifier (e.g., ctrl as the use case is strong enough to warrant) - so this would not be useful (unless we want to allow further specification to allow single modifier but I think this is getting too complicated).

Certainly Callable - I am envisioning that the function will raise an error if the key sequence is not valid.

I think raising here would be strange if we name this a filter rather than a validator.

(alternatively Callable[[KeyBindingRule], str] ... where the str is a message to include in the exception explaining why it's not an acceptable keybinding?, and an empty string implies valid)

I like the idea of the message including which part of the keybinding failed and why. I imagine if we were to go with a bool, the first request we'd get is for a message

(alternatively Callable[[KeyBindingRule], str] ... where the str is a message to include in the exception explaining why it's not an acceptable keybinding?, and an empty string implies valid)

This is great, sorry I mis-read the typing.
The only snag here is that we may want app-model to give a warning in some instances instead of error, but we can go with YAGNI for now.


Tuple foreach fails when output has a comma

So I don't forget, tuple foreach needs to have its eval function changed to use __VA_ARGS__, just like list foreach

It wasn't even named properly!


Provide buildable source tarballs as release artifacts

This request comes from the .NET 8.0 Preview 1 release announcement.
The source tarballs Assets associated with the GitHub Release are not buildable.  In order to get a buildable source-tarball, you must use  ./eng/pack-source.sh.  To improve the distro maintainer workflow, .NET should provide a buildable source tarball.

There are some issues we should re-open (or re-examine) if we want to provide tarballs:

https://github.com/dotnet/source-build/issues/298
https://github.com/dotnet/source-build/issues/2927
https://github.com/dotnet/source-build/issues/2895

https://github.com/dotnet/source-build/issues/298 is a much older request for a tarball.
Besides the sources, this issue also talked about archiving the needed pre-built.
So then, when given a bootstrap SDK, the source tarball, and a prebuilts tarball, you'd have everything to do an offline build.
Such prebuilts archives would be per portable rid.
@ayakael mentioned ./eng/pack-source.sh is mostly about some git files:

those files are missing .git/HEAD and .git/config

For my understanding: why does source-build need these git files?

For sourcelink: https://github.com/dotnet/source-build/issues/3112#issuecomment-1359275858

For sourcelink: https://github.com/dotnet/source-build/issues/3112#issuecomment-1359275858

Yes, I was assuming that would be it.
The source-build based builds will refer to https://github.com/dotnet/dotnet for their sources then.
That won't include any local patches, but it would be accurate for most sources.

The source-build based builds will refer to https://github.com/dotnet/dotnet for their sources then.
That won't include any local patches, but it would be accurate for most source files.

The idea would be that distro maintainers would either push their patches upstream or create a downstream of the VMR with any customization applied and build from there.

@MichaelSimons I believe I can easily take care of this as I am working on the automation that will push the release+tag to dotnet/dotnet. That is, calling pack-sources.sh and appending the tarball to the release.
I will have to check whether I can get rid of the default assets and I need good naming for the new asset to make it clear which one is the one people should download.

We discussed this in triage a bit but ran out of time to finish.  The discussion was that it would be desirable to be able to build from a GitHub tarball/zip.  We know that isn't possible as is because of the sourcelink requirements.  A suggestion was made that if building outside the context of a git repo, we could have a way to specify a sha and url for sourcelink to utilize.  The build would then init a .git/HEAD and .git/config from these.
This approach has the benefit of being able to use the native constructs to produce the tarball versus the custom pack-sources.sh.

I think that sounds like a better solution maybe. It would be good if the build script checked for the existence of these and print a nicer error message too btw.
Btw, I just tried to publish a release from and it looks like this:

It would be good if the build script checked for the existence of these and print a nicer error message too btw.

Agree, I envision the build script considering these options required executed outside the context of a git repo.

@MichaelSimons I have already implemented appending the exported tarball amidst my current SB pipeline changes. We only need to settle on a suitable name for the attachment. I'd keep it there until we have a solution on SB infra's side?
It's now part of https://github.com/dotnet/source-build/pull/3276

Besides the sources, this issue also talked about archiving the needed pre-built.

I wonder if there is an interest in archives with pre-builts for the portable rids?
Without such a tarball, a bootstrap build starts by downloading nuget packages from the Internet.
It seems better for reproducibility to archive pre-builts too.
@omajid @ayakael what do you think? Is this something you consider useful?

Besides the sources, this issue also talked about archiving the needed pre-built.

I wonder if there is an interest in archives with pre-builts for the portable rids?
Without such a tarball, a bootstrap build starts by downloading nuget packages from the Internet.
It seems better for reproducibility to archive pre-builts too.
@omajid @ayakael what do you think? Is this something you consider useful?

I think it'd be useful in terms of making it explicit where to get the prebuilts. I remember when first packaging dotnet that it was harder than it should've been to find prebuilts as the link to them isn't explicitely put anywhere and then you had to dig around to find the version number (i.e. in eng/Version.Details.props)

[Triage] Unfortunately as noted in the preview 1 release announcement, the current state requires a rid specific prebuilts (no including the SDK or prevously source-built packages) that distro maintainer need to provide themselves.  This is to say we cannot provide the full set.  Ideally the best solution is to get to zero prebuilts as quickly as possible to address that problem.
We can start attaching the SDK, artifacts and prebuilts to the release.  This does require some changes to our CI process so that it produces and captures a bootstrap version of the artifacts.
The following is the work I see here.

[ ] Modified build.sh to take in a url and sha for the source to use by sourcelink.  If not provided require the build is executing in a git context and read the values from it.
[ ] Update the release pipeline to no longer generate the source tarball and attach it to the release.  We will use the sources attached by default.
[ ] Factor out the logic to generate a bootstrap artifacts from rid specific artifacts.  Invoke this at the end of CI so that we product the bootstrap artifacts with every build.
[ ] Modify the release pipeline to upload the new bootstrap artifacts to blob storage
[ ] Modify the release pipeline to attach the SDK, bootstrap artifacts and prebuilts to the release.

I felt like this issue is being overloaded.  I logged Provide release artifacts necessary to perform bootstrap build offline to cover the remaining discussed here.  I am therefore closing this issue.


Are 'Interests' the same as 'groupings'?

The README file has an example of subscribing a member to a list with specific interests. However, I am  confused by the terminology "interests." The MailChimp support document About Segments and Groups describes segments and groups. The JSON schema for List Members includes "Interests." Do you know whether this refers to Segments or Groups?
I've got Gibbon 2.0 code that looks like this:
      merge_fields: {:NAME => user.name,
                      :groupings => [{:name => 'AFFILIATION',
                                      :groups => ['some_list_group']
                                     }]

Does this get replaced by interests?

I asked MailChimp support to clarify. Here's what they said:
Interests in API 3.0 are Group Names in your List (the subgroups), and Categories are the Group Titles. Just like back in API 2.0 with Interest Groupings:
/lists/interest-groupings.format -v2.0
For example, if I have a Group Title Ice Cream Flavors and two Group Names Chocolate and Birthday Cake, that would mean that Ice Cream Flavors is the category for my API call, and Chocolate would be one of the interests.
We have some documentation that can help explain here:
List Interest Categories Instance
List Interests Instance

Yes. Interests is short for interest groups.
Thanks,
Amro
Sent from my iPhone

On Aug 19, 2015, at 3:19 AM, Daniel Kehoe<EMAIL_ADDRESS>wrote:
The README file has an example of subscribing a member to a list with specific interests. However, I am confused by the terminology "interests." The MailChimp support document About Segments and Groups describes segments and groups. The JSON schema for List Members includes "Interests." Do you know whether this refers to Segments or Groups?
I've got Gibbon 2.0 code that looks like this:
  merge_fields: {:NAME => user.name,
                  :groupings => [{:name => 'AFFILIATION',
                                  :groups => ['some_list_group']
                                 }]

Does this get replaced by interests?
—
Reply to this email directly or view it on GitHub.

Thanks for posting their response


chore(litmus-portal): Refactoring components + added routes to homepage and blog

Signed-off-by: Amit Kumar Das<EMAIL_ADDRESS>
What this PR does / why we need it: Refactoring components + added routes to homepage and blog
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Checklist

[ ] Does this PR have a corresponding GitHub issue?
[ ] Have you included relevant README for the chaoslib/experiment with details?
[ ] Have you added debug messages where necessary?
[ ] Have you added task comments where necessary?
[ ] Have you tested the changes for possible failure conditions?
[ ] Have you provided the positive & negative test logs for the litmusbook execution?
[ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
[ ] Have you used non-shell/command modules for Kubernetes tasks?
[ ] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
[ ] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
[ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
[ ] Do the artifacts follow the appropriate directory structure?
[ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
[ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
[ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
[ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
[ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
[ ] Can you suggest the minimal resource requirements for the litmusbook execution?
[ ] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
[ ] Has the litmusbooks been linted?

Special notes for your reviewer:

/preview 15

/preview 10

@Jonsy13 can you review the testing code

/preview 60

/preview 30

/preview

/preview


Enhance Metadata OSAllLocators query to fully utilize the pagination fields.

Summary
The Metadata module's OSAllLocatorsRequest message contains a cosmos.base.query.v1beta1.PageRequest message, but the module's query_server OSAllLocators method does not use the query.Paginate or query.FilteredPaginate methods. So not all pagination functionality is available on that query, e.g. pagination using a next_key and key.
Problem Definition
Most of the other paginated queries have full pagination support, so not having it here can cause confusion and frustration. Additionally, there's no way to know how many results there are without getting all of them.
Proposal
Refactor the Metadata module's OSAllLocators query to use either the query.Paginate or query.FilteredPaginate function in order to enable full pagination support.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

These issues are all similar:

#400
#401
#402


Can you give an example about handles

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

http://react-dnd.github.io/react-dnd/examples/customize/handles-and-previews


Alters not all visible on Q16

At first, only 12 alters were visible...as edges were created, I could see alters appearing on the bottom right corner. Sizing issues?

Another error warning...not sure if it applies to the issue.

I also realized that I cannot access the login page to make an account. It always directs me to the name generator. I closed the window and lost all the alters. Let me know if you need more info!

I'm still having issues with Q16. The alters float out of the field of view after making ties. Examples below:


infra: update golang version

Go 1.16 is end of support since 1.18 is released.

SGTM

SGTM, let's update it to 1.17.

I'm also thinking using generics to reduce code duplication for multi-version support.

How about we upgrade to 1.18?


Lazy Loading is kinda not working.

Version
4.5.4
Reproduction link
https://github.com/MisterJ936/MyPortFolio/tree/master/jenuelganawed_home
Environment info
 System:
    OS: Windows 10 10.0.19041
    CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - D:\Program Files\yarn\bin\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 85.0.4183.83
    Edge: Spartan (44.19041.423.0), Chromium (85.0.564.44)
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
npm install
npm run serve
and try goind to different pages
What is expected?
I created a route with importing components to be lazy loaded. Im expecting that when I go to other route. It will download the data or chunks.
What is actually happening?
It is prefetching the chunk. this means that when the site is opened. All chunks are downloaded.

Prefetching happens at browser idle time, rather than on the initial load. https://developer.mozilla.org/en-US/docs/Web/HTTP/Link_prefetching_FAQ
So it can still be considered a lazy-loaded chunk.

thanks a lot 👍🏻


Update yarn.lock

https://github.com/istarkov/google-map-react/commit/e344c3c8f4e51f6edea0d0f2d437f2bee661220d switched from point-geometry to @mapbox/point-geometry, but it didn't update yarn.lock accordingly. This does.

Thanks! If you'd like, I can add a command to .travis.yml that ensures yarn.lock stays updated. See here for an example: https://github.com/OctoLinker/browser-extension/blob/f2b242cdfbacaeeb6c973ae791fb01b8aabba7de/.travis.yml#L20-L21

@josephfrazier That would be great! Feel free to do so and I'll approve.


Update tiller deployment to use sles-based docker image

Currently the tiller image being used for the tiller deployment is
from the upstream registry at gcr.io. We should be using the SLES
based docker image instead of the upstream one.
Fixes: bsc#1062380

CI is broken right now, and won't test this anyway. Verified the new image name is correct:

sles12/tiller             2.5.1               a47207fd2d81        3 days ago          261 MB

will merge without CI.


New CI based on GH-actions

Update CI to use GitHub Actions. It's based on the ci.yml from Distributions.jl as it's quite recent.

coverage folder was removed since coverage should be handled by julia-actions/julia-processcoverage@v1 now
switched to using general Julia registry from depercated BioJuliaRegistry
removed older travis/appveyor.yml and related scripts from the root folder

@jakobnissen OK, the new CI seems to be running fine.
The check is failing because of AppVeyor (I guess it is set up somewhere in repository settings, probably it has to be removed from there).
Also, I'm not sure why I don't see codecov reports here. Is it because some permission/integration has to be updated in repository settings too?
It would be nice to merge, then reviewing PRs like #44 would not be like guessing in the dark. :)

Thanks! It would be nice to also have MacOS CI - but maybe that's just too expensive. Not sure.


Update to latest engine, bump package version

Fixes: #286
Update to the latest engine which has faster PLY loading and SH support for PLY.
Also bump package version.

Ooops, should I revert eslint upgrade @willeastcott?

Yes, let's upgrade that in it's own PR.


Alejandro (hero) - Description Text Error

The description states he is looking for "challeneges" instead of "challenges".
Scribes gotta change that :P

Fixed it, thanks for the report.


Consider adding tags for the repo.

Hi~
Adding tags for repo could specify points in history and mark release points.
It's helpful for user to know the version and status of repository, and would enable wider distribution of the library, for example on CDNJS
Would you please consider on using tags?
Thanks for your great work!!
Piicksarn

Hi. I don't understand what tags are. And I don't see it in git hub. Could
you please explain?
On Sun, Aug 16, 2015 at 10:03 AM, Piicksarn<EMAIL_ADDRESS>wrote:

Hi~
Adding tags for repo could specify points in history and mark release
points.
It's helpful for user to know the version and status of repository, and
would enable wider distribution of the library, for example on CDNJS
https://github.com/cdnjs/cdnjs
Would you please consider on using tags?
Thanks for your great work!!
Piicksarn
—
Reply to this email directly or view it on GitHub
https://github.com/vvvmax/unitegallery/issues/18.

@vvvmax
the link below show more detail about tagging.
https://git-scm.com/book/en/v2/Git-Basics-Tagging

Hi. It would be too complicated for me. I like it simple. do update and
upload it to github.
On Tue, Aug 25, 2015 at 7:13 AM, Piicksarn<EMAIL_ADDRESS>wrote:

@vvvmax https://github.com/vvvmax
the link below show more detail about tagging.
https://git-scm.com/book/en/v2/Git-Basics-Tagging
—
Reply to this email directly or view it on GitHub
https://github.com/vvvmax/unitegallery/issues/18#issuecomment-134469257.

@vvvmax, it's fine :)))
Thank you for response!


Probot app throwing 'ERROR (server): Bad Request'

Bug Report
Current Behavior
App not working, giving error whenever it receives a payload.
/**
 * This is the main entrypoint to your Probot app
 * @param {import('probot').Probot} app
 */
module.exports = (app) => {
  // to run when a pull request is opened
  app.on(['pull_request'], async (context) => {
    console.log('hi')
  }

Expected behavior/code
Code should work
Environment

Probot version(s): 12.2.5
Node/npm version: Node v18.7.0/NPM 8.15.0
OS: MacOS 12.5

Additional context/Screenshots
❯ npm run dev
Debugger attached.

><EMAIL_ADDRESS>dev
> nodemon --exec "npm start"

Debugger attached.
[nodemon] 2.0.19
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `npm start`
Debugger attached.

><EMAIL_ADDRESS>start
> probot run ./src/app.js

Debugger attached.
Debugger attached.
INFO (server): Running Probot v12.2.5 (Node.js: v18.7.0)
INFO (server): Forwarding https://smee.io/0ADrNP0EXPCsJRv6 to http://localhost:3000/
INFO (server): Listening on http://localhost:3000
INFO (server): Connected
INFO (http): POST / 400 - 9ms
ERROR (server): Bad Request
    Error: Bad Request
        at Request.callback (/Users/divkix/Documents/GitHub/dependabot-auto-merger/node_modules/superagent/lib/node/index.js:921:17)
        at /Users/divkix/Documents/GitHub/dependabot-auto-merger/node_modules/superagent/lib/node/index.js:1165:20
        at IncomingMessage.<anonymous> (/Users/divkix/Documents/GitHub/dependabot-auto-merger/node_modules/superagent/lib/node/parsers/json.js:22:7)
        at IncomingMessage.emit (node:events:525:35)
        at IncomingMessage.emit (node:domain:489:12)
        at endReadableNT (node:internal/streams/readable:1359:12)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
status: 400

Be sure that you have set your WEBHOOK_SECRET environment variable. Even though this is specified as 'optional' for GitHub applications, it's required for Probot applications!


Bugs fixed

There were two bugs in the site:
- There were unneded heights for some of the sections
- One of the buttons was missing

LGTM


fix: resolve eslint errors and warnings

Description
In this PR I added the required eslint rule ie. eslint:recommended and fixed all errors and warnings.
Fixes #48
Type of change
Please delete options that are not relevant.

[x] Code clean up as per Eslint

How Has This Been Tested?
Ran the application locally and checked for example if the Try It and home links still work. The remaining changes relate to unsused variable so those should have been pretty safe to just delete. There weren't any automated tests to change, though as these are eslint fixes there wouldn't have been much need for unit tests.
Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@rzhekova Please resolve the conflict.
@niteshseram could you please review?

Conflicts should be resolved now

@rzhekova Please resolve the conflict.
@niteshseram could you please review?

@atapas I am out of station and don't have laptop with me. Give me two day.

@niteshseram Please finish your review.

@niteshseram please review it sooner you can. I want to merge this one before including more code changes.
@rzhekova Could you please confirm the changes are done and tested on the latest from the master?

@atapas Hi, yes I have checked against latest master and there are no eslint errors :)

Have you installed dependencies? When I run yarn lint I don't get these errors

Try running yarn build and see if you can see any error there. If you found some error there, that is the problem. Otherwise we have to see the vercel console.

I've run it before pushing and there weren't any errors at all, and all changes I made have been pushed up

Try running yarn build and see if you can see any error there. If you found some error there, that is the problem. Otherwise we have to see the vercel console.

I've run it before pushing and there weren't any errors at all, and all changes I made have been pushed up. Ran yarn lint too and no issues there too

From vercel log

Try a yarn build locally. I have reinitiated the build on vercel too.. let's see

If it builds locally, vercel may be down.

I guess the build worked

I think we can move fixing of the search box into a separate PR and make this PR only to fixing linting issue

Unfortunately, we can not @niteshseram. As the break is found in the branch code and master it is working. So merging this without the fix would break a working feature in the master and that is not acceptable.

Unfortunately, we can not @niteshseram. As the break is found in the branch code and master it is working. So merging this without the fix would break a working feature in the master and that is not acceptable.

No no, it doesn't break if we don't try to fix the linting warning on the search box component. It was breaking because she added onSearch on the useEffect dependency. If we don't add that, it works. Just need to confirm, if the build passes or not with the linting warning since it is not an error but a warning.

Got it. So @rzhekova has to confirm it right?

@rzhekova
Thanks a lot for taking the issue and making the app better. Please feel free to pick up more, contribute more. I wish you a great #Hactoberfest ahead. You will be added to the contribution list right after we merge this PR. Don't forget to share about your contribution publicly and provide your support with a star ⭐.
Great work 🔥 !!!!

@all-contributors please add @rzhekova  for Code


[ENH] Add algorithm_type tag to clusterers

Describe the feature or idea you want to propose
for classification/regression we group algorithms by core technique, e.g."algorithm_type": "distance". Currently clusterers do not have this tag,
Describe your proposed solution
would be good to add it
Describe alternatives you've considered, if relevant
No response
Additional context
No response

aeon-assign bot assign @aryanpola

@aeon-actions-bot assign @aryanpola

fixed by #2041


Can't build Android after upgrading to RN 0.69

Hello,
I have upgraded my project to use the latest version of React Native 0.69
While I can make a debug build without issue, I'm facing an error I cannot resolve when I make a production build on Android
Execution failed for task ':iterable_react-native-sdk:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
   > Android resource linking failed
     ERROR:/Users/Alexis/.gradle/caches/transforms-3/c5bd231533bac8afd0a3a300eabfc673/transformed/core-1.7.0/res/values/values.xml:105:5-114:25: AAPT: error: resource android:attr/lStar not found.

I have the same issue with my local machine and the CI.
Removing the iterable dependency from my project allows me to build.
I've tried different versions of iterable, including the latest version 1.3.6.
I've also tried to use different versions of kotlinVersion and androidXCore but it's still failing.
How to reproduce?
Initialise a new React-Native project - will be 0.69.4 as of today
npx react-native init AwesomeProject

Install iterable sdk
npm install @iterable/react-native-sdk

Create an android release build
cd ./android
./gradlew assembleRelease

Thanks for reporting @alexmngn.
What is your Android app's targetSDK version?
Have you tried updating it?

This is my gradle config which is the same one as RN 0.69
    buildToolsVersion = "31.0.0"
    minSdkVersion = 21
    compileSdkVersion = 31
    targetSdkVersion = 31

Hi @alexmngn ,
Have you tried this?
./gradlew app:assembleRelease
Let me know if that helps...
Reference: https://stackoverflow.com/a/61932616/6059451

@Ayyanchira I have just tried to use this command and yes, it does build properly.
That's a workaround I can use for now until the versions of the iterable sdk get more in sync with the latest RN.

@Ayyanchira I was working on fixing this error and just found this answer, thanks bro.

Ayyanchira

it work for me, thanks

Hi @alexmngn , Have you tried this? ./gradlew app:assembleRelease
Let me know if that helps... Reference: https://stackoverflow.com/a/61932616/6059451

nice this also work for me


Line height?

Could i even change this value?

Unfortunately this is something this control does not currently supports. I have been looking at the code and it is such a quick modification that I will try to find some time during this weekend to add it.
Thanks for reporting it :)

The PR is here: https://github.com/jobandtalent/AnimatedTextInput/pull/36
As soon as my colleagues review and approve we will push a new version.


Javascript compiler

Implement a Javascript/Node.js compiler, which would nicely complement the Arduino/C/Java offer we have now. It should make it possible to interact with e.g. Node-RED

Compiler now passes 100% of the tests.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/76738

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77425

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87374

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87386

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87387

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94125

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94129

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94131

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95868

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98795

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98925

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98926

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/99132

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98927

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/99141

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/102544

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/102546

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/102545

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/102547

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104808

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104809

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104810

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104811

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104814

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105389

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105392

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105396

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111028

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

TagBot fix

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116402

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116406

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116408

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116409

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116415


Dynamic prompt updates in screen example

I'm trying to make the prompt in the screen example evolve over time.
However, if I move
        stream.prepare(
            prompt=prompt,
            negative_prompt=negative_prompt,
            num_inference_steps=50,
            guidance_scale=guidance_scale,
            delta=delta,
        )

from before the main loop to within it, just before the call to
        output_images = stream.stream(
            input_batch.to(device=stream.device, dtype=stream.dtype)
        ).cpu()

then my output becomes pretty much some random uniform color.
If I add a timer to call stream.prepare for instance once every second, then once every second I get some grey / blank frame in the middle of the stream. How can I make this more fluid and continuous ?

hmm does not seem to work very well here if I replace my call to prepare:

[E] 3: [executionContext.cpp::validateInputBindings::2046] Error Code 3: API Usage Error (Parameter check failed at: runtime/api/executionContext.cpp::validateInputBindings::2046, condition: profileMinDims.d[i] <= dimensions.d[i]. Supplied binding dimension [2,77,1024] for bindings[2] exceed min ~ max range at index 0, maximum dimension in profile is 4, minimum dimension in profile is 4, but supplied dimension is 2.

this gives me a lot of visual artifacts too

i mean, you need to prepare stream anyway, but after you can change prompt with function above.

I do, I first have a call to prepare() unchanged from screen.py, and then I call stream.update_prompt("blah") whenever I get a new prompt


Update private-endpoint-dns.md

Added Azure IoT Central and Device Update

@asudbring
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

I've resolved a conflict and will merge shortly.


"draw" vs. "render"

When should we use each?

so in game stuff is almost all render. gui is like a mix of render and draw for now

Rendering or image synthesis is the automatic process of generating a photorealistic or non-photorealistic image from a 2D or 3D model (or models in what collectively could be called a scene file) by means of computer programs.

Draw for simple things (rectangles, circles, buttons; text is a bit on the edge since it's not trivial).
Render for complex things/models (items, blocks, entities).

But then the question is what do we consider "simple"? Is the sky rendered or drawn? Does the PathfindingDebugRenderer draw or render paths? Is a box drawn or rendered (we currently have drawBox, which calls renderQuad!)? Is text rendered or drawn?

I would say for everything you've mentioned it should be render (apart from the PathfindingDebugRenderer  since I don't know what that is).

I use render and draw interchangeably as synonyms. Usually render is for more involved processes whilst draw is a blunt edge.
In places I have used render for public-facing methods and draw for the internal/supporting methods as well though.

Maybe render for world & 3D stuff and draw for screen & 2D stuff will be fine?

Agree, draw for 2d and render for 3d. e.g. drawTexturedRect (mojang called it blit, a 2d operation, before) is 2d, and renderEntity is 3d.

 For example, you draw a line, or draw a texture, or draw text. But you render a model.

How about a piece of text? should it be draw or render string?
Imo the distinguishing feature for 2d and 3d is the matrix transformation. If there is no transformation involved in one step, I'd call that step and its components "draw"; if there is transformation, I'd call it "render".
For instance, if we draw a string that is the name of an entity, we call it drawing a name. But if we goes to upper level and see how the name is affected by the transforms of the entity, we call it rendering a name plate.

I agree


19 verbose mode

Description
^ Added -v, --verbose flag to the CLI

If flag is present and true configure the logger to log to stdout
If flag is not present or false do  show logging
By default logging is hidden

Fixed #19