Error building the latest master

So I wanted the latest and greatest commits on master, but I keep getting compilation errors from tsc. I tried node-4.x and 5.x. I tried with tsc 1.7.3 and then by updating to 1.7.5. But the errors persist.
Error:
Using tsc v1.7.5
/home/ubuntu/dopp/doppio/src/ClassData.ts(1384,7): error TS2346: Supplied parameters do not match any signature of call target.
/home/ubuntu/dopp/doppio/src/jvm.ts(198,15): error TS2346: Supplied parameters do not match any signature of call target.
/home/ubuntu/dopp/doppio/src/jvm.ts(217,7): error TS2346: Supplied parameters do not match any signature of call target.
/home/ubuntu/dopp/doppio/src/jvm.ts(225,7): error TS2346: Supplied parameters do not match any signature of call target.
/home/ubuntu/dopp/doppio/src/natives/java_lang.ts(711,24): error TS2305: Module 'JVMTypes' has no exported member 'JVMFunction'.
/home/ubuntu/dopp/doppio/src/natives/java_lang.ts(1246,5): error TS2346: Supplied parameters do not match any signature of call target.
/home/ubuntu/dopp/doppio/src/natives/java_security.ts(13,3): error TS2346: Supplied parameters do not match any signature of call target.
/home/ubuntu/dopp/doppio/src/natives/java_util.ts(215,34): error TS7017: Index signature of object type implicitly has an 'any' type.
/home/ubuntu/dopp/doppio/src/natives/java_util.ts(323,79): error TS2305: Module 'JVMTypes' has no exported member 'java_util_zip_Deflater'.
/home/ubuntu/dopp/doppio/src/natives/java_util.ts(385,78): error TS2305: Module 'JVMTypes' has no exported member 'java_util_zip_Inflater'.
/home/ubuntu/dopp/doppio/src/natives/sun_reflect.ts(127,20): error TS2305: Module 'JVMTypes' has no exported member 'JVMFunction'.
/home/ubuntu/dopp/doppio/src/natives/sun_reflect.ts(179,18): error TS2305: Module 'JVMTypes' has no exported member 'JVMFunction'.
/home/ubuntu/dopp/doppio/src/natives/sun_reflect.ts(181,18): error TS2305: Module 'JVMTypes' has no exported member 'JVMFunction'.
/home/ubuntu/dopp/doppio/src/threading.ts(830,13): error TS2346: Supplied parameters do not match any signature of call target.
/home/ubuntu/dopp/doppio/src/threading.ts(830,55): error TS7006: Parameter 'e' implicitly has an 'any' type.

The errors mostly seem to be related to JVMTypes not exporting some members.

Delete includes and rebuild. The build system is too dumb to know that it needs to regenerate them after the recent change I made to function signatures.

That worked, thanks!
I don't want to spam you with issues, so asking here itself:
Is there a way to detect, at runtime, if the doppio build is a dev build or a release build? I want to ensure that our tests always use the dev build.

You can spam me with issues; that's not a problem. So far, you've helped me identify what's important to end users.
I just added a function to do just that: isReleaseBuild() is a static method on the JVM class.
Also, note that there is a fast-dev build that removes tracing functionality (-Xlog vtrace /-Xlog trace), but keeps the assertion functions. It's faster than a full dev build.


Mupx deploy error

I get the following error when I try to deploy my app error: npm-container is not compatible with architecture 'os.linux.x86_64'. The DEBUG command isn't helpful either.

+1 on Digital Ocean

Also running into the same issue.

Maybe something in this thread will help...
https://github.com/meteorhacks/npm/issues/40

Yes exactly. This is when you've a binary NPM module. Meteor does not allow to do that via meteorhacks:npm. You need to wrap it as a Meteor package and build binaries.
@MasterJames's link has all the info.
Also, someone else may also got this issue. So check atmosphere as well.

Would this explain why MUP is working but not MUPX?
I am not having this issue with MUP, but I am having this issue with MUPX.

Yes. Mup try to build them on the server. That's leads a lot of runtime
issues.
Yeah! I'd like to see this on README. Can you send me a PR?
On 2015 සැප් 18, සිකු at පෙ.ව. 9.05 Pat Brown<EMAIL_ADDRESS>wrote:

Would this explain why MUP is working but not MUPX?
I am not having this issue with MUP, but I am having this issue with MUPX.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/588#issuecomment-141334671.

To be clear: the runtime issues you're talking about are for MUPX, not MUP (as stated), right?

Nope. It's for mup. This is not the runtime issue I mentioned.
While we are building npm modulus on the server in mup, it introduced a lot
of issues because of the environment in the server. Mup has no control over
that. That's why we removed it from mupx.
Meteor deploy also act like mupx. That was another reason for this choice.
On 2015 සැප් 18, සිකු at පෙ.ව. 9.25 Pat Brown<EMAIL_ADDRESS>wrote:

To be clear: the runtime issues you're talking about are for MUPX, not MUP
(as stated), right?
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/588#issuecomment-141336384.

Ok, I see.  I just (wrongly) assumed that MUPX had more features rather than less.  :)
I'll get a pull request done.

i don't understand why this issue is closed if there is no clear solution stated anywhere... i mean, i get the error "error: this app is not compatible with architecture 'os.linux.x86_64'" without any details on why it's not compatible.. how i'm supposed to fix that? :'(
that didn't happen when using mup...


LoadError: cannot load such file after updating from 3.6.1 to 3.15.0

Deployments were working fine for several years with 3.6.1. As part of trying Ruby 3.0 migration we upgraded capistrano to 3.15.0 and getting the following error during deploy:
LoadError: cannot load such file -- capistrano/git
Capfile has:
require "capistrano/setup"
require "capistrano/multiconfig"
require "capistrano/deploy"
require "capistrano/scm"
require "capistrano/git"
require "capistrano/bundler"
require "whenever/capistrano"
require "time"
require "capistrano/scm/git"
We also tried by removing require "capistrano/git" and including:
require "capistrano/scm/git"
install_plugin Capistrano::SCM::Git
But with this we are getting:
cannot load such file -- capistrano/default-git.rb
Are we supposed to make some changes to Capfile when upgrading to 3.15.0?

Your Capfile should start like this, in this order:
require "capistrano/setup"
require "capistrano/deploy"
require "capistrano/scm/git"
install_plugin Capistrano::SCM::Git

# The rest of your custom config can go here:
require "capistrano/bundler"
require "whenever/capistrano"
require "time"

You can refer to the upgrade guide: https://github.com/capistrano/capistrano/blob/master/UPGRADING-3.7.md
You can also refer to the Capfile template that ships with 3.15.0: https://github.com/capistrano/capistrano/blob/v3.15.0/lib/capistrano/templates/Capfile
I see you have require "capistrano/multiconfig" before many of the standard capistrano require statements. I do not know what that does. It is not an official capistrano project. Perhaps it is not compatible with 3.15.0? You might want to check with its maintainers: https://github.com/railsware/capistrano-multiconfig


Not able to import colormaps from matplotlib

I tried installing gw_eccentricity in one igwn-py39 enviornment and import gw_eccentricity gives me the following error:
File ~/.local/lib/python3.9/site-packages/gw_eccentricity/plot_settings.py:4, in <module>
      2 from matplotlib import rc
      3 from cycler import cycler
----> 4 from matplotlib import colormaps
      6 dark2 = colormaps["Dark2"].colors
      8 colorsDict = {
      9     "default": dark2[1],  # brown
     10     "apocenter": dark2[3],  # dark2[2],  # purple
   (...)
     29     "blue": "tab:blue"
     30 }

ImportError: cannot import name 'colormaps' from 'matplotlib' (/home1/mukesh.singh/miniconda3/envs/igwn-py39/lib/python3.9/site-packages/matplotlib/__init__.py)

which essentially means that there is no colormaps object in matplotlib. Do you think it's some version issue?

What version of matplotlib do you have? I think before matplotlib 3.5.0, the way to do this was from matplotlib.cm import _colormaps as colormaps. Starting with 3.5.0, you can do from matplotlib import colormaps.

I am using matplotlib version: 3.4.3. Ok then it seems the import statements has to be changed for the older versions. Thanks!

Added a matplotlib version check and import colormaps accordingly #190


"Error: It seems the symlink source is not there" for Rocket.Chat.

I met this problem when installing Rocket.Chat., would you please fix it? Thank you!
➜  ~ brew cask install rocket-chat
==> Downloading https://github.com/RocketChat/Rocket.Chat.Electron/releases/down
Already downloaded: /Library/Caches/Homebrew/rocket-chat-1.3.1.dmg
==> Verifying checksum for Cask rocket-chat
Error: It seems the symlink source is not there: '/opt/homebrew-cask/Caskroom/rocket-chat/1.3.1/Rocket.Chat.app'

@nixlehrer fixed, thanks for reporting...just need a maintainer to pull the PR and you can go ahead and brew cask install rocket-chat without issue 😁

Thank you!


Broken gyro support for ROG Ally

Describe the bug
First of all, thank you all for the amazing work. When I first installed bazzite on my ROG Ally, everything works perfectly including back buttons and gyro. But the gyro has been broken since recent updates. I suspect this happens due to kernel 6.7 update.
What did you expect to happen?
Gyro works as intended.
Output of rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-ally:stable
                   Digest: sha256:7a6928058d13ad1e20cd7df1671098b435d6ad853dfed4b12eadb355e4df61e0
                  Version: 39.20240212.0 (2024-02-13T01:41:49Z)
          LayeredPackages: deluge v2raya
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf"'

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-ally:stable
                   Digest: sha256:719a78c37f255eb7f6a84362f7c25d74f61a71c5a06abe3cc79f8eeda2d7c235
                  Version: 39.20240210.0 (2024-02-11T07:14:43Z)
          LayeredPackages: deluge v2raya
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf"'

Hardware
Asus ROG Ally with latest version of bios and without any modding except 2TB SN740 SSD replacement.
Extra information or context
No response

We'll check into it, for the time being you can rebase to the previous kernel by date, or by pinning the previous deployment if you just updated.

Just updated bazzite a few minutes ago, and the gyro works again.


GROOVY-8305: build "file:" URL for "user.home" and set as Ivy variable

closes #597

+1

+1

Merged. Thanks.


Add TLS configuration support to spring-autoconfigure

Changes:

Fork Spring's Ssl to support both spring-boot1, spring-boot2.
Move TLS configuration setup to boot-autoconfigure to allow to setup TLS at non-reactive servers

Results:

Cloeses #1659

TODO:

[ ] Update unit tests

@imasahiro You need to update https://github.com/line/armeria/blob/master/spring/boot-webflux-autoconfigure/build.gradle#L28-L37 too. :-)

in zipkin, we're going to need to cut a release soon to fix a version alignment issue. This particular change was requested by one of our users. Not sure if it can be cut soon, but if not in the next day or two, we'll have to wait until our next version to work it in. Thanks for the help here!

@imasahiro Could you fix the Checkstyle violations? I think we're good to go except them.
@hyangtack @minwoox PTAL
@adriancole Will try to release a new version of Armeria today.

Hm, test was failed due to WRONG_VERSION_NUMBER ssl error. Does anyone know how to solve this?
10:30:02.100 [Test worker] INFO  c.l.a.s.ArmeriaAutoConfiguration - Armeria server started at ports: {/0:0:0:0:0:0:0:0:55437=ServerPort(/0:0:0:0:0:0:0:0:55437, [http]), /0:0:0:0:0:0:0:0:55438=ServerPort(/0:0:0:0:0:0:0:0:55438, [https])}
10:30:02.454 [Test worker] INFO  c.l.a.s.ArmeriaSslConfigurationTest - Started ArmeriaSslConfigurationTest in 3.564 seconds (JVM running for 4.816)
10:30:02.942 [armeria-common-worker-nio-2-1] WARN  c.l.a.c.HttpClientPipelineConfigurator - [id: 0x65a5cca6, L:/<IP_ADDRESS>:55440 - R:<IP_ADDRESS>/<IP_ADDRESS>:55437] TLS handshake failed:
javax.net.ssl.SSLHandshakeException: error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER
	at io.netty.handler.ssl.ReferenceCountedOpenSslEngine.sslReadErrorResult(ReferenceCountedOpenSslEngine.java:1204)
	at io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1165)
	at io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1236)
	at io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1279)
	at io.netty.handler.ssl.SslHandler$SslEngineType$1.unwrap(SslHandler.java:217)

@imasahiro This is a fix for this. https://gist.github.com/hyangtack/bf38e15c754044b30e4710e12279da0a

https port should be specified first so that we can get it by server.activePort().get().localAddress().getPort()
We need to configure InsecureTrustManagerFactory.INSTANCE as a trust manager on the client side because we don't have a domain name.

But still we need to investigate why ReactiveWebServerAutoConfigurationTest is also failed. Seems that @LocalServerPort is injected with a different port number.

Thanks, @imasahiro and reviewers!


[FEATURE REQUEST] Word count / line count filters - LMAY75

The ability to white/blacklist based off of characters/line count on the response page would be greatly appreciated. Sometimes you won't find what you want from a response code, but will from a char or line count. Both features are in wfuzz for comparison.
Originally reported by @LMAY75

Add new command line option checklist

config.rs

add value to Configuration struct
add value to Configuration::default
update Configuration docstring
add value to Configuration::new
add value to Configuration::merge_config
update Configuration::tests::setup_config_test with new value
add test to check config parsing

ferox-config.toml.example

add new value

banner.rs

add new value
add new emoji
add new test or update existing so that it's displayed

Cargo.toml

bump version - minor release +1 - patch release = 0

README.md

update default config section (if needed)
update example config file section
update help output section
consider adding to an example (new or existing)

parser.rs

add the option

wherever.rs

implement the new feature

The actual implementation will look something like

add word count / line count filter to filters.rs where each one implements the FeroxFilter trait
within scanner::scan_url, use add_filter_to_list_of_ferox_filters in order to register w/e filters the user specifies

consider breaking out all of the 'add filters' code from scan_url to another function; scan_url has a lot going on and continuing to add new filters to it probably isn't the best long term decision

There's also an implicit update to the format of reported urls here.
Current output looks like this (no word count or line count for the response is shown)
200       4133 https://somecompany.com

For word count and line count filters to be useful, that info would need ot be provided.

Closed by PR #122


newest n8n.io version

I've removed the version tag when installing n8n.
There is no option to update. For now you just would need to rebuild the Addon to get the latest version.
I've tried to add ingress to the addon since my server operates behind a proxy. Unfortunally I didn't got it to a working state. The n8n Server listens on <IP_ADDRESS> judging from the log. So Home Assistant tries to connect to that ip which is obviously not working. I've tried modifieing the n8n parameters to take an ip as well but with that I just got more errors.
I just need it for a very simple automation so this ist working enough for me. Maybe someone will trie to get it working.

Hi Lucas, thanks you for your PR, I'll check it out when I'll have a bunch of time

Just checked. So, there is two subjects here :

Removing the n8n version in the dockerfile to have always the latest version of n8n

I disagree with this, it's pretty for the same reason you should not use the :latest tags on your docker image. if you always use the latest version, you're not sure every installations would be the same, you wouldn't be sure there is no breaking change etc... So I'll try to regurlaly bump the n8n version in the Dockerfile with a bit of local tests.

Accessing n8n from a reverse proxy.

I just tried on my personnal instance. As per I exposed the application, it's recheable from http(s)://<hass_ip>:5678 so if your reverse proxy can access your hassio instance on port 8123, I guess it sould reach the 5678 port. Just be careful with the protocol, I had an issue when setting the protocol as http in the config, when using the UI button to get to the service, it always tried https.

I agree with you on the first issue. But like you said it requires manual Labour from you or any other participants. The current version in the docker file is pretty old and I needed a newer version since the integration I wanted to use didn't exist in the old one. Maybe the best way to tackle this is to use a config entry for the version you wanna use.
On the second topic: it's not that I couldn't get it to work with the according forwarding or proxy settings but more a convenience feature. I like the ingress feature since you have everything you need in one interface and don't need to configure your router on every new addon.
For now this isn't really relevant for me anyways since the integration I wanted to use is not functional for what I wanted to do with it. So until this changes I don't need n8n.

Version have been bumped to 0.134.0
For the proxy part, can you open an issue with details about how your system work to reproduce it locally and try to fix it ?
Sorry for the delay, I've been busy for a while.
I'll close the PR for now. Thanks you for your contribution to the addon


feature: A way to disable welcome message?

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
I know this is brand new (like 2 hours old), but is there a way to disable the Welcome to LazyVim message?
Describe the solution you'd like
A toggle in the config.
Describe alternatives you've considered
N/A
Additional context
No response

It should only be shown after a clean install. Are you seeing it more than that?

I see it on every run of neovim. I am using nix to configure my neovim install and I would guess that the state is not allowed to be written somewhere?
I put up a PR for the toggle: https://github.com/LazyVim/LazyVim/pull/1724

It's the file ~/.config/nvim/lazyvim.json. That contains installed extras and some state information on what news you have seen. This file should be part of your configuration.
Putting the news state in config instead of stdpath.state is on purpose, since it's not dependent on the machine where LazyVim is running on, but on the user's dotfiles.
When the file doesn't contain a state for news, it means a new user that never used LazyVim before.
I assume your nvim config dir is not writable?
Easiest way to fix showing that welcome message, is to make sure there's a lazyvim.json file containing:
{
  "news": {
    "NEWS.md":0
  }
}

Things like :LazyExtras obviously won't work in a setup where that file is not writeable

Thank you for circling back!  (love you work)

I assume your nvim config dir is not writable?

That is correct. Nix has the directory locked down.
There is probably a way to do it the nix way. I will report back when I figure it out.

"0" threw an error but the setting below worked:
"extras": [

],
"news": {
"NEWS.md": "2123"
},
"version": 2
}```

I'm having this same problem, but I'm on Arch. The file is readable and writable. NEWS.md is already "2123" (it was by default); changing it to 0 or "0" still triggers the welcome message on the next run AND the value gets changed back to "2123".

I am getting the same issue on Nix. The lazy.json is readonly. Manually (forcing) setting the new.md value has no effect and the pop up shows at every launch.

I see in lazyvim/config/init.lua the following option:
 news = {     -- When enabled, NEWS.md will be shown when changed.     -- This only contains big new features and breaking changes.     lazyvim = false,     -- Same but for Neovim's news.txt     neovim = false,   },
how to set the news.lazyvim to false in an existing config?
Manually overriding the value in .local/share/nvim/lazy/LazyVim/lua/config/init.lua works to get rid of the message but that is not a permanent solution.

You should set it in your ~/.config/nvim/lua/config/lazy.lua file.

@dpetka2001
I already tried with the following but it has no effect:
require("lazy").setup({
  spec = {
    -- add LazyVim and import its plugins
    { url="https://gitlab.com/Julien76/LazyVim.git", import = "lazyvim.plugins" },
    -- { "LazyVim/LazyVim", import = "lazyvim.plugins" },
    -- import any extras modules here
    { import = "lazyvim.plugins.extras.lang.typescript" },
    { import = "lazyvim.plugins.extras.lang.json" },
    -- { import = "lazyvim.plugins.extras.editor.flash" },
    { import = "lazyvim.plugins.extras.ui.mini-animate" },
    { import = "lazyvim.plugins.extras.dap.core" },
    { import = "lazyvim.plugins.extras.dap.nlua" },
    { import = "lazyvim.plugins.extras.test.core" },
    { import = "lazyvim.plugins.extras.util.project" },
    { import = "lazyvim.plugins.extras.coding.copilot" },
    -- { import = "lazyvim.plugins.extras.coding.yanky" },
    -- import/override with your plugins
    { import = "plugins" },
    { import = "plugins.lang" },
  },
  defaults = {
    -- By default, only LazyVim plugins will be lazy-loaded. Your custom plugins will load during startup.
    -- If you know what you're doing, you can set this to `true` to have all your custom plugins lazy-loaded by default.
    lazy = false,
    -- It's recommended to leave version=false for now, since a lot the plugin that support versioning,
    -- have outdated releases, which may break your Neovim install.
    version = false, -- always use the latest git commit
    -- version = "*", -- try installing the latest stable version for plugins that support semver
  },
  news = {
    -- When enabled, NEWS.md will be shown when changed.
    -- This only contains big new features and breaking changes.
    lazyvim = false,
    -- Same but for Neovim's news.txt
    neovim = false,
  },
  install = { colorscheme = { "tokyonight", "habamax" } },
  checker = { enabled = true }, -- automatically check for plugin updates
  performance = {
    rtp = {
      -- disable some rtp plugins
      disabled_plugins = {
        "gzip",
        -- "matchit",
        -- "matchparen",
        -- "netrwPlugin",
        "tarPlugin",
        "tohtml",
        "tutor",
        "zipPlugin",
      },
    },
  },
})

``

I'm sorry. I was wrong. You should set it in the LazyVim spec. So, create a file in ~/.config/nvim/lua/plugins/core.lua with contents
return {
	{
	  "LazyVim/LazyVim",
	  opts = {
	    news = { lazyvim = false },
	  },
	},
}

@dpetka2001 , works great thank you so much :smiley:


Move servicebus to sdk

Moves code from servicebus/data-plane/ to sdk/servicebus.

@JonathanGiles for input on the Java side.
@weshaggard for input on the approach I'm taking with the streamlined pipelines.

More generally, I am not clear how track two service bus will be expected to co-exist in this directory structure: https://github.com/mitchdenny/azure-sdk-for-java/tree/move-servicebus-to-sdk/sdk/servicebus @weshaggard Can you speak to the plan here?

Hrm - good point. Seems that there are a few options here (don't think this is exhaustive):

Co-exist with different library names.
Do servicing for the track 1 version on a branch.
Converge the code into a single library (and when appropriate deprecate the old classes/interfaces).

This kind of problem will likely come up again and again so it would be good to have a general strategy we apply.

The guidelines I've currently outlined in https://github.com/Azure/azure-sdk/blob/master/docs/engineering-system/repo-structure.md.

<package name> - Should be the name of the shipping package, or an abbreviation that distinguishes the given shipping artifact for the given service. The key is that there is source for only one shipping package in this folder.

If there are multiple packages with the same name but different scope/org/groupid/SxS-version/etc then put them each in their own folder under the service name directory with names that match whatever distinguishes them from each other.
If there are long file path issues then you can use an abbreviation of the package name to help avoid issues. For example Java tools require every part of the package/namespace to be a separate folder which can make the paths extra long and thus may need to abbreviate the package name to help alleviate the impact of long file paths on windows.
If there are other assets that aren't shipping packages, such as shared libaries/source code or tools, they can also go in a folder under the service name directory.

So based on those it boils down to whether or not there they will share the same artifactid and/or ship SxS. @JonathanGiles correct me if I'm wrong but I believe for the Java track 2 libraries they are going to be new libraries SxS with only the groupId changed from com.microsoft.azure to com.azure? If that is the case then I'll suggest the following convention:

track 1: package folders should be named microsoft-<artifactid>
track 2: package folders should be named <artifactid>

Does that sound reasonable to you @JonathanGiles?

Thanks for that @weshaggard! That sounds like a reasonable plan to me and it'll allow us to continue servicing off the master branch for the older package versions.

I know I've raised this concern before. I'll outline it again now because there is a little more concrete detail thanks to this PR. For reference, here is the directory structure of the move: https://github.com/mitchdenny/azure-sdk-for-java/tree/move-servicebus-to-sdk/sdk/servicebus
The concern I have is that there are two pom.xml files for this track 1 move, within the /sdk/servicebus directory. There is a /sdk/servicebus/pom.xml and a /sdk/servicebus/azure-servicebus/pom.xml. The latter /sdk/servicebus/azure-servicebus/pom.xml refers to the /sdj/servicebus/pom.xml as its parent pom.
Introducing track two will mean we add additional directories under /sdk/servicebus, presumably in, e.g. servicebus. So that means we will have /sdk/servicebus/servicebus for track two, and /sdk/servicebus/azure-servicebus. To me, this is not a clear enough difference.
Additionally, this approach requires reworking of the pom files for each move, assuming we keep the 'root' /sdk/servicebus/* files - these are all explicitly track one files.
If it were me, I would like to have /sdk/servicebus/data-plane (where all files from this move would go into), and /sdk/servicebus/client (where track two will go). This makes moving vastly simpler, and in my opinion makes identifying modules and which are relevant to a users interest far simpler.

I think that would make the migration easier for the track 1 libraries. I'd also like to think over the horizon a little bit here and I wonder how we would approach revving these libraries if we decide that the external library types that we are exposing on our public interfaces aren't all the rage anymore and we want to really shake up our API - do we end up creating another folder under sdk/[service].
Or - will we be evolving the API in place whilst managing deprecation etc?

If it were me, I would like to have /sdk/servicebus/data-plane (where all files from this move would go into), and /sdk/servicebus/client (where track two will go). This makes moving vastly simpler, and in my opinion makes identifying modules and which are relevant to a users interest far simpler.

Thanks for the feedback @JonathanGiles I know you are still a little uneasy about having these mixed but I think I'd still like to continue with this path for now. The hope is that each service directory will have a ReadMe.md that has information about each of the directories/packages and will help guide folks to better understanding what they are and which ones they should pay attention to, I already chatted with @kaerm about this adding that information to the readmes.
If in the end we figure out this causes too many issued then we will consider other options, one that I'm thinking about is having another root level service folder like "servicebus-old"  (not sold on the name yet) to hold the track 1 packages and then use "servicebus" for the track 2 and management libraries which are still actively developed.

OK - thanks all, I'd like to move forward for now with this then - @JonathanGiles do you know who I need to ping specifically around the servicebus folder move here? Or can you give this one a tick of approval?

@mssfang ported this code to the repo. @mssfang are you the owner of the servicebus java library? If so can you please take a look at this change and ensure it looks reasonable.

There is a new service bus pull request you might want to reconcile with.
In terms of my concerns, my primary worry here is the extra work we will have to do when a track two library is added. It will break track one developers on that library, it will confuse people about directory structure, there will need to be additional refactoring for every client move, etc. Anyway, I have no additional feedback beyond these concerns, so feel free to merge as desired.

This PR includes java complied ***.class files. Please make sure to exclude them before merging to master.
Additionally, FYI, the new PR from the service team merged into the master recently but no more incoming PR for the next few days.   Seems there are no Java and Maven code changes, it looks fine to me.

Thanks folks - I'll fix the PR up.

@mitchdenny for the libraries you are moving that we know are track 1, can you also add the microsoft- prefix to help avoid another move for them when their track 2 library comes in?

Dunno what happened there - didn't mean to close the PR. I've updated the PR against the changes in master. I've renamed servicebus to microsoft-servicebus to make room for the future track 2 version of the library.

Merging this now.

This is still bizarre to me. We now have microsoft-servicebus for track one, and the artifactId of that product is 'azure-servicebus' (which will also likely be what we name our track two library).

This was supposed to be microsoft-azure-servicebus (fixed in https://github.com/Azure/azure-sdk-for-java/pull/3911) and I expect our track 2 will be azure-servicebus. Regardless we are going to have to explain to customers which one is which and we will do it in the readme in the service folder and most likely some other public facing documentation when we ship.


No license for redgreen gem

The redgreen gem is very old and do not include license information.

Hmmm....

@gudata If your licence warning is coming through certificate_authority
gem, I created a PR https://github.com/cchandler/certificate_authority/pull/56 which remove jewler dependency. I hope it'll be merged soon.


Game crash / very long hang

Decided to post it here, in case it gets buried in the discord. There's a seemingly random crash happening whenever I select Gae Bolg Nexus as the VFX being replaced. This hang / crash doesn't happen unless I have a workspace open. Initially I assumed this was caused by a corrupted workspace, but I completely remade it and it still causes the issue. I've attached to workspace in question, and to reproduce, simply create a new item in the workspace, then select Gae Bolg Nexus as VFX being replaced.
Nexus Workspace.zip

hmm...I haven't been able to reproduce it. Is there anything weird in your /xllog (or the dalamud.log file located in %appdata%\XIVLauncher\)? Also, is the Gae Bolg Nexus the glamour you currently have equipped, or modified by any mods?

There isn't any log regarding this since the game just hangs, also no the Gae Bolg Nexus isn't equipped / glamoured or otherwise affected by mods.

do you have any other plugins that affect VFXs enabled? And was this tested in a crowed area?

It was tested in a seemingly empty residential district, and I do use penumbra which in turn affects other VFX, but this happens even without it enabled.

Huh, I guess I was wrong and technically there are 2 log lines regarding this, but nothing useful.
2023-05-30 03:39:55.543 +03:00 [WRN] [HITCH] Long UiBuilder(VFXEditor) detected, 190.9975ms > 100ms - check in the plugin stats window.
2023-05-30 03:40:07.912 +03:00 [INF] [VFXEditor] Loading Vfx-Item

does it still happen with v<IP_ADDRESS>?

It still happens, yeah

It seems to be something about these items being together in the workspace.

Interestingly enough, I was able to trigger it if I had 2 random weapons, then added Curtana Nexus,Gae Bolg Nexus,and Bravura Nexus, then deleted the random weapons, the hang happening as soon as the delete went through.

some more things to try, since this is kind of stumping me:

Can you check the folder that the workspace is located in? Is there anything weird there?
Can you try setting the Dalamud style to "Dalamud Standard"?
Can you send me your VFXEditor settings (located in %appdata%\XIVLauncher\pluginConfigs)?

The folder only contains other workspace files, and only a few ones.
Still crashed on Dalamud Standard
Attached VFXEditor.zip
Also I noticed I have some temp avfx files stored, a few of them are dated recently, but 2 of them are older.

Hiding tabs with the latest update seems to fix it, so there's something funky going on with tabs I guess.


make  error! (missing the VERSION field)

bash: % 86400: syntax error: operand expected (error token is "% 86400")
/home/snakwu/openwrt-master/openwrt/feeds/luci/luci.mk:277: *** Package/luci-i18n-acces
scontrol-zh-cn is missing the VERSION field.  Stop.

Anything special with you build environment?
Normal OpenWrt repo with LuCI as a feed?
Did you compile full firmware, or just a module?
(The LuCI version string logic was modfied a few days ago, but it should work ok in normal conditions.)
@jow-
see also
https://forum.openwrt.org/t/luci-mk-package-luci-base-is-missing-the-version-field-stop/60547
Just wondering, which conditions trigger the error.

I guess it happens for LuCI packages not being in Git.

Anything special with you build environment?
Normal OpenWrt repo with LuCI as a feed?
Did you compile full firmware, or just a module?
(The LuCI version string logic was modfied a few days ago, but it should work ok in normal conditions.)
@jow-
see also
https://forum.openwrt.org/t/luci-mk-package-luci-base-is-missing-the-version-field-stop/60547
Just wondering, which conditions trigger the error.

I added some plug-ins to compile, it is normal before the fields have been modified, now it is wrong!

I guess it happens for LuCI packages not being in Git.

I think this is also possible

I guess it happens for LuCI packages not being in Git.

The problem has not been solved!
make[3]: Entering directory '/home/snakwu/openwrt-master/openwrt/package/lean/luci-app-accesscontrol'
bash: % 86400: syntax error: operand expected (error token is "% 86400")
/home/snakwu/openwrt-master/openwrt/feeds/luci/luci.mk:288: *** Package/luci-i18n-accesscontrol-zh-cn is missing the VERSION field. Stop.
make[3]: Leaving directory '/home/snakwu/openwrt-master/openwrt/package/lean/luci-app-accesscontrol'
time: package/lean/luci-app-accesscontrol/compile#0.83#0.14#1.74
package/Makefile:111: recipe for target 'package/lean/luci-app-accesscontrol/compile' failed
make[2]: *** [package/lean/luci-app-accesscontrol/compile] Error 2
make[2]: Leaving directory '/home/snakwu/openwrt-master/openwrt'
package/Makefile:107: recipe for target '/home/snakwu/openwrt-master/openwrt/staging_dir/target-x86_64_musl/stamp/.package_compile' failed
make[1]: *** [/home/snakwu/openwrt-master/openwrt/staging_dir/target-x86_64_musl/stamp/.package_compile] Error 2
make[1]: Leaving directory '/home/snakwu/openwrt-master/openwrt'
/home/snakwu/openwrt-master/openwrt/include/toplevel.mk:218: recipe for target 'world' failed
make: *** [world] Error 2

Provide the output of the following commands:
cd /home/snakwu/openwrt-master/openwrt/package/lean/luci-app-accesscontrol
git log -1
git log -1 --format="%ct %h" --abbrev=7 -- ':(exclude)po'

Provide the output of the following commands:
cd /home/snakwu/openwrt-master/openwrt/package/lean/luci-app-accesscontrol
git log -1
git log -1 --format="%ct %h" --abbrev=7 -- ':(exclude)po'

commit 7c2e0fa5865406d0f2d1987bdd2180c1d1913bf2 (HEAD -> master, origin/master, origin/HEAD)
Author: Daniel Golle<EMAIL_ADDRESS>Date:   Tue Apr 14 16:11:05 2020 +0100
procd: jail fixes and improvements

 32c717e jail: only mess with rootfs if CLONE_NEWNS was set
 b275a62 instance: harmonize instance API
 511fd97 jail: make /proc more secure
 4953b7c jail: mount /sys read-only
 a4d6442 jail: replace /etc/resolv.conf with symlink in extroot+overlay
 a4cc165 jail: always mount /dev as additional tmpfs

Signed-off-by: Daniel Golle<EMAIL_ADDRESS>
snakwu@hassio-server:~/openwrt-master/openwrt/package/lean/luci-app-accesscontrol$ git log -1 --format="%ct %h" --abbrev=7 -- ':(exclude)po'
1586877366 7c2e0fa
snakwu@hassio-server:~/openwrt-master/openwrt/package/lean/luci-app-accesscontrol$

Provide the output of the following commands:
cd /home/snakwu/openwrt-master/openwrt/package/lean/luci-app-accesscontrol
git log -1
git log -1 --format="%ct %h" --abbrev=7 -- ':(exclude)po'

Compilation passed, but the settings interface of some plugins was lost!

@a-kibou  请不要把其他分支的问题相互引用，以免混乱！

@a-kibou 请不要把其他分支的问题相互引用，以免混乱！

抱歉，那我應該如何刪除？


rawgpsd died during test run

Describe the bug
RawGPS died and it forced me to take control, I don't know how to reproduce it reliably, sorry!
Provide a route where the issue occurs
e1107f9d04dfb1e2|2023-10-09--21-02-26--0
openpilot version
0.9.5
Additional info
No response

Similar thing happened on sunnypilot too, I have a stacktrace, this was the issue I created https://github.com/commaai/openpilot/issues/30226
Stacktrace:
Traceback (most recent call last):
  File "/data/openpilot/openpilot/selfdrive/manager/process.py", line 40, in launcher
    mod.main()
  File "/data/openpilot/system/sensord/rawgps/rawgpsd.py", line 288, in main
    r = setup_quectel(diag)
        ^^^^^^^^^^^^^^^^^^^
  File "/data/openpilot/system/sensord/rawgps/rawgpsd.py", line 223, in setup_quectel
    send_recv(diag, DIAG_SUBSYS_CMD_F, pack('<BHBBIIII',
  File "/data/openpilot/openpilot/system/sensord/rawgps/modemdiag.py", line 65, in send_recv
    opcode, payload = diag.recv()
                      ^^^^^^^^^^^
  File "/data/openpilot/openpilot/system/sensord/rawgps/modemdiag.py", line 48, in recv
    unframed_message = self.hdlc_decapsulate(raw_payload)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/openpilot/openpilot/system/sensord/rawgps/modemdiag.py", line 35, in hdlc_decapsulate
    assert payload[-2:] == pack('<H', ModemDiag.ccitt_crc16(payload[:-2]))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError

Been getting this too on OPGM.

I'm seeing 3 recent instances of this, all from your device. Still looking into this, but I suspect we'll have to add some more logging to get to the bottom of this.

Could it be then a hardware issue ? 😭 this is where I hate being in Europe 😂 it happens quite often for me

This is likely software.

That's reassuring! I'd hate going through the customs process... Anything I can do to help?

I was getting this same error when I was working on a custom feature. I had a made a new daemon that updated once a minute. When I added 'liveLocationKalman' to the SubMaster, I would randomly get this error on startup. I re-implemented the feature using the 'LastGPSPosition' param and the error went away.

@dimdom69 on the SunnyPilot failure I was doing something similar, and I was also subscribing to liveLocationKalman IIRC. However, on the stock route I didn't make any modification, maybe I was already on some sort of failure state that remained through the reinstall of stock perhaps?
Also, thanks for hsaring about the LastGPSPosition I wasn't aware of it!

I was getting this same error when I was working on a custom feature. I had a made a new daemon that updated once a minute. When I added 'liveLocationKalman' to the SubMaster, I would randomly get this error on startup. I re-implemented the feature using the 'LastGPSPosition' param and the error went away.

I don't see how this could cause any issues with rawgpsd. If you have a branch that reproduces this reliably, that would be very helpful.

I was getting this same error when I was working on a custom feature. I had a made a new daemon that updated once a minute. When I added 'liveLocationKalman' to the SubMaster, I would randomly get this error on startup. I re-implemented the feature using the 'LastGPSPosition' param and the error went away.

I don't see how this could cause any issues with rawgpsd. If you have a branch that reproduces this reliably, that would be very helpful.

Reverted to using liveLocationKalman and now I don't get any errors. I guess I somehow got into an error state that resolved itself with a fresh install? Not sure.

I was getting this same error when I was working on a custom feature. I had a made a new daemon that updated once a minute. When I added 'liveLocationKalman' to the SubMaster, I would randomly get this error on startup. I re-implemented the feature using the 'LastGPSPosition' param and the error went away.

I don't see how this could cause any issues with rawgpsd. If you have a branch that reproduces this reliably, that would be very helpful.

Reverted to using liveLocationKalman and now I don't get any errors. I guess I somehow got into an error state that resolved itself with a fresh install? Not sure.

I don’t suggest using liveLocationKalman for any realtime gps stuff, it’s better to use gpsLocation and gpsLocationExternal (C3) otherwise the location won’t be updated properly :(


was AddRecursively removed from the source??? how ignore files and folders without permission???

Hello, hope you're great...I'm trying to follow the sample but I've two problems here

seems than AddRecursively was removed and Add doesnt watch recursively by default, how can I watch files recursively right now?
if I add the root folder I get some errors based on permission, would be possible skip those files than generates me errors???

thank you so much

ok my fault...I was using an old version of the package, after update I get the AddRecursively :dagger:
but I keep my second question: How could I ignore those files that are not possible watch and don't break my code??? thank you!!!

Hi @cocodrino,
It may have appeared to be missing because it's actually AddRecursive and not AddRecursively.
There is also the method Ignore if you'd like to check that out.


Add comments to publish/upgrade methods in (Programmable)TransactionBuilder

Description
As a downstream consumer of sui-sdk, I found it a little difficult to understand how to use TransactionBuilder::{publish, upgrade} without jumping some IDE hoops.
Hopefully, the documentation added in this PR will help others who are also unfamiliar with the codebase.
Test Plan
No tests required.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Thanks for bringing this to our attention and for putting up this PR! Please let us know if anything else could use better documentation.
I'll approve & merge this PR once the doc tests are fixed.

@oxade quick question: when you say

using the proper type path
do you mean for this PR to use relative paths?

I've taken a look at

https://github.com/rust-lang/rust/issues/74481, and
https://github.com/rust-lang/api-guidelines/discussions/186

and it would seem this is the only way to have links in documentation that does not require introducing dependencies.

@oxade quick question: when you say

using the proper type path

do you mean for this PR to use relative paths?
I've taken a look at

Figure out a way to link to downstream crates rust-lang/rust#74481, and
Add guidance about linking to external crates rust-lang/api-guidelines#186

and it would seem this is the only way to have links in documentation that does not require introducing dependencies.

For simplicity, you could just use rust,ignore in the comments.

@oxade should be fixed, now.
By the way:

Please let us know if anything else could use better documentation.
I will - as I continue to use the SDK, I'll be submitting more PRs if I find anything I can help clarify for other users.


Code for chapter 11

Hello, will there be code examples for Chapter 11 about scaling_

Bump

Hello….  code on scaling please :)


Use "(n)vim -d" to show diff of PKGBUILDS and install scripts if available

At the moment you are using git show to compare PKGBUILD and install script diffs, if I looked correctly in the pacaur script. Git is using a pager for git show, so it is not possible change anything in the diff.
My suggestion is to compare the old local PKGBUILD and install script to the new ones using (n)vim -d, if available on the system. This way also allows to copy changes you make regularly to specific PKGBUILDS or install scripts.

There is no old PKGBUILD stored on the system, only the git repo.


HMAC-SHA256/512 non 32 byte keys supporting

Hi,
Here is my PR with non 32 keys supporting. This would be really useful.
Thanks!

#165

Hi @tarcieri, what do you think about my PR?

I think if you're doing this much, you might as well expose the full IUF API

@tarcieri You mean, change hmac512256 libsodium calls to Init/Update/Final API? And what about OpenSSL::HMAC?

@nsheremet you've done most of the work here to expose the IUF API (i.e. initialize, update, finalize or as the OpenSSL::HMAC, or perhaps more generally the Ruby Digest API calls them #initialize, #update, and #digest), but it's not a particularly friendly or idiomatic API. I think if you're adding access to this API it probably should be, and would ideally implement something more akin to a Ruby Digest or OpenSSL::HMAC

@tarcieri hm. I will add IUF Api soon.

@tarcieri I also can make that after you call #update method, it will return hexdigest. The same functionality as in openssl #update method.

@nsheremet sorry I misunderstood how this works. I think the change you suggest (to match the OpenSSL::HMAC behavior) sounds good

@tarcieri I updated #update method. Done.

@tarcieri so, will you merge this PR?

One typo and one nit, otherwise it looks good, thanks for your contribution!

@tarcieri I fixed typos.

@tarcieri I think that's all 😄

Thanks!

@tarcieri I am glad to help!


Add dates to the 3d display

It seems like we need the dates somewhere in the visualization.

To add this in as a 3D element might take some time... Let's chat on Slack on how we can achieve this in a time frame suitable for you.

Closing this, because we added them at the top of the page in the chrome


Notification number shown even if there's no notification

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Duplicate of #493

Rackover reports that this is still happening.

Might be fixed, closing until further reports


splitting up tests of cassandra and sqlalchemy

After playing about with Robert Smallshire's kanban example, I was very interested in trying out your more generic event sourcing project.
However I know nothing of the Cassandra db. I ran the test suite be noticed tests were failing due to my missing Cassandra dependency. I tried to split out the cassandra tests and sqlachemy tests into different modules. So that my lack of Cassandra was not hampering my ability to test SqlAlchemy.
https://github.com/leonh/eventsourcing/commit/919fad7fca93a1052e25fb39c61046dd971d0b05

Hey! Thanks a lot for forking.
Good move splitting out the tests :+1:. If Cassandra is running locally with default settings, the tests should pass. But do you think it would be better if the test was skipped when Cassandra isn't running locally?
Will definitely merge your changes. Maybe you wanted to do a pull request into my develop branch when you're ready? I had a look just now through the changes you made - it all looks good to me ;-).

Hiya here's a pull request. I don't have any strong opinion about letting tests fail or be skipped. If you were to skip them then you could test if the cassandra package was importable or not. Or more explicitly add a setting/config file where the persistence backend is selected.
https://github.com/johnbywater/eventsourcing/pull/2
On a side note - one of the things I liked about the sixty-north Kanban example was the file based event store. Obviously that type of store would present problems in production but for learning and generally understanding the technique of event sourcing it was really good to see the basic event appended in a file. (I'm deffo in the learning and kicking-the-tyres stage at this point)

Thanks for the suggestions. The simplest alternative seems to be skipping the test when the Cassandra package is not importable. I'll try to do that. Good point about the simple file format, the sixty-north Kanban example is neat. SQLite uses a single file, but it would be cool to have a very simple file format.

Also thanks for the PR! I merged it in the other day ;-).

Hey Leon, just wanted to let you know I set up a new mailing list for this project. If would be great if you were to join so that we could discuss things a bit better? Here's the link:
https://groups.google.com/forum/#!forum/eventsourcing-users


issue forking and developing when github username has mixcase

When trying to develop locally I run into issues because my github username (MxNxPx) contains mixcase and the repo that is used in github requires lowercase. Resulting in all delivery tests failing.
Along the way I ran into some other issues including references to a tag version ":0.2.7" that I don't have in my repo and I figure setting it to ":latest" fixes my issue (and probably other folks as well).

Fixed by #169, thanks @MxNxPx!


Typescript typings missing after 1.4.0

Environment

React Native Environment Info:
System:
OS: macOS 10.14.4
CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Memory: 700.40 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.4.1 - /usr/local/bin/node
Yarn: 1.15.2 - /usr/local/bin/yarn
npm: 6.5.0 - /usr/local/bin/npm
Watchman: 4.7.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 23, 25, 26, 27, 28
Build Tools: 25.0.2, 27.0.3, 28.0.3, 29.0.0
System Images: android-27 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.54<IP_ADDRESS>52501
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.8 => 0.59.8
npmGlobalPackages:
react-native-cli: 1.0.0
Platforms

Issue in typings, so not platform related.
Versions

Android: -
iOS: -
react-native-geolocation: 1.4.0
react-native: 0.59.8
react: 16.8.3

Description

The typings directory is missing from node_modules/@react-native-community/geolocation after updating to 1.4.0. Works as expected when downgrading back to 1.3.0

Same issue


[BUG] Trying to consume the RoleAssignment create API puts the thread in blocking state forever

Describe the bug

We are using the Azure SDK for Java (v1.33.1; we tried upgrading it to v1.36.3 too) to create RoleAssingments on resource groups in Azure. Since, recently the call shown  under "Code Snippet" seems to never return in a specific system and is in an ever blocking state. We have not been able to get passed this even with the latest Azure version v1.36.3. Please find the thread dump below

Exception or Stack Trace
"schedulerFactory_Worker-6" #64 prio=5 os_prio=0 cpu=1749.39ms elapsed=822.08s tid=0x00007fa99caa9000 nid=0x1fa4 waiting on condition  [0x00007fa9397e5000]
   java.lang.Thread.State: WAITING (parking)
	at<EMAIL_ADDRESS>Method)
	- parking to wait for  <0x00000000d5f00000> (a java.util.concurrent.CountDownLatch$Sync)
	at java.util.concurrent.locks.LockSupport.park(java.base@11.0.8/LockSupport.java:194)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.8/AbstractQueuedSynchronizer.java:885)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(java.base@11.0.8/AbstractQueuedSynchronizer.java:1039)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(java.base@11.0.8/AbstractQueuedSynchronizer.java:1345)
	at java.util.concurrent.CountDownLatch.await(java.base@11.0.8/CountDownLatch.java:232)
	at rx.internal.util.BlockingUtils.awaitForComplete(BlockingUtils.java:47)
	at rx.observables.BlockingObservable.blockForSingle(BlockingObservable.java:460)
	at rx.observables.BlockingObservable.single(BlockingObservable.java:340)
	at com.microsoft.azure.management.resources.fluentcore.model.implementation.CreatableUpdatableImpl.create(CreatableUpdatableImpl.java:251)
	at com.microsoft.azure.management.resources.fluentcore.model.implementation.CreatableUpdatableImpl.create(CreatableUpdatableImpl.java:33)
	at com.cloudops.mc.plugin.azure.components.AzureManagementController.addUserToEnvironment(AzureManagementController.java:212)
	at com.cloudops.mc.manager.services.async.EnvironmentStages.addUserToServiceEnvironment(EnvironmentStages.java:372)
	at com.cloudops.mc.manager.services.async.EnvironmentStages.lambda$addUserToServiceEnvironment$1(EnvironmentStages.java:114)
	at com.cloudops.mc.manager.services.async.EnvironmentStages$$Lambda$2068/0x0000000841825c40.apply(Unknown Source)
	at com.cloudops.mc.manager.services.chain.StageChecker.execute(StageChecker.java:95)
	at com.cloudops.mc.manager.services.chain.StageCheckerFactory.execute(StageCheckerFactory.java:40)
	at com.cloudops.mc.manager.services.chain.ChainChecker.checkCompletion(ChainChecker.java:74)
	at com.cloudops.mc.service.OperationCompletionPollingJob.execute(OperationCompletionPollingJob.java:89)
	at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
	- locked <0x00000000cc228028> (a org.quartz.simpl.SimpleThreadPool$WorkerThread)
   Locked ownable synchronizers:
	- None

To Reproduce

It seems to be an issue in heavily loaded systems

Code Snippet
      RoleAssignment roleAssignment = az.accessManagement().roleAssignments().define(roleAssignmentName)
              .forServicePrincipal(servicePrincipal)
              .withBuiltInRole(BuiltInRole.CONTRIBUTOR)
              .withResourceGroupScope(rg)
              .create();

Expected behavior

Should successfully create a RoleAssignment

Setup:

OS: CentOS Linux
IDE : None
v1.33.1 and v1.36.3

Additional context

Could it be somethingn to do with the Azure API throttling the requests for specific IPs or systems?

Information Checklist

[ X] Bug Description Added
[ X] Repro Steps Added
[ X] Setup information Added

@yungezz could you please help route this issue?

hi @xccc-msft could you pls help on this? thanks

Thank you @joshfree @yungezz @xccc-msft
It seems like the issue was related to conflicting versions of JavaNetCookieJar from deifferent dependencies we have. The logs probably were subsumed due to logback settings  that hide most microsoft package logs


[FEATURE REQUEST] Invoke code formatting from CLI

I have a project with 3K+ Lua files I need to format. The problem is if I use something like this it takes forever. I disabled diagnostics like this:
    "Lua.diagnostics.enable": false,
    "Lua.diagnostics.workspaceDelay": 10000,
    "Lua.diagnostics.workspaceRate": 1,
    "Lua.diagnostics.disableScheme": ["git", "."]

Yet for some reason lua-language-server triggers diagnostics all the time and it slows down the process.

So, it would be great to trigger code formatting from CLI without doing any diagnostics.
I tried this tool but it has different styling by default so it was not really helpful, but it's blazing fast.

3K+ files don't need such a high occupation. There should be a bug. Can you provide a log?

Where's it located?

Please set Lua.semantic.enable to false , check whether the occupancy returns to normal?

Is this project open source?
If I can debug directly, I can solve the problem faster.

code format has standlone cli tool

this repo's formatting algorithm is come from EmmyluaCodeStyle. you can get cli tool from release

Oh, wait, this is different format tool, sweet will try it too, thanks!

this repo's formatting algorithm is come from EmmyluaCodeStyle. you can get cli tool from release

Works like a charm, thank you!

Is this project open source? If I can debug directly, I can solve the problem faster.

https://github.com/Real-Gecko/hw2-complex
This is the code, beware that's huge:

It contains a lot of legacy stuff that needs to be removed.
.vscode/settings.json for the project contains everything needed for project to work except one thing: library files.
globals.zip
Unpack this globals.zip anywhere on your drive and adjust Lua.workspace.library accordingly.

Thanks for your project, I have found a performance issue!

You can install this version to check if the performance issue resolved: https://github.com/sumneko/lua-language-server/actions/runs/2569280528

Yes, f9b3b65 is much better. Not only file formatting happens faster even with "Lua.semantic.enable": true, it also was able to detect some issues with the current code which 3.3.1 was unable to detect for some reason. https://github.com/CppCXY/EmmyLuaCodeStyle also works like a charm from CLI. If you make code formatting from CLI available with lua-language-server binary it's up to you.


tpm2 quote validation

ta10: send marshaled TPM structures for quote and signature
ga10: remove name and use marshaled TPM structure for Public instead
ga10: add TPM signature verification and don't rely on JSON from agent

Done


add steamdriddb.rommanager

Signed-off-by: Masamune3210<EMAIL_ADDRESS>WinGet Automation Pull Request Checklist

[ ] Have you verified that a previous version of the package is already there in the Windows Package Manager Community Repository?
[ ] Have you tested the package using the Test-Package script, provided in the tools folder?
[ ] The commit message(s) follows the conventional commits guidelines.

Extra Changes & Notes

@Masamune3210 adding package identifier in the list won't automatically update the package. You'll have to create a JSON for the package using New-Package script provided in tools folder.

Think I did it right, if not let me know and Ill try to fix it

Test-Package wouldnt work, kept dying on line 174 and whining about a Missing file specification after redirection operator

@allcontributors please add @Masamune3210 for code


Updated: Apt Clean up to make img smaller

@frank-dspeed the base ubuntu:14.04 image does this by default, see /etc/apt/apt.conf.d/docker-clean.

This can't be realy true have tested it got diffrent results with the original base img i know tianons change but you can test it your self you get diffrent img size

@frank-dspeed I see no difference what so ever. the apt-get clean command is supposed to affect the /var directory, particularly the /var/cache directory. Since you insist, here is my test.
<- docker exec -it redmine bash
<- du -s /var
-> 21156	/var
<- apt-get clean
<- du -s /var
-> 21156	/var

As you can see, there are no changes in the size of the /var directory. I cannot comment on why you are seeing changes in the image size, but I am sure we do not need to explicitly specify apt-get clean because it is part of the default apt configuration in the docker ubuntu images.
P.S. apt-get clean used to be called earlier, since the base image now does it by default the command was removed from the dockerfile.

@frank-dspeed FYI,
Here is the before and after sizes of the effect of apt-get clean in the docker file
# BEFORE
sameersbn/redmine            latest              25c4044d1f2e        5 days ago          695.8 MB

# AFTER
sameersbn/redmine            latest              8b70e7507af0        6 seconds ago       695.9 MB

wirred maybe there is then a older ubuntu base img in my registry


Fix expired certificate test

What this PR does / why we need it:
Fixes a broken test caused by a hardcoded certificate that has expired.
Special notes for your reviewer:
This isn't a good fix. What we should actually do is use one of our existing utility functions to generate a cert on the fly. However, as this failing test blocks all PRs the quick fix is to regenerate the cert and fix it properly later.
Release note:

NONE

/kind bug

/hold
/lgtm

/hold cancel


proper chip and lines simulation to integrate on CI/CD

gather here any info related to the simulator.
for the two major versions if possible.

one partial update on this,
assuming that the kernel has the gpio-sim module, the following commands should create a fake chip for testing purposes:
mount | grep configfs  # provavelmente /sys/kernel/config
sudo su
modprobe gpio-sim
mkdir -p /sys/kernel/config/gpio-sim/fakegpio/gpio-bank0/line0
echo 1 > /sys/kernel/config/gpio-sim/fakegpio/live
chmod a+rw /dev/gpiochip1

then we can manipulate that chip like a real one, using libgpiod, or by /sys/devices/platform/gpio-sim.0/gpiochip1/sim_gpio0
detailed info at

https://www.kernel.org/doc/html/v6.7/filesystems/configfs.html?highlight=configfs
https://www.kernel.org/doc/html/v6.7/admin-guide/gpio/gpio-sim.html?highlight=gpio+sim

if it works as expected, our test suite will be for real and helps immensely in the implementation of missing feature, so we will be able to do a 1.x release and work into 2.x s well.

ok the thing is gpio-sim isn't available on older fedora (i am using 38 to develop 1.x branch) but gpio-mockup was supposed to be there but it is not.
so i need to compile the kernel module and try it again.
and, if it works, i need to proper document the process so everyone else could do it as well.
and, finally, do this in github actions so i can simulate a chip under my CI

this is almost solved. https://github.com/sombriks/node-libgpiod/blob/536bc75fc80d3ba78fb33d5f6ad78f150e55c168/test/prepare-gpio-sim.sh
still need to setup the github runner to be able to modprobe gpio-sim but it already allows local development to proceed.
closing this one to create more specific ones.


Housekeeper overwrites DH client ID after explicit dynamic client registration

Hi,
I have noticed that the housekeeper for the DynamicClientRegistration triggers a new registration request which overwrites a previous explicit registration request as the DataHolderRegistrationManager cache does not get updated by /idp/register call. Is this by design?
The problem with this is that the clientId return by the /idp/register API call can't be used in subsequent maintenance requests.
To reproduce:

Get Client Token from CDR Register (my own helper API)

Get Software Statement Assertion /v1/banking/data-recipients/brands/:dataRecipientBrandId/software-products/:softwareProductId/ssa

Create Dynamic Client Registration request DCR (my own helper API)

Register Software at Data Holder using DCR /idp/register -> returns clientId

-> doesn't update DataHolderRegistrationManager cache and no db entry (sandbox adr.sqlite)
Housekeeper gets triggered at interval
-> checks DataHolderRegistrationManager cache and can't find registered productID
-> generates new DCR which creates a new clientID and sets status of record above to DELETED
-> updates DataHolderRegistrationManager cache and db
Could you please advise if this works as expected? Thank you very much.
Best, Nils

Hi @NilsFrkal,
In step 1 and 3, is it ADR Backend that is doing DCR or are you using your own code to it? (Not sure what you mean by your own helper API.). Also, is this on a clean DB?
The central decision is expressed here:
https://github.com/Regional-Australia-Bank/ADR-Gateway/blob/83bfae6676c4f5f33b74f432fb2c7e088135fd47/src/Common/Connectivity/DependencyGraph.generated.ts#L404
CurrentClientRegistration is run first, to get any existing details from the database (RegistrationManager). DhNewClientRegistration will be executed if and only if the database did not return an object.
So the actual behaviour of the housekeeper is to not check a cache, but to check the database directly (DataHolderRegistrationManager is not a cache interface but a database interface).
It looks like this would be the core issue:

doesn't update DataHolderRegistrationManager cache and no db entry (sandbox adr.sqlite)

Are you able to set breakpoints and confirm that this code is not being run in your reproduction step 4?:
`. https://github.com/Regional-Australia-Bank/ADR-Gateway/blob/83bfae6676c4f5f33b74f432fb2c7e088135fd47/src/Common/Connectivity/Evaluators/DynamicClientRegistration.ts#L285
2. https://github.com/Regional-Australia-Bank/ADR-Gateway/blob/83bfae6676c4f5f33b74f432fb2c7e088135fd47/src/Common/Entities/DataHolderRegistration.ts#L119
Even better, if you can use the postman collection as a basis and step through calling the ADR Backend endpoints to create the registration, and copy the requests and responses here, that would be beneficial. This is the way that ADR-Gateway is designed to be used -- as a webservice and a single access point for accessing the CDR ecosystem as a data recipient. For what it's worth, a version 2 of Dr. G might expose the APIs as a node.JS package for consumption in your own service implementation.

Thanks a lot for your response, this makes sense. The "mistake" I made was calling the /register API from Postman directly (bypassing ADR Gateway and passing the DCR JWT to the dataholder endpoint). In this case the housekeeper will generate a new registration request as described above. I have now moved to DhNewClientRegistration via ADR Gateway and this creates the required entries. Thanks again.


docs: first pass at consolidating API docs

This is a first pass at consolidating the API service documentation. It does not include revisions to the API usage documentation.
This is an iteration towards #337

The docs PR has revealed some bitrot in our API unit tests: https://pantheon.corp.google.com/cloud-build/builds;region=global/b7d3be9a-68bb-4ca7-bb7e-45a2bb702f1c;step=3?project=emblem-ops
These seem unrelated to this change.

Noting for reviewers: this PR moves some docs around, removes some redundant text, and clarifies a few things. It's meant as a raw first iteration. I would prefer to keep scope tight and not reopen discussions about what's been written. More PRs to improve it are very welcome!


⚠ ClamAV has degraded performance

In 4f986b1, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 183 ms

Resolved: ClamAV performance has improved in b8d7d5f.


Avoid ownership for API parameters being serialised

A simple, non-functional change to avoid requiring ownership of objects passed to API methods. The objects are just getting serialized, no need for ownership.
This avoids clones for upstream programs.

cc @realbigsean


asset slider shows half height on macos

mixer needs to be enabled to notice this, as it happens when the asset slider shares the screen width with the mixer card

this is on fullscreen, the height is over extended

this is on fullscreen, the height is over extended

I think we should just center the logo and text for the slider.


Add support for new tooltip callback events

Adding a few additional tooltip callback events which I think are useful.

@rowanwins when we introduced inline plugins, we talked about deprecating use of callbacks because it adds redundancy to the code, so I would rather just implement plugin hooks and remove this new callbacks.
new Chart(ctx, {
    plugins: [{
        'beforeTooltipShow': // cancelable
        'afterTooltipShow':
        'beforeTooltipChange': // cancelable
        'afterTooltipChange':
        'beforeTooltipHide': // cancelable
        'afterTooltipHide':
    }]
});

That's a lot of new plugin hook, we could also have simply:
new Chart(ctx, {
    plugins: [{
        'beforeTooltipEvent': function(chart, args) { // cancelable
            var event = args.event;
            var type = event.type; // 'show', 'change', 'hide'
            //...
        },
        'afterTooltipEvent':
    }]
});

@etimberg @rowanwins thoughts?

Hi @simonbrunel
While Im happy to implement things your prefered way I'll need some guidance on where or how I do that? I also don't understand the Chart.plugins.notify reference from @etimberg . Sorry Im still very fresh at looking through this code base and understanding how it all works.

@rowanwins notify is the method that actually dispatches the call to all the plugins (inline or global).
code
example use

An example how to cancel an action with before hook.

Thanks for the information @etimberg & @simonbrunel , that definitely makes things a bit clearer. I'll revise my request and resubmit.

Sounds good :)
That's minor, but I would go for hide, show and update instead of open, close and change. I usually associate open/close to create/destroy, which is not the case here. And update for consistency with other *Update hooks.

hey @rowanwins are you still interested in making the updates discussed above?

Hey @etimberg
Sorry I kinda ran out of puff on this pull request. At the time I had a use for it but not so much any more. Between various commitments I'm probably not going to find time to implement it sorry. Im happy to close the request off if you'd like or someone else might want to take it on.

@rowanwins no worries! I'll keep this open for a few days to see if anyone is interested in taking it up. If not, I'll close it out.


Disable unnecessary mirroring elements

This mod fixes disabling unnecessary mirroring elements (UI items and cron job).
Related: https://github.com/go-gitea/gitea/pull/16957
Related: https://github.com/go-gitea/gitea/pull/13084
Author-Change-Id: IB#1105104

This is updated version of #13084 adjusted to current main.

I think there is only one block here.

Please update the branch

Done.


[Feature Request] Private calendar

Dear Milan
First of all, thank you for your awesome formatter.
Is it (already) possible to use it with a private calendar, will it be implemented soon or is it not possible at all, because of google?

@jonathanwinter123 I have checked that. In the Google API Manager you are able to generate a key with specific restrictions and use it as the "key" parameter in your calendar url "https://www.googleapis.com/calendar/v3/calendars/{calendarid}/events?key={Your Public API Key}". If an environment in which the "FormatGoogleCalendar" script is executed doesn't fit the restrictions Google doesn't return requested calendar JSON output. So there is nothing to do on the side of the script to make Google return a correct response. See the image: https://postimg.org/image/bbr1ixg9z/


chore(main): release 0.1.0

:robot: I have created a release beep boop
0.1.0 (2024-04-27)
Features

add ligatures plugin (7bfff60)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/jozan/tailwind/releases/tag/v0.1.0 :sunflower:


How do we run this in production?

Thanks for the article! How should we deploy this/ run it in production?

I suggest looking at https://github.com/electron-userland/electron-builder or https://github.com/electron/electron-packager. I've used both and they are pretty popular for packaging an application for distribution/installation.
https://github.com/vicentedealencar/electron-with-create-react-app/commit/f1729381d588e65ac140ce5a08cc6277babd9641 shows an example with electron-builder


[Tutorials: NER against custom dataset] add paragraph: How to upload a large dataset

In this tutorial, @jnehring how should this look like? Via a file upload? Or just a description how to do this?

Just a description how to do this. Right now I think of explaining how to chunk the dataset and also suggesting a rdf serialization format for the data like n-triples.
There is a similar discussion here: https://github.com/freme-project/freme-ner/issues/114 .

Implemented first draft. @jnehring please have a look at api-dev.freme-project.eu/doc/tutorials/entity-recognition-against-custom-dataset.html#upload-large-dataset.

I changed the new content a bit and moved it to the bottom of the article. This issue is finished.


Fixed renaming config path references

Short description of the work completed

Steps to test (if not obvious)

For Reviewer Use Only

[x] Code Reviewed
[x] Tests Passed
[x] Coverage Reviewed
[ ] Feature worked as expected
[ ] Updated src/help.js and README.md
[ ] Is the version upgrade path clear for this change? (breaking vs minor vs
patch)
[ ] Follow up work tracked in a card if needed

Testing Steps...
[x] Reset Flow (tag-release reset)
[x] Library Worked (npm start from catch-tag-release)
[ ] Normal Flow (tag-release)
[ ] Config Flag (tag-release -c ./public/manifest.json)
[ ] Dev Flow (tag-release dev)
[ ] QA Flow (tag-release qa)
[ ] Pre Flow (tag-release pre)
[ ] Post Flow (tag-release pro)
[ ] Post Flow with Conflict (tag-release pro)
[ ] PR Flow (tag-release pr)


Don't understand the utility of "Confirm profile" button

On "my profile" page, we have a "confirm profile" button. I'm not sure about its utility, cause we can update information directly with an Onclick() event. I think we can remove it

After looking at this issue, it seems that the confirm button is only a redirection to the homepage.
All user informations are successfully saved without clicking on it, even on a first sign in.
I think we can remove it, what do you think ?


Update widlparser

https://github.com/plinss/widlparser/commit/b144ef226a7fd98f9c404fd385eaf99719988a82 adds support for mixins, which many specs would love to use.

See also #1124.


Adding orderBy to included field breaks typings

Bug description
OrderBy in deeper include breaks types.
How to reproduce

Use https://github.com/prisma/prisma-examples/tree/prisma2/typescript/graphql
Add new queryField

const test = queryField('test', {
  type: 'Boolean',
  resolve: async (self, args, { prisma }) => {
    const users = await prisma.user.findMany({
      include: {
        posts: {
          include: {
            author: true
          },
          orderBy: {
             title: "asc"
          },
        },
      },

    })
    // Here author is not available in typescript suggestion
    users.map(d => d.posts[0].author)
  },
})

Expected behaviour
Author type should be available in the post
Prisma
Using Preview-24 but also fails on 2.0.0-alpha.972

I can confirm this bug in preview025 and in 	2.0.0-alpha.997


'Wrong labels used for evaluation, possibly caused by training examples left in the input pipeline

I get Assertion error:
'Wrong labels used for evaluation, possibly caused by training examples left in the input pipeline'
I am playing with
epoch_size and batch_size

But I can't seem to trace down why it happens.
Any tip?

Closing this. Reopen if it's still a problem.

ANy updates on why this error tends to occur? I am trying to do LFW evaluation after certain batches and not after every epoch. SO I moved the save and evaluate functions into the train() function.  I can post a more detailed question in a separate post. Should I open a new issue?


Ty/instructor in agent

This PR swaps out zod-gpt for instructor. This gives us better control over object generation + access to many more models.

Basically happy with this, openai functions same as before, Anthropic supports claude-3-5-sonnet-20240620. Opened #102 to preserve our API, merge that and we can merge this.


History mode config example for Caddy 2 webserver

What problem does this feature solve?
!1555 has introduced a snippet to configure the Caddy web server to be compatible with vue-router's history mode. However, for version 2 of Caddy, the config directives' syntax has changed.
What does the proposed API look like?
One might either use try_files or rewrite.

Never mind, just found that there's already a PR for it (#3215).


mocap4r2: 0.0.6-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository mocap4r2 to 0.0.6-1:

upstream repository: https://github.com/MOCAP4ROS2-Project/mocap4r2.git
release repository: https://github.com/MOCAP4ROS2-Project/mocap4r2-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.0.3-1

mocap4r2_control

No changes

mocap4r2_control_msgs

No changes

mocap4r2_marker_publisher

No changes

mocap4r2_marker_viz

No changes

mocap4r2_marker_viz_srvs

No changes

mocap4r2_robot_gt

No changes

mocap4r2_robot_gt_msgs

No changes

rqt_mocap4r2_control

No changes

Hi!!
This is a new version trying to fix the buildfarm errors.


Json Data Issue

pls help on this
which key is used to show the selected value in json data.

Component JSON is only used to represent component options that are used to render it. Current value of the component is stored in the component state. If you want to perform some manipulations with it or make the value dependent on the other components, you can try to set up Custom Logic or Conditionals. For further info see https://help.form.io/userguide/form-building/logic-and-conditions.


EKS Managed node groups autoscaling

Request to improve aws_eks_node_group module

[ ] bug report
[x] feature request
[ ] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
In the aws_eks_node_group scaling_config block you are required to set the desired size.  This is undesirable b/c I want to let my nodes autoscale within the min-max range I set.  Everytime my terraform is deployed it tries to reset the ASG to the desired size set within terraform.
I believe desired size should be optional.  When you use an ASG directly with Terraform the desired_capacity is optional and would expect the same for this API that manages an ASG behind the scenes.
What's the expected behavior?
Would expect to set a scaling min and max size without setting a hard desired size.

I think you need something like this? https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/workers_launch_template.tf#L214-L218

@max-rocket-internet Sorry for the confusion I posted this in the wrong place.  I was referring to fixing the official AWS provider resource aws_eks_node_group
If anyones interested I opened an issue for this there now:
https://github.com/terraform-providers/terraform-provider-aws/issues/11296


Add guest-profiler support to serve mode

I don't understand why the package-check CI job is failing for me, but since it's failing to pull in test-fixtures/data/ca.pem which was just merged a few hours ago, maybe @acw can take a look?


Update keyvault to enable live testing in sovereign clouds for multiple services

These changes enable keyvault to run live tests against AzureUsGovernment and AzureChina clouds. The sovereign cloud live tests will be green with the changes.
@benbp @danieljurek @jongio

@benbp @danieljurek @jongio

@benbp - Next steps on this one?

/azp run net - keyvault - tests-weekly

@jongio based on the test weekly pipeline results there seem to still be functional issues that need to be addressed with this PR. I'm re-running since the old build logs got cleaned up, but as far as I can tell there's still work to be done?

@zedy-wj / @v-xuto - Please have a look.  Thanks

@benbp The issue was about HSM tests for UsGov and China clouds. I excluded them.

/azp run net - keyvault - tests-weekly

@benbp there is a passing test-weekly build https://dev.azure.com/azure-sdk/internal/_build/results?buildId=890077&view=results.

Great, thanks @zedy-wj!


Have problem in the MoNuSegTrainingData?

I could not see the label in the Annotations folder. In this folder has only .xml file. Please help me have labels in order train. Thank you.

Thank you.

You will have a matlab script in that folder to convert these .xml files to .tiff files.

Thank you @jeya-maria-jose ,
Please help me, How do I run the "he_to_binary_mask_final.m" file ( this file is the convert file as you comment).

The link to dataset is ./MoNuSegTraningData/Annotations
Thank you @jeya-maria-jose very much.

You should send input the directory containing .xml files as the input argument to the function.


Publish micro-json to npm?

The json() function in the micro lib is very useful on its own outside of micro contexts. Should we publish it to npm?

@TooTallNate we moved stuff into micro-core. Since everything is so small there already…

you can just do
import { json } from 'micro-core';


Optimized ZFS refresh in LXD 5.0 prevents migration from LXD 4.0 LTS

Trying to migrate an instance from LXD 4.0 LTS to a LXD current server fails, even after https://github.com/lxc/lxd/pull/10567 has been fixed when using ZFS on both sides. BTRFS seems OK, as does ZFS to a non-ZFS pool.
Reproducer:
LXD 4.0 Source v1:
lxc launch images:ubuntu/jammy v1
lxc shell v1
snap install lxd --channel=4.0/stable
lxd init # Choose ZFS storage pool
lxc config set core.https_address=[::]:8443 core.trust_password=pw
lxc init images:alpine/3.16 c1
lxc snapshot c1

LXD 5.x Target v2:
lxc launch images:ubuntu/jammy v2
lxc shell v2
snap install lxd --channel=latest/edge
# If edge doesn't include https://github.com/lxc/lxd/pull/10567 make sure to side load it.
lxd init # Choose ZFS storage pool
lxc config set core.https_address=[::]:8443 core.trust_password=pw

On the source v1:
lxc copy c1 v2: --refresh
lxc copy c1 v2: --refresh # Works
lxc copy c1 v2: --refresh # Fails
Error: Failed instance creation: Error transferring instance data: Failed creating instance on target: Problem with zfs receive: ([exit status 1 write |1: broken pipe]) cannot receive new filesystem stream: destination has snapshots (eg. default/containers/c1@snapshot-snap0)
must destroy them to overwrite it

# Oops it has left behind a zfs send on the source too. Preventing deletion of the instance.
ps aux | grep zfs
root        4994  0.0  0.4   8704  4500 ?        S    09:08   0:00 zfs send -c -L default/containers/c1@migration-9af76474-da35-483b-a063-
kill 4994

Sending to a non-optimized storage pool works:
lxc shell v2
lxc delete c1
lxc storage create dir dir
exit
lxc shell v1
lxc copy c1 v2: --refresh -s dir # Works
lxc copy c1 v2: --refresh -s dir # Works

Follows on from https://github.com/lxc/lxd/issues/10186

Fixed in #10591.


MacOS build fail due to getgroups

error[E0425]: cannot find function `getgroups` in module `nix::unistd`
   --> vm/src/stdlib/os.rs:265:35
    |
265 |     let groups_ids = nix::unistd::getgroups()?;
    |                                   ^^^^^^^^^ not found in `nix::unistd`
help: possible candidate is found in another module, you can import it into scope
    |
1   | use libc::getgroups;
    |

I am working on this issue.


Support for GE Jasco Ultra Pro Dimmer, Toggle, and TH16 Temp sensor

GE Jasco Ultra Pro Toggle Dimmer v2
GE Jasco Ultra Pro Toggle Switch
TH16 TH06WB3S Temperature and Humidity Sensor

The test failures are all from the main branch hotfix last night.  Auto version rollover was updated to be async, so the tests need updating.