A somewhat negative user experience anecdote for a great code generation package.

I've found myself quite happy with the package so far, it really saves me a lot of time.
I wanted to share a little negative experience I've had today about debugging and the danger of blindly relying on code generation.
Basically I had a somewhat complex query with 3 text/string arguments and a certain number of joins and subqueries.
It was pretty yucky so today I've been refactoring it.
To do so I've taken a populated database .sqlite file and I've been testing the query during refactoring in DBeaver.
After that the new query was ready and tested I've re-applied the same parameter names to the 3 parameters, placed the modified query in the .moor file and restarted generation.
So far, so good.
However during tests I've started getting wrong expected results on examples I've already tried before in DBeaver.
After spending a considerate amount of time trying to get the exact query that was being launched on the database (which I was unable to do anyway) I've noticed that on the generated query method the parameters changed order and not only I felt quite stupid but I've also thrown precious time in the garbage.
So, let's make it clear again: it's totally my fault I'm not saying this is an urgent issue.
Anyway I think it would be neat for the generated methods to have a set of named parameters so that you do not get semantically broken (but syntactically valid) method calls in case of a change of order during query definition generation.
This would make easier to join query parameter semantic with code semantic as users do not have to check parameter order for every query call when a query refactoring happens.

Thanks for sharing your experience!

After spending a considerate amount of time trying to get the exact query that was being launched on the database (which I was unable to do anyway)

All database implementations (VmDatabase, FlutterQueryExecutor, ...) have a logStatements parameter for this purpose. I see how that's pretty hard to find, but its rarely used so I'm not sure how much publicity it deserves. The documentation should probably mention it somewhere.

Anyway I think it would be neat for the generated methods to have a set of named parameters so that you do not get semantically broken (but syntactically valid) method calls in case of a change of order during query definition generation.

I fully agree with this, and really like your suggestion. We could generate positional parameters for positional variables (?, ?123) and named parameters for named variables (:apply_filter). This would be breaking for existing code so we need to make it opt-in, but we can make it the default eventually.

I added a build option to generate named parameters for named SQL variables, it will be available with the next moor version. I also added documentation for the logStatements option to the FAQ. Thanks again for your feedback and suggestions!

Great idea! I also ran into this once :)


Ken/about page

Adds the about page.

Not done but we gonna merge rn and @tonyanguyen will finish in [FILL]


Add helpful error message when assert basem fails

https://github.com/asottile/setup-cfg-fmt/blob/8b497a9a7036a9589395e5c128bece2c7990cc45/setup_cfg_fmt.py#L259-L261 can fail with error that I'm finding hard to interpret. For example running this on https://github.com/ianhi/mpl-interactions/blob/0.18.0/setup.cfg fails with the below error and it's not clear to me how to fix it.
Traceback (most recent call last):
  File "/home/ian/mambaforge/envs/mpl-dev/bin/setup-cfg-fmt", line 8, in <module>
    sys.exit(main())
  File "/home/ian/mambaforge/envs/mpl-dev/lib/python3.9/site-packages/setup_cfg_fmt.py", line 502, in main
    if format_file(
  File "/home/ian/mambaforge/envs/mpl-dev/lib/python3.9/site-packages/setup_cfg_fmt.py", line 412, in format_file
    group_requires = _requires(cfg, key, 'options.extras_require')
  File "/home/ian/mambaforge/envs/mpl-dev/lib/python3.9/site-packages/setup_cfg_fmt.py", line 220, in _requires
    normalized = sorted(
  File "/home/ian/mambaforge/envs/mpl-dev/lib/python3.9/site-packages/setup_cfg_fmt.py", line 221, in <genexpr>
    (_normalize_req(req) for req in require_group),
  File "/home/ian/mambaforge/envs/mpl-dev/lib/python3.9/site-packages/setup_cfg_fmt.py", line 230, in _normalize_req
    normalized = _normalize_lib(lib)
  File "/home/ian/mambaforge/envs/mpl-dev/lib/python3.9/site-packages/setup_cfg_fmt.py", line 244, in _normalize_lib
    base = _req_base(lib)
  File "/home/ian/mambaforge/envs/mpl-dev/lib/python3.9/site-packages/setup_cfg_fmt.py", line 261, in _req_base
    assert basem
AssertionError

substitution hacks are not portable, allowed, or supported

Hi @asottile thanks for the information I didn't know that. I appreciate the pointer on what was wrong but what I'm trying to suggest is to have something like this:
if not basem:
   raise ValueError(f"Library {lib} is invalid")

or something more verbose so that users (i.e. me) have a hint as to where to start looking to fix things.

are you interested in sending a patch?

Happy to, when I opened I wasn't totally clear what was happening - now that I understand will do.


Urlgenerator with collection_name doesnt work

Passkit::UrlGenerator.new(Passkit::CartTicket, {generator: @cart, collection_name: :tickets}).android
→  undefined method `id' for an instance of Hash
Passkit::UrlGenerator.new(Passkit::CartTicket, @cart, :tickets).android
→ wrong number of arguments (given 3, expected 1..2)
I tried the following ways to generate a url for multiple tickets from a cart. But both options returns errors. What am I doing wrong?
Without the collection:
Passkit::UrlGenerator.new(Passkit::CartTicket, Ticket.last).android
everything works fine.

Fixed it by changing the gemfile to:
gem 'passkit', git: "https://github.com/coorasse/passkit.git"
The 7.0 release isn't on rubygems.


Fix: Update preview.sh script to reflect overlay change

This change is necessary to sync with the overlay changes done with PR

/lgtm


"Debug: Attach to Node Process" + sourceMapPathOverrides

Debug: Attach to Node Process is an awesome feature – no need to update npm scripts with --inspect and, most of the time, no need to create launch.json configs.
However, I'm in a situation where I'm trying to debug a Node.js project in a subfolder in my workspace. So in a console, I do:
cd subfolder
yarn dev

VSCode can successfully attach to the process but all paths are broken – the debugger sends paths like src/server.ts but VSCode should interpret this as subfolder/src/server.ts.
If I started the process via launch.json (which I generally don't like too much – it duplicates a few things from package.json, not all team members are using VSCode, etc.), this would work:
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Example",
      "runtimeExecutable": "node",
      "runtimeArgs": ["--inspect", "node_modules/.bin/next", "dev"],
      "port": 9229,
      "cwd": "${workspaceFolder}/subfolder",
      "sourceMapPathOverrides": {
        "webpack:///./*": "${workspaceRoot}/subfolder/*",
      }
    }
  ]
}

I just learned today about sourceMapPathOverrides and it makes VSCode work, however, I'd really much prefer to be able to do Debug: Attach to Node Process and still somehow tell VSCode to apply a custom mapping.

In tomorrow's nightly of our new debugger (when installed, it will register a command Debug: Attach to Node Process (preview)) you'll be able to add defaults in your user or workspace settings, like so:
"debug.javascript.pickAndAttachOptions": {
  "sourceMapPathOverrides": {
    "webpack:///./*": "${workspaceRoot}/subfolder/*",
  }
}

Let us know if you run into any more issues!
(Versifiers: easiest way to test is add this option with trace: true and verify that the debug adapter prints "Verbose logs are written to: ..." in the debug console)

Oh wow, I thought I'm in some edge case and a few hours later, this issue is fixed 😄.
Workspace setting sounds great, and what you suggest in https://github.com/zeit/next.js/pull/10807#issuecomment-608171931, i.e., being able to detect path mappings automatically with the help of lsof, sounds even better. Is there already an open issue for it?

@connor4312 Actually one point to the solution mentioned above:
Our monorepo has several Next.js projects in subfolders, like this:
- <workspace root>
    - nextjs-app-1
    - nextjs-app-2
    - nextjs-app-3

So having a single path mapping probably will help only partially – in some README, I'll probably need to suggest that the person debugging should update .vscode/settings.json temporarily (making the file modified as far as Git is concerned, which is a bit annoying).
Again, if lsof could solve that, that would be great. Otherwise, I'm not sure that there's much to do about that, maybe some sort of "interactive Attach to Node Process" that would ask for a real folder path via quick pick UI?

We already use lsof when it's available 🙂 But right now it's only used when there's 0 or >= 2 workspace folders open--if there's exactly one open folder, we use that as the process cwd. As of https://github.com/microsoft/vscode-js-debug/issues/326, for normal launches we set the cwd based on the nearest package.json-containing folder. Maybe we can adjust our attachment algorithm to do the same--if lsof is available, use the nearest package.json-containing folder inside any workspace folder. For Node.js, sourcemap resolution happens relative to the working directory, so that should work here, I think.

For normal launches we set the cwd based on the nearest package.json-containing folder. Maybe we can adjust our attachment algorithm to do the same.

That sounds great indeed.
If I understand correctly, the attach would detect nextjs-app-1/package.json, set cwd to nextjs-app-1 and all paths (which are currently relative to nextjs-app-1, not our workspace root) would suddenly work.

Yep, that's right.

To verify:

Add the setting "debug.javascript.pickAndAttachOptions": { "trace": true }
Run node --inspect in some terminal
Run the command Attach to Node.js Process (preview) and pick that process
Verify that the location debug log file is printed to the debug console (i.e. that the trace setting applied to attachment)

Followed the steps but not seeing the log?

@JacksonKearl the log should be in the "debug console" tab, rather than the terminal.

I'm seeing the attach create two debug consoles, Node.js Process and process, and the log is shown in process. Is this expected?

I think that's intended behavior (cc @isidorn) so that you don't lose previous logs if you run a new launch config. (I see the same thing, but with an "Extension Host" entry since that happens to be the last thing I debugged).

Yes this is designed behavior.


Upstream repository PRs

There are upstream packages that we would need to submit PRs for before we reach point of removal our, eigerco dependencies from the celestia-node.
It's quite hard to estimate this as it would involve 3rd party teams and organizations. It may take some time for all of the PRs to be reviewed and accepted.

This wont be part of the Milestone 1


chore(main): release sinkchart 1.17.1

:robot: I have created a release beep boop
1.17.1 (2023-02-10)
Bug Fixes

crash for undefined dependencyVulnerabilities (1214155)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sinkchart/releases/tag/sinkchart-v1.17.1 :sunflower:


Clean up CfL implementation

CPU feature check for SSSE3.
Measure rdo_cfl_alpha() speed.
Remove redundant loop for 2x speed-up.
Tidy up formatting.

Impact to encoding time (0.4%) and BD-rate is quite small:

PSNR
PSNR Cb
PSNR Cr
PSNR HVS
SSIM
MS SSIM
CIEDE 2000

0.0097
0.0673
0.0792
0.0059
0.0106
0.0125
0.0519

Whether the new linear search is better is a question of taste.

Allowing to skip CfL mode if best alpha is zero gives a 1% reduction in encoding time.
However, it shifts AWCY results in favor of chroma somewhat.

PSNR
PSNR Cb
PSNR Cr
PSNR HVS
SSIM
MS SSIM
CIEDE 2000

0.1842
-0.1632
-0.2235
0.2150
0.2236
0.2596
0.0083


Update the pkg in Bioc devel

For the named package maintainer:
Time to make sure that the latest updates to Bioc packages are pushed to Bioc devel branch (note the approaching DLs):
https://www.bioconductor.org/developers/release-schedule/
And checked for builds
https://bioconductor.org/checkResults/devel/bioc-LATEST/miaViz/lconway-buildsrc.html
See "Sync an existing GitHub repository with Bioconductor" in
https://contributions.bioconductor.org/git-version-control.html#sync-existing-repositories

Up.


Disable lettuce lib telemetry instrumentation shows different behaviour for Env variable disable vs System property disable.

Bug Report

Current Behavior

There are 2 ways to disable instrumentation
1. Set Env variable OTEL_INSTRUMENTATION_LETTUCE_ENABLED to false
2. Set System property otel.instrumentation.lettuce.enabled to false
There should not be any difference in performance with the approaches but there is. Difference was observed in write time, CPU utilisation and failure in some cases.
When instrumentation is disabled via System property.
Size      Latency    CPU utilisation
209MB     27528      0.75
150 MB    Failure    RedisCommandTimeoutException

When instrumentation disabled via env variable.
Size      Latency      CPU utilisation
209MB     915          0.11
150MB     731          0.08

Summary : Disabling lettuce instrumentation using env variable has resulted in 100% reduction in failure and huge latency improvement.
Question
Why there is difference using those 2 behaviour?
How can we make sure the behaviour with both the approaches are same?
Environment

Lettuce version(s): lettuce-core-6.1.10.RELEASE

Hey @neer112233 apologies for the late reply.
This issue should perhaps be directed to the https://github.com/open-telemetry/opentelemetry-java-instrumentation project, as it is the one that seems to manage these settings.
Can you verify my understanding?


Customizable Transition Duration

Description
Describe your issue here.
What type of issue is this?

[x] enhancement (feature request)

Requirements

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
I was really excited to see the addition of a full screen presentation mechanism for PanModal recently. I noticed in the Full Screen example there was a custom spring damping, which seems reasonable, but the animation doesn't feel quite native as a result. The issue isn't the spring damping though, but the fact that the animation duration isn't customizable.
I'd like to request to add an animationDuration property to PanModalPresentable for use in the modal presentation, that will allow the timing to be customized.
Thanks a lot!
Reproducible in:
PanModal version:
1.2.2
iOS version:
Tested on 12.2, but should be all versions that PanModal supports.

Hey @mergesort,
Glad to hear that you find it useful :D I went ahead and added
both transitionDuration & transitionAnimationOptions https://github.com/slackhq/PanModal/commit/0d999396a5e05b95479ad559321bb39f7ccc50ec let me know if this helps!
Stephen

@tun57 Just gave it a shot, works great. Thanks a bunch!


Design aggregator of cells

Resource binding service in https://github.com/ckb-js/kuai/issues/7

Duplicated with https://github.com/ckb-js/kuai/issues/85


WIP flink hacking --rpm build complete

This looks like its rolling along nicely.
Bhupendra can you paste the results of some manual tests if it's working?

Updated the spec file for adding features and yes surely will look into 1.0 RC for merging.

Sure Jay, were working on Debian packaging, completed that. Will definitely try to deploy and run some manual tests.

This is great indeed. For the next pass (@Jayunit100 ?), since Flink has streaming connectors with Kafka 0.8.x, 0.9x and Storm, it would be great to add end-2-end integration tests to validate the connectors.

@c0s updated the bigtop repo url for openstack provider..

There's four different commits in here. I will just pick one for the repo url and generate the patch from it.

Bhupendra, do u have any manual test results yet that you would like to share about Flink-BigTop integration ?

@smarthi  We went over the work so far saturday.  As of now the RPMs are able to launch flink masters and slaves.  Now its just a matter of tooling the puppet stuff to launch similar to how spark does, rather than using a node-aware bash wrapper.

Thanks @jayunit100, looking forward to it

I've built the pull request to see if RPM package generation works. The binary package contents look fine. The Debian package is still missing. Are you working on it or do you want to do a follow-up pull request? I haven't played around with Bigtop much but it looks like it wouldn't be too hard to build a Debian package, now that we have the RPM.

The scripts for building the Debian package are also part of the prior commits. You can check those scripts in /bigtop-packages/src/deb/Flink.

Ah thanks. I've also checked out the Debian package contents. Look good as well. I went ahead and installed it on my Ubuntu machine.
I was wondering, why does the package depend on hadoop-client? Flink packages Hadoop and doesn't require an existing installation of Hadoop. Further, it depends on bigtop-utils which is IMHO only necessary because of a java detection check. The latter is probably ok because most people have that package installed anyways if they work with Bigtop. However, I think we should consider removing the Hadoop dependency.

I've gone ahead and installed the Debian package and commented on some issues. The log4j*.properties files are not included in the Debian package, probably because the /log directory is missing from flink.dirs.

Overall this is coming together nicely.  I think given the community demand if the rpm builds I'm on the side of merging after I test this , with smoke tests to come in a follow up patch, so that the community can start banging it around.
We should remove the vagrantfile changes but that is mostly just a nit.

Obviously i will work with Bhupendra and the others to rebase the commits and so on so that attribution is done properly
And so it's a clean patch.  But overall seems like it should work now.zzz

What is the status on this pull request?
We have a flink user who's using Bigtop and who would like to have a Flink integration from bigtop, in particular the packaging.
I'm pretty busy right now but maybe tomorrow I have some time to address the open comments and open another pull request based on this one.

Looks like the tests are still failing as is but I think it is in a state where it might be useable.
Maybe we should commit it to a WIP branch?

If you agree I can address @mxm comments regarding the rpm packaging. Once these comments are addressed I assume the code is good to be merged to master.

The issues pointed out by @mxm have been addressed and we have also tested the new rpm package on local environment as standalone package. We have also incorporated the master worker configuration and currently facing some issues during puppet deployment. We are still resolving the issue. Should I push the latest code so that others can also have a look.?

Ignore the changes in the vagrantfile and vagrantconfig.yaml, they were only for testing purpose.

Also rebase into 2 or 3 commits attributed to your team after you fix the merge.

Need a couple of days, have got submissions and finals this week. So everyone on the team is busy. We will take this up on Friday and hope to fix everything over the weekend. :)

Just FYI: I opened a pull request just for the packaging, based on this one: https://github.com/apache/bigtop/pull/101

Since #101 has been merged, this pull request is obsolete (I have to admit that I forgot to properly attribute the work from #101. This was a mistake while rebasing on my end when I was addressing some of the PR feedback)


Support CSS media queries

Just needed the proper  tag

Please update https://github.com/ruby-grape/grape-swagger-rails/blob/master/CHANGELOG.md too, via --amend.

Was able to replicate the earlier spec failures by downgrading my FF.  Adding sleep 1 does the trick with selenium_webdriver sometimes, although I know find shouldn't timeout so quickly. (shrug)
Current CI problems look to be 2.0.0 and 1.9.3 gem installation issues.

Indeed, sleep is definitely not the way to go. Lets worry about the build separately.

Merged via https://github.com/ruby-grape/grape-swagger-rails/commit/0c9c65a4486e94f595525a686b52b64b5bbb014b.
I fixed the build issue by locking mime-types to < 3.0 in https://github.com/ruby-grape/grape-swagger-rails/commit/6293c7c8d09883d1329b9a2bb1725053d3fcb3e5, same as we did in Grape.

Build fixed in https://github.com/ruby-grape/grape-swagger-rails/pull/40, disabled animations to avoid the sleeps.

Excellent!  Thanks for the quick turnaround and tip off to https://github.com/mikz/rack-no_animations


File not found error on Movie_Recommendation page

Describe the bug
File not found error on Movie_Recommendation page
To Reproduce
Steps to reproduce the behavior:

Go to Movie_Recommendation page
See error

Expected behavior
No server error should be there.
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Closing it because of setup issues


Adding measure to market models

I don't think this is needed anymore, as foundations and measures are going to be combined into one object.
Sorry to have wasted your time, @grdw. I'll close this, but please re-open it if I've misunderstood something...


Feature Request: export prom style metrics about what kubeip is doing.

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Feature Request: export prom style metrics about what kubeip is doing in order to monitor it for errors.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

what we need to expose ? So far for my case, I think we can export which IP address that pointed to what node VM name

no plans to implement this for KubeIP v1.
KubeIP v2 can use log-based metrics for this case (together with --json flag or LOG_JSON env)


Version bump to Squirrel 1.0 Preview

https://github.com/Squirrel/Squirrel.Windows/releases/tag/0.99.0

:+1:

Published in 0.32


Always generate appearance.js in js folder

depending on the basePath, the "appearance.js" was generated in an additional subfolder (Example: set the basePath to "https://example.com/foobar/", the file was generated into "/js/foobar/appearance...js" instead of "/js/appearance...js" ).
This fixes the behaviour, the javascript resource is always generated into the target "js" folder along with all the other js files.

Not sure about this one @fuse314. What is this fixing?

Steps to reproduce:

open config.toml, set baseURL = 'https://example.com/foo/bar/baz/'
delete local "public" directory
run hugo
check content of "public" directory for a directory called "foo":

example:

the pull request always generates the javascript file into the "js" directory, along with the other javascript files.

@fuse314 which given that you defined a baseUrl like that makes sense right? What exactly doesn't work when you do this?

@nunocoracao no, it does not. If I deploy the public folder to /foo/bar/baz/ on the webserver, the full url to this file is /foo/bar/baz/foo/bar/baz/js/appearance....
It is the only file in the double relative path, all other js files are deployed in the /js/ folder.
Just try it out locally and look at the resulting folder structure and the files.
I have various existing folders in my webroot and I have to create "include" and "ignore" rules for ftp deployment. It just makes these rules unneccessarily more complex.


A viewer must specify exact sources for them to show up in the tray

should be able to just say "photos" or "places" and get the whole lot.

@ctide, assigned to you to make sure this gets fixed with the new UI, not the old one.


Updated MySQL connector Jenkins job to use custom ports for MySQL

Jenkins slaves in http://ci.hibernate.org have a MySQL server already running at port 3306 (probably with root permissions).
SourceTaskContext#configs() wasn't present in Kafka API v1.x, thus removing @Override annotation

@jpechane?

@jcechace Fine for me. Please prefix the commit messages with [jenkins-jobs]  stirng prefix so we can easily categorise them

Could you merge it then, please? Thanks!

@jpechane  done


Feature/add comments

Added rendering of comments and sub-comments and added data fetching to comment input

made a few comments on how state is handled.
is upvoting comments supposed to currently work?

Nope, not yet. Check my lasted post in our Discord channel. I put a question there about upvoting comments.


img ng-src doesn't work as expected with 404 server errors

Hello,
the ng-src binding for error doesn't work as expected if the server responds with an image but the response status is 404.
in a link function on a directive to manage the ng-src events I have this code:
element.bind('load', function() {
    console.log('image is loaded');
});
element.bind('error', function() {
    console.log('image could not be loaded');
});

From some tests I did, if I have a broken link in the url, the ng-src triggers the error function (even if the status of a broken url is 200) but if I send a status code of 4xx with an image in the response, the error function is not triggered.
Can you check if this behavior is correct (maybe it is a feature of the img element and there are no options to check the header status) and eventually suggest a workaround?
Many thanks in advance,
Daniele

IIrc correctly, this is a problem with the img element and not with angular. The error handler will be called if the response is not an image, the success fn will be called even if there is error status code.  I think they will show the same behavior. As far as I know, there's no workaround for this problem except loading the image via XHR, which will correctly read the status.

Hello Narretz, thanks for answering.
Yes, you're right, the behavior is the same with ng-src or src.
Probably, for maintaining consistency between these two way to load an image, it is better to leave ng-src working like now and maybe create a custom directive for an image element that load image data with an XHR call.
Thanks again for the answer.
I'm leaving this issue open for now just to see if that topic could be relevant for some other people.
Daniele

Yes, I think a custom directive could be interesting - but not in the core. ;) Feel free to link to such a directive here if you find / create one.
I'm going to close this issue. I think people will still find it when they search for it.


Added custom marketplace image and second nic

Describe your changes

Added the ability to deploy custom Marketplace images that have Licenses that need to be accepted.
Added the ability to have the VM created with a second NIC.

Issue number
None
Checklist before requesting a review

[x] The pr title can be used to describe what this pr did in CHANGELOG.md file
[x] I have executed pre-commit on my machine
[x] I have passed pr-check on my machine

Thanks for your cooperation!

Also as a way to reduce debt, I think we need to rethink the way we create multiple nics.
The way I am thinking is:
Nics are created by one block
nic_configuration = {
primary = {
subnet_id          = azurerm_subnet.temp-snet.id
primary = false
private_ip_address = "<IP_ADDRESS>"
},
secondary= {
subnet_id          = azurerm_subnet.temp-snet.id
primary = false
private_ip_address = "<IP_ADDRESS>"
}
}
Code block
resource "azurerm_network_interface" "nic" {
  for_each                         = toset(var.instances_count  > 0 ? var.nic_configuration : 0)
  name                          = var.instances_count == 1 ? lower("${local.vm_nic_name}") : lower("nic-${format("%s%s", lower(replace(local.vm_nic_name, "/[[:^alnum:]]/", "")), count.index + 1)}")
  location                      = local.location
  resource_group_name           = local.resource_group_name
  dns_servers                   = var.dns_servers
  enable_ip_forwarding          = var.enable_ip_forwarding
  enable_accelerated_networking = var.enable_accelerated_networking
  internal_dns_name_label       = var.internal_dns_name_label
  tags                          = merge({ "ResourceName" = var.instances_count == 1 ? lower("${local.vm_nic_name}") : lower("nic-${format("%s%s", lower(replace(local.vm_nic_name, "/[[:^alnum:]]/", "")), count.index + 1)}") }, var.add_tags, var.nic_add_tags, )

  ip_configuration {
    name                          = lower("ipconfig-${format("%s%s", lower(replace(local.ip_configuration_name, "/[[:^alnum:]]/", "")), count.index + 1)}")
    primary                       = each.value.primary
    subnet_id                     = each.value.subnet_id
    private_ip_address_allocation = each.value.private_ip_address_allocation_type
    private_ip_address            = var.private_ip_address_allocation_type == "Static" ? element(concat(each.value.private_ip_address, [""]), count.index) : null
    public_ip_address_id          = var.enable_public_ip_address == true ? element(concat(azurerm_public_ip.pip.*.id, [""]), count.index) : null
  }

  lifecycle {
    ignore_changes = [
      tags,
    ]
  }
}


Update README.md

Change Share to Sync(see https://github.com/mrmonday/rust/commit/8f1b4f0305007f53714d4212885dc9598f49664f).
Add a "Getting Started" section.

Hi, thanks for this contribution! Regarding the two dependency variations: Maybe it would make sense to make the package dependency to be something like lazy_static = "0.*" instead, to not break the instruction with every update?

Ok, I edited the commit to address this.
Let me know what you think.

Actually, I meant to use the actual string "0.*" - semver supports wildcards, so that kind of dependency would match any version of this package less than 1.0.0.
However, reading up a bit on semver, it seems like using something like "0.1.*" would be more appropriate, because that allows for any update of this package that does not change its API.
The idea here being that the README contains a cargo dependency line that can be copied directly, and that will do the right thing even if I have to release new versions due to compiler changes :)

Yeah, its kinda hidden away, I only found it because I happened to know it was supported.
Anyway, I'm happy with the text now, thanks for your contribution! :)


quite a few links are broken

looks like there are missing docs
These are all links on https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md that 404 on github for me (basically any link that isn't self referencing spec.md):
https://github.com/openservicebrokerapi/servicebroker/blob/devguide/services/index.html
https://github.com/openservicebrokerapi/servicebroker/blob/master/v2-api-changelog.md
https://github.com/openservicebrokerapi/servicebroker/blob/master/app-log-streaming.md
https://github.com/openservicebrokerapi/servicebroker/blob/master/route-services.md
https://github.com/openservicebrokerapi/servicebroker/blob/master/volume-services.md
https://github.com/openservicebrokerapi/servicebroker/blob/master/catalog-metadata.md
https://github.com/openservicebrokerapi/servicebroker/blob/master/dashboard-sso.md
https://github.com/openservicebrokerapi/servicebroker/blob/master/managing-service-brokers.md#register-broker
https://github.com/openservicebrokerapi/servicebroker/blob/master/api.md#broker-errors
https://github.com/openservicebrokerapi/servicebroker/blob/master/examples.md
https://github.com/openservicebrokerapi/servicebroker/blob/devguide/services/managing-services.html#update_service
this is a 404 on cloudfoundry.org
http://docs.cloudfoundry.org/running/managing-cf/quota-plans.md
I only made it about 20% though spec.md before creating this issue, but it looks like the supporting docs might not have been migrated.

This is a duplicate of #120, and will be fixed by #131.


Cleanup logging (again)

Replace string concatenation in logging statements with parameterized messages.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Current WS-Gate is using Version lacking Basic-Auth support

Working on patched version that generates session-cookies instead

As described in https://en.help.internetx.com/display/APIADDITIONALEN/DomainStudio+Guide#DomainStudioGuide-Activatingtheasynchronousresponse


second pass impact page

made dashboards section a new page.

[ ] change page title Dashboards :  Measuring BIDS Impact
[ ] for the Gender of contributors, add as of June 2024

for the Gender of contributors, add as of June 2024

Will do that in a follow up PR to make sure this is automatically updated when recount this when we have new contributors.


Remove singleton store and unused global STRef class

The deleted code provides a singleton store. I propose we remove it, as it's untested, and users can just hold onto their own reference to the store they create.

Nice! Though we need to have an agreement, how we handle deprecations and removing code. This will not be backwards-compatible and I am unsure what approach we should take:

Keep deprecations until we finally have some stable version and can release 1.0. This will become more and more tedious.
Make one more RC release with a lot of deprecations and point migrating users to that release, so they can fix the deprecations. Then they can update where these APIs will be removed.
Just move fast and accept that we are not really backwards-compatible until 1.0.

Not sure which approach to take.

I think most of the deprecation warnings were added a long time ago. Why don't we do a RC with all the deprecated code deleted, and all deprecation warnings deleted, and then move forward from that point with a goal of responsible deprecation/backwards compatibility thru 1.0?

I have talked about backwards-compatibility and how to move forward with @fdietze as well. We agree that we want to keep the basic API compatible, so that most stuff keeps on working. But we also want to move forward with OutWatch, so if some parts of the API will break that is accepted for now. So for the next RC release, we want to get rid of deprecations and further improve on our API (especially with regards to #328).

As a newcomer, with a tiny project started on this library, I'm fully behind removing all deprecated code and moving forward!


GH-4014 handle function over var declared in group by

GitHub issue resolved: #4014
Briefly describe the changes proposed in this PR:

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

@damyan-ognyanov I think this should work for you.


Add anisotropy factors to points

Description
This PR closes #480 by introducing an anisotropy keyword arg to the Points layer and making the points sizes a 1-D array to resolve potential broadcasting ambiguity. The anisotropy factor is global for the layer (i.e. applies to all Points), but I think that is a good abstraction.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

How has this been tested?

[x] added anisotropy test to test_points.py

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

Thanks for catching this stuff, I've never been so good with the typing stuff. As noted above we'll have to go through the repo some time and type everything, but for now there's no point in making it worse by having the wrong types!!!

Hmm ok @jni I share your concern that anisotropy is a bad keyword argument as not as many people will know it.
Also - scale is already used as a keyword argument, it's used as a keyword argument for every layer, but it will be applied to the entire layer, not just the radii, i.e. if you have a point at [50, 50] with radii [10, 10] and apply scale [2, 2] it will move your point to [100, 100] and the radii will now be [20, 20]. This is desirable for some things, but different then rescaling the size of the just the radii.
Alternative proposal (as @jni posted on the issue) - how about we just keep the size keyword argument and force it to be broadcastable into data.shape (N, D)? So a scalar ->(N, D), vector of shape (D,) -> (N, D), vector of shape (N,) -> crashes, (N, 1) -> (N, D), (1, D) -> (N, D), and (N, D) -> (N, D).
The one thing I don't like about this is I feel that a lot of the time people will just have a length N list of sizes and a length D list of scale factors, but then maybe they just combine them ahead of time. This option is also strictly more general as it allows for different points to have different anisotropy.

i.e. if you have a point at [50, 50] with radii [10, 10] and apply scale [2, 2] it will move your point to [100, 100] and the radii will now be [20, 20].

fwiw I'm not positive this is the correct behaviour... If I give you coordinates at [50, 50], I can mean two things:

these are pixel coordinates, and therefore don't move them
these are data coordinates, in which case, with scale [2, 2], you should move them to [25, 25] in pixel space, not [100, 100]?

But, the problem remains: how can we adjust radii and coordinates independently?
I kinda sorta like your broadcasting idea, but I agree with you that it's not very user-friendly. Additionally, maybe this should be the time where we separate data from display. imho, points should not have a "size", as they are points. =) However, they can have a "value". Then, the UI can display that value as a size property or as a colormapped color, for example. So, a suggestion for a deeper refactor:

points have two attributes, coordinates and values. Coordinates have a fixed dimensionality, but values can be (N, F), where F is the "number of features" and can be arbitrary
in the UI or programmatically, you can map those values to attributes such as size, color, or shape (for categorical values).
we support providing feature names either by making values a pandas dataframe or by a separate "feature_names" kwarg that takes in a list of strings.

Thoughts?

I'll have to sleep on this one. Maybe we'll table this till after the 0.2.0 release. Colo rmapping with a value would be nice too though ...

@kevinyamauchi i wonder if we should revisit this and close #480 in a new PR before the 0.3.0 release? Now that we have the properties dictionary there are more options available to us for mapping values to size

Is this PR still something to work on, or can it be closed @sofroniewn?
Thanks!

I think we can probably close this PR as we don't need to use this approach, but we still probably want to address #480 as that is a real issue. I think @jni might have better ideas for how to do this now too (thinking about what we decided to do for the labels painting anistropicaly too). I'm not sure though


tsconfig.json completely ignored in Visual Studio 2015 (Update 3) Typescript > 1.7

TypeScript Version:  1.8.0 and 2.0 RC
My tsconfig
{
  "compilerOptions": {
    "noImplicitAny": false,
    "noEmitOnError": true,
    "removeComments": false,
    "sourceMap": true,
    "target": "es5",
    "outDir": "./Scripts"
  },
  "exclude": [
    "node_modules"
  ]
}

I tried already different settings in the file - but nothing works.
My Solution structure:

SharePoint 2013 App Project template
Dev.-Env.: SharePoint 2013 on-prem. / Visual Studio 2015 (Update 3)
OS: Windows Server 2012 R2

I've tried TypeScript 1.8 and 2.0 RC. Both are not working correct in Visual Studio 2015. As soon if I add a tsconfig file to the project root, the typescript file will not be compiled (transpiled - no js file). When I move the tsconfig file in a different directory, the TS-file will be compiled but without the defined settings in the tsconfig.
I've checked the PATH to the TypeScript Installation folder and everything is correct.
Also I missing the TypeScript configuration section within the project properties. I've only:

Application
Build
Build Events
Debug
Resources
Reference Paths
Signing
SharePoint
Code Analysis

Any help would be great!

Do you have an import to the TypeScript targets in your project file? Can you share the project file? or at least a build log with /verbosity: diagnostic

Have you inspected your csproj file? Could be that the msbuild TypeScript
directives are missing or incorrect. At least this was the case at some
point in the time in the past. OOTB there was no support for TypeScript
embedded in the template. You can diagnose yourself by creating a project
with the TypeScript project template and then compare the generated csproj
with the other one. Take special notice of a possible enforcement of a
specific TypeScript version.
2016-09-15 21:52 GMT+02:00 Mohamed Hegazy<EMAIL_ADDRESS>
Do you have an import to the TypeScript targets in your project file? Can
you share the project file? or at least a build log with /verbosity:
diagnostic
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/TypeScript/issues/10891#issuecomment-247434009,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF6MJIzn_2EjDW3T-Y9jmKh_Gez2RAULks5qqaIKgaJpZM4J7VTr
.

Please reopen if this is still an issue and you have more information.

If someone stumbles upon issue and can't figure why VS is not picking up your tsconfig.json: make sure your tsconfig.json's build action is set to Content (select the file, go to Properties and check Build Action).

I'm having the same problem, but I'm in a Visual Studio Website project, not a Web Application project, so there is no .csproj file.

@jpmnteiro you are my hero... thank you so much for this small but invaluable detail. Worked like a charm.

@jpmnteiro - champion!
@mhegazy it is something you guys need to get fixed. There is no indication why tsconfig.json isn't being read.


Implemented message-throttling and minor fixes.

@maf0115 Hey, since I need these features running for the sim-test on Thursday, please consider theses changes.

Many thanks for your suggestions @di-math . I was in the process of writing a parser which wouold have parsed each log message and sent every xth message, excluding the ones characterized by a pseverity level above 'INFO'. I was doing this because I thougth that it wouldn't have been a good idea to use the time (Python) module, since there is no global time. Guess I was wrong

You're right, there is no global time in distributed system. But locally we can rely on our clock.


Composite storage optimization

Hm, there are of course tests for the storage configuration, which need to be adapted.

Hm, there are of course tests for the storage configuration, which need to be adapted.

True, I just finished doing that 😀


chore: load helper images during cluster creation

We were creating loading the helper images only when running in a local
run, this wasn't considering when running in the E2E tests, this will
fix that by loading the helper images during the cluster creation.
Closes #652
Signed-off-by: Jonathan Gonzalez V<EMAIL_ADDRESS>

/test

/test

/test

/ok-to-merge


Fix validation error overlap on field hint in application creation

Issue
https://github.com/gravitee-io/issues/issues/6605
Description
Fix validation error overlap on field hint in application creation
Before:

After:

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.


[FEATURE REQUEST] Change Payee for a Group of Selected Transactions

Is your feature request related to a problem? Please describe.
For example, I have a number of transactions that are labeled Mobile Deposit.
Most of them but NOT all of them are from the same employer. It would be a time saver to take my years worth of Mobile Deposits and assign them accordingly in order to make my past and present reports more meaningful.
Describe the solution you'd like
The ability change Payee for a group of selected transactions
Describe alternatives you've considered
Changing them one at a time.
Using Manage Payee's to combine or change the name, but this would change all of my Mobile Deposits regardless of the ones selected or not.

I agree this would be helpful!

+feature

We use Trello to track Feature Requests so that users can vote on what they'd like to see next. This is crucial for us since there are so many requests and so little time amongst those of us who work on the Toolkit.
Your feature request has been added here and will need to be manually sorted.
This issue can now be closed.

The opened Trello is actually a duplicate of https://trello.com/c/0LkDJsHX which will be used instead.


User feedback

Below is user feedback via Slack. Posting it here so it doesn't get lost with Slack message rollover
StackStorm's New Workflows
Unit Testing
Currently, in my opinion, the biggest downfall of Mistral is the lack of unit
testing around workflows. Without unit testing we're relying on smoke testing to
ensure these workflows behave properly (not very effective or maintainable).
Things we would like to test in a workflow include:

Task execution yes/no
Task execution order
Error handling
Publish expressions (Jinja, YAQL)
Transition expressions (Jinja, YAQL)
Workflow inputs and outputs

I think this would require some sort of ability to mock action output so that
these things can be tested.
Publish and reuse in same task
Currently, in Mistral, all of the publish and publish-on-error statements
occur in bulk meaning i can't reuse one of the variables published in the
current task until the next task is executed.
Example:
task1:
  action: core.local
  input:
    cmd: "echo hello"
  publish:
    output: "{{ task('task1').result.stdout }}"
    # this errors out because output isn't available in the contex yet
    hello_world: "{{ _.output + ' world' }}"

Maybe converting the publish statement to an array would make it easier
to execute in sequence?
task1:
  action: core.local
  input:
    cmd: "echo hello"
  publish:
    - output: "{{ task('task1').result.stdout }}"
    # output should now be available in the current context, so the following
    # should work
    - hello_world: "{{ _.output + ' world' }}"

When condition on a task level
Sometimes it's necessary to skip a task given a condition. Currently we have to
work around this by adding this "skip" condition into every on-success statement
in the workflow that may call our task. This is a maintenance burdem.
Ansible example:
- name: install stackstorm pack
  shell:
    cmd: "st2 pack install {{ st2_pack }}"
  when: st2_pack is defined

Mistral example (current implementation):
input:
  - servicenow_provision_id: null

task_1:
  action: std.noop
  publish:
    last_task: "task_1"
  on-success:
    - task_servicenow_update: "{{ _.servicenow_provision_id }}"
    - task_2

task_2:
  action: std.noop
  publish:
    last_task: "task_2"
  on-success:
    - task_servicenow_update: "{{ _.servicenow_provision_id }}"

task_servicenow_update:
  action: encore_servicenow.provision_state_update
  input:
    provision_id: "{{ _.servicenow_provision_id }}"
    current_state: "{{ _.last_task }}"

Mistral example using a when condition on task_servicenow_update task:
input:
  - servicenow_provision_id: null

task_1:
  action: std.noop
  publish:
    last_task: "task_1"
  on-success:
    - task_servicenow_update
    - task_2

task_2:
  action: std.noop
  publish:
    last_task: "task_2"
  on-success:
    - task_servicenow_update

task_servicenow_update:
  action: encore_servicenow.provision_state_update
  when: "{{ _.servicenow_provision_id }}"
  input:
    provision_id: "{{ _.servicenow_provision_id }}"
    current_state: "{{ _.last_task }}"

"Main" task / entry-point
There are many occasions on Slack where users of Mistral are confused by its
default execution behavior. People usually forget to tie tasks together with
explicit on-success, on-error, or on-complete statements, causing tasks
to be run in parallel resulting in odd and unpredictable behaviors.
It might be better to explicity define a "main" or "entry-point" in the workflow.
description: My entry-point workflow
input:
  - x
  - y
  - z

# the tasks that should be executed as "roots"
# this can either be a string, or a list so that >1 can be executed in parallel?
entry-point: my_first_task

tasks:
  my_first_task:
    action: std.noop
    on-success:
      - some_other_task

  some_other_task:
    action: std.noop

Linear execution by default
On the same lines as the last point about "main tasks" people new to Mistral are
often confused by the non-linearity as the default operating state of the
workflow engine.
Maybe as an alternative to the "main task" idea above, workflows could be executed
linearly and in parallel/DAG-optimized using an option. I'm going to
suggest a workflow parameter called execution_model. The execution_model
with a value of linear means that tasks are executed in order just like an
actionchain or Ansible. Another implementation could be the parallel execution
model that will switch it over to a Mistral-like parallel execution by creating
a DAG and  executing as much in parallel as possible.
description: >
  My linear workflow, all of these are executed in order
  without the need for on-success.
execution_model: linear

tasks:
  task_0:
    action: std.noop

  task_1:
    action: std.noop

  task_2:
    action: std.noop

description: >
  Parallel execution model tries to do as much in parallel as possible, requires
  on-success and on-error to construct our DAG.
execution_model: parallel

tasks:
  task_0:
    action: std.noop
    on-success:
      - task_1

  task_1:
    action: std.noop
    on-success:
      - task_2
      - task_3

  task_2:
    action: std.noop

  task_3:
    action: std.noop

Keep: defined inputs and output
We really like having the inputs and outputs sections explicity defined.
Please keep these!
Keep: allowed temporaries in workflow
We currently use (and maybe abuse) the ability of having input values defined
in the workflow that are not present in the parameters of the action itself.
These are mostly used as temporary variables that are local to the workflow

Perhaps the execution models are defined not by an execution_model key, but by the data type of tasks.  If it's a hash/dict it should use parallel execution and tasks must be explicitly linked together with next sections.
Defining an entry-point in the workflow itself doesn't sound interesting to me, other than maybe as the default workflow entry-point. But, specifying the entry-point via a workflow input parameter would enable targeting pieces of workflows. Sure, someone could split their workflows into additional workflows to be able to select just a few tasks in the workflow. But, if a few tasks break in a workflow, and the rest of the (ran in parallel tasks) completed, it would be nice to re-run just the branch of the task graph that failed. Maybe I forgot to add a key to the key-value store, or a github was down when that task ran, or ... Re-run with a target entry-point would be fantastic.

:+1: to publish as a list.

:+1: to publish as a list
I can't tell you how many times I've tried this:
  publish:
    output: "{{ task('task1').result.stdout }}"
    # this errors out because output isn't available in the contex yet
    hello_world: "{{ _.output + ' world' }}"

and then done approximately this:
    publish:
      output: "{{ task('task1').result.stdout }}"
    do: finish_publishing
finish_publishing
  action: noop
  next:
    publish:
      # this errors out because output isn't available in the contex yet
      hello_world: "{{ _.output + ' world' }}"

:+1: to when conditions
:100: for Orchestra ;)

We will close this issue here as this is for general user feedback during alpha/beta.  If there are specific feature request or problem with orquesta, please open a separate issue for each.


Discord @ mentions using the wrong name in IRC

Describe the bug
When somebody on Discord mentions another user using @, and that user is using a server-specific name different from their global Discord username, the @ mention in IRC shows up as the global username in stead of the server-specific name.
In other cases the correct name is displayed. Also using @ with the server-specific name from IRC seems to work fine.
To Reproduce
Have a Discord server bridged to IRC. Change your nickname in the server profile for the bridged server on Discord to something different from your global Discord username. Have somebody @ mention the server-specific name on Discord. Check what it appears as on IRC.
Expected behavior
It should show up on IRC as the server-specific name, like normal messages do.
Screenshots/debug logs

20220501 16:20:44<+wDiscord> [Vultraz] @Yobbo Cake something else to consider probably soon is we want draw events to happen every frame
Environment (please complete the following information):

OS: linux
Matterbridge version: 1.23.0 55f41dda

Additional context

https://github.com/42wim/matterbridge/wiki/Settings#useusername
Wouldn't setting UseUserName=false do what you want?

Word of advice, though: anyone using whack-ass characters in their name means their messages won't come across. StripNick can help, but if someone's nickname on Discord is only whack-ass unicode characters, then their messages will never go to IRC.

We tried the UseUserName=false setting, but apparently that's already the default so it didn't help. The server nicks are correctly used when the bot translates messages, just not when translating mentions specifically.
When we set it to true, it used the global name for all messages as well as mentions. So it seems like it should come under the same setting, just it isn't currently applied in this case.


CriticalCSS plugin prints error message when trying to process image files

🐞 Bug report
Description
When using the @scullyio/scully-plugin-critical-css plugin, the plugin does not automatically ignore image files and will instead error out and print an error message to the console during Scully build. The plugin handler is skipped so this does not result in build failure, but the generated error messages are noise in the console.
The ideal behaviour here would be to not print anything to the console and just skip the image file without an error.
Also, I believe there is a typo in the error message, the word "handler" is misspelled as "hander" (see exact error message in "🔥 Exception or Error" section below).
🔬 Minimal Reproduction
Any Scully project using the @scullyio/scully-plugin-critical-css plugin in defaultPostRenderers of the Scully config with a fileHandler plugin registered e.g. registerPlugin('fileHandler', 'png', imageFilePlugin);.
💻Your Environment
Angular Version:

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 11.0.5
Node: 14.8.0
OS: darwin x64

Angular: 11.0.5
... animations, cli, common, compiler, compiler-cli, core
... elements, forms, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1100.5
@angular-devkit/build-angular   0.1100.5
@angular-devkit/core            11.0.5
@angular-devkit/schematics      11.0.5
@angular/cdk                    11.0.3
@angular/material               11.0.3
@schematics/angular             11.0.5
@schematics/update              0.1100.5
rxjs                            6.6.3
typescript                      4.0.5

Scully Version:

"@scullyio/init": "^1.0.1"
"@scullyio/ng-lib": "^1.0.0"
"@scullyio/scully": "^1.0.0"
"@scullyio/scully-plugin-critical-css": "0.0.2"

🔥 Exception or Error

Error during content generation with plugin "criticalCss" for ./projects/website/blog-posts/images/banner.jpg. This hander is skipped.

The error is printed from inside of the Critical tool, and can't be prevented. (I looked into this)
We have an outstanding discussion (#1161) that would somewhat take care of this, but there isn't much we can do otherwise.
Closing this as there is nothing actionable for us now. If you know/find a way to handle this, we will reopen this issue

The error is printed from inside of the Critical tool, and can't be prevented. (I looked into this)
We have an outstanding discussion (#1161) that would somewhat take care of this, but there isn't much we can do otherwise.
Closing this as there is nothing actionable for us now. If you know/find a way to handle this, we will reopen this issue

@chriskinzel It just occurred to me that you can "fix" this in your config file.
somewhere in your config:
console.log = (...args) => {let [first,...rest]=args;  first = first typeof 'string' ? first.slice(0,40) : first; log(first,...rest)}
console.error = (...args) => {let [first,...rest]=args;  first = first typeof 'string' ? first.slice(0,40) : first; logError(first,...rest)}

Those will overwrite the global console log and error, and make them more in line with the rest of Scully output

@chriskinzel It just occurred to me that you can "fix" this in your config file.
somewhere in your config:
console.log = (...args) => {let [first,...rest]=args;  first = first typeof 'string' ? first.slice(0,40) : first; log(first,...rest)}
console.error = (...args) => {let [first,...rest]=args;  first = first typeof 'string' ? first.slice(0,40) : first; logError(first,...rest)}

Those will overwrite the global console log and error, and make them more in line with the rest of Scully output


Get-LatestCumulativeUpdate not working for 1909

Expected Behavior
I should be able to get updates for Windows 10 1909
Current Behavior
Get-LatestCumulativeUpdate : Cannot validate argument on parameter 'Version'.
The " $_ -in $script:resourceStrings.ParameterValues.Windows10Versions "
validation script for the argument with value "1909" did not return a result
of True. Determine why the validation script failed, and then try the command
again.

1909 is not included in LatestUpdate.json, therefore it can't be mapped to a build number which we need to search the Update Feed.
Expected Behavior
It should not return an error
Steps to Reproduce
Get-LatestCumulativeUpdate -Version 1909

Potential Fixes
Let the Get-LatestCumulativeUpdate accept build number as a parameter as this can be used to search for the appropriate update in the Update Feed.

Microsoft changed the URL from http://download.windowsupdate.com to http://dl.delivery.mp.microsoft.com. Is therefore a download not possible?

The link is retrieved from the catalog. It's just sometimes that there's no url returned.
Also found that ordering on KB ID works better than sorting on the note.

@Fonta i'm with you but when you are executing Get-LatestServicingStackUpdates the script doesn't return any URL.

@kilianmeister Just saying that the change from MS shouldn't matter as the url is automatically retrieved. :)


[BUG] Not all tags automatically load from web instance of Shiori

Bug Description
If I open the android app and click on the filter icon at the top right, not all the tags show up in the slide-up card.
However, if I scroll through all the bookmarks before selecting the filter, then all the tags show up.
Steps to Reproduce
Steps to reproduce the behavior:

Close the app
Open the app and immediately tap the filter button in the top right-hand corner.
Observe that not all the tags show up.
Now close the filter and scroll to the bottom of all the bookmarks
Open up the filter again and you will see all of the tags appear

Expected Behavior
All the tags should appear when tapping the filter button, without needing to scroll through all the bookmarks.
Screenshots

Device Information

Brand and Model: Pixel 7
Android Version: Android 14
App Version: 1.30

Additional Context

That's a good point.
I think, from a user's perspective, if they have reached 6000 bookmarks, then tags would be pretty much the only way of navigating all of those bookmarks.
So, minimally, I think all the tags should be available offline. And then, when a tag is selected, the associated articles can be downloaded.

I can confirm that this is now working for me. Thank you!


Installer Success Callback

Description
In the Installer success callback I would like to add a link to the web version of my slack app. I tried using the same IDs that the link for the desktop app uses, but the web seems to go to a settings page for the app.
redirectAppUrl = `slack://app?team=${installation.team.id}&id=${installation.appId}`;  -- opens desktop in the right place
redirectWebUrl = `https://app.slack.com/client/${installation.team.id}/${installation.appId}`; -- opens web on settings page

Also, how can I get the name of the app that was just installed?  I would like to display the name of the app on the success page, but I can't hard code it because there are several versions for different environments..
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Hey @T-Roth,
I think your best bet is to use https://slack.com/app_redirect?app=${installation.appId}.
For finding out the name, I believe you have a installation.bot.id value you can use to call bots.info. bots.info returns a bot.name field you could use.

@stevengill thanks for the response, unfortunately I still have some issues.
https://slack.com/app_redirect?app=${installation.appId} works but it also prompts the user to open the desktop Slack and has a few seconds delay before navigating to the web version.   I wanted to have 2 buttons on my success page and let the user decide if they wanted to launch the desktop or web version.
I got bots.info() to work, but what I really wanted was the app name, since the bot name could be different.

Hey @T-Roth!
Sorry I realized I never responded to your last message. Did you manage to find a solution? I did dig around this problem and struggled to find the proper answer. I can take another dive if you are still stuck here.

So after the user successfully installs the app, we send them to this view letting them pick if they want the launch the desktop or web version of slack.
The desktop link works great. The web link they end up on the last channel/message they had selected.  <- this is where I can't seem to get the correct ID's to send them to the app they just installed

Hi @T-Roth, sorry for the late reply here but, in this scenario, utilizing slack://app?team={team_id}&id={app_id} may work for you.

Let us close this issue due to its inactivity. But please feel free to write in if you have something further!


Specifying columns to select causes Columns to be read-only in results grid

Description
When running a query and selecting specific columns, the results grid ends up in read-only mode, the user is unable to edit values in the grid.  Run the query as SELECT * allows the results grid to be editable.
DBeaver Version
<IP_ADDRESS>302060909
Operating System
macOS 13.2
Database and driver
PostgreSQL JDBC Driver
Steps to reproduce

Start a new query
run a SELECT * on any table, for example
SELECT *
FROM "AspNetUsers" anu
ORDER BY anu."UserName"
Modify the query to select specific columns and run again, for example
SELECT anu."Id", anu."UserName", anu."PhoneNumber", anu."DateCreated"
FROM "AspNetUsers" anu
ORDER BY anu."UserName"
Attempt to edit a column value in the results grid

All columns end up as read-only, the yellow lock icon shows up in top left of results grid.  The error when attempting to edit a column comes back as Column is read-only: No corresponding table column.

Additional context
Adding as a new bug per request in issue #17724. Also as was requested previously see attached for the DDL from the table shown in example.
AspNetUsers DDL.txt

Thank you for bug report.
The issue is reproducible only if the column names are in quotes.

But the quotes are necessary, otherwise Postgres will interrupt Id as id, which then causes an Error Column does not exist.  So omitting the quotes only works when working with a table were the column names are using all lowercase, which isn't typically the case in my experience.

I know. I just highlights an important point to reproduce the issue.


Revive

Coverage increased (+0.3%) to 99.616% when pulling 23bbe003e38e41b64a6e0a539725507251858538 on revive into c13ed13a51ba8ddaedb8b2d09f0441cb6f7498b9 on master.

Coverage increased (+0.3%) to 99.616% when pulling 23bbe003e38e41b64a6e0a539725507251858538 on revive into c13ed13a51ba8ddaedb8b2d09f0441cb6f7498b9 on master.

Coverage increased (+0.3%) to 99.616% when pulling 23bbe003e38e41b64a6e0a539725507251858538 on revive into c13ed13a51ba8ddaedb8b2d09f0441cb6f7498b9 on master.

Coverage increased (+0.3%) to 99.616% when pulling 23bbe003e38e41b64a6e0a539725507251858538 on revive into c13ed13a51ba8ddaedb8b2d09f0441cb6f7498b9 on master.


BIOS download issues HP and Dell

Hi
I'm unable to download HP BIOS packages because the tool cannot reach the URL. I'm guessing the tool get's an old cab list which does not work anymore. Can this be fixed please? The new URLs are using https because ftp over http is deprecated if I recall correctly.

I'm also experiencing issues to download Dell BIOS packages. As soon as you download a second BIOS package, it fails on the flash tool. I think this has been posted a few times already, but I just want to let you know it is still an issue.
Kind regards

I can into something similar, so I tried wget http://ftp.hp.com/pubs/......cab in a PS console. I got an error about IE and not having done first-launch.

I used this command to disable the first launch check via Registry, and was able to test with wget successfully.
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Internet Explorer\Main" -Name "DisableFirstRunCustomize" -Value 2
This appears to have fixed my download issue.
Maybe a change to the Invoke-WebRequest method to add the use -UseBasicParsing parameter would fix this reliance on the IE engine


This is an automated build for release 0.2.4
[x] website builds and runs in production - for information on how to test locally go here.

Description

Docs generated for Release 0.2.4
Related Issues

#issue-number

I configured the website locally and see the following are correct:

the 'S' in macOS is capitalized.
All 16 'Auto generated by' lines are removed
the --name flag is added for appsody stop

The formatting appeared correct and the links function.


Okay to include PEER covariants?

Hi Graham,
The final combined_test.py can take principle components into account. Would it be okay to use PEER factors, age, gender and other covariates?
Bosh

In principle this should work, but I have not tried this myself. I have also not tested the PC option of the CHT for a long time, so let us know if you try this and run into any problems.

Since the coefficients are fit one at a time, it would likely work better
if the covariates are orthogonal (as PCs are ).  I might suggest
orthogonalizing the covariate matrix (perhaps using PCA).
On Mon, Oct 10, 2016 at 2:28 PM, Graham McVicker<EMAIL_ADDRESS>wrote:

In principle this should work, but I have not tried this myself. I have
also not tested the PC option of the CHT for a long time, so let us know if
you try this and run into any problems.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bmvdgeijn/WASP/issues/55#issuecomment-252701518, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADSDguM89IN11l4qstjEiWbrjNfmTp7Pks5qyoPCgaJpZM4KSJx2
.


"ValueError: axes don't match array" in sample_segmentation_pairs_d.py

Thank you for sharing synthseg.
To train the denoiser in synthseg+,  I'm working on sample_segmentation_pairs_d.py, however, it returns "ValueError: axes don't match array". Here is the way the error is reproduced.
Environment: requirements_python3.6.txt

Prepare image/lanel dataset by running scripts/tutorials/1-generation_visualisation.py

cd Synthseg/scripts/tutorials/
python 1-generation_visualisation.py

Reproduce error by runinng following code.

from SynthSeg.sample_segmentation_pairs_d import sample_segmentation_pairs

image_dir = './outputs_tutorial_1/image/image.nii.gz'
labels_dir = './outputs_tutorial_1/labels/labels.nii.gz'
results_dir = './outputs_tutorial_1/sample_seg_pair'
n_examples = 1
path_model = "../../models/synthseg_1.0.h5"
segmentation_labels = "../../data/labels_classes_priors/generation_labels.npy"

if __name__ == "__main__":
    sample_segmentation_pairs(
        image_dir=image_dir,
        labels_dir=labels_dir,
        results_dir=results_dir,
        n_examples=n_examples,
        path_model=path_model,
        segmentation_labels=segmentation_labels,
        n_neutral_labels=18, # n_neutral_labels=None,
        batchsize=1,
        flipping=True,
        scaling_bounds=.15,
        rotation_bounds=15,
        shearing_bounds=.012,
        translation_bounds=False,
        nonlin_std=3.,
        nonlin_scale=.04,
        min_res=1.,
        max_res_iso=4.,
        max_res_aniso=8.,
        noise_std_lr=3.,
        blur_range=1.03,
        bias_field_std=.5,
        bias_scale=.025,
        noise_std=10,
        gamma_std=.5)

This eventually return the error.

2023-01-28 11:42:52.894375: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2023-01-28 11:42:52.944030: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x7fee3e57bb80 executing computations on platform Host. Devices:
2023-01-28 11:42:52.944090: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): Host, Default Version
Using TensorFlow backend.
Traceback (most recent call last):
  File "7-test-degradation_error.py", line 37, in <module>
    gamma_std=.5)
  File "/Users/chiba/Github/SynthSeg/SynthSeg/sample_segmentation_pairs_d_error.py", line 205, in sample_segmentation_pairs
    generation_model.load_weights(path_model, by_name=True)
  File "/Users/chiba/anaconda3/envs/synthseg_env3.6/lib/python3.6/site-packages/keras/engine/saving.py", line 492, in load_wrapper
    return load_function(*args, **kwargs)
  File "/Users/chiba/anaconda3/envs/synthseg_env3.6/lib/python3.6/site-packages/keras/engine/network.py", line 1227, in load_weights
    reshape=reshape)
  File "/Users/chiba/anaconda3/envs/synthseg_env3.6/lib/python3.6/site-packages/keras/engine/saving.py", line 1294, in load_weights_from_hdf5_group_by_name
    reshape=reshape)
  File "/Users/chiba/anaconda3/envs/synthseg_env3.6/lib/python3.6/site-packages/keras/engine/saving.py", line 980, in preprocess_weights_for_loading
    weights[0] = np.transpose(weights[0], (3, 2, 0, 1))
  File "<__array_function__ internals>", line 6, in transpose
  File "/Users/chiba/anaconda3/envs/synthseg_env3.6/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 651, in transpose
    return _wrapfunc(a, 'transpose', axes)
  File "/Users/chiba/anaconda3/envs/synthseg_env3.6/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 61, in _wrapfunc
    return bound(*args, **kwds)
ValueError: axes don't match array

Hi,
so if you want to run sample_segmentation_pairs with path_model = "../../models/synthseg_1.0.h5", then you would need the corresponding segmentation label list, which is located under SynthSeg/data/labels_classes_priors/synthseg_segmentation_labels.npy.
But I strongly suggest that you use real images as inputs to sample_segmentation_pairs, because SynthSeg will be very good on synthetic data, so the sampled segmentations will be pretty good. This is bad because those segmentations will utlimately be used to train D, and you need D to be exposed to bad segmentations, such that it knows how to deal with them at test time.
More generally, note that I wrote tutorial 7, just to explain the mechanism of training SynthSeg+, so it's kind of a "sand-box" for users to experiment ;)
Hope this helps
Benjamin

Thanks!
When I fixed the code as mentioned and ran, I encountered following errors...
Please note that I tried two environments; with and without GPU machine.
This eventually returns the different errors.
(Could be my typo between machines, of course I double checked)
As below, do you think the code can load the corresponding segmentation labels with GPU,
and the issue is Out of memory?

Environment 1:
macOS Monterey
Intel CPU (without GPU)
NOTE: Same machine in previous comments.

Error:  ValueError: axes don't match array
2023-03-05 11:50:15.595083: I tensorflow/core/platform/cpu_feature_guard.cc:143] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2023-03-05 11:50:15.614121: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x7f78314d21e0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2023-03-05 11:50:15.614158: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
Using TensorFlow backend.
Traceback (most recent call last):
  File "7-test-degradation.py", line 28, in <module>
    sample_segmentation_pairs(
  File "/Users/chiba/Github/SynthSeg/SynthSeg/sample_segmentation_pairs_d_dev.py", line 205, in sample_segmentation_pairs
    generation_model.load_weights(path_model, by_name=True)
  File "/Users/chiba/anaconda3/envs/synthseg_env/lib/python3.8/site-packages/keras/engine/saving.py", line 492, in load_wrapper
    return load_function(*args, **kwargs)
  File "/Users/chiba/anaconda3/envs/synthseg_env/lib/python3.8/site-packages/keras/engine/network.py", line 1225, in load_weights
    saving.load_weights_from_hdf5_group_by_name(
  File "/Users/chiba/anaconda3/envs/synthseg_env/lib/python3.8/site-packages/keras/engine/saving.py", line 1289, in load_weights_from_hdf5_group_by_name
    weight_values = preprocess_weights_for_loading(
  File "/Users/chiba/anaconda3/envs/synthseg_env/lib/python3.8/site-packages/keras/engine/saving.py", line 980, in preprocess_weights_for_loading
    weights[0] = np.transpose(weights[0], (3, 2, 0, 1))
  File "<__array_function__ internals>", line 5, in transpose
  File "/Users/chiba/anaconda3/envs/synthseg_env/lib/python3.8/site-packages/numpy/core/fromnumeric.py", line 651, in transpose
    return _wrapfunc(a, 'transpose', axes)
  File "/Users/chiba/anaconda3/envs/synthseg_env/lib/python3.8/site-packages/numpy/core/fromnumeric.py", line 61, in _wrapfunc
    return bound(*args, **kwds)
ValueError: axes don't match array

Environment 2:
AWS g4dn.xlarge
GPU: Tesla T4

Error:  Out of memory
2023-03-05 02:12:07.126992: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2023-03-05 02:12:07.184541: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.185136: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:00:1e.0 name: Tesla T4 computeCapability: 7.5
coreClock: 1.59GHz coreCount: 40 deviceMemorySize: 14.75GiB deviceMemoryBandwidth: 298.08GiB/s
2023-03-05 02:12:07.185427: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2023-03-05 02:12:07.187318: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2023-03-05 02:12:07.188457: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10
2023-03-05 02:12:07.188786: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10
2023-03-05 02:12:07.190725: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10
2023-03-05 02:12:07.191829: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10
2023-03-05 02:12:07.195805: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2023-03-05 02:12:07.195947: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.196562: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.197081: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2023-03-05 02:12:07.197342: I tensorflow/core/platform/cpu_feature_guard.cc:143] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 AVX512F FMA
2023-03-05 02:12:07.222530: I tensorflow/core/platform/profile_utils/cpu_utils.cc:102] CPU Frequency:<PHONE_NUMBER> Hz
2023-03-05 02:12:07.222841: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x7f9124000b60 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2023-03-05 02:12:07.222868: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2023-03-05 02:12:07.325551: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.326210: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x3ef01c0 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2023-03-05 02:12:07.326241: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Tesla T4, Compute Capability 7.5
2023-03-05 02:12:07.326510: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.327086: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:00:1e.0 name: Tesla T4 computeCapability: 7.5
coreClock: 1.59GHz coreCount: 40 deviceMemorySize: 14.75GiB deviceMemoryBandwidth: 298.08GiB/s
2023-03-05 02:12:07.327168: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2023-03-05 02:12:07.327190: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2023-03-05 02:12:07.327223: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10
2023-03-05 02:12:07.327243: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10
2023-03-05 02:12:07.327262: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10
2023-03-05 02:12:07.327280: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10
2023-03-05 02:12:07.327300: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2023-03-05 02:12:07.327383: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.327974: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.328513: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2023-03-05 02:12:07.328589: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2023-03-05 02:12:07.329305: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102] Device interconnect StreamExecutor with strength 1 edge matrix:
2023-03-05 02:12:07.329328: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1108]      0
2023-03-05 02:12:07.329338: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1121] 0:   N
2023-03-05 02:12:07.329477: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.330102: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-03-05 02:12:07.330701: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1247] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 14109 MB memory) -> physical GPU (device: 0, name: Tesla T4, pci bus id: 0000:00:1e.0, compute capability: 7.5)
2023-03-05 02:12:22.282408: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2023-03-05 02:12:24.203807: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2023-03-05 02:12:41.775504: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 1.52GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available.
2023-03-05 02:12:41.775580: W tensorflow/core/kernels/gpu_utils.cc:49] Failed to allocate memory for convolution redzone checking; skipping this check. This is benign and only means that we won't check cudnn for out-of-bounds reads and writes. This message will only be printed once.
2023-03-05 02:12:48.380029: W tensorflow/core/framework/cpu_allocator_impl.cc:81] Allocation of<PHONE_NUMBER> exceeds 10% of free system memory.
2023-03-05 02:13:00.496689: W tensorflow/core/framework/cpu_allocator_impl.cc:81] Allocation of<PHONE_NUMBER> exceeds 10% of free system memory.

-> Eventually process kept running more than 10hours that I finally terminated. There were no output...

Thank you for comment!
Here is the code I ran.
Both environments installed the python3.8.
It could be relevance to other mentions as #49.
I will try the followings;

Cropping inout file

from SynthSeg.sample_segmentation_pairs_d import sample_segmentation_pairs

image_dir = './outputs_tutorial_1/image.nii.gz'
labels_dir = './outputs_tutorial_1/labels.nii.gz'
results_dir = './outputs_tutorial_1/sample_seg_pair'
n_examples = 1
path_model = "../../models/synthseg_1.0.h5"
# segmentation_labels = "../../data/labels_classes_priors/generation_labels.npy"
segmentation_labels = "../../data/labels_classes_priors/synthseg_segmentation_labels.npy"

if __name__ == "__main__":
    sample_segmentation_pairs(
        image_dir=image_dir,
        labels_dir=labels_dir,
        results_dir=results_dir,
        n_examples=n_examples,
        path_model=path_model,
        segmentation_labels=segmentation_labels,
        n_neutral_labels=18,
        batchsize=1,
        flipping=True,
        scaling_bounds=.15,
        rotation_bounds=15,
        shearing_bounds=.012,
        translation_bounds=False,
        nonlin_std=3.,
        nonlin_scale=.04,
        min_res=1.,
        max_res_iso=4.,
        max_res_aniso=8.,
        noise_std_lr=3.,
        blur_range=1.03,
        bias_field_std=.5,
        bias_scale=.025,
        noise_std=10,
        gamma_std=.5)

the issue should be fixed now :)
two remarks though:

if you're using synthseg_1.0.h5, I would strongly recommend you tune down the augmentation, because it is less robust than synthseg 2.0. Another solution si to use synthseg 2.0:
path_model = "../../models/synthseg_2.0.h5"
segmentation_labels = "../../data/labels_classes_priors/synthseg_segmentation_labels_2.0.npy"
n_neutral_labels = 19

note that this script will give you segmentations with the label values of synthseg (ie.e for around 30 structures). However, these are probably note the labels that you want, since the training data for D should match the label values given by S1, which are typically way fewer (ie around 5).

Thanks!

I tried your comment as following code on my macOS (CPU),
and it resulted in the same error; Error: ValueError: axes don't match array.
This happened in both of python 3.6 and 3.8.

It makes sense. So when I run sample_segmentation_pairs for the degradation of S1 images, should I set the value n_neutral_labels = 5, segmentation_labels = np.array([0, 1, 2, 3, 4]), and labels_dir = [label images predicted by S1]?

Code;
from SynthSeg.sample_segmentation_pairs_d import sample_segmentation_pairs

image_dir = './outputs_tutorial_1/image.nii.gz'
labels_dir = './outputs_tutorial_1/labels.nii.gz'
results_dir = './outputs_tutorial_1/sample_seg_pair'
n_examples = 1

# path_model = "../../models/synthseg_1.0.h5"
path_model = "../../models/synthseg_2.0.h5"

# segmentation_labels = "../../data/labels_classes_priors/synthseg_segmentation_labels.npy"
segmentation_labels = "../../data/labels_classes_priors/synthseg_segmentation_labels_2.0.npy"

n_neutral_labels = 19  #18

if __name__ == "__main__":
    sample_segmentation_pairs(
        image_dir=image_dir,
        labels_dir=labels_dir,
        results_dir=results_dir,
        n_examples=n_examples,
        path_model=path_model,
        segmentation_labels=segmentation_labels,
        n_neutral_labels=n_neutral_labels,
        batchsize=1,
        flipping=True,
        scaling_bounds=.15,
        rotation_bounds=15,
        shearing_bounds=.012,
        translation_bounds=False,
        nonlin_std=3.,
        nonlin_scale=.04,
        min_res=1.,
        max_res_iso=4.,
        max_res_aniso=8.,
        noise_std_lr=3.,
        blur_range=1.03,
        bias_field_std=.5,
        bias_scale=.025,
        noise_std=10,
        gamma_std=.5)

Error;
Using TensorFlow backend.
2023-03-10 23:36:07.328249: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2023-03-10 23:36:07.386534: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x7fa1a2e552d0 executing computations on platform Host. Devices:
2023-03-10 23:36:07.386562: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): Host, Default Version
Traceback (most recent call last):
  File "7-test-degradation.py", line 59, in <module>
    gamma_std=.5)
  File "/Users/chiba/Github/SynthSeg/SynthSeg/sample_segmentation_pairs_d.py", line 205, in sample_segmentation_pairs
    generation_model.load_weights(path_model, by_name=True)
  File "/Users/chiba/anaconda3/envs/synthseg36/lib/python3.6/site-packages/keras/engine/saving.py", line 492, in load_wrapper
    return load_function(*args, **kwargs)
  File "/Users/chiba/anaconda3/envs/synthseg36/lib/python3.6/site-packages/keras/engine/network.py", line 1227, in load_weights
    reshape=reshape)
  File "/Users/chiba/anaconda3/envs/synthseg36/lib/python3.6/site-packages/keras/engine/saving.py", line 1294, in load_weights_from_hdf5_group_by_name
    reshape=reshape)
  File "/Users/chiba/anaconda3/envs/synthseg36/lib/python3.6/site-packages/keras/engine/saving.py", line 980, in preprocess_weights_for_loading
    weights[0] = np.transpose(weights[0], (3, 2, 0, 1))
  File "<__array_function__ internals>", line 6, in transpose
  File "/Users/chiba/anaconda3/envs/synthseg36/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 651, in transpose
    return _wrapfunc(a, 'transpose', axes)
  File "/Users/chiba/anaconda3/envs/synthseg36/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 61, in _wrapfunc
    return bound(*args, **kwds)
ValueError: axes don't match array

It worked! Thank you very much!
Sorry, I missed the commits.
It worked with my own trained S1 network and real images either by pulling the current commit
or by setting n_labels = np.size(np.unique(segmentation_labels) in the previous commit.
Yes, I understand why the real images should be used.
I will try to prepare an enough amount of sample segmentation pairs and to train the denoiser.
Thank you!

Sorry, but you also need to implement the other change of the commit https://github.com/BBillot/SynthSeg/commit/7f239508d77f17f23fa05a0d5fe1972c931890a6
In other words, please also delete lines 203->206 from SynthSeg/sample_segmentation_pairs_d.py:
        nn = np.sum(np.squeeze(outputs[1]).argmax(-1) > 0)
        if (nn > 500000) | (nn < 10000):
            continue

Thank you. Apologies for the late reply. I was on vacation.
By pulling the latest version, I generated the sample segmentation pairs for 1,000 pairs and started the training of denoiser. Thank you very much!
This is a minor question: Should I use all sample segmentation pairs generated by sample_segmentation_pairs.py or pick them up with the appropriate quality?
Because there are a variety of noisy labels in the labels_seg folder. In extreme cases, the entire image is filled with noise.

Thank you! I understand why the denoiser needs to learn the good and bad segmentations.
That's helpful, I will try managing the dataset imbalance.
Honestly, the prediction accuracy seems not good (denoising looks nice, but the segmentation doesn't) for my own dataset
yet the train step reaches only 16 epoch. This might be caused by the imbalance of sample segmentation pairs as mentioned (now the ratio is approximately 2:8 for good and bad segmentations).

May I ask once again about the denoiser?
Do you think the following images are correct to use for training of denoiser? Input & output images were generated by ‘sample_seg_pairs.py’, and the predicted image was done by ‘predict_denoiser.py’. As mentioned, there are roughly two types of image pairs, NOISEY and LESS NOISY. The denoiser was trained by a dataset consisting of 10 pairs of each NOISEY and LESS NOISY, for a total of 20 pairs during 10 epochs.

NOISY

LESS NOISY


SDK 19 doesn't support runtime permissions

Hello folks,
I am getting a
Performing Streamed Install
adb: failed to install tmp\LegacyWhatsApp.apk: Failure [-26: Package com.whatsapp new target SDK 19 doesn't support runtime permissions but the old target SDK 31 does.]

on WhatsApp-Key-DB-Extractor-master with Android 12 (Realme RMX3393).
Using the WhatsApp Messenger Version 2.11.431 APK file.
Any ideas how to cirumvent that or what else to try?

try running with --allow-reboot flag.


fix: ParamManager cannot provide default SSM & Secrets providers

Issue #, if available: #1280
Description of changes:

It was partially fixed in https://github.com/aws-powertools/powertools-lambda-java/commit/c7aedc4d2a61013450bf472bb7a8285f8cf80e41 with the addition of constructors with no client in parameter
Completed the fix, adding the creation of the Client
Deprecated the generic method to get Providers by passing a class (will be removed in V2)

Checklist

[x] Meet tenets criteria
[x] Update tests
[ ] Update docs
[x] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

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

Codecov Report
Patch coverage: 34.28% and project coverage change: +0.10 :tada:

Comparison is base (a19def3) 79.08% compared to head (9140cf2) 79.18%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1282      +/-   ##
============================================
+ Coverage     79.08%   79.18%   +0.10%
- Complexity      634      639       +5
============================================
  Files            73       73
  Lines          2352     2359       +7
  Branches        256      258       +2
============================================
+ Hits           1860     1868       +8
+ Misses          412      410       -2
- Partials         80       81       +1

Impacted Files
Coverage Δ

...lambda/powertools/parameters/DynamoDbProvider.java
80.32% <8.33%> (-3.01%)
:arrow_down:

.../lambda/powertools/parameters/SecretsProvider.java
65.85% <10.00%> (-0.82%)
:arrow_down:

...azon/lambda/powertools/parameters/SSMProvider.java
87.14% <70.00%> (+6.26%)
:arrow_up:

...zon/lambda/powertools/parameters/ParamManager.java
77.77% <100.00%> (+0.85%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update Chromium versions for api.Location.toString

17385

 Quality gate: NA
Details

 Quality gate: NA
Details


ARM OSX Migrator (again)

Supercedes #21

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)

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.

@conda-forge-admin, please rerender

@conda-forge/cairomm This is ready for review.


Consistent gracefulReload RPC

Is your feature request related to a problem? Please describe.
https://github.com/fluent/fluentd/pull/3396 tried to keep consistency even though excessive gracefulReload request is thrown
(It has same problem with SIGUSR2 too)
It tries to introduce blocking interval - @blocking_reload_interval parameter, but it seems that it turned out that it is too simple an approach.

The behaviour is changed without @blocking_reload_interval = 0.
There is a case that request is just ignored (it returns an error but it requires the user to implement retry for such a case. The breaking change)
It depends the previous API call

Describe the solution you'd like

Treat gracefulReload subsequently (somehow like a queue) or
Ensure to wait reloading thread has finished

Describe alternatives you've considered

N/A

Additional context
See https://github.com/fluent/fluentd/pull/3396
Feedbacks against #3396

https://github.com/fluent/fluentd/pull/3396#commitcomment-51857485
https://github.com/fluent/fluentd/pull/3396#commitcomment-51869670
https://github.com/fluent/fluentd/pull/3396#issuecomment-856981757

It's for #3341

I confirmed that current implementation can run multiple reload threads simultaneously when it receives excessive gracefulReload request.


[BEAM-9911]Replace SpannerIO.write latency counter to distribution

As part of improvements to spanner write, spanner_write_total_latency_ms was added for more visibility. This counter tracks the total latency in milliseconds suffered by all the write calls to spanner and is not actionable.
Replacing this with a Distribution make this more actionable as it provides 4 counters(MIN, MAX, MEAN, COUNT)
@nielm  @chamikaramj

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Java PostCommit

LGTM. Thanks.

Run Java PreCommit