v4 issues

Hi there,
I am trying out v4 and I am a bit confused.
middleman 4.0.0.rc.1
middleman-blog 4.0.0.rc.1 from git://github.com/middleman/middleman-blog.git (at master)

first thing in readme didn't work:
 middleman init MY_PROJECT --template=blog
Template `blog` not found in Middleman Directory.
Did you mean to use a full `user/repo` path?

so created middleman app and added middleman-blog manually. then I went to guide mentioned in readme but no that much more successful:
middleman article TITLE
Could not find command "article".

So I went to check the source and I see that v4 removed article command and a lot of blogging features? Is this gonna be changed or this is a new direction?

The init issue is an oversight on my part, will fix ASAP.
You are correct, the article command is being removed. I don't think any other blogging features are, though.

Thanks,
what I mean by blogging features are files like: calendar.html.erb, feed.xml.builder, index.html.erb, layout.erb, tag.html.erb
At least for me they are the place where I start: they give me idea of what I should build. Example is always good way to start.

Those should still all work, but I'll double check

they got removed in 6d7fdd6521dcf2e38605db7bdf9425868305e4d5, so that's why

Yes, that will be the new home for the template in v4

any eta on fix?

The init part is fixed.

Thanks. It would be nice to be able to use version 4, thought.
When I use gem install middleman --pre it will install middleman, middleman-cli, middleman-core 4.0.0.rc.1. But running middleman init MY_PROJECT --template=blog installs middleman-core 3.4.0 middleman-blog 3.5.3 so I end-up  using middleman-blog (3.5.3) and  middleman-core (~> 3.2) and middleman-core (3.4.0)
When then I run 'middleman' all I can see is
Recent Articles

Tags

By Year

Example article from template is not there.
When I use gem "middleman-blog", github: "middleman/middleman-blog" and run bundle, I end up using middleman-core (4.0.0.rc.1),middleman-blog (4.0.0.rc.1) and middleman-core (>= 4.0.0.rc.1) but running middleman will bring error /path/to/MY_PROJECT not found

@tdreyno I am trying out new version v4 but it's not working for me, any ideas what am I doing wrong?
gem install middleman
Fetching: concurrent-ruby-0.9.2.gem (100%)
Successfully installed concurrent-ruby-0.9.2
Fetching: hamster-2.0.0.gem (100%)
Successfully installed hamster-2.0.0
Fetching: contracts-0.12.0.gem (100%)
Successfully installed contracts-0.12.0
Fetching: addressable-2.4.0.gem (100%)
Successfully installed addressable-2.4.0
Fetching: fastimage-1.8.1.gem (100%)
Successfully installed fastimage-1.8.1
Fetching: capybara-2.5.0.gem (100%)
Successfully installed capybara-2.5.0
Fetching: padrino-support-0.13.1.beta1.gem (100%)
Successfully installed padrino-support-0.13.1.beta1
Fetching: padrino-helpers-0.13.1.beta1.gem (100%)
Successfully installed padrino-helpers-0.13.1.beta1
Fetching: middleman-core-4.0.0.gem (100%)
Successfully installed middleman-core-4.0.0
Fetching: middleman-cli-4.0.0.gem (100%)
middleman-cli's executable "middleman" conflicts with middleman-core
Overwrite the executable? [yN]  y
Successfully installed middleman-cli-4.0.0
Fetching: middleman-4.0.0.gem (100%)
Successfully installed middleman-4.0.0
Parsing documentation for addressable-2.4.0
Installing ri documentation for addressable-2.4.0
Parsing documentation for capybara-2.5.0
Installing ri documentation for capybara-2.5.0
Parsing documentation for concurrent-ruby-0.9.2
Installing ri documentation for concurrent-ruby-0.9.2
Parsing documentation for contracts-0.12.0
Installing ri documentation for contracts-0.12.0
Parsing documentation for fastimage-1.8.1
Installing ri documentation for fastimage-1.8.1
Parsing documentation for hamster-2.0.0
Installing ri documentation for hamster-2.0.0
Parsing documentation for middleman-4.0.0
Installing ri documentation for middleman-4.0.0
Parsing documentation for middleman-cli-4.0.0
Installing ri documentation for middleman-cli-4.0.0
Parsing documentation for middleman-core-4.0.0
Installing ri documentation for middleman-core-4.0.0
Parsing documentation for padrino-helpers-0.13.1.beta1
Installing ri documentation for padrino-helpers-0.13.1.beta1
Parsing documentation for padrino-support-0.13.1.beta1
Installing ri documentation for padrino-support-0.13.1.beta1
Done installing documentation for addressable, capybara, concurrent-ruby, contracts, fastimage, hamster, middleman, middleman-cli, middleman-core, padrino-helpers, padrino-support after 24 seconds
11 gems installed

 middleman init talks --template=blog
         run  git clone --depth 1 https://github.com/middleman/middleman-templates-blog /var/folders/cw/7dm5d5fd2rg18szl26z10_rw0000gn/T/d20151216-15131-1l9pjqy from "."
Cloning into '/var/folders/cw/7dm5d5fd2rg18szl26z10_rw0000gn/T/d20151216-15131-1l9pjqy'...
remote: Counting objects: 16, done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 16 (delta 2), reused 12 (delta 2), pack-reused 0
Unpacking objects: 100% (16/16), done.
Checking connectivity... done.
       exist
      create  .gitignore
      create  Gemfile
      create  config.rb
      create  source/2012-01-01-example-article.html.markdown
      create  source/calendar.html.erb
      create  source/feed.xml.builder
      create  source/index.html.erb
      create  source/layout.erb
      create  source/tag.html.erb
         run  bundle install from "./talks"
Fetching gem metadata from https://rubygems.org/..............
Fetching additional metadata from https://rubygems.org/..
Resolving dependencies...
Using i18n 0.7.0
Using json 1.8.3
Using minitest 5.8.3
Using thread_safe 0.3.5
Using tzinfo 1.2.2
Using activesupport 4.2.5
Using addressable 2.4.0
Using backports 3.6.7
Using builder 3.2.2
Using bundler 1.7.4
Using mime-types-data 3.2015.1120
Using mime-types 3.0
Using mini_portile2 2.0.0
Using nokogiri 1.6.7
Using rack 1.6.4
Using rack-test 0.6.3
Using xpath 2.0.0
Using capybara 2.5.0
Using concurrent-ruby 0.9.2
Using contracts 0.12.0
Using erubis 2.7.0
Using execjs 2.6.0
Using fastimage 1.8.1
Using ffi 1.9.10
Using hamster 2.0.0
Using hashie 3.4.3
Using rb-fsevent 0.9.6
Using rb-inotify 0.9.5
Using listen 3.0.5
Installing padrino-support 0.13.0
Using tilt 1.4.1
Installing padrino-helpers 0.13.0
Installing sass 3.4.20
Using uglifier 2.7.2
Using middleman-core 4.0.0
Installing middleman-blog 4.0.0
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.

cd talks

middleman server
/Users/janhovancik/Workspace/Play/talks not found

how about bundle exec middleman server?

/Users/janhovancik/.rvm/gems/ruby-2.1.3@global/gems/bundler-1.7.4/lib/bundler/rubygems_integration.rb:256:in `block in replace_gem': middleman-cli is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
	from /Users/janhovancik/.rvm/gems/ruby-2.1.3/bin/middleman:22:in `<main>'
	from /Users/janhovancik/.rvm/gems/ruby-2.1.3/bin/ruby_executable_hooks:15:in `eval'
	from /Users/janhovancik/.rvm/gems/ruby-2.1.3/bin/ruby_executable_hooks:15:in `<main>'

gemfile is:
# If you do not have OpenSSL installed, change
# the following line to use 'http://'
source 'https://rubygems.org'

# For faster file watcher updates on Windows:
gem 'wdm', '~> 0.1.0', platforms: [:mswin, :mingw]

# Windows does not come with time zone data
gem 'tzinfo-data', platforms: [:mswin, :mingw, :jruby]

# Middleman Gems
gem "middleman-blog"

# For feed.xml.builder
gem "builder", "~> 3.0"

so it finally works for me with this gemfile
# If you do not have OpenSSL installed, change
# the following line to use 'http://'
source 'https://rubygems.org'

# For faster file watcher updates on Windows:
gem 'wdm', '~> 0.1.0', platforms: [:mswin, :mingw]

# Windows does not come with time zone data
gem 'tzinfo-data', platforms: [:mswin, :mingw, :jruby]

# Middleman Gems
gem "middleman-blog"

# For feed.xml.builder
gem "builder", "~> 3.0"

gem "middleman-cli"

gem 'redcarpet', '~> 3.3', '>= 3.3.3'

Well, gem "middleman" definitely should be included by default. Is this coming from a project template?

yes, the gemfile i am mentioning before is what I got after doing gem install middleman and middleman init talks --template=blog

cool. I think I forgot a line. Will fix the template asap

Updated. Try now

many thanks, works just fine now.

ok, so what is middleman article replaced with? I loved that command.

Nothing, but I plan on bringing it back as time allows

Oh, ok. I appreciate it.


[Hotfix] Add encode info

What is this PR for?
To dump a Kubernetes service configuration file, we have to specify an encoding info for Japanese characters.
This PR includes

Add encoding info when write file.

What type of PR is it?
Bugfix
What is the issue?
N/A
How should this be tested?
Save Japanese character in memo

 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.

Thank you :)


Is this up-to-date and working with Jellyfin server?

Hello.
I see no new commits have been made since forked from the Emby version.
Is that a sign that no api's have changed when comparing to Emby? Or is this project simply a "todo"?
I wanted to know if this api client works, for when I am going to add Jellyfin support to my audiobook app.
If the same api client is used for Emby and Jellyfin, then that makes things a lot easier.
If on the other hand, this project is simply just a todo, and there is no up-to-date C# api client for Jellyfin, then that makes my work a lot harder, since I'd have to make one.

The API client here is much more active, I would suggest that one.

Yeah I just found that by myself as well. However, it clearly states that it's a work in progress, and not ready for use yet.

I believe @villagra has been using it for his C# client with great success, so it could only be a disclaimer. Maybe he will jump in here and set the record straight, I'm not too sure.

Ey... yes. That's the client I'm using for my app. It's not feature complete, but all operations needed in videotape to talk to jellyfin/emby are there. I'll try to add some documentation during the next days explaining how to use it.

I'm not on my way to use it right now. Just doing a bit of research beforehand. I'm looking to make my app ready with Plex first. And then around version 1.0 I'll add Emby and Jellyfin

Also I'm not afraid to step in and add whatever functionality I need to the client. I've had to add a bit to the unofficial Plex client that I was able to find as well.

I'll publish the client to nuget soon as well.
btw: thanks for pointing to the plex client, I was looking for it.

There are 2 different C# plex clients in my repositories. I first used https://github.com/Inrego/fa.standard.libraries and added stuff I was missing. But it didn't support connecting to servers you were invited to (only your own). And since plex auth is a not very well documented mess, I looked around and found another rather new client, which supported it. And it's working well so far. It's not feature complete, and I still need to add a few things, I think. https://github.com/Inrego/plex-api
I'll commit my latest changes now. Didn't really think too much about it as I didn't think anyone else was going to use it.

Oh and btw, on the plex-api project, I mostly just added missing models to already support api's, and made the client more subclass-friendly. I then subclass it in my audiobook app and implement the extra functionality there. I don't remember my reasoning for not adding the extra functionality directly in the library, so I guess I'll move it there within the coming days, as it might benefit others.

Moved my changes to the repo now. So now it contains all the customizations/changes that I've made.

@Inrego we like to announce new clients on the official blog, I believe we have a post from @jmvillagra that's going up soon. Let us know when you add support and we can put something on the site.


Large-core quasirelativistic ECPs (Stuttgart)

Hello,
I am trying to find the large-core quasirelativistic ECPs for the lanthanides from
M. Dolg, H. Stoll, A. Savin and H. Preuss, Theor. Chim. Acta, 1989, 75, 173–194
It seems like they would logically go with "Stuttgart RLC"
What would be the process of including them?
Thanks,
Felix

I guess the problem is that there are a number of different ways. One could either use +2 or +3 charge and one could use nonrelativistic and quasirelativstic potentials. Gaussian differentiates 6 different forms of these potentials in their manual: SDD, SHF, SDF, MHF, MDF, MWB (https://gaussian.com/basissets/)

And Gaussian lists 25 references for the pseudopotentials...

I assume you’re aware of M. Dolg’s website? http://www.tc.uni-koeln.de/PP/index.en.html http://www.tc.uni-koeln.de/PP/index.en.html
Best wishes,
Grant

On 18 Nov 2021, at 15:02, Felix Plasser @.***> wrote:
Hello,
I am trying to find the large-core quasirelativistic ECPs for the lanthanides from
M. Dolg, H. Stoll and H. Preuss, Theor. Chim. Acta, 1989, 75, 173–194 http://aip.scitation.org/doi/10.1063/1.456066
It seems like they would logically go with "Stuttgart RLC"
What would be the process of including them?
Thanks,
Felix
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/MolSSI-BSE/basis_set_exchange/issues/237, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIRM6VTVSNFJ5JBF23RN6BLUMUIOZANCNFSM5IJ2VI2A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

ok, thanks! I'll go via the Dolg website then. I guess it is not trivial to incorporate any of this into a general purpose basis set exchange.


Fix advanced happy path

Description
Fix the advanced happy path flow as it is broken now due to large UI changes.

[test]

[test]

[test]

[test]

[test]

/lgtm


Types resolution does not honor "types" in tsconfig, and doesn't match the logged trace

I am tearing my hair out trying to figure out how to ignore @types/node without deleting it and turning on skipLibCheck. Explicitly declaring all of my types in tsconfig.json doesn't seem to be honored by Typescript.
TypeScript Version: 3.5.2, next

Search Terms:
module resolution, types, tsconfig, typings, node
Code
See the minimal repo here
output for traceResolution can be found in trace.txt
Expected behavior:
Typescript should use the correct type declarations for the events package, which includes the Listener type. Typescript should use the types declared in the types array. Typescript should use the types declarations that are logged in traceResolution
Actual behavior:
Even though the only member of the types array is "events" and the logged resolved module (@types/events/index.d.ts) is correct, Typescript still outputs the error even though the this file has the Listener export:
index.ts:1:24 - error TS2305: Module '"events"' has no exported member 'Listener'.

1 import { EventEmitter, Listener } from 'events'

Output of trace shown here although the error indicates that these are not the types acatually being used:
======== Resolving module 'events' from '/Users/rvinzent/test-project/index.ts'. ========
Explicitly specified module resolution kind: 'NodeJs'.
Loading module 'events' from 'node_modules' folder, target file type 'TypeScript'.
Found 'package.json' at '/Users/rvinzent/test-project/node_modules/events/package.json'.
'package.json' does not have a 'typesVersions' field.
File '/Users/rvinzent/test-project/node_modules/events.ts' does not exist.
File '/Users/rvinzent/test-project/node_modules/events.tsx' does not exist.
File '/Users/rvinzent/test-project/node_modules/events.d.ts' does not exist.
'package.json' does not have a 'typings' field.
'package.json' does not have a 'types' field.
'package.json' has 'main' field './events.js' that references '/Users/rvinzent/test-project/node_modules/events/events.js'.
File '/Users/rvinzent/test-project/node_modules/events/events.js' exist - use it as a name resolution result.
File '/Users/rvinzent/test-project/node_modules/events/events.js' has an unsupported extension, so skipping it.
Loading module as file / folder, candidate module location '/Users/rvinzent/test-project/node_modules/events/events.js', target file type 'TypeScript'.
File '/Users/rvinzent/test-project/node_modules/events/events.js.ts' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/events.js.tsx' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/events.js.d.ts' does not exist.
File name '/Users/rvinzent/test-project/node_modules/events/events.js' has a '.js' extension - stripping it.
File '/Users/rvinzent/test-project/node_modules/events/events.ts' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/events.tsx' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/events.d.ts' does not exist.
Directory '/Users/rvinzent/test-project/node_modules/events/events.js' does not exist, skipping all lookups in it.
File '/Users/rvinzent/test-project/node_modules/events/index.ts' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/index.tsx' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/index.d.ts' does not exist.
Found 'package.json' at<EMAIL_ADDRESS>'package.json' does not have a 'typesVersions' field.
File<EMAIL_ADDRESS>does not exist.
'package.json' does not have a 'typings' field.
'package.json' has 'types' field 'index' that references '/Users/rvinzent/test-project/node_modules/@types/events/index'.
File '/Users/rvinzent/test-project/node_modules/@types/events/index' does not exist.
Loading module as file / folder, candidate module location '/Users/rvinzent/test-project/node_modules/@types/events/index', target file type 'TypeScript'.
File<EMAIL_ADDRESS>does not exist.
File<EMAIL_ADDRESS>does not exist.
File<EMAIL_ADDRESS>exist - use it as a name resolution result.
Resolving real path for<EMAIL_ADDRESS>result<EMAIL_ADDRESS>======== Module name 'events' was successfully resolved to<EMAIL_ADDRESS>with Package ID '<EMAIL_ADDRESS>========

"Go To Definition" in VSCode points to the incorrect @types/node/events.d.ts definition.
Additionally, in the dependency that actually requires Node's events, the module is incorrectly resolved to the independent events package. Trace output shown here:
======== Resolving module 'events' from<EMAIL_ADDRESS>========
Explicitly specified module resolution kind: 'NodeJs'.
Loading module 'events' from 'node_modules' folder, target file type 'TypeScript'.
Directory '/Users/rvinzent/test-project/node_modules/@types/node/node_modules' does not exist, skipping all lookups in it.
Directory '/Users/rvinzent/test-project/node_modules/@types/node_modules' does not exist, skipping all lookups in it.
Found 'package.json' at '/Users/rvinzent/test-project/node_modules/events/package.json'.
'package.json' does not have a 'typesVersions' field.
File '/Users/rvinzent/test-project/node_modules/events.ts' does not exist.
File '/Users/rvinzent/test-project/node_modules/events.tsx' does not exist.
File '/Users/rvinzent/test-project/node_modules/events.d.ts' does not exist.
'package.json' does not have a 'typings' field.
'package.json' does not have a 'types' field.
'package.json' has 'main' field './events.js' that references '/Users/rvinzent/test-project/node_modules/events/events.js'.
File '/Users/rvinzent/test-project/node_modules/events/events.js' exist - use it as a name resolution result.
File '/Users/rvinzent/test-project/node_modules/events/events.js' has an unsupported extension, so skipping it.
Loading module as file / folder, candidate module location '/Users/rvinzent/test-project/node_modules/events/events.js', target file type 'TypeScript'.
File '/Users/rvinzent/test-project/node_modules/events/events.js.ts' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/events.js.tsx' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/events.js.d.ts' does not exist.
File name '/Users/rvinzent/test-project/node_modules/events/events.js' has a '.js' extension - stripping it.
File '/Users/rvinzent/test-project/node_modules/events/events.ts' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/events.tsx' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/events.d.ts' does not exist.
Directory '/Users/rvinzent/test-project/node_modules/events/events.js' does not exist, skipping all lookups in it.
File '/Users/rvinzent/test-project/node_modules/events/index.ts' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/index.tsx' does not exist.
File '/Users/rvinzent/test-project/node_modules/events/index.d.ts' does not exist.
Found 'package.json' at<EMAIL_ADDRESS>'package.json' does not have a 'typesVersions' field.
File<EMAIL_ADDRESS>does not exist.
'package.json' does not have a 'typings' field.
'package.json' has 'types' field 'index' that references '/Users/rvinzent/test-project/node_modules/@types/events/index'.
File '/Users/rvinzent/test-project/node_modules/@types/events/index' does not exist.
Loading module as file / folder, candidate module location '/Users/rvinzent/test-project/node_modules/@types/events/index', target file type 'TypeScript'.
File<EMAIL_ADDRESS>does not exist.
File<EMAIL_ADDRESS>does not exist.
File<EMAIL_ADDRESS>exist - use it as a name resolution result.
Resolving real path for<EMAIL_ADDRESS>result<EMAIL_ADDRESS>======== Module name 'events' was successfully resolved to<EMAIL_ADDRESS>with Package ID '<EMAIL_ADDRESS>========

I have not found a good solution to allow testing dependencies to use @types/node while ignoring those types for my browser code. It also appears the the trace log is not displaying the actual resolved module.

types only controls what type packages are automatically added to your compilation. It doesn't change anything about module resolution, which is what's being triggered by having imports or references in your project.
You have the following dependency chain here:

index.spec.ts imports enzyme
@types/enzyme/index.d.ts references cheerio
@types/cheerio/index.d.ts references node

node is also in the dependency chain from the jest-runner, and perhaps others. Basically, several components you have loaded here claim to only be able to run in the node runtime environment, and in that environment, "events" unambiguously refers to the built-in nodejs module, not the other one you have loaded.
So at this point you have both @types/node and @types/events trying to provide a definition for the events module. It's simply a conflict at this point and there's no principled way to resolve it.
The fix here is a broader one where all the packages on DT (and in the broader ecosystem) stop taking hard dependencies on the node package, especially just to grab EventEmitter or Buffer. We should take some effort here to make a separate package for these kinds of types.

@rbuckton let's think about a long-term fix here

@RyanCavanaugh It's interesting to me that it says that the module was successfully resolved to @types/events/index.d.ts on the events import, but the compiler still throws the error on that import. Something doesn't match.


[Module Proposal]: Azure Firewall Policy (tf)

Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals

Check this module doesn't already exist in another project that is being evolved into AVM

[X] I have checked for that this module doesn't already exist in CARML or TFVM

Terraform or Bicep?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-network-firewallpolicy
Module Details
Creating a module for firewall policy that will be used with the azure firewall policy.
Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username
cshea15

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

@cshea15
i supposes that statement above confirms that you agree to the below pages that define what module ownership means:
https://azure.github.io/Azure-Verified-Modules/specs/shared/team-definitions
https://azure.github.io/Azure-Verified-Modules/specs/shared
https://azure.github.io/Azure-Verified-Modules/help-support/module-support
Please confirm that i am not wrong about this.
module name: avm-res-network-firewallpolicy
Github repo name: terraform-azurerm-avm-res-network-firewallpolicy
i will move this request from "Proposed" to "In Development"
Please reach out to AVM core team in case that you need any assistance.

You are correct, I was just getting ahead of it thanks @prjelesi

pr is ready for review https://github.com/Azure/terraform-azurerm-avm-res-network-firewallpolicy/pull/1

waiting for PR to be approved.

PR is merged and content has been published. https://registry.terraform.io/modules/Azure/avm-res-network-firewallpolicy/azurerm/latest


Have the entire side menu buttons be clickable. Right now only the text inside the button is clickable.

The side menu buttons as in the "Industries", "Companies", "MarkLogic 9 Features", and "Regions" buttons

deployed


Protect Applications on SKRs

Description
Changes proposed in this pull request:

Protect applications
Adjust messages

Testing

Disabling Connect Application - I've added configmap on sundown cluster (kubectl -n kyma-system get configmap skr-configmap -oyaml), edit the data to disable protection.
Protecting Applications - add

"PROTECTED_RESOURCES": {
        "isEnabled": true,
        "config": {
          "resources": [
            {
              "match": { "$.metadata.labels['applicationconnector.kyma-project.io/managed-by']": "compass-runtime-agent" }
            }
          ]
        }
      }

to local config.json.
Related issue(s)
Resolves #712

/test pre-busola-integration-test-k3s

/test pre-busola-integration-test-k3s

/test pre-busola-integration-test-k3s

/test pre-busola-integration-test-k3s


Initial value incorrectly appears above List values for report field configuration

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.8-3
Reproducible in staging?: Y
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1721250852064199
Action Performed:

Make sure you are on the reportFields beta
On NewDot, create a workspace
In More features, enable Report fields
Create a dropdown report field, with several values. Add several initial values

Expected Result:
Initial value appears below List values
Actual Result:
 Initial value appears above List values
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub

Holding on this one until we decide what to do with the list values row: internal link

@Krishna2323 @gijoe0295 @dominictb Based on the internal discussion, we also want to make one change to how we show the list values, this is covered in this issue https://github.com/Expensify/App/issues/45990 and I will close this one in favour of the more generic issue as this change is super simple and not worth exporting on its own.
Waiting for a confirmation from design on that issue


PSShouldProcess false positive on function inside of a begin/process/end function

It isn't uncommon to have helper functions inside the begin function to process items.  These functions can use $pscmdlet.ShouldProcess() but because they are not marked with the [CmdletBinding(SupportsShouldProcess)] this rule fires.
Here's a simple repro:
function Foo {
   [CmdletBinding(SupportsShouldProcess)]
   param()

   begin {
       function helper {
           if ($PSCmdlet.ShouldProcess('','') {

           }
       }
   }
}

@rkeithhill This is part of a bigger issue - analyzing dependencies within and/or across PowerShell scrips/modules - that PSScriptAnalyzer doesn't address as of yet.
How common is this pattern of using $pscmdlet.shouldprocess in a helper function? If such a feature were to exist would it reduce the false alarm rate by a significant amount? Also, would RuleSuppression be helpful in reducing these kinds of false alarms?

I can't speak for other modules but I use it commonly enough.  Let me try the suppressing it. I think I tried once by putting the attribute on the outermost function but it didn't suppress.  I just tried with the latest version of PSScriptAnalyzer and that is working now.
So that is a reasonable workaround for now.  But I do think it should be fixed.  Seems like you would just examine the context of where the function is defined.  If defined inside the context of an advanced function, then if that adv function has the SupportsShouldProcess attribute then the current function is covered.  Easy peasy, right?  :-)  I know, it's never that easy.

I agree that it should be fixed. But, do we just examine the context of the function? What if someone if dot-sourcing the helper function? What is the level of nesting that we should examine? There may be other cases that I am probably missing but I think this raises more questions and we need more discussion around this issue on how do we handle such situations in general. But of course, we can just go ahead and start with examining the context of the function to see if it is defined in an advanced function.

But, do we just examine the context of the function?

I think that is the best place to start as it will cover the vast majority of cases.  While I often have helper functions defined within a `begin

Also reported in #608


test-driver.py: handle qemu process exit

qemu process may exit during execution of the test.
It could happen

due to a bug (we are testing software for bugs, so they are expected)
or after the guest executes poweroff
or user click [x] if the test is run intercatively

Now, testdriver just hangs forever in such cases

Result of nixpkgs-review pr 129829 at 8403e00d run on x86_64-linux 1

1 package failed to build:

tests.trivial

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

The test driver has been refactored since, and the broken pipe handling seems to have improved as well, but not throwing exceptions. In at least one case, such an exception would be unhelpful, as the VM is expected to close its handle, for example when shutting down.
Please open a new issue or PR if you're still experiencing issues. (Which has the benefit of better exposure compared to this one)


maks sure we don't change dtype in zero_mean preprocessing

I'm having trouble trying to test this fix with this model: https://bioimage.io/#/?id=10.5072%2Fzenodo.880412
It seems like my pytorch version does not match or something similar environment related:
C:\conda\envs\tiktorch-server-env\python.exe C:/repos/tiktorch/tiktorch/runner/model_test.py -m C:\Users\fbeut\Downloads\em-mitochondria-boundarymodel_pytorch_state_dict\rdf.yaml
Traceback (most recent call last):
  File "C:/repos/tiktorch/tiktorch/runner/model_test.py", line 51, in model_test
    model_zip, devices=["cuda" if torch.cuda.is_available() else "cpu"], preserve_batch_dim=True
  File "C:\repos\tiktorch\tiktorch\runner\utils.py", line 37, in eval_model_zip
    bioimageio_model=bioimageio_model, devices=devices, preserve_batch_dim=preserve_batch_dim
  File "C:\repos\tiktorch\tiktorch\runner\prediction_pipeline\_prediction_pipeline.py", line 201, in create_prediction_pipeline
    bioimageio_model=bioimageio_model, devices=devices, weight_format=weight_format
  File "C:\repos\tiktorch\tiktorch\runner\prediction_pipeline\_model_adapters\_model_adapter.py", line 73, in create_model_adapter
Failed to load prediction pipeline from source package
    return adapter_cls(bioimageio_model=bioimageio_model, devices=devices)
  File "C:\repos\tiktorch\tiktorch\runner\prediction_pipeline\_model_adapters\_pytorch_model_adapter.py", line 24, in __init__
    state = torch.load(weights.source, map_location=self.devices[0])
  File "C:\conda\envs\tiktorch-server-env\lib\site-packages\torch\serialization.py", line 367, in load
    return _load(f, map_location, pickle_module)
  File "C:\conda\envs\tiktorch-server-env\lib\site-packages\torch\serialization.py", line 528, in _load
    magic_number = pickle_module.load(f)
_pickle.UnpicklingError: A load persistent id instruction was encountered,
but no persistent_load function was specified.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:/repos/tiktorch/tiktorch/runner/model_test.py", line 98, in <module>
    sys.exit(main())
  File "C:/repos/tiktorch/tiktorch/runner/model_test.py", line 90, in main
    raise e
  File "C:/repos/tiktorch/tiktorch/runner/model_test.py", line 87, in main
    model_test(args.model, args.weight_format, args.decimals)
  File "C:/repos/tiktorch/tiktorch/runner/model_test.py", line 54, in model_test
    raise RuntimeError("Failed to load prediction pipeline from source package") from e
RuntimeError: Failed to load prediction pipeline from source package

Process finished with exit code 1

What pytorch version do you have? It should be >1.6.

What pytorch version do you have? It should be >1.6.

1.9.0

pretty late to the game, but the patch will fail for any kind of integer data.

pretty late to the game, but the patch will fail for any kind of integer data.

I see. It was merged in a bit of a panic mode...
Let's discuss a clean solution in #184.


Please update the NPM version

Hello,
Currently, the NPM version is 3.4.2 so please update it to 3.4.4
Thanks

I would like to reopen this.
Composer is not happy with the not released version 3.4.4 on npmjs and it does not currently see the 3.4.5. Took me a long time …
The hard problem is that 3.4.4 has a git+ssh url which composer tries to download. For that to work you need a private key linked to your github account. And then give your build server a likewise key and account … simply not cutting it.

% composer info --all npm-asset/flag-icon-css
name     : npm-asset/flag-icon-css
descrip. :
keywords :
versions : dev-master, 3.4.4, 3.4.3, * 3.4.2, 3.4.1, 3.4.0, 3.3.0, 3.2.1, 3.2.0, 3.1.0, 3.0.0, 2.9.0, 2.8.0, 2.7.0, 2.6.0, 2.5.0, 2.4.0, 2.3.1, 2.3.0, 2.2.0, 2.1.0, 2.0.0, 1.4.0, 1.3.0, 1.2.0, 1.1.0, 1.0.0, 0.8.6, 0.8.5, 0.8.4, 0.8.3, 0.8.2, 0.8.0, 0.7.1, 0.7.0, 0.6.5, 0.6.4, 0.6.3, 0.6.2, 0.6.1, 0.6.0, 0.5.1, 0.5.0, 0.4.0, 0.3.0, 0.2.0, 0.1.0, dev-gae
type     : npm-asset
source   : []
dist     : [tar] https://registry.npmjs.org/flag-icon-css/-/flag-icon-css-3.4.2.tgz
path     : /Users/CKirschner/repositories/bayermsgateway/docroot/libraries/flag-icon-css
names    : npm-asset/flag-icon-css
requires
npm-asset/opencollective-postinstall 2.0.2

% composer info --all npm-asset/flag-icon-css 3.4.4
name     : npm-asset/flag-icon-css
descrip. :
keywords :
versions : 3.4.4
type     : npm-asset
source   : [git]<EMAIL_ADDRESS>1b0d2f6eb78ee1cecbcce0c63ab106aa51d044d6
dist     : []
names    : npm-asset/flag-icon-css
requires
npm-asset/opencollective-postinstall 2.0.2

% composer info --all npm-asset/flag-icon-css 3.4.5
[InvalidArgumentException]
Package npm-asset/flag-icon-css not found

@Xarno the NPM latest version is already 3.4.5

but for composer it is still 3.4.4

That's exactly the problem. Version 3.4.4 is not on NPM.
Compare
https://www.npmjs.com/package/flag-icon-css/v/3.4.4
with
https://www.npmjs.com/package/flag-icon-css/v/3.4.2


feat: generate release notes support

supports the new feature github announced today: generate release notes (link)
while there are no official docs yet, one of the product managers posted screenshots of it on twitter: https://twitter.com/MylesBorins/status/1445102641214861318
This implements both the new /releases/generate-notes endpoint and the new generate_release_notes release option.

Thanks for the review @gmlewis! Just fixed the based on this tweet.

@Parker77 - do you have time to review this?


Publish to AWS: I could not deploy to an existing cloud app

In Publish to AWS, the Existing Targets list did not show my project. I expected to see it there.

Toolkit: <IP_ADDRESS>
Visual Studio: 17.10.2

Closing as duplicate of https://github.com/aws/aws-toolkit-visual-studio/issues/430


"Go to Definition" does not work with wildcard imports

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.83.0
OS Version: Ventura 13.6

Steps to Reproduce:

Use this configuration in jsconfig.json:

{
  "compilerOptions": {
    "moduleResolution": "classic",
    "paths": {
      "~/*": ["./src/*"]
    }
  }
}

Create a component in src/components/component.js and default export it:

export default function Component() {
  return (

  );
}

Import the component using wildcard syntax and invoke it:

import { Component } from '~/components/*';`

export default function Page() {
  return (

      <Component />

  );
}

Right-click the component in either the import statement or invocation and select "Go to Definition."

Expected Behavior:
component.js is opened in a new tab.
Actual Behavior:
Cursor simply moves to the other occurrence of Component within Page.
Notes:

import Component from '~/components/component'; does work as expected.
There is no index.js file in components.
Changing the value of the moduleResolution property in jsconfig.json or adding a baseUrl hasn't changed anything.
The expected behavior occurs in this scenario when using Sublime Text.

What tools support using * in the import path?

What tools support using * in the import path?

Sublime Text!

But what JS bundlers or frameworks support it?

I'm doing a transformation with Next in my next.config.js under modularizeImports if that's any kind of answer? But your questions make me feel like I'm missing something. If I'm wrong to expect this behavior from every IDE and/or it's not a bug, please don't let me waste your time!

* in an import path is generally not supported; this is the first I've heard of someone trying.

I'm doing a transformation with Next in my next.config.js

The JS language service has no idea about this kind of operation, so can't predict what the output path will look like, e.g. if you had component1.js, component2.js, and component3.js in /component/, each of those seems like equally valid targets. I'm not really clear on what this schema is -- it's possible if the only file in there was named index.js it would be resolved, but I'm not sure.


Layers: Correctly update iterator when erasing vector element

ApiLayerInterface::LoadApiLayers would load the manifest files for explicit layers in order to match them against requested layers. As the layers are matched, they would be erased from the manifest vector in order to prevent double-matching. However, in the erase case, the iterator wasn't being updated correctly.

Oh, I forgot about the repro. I hit this while trying to enable the core validation layer with hello_xr. I used the environment variables below (Windows 10 x64, VS 2019):
XR_API_LAYER_PATH=D:\\git\\OpenXR-SDK-Source\\build\\win64\\src\\api_layers
XR_ENABLE_API_LAYERS=XR_APILAYER_LUNARG_core_validation

@bradgrantham-lunarg thanks for looking into this. Is there some way we could extend the loader test to test for this? I just checked and the loader test passed fine here as-is (once I disabled the active runtime, at least - that part never seems to work quite right)

@bradgrantham-lunarg thanks for looking into this. Is there some way we could extend the loader test to test for this? I just checked and the loader test passed fine here as-is (once I disabled the active runtime, at least - that part never seems to work quite right)

Oh, I don't get any credit for this, Rob just filed it independently.  This does now match the idiom cppreference.com reports for vector::erase. :sheepish:
However, If I remember this correctly, the outer loop walks the layers enabled by environment variable or by CreateInstance.  The inner loop walks the manifest list to make sure the enabled layer was discovered, and if so it deletes that name from the discovered list so it's ignored if it's in the enabled layer list twice.  I mean, that is wrong, and in that case the iterator would have been double-incremented, but I'm wondering what the failure would be in the case that there's just one explicit layer.  Crash because iterator was end() and then was incremented restarting the loop body?  I thought I had tested the case of one layer but maybe I didn't test properly or was sloppy.
@robbiesri , what is the failure and could you post the output of XR_LOADER_DEBUG=all?

Hey all!

@robbiesri , what is the failure and could you post the output of XR_LOADER_DEBUG=all?

The failure was indeed iterating past end with the iterator for explicit_layer_manifest_files. In my setup, I had the api_dump and core_validation layers built, and I was trying to enable core_validation when I hit this issue.
Let me get you the dump from XR_LOADER_DEBUG.

@robbiesri Would you mind adding a changelog fragment in changes/sdk/ named pr.256.gh.OpenXR-SDK-Source.md to include in the next release changelog?

Yep, no problem! I'll add that in a minute!

here's the output from XR_LOADER_DEBUG
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
[10:20:41.725][Info   ] Press any key to shutdown...
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Info [GENERAL |  | OpenXR-Loader] : RuntimeManifestFile::FindManifestFiles - using registry-specified runtime file C:\Program Files\Oculus\Support\oculus-runtime\oculus_openxr_64.json
Info [GENERAL |  | OpenXR-Loader] : RuntimeManifestFile::FindManifestFiles - using global runtime file C:\Program Files\Oculus\Support\oculus-runtime\oculus_openxr_64.json
Info [GENERAL |  | OpenXR-Loader] : RuntimeManifestFile::CreateIfValid - attempting to load C:\Program Files\Oculus\Support\oculus-runtime\oculus_openxr_64.json
Info [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : RuntimeInterface::LoadRuntime succeeded loading runtime defined in manifest file C:\Program Files\Oculus\Support\oculus-runtime\oculus_openxr_64.json using interface version 1 and OpenXR API version 1.0
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateApiLayerProperties | OpenXR-Loader] : Entering loader trampoline
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Verbose [GENERAL | xrEnumerateApiLayerProperties | OpenXR-Loader] : Entering loader trampoline
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
[10:20:41.764][Info   ] Available Layers: (2)
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrCreateInstance | OpenXR-Loader] : Entering loader trampoline
Warning [GENERAL |  | OpenXR-Loader] : ReadLayerDataFilesInRegistry - failed to read registry location \ApiLayers\Implicit in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER

Added the changelog fragment!

Thanks very much!


Can crash the debugger after running this program many times with Ctrl+Shift+F5

Tested this on the latest master and dev branches.
Steps to reproduce:

Compile this program with MSVC - normal flags e.g. (cl -Zi -Od test.c)

#include <stdio.h>
#include <stdint.h>
#include <windows.h>

DWORD WINAPI thread_func(VOID *param) {
    while(TRUE) {
        int lol = 3;
    }
}

int main(void) {
    DWORD thread_id = 0;
    HANDLE thread_handle = CreateThread(0, 0, thread_func, 0, 0, &thread_id);

    return 0;
}

Put a breakpoint on line "int lol = 3;"
Hold down the Restart debugging key (Ctrl+Shift+F5) for 30 seconds (or longer). Eventually you will get the following error message:

[Window Title]
Fatal Exception

[Content]
A fatal exception (code 0xc0000005) occurred. The process is terminating.

Press Ctrl+C to copy this text to clipboard, then create a new issue in
https://github.com/EpicGames/raddebugger/issues

Call stack:
0. [0x7ff71df054db] demon_run +507, demon_core.c line 289
1. [0x7ff71df2c0ef] ctrl_thread__next_demon_event +2991, ctrl_core.c line 1730
5. [0x7ff71df2d52d] ctrl_thread__launch_and_init +461, ctrl_core.c line 2069
6. [0x7ff71df2b3c2] ctrl_thread__entry_point +418, ctrl_core.c line 1544
7. [0x7ff71de977f8] w32_thread_base +56, os_core_win32.c line 173
8. [0x7ffa28077344] KERNEL32
9. [0x7ffa29b226b1] ntdll

edit: looks like this in remedy when I attach to the crashed process:

This line decrements run_ctrls.run_entity_count when it is zero. For some reason the "ctrl_thread__launch_and_init" function is encountering a DEMON_EventKind_ExitProcess event after all run entities have been removed.

I think this crash is just one symptom of a greater issue. Holding (Ctrl+Shift+F5) to restart the debugged process in quick succession eventually somehow leads to the current instance of process not being restarted but new instances being created. See the Scheduler panel here and also the crazy breakpoint hit graphic.

This has been more thoroughly addressed with 62659c5161ce25a671b6585726f2cbaa531f4f54.


gitea: 1.15.9 -> 1.15.10

Motivation for this change
update gitea to latest version
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Note: the upstream source zip hasn't been uploaded yet, and so I'll update this PR with correct hash once that is complete.

Why are we not fetching the git source?

@mohe2015  not fetching directly from the git repo, because that lacks several vendor files for the web UI


[SelectField] in alpha/next

Description
The SelectField component (http://www.material-ui.com/#/components/select-field) has not yet been implemented in the alpha/next branch. I think this is the most common element that is missing.
Is there a reason for it not being one of the last form elements to be migrated? I can potentially help out with any work required.
Images & references
This has been asked by others who are wanting to use the Grid, but then can't use SelectField: https://stackoverflow.com/questions/33671469/material-ui-and-grid-system/42474014#comment74801296_42474014

@ianchanning Please have a look at #6608 and #6301
You can continue this work 😄

Cheers @kybarg. My searching completely failed! - I did try searching for those, but came up empty. I'll close this and look at those.


Fix for non-default install directory

This will allow the module to work if PowerCLI is installed in a non-default directory (or if the workstation is 32 bit Windows).

Nice fix.
Just one remark, the code assumes there is a module, so it won't work with PowerCLI 5.x.
Would we need to have PowerCLI 5.x support?
Thoughts?
Luc

Yes, good catch -- thanks for creating a fix, @NamedJason.
My thoughts on this not working for PowerCLI 5.x:  PowerCLI 6.x has been out since Mar 2015, so it seems that there has been ample time for people to get current with their PowerCLI install.  And, if there are still some people that, for some reason, "must" stay on a PowerCLI 5.x version, they can stay on v1.0.1 of the DRSRule module...
As for the bit in the updated code that "creates" the path to the given .dll from the module path, I suggest that we leverage some path-management cmdlets like Split-Path and Join-Path, staying out of the substring() game if we can.  Like, instead of:
$pcliDll = "$($modulePath.substring(0,$modulePath.indexOf('Modules')))VMware.Vim.dll"
use something like:
$pcliDll = Join-Path -Path ((Get-Module VMware.VimAutomation.Core).ModuleBase | Split-Path -Parent | Split-Path -Parent) -ChildPath "VMware.Vim.dll"
A bit longer, but keeps us away from manual string manipulation.  What do people think?
Matt

How about this?
$pcliDLL = join-path -path (get-installpath) -childpath "VMware.Vim.dll"
I'm skeptical of it because it seems too simple...

Ok, with the PowerCLI 6.x requirement, but then we should add something like this.
#Requires -Modules VMware.VimAutomation.Core, @{ModuleName="VMware.VimAutomation.Core";ModuleVersion="<IP_ADDRESS>"}

I'm not super familiar with GitHub, but I think that I changed this pull request to use that #Requires statement and the join-path (get-installpath) technique to populate pcliDll.


Warning when using Load_model_from_directory(dir)

"WARNING:tensorflow:Please fix your imports. Module tensorflow.python.training.tracking.data_structures has been moved to tensorflow.python.trackable.data_structures. The old module will be deleted in version 2.11."
I would like my scripts to not just stop working one day.

Closing as it's already covered by #56.


[WIP] Commands to generate tx volume

Use-cases include load-testing networks.

Interesting but ultimately out of scope for this tool


feat: Select Menu Component

Select Menu Component Documentation

[x] Types
[x] Context
[ ] Tests
[ ] Documentation
[ ] Additional

[ ] DMMessageComponentRequestData changes to reflect on GuildMessageComponentRequestData

ComponentActionRow#components has been modified as per the spec of this component, which states:

An Action Row can only contain one select menu
An Action Row containing a select menu cannot also contain buttons

That said, I would expect changes to be suggested on this if this is considered as conflicting behaviour.
Changelog
Added

Types ComponentSelectMenu and ComponentSelectOption are exported to the index
ComponentActionRow now accepts an overload of a single ComponentSelectMenu
Added SELECT to enum ComponentType
Added ComponentSelectMenu as a component alternative of AnyComponent

It looks pretty good so far, the interaction data should be accessible through ComponentContext.

Note: I couldn't get the overload for a single ComponentSelectMenu to work properly without errors.


fix: heartbeatTimer canceled on both socket status closed and disconnnected

What kind of change does this PR introduce?
Fixes a memory leak problem that was caused by the heartbeatTimer not being canceled when the user called socket.disconnect().
What is the current behavior?
heartbeatTimer is not being canceled when the user calls socket.disconnect().
What is the new behavior?
heartbeatTimer is canceled on both when the user calls socket.disconnect() and when socket closes unexpectedly.

so fast @dshukertjr


[WIP] Feature: Task resiliency

Problem
In the current implementation:

Failure to schedule a task will terminate the workflow.
-- A Task scheduling can fail when failing to persist the task, or pushing the taskId to Task Queues.
A task could remain stuck if the persistence layer and queuing layer doesn’t agree:
-- For eg: if the relevant message is lost in the Task queue.

Solution
The process for scheduling a task would remain the same as now:

Task status is set as SCHEDULED, and persisted.
Task is pushed to the Task queue.

In this PR, if Step 1 fails, we'll continue to terminate workflows (which is the existing behavior). If Step 2 fails, The next run of sweeper fixes the inconsistency by verifying the state of the message in the Queue. I.e if the Task is in SCHEDULED state, but a relevant message is not found in the Queue (including those messages in invisible state), a new message will be pushed.
A new WorkflowRepairService has been introduced, that checks non-terminal workflow and task state with message in queue, and performs necessary actions as required. This will be called from Sweeper service.
Todos

[ ] Verify this in a beta release.
[ ] Introduce on/off feature for WorkflowRepairService, or ensure all QueueDAO implementations can confirm to QueueDAO's containsMessage.
[ ] Verify the complications in running WorkflowRepairService for Step 1 failure above, especially when creating a group of tasks together like Fork-Joins, Decision etc. Verify the semantics of getNextTask, if we were to make scheduling tasks deterministic, instead of considering roll back mechanisms.

Pull Request Test Coverage Report for Build 4442

68 of 70 (97.14%)  changed or added relevant lines in 8 files are covered.
30 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.08%) to 69.297%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core/src/main/java/com/netflix/conductor/core/execution/WorkflowRepairService.java
21
23
91.3%

Files with Coverage Reduction
New Missed Lines
%

es5-persistence/src/main/java/com/netflix/conductor/dao/es5/index/ElasticSearchRestDAOV5.java
3
75.39%

core/src/main/java/com/netflix/conductor/core/execution/WorkflowSweeper.java
4
80.7%

postgres-persistence/src/main/java/com/netflix/conductor/dao/postgres/PostgresQueueDAO.java
5
91.74%

cassandra-persistence/src/main/java/com/netflix/conductor/dao/cassandra/CassandraEventHandlerDAO.java
8
68.42%

cassandra-persistence/src/main/java/com/netflix/conductor/dao/cassandra/CassandraMetadataDAO.java
10
55.44%

Totals

Change from base Build 4419:
-0.08%

Covered Lines:
12639

Relevant Lines:
18239

💛  - Coveralls


OCR0002: Peytsuk Training data from annotation transfer (4)

Description:
We have Pecha images from BDRC of Nyingma Gybum with Peytsuk font or scripts, we need to create those into training data to do so we have to do:

OCR the images, use OCR output to get the etext with line annotations
Get the clean text of the volume, transfer the line annotations from the OCR data to clean text.
Use the Eric's line segmentor model to segment the line images and map it to the clean text with line annotations each line
upload the line images to s3 and create csv with line images object key and its line text.
Give them to annotators to be reviewed

Completion Criteria:

We should have Nyima Gybum peytsuk line images and its text for training data.
pipeline to use that for other works in the future.

Implementation plan:
Implementation without line image co-ordinates

Implementation with line image co-ordinates

Subtask:

[x] OCR to text and remove annotations from cleaned text
[x] Transfer page annotations and line annotations from source to target
[x] Map page images to the page text
[x] Use line detection model to predict lines
[x] Use the co-ordinates to crop the images
[x] map line images to the line text
[ ] create csv of the mapping and upload the images to s3

Need to include the line segmentation in the final pipeline but for the start get the Nyima Gybum data ready using the co-ordinates provided in the xml files

the models are also available are in here https://github.com/OpenPecha/monlam_ocr/releases

In batch 23, there are 760 images. from there 584 were successfully cropped and mapped. and uploaded to monlam.ai.ocr/line_to_text/batch23/.

For filtering out the wronged cropped images, new repo monocheck has been coded.
referenced from  reference.
successfully filtered the wronged cropped images(Majority). Below are some of the examples.

For batch 23, there are still 30 case where no of images > no of line texts, and while observing those, majority of the cases are where for particular line image, it was cropped into two.
Below is an example where the last line image is splited into two cropped images by the line detection model.

So for this cases, to match the no images to no line texts, we took the cropped images by images size in an increasing order.
For eg: if no of cropped images = 6 and no of line texts = 5.  we took the  5 cropped images which has the larger image size.

And for 4 cases, where the no of texts > no of line images, manual correction has been done.
ocr_output/I1KG812750082, images: 6, texts: 7
ocr_output/I1KG812750162, images: 6, texts: 7
ocr_output/I1KG812750551, images: 6, texts: 7
ocr_output/I1KG812750762, images: 1, texts: 2

for batch24, there were 6 mismatches
ocr_output/I1KG812760059, images: 6, texts: 7
ocr_output/I1KG812760121, images: 5, texts: 6
ocr_output/I1KG812760125, images: 6, texts: 7
ocr_output/I1KG812760133, images: 1, texts: 2
ocr_output/I1KG812760658, images: 6, texts: 11
and 13 empty images.


Basic design description for the gui

Summary
Give a basic description how the Gui should look and act.
Description
For easier implementation and consultation, the design of the GUI app should be discussed and recorded in this ticket.
Acceptance Criteria
Which criteria has to be reached to be accepted

[ ] The design has been described (text or image)
[ ] The behavior was described (text or flowchart)
[ ] All developers agree with the design
[ ] The design is considered feasible.

Tasks
Which tasks are included to add this feature

[ ] Create a basic app design
[ ] Describe the expected behavior of the GUI
[ ] Discuss the results with the other developers.

Dependencies
Which dependencies are introduced to the project

[ ] Dioxus

Estimates
4 hours
Additional Information
None

** GUI process: **

Start the application: The user starts the GUI.
Selection of send or receive: The user selects between send or receive.
If "Send" is selected:

The user can select the files to be sent using drag & drop or file picker.
The user clicks on "Send".
The screen changes and the user sees a name for the transfer and a matching QR code.
The transfer is carried out and a progress bar is displayed to the user.
Once completed, the user will see that the transfer was successful.

When "Receive" is selected:

The user has an input field for the transfer name or the option to scan a QR code.
The user clicks on "Start transfer".
A progress bar is displayed to the user during the transfer.
The user is shown that the transfer was successful.

Sender GUI:

Receiver GUI:

Since we are short on time, I would just close this ticket and we will decide which design to use based on a simple A/B test.


Query params shouldn't accept Record<string, unknown>

Description
The lib is generating a union with Record<string, unknown> for query parameters, which doesn't throw type errors when the query schema changes.

If one doesn't set any query parameters in the schema, it should have type never.
If one sets query parameters, it should only accept the configured schema.

I realized it also happens for body if it isn't defined (check the sample code). I think it should be never when it isn't defined.
Maybe add a configuration like --use-never to default any unset value to never.
Reproducible example or configuration
Check App.tsx:73
https://stackblitz.com/edit/hey-api-client-fetch-example-ssbzuv?file=src%2FApp.tsx&view=editor
OpenAPI specification (optional)
Use the example above.
System information (optional)
@hey-api/openapi-ts: v0.53.6

Hi @jpenna, can you try with the experimental parser? I think it might be fixed there https://heyapi.dev/openapi-ts/configuration.html#parser

@mrlubos Will try it on Monday!

Hello @mrlubos , I just upgraded to the latest version 0.53.12 and added the option for the parser (it is actually experimental_parser with underscore, according to the types).
But it is still including the Record<string, unknown>
 path: Record<string, unknown> & {
    threadId: string;


Decode response.content

HttpResponse.content is binary data, but code usually assumes it to be text.
Fix that by using response.content.decode('utf-8') instead of response.content where appropriate.

Automated message from Dropbox CLA bot
@sharmaeklavya2, it looks like you've already signed the Dropbox CLA. Thanks!

For these:
self.assertEquals(result.status_code, 200)
self.assertIn(u"Let's get started…", result.content.decode('utf-8'))

I think we should convert these all to use a new test helper function that's something like this: self.assert_html_success(u"Let's get started") (with maybe a self.assert_html_error(400, u"Let's get started") as well for ones where the goal isn't success).
That'd be a lot cleaner and I think more likely for folks to write new tests correctly in the future.

We'll also need to pass in the HttpResponse object to self.assert_html_success.
I think the methods should be named self.assertInResponse and self.assertEqualResponse, corresponding to self.assertIn and self.assertEqual respectively. We'll use it like this:
self.assertEqualResponse(u"Some text!", response)

We can also add a third optional parameter status_code.

Sounds good!

Done.

Merged, thanks @sharmaeklavya2!


Add max_stream_count parameter to read_gbq

We had discussed here that adding max_streams_count as a parameter might be confusing, and it seemed to me at the time that you'd probably always want as many streams as possible so why bother?
But I have a use case now where requesting too many streams is a problem: we have a microservice that loads data from BQ storage (say 10GB or so), and I'm using dask_bigquery.read_gbq to speed up the load using local threads. But as I scale the number of replicas of this service, I've started running into BQ storage quota issues; there's no benefit in this case to using hundreds of streams, a dozen or so would be just as good and save me from this quota headache.
It's probably an unusual situation but I think it's compelling enough that adding the argument does seem worth it after all.

@bnaul this seems reasonable to me, I'll take a deeper look but CI was crushing bad. I just fixed the GHA that is causing all the Ci to fail and merged it to main. Can you merge main into your branch so we trigger the CI with the fix?

@ncclementi rebased and all looks happy now, thanks for fixing!


Fix moveit_core unit tests

Description
The reason why the unit tests are failing is that when we add ament_add_gtest the timeout default is 60s which is lower than what running the unit tests takes, for the tests that take more than 60s I set the timeout to the ctest default value which is 1500s
Checklist

[ ] Required by CI: Code is auto formatted using clang-format
[ ] Extended the tutorials / documentation, if necessary reference
[ ] Include a screenshot if changing a GUI
[ ] Document API changes relevant to the user in the moveit/MIGRATION.md notes
[ ] Created tests, which fail without this PR reference
[ ] Decide if this should be cherry-picked to other current ROS branches
[ ] While waiting for someone to review your request, please consider reviewing another open pull request to support the maintainers

Now all the tests pass, but Travis is failing due to moveit_core warnings, please see

The reason why the unit tests are failing is that when we add ament_add_gtest the timeout default is 60s which is lower than what running the unit tests takes, for the tests that take more than 60s I set the timeout to the ctest default value which is 1500s

Wow, the tests really take 17min total to finish in Travis. On my local machine its <20s. I think 1500s is still way too much for each test. The default for catkin_add_test was also 60s so there must be something wrong when running it in Travis.

In my local machine, it takes about 10 minutes for the 3 tests that I added the timeout to them

In my local machine, it takes about 10 minutes for the 3 tests that I added the timeout to them

colcon test --packages-select moveit_core takes 10 minutes? Anyway, 60s for each test should be enough, even in that case

This's what I get, it timeout after 60s


Support empty subgraph names

Example test case:
flowchart
    subgraph B[ ]
    V1(Visitor 1)-.->Hey[Server]
    end

flowchart
    subgraph B[ ]
    V1(Visitor 1)-.->Hey[Server]
    end

Today, this causes console errors:
react-dom.development.js:4299 Uncaught TypeError: Cannot read properties of undefined (reading 'length')
    at isTransparent (utils.ts:603:34)
    at isElementDraggableFromInside (collision.ts:60:19)
    at isHittingElementNotConsideringBoundingBox (collision.ts:155:7)
    at hitTest (collision.ts:103:10)
    at eval (App.tsx:3090:14)
    at eval (comparisons.ts:67:40)
    at Array.filter (<anonymous>)
    at getElementsAtPosition (comparisons.ts:66:19)
    at App.getElementsAtPosition (App.tsx:3089:33)
    at App.getElementAtPosition (App.tsx:3037:33)

@punkeel I just tried this test case in playground and its working well

where are you seeing this error ?

The error occured on https://mermaid-to-excalidraw.vercel.app/
I can confirm this is working now 👍  - thanks!


R-T3.4-11: The tool must decrease bug-fixing times with respect to manual inspection

ID
R-T3.4-11

Section
WP3: Methodology and Quality Assurance Requirements

Type
PERFORMANCE_EFFICIENCY

User Story
As an Operations Engineer I want the tool to decrease the time to inspect the infrastructure manually considerably

Requirement
The tool must diminish the time to detect defects with respect to manual inspection by at least 20%

Priority
Must have

Affected Tools
DEFECT_PRED_TOOL

Means of Verification
User study with time improved by at least 20%

Dependency
R-T3.4-10 https://github.com/radon-h2020/radon-defect-prediction-api/issues/5

@maelstromdat @dardin88 (TDJ) @sdagostini (ENG) @naesheim (PRQ) I think we have to design the industrial case studies keeping in mind this must-have requirement.

@gcasale
Similar to issue #5, this requirement will take time to be addressed. We are designing industrial cases studies with ENG and PRQ to address it.

Removed.
First, the requirement partially overlaps R-T3.4-10 (#5), which states that the defect-prediction tool must improve performances over manual inspection. Second, the bug-fixing time is a developers’ concern rather than the defect predictor tool and depends on their ability to find a fix for a given bug. As the defect-predictor is essentially a detector, we stick with the requirement R-T3.4-10 to improve the performance in identifying defects during manual inspection.

Closed state approved.


Offseason2022: Change drive encoders to use an offset instead of reset to zero

We currently read Talon FX drive encoders for left and right sides by doing a getSelectedSensorPosition of the exact position. We depend on these encoders to be reset to zero using setSelectedSensorPosition when we initialize the drivetrain or enter disabledinit, so our auton routines work correctly.
Using setSelectedSensorPosition is known to require a significant delay before the encode will actually report the updated sensor value--in this case zero.
We should change our resetEncoders() method to read the sensor using getSelectedSensorPosition and calculate its offset from zero. Then in getDistanceMetersLeft/Right() apply that offset to the encoders to get the correct value.
The resetGyro function already does this in the drivetrain subsystem.

@reevar24 did a great first implementation, but needs to fix a single bug to make it work right.

Fixed in other merge


New Project: Study Timer and  Scheduler

I would like to add a Web Application which, would have the following features:
Allows you to set your session length and break length
Allows you to change your study session time, break length the effect is noticed dynamically in the session clock
It prevents you from resetting your break time  and  you can't extend your break periods
There is a single slot allocated for both session and break timers, once the session timer hits 00:00 the break timer automatically gets started and it replaces the session timer in place
The time is displayed along with the name of the current state of the session on the title bar of the webpage so that the user can keep track of his time even when he is on another page
Please assign me this issue under GSSoC 2021

@guruc-134 go for it :)

@urvashi-code1255  Thank, you

@urvashi-code1255
Current Progress:
-->completed the timer
-->added the planner
--> completed dropdown bar.
current website look:-  https://guruc-134.github.io/Pomodoro-Timer/
I'm also planning to add a local storage feature so that in that way the user will not loose his session progress if the tab is closed
Im also planning to add an alternate theme and alternate font option for the page
could you review the changes and let me know if there are any suggestions?

@urvashi-code1255  once check it out I have made a pull request once check it out


strat_name_id 2398 format - no geometry?

$ curl -k https://macrostrat.org/api/v2/geologic_units/map?strat_name_id=2398format=geojson_bare > 2398.geojson
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 76.5M  100 76.5M    0     0  1202k      0  0:01:05  0:01:05 --:--:--  639k

Lots of stuff, but no geometry - something different about this one?
{
  "success": {
    "v": 2,
    "license": "CC-BY 4.0",
    "data": [
      {
        "map_id": 1936270,
        "source_id": 22,
        "name": "Pikeville Formation",
        "strat_name": "Pikeville Formation",
        "lith": "sandstone | shale | silty shale | siltstone | coal  | underclay",
        "descrip": "Sandstone, shale, silty shale, siltstone, coal, and underclay: Sandstone, light-gray; weathers buff, very fine to medium grained, thick bedded to massive, micaceous; includes large ellipsoidal calcareous sandstone concretions; forms prominent bench in northwestern part of quadrangle; grades laterally into medium- to dark-gray shale, silty shale, and siltstone with large ellipsoidal silty limestone concretions.  Thin coal bed with medium-gray plastic underclay converges northwestward with overlying Fire Clay coal bed. \\nCoal, thin, banded; truncated at base of overlying sandstone throughout most of the quadrangle. \\nShale, sandstone, and underclay: Mostly shale, medium- to dark-gray; contains few small ellipsoidal to round siderite nodules; locally includes one or two thin beds of light-gray very fine to fine-grained micaceous sandstone.  Underclay at top is plastic and light to medium gray. \\nCoal, dull and bright attritus, banded; truncated at base of overlying sandstone in the northern part of the quadrangle. \\nSandstone, shale, silty shale, and underclay: Sandstone, light-gray, very fine to fine-grained, thick-bedded to massive, micaceous; forms cliff locally; grades laterally into medium-gray silty shale.  Shale, medium- to medium-dark-gray; contains small ellipsoidal siderite nodules.  Unit includes persistent zone of large ellipsoidal concretions of calcareous sandstone or silty limestone.  Underclay at top of unit is light to medium dark gray, plastic; contains abundant fossil rootlets. \\nCoal, dull to bright attritus with sparse vitrain bands and a few discontinuous fusain laminae; thins northwestward and locally consists of a few inches of impure coal overlain by 1 to 3 inches of black carbonaceous shale. \\nShale, sandstone, and underclay: Mostly shale, medium- to medium-dark-gray; with interbeds of light-gray very fine to fine-grained thin- to thick-bedded micaceous sandstone in the lower and upper parts of the unit.  Underclay at top is medium gray, as much as 2 feet thick; contains abundant elongate siderite nodules at base and fossil rootlets throughout. \\nCoal, predominantly bright attritus; thin but persistent bed. \\nShale, sandstone, coal, and underclay: Mostly shale, dark-gray to black, carbonaceous; comprises widespread bed in upper part of unit; includes siderite bed as much as 11 inches thick at base.  Shale in lower part of unit is medium to medium dark gray but basal beds are distinctly grayish red locally and in places include a ferruginous or calcareous bed with marine fossils.  Sandstone, very light gray to light-gray, very fine to medium-grained; bed in lower part is quartzose in the northwestern part of area, thins southeastward and grades into micaceous very fine to fine-grained argillaceous sandstone.  Underclay is clayey to silty and about 1 foot thick.  Coal thins northwestward and only underclay is present locally.",
        "comments": "Ppk; Sandy Hook Quadrangle (GQ-521) | http://kgs.uky.edu/kgsweb/PubsSearching/MoreInfo.asp?titleInput=726 | Map description and column: http://kgs.uky.edu/kgsmap/kgsgeoserver/geolDescID.asp?idType=pointID&fmcode=324PKVL&gq_num=521&map_level=24K",
        "macro_units": [],
        "strat_names": [
          64789
        ],
        "liths": [
          8,
          9,
          10,
          38
        ],

Hi @RichardScottOZ there are several query paths that occur on the "geologic_units" route depending on what exactly is being searched for. One of those for linking many map_id together by strat name apparently does not properly implement the geojson output types. This is clearly a bug; unfortunately we likely won't fix it because those API queries would be incredibly costly on our servers and return voluminous data (in some cases, single strat names are linked to hundreds or thousands of polygons across tens of maps).
Searching for each map_id individually will return polygons, or using our newer vector tile endpoints (see demo interface in #56) can form a stopgap; we are working on filterable vector tile endpoints as well.

Thanks daven.


Question: Is there a health check URL for Registry V2

The V1 Registry had /_ping for the purposes of health check. Is there something similar available in V2? This is needed for putting the servers behind ELBs etc.

@diptanu go with the health check endpoints: https://github.com/docker/distribution/blob/master/docs/configuration.md#debug

@diptanu The standard "/v2/" endpoint should be sufficient. This requires authentication. If they respond with 401 or 200, you can safely assume the registry is up.
There is also the "/debug/health" endpoint. This is meant to be an internal health check endpoint running on a separate port and application. Note that there may some more work before this becomes a full recommended approach. It is not necessarily recommended to make this available over any unsecured network.

@diptanu closing this for book keeping. Let us know if you need more here.

It would be great if there was an easy way to put a docker registry behind an AWS Elastic Load Balancer, when authentication is enabled.
The AWS ELB HTTP health check[1] is quite limited. It is only successful when a response code of 200 OK is returned. It does not support authentication for health check HTTP GET requests.
When authentication is enabled in the docker registry, there aren't any endpoints that respond with 200 OK from an anonymous HTTP GET. We then need to fall back to a proxy that does authentication, that can expose an anonymous endpoint for health, or a lower layer health check such as the ELB TCP health check.
We had a look at the debug server, but from looking at the source, it doesn't seem to give much confidence the registry itself is working.
It would be very helpful if there was an endpoint that gave a strong indication of health, that could be accessible from an anonymous HTTP/HTTPS GET, that would be available even when authentication is enabled.
[1] http://docs.aws.amazon.com/ElasticLoadBalancing/latest/APIReference/API_HealthCheck.html

We had a look at the debug server, but from looking at the source, it doesn't seem to give much confidence the registry itself is working.

Several items can be accessed, such as expvar, pprof and the health endpoint. The output of expvar is a great indication of registry health. Right now, unfortunately, /debug/health is not attached to much, so it only indicates whether or not the service is up. We don't recommend exposing this a load balancer, but it can be used as such.
Serving the debug endpoints to a load balancer presents a security risk and exposing an unauthenticated endpoint under registry APIs is a non-option (perhaps, we may consider a /health endpoint but the necessity is dubious). The right solution is to have the health checks gate the entire service and return a 503 on failure. Unfortunately, the AWS ELB design makes a very poor assumption in assuming that 200 OK is the only indication of health. For a registry with authentication, a 401 Unauthorized return code on an unauthenticated response is very healthy.

Thank you@stevvooe for PR #874. This will suit our load balancing needs nicely.

401 Unauthorized doesn't integrate well with tooling such as Hashicorp Consul which will interpret 401 as down. I also don't want to bake credentials into the health check definition, as it goes against the principle of least privilege.


Add Full-TCP test suite

Description
This PR adds the Full-TCP test suite present in amazon-FreeRTOS repository after some modifications to the FreeRTOS/FreeRTOS repository. This is a part of a range of additions to the FreeRTOS/FreeRTOS repository to enhance the testing capabilities of this repository. The specific modifications are listed below:

The Full-TCP test suite uses the Secure-Socket abstraction whereas the tests being added just use FreeRTOS_Sockets since Secure Sockets is not a part of FreeRTOS/FreeRTOS.
The test names have been changed to reflect the above changes. The names follow this convention: TCP_Sockets_<name of function>_<TestCase>.
The test case execution order has been changed to make sure that a functionality (e.g. 'FreeRTOS_send') is tested before it is used in some other test-case.

Note For reviewers: Important changes are restricted to only 2 files, namely: FreeRTOS_Sockets.c and test_tcp.c. (Other files are just additions to the project)
OR
You can try running the demo on your local setup.
Test Steps

Clone the Repository with --recurse-submodules.
Go to 'FreeRTOS-Plus/Test/FreeRTOS_Plus_TCP_Integration_Tests/Full-TCP_tests' directory.
NOTE: You'll need an active ethernet connection and probably need to switch off any VPN service.
Open the Full-TCP-tests project.

Change the interface to use by modifying the 'configNETWORK_INTERFACE_TO_USE' define.
Change the tcptestECHO_SERVER_ADDR[0-3] and tcptestECHO_PORT in test_tcp.h to reflect the address of your echo server.
Save the changes.

Compile and run the project. It should run 23 tests which should all pass.

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

Closing this PR to incrementally add changes.
Will Split the PR into multiple smaller PRs.


Firebase Performance + Kotlin/Native crashes trying on http request in InstrumentSessionWithConfigurationDelegateDelegateQueue

[REQUIRED] Step 1: Describe your environment

Xcode 12.1
Firebase 7.0.0
Carthage

[REQUIRED] Step 2: Describe the problem
This is the same problem: https://github.com/firebase/firebase-ios-sdk/issues/2626
thread #1, queue = 'com.google.FPRNSURLSessionDelegateInstrument', stop reason = EXC_BAD_ACCESS (code=1, address=0x5fff8c1e8988)
    frame #0: 0x000000010783f228 CircletEAP`BackRefFromAssociatedObject::releaseRef() + 8
    frame #1: 0x000000010627a2d4 CircletEAP`-[GULObjectSwizzler swizzle] + 199
    frame #2: 0x000000010628f8ab CircletEAP`__52-[FPRNSURLSessionDelegateInstrument registerObject:]_block_invoke + 886
    frame #3: 0x000000010cc8ca88 libdispatch.dylib`_dispatch_client_callout + 8
    frame #4: 0x000000010cc9bcac libdispatch.dylib`_dispatch_lane_barrier_sync_invoke_and_complete + 132
    frame #5: 0x000000010628f50d CircletEAP`-[FPRNSURLSessionDelegateInstrument registerObject:] + 116
  * frame #6: 0x00000001062916b0 CircletEAP`__InstrumentSessionWithConfigurationDelegateDelegateQueue_block_invoke + 175
    frame #7: 0x000000010647af9f CircletEAP`kfun:runtime.net.Http.$doRequestCOROUTINE$658#invokeSuspend(kotlin.Result<kotlin.Any?>){}kotlin.Any? [inlined] <anonymous> at Http.kt:91:36
    frame #8: 0x000000010647ab32 CircletEAP`kfun:runtime.net.Http.$doRequestCOROUTINE$658#invokeSuspend(kotlin.Result<kotlin.Any?>){}kotlin.Any? [inlined] <anonymous>_1 at Http.kt:140
    frame #9: 0x000000010647aa99 CircletEAP`kfun:runtime.net.Http.$doRequestCOROUTINE$658#invokeSuspend(kotlin.Result<kotlin.Any?>){}kotlin.Any? [inlined] suspendCoroutineUninterceptedOrReturn at Coroutines.kt:14
    frame #10: 0x000000010647aa6c CircletEAP`kfun:runtime.net.Http.$doRequestCOROUTINE$658#invokeSuspend(kotlin.Result<kotlin.Any?>){}kotlin.Any? [inlined] suspendCancellableCoroutine at CancellableContinuation.kt:189
    frame #11: 0x000000010647aa6c CircletEAP`kfun:runtime.net.Http.$doRequestCOROUTINE$658#invokeSuspend(_this=0x0000600003557f68, result=0x00000001080fe798){}kotlin.Any? at Http.kt:41
    frame #12: 0x000000010647ca2a CircletEAP`kfun:runtime.net.Http#doRequest(_this=0x0000600004cce2b8, method=0x00006000054b2c28, url=0x0000600003556f48, parameters=0x0000600003557428,

Steps to reproduce:
Use Ktor Http or just bare NSURLSession in Kotlin/Native with the Firebase Performance enabled.

Is there any way to disable only HTTP requests part of Firebase Performance?

@ptmt Sorry about the trouble. This looks like a duplicate of #6930. See the discussion there.

7.1.0 is now out. I'm going to close here. Please follow up if you find that it doesn't solve the crash.

It doesn't work with the 7.1.0, still crashes. Also, I'm not quite sure it's related to https://github.com/firebase/firebase-ios-sdk/issues/6930.
It probably should be fixed on the Kotlin/Native side https://youtrack.jetbrains.com/issue/KT-42482. At the moment, I would like to overcome it and disable HTTP logging, but as far as I understand, it's not possible.

Thanks for the follow-up. I'll reopen.

Possible root cause: swizzler ignores indexed ivars of class objects: https://github.com/firebase/firebase-ios-sdk/blob/eb21690b803cbbad83a8ad2fa51d43fd1f3fa2b4/GoogleUtilities/ISASwizzler/GULObjectSwizzler.m#L95
Kotlin/Native runtime makes classes with indexed ivars here: https://github.com/JetBrains/kotlin-native/blob/4633b4ae2789065364ca839c8bfcda530587cad9/runtime/src/main/cpp/ObjCInterop.mm#L245

@ptmt URL requests instrumentation may be temporary disabled with isDataCollectionEnabled property. Note that it disables other metrics requiring swizzling.

@SvyatoslavScherbina Thank you for the idea!
Based on the docs the extraBytes parameter affects only the newly created subclass, so this part looks correct to me for both GULObjectSwizzler and ObjCInterop.
Based on the stack trace it looks like the func BackRefFromAssociatedObject::releaseRef() is called when GULObjectSwizzler tries to store the swizzled object ling to the associated property here. I didn't dive too deep into Kotlin code, but the crash may happen because of an attempt to deallocate an old value of the associated property which is nil which leads to the EXC_BAD_ACCESS because nil may be not checked somewhere on the way. BTW, the nullptr check was added a couple month ago, so I curious if the issue may've been already fixed on the Koltin side?

@maksymmalyhin

Based on the docs the extraBytes parameter affects only the newly created subclass, so this part looks correct to me for both GULObjectSwizzler and ObjCInterop.

I guess I wasn't entirely correct. I meant that Kotlin runtime (including releaseRef) expects object's class to have these extra bytes filled with data, while swizzler breaks this expectation. Generally these classes created by Kotlin runtime aren't supposed to be subclassed at all. So it is probably not a bug in swizzler, but rather expectations mismatch.

Based on the stack trace it looks like the func BackRefFromAssociatedObject::releaseRef() is called when GULObjectSwizzler tries to store the swizzled object ling to the associated property here. I didn't dive too deep into Kotlin code, but the crash may happen because of an attempt to deallocate an old value of the associated property which is nil which leads to the EXC_BAD_ACCESS because nil may be not checked somewhere on the way. BTW, the nullptr check was added a couple month ago, so I curious if the issue may've been already fixed on the Koltin side?

Not sure about this, see explanation above. Copying indexed ivars from old class to new one fixes the issue.
Anyway, we consider fixing this on our side, but no ETA yet.

@SvyatoslavScherbina Thank you for the explanation.
Unfortunately my knowledge about objc_allocateClassPair method is mostly limited to the public docs, so I may miss some details. I was pretty sure that  if objc_allocateClassPair is called on another class that leverages the indexed properties then the extra bytes should be automatically taken  into account. If it is not the case, do you have any suggestion on how GULObjectSwizzler may be modified to account for the extra bytes? I could not find any Objective-C runtime API for this, but I may be missing something.

I was pretty sure that if objc_allocateClassPair is called on another class that leverages the indexed properties then the extra bytes should be automatically taken into account

I'm not sure about this. My experiments show that this is not the case: https://gist.github.com/SvyatoslavScherbina/a5dfaf1d567ae9fdb8f8b1d83d44a61c

If it is not the case, do you have any suggestion on how GULObjectSwizzler may be modified to account for the extra bytes?

I'm not sure that there is a more correct way of handling the extra bytes than the current one. I guess having indexed ivars in class objects is quite uncommon, and there aren't enough cases to make proper decision here.

I could not find any Objective-C runtime API for this, but I may be missing something.

Me neither, the same.

@SvyatoslavScherbina Thank you for provided details.
As far as I understand the current Kotlin ObjCInterop is incompatible with ISA swizzling (and potentially with KVO, because as far as I know KVO relies on kind of ISA swizzling internally). As Firebase Performance network measurements rely on ISA swizzling, it has to be disabled (with isDataCollectionEnabled) until the Kotlin Objective-C interop implementation changed.
@SvyatoslavScherbina As far as I understand, the indexed properties are used to store KotlinClassData for an Objective-C object. I wonder if associated objects can be used instead? Anyway could you please keep the thread posted and let us know if we can help with anything.

As far as I understand the current Kotlin ObjCInterop is incompatible with ISA swizzling (and potentially with KVO, because as far as I know KVO relies on kind of ISA swizzling internally).

Yes, this particular code appears to be incompatible with ISA swizzling.

As far as I understand, the indexed properties are used to store KotlinClassData for an Objective-C object. I wonder if associated objects can be used instead?

Performance concerns.

Anyway could you please keep the thread posted and let us know if we can help with anything.

Thanks! Sure. But, as I've already mentioned above, I don't think it is possible to fix this problem on your side.

JFYI: we fixed this on Kotlin/Native side.

@SvyatoslavScherbina That's great news! I’m really curious to see what the fix you decided on.

@maksymmalyhin https://github.com/JetBrains/kotlin-native/pull/4569

@SvyatoslavScherbina thank you for sharing. I'll note this approach for the future.

I'm closing Firebase issue based on the fix on Kotlin/Native side.


'Cannot find module' in heroku deploy

I have followed instructions in the heroku branch and read through prior issues, but I cannot figure out why my heroku deployment keeps crashing.
I have:

confirmed the heroku branch works by deploying it
tested using a Procfile with web: npm run build and web: npm run start as another issue suggested
confirmed that npm run build, npm start with a PORT specified in packages.json, and npm run dev works fine
double-checked all the heroku configs match the docs in the heroku branch.

Am I missing something obvious?
Error message:
Jan 22 23:43:11 aditive-frontend-staging app/web.1:  [0] ><EMAIL_ADDRESS>start-prod /app
Jan 22 23:43:11 aditive-frontend-staging app/web.1:  [0] > better-npm-run start-prod
Jan 22 23:43:11 aditive-frontend-staging app/web.1:  [0]
Jan 22 23:43:11 aditive-frontend-staging app/web.1:  [0] running better-npm-run in /app
Jan 22 23:43:11 aditive-frontend-staging app/web.1:  [0] Executing script: start-prod
Jan 22 23:43:11 aditive-frontend-staging app/web.1:  [0]
Jan 22 23:43:11 aditive-frontend-staging app/web.1:  [0] to be executed: node ./bin/server.js
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0] module.js:338
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     throw err;
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     ^
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0] Error: Cannot find module './campaign/Campaigns'
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at Function.Module._resolveFilename (module.js:336:15)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at Function._module3.default._resolveFilename (/app/node_modules/webpack-isomorphic-tools/node_modules/require-hacker/babel-transpiled-modules/require hacker.js:403:34)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at Function.Module._load (module.js:286:25)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at Module.require (module.js:365:17)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at require (module.js:384:17)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at Object.<anonymous> (/app/src/containers/index.js:15:20)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at Module._compile (module.js:434:26)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at normalLoader (/app/node_modules/babel-core/lib/api/register/node.js:199:5)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at require.extensions.(anonymous function) (/app/node_modules/babel-core/lib/api/register/node.js:216:7)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0]     at Object._module3.default._extensions.(anonymous function) [as .js] (/app/node_modules/webpack-isomorphic-tools/node_modules/require-hacker/babel-transpiled-modules/require hacker.js:250:71)
Jan 22 23:43:20 aditive-frontend-staging app/web.1:  [0] npm run start-prod exited with code 0
Jan 22 23:43:20 aditive-frontend-staging heroku/web.1:  Process exited with status 0
Jan 22 23:43:26 aditive-frontend-staging heroku/web.1:  State changed from starting to crashed

Apparently, I did miss something obvious: that lowercasing a filename from multiForm.js to multiform.js does not actually show up in git status.


Fix missing subscription bug max subs change

Context
Unreverted the change to fix the max subscription bug. The issue with this code is that it does not recognize the stream named __default__ coming from the job subscription map. Previously this was hidden by duplicate record keeping. The simplest possible change is to just treat __default__ as defaultStream when looking up existing subscriptions. However this calls for a larger discussion around:

Sundaram's idea of introducing a data structure to represent Stream keys.
Calvin's proposal to remove streamName from propagateSubscriptionChanges altogether and simply have it manage all streams at once.

The relevant code is in 6f0dd7ce8aa0f82c3d865ce0cca17473167e8475.
Checklist

[x] ./gradlew build compiles code correctly
[x] Added new tests where applicable
[x] ./gradlew test passes all tests
[x] Extended README or added javadocs where applicable
[x] Added copyright headers for new files from CONTRIBUTING.md

Nice find @codyrioux 😄

Thanks @jeffchao but credit goes to Calvin for the original bug find, this one just fixes a performance issue with the fix.
I think I have the smallest possible change that will work here but am considering some larger changes this afternoon.

Some flaky tests that don't seem to be failing under a local gw clean build.

Does anyone know if there is a way to get at the /home/runner/work/mantis/mantis/mantis-control-plane/mantis-control-plane-server/build/reports/tests/test/index.html file so I can actually see what is happening on the CI server here?

Try download log archive to see if it contains the html file:

If you not, then only option is to try to reproduce locally.

The failing unit tests were caused by the gradle cache change on the main branch. Reverting it here appears to have fixed it, all subsequent commits are hit/miss if we re-run the validation checks.

The failing unit tests were caused by the gradle cache change on the main branch. Reverting it here appears to have fixed it, all subsequent commits are hit/miss if we re-run the validation checks.

@sundargates did you see this problem when you made the gradle cache change?

It seems intermittent. I re-ran the cache commit's validation three times with Attempt #2 and Attempt #3 failing but Attempt #4 succeeding. This branch passes with the revert.

Just played around with caching / parallel disabled but could only get success with both disabled.


Update Calico from v3.1.3 to v3.2.0

Manifest changes in https://github.com/poseidon/terraform-render-bootkube/pull/74

https://github.com/projectcalico/calico/pull/1884
https://github.com/projectcalico/calico/pull/1853
https://github.com/projectcalico/calico/pull/2069
https://github.com/projectcalico/calico/pull/2032
https://github.com/projectcalico/calico/pull/1841
https://github.com/projectcalico/calico/pull/1770

Typhoon publishes expected pod-to-pod network performance details. A Typhoon AWS v1.11.2 cluster with Calico v3.1.3 nearly saturates the link with ~980MB/s (950-1000MB/s) with 8981 MTU. Testing Calico v3.2.0, with both MTU 1480 and 8981 shows only 400-500MB/s.
This update is on hold.


In the new version I will add new options for water lilies. How are they to you?

In the new version I will add new options for water lilies
How are they to you?


Ast: Distiguish class/object methods with ordinary function expressions in FunctionType

The FunctionType enum already distinguishes function declarations and expressions. However, class methods and object methods are also considered to be function expressions, although they are different in some ways. For example:
const object = {
  fn: function(){},
  method(){}
}
object.fn.prototype     //=> {}
object.method.prototype //=> undefined

A possible solution is adding MethodFunction to the FunctionType enum.

Similar to: https://github.com/oxc-project/backlog/issues/142

This conforms to estree. The caller will need to figure out whether it's a function inside a class / object or not.

Personally, I don't think we need to conform to ESTree. Serialization can take care of translating our AST to ESTree-compatible AST. But I think it's fine to close this issue, as https://github.com/oxc-project/backlog/issues/142 is sufficiently similar.


Add docker files

Codecov Report
Attention: Patch coverage is 88.88889% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 82.56%. Comparing base (856bbd5) to head (6b60d95).
Report is 1 commits behind head on master.

 Share it here.


Standard Markdown linebreak support

As discussed in #1087, Ghost currently uses its own Markdown flavour that deviates from the spec by converting single line breaks to <br> tags.
While I understand that this probably enhances usability for those not familiar with Markdown, it does create interoperability problems for those that use Markdown in lots of places, or use external editors which does hard wrapping.
So I hope it would be possible to make this configurable, so Markdown-nerds can still be happy :neckbeard:

This feature makes it really annoying to work with blog posts in an external editor like Emacs.