docs: Copilot extra documentation is missing nvim-cmp config

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.2
Operating system/version
Mint 21.2
Describe the bug
I was checking the copilot extra config because I have my own config of lualine, and importing the extra "breaks" it.
In the docs full spec says  "zbirenbaum/copilot.lua" and "zbirenbaum/copilot-cmp" should be configured.
Checking the source code of the extra, it is "nvim-cmp" which should be configured, with "zbirenbaum/copilot-cmp" as dependency:
{
    "nvim-cmp",
    dependencies = {
      {
        "zbirenbaum/copilot-cmp",
        dependencies = "copilot.lua",
        opts = {},
        config = function(_, opts)
          local copilot_cmp = require("copilot_cmp")
          copilot_cmp.setup(opts)
          -- attach cmp source whenever copilot attaches
          -- fixes lazy-loading issues with the copilot cmp source
          require("lazyvim.util").lsp.on_attach(function(client)
            if client.name == "copilot" then
              copilot_cmp._on_insert_enter({})
            end
          end)
        end,
      },
    },
    ---@param opts cmp.ConfigSchema
    opts = function(_, opts)
      table.insert(opts.sources, 1, {
        name = "copilot",
        group_index = 1,
        priority = 100,
      })
    end,
  },
}

Steps To Reproduce

Copy the full spec in the docs
Copilot does not show suggestions in nvim-cmp

Expected Behavior
To copy  the full spec of the docs and get copilot working
return {
{
  "zbirenbaum/copilot.lua",
  cmd = "Copilot",
  build = ":Copilot auth",
  opts = {
    suggestion = { enabled = false },
    panel = { enabled = false },
    filetypes = {
      markdown = true,
      help = true,
    },
  },
},
{
  "zbirenbaum/copilot-cmp",
  dependencies = "copilot.lua",
  opts = {},
  config = function(_, opts)
    local copilot_cmp = require("copilot_cmp")
    copilot_cmp.setup(opts)
    -- attach cmp source whenever copilot attaches
    -- fixes lazy-loading issues with the copilot cmp source
    require("lazyvim.util").lsp.on_attach(function(client)
      if client.name == "copilot" then
        copilot_cmp._on_insert_enter({})
      end
    end)
  end,
}
}

You should never copy the full spec. There's a big warning on top that literally says that is just shows the options as a reference.
Either way, I will check why nvim-cmp is not included in the doc for the extra. Those docs are auto generated, so there's probably a bug in there.
I'll also add a link to the full source on GitHub for every extra.

I fixed the doc-gen in the meantime, and the new docs are live!


Git: open file in diff view title bar should always open in the same editor group

Open some file in left editor group
Open some diff view in right editor group
Click on the open file git title bar action in the diff view
The file is opened in the left editor group. I would expect it to open in the right group

I find this frustrating 🙃

#23667


Refactor API spec helper expect_result_resource_keys_to_be_like_klass

Purpose or Intent
Another small refactoring of API specs to arrive at fewer total expectations, removing the expect_result_resource_keys_to_be_like_klass in favor of RSpec's composable matchers, which can be combined with other expectations on the response for better readability and feedback.
@miq-bot add-label api, test, refactoring
@miq-bot assign @abellotti

:musical_score:


add {index} in workspace modules

As far as I've seen, I can show in my workspace area the name of the workspace and icon.
Would it be possible to add {index}?

Duplicated issue #48


Make sure UDPServer can run on it's own without anything else.

Need to add flags to the go code to turn off every else but the UDPServer.

go run . serve --disable-es --disable-load-peers --disable-start-prometheus --disable-write-peers --disable-federation

https://github.com/lbryio/hub/pull/24


Fix push to create with capitalize repo name

Fix #29073

I was unable to create a backport for 1.21. @lunny, please send one manually. :tea:
go run ./contrib/backport 29090
...  // fix git conflicts if any
go run ./contrib/backport --continue


chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-k8s-28-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4318

Questions ?
Please refer to the Backport tool documentation


feat: new userOp structure for EPv0.7

📖 Context
Type of change

[x] Non-breaking change (backwards compatible)

Why are we doing this?
ERC-4337 got a new update with EntryPoint v0.7, which affected the UserOps structure.
The new object doesn't contain initCode and paymasterAndData fields (as in used to up to EPv0.6),
and it introduced new fields: factor, factoryData, paymaster, paymasterVerificationGasLimit, paymasterPostOpGasLimit, and paymasterData.
All this can be found at https://eips.ethereum.org/EIPS/eip-4337#useroperation

Related issues:
link to issue
What did we do?

We changed interface of several client-facing endpoints (only v3 version)
Changed the underlying structure that is stored in the Mongo
Added a new queue type for new object (as well as its appropriate consumers and producers)
Fix the old tests

How Has This Been Tested?

Tested this manually by sending a user op on the Base Sepolia network
(here is a link to the successful transactions against EPv0.7 contract - https://sepolia.basescan.org/tx/0xb48b098665b1d74a8d26e02a8549af270113cf147232de08088406de28fa87e3 )

More thorough testing is still pending (tbd)

👀 How do I review this?

To test this you first need to checkout this branch and run the Nexus SDK against v3 set of endpoints

@veljkovranic please add instructions how do I run the Nexus SDK and test the new v7 endpoints.


Revert "encryption: Limit encryption keys to 2 bits"

This revert fixes the failing CI on 4.9 (Transparent encryption DirectRouting Check connectivity with transparent encryption and direct routing*). Let's revert until the PR has been fixed.

test-4.9

test-me-please

@borkmann Thanks, I've extended the git commit msg.

test-me-please

test-runtime

test-1.13-netnext

test-1.19-4.19

test-1.20-4.9

merging as this fixes the regressions


Hi here is my exercise uploading again

i tried by myself but i am not very bad at this, so i watched the video to understand it

Worked great that time! Thanks for getting it in so quickly. Your code looks good.


FF-2945 feat: Python SDK

This PR is ready for review.
It's probably best to start review with the announcement to understand main changes: https://github.com/Eppo-exp/eppo-docs/pull/454

I'm able to install with pip but not able to integrate it into a sample program:
➜  python-sdk git:(feat-python-sdk) ✗ pip install -e .
Obtaining file:///Users/leo/src/rust-sdk/python-sdk
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... done
  Preparing editable metadata (pyproject.toml) ... done
Building wheels for collected packages: eppo-server-sdk
  Building editable for eppo-server-sdk (pyproject.toml) ... done
  Created wheel for eppo-server-sdk: filename=eppo_server_sdk-4.0.0-cp311-cp311-macosx_11_0_arm64.whl size=4297 sha256=d3076a814895414aff8a1e5b29785242d953393c21c320d91d93054dc412e1cb
  Stored in directory: /private/var/folders/1f/95qsl9p95fz0k6jgh5cgcd3r0000gn/T/pip-ephem-wheel-cache-wsivpflm/wheels/05/a2/8b/febb161210fb0561c324e64b7ff9400edef701dbe616d25850
Successfully built eppo-server-sdk
Installing collected packages: eppo-server-sdk
  Attempting uninstall: eppo-server-sdk
    Found existing installation: eppo-server-sdk 4.0.0
    Uninstalling eppo-server-sdk-4.0.0:
      Successfully uninstalled eppo-server-sdk-4.0.0
Successfully installed eppo-server-sdk-4.0.0

[notice] A new release of pip is available: 24.1.2 -> 24.2
[notice] To update, run: python3.11 -m pip install --upgrade pip

❌
➜  python-sdk git:(feat-python-sdk) ✗ python3 -c "from eppo_client import EppoClient; print(EppoClient)"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'eppo_client'

The existing sample program I have is:
import eppo_client
import time
from eppo_client.config import Config
from eppo_client.assignment_logger import AssignmentLogger

# Set this as your Eppo API Key - https://docs.geteppo.com/prerequisites/feature-flagging/randomization-sdk/api-keys
api_key = ""

# Set this one of your Eppo experiment keys
experiment_key = ""

class ExampleAssignmentLogger(AssignmentLogger):
  def log_assignment(self, assignment_event):
    return print("Assigned experiment %s variation %s to subject %s" %(assignment_event["experiment"], assignment_event["variation"], assignment_event["subject"]))

if __name__ == "__main__":
  if not api_key:
    print("Edit example.py to enter your Eppo API key")
    exit(1)

  config = Config(api_key=api_key, assignment_logger=ExampleAssignmentLogger())
  client = eppo_client.init(config)
  time.sleep(1) # wait for initialization
  variation = client.get_assignment("my-user", experiment_key)
  if variation is None:
    print("No variation assigned. Check that the experiment is running.")

Are adjustments needed to it or to pyproject.toml ?

@leoromanovsky that's interesting. The import should work without any changes.
Could you give me the output of the following:

which pip
which python3
ls python/eppo_client

also, does it work with non-editable install (pip install .)?

ls python/eppo_client

➜  python-sdk git:(feat-python-sdk) ✗ pwd
/Users/leo/src/rust-sdk/python-sdk
➜  python-sdk git:(feat-python-sdk) ✗ which pip
/opt/homebrew/bin/pip
➜  python-sdk git:(feat-python-sdk) ✗ which pip3
/opt/homebrew/bin/pip3
➜  python-sdk git:(feat-python-sdk) ✗ which python3
/opt/homebrew/bin/python3
➜  python-sdk git:(feat-python-sdk) ✗ python3 --version
Python 3.12.5
➜  python-sdk git:(feat-python-sdk) ✗ ls python/eppo_client
__init__.py                        _eppo_client.pyi                   config.py
__pycache__                        assignment_logger.py               py.typed
_eppo_client.cpython-311-darwin.so bandit.py                          version.py

➜  python-sdk git:(feat-python-sdk) ✗ pip install .
Processing /Users/leo/src/rust-sdk/python-sdk
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: eppo-server-sdk
  Building wheel for eppo-server-sdk (pyproject.toml) ... done
  Created wheel for eppo-server-sdk: filename=eppo_server_sdk-4.0.0-cp311-cp311-macosx_11_0_arm64.whl size=2235806 sha256=3983ad3721e3ff5c7d941f55e90670b8bada7b8bbb0de72ed825f7bf42d12bf5
  Stored in directory: /Users/leo/Library/Caches/pip/wheels/05/a2/8b/febb161210fb0561c324e64b7ff9400edef701dbe616d25850
Successfully built eppo-server-sdk
Installing collected packages: eppo-server-sdk
  Attempting uninstall: eppo-server-sdk
    Found existing installation: eppo-server-sdk 4.0.0
    Uninstalling eppo-server-sdk-4.0.0:
      Successfully uninstalled eppo-server-sdk-4.0.0
Successfully installed eppo-server-sdk-4.0.0

[notice] A new release of pip is available: 24.1.2 -> 24.2
[notice] To update, run: python3.11 -m pip install --upgrade pip

Going to merge this, so next PRs take python into account. Will coordinate with you to release it later


Update to HEAD

Depends on https://github.com/conda-forge/arrow-cpp-feedstock/pull/7.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I wonder what's wrong with Travis CI. @jakirkham?

They made some changes. ( https://github.com/conda-forge/status/issues/30 ) Though they have been working with us to correct things. I'm going to try something to see if it will work here.


Message filters and formats

What options do I have to pass a filter or map to decide what messages to accept and what format to accept them in? I know we talked about that but forgot if this was already available to developers today or planned for a future Kafka release.

David Tucker<EMAIL_ADDRESS>In terms of filtering, the current framework allows you to implement almost anything you like.   You'll see some connectors that support regexp filters for given fields within the record.   The Connect team is working on an abstraction we call "Single Message Transforms" to support a standard way of doing that across connectors; that will be available next year.   The team at DataMountaineer (http://docs.datamountaineer.com/en/latest/connectors.html#connectors) has a very powerful SQL-like model for filtering that may give you some ideas.

Closing, SMTs are available to do this.


Questions about the run_sim.py implementation

hello. While looking at the simulator code, I have a question.
While looking at the SRTF code (def shortest_first_sim_jobs(...)) in run_sim.py, I saw that the execution time including overhead was subtracted from the code that updates the remaining_iteration of the job in the runnable_jobs list.
In my opinion, this overhead is the time from the start of initial training to the start of iteration.
Therefore, it seems that this overhead needs to be subtracted only once at the beginning, but in this code, it seems that this time is repeatedly subtracted to calculate it.
Thanks for answering the question :)

Thanks for your question.
For every scheduling interval, the jobs are scheduled and restarted in SRTF. Therefore, the overhead is calculated every scheduling interval.

What exactly does overhead mean?
Thanks

Sorry for the misleading "schedule interval". In our comparison, the SRTF scheduler stops, re-schedules, and restarts all jobs once some event happens (e.g., job starts/ends), i.e., the scheduler re-schedules all jobs for every while iteration. In the simulator code, however, we do not stop and restart the job explicitly, but use the overhead to represent preemption.
Minimizing the reschedule overhead is an optimization for these schedulers, which is out of the scope of our paper and this implementation.
Besides, we calculate the execution information at the beginning of next schedule interval.
So we add an overhead for all running jobs at the beginning of every schedule interval.


Add more Button state templates

First of all, I greatly admire your contribution to the HomeAssistant community with such a modern front-end UI project, which I also use regularly.
I've noticed quite a few FRs mentioning customization templates of Button state styles, a problem I've encountered myself, and you've recently merged some corresponding logic optimization code.
For instance, with Occupancy sensors, we receive an On/Off status, but for a user-friendly Dashboard, displaying "Occupied" or "Unoccupied" might be a better choice of wording.
As a user from China, I've noticed in the translation configurations that Chinese is not only zh-Hans and zh-Hant but also have a generic "zh". Each of these versions lacks certain translations, leading to scenarios where, if I choose zh-Hans, the terms for user presence, like "Home" or "Away", only appear in English.
Additionally, in some cases, users might want a Button to be highlighted only when it's in the Off state.
I've noticed that you've actively addressed many such scenarios, and just yesterday, you fixed the issue where StateOn and StateOff can now correctly display after setting the state value to custom code.
However, my suggestion is that with the myriad of smart devices and diverse requirements, it's impossible to preset every scenario for users. This could limit your capacity to develop more interesting controls if too much focus is placed on this aspect alone.
For example, I have a category specifically for monitoring all consumable sensors in my home. Some use On/Off to indicate a warning, while others use percentages, like battery level for button cells or filter percentage for air purifiers. In these cases, I would prefer to have the sensor light up in red when the battery or filter percentage drops to a certain level to provide a clearer warning.
I believe you've done an excellent job so far. At this stage, it might be wise to let users handle these complex style configurations themselves. I've tried modifying the code to allow users to configure the Button's background color, title text color, and state text color through Templates. Once the project is strong enough, we can aim to perfect the configurations for all scenarios as much as possible.
I am an Android App developer, not very familiar with many front-end technology stacks, and can only modify based on existing code, hoping it's not too bad.
Lastly, I wish for this project to become more widely known, attracting more people to maintain and use it 🎉.

For instance, with Occupancy sensors, we receive an On/Off status, but for a user-friendly Dashboard, displaying "Occupied" or "Unoccupied" might be a better choice of wording.

This is solved by implementing the device class https://github.com/matt8707/ha-fusion/issues/70

As a user from China, I've noticed in the translation configurations that Chinese is not only zh-Hans and zh-Hant but also have a generic "zh". Each of these versions lacks certain translations, leading to scenarios where, if I choose zh-Hans, the terms for user presence, like "Home" or "Away", only appear in English.

Unless it's a bug specific to Chinese, it appearing in English indicates that it lacks translations
https://developers.home-assistant.io/docs/translations/, I'd love to help fix this

I've tried modifying the code to allow users to configure the Button's background color, title text color, and state text color through Templates.

Thanks, but I don't think this is the right approach. Adding an input field for every style isn't feasible. There could be support for custom CSS, but that would come after adding themes. I'll close this PR for now.


List of categories not sorted when add new post

Hi,
When add a new post the list of categories is not sorted. I want to have it sorted. I think that I should modify nova-categories/lib/custom_fields.js
Posts.addField(
{
fieldName: 'categories',
fieldSchema: {
type: [String],
control: "checkboxgroup",
optional: true,
insertableBy: ['members'],
editableBy: ['members'],
viewableBy: ['guests'],
form: {
noselect: true,
type: "bootstrap-category",
order: 50,
options: formProps => getCategoriesAsOptions(formProps.client),
},
resolveAs: 'categories: [Category]'
}
}
);
to add something equivalent to the version in Nova Classic
var categories = Categories.find({}, {sort: {name: 1}}).map(function (category)
I spent many hours, reading Nova code, but still don' t find how to do it with Nova Apollo/GraphQL.
Could you please point out how to do or add this sort to the next release (when having many categories, it's more convenient to have them sorted).
Thank You
Adalidda

You will want to use array method .sort to sort the result of getCategoriesAsOptions(formProps.client).
You can see the code of the functions used here: https://github.com/TelescopeJS/Telescope/blob/master/packages/nova-categories/lib/schema.js#L15-L24
Sort docs: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort
Btw, if you want to get better at this kind of things, I recommend JS30 🚀 http://javascript30.com

And you should do the modifications in your own custom package, not in nova:categories directly :)

Thank You Xavier
Adalidda
On Sun, Feb 5, 2017 at 10:14 PM, Xavier Cazalot<EMAIL_ADDRESS>wrote:

You will want to use array method .sort to sort the result of
getCategoriesAsOptions(formProps.client).
You can see the code of the functions used here: https://github.com/
TelescopeJS/Telescope/blob/master/packages/nova-
categories/lib/schema.js#L15-L24
Sort docs: https://developer.mozilla.org/en-US/docs/Web/JavaScript/
Reference/Global_Objects/Array/sort
Btw, if you want to get better at this kind of things, I recommend JS30 🚀
http://javascript30.com
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/1560#issuecomment-277525880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOoSB-v4Tj7ml991l4K7cwve3swnoWYOks5rZec9gaJpZM4L3gc3
.


d3 4.x support

The title says it all

restarting this project with v4 support @ https://github.com/skokenes/d3-lasso

v4 alpha done! could use help testing it out with some examples...
https://github.com/skokenes/d3-lasso


Android: Allow use of custom RavenFactory

As the Raven.init() method supplies its own call to RavenFactory.registerFactory() we're unable to provide our own RavenFactory instance and thus unable to add additional builderHelpers to the Raven instance used by the com.getsentry.raven.android.Raven class
This PR adds methods that allow initialising with a custom RavenFactory class

Thanks, will merge this in #294 so I can make edits.


Misc ideas

In flit default, make "home_page_template" a list.
Propose each.
if user type something complex -> assume it's what is ment.
otherwise if it parses to an int, select that from the list.

License, same principle with Non-shown licence. Typing BSD, GPL should match.

I don't want to make flit init too complex - it's supposed to be a quick way to get a simple, working config file (with license choice integrated to encourage people to give their code a license). Let's focus on building and uploading packages for now. At some point, perhaps a nicer interactive package metadata editor would be good as a separate tool.


Issue livery 787-8

On the 787-8, the livery on the rudder doesn't change, but only on the moving part of it

we know
On Mon, 26 Jun 2023 at 12:47, CharlieDelta28 @.***>
wrote:

On the 787-8, the livery on the rudder doesn't change, but only on the
moving part of it
—
Reply to this email directly, view it on GitHub
https://github.com/kolos26/GEOFS-LiverySelector/issues/359, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AYSKEJZZZTF5C3PJTHFEORDXNFZGHANCNFSM6AAAAAAZUBKKJ4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add git alias for log graph without --all.

I created this alias because the --all option cannot be overridden.
If possible, I'd like to change the existing glg (has --all option) to glga or glG and make this alias as glg.

I would be fine with reversing the aliases (make --all glG). If you want to make that change, I can merge it in with this.

@belak what's the policy with addition of new aliases? Do we look at them case by case?
My personal muscle memory doesn't really gel well with prezto aliases so I have my own set which is mostly confined to git based aliases and shortening some common commands I use.

@srijanshetty It's mostly case-by-case... I try to look at them logically since I generally don't use them either. In this case, it makes more sense to make the base alias without --all and have the modifier add it. We've done other aliases similar to this in the past.

@belak I agree with you. It might be simpler to remove --all from glg.

update issue subject.
Issue Descriptions
remove --all flag to be able to control revision to displaying.

Is there anything else I should do?
Should I withdraw my PR?

This looks good to me - sorry, I've just got a ton of real life stuff going on at the moment.

@belak Thank you for your time!


SPFx 1.4 Deploy assets to public CDN in tenant

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
When public CDN in tenant is enabled I expect the sources to be stored there and not in app_catalog/clientsideassets.
Steps to Reproduce
Public CDN in tenant was enabled and re-enabled

package-solution.json contains: "includeClientSideAssets": true,
write-manifests.json contains: "cdnBasePath": ""
Bundled en packaged the solution for shipping.
Solution package dropped in app catalog and deployed.
Added app to site.
Added web part to page.
Developer tools:

Result: Source points to app_catalog.
Expected: Source points to /sites/cdn/content
Did I miss a step?
Is my expectation not correct?

i think the tooling deploys the javascript to the client side assets library in the site the solution was deployed on. if the tenant has cdn enabled with the default settings then that client side assets library is cdn-enabled, and your code will be served from the cdn. if you enabled a custom site collection to be used as a cdn(like i did) the tooling has no way of knowing that. it just puts the code in the  site it was deployed on and if it's cdn enabled, your stuff is served from the cdn. if cdn is not enabled, stuff is seveed from the sites client side assets library.

@AnitaBoerboom this might sound strange and we'll adjust this this still in our side, but even thought you have includeClientSideAssets set to true, you should not change the default value of cdnBasePath, which will need to be still as "cdnBasePath": "<!-- PATH TO CDN -->" to make things work.


Phoenix Path / Module Utilities

Is your feature request related to a problem? Please describe.
When creating phoenix controllers, they are written to a location not adhering to the phoenix conventions.
MyAppWeb.TestController => lib/my_app_web/test_controller.ex instead of lib/my_app_web/controllers/test.ex
Describe the solution you'd like
Provide Igniter.Libs.Phoenix.proper_location/2, and a way to override the path for Igniter.Code.Module.create_module/4.
Additionally, the modules should not be moved to their "correct" location at the end or there should be a convenient function to add it to the do_not_move igniter configuration.
Describe alternatives you've considered

Express the feature either with a change to resource syntax, or with a change to the resource interface
For example
Igniter.Libs.Phoenix.proper_location(igniter, TestWeb.TestController) # => lib/test_web/controllers.test.ex

Additional context
None

Summary from discussions with @zachdaniel and on Twitter

The current phoenix conventions are optional. You can theoretically name controllers / live views etc. however you like.
To be able to handle the current conventions with igniter, it would be good to be able to influence Igniter.Code.Module.proper_location/2

This could be achieved by allowing to configure extensions in the ingiter configuration.

We could theoretically also introduce new conventions.

For example MyAppWeb.Controller.Foo instead of MyAppWeb.FooController and keep the paths according to normal elixir best practices.
If we decide to implement a new convention, we should provide a migration command. (Best case would also move templates.)

To be able to generate correct module names according to any convention, a few Phoenix helpers would be helpful to create module names.

controller_name(igniter, "Foo")

current convention: MyAppWeb.FooController
hypothetical new convention: MyAppWeb.Controller.Foo

same for view modules / live views, channels etc.

Alright, so what I've come up with really might not be great. We will have to see. But we now have a Phoenix extension that uses module naming heuristics to figure out where a given newly created module ought to go. We can see where this takes us. It is possible that it will need to be reworked to be able to take the zipper contents of what is being created, to peek inside and see what's going on, etc. But for now it will have to do.
The remaining things are things I probably won't tackle in the near future. Specifically:

coming up with an alternative and more consistent with elixir patterns naming convention for phoenix
adding functions like .controller_name to help with this consistency. These I will add as I need them, and encourage others to do so as well.

There is no seamless way to allow people to magically adopt this new standard, because they may not be using the function we provide in the first place, and relying on igniter to "do its thing". More realistically there would be some kind of migration task.


Add a modal for copying a JS tag for privacy experiences

Is your feature request related to a specific problem?
Add a modal with a JS snippet that the user can copy and paste into their own site
Describe the solution you'd like
Need to coordinate based on https://github.com/ethyca/fides/issues/3160 for what this link should look like
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context

From @eastandwestwind :
the script will look like
<script src="https://{privacy-center-hostname-and-path}/fides.js"></script>

3 options for path forward to get PC URL:

have the customer replace the {privacy-center-hostname-and-path} with their own before pasting on their site
have this url configurable in admin-ui, writing to fides db. If we do this, we need to make it obvious this is required to setup fides consent
have this url configurable in .env of fides. Downfall is having to redeploy fides if this PC url changes

Option 1 would be the easiest for us at the moment, but puts the burden on the customer. we should think through how we'd go the 2/3 route

I'd probably vote #2, because won't the components also need that URL for their own configuration? For example, we'll need notices/banners to be able to link to the privacy center.

moving to done


Cannot set breakpoints in source code of dependencies after navigating to them using jump-to-definition

The index build and the real build maintain two separate checkouts of the package dependencies. Because of this, jump-to-definition takes you to the source file in the .build/index-build folder, while the build uses the checkout in the .build. Hence, setting a breakpoint in the index-build checkout does not cause the breakpoint to be hit at runtime.

Synced to Apple’s issue tracker as rdar://141016927


Update reference-error-codes.md

added AADSTS5000819 and AADSTS76021
https://identitydivision.visualstudio.com/Engineering/_queries/edit/2490478/?triage=true https://identitydivision.visualstudio.com/Engineering/_queries/edit/2490489/?triage=true

@cfzhang6688  Thanks for making the update.  #sign-off


How to close a position at limit price?

I confirmed that I can close existing position by placing an order at market price. (using um_futures module)
I think there is 2 way to close a position at limit price.
(1)  Just place an order at limit price like using market price.
(2)  Set a TP when place an order at limit price all at once.
(1) might be works well, but I wanna use TP.
Here is my code, but it doesn't work. The result is stop price is applied "Trigger Conditions" not "TP/SL"
params = {
    'symbol': symbol,
    'side': 'BUY',
    'type': 'TAKE_PROFIT',
    'quantity':0.001,
    'price': 27000.1,
    'stopPrice': 27200
    }
client.new_order(**params)

Anyone let me know how to solve this.

Sorry I got confused.  A limited order is a order that is expecting to be filled at the limit price.  If it's not filled, it won't have any change to existing position if there is one.

You can't "close" the position. You can place an order (limit or market) that is filled and become the position (or "close" an existing position).


chore: release sorald 0.7.4

There is one breaking change in this PR. Better to release sorald 1.0.0.


Why there is a huge gap between the accuracy of training and testing?

why the accuracy is so poor in testing? Is it normal?

比如,这在测试时,正确率基本为0,我很困惑.

This is due to the size of training set in SVT is very small. We can expect to see super overfitting in its test set performance.

非常感谢你及时的回复.我明白了,由于第一次遇到这种情况,于是没读代码就来询问了,我感觉抱歉.


Feature: 关于增加类似dynamic-prompts插件的or语法功能

Scope
Stable Diffusion WebUI (AUTOMATIC1111)
Describe the problem related to the feature request
在调用NAI时，有时需要切换绘画风格，或者增加一些随机性，但是SD webui的内部可以实现的插件（SD-dynamic_prompts，stable-diffusion-webui-wildcards）NAI调用不到，所以希望NAI也能支持这个功能。
增加随机性是指(借用dynamic_prompts的语法表述)：
an {red|yellow} apple
会随机生成 an red apple或者an yellow apple的两种提示词之一
Describe the solution you'd like
在NAI的语法中增加对or语法的支持
Describe alternatives you've considered
是否可以从API调度SD webui中的插件实现语法支持？
Additional context
另外就是，如果在prompts里写这种or的条件句，可能会导致发送图片和关键信息)时候的信息过长和编写prompts时候输入过于复杂，是否可以同时考虑后续增加类似SD-dynamic_prompts的wildcard功能。
将prompts写入command.txt中，当使用__command__作为提示词时，在command.txt中随机提取一行填充为提示词。
当然，如果能从API调度插件的话，这个问题就已经解决了。

Currently, we DON'T support ANY extensions or scripts of sd-webui, so even if we add this syntax support, you'll not still be able to use that feature the extension provided.
In the meantime, novelai plugin knows nothing about the backend, it doesn't know which model the WebUI running, which scripts could be used, or even whether the payload is correct (which broke our plugin several times because WebUI changed their API), there should be always an extra effort for the user to remember and type these different things that you mentioned above.

那我认为如果在您精力允许的情况下，可以在NAI的层面对这个语法进行一种实现。让or的语法在koishi中完成，并将结果发送到webUI进行处理会比较好。当然，我不知道这个功能的重要性是否值得去进行更新支持。
我可以描绘一个环境使用它，比如我在Stable diffusion中已经固定下来了一个大家都很喜欢的风格，在大家进行创作的时候加入or的随机性来增加趣味性。有些时候，用户只是想要一张好看的图，但是你让他去确定发色，确定体征，确定pose，会拉高使用难度。

Yeah, supporting this syntax is not a difficult thing. But what I pointed out above is that even if we have supported this syntax, WebUI would not just magically enable the script and generate those images you want. Not only there is a property in the API payload called script_name that should be passed, but many scripts also require arguments.
Once we support this, that means, let me take your example here, you should write something like:
Yeah, you should pass all of the arguments here and the correct script title
In this case, the title is also dynamically updated between version bumps!
nai --script "Dynamic Prompts v2.5.6"
    --script-args "
        is_enabled=true,
        is_combinatorial=false,
        combinatorial_batches=1,
        is_magic_prompt=false,
        is_feeling_lucky=false,
        is_attention_grabber=false,
        min_attention=1.1,
        max_attention=1.5,
        magic_prompt_length=100,
        magic_temp_value=0.7,
        use_fixed_seed=false,
        unlink_seed_from_prompt=false,
        disable_negative_prompt=true,
        enable_jinja_templates=false,
        no_image_generation=false,
        max_generations=0,
        magic_model=Gustavosta/MagicPrompt-Stable-Diffusion,
        magic_blocklist_regex=
    "
    an (yellow|red) apple

Okay, you might say, what about adding a new configuration for this feature?
Well, it could be a configuration, too. But would you like to modify the configuration every time that you want to change the script you're using, or when there's an update that causes the script name or arguments to no longer be usable?
Why talk about this is that I want to show you that the script support is complicated and user-unfriendly, so it would not be in our plan currently. But if there are kind people who want to deal with these bananas, I would appreciate the who.
In a nutshell, it is implementable and wonderful. But considering our schedule and abilities, it's a pity that I cannot list this in our plan. Sorry!

Sorry to hear that, but it's ok and thanks for the detailed explanation.

@MaikoTan
我认为因为我功能的描述不太准确而导致您对此功能思考的过于复杂，我个人的想法并不是要将SD-dynamic_prompts这个脚本移植到koishi中去完全实现。而是主要希望实现其中的random prompts功能和wildcard功能，这样做的意义就像上面表述的那样，能降低用户使用门槛，让管理员做出方便的preset让用户进行调用。
实际上逻辑层面我想跟您表述的功能是类似于这样的
NAI 接受到 an {red|yellow} apple

NAI 识别为 an red apple

SDwebUI prompts:an red apple

我觉得这样做的好处就是，因为模型训练素材来源的问题，大部分模型生成的图会普遍趋向于一个定式。例如我画 1 girl的时候，极大的概率会出现黑色头发或者黄色头发的角色。而我需要其他发色的时候我就需要进行强调，当我需要概率基本相同时出现不同的发色的case时就可以发挥作用。于是在随机的将可控提示词进行组合，可以在保证质量的前提下得出尽可能多的不重复内容的结果。

我个人的想法，将这些打包好的随机数写到baseprompt属性中作为preset（当然如果做一个类似wildcard功能的东西进行变量的管理应该会更好），用户要做的仅仅是执行一个nai 1girl就可以得出质量可控的多样化结果。
为什么我尝试继续解释这件事，我个人的理解在于，novelai的初衷就是为了降低使用门槛，复杂的事情由您这样的开发者，和我们这类给他们提供算力和bot的人来完成，用户面对的应该是尽可能符合他们使用习惯和便利的东西。

Sorry I am confused. So you are referring to the dynamic extension, but we implement part of its features on our side?
In my opinion, the preset feature seems like be covered by #58 recipe feature, or at least could be implemented in the same thread. Is it what you mean?
If so, it is a doable feature now.
BTW, Although the issue #58 was closed, but I would work on this when anyone open a new issue to talk about the details of it.

OK,let me check the issue #58 and give you a feedback again. btw, I know it is quiet impolite to continue to leave comments in closed issues, thank you for your tolerance.

I hav read the function description of presets in the issue #58.It's what I want, but I think it should be more functional. These functions are exactly what I described 'wildcard' and 'or command' in this issue.
1.The preset should be used as a collection of prompts, which can be called with other prompts.
2.Like the concept of wildcard, preset can have multiple lines, and a line is randomly selected when executing it (is equivalent to ‘or‘ command)

I do a research for this feature and also recipe that mentioned in #58 these days. I think this is a bit complicated to merge into our plugin, sorry I could not implement it in our side.
BUT, I could make it a new plugin which could parse the syntax that you described above and then programmatically invoke novelai to generate the image(s).

Thank you for your efforts, no matter which node implements this function.

@shigma Is there a way to mark an issue never stale?

@MaikoTan Issues only with certain labels can be marked as stale.

ai-tag中已实现此功能，故关闭这个comment。

ai-tag中已实现此功能，故关闭这个comment。

It is not exactly the feature described in this issue, and I didn't say I would not implement this.
So I wanna leave this issue keeping open until it is got implemented.

使用 https://github.com/koishijs/novelai-bot/commit/5c8a76c44b25f9385f0688eae8524b1d8e62f0e7 可以一定程度上实现该功能，虽然不是非常优雅


Most of Falcor's Vulkan samples fail to run due to internal compiler error [URGENT]

Note that Falcor now uses VK SDK <IP_ADDRESS>
VulkanFixes branch:

AmbientOcclusion
HashedAlpha
SimpleDeferred
HDRToneMapping
Shadows
SkyBoxRenderer
ModelViewer
ForwardRenderer
SceneEditor

I'll look into it. All of these were working at the time I first created the PR to integrate Slang v0.10.*, so there must have been a regression at some point.

Everything works with 0.10.3, except for:

ComputeShader
MultiPassPostProcess (load an image, enable GuassianBlur and Grayscale. It complains about static being a reserved word).


Remove opentracing from core of webserver

As OpenTelemetry has gained momentum, we should remove opentracing support from webserver core, and add new module(s) for tracing support that are not built into webserver.
This will have the following impact:

configuration will be separated into the tracing module only (e.g. tracer would not be available on webserver or its builder)
performance impact will be visible only when tracing module would be used and registered
tracing integration would be less optimal, as it would no longer be part of the core code

Fixed by #4458


Hashie and Virtus.model Hash attribute

Anyone have this issue where when extending Hashie::Extensions::DeepFind you get a no method error for the deep_find method?

Try to build a repro?

It works well for me.
options = {user: {location: {address: '123 Street'}}} # {:user=>{:location=>{:address=>"123 Street"}}}

options.extend(Hashie::Extensions::DeepFind)
options.deep_find(:address) #"123 Street"

@magicalbanana Are you still having this issue?

@michaelherold I did it the way @u2 did it. I just thought you could extend it on the class level instead.

Thanks for the feedback. I clarified the inline documentation to help future users avoid this issue.


LetsEncrypt error: Could not validate CAA record

I am seeing the following error messages in the cert-manager logs when using BKPR on a AKS cluster. The domain in question does not implement a CAA record and as per the docs (https://letsencrypt.org/docs/caa/) CAA record is optional.
...
Unexpected response code 'SERVFAIL' for run.
I0506 05:37:43.271113       1 controller.go:206] challenges controller: syncing item 'kubeprod/prometheus-tls-1925554735-0'
I0506 05:37:43.271288       1 logger.go:103] Calling Discover
E0506 05:37:43.340452       1 controller.go:208] challenges controller: Re-queuing item "kubeprod/prometheus-tls-1925554735-0" due to error processing: Could not validate CAA record: Could not determine the zone for "run.": Unexpected response code 'SERVFAIL' for run.
I0506 05:37:43.977281       1 controller.go:206] challenges controller: syncing item 'kubeprod/kibana-logging-tls-622968911-0'
I0506 05:37:43.977448       1 logger.go:103] Calling Discover
E0506 05:37:44.026870       1 controller.go:208] challenges controller: Re-queuing item "kubeprod/kibana-logging-tls-622968911-0" due to error processing: Could not validate CAA record: Could not determine the zone for "run.": Unexpected response code 'SERVFAIL' for run.
...

To fix the issue, I added CAA records to my BKPR domain. Do you think kubeprod install should add this record while installing BKPR to the cluster?
P.S. This issue cannot be seen while using GKE or EKS

Seems to be an issue in cert-manager. CM release 0.7.2 seems to fix the issue.


[DDW-1086]: Fix incorrect wallet password change issue

This PR fixed incorrect wallet password change issue
YouTrack Ticket
Todos

[x] Fix incorrect wallet password change issue

Screenshots

Testing Checklist

Slack QA thread
[x] Select any wallet and go to Settings, and then try to change password inputting current password as shorter than 10 characters and check if error result is "Incorrect wallet password"

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

@yakovkaravelov can we do something with the pink border on the button when we click several times on it, it appears.

@a-rukin please share button design with @IuliaDolishniak
I believe this is correct border color.


EL: Always call depmod

Right now we call depmod for EL 8. Based on #1139, we should call it for EL 7, and perhaps for EL 6 as well.

@EricEdens, here's a permalink, before it runs away (the one in ticket is already off by 10 or so lines):
https://github.com/GoogleCloudPlatform/compute-image-tools/blob/746981f1855c2e45bc7e1c38f4e7932fe7e3f2d7/daisy_workflows/image_import/enterprise_linux/translate.py#L166-L168


Rewrite the GL binding model

Closes #2858
Closes #2784
Depends on https://github.com/gfx-rs/naga/pull/333
I was having a hard time trying to map our Naga semantics to the old binding model of gfx-backend-gl. I also couldn't stand the fact that the pipeline layouts were internally mutable, and mapping could grow as more pipelines are created. That seemed very out of line with regards to how other backends are written, and I didn't fully understand that code...
So the binding model is totally rewritten here. It becomes somewhat similar to Metal or D3D11, but with special logic to update the texture binding state instead of having true sampler objects.
The new code likely hosts bugs, I wasn't able to test it a lot, especially given the overall state of the backend. I think this rewrite is still a good investment into the future of the backend, and we should cope with the bugs coming our way.
The thing I'm most interesting in getting reviewed here is the general approach, the architecture of the binding model, which is described a bit in the crate lib.rs comment.

Rebased now, also added a bit of logic to reflect Naga's buffer resources.
bors r+


C3SXGate inconsistent with SXGate

Information

Qiskit Terra version: 0.18.3
Python version: any
Operating system: any

What is the current behavior?
The definition of C3SXGate() is currently equivalent to SXdgGate.control(3), but its name and its base gate definition indicate it should be equivalent to SXgate.control(3).
Steps to reproduce the problem
In [1]: from qiskit.circuit.library import SXGate, SXdgGate, C3SXGate
   ...: from qiskit.quantum_info import Operator
   ...: import numpy as np
   ...:
   ...: (
   ...:     np.linalg.norm(Operator(SXGate().control(3)) - Operator(C3SXGate())),
   ...:     np.linalg.norm(Operator(SXdgGate().control(3)) - Operator(C3SXGate())),
   ...: )
Out[1]: (1.9999999999999984, 6.088839805355096e-15)

What is the expected behavior?
C3SXGate should be consistent with SXGate().control(3).
Suggested solutions
Swap the negatives of the angles in C3SXGate.definition.  There's a fair amount more to do as well to ensure consistency - checking the equivalence library, QASM definitions, etc.

I have taken a look at it and it seems flipping the angles makes it work. I have tested the equivalence among these two comparing a circuit in which a C3SX gate was added with the SXGate with control, it passes the equivalence decomposition. What else is required for consistency?

The test suite doesn't pass if all you do is flip the angles in the C3SXGate class, because the C4XGate class depends on it for its definition, and there's also a redefinition in the QASM 2 library file qelib1.inc (and a c4x in there too).  Everything needs to stay consistent if one gate changes.  There don't appear to be any defined equivalences in the equivalence library, so that part's not a problem.
However, I'm not even sure if the change is correct - I don't know if there's context as to why the C3SXGate disagrees with SXGate.control(3); there might be a reason for the redefinition.  After all, this form of C3SXGate applied twice still does produce a C3XGate, so in a vacuum, it's not entirely wrong.
Perhaps @Cryoris knows more - the gate was added in #5668.

Well, maybe the problem isn't in the C3SXGate class, because it is defined using the decomposition that is theoretically correct. Since the C4XGate also works fine using it as a base, maybe the problem isn't in the C3SXGate class, but rather there may be something funky going on in the control method of the SXGate class, with problems popping up with more than 2 units of control. Since the C4XGate and the XGate with 4 control bits is equivalent, maybe the phase transition could be changed in the SXGate to accomodate that.
Any thoughts on this ?

The control method is fine - it just defers to the standard Gate.control decomposition, and you can just see in the tensor-product structure of the output matrix that it's correct in this simple case.  If you construct the controlled gate matrix with np.kron, it's clear:
In [1]: import qiskit
   ...: import numpy as np
   ...:
   ...: np.set_printoptions(suppress=True)  # suppress very small values in prints
   ...:
   ...: sx = np.array(qiskit.circuit.library.SXGate())
   ...: control_state = np.array([0]*7 + [1])  # control on |111>
   ...: i3 = np.eye(8)
   ...: proj = np.outer(control_state.conj(), control_state)
   ...: np.kron(np.eye(2), i3 - proj) + np.kron(sx, proj)
Out[1]:
array([[1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0.5+0.5j, 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0.5-0.5j],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 1. +0.j , 0. +0.j ],
       [0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0.5-0.5j, 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0. +0.j , 0.5+0.5j]])

In [2]: np.array(qiskit.quantum_info.Operator(qiskit.circuit.library.C3SXGate()))
Out[2]:
array([[ 1. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  1. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  1. -0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j , -0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  1. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. -0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j , -0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. -0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. -0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j , -0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0.5-0.5j,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0.5+0.5j],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j , -0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. -0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. -0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j , -0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. -0.j ,  0. +0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j , -0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  1. -0.j ,  0. +0.j ],
       [ 0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0.5+0.5j,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0. +0.j ,  0.5-0.5j]])

The problem is that C3SXGate is giving exactly the same matrix as SXdgGate with 3 controls, not SXGate.  This is a naming convention issue, to some degree - both SXGate and SXdgGate could have been called SX, because applying either twice gets you an X, just like how either 1 or -1 is the square root of 1.  The issue is the inconsistency between the two.
Why do you say the current decomposition is theoretically correct?  It's producing the wrong result here, at least by the name of the class.

Well because it is defined according to the method described in  Barenco et al., 1995. in

n-bit networks.

But looking closer, the decomposition is supposed to start and end with a positive phase in the paper as opposed to starting and ending with the negative phase (pi/8) I guess but you can have a look

I think @wahaj is right, the decomposition in Qiskit has the wrong sign. The decomposition uses

where V should be H P(pi/8) H, since then V^4 equals the square root of X. Instead in the code it uses P(-pi/8).
If we fix that, we can also directly remove the deprecated angle keyword argument 🙂

I actually found this as part of trying to remove the angle keyword!  Still, though - if we remove the angle keyword, we won't have an efficient representation for C3SXGate().inverse() any more (though we can always just put in a C3SdgXGate in theory).
I think we're actually on the same page here - flipping the angles is the same as the replacement for V that you're talking about, and that's what I meant by the decomposition being incorrect.
I think the decomposition of C4XGate may be wrong in a related manner - it produces the correct result, but since it depends on C3SXGate with an incorrect phase convention, its decomposition is likely wrong as well, but just in a way that happens to cancel out.  For example, if I do Operator(C4XGate().definition) on the current main, it produces the correct result.  However, if I swap the phases of C3SXGate over, like discussed, then Operator(C4XGate().definition) gives me the identity matrix.  We then also need to swap the phases in the CU1Gate instances of C4XGate to make it work.
I've PR'd a fix in #7230.

Good question for the inverse but maybe the default inverse is actually good enough since that should just invert every gate which should do nothing but inverting the angle.

We'll need to redefine its inverse method to dodge ControlledGate's inverse which will mess everything up, but otherwise, yeah, it should work.  I suppose it'll invert the order of the gates as well, but that's no big deal.


entire thread closes on window close, using another thread is not allowed by winit.

i noticed that closing a window closes the entire thread, how can i make it so that the program continues after the window is closed?
im not able to run iced on another thread besides the main thread as i get this when i try:
Initializing the event loop outside of the main thread is a significant cross-platform compatibility hazard. If you really, absolutely need to create an EventLoop
on a different thread, please use the `EventLoopExtWindows::new_any_thread`

i'd also like to point out that there is a problem with sharing COMs on certain threads. for example in one of my programs my main function calls CPAL's audio thread before starting my iced GUI, but im given an error about different COM modes. I have to get to a math assignment right now so i will post about the COM problem later. thanks!

Fixed by #1112!


added a gantt table component named jz-gantt

General

✏ Mark the necessary items without changing the structure of the PR template.

[x] Pull request template structure not broken

Type

ℹ  What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Fix
[x] Feature

Checklist

ℹ  Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉  Put an x in the boxes that apply.

[x] Title as described
[x] Make sure you put things in the right category!
[x] Always add your items to the end of a list

Open Source

[x] Link description does not contain a link to an author / third-party resource
[x] The documentation (README) contains a description of the project, illustration of the project with a demo or screenshots and a CONTRIBUTING section
[x] The documentation is in English.
[x] The project is active and maintained.
[x] The project accepts contributions.
[x] Not a commercial product

Apps/Websites

[ ] The website is available without errors or ssl certificate problems, and load in a reasonable amount of time.
[ ] The website is using vuejs intensively. It should detect vue with vue-devtools.

If you cannot detect vue with vue-devtools due to work at non public pages (e.g. for enterprise website), you can send Pull Request with screenshot that detected it.

[ ] The website is original and not too simple. For that reason, blogs and simple landing pages are rejected.
[ ] A commercial product using Vue, provided that guests could reasonably check out how Vue was used (i.e. A headless CMS which uses Vue for the Admin/editor Area and offers a free tier).

It has been modified as required

It has been modified as required. vue to Vue

@jeremyjone need resolve conflicts

@Scrum  Conflict resolved. :)

Sorry, I didn't notice it. I have revised

Sorry, I didn't notice it. I have revised

Please, create a new PR


Add airbnb config using plugins rules

Clear and concise description of the problem
It would be nice to have a config with this plugin's rules emulating the Airbnb style guide instead of having to copy their whole ruleset and tweak it to no longer use deprecated rules. It's not possible to get all the way to Airbnb style with just the configuration factory.
Suggested solution
Create a default config mirroring airbnb's style rules.
Alternative
Add enough options to the configuration factory to reach Airbnb style that way.
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Contributes

[ ] If this feature request is accepted, I am willing to submit a PR to fix this issue

I think it would be easier for Airbnb to update their config to migrate over - we can't fork and maintain every config set (hard to sync with as well) - it's also not in the scope of this project.

Hey, sorry for necrobumping
If you still need AirBnb style, I created a port of original airbnb eslint rules using @stylistic plugin rules
https://www.npmjs.com/package/eslint-stylistic-airbnb


Feature request: Access to RetroArch through Steam UX

Would it be possible to get a shortcut to launch RetroArch manually and be able to take advantage of the full application? Not necessarily replacing the existing ROM upload method but some people might have large collections and a bulk upload and launching through RetroArch might be easier for some.

The idea is to hide RetroArch because it is not user friendly. If you would like to use RetroArch, then Steam RetroArch is always an option.

I forgot to mention you can also add your own shortcuts, which could include launching RetroArch itself. See here for details: https://github.com/chimeraos/chimera#steam-shortcuts-chimera---shortcuts


Hello, can hyperparameter optimization be done for multi-objective problems?

Hello, can hyperparameter optimization be done for multi-objective problems?

I would like to call out the pymoo has not been designed for hyperparameter optimization.
However, you can use the example for mixed variables: https://pymoo.org/customization/mixed.html


Is finetuning of LLaVA-CoT not available yet? (2024/11/26)

Thank you for releasing this model. I tried finetuning this model with my custom dataset using this script from LLaVA. However, I think I will have to set the version, visual encoder, and so on in order to use the model for finetuning, so I don't think I can do that now.
So far, since it says "Stay tuned! Our code, dataset, and pretrain weights are coming soon." here (2024 November 26th), is finetuning not available at the moment? If so, how can I finetune this model for now?
Thank you.

No, you can finetune the model using exactly the method as Llama-3.2-11B-Vision-Instruct. Most finetuning libraries support Llama-3.2-Vision, and we used https://github.com/Meta-Llama/llama-recipes. You may follow the instructions here: https://github.com/meta-llama/llama-recipes/blob/main/recipes/quickstart/finetuning/finetune_vision_model.md

Thank you for that. But since I am not familiar with Llama-recipe, did you have to upload the custom dataset to Huggingface? I can try it as well but I am thinking of using the dataset in my local directory of my linux server.
I think I am suffering for the dataset setting since the settings for that are quite different from LLaVA-v1.5 and v1.6 on which I have been originally focusing on.

Yes, the dataset is available at https://huggingface.co/datasets/Xkev/LLaVA-CoT-100k.
The dataset format is actually very similar to LLaVA-v1.5 and v1.6.
If you need further help on the dataset format conversion, I can help with that.


Сannot pull images

Hello everyone, the following error occurs: cannot pull images.
Could this be because I'm using a custom Docker registry? Or is there an error in something else? If I simply make a curl request like curl https://quay.io/v2/stackrox-io/scanner-db/manifests/4.1.2, everything is displayed successfully.
Here is the output of the command "kubectl describe pod scanner-db-d94f4cc77-sbc8m":
`Name:             scanner-db-d94f4cc77-sbc8m
Namespace:        stackrox
Priority:         0
Service Account:  scanner
Node:             cl1s0kq580gglkll6f9v-yzed/<IP_ADDRESS>
Start Time:       Fri, 28 Jul 2023 15:56:25 +0000
Labels:           app=scanner-db
app.kubernetes.io/component=scanner
app.kubernetes.io/instance=stackrox-central-services
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=stackrox
app.kubernetes.io/part-of=stackrox-central-services
app.kubernetes.io/version=4.1.2
helm.sh/chart=stackrox-central-services-400.1.2
pod-template-hash=d94f4cc77
Annotations:      email<EMAIL_ADDRESS>meta.helm.sh/release-name: stackrox-central-services
meta.helm.sh/release-namespace: stackrox
owner: stackrox
traffic.sidecar.istio.io/excludeInboundPorts: 5432
Status:           Pending
IP:               <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/scanner-db-d94f4cc77
Init Containers:
init-db:
Container ID:
Image:          quay.io/stackrox-io/scanner-db:4.1.2
Image ID:
Port:
Host Port:
State:          Waiting
Reason:       ImagePullBackOff
Ready:          False
Restart Count:  0
Limits:
cpu:     2
memory:  4Gi
Requests:
cpu:     200m
memory:  200Mi
Environment:
POSTGRES_PASSWORD_FILE:  /run/secrets/stackrox.io/secrets/password
ROX_SCANNER_DB_INIT:     true
Mounts:
/run/secrets/stackrox.io/certs from scanner-db-tls-volume (ro)
/run/secrets/stackrox.io/secrets from scanner-db-password (ro)
/var/lib/postgresql/data from scanner-db-data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5dhzd (ro)
Containers:
db:
Container ID:                             Image:          quay.io/stackrox-io/scanner-db:4.1.2
Image ID:
Port:           5432/TCP
Host Port:      0/TCP
State:          Waiting
Reason:       PodInitializing
Ready:          False
Restart Count:  0
Limits:
cpu:     2
memory:  4Gi
Requests:
cpu:        200m
memory:     200Mi
Environment:
Mounts:
/run/secrets/stackrox.io/certs from scanner-db-tls-volume (ro)
/var/lib/postgresql/data from scanner-db-data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5dhzd (ro)
Conditions:
Type              Status
Initialized       False
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
scanner-config-volume:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      scanner-config
Optional:  false
scanner-tls-volume:
Type:        Secret (a volume populated by a Secret)
SecretName:  scanner-tls
Optional:    false
scanner-db-tls-volume:
Type:        Secret (a volume populated by a Secret)
SecretName:  scanner-db-tls
Optional:    false
scanner-db-data:
Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
scanner-db-password:
Type:        Secret (a volume populated by a Secret)
SecretName:  scanner-db-password
Optional:    false
kube-api-access-5dhzd:
Type:                    Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds:  3607
ConfigMapName:           kube-root-ca.crt
ConfigMapOptional:       ConfigMapOptional:
DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type     Reason             Age                    From                Message

Normal   NotTriggerScaleUp  12m (x31 over 17m)     cluster-autoscaler  pod didn't trigger scale-up:
Warning  FailedScheduling   12m (x2 over 17m)      default-scheduler   0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Normal   Scheduled          9m50s                  default-scheduler   Successfully assigned stackrox/scanner-db-d94f4cc77-sbc8m to cl1s0kq580gglkll6f9v-yzed
Warning  Failed             9m19s                  kubelet             Failed to pull image "quay.io/stackrox-io/scanner-db:4.1.2": rpc error: code = DeadlineExceeded desc = failed to pull and unpack im
age "quay.io/stackrox-io/scanner-db:4.1.2": failed to resolve reference "quay.io/stackrox-io/scanner-db:4.1.2": failed to do request: Head "https://quay.io/v2/stackrox-io/scanner-db/manifests/4.1.2": dial
tcp <IP_ADDRESS>:443: i/o timeout
Warning  Failed             8m35s                  kubelet             Failed to pull image "quay.io/stackrox-io/scanner-db:4.1.2": rpc error: code = DeadlineExceeded desc = failed to pull and unpack im
age "quay.io/stackrox-io/scanner-db:4.1.2": failed to resolve reference "quay.io/stackrox-io/scanner-db:4.1.2": failed to do request: Head "https://quay.io/v2/stackrox-io/scanner-db/manifests/4.1.2": dial
tcp <IP_ADDRESS>:443: i/o timeout
Warning  Failed             7m38s                  kubelet             Failed to pull image "quay.io/stackrox-io/scanner-db:4.1.2": rpc error: code = DeadlineExceeded desc = failed to pull and unpack im
age "quay.io/stackrox-io/scanner-db:4.1.2": failed to resolve reference "quay.io/stackrox-io/scanner-db:4.1.2": failed to do request: Head "https://quay.io/v2/stackrox-io/scanner-db/manifests/4.1.2": dial
tcp <IP_ADDRESS>:443: i/o timeout
Normal   Pulling            6m56s (x4 over 9m49s)  kubelet             Pulling image "quay.io/stackrox-io/scanner-db:4.1.2"
Warning  Failed             6m26s (x4 over 9m19s)  kubelet             Error: ErrImagePull
Warning  Failed             6m26s                  kubelet             Failed to pull image "quay.io/stackrox-io/scanner-db:4.1.2": rpc error: code = DeadlineExceeded desc = failed to pull and unpack im
age "quay.io/stackrox-io/scanner-db:4.1.2": failed to resolve reference "quay.io/stackrox-io/scanner-db:4.1.2": failed to do request: Head "https://quay.io/v2/stackrox-io/scanner-db/manifests/4.1.2": dial
tcp <IP_ADDRESS>:443: i/o timeout
Warning  Failed             6m1s (x6 over 9m19s)   kubelet             Error: ImagePullBackOff
Normal   BackOff            5m46s (x7 over 9m19s)  kubelet             Back-off pulling image "quay.io/stackrox-io/scanner-db:4.1.2"
Warning  Failed             4m28s                  kubelet             Failed to pull image "quay.io/stackrox-io/scanner-db:4.1.2": rpc error: code = Unknown desc = failed to pull and unpack image "quay
.io/stackrox-io/scanner-db:4.1.2": failed to resolve reference "quay.io/stackrox-io/scanner-db:4.1.2": failed to do request: Head "https://quay.io/v2/stackrox-io/scanner-db/manifests/4.1.2": dial tcp 3.23
4.28.1:443: i/o timeout
`

@agorbovv Does this problem still exist?
If yes, can you provide the following information:

Does it happen for all images or only scanner-db?
Did you use curl from within the cluster? (i.e., from cluster container)

This looks like it was due to a networking issue. I was just able to pull the image.


Angular Query's data signal is not updating if data is present in the cache

Describe the bug
I am facing an issue with Angular Query regarding query.data signal not emitting new value when the query key changes AND there is already data in the cache
In the devtools the active query is updating as expected but the data signal still has the data of the old (now inactive) query
If data is not in the cache it works as expected by calling the query fn and the data signal emits the latest value
Your minimal, reproducible example
https://github.com/shessafridi/angular-query-data-issue
Steps to reproduce
How to reproduce the issue

Open the browser's console
Click the "Search" button
You will see a message with the start and end date after 2 seconds
Change the date and click the "Search" button again, you should see the message for that date appear as well
Now go back to the date you started with and click "Search" again, you will see the query for that date become active again but this time no message is being logged to the console and the UI is still showing the data for the old date

Expected behavior
I expect the query.data signal to emit new data when the a new query becomes active
How often does this bug happen?
None
Screenshots or Videos
No response
Platform
OS: Windows 11
Browser: Chrome
Angular Query Version: 5.14.2
Tanstack Query adapter
None
TanStack Query version
5.14.2
TypeScript version
5.2.2
Additional context
No response

@arnoud-dv FYI

Thank you for adding the detailed issue with reproduction. When looking at your reproduction it does indeed look like a bug in the Angular adapter. I will look into this if I can find the cause and fix it.

Fixed in v5.14.6


vimPlugins.staline-nvim: init at 2024-02-14

Description of changes

Things done

Built on platform(s)

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

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

[x] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

plugin authors sure know how to name their plugins, waiting for leninvim.

plugin authors sure know how to name their plugins, waiting for leninvim.

Hahahaha


Support for null safety

fixes #2

Thank you so much for contributing @niku!
happy Hacktoberfest!


V 1.1.0

Fixes : https://github.com/NRCHKB/node-red-contrib-unifi-os/issues/73
Fixes  : https://github.com/NRCHKB/node-red-contrib-unifi-os/issues/72
Fixes : https://github.com/NRCHKB/node-red-contrib-unifi-os/issues/51

Adds Line Crossing event support
Attempts to decode Gzip Responses
Improves  websocket management

That is a lot of lines

1 problem (on the Unifi end) I have discovered
If multiple Lines are added to a camera, it does not show the state of them  - they are still In the payload, but not their state.
When the camera has 1 Line :
payload.metadata.linesStatus exists
When the camera has > 1 Line(s) :
payload.metadata.linesStatus does not exists
Not sure we can fix that, as its a problem, in the original payload form Unifi
🤷

Push it!
Push it real good!

I don't even see anywhere on the official webpage or app where it will show which line was crossed...

Something is better than nothing - push it. Hope in some new updates, we will get info which one was crossed.

Beta available.
within the .node-red dir.
npm install node-red-contrib-unifi-os@dev

@Supergiovane
Has your system been stable since your contriubtion (that I have merged into this PR)?
I want to do a release maybe today - providing you have not needed to address any issues since?

@Supergiovane
Has your system been stable since your contriubtion (that I have merged into this PR)? I want to do a release maybe today - providing you have not needed to address any issues since?

Hi
Yes, rock solid.


w3signer support

Every validator client implements https://github.com/Consensys/web3signer.
The w3s will hold the keys to sign the duties that the validator sends. And the validator does not hold any private keys but ask the w3s to sign.
It would be great if kurtosis would support w3s for 'genesis', so instead of inserting the private keys on the validators, it would use the w3s keymanager API to import them.
(https://consensys.github.io/web3signer/web3signer-eth2.html#tag/Keymanager)

Hey @franjoespejo - thanks for sharing the context in Discord and for filing this Feature Request! I support the addition of this!
Can you put up a PR for this? We'd be more than happy to review & help you implement your suggestion - but do not currently have the bandwidth to make these changes ourselves. Thank you!

Some research - might have to tls generate certs but mostly not;

https://github.com/Consensys/web3signer - this is the web3signer repo; 130 :star: . They seem to support mainnet and other testnets, and have overridable epochs / trusted nets; so theoretically should work with KT
Prysm - has no support for them but has a README that link s to an issue which is OPEN  :x: https://github.com/prysmaticlabs/prysm/blob/867db1aeee8eb603871d54a9161030d7aabf198f/validator/keymanager/remote-web3signer/README.md?plain=1#L4
Nimbus supports web3signer - https://github.com/status-im/nimbus-eth2/blob/cfa0268d89461bfcba75a6d15e994037a0527726/docs/the_nimbus_book/src/web3signer.md?plain=1
LodeStar has support for them but no docs - https://github.com/ChainSafe/lodestar/blob/1aa656191c84e3b55281bb8f21c9f4a529282500/packages/cli/src/cmds/validator/options.ts#L52 they have an issue about the docs for setting this up; i think they call it externalSigner internally
Lighthouse - has support and calls using it risky- https://github.com/sigp/lighthouse/blob/441fc1691b69f9edc4bbdc6665f3efab16265c9b/book/src/validator-web3signer.md?plain=1#L2
Teku has support for it too  - https://docs.teku.consensys.net/how-to/use-external-signer/use-web3signer

It looks like a few days of work.
@franjoespejo Do you know any other teams or devs that could use the etheruem-package if we supported web3signer? I am willing to put time into this if we have a few more people lined up to use it.

Copy-pasting what @franjoespejo shared with us on Discord about this:

To be honest having this w3s support does not enable new cases with Kurtosis for us, it just would save us one step: looking for priv-keys within the kurtosis validator container and moving them to the w3s.

Action: given resource and time constraints, we're going to keep this Github issue on the back burner for now and revisit if more people ask for it. Alternatively, we welcome outside contributions as well & are available to assist where needed.

@franjoespejo I am closing this as you have already started working on the diva-package!


[Issue] - Health Checker - no indication that Windows Extended Protection is enabled

Provide Version Number
Provide the version of the script that has the issue.
<IP_ADDRESS>8
Describe the issue
A clear and concise description of the issue.
once Windows Extended Protection is enabled (i used the script) i don't see any indication in the healthchecker script that it is enabled aside from no longer seeing the list of IIS virtual directories that previously showed u in the Security Vulnerability section
Expected behavior
A clear and concise description of what you expected to happen.
i would expect to see an indication in the healthchecker script that the Extended Protection is enabled (like for AMSI and Emergency Mitigation Service) given it does indicate when its not configured
Script Output
If applicable, add the exception that wasn't handled.
Additional context
Add any other context about the problem here.

This is correct, by design we are only going to show the current settings of the Extended Protection if something is configured to the unrecommended setting it is a security vulnerability, thus showing the results.
If there is no security vulnerability, we don't show the results.
In the Exchange Information section, you should see a new property that will show you that Extended Protection is enabled.

We should see this section, is this not good enough? Or should we have something else?

thanks so much i see it now
i missed that line as i was looking for the extended protection stuff down at the bottom

thanks so much i see it now
i missed that line as i was looking for the extended protection stuff down at the bottom

If you think we should show this in a different fashion, let us know.

i can see why you chose to put it in the exchange information section instead of the security settings area. i was expecting it to be in security settings which is how i think i just skipped right over it in my initial scan of the results post implementation
it does feel that there is so much IIS specific setup/tuning now required on these exchange systems that it might be worth having a dedicated "IIS settings" area (which might also be a good place to put security headers information in the future)
thanks so much for all the work you folks do on this tool. its a real time saver for me these days


Fix: regex

The current regex does not handle all cases for github remote URLs, this PR fixes that.
Link to proof for all cases I could come up with: https://regex101.com/r/hQlSdz/1

Thank you @liss-h 🎉🚀


how to install on mac

how to install on mac

I haven't tried this myself, but you can probably get away with following the Manual Installation instructions on the documentation page.  Of course you won't be able to use apt-get, but you can use whatever package manager you have installed.
As long as you get all the dependency packages installed, jasper should work correctly.
If you attempt this, please record your steps and post them to this issue.  It would be nice to have step-by-step instructions on how to achieve this on Mac.

Yes please! Id love to get it installed on my MAC..

I have it working easily, just message me.

I was going to write an installer, I just haven't had time; or a blank mac to test on...


unregister device

I have a settings menu where the user can set push notifications to on or off.
What I do now is window.FirebasePlugin.unregister();
If I do that, than I don't get any notifications anymore, which is great.
But if I want to register again with  window.FirebasePlugin.getToken() , I do not get any notifications anymore. So I can't register again.
What am I doing wrong ?

Hey, I have the same issue. I only use topics and I accidently unregistered(), now I don't know how to register back. Any idea ?

Is this the same issue I found at Stackoverflow, because I have an issue with Android (same as in the SO post mentions). Unregistered device still gets notifications..

Yes it is the same issue, I asked that question on stackoverflow.

OK!
I just tried to fix it on Android by commenting out some code at platforms\android\src\org\apache\cordova\firebase\FirebasePlugin.java (ionic v1 project):
private void unregister(final CallbackContext callbackContext) {
        cordova.getThreadPool().execute(new Runnable() {
            public void run() {
                try {
                    FirebaseInstanceId.getInstance().deleteInstanceId();
                    /*
                    String currentToken = FirebaseInstanceId.getInstance().getToken();
                    if (currentToken != null) {
                        FirebasePlugin.sendToken(currentToken);
                    }
                    */
                    callbackContext.success();
                } catch (Exception e) {
                    callbackContext.error(e.getMessage());
                }
            }
        });
    }

It seems that the code was getting a new token right after unregistering the current one. Now it's working as expected on Android at least.

I've tried that with iOS by commenting out this code
- (void)unregister:(CDVInvokedUrlCommand *)command {     [[FIRInstanceID instanceID] deleteIDWithHandler:^void(NSError *_Nullable error){         if (error) {             NSLog(@"Unable to delete instance");         } else {             /*NSString* currentToken = [[FIRInstanceID instanceID] token];             if (currentToken != nil) {                 [self sendToken:currentToken];             }*/             CDVPluginResult *pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK];             [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];         }     }]; }
But that didn't work. I still can't register again.

I have this bug too. At least on Android, haven't tested iOS. I get a new token and continue to receive push notifications right after I've run the unregister() function.

@Regicollis  I have solved it (#522)

closing as resolved, see comment


New version: Nvidia.GeForceExperience version <IP_ADDRESS>

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

To whoever manually validating, its failing with the error code<PHONE_NUMBER> because it requires a NVIDIA GPU.


How to work with async loop and file descriptor

I'm working with asyncio loop and I would like to await a nfqueue.run(block=False) function.
I read that I could do that with the nfqueue.get_fd() method but this method seems to only return a integer.
I really don't understand the concept of file descriptor and how to use them.
Could someone help me please ?

I'm not an asyncio expert but I think something like this will work (once you're already inside an asyncio.run() context):
loop = asyncio.get_event_loop()

def on_readable():
    nfqueue.run(block=False)

loop.add_reader(nfqueue.get_fd(), on_readable)

The file descriptor is indeed a plain old integer, but one that has special meaning to the operating system: it represents an open file, socket, or other thing you can do I/O on. The netfilter queue is implemented using a special kind of socket, so you can wait for it to have data available to read, in the same way you would for any other socket. And then when there is data available to read, you call run(block=False) to tell the netfilterqueue library to read everything that's currently available, but not wait for more things after that.

I have a better understanding of file descriptors and I can progress in my work with this little piece of code now.
Thank you very much!
I have another question if you don't mind. Does the netfilterqueue library work with nftables instead of iptables?

Yes, nftables should work too, but the syntax for setting up a firewall rule to route to the queue is different. https://wiki.nftables.org/wiki-nftables/index.php/Queueing_to_userspace -- it's the same mechanism inside the kernel, so the  netfilterqueue library doesn't care whether you're using nftables or iptables as long as you give it the same queue number listed in your firewall rule.

Ok! Thank you again!


Load Gradle properties earlier at launch

This PR changes launcher build stages to load Gradle properties as a first stage, before loading settings.
This makes Gradle properties available earlier allowing for instant execution to properly check if it is enabled, paving the way to use regular "build options" to add a command line flag & co in a normal way (drafted in https://github.com/gradle/gradle/pull/13076). Instant execution can now also use a correct settings location when loading its cache.
This also makes system properties from gradle.properties available to init scripts for buildSrc. Due release notes for this behavioural change are missing and would be added after a first round of review.

I think this is overly complex, because it basically adds work arounds for existing complexity. The result would end up simpler if we instead address the existing complexity.
The actual structural problem is basically down to the fact that when we read the properties from gradle.properties, we also mutate System.getProperties(). I think it would be better to decouple these two steps, so that we can load and query the properties as early as we like, while keeping backwards compatible behaviour for mutating System.getProperties() and making the values visible to the various builds in the tree.
Specifically, I would:

Move the mutation of System.getProperties() from DefaultGradlePropertiesLoader up to DefaultGradlePropertiesController.loadGradlePropertiesFrom(), so that the mutation continues to happen at the same time it does now. This way, we don't need to deal with breaking changes at this point. Maybe we want to deal with that issue at some later time, but we should avoid doing this now, because we don't need to.
Load the properties earlier, either on demand when queried or in the controller's constructor. The settings directory is known as soon as the build scope is created, so this can be injected into the controller's constructor.

@adammurdoch, I tried to follow your advice but it leads to different breakages.
Just moving system properties mutation up to the controller doesn't change the fact that properties are loaded too late.
Then, if loading the properties in the controller constructor, it makes project properties visible in buildSrc and included builds which is a breaking change.
If using the settings dir from injected BuildLayout in the controller it breaks composite builds by letting root build properties shadow included builds properties.
So, I'm basically stuck and don't know how to proceed with your comments. Please advise.

It sounds like you still need to separate loading the properties from files and mutating the System properties map. We can load properties from files into some in-memory map at any time during the session, but we can't mutate the System properties map using the contents of this in-memory map until a fixed point in time.
So, the constructor of the controller should load the properties from the files and create and retain a map containing the effective merged properties, but it should not do anything more than this. The controller method loadGradlePropertiesFrom(dir) should be replaced by something like applyToSystemProperties() which takes the values from the effective properties map and mutates System.getProperties(). This should still be called from the same place that loadGradleProperties() is called so as to not affect the visibility.
Then, in order to decide whether a build option is enabled or not, we would look in the effective properties map that the controller built. We would not look in System.getProperties(). We should also probably change the value supplier to do the same.

Thanks. So, read the properties files early and query that for features that require early enablement. Then, later, same time as now, do the rest of "loading gradle properties" merging system properties. I think it also brings back complexity we've been trying to remove because then "loading system properties" has two phases.  But it might be less complex than the current set of changes in this PR.
Loading the properties files requires locating the settings dir though, and init scripts will still be allowed to mutate the start parameters that influence locating the settings dir, potentially leading to undefined/changed behaviour. Would it make sense to freeze those properties once the properties files are loaded making such mutation throw (currentDir, searchUpwards, settingsFile and useEmptySettings)?

Depends what we mean by "merging system properties". If it means looking for system properties whose name starts with org.gradle.project. in order to define some Gradle properties, then I would do this early. This is not intended to be used by build logic but only via JVM args. But for backwards compatibility, we can do this when applyToSystemProperties() is called. Either way, we could look at using our instrumentation to disallow build logic from settings these properties. For me, this is still less complex than where we started, because we've detangled these different pieces of the lifecycle so that they are explicit and can be applied at different points in time, including having a bunch of properties that we can query at the start of the build session.
Regarding mutating the StartParameter properties, I'd be surprised if this works. There are a bunch of things that query these properties early (including the instant execution stuff) and would ignore changes already. I would calculate the properties early as well and deprecate mutating those properties from build logic. I probably wouldn't throw an exception on mutation as it doesn't fail now (which is different to the change being ignored).

Then, in order to decide whether a build option is enabled or not, we would look in the effective properties map that the controller built. We would not look in System.getProperties().

I think this is another breaking change because then enabling build options via system properties wouldn't work anymore.

Regarding mutating the StartParameter properties, I'd be surprised if this works. There are a bunch of things that query these properties early (including the instant execution stuff) and would ignore changes already. I would calculate the properties early as well and deprecate mutating those properties from build logic.

Right. And that would make my previous comment about enabling build options via system properties on the command line irrelevant.
Thanks!

I tried to spike this strategy in https://github.com/gradle/gradle/compare/eskatos/cc/load-gradle-properties but it also has some side effects https://builds.gradle.org/buildConfiguration/Gradle_Check_Stage_QuickFeedbackLinuxOnly_Trigger/34870641?buildTab=dependencies&mode=list&state=failed

Working on a new simpler change, will open another PR

Take 2 at https://github.com/gradle/gradle/pull/13131


Shorten name by using ellipsis.

But this is the only way to get readable sink otherwise we just
have the prefix which are all equals. "Audio interne Stéréo analogique".

Not sure this is the best solution but as least I cannot now properly select the proper sink.

Thank you for your merge request, I'll review in more detail in the following days.

Hello ! Any news about this ?

Hi! I haven't had a lot of time to focus on my side projects.
Altough I am running an older version of the extension of my system ellipsis are automatically for long menu strings, this is not the case on more recent versions of Gnome? (I'm still running 3.30)
See below a screenshot of my system:

Could you share a screenshot of what is happening on your system perhaps?

No I have ellipsis but at the end. But the ellipsis are coming after a common long prefix (maybe because of French translation), so I have many entries like:
Audio interne Stéréo analogique...
Audio interne Stéréo analogique...

Because real names are:
Audio interne Stéréo analogique on arthur
Audio interne Stéréo analogique on salon

Where atrthur and salon are computer names on my network.

I misundertood what you intended to do (sorry) ! I though you were adding ellipsis at the end of the string, and I was not undertanding why that would solve your issue. After running the name of your devices in the fuction you wrote I get it now. I should have read the code more carefully ;)
End result: Audio int...analogique on arthur
I have mixed feelings about this because I feel that I might be solving your use case, but breaking some one else because the string is now cut in the middle. I will need to think about this, one way out would be to make this an option, but I would like to avoid that.


Documentation Needs to be Updated

File: compose/install.md
The documentation states "The instructions below outline installation of the current stable release (v2.5.0) of Compose." When you look below in large bold text "Uninstallation" it gives instructions for how to uninstall compose. This should be updated. It's confusing. There is a link that goes to the install instructions but seeing as the page is specifically for install and not uninstall, the uninstall instructions should be on it's own page.

Thanks for sharing the issue. The uninstall instructions were moved in https://github.com/docker/docker.github.io/commit/d49af6a4495f653ffa40292fd24972b2df5ac0bc


Update mentions of Offset.Earth to Ecologi

Hi @jordmondson and thank you very much for this contribution.
It's something I have been meaning to do for a long time now.


"Paath=" chack is case sensitive and won't work on many machines.

[Enter feedback here]
This doesn't actually work on my machine (and many more, I would guess) because the "Path="  test is case sensitive.
The Line
<If Left(EnvString, 5) = "PATH=" Then    ' Check PATH entry.>
should read
<If Left(UCase(EnvString), 5) = "PATH=" Then    ' Check PATH entry.>
Doing this makes the check case insensitive.

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

ID: 3476023f-79e8-05db-c11d-8f8a25f0ff35
Version Independent ID: 8ab5d342-ca9e-8b8b-5a02-d83c92a20d9e
Content: Environ function
Content Source: Language/Reference/User-Interface-Help/environ-function.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

@RadioPlanner13 Thanks for your feedback. We use Github issues for documentation bugs, not for developer support. Please try the VBA developer community on Stack Overflow (https://stackoverflow.com/questions/tagged/vba) where you can get help from actual developers. If you find a bug in our documentation, please let us know. Thanks!


update document

You can also configure how locally defined lists are combined or merged with globally defined lists. This setting applies to exclusion lists and specified remediation lists and [Exploit Guards ASR rules].

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

ID: fcbd9d0e-c614-6a48-e70d-4daedcb9a670
Version Independent ID: e2c5a8e5-9beb-6e3f-a566-6b134dd1885f
Content: Configure local overrides for Windows Defender AV settings
Content Source: windows/security/threat-protection/windows-defender-antivirus/configure-local-policy-overrides-windows-defender-antivirus.md
Product: w10
Technology: windows
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@Simon-MS. I agreed your points. Because I usually configured by GPO and also by registry keys.

@Simon-MS, @illfated, and @RAJU2529 thank you for the feedback and discussion. I've updated this article to include attack surface reduction in the sentence in question, and added a link to that content. Please let me know if you have any additional feedback. I'm closing this issue for now, with kind regards.