Get 404 when fetch compiler list

Describe your issue here.
Environment

Deployment type (Manual/Docker/Docker-compose): Manual
Elixir & Erlang/OTP versions (elixir -version): Elixir 1.13.4 Erlang/OTP 24
Node JS version (node -v): v16.19.1
Operating System: ubuntu 22.04
Blockscout Version/branch/commit: 944434363d03607c45f95e00664b24138bae4093
Archive node type && version (Erigon/Geth/Nethermind/Ganache/?): Geth

Steps to reproduce
blockscout-rs commit is 8c849460e10129b10418e7142e2bcf2ac7ac3b3f
apps/explorer/lib/explorer/smart_contract/rust_verifier_interface.ex
function get_versions_list get
%HTTPoison.Response{
  body: "",
  headers: [{"content-length", "0"}, {"date", "Sat, 25 Feb 2023 15:43:50 GMT"}],
  request: %HTTPoison.Request{
    body: "",
    headers: [],
    method: :get,
    options: [],
    params: %{},
    url: "http://<IP_ADDRESS>:8043/api/v2/verifier/solidity/versions"
  },
  request_url: "http://<IP_ADDRESS>:8043/api/v2/verifier/solidity/versions",
  status_code: 404
}

Expected behaviour
Follow the doc here
I can get a list from curl <IP_ADDRESS>:8043/api/v1/solidity/versions
{"versions":["v0.8.19+commit.7dd6d404","v0.8.18+commit.87f61d96","v0.8.17+commit.8df45f5f","v0.8.16+commit.07a7930e","v0.8.15+commit.e14f2714","v0.8.14+commit.80d49f37","v0.8.13+commit.abaa5c0e","v0.8.12+commit.f00d7308","v0.8.11+commit.d7f03943","v0.8.10+commit.fc410830","v0.8.9+commit.e5eed63a","v0.8.8+commit.dddeac2f","v0.8.7+commit.e28d00a7","v0.8.6+commit.11564f7e","v0.8.5+commit.a4f2e591","v0.8.4+commit.c7e474f2","v0.8.3+commit.8d00100c","v0.8.2+commit.661d1103","v0.8.1+commit.df193b15","v0.8.0+commit.c7dfd78e","v0.7.6+commit.7338295f","v0.7.5+commit.eb77ed08","v0.7.4+commit.3f05b770","v0.7.3+commit.9bfce1f6","v0.7.2+commit.51b20bc0","v0.7.1+commit.f4a555be","v0.7.0+commit.9e61f92b","v0.6.12+commit.27d51765","v0.6.11+commit.5ef660b1","v0.6.10+commit.00c0fcaf","v0.6.9+commit.3e3065ac","v0.6.8+commit.0bbfe453","v0.6.7+commit.b8d736ae","v0.6.6+commit.6c089d02","v0.6.5+commit.f956cc89","v0.6.4+commit.1dca32f3","v0.6.3+commit.8dda9521","v0.6.2+commit.bacdbe57","v0.6.1+commit.e6f7d5a4","v0.6.0+commit.26b70077","v0.5.17+commit.d19bba13","v0.5.16+commit.9c3226ce","v0.5.15+commit.6a57276f","v0.5.14+commit.01f1aaa4","v0.5.13+commit.5b0b510c","v0.5.12+commit.7709ece9","v0.5.11+commit.22be8592","v0.5.10+commit.5a6ea5b1","v0.5.9+commit.c68bc34e","v0.5.8+commit.23d335f2","v0.5.7+commit.6da8b019","v0.5.6+commit.b259423e","v0.5.5+commit.47a71e8f","v0.5.4+commit.9549d8ff","v0.5.3+commit.10d17f24","v0.5.2+commit.1df8f40c","v0.5.1+commit.c8a2cb62","v0.5.0+commit.1d4f565a","v0.4.26+commit.4563c3fc","v0.4.25+commit.59dbf8f1","v0.4.24+commit.e67f0147","v0.4.23+commit.124ca40d","v0.4.22+commit.4cb486ee","v0.4.21+commit.dfe3193c","v0.4.20+commit.3155dd80","v0.4.19+commit.c4cbbb05","v0.4.18+commit.9cf6e910","v0.4.17+commit.bdeb9e52","v0.4.16+commit.d7661dd9","v0.4.15+commit.8b45bddb","v0.4.14+commit.c2215d46","v0.4.13+commit.0fb4cb1a","v0.4.12+commit.194ff033","v0.4.11+commit.68ef5810","v0.4.10+commit.9e8cc01b"]}

Actual behaviour
Get 404 from /api/v2/verifier/solidity/versions

@hundredark It looks like you are starting the old version of verifier. If you are running all services via https://github.com/blockscout/blockscout/blob/master/docker-compose/docker-compose.yml, then could you try to manually remove all smart-contract-verifier images (especially with a main tag), and try to docker compose up it again

I follow the doc
Install by
git clone git@github.com:blockscout/blockscout-rs.git
cd blockscout-rs/smart-contract-verifier
cargo build --release --bin smart-contract-verifier-http

then run blockscout-rs/smart-contract-verifier/target/release/smart-contract-verifier-http with SMART_CONTRACT_VERIFIER__CONFIG of a .toml config
Must I run verifier from docker?

Sorry, I believe we need to update the documentation.
Could you run cargo build --release --bin smart-contract-verifier-server instead?
And use configuration as specified in https://github.com/blockscout/blockscout-rs/tree/main/smart-contract-verifier/smart-contract-verifier-server

The new version of verifier uses grpc/http transcoding to support both grpc and http endpoints. To compile proto files you also need to install protoc compiler, and protoc-gen-openapiv2 to generate corresponding OpenApi spec.
You may have a look into the following action, to get the idea of what is require and how those dependencies could be obtained: https://github.com/blockscout/blockscout-rs/blob/main/.github/actions/deps/action.yml

Problem solved. Thank you for your help.


fix pool snapshot and linear pools events

This PR adds liquidity field to PoolSnapshot and removes price rate events from Linear Pools (we won't emit those events anymore).
The saveSwapToSnapshot isn't needed because we create and update the PoolSnapshot inside the createPoolSnapshot function. Also, I changed the argument of that function from poolId to pool so we don't need to load that entity every update.
Finally, this condition ensures we don't sum up volume and swapFees when investing or withdrawing liquidity from Linear Pools.

I'm deploying some last-minute changes I made to it. After my Subgraph syncing, I'll make sure everything is fine and add the links here.


this fixes the cannotReturn implementation and adds a couple of tests for it.

For the testcases I also had to fix the doItContext creation - while a doItMethod does not have arguments or copiedValues, it may have temporaries. Also the class is UndefinedObject, but the receiver is nil

Not sure if you had something like this in mind.
I ended up adding not a flag to contexts but their associated process (the process with the (potentially conceptual for active process) stack trace they live on). I think this has similar runtime performance impact, but greater potential for other uses in the future

Not sure if you had something like this in mind.
I ended up adding not a flag to contexts but their associated process (the process with the (potentially conceptual for active process) stack trace they live on). I think this has similar runtime performance impact, but greater potential for other uses in the future

Cool that you got this working without iterateFrames! My only concern, however, is that you are using a Map in SqueakImageContext. This could cause two different problems: 1) it may introduce a leak (you never know what kind of code is running, not sure we can ensure there won't be any leaks). And 2) Map is highly recursive which the partial evaluator does not like much. So there could again be a performance problem. Having learned from my own premature optimizations, I wonder what other uses you have in mind for this. AFAICT the OpenSmalltalkVM does not have such an infrastructure, but maybe you have a good reason we want this in GraalSqueak. With a flag, on the other hand, we wouldn't hit the problems I mentioned before.

The map is not part of the infrastructure, it is only used during image load time, as just another step in initializeAfterLoadingImage(), before any activity starts, and it is cleared right there as well

It is used just as a temporary holder for the suspended contexts when filling the process objects, since at that time contexts are not yet initialized.

The only thing that is added as part of the infrastructure is a process field (instead of a flag) on the context

The map is not part of the infrastructure, it is only used during image load time, as just another step in initializeAfterLoadingImage(), before any activity starts, and it is cleared right there as well.
It is used just as a temporary holder for the suspended contexts when filling the process objects, since at that time contexts are not yet initialized.

Sorry my bad...you are right!

The only thing that is added as part of the infrastructure is a process field (instead of a flag) on the context

What other uses of this new reference do you have in mind?

for one, I think this could also be used for the other places where we do iterate over frames - finding the unwind and exception handling blocks

Hi @fmateoc,
Sorry for the delay...I haven't forgotten about this PR. I've just been very busy with a couple of other things. Plus our benchmark infrastructure is currently broken due to the upgrade to 19.3. But once that's fixed, I'll check if this PR introduces any significant performance penalties and will try to integrate it.

No problem, I knew when I started that this was an open-source project, with everyone a volunteer, plus with apparently only you as an active developer, and you might have other priorities as well. Anyway, I am interested enough in the project that I did not just stop and wait for your feedback - I continued on my own, I think I am making good progress, and, quite frankly, it feels liberating to not be subject to the restrictions of having to have everything approved by somebody else.

Well that's fair enough. I'm going to re-open this PR as it adds support for cannotReturn. Handling error cases correctly is important, but as you suspected, I have other priorities at the moment (in no particular order):

Supporting language interop
Improving performance
Staying up-to-date with GraalVM releases
Adding missing primitives (e.g snapshot), plugins, and other core features

As I mentioned before, I'm particularly cautious and hesitant when it comes to changes to the interpreter loop or bytecode implementations as these are performance-critical parts in GraalSqueak.
Nonetheless, I'd also like to understand your goals and priorities, and I would really appreciate any contributions from you. So if we could work something out that works for both of us, that'd be great. Maybe we could talk about this over a video call?

Sure, I'd be happy to talk, but I am right now on vacation in a remote national park (Big Bend, Texas), with very poor connectivity. I'll be back in NY on Jan 4th.
Anyway, my priorities regarding this project are (I think for me they do have a ranking)

adhering strictly to the language semantics
improving performance
improving runtime debuggability
improving source readability
staying up-to-date with graalvm
adding missing primitives - indeed, I think snapshot would be an important one

@fmateoc Sounds good, looks like our goals are not that different. With regard to 1. and 2., however, we had to make some trade-offs (e.g. interrupt handling).
Nonetheless, enjoy your days off! Would you have some time on Jan 7th for a call? We can also move this sort of conversation to a private chat in the GraalVM Slack.

January 7th sounds good. GraalVM slack also sounds good :)

Looks like the AWFY benchmarks show no performance regressions (probably because they are not using non-local returns). Also, I've cleaned a few things up (https://github.com/hpi-swa/graalsqueak/commit/bf7ba33ea29d5721e87dbe40f4eb668d1b8900bf) and moved the suspendedContexts map to the image reader (https://github.com/hpi-swa/graalsqueak/commit/e633184319f23dd8b5a163cabc8ef3ead3ecba7d). If all tests are still passing, it's time to get this merged! :)


"Error: Not supported at MyAlgoConnect.signTransaction" when signing app create transaction

I keep getting Error: Not supported at MyAlgoConnect.signTransaction when signing an app create transaction, and it doesn't seem to matter which TEAL version I'm using.
Example code below:
let createApp = async () => {
  let accounts = await myAlgoWallet.connect();
  let params = await algodClient.getTransactionParams().do();

  let transaction = {
    from: accounts[0].address,
    type: 'appl',
    appOnComplete: 0,
    appApprovalProgram: "AiABASI=",
    appClearProgram: "AiABASI=",
    appLocalInts: 0,
    appLocalByteSlices: 0,
    appGlobalInts: 1,
    appGlobalByteSlices: 1,
    ...params
  };

  let signedTransaction = await myAlgoWallet.signTransaction(transaction);
}

Am I doing something wrong or is application create transactions really not supported?
Thanks!

@salgodev thanks for reporting. Today, we allowed signing create and update appl.

Thanks @Alex99y! I've tried it out and it works perfectly!


temperature and humidity not reflected for the tvoc sensor

The TVOC gets updated fine, but humidity and relative humidity stays 0.0. Is it a known problem? Thanks!

I have the same problem after i updated the firmware of the sensor from 24 to 29. With the older firmware the temperature and humidity was working.

I am new to this... But I see the same issue with a recently acquired TVOC. Any chance of a fix?

Found confirmation that the firmware 29 has changed how the device is reporting the values. The zigpy project has updated code to handle the new reporting: https://github.com/zigpy/zha-device-handlers/commit/b6556169bf641e8f2eb882e8ace4a5a1ab4552d5


Azure Automate Module

How do you import this module into Azure Automation runbooks?

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

ID: 0d545e9a-1c44-5e71-4d9a-2ad6aa31ddab
Version Independent ID: 67677fbc-3e52-d292-659d-6d3e11d0fef1
Content: ActiveDirectory
Content Source: docset/windows/addsadministration/ActiveDirectory.md
Product: w10
Technology: powershell-windows
GitHub Login: @andreabarr
Microsoft Alias: v-anbarr

The issues section of this repository is intended for documentation problems.
Please consider checking any relevant resources and asking the community about your problem via the following link.
PowerShell Community
Also, feel free to reply if there is anything else that could be done to improve the document itself.
Thanks.


docs: Re-add 'Tags for the ASG to support cluster-autoscaler scale up from 0' example

Description
Re-added the example for how to tag ASGs for Cluster autoscaler labels and taints alongside this module, which was removed here: https://github.com/terraform-aws-modules/terraform-aws-eks/commit/b2e97ca3dcbcd76063f1c932aa5199b4f49a2aa1#diff-71ded283a800b9517e86d6155ef5af95710eacbbfda4a87d39b4339e3a6f211fL672
Motivation and Context

This example is incredibly helpful and can be used by the many people asking about cluster autoscaler scale from 0.
Breaking Changes

None
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

/un-stale

I think these are no longer needed starting with 1.24: https://github.com/kubernetes/autoscaler/pull/4491
Seems that autoscaler picks up this info directly from the managed node group now

This PR is included in version 19.15.0 :tada:


network: Only insert global addresses into the DHT.

Currently every address reported via libp2p-identify is inserted into the DHT which thus contains a multitude of unreachable addresses such as from <IP_ADDRESS>/8 or <IP_ADDRESS>/8.
Issue #5099 suggested a dedicated service over UDP to gauge the reachability of an address, which would however incur extra I/O costs and be of limited use.
As an alternative and simpler tactic, this PR only allows global IP addresses to be inserted into the DHT unless an explicit command-line flag --allow-non-global-addresses-in-dht is given or a node is started with --dev. This opt-in behaviour is meant to allow site-local networks to still make use of a DHT.

You probably have to enable the flag for tests to pass. The tests use /memory/... addresses.

:+1: for B1-clientnoteworthy. Maybe someone is using Substrate in a private IPv4 network.

CLI option name could be a bit more user friendly. Something like --discover-local - Enable peer discovery on local networks. "DHT" is an implementation detail.

CLI option name could be a bit more user friendly. Something like --discover-local - Enable peer discovery on local networks. "DHT" is an implementation detail.

I would be fine changing it to this. The meaning of "discover-local" overlaps perhaps slightly with mDNS but since we have a separate option to disable mDNS I guess it is fine.

Please merge master for the CI to pass.


Adopt initial split of Foundation into multiple modules

Ensure that component module libraries are now picked up alongside Foundation’s.

cfr. https://github.com/apple/swift-corelibs-foundation/pull/1799

hi @millenomi is this still relevant?

based on @millenomi (on slack):  this is obsolete — it’s a different split. it can be closed.


Update-Database is attempting to create a column that would duplicate an existing computed column

I have some computed columns in a SQL database that're giving EF6.2 a good bit of trouble. I'm using this technique.
For some reason, the PM command Update-Database insists on trying to add a column to a table that already exists as a computed column.
I only discovered this by temporarily enabling Automatic Migrations. With Automatic Migrations disabled, I get the famously obscure "Unable to update database to match the current model because there are pending changes and automatic migration is disabled."
Here's the relevant excerpted SQL output from Update-Database -Verbose:
Applying explicit migration:<PHONE_NUMBER>55477_001.
CREATE TABLE [dbo].[LogEntries] (
    [Id] [int] NOT NULL IDENTITY,
    [ReceiveTime] [datetime] NOT NULL DEFAULT '1753-01-01T00:00:00.000',
    [SendTime] [datetime] NOT NULL DEFAULT '1753-01-01T00:00:00.000',
    [LogTime] [datetime] NOT NULL DEFAULT '1753-01-01T00:00:00.000',
    [Scale] [real] NOT NULL DEFAULT 0,
    [Co] [real] NOT NULL DEFAULT 0,
    [O2] [real] NOT NULL DEFAULT 0,
    CONSTRAINT [PK_dbo.LogEntries] PRIMARY KEY ([Id])
)

...

ALTER TABLE [LogEntries] ADD [CorrectionFactor] AS (13.9 / (20.9 - [O2])) PERSISTED

...

Applying automatic migration:<PHONE_NUMBER>07184_AutomaticMigration.
ALTER TABLE [dbo].[LogEntries] ADD [CorrectionFactor] [real] NOT NULL DEFAULT 0
System.Data.SqlClient.SqlException (0x80131904): Column names in each table must be unique. Column name 'CorrectionFactor' in table 'dbo.LogEntries' is specified more than once.

(Note that I've created no migration named AutomaticMigration. EF6.2 seems to be doing this on its own.)
It's worth mentioning that both the database and the table are created successfully. This problem doesn't occur until after my last migration has run.
Expected result
The Update-Database command should complete without error
Actual result
The Update-Database command attempts to create the duplicate column, resulting in a database error
Things I've tried

Use Data Annotations instead of Fluent API, in case of an obscure bug in EF6.2
Delete the database entirely, so as to start from scratch
Double-check all migrations (and supporting code) for accuracy
Exclude all migrations from the project and generate a new one
Add the .Ignore() API; however, that and the .HasDatabaseGeneratedOption() API are mutually exclusive

The .HasDatabaseGeneratedOption() API appears to have no effect. What else can be done to instruct EF6.2 to not attempt to create that column?
Here's my code:
Context
Namespace Db
  Public Class Context
    Inherits DbContext

    Public Sub New()
      MyBase.New(Utils.DbConnectionString)
    End Sub

    Private Sub New(Connection As DbConnection)
      MyBase.New(Connection, True)

      Database.SetInitializer(New CreateDatabaseIfNotExists(Of Context))
      Database.SetInitializer(New MigrateDatabaseToLatestVersion(Of Context, Migrations.Configuration))

      Me.Database.Initialize(False)
    End Sub

    Public Shared Function Create() As Context
      Return New Context(DbConnection)
    End Function

    Private Shared ReadOnly Property DbConnection As SqlConnection
      Get
        Return New SqlConnection(Utils.DbConnectionString)
      End Get
    End Property

    Protected Overrides Sub OnModelCreating(Builder As DbModelBuilder)
      Builder.Configurations.AddFromAssembly(Assembly.GetExecutingAssembly)
      MyBase.OnModelCreating(Builder)
    End Sub

    Public Property LogEntries As DbSet(Of LogEntry)
  End Class
End Namespace

Entity
Namespace Db
  Public Class LogEntry
    Public Property Id As Integer
    Public Property ReceiveTime As Date
    Public Property SendTime As Date
    Public Property LogTime As Date
    Public Property Scale As Single
    Public Property Scc As Single
    Public Property Co As Single
    Public Property O2 As Single

#Region " Computed Columns "

    Public Property CorrectionFactor As Single
      Get
        Return 13.9 / (20.9 - Me.O2)
      End Get
      Private Set(Value As Single) : End Set
    End Property

    Public Property MinutesOffline As Single
      Get
        Return IIf(Me.Scale < 1, 1, 0)
      End Get
      Private Set(Value As Single) : End Set
    End Property

    Public Property OffsetTime As Date
      Get
        Return Me.LogTime.AddHours(-7)
      End Get
      Private Set(Value As Date) : End Set
    End Property

    Public Property Co7Online As Single
      Get
        Return IIf(Me.Scale > 1, Me.Co7, 0)
      End Get
      Private Set(Value As Single) : End Set
    End Property

    Public Property Shift As Short
      Get
        Return IIf(Me.OffsetTime.Hour < 12, 1, 2)
      End Get
      Private Set(Value As Short) : End Set
    End Property

    Public Property Co7 As Single
      Get
        Return Me.Co * Me.CorrectionFactor
      End Get
      Private Set(Value As Single) : End Set
    End Property

#End Region

  End Class
End Namespace

Configuration
Namespace Configurations
  Public Class LogEntry
    Inherits EntityTypeConfiguration(Of Db.LogEntry)

    Public Sub New()
      Me.Property(Function(Entry) Entry.ReceiveTime).IsRequired()
      Me.Property(Function(Entry) Entry.SendTime).IsRequired()
      Me.Property(Function(Entry) Entry.LogTime).IsRequired()
      Me.Property(Function(Entry) Entry.Scale).IsRequired()
      Me.Property(Function(Entry) Entry.Scc).IsRequired()
      Me.Property(Function(Entry) Entry.Co).IsRequired()
      Me.Property(Function(Entry) Entry.O2).IsRequired()

      Me.HasIndex(Function(Entry) Entry.ReceiveTime).HasName("IX_LogEntries_ReceiveTime")
      Me.HasIndex(Function(Entry) Entry.SendTime).HasName("IX_LogEntries_SendTime")
      Me.HasIndex(Function(Entry) Entry.LogTime).HasName("IX_LogEntries_LogTime")
      Me.HasIndex(Function(Entry) Entry.Scale).HasName("IX_LogEntries_Scale")
      Me.HasIndex(Function(Entry) Entry.Scc).HasName("IX_LogEntries_Scc")
      Me.HasIndex(Function(Entry) Entry.Co).HasName("IX_LogEntries_Co")
      Me.HasIndex(Function(Entry) Entry.O2).HasName("IX_LogEntries_O2")

      Me.Property(Function(Entry) Entry.CorrectionFactor).HasDatabaseGeneratedOption(DatabaseGeneratedOption.Computed)
      Me.Property(Function(Entry) Entry.MinutesOffline).HasDatabaseGeneratedOption(DatabaseGeneratedOption.Computed)
      Me.Property(Function(Entry) Entry.OffsetTime).HasDatabaseGeneratedOption(DatabaseGeneratedOption.Computed)
      Me.Property(Function(Entry) Entry.Co7Online).HasDatabaseGeneratedOption(DatabaseGeneratedOption.Computed)
      Me.Property(Function(Entry) Entry.Shift).HasDatabaseGeneratedOption(DatabaseGeneratedOption.Computed)
      Me.Property(Function(Entry) Entry.Co7).HasDatabaseGeneratedOption(DatabaseGeneratedOption.Computed)
    End Sub
  End Class
End Namespace

@InteXX I don't understand how the technique described in the blog can be used with automatic migrations since it requires editing of the migrations. Can you explain a bit more?

@ajcvickers While the blog author doesn't specify whether he's using them, I suspect not—for exactly the reason you point out. I only enabled them (temporarily) as a last-ditch debugging effort in my attempts to discover what the problem was.

EF Team Triage: This issue is lacking enough information for us to be able to effectively triage it. In particular, it is missing the following information requested in the new issue template. Can you please provide this information?

Steps to reproduce

Ideally include a complete code listing that we can run to reproduce the issue.
Alternatively, you can provide a project/solution that we can run.
BTW we're not just doing this to be mean :smile:... we get a lot traffic on this project and it takes time to attempt to reproduce an issue based on fragments of information. In addition, our attempt is often unsuccessful as the exact conditions required to hit the issue are often not explicitly included in the code provided. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we ask that folks give us a self-contained way to reproduce an issue.
For a guide on submitting good bug reports, read Painless Bug Tracking.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

@ajcvickers
I'm glad you asked for a demo project. While building it up for you today, I was able to identify and solve my problem. You can read about the solution here.
It's been a while since I opened this issue, but I'm pretty sure that at the time I was changing a computed column's datatype in the entity class after the column had already been created in the database. That's what I did today, anyway, and I was able to reproduce the error. However, this time I dug a little deeper and flushed out the casting problem (see link above).
EF must see that different cast and figure it's a new column altogether.
FYI it was the casting error that had me experimenting with changing the entity column datatypes in the first place.
So all is well. I believe we can close the issue unless you have something further you'd like to add.


Update Latest Release

Hey VividCortex,
The latest release on your Releases page is pointing to v.4.1.0. Can you please point it to 4.1.5?

That is just github, it doesn't actually affect anything (unless you are using GitHub's API to get a list of releases... maybe that is how bower works?).
npm had the correct version https://www.npmjs.com/package/angular-recaptcha
Anyway, the latest one has been marked as such. Closing.


Request for Apple Silicon Binaries (v5.5.0 and V4.4.1)

Goals
Run native on Apple Silicon
Expected Results
We are still experiencing random crashes with v5.5.0 but v4.4.1 has proven to be extremely stable.
Testing on Apple Silicon DTK shows a significant performance increase and we would like to release a production version of the application using Realm Cloud on Apple Silicon to showcase the performance improvements of the new hardware.
In order to do this we would need binary builds for Xcode 12 that support Arm64 and x86.  In the longer term we aim to migrate to Mongo Realm and RealmSwift v10.

@duncangroenewald ,
This is basically a duplicate of your previous question. I'll close it.
You can find more information in the Ian's answer here #6929

@pavel-ship-it - and now both issues are closed without any satisfactory answer!
As far as I am aware it is not possible to download and build the Realm Cloud sync versions from the repo.  Yes we can already build RealmSwift standalone version from the repo but we are running with Realm Cloud sync.
Is the client sync component source code available somewhere  or did I miss something ?

@duncangroenewald Please open a ticket via the support portal and we can route you appropriately there. The github is generally for open source users of Realm, ie. without Realm Sync.


Justcoin is coming back

I sure hope our implementation isn't gone forever. I just got an email saying that they are returning.
http://new.justcoin.com

It seems like another ANX domain


[boost-vcpkg-helpers] Build error on x64-windows-static

issue_body.md

Please see https://github.com/microsoft/vcpkg/issues/30604 for how to report an issue.

Duplicate of  https://github.com/microsoft/vcpkg/issues/35681.


Tailwind breakpoints don't work

Why Reproductions are Required

Closing for now. Feel free to reopen with a reproduction link.


Request - Please consider using m4a suffix for downloaded "--extract-audio" aac files.

Hi
I've been using the "--extract-audio" feature.
It seems to do a good job. It extracts the audio without transcoding. That's fine.
When I run command:-
youtube-dl -F http://www.youtube.com/watch?v=RdopMqrftXs
It tells me:-
Available formats:
34	:	flv	[360x640]
18	:	mp4	[360x640]
43	:	webm	[360x640]
5	:	flv	[240x400]
When I use command:-
youtube-dl -t -f 5 --extract-audio http://www.youtube.com/watch?v=RdopMqrftXs
It downloads file:- The_Beatles_-_Let_It_Be-RdopMqrftXs.mp3
When I use command:-
youtube-dl -t -f 43 --extract-audio http://www.youtube.com/watch?v=RdopMqrftXs
It downloads file:- The_Beatles_-_Let_It_Be-RdopMqrftXs.ogg
These are both OK.
But when I use command:-
youtube-dl -t -f 18 --extract-audio http://www.youtube.com/watch?v=RdopMqrftXs
It downloads file:- The_Beatles_-_Let_It_Be-RdopMqrftXs.aac
Would it not be better if the downloaded aac file was muxed in mp4 container - so that the file suffix is m4a, not aac?
I think that FFmpeg can do this job.
If you agree that m4a is more suitable than aac, it might need to be applied to the "audio-format FORMAT" option also.
--audio-format FORMAT    "best", "aac", "vorbis" or "mp3"; best by default
Thanks.

EDIT
I've just tried muxing the TheBeatles aac into m4a with FFmpeg.
It needs "-absf aac_adtstoasc".
Like this:-
ffmpeg -i filename.aac -vn -acodec copy -absf aac_adtstoasc filename.m4a

--extract-audio extracts the aac audio from the mp4 A/V file.
If you want it to remove video it should be called --remove-video ;)

You can now specify --audio-format m4a to get the desired behavior. I'm not sure why mp4 is preferable.
Unless there is a significant advantage of the mp4 container, I'm reluctant to adopt it as the default though.


Fix: mark MaxAliasesOptions's allowList property as optional

The allowList property of the MaxAliasesOptions type is currently marked as required. maxAliasesDefaultOptions provides a default of allowList: [], therefore the allowList option property should be marked as optional.
Currently, to satisfy type checking, consumers not using an allow list still need to explicitly pass an empty array for allowList when configuring maxAliasesPlugin.
Simple fix, just marking the property as optional :+1:

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.94%. Comparing base (30acee6) to head (ff2a1b2).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #685   +/-   ##
=======================================
  Coverage   92.94%   92.94%
=======================================
  Files          17       17
  Lines         340      340
  Branches       90       98    +8
=======================================
  Hits          316      316
  Misses         24       24

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


What is a column?

Ideally we want a binding to a good implementation C function wcswidth to determine how many columns characters takes up, because as far as I can tell, this is the closest to the standard, at least for counting columns on monospace terminals.
vty has an implementation but we probably don't want to depend on the whole thing, so either asking for that to be split out or making our own standalone library for it would be good

[ ] Make a wcswidth package
[ ] Add helper functionality to Chapelure to turn column numbers in terms of unicode codepoints (what you get from length applied to a String, basically) to proper column counts
[ ] Render in terms of proper column numbers. Care needs to be taken to match up the highlights, etc, properly

There already seems to be https://github.com/solidsnack/wcwidth but it seems to have a few issues


chore: config clean-up

:tada: This PR is included in version 1.1.3 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


response gets truncate

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[] iOS
[] Android
[] .NET Standard

Version of OS(s) listed above with issue
Working on Visula studio 2017 professional , Windows 10 and Andoid 8.1 API.
Version of Library
Plugin.BluetoothLE
Installed version : 6.2.0
Expected Behaviour
There should be same behaviout for both Android and IOS. only one response would be there for one request instead of 2.
Actual Behavior
If applicable, please include entire exception - type, message, stacktrace
When I am executing request  with writeWIthResponse, Getting 2 responses in android for same request. Same I do with IOS , Getting single response for same request.
Code of Conduct

No Library Update Requests
No Timeline Requests
Please read through the documentation and FAQs
If you have a complaint about the docs, FIX IT - DO NOT FILE IT HERE!  I won't guarantee everything is always 100% up-to-date since I am just 1 person.
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

Please provide a reproducible test case.  You've given me absolutely nothing to work with.
The description of the issue and the title also aren't matching.  Are you having two different issues?

Title Question - what's being truncated???
Description Question - Do you mean Write?  What is replying twice - I don't understand your issue.

Also please note - this is not a support forum.  If you need help beyond the samples and documentation, I do offer consultancy services.

Hi ,
I am sending command  like below and using write method with notification on. (ToggleNotify method)
var bytes = Encoding.UTF8.GetBytes(command);
var result = await CharacteristicTX.Write(bytes);
After executing it, I m getting response twice in Android.
for example I am expecting result data like $got,1,1.00000,2.00000\r\n
so in first response I receive $got,1,1.0000
and in second response I get  ,2.00000\r\n
but in case of ios I get whole data in one response .
I am expecting whole string in one response for android as well.
hope this info would be sufficient.
Thanks.

The library doesn’t echo commands.  It will only send what you give it, so your issue is not with the library.  I’m assuming by response, you mean the data you are seeing on your peripheral?
  IOS auto negotiates the largest MTU possible.  On android, you must do this yourself as the default MTU is 20 bytes.

Also, you aren’t providing nearly enough for me to figure out what is going on.  You will need to provide a test case of what I have said above is not your issue.
That being said, please be respectful of my time, provide as much detail as possible in the future, and know that support requests are not welcome here.  Only properly framed issues or feature requests

No response - closing due to insufficient details


Issue on startup

Microsoft PowerToys version
0.62.1
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
General
Steps to reproduce

Start PC
Get error
2023-01-13.txt

✔ Expected Behavior
Expected no errors
❌ Actual Behavior
Got error
Other Software
No response

Not updated version

Updated, problem not appering anymore


chore!: bump poa module to d321226

POA params were removed in d321226
GetPoAAdmin() now returns the x/gov module address if POA_ADMIN_ADDRESS is not set
Fix tests, parameters, and documentation to reflect the update

Fixes #21

Summary by CodeRabbit

Documentation

Removed the "Update Parameters (update-params)" section from documentation, streamlining the content.
Updated the README.md to reflect the removal of references to PoA administrators in genesis file descriptions.

New Features

Improved flexibility in retrieving PoA admin addresses during application initialization.
Enhanced testing environment by dynamically setting the POA admin address.

Configuration Changes

Significant adjustments to economic parameters in genesis.json, including setting community tax and inflation to zero.
Removed specific PoA parameters and admin configurations from scripts and configuration files.

Bug Fixes

Improved robustness of the testing environment by ensuring valid admin addresses are set during tests.

ictest-manifest fails because of docker hub "too many request". I confirm it passes locally.


Dead link

The link behind the following text is broken: "See the configurable settings in ApplicationInsightsServiceOptions for the most up-to-date list".
It opens https://github.com/microsoft/ApplicationInsights-aspnetcore/blob/develop/src/Shared/Extensions/ApplicationInsightsServiceOptions.cs which results in a FileNotFound error.

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

ID: 9d4fa84d-4cd3-216e-ca60-885f1565ee29
Version Independent ID: 5c08427b-21d3-b22a-924a-d07d1461ba79
Content: Application Insights for Worker Service apps (non-HTTP apps)
Content Source: articles/azure-monitor/app/worker-service.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @cijothomas
Microsoft Alias: cithomas

https://github.com/microsoft/ApplicationInsights-dotnet/blob/develop/NETCORE/src/Shared/Extensions/ApplicationInsightsServiceOptions.cs new link.

@NenoLoje Thanks for bringing this to our attention.
Thank you @cijothomas for providing the correct link

@NenoLoje Thanks again for bringing this to our notice, a PR has been raised to correct the link in the original documentation, once reviewed and approved the document should reflect the correct link.
Closing this issue for now, if you have any further queries feel free to tag us in your reply and will be happy to continue the conversation. Thanks


DNS to block browser update nag not working

I'm on 10.7.0-32U and trying to follow the guide. Using the given DNS and browser QR code I keep getting the following message: "The Internet browser cannot be used at this time"
This has been reported a number of times on the /r/3dshacks QA thread as well:
https://www.reddit.com/r/3dshacks/comments/548rc3/3dshacking_qa_general_sleep_schedule_edition/

AFAIK, you should have added the DNS before the browser could find out it was outdated. Otherwise, I think it's impossible.

I also get this message, but this is another message. I just think the DNS is down.

It was a brand new 3ds, browser launched for first time.

I was misinformed and have removed those instructions.

The guide is now misleading for 10.7 users. Can't 10.7 users just use nonbrowser entrypoints?


License?

Is this script intended to be shared with others? If so, you sould probably add a license to the repo.

done


Fail to download pre-build dll for Intel Mac

Hi,
I've built CI using GitHub Actions and EXLA.
It succeeded when 0.5 but failed when 0.6. The log shows downloading was failed.
XLA still supports Intel Mac? Will binary for it be available?

Download worked fine for me on both Intel and Arm Macs. What are your logs? Could it be something related to the internet connection?

Oh, really?
I'm testing it again.

This is the same as #43. GitHub Actions macOS runners have fixed IPs, so calls to GitHub API may fall under rate limiting. You can try authorizing the requests by using the CI token:
env:
  XLA_HTTP_HEADERS: "Authorization: Bearer ${{ secrets.GITHUB_TOKEN }}"

@jonatanklosko Thanks! It works well!


Fix UIKit import issue while using MBProgressHUD framewok in Package …

I am using MBProgressHUD in one of my framework.
This framework has Swift.package file which has MBProgressHUD
.package(name: "MBProgressHUD", url: "https://github.com/jdg/MBProgressHUD.git", from: "1.2.0")
When I try to build or test my framework using command swift build & swift test Getting below error.

I have verified after these changes both swift build & swift test working fine.

@matej This repo won't allow me to add you as a reviewer. Just wanted to check and see if there's a process I should go through to get PRs reviewed. I think this PR is necessary to fully accomplish to Swift Package Manager.


[FLINK-34127] Upgrade to flink-connector-parent 1.1.0 to exclude runn…

…ing nested unit tests
The root cause of the duplicate nested test execution is noted in this github issue: https://github.com/junit-team/junit5/issues/3782. TLDR, the outer test runs once (running all its nested tests), then the nested tests run again due to the include test regex.
Surefire also excludes nested tests by default. https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html
I have tested this approach in https://github.com/mas-chen/flink-connector-kafka/pull/8 and realized that excluding tests was only available from 1.1.0 of the parent pom.

This shaves 1-2 minutes from CI


[feature] Add acls visualization

Hi,
I've started to work a little on this feature cause I wanted it for my cluster. Before to go further, as you made a survey with it, I wanted to know if you're okay with this new feature, and to be sure we agree on the good design on it.
The goal is to add a tab in a topic view, called "Acls".
This tab will be divided in two parts :
One is to display user acls and the other to display groups acls. In fact, to connect to a topic, a producer need only to have the user correct but a consumer can be limited to one or more groups.
As I imagine this, I would make it simple, like two tables. One with "user, permission, hosts" and the other with "group, permission, hosts".
I also want to add a new role called "acls/read", because that's a thing we may want to keep for an admin account.
For now, I don't think it's "usefull" to add the modify acls, to start I guess just the visualization is good.
What do you think ?

Hello,
I've no objection on acl on KafkaHQ, and I will be a nice addition to it.
To be honest, it was on my roadmap but I don't have the time for now, so PR will be really appreciate.
For the visualization, I will have opt to a list of users in a table and a detail page with tabs for group and user right.
This one will be transform into a form later when the edition will be available (you know like schema registry page)
The edit part will be a nice addition also, but starting with visualization is already nice.
Does this make sense for you ?

To be sure, I made a quick model.
As I understand, we could have a new view called "users" on the left menu, linking to a list of users :

Then, when we click on the detail link, we go to a dedicated page :

And of course, we may add a tab in the topic visualization to quickly see who has permissions on the topic :

Later, the detail page could be transformed into a form.
Did I get it ?

Exactly !
Just try to condensed the view on detailed page : one rows per topic (or groups) / host and maybe used bootstrap label to display acls inline.
Later, we will add a button on this line to edit the whole part on a dedicated form
Good catch to tab on topic page, maybe also on consumer page :angel:
On these page, I think the same expanded view could be fine (group per user / host this time).
Also could you named it "ACLS" please.
Thanks a lot :+1:


documentation bugs on mobile

docs.binary.ninja has a number of mobile rendering bugs that make it hard to read

resolved on 4_0 docs branch


Why was astropy PR 11693 closed?

PR https://github.com/astropy/astropy/pull/11693 was closed by the bot "because of his previous message". That message was from over four months ago and said that it would close the PR within 30 days if the PR wasn't rebased. The PR was rebased within those 30 days.

Please see https://github.com/astropy/astropy/pull/11693#issuecomment-1066133766 for an explanation. Sorry for the confusion!


Change agent username/password into auto_registration

This change builds upon #189 and replace the username + password authentication between the agents and the lapi with auto_registration (similar to appsec). When use (auto)scaling this approach is preferred as every pod is seen by the lapi as a separate agent, showing a meaningfull name and its ip.

/area agent
/kind enhancement


Swift 3.1 compatibility

I know stable Xcode 8.3 isn't out yet, but Beta version seem unable to compile current version of Dollar (6.1.0). Apparently there are some changes that prevent from evaluating this method properly (Dollar.swift: 150)
open class func compose<T>(_ functions: ((T...) -> [T])...) -> ((T...) -> [T]) {
	 typealias Function = ([T]) -> [T]
	 return {
              var result = $0
	      for fun in functions {
	            let f = unsafeBitCast(fun, to: Function.self)
		    result = f(result) // Cannot convert value of type '(T...)' to expected argument type '[_]'
	      }
	      return result // Cannot convert return expression of type '(T...)' to return type '[T]'
	 }
}

Taking a look.

I just ran with latest Xcode 8.3 and there are no issues. Closing this.


packetry: init at 0.1.0

Description of changes
A fast, intuitive USB 2.0 protocol analysis application for use with Cynthion. https://github.com/greatscottgadgets/packetry
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Thanks for the review & suggestions @afh!

Result of nixpkgs-review pr 332070 run on aarch64-darwin 1

1 package built:

packetry

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1882

Closing in favor of https://github.com/NixOS/nixpkgs/pull/349828


Update README.md

faciliate -> facilitate

Bruhh.

Just make an issue. Why are you so desperate in getting your name in the collaborators


Changes for 3.0

Closes #47
Copied from there:
A summary of the new API / changes that need to be made (likely incomplete and maybe some points are still up for debate):

[x] new function chunk(x; ...) that returns an iterator that delivers the chunks, i.e. views into x. (We choose chunk, singular, here to indicate the verb form to chunk. This is to be in line with enumerate, zip, and co.)
[x] rename chunks(x; ...) to chunk_indices(x; ...) and make the latter return an iterator that delivers the indices (of x) for each chunk.
[x] iterator names: Chunk (returned by chunk) and ChunkIndices (returned by chunk_indices). This is in line with Base.Iterators.Enumerate (returned by enumerate), Base.Pairs (returned by pairs), and Base.Iterators.Zip (returned by zip) I implemented a single iterator ChunksIterator that has a type parameter ReturnIndices or ReturnViews to indicate what will be eventually returned.
[x] drop the legacy API that relies on positional arguments
[x] drop the Symbol option for split. While it is slightly more convenient, it can be less efficient and it doesn't make much sense to have two ways to do the same thing.
[x] make getchunk internal (not public API anymore) + rename it to getchunkindices

What I think might make sense but I'm unsure about / not sure it's worth it:

Should we rename BatchSplit to ContiguousSplit? The latter seems to communicate the critical point more clearly: the resulting chunks hold contiguous data.
I don't like that we use "chunk" on the one hand and "split" on the other hand. Why two terms for the same thing? Perhaps something like chunk(x; n=4, strategy=Contiguous()) or something less verbose makes more sense as it gets rid of "split" terminology entirely?

julia> using ChunkSplitters

julia> function f(x)
           s = zero(eltype(x))
           for xc in chunk(x; n=4)
               s += sum(xc)
           end
           return s
       end
f (generic function with 1 method)

julia> x=rand(10^3);

julia> f(x) ≈ sum(x)
true

julia> function f_indices(x)
           s = zero(eltype(x))
           for idcs in chunk_indices(x; n=4)
               s += sum(@view(x[idcs]))
           end
           return s
       end
f_indices (generic function with 1 method)

julia> f_indices(x) ≈ sum(x)
true

julia> @benchmark f($x)
BenchmarkTools.Trial: 10000 samples with 788 evaluations.
 Range (min … max):  160.057 ns … 195.801 ns  ┊ GC (min … max): 0.00% … 0.00%
 Time  (median):     160.426 ns               ┊ GC (median):    0.00%
 Time  (mean ± σ):   160.774 ns ±   1.690 ns  ┊ GC (mean ± σ):  0.00% ± 0.00%

  ▄██▄                                                          ▂
  ████▇▆▅▄▅▅▅▆▇██▆▅▅▄▄▅▅▄▃▅▅▆▄▄▅▄▅▄▄▅▆▆▇▇▇███▇▇▅▆▅▅▅▅▃▅▁▄▄▄▄▁▄▆ █
  160 ns        Histogram: log(frequency) by time        170 ns <

 Memory estimate: 0 bytes, allocs estimate: 0.

julia> @benchmark f_indices($x)
BenchmarkTools.Trial: 10000 samples with 788 evaluations.
 Range (min … max):  159.688 ns … 181.313 ns  ┊ GC (min … max): 0.00% … 0.00%
 Time  (median):     159.898 ns               ┊ GC (median):    0.00%
 Time  (mean ± σ):   160.350 ns ±   1.865 ns  ┊ GC (mean ± σ):  0.00% ± 0.00%

  ▇█▄▂      ▁                                                   ▁
  █████▆▆▆▆▇█▇▇▅▆▅▄▄▄▁▁▆▅▄▅▅▄▃▃▅▅▇▆▆▇██▇▆▅▆▆▅▄▃▅▄▄▅▅▅▄▅▆▆▃▄▆▃▄▇ █
  160 ns        Histogram: log(frequency) by time        171 ns <

 Memory estimate: 0 bytes, allocs estimate: 0.

Revamped documentation preview: https://juliafolds2.github.io/ChunkSplitters.jl/previews/PR48/

On 1.10, chunk(x; size=10) seems to allocate... Why?
function f_chunk(x; n=nothing, size=nothing)
    s = zero(eltype(x))
    for xdata in chunk(x; n=n, size=size)
        s += sum(xdata)
    end
    return s
end
x = rand(10^3)
b = @benchmark $f_chunk($x; n=4) samples = 1 evals = 1
@test b.allocs == 0
b = @benchmark $f_chunk($x; size=10) samples = 1 evals = 1
if VERSION < v"1.11"
    @test_broken b.allocs == 0 # TODO: why does this allocate on 1.10?
else
    @test b.allocs == 0
end

julia> b = @benchmark $f_chunk($x; size=10) samples = 1 evals = 1
BenchmarkTools.Trial: 1 sample with 1 evaluation.
 Single result which took 1.542 μs (0.00% GC) to evaluate,
 with a memory estimate of 6.19 KiB, over 99 allocations.

Note that chunk_indices(x; size=10) does not allocate.

I noticed that the svg in the old/current docs is wrong. Which one of the two do you prefer?
Indicating the scattering by coloring chunks:

Indicating the scattering by arrows:

I think I prefer the latter. However, the former is kind of the package logo :D

Alright guys, as it turned out, I had the motivation to implement this right away. Please checkout the new (preview) docs and run some tests to see if things are stable.
What I did beyond the points mentioned in the OP is drop 1.6 support (1.10 is the new lower bound).
Also, if you have an idea about https://github.com/JuliaFolds2/ChunkSplitters.jl/pull/48#issuecomment-2363287934 that would be great as well.

The natural next step is to test OhMyThreads.jl with this.

[ ] add a transition guide, that highlights the most important breaking changes

I'll try to look at this tonight. I suspect there's an inference problem here on 1.10, but I'll dig in and see if we can figure out what went wrong.

Should we rename BatchSplit to ContiguousSplit? The latter seems to communicate the critical point more clearly: the resulting chunks hold contiguous data.

I don't like that we use "chunk" on the one hand and "split" on the other hand. Why two terms for the same thing? Perhaps something like chunk(x; n=4, strategy=Contiguous()) or something less verbose makes more sense as it gets rid of "split" terminology entirely?

I also like these changes, in any case.
Concerning https://github.com/JuliaFolds2/ChunkSplitters.jl/pull/48#issuecomment-2363287934 , I've tried now many things, including manually defining functions for each case instead of relying on dispatch for _getchunkindices, but nothing worked. I couldn't detect any type inference problem either.

I also like these changes, in any case.

I still think that it might make sense to consider renaming Batch → Consecutive and Scatter → RoundRobin.
As for renaming split to strategy (or something similar), there are two reasons I didn't do it right away (but I'm still open to be convinced):

strategy feels long compared to split
The package name ChunkSplitters.jl already establishes "chunk" and "split" as terminology.

I prefer not exporting, in particular since the practice of always explicitly using symbols anyway is getting more common (ericphanson/ExplicitImports.jl).

On the one hand, it is nice that one can just do using ChunkSplitters and write chunks(x; n=10, split=RoundRobin()).

I like the trend of explicitly using the bits that one actually needs. However, for this case, it doesn't matter whether we export the <:Split types or not. The question is about what should be "imported" if one simply does using ChunkSplitters. Not exporting anything (are you suggesting that?) seems radical to me. The naive using ChunkSplitters is useful in interactive workflows

This export is actually slightly annoying because the perfect variable name for the return value is chunks, and obviously chunks = chunks(...) doesn't work.
With the current export situation I would simply use
using ChunkSplitters: ChunkSplitters

and always use the ChunkSplitters. prefix for clarity.

Once again, not exporting chunks, the main API of this package, seems bad/too radical to me. And while I see your point about the chunks name clash, the same could be said about size = size(...), length = length(...), and probably many more functions. Moreover, the typical use case of chunks(...) is in combination with for or map in which case you don't store it in a variable anyways.

Yea I just meant that if anything chunks would be the "problematic" export, not the split types.

Just to say that I think this PR is fine, but we need to find a solution to https://github.com/JuliaFolds2/ChunkSplitters.jl/pull/48#issuecomment-2363287934 .

https://github.com/JuliaFolds2/ChunkSplitters.jl/pull/50 fixes https://github.com/JuliaFolds2/ChunkSplitters.jl/pull/48#issuecomment-2363287934

I think this is good to go (unless we want to make other breaking changes).

Thanks a lot @carstenbauer, and others of course, great work!


Document conventional dist jar layout for single-shim deployments [skip ci]

Contributes to #8181
Signed-off-by: Gera Shegalov<EMAIL_ADDRESS>

build


The Create Auctions API

Details

The online Auctions API validator only checks if the item type in the body is a string.
When I tried calling the API, it failed.
The item type should be an available currency, such as "DINERO" or "NEELAM".
The quantity cannot exceed what you own.
This can cause issues for users unaware of these requirements.
It is important to update the validator to reflect these requirements and prevent future errors accurately.
Please fix this in the validator to improve user experience.

assign me


Unit test task attachments

The code introduced in PR #1660 is not completely unit tested. We should at least introduce tests to TaskAttachmentService but preferably to the other classes involved in the PR.

@DanielSchiavini
We can't test TaskAttachmentService b/c it contains the real implementation for CRUD based blob storage in Azure. That's why TaskAttachementService is abstracted by ITaskAttachmentService. Any code that uses ITaskAttachementService should be tested/testable, but testing the service itself has no value.
The only thing I think could be testable by taking a look at the code is how we're building the path to the actual blob. That would be something I consider testable, but it's a very small piece and not really worth the effort.
That, OR we move the abstraction closer to the Azure API and abstract ONLY the Azure calls. For example, any code working with CloudBlobContainer and/or CloudBlockBlob would be abstracted away and our TaskAttachement service would use that abstraction in order to communicate with Azure.
So lines like this:
var blobContainer = CloudStorageAccount.Parse(_options.AzureStorage)
                .CreateCloudBlobClient()
                .GetContainerReference(ContainerName);

blobContainer.Uri.AbsoluteUri
blobContainer.GetBlockBlobReference
blockBlob.DeleteAsync()
container.CreateIfNotExistsAsync
container.GetBlockBlobReference
blockBlob.Properties.ContentType
blockBlob.UploadFromByteArrayAsync
blockBlob.Uri
would have to be abstracted. That's a lot of work, and as we use more and more Azure based functionality, this abstraction would only grow more unweildy... so again, I don't think there is value here.

Also, the Debug.WriteLine statements in this class should be deleted. We don't want that type of stuff in production code.


Make PerformanceStats rendering more efficient

Instead of clearing previous bars and creating new bars each time we render stats graph, try to re-use existing bars.
Also don't re-position the target line every render; it never moves.

OK I believe I have addressed your points.
Thanks
Doug
On Mon, Oct 10, 2016 at 3:13 PM, Ben Tkacheff<EMAIL_ADDRESS>wrote:

@hockeychaos requested changes on this pull request.
In CoreScriptsRoot/CoreScripts/PerformanceStatsManagerScript.lua
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3581774
:

@@ -132,10 +132,19 @@ end
function UpdatePerformanceStatsVisibility()
local localPlayer = PlayersService.LocalPlayer

local isVisible = (GameSettings.PerformanceStatsVisible and localPlayer ~= nil)
if isVisible then

local shouldBeVisible = StatsUtils.PerformanceStatsShouldBeVisible()
print("\n\nUpdatePerformanceStatsVisibility: shouldBeVisible = ", shouldBeVisible);

lets remove this print
In CoreScriptsRoot/CoreScripts/PerformanceStatsManagerScript.lua
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3581774
:

 masterFrame.Visible = true

 masterFrame.Parent = CoreGuiService.RobloxGui

-- Refresh, the contents are stale.
statsViewer:Refresh();

mostly a style thing, but don't need the semicolon
In CoreScriptsRoot/CoreScripts/PerformanceStatsManagerScript.lua
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3581774
:

 masterFrame.Visible = true

 masterFrame.Parent = CoreGuiService.RobloxGui

-- Refresh, the contents are stale.
statsViewer:Refresh();
for i, buttonType in ipairs(StatsUtils.AllStatTypes) do

   local button = statsButtonsByType[buttonType]

   button:Refresh();

same there here wrt semicolon
In CoreScriptsRoot/Modules/Stats/StatsAggregator.lua
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3581774
:

@@ -61,6 +61,11 @@ end
function StatsAggregatorClass:StartListening()
-- On a regular heartbeat, wake up and read the latest
-- value into circular buffer.

-- Don't bother if we're already listening.
if (self._listneing == true) then

typo
In CoreScriptsRoot/Modules/Stats/StatsAnnotatedGraph.lua
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3581774
:

@@ -176,7 +176,11 @@ function StatsAnnotatedGraphClass:_recursiveGetOrderOfMagnitude(estimate, target
return self:_recursiveGetOrderOfMagnitude(estimate*10.0, target)
end

-function StatsAnnotatedGraphClass:_updateValue()
+function StatsAnnotatedGraphClass:UpdateValuesAndRender()

if not StatsUtils.PerformanceStatsShouldBeVisible() then

would it make sense to register/desregister listeners instead of doing if
checks like this? Would be more performant to only make these calls if we
need to
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3581774,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHHDJfq1PV36O3dgnAurXK_yYufIGxjnks5qyriggaJpZM4KS-gr
.

Done, please take a look.
On Mon, Oct 10, 2016 at 5:40 PM, Ben Tkacheff<EMAIL_ADDRESS>wrote:

@hockeychaos commented on this pull request.
In CoreScriptsRoot/Modules/Stats/StatsAnnotatedGraph.lua
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3596455
:

@@ -176,7 +208,11 @@ function StatsAnnotatedGraphClass:_recursiveGetOrderOfMagnitude(estimate, target
return self:_recursiveGetOrderOfMagnitude(estimate*10.0, target)
end

-function StatsAnnotatedGraphClass:_updateValue()
+local counter = 0
whats up with this counter?
In CoreScriptsRoot/Modules/Stats/StatsAnnotatedGraph.lua
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3596455
:

end

self:_updateValue()

self._listenerId = self._aggregator:AddListener(function()

 self:_updateValuesAndRender()

end)
+end

+function StatsAnnotatedGraphClass:OnVisibilityChanged()

if StatsUtils.PerformanceStatsShouldBeVisible() then
self:_maybeStartListening()
self:_updateValuesAndRender()
else
self:_maybeStopListening()

the maybe seems ambiguous. To the person calling this function we will
definitely stop listening when we call this, just the function itself might
not have to do anything as it already is not listening. Can we call it just
stopListening and startListening since the maybe seems like an
implementation detail?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ROBLOX/Core-Scripts/pull/577#pullrequestreview-3596455,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHHDJc8hvP4cNC8s55t-OTBngvANkcLAks5qytrtgaJpZM4KS-gr
.

OK.
Can I resolve the Jira ticket (
https://jira.roblox.com/browse/CLISTUDIO-10755)?
If so, what CL number?
Thanks
Doug
On Tue, Oct 11, 2016 at 10:37 AM, Ben Tkacheff<EMAIL_ADDRESS>wrote:

Merged #577 https://github.com/ROBLOX/Core-Scripts/pull/577.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ROBLOX/Core-Scripts/pull/577#event-819847403, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHHDJaVVNSkALruyxKFqa9ycJtdVZe_Zks5qy8lUgaJpZM4KS-gr
.


fix: mongodb.ts file not removing mongoose-autopopulate library bug

When I select the postgres database, it leads to remove the mongodb related code, but I found that “mongoose-autopopulate”:“^1.1.0” in package.json is not removed.

@hankaibo good catch, thank you!


Blocks don't drop an item when broken

When breaking aether grass, it never dropped an item. I tried using my fist, a diamond shovel, a netherite shovel, a gravitite shovel. Nothing seemed to work. The same is true for aether stone, aether dirt, blueberry bushes, quicksoil, skyroot log, various other blocks. Although cold aether cloud does drop its item.

Ah I see the pinned TODO loot table list. Will close.


Unit testing QR Code Scanner

I have used this qr scanner in my application and this qr scanner runs very well. but I'm having trouble doing unit testing on the qr scanner. how to do unit testing on this qr scanner? should i mock that or there is a way to send values to onRead props?
before, I have tried to mock react-native-qrcode-scanner with this code
jest.mock('react-native-qrcode-scanner', () => {
    const React = require('react');
    const PropTypes = require('prop-types');
    return class MockQRCodeScanner extends React.Component {
        static propTypes = { children: PropTypes.any };

        render() {
            return React.createElement('react-native-qrcode-scanner', this.props, this.props.children);
        }
    }
})

but gives an error "TypeError: scanner.current.reactivate is not a function"
this my code :
ScanQRCodeScreen.js
'use strict';
import React, {useEffect} from 'react';
import {
    View,
    StyleSheet
} from 'react-native';
import QRCodeScanner from 'react-native-qrcode-scanner';

const ScanQRCodeScreen = ({navigation}) => {
    const scanner = React.useRef(null);
    useEffect(() => {
        navigation.addListener('focus', async() => {
            await scanner.current.reactivate();
        });
    },[]);

    const onSuccess = e => {
        console.log(e.data);
    }

    return (
        <View>
            <QRCodeScanner
                onRead={onSuccess}
                ref={scanner}
                showMarker={true}
            />
        </View>
    );
};

ScanQRCodeScreen-test.js
import React, {useRef} from 'react';
import { render, act } from '@testing-library/react-native';

import ScanQRCodeScreen from '../screens/ScanQRCodeScreen';

jest.mock('react-native-qrcode-scanner', () => {
    const React = require('react');
    const PropTypes = require('prop-types');
    return class MockQRCodeScanner extends React.Component {
        static propTypes = { children: PropTypes.any };

        render() {
          return React.createElement('react-native-qrcode-scanner', this.props, this.props.children);
        }
    }
});

let wrapper = null;
const map = {};
const mockedParams = {
    navigation: {
        addListener: jest.fn((events, cb) => {
            map[events] = cb
        })
    },
};
beforeEach(() => {
    wrapper = render(
        <ScanQRCodeScreen {...mockedParams}/>
    );
})

describe('<Renderable>', () => {
    test('ScanQRCodeScreen snapshot', async() => {
        await act(async() => map.focus());
        expect(wrapper).toMatchSnapshot();
    })
})

Hey, as it seems, you're actually mocking it wrongly. Take a look on a log from scanner.current, but much probably, it will be the component instance, which you'll be able to call the methods.
So, try to add the reactivate method in your class-component, as as jest.fn, and probably will gonna work, and additionaly will be able to test the method call as well as it's mocked.


feat(ostracon): add ip filter for kms connection - Triage finschia-sdk#1089

The subject of the triage:

Finschia/finschia-sdk#1089

Desc

Add feature of KMS connection IP filter

Suggestion(Abandon/Maintain/Submit)

Abandon:

We may need this feature or similar ACL features, If someone in security or devops request.

Links

https://github.com/Finschia/finschia-sdk/pull/602

TODO: Check alternative and if there is issue or bug with it then report issue to upstream.


Code: 32 While Trying To Connect To Clickhouse With clickhouse-client

Describe the bug
So I have installed the Clickhouse on ubuntu 18.04 as it was described on the official doc. Everything went fine but when I tried to connect to the clickhouse client with command 'clickhouse-client', it raised the exception ; 'Code: 32. DB::Exception: Attempt to read after eof'. So I googled it and changed the host like 'clickhouse-client --host=<IP_ADDRESS>', but it did not work either. After that I added the line '<listen_host>::</listen_host>' to make the server accept both IPv4 and IPv6 connections. And I restarted the clickhouse-server but this time it did not start. It failed with the following log ;
May 20 14:26:18 whale1 systemd[1]: Started ClickHouse Server (analytic DBMS for big data).
May 20 14:26:18 whale1 clickhouse-server[19659]: Include not found: clickhouse_remote_servers
May 20 14:26:18 whale1 clickhouse-server[19659]: Include not found: clickhouse_compression
May 20 14:26:18 whale1 clickhouse-server[19659]: Logging trace to /var/log/clickhouse-server/clickhouse-server.log
May 20 14:26:18 whale1 clickhouse-server[19659]: Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log
May 20 14:26:18 whale1 clickhouse-server[19659]: Include not found: networks
May 20 14:26:18 whale1 systemd[1]: clickhouse-server.service: Main process exited, code=exited, status=70/n/a
May 20 14:26:18 whale1 systemd[1]: clickhouse-server.service: Failed with result 'exit-code'.

How to reproduce

Which ClickHouse server version to use: ClickHouse server version <IP_ADDRESS> (official build)
Which interface to use, if matters: None
Non-default settings, if any: None
CREATE TABLE statements for all tables involved: No Tables
Sample data for all these tables, use clickhouse-obfuscator if necessary : None
Queries to run that lead to unexpected result: None

Expected behavior
Connecting to the clickhouse client
Error message and/or stacktrace
ClickHouse client version <IP_ADDRESS> (official build).
Connecting to <IP_ADDRESS>:9000 as user default.
Code: 32. DB::Exception: Attempt to read after eof
Clickhouse-server.err.log :::
2019.05.20 10:56:24.657140 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 10:56:24.657218 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 11:39:46.281177 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 11:39:46.281250 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 12:53:19.848887 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 12:53:19.848962 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 12:58:09.012696 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 12:58:10.204468 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 12:58:11.712129 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 12:58:41.952624 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 12:58:49.642155 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 12:59:19.933824 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 12:59:50.236080 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:00:20.487606 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:00:50.736125 [ 1 ] {} <Error> Application: Net Exception: Address already in use: <IP_ADDRESS>:9000
2019.05.20 13:00:57.926192 [ 1 ] {} <Error> Application: Net Exception: Address already in use: <IP_ADDRESS>:9000
2019.05.20 13:01:28.240330 [ 1 ] {} <Error> Application: Net Exception: Address already in use: <IP_ADDRESS>:9000
2019.05.20 13:01:48.137141 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:01:48.137252 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:02:50.838309 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:03:19.934140 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:03:50.237363 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:04:20.439085 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:04:23.856683 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:04:53.961758 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:05:14.898698 [ 1 ] {} <Error> Application: Net Exception: Address already in use: <IP_ADDRESS>:9000
2019.05.20 13:05:45.211912 [ 1 ] {} <Error> Application: Net Exception: Address already in use: <IP_ADDRESS>:9000
2019.05.20 13:06:04.365573 [ 1 ] {} <Error> Application: Net Exception: Address already in use: <IP_ADDRESS>:9000
2019.05.20 13:06:34.480923 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:06:34.481110 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:06:37.078334 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:06:37.078418 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:07:31.004405 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:08:01.176154 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:08:01.176224 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:08:04.751931 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:08:04.752063 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:09:19.681610 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:09:19.681699 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:14:09.162430 [ 1 ] {} <Error> Application: DB::Exception: Effective user of the process (root) does not match the owner of the data (clickhouse). Run under 'sudo -u clickhouse'.
2019.05.20 13:14:47.350694 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:15:17.410533 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:15:47.649017 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:16:17.923267 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:16:48.182886 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:17:05.929757 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:17:36.243328 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:18:06.485609 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::1]:9000
2019.05.20 13:18:35.377643 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 13:18:35.377740 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 14:26:18.535014 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:26:48.710009 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:27:18.970821 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:27:49.237225 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:28:19.514357 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:28:49.728122 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:29:19.990879 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:29:44.655524 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 14:29:44.655590 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>

/var/log/clickhouse-server/clickhouse-server.log : : :
2019.05.20 14:27:49.235449 [ 1 ] {} <Information> Application: Listening http://[::]:8123
2019.05.20 14:27:49.235990 [ 1 ] {} <Information> Application: Shutting down storages.
2019.05.20 14:27:49.236252 [ 1 ] {} <Trace> BackgroundSchedulePool: Waiting for threads to finish.
2019.05.20 14:27:49.236327 [ 1 ] {} <Debug> Application: Shutted down storages.
2019.05.20 14:27:49.236983 [ 1 ] {} <Debug> Application: Destroyed global context.
2019.05.20 14:27:49.237225 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:27:49.237241 [ 1 ] {} <Information> Application: shutting down
2019.05.20 14:27:49.237246 [ 1 ] {} <Debug> Application: Uninitializing subsystem: Logging Subsystem
2019.05.20 14:27:49.237298 [ 21 ] {} <Information> BaseDaemon: Stop SignalListener thread
2019.05.20 14:28:19.476193 [ 1 ] {} <Information> : Starting ClickHouse <IP_ADDRESS> with revision 54418
2019.05.20 14:28:19.485628 [ 1 ] {} <Information> Application: starting up
2019.05.20 14:28:19.490554 [ 1 ] {} <Debug> Application: rlimit on number of file descriptors is 500000
2019.05.20 14:28:19.490593 [ 1 ] {} <Debug> Application: Initializing DateLUT.
2019.05.20 14:28:19.490605 [ 1 ] {} <Trace> Application: Initialized DateLUT with time zone `Europe/Berlin'.
2019.05.20 14:28:19.492593 [ 1 ] {} <Debug> Application: Configuration parameter 'interserver_http_host' doesn't exist or exists and empty. Will use 'whale1' as replica host.
2019.05.20 14:28:19.498806 [ 1 ] {} <Debug> ConfigReloader: Loading config `/etc/clickhouse-server/users.xml'
2019.05.20 14:28:19.500518 [ 1 ] {} <Information> Application: Loading metadata from /var/lib/clickhouse/
2019.05.20 14:28:19.507308 [ 1 ] {} <Debug> Application: Loaded metadata.
2019.05.20 14:28:19.507341 [ 1 ] {} <Information> BackgroundSchedulePool: Create BackgroundSchedulePool with 16 threads
2019.05.20 14:28:19.509654 [ 1 ] {} <Information> Application: Listening http://[::]:8123
2019.05.20 14:28:19.510075 [ 1 ] {} <Information> Application: Shutting down storages.
2019.05.20 14:28:19.510383 [ 1 ] {} <Trace> BackgroundSchedulePool: Waiting for threads to finish.
2019.05.20 14:28:19.510404 [ 1 ] {} <Debug> Application: Shutted down storages.
2019.05.20 14:28:19.511021 [ 1 ] {} <Debug> Application: Destroyed global context.
2019.05.20 14:28:19.514357 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:28:19.514379 [ 1 ] {} <Information> Application: shutting down
2019.05.20 14:28:19.514385 [ 1 ] {} <Debug> Application: Uninitializing subsystem: Logging Subsystem
2019.05.20 14:28:19.514442 [ 21 ] {} <Information> BaseDaemon: Stop SignalListener thread
2019.05.20 14:28:49.692481 [ 1 ] {} <Information> : Starting ClickHouse <IP_ADDRESS> with revision 54418
2019.05.20 14:28:49.701540 [ 1 ] {} <Information> Application: starting up
2019.05.20 14:28:49.706431 [ 1 ] {} <Debug> Application: rlimit on number of file descriptors is 500000
2019.05.20 14:28:49.706473 [ 1 ] {} <Debug> Application: Initializing DateLUT.
2019.05.20 14:28:49.706487 [ 1 ] {} <Trace> Application: Initialized DateLUT with time zone `Europe/Berlin'.
2019.05.20 14:28:49.708339 [ 1 ] {} <Debug> Application: Configuration parameter 'interserver_http_host' doesn't exist or exists and empty. Will use 'whale1' as replica host.
2019.05.20 14:28:49.714754 [ 1 ] {} <Debug> ConfigReloader: Loading config `/etc/clickhouse-server/users.xml'
2019.05.20 14:28:49.719616 [ 1 ] {} <Information> Application: Loading metadata from /var/lib/clickhouse/
2019.05.20 14:28:49.725141 [ 1 ] {} <Debug> Application: Loaded metadata.
2019.05.20 14:28:49.725177 [ 1 ] {} <Information> BackgroundSchedulePool: Create BackgroundSchedulePool with 16 threads
2019.05.20 14:28:49.726430 [ 1 ] {} <Information> Application: Listening http://[::]:8123
2019.05.20 14:28:49.727109 [ 1 ] {} <Information> Application: Shutting down storages.
2019.05.20 14:28:49.727356 [ 1 ] {} <Trace> BackgroundSchedulePool: Waiting for threads to finish.
2019.05.20 14:28:49.727384 [ 1 ] {} <Debug> Application: Shutted down storages.
2019.05.20 14:28:49.727895 [ 1 ] {} <Debug> Application: Destroyed global context.
2019.05.20 14:28:49.728122 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:28:49.728139 [ 1 ] {} <Information> Application: shutting down
2019.05.20 14:28:49.728143 [ 1 ] {} <Debug> Application: Uninitializing subsystem: Logging Subsystem
2019.05.20 14:28:49.728221 [ 21 ] {} <Information> BaseDaemon: Stop SignalListener thread
2019.05.20 14:29:19.948454 [ 1 ] {} <Information> : Starting ClickHouse <IP_ADDRESS> with revision 54418
2019.05.20 14:29:19.956613 [ 1 ] {} <Information> Application: starting up
2019.05.20 14:29:19.961093 [ 1 ] {} <Debug> Application: rlimit on number of file descriptors is 500000
2019.05.20 14:29:19.961123 [ 1 ] {} <Debug> Application: Initializing DateLUT.
2019.05.20 14:29:19.961133 [ 1 ] {} <Trace> Application: Initialized DateLUT with time zone `Europe/Berlin'.
2019.05.20 14:29:19.963038 [ 1 ] {} <Debug> Application: Configuration parameter 'interserver_http_host' doesn't exist or exists and empty. Will use 'whale1' as replica host.
2019.05.20 14:29:19.968895 [ 1 ] {} <Debug> ConfigReloader: Loading config `/etc/clickhouse-server/users.xml'
2019.05.20 14:29:19.973615 [ 1 ] {} <Information> Application: Loading metadata from /var/lib/clickhouse/
2019.05.20 14:29:19.981624 [ 1 ] {} <Debug> Application: Loaded metadata.
2019.05.20 14:29:19.981682 [ 1 ] {} <Information> BackgroundSchedulePool: Create BackgroundSchedulePool with 16 threads
2019.05.20 14:29:19.985095 [ 1 ] {} <Information> Application: Listening http://[::]:8123
2019.05.20 14:29:19.985906 [ 1 ] {} <Information> Application: Shutting down storages.
2019.05.20 14:29:19.986421 [ 1 ] {} <Trace> BackgroundSchedulePool: Waiting for threads to finish.
2019.05.20 14:29:19.986501 [ 1 ] {} <Debug> Application: Shutted down storages.
2019.05.20 14:29:19.987496 [ 1 ] {} <Debug> Application: Destroyed global context.
2019.05.20 14:29:19.990879 [ 1 ] {} <Error> Application: Net Exception: Address already in use: [::]:9000
2019.05.20 14:29:19.990916 [ 1 ] {} <Information> Application: shutting down
2019.05.20 14:29:19.990924 [ 1 ] {} <Debug> Application: Uninitializing subsystem: Logging Subsystem
2019.05.20 14:29:19.991035 [ 21 ] {} <Information> BaseDaemon: Stop SignalListener thread
2019.05.20 14:29:44.640941 [ 1 ] {} <Information> : Starting ClickHouse <IP_ADDRESS> with revision 54418
2019.05.20 14:29:44.645148 [ 1 ] {} <Information> Application: starting up
2019.05.20 14:29:44.647420 [ 1 ] {} <Debug> Application: rlimit on number of file descriptors is 500000
2019.05.20 14:29:44.647432 [ 1 ] {} <Debug> Application: Initializing DateLUT.
2019.05.20 14:29:44.647437 [ 1 ] {} <Trace> Application: Initialized DateLUT with time zone `Europe/Berlin'.
2019.05.20 14:29:44.648242 [ 1 ] {} <Debug> Application: Configuration parameter 'interserver_http_host' doesn't exist or exists and empty. Will use 'whale1' as replica host.
2019.05.20 14:29:44.650653 [ 1 ] {} <Debug> ConfigReloader: Loading config `/etc/clickhouse-server/users.xml'
2019.05.20 14:29:44.651339 [ 1 ] {} <Information> Application: Loading metadata from /var/lib/clickhouse/
2019.05.20 14:29:44.654354 [ 1 ] {} <Debug> Application: Loaded metadata.
2019.05.20 14:29:44.654375 [ 1 ] {} <Information> BackgroundSchedulePool: Create BackgroundSchedulePool with 16 threads
2019.05.20 14:29:44.655424 [ 1 ] {} <Information> Application: Listening http://[::1]:8123
2019.05.20 14:29:44.655524 [ 1 ] {} <Error> Application: Listen [::1]: 98: Net Exception: Address already in use: [::1]:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 14:29:44.655559 [ 1 ] {} <Information> Application: Listening http://<IP_ADDRESS>:8123
2019.05.20 14:29:44.655590 [ 1 ] {} <Error> Application: Listen [<IP_ADDRESS>]: 98: Net Exception: Address already in use: <IP_ADDRESS>:9000  If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host><IP_ADDRESS></listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
2019.05.20 14:29:44.655740 [ 1 ] {} <Information> Application: Available RAM: 62.70 GiB; physical cores: 4; logical cores: 8.
2019.05.20 14:29:44.655752 [ 1 ] {} <Information> Application: Ready for connections.
2019.05.20 14:29:46.662025 [ 21 ] {} <Debug> ConfigReloader: Loading config `/etc/clickhouse-server/config.xml'

Thank you in the advance

Please examine (or just attach) the contents of log files:

/var/log/clickhouse-server/clickhouse-server.err.log
/var/log/clickhouse-server/clickhouse-server.log

Okay, so I forgot to check the logs, sorry about that. There was an another app using the same port. It was about it.


Scrolls down only after 2 or 3 scroll steps

Hi,
I wonder why on my website it doesn't scroll down after the very first scroll step. On the demo page I get that behavior, on my website I don't. Can you check please? synergies.ch
All settings are default, I use sections.
Thanks a lot!

Try posting your issue on Stackoverflow, the community there may be able to help you.


New interface for MVDR beamforming

🚀 The feature
It would be very helpful to provide the following interface for the beamforming module (torchaudio.transforms.MVDR):
forward(specgram: torch.Tensor, psd_s: torch.Tensor, psd_n: torch.Tensor) → torch.Tensor

and maybe add some high-level glue functions that takes the masks as input, but has only a few lines of code.
Motivation, pitch
The current forward method of torchaudio.transforms.MVDR only accepts spectrogram and masks as input, and calculates the PSD matrices internally.
The current design is easy to use mainly for mask-based beamforming, but it may lose the flexibility for the users to:

use their own PSD estimates (e.g. mask-based PSDs, neural-network-based PSD estimates in ADL-MVDR and NICE-BEAM)
adjust PSD estimates with some additional regularization/stabilization techniques (e.g. PSD diagonal loading and PSD eigenvalue flooring)

Because in different setups, a different stabilization may be ideal or preferred. It would be better to allow the user to make the choice.

combine with conventional blind beamforming methods
etc.

Alternatives
No response
Additional context
No response

@mthrok What do you think? I feel like the current torchaudio.transforms.MVDR can be used as the high-level module, which calls another module with PSD as input arguments in the forward method.
Maybe we should rename the current MVDR module to a generalized MaskBasedBeamforming module which accepts any kind of beamforming method, similar to  DNN_Beamformer in ESPNet, but without trainable parameters. Then everytime we add a new beamforming module, we can add such support in the MaskBasedBeamforming.

@nateanl Can you make a diagram of changes you propose with call graph and signatures? (see the following for an inspiration)

Here is the diagram for changing the API of MVDR.

Move the get_mvdr_vector and apply_beamforming_vector to torchaudio.functional, and let the current MVDR module call the methods under torchaudio.functional. This aligns with ESPNet's function design.
Add a new module called MVDRBeamformer (for example). Use specgram, psd_s, psd_n, and ref_mic as the input arguments of forward method, as @popcornell mentioned the reference microphone might be dynamic (estimated via a neural network). This design aligns with Asteroid.
Add a warning in the current MVDR module notifying users to use MVDRBeamformer instead.

Here is the diagram for changing the API of MVDR.

[ ]  Move the get_mvdr_vector and apply_beamforming_vector to torchaudio.functional, and let the current MVDR module call the methods under torchaudio.functional. This aligns with ESPNet and pb_bss's function design.
[ ]  Add a new module called MVDRBeamformer (for example). Use specgram, psd_s, psd_n, and ref_mic as the input arguments of forward method, as @popcornell mentioned the reference microphone might be dynamic (estimated via a neural network). This design aligns with Asteroid.
[ ]  Add a warning in the current MVDR module notifying users to use MVDRBeamformer instead.

Sounds good.

What happens to PSD(specgram, mask) module?
I prefer using a prefix other than get_. say, for example compute_. Thoughts?

What happens to PSD(specgram, mask) module?

It will be outside of the new MVDR module. When users want to apply MVDR beamforming, they need to compute the psd matrices either by PSD module with the mask, or estimate them in other ways.
We can also add a function like compute_power_spectral_density_matrix under torchaudio.functional.

I prefer using a prefix other than get_. say, for example compute_. Thoughts?

Sounds good to me. Since there are three solutions to MVDR, we can make those methods names as:

compute_mvdr_vector_souden(psd_speech, psd_noise, ref_channel)
compute_mvdr_vector_rtf(psd_speech, psd_noise, ref_channel, solution="power")
compute_gev_vector(psd_speech, psd_noise, ref_channel)
apply_beamforming(bf_vector, specgram)

However, apply_beamforming may only apply to traditional beamforming methods. For the new proposed ones like multi-frame MVDR or WPD, we need to think of a new API. Any thoughts? @Emrys365 @popcornell @boeddeker

for multi-frame MWF as defined in https://arxiv.org/abs/1911.07953 I think there won't be a problem as basically the other frames are treated as other microphone channels.
I think it should be fine to have one function which can handle 90% of the use-cases out there. Might want to design it also to handle time-varying beamforming filters too. It should not be too hard.

I would say, try to keep it simple and "low level" (i.e. one equation, one function). With apply_beamforming you get, as popcornell said, most users and maybe there is no generalization. The WPD beamformer (probably also multi-frame MWF) can be formulated, such that apply_beamforming can be used (i.e. manipulate specgram and stack the history to the channel dimension). Since it is essentially just an einsum, it should be easy for a user to implement alternatives.
I have a question to the compute_mvdr_vector_rtf. From the name, I thought, it would take the RTF (relative transfer function) as input. I think that function combines two things, the calculation of the mvdr_vector and the calculation of the rtf.

We can split it into these functions:

compute_mvdr_vector_rtf(rtf, psd_noise, ref_channel)
compute_rtf_power(psd_speech, psd_noise, ref_channel)
compute_rtf_evd(psd_speech)

On the module-based design, for example, torchaudio.transforms.RTFMVDRBeamformer, shall we include the computation of rtf and mvdr vector together, or shall we also use rtf as the argument, same as compute_mvdr_vector_rtf?


fix: add newline so actions run

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


broadly investigate the NFT errors on ipv6

https://github.com/kubernetes-sigs/kpng/blob/master/hack/test_skip_list.sh#L138
Seems to highlight LOTS of NFT errors on ipv6...
Are they all related. ?

Run the test_e2e.sh script locally with nft backend and IPv6 set, use GINKGO_FOCUS with one the SKIPPED test for example
GIKGO_FOCUS="should work after the service has been recreated", and fill out the error on an issue or try to fix it directly.