Rails 6      ActionView::Template::Error  wrong number of arguments (given 2, expected 1)

Steps to reproduce:
Given I install fresh new Rails 6 project with RSpec and I write controller test as following:
# a/c/companies_controller
class CompaniesController < ApplicationController
  def show
    @company = Company.find(params[:id])
    render :show  # test will blow up at this point
  end
end

# spec/controller/companies_controller_spec.rb
require 'rails_helper'
RSpec.describe CompaniesController, type: :controller do
    it 'should load page' do
      get :show, params: { id: Company.create.id }  # doesn't matter what test is testing, it will fail with ActionView::Template::Error: wrong number of arguments (given 2, expected 1)  at his point
       # ....
    end
end

What Ruby, Rails and RSpec versions are you using?
Ruby version: 2.6.3
Rails version: 6.0.0
RSpec version:
bundle exec rspec --version

RSpec 3.8
  - rspec-core 3.8.2
  - rspec-expectations 3.8.4
  - rspec-mocks 3.8.1
  - rspec-rails 3.8.2
  - rspec-support 3.8.2

cat Gemfile.lock  | grep rspec

    rspec-core (3.8.2)
      rspec-support (~> 3.8.0)
    rspec-expectations (3.8.4)
      rspec-support (~> 3.8.0)
    rspec-mocks (3.8.1)
      rspec-support (~> 3.8.0)
    rspec-rails (3.8.2)
      rspec-core (~> 3.8.0)
      rspec-expectations (~> 3.8.0)
      rspec-mocks (~> 3.8.0)
      rspec-support (~> 3.8.0)
    rspec-support (3.8.2)
    spring-commands-rspec (1.0.4)
  rspec-rails
  spring-commands-rspe

related links

http://jessehouse.com/blog/2019/06/19/actionview-template-error-wrong-number-of-arguments-given-2/
https://github.com/rails/rails/issues/36315

so according to http://jessehouse.com/blog/2019/06/19/actionview-template-error-wrong-number-of-arguments-given-2/ if I replace
# Gemfile
gem 'rspec-rails'

with
  # Gemfile
  gem 'rspec-core', git: 'https://github.com/rspec/rspec-core'
  gem 'rspec-expectations', git: 'https://github.com/rspec/rspec-expectations'
  gem 'rspec-mocks', git: 'https://github.com/rspec/rspec-mocks'
  gem 'rspec-rails', git: 'https://github.com/rspec/rspec-rails', branch: '4-0-dev'
  gem 'rspec-support', git: 'https://github.com/rspec/rspec-support'

it will work
but the point is that Rails 6 is out some time => would be nice if I can just use gem 'rspec-rails'

:wave: Hi, yes 4-0-dev contains the version of rspec-rails with Rails 6 compatibility. It will be released soon but we are all volunteers.

@JonRowe  oh I see, sorry didn't want to push just thought there are some fixes prepared in 3.8.x version not released yet,  didn't know  they are in 4.0 only. No pressure ;)

When I try to add this to my Gemfile
gem 'rspec-rails', git: 'https://github.com/rspec/rspec-rails', branch: '4-0-dev'
I got error:
Revision 4-0-dev does not exist in the repository https://github.com/rspec/rspec-rails. Maybe you misspelled it?

The PR was merged, you can use master or 4.0.0.beta3 until the final version is released.

I got same problem.

This working for me
gem 'rspec-core', git: 'https://github.com/rspec/rspec-core'
gem 'rspec-expectations', git: 'https://github.com/rspec/rspec-expectations'
gem 'rspec-mocks', git: 'https://github.com/rspec/rspec-mocks'
gem 'rspec-rails', git: 'https://github.com/rspec/rspec-rails'
gem 'rspec-support', git: 'https://github.com/rspec/rspec-support'

Is there any ETA for when the "final version" is released? Having the same problem on a Rails 6 app.
My solution:
gem 'rspec-rails', git: 'https://github.com/rspec/rspec-rails', branch: "4-0-maintenance"

gem 'rspec-rails', 4.0.0.beta3 will work, waiting on a fix for a PR to release final


Daily Wisdom

A feature enhancement here could be that:
A “Daily Wisdom” section that presents a random or scheduled audio clip or quote from Chanakya Neeti.
Push notifications or email subscriptions for daily wisdom.

Full name: umashri
Contributor - SSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@MetiUmashri i'm confused where should i keep this feature on the website? And mention me your workflow to clarify this idea in my mind. You can discuss with me on discord server.


Add oidc login to vault

Signed-off-by: Brandon Mitchell<EMAIL_ADDRESS>
Summary

This adds the ability to login to vault using OIDC to get a token, and removes dependencies on environment variables.
I'm using this with Spire+OIDC to use Vault as a KMS without hard coding credentials in CI. Here's what that code looks like:
...
	kmsOpts := []signature.RPCOption{}
	rpcAuth := options.RPCAuth{
		Address: cfg.Auth.Address,
		OIDC: options.RPCAuthOIDC{
			Role: cfg.Auth.Role,
			Path: cfg.Auth.Path,
		},
	}
	jwtSource, err := workloadapi.NewJWTSource(
		ctx,
		workloadapi.WithClientOptions(workloadapi.WithAddr(cfg.Auth.Spire.Sock)),
	)
	if err != nil {
		return err
	}
	svid, err := jwtSource.FetchJWTSVID(ctx, jwtsvid.Params{Audience: cfg.Auth.Spire.Audience})
	if err != nil {
		return err
	}
	rpcAuth.OIDC.Token = svid.Marshal()
	kmsOpts = append(kmsOpts, options.WithRPCAuthOpts(rpcAuth))
	k, err := kms.Get(context.Background(), cfg.KMSRef, crypto.SHA256, kmsOpts...)
	if err != nil {
		return err
	}
...

Ticket Link

Fixes
Release Note

Adding ability to login to Vault using OIDC

Test cases are in the works for this. I've got them done for passing the vault token, address, and transit path. Just doing a bit more research on the oidc side to see if that can be easily added to the e2e tests.

@sudo-bmitch golangci-lint is complaining here https://github.com/sigstore/sigstore/runs/4951957521?check_suite_focus=true.

@hectorj2f yup, I got those fixed in https://github.com/sigstore/sigstore/commit/c1d6eb13d8b63c2707982233b10d18833935b8b4. Sorry for missing that in the first pass, I know better. I'll have another commit later today for e2e testing, so no need to rerun CI just yet.

Test cases added for the easy parts. I went down the path of trying to get a JWT out of Dex programmatically and started to hit a wall. If anyone has some go or shell code for that, I can add more tests for OIDC auth into vault.
This should be ready for CI @dlorenc

Double ack. I've now installed golint-ci so I can stop messing up that CI job.


(Migration) Reorganize step 4 data

After migration to auth-os we should display the source code and ABI of auth-os applications

Minted capped crowdsale:

Dutch Auction crowdsale:


Build error with Jenkins

I'm getting an error when I try and build with Jenkins. I've had it working up until I changed the settings for code signing following the guide for code signing and modifying the project.pbxproj file.
[23:26:08]: set -o pipefail && krausefx-ipa build -s "SyncSpace" -m "/Users/jenkins/.jenkins/jobs/SyncSpaceBeta/workspace/iOS/AdHoc_com.infinitekind.whiteboard-beta.mobileprovision" --verbose | xcpretty
[23:26:08]: [SHELL COMMAND]: set -o pipefail && krausefx-ipa build -s "SyncSpace" -m "/Users/jenkins/.jenkins/jobs/SyncSpaceBeta/workspace/iOS/AdHoc_com.infinitekind.whiteboard-beta.mobileprovision" --verbose | xcpretty
[23:26:32]: [SHELL]: 2015-07-29 23:26:32.133 xcodebuild[49686:3674967] [MT] DVTAssertions: Warning in /SourceCache/IDEFrameworks/IDEFrameworks-7703/IDEFoundation/SourceControl/Model/IDESourceControlManager.m:423
[23:26:32]: [SHELL]: Details:  Error Domain=com.apple.dt.IDESourceControlErrorDomain Code=-1 "Missing extension: public.vcs.subversion" UserInfo=0x7fc88ce6cfa0 {NSLocalizedDescription=Missing extension: public.vcs.subversion}
[23:26:32]: [SHELL]: Object:   <IDESourceControlManager: 0x7fc88ce69310>
[23:26:32]: [SHELL]: Method:   -loadRepositories
[23:26:32]: [SHELL]: Thread:   <NSThread: 0x7fc888d2e430>{number = 1, name = main}
[23:26:32]: [SHELL]: Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
[23:26:32]: [SHELL]: ▸ Cleaning SyncSpace/ExtensionKit [Release]
[23:26:33]: [SHELL]: ▸ Cleaning SyncSpace/SyncSpaceToday [Release]
[23:26:33]: [SHELL]: /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/parser.rb:350:in `===': invalid byte sequence in US-ASCII (ArgumentError)
[23:26:33]: [SHELL]: from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/parser.rb:350:in `update_test_state'
[23:26:33]: [SHELL]: from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/parser.rb:247:in `parse'
[23:26:33]: [SHELL]: from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/formatters/formatter.rb:78:in `pretty_format'
[23:26:33]: [SHELL]: from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/printer.rb:15:in `pretty_print'
[23:26:33]: [SHELL]: from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/bin/xcpretty:80:in `block in <top (required)>'
[23:26:33]: [SHELL]: from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/bin/xcpretty:79:in `each_line'
[23:26:33]: [SHELL]: from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/bin/xcpretty:79:in `<top (required)>'
[23:26:33]: [SHELL]: from /usr/bin/xcpretty:23:in `load'
[23:26:33]: [SHELL]: from /usr/bin/xcpretty:23:in `<main>'
[23:26:42]: [SHELL]: ** BUILD FAILED **
[23:26:42]: [SHELL]:
[23:26:42]: [SHELL]:
[23:26:42]: [SHELL]: The following build commands failed:
[23:26:42]: [SHELL]: Check dependencies
[23:26:42]: [SHELL]: (1 failure)
[23:26:43]: [SHELL]: ** ARCHIVE FAILED **
[23:26:43]: [SHELL]:
[23:26:43]: [SHELL]:
[23:26:43]: [SHELL]: The following build commands failed:
[23:26:43]: [SHELL]: Check dependencies
[23:26:43]: [SHELL]: (1 failure)
[23:26:43]: -------------------------------------------------------
[23:26:43]: Original Error:
[23:26:43]:  => Exit status of command 'set -o pipefail && krausefx-ipa build -s "SyncSpace" -m "/Users/jenkins/.jenkins/jobs/SyncSpaceBeta/workspace/iOS/AdHoc_com.infinitekind.whiteboard-beta.mobileprovision" --verbose | xcpretty' was 256 instead of 0.
2015-07-29 23:26:32.133 xcodebuild[49686:3674967] [MT] DVTAssertions: Warning in /SourceCache/IDEFrameworks/IDEFrameworks-7703/IDEFoundation/SourceControl/Model/IDESourceControlManager.m:423
Details:  Error Domain=com.apple.dt.IDESourceControlErrorDomain Code=-1 "Missing extension: public.vcs.subversion" UserInfo=0x7fc88ce6cfa0 {NSLocalizedDescription=Missing extension: public.vcs.subversion}
Object:   <IDESourceControlManager: 0x7fc88ce69310>
Method:   -loadRepositories
Thread:   <NSThread: 0x7fc888d2e430>{number = 1, name = main}
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
▸ Cleaning SyncSpace/ExtensionKit [Release]
▸ Cleaning SyncSpace/SyncSpaceToday [Release]
/Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/parser.rb:350:in `===': invalid byte sequence in US-ASCII (ArgumentError)
	from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/parser.rb:350:in `update_test_state'
	from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/parser.rb:247:in `parse'
	from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/formatters/formatter.rb:78:in `pretty_format'
	from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/lib/xcpretty/printer.rb:15:in `pretty_print'
	from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/bin/xcpretty:80:in `block in <top (required)>'
	from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/bin/xcpretty:79:in `each_line'
	from /Library/Ruby/Gems/2.0.0/gems/xcpretty-0.1.10/bin/xcpretty:79:in `<top (required)>'
	from /usr/bin/xcpretty:23:in `load'
	from /usr/bin/xcpretty:23:in `<main>'
** BUILD FAILED **

Fastfile - This is the lane that's being run
  desc "Build a new beta release"
  lane :beta do
    sigh(adhoc: true)

    # use the UDID of the newly created provisioning profile
    ENV["PROFILE_UDID"] = lane_context[SharedValues::SIGH_UDID]

    ipa(scheme: "SyncSpace")
  end

Appfile
for_platform :ios do
	for_lane :beta do
		app_identifier "com.mysite.myapp-beta"
	end
end

Jenkins configures your environment wrong, so you have to fix it: http://stackoverflow.com/a/17031697/445598, should be easy to do so :+1:

Do I just run this directly from the command line when running as jenkins or is there some other step I need to follow or some place that this should be interred in my jenkins configurations?

You can just add this in your Build Step before triggering fastlane.

I added this and it didn't fix my issue. Building directly on the machine that runs Jenkins gave me a different error. It seems like it's down to an issue of sigh not finding the manually created profiles and making its own. It finds those just fine each time, just not the ones that were created for the project.
I'm having to do the signing with sigh and inject them into the project directly as it contains a Today widget which needs its own provisioning and I'm trying to get an AdHoc build created.
Is there any advice you can give me on to the sigh issue or should I add another issue within sigh for that and close this one?
Thanks.

@mark5422 I assume you don't have the private key and certificate on your Jenkins machine installed. How does Jenkins run? As its own user? Did you take a look at the Jenkins guide in the docs section of this repo?

Jenkins runs as its own user. I did take a look at the Jenkins guide. Everything runs so long as I don't try and use a specific profile or build using a configuration that requires one. As soon as I do either I get the problem.
What I'm seeing right now is this
Code Sign error: Provisioning profile does not match bundle identifier: The provisioning profile specified in your build settings (“SyncSpaceToday AdHoc<PHONE_NUMBER>”) has an AppID of “com.infinitekind.whiteboard-beta.SyncSpaceToday” which does not match your bundle identifier “com.infinitekind.whiteboard.SyncSpaceToday.SyncSpaceToday”.
The profile with the number on the end is being generated when sigh cannot find the profiles. I cannot find out where the bundle identifier is coming from that it's not matching.

Got the same issue, worked like a charm few days ago, did update and have this problem.

This is a jenkins and not a fastlane issue, so it can be closed.  One solution is to set the locale environment variables at the beginning of the shell script step.

:+1:


Improvement

Changed

Use different visitors for different purposes
Use prettyPrintFile instead of prettyPrint method of prettyprinter

Much better! Thanks!

I'll just give you write rights

Wait... Not sure if tests did succeed. Better enable travis.


WIP: Manage Self-hosted runners with Garm

related to #77.
Exploration on how to have a lightweight mgmt solution for Self-hosted runners on Azure using Garm .
Garm needs a Webhook exposed on the Internet that can be called by GitHub to register workloads. Potentially we can have lightweight solution with ACI using letsencrypt, managed identity, sqlite on a volume.

cc @wainersm

Closed in favor of https://github.com/confidential-containers/infra/pull/1


load all of the Atkinson RNA

Using the 3 gff files you created for me back in June.
There are  a number of issues with the ncRNAs

Clearly redundant  entities
Some old ncRNAs are no longer supported (this is mainly ncRNAs from Wilhelm et al that are not present in this dataset).
I was hoping to use this data to resolve these but I won't have time so we should just load them all.

We can resolve  problems later. I  have a list of problems that I noticed whilst revising the TSS's on chromosome 1 so I will open a ticket to resolve these on a case-by-case basis). We can also do some checks later for largely overlapping entities.
This will make @bahler  very happy.

:-D
Cheers,

Jurg

Sent from my phone
On 21 Dec 2021, at 08:47, Val Wood @.***> wrote:

⚠ Caution: External sender
Using the 3 gff files you created for me back in June.
There are a number of issues with the ncRNAs

Clearly redundant entities
Some old ncRNAs are no longer supported (this is mainly ncRNAs from Wilhelm et al that are not present in this dataset).
I was hoping to use this data to resolve these but I won't have time so we should just load them all.

We can resolve problems later. I have a list of problems that I noticed whilst revising the TSS's on chromosome 1 so I will open a ticket to resolve these on a case-by-case basis). We can also do some checks later for largely overlapping entities.
This will make @bahlerhttps://github.com/bahler very happy.
—
Reply to this email directly, view it on GitHubhttps://github.com/pombase/pombase-chado/issues/904, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADMTWVBNPGN4PNORQBMIPNLUSA5KBANCNFSM5KPTK6NQ.
Triage notifications on the go with GitHub Mobile for iOShttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|j.bahler%40ucl.ac.uk|51a53890a6f2418a0ec308d9c45e85e3|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637756732514282793|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=1vy5LZhBTGlbahjwEhqZZu%2F%2F8uM6q9JCJiNzC6isdvI%3D&reserved=0 or Androidhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|j.bahler%40ucl.ac.uk|51a53890a6f2418a0ec308d9c45e85e3|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637756732514282793|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=riJUeeGeToYk9fXbDRvTzqfnxt7PooXvSTqMv0mao10%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

Hi Val.  What do I need to do here?  Should the GFF files be loaded into Chado or JBrowse?

We want to load them as features into Chado.
We already have JBrose data loaded
https://www.pombase.org/reference/PMID:29914874
I think  with this quick route, with no checks for inconsistencies, and not removing legacy ncRNAs that are not longer supported it should be fairly straightforward.
You will probably have some questions though (I think the gff files contain all ncRNAs that are 'believed' , but we only want to load the new ones.

Hi KIm,
The files you prepared for me from the Atkinson data are called
chr_1.gff3, chr_2.gff3, chr_3.gff3
They have feature type ncRNA, and source 'rtrackleyer'

chr_1.gff3, chr_2.gff3, chr_3.gff3

I can't find any files with those names and I can't find an email or issue mentioning them.  Is a possible you renamed them after I gave them to you?

source 'rtrackleyer'

I don't recognise that.  Any idea what it means?

Sorry typo-  'rtracklayer'
I don't know-  I guess it is the algorithm or method.
The file headers say:
##gff-version 3
##source-version rtracklayer 1.48.0
##date 2020-11-16

I don't think I renamed them. I'll look back for the original e-mails from Maria.

I still can't find out what I did to make the files.  I'll have a think tomorrow and maybe you'll be able to jog my memory when we chat.

OK I will check in the files I have to svn.

We have existing 1526 ncRNAs from various sources.
In the new dataset there are 7356 ncRNAs. These include many in the 1-1526 ID range (this dataset provides additional support for this data).
Step 1

[ ] If there is an existing RNA, we only need to add a db_ref to  PMID:29914874
[ ] Create features  all of the new ones

Step2

[ ] Database query to identify any ncRNAs supported by PMID:21859475
but unsupported by this dataset to review and possible deprecate

If there is an existing RNA, we only need to add a db_ref to PMID:29914874
Create features all of the new ones

I have a script ready to go to do those two steps.
PMID:29914874 has been added to the existing features:
FT   ncRNA           complement(11027..11556)
FT                   /db_xref="PMID:29914874"
FT                   /db_xref="EMBL:AF087836"
FT                   /gene="SPNCRNA.70"
FT                   /product="non-coding RNA (predicted)"
FT                   /systematic_id="SPNCRNA.70"
FT                   /controlled_curation="term=warning, no detectable long
FT                   open reading frame; qualifier=predicted;
FT                   db_xref=EMBL:AF087836; date=20050412"

And the new features look like:
FT   ncRNA           4057..4311
FT                   /db_xref="PMID:29914874"
FT                   /systematic_id="SPNCRNA.2003"
FT   ncRNA           4784..5129
FT                   /db_xref="PMID:29914874"
FT                   /systematic_id="SPNCRNA.2004"
FT   ncRNA           5256..6263
FT                   /db_xref="PMID:29914874"
FT                   /systematic_id="SPNCRNA.2005"
FT   ncRNA           complement(7216..8253)
FT                   /db_xref="PMID:29914874"
FT                   /systematic_id="SPNCRNA.2006"

Here are the number of new RNA features and the number that have been updated with the extra /db_xref:
chr 1:
  new: 2545
  updated: 660
chr 2:
  new: 2177
  updated: 554
chr 3:
  new: 1124
  updated: 288

we should give them all the new ones the product /product="non-coding RNA"
(to be refined in future)

Looks good though.

we should give them all the new ones the product /product="non-coding RNA"

I've done that and committed the new features to SVN.

The load failed last night because of the new features.  I'm trying to figure out why.  It isn't clear.

The load failed last night because of the new features. I'm trying to figure out why. It isn't clear.

A single ncRNA ID was causing the failure which is why it wasn't clear what was going on.  "SPNCRNA.5" was confusing the code because it looks a bit like the 5th transcript of a gene called "SPNCRNA".
It's now fixed so tonight's load should be OK.

It's now fixed so tonight's load should be OK.

Seem fine: https://www.pombase.org/gene/SPNCRNA.2176

Database query to identify any ncRNAs supported by PMID:21859475

I can't find any features supported by PMID:21859475.   It doesn't appear in the contig files.

wrong Wilhelm paper!
PMID:18488015

Database query to identify any ncRNAs supported by PMID:18488015 but unsupported by this dataset to review and possible deprecate

It's mostly protein coding genes?:
 SPAC212.12
 SPAC12G12.17
 SPAC227.19c
 SPAC22F3.15
 SPAC222.17
 SPAC222.18
 SPAC57A7.15c
 SPAC167.09
 SPAC23H4.21
 SPAC25H1.10c
 SPAC6F6.19
 SPAC3F10.19
 SPAC688.16
 SPAP4C9.02
 SPAC27E2.14
 SPAC23D3.16
 SPAC23D3.17
 SPAC20G4.09
 SPBC29A10.17
 SPBC1604.25
 SPBC26H8.16
 SPNCRNA.438
 SPCC757.15
 SPCC16C4.22
 SPCC1442.19
 SPCC569.09

OK, I expected many more. I think they must have included all of the Wilhelm data even if unsupported (I know that a proportion of them are unsupported and on the wrong stand, because I have seen them.)
If this is the case, then we were wrong to include the PMID:29914874 for every ncRNA in the provided dataset.
I will need to speak to @bahler about this.

I don’t know what comparison you did. But we left all previously annotated ncRNAs (those with names in PomBase up to ~ SPNCRNA.1550) and included them in the analyses without making judgment whether they were supported by the new data or not. Out new data are only SPNCRNA.2000 to SPNCRNA.7774, so only those should be associated with PMID:29914874
.
Cheers,
-Jürg
From: Val Wood @.***
Sent: 18 January 2022 08:39
To: pombase/pombase-chado @.>
Cc: Bahler, Jurg @.>; Mention @.***>
Subject: Re: [pombase/pombase-chado] load all of the Atkinson RNA (Issue #904)
⚠ Caution: External sender
OK, I expected many more. I think they must have included all of the Wilhelm data even if unsupported (I know that a proportion of them are unsupported and on the wrong stand, because I have seen them.)
If this is the case, then we were wrong to include the PMID:29914874 for every ncRNA in the provided dataset.
I will need to speak to @bahlerhttps://github.com/bahler about this.
—
Reply to this email directly, view it on GitHubhttps://github.com/pombase/pombase-chado/issues/904#issuecomment-1015183607, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADMTWVG2SI2NHZ5EUUPUJFDUWURJLANCNFSM5KPTK6NQ.
Triage notifications on the go with GitHub Mobile for iOShttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|j.bahler%40ucl.ac.uk|ea340b8dab5048d1fbf608d9da5df170|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637780919287778278|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=JicSmTw6ZKhNyRDiaaPN1gWHJwL4Vbwr1jf9ENwoOSk%3D&reserved=0 or Androidhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|j.bahler%40ucl.ac.uk|ea340b8dab5048d1fbf608d9da5df170|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637780919287778278|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=yKZ42XJbzXYZaj%2FHm7Rth%2FDZgSwiCG2XHi%2Falgnxldo%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

So you don't have a record of the ones you did not see at all? (or conversely the old ones that your data supports?)

No, we did not systematically check whether we see the previously annotated ones. A negative result would not be conclusive as the conditions were different for different studies. But anecdotally speaking, it is clear that many of the older annotations are not supported by newer data.
Cheers,
-Jürg
From: Val Wood @.***
Sent: 18 January 2022 10:36
To: pombase/pombase-chado @.>
Cc: Bahler, Jurg @.>; Mention @.***>
Subject: Re: [pombase/pombase-chado] load all of the Atkinson RNA (Issue #904)
⚠ Caution: External sender
So you don't have a record of the ones you did not see at all? (or conversely the old ones that your data supports?)
—
Reply to this email directly, view it on GitHubhttps://github.com/pombase/pombase-chado/issues/904#issuecomment-1015280842, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADMTWVAQAE3RASXZ5DLR64LUWU7BPANCNFSM5KPTK6NQ.
Triage notifications on the go with GitHub Mobile for iOShttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|j.bahler%40ucl.ac.uk|e8c83cf7198742178e7908d9da6e56c4|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637780989699748328|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=Fb4UmY6iiAXTWmV%2FMPc90CRoeSCPHE%2B8ZSROXeKhf8U%3D&reserved=0 or Androidhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|j.bahler%40ucl.ac.uk|e8c83cf7198742178e7908d9da6e56c4|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637780989699748328|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=sqFKo0rivN5Rdk8Dyv06udbwlDQ9Nv4k8Ti9fB4Vqto%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

So, what I am trying to get at is, if your data does support the old ones, we can add your recent paper as additional evidence. So do you have a list of the older RNAs that you support? This will not affect the existing RNAs because as you say a negative result is not conclusive. it will however help us to identify the unsupported ones and to see if they were reported on the wrong strand.

No, we did not systematically check this I think. But I will meet Sam later this week and will check with him.
Cheers,
-Jürg
From: Val Wood @.***
Sent: 18 January 2022 10:54
To: pombase/pombase-chado @.>
Cc: Bahler, Jurg @.>; Mention @.***>
Subject: Re: [pombase/pombase-chado] load all of the Atkinson RNA (Issue #904)
⚠ Caution: External sender
So, what I am trying to get at is, if your data does support the old ones, we can add your recent paper as additional evidence. So do you have a list of the older RNAs that you support? This will not affect the existing RNAs because as you say a negative result is not conclusive. it will however help us to identify the unsupported ones and to see if they were reported on the wrong strand.
—
Reply to this email directly, view it on GitHubhttps://github.com/pombase/pombase-chado/issues/904#issuecomment-1015294834, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADMTWVGSQI5PTYOVRVOFX2DUWVBFTANCNFSM5KPTK6NQ.
Triage notifications on the go with GitHub Mobile for iOShttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|j.bahler%40ucl.ac.uk|f08961d4fd2f48fc187c08d9da70e011|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637781000589864041|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=9xhoe1j0UoUynf6smWGyQoZitDQWeK3k8m5qnzeUZ8k%3D&reserved=0 or Androidhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|j.bahler%40ucl.ac.uk|f08961d4fd2f48fc187c08d9da70e011|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637781000589864041|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=YrrJ7p%2Bu0mm%2BI%2FVnNROevYhf7bvztngQq1SGT97n8GE%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi Jürg.  Did you have a meeting with Sam?

I heard back from Jurg and forgot to update the ticket. This information isn't available....

So I guess we need to make sure PMID:29914874 is only associated with
SPNCRNA.2000 to SPNCRNA.7774
Then this ticket can close. I  will open new ticket to improve the products.
I think we can also capture more information about the degradation, but I need to speak to Jurg about the best way to do that at some point.

action:
only associated with PMID:29914874 with
SPNCRNA.2000 to SPNCRNA.7774

only associated with PMID:29914874 with SPNCRNA.2000 to SPNCRNA.7774

It a little bit of work because it will require a script to parse the contig files and remove the PMID:29914874 /db_xref from SPNCRNA.01 to SPNCRNA.1999, then write the files.  How urgent is that?

Not so urgent. Bit I think there is a list somewhere of  the existing RNAs which are unsupported. I will try to locate this.
I think of these we can deprecate the ones from the Wilhelm paper - this is from @bahler so it seems these are no longer believed (I thought quite a few were spurious).
This would make this task unnecessary and would have a better outcome.

not sure I understand. This action seems to ensure that the correct SPNCRNAs are associated with PMID:29914874, so nothing to do whether old SPNCRNAs are supported or not?

hi @bahler
The data provided for the Atkinson paper included all previously observed RNAs, plus the new ones.
The plan was that we ignored the ones we had 'seen' previously.
This has caused a number of problems for us.

A lot of non coding RNAs which. had previously been merged were re-imported.
The ID from the Atkinson paper is now associated with  some RNAs that were not in the Atkinson dataset. This makes some of these appear more likely to be real.

For example

did you see SPNCRNA.163 in the Atkinson dataset? It was from. the Wilhelm dataset, but many of these were not strands specific, and the new RNA is on the opposite strand?
2, SPNCRNA.156 is labelled "this transcript could be on either strand", and the opposite strand appears to be correct.
There are quite a lot of these:
https://www.pombase.org/term/PBO:0006231

It would be useful to get the list of existing ncRNAs that are supported by the Atkinson dataset. This way we can  look more closely at the Wilhelm data that is unsupported and see if we can refine these.

Here is another example
https://www.pombase.org/gene/SPNCRNA.279
Because it was supplied again from the Atkinson data, this is now added as support. But it looks as though the ncRNA is on the opposite strand.


Minor changes to dispatchers (action creators will dispatch multiple actions)

For #9898

Part of #9898
More strong typing for actions created (found one scenario where we weren't passing in the right stuff)
Fixed two bugs related to adding cells and deleting all cells
Fixed a bug related to adding cells using a and b keys, old approach resulted in a and b being typed into the new cell that was created as a result
Re-used actions to add cells (makes it much easier for syncing of messages across)
Fixed a bug in react (we were expecting an HTML dom element, however I think we were getting an canvas element where className was not a string but an object.

Codecov Report

Merging #9920 into ds/custom_editor will increase coverage by 0.04%.
The diff coverage is 55.55%.

@@                 Coverage Diff                  @@
##           ds/custom_editor    #9920      +/-   ##
====================================================
+ Coverage             60.61%   60.66%   +0.04%
====================================================
  Files                   555      556       +1
  Lines                 29737    29792      +55
  Branches               4482     4483       +1
====================================================
+ Hits                  18026    18072      +46
- Misses                10710    10718       +8
- Partials               1001     1002       +1

Impacted Files
Coverage Δ

...ience/interactive-common/interactiveWindowTypes.ts
100% <100%> (ø)
:arrow_up:

...ence-ui/interactive-common/redux/reducers/types.ts
95.91% <50%> (ø)

...ient/datascience/interactive-ipynb/nativeEditor.ts
12.66% <50%> (+1.05%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 05bf2ea...df0563a. Read the comment docs.


MFA licensing changes

Hi folks, Please update this to reflect the broader availability of Azure MFA, given that it helps this scenario - if it is freely available, perhaps the statement "some dependencies require AADP" is no longer applicable, which would remove a customer objection... KUTGW
J

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

ID: 5739fab2-c6db-a7a9-b0e7-2bf4b85912a7
Version Independent ID: 82c58053-c1d7-d938-1b0f-f3f7f70ada3b
Content: Planning a Windows Hello for Business Deployment - Microsoft 365 Security
Content Source: windows/security/identity-protection/hello-for-business/hello-planning-guide.md
Product: w10
Technology: windows
GitHub Login: @mapalko
Microsoft Alias: mapalko

@mapalko It seems like insider information is needed to address this issue. Please let me know in any way that we could help. Thanks.

I don't want to make a mystery of it: here (https://azure.microsoft.com/en-gb/pricing/details/active-directory/) it says that MFA is free. This doc refers to the old licensing where AADP or other licences were required for MFA, so that could be changed. Also, the rather vague "there may be prerequisites which require AADP" probably refers to MFA, so this could be examined as well... HTH
J

@JBWCowling
Thank you for “demystifying” the situation and let’s see what one of the independent contributors has to say about the issue.

Came here to file this issue as well. Azure MFA using Microsoft Authenticator is free as part of security defaults now. https://techcommunity.microsoft.com/t5/azure-active-directory-identity/introducing-security-defaults/ba-p/1061414

@JBWCowling @libbro2006 Could you please let us know exactly which paragraph(s) you are reffering to? I don't want to assume something, that's why i want to confirm with you first.
What i see in the article is:
"Windows Hello for Business does not require an Azure AD premium subscription. However, some dependencies do." -> in my understanding, these dependencies do not imply MFA, but rather things like MDM auto-enrollment, Conditional Access, which require Azure AD P1/P2 subscription.
What exactly do you want to be changed?

The article has been revised in accordance with your feedback via #6416. Thank you.


Not all tabbable elements are in your selector

These come to mind: area, object.
I see contenteditable is impossible to implement correctly.

Thanks, @adamvleggett. This is noted in the README as a caveat:

This plugin ignores the rarely used  and  elements, which are focusable in some circumstances. (If you need them, maybe PR?)

If you need those and want to create a PR, feel free!
For reference, here's the issue where we discussed the possibility of contenteditable: https://github.com/davidtheclark/tabbable/issues/7


Compile error: unary negation issue

[Shaders, screenshots, error log, reproduction steps, etc.] [ZIP]
This is an issue that was filed to Intel a while ago, but which has not been acted on:
https://software.intel.com/en-us/forums/developing-games-and-graphics-on-intel/topic/607206
Looks like we have ended up finding the problem again:
https://github.com/mc-imperial/shader-compiler-bugs/issues/4
So I'm raising this just to record that it was reported before, but marking this one as the duplicate (since the issue persists in a more recent driver, as indicated by the other issue).

Closing the issue since it is a duplicate.


chore: Update image URLs in chart templates

What this PR does / why we need it:
Updates image URLs in cluster-api-operator in core-provider, rke2-bootstrap, and rke2-controlplane templates

Fixes #532
Checklist:

[x] squashed commits into logical changes
[x] includes documentation
[ ] adds unit tests
[ ] adds or updates e2e tests

@Danil-Grigorev I think they are both the same, xref: https://github.com/kubernetes-sigs/cluster-api-operator/blob/main/docs/README.md?plain=1#L398. But let's wait for tests to pass after retrigger.

Closing in favor of https://github.com/rancher/turtles/pull/533.
Thanks @MAXxATTAXx for your contribution!


On submit validation failure, focus on first invalid input

On submit validation failure, is there any feature that would help to focus on the first invalid input element?

You can create a hook that stores an array of tuple (or map) of (Field, React.domRef) and check for fields with errors to focus/scroll to the input.
Here it is an example of how to do something similar (scroll to instead of focusing):
// FormWrapper.res
module Make = (Config: ReForm.Config) => {
  include ReForm.Make(Config)
  module ComparableField = Belt.Id.MakeComparable({
    type t = field
    let cmp = Pervasives.compare
  })

  type fields = Belt.MutableMap.t<ComparableField.t, Dom.element, ComparableField.identity>

  type registerFieldFn = (field, Js.Nullable.t<Dom.element>) => unit

  let useScrollToField = (~offsetTop=0, ()) => {
    let fieldsRef: React.ref<fields> = React.useRef(
      Belt.MutableMap.make(~id=module(ComparableField)),
    )

    let register = (fieldName, fieldRef) => {
      switch fieldRef->Js.Nullable.toOption {
      | Some(el) => fieldsRef.current->Belt.MutableMap.set(fieldName, el)
      | None => ()
      }
    }

    let scrollToFieldWithError = ({state}: onSubmitAPI) => {
      state.fieldsState
      ->Belt.Array.get(0)
      ->Belt.Option.map(((field, _)) => field)
      ->Belt.Option.flatMap(field => fieldsRef.current->Belt.MutableMap.get(field))
      ->Belt.Option.map(el => DomApiExtra.Window.scrollTo(0, el->DomApiExtra.offsetTop - offsetTop))
      ->ignore
    }

    (register, scrollToFieldWithError)
  }

}

// MyApp.res
module Lenses = %lenses(
 type state = {
  name: string,
 }
)
module MyForm = FormWrapper.Make(Lenses)
@react.component
let make = () => {
   // reform stuff here (useForm, etc)
  let (registerField, scrollWhenFail) = MyForm.useScrollToField()

  <input ref={Field(Name)->registerField->ReactDOM.Ref.callbackDomRef}  />
}

Thanks I'll give your example a shot.
I thought that's what it would boil down to but was hoping there might be some magic to help out.

Let me know if you need help to change the example from scrolling to a focusing behaviour.

Any progress here? Can I close this issue?
Let me know if you need help.

Had some friction getting things wired up but finally got it:

Wired scrollWhenFail up to onSubmitFail when configuring ReForm use.
Realized order of the Validation.Schema array determines order that the fields will appear in the fieldsState array.
Realized that, for onSubmitFail, the fieldsState array only contains the fields that have an error which is why it was safe to state.fieldsState->Belt.Array.get(0).
Added external to allow  el.focus({preventScroll: true}). Without preventScroll the focused element would just pop into view. Having it lets me follow up with `el.scrollIntoView({"behavior": smooth, "block": center}) to smoothly scroll the invalid input into view.

Thanks!


Large difference in vic run walltime before and after vic_run cleanup and veg classes memory allocation changes

Assessing VIC RUN walltime between January 17 and January 18 (before and after the vic_run and prepare_full_energy changes were made shows large timing differences over the RASM domain. Before the PR was merged, maximum walltime for a single grid cell in the RASM domain over a year-long period was up to 2.5s, but after the PR was merged maximum run time decreased to 0.2 s over the entire domain and time period for a single timestep.
Looking more closely at the actual values, and run for a single grid cell in the RASM domain (located in Central Asia), SWE is different before and after the Jan 17th change - this is a plot showing SWE from Sept 1948 - Aug. 1949 with the VIC 5 image driver run at a 3-hourly timestep for the gridcell in the RASM domain in Central Asia, showing results from: a) pre vic run change, b) post vic run change, and c) delta cc bug fix (merged into develop after the vic run cleanup PR from Jan 17)

We need to investigate these changes further and look at the science test results to determine what's going on.
cc @tbohn @jhamman @yixinmao @bartnijssen

Closed via #780


integral() not working with relative time ranges

By posting my findings in the InfluxDB comunity I think I have found a bug:
https://community.influxdata.com/t/integral-gives-incoherent-values/18457/2
It seems like using relative time range gives inchoerent values from integral while using absolute time range seems to be working fine.

Curious, the result of integral() is not even consistent.
If I click refresh the integral() value keeps changing to incoherent values. Screen captures done in real short period of time:

More info from community slack:

Using InfluxQL
Running against 1.8.3 server, 1.8.4 CLI


Array index out of range when removing entries from DataSet

Is there a specific reason why I am getting fatal error: Array index out of range: with this code?
for (int i = 0; i < [self.currentBarChartDataSet entryCount]; i++) {

        [self.currentBarChartDataSet removeEntryWithXIndex:i];
//        [self.pastBarChartDataSet removeEntryWithXIndex:i];

}

I'm basically trying to remove all data from the bar chart in prepareForReuse in a UICollectionViewCell so that the chart isn't visible when the collection view is reloaded.
If I log the count, it is 7 and the loop is running 7 times.

Ok I changed my code to this because I realized what I was doing wrong before, but it's still crashing with the same error
    NSInteger count = [self.currentBarChartDataSet entryCount];

    for (int i = 0; i < count; i++) {

        [self.currentBarChartDataSet removeEntryWithXIndex:0];
//        [self.pastBarChartDataSet removeEntryWithXIndex:i];

    }

It's crashing on this line #395 in ChartDataSet.swift
calcMinMax(start: _lastStart, end: _lastEnd)

Call notifyDataSetChanged() after done changing the data
On Fri, Jul 10, 2015 at 6:50 PM, Brandon Shega<EMAIL_ADDRESS>wrote:

It's crashing on this line #395 in ChartDataSet.swift
calcMinMax(start: _lastStart, end: _lastEnd)
—
Reply to this email directly or view it on GitHub
https://github.com/danielgindi/ios-charts/issues/203#issuecomment-120442038
.

It doesn't even let me get that far, it's crashing before it even moves over the line where the entry is removed.


add a small "when to expect R4" post.

Prodded by @frosty-geek in #571. thanks for raising this.

@frosty-geek noticed that I deepl'ed the german variant ;) I'll fix that.

besides that (#20millionchangesrequested SCNR), LGTM ;-)

closes #571


Invalid column index used for RSS memory on Linux

It seems a wrong column index is used to assign RSS memory size:
processes_linux.go
	Add(md, "linux.proc.mem.virtual", stats[22], tags, metadata.Gauge, metadata.Bytes, descLinuxProcMemVirtual)
	Add(md, "linux.proc.mem.rss", stats[23], tags, metadata.Gauge, metadata.Page, descLinuxProcMemRss)

linux.proc.mem.rss shoud use stats[21] for RSS memory.
cat /proc/28446/stat
28446 (java) S 1 28391 28391 0 -1<PHONE_NUMBER> 249984 555 81 0<PHONE_NUMBER>3 0 0 20 0 196 0 612712882<PHONE_NUMBER><PHONE_NUMBER>6744073709551615 4194304 4228916<PHONE_NUMBER>42800<PHONE_NUMBER>33840<PHONE_NUMBER>91371 0 0 4098 16796877<PHONE_NUMBER>3709551615 0 0 17 5 0 0 0 0 0 6327688 6328928 26198016<PHONE_NUMBER>50866<PHONE_NUMBER>51083<PHONE_NUMBER>51083<PHONE_NUMBER>53065 0

cat /proc/28446/status
Name:   java
State:  S (sleeping)
Tgid:   28446
Ngid:   0
Pid:    28446
PPid:   1
TracerPid:      0
Uid:    1000    1000    1000    1000
Gid:    1000    1000    1000    1000
FDSize: 512
Groups: 999 1000
VmPeak:  8960800 kB
VmSize:  8960796 kB
VmLck:         0 kB
VmPin:         0 kB
VmHWM:    676680 kB
VmRSS:    671844 kB
VmData:  8866028 kB
VmStk:       136 kB
VmExe:        36 kB
VmLib:     18444 kB
VmPTE:      2528 kB
VmSwap:     1224 kB
Threads:        196
SigQ:   0/386186
SigPnd:<PHONE_NUMBER>000000
ShdPnd:<PHONE_NUMBER>000000
SigBlk:<PHONE_NUMBER>000000
SigIgn:<PHONE_NUMBER>001002
SigCgt:<PHONE_NUMBER>004ccd
CapInh:<PHONE_NUMBER>000000
CapPrm:<PHONE_NUMBER>000000
CapEff:<PHONE_NUMBER>000000
CapBnd: 0000001fffffffff
Seccomp:        0
Cpus_allowed:   0ff
Cpus_allowed_list:      0-7
Mems_allowed:   00000000,00000001
Mems_allowed_list:      0
voluntary_ctxt_switches:        1
nonvoluntary_ctxt_switches:     3

ps aux | grep 28446
user  28446 16.3  1.3 8960796 674068 ?      Sl   10:33  40:08 java ...

uname -a
Linux NURSWGDKR002 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

What does your man proc 5 says on /proc/[pid]/stat format?
              (24) rss  %ld
                        Resident  Set  Size:  number  of pages the process has in real memory.  This is just the pages which count
                        toward text, data, or stack space.  This does not include pages which have not been demand-loaded  in,  or
                        which are swapped out.

Also
674388

gives close result to
user  28446 16.3  1.3 8960796 674068 ?      Sl   10:33  40:08 java ...

Yes, my mistake. Please close the issue. The number I was looking at showed number of pages whereas I was expecting RSS in kilobytes. If I multiply rss page count by 4KB I get RSS in kilobytes which is the number I was looking. It would have been useful to have a derived scollector metric that computes RSS in KB taking PAGE_SIZE into account.


Support gradual ramp-up

With this commit we allow users to ramp-up load gradually by specifying
the task property ramp-up-time-period. If a non-zero value is
specified, Rally will gradually add clients during that time period
until the target client count as specified by clients is reached. This
reduces the potential for initial load spikes when running with many
concurrent clients.
Closes #1195

This can be tested with the following configuration:

Create a track and store it as ramp-up.json:

{
  "version": 2,
  "schedule": [
    {
      "operation": {
        "name": "query-match-all",
        "operation-type": "search",
        "index": "_all",
        "body": {
          "query": {
            "match_all": {}
          }
        }
      },
      "clients": 100,
      "ramp-up-time-period": 120,
      "warmup-time-period": 120,
      "time-period": 120,
      "target-throughput": 1000
    }
  ]
}

We'll use static responses, so also create responses.json:

[
  {
    "path": "*/_search",
    "body": {
        "took": 1,
        "timed_out": false,
        "hits":{
            "total" : {
                "value": 1,
                "relation": "eq"
            }
        }
    },
    "body-encoding": "raw"
  },
  {
    "path": "*",
    "body": {},
    "body-encoding": "json"
  }
]

Run a race:

esrally race --track-path=ramp-up.json --pipeline=benchmark-only --distribution-version=8.0.0 --client-options="static_responses:'responses.json'"

If we specify an Elasticsearch metrics store, we can visualize the ramp-up. The following chart shows how query throughput is linearly increasing during ramp-up and is then kept steadily at the specified target througput:

@DJRickyB can you please have another look?


evp_test: Add the missing check after calling OPENSSL_malloc

The OPENSSL_zalloc() could return NULL pointer if fails.
Add the check for it does make sense, like how digest_test_init() deals
with.
CLA: trivial
Signed-off-by: Jiasheng Jiang<EMAIL_ADDRESS>
Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Please drop the last commit. We do not allow merging with merge commits.

(Just git reset --hard HEAD~ and force push should suffice.)

(Just git reset --hard HEAD~ and force push should suffice.)

Fine, I have done it.

This pull request is ready to merge

Merged to master and 3.0 branches. Thank you for your contribution.


Consider a "noindex" key

In the last couple of months we faced situations where the publiccode.yml:

is a "placeholder" filled with Lorem Ipsum;
is under construction (not totally filled);
has been copied from another repo and the information contained inside are not related to the project;
is a test repo;
other possibilities.

As such, I wonder if it could be feasible to add a decentralized mechanism to tell the spiders not to index such a file.
I was thinking at something like a boolean "noindex" key which simply states whether the repo should be indexed or not yet.
What do you think about this?
I think that acting in a centralized way from the spider perspective (e.g., using something like a blacklist) is harder since it requires the intervention of the spider's responsibles who are external from the software publishers group, it does not scale, it is very error prone and it requires a communication channel to be established at least twice.
The main risk is of course that someone could leave the value to "true" and such a software would never be indexed.
What do you think?

Here's my two cents. As I see it, either the file is willingly incomplete or its contents are wrong.
In the first case (fe. placeholder, under construction, test repo) the developer doesn't want the file to be crawled yet, and they should be able to express that, but in the second case (fe. copied from another repo or plain wrong info) the file should just be fixed.
I'd KISS and just hint in the documentation to rename the file to something like publiccode.yaml.wip or whatever if it's not ready to be crawled.

In the first case (fe. placeholder, under construction, test repo) the developer doesn't want the file to be crawled yet, and they should be able to express that, but in the second case (fe. copied from another repo or plain wrong info) the file should just be fixed.

Yeah, I discarded the filename change in the first place since that always implies changing all the places where that file is used (I can think of a CI calling the validator already in use in some repos).
Furthermore, by keeping the publiccode.yml name consistent and adding the proposed key a crawler could also keep track of all the non-yet-indexed repos and that could be valuable (e.g., we could feed the issue-opener tool with such a list and automatically open a reminder issue).
But again I'm just thinking aloud and I haven't made up my mind yet, thanks for your cents 😄

issue-opener

I didn't know such a tool was in the works, nice!
What about using a robots.txt file in the repo's root directory? It's a well known format and we could reuse the same solution in similar circumstances, both present (projects_settings.yml?) and future.
User-agent: Golang_italia_backend_bot
Disallow: /publiccode.yml


Rename master to main

As discussed yesterday (Monday, 2021-01-25), we plan to switch the default branch name from master to main during the hackfest on February 10th.

Done


Differences between TCP and UDP data handling

Hi there,
I noted that statser handles differently the data feeds received by the TCP and UDP handlers.
While the TCP received metrics are processed using a binary:split pattern of space and tab, like this:
process_line(#state{pattern=Pattern, filters=Filters}, Data) ->
    case binary:split(Data, Pattern, [global, trim_all]) of
        % usual graphite format: 'path value timestamp'
        [Path, ValueBS, TimeStampBS] ->
            Value = statser_util:to_number(ValueBS),
            TimeStamp = to_epoch(TimeStampBS),
            {filter_path(Path, Filters), Value, TimeStamp};

        % graphite format w/o timestamp: 'path value'
        [Path, ValueBS] ->
            Value = statser_util:to_number(ValueBS),
            TimeStamp = statser_util:seconds(),
            {filter_path(Path, Filters), Value, {ok, TimeStamp}};

        _Otherwise ->
            error
    end.

the UDP handler does a totally different thing:
handle_packet(Packet, State) ->
    lager:info("handling UDP packet: ~p", [Packet]),
    case binary:split(Packet, ?DELIMITER_COLON, [global, trim_all]) of
        [Metric | Rest] ->
            case statser_config:metric_passes_filters(Metric, State#state.filters) of
                true ->
                    handle_metrics(Metric, Rest, State);
                false ->
                    statser_instrumentation:increment(<<"metrics-blacklisted">>),
                    {ok, State}
            end;
        _ ->
            % TODO: check for valid metrics name
            handle_metric(State, Packet)
    end.

So it is clear that this statser behaviour is by design.
However, by reading the graphite docs about feeding data it seems that both TCP and UDP accept  the plaintext protocol, so this seems a major difference with statser.
Am I missing something?
Thank you

The UDP port is used for the StatsD-like data ingestion.


use snake case for kafka events

Tested both Kafka and SQS events
@JsonProperty is for Kafka since it uses Json for serialization
@SerializedName is for SQS since it uses Gson for serialization
this addresses - https://github.com/stellar/java-stellar-anchor-sdk/issues/370

Reference Server Preview is available here:https://anchor-ref-pr374.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr374.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr374.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr374.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr374.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr374.previews.kube001.services.stellar-ops.com/

@stfung77, another interesting option is that in spring boot apps, it is also possible to change jackson serialization behavior at app level by setting the property spring.jackson.property-naming-strategy=SNAKE_CASE.


Learning: why do you use dispatchNow in controllers?

Hey, this is a question for learning rather then an issue.
In your controller classes, you always use dispatchNow() for doing the the real work like creating replies etc. I wonder why do you use this approach? What are the benefits instead of doing it directly in the controller?
Cheers

Heya, sorry to keep you waiting. I wanted to take my time to properly explain this. So there are a couple of reasons why I take this approach.
First of all DRY: by moving all of the logic towards commands (in this case we're using "jobs" but it's the same principle) we can re-use the commands anywhere in the app. They're completely de-coupled from the presentation layer except for a few named constructors.
Second reason is that because we're using commands we get a complete list of everything our app can "do". If you visit the app/jobs directory you can see an entire list of actions the app can perform. This works also well into the mindset of DDD. Think of the commands there as Domain services. I'm planning on moving a bit more logic from the models to these commands so we can keep our models cleaner and slim but that for a future update.
Third reason is that I don't want my controllers to "do" anything. Controllers merely pass along data to the appropriate services and send responses back. They live in the presentation layer of your app and need to be unaware of anything too specific to your domain. By taking this approach our controllers become super slim and small and are easy to digest and read through.
There are more smaller benefits but these are the top ones. Hope this helps a bit. Feel free to ask more questions if you want! :)

Thank you very much for the explanation.
It makes sense to me now and I think I will try this in my next project. However, you still use the request validation feature. What if you dispatch a job somewhere else in the code. You would still have to validate it before you call the job right? Is this a good practise? What about error handling in the job if no validation has been done before?

@pr4xx This is a really good remark. This approach indeed requires you to validate the data upfront. We could add some extra validation inside the constructor of the command. If we would be working with Doctrine I would do this inside the constructor of the entities. Of course you can't perform all the validation inside of the command, just a few basic things.
If you look at the RegisterUser command you can see that we're validating two things here. This works well and adds an extra layer of validation that makes sure the data is correct before we attempt to persist it.
There's definitely no harm in adding more validation to your commands but you'll need to handle the exceptions properly when they're throw. Request validation up-front makes this easy. My suggestion for this particularly app would be to rely on request validation in the first place and do whatever you can in the command if it's really needed. At this point I'd leave the commands as is but I might add more validation in the future if I see the need.

Why synchronously jobs instead events?

Why synchronously jobs instead events?

At the moment I'm dispatching commands from controllers. Events may be later added when I have need for them.

@lukashl as far as i know events refer to things that already have happened(e.g. UserRegistered, UserConfirmed) and jobs are more like tasks that need to be done(e.g. CreateUser, BanUser).


Enabling admin ssl port for dynamic cluster

Dynamic cluster setup, for admin server ssl port is not enabled.

Changes are merged, hence closing this issue.


accepting transfer spending RGB change fails

Using commit f9813b7 plus a cargo update to include rgb-std #193 and trying to execute 2 consecutive transfers, I face an issue.
This is what I'm doing (wallet 1 is the issuer/sender, wallet 2 is the recipient):

issue a NIA asset on wallet 1
sending some assets from wallet 1 to wallet 2
sending some more assets (spending RGB change) from wallet 1 to wallet 2

The 2nd transfer fails when trying to accept it with:
Error: index already contains information about bundle d0dd9f86be169ec70e6d3041f1fda0dfe4e65da46327d1d4121771589fa2f6af which specifies witness bc:f58173072ef1c98148bfe60ebb281f5bb4f90dbc3d9b6540a95d641f8884a9fa instead of witness bc:f58173072ef1c98148bfe60ebb281f5bb4f90dbc3d9b6540a95d641f8884a9fa.
It may happen due to RGB standard library bug, or indicate internal stash inconsistency and compromised stash data storage.

Re-tested after a cargo update to include commit https://github.com/RGB-WG/rgb-std/commit/5084eb2f9244102a263d1b23d66fb1c5c61cfa7c (part of https://github.com/RGB-WG/rgb-std/pull/193) and the transfer spending the change now succeeds.

@zoedberg waiting for your confirmation that your issue is also fixed

Fixed, thank you


Implement interface for meltano validator plugins

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2838
Originally created by @aaronsteers on 2021-07-06 22:42:10

Related to #2454, we will need a spec for how validators should interface with meltano CLI.
As part of the spec definition, we're looking at how the following validators would work:

Great Expectations (full)
dbt test (native dbt feature)
Stream maps
SQLFluff - (potentially as this could be considered a code validator)

Latest Proposal (2021-12-07):
Similar to the below from 2021-10-27, except that there is no "top level tests:" config. Instead, "plugins" have "commands" and "commands" can be of type "test". A command is of type test if its name starts with the word test.
Older Proposal (2021-10-27):

Discussion of the proposed spec from this comment thread: https://gitlab.com/meltano/meltano/-/issues/2838#note_682557413

Already today: Any plugin type can have a test command, added inline with other commands using existing command syntax.
Already today: Each test command is invocable directly and can perform its actions based on just environment vars and other context such as command line args.
New: Any plugin with a test command can also have a tests: list entry in the top-level plugin config. Each item in the list of tests can have the following properties:

name - optional, if test is to be referenced by name
executable - optional, overrides the executable of the default test command at the plugin level
args - optional, overrides the args of the test command at the plugin level
env (or vars) - a list of env variable name/value combinations to be passed to the executor

New: Tests could be invoked with any of the following syntaxes:

meltano run <plugin>:test - runs any and all tests defined in the plugin declaration.

If the test command exists but no tests: declaration, only the one test command will be executed.
If the tests: entry also exists, all enumerated tests will be run in order.
If the test command does not exist, the command fails.

meltano test --all (a new cli command) runs all defined tests in all plugins.
meltano test <plugin> runs all defined tests for the named plugin.
meltano test <plugin1> <plugin2> runs all defined tests for the named plugins.
meltano test <plugin>:<test-name> runs a named test for the named plugin.
meltano test <plugin1>:<test-name1> <plugin2>:<test-name2> runs multiple named tests for the named plugins.

Future Considerations:
Sequencing would need to be provided explicitly in the v1 release, but depends_on behavior could be added in a v2, perhaps after environments (#2869) is released.
Previous proposals, click to expand
## Option A: Dedicated CLI command `meltano validate` (confirmed first iteration)
This would run validations as a dedicated top-level command. How the integration is performed would be governed by (a) custom code in meltano library and/or (b) configuration specs in the validators: entry in discovery.yml.
Option B: Integration with meltano elt (won't do, deprecating in favor of meltano run)
Could be enabled/disabled similar to how transforms are treated, with a CLI flag.
Option C: Integration with (WIP) meltano run (will do, but in future iteration)
Could be listed in a pipeline definition such as:
meltano run tap-salesforce target-snowflake dbt:test ge:test
Given an invocation such as the above, Meltano may be able to infer that the two validators can run in parallel, and may automatically parallelize them.

View 45 previous comments from the original issue on GitLab


fix: Fix missing arguments in native func decl on Android

We were missing the two new arguments in the native function declaration. cc @rodgomesc
Fixes #44

Uops 😅


bump version and republish gem?

The gem paymill command installs an old version of the gem.

Any news on the RubyGems release? I can't currently use this repo in a gem I'm maintaining and have to resort to the dkd gem.

Looks like paymill gem on rubygems https://rubygems.org/gems/paymill points to dkd repo.
Which one is official?
There are no commits on both repos for a whle.

@morgoth I believe this is the "official" repo but its sadly not available as a standalone gem, you can use it by using the github option in your Gemfile.

I'm using dkd repo as I need a commit https://github.com/dkd/paymill-ruby/commit/3f18fd706909aad1b994a4c8d56ab2f085657e62 which is not present in this repo.

released under https://rubygems.org/gems/paymill_ruby


Reduction of the number of colors in the Project Settings Quality options

The ability to reduce the amount of colors like 256 colors in the project settings could allow to convert a 3D game into a retro game. It could be used in combination with a video scaler with sharp pixels for a pixel art look: https://github.com/godotengine/godot/issues/18661

Modern graphics hardware cannot always use a 16-bit color depth, let alone a 8-bit color depth. Palette reduction can be done using a shader (this way, you have full control over the palette to use).

I think the actual intention is not converting an image to 8/16-bits but actually having an ability to reduce the number of colors alone even if the format is unchanged.

This can be implemented using a paletting shader (as is done in engines like GZDoom), closing. Video scaling can be implemented using custom viewports or setting the stretch mode to viewport in the Project Settings.


Italicizing with jQuery .text not working

Challenge Change Text Inside an Element Using jQuery has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

jQuery Playground

#left-well

        <button class="btn btn-default target" id="target1">#target1</button>
        <button class="btn btn-default target" id="target2">#target2</button>
        <button class="btn btn-default target" id="target3">#target3</button>

#right-well

        <button class="btn btn-default target" id="target4">#target4</button>
        <button class="btn btn-default target" id="target5">#target5</button>
        <button class="btn btn-default target" id="target6">#target6</button>

This is not a challenge issue. Reread the instructions and look carefully at the jQuery method you're using. Please visit the Help Chat if you need further challenge help. Thanks and happy coding!


Latest docker image crashes on bootstrap

Description of bug:
I noticed that my docker node was using a lot more cpu than normal. It was stuck in trying to resolve a fork during bootstrap. I've seen that before and usually restarting will fix everything.
So I killed the docker instance.
docker pull nanocurrency/nano
That got me the latest:
Digest: sha256:eebfa377e35f733f5cde8b99a36f73951ee4c7ac31fa446daf187a06077a35db                                                                                Status: Downloaded newer image for nanocurrency/nano:latest
Then I ran:
docker run -d -p 7075:7075/udp -p 7075:7075 -p [::1]:7076:7076 -v ~:/root nanocurrency/nano
That starts up and I can curl and get blocks:
curl -g -d '{ "action": "block_count" }' '[::1]:7076' {                                                                                "count": "6054794",                                                                                "unchecked": "62366"                                                                                }
However it will crash again after a few minutes.
Describe the results you received:
Crashed.
Describe the results you expected:
It not to crash.
Additional information you deem important (e.g. issue happens only occasionally):
Environment:

logs
[2018-02-15 19:51:40.104973]: Completed frontier request, 259 out of sync accounts according to [::ffff:<IP_ADDRESS>]:7075                                          [2018-02-15 19:51:40.105230]: Requesting account xrb_1w51hsajzf4ksz36hri997yr8xi9uzhyfaa4gmzd6ydwxbjr9sy6j77fz8f9 from [::ffff:<IP_ADDRESS>]:7075. 255 accounts in queue                                                                                [2018-02-15 19:51:40.524711]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:40.526373]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:40.527546]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:40.548008]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:40.573461]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:44.033547]: Requesting account xrb_3ace3kkhe6wdygadnwktkajuqn6xdc11nqckzrjdopi77bs4kik5jwqdfeyp from [::ffff:<IP_ADDRESS>]:7075. 5 accounts in queue                                                                                [2018-02-15 19:51:45.105586]: Error receiving block type Operation canceled                                                                                [2018-02-15 19:51:45.105544]: Error receiving block type Operation canceled                                                                                [2018-02-15 19:51:45.105585]: Error receiving block type Operation canceled                                                                                [2018-02-15 19:51:45.438427]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.451601]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.453951]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.522396]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.527986]: Error receiving block type Operation canceled                                                                                [2018-02-15 19:51:45.531654]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.569697]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.572297]: Flushing unchecked blocks                                                                                [2018-02-15 19:51:45.572385]: Finished flushing unchecked blocks                                                                                [2018-02-15 19:51:45.572413]: Completed pulls                                                                                [2018-02-15 19:51:45.572715]: Bulk push finished                                                                                [2018-02-15 19:51:45.572891]: Exiting bulk push client                                                                                [2018-02-15 19:51:45.589418]: Missing confirmed block 0F227997247D31AE650776DDABC7BE3FBAD2F23F11CC14FBEF0C7E6257519B89                                                [2018-02-15 19:51:45.589595]: Starting bootstrap attempt                                                                                [2018-02-15 19:51:45.605374]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.606991]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.671927]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.680508]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.756117]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.769161]: Connection established to [::ffff:<IP_ADDRESS>]:7075                                                                                [2018-02-15 19:51:45.771886]: Connection established to [::ffff:<IP_ADDRESS>]:7075

I wiped all of the data in RaiBlocks and started bootstrapping. Then it got stuck at 4.8 Million blocks.

I'm getting the following error with the newest build.  Will try moving DB and starting from scratch.
/entry.sh: line 10: 8 Segmentation fault /usr/bin/rai_node --daemon

Yeah there's for sure a segfault somewhere when using an old db.

I copied my old DB back in after it created the new config.json, and it started up just fine with the v9 DB.

This is by design, build with Debug and you'll see an assertion instead.

You got this behavior with the v9.0 DB?  That's not expected.
If you had one from master leading up to 10.0.

I was just using the nanocurrency/nano docker image

Hopefully this is fixed now that there's a proper versioning for docker.


Add SD card data logging capability

The iSensor-SPI-Buffer hardware platform has a SD card slot connected to SPI3. Need to develop software support for autonomous data logging to the SD card (for use in battery powered applications without a PC).

In an effort to prevent data corruption, we might be able to use the LTC4412 to detect power loss and swap over the MCU supply to a supercap backup. The proposed supercap is CPH3225A-2K.

Software support in progress. Should be mostly done, having issue getting SD card to mount correctly.

Finally done!!! Want to resolve USB data corruption issues, then will push a firmware rev 2.0 release with this data logging feature


Sorting Algo Visualizer Using HTML-CSS-JS

@Durgesh4993 I have submitted the Pull Request. Please merge it with "Hacktoberfest-label".

@Durgesh4993 I have submitted two PR but still it is showing not accepted. Please merge it so that I can contribute further.

@Durgesh4993  I have submitted two PR but still it is showing not accepted. Please merge it so that I can contribute further.

@Durgesh4993 I have submitted two PR but still it is showing not accepted. Please merge it so that I can contribute further.

@Durgesh4993 I have submitted two PR .Kindly merge it.

Hey @Durgesh4993,
I kindly request that you merge the pull request, as it has already been pending for more than four days.
Thank you!

Hey @Durgesh4993,
I kindly request that you merge the pull request, as it has already been pending for more than four days.
Thank you!


[BUG] Import backup offering:  missing parameter 'allowuserdrivenbackups'

Describe the bug
'Import backup offering' cannot be created due to missing required parameter in the dialog. The API complains that the required parameter 'allowuserdrivenbackups' is missing.
To Reproduce
Steps to reproduce the behavior:

Go to 'Offerings > Backup offerings' and try to create a new import.

Expected behavior
User must be able to create a new backup offering.
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 18.04 LTS
Browser: Chrome
Version: 80.0.3987.149 (Official Build) (64-bit)

Additional context
None

@vladimirpetrov as discussed yesterday this form is a missing feature per https://github.com/apache/cloudstack-primate/issues/253
This is duplicate sub-set of above, will close.


Slow detection speed using GPU

Refer to #61 post. I added the custom code for using a video demo. However, when I run the code. The video is process at an average of 5 fps. Even I added --gpu 0 . I tested on picture with both cpu and gpu. The execution time is the same. How to increase the processing speed?

I have met the same problem, have you solved it?

Refer to #61 post. I added the custom code for using a video demo. However, when I run the code. The video is process at an average of 5 fps. Even I added --gpu 0 . I tested on picture with both cpu and gpu. The execution time is the same. How to increase the processing speed?

Maybe you used tensorflow rather than tensorflow-gpu, because when you installed tensorflow-CPU and tensorflow-GPU, only CPU will work, you can try
import tensorflow as tf
with tf.device('/cpu:0'):
a = tf.constant ([1.0, 2.0, 3.0], shape=[3], name='a')
b = tf.constant ([1.0, 2.0, 3.0], shape=[3], name='b')
with tf.device('/gpu:1'):
c = a + b
sess = tf.Session(config=tf.ConfigProto (allow_soft_placement=True, log_device_placement=True))
sess.run(tf.global_variables_initializer())
print sess.run(c)
if error, you need uninstall protobuf, tensorflow-CPU and tensorflow-GPU, and only install tensorflow-GPU


Add /me command, closes #836

It should be better to simply create and override the /me command, instead of blocking it. Here's an image of how it looks like https://gyazo.com/dc6c7193eeb418ab816eaedd1508a9b3

You can still use /minecraft:me no matter what. We can't overwrite that command.

@iEli2tyree011 That's why I added this https://github.com/twizmwazin/CardinalPGM/pull/837/files#diff-c2eee098f5e1d9f71d4efd97974e23a2R5

@Alfalik Did you test that? I've always had problems removing default permissions with the permission module.

@iEli2tyree011 Meh, players can still use default minecraft permissions, minecraft:me in this case.

I'll be honest I'd rather just outright disable the vanilla command

what about just a #toLowerCase.startsWith(/me)

This PR can be closed

it still would be nice to add a cardinal /me so that it uses display names (with ranks and team) instead of white names, but the vanilla one should be left as it is (usable by default, and blocked during mute or gmute) and the same behaviour should be used for cardinal:me

I've ammend the commit, so if a player do /minecraft:me, the player won't have access. Also, a /me command has been added (https://gyazo.com/c584771128c1a7ed04d39871b2d5cb97). As @Pablete1234 said, it display the actual rank and team of the player.

Leave the old chat module as it was, if someone has their server on the bukkit setting that uses vanilla by default it will be better to also block the regular /me (bcos it will be the vanilla one)

The vanilla command is now totally disabled, and I've added a /me command that shows the rank and team of the player.

:+1:

Should have been fixed in 6ce8cbd , thanks for your work in this PR!

@SungMatt it isn't quite fixed, but i agree thar 1.9 fixed quite alot of stuff with player selectors (try /minecraft:say @a[team=observers]) now bukkit properly uses scoreboard team color / names or something, but it's still not the bukkit display name, it's just the scoreboard team color


Google Drive Extension - Rendering No Preview for Images & PDF

I browsed through the code and it looks like there is some issue getting the correct MIME type. It always goes to the 'Unknown File' path. No preview is rendered even for images or PDFs.

the latest version simply failed to deploy https://github.com/dvargas92495/roamjs-google-drive/actions/runs/969862956.
Should be fixed now! https://github.com/dvargas92495/roamjs-google-drive/runs/2958333446

Work perfect now! Thanks very much.


App icon added

App Icon
Added app icon
Linked issues
Resolves #82

Hey, @dk-a-dev, what's the progress on this PR?

@Yash-Waghmare Sorry to kept u waiting this icon was rejected
can u make an iteration of a pumpkin carved with "H" in Halloween styles scary font

@Yash-Waghmare Sorry to kept u waiting this icon was rejected can u make an iteration of a pumpkin carved with "H" in Halloween styles scary font

Actually, I have used current year font for hacktoberfest

will you give me an example of what is wanted ?

@Yash-Waghmare bro i got an awesome design try to implement this one as an app icon
Please try to finish it by today
here is the reference

I know u worked hard on last icon but unfortunately it got rejected, please work on this one and I will merge ur pr by today for sure
Happy Halloween🎃

will you give me an example of what is wanted ?

refer sent message @Yash-Waghmare

@Yash-Waghmare bro i got an awesome design try to implement this one as an app icon Please try to finish it by today here is the reference  I know u worked hard on last icon but unfortunately it got rejected, please work on this one and I will merge ur pr by today for sure Happy Halloween🎃

Great, so should I use this logo directly without modifying it further?

And, also can you send the link of this logo to download

yes u can use it directly, but feel free to experiment with the colours of the logo if you can, if not use it directly

Yaa, got it, thanks

Hey, how is this

Hey, how is this

Do not seem like a logo
Use the earlier one only
I don't have a link
Do u use discord I can send u there drop me hi

Dk_A_Dev#6560

yes u can use it directly, but feel free to experiment with the colours of the logo if you can, if not use it directly
also the image given is itself a cutout shaped logo try to extract the pumpkin use bing ai tools for purpose
@Yash-Waghmare

Ig u can download that from GitHub also

yes u can use it directly, but feel free to experiment with the colours of the logo if you can, if not use it directly
also the image given is itself a cutout shaped logo try to extract the pumpkin use bing ai tools for purpose
@Yash-Waghmare

Ig u can download that from GitHub also

Downloaded, I will do it immediately.

Added the required icon


groupBy nested query using v2 strategy

This PR changes the way v2 groupBy strategy process outer query using the result of inner query as datasource, addressing #3246.
v1 groupBy strategy will use the same approach as before, by building an IncrementalIndex of inner query result, then use the query engine to process each interval on the built inner IncrementalIndex, and build an outer IncrementalIndex to merge the results.
v2 groupBy strategy will process the inner query results directly using a combined approach of process and merge with the v2 Grouper.
This change also fixes #3239 for v2 since AggregatorFactory.getRequiredColumn() is no longer used.

@acslk we won't need incremental index for groupBy after this right?

@fjy the v2 nested query doesn't need incremental anymore. I don't believe incremental index was used anywhere else for v2, so yeah.

@acslk Could you please include a test for the bug in #3239? Since I guess it'll still fail for v1, we could have the test expect a failure for v1 and a pass for v2. (along with a comment explaining what's going on)
See GroupByQueryRunnerTest.testGroupByMaxRowsLimitContextOverrid for an example of another test that works like that.

Some benchmarks:
basic groupBy query:
Benchmark                                     (defaultStrategy)  (initialBuckets)  (numProcessingThreads)  (numSegments)  (rowsPerSegment)  (schemaAndQuery)  Mode  Cnt       Score       Error  Units
GroupByBenchmark.queryMultiQueryableIndex                    v1                -1                       4              4            100000           basic.A  avgt   25  377404.567 ± 12965.980  us/op
GroupByBenchmark.queryMultiQueryableIndex                    v2                -1                       4              4            100000           basic.A  avgt   25  123248.725 ±  2217.685  us/op
GroupByBenchmark.querySingleIncrementalIndex                 v1                -1                       4              4            100000           basic.A  avgt   25  246516.135 ±  8189.603  us/op
GroupByBenchmark.querySingleIncrementalIndex                 v2                -1                       4              4            100000           basic.A  avgt   25   65689.103 ±  2379.866  us/op
GroupByBenchmark.querySingleQueryableIndex                   v1                -1                       4              4            100000           basic.A  avgt   25  205624.715 ±  9910.958  us/op
GroupByBenchmark.querySingleQueryableIndex                   v2                -1                       4              4            100000           basic.A  avgt   25   41422.967 ±  2396.144  us/op

nested groupBy query on master:
Benchmark                                     (defaultStrategy)  (initialBuckets)  (numProcessingThreads)  (numSegments)  (rowsPerSegment)  (schemaAndQuery)  Mode  Cnt       Score       Error  Units
GroupByBenchmark.queryMultiQueryableIndex                    v1                -1                       4              4            100000          nested.A  avgt   25  422383.160 ± 17237.959  us/op
GroupByBenchmark.queryMultiQueryableIndex                    v2                -1                       4              4            100000          nested.A  avgt   25  208302.359 ±  5632.006  us/op
GroupByBenchmark.querySingleIncrementalIndex                 v1                -1                       4              4            100000          nested.A  avgt   25  296041.435 ± 14012.584  us/op
GroupByBenchmark.querySingleIncrementalIndex                 v2                -1                       4              4            100000          nested.A  avgt   25  265163.983 ±  6364.364  us/op
GroupByBenchmark.querySingleQueryableIndex                   v1                -1                       4              4            100000          nested.A  avgt   25  255939.918 ± 14872.745  us/op
GroupByBenchmark.querySingleQueryableIndex                   v2                -1                       4              4            100000          nested.A  avgt   25  265171.625 ± 13430.492  us/op

nested groupBy query on patch:
Benchmark                                     (defaultStrategy)  (initialBuckets)  (numProcessingThreads)  (numSegments)  (rowsPerSegment)  (schemaAndQuery)  Mode  Cnt       Score       Error  Units
GroupByBenchmark.queryMultiQueryableIndex                    v1                -1                       4              4            100000          nested.A  avgt   25  419281.432 ± 16808.199  us/op
GroupByBenchmark.queryMultiQueryableIndex                    v2                -1                       4              4            100000          nested.A  avgt   25  177766.921 ±  3032.577  us/op
GroupByBenchmark.querySingleIncrementalIndex                 v1                -1                       4              4            100000          nested.A  avgt   25  291045.426 ± 16448.389  us/op
GroupByBenchmark.querySingleIncrementalIndex                 v2                -1                       4              4            100000          nested.A  avgt   25   77774.245 ±  4433.090  us/op
GroupByBenchmark.querySingleQueryableIndex                   v1                -1                       4              4            100000          nested.A  avgt   25  246214.304 ±  4907.190  us/op
GroupByBenchmark.querySingleQueryableIndex                   v2                -1                       4              4            100000          nested.A  avgt   25   54673.400 ±  4017.427  us/op

:+1:

@acslk please also update groupbyquery.md describing how nested queries are done (see the "Implementation details" section)

@acslk there's a compilation error:
[ERROR] /home/travis/build/druid-io/druid/processing/src/main/java/io/druid/query/groupby/epinephelinae/GroupByRowProcessor.java:[222,26] cannot infer type arguments for io.druid.query.groupby.epinephelinae.CloseableGrouperIterator<>;

Added the helper class RowBasedGrouperHelper for some common code between RowProcessor and GroupByMergingQueryRunnerV2. The main common thing between these two classes is that they both aggregate on row sequence using the same grouping and spilling mechanism. The helper class include function to create the grouper and accumulator, and make row iterator from grouper.

@acslk could you update the groupbyquery.md docs too, under "Nested groupBys"?

👍

👍


Optimistically reading file footer breaks Tempo caching logic

I like this recent PR and believe it will help in the general case, but Tempo has logic to immediately return the footer length and cache the footer in an off process cache. This PR breaks that behavior by changing the ranges it attempts to read.
Are we good on a PR to make this new behavior configurable? I'd be glad to submit it.

Thanks for chiming in!
OK, let me revert it first and let's think more about it 👍

I opened #195, I think I'm satisfied with this approach, let me know if you have any concerns.

Thanks Achille!


Add controller-tools to /vendor

Adds a fake file (hack/tools.go) to fool go mod tidy into believing
there's a dependency on sigs.k8s.io/controller-tools, and modifies the
makefile to a) use the vendored version of this file and b) avoid ever
trying to compile it (you can't import a non-package).
Tested: regenerated manifests and autogenerate Go code
Fixes #778

/assign @rjbez17
/cc @yiqigao217 @adrianchung @GinnyJI
Ryan - I got tired of people accidentally having the wrong version of controller-gen in their paths so figured that we could just include it as a vendored dependency. The way to do this isn't great but it does appear to work.
wdyt about this?

It seems hacky but I could not find/think of any better solution at the moment. One thing to note was this answer in your linked thread: https://stackoverflow.com/a/55939956. TL;DR: As we think about including client libraries, the tools.go could cause us some pain.
/lgtm
/approve

It seems hacky but I could not find/think of any better solution at the moment. One thing to note was this answer in your linked thread: https://stackoverflow.com/a/55939956. TL;DR: As we think about including client libraries, the tools.go could cause us some pain.

That's a good point, but I think we can use submodules to get around that. The client library should have vastly fewer imports than the service anyway (e.g. no Prometheus).


Support new Wazuh version 4.12.0 in wazuh-security-dashboards-plugin repository

Description
This issue attempts to support a new version 4.12.0 in the wazuh-security-dashboards-plugin repository.
Tasks

[x] Bump 4.12.0 branch to 4.12.0 version on wazuh-security-dashboards-plugin repository, including revision and changelog.

https://github.com/wazuh/wazuh-security-dashboards-plugin/pull/159

LGTM!

LGTM


Screen recording crashes after +15min running

When using screen recording to MP4 (x264 | AAC) recording stops after 15-20min. running.
No webcam or audio, just screen #1 with default options. Tested on v6.0 under W10.

PS.
Beautiful code. Congratulations.

I need to know a few more things:

FPS
Screen Size

Also, is there high CPU or Memory usage before recording stops.

Tested on 2 different screens: 1920x1080 and 1680x1050.
FPS as default (10).
Not high CPU usage observed. Memory consumption goes up and down during whole test, with max. around 3.2GB.

So, memory consumption should be the problem.
Since, Capture is built in Prefer32bit mode, the maximum memory available to it is 4GB.
I will try to reproduce this issue on my systems.

Fine, I have confirmed the issue.
It's happening when not using Desktop Duplication.
Will try to fix and do a new release ASAP.

Thank you!

v6.0.1 released

Fine, I have confirmed the issue.
It's happening when not using Desktop Duplication.
Will try to fix and do a new release ASAP.

I'm also having this issue. Unfortunately "Desktop Duplication" isn't available as I'm running the video recorder in a virtual machine in Azure. Is there any other way to fix this for GDI as well? :)


Update readme about backend implementation.

Update the description of the method for adding a new adapter.

Thanks. A more thorough update to the docs is coming soon, but this helps.


simple_launch: 1.7.1-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository simple_launch to 1.7.1-1:

upstream repository: https://github.com/oKermorgant/simple_launch.git
release repository: https://github.com/ros2-gbp/simple_launch-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: 1.7.0-1

simple_launch
* list[] -> List[] for type hints in 20.04
* detail on __ns for services
* add service call at launch
* Contributors: Olivier Kermorgant

I merged this by mistake even though Humble is currently being held for sync.
@audrow please feel free to revert this PR if it creates problems for the sync. We can then revert the revert once the sync hold is released.

Hi,
I released one day too late and did not dare to ask for a last-minute merge.
Anyway there is no breaking change in this commit, only an additional feature (call a service from a launch file).


subsys: usb/class/hid: make interrupt endpoint size configurable

The Kconfig option HID_INTERRUPT_EP_MPS does not have a prompt entry,
so it is not configurable in practice. Fix that.
Signed-off-by: Aurelien Jarno<EMAIL_ADDRESS>

Codecov Report

Merging #8372 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8372   +/-   ##
=======================================
  Coverage   64.61%   64.61%
=======================================
  Files         422      422
  Lines       40284    40284
  Branches     6800     6800
=======================================
  Hits        26030    26030
  Misses      11121    11121
  Partials     3133     3133

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8df42eb...917480b. Read the comment docs.


Bug: WASM library is crashing in Node.js

Describe the bug
The package wasm-themis can not be used with Node.js because it tries to call fetch() on a file path.
To Reproduce
Steps to reproduce the behavior:

Install Node.js v22
Run npm i wasm-themis
Minimal example script

const themis = require('wasm-themis');

async function test() {
    await themis.initialized;
    console.log('Themis initialized');
    const keyPair = new themis.KeyPair();
    console.log('Generated key pair:', keyPair);
}

test();

Exception:
TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13 {
  [cause]: Error: unknown scheme
      at makeNetworkError (node:internal/deps/undici/undici:9166:35)
      at schemeFetch (node:internal/deps/undici/undici:10568:34)
      at node:internal/deps/undici/undici:10410:26
      at mainFetch (node:internal/deps/undici/undici:10429:11)
      at fetching (node:internal/deps/undici/undici:10377:7)
      at fetch (node:internal/deps/undici/undici:10246:20)
      at fetch (node:internal/deps/undici/undici:13390:10)
      at fetch (node:internal/bootstrap/web/exposed-window-or-worker:72:12)
      at instantiateAsync (C:\Users\info\Documents\Git\hash-chat\backend\node_modules\wasm-themis\dist\libthemis.js:9:19056)
      at createWasm (C:\Users\info\Documents\Git\hash-chat\backend\node_modules\wasm-themis\dist\libthemis.js:9:19666)
}

Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):

OS: Windows 11
Hardware: 64-bit
Themis version<EMAIL_ADDRESS>Installation way: via package manager

Additional context
A temporary workaround I found is modifying the function instantiateAsync in the file libthemis.js by adding return instantiateArrayBuffer(receiveInstantiationResult); to the begging of the function.

Thank you for reporting!
That's definitely not expected, we will test on Linux/macOS to see if we could reproduce the issue, or maybe it will required a windows-only fix.