AIX builds failing on ar commands

Thank you for reporting a broken build! Please fill in the following details:

Jenkins link to the failing log: For example, https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-hotspot/1002/consoleFull - started failing with bulid 1002 on the 28th September
Which platforms (OS+arch) are affected: AIX/ppc64
If you look at the historic logs, does the problem appear to be specific to one machine? No - happens on both
Link to any upstream project bug report (e.g. OpenJ9/JBS) n/a but it may be related to the addition of the static-libs target in https://github.com/adoptium/temurin-build/pull/2725 (FYI @jerboaa)

At @aixtools' suggestion I've set OBJECT_MODE=64 on the jenkins agent configuration for the two AIX build machines to see if that resolves the problem.

Posting the failure here for posterity:
20:25:53  	Use the -X option to specify the desired object mode.
20:25:53  ar: 0707-126 /home/jenkins/workspace/build-scripts/jobs/jdk11u/jdk11u-aix-ppc64-hotspot/workspace/build/src/build/aix-ppc64-normal-server-release/support/native/java.management/libmanagement/static/VMManagementImpl.o is not valid with the current object file mode.

If this keep failing, we can disable static-libs for AIX. It wouldn't be a supported OS for Graal VM/Mandrel builds anyway.

Seems to be working ok, but that's a fair point about the builds not being supported for that use case. For some reason after enabling it the builds have got very slow (2h15 vs 40 minutes), but unclear if that's just a one off.
I'm assuming the use of OBJECT_MODE=64 isn't causing any other side effects. If it turns out to be the correct solution (relative to disabling the static libs on AIX, or any other option we try) then we should put that into the aix.sh in this repository rather than in the jenkins agent configuration.

This issue appears to have been seen again on test-osuosl-aix72-ppc64-6. The Jenkins environment variables have been checked, and it seems OBJECT_MODE was never set for this machine (nor test-osuosl-aix72-ppc64-5).
The OBJECT_MODE variables have now been set on both of these machines, and I ask that the jenkins agent be reset at the earliest opportunity.
Also, this error is in the same job output: "1586-495 (U) SYSTEM LIMIT EXCEEDED: Too many processes are active."
So please also review the ulimits on these machines, as well as the mechanism for setting both ulimits and jenkins environment variables.


fix: expose return type of dialog ref

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[x] Other... Please describe: Fix for typing

What is the current behavior?

Issue Number: #86
What is the new behavior?
Does this PR introduce a breaking change?
[x] Yes
[ ] No

Typing changes might be incompatible resulting in failed builds, this change should not introduce any runtime changes.
Dialogs that do have a result type defined will now expose said type in the afterClosed$ observable, instead of an any Observable.
Other information
I did not observe any obvious place to add a test, there do not seem to be any typing-specific tests.

I don't know enough about this library to conclude what "all cases" is; the happy path works as expected;
If you do provide a result type to the DialogRef, it is properly exposed in afterClosed$.
There is however the breaking change that was described, which makes the current tests fail.
Error: projects/ngneat/dialog/src/lib/specs/dialog.spec.ts:157:28 - error TS2322: Type 'unknown' is not assignable to type 'boolean'.

157         next: (result) => (value = result),
                               ~~~~~
Error: projects/ngneat/dialog/src/lib/specs/dialog.spec.ts:171:30 - error TS2322: Type 'unknown' is not assignable to type 'boolean'.

171           next: (result) => (value = result),

Since, in both cases, value is of type boolean while result is of type unknown.
It seems like the Result type should be any except for cases where it is well defined as another type.
However, I have no clue on how to achieve this.
This MR fixes the happy path but not the edge cases.

I don't know enough about this library to conclude what "all cases" is; the happy path works as expected;
If you do provide a result type to the DialogRef, it is properly exposed in afterClosed$.
There is however the breaking change that was described, which makes the current tests fail.
Error: projects/ngneat/dialog/src/lib/specs/dialog.spec.ts:157:28 - error TS2322: Type 'unknown' is not assignable to type 'boolean'.

157         next: (result) => (value = result),
                               ~~~~~
Error: projects/ngneat/dialog/src/lib/specs/dialog.spec.ts:171:30 - error TS2322: Type 'unknown' is not assignable to type 'boolean'.

171           next: (result) => (value = result),

Since, in both cases, value is of type boolean while result is of type unknown.
It seems like the Result type should be any except for cases where it is well defined as another type.
However, I have no clue on how to achieve this.
This MR fixes the happy path but not the edge cases.

I'm using this and it works fine for me. The only issue is that the result can be undefined when closing via the default close button or backdrop, which doesn't get caught by typescript

This push was a simple rebase to get our downstream fixed for another branch, please disregard these changes.
I still want to take some time to fix this MR but that will be at a later time, thank you for you patience.

The last changes fix the previous issues with the test and remove the "breaking change".
This PR does not introduce any run-time changes.
I added some regression tests for the ExtractData and ExtractResult test helpers.

@milo526 the breaking change should be included in the commit

Breaking change footer is added to the commit.


Support STARTTLS

Originally reported 2016-10-04 by @arnaud-lb: https://github.com/reactphp/socket-client/issues/69

Any possibility this will ever be supported?

@ellisonpatterson Definitely on the roadmap and would love to see this feature! :+1:
That said, there are currently no immediate plans to build this from my end (no demand at the moment and more important outstanding issues currently), but we always welcome PRs! If you need this for a commercial project and you want to help sponsor this feature, feel free to reach out and I'm happy to take a look.

@clue @ellisonpatterson Spent the better part of this today looking into https://github.com/voryx/PgAsync/issues/38 and it looks like STARTTLS, or put better, the ability to enable TLS encryption on a connection at some point after the connection has been opened and used is required there as well. Had a look at #199 and it looks overly complex for what we need.
In short, we need the tls connection context and the ability to enable the TLS when both sides negotiate to be ready for it. Most of what is required for this is already in this package. I'll look into how this can be achieved without breaking out current API, if a break is required this could land in v3.


Set up extension to get @jupyterlab/csvviewer and @lumino/datagrid from forked verisons of Jupyterlab and Lumino

We would like to be able to modify some of the attributes in DSVModel class https://github.com/lmcnichols/jupyterlab/blob/master/packages/csvviewer/src/model.ts and the DataGrid class https://github.com/jupyterlab/lumino/blob/master/packages/datagrid/src/datagrid.ts. However, many of the attributes & methods we would like to change are set to private.
As a fix, we would like to have our extension depend on some node modules which come from Jupyterlab and Lumino forks on our local repository. In these forks, we would modify the source code so that the private attributes we need are set to protected.
We haven't figured out a way to set a dependency to a subdirectory of a git repository. This is a known issue (see https://github.com/yarnpkg/yarn/issues/4725 and https://github.com/npm/npm/issues/2974). Attempts to use existing tools (e.g. https://gitpkg.now.sh/) have failed, although we are still unclear on why they are failing.

Hey @lmcnichols!
Yeah this is a tricky problem. A couple of options on your end:

Publish your fork of the lumino CSV viewer as another package (rename it to some other package name) and import from there. This will let anyone who installs your package pull in the desired lumino fork.
Set the version of @lumino/datagrid to a file:// package pointing to your local edits. You don't have to change the name here, but it will only work locally for development, not for end user install.
Do a version of the above, but when building your extension pre-build it with webpack so that forked lumino source is essentially inlined into the build. Then you don't have to depend on any @lumino/datagrid extension.

I am happy to jump on a call with you, to talk about this more, if that would be helpful, feel free to reach out at<EMAIL_ADDRESS>to set up a time to chat.

As of right now, we have decided to publish our own npm package tde-csviewer to handle the necessary changes for our extension to work. These changes will soon be requested as a PR into JupyterLab core


Disable scrolling in webview

Hi,
it should be possible to pass as a prop the scrolling option for the iframe to disable scrolling. It may be look like:
<Webview src='http://url.com scrolling={false}>
And include in the iframe scrolling="no" if false is passed as the value of the scrolling prop.
Thank you in advance.

I'm sure the maintainer won't mind reviewing a PR ;). Luckily the change could be as trivial as #5 .
Regarding property name. How about calling it scrollEnabled to be inline with the React native component?

Here is the PR :slightly_smiling_face:  #9

Thanks @adrianicv! It's live in 0.2.2 :)


Update to cbor-java 0.9.1

There's no official Maven release for this version yet (https://repo.maven.apache.org/maven2/co/nstant/in/cbor/), so we'll need to wait on that first


Observer ward is free in shop, could mess up the inventory slots in later sections

Current behavior: Observer ward is free in shop.
Potential issue: Player could buy wards in Chapter 1 and mess up the inventory slots or goals in later sections.
Expected behavior: Make ward unpurchasable or not free.

Keep purchase blocked in order filter (think we already do that for part of the tutorial?).

Fixed in https://github.com/ModDota/dota-tutorial/pull/319


Using loadjs in a Vanilla project: require is not defined error

I'm running a Vanilla JS project without any builders or frameworks. I would like to make use of loadjs but I'm getting the error:

require is not defined

My code:
  <script<EMAIL_ADDRESS>  <script>const loadjs = require('loadjs');</script>

How to include loadjs in a Vanilla project?

Since you're using the standalone browser payload, the loadjs library is available via the loadjs global:
<script<EMAIL_ADDRESS><script>
  loadjs(["/path/to/foo.js", "/path/to/bar.js"], function() {
    /* foo.js and bar.js loaded */
  });
</script>

Hope that helps! I updated the README to make this clearer.

@amorey Thanks for the reply. It works. Close #104


allow users to configure session restore (system settings > startup and shutdown)

i'm tired of closing 20 apps everytime i start a kde session and i can't change it using plasma-manager. that's all

I will make it an option soon :)

Is there any way to configure this through the configFile option? I can't seem to find it in the output of rc2nix.

It's this ksmserverrc.General.loginMode; and the possible values are "restoreSavedSession", "emptySession", and null (where it just doesn't exist at all)

Sorry for the delay guys, I'm really busy these days, I will create a new module only for session in this weekend (maybe before) that will include this option.


replace node-sass with sass to support apple ARM64

I am using Apple M1 MacBook Pro with 16GB RAM.
When I tried to install dependencies of frontend environment by running yarn, the following error message was shown:

It seems that node-sass does not support ARM64 arch environment.
This issue can be solved by replacing node-sass package with sass, and everything works fine for me (at least I did not see any sass issues). Reference: https://github.com/sass/node-sass/issues/3033

私は日本語が未熟なので、先に英語で書きました。m(_ _)mｺﾞﾒﾝ
Apple M1 MacBook Pro 16GB RAMを使っています。
node-sass というパッケージがARM64のパソコンでコンパイルできないようです。
node-sass を sass で置き換えてから、無事にyarnでパッケージをインストールできました。

I'm not pretty sure that node-sass can be replaced with sass, but let me merge it for now. Thank you for your contribution!


Slight mistake in sample RandomRetryPolicy implementation

The sample code uses the expression _random.Next() * 10 to generate a random number between 0 and 10 but the range of integers is much larger.
Can you change this to _random.NextDouble() * 10?

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

ID: c9bc1072-be2c-94f6-49bf-daa9e97dff2d
Version Independent ID: 36052173-7061-6d01-8aed-915685cd7cf6
Content: ASP.NET Core SignalR .NET Client
Content Source: aspnetcore/signalr/dotnet-client.md
Product: aspnet-core
Technology: aspnetcore-signalr
GitHub Login: @bradygaster
Microsoft Alias: bradyg

Sure, PRs are welcome if you're interested in contributing.

@stanimirsellercloud  this is just a sample. Use whatever range you like.

@stanimirsellercloud this is just a sample. Use whatever range you like.

Rick, a lot of developers will follow the official SignalR + .NET client page which references the sample code (I did) -- the problem is that the code does not do what it is intended to.
I had to debug it before I realised it was wrong - it's not generating the range of seconds it's supposed to.

@stanimirsellercloud
Any chance you could PR this? At the top right of the article, select the Edit pen icon:

Select the pen icon again. Save.


[sqlpp11] update to 0.61

The sqlpp11 port has been updated to version 0.61.
The related [sqlpp11-connector-sqlite] and [sqlpp11-connector-mysql] auxiliary libraries have become part of version 0.61. They can be enabled using BUILD_<DBMS>_CONNECTOR=ON in the build. So their dependence on sqlpp11 has been explicitly changed to version 0.60, where they should be installed separately.
Only SQLite3 was added as a feature because only it was tested. It is assumed that other connectors will be added by whoever needs them.

Can someone help me with versioning? How does it work?
Connector ports cannot use version >= 0.61, and specifying >=0.60 is actually wrong, it should be <=0.60 but I cannot set such version as well as just version = 0.60.
How to force not use version 0.61?

I think you need to make a 0.61 version of the connector ports which will be empty but depend on sqlpp >= 0.61.
And you can add (obsolete) to the ports' description.

Now that the ports [sqlpp11-connector-sqlite] and [sqlpp11-connector-mysql] have become part of sqlpp11, we can directly set them to empty ports.

Now that the ports [sqlpp11-connector-sqlite] and [sqlpp11-connector-mysql] have become part of sqlpp11, we can directly set them to empty ports.

What does actually mean "empty port"? Should the portfile.cmake be empty?

What does actually mean "empty port"? Should the portfile.cmake be empty?

Almost. It needs:
set(VCPKG_POLICY_EMPTY_PACKAGE enabled)

Example: ports/proj4/portfile.cmake (The implementation is now in port proj.)

Thanks for the asnwer guys!
If I understand the questions correctly, find_package(sqlpp11 CONFIG REQUIRED) will add, for example, sqlpp3::sqlite3 and sqlpp3::mysql targets with all required headers and libs if sqlpp11 is built with connectors support.

Should the mysql connector also be controlled by a feature?

We should ensure that the original dependencies and features can be used normally

I can move changes from the mysql connector to the sqlpp11 port, but I'm not sure that I can test it.

Now I am confused. You originally wrote:

The related [sqlpp11-connector-sqlite] and [sqlpp11-connector-mysql] auxiliary libraries have become part of version 0.61.

I mean I can move build flags and dependencies from the mysql port to the sqlpp11 port as I did for the sqlite3 port, not code. Don't worry, all required code is already part of sqlpp11.
But I have not used mysql, don't know what it requires and which library(ies) should be link and so on, so I cannot guarantee that these changes will be good.

Hm, it would be good to have a test project which builds an executable, to avoid regression for these types of transitions.


Doubly linked list #182

Issue Number: #182
This is my implementation for the doubly linked list. It posses the ability to destroy the list as well as initialise it.
The main processes of insert and delete, as well as display, are present.

Yes, I have been assigned this pull request and I have updated the files respectively.
You can merge the files now.  #182  @avinash201199

@Mohamed-Ayaan358  write full name of the program .

Done

@Mohamed-Ayaan358  closing this pr because all the changes you have made was reflected on the pr which I have merged right now so make only obe pr at a time

So am i allowed to make another pull request or is that it ?


Can't update a product variant

Saving edits to an existing product variant or creating a new product variant with an existing product always results in an Error message ("Failed to update variant" or "Undefined")

on saving a variant in the admin app, medusa logs the error message " inventory_quantity must be a number conforming to the specified constraints"

a fix for this issue:
https://github.com/medusajs/admin/pull/237

Seems like I can only update custom variations if the inventory field is blank.  Get an error if it says 0.

Solved in #325


Integer value with float type decorator is a type mismatch

Repro is with Zed commit c927ae9.
I happened to be making ZSON literals as output from a crude tool to measure busy CPU % on Linux.
$ while true; do   echo "{ts: $(date -u +%FT%T.%NZ), cpu: $(top -b -n 1 | grep Cpu | awk '{ print 100 - $8 }')}" | tee -a cpu.zson;   sleep 1; done
{ts: 2023-05-24T17:54:17.099530853Z, cpu: 6.7}
{ts: 2023-05-24T17:54:18.274062846Z, cpu: 5}
{ts: 2023-05-24T17:54:19.449979136Z, cpu: 4.8}
{ts: 2023-05-24T17:54:20.635095707Z, cpu: 70.3}
{ts: 2023-05-24T17:54:21.856906380Z, cpu: 100}

This had the undesirable side effect of giving me two type definitions.
$ cat cpu.zson | zq -Z -i zson 'count() by typeof(this)' -
{
    typeof: <{
        ts: time,
        cpu: int64
    }>,
    count: 2 (uint64)
}
{
    typeof: <{
        ts: time,
        cpu: float64
    }>,
    count: 3 (uint64)
}

I thought a good way to address this would be to explicitly decorate all my values with (float64) so even the integers like 100 would land under the same type definition, but this currently results in an error.
$ echo '{ts:2023-05-24T17:54:21.85690638Z,cpu:100 (float64)}' | zq -Z -i zson -
stdio:stdin: type mismatch: "int64" cannot be used as "float64"

Verified in Zed commit 45f3a37.
Repeating the command above that previously failed, now we see the input numeric value 100 is accepted alongside the (float64) decorator, and when it's echoed back in the ZSON output the value is 100. to reflect its float nature.
$ zq -version
Version: v1.8.1-31-g45f3a378

$ echo '{ts:2023-05-24T17:54:21.85690638Z,cpu:100 (float64)}' | zq -Z -i zson -
{
    ts: 2023-05-24T17:54:21.85690638Z,
    cpu: 100.
}

Thanks @nwt!


how to use tree_templates? is there a more clear document?

I want to convert a grammar to another grammar, and I can't understand the example in the document(py3 to py2) beacaue I don't know about tree_templates, so how can I learn to use tree_templates?
Thank you!

try this https://lark-parser.readthedocs.io/en/latest/examples/advanced/py3to2.html


A test BaseBufferTest throws when calling compact() in the JVM.

This is a bug in the JDK. It was fixed in JDK 9. The following Java source file reproduces the bug on JDK 8 but not on 9, 10 nor 11 EA:
import java.nio.*;

public class Test {
    public static void main(String[] args) {
        ByteBuffer buf = ByteBuffer.allocate(65);
        buf.position(17);
        buf.limit(17 + 40);

        ByteBuffer slice = buf.slice();
        slice.order(ByteOrder.LITTLE_ENDIAN);

        IntBuffer view = slice.asIntBuffer();

        assert view.capacity() == 10; // 40 / 4
        assert view.position() == 0;
        assert view.limit() == 10;

        view.put(new int[] { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 });
        view.position(0);
        assert view.remaining() == 10;

        view.position(6);
        view.compact();

        assert view.position() == 4;
        assert view.limit() == 10;
        for (int i = 0; i < 4; i++)
          assert view.get(i) == i + 6;

        System.out.println("done");
    }
}

So our implementation is correct. We should at some point enable the test on the JVM is the version is >= 9.

Fixed in 07c2c6e07b391858c18cc782bebbc33b035a2f02


Add flutter_lints, dart fix, flutter format

Also convert a bunch of functions to StatelessWidgets to make screen re-paints more sane.
Checklist

[ ] ✅ My code follows the code style of this project.
[ ] 📝 My change requires a change to the documentation.
[ ] 🎀 I have updated the documentation accordingly.
[ ] 👀 I have read the CONTRIBUTING document.
[ ] ✨ I have added tests to cover my changes.
[ ] 🚩 All new and existing tests passed.
[ ] 🌟 ed the repo

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

Title goes here
Title goes here

Image goes here
Image goes here

Thanks for your contribution sir , but my project is not selected in advocu though 🥲

@all-contributors please add @domesticmouse  review , code


Allow overriding receiver to be &const Self for non-const C++ member functions

I don't see an existing issue for this so here we go...
I have run into an issue with the current treatment of C++ const member functions as being equivalent to Rust members accepting &self.

C++ defines a constant member as a function which does not modify the object.
Rust defines a &self receiving function as one which does not mutate the object but allows for internal mutability under verifiably safe conditions (Cell/Mutex/...)

My specific case is something akin to (forgive my rough example)
class Foo {
  Mutex mutex;
  int data;

public:
  Foo(): data(0) {}

  // this cannot be `const` because it modifies the obj
  void doThing() {
    auto lock = mutex.lock();
    data++;
  }
}

So in Rust a native implementation would look like
pub struct Foo {
  data: Mutex<i32>,
}

impl Foo {
  pub fn doThing(&self) {
    *self.data.lock() += 1
  }
}

But then using CXX we have a problem because we cannot define
#[cxx::bridge]
mod ffi {
  unsafe extern "C++" {
    type Foo;
    fn doThing(&self);
  }
}

without (in my case) getting the error

cannot convert from 'void (__cdecl Foo*)()' to 'void (__cdecl Foo*)() const'

Which means we now need to write it as a mut which means we have to have another mutex which is non-ideal for performance reasons and also makes things a lot less easy to use.
My proposal specifically is to make the following (or some variant thereof) valid
#[cxx::bridge]
mod ffi {
  unsafe extern "C++" {
    type Foo;
    fn doThing(self: &const Self); // <- developer is explicitly stating this is valid
  }
}

The closest C++ equivalent of the Rust implementation you wrote:
pub struct Foo {
    data: Mutex<i32>,
}

impl Foo {
    pub fn doThing(&self) {
        *self.data.lock() += 1
    }
}

is:
class Foo {
  mutable Mutex mutex;
  mutable int data;

public:
  Foo() : data(0) {}

  void doThing() const {
    std::lock_guard<std::mutex> guard(mutex);
    data++;
  }
};

which is perfectly fine to bind via cxx. That is the recommended implementation if this is first party code. The interpretation of const == threadsafe is common, well known, and is a design pattern in the C++ standard library.

As a Rust developer I see where you are coming from, and if it were my code to maintain, I would make the change. However, multiple C++ devs seem to disagree very strongly with your stance. While I am not going to post their arguments here because I do not think this is an appropriate place to argue about C++ best practices or ideology, please consider the following:
Even if modern C++ does define const as threadsafe, it seems it is not widely accepted or widely known especially for code which is not a public-facing interface. Further, we don't always have control over the code we need to interface with, and interfacing with C++ should not require changes to working C++ code.
For these reasons and because I wish to not irritate everyone with my Rust evangelism, I am still in favor of allowing the cxx crate to manually override the receiver to a &const Self since it means I can make the assertion in the foreign interface code (which is inherently unsafe) and take responsibility.
I will work on a PR for this.

Shrug -- I feel that this has been a consensus position for nearly 10 years at this point. Herb Sutter, Bjarne Stroustrup in The C++ Programming Language, Fourth Edition, and everybody else who typically gets involved in such things has advocated it. https://channel9.msdn.com/posts/C-and-Beyond-2012-Herb-Sutter-You-dont-know-blank-and-blank is a good explainer.

Remember, the fact that people expect this is not new. People have been expecting this for 25 years, and we've had to keep telling them "no it's really not that way, it's this embarrassing thing, sort of 'logically const' and I'll explain it to you over lunch one day", right? No more! Const means thread-safe.

We used to say "const means logically const". And that's kinda awkward, but you know we got over it and that's what we taught people. The new reality is const means thread-safe -- either bitwise const or internally synchronized.

We used to teach "mutable == not observably non-const", which is kinda awkward, but it's what we taught. Now it's much clearer. Mutable means thread-safe too. It means bitwise const or internally synchronized.

I'll go ahead and close the issue since I don't think I would want to take a PR for this. The cxx crate is fundamentally geared around "cooperative FFI", which is why it's okay for the readme to explain that handling any arbitrary signature (particularly a signature that is antagonistic to being bound from Rust) is not a goal.

Even though this has been closed, I wanted to follow up on this if anyone else stumbles into it and because I think we had a misunderstanding fundamentally and I at least think I see now.
My solution to this (without changing a bunch of C++ code that does not belong to me), was to create wrapper C++ code. My project now looks like:
src/
  lib.rs
  somemod.rs
  somemod.hpp
  somemod.cpp
  othermod.rs
  othermod.hpp
  othermod.cpp
  ...

Which I have found to be a somewhat clean way of also creating more support for things such as being able to return a rust vec from C++ or create a builder struct to handle some opaque types. It also means things like const and mutable can be added as needed without having to "clutter" (co-workers' word choice) an existing repo.
My fundamental misunderstanding was that cxx is trying to make these wrappers unneeded, and really what I should have seen is that it makes C wrappers unneeded. Writing a C++ wrapper is far more pleasant. (And if you are writing code from scratch in both langs you can probably avoid them altogether).
It is my belief that in the future cxx could get good enough to prevent needing any wrappers at all, but at least right now this wrapper approach seems optimal for at least my use case.


[release-1.22] bootstrap: interpolate HOST_IP like we do for native traces

This is an automated cherry-pick of #50895

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.22
4fc9d56a17817adb707df4db6564f747926b7b8b
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test integ-security-multicluster


Babel like traspiler to convert actual HTML or some of its simpler extension to Elm like HTML

Can we have a babel-like transpiler to convert actual HTML that the browser can render to the Elm HTML format?
After doing HTML for so many years, learning an all-new type of HTML can be cumbersome and can even raise the bars for beginners and even experienced devs into the em world. In such cases, a transpiler can be of good help.

You mean, like, https://mbylstra.github.io/html-to-elm/, the first Google result for "html to elm"? (I'm sure this can be turned into a command line tool, the processing logic should all be there in the source repository.)

Hey, @jvoigtlaender
Sorry for not looking harder. And yes this was the tool I was looking for.

No need to be sorry. And maybe close this issue here now? You could ask in the tool‘s repository itself whether a command line version is possible (if that’s more desirable than an online tool).


Camera far clipping not adjustable

Camera far clipping not adjustable when using appleseed as render engine.

#238


Create gather-chrome-based-browser-login-information.yml

Simple string-based rule to look for Chrome (and Chrome-based) browser login data being referenced.   I've included a stealer in https://github.com/mandiant/capa-testfiles/pull/135 that is referenced in this rule.
May help contribute to https://github.com/mandiant/capa-rules/issues/328.
I leaned on regex for case-insensitivity, if there are any performance concerns I'd be happy to use regular string operators.

thank you!


Store editor config in cookies

It'd be really useful to store config in cookies for consistency.

@selrond This seems like a duplicate of #26, maybe?

yep, sorry


[BUG] Image imports failing

@iwilltry42 I'm seeing this issue on ubuntu when upgrading from k3d 5.3.0 to 5.4.1.
I'm seeing output like:
INFO[0000] Importing image(s) into cluster '$CLUSTER_NAME'
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-$CLUSTER_NAME-tools'
INFO[0000] Saving 3 tarball(s) to shared image volume...
INFO[0000] Importing images into nodes...
INFO[0000] Importing images from tarball '/k3d/images/k3d-$CLUSTER_NAME-images-$IMAGE1.tar' into node 'k3d-$CLUSTER_NAME-server-0'...
INFO[0000] Importing images from tarball '/k3d/images/k3d-$CLUSTER_NAME-images-$IMAGE2.tar' into node 'k3d-$CLUSTER_NAME-server-0'...
INFO[0000] Importing images from tarball '/k3d/images/k3d-$CLUSTER_NAME-images-$IMAGE3.tar' into node 'k3d-$CLUSTER_NAME-server-0'...
ERRO[0001] failed to import images in node 'k3d-$CLUSTER_NAME-server-0': Exec process in node 'k3d-$CLUSTER_NAME-server-0' failed with exit code '1'
ERRO[0001] failed to import images in node 'k3d-$CLUSTER_NAME-server-0': Exec process in node 'k3d-$CLUSTER_NAME-server-0' failed with exit code '1'
ERRO[0001] failed to import images in node 'k3d-$CLUSTER_NAME-server-0': Exec process in node 'k3d-$CLUSTER_NAME-server-0' failed with exit code '1'
INFO[0001] Removing the tarball(s) from image volume...
INFO[0002] Removing k3d-tools node...
INFO[0003] Successfully imported image(s)
INFO[0003] Successfully imported 3 image(s) into 1 cluster(s)

One thing that jumps out: the code in importWithToolsNode() that logs these failures when copying images swallows errors without returning them to the caller: https://github.com/k3d-io/k3d/blob/852df7786ab5a98b9ecd95e1b215d593cf9201d8/pkg/client/tools.go#L125-L127 which allows the "successfully imported images" result to get printed.
Compare that to this other k3d code to import images into clusters (rather than nodes) which fails if any individual image fails to import: https://github.com/k3d-io/k3d/blob/7b1b416c2298f1aa30950eaae1d2847140ee285a/cmd/image/imageImport.go#L75-L86
Or even this code in the same importWithToolsNode() method that returns errors if any image fails to save: https://github.com/k3d-io/k3d/blob/852df7786ab5a98b9ecd95e1b215d593cf9201d8/pkg/client/tools.go#L114-L116
Should importWithToolsNode() return an error whenever any image installations encounter an error? That would at least mean that image installation errors are reported as overall install errors: that doesn't fix the install errors themselves, but it seems more appropriate than treating them as successes.
Originally posted by @CodingCanuck in https://github.com/k3d-io/k3d/issues/954#issuecomment-1103165790

Any update on this? we are building a tool based on k3d, we meet this problems too. And BTW, is there any way around to import image in arm64 ?

I have the same problem with a mac M1 pro, any updates ?

Not sure if related, but we sporadically get this in our Github actions workflows.
  k3d image import rancher/fleet:dev rancher/fleet-agent:dev
  shell: /usr/bin/bash -e {0}
  env:
    GOARCH: amd64
    CGO_ENABLED: 0
    SETUP_GO_VERSION: ^1.18
INFO[0000] Importing image(s) into cluster 'k3s-default'
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-k3s-default-tools'
INFO[0001] Saving 2 image(s) from runtime...
INFO[0001] Importing images into nodes...
INFO[0001] Importing images from tarball '/k3d/images/k3d-k3s-default-images-20220804121758.tar' into node 'k3d-k3s-default-server-0'...
INFO[0001] Importing images from tarball '/k3d/images/k3d-k3s-default-images-20220804121758.tar' into node 'k3d-k3s-default-agent-2'...
INFO[0001] Importing images from tarball '/k3d/images/k3d-k3s-default-images-20220804121758.tar' into node 'k3d-k3s-default-agent-1'...
INFO[0001] Importing images from tarball '/k3d/images/k3d-k3s-default-images-20220804121758.tar' into node 'k3d-k3s-default-agent-0'...
ERRO[0002] failed to import images in node 'k3d-k3s-default-agent-2': Exec process in node 'k3d-k3s-default-agent-2' failed with exit code '1'
ERRO[0002] failed to import images in node 'k3d-k3s-default-agent-1': Exec process in node 'k3d-k3s-default-agent-1' failed with exit code '1'
ERRO[0002] failed to import images in node 'k3d-k3s-default-server-0': Exec process in node 'k3d-k3s-default-server-0' failed with exit code '1'
ERRO[0003] failed to import images in node 'k3d-k3s-default-agent-0': Exec process in node 'k3d-k3s-default-agent-0' failed with exit code '1'
INFO[0003] Removing the tarball(s) from image volume...
INFO[0004] Removing k3d-tools node...
INFO[0005] Successfully imported image(s)
INFO[0005] Successfully imported 2 image(s) into 1 cluster(s)

I'd prefer a os.Exit in that case, but it doesn't happen too often.

I'm seeing this as well.
Failure, but success?
And then when I try to run the app, it sees the images is there, but then a kubelet error:
Error: failed to create containerd container: error unpacking image: failed to resolve rootfs: content digest sha256:XYZ: not found

The image does not have that sha in the registry. k3d must have changed it???

Same here, running on M1. Please consider improving UX by possibly returning error explicitly and stopping execution. Successful messages after failing conditions are misleading. Cheers!

It seems that the image gets imported, but with a different hash. So there may have been an initial error, but it seems to have imported something in the end. Perhaps there is a tiered set of instructions to load, and the top tier may have failed. But changing the hash of the image is not acceptable.
Sent from my iPhone

On Nov 24, 2022, at 10:04 AM, Jakub Jarosz @.***> wrote:

Same here, running on M1. Please consider improving UX by possibly returning error explicitly and stopping execution. Successful messages after failing conditions are misleading. Cheers!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

Still happening:
k3d version v5.4.7
k3s version v1.25.6-k3s1 (default)

What's strange too is that it happens when I pull the image from a cloud registry, not when I build the same image in local.


Bump to embassy-net-0.5 and reflect API changes

embassy-net 0.5 is out.
Since and it switched to core::net, it is easier to use it with other crates.

@oleid please also see https://github.com/sammhicks/picoserve/pull/53 and https://github.com/sammhicks/picoserve/pull/52 related to the same issue :)

Resolved by 00266199e6db138fe61e64034671458ab2f4135d


Notes : source data must be an array or slice, got map;

Cannot insert map[string]string in notes from razorpay go client. When I am hitting the api manually, it accepts notes as map[string]string type but in client it does not support that.
{
"amount": 1000,
"currency": "INR",
"receipt": "Receipt no. 1",
"notes": {
"notes_1": "123145125"
}
}
This request body is valid in create orders api.
But when I replicate in go client using this:
paramsMap := map[string]interface{}{
"amount":   checkout.Total.Amount(),
"currency": checkout.Total.Currency().Code,
"receipt":  "receipt_1",
"notes": map[string]string{"notes_1":"12234125"},
}
razorpayOrderMap, err := razorpayClient.Order.Create(paramsMap, nil)
It gives the following err :
Notes : source data must be an array or slice, got map

Hey @tiwariayush700
One way that works is you create a struct Notes
type Notes struct {
	ZipCode string `json:"zipCode"`
}

and when creating an order:
notes := Notes{ZipCode: order.User.ZipCode}
data := map[string]interface{}{
	"amount":   order.Amount,
	"currency": order.Currency,
	"receipt":  fmt.Sprintf("SY#%s#%d", order.User.ZipCode, order.Id),
	"notes":    notes,
}

I can vouch for this working.
Hope it helps.

@tiwariayush700 Sorry for the long delay. I haved checked the same api with yours params and i didnt get any error. Might it be fixed. Could you please let us know if you fixed the issue?


How can I use this bottom sheet as a component?

Can I do something like this?
// components/BottomSheet.js
import React from 'react'
import ReanimatedBottomSheet from 'reanimated-bottom-sheet'
import { useWindowDimensions, View } from 'react-native'

const BottomSheet = ({ children }) => {
  const dimensions = useWindowDimensions()

  return (
    <View>
      <ReanimatedBottomSheet
        snapPoints={[0, dimensions.height - 200]}
        renderContent={children}
        initialSnap={0}
      />
    </View>
  )
}

export default BottomSheet

// pages/home.js
import BottomSheet from '../../components/BottomSheet'
...
return (
    <BottomSheet>
     ...
    </BottomSheet>
)

No, because the renderChildren prop on ReanimatedBottomSheet expects a function which returns components. However, this would be easy to fix:
// components/BottomSheet.js
import React from 'react'
import ReanimatedBottomSheet from 'reanimated-bottom-sheet'
import { useWindowDimensions, View } from 'react-native'

const BottomSheet = ({ children }) => {
  const dimensions = useWindowDimensions()

  return (
    <View>
      <ReanimatedBottomSheet
        snapPoints={[0, dimensions.height - 200]}
        renderContent={() => children}
        initialSnap={0}
      />
    </View>
  )
}

export default BottomSheet

// pages/home.js
import BottomSheet from '../../components/BottomSheet'
...
return (
    <BottomSheet>
     ...
    </BottomSheet>
)

@SConaway I see, thanks for the update!
But going this way, how can I handle the show/close action of the bottomsheet? We have ref in all examples so I'm bit confused about how to work with that since I couldn't find a properly way to use it as a props.

Yeah, it takes a bit to get used to refs. basically, you would do something like this:
const bottomSheet = useRef(null);
// Then somewhere later, say in an onPress for a touchable
// bottomSheet.current.snapTo(0); // Snaps to the first snapPoint
// Or to close:
// bottomSheet.current.snapTo(2); // Snaps to the last snapPoint, i.e., closed
 return (
        <View styles={styles.container}>
            // ...
            <BottomSheet
                snapPoints={400, 200, 0]}
                initialSnap={1}
                renderContent={renderDetails}
                renderHeader={renderHeader}
                ref={bottomSheet}
            />
        </View>


IModel

It might be nice if the user was allowed to inherit their model from an IModel interface that looked something like this:
interface IModel
{
    int/Guid Id { get; set;}
}

This would allow the code not to have to use the Type.GetProperty() method and provide more IntelliSense.

As we're working with entities I would go with:
public interface IEntity { }

public interface IEntity<TId> : IEntity
{
    public TId Id { get; set; }
}

Also pretty sure you can derive your model from that interface and it should just work in it's current form.

Sure, that would be better.

Thinking this through...  if this interface was implemented by a class and a collection, how do you see this applying to the APIs?
This feels like it plays in the same space as the #4 Repository support.
Thoughts?

Yeah I would agree this kind of falls into repository pattern territory

Yeah, I think this is the same thing as Repository support. This (or repository support) would allow the client/user to get a compilation error if their Model does not contain an Id property rather than getting an exception thrown during Type.GetProperty().


pigpio will not run on a Pi 5

pigpio is hard-coded to not run on a Pi5.  See https://github.com/joan2937/pigpio/blob/c33738a320a3e28824af7807edafda440952c05d/pigpio.c#L7353-L7356
Do the maintainers plan to update pigpio to support the Pi5?  Will this repository entertain pull requests to port pigpio to the pi5?
If not, please update the README and/or archive this repository to let users know.

or archive this repository to let users know

... seems fairly rash given the installed base of a bazillion working devices vs the literal handful of pi5.

Do the maintainers plan to update pigpio to support the Pi5?

I have the aspiration to do so but my first quick read of the available docs suggest this will be a huge task, if not impossible without breaking compatibility.

Will this repository entertain pull requests to port pigpio to the pi~6~5?

Given the potentially monumental task, I think it would be wise to lean into the community for help.  At a minimum, we would want to retain architectural oversight of the project.

@guymcswain what would be so different between thos pi's 4 and 4 ? Isn't the pi meant to be backwards compatible?

@sworteu pi4 is supported.  You need to open a separate issue and give details around the failure.

Isn't the pi meant to be backwards compatible?

Yes but this meaning ends at the os level.  pigpio touches the metal.

i tried libgpiod and that seems to work..;)
https://kernel.googlesource.com/pub/scm/libs/libgpiod/libgpiod/+/v0.2.x/README.md
installed trough: sudo apt install gpiod
Note this is not pigpiod but gpiod.

Or more precisely, the code for the BCM2712.
https://github.com/joan2937/pigpio/blob/c33738a320a3e28824af7807edafda440952c05d/pigpio.c#L13791-L13830
I would create a PR, but I don't know what values to provide.  I suspect the BCM2711 values won't work, now that GPIO is handled by the RP1 southbridge?

pi5 is not supported by pigpio.  pi5 is built with a new chip architecture that is incompatible with previous iterations.

Some thoughts of a user:
Perhaps one could evaluate which features still work on the Pi5 and which do not, and then create a slimmed-down PiGpio version just for the Pi5, to which the (still) missing features are gradually added. This would destroy backwards compatibility, but it would allow users to use still working features (if available) right away and at the same time create a basis for the future.
Unfortunately, I do not have the expertise to support in the development. I am using PiGpio only, especially I2C and Wave Pulsing.

Although I recommend the use of libgpiod, for direct hardware access you may find the RP1 support in pinctrl (https://github.com/raspberrypi/utils) useful as a starting point.

... create a slimmed-down PiGpio version just for the Pi5, to which the (still) missing features are gradually added.

I would generally agree with this strategy, however, there are features/capabilities of pigpio that distinguish it from all other gpio libraries:  the DMA read engine for sampling gpio and the DMA write engine for pwm, servo and custom waveforms.  I have not taken the time to look into it yet but I'm hoping there exists compatible interfaces on Pi5 such as the VPU mailbox registers allowing the DMA peripheral to be memory mapped.  If a more kernel friendly approach is available, that should be explored as well.

I have just experienced this problem too

gpioHardwareRevision: unknown rev code (d04170)

so  I am currently snookered

Is there a beer/coffee fund to which one could contribute to support RPi5 development? Appreciate it's a monumental task, but this is an excellent library and it would be a shame to see the ecosystem of RPi GPIO libraries grow ever larger!

Between this repo https://github.com/G33KatWork/RP1-Reverse-Engineering and the pinctrl source, it shouldn't be too hard to implement basic GPIO features... on the other hand, re-implementing servo control etc can become a little harder...

IS rpi-lgpio a near drop in replacement for basic functionality?
Can we do this?
sudo apt remove python3-rpi.gpio
pip3 install --break-system-packages rpi-lgpio

Is there a beer/coffee fund to which one could contribute to support RPi5 development? Appreciate it's a monumental task, but this is an excellent library and it would be a shame to see the ecosystem of RPi GPIO libraries grow ever larger!

Beer and coffee are not the problem.  I'd do it for free if the Raspberry Pi Foundation would publish APIs to access the internal peripherals - like DMA in particular - and memory mapping IO.  All of this was done using a mailbox interface to the VC processor in generations 1-4.  That's all changed in gen 5.  Thus, a new standard (architecture).

Unfortunately, I don't have any working relationship or contacts within the foundation.  The author of this library, @joan2937, perhaps does.

It's not the Foundation - it's the engineering company Raspberry Pi Ltd. that you would need to talk to, but...
I don't know which API you are referring to. Most of pigpio does direct accesses to the hardware from userspace. The datasheet for RP1 (responsible for the user-facing GPIOs on Pi 5) is available, as is the source code for pinctrl - the replacement for raspi-gpio that also does direct hardware accesses.
I don't think you should ping Joan - if they wanted to be involved with Pi 5 they would have by now.

Thanks Phil, the problem is not the gpio control but all of the DMA control that is at the core of pigpio.  All that was done through facilities known as mailbox registers via the video core processor.  All is that is gone with pi5.
It will be a huge lift to rewrite the core part of this library and a non starter if there is no assurance that it changes again in the future.
People smarter than me wrote this code.  I’d be happy to take a look if someone could point me to documentation that allows the same functionality on the pi5.

With Pi 5 the role of the firmware has reduced. Apart from some basic power and clocks management, its job is basically to load the kernel and get out of the way. Having said that, I think it's only the memory allocation that is performed by the firmware - there is no "DMA this data to here" API. Since RP1 has access to all of system RAM there is no need for a special allocator.
AFAIK we aren't permitted to publish the documentation for the Synopsys DMA controller, but the Linux driver is available as executable documentation: https://github.com/raspberrypi/linux/blob/rpi-6.1.y/drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c

@pelwell I think the DMA feature that is being referred to here is the clever usage of it to achieve hardware timed PWM.  See https://stackoverflow.com/a/53033272/539972
PIO is supposed to come to the Pi5, right?  If so, I think that would make pigpio less relevant for the Pi5, or at least provide a way to implement the features that pigpio currently provides for the Pi4 and earlier.

在 py 中使用gpiod
apt update && apt upgrade && pip install gpiod && apt install libgpiod-dev


Provide support for using Prometheus scaler with Azure Monitor managed service for Prometheus (preview)

Proposal
Provide support for using Prometheus scaler with Azure Monitor managed service for Prometheus (preview) which relies on Azure AD authentication.
Use-Case
Customers using Azure Monitor managed service for Prometheus (preview) can scale their applications based on existing metrics.
Is this a feature you are interested in implementing yourself?
No
Anything else?
This requires the addition of Azure AD authentication, I'll dig in to the requirements for this.

Thankyou @tomkerkhove for opening this issue. I am starting to look into this support and would need some time to go through the details and come up with a plan. Will share the proppsal/idea for further discussion/brainstorming once I am there!

Great, thank you @raggupta-ms!

I spent some time on KEDA code and this is what I am thinking:

Add support for Azure Workload Identity in the first iteration i.e. hoping to get released in March's release.
Add support for Azure AD App Auth iteratively after the first version is hipped.
Do not add support for Azure Pod Identity Auth since Pod Identity is deprecated in lieu of Workload identity. See these links for reference: https://learn.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity and https://github.com/Azure/aad-pod-identity#-announcement
For the implementation of workload identity support:
-- Use/enhance existing Azure workload identity code to get the token in required format (https://github.com/kedacore/keda/blob/main/pkg/scalers/azure/azure_aad_workload_identity.go)
-- Add a new http round tripper for Azure auth that will utilize the code in above mentioned file azure_aad_workload_identity.go.
-- Use this new Azure round tripper in existing Prometheus scaler i.e. if the auth in scaler config is set to azure workload identity (https://github.com/kedacore/keda/blob/22a5111a7997c7fceb6c4839e8ae74a299c5a131/pkg/scalers/scaler.go#L95), use this azure round tripper instead of the one used currently in code (https://github.com/kedacore/keda/blob/main/pkg/scalers/prometheus_scaler.go#L94).
-- Might need to change some code here and there such as auth config parsing in Prometheus scaler etc.
-- Overall, doesn't seem to be a lot of changes.

@tomkerkhove, please share your comments on the above thought. Also, please add/tag other folks who can help reviewing.

Add support for Azure Workload Identity in the first iteration i.e. hoping to get released in March's release.
Add support for Azure AD App Auth iteratively after the first version is shipped.

This is OK for me, if we agree on it with other maintainers then we should track a new issue for it.

Do not add support for Azure Pod Identity Auth since Pod Identity is deprecated in lieu of Workload identity. See these links for reference: learn.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity and Azure/aad-pod-identity#-announcement

I am on the fence on this one since we do support it for other Azure scalers and implementation should be minimal. Pod Identity is deprecated, but not archived yet so I'm leaning toward adding it. @JorTurFer @zroubalik?

As a sample of ScaledObject and TriggerAuthtication, it will be very similar to how it looks today for Prometheus scaler and a sample is:

Correct, this should work as an end outcome.

KEDA will need label/annotation which is pre-existing to enable azure workload identity for any azure scaler, as described here: keda.sh/docs/2.9/authentication-providers/azure-ad-workload-identity

This is already a pre-requisite so a non-action for you.

For the implementation of workload identity support:
-- Use/enhance existing Azure workload identity code to get the token in required format (main/pkg/scalers/azure/azure_aad_workload_identity.go)
-- Add a new http round tripper for Azure auth that will utilize the code in above mentioned file azure_aad_workload_identity.go.
-- The round tripper will ensure to inject the workload identity token in authorization header.
-- Use this new Azure round tripper in existing Prometheus scaler i.e. if the auth in scaler config is set to azure workload identity (https://github.com/kedacore/keda/blob/22a5111a7997c7fceb6c4839e8ae74a299c5a131/pkg/scalers/scaler.go#L95
), use this azure round tripper instead of the one used currently in code (main/pkg/scalers/prometheus_scaler.go#L94).
-- Might need to change some code here and there such as auth config parsing in Prometheus scaler etc.

@JorTurFer @zroubalik can you validate this, Sounds legit to me though.

-- Overall, doesn't seem to be a lot of changes.

I agree, changes should be easy.

Add support for Azure Workload Identity in the first iteration i.e. hoping to get released in March's release.
Add support for Azure AD App Auth iteratively after the first version is shipped.

This is OK for me, if we agree on it with other maintainers then we should track a new issue for it.

I have no idea about what is Azure AD App auth, but it looks good to me

I am on the fence on this one since we do support it for other Azure scalers and implementation should be minimal. Pod Identity is deprecated, but not archived yet so I'm leaning toward adding it. @JorTurFer @zroubalik?

Agree with @tomkerkhove , if AAD-Pod-Identity is still alive (its EOL is December if I'm not wrong), we should support both. The best part is that we already have the code to get the token (like for AAD-WI), so the extra required code should be low
About the implementation, sound good in my mind, but I need to see the code to have a real opinion about it. From my side, you can go ahead.
Remember that e2e test is required as part of the feature. You will need to do another PR to the testing infra repository, adding the needed terraform to deploy the managed prometheus and performing the role assignment required to grant permissions to the e2e managed identity

Thankyou @tomkerkhove and @JorTurFer for reviweing. I didn't have strong opinion on not adding support for Pod Identity. Since you feel it should be there (I also agree somewhat that it is going to stick in for probably around an year more), I will add that as well.
Will proceed to make code changes at my end. Noted the testing part, I may have more questions, especially around testing when I reach there. Thanks for the support!

@tomkerkhove @JorTurFer I am facing an issue while trying to setup my VSCode for debugging and could use your help, in case you know.
I am following the steps listed here: https://github.com/kedacore/keda/blob/main/BUILD.md#operator but when I launch VS Code, I get following error:
{"level":"error","ts":"2023-02-12T00:28:16-08:00","logger":"setup","msg":"problem running manager","error":"open /certs/ca.crt: no such file or directory","stacktrace":"main.main\n\t/home/raggupta/code/keda/cmd/operator/main.go:284\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}
Looks like the operator is trying to get hold of ca and tls certs. Is this expected when debugging locally? Is there a way to disable tls on local setup? I am using minikube cluster. I could find some annotation related to tls cert in keda-metrics-apiserver yaml file and removed all of it, annotated with --kubelet-insecure-tls and --kubelet-preferred-address-types="InternalIP", but very likely I am looking at wrong place since I want to debug operator but these config is for api server.
I tried to supply a ca.crt at the mentioned location but then it asked for tls.crt etc. and I could not resolve that completely - am no expert on tls and certs :(
Any idea what I might be doing wrong or to get it working? Note that when I deploy by scaling keda operator to 0 and then make deploy, it works fine - I don't see any cert issues in logs and keda containers are up and running fine. Just that VS Code launch isn't working.

Oh! Sorry, this has been my fault :(
I'll update the docs asap, in the meantime, you can get the certificates that the operator has created in the cluster (it's a secret in KEDA namespace, you will find them together inside the secret) and create the files in that folder

Hi @raggupta-ms ,
I have just opened a PR with the information you need. It sin't merged yet, but you can check the process directly there.
Thanks for notifying the documentation gap :)

@JorTurFer thankyou for the instructions. It did the resolve the issue :)

no worries, it was missing due to my fault xD

created a PR: https://github.com/kedacore/keda/pull/4256
@tomkerkhove @JorTurFer Please take a look.

Docs and feature are in, we are good to go!

Thank you @raggupta-ms !


Implement discussion section

Create a section where users can view and participate in discussions related to resources. Display threaded comments, allow users to post comments, reply to comments, and upvote/downvote comments.

I would like to work on this issue.

I would like to work on this issue.

Assigned!


⚠ ClamAV has degraded performance

In 56d8fba, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 71 ms

Resolved: ClamAV performance has improved in d44d103.


CSV not a supported file format

$ inventree-part-import parts.csv
reading parts.csv ...
error: .csv is not a supported file format

Hows the csv formatted? Can you share it?

Seems like tablib doesn't handle single column files. Added some code to handle this case manually now, should be fixed!


'Cannot read property 'type' of undefined '-error, when DOM element is not on the page.

To validate if the form data is correct, I send the data via AJAX to a Web API. When the entered data is invalid, a list of error results are send back to the client.
I'm using the jQuery Validation Plugin 'showError' method to map the error results to the right DOM elements.
Some times the Web API can send back more error results then there are DOM elements on the page, in this case the 'showErrors' method will throw an error ('Cannot read property 'type' of undefined').
It would be nice if the 'showErrors' method would just skip the element/error mapping if it cannot a find the DOM element on the page.
Is this by design or a bug? Will this be fixed or is there a workaround? Or am I doing something wrong and is there another way to achieve the same thing.
http://jsfiddle.net/uX9JJ/1

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


Add image for Bitcoind 0.15

We should create an image for Bitcoind 0.15.

Added support in https://github.com/ruimarinho/docker-bitcoin-core/commit/a620648dbabca9596133c3cfcd81d74f2038ed85.


Razor Views Fail To Compile because DependencyContext does not load deps.json dependencies

Since I upgraded to 1.0.0-rc2-16551 my project fails to compile razor views at runtime.
The errors I get are that the System namespace and other namespaces can not be resolved.
I debugged the issue into asp.net code and found that the problem is in DefaultRoslynCompilationService.cs which is supposed to compile the code using assemblies references taken from the current running assembly, however the list of referenced assemblies is empty in:
https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc.Razor/Internal/DefaultRoslynCompilationService.cs#L110
I found that the referenced assemblies are attempted to be found using DependencyContext class in Microsoft.Extensions.DependencyModel namespace.
The DependencyContext  class attempts to get the references from {project_name}.deps.json file which does not exist: https://github.com/dotnet/cli/blob/acd581c376c622743480176f75d7aed3088d5462/src/Microsoft.Extensions.DependencyModel/DependencyContext.cs#L52
This is an urgent bug which prevents me from continuing development. Please deal with this soon.
More information:
I am running asp.net mvc with target framework dnx451.
I tried to both compile the project with "preserveCompilationContext": true and without and it did not help. This flag is supposed to create the .deps.json resource according to: https://github.com/aspnet/Announcements/issues/149 but it does not create it.

This is an urjent bug which prevents me from continuing development. Please deal with this soon.

If it's urgent why don't you downgrade to what used to work? It's Saturday and you can't expect this to be fixed until Monday at the very least.

Unfotunately my project.json files had rc2-* in all the dependencies (changed it now to concrete versions) and I have many projects in my solution so I don't know which version worked, and in addition I have upgraded all my code with the new changes (like the change in the HttpOkResult and HttpBadRequest, etc) so to revert all changes will hurt.
I do not expect this to be fixed soon if its really a bug in your code, however I would like to know if its really a bug in your code or is it a bug in my code.

I do not expect this to be fixed soon if its really a bug in your code, however I would like to know if its really a bug in your code or is it a bug in my code.

Expecting any sort of investigation on the weekend is too much. Unless you already figured it out I wouldn't expect anything that will unblock you immediately.

@guylando the compilation errors you're seeing are probably caused by this (deliberate) change: https://github.com/aspnet/Mvc/pull/4139.
Luckily, https://github.com/aspnet/Mvc/pull/4171 will bring a new MVC/DNX compatibility package fixing these errors.

@PinpointTownes Thanks for your answer, you are probably right. Followup questions:
1)Do you know in which version of the packages did #4319 occure? (i am new to github, is there a way to see such information?)
2)Do you know when #4171 will be available on aspnetcidev feed?
Thanks!

@guylando, the package should be on the feed now.

That fixed my bug. Thanks!
Will never use wildcard * in my project.json again.


fluxv2-notification schema issue

Describe the bug a clear and concise description of what the bug is.
We are using fluxv2-notification chart version 1.10.0 and creating secret and provider and alert configurations through terraform.
we are sending below values.yaml to the chart.
chart input:
secretlist:

name: slack-token
value:
data:
address: "${slack-url}"
providerlist:
name: slack
spec:
type: slack
channel: general
secretRef:
name: slack-token
alertlist:
name: webapp
spec:
providerRef:
name: slack
eventSeverity: info
eventSources:
- kind: GitRepository
name: flux-system
- kind: Kustomization
name: '*'

error description:
template: flux2-notification/templates/provider.yaml:33:18: executing "flux2-notification/templates/provider.yaml" at <$provider.spec.certSecretRef.name>: nil pointer evaluating interface {}.name
as per the schema   "certSecretRef"  is optional.
What's your helm version?
v3.4.1
What's your kubectl version?
v1.24.0
What's the chart version?
1.10.0
What happened?
No response
What you expected to happen?
secretlist:

name: slack-token
value:
data:
address: "${slack-url}"
providerlist:
name: slack
spec:
type: slack
channel: general
secretRef:
name: slack-token
alertlist:
name: webapp
spec:
providerRef:
name: slack
eventSeverity: info
eventSources:
- kind: GitRepository
name: flux-system
- kind: Kustomization
name: '*'

error:  template: flux2-notification/templates/provider.yaml:33:18: executing "flux2-notification/templates/provider.yaml" at <$provider.spec.certSecretRef.name>: nil pointer evaluating interface {}.name
How to reproduce it?
run fluxv2- notification chart using below values.yaml input
Enter the changed values of values.yaml?
secretlist:

name: slack-token
value:
data:
address: "${slack-url}"
providerlist:
name: slack
spec:
type: slack
channel: general
secretRef:
name: slack-token
alertlist:
name: webapp
spec:
providerRef:
name: slack
eventSeverity: info
eventSources:
- kind: GitRepository
name: flux-system
- kind: Kustomization
name: '*'

Enter the command that you execute and failing/misfunctioning.
terraform apply with fluxv2-notification chart version 1.10.0
Anything else we need to know?
No response

faced the same issue, chart version 1.11
workaround:
          certSecretRef:
            name: false


Checking "Automatically add brackets to functions" has no effect.

Describe the bug

Steps to Reproduce

Check  "Automatically add brackets for functions" (Tools/Options/Text Editor/Python/Advanced)
Add "import os" to python file.
Write "os.getc", you'll see autocomplete for os.getcwd, selecting it, ensure:
a. Auto-complete adds os.getcwd() to the source code.

Additional context and screenshots
Only os.getcwd is added to the file.

#7827 , #7830 , #7831 , #7832 repro with pylance version >= 2023.12.103, which indicates the bugs might be caused by one of the pyrx commits from 1/4/2024 - 1/10/2024.

The commit that caused all these regressions has been narrowed down to https://github.com/microsoft/pyrx/commit/bad397c6c7a04e40ec917e3da412cd7b04e74f2d

Update: this bug is probably not caused by any changes in pylance, it also repros with pylance 12.1. Seems like something broken in the upstream.

Verified this has been fixed in Microsoft Visual Studio Enterprise 2022 (64-bit) - Int Preview Version 17.10.0 Preview 2.0 [34701.24.main]


"AxiosError" - "Request failed with status code 429"

When I'm trying bulk search, I'm getting error shown below. However, a single number search works perfectly fine.

Similar to #6
Please read this Limitations


Fix kubectl version not using YAML & JSON printers

Expected Behavior

kubectl version → VersionPrinter
kubectl version -o json → JsonPrinter
kubectl version -o yaml → YamlPrinter

Current Behavior

kubectl version → VersionPrinter
kubectl version --client=true → VersionClientPrinter

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

Operating System: linux
kubectl version: v1.29.2
kubecolor version: v0.2.2

The kubectl version output was changed. Before it used a Go struct output format and had a --short flag. Nowadays the default format is the --short format, and the --short flag was removed. In addition we now have -o json and -o yaml.

It is using the correct printers. Don't know when this was fixed, but now it works :)


Registration view seems to not work

I have configured all the flags in the app most of the functionalities are working fine but the registration view is not working.

@alihaidermalik what issue are you exactly facing?

@alihaidermalik what issue are you exactly facing?

When I click on register button in the app it gets hang and after some second gets crash.

Can you share logs?

Can you share logs?

@alihaidermalik pease join OpenEdX slack channel and post your question over there, with proper formatted text log.
joing uisng:
https://open.edx.org/blog/open-edx-slack

I have resolved this issue by commenting out this code
// [weakSelf populateDefaultFormFields];
from OEXRegistrationViewController.m file


Change where pids and log files are kept

I'd like to put them in a hidden dot folder (./.procodile/pids/ and ./.procodile/procodile.log so it doesn't pollute the project root with these files.

You can configure this in the Procfile.options config file by setting the pid_root and log_path.
https://github.com/adamcooke/procodile/wiki/Configuration

So it does. Missed that in the docs. Thank you :-)
Regards
Kieran Pilkington
http://twitter.com/k776 - http://k776.tumblr.com
On 31 October 2016 at 16:26, Adam Cooke<EMAIL_ADDRESS>wrote:

You can configure this in the Procfile.options config file by setting the
pid_root and log_path.
https://github.com/adamcooke/procodile/wiki/Configuration
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adamcooke/procodile/issues/6#issuecomment-257237618,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABA7NcPJuW8hjHy08WV-sHMxH2c9mUZks5q5aZJgaJpZM4Kktug
.


Gitmanager refactor

This does two things to help improve Smokey's Git workflow:

Adds a pre-commit hook that checks to see if we're on deploy, and refuse to commit if so. This is to prevent people from accidentally committing to deploy and creating nasty local changes.
Simplify the blacklisting process and avoid checking out or modifying the local master branch (in case it's not up to date or has local changes):

Fetch origin/master from Github
Check it out into a detached HEAD
Make blacklist commit
If the user has code privileges, push directly to master from detached HEAD
Else, checkout a new temporary branch and make a PR.

Note that at no point do we commit directly to the local master or even check it out. This also eliminates any merging, which would run into issues if the changes couldn't be fast-forwarded.

This also eliminates the notorious "HEAD isn't at the tip of origin's master branch" error.

I'm here but I'm waiting for the revamp which avoids detached head for privileged users.
https://chat.stackexchange.com/transcript/message/41039077#41039077

Pulling this out of an embedded comment, discussion about this in CHQ: https://chat.stackexchange.com/rooms/11540/conversation/pr-1216

As we're currently discussing in chat, I think there might be a bit of a misunderstanding here. Nothing about this will clobber remote commits -- the only window of opportunity for a remote commit to cause a conflict is between the fetch as the push which is a few seconds at max, and if it did occur the push would simply fail (Git never tres to fast forward commits when pushing.)
As for local commits, they're all still there -- they just won't be pushed with the blacklist (by design). Presumably they were created by a human, so a human should resolve and push them.

I should add that the finally clause makes it so that it always switches back to deploy and deletes any temporary branch ade no natter what, if say the push did fail. I should probbly add in a stash just in case deploy has uncommitted changes.

I've set up another repository with a clean Git tree with my modifications, and confirmed that blacklisting (at least calling gitmanager.GitManager.add_to_blacklist directly) works. Feel free to experiment.

Pull requests also work, and no local deploy or master changes were harmed: https://github.com/quartata/smokey-git-test/pull/1

Coverage remained the same at 65.087% when pulling e973b7acde73559ca4026f126b07c23575e88970 on quartata:gitmanager into 836dd08b21075f547b3e1cfdab9d5c2d3e00a69e on Charcoal-SE:master.


Add support for http basic auth

@guyanbiao
Can you add a test case to spec/ethereum/http_client_spec.rb?

@guyanbiao
Thanks for the issue. Please migrate as we will maintain the eth.rb library here. ;)


⚠ Bofrost.be has degraded performance

In 65997a7, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2102 ms

Resolved: Bofrost.be performance has improved in 8e5eaa1 after 26 minutes.


Data channel improvements.

Implemented low buffer amount callback
Fixed onopen() not being called when a new data channel is added if peer connection was already connected.

RFC portion related to low buffer amount.

A could of nits, but the changes look good! @ibc is on vacation, so it will take him a bit to review, FYI.

Fixed

Hey Jose, sorry for the delay! Landed in 10515a4, thanks!


Create harun.toml

Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

Hi
The email part was invalid but has now been corrected. Could you check again? Thank you

Gönderen: Bengt Lofgren @.>
Gönderildi: 14 Aralık 2023 Perşembe 14:41
Kime: anoma/namada-testnets @.>
Bilgi: harunbrgn @.>; Author @.>
Konu: Re: [anoma/namada-testnets] Create harun.toml (PR #2786)
The transactions.toml file for 0a4316ehttps://github.com/anoma/namada-testnets/pull/2786/commits/0a4316e6d05869d844246eec230b3ff5afa7e30c was deemed invalid with error Invalid email<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHubhttps://github.com/anoma/namada-testnets/pull/2786#issuecomment-1855692746, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZEGA6NZD6X5FAUTEQGEXBLYJLQWRAVCNFSM6AAAAABANZLEI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVGY4TENZUGY.
You are receiving this because you authored the thread.Message ID: @.***>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

Hi
Can you please check now, I fixed the error. and I entered the information correctly.

Gönderen: Bengt Lofgren @.>
Gönderildi: 14 Aralık 2023 Perşembe 14:59
Kime: anoma/namada-testnets @.>
Bilgi: harunbrgn @.>; Author @.>
Konu: Re: [anoma/namada-testnets] Create harun.toml (PR #2786)
The transactions.toml file for 0a4316ehttps://github.com/anoma/namada-testnets/pull/2786/commits/0a4316e6d05869d844246eec230b3ff5afa7e30c was deemed invalid with error Invalid email<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHubhttps://github.com/anoma/namada-testnets/pull/2786#issuecomment-1855718582, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZEGA6NVDCU75WZOFZNQUVTYJLS3XAVCNFSM6AAAAABANZLEI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVG4YTQNJYGI.
You are receiving this because you authored the thread.Message ID: @.***>

I removed the @ sign and edited it, but why am I still getting the error?

Gönderen: Bengt Lofgren @.>
Gönderildi: 14 Aralık 2023 Perşembe 15:12
Kime: anoma/namada-testnets @.>
Bilgi: harunbrgn @.>; Author @.>
Konu: Re: [anoma/namada-testnets] Create harun.toml (PR #2786)
The transactions.toml file for 0a4316ehttps://github.com/anoma/namada-testnets/pull/2786/commits/0a4316e6d05869d844246eec230b3ff5afa7e30c was deemed invalid with error Invalid email<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHubhttps://github.com/anoma/namada-testnets/pull/2786#issuecomment-1855737681, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZEGA6IG7HHMGU267BTNBRTYJLUKXAVCNFSM6AAAAABANZLEI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVG4ZTONRYGE.
You are receiving this because you authored the thread.Message ID: @.***>

The transactions.toml file for 0a4316e was deemed invalid with error Invalid email<EMAIL_ADDRESS>

The transactions.toml file for a797d75 was deemed invalid with error Invalid signatures: Signatures could not be verified

I really don't understand why I wasn't chosen.

Gönderen: Bengt Lofgren @.>
Gönderildi: 14 Aralık 2023 Perşembe 15:32
Kime: anoma/namada-testnets @.>
Bilgi: harunbrgn @.>; Author @.>
Konu: Re: [anoma/namada-testnets] Create harun.toml (PR #2786)
Closed #2786https://github.com/anoma/namada-testnets/pull/2786.
—
Reply to this email directly, view it on GitHubhttps://github.com/anoma/namada-testnets/pull/2786#event-11247543220, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZEGA6LZ2USCLRZ4HVNKCR3YJLWWZAVCNFSM6AAAAABANZLEI2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGI2DONJUGMZDEMA.
You are receiving this because you authored the thread.Message ID: @.***>


Update rxjava version

Fixes #2248.  Passed unit tests and acceptance tests.

LGTM

Codecov Report

Merging #2256 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2256      +/-   ##
==========================================
+ Coverage   68.03%   68.05%   +0.02%
==========================================
  Files         230      230
  Lines        8118     8118
  Branches     1013     1013
==========================================
+ Hits         5523     5525       +2
+ Misses       2210     2208       -2
  Partials      385      385

Impacted Files
Coverage Δ

...a/server/EurekaServerInitializerConfiguration.java
79.31% <0%> (+6.89%)
:arrow_up:

Continue to review full report at Codecov.

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


[Draft] Models Repository Refactor

Refactor with respect to track 2.

@digimaun

Local IT with different (clean) environments:
python 3.6:

python 3.7

python 3.8

python 3.9


Issue with updating state_dict

I cloned  from scratch and am encountering this error:
Traceback (most recent call last):

  File "multivers/predict.py", line 109, in <module>

    main()

  File "multivers/predict.py", line 101, in main

    predictions = get_predictions(args)

  File "multivers/predict.py", line 36, in get_predictions

    model = MultiVerSModel.load_from_checkpoint(checkpoint_path=args.checkpoint_path)

  File "/opt/miniconda3/lib/python3.8/site-packages/pytorch_lightning/core/saving.py", line 156, in load_from_checkpoint

    model = cls._load_model_state(checkpoint, strict=strict, **kwargs)

  File "/opt/miniconda3/lib/python3.8/site-packages/pytorch_lightning/core/saving.py", line 198, in _load_model_state

    model = cls(**_cls_kwargs)

  File "/Users/anna/Desktop/mv/multivers/multivers/model.py", line 86, in __init__

    self.encoder = self._get_encoder(hparams)

  File "/Users/anna/Desktop/mv/multivers/multivers/model.py", line 170, in _get_encoder

    new_state_dict[name] = orig_state_dict[name]

KeyError: 'embeddings.position_ids'

This is from line 168 in model.py:  ADD_TO_CHECKPOINT = ["embeddings.position_ids"]
So I tried changing this to: ADD_TO_CHECKPOINT = ["embeddings.position_embeddings.weight"]
as this seemed to be the missing item from the Huggingface state_dict.
However I then encountered this error:
Traceback (most recent call last):

  File "multivers/predict.py", line 109, in <module>

    main()

  File "multivers/predict.py", line 101, in main

    predictions = get_predictions(args)

  File "multivers/predict.py", line 36, in get_predictions

    model = MultiVerSModel.load_from_checkpoint(checkpoint_path=args.checkpoint_path)

  File "/opt/miniconda3/lib/python3.8/site-packages/pytorch_lightning/core/saving.py", line 156, in load_from_checkpoint

    model = cls._load_model_state(checkpoint, strict=strict, **kwargs)

  File "/opt/miniconda3/lib/python3.8/site-packages/pytorch_lightning/core/saving.py", line 204, in _load_model_state

    model.load_state_dict(checkpoint['state_dict'], strict=strict)

  File "/opt/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1051, in load_state_dict

    raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(

RuntimeError: Error(s) in loading state_dict for MultiVerSModel:

Unexpected key(s) in state_dict: "encoder.embeddings.position_ids"

Which I've been unable to resolve so far. This is the same for all checkpoints (e.g. scifact, healthvers). Thanks!

Can you provide me with the command you're running to get this error so I can reproduce?

python multivers/predict.py
model is scifact.ckpt, but same result when using healthvers

Got it - it may be just an issue of calling the wrong script. Can you follow the instructions in the inference section of the README and let me know what this does? In particular, try calling bash script/predict.sh scifact rather than running the Python script.

My bad Dave, had I installed sentence-transformers, which isn't compatible with transfromers 4.2.2. Uninstalled and is working now - thanks for the help and sorry for taking up your time!

No problem, I'm glad it worked!


Fix mistake in policy

what
Fix mistake in policy
why
The policy is created simply by ARN without the ":" construct, which is necessary to create the correct policy for the role.
Without this ":" construct, the policy is created, but it does not work correctly.
This error was discovered when I tried to create a cloudwatch group in the cloudtrail module.
I got the response "Error: Error updating CloudTrail: InvalidCloudWatchLogsLogGroupArnException: Access denied. Verify in IAM that the role has adequate permissions."
After studying the code, I realized that I need to add the construction ":*" in a couple of lines.
My solution looks like this, I need to replace the lines in file :
This line:
join("", aws_cloudwatch_log_group.default..arn),
replaced by
"${join("", aws_cloudwatch_log_group.default..arn)}:*"
You need to do this in both identical lines.
Perhaps you can suggest a better solution, I'm new to terraforming.
references
https://github.com/cloudposse/terraform-aws-cloudwatch-logs/issues/37
https://github.com/cloudposse/terraform-aws-cloudwatch-logs/blob/master/iam.tf#L55

/test all

@nitrocode
Hello, "All checks have passed"

@nitrocode I've been using this fix in a production environment for a couple of months now. It is correct.

@nitrocode I've been using this fix in a production environment for a couple of months now. It is correct.


Implement IHostedService instead of IStartable

Description
Removing the synchronous IStartable interface. In its place, we implement the built-in IHostedService, which is asynchronous and is invoked by the Host after the DI container has been built.
Testing
I've implemented the changes on the fhir server and have tests passing.

This PR is pretty scary for me. IStartable has a guarantee that it will happen after the construction of the IoC container, but before app initialization is complete. This PR changes that behavior to async background tasks that complete at unknown intervals


[internal] Generate API diff report

In preparation for a migration guide from 0.10.x to 1.0, we need to create an API diff report.
There exist a tool japicmp which uses javassist under the hood. It will not cover all of our use cases, e.g. when methods are renamed.

Hi dear @danieldietrich
I try to understand the generated report by japicmp (And it was a little bit hard at first impression).  then I tried to use it programmatically and the power has unleashed!
Solution 1
My solution is to use an annotation on every method (and also classes) that has been renamed, I mean use the annotation as a flag to find which methods are only renamed.
Here is a sample project to manipulate the report by annotation (please also check out the report.md).
Here is the vavr's side sample.
By the annotation, we could assign some metadata to the method (like the old name) if needed.

Add a little bit of complexity and code to the VAVR project
More flexibility

Solution 2
We could also declare a list of method names in the sample and use the list for generating API diffs.

Less flexibility


Solution of task - Group people by city

Added solution to group people by city.
Added solution to group people by gender.
Added generic function "groupBy" to group by any property .
Added test case for  group people by city
Added test case for  group people by gender.

Also please link the original issue for this pull request in the Linked Issues section.


add example screenshot

There are many complaints on Hacker News about the lack of example screenshots.
The screenshot was taken of the ROM running in the Ares emulator.

This is off topic while I review, but could you link the Hacker News thread? I was wondering why I have so many stars lately.

I was wondering why so many people were starting my incomplete project!


fsevents install script failing

Hi, I am trying to get F8 app to build for Windows Phone. When running npm install, I get the following error:

After I ran it as administrator, it managed to create npm-debug.log (attached)
npm-debug.zip
Any idea what the problem could be?
N.B: I am running that on a Windows 10 machine and I have node 6.2.1 and npm 3.9.3 (as shown in the attached screenshot).
Any help would be appreciated,
Hisham

Same thing here :

node: v6.2.1
npm : v3.9.6
<EMAIL_ADDRESS>

fsevents is an OS X-only module.  I don't know what F8 is but it sounds like it needs to add fsevents to its optionalDependencies rather than its normal dependencies.  Hope that helps.

Hi,
F8 is a facebook app that is now available for Windows. I'm following instructions on:
https://github.com/ReactWindows/f8app/tree/ReactWindows/windows
If fsevents is an OS X-only module then I think I should get in touch with ReactWindows/f8app guys then.
Thanks!

The problem is actually that they've included a npm-shrinkwrap.json file in the repo that was generated on a Mac. Shrinkwrap files don't play well with optional dependencies (see https://github.com/npm/npm/issues/2679).
If you delete the shrinkwrap or remove the fsevents entry from it and npm install you should be fine. Alternately, the f8 maintainers should take care to ensure fsevents is not included in the shrinkwrap file they distribute.


Segmentation Fault with Dill pickling library

Description
Lightgbm fails to serialize with a segmentation fault 11 after recent version upgrades after training on a subset of data, but not when trained on more data.
Reproducible example
from lightgbm import LGBMClassifier
clf = LGBMClassifier()
clf.fit(my_dataset)

import dill
with open("output.pkl", 'wb+") as out:
    dill.dump(clf)

Unfortunately, I can't share my data, as it belongs to my employer.
Environment info
LightGBM version or commit hash:
3.2.1
Command(s) you used to install LightGBM
python3 -m pip install lightgbm

Additional Comments
It used to only happen on MacOSX. Now it happens on both Mac and Linux. It is important that LGBM supports pickle, as I will have to drop the library otherwise.
I am searching for the version of lightgbm which works.

Thanks for taking the time to come back and explain why you closed this, @chrisdonlan !


Add Japanese translations for delay node enhancements

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
I added Japanese translations for the pull request #2949.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 67.532% when pulling baed43efaa82a64babc2cca85bb03ca3824b0060 on kazuhitoyokoi:delay-node-enhance-addjpn into 93971537b4009e8da2f47d5c1ef2ace328c03e09 on node-red:delay-node-enhance.


Does It Work With Core 2.0?

I got this error today after upgrading to core 2.0

I have just looked into this.
These seems to be problem with packages versions.
Cause of the problem is method context.Database.ExecuteSqlCommand(... (from Relational package).
What is even more strange is that the exception is thrown form a line where another method is being called just because that method contains call to this ExecuteSqlCommand_.
So it was quite hard to find the bug.
Now this library uses Microsoft.EntityFrameworkCore.Relational 1.1.2 and it seems that is not compatible with 2.0
But if I switch 2.0 then older versions will not work.
One solution would be to have 2 nuggets but I would first like to check is both could be supported from single library.

Single library can Not support both versions.
[https://github.com/aspnet/EntityFrameworkCore/issues/9653(https://github.com/aspnet/EntityFrameworkCore/issues/9653)
But I don't want to have 2 repos and 2 nugget either.
So I plan to make a switch to 2.0 soon and publish it as pre-release for some period so it can be used with 2.0 version.
And once I make a release anyone needing older versions will be able to install older nugget versions before this switch was made, but in the long run everybody should switch their projects to 2.0+

Any Time Frame for the change?

Next week.

Oh good good, wish we can take you on our development team. our developer rushes always to the newest technology and it creates headaches, what is the benefit of jumping on the wagon at the earliest time

:)
I have just released v1.0.8 where support for explicit transaction is added, which enables multiple bulk operations in single transaction.
README is updated with example of it.

Prerelease 2.0.0-rc published.

Good, Big Thanks
----- Original Message -----
From: Boris Djurdjevic
To: borisdj/EFCore.BulkExtensions
Cc: nafberger ; Author
Sent: Monday, September 04, 2017 6:45 AM
Subject: Re: [borisdj/EFCore.BulkExtensions] Does It Work With Core 2.0? (#20)
Prerelease 2.0.0-rc published.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Add struct for workflow_job event

This is a new (as of now undocumented) event that has been darkshipped by GitHub.
It provides three actions: queued, started and completed, reusing the existing WorkflowJob struct.
Official documentation is supposedly soon to follow, but advance submission of this PR has been approved by GitHub staff.
You can hold up this PR until it drops. I will update it accordingly.

@googlebot I signed it!

Thank you, @Parker77 !
Merging.


Adds tag support to construction

Closes #3318
I'll document all this in the critically-acclaimed, best-seller "Construction" hackMD document.

cum


atom-typescript specific settings shouldn't be in tsconfig.json

It's really untidy to have atom-typescript specific settings mixed in with normal TS settings. It's not clear that they relate to atom-typescript to anyone unfamiliar with atom-typescript. It confused me when I started using atom-typescript, since I'm also new to TS. The norm is for tools to create their own config files, like tsd does with tsd.json, or wallaby does with wallaby.json, etc. This makes it easy to manage the settings and prevents confusion.

This makes it easy to manage the settings and prevents confusion

Agreed. However I'd rather it be under a key like atom-typescript. But I'm not looking forward to making that breaking change anytime soon.

Doesn't seem right to just close valid and unresolved issues…

Doesn't seem right to just close valid and unresolved issues.

Sure. It's open and up for grabs.
Implementor's guide

Move all the atom-typescript specific stuff under atom key in tsconfig.json.
Update https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md
Code needs to go here : https://github.com/TypeStrong/atom-typescript/blob/master/lib/main/tsconfig/tsconfig.ts
Republish as a major version and document the breaking change : https://github.com/TypeStrong/atom-typescript/blob/master/docs/CHANGELOG.md
Also update the FAQ https://github.com/TypeStrong/atom-typescript/blob/master/docs/faq.md

:rose:

You shouldn't put non-TS settings in the TS config file. It's invalid according to its schema, and coupling the TS and atom-ts settings makes them both more difficult to manage, because you need to edit JSON in cases where you would otherwise be able to just work with files. Every other tool uses their own config files too. It should just be atomts.json or something for this tool as well. It should also be fixed sooner than later because it's needed and putting off breaking changes makes implementing them harder.

Thank you for your feedback.

Agreed. If I can get some time in the near future, I'll take a stab at this.

Early on, the TypeScript team said they were OK with third-party extensions to the tsconfig.json file as long as they didn't conflict with first-party functionality.
The extensions used by atom-typescript (and now grunt-ts as of v5 beta) have been around for a long time and do not conflict with present or anticipated first-party functionality to my knowledge (if I am wrong here, please let me know).  They are also quite useful to thousands of developers in their present state.  Therefore, this seems like needless work for the person writing the change, the TypeStrong team, and our end users.
I don't see the value in taking a breaking change for this.  I appreciate your comments @slikts and @nickroberts, but I think your time might be much better spent on either improving atom-typescript's documentation for this issue (to lessen any confusion), to advocate for an official mechanism for third party extensions for tsconfig.json with the TypeScript team (in which case it would be worth taking a breaking change), or on our many other issues.
In particular, we could really use a globbing library that supports exclusions.

Agreed. If I can get some time in the near future, I'll take a stab at this.

@nickroberts don't. Based on @nycdotnet's comments I've re-evaluated the stance and decided that the options we have make a lot of sense for the community (and its not just my opinion).
All the options we have are documented here : https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md#options
I'll be (and have been in the past) very careful adding further extensions. We will no longer think of moving / or removing any of the options we have right now without very strong justification.


Validation of pydantic models in query params

If a pydantic model is supplied as params and auto cast via fastapi.Depends() the models config is ignored:
Take a look at this example:
app = FastAPI()

class NoExtraFields(BaseModel):
    model_config = ConfigDict(extra="forbid")
    a: int
    b: int

@app.get("/")
def foo(foo: NoExtraFields = Depends()):
    return foo

client = TestClient(app)

response = client.get("/", params={"a": 1, "b": 2, "c": 3})
assert response.status_code == 200, response.text

This assert will pass, since the config is ignored. This is a result of all the params field getting validated separately in solve_dependencies instead of together as is done with body_params.
While there are workarounds as discussed here, this is not a satisfactory state considering the otherwise great compatibility with pydantic.
This PR addresses this by doing a validation for the model as a whole for query params as well.

Thanks @mylius!
Using Depends() with Pydantic models was never officially supported, it was a hack that happened to work, discovered by chance by someone. 😅
But now there's official support for Pydantic models with Query, Cookie, Header (https://github.com/fastapi/fastapi/pull/12199), so that should cover this use case.
Given that, I'll pass on this one, but thanks for the effort! ☕🍰


Feature Suggestion: Have the ability to give a name to connections

Instead of just showing server names in the left panel; when creating a new connection give the ability to give a name to the connection that would then be used in that list (same as registered servers in SSMS)

Refer to https://github.com/Microsoft/sqlopsstudio/issues/240 for design suggestions

IMO it's crucial feature that should be there from the beginning. I have like 5 connections only and yet I have problems with knowing which one's which as they are all on the internal VPN network and only difference is one digit in the IP address (username is same on each of them).


Starting to add more (con)text

@andrewkbradshaw this is my start at adding more text to the moments notebook. There are still several places that need help from you. Most importantly, adding some more description of your non-adaptive, Gaussian-weighted moments (both the motivation and implementation), would be very useful for users.
This can be merged, but would probably benefit from some more iteration.

@andrewkbradshaw pinging on this. Think we can get it finished today?