gradients using loss=F.make_loss(myloss) are not same as gradients not using loss=F.make_loss(myloss) in Hybrid programming

This operator accepts a customized loss function symbol as a terminal loss and the symbol should be an operator with no backward dependency. The output of this function is the gradient of loss with respect to the input data.

The description of ndarray.make_loss is same as the description of symbol.make_loss. And it only explains symbol, not ndarray.
I want to know what F.make_ loss() will do when I use net.hybridize() and loss.backward().
https://mxnet.apache.org/versions/1.7.0/api/python/docs/api/ndarray/ndarray.html?highlight=make_loss#mxnet.ndarray.make_loss
https://mxnet.apache.org/versions/1.7.0/api/python/docs/api/symbol/symbol.html#mxnet.symbol.make_loss
class Myloss(mx.gluon.nn.HybridBlock):
    def __init__(self):
        super(Myloss, self).__init__()
    def hybrid_forward(self, F, pred, gt):
        loss_l2 = F.sum(F.square(pred - gt), axis=1) / 2
        return F.make_loss(loss_l2)
net=resnet()
net.hybridize()
x = net(input)
myloss = Myloss()
loss = myloss(x, y)
loss.backward()

@Sundrops there's no need to use make_loss in Gluon as all values can be used as head gradients now.


How to install Berkeley DB

Please could you explain how to install Berkeley DB? Is an Oracle account needed?
I am on Linux Mageia.
Viele Grüße.
Roland

Hi Roland,
while I can‘t help you with that specific Linux version, you should be able to download and compile BerkeleyDB directly from source without an Oracle account. Here is a step-by-step guide I found: https://noknow.info/it/os/install_oracle_berkeley_db_from_source
Hope that helps!
Best,
-Thorsten

Hi Roland,
while I can‘t help you with that specific Linux version, you should be able to download and compile BerkeleyDB directly from source without an Oracle account. Here is a step-by-step guide I found: https://noknow.info/it/os/install_oracle_berkeley_db_from_source
Hope that helps!
Best,
-Thorsten


Drop IE 9/10 support

There are about three months left until IE 10 end-of-life and I think their usages have dropped to reasonable rate. We've released v0.11.1 last month, but maybe we can release another version, if necessary. (Related: #1919, #1409)

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2136   +/-   ##
=======================================
  Coverage   94.81%   94.81%
=======================================
  Files          81       81
  Lines        5281     5281
  Branches      926      926
=======================================
  Hits         5007     5007
  Misses        250      250
  Partials       24       24

Flag
Coverage Δ

#screenshotter
89.69% <ø> (ø)
:arrow_up:

#test
88.54% <ø> (ø)
: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 d10f375...2eba8b1. Read the comment docs.

@ylemkimon I realize that line of code has a comment stating that it is there only to resolve an IE problem. But I think the comment is wrong. The screenshots clearly show a problem if the line of code is removed.
I think we should keep the line of code and remove the comment that only IE made it necessary.


Remove schemas from meshery/meshery.

Notes for Reviewers
This PR fixes #9857
Signed commits

[ ] Yes, I signed my commits.

The schemas in meshery/schemas are up to date.

Thank you. Please confirm when duplication has been eliminated in Meshery, in Cloud, MeshKit, and the folders cleaned up in Schemas.


Regression: serializing vector<> of objects

Hello,
I've found that the behavior of the following code snipped is different for different boost versions.
Version of Boost

1.75.0:

[[42],[42],[42],[42]]

1.79.0, 1.81.0, 1.83.0:

[42]

I believe that 1.75.0 behavior should be correct here.
Steps necessary to reproduce the problem
#include <iostream>
#include <vector>

#include <boost/json.hpp>

class any_result {
public:
	inline any_result() {}
	template<class T> any_result(const T&) {}
	template<class T> any_result(T&&) {}

	void value_from(boost::json::value& jv) const;
};

void any_result::value_from(boost::json::value& jv) const {
	jv = { 42 };
}

inline void tag_invoke(boost::json::value_from_tag, boost::json::value& jv, const any_result& r) {
	r.value_from(jv);
}

template<class T>
auto save(T&& t) {
	return boost::json::value_from(std::forward<T>(t));
}

template<class T>
auto save_json(T&& t) {
	return boost::json::serialize(save(std::forward<T>(t)));
}

int main(int argc, char** argv) {
	std::vector<any_result> r;

	r.reserve(4);
	for (std::size_t i = 0; i < r.capacity(); ++i) {
		r.emplace_back();
	}

	std::cout << save_json(r) << std::endl;

	return 0;
}

All relevant compiler information
gcc 9--13 have been tested on Wandbox.

There are multiple things going on here. First of all, your any_result has an overly tolerant constructor. As a result, any_result x = std::vector<any_result>(); compiles. In addition, C++ considers the namespace of any_result to be associated for std::vector<any_result>. Together, these two things lead to
vector<any_result> v;
boost::json::value jv;
tag_invoke(boost::json::value_from_tag(), jv, v);

choosing your tag_invoke overload. Now, in older versions of Boost.JSON a library-provided implementation was always used for containers, but that lead to a problem where a user provides a more specific implementation, but the library disregards it. So, now we are ranking user-provided overloads higher and always prefer them over generic implementation.
The second thing is that jv = { x }; was considered on some compilers called value(std::initializer_list<value_ref>) constructor, and on others value(T) constructor. This called incosistency between compilers, which we removed by special treatment of initializer_lists of size 1. Now they are equivalent to value(x).
If you want the previous behaviour

Make any_result constructors explicit.
use jv = {{ 42 }}; or jv.emplace_array().emplace(42);

Corerction: the "second thing" is only applicable to version 1.84.0, in which your test would produce 42 and not [42].

If making any_result's constructor explicit is undesirable you can instead do this:
struct any_result_arg
{
    any_result const& r;

    any_result_arg(any_result const& r) : r(r) {}
};

void
tag_invoke(boost::json::value_from_tag, boost::json::value& jv, any_result_arg const& arg)
{
    arg.r.value_from(jv);
}

any_result_arg has a more restrictive constructor which solves issue number 1.

Yet another version:

template< class T >
typename std::enable_if< std::is_same<T, any_result>::value >::type
tag_invoke(
    boost::json::value_from_tag, boost::json::value& jv, const T& r)
{
    r.value_from(jv);
}

Since there were no complaints for any of my suggestions, I consider this solved.


Play integration

[ ] Don't try to run freestyle-play tests with Scala 2.12

This is an initial approach to #111
It allows you to use a FreeS program that returns an HTTP result as an action. It can handle both programs that depend on the request or not, so we should be able to use this in Scala Exercises.

Codecov Report

Merging #125 into master will decrease coverage by 0.37%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master     #125      +/-   ##
==========================================
- Coverage   75.83%   75.45%   -0.38%
==========================================
  Files          30       30
  Lines         269      273       +4
  Branches        2        2
==========================================
+ Hits          204      206       +2
- Misses         65       67       +2

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 f5c6d57...b8ba966. Read the comment docs.

I haven't had success trying to exclude the freestylePlay sbt project from running with Scala 2.12. I've tried this plugin and fiddling with sbt settings but I finally settled for changing the Travis configuration to run the full suite for 2.11, and only the tests integration project under 2.12.

@juanpedromoreno can you check the new Travis configuration and if it works merge this? Thanks!

@dialelo @raulraja The last commit should work (https://github.com/47deg/freestyle/pull/125/commits/46bb539a8c85ae9730255664d38c3b6b73423511), since it's going to run all the tests except the play integration tests when running on scala 2.12.

💚 thanks @juanpedromoreno


retire nodisplay store configuration

and avoid default connection initialization for these stores

and lucky for us, the code that was inserting undefineds in connections, is the deleted code...
i didn't immediately figure that:
candidates[store].map(this.formatConnection);

will be calling formatConnection with no this, and this.delimiter will be undefined... it was a wrong connection anyway!


Re-generate spec.rs tests

It looks like spec.rs was modified by hand in
505b0a5510ad238c525c14c8af7280f60791d27d and possibly elsewhere.
Rerunning the build with gen-tests results in these changes to
spec.rs.
Making this change causes fewer tests to pass, but all the changes to
the tests appear to be correct -- they match the CommonMark spec
document now.
I will go through the CLA process if you approve this change.

Yes, it's clearly wrong when the auto-gen stuff diverges from the input. One thing I think would help here is a strongly worded warning at the top of the auto-gen output not to edit it.
Thanks!

Okay, I submitted the CLA form.
The top two lines of the spec.rs file do warn not to edit it, not sure what else can be done there.

Right, I agree. I should have caught them being edited in the first PR :)


Update runit to 3.0.0+ to unblock the build

Using the runit 3.0 cookbook gets around the dep solving bug that is causing our build failure.  We're continuing to work on tracking down the bug and opening an issue for it, but I wanted to run this through CI to get things unblocked - and because we're quite out of date for this cookbook anyway...

http://wilson.ci.chef.co/job/opscode-push-jobs-server-trigger-ad_hoc/26/downstreambuildview/

Weird...  why not :)


Fix the Chinese Document of Java index.md

Remove some words "的" which would make the description be more fluent.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@jack870131 Congratulations on your first merged pull request to freeCodeCamp repository! Thanks for removing those unnecessary and funny "的"!


Feature request: Allow automatic clear of output window before running task

VSCode Version: Code 1.8.1 (ee428b0eead68bf0fb99ab5fdc4439be227b6281, 2016-12-19T14:49:23.350Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author
Version

read-only-indicator
alefragnani
0.6.0

alignment
annsk
0.3.0

Doxygen
bbenoist
1.0.0

vscode-astyle
chiehyu
0.4.0

python
donjayamanne
0.5.6

EditorConfig
EditorConfig
0.3.4

copy-relative-path
enochc
0.1.1

matlab
Gimly81
0.4.0

status-bar-tasks
GuardRex
0.1.2

vscode-dimmer
hoovercj
2.1.0

docthis
joelday
0.3.10

cpptools
ms-vscode
0.10.0

copy-file-name
nemesv
1.0.0

vscode-clearcase
OpenNingia
1.4.2

vscode-icons
robertohuertasm
7.1.2

theme-cyanicpastels
SamuelLampa
0.0.9

indenticator
SirTori
0.2.1

vscode-hexdump
slevesque
1.1.4

code-spell-checker
streetsidesoftware
0.14.8

comment-snippets
Tobiah
0.2.0

dark-plus-material
vangware
0.1.4

change-case
wmaurer
1.0.0

highlight-trailing-white-spaces
ybaumes
0.0.2

Steps to Reproduce:

Run a task.
Output is appended to output window.
Expected behaviour: Output window is cleared before starting the task so it easier to see the results of the current task. This should be a configurable option. Probably a global one plus a per task one.

@dbaeumer Any update on this?

This got partly addressed with the new terminal runner which support a presentation property that lets you control the panel usages. For example
			"presentation": {
				"panel": "new"
			},

which creates a new panel for every run (but it doesn't automatically clear /close and old one).
The story forward is to use the terminal runner not the old output runner. If you think there is something missing for you please open a new issue. I will close this one since no work is planned to support new features in the output runner.

How do we use the "terminal runner" and get the output cleared at the start of running a task?

June release notes or https://code.visualstudio.com/docs/editor/tasks#_convert-from-010-to-200

I have already converted to "version": "2.0.0", but had not added "runner": "terminal". After adding this my existing tasks (or at least one of them) seem to be working
  "version": "2.0.0",
  "type": "shell",
  "presentation": {
    "echo": true,
    "reveal": "always",
    "focus": false,
    "panel": "dedicated"
  },
  "runner": "terminal",
  "tasks": [
    {

What new can I now do?
I've just tried adding add "cls" to the start of my tasks, but it didn't work:
"args": [
        "cls &&",
        "my_build_program options"
]

BTW: I'm using an external batch file to beep at the end of the build, so I don't have to watch the long builds:
(my_build_prog || beepbeepbeep.bat)
&&
beep.bat

I get three beeps if it fails and one if it succeeds.

The cls trick doesn't work. You get a fresh console process anyways, however in the UI by default we append the output unless you create a new panel on every run.

I don't want to create a new panel each run as I would end with a lot of panels to delete. Is there any way of clearing the panel (i.e the equivalent of Terminal Clear) when the build starts?

No, but there is a feature request for it here: https://github.com/Microsoft/vscode/issues/30058


NextJS 14 causes issue: fetch is not a function

I upgraded nextjs to v14.0.1 and since then I cannot send out any notifications:
Error: fetch is not a function
    at Webhook.send (webpack-internal:///(rsc)/./node_modules/discord-webhook-node/src/classes/webhook.js:62:41)

Not sure what we can do here?

Having the same issue. No change in relevant code other than updating to nextjs 14

Same issue here. Might be due to the override NextJS does to fetch.

Still issue here, using just Nodejs.


[PLAT-7855] Update to the latest bugsnag-cocoa

Goal
Bugsnag Cocos2d has fallen far behind the mainline cocoa library, and needs to be brought up to date.
Design

The "fat binary" static libraries have been replaced with an xcframework. This is necessary because with the new M1 Mac, the arm architectures will clash between iphoneos, iphonesimulator, and macos.
The headers now reside inside the xcframework so that integrating bugsnag cocos2d-x is now simply a matter of adding the xcframework to your project. The documentation will need to be updated to reflect this.
The zipfile now has everything inside a top-level "bugsnag" directory to avoid any mess when extracting (so that it doesn't fill the current directory with stuff). The documentation will need to be updated to reflect this.
Runtime version info for cocos2d and the bugsnag plugin are now set automatically on plugin load, and do not have to be passed in by the user. The documentation will need to be updated to reflect this.
The bugsnag cocos2d-x cocoa plugin is loaded as a regular plugin (via the configuration object).

The new installation instructions will be:

Modify CMakeLists.txt (same as currently done)
Unzip bugsnag-cocos2dx.zip to your top level app directory (creates a bugsnag dir)
Drag bugsang/cocoa/BugsnagCocos2dx.xcframework to "Frameworks, Libraries, and Embeded Content" in your app's General tab, and select Do Not Embed
In AppController.mm, add the following:

#import <Bugsnag/BugsnagCocos2dxPlugin.h>

...

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    BugsnagConfiguration *configuration = [BugsnagConfiguration loadConfig];
    [configuration addPlugin:[BugsnagCocos2dxPlugin new]];
    [Bugsnag startWithConfiguration:configuration];

...

Testing
E2E tests will be added in a later PR

Updated to use BugsnagCocos2dx all around.


Gom revisit

Summary

This PR standardizes the gom interface using loadswitch objects.
Testing

Will need to flatsat test this - not sure how good mocking will be.
Notes

Comments

[x] Add an x between the brackets if you commented your code well!

That will suffice for the gom-related stuff. I will probably have to get a multimeter and verify the GPIO though

Idk if you also want to merge master in but once you address my comment I'll approve

Why would I write code if I didn't want to merge into master?????

Merge master into this branch

Oh sorry I completely misunderstood what you said. Github says This branch has no conflicts with the base branch so no need to merge master into this branch

Lesson learned: just because there's no merge conflict doesn't mean there will be no errors caused by the merge


Instrument back/forward cache navigations

This change builds instrumentation for navigations enhanced by browser back/forward caches into the library.
This uses the pageshow event and it's .persisted property to identify a navigation and trigger a new measurement.
NOTE: This change bakes into the library that we should start a new measurement for TTVC whenever a page is restored from the back/forward cache.  I think this is almost always desirable, and therefore a good default, but I am not certain.
It's possible for a user to accomplish this today in user space, by importing the start() method and calling it manually.  It would also be possible to make this an opt-out configuration property.
I think a related question is how or whether we should let the user know that the measurement was started via back/forward cache restore.
Edit: I pushed another commit which reports navigationType in the detail object for each metric result.  I think this addresses most of my own concerns.  If someone wants to exclude back/forward measurements, they can do so by dropping values reported with the matching navigationType.  Similarly, they can include that metadata as a tag when persisting that measurement anywhere.

Thanks for the thorough reviews @hongrich and @umairnadeem!


Cross-client Teku VC Lodestar BN is not working

Description
According to the Kurtosis data (verified) Teku VC is not working with Lodestar BN. Should be fixed.
Actual list of compatibility is available at https://github.com/kurtosis-tech/ethereum-package?tab=readme-ov-file#beacon-node--validator-client-compatibility :

Grandine is not supporting separate BN/VC
Prysm VC is not supporting non-Prysm BN
Lighthouse BN + Teku VC is fixed by #8117

So it's the only case to resolve at the moment of creating this issue.

Lodestar API response doesn't contain required field finalized so we fail on this. I think we shouldn't try to guess it and could continue on this issue when Lodestar starts to provide spec response.

I picked this up from https://github.com/Consensys/teku/issues/8180

While experiencing the issue Teku-VC is complaining with
Apr 04 09:52:41 ursa-Xset teku[2401221]: 09:52:41.974 ERROR - Validator *** Error while connecting to beacon node event stream com.launch
darkly.eventsource.StreamIOException: java.net.ConnectException: Failed to connect to /<IP_ADDRESS>:1752 (See log file for full stack trace)

I am debugging Lodestar BN <> Teku VC right now trying to figure out remaining compatiblity issues like https://github.com/ChainSafe/lodestar/issues/6635 using Kurtosis. Teku VC seems to be stuck at startup.
I have this massiv stack trace, maybe it's helpful
024-04-08 22:43:32.374+00:00 | okhttp-eventsource-events[null]-1 | ERROR | teku-validator-log | Validator   *** Error while connecting to beacon node event stream
com.launchdarkly.eventsource.StreamIOException: java.net.SocketTimeoutException: timeout
at com.launchdarkly.eventsource.HttpConnectStrategy$Client.connect(HttpConnectStrategy.java:455) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
at com.launchdarkly.eventsource.EventSource.tryStart(EventSource.java:292) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
at com.launchdarkly.eventsource.EventSource.requireEvent(EventSource.java:595) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
at com.launchdarkly.eventsource.EventSource.readAnyEvent(EventSource.java:390) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
at com.launchdarkly.eventsource.background.BackgroundEventSource.pollAndDispatchEvent(BackgroundEventSource.java:194) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
at com.launchdarkly.eventsource.background.BackgroundEventSource.access$900(BackgroundEventSource.java:73) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
at com.launchdarkly.eventsource.background.BackgroundEventSource$1.run(BackgroundEventSource.java:141) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
at java.base/java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.net.SocketTimeoutException: timeout
at okio.SocketAsyncTimeout.newTimeoutException(JvmOkio.kt:146) ~[okio-jvm-3.6.0.jar:?]
at okio.AsyncTimeout.access$newTimeoutException(AsyncTimeout.kt:161) ~[okio-jvm-3.6.0.jar:?]
at okio.AsyncTimeout$source$1.read(AsyncTimeout.kt:339) ~[okio-jvm-3.6.0.jar:?]
at okio.RealBufferedSource.indexOf(RealBufferedSource.kt:430) ~[okio-jvm-3.6.0.jar:?]
at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.kt:323) ~[okio-jvm-3.6.0.jar:?]
at okhttp3.internal.http1.HeadersReader.readLine(HeadersReader.kt:29) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http1.Http1ExchangeCodec.readResponseHeaders(Http1ExchangeCodec.kt:180) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.connection.Exchange.readResponseHeaders(Exchange.kt:110) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.kt:93) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:34) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154) ~[okhttp-4.12.0.jar:?]
at com.launchdarkly.eventsource.HttpConnectStrategy$Client.connect(HttpConnectStrategy.java:452) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
... 9 more
Caused by: java.net.SocketException: Socket closed
at java.base/sun.nio.ch.NioSocketImpl.endRead(Unknown Source) ~[?:?]
at java.base/sun.nio.ch.NioSocketImpl.implRead(Unknown Source) ~[?:?]
at java.base/sun.nio.ch.NioSocketImpl.read(Unknown Source) ~[?:?]
at java.base/sun.nio.ch.NioSocketImpl$1.read(Unknown Source) ~[?:?]
at java.base/java.net.Socket$SocketInputStream.read(Unknown Source) ~[?:?]
at okio.InputStreamSource.read(JvmOkio.kt:93) ~[okio-jvm-3.6.0.jar:?]
at okio.AsyncTimeout$source$1.read(AsyncTimeout.kt:128) ~[okio-jvm-3.6.0.jar:?]
at okio.RealBufferedSource.indexOf(RealBufferedSource.kt:430) ~[okio-jvm-3.6.0.jar:?]
at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.kt:323) ~[okio-jvm-3.6.0.jar:?]
at okhttp3.internal.http1.HeadersReader.readLine(HeadersReader.kt:29) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http1.Http1ExchangeCodec.readResponseHeaders(Http1ExchangeCodec.kt:180) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.connection.Exchange.readResponseHeaders(Exchange.kt:110) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.kt:93) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:34) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201) ~[okhttp-4.12.0.jar:?]
at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154) ~[okhttp-4.12.0.jar:?]
at com.launchdarkly.eventsource.HttpConnectStrategy$Client.connect(HttpConnectStrategy.java:452) ~[okhttp-eventsource-4.1.1.jar:4.1.1]
... 9 more

I have been running Teku VC in the past with Lodestar and this was no an issue previously, and there haven't been any changes to Lodestar event stream API in a while, not sure what I would be looking for right now on our side.

Lodestar API response doesn't contain required field finalized so we fail on this. I think we shouldn't try to guess it and could continue on this issue when Lodestar starts to provide spec response.

Will be part of our next release https://github.com/ChainSafe/lodestar/pull/6645 so this issue should be resolved.
But I am seeing another issue, Teku is trying to call postStateValidators and if it's gets a 404 then it retries the getStateValidators API, so far so good. However, it looks like Teku does not property format the query parameters, as commas are encoded as %2C which means if you send multiple keys Lodestar will handle that as a single pubkey and not return any data.
Which is why I think Teku VC is stuck
22:45:02.158 WARN  - Validator   *** Slashing protection not loaded for validators: afa0594, a09202a, a4ee262, a9a7af2, a36bd97, 9531099, a0f52ee, abcb932, 8bbff01, 8ab4ac6, ad2becc, ae411a9, b02b9ed, 91edd2b, 8ea53b5, ab5b878, 824f5d9, 8fc37a8, a338e96, 8b3edb7… (250 total)
22:45:07.149 WARN  - Unable to retrieve status for 250 validators.

The interesting part though is that this encoding was fixed a while ago, I am running consensys/teku:latest

https://github.com/Consensys/teku/pull/7757

Making some progress, have just implemented the post validators endpoint and this fixes the issues mentioned in https://github.com/Consensys/teku/issues/8118#issuecomment-2043814649
But there is an issue that Teku VC thinks that the beacon node is not synced but I am not seeing GET /eth/v1/node/syncing being called, any chance Teku uses the head event to determine if beacon node is synced?
2024-04-09 23:32:02.001+00:00 | ValidatorTimingChannel-1 | WARN  | teku-validator-log | Validator   *** Skipped producing sync_signature while node is syncing  Count: 1, Slot: 65
2024-04-09 23:32:02.216+00:00 | validator-async-0 | INFO  | teku-validator-log | Validator   *** Published attestation        Count: 9, Slot: 65, Root: fefe653716e7dec9dc1737f20ed9b3a7a0d596ff83bdacbcd8e2405c1f3d4314

/eth/v1/events?topics=head is called but it fails to establish stream due to https://github.com/Consensys/teku/issues/8118#issuecomment-2043788664, I am still not sure why this happens, look like an issue at the socket layer.
The last issue that might be worth mentioning is that block production fails as well with the following error
2024-04-09 23:58:10.038+00:00 | validator-async-0 | ERROR | teku-validator-log | Validator   *** Failed to produce block  Slot: 196 Validator: 89ac09c
tech.pegasys.teku.api.exceptions.RemoteServiceNotAvailableException: Server error from Beacon Node API (url = http://<IP_ADDRESS>:8562/eth/v1/beacon/blocks, status = 500, message = Internal Server Error)
at tech.pegasys.teku.validator.remote.typedef.ResponseHandler.serviceErrorHandler(ResponseHandler.java:142) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.typedef.ResponseHandler.handleResponse(ResponseHandler.java:118) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.typedef.handlers.AbstractTypeDefRequest.executeCall(AbstractTypeDefRequest.java:152) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.typedef.handlers.AbstractTypeDefRequest.postOctetStream(AbstractTypeDefRequest.java:145) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.typedef.handlers.SendSignedBlockRequest.sendSignedBlockAsSsz(SendSignedBlockRequest.java:93) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.typedef.handlers.SendSignedBlockRequest.sendSignedBlockAsSszOrFallback(SendSignedBlockRequest.java:82) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.typedef.handlers.SendSignedBlockRequest.sendSignedBlock(SendSignedBlockRequest.java:72) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.typedef.OkHttpValidatorTypeDefClient.sendSignedBlock(OkHttpValidatorTypeDefClient.java:142) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.RemoteValidatorApiHandler.lambda$sendSignedBlock$11(RemoteValidatorApiHandler.java:270) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.infrastructure.async.SafeFuture.of(SafeFuture.java:80) ~[teku-infrastructure-async-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.RemoteValidatorApiHandler.sendRequest(RemoteValidatorApiHandler.java:479) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.validator.remote.RemoteValidatorApiHandler.lambda$sendRequest$34(RemoteValidatorApiHandler.java:474) ~[teku-validator-remote-24.3.1.jar:24.3.1]
at tech.pegasys.teku.infrastructure.async.SafeFuture.of(SafeFuture.java:72) ~[teku-infrastructure-async-24.3.1.jar:24.3.1]
at tech.pegasys.teku.infrastructure.async.ScheduledExecutorAsyncRunner.lambda$createRunnableForAction$1(ScheduledExecutorAsyncRunner.java:124) ~[teku-infrastructure-async-24.3.1.jar:24.3.1]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
at java.base/java.lang.Thread.run(Unknown Source) [?:?]

Not sure why Teku calls block v1 API (fork is deneb) but anyhow the call is never received by Lodestar bn although Teku claims an 500, Internal server error. Additionally confirmed this by looking at the network traffic

Hello @nflaig
Thank you for collaboration!
I made a fix following your feedback, #8189
With it merged I was able to run Teku-Lodestar (:next docker) but only with count:2, which is not a requirement for any other BN/VC pair. While running it single, I have following issue for any submit/publish endpoint, we receive the same kind of error in Teku with 500 code:
Apr-11 16:18:56.327[api]             error: Error on submitPoolAttestations [1] slot=1, index=0 - PublishError.InsufficientPeers
Error: PublishError.InsufficientPeers
    at Eth2Gossipsub.publish (file:///usr/app/node_modules/@chainsafe/libp2p-gossipsub/dist/src/index.js:1561:19)
    at async NetworkCore.publishGossip (file:///usr/app/packages/beacon-node/lib/network/core/networkCore.js:291:32)
Apr-11 16:18:56.328[api]             error: Error on submitPoolAttestations [0] slot=1, index=0 - PublishError.InsufficientPeers
Error: PublishError.InsufficientPeers
    at Eth2Gossipsub.publish (file:///usr/app/node_modules/@chainsafe/libp2p-gossipsub/dist/src/index.js:1561:19)
    at async NetworkCore.publishGossip (file:///usr/app/packages/beacon-node/lib/network/core/networkCore.js:291:32)
Apr-11 16:18:56.328[rest]            error: Req req-12 submitPoolAttestations error - Multiple errors on submitPoolAttestations
PublishError.InsufficientPeers
PublishError.InsufficientPeers
Error: Multiple errors on submitPoolAttestations
PublishError.InsufficientPeers
PublishError.InsufficientPeers
    at Object.submitPoolAttestations (file:///usr/app/packages/beacon-node/src/api/impl/beacon/pool/index.ts:104:15)
    at Object.handler (file:///usr/app/packages/api/src/utils/server/genericJsonServer.ts:45:23)
Apr-11 16:18:58.003[]                 info: Searching peers - peers: 0 - slot: 1 - head: (slot -1) 0x1a06…570b - exec-block: valid(0 0xd668…) - finalized: 0x0000…0000:0
Apr-11 16:19:00.152[api]             error: Error on publishAggregateAndProofs [0] slot=1, index=0 - PublishError.InsufficientPeers
Error: PublishError.InsufficientPeers
    at Eth2Gossipsub.publish (file:///usr/app/node_modules/@chainsafe/libp2p-gossipsub/dist/src/index.js:1561:19)
    at async NetworkCore.publishGossip (file:///usr/app/packages/beacon-node/lib/network/core/networkCore.js:291:32)
Apr-11 16:19:00.153[rest]            error: Req req-14 publishAggregateAndProofs error - PublishError.InsufficientPeers
Error: PublishError.InsufficientPeers
    at Eth2Gossipsub.publish (file:///usr/app/node_modules/@chainsafe/libp2p-gossipsub/dist/src/index.js:1561:19)
    at async NetworkCore.publishGossip (file:///usr/app/packages/beacon-node/lib/network/core/networkCore.js:291:32)
Apr-11 16:19:04.239[rest]            error: Req req-17 publishBlock error - PublishError.InsufficientPeers
Error: PublishError.InsufficientPeers
    at Eth2Gossipsub.publish (file:///usr/app/node_modules/@chainsafe/libp2p-gossipsub/dist/src/index.js:1561:19)
    at async NetworkCore.publishGossip (file:///usr/app/packages/beacon-node/lib/network/core/networkCore.js:291:32)

For all other issues:

" Validator   *** Error while connecting to beacon node event stream"
I see this issue, it's ok with snooper disabled, will check more tomorrow a bit more, it looks like a snooper issue, because all is good with eventstream with snooper disabled
I am running consensys/teku:latest
you could use consensys/teku:develop now, it will include getStateValidators fix
Skipped producing sync_signature while node is syncing
it's linked with eventstream subscription failure, no head, no sync_signature could be produced, I will dig more, what is the source of the issue
Not sure why Teku calls block v1 API (fork is deneb)
It's not required to switch to v2 on Deneb, deneb should be supported for v1. We have v2 implemented but we don't want to make it default yet, see #8126
 but anyhow the call is never received by Lodestar bn although Teku claims an 500
We send ssz encoded block, there was a bug in snooper (Kurtosis http requests logging proxy) with octet-streams, it's now fixed, if you update Kurtosis, it will work. So Teku will try ssz, get 415 error and fallback to json, which is supported by Lodestar. Also ssz could be disable by flag, but not required as fallback is working.

I made a fix following your feedback, https://github.com/Consensys/teku/pull/8189

Awesome, thanks for that. We also merged the post variant of validators endpoint (https://github.com/ChainSafe/lodestar/pull/6655), our :next image has it now, and will soon be released.

With it merged I was able to run Teku-Lodestar (:next docker) but only with count:2, which is not a requirement for any other BN/VC pair. While running it single, I have following issue for any submit/publish endpoint, we receive the same kind of error in Teku with 500 code:

This is kinda expected, we require additional flags to run Lodestar without peers, see https://github.com/kurtosis-tech/ethereum-package/issues/555.

For all other issues:

Great catch, disabling snooper indeed fixes all the remaining issues
or Lodestar next with post endpoints
Seems fixed with snooper disabled and event stream working
Fair, was thinking it's maybe part of the issue but your are totally right, it's fine to still use the API
Likely better for users to disable ssz if they run with Lodestar as beacon node (will add support soon™) as the retry delay might be problematic due to additional delay, oh well, most people run mev-boost anyways

Looks pretty healthy now
09:43:41.056 INFO  - Validator   *** Published block              Count: 1, Slot: 156, Root: ce036eaea8d1977c8854d071c19c3e21fa5f083264d9940977b1854183d4d980, Blobs: 0, 0 (0%) gas, EL block: 039c0e1fa5f3fea49fba5dc38bb6492a03095cd92b20391492dafb9c035e8d9b (118)
09:43:41.721 INFO  - Validator   *** Published sync_signature     Count: 123, Slot: 156, Root: ce036eaea8d1977c8854d071c19c3e21fa5f083264d9940977b1854183d4d980
09:43:41.722 INFO  - Validator   *** Published attestation        Count: 9, Slot: 156, Root: ce036eaea8d1977c8854d071c19c3e21fa5f083264d9940977b1854183d4d980
09:43:49.434 INFO  - Validator   *** Published aggregate          Count: 1, Slot: 156, Root: ce036eaea8d1977c8854d071c19c3e21fa5f083264d9940977b1854183d4d980
09:43:49.489 INFO  - Validator   *** Published sync_contribution  Count: 15, Slot: 156, Root: ce036eaea8d1977c8854d071c19c3e21fa5f083264d9940977b1854183d4d980
09:43:53.707 INFO  - Validator   *** Published sync_signature     Count: 123, Slot: 157, Root: 91fbfb851b05585d95aa5c2f3c9a1bd8de43e5de807779f29d53f476aecacfc8
09:43:53.768 INFO  - Validator   *** Published attestation        Count: 3, Slot: 157, Root: 91fbfb851b05585d95aa5c2f3c9a1bd8de43e5de807779f29d53f476aecacfc8
09:44:01.404 INFO  - Validator   *** Published aggregate          Count: 1, Slot: 157, Root: 91fbfb851b05585d95aa5c2f3c9a1bd8de43e5de807779f29d53f476aecacfc8
09:44:01.550 INFO  - Validator   *** Published sync_contribution  Count: 12, Slot: 157, Root: 91fbfb851b05585d95aa5c2f3c9a1bd8de43e5de807779f29d53f476aecacfc8
09:44:09.769 INFO  - Validator   *** Published sync_signature     Count: 123, Slot: 158, Root: 91fbfb851b05585d95aa5c2f3c9a1bd8de43e5de807779f29d53f476aecacfc8
09:44:09.773 INFO  - Validator   *** Published attestation        Count: 7, Slot: 158, Root: 91fbfb851b05585d95aa5c2f3c9a1bd8de43e5de807779f29d53f476aecacfc8

Closing the compatibility issue on our side, thanks @zilm13, great collaboration :rocket:

Great!
Checked how it runs single with the flags, everything is perfect.
Yeah, it's better to disable ssz on prod nodes in this case.
I've also contacted Kurtosis team, they will investigate on events stream issue in snooper, let's see.
Thank you again, closing the issue on our side, too.

Updated snooper has been released, which supports ssz. Thanks to @parithosh


IE8 compatibility fix

addEventListener is not supported in IE8.

This project is no longer maintained now that their is widespread support for the object-fit and object-position CSS properties in modern browsers


handle Ansilbe 2.0 compatibility issues

With this update the scripts works with Ansible 2.1.0

@nirmaayan can you test with Ansible 1.9, to validate backward compatibility?

tested with Ansible 1.9 on Ubuntu 14 as well


Change 'Your Name' to something more friendly

For those who don't want to customise the page it makes for nicer reading if there's a friendlier default for name instead of 'Your Name' otherwise the first message you see is 'Good Morning Your Name' perhaps you could change it to one of these:

Friend
Old bean
Chum
Matey
Me old china
...

N.B. I'm not saying this just because it's April 1st :)

Yeah could change this :)


Allow a description to be specified at point of file creation

Allow a description to be specified at point of file creation that can be used to search for files.
This is useful because currently users need to encode this type of information in the filename.

Release notes


add 2025 edition

Hi @nwlandry , thanks for this. Unfortunately the link to the 2024 edition doesn't work. Could you take a look?

Hi @vtraag --- I'm not sure that I will be able to figure this out in a short amount of time (the real issue is compiling multiple index files), so I will remove the link and we can figure it out later. On another note, it would streamline the process if you can enhance my permissions so I can directly contribute to this repo.

I also took a quick look, but I'm not that familiar with Jekyll anyway. It seems that you can link to it from navigation, but I couldn't figure out how to make a two-level hierarchy in the navigation menu (which is what you'd like).
Yes, indeed, probably more convenient with direct access. Gave you write access to the repo now!


Fix subtitles to work for current stable version of subliminal (1.0.1)

Updated to work with the current stable version of subliminal (1.0.1)
This solves this problem http://flexget.com/ticket/3047

@nikdoof thanks


Fixed #28575 - Added a custom metaclass for exceptions to ensure they are pickleable

This adds a custom metaclass for dynamically created exceptions attached to models on creation. It also adds a pickling function and registers it with the pickler dispatch table for the custom metaclass.

Oh, I didn't notice the PR is for stable/1.11.x. All pull requests should go to master. This doesn't qualify for a backport to 1.11 per our supported versions policy as it's not a regression or a bug in a new master. Thanks!


Array of objects as option

Works fine when you set a renderRow function.
But when you select a option, the selected data is set to [Object object].. it should use the renderRow function to extract the data to show.
Or a seperate function that is

Yes. I don't know the data structure of your array so you have to do the work on your own renderRow.

it should implemented a function for the render of the current element.
As your example and docs provide information that points to Objects can be used.

I think it's the same for developers to just use renderRow to do it.
Or I missunderstand what you mean?

Hi @sohobloo  firstly, thanks for the component. But I am facing the same issue as @stoffern. I have provided a function to generate the view required for renderRow. However, after the row is selected, the name displayed is [object Object]. This is the code I am using:
<ModalDropdown              options={collection}             renderRow={(row) => displayRow(row)}             onSelect={...} />
const displayRow = (data) => {     return (         <TouchableHighlight>             <View style={styles.row}>                 <Image source={{ uri: data.image}} style={styles.photo} />                 <Text style={styles.selectedFont}>{${data.name} (${data.age})}</Text>             </View>         </TouchableHighlight>     ) }
Do you see anything wrong here? Ignore the onSelect function.

@Amila17 @stoffern

As I mentioned in this commit 9f3bc087bdb5ad4748cb2e7030d144249a367c50
Be sure to render your own trigger or I don't know what text to display
on it.

@sohobloo yeap, that makes sense now. For the moment I will use the workaround you have mentioned above. But I guess it would be better to specify a property like modalDropDownName when providing object array's as a source. This would make things cleaner.
Thanks for the response 👍

@Amila17 can you show me how you solved this problem?
Im having the same problem with data fetched from json array. But I don't know how to render my own button and use it as wrapper. Im new to react native.

我觉得他的意思就是用object类型的array作为数据放入  options里面不能使用，因为 没有类似 picker组建的 selectedValue 和 onvaluechange,   当用objectArray作为options，你选择某个选项上面只会显示{object,object} 不能正常显示 object的 key 或 value

我现在就碰到了这个问题~显示{object,object} 。看来得自己改下了。

传入对象的时候显示[object object]这个到底咋解决啊，一脸懵逼


Use the same identity for Titan uploads

I was quite confused when I tried to edit pages in the new Transjovian capsules. There's a quick introduction at gemini://transjovian.org/phoebe/page/Capsules, the capsules themselves are gemini://transjovian.org/capsule – the problem is that uploading there requires a client certificate and the Titan uploads do not default to using the same certificate as I used while browsing. This makes sense from a technical perspective, since the URL scheme is different, but from a practical perspective, I think it's highly likely that the same client certificate is going to be used. Alternatively, we could use the same solution as for text and token: keep the last one used so that we don't have to keep picking one for every edit.
(And on my side, I should make sure that the token is not checked when a client certificate is used. Right now, both are checked.)

keep the last one used so that we don't have to keep picking one for every edit.

This is probably a good idea. Currently, the upload dialog's identity selection only applies to the current upload URL in its entirety, when in practice it should be remembered as a site-specific setting. The infrastructure for that exists now in v1.8; it didn't before.

This will be included in 1.8.3.


The AppSmith EDITOR is constantly hanging showing browser "Kill or Wait" window

The AppSmith EDITOR is constantly hanging showing browser "Kill or Wait" window
How I reproduce this:

Created table that displays some query data.
Created Textbox
In the text box property started creating binding: typed "{{table."  after I typed dot it hangs. Sometimes it may not hang. But when I repeat it later it will may hang
When I reload the page it will be displaying error and will hang again - w/o ability to edit something.

@President Apologies! Is this on Appsmith cloud or self-hosted? Do you face this only while typing in the property pane? Is it possible to record a video of this happening?

FYI:
I have found that it happens when I am using query that returns 4000+ rows and 20 columns.
It seems AppSmith tries to fetch and put all that data right into single text element and it halts whole the Editor.
When I limited the result to just 3 rows (temporary added LIMIT to the query) - it all started working well

Hi @President , Thanks for the details.
If you are using it in a table, it exposes the pageSize and pageNo properties. You can use them in your query like this.
Example
select * from users limit {{ Table1.pageSize }} offset {{ (Table1.pageNo - 1) * Table1.pageSize }}
Ref: https://docs.appsmith.com/core-concepts/displaying-data-read/display-data-tables#pagination
Let me know if this solves your use case or if you need further help.


Postpending & prepending at the same time?

Everything's working nicely, apart from one thing. I would like to apply prepending and postpending for different criteria at the same time. But seems just to work for one. For example frontmatter value_A: 1 gets prepended with 1_ and frontmatter value_B: X gets postpended with X. There is no logical contradiction, but it doesn't work. What am I doing wrong?  I use Samsung S4 Tablet and all Software up to date. Suggestions welcome:😉

A

It works for me, but I've specifically disabled unneeded styling options, so prefix rules can only prepend and postfix rules can only append - so maybe that's why I had no issues


Split backends

Split each backend to a separate file, makes it more clearer to read, understand and maintain.

@kisvegabor I've did a general clean up, I need to also add X11 support, because it's still used on many systems.


FINERACT-1022 - Update to org.ehcache

sues.apache.org/jira/browse/FINERACT-1022

FINERACT-1022 says this may be broken, and we thus may revert this again.


Don't leak enum names.

The ->name field of the typeinfo is never freed at the moment.

Oops, you are right. Thanks!


add an in-memory xattr implementation

This didn't seem to fix anything so far, but I thought it might be useful for future stuff thus the PR. Also if this implementation has some major flaws this would be a good opportunity to find out and re-do some tests for GarageBand.
Thanks!

Thanks for looking! I actually don't know why those name replacement; but that's what osxfuse does. I followed the same logic in hope to fix it. It didn't fix anything so I never went further to find out why.


Using setState within afterFilter hook call results in the cancelation of filtering

Description

Using setState within afterFilter hook call results in the cancelation of filtering.
Steps to reproduce

Filter out any values via filter by value option.

Result
The values as still there. They are removed if you comment our the setState method in the afterFilter hook.
Demo

https://jsfiddle.net/eudmgt63/2/
Related issues

https://github.com/handsontable/react-handsontable/issues/132
(forum origin) https://forum.handsontable.com/t/call-setstate-in-after-hooks-will-not-trigger-rerender/4761

Your environment

React wrapper version: 4.0.0
Handsontable version: 8.0.0
Browser Name and version: Chrome 86
Operating System: macOS Catalina 10.15.6

Hi there,
Do we get a solution for this bug?

Hi @masry707
This issue is still replicable using the latest version of Handsontable (8.3.0 https://jsfiddle.net/handsoncode/u93gjbs8/) and hasn't been scheduled yet.
However, I will make sure to notify you upon the release.

Hi @masry707,
We merged wrapper for React into our main repository, handsontable/handsontable. Now library and wrapper are available in monorepo.
We also transfer all issues into one common issue board, where you can follow work progress and request issues.


wrong ELF class: ELFCLASS32) : ignored

ERROR: ld.so: object '/home/motafa/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/usr/bin/sh: 0: cannot open ./cream.sh: No such file

What game is this? Can you post a screenshot of your game's directory?

Gotham knights is the game

I suppose you actually put the files in the game's directory now. :P Once you test, can you please let me know if the game does actually work with creamlinux and the DLCs are unlocked?

sorry for bothering you, the creamlinux launch option command work i can start the game but no dlc still its a plus i can start the game lol

Don't worry about it, I'm here to help. I can't count the amount of times I forgot to unpack creamlinux or something like that too :)
Do you have the actual physical DLC files in the game? Some games include all the DLC files by default and just need creamlinux to "unlock" them, but for others you need to source the actual DLC files yourself in addition to using creamlinux.

Also you will in any case have to add the IDs of the DLCs to the file cream_api.ini. Since it looks like the game only has 1 DLC, you can just add this to the end of cream_api.ini:
41516930 = Gotham Knights: Visionary Pack

i dont have the physical dlc file imma try it tho.
ps: your the best <3

wait i dont get it how did you fix it?


v0.37.x: Unscheduled Runs shouldn't be included in full status

Changes
Fixes #5282
When removing conditions, I accidentally made GetRunsStatus not skip including custom task ResolvedPipelineTasks without Runs in the PipelineRun.Status.Runs map. This resulted in cancellation failing, because the cancellation logic tries to patch each Run or TaskRun in the PipelineRun status (either in the Runs and TaskRuns maps for full embedded status, or ChildReferences for minimal or both embedded status). Unscheduled PipelineTasks for Tasks were already properly excluded from the status map, and ChildReferences was fine either way, but due to the oversight I mentioned above, unscheduled PipelineTasks for custom tasks were included in the full embedded status map, and cancellation would error due to that.
cherry-picked from #5287, with some additional modifications to child reference population for custom tasks without a Run which have been fixed in v0.38.x.
/kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Fix cancellation of PipelineRuns with unscheduled custom tasks.

/assign @afrittoli @pritidesai @dibyom @lbernick @jerop

/lgtm

/test check-pr-has-kind-label


Ability to change allowEmpty from false to true

There was a couple weird things going on that prevented this from happening in the current build.
For one, if allowEmpty was false, clearButton was permanently hidden. After changing allowEmpty to true it was still empty, even with the sp-clear-enabled class applied. I couldn't find any benefit to hiding the button (it seems to hide itself just fine without using .hide()), so I removed it.
Two, once allowEmpty is false it was always false, so when trying to apply new options it's pretty much skipped over.

Weird fix but I couldn't access isInputTypeColor in applyOptions for unknown reasons, so I had to give it a value again.


Graph Connection

Running version 5.5.17 , on Win11.
It was working fine but now just get a spinning wheel on the Teams Status tab, and the below error message.

When my PC started it normally opens the web browser and signs into Teams and then the presence light minimizes down. But its not doing that anymore.

Do you have any more logs than this? There are some file logs as well

having the same issue - here's a log file:
log-2022092810.zip

@jeroenterheerdt can you try to logout of PresenceLight and log back in?

Not sure how to, because there is nothing in the UI that allows me to log out / log back in:

I tried restarting the app / rebooting, but that did not help at all.

I did, but for whatever reason that fixed it now. Only difference is that I was working from home yesterday when I tried that.

It might have been some caching issue. Glad you got it working

Closing


chore: LEAP-1700: bump pyredis and fakeredis

Groundwork for addressing https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-31655

/git merge develop

/git merge develop


Added support for Android "Reliable Writes" to my repo

I've added Reliable Writes for Android to my fork's master branch. I don't want to send you a pull request as I hacked the code a lot to remove the platforms I can't build/don't care about. If it is useful to you, feel free to take a look.
This fixed an issue we were seeing where is we had a low MTU, we could not reliable send bulk data to an ESP32 based device. The guys fixed a similar issue on the ESP32 side by using a similar approach, so I had a look around and found that others had gotten it working using the Reliable Write API.
If I get a chance I'll look at making it work on other platforms - but I don't do much other than Android at the moment and so it might be a while before I need to get it working.

Hi @memsom,
I'm the friendly issue checker.
It seems like (100.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!


feat: 🎸 paging carousel card (WIP)

Add drag gesture for page control.
Add a new carousel detail page.

video
preview

@MarcoEidinger  👍 , I will fix it.

@MarcoEidinger  For description and status, design is not provided yet, so I just add them by the mail showed.

One Card
Details Status

@ShadowTourist design for description and status was changed per email. Please adjust implementation. Thanks!

According to @ShadowTourist the implementation matches the design so lets get this PR merged, I'll provide build for verification and further feedback has to be uptaken by new PRs


Link not found

script.py is the basic file in the readme.

I just pulled in the latest code from master and ran this installation. I have configured universe correctly, since importing it works, so I'm sure configuration is not an issue. Please tell me if I am doing something wrong.

 flipswitch@devcenter  ~  python
Python 3.5.2 |Anaconda 4.2.0 (64-bit)| (default, Jul  2 2016, 17:53:06)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import universe
>>> import gym
>>> exit()

 flipswitch@devcenter  ~  cd junkyard/universe-example

 flipswitch@devcenter  ~/junkyard/universe-example  ls
script.py

 flipswitch@devcenter  ~/junkyard/universe-example  python script.py
[2016-12-06 03:31:29,706] Making new env: flashgames.DuskDrive-v0
[2016-12-06 03:31:29,723] Writing logs to file: /tmp/universe-10115.log
[2016-12-06 03:31:29,724] Configuring VNCEnv
[2016-12-06 03:31:29,751] [0] Creating container: image=quay.io/openai/universe.flashgames:0.19.45. Run the same thing by hand as: docker run -p 10000:5900 -p 10001:15900 --ipc host --cap-add NET_ADMIN --cap-add SYS_ADMIN quay.io/openai/universe.flashgames:0.19.45
[2016-12-06 03:31:29,756] Image quay.io/openai/universe.flashgames:0.19.45 not present locally; pulling
Pulling repository quay.io/openai/universe.flashgames
Traceback (most recent call last):
  File "/opt/anaconda3/lib/python3.5/site-packages/docker/client.py", line 170, in _raise_for_status
    response.raise_for_status()
  File "/opt/anaconda3/lib/python3.5/site-packages/requests/models.py", line 844, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localunixsocket/v1.24/containers/create?name=universe-gXhBpc-0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/flipswitch/junkyard/universe/universe/remotes/docker_remote.py", line 243, in _spawn
    container = self._spawn_container()
  File "/home/flipswitch/junkyard/universe/universe/remotes/docker_remote.py", line 282, in _spawn_container
    'com.openai.automanaged': 'true',
  File "/opt/anaconda3/lib/python3.5/site-packages/docker/api/container.py", line 135, in create_container
    return self.create_container_from_config(config, name)
  File "/opt/anaconda3/lib/python3.5/site-packages/docker/api/container.py", line 146, in create_container_from_config
    return self._result(res, True)
  File "/opt/anaconda3/lib/python3.5/site-packages/docker/client.py", line 178, in _result
    self._raise_for_status(response)
  File "/opt/anaconda3/lib/python3.5/site-packages/docker/client.py", line 173, in _raise_for_status
    raise errors.NotFound(e, response, explanation=explanation)
docker.errors.NotFound: 404 Client Error: Not Found ("b'{"message":"No such image: quay.io/openai/universe.flashgames:0.19.45"}'")

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "script.py", line 5, in <module>
    env.configure(remotes=1)  # automatically creates a local docker container
  File "/opt/anaconda3/lib/python3.5/site-packages/gym/core.py", line 246, in configure
    self._configure(*args, **kwargs)
  File "/home/flipswitch/junkyard/universe/universe/vectorized/core.py", line 57, in _configure
    super(Wrapper, self)._configure(**kwargs)
  File "/opt/anaconda3/lib/python3.5/site-packages/gym/core.py", line 350, in _configure
    return self.env.configure(*args, **kwargs)
  File "/opt/anaconda3/lib/python3.5/site-packages/gym/core.py", line 246, in configure
    self._configure(*args, **kwargs)
  File "/home/flipswitch/junkyard/universe/universe/wrappers/render.py", line 18, in _configure
    super(Render, self)._configure(**kwargs)
  File "/home/flipswitch/junkyard/universe/universe/vectorized/core.py", line 57, in _configure
    super(Wrapper, self)._configure(**kwargs)
  File "/opt/anaconda3/lib/python3.5/site-packages/gym/core.py", line 350, in _configure
    return self.env.configure(*args, **kwargs)
  File "/opt/anaconda3/lib/python3.5/site-packages/gym/core.py", line 246, in configure
    self._configure(*args, **kwargs)
  File "/home/flipswitch/junkyard/universe/universe/wrappers/throttle.py", line 27, in _configure
    super(Throttle, self)._configure(**kwargs)
  File "/home/flipswitch/junkyard/universe/universe/vectorized/core.py", line 57, in _configure
    super(Wrapper, self)._configure(**kwargs)
  File "/opt/anaconda3/lib/python3.5/site-packages/gym/core.py", line 350, in _configure
    return self.env.configure(*args, **kwargs)
  File "/opt/anaconda3/lib/python3.5/site-packages/gym/core.py", line 246, in configure
    self._configure(*args, **kwargs)
  File "/home/flipswitch/junkyard/universe/universe/envs/vnc_env.py", line 180, in _configure
    api_key=api_key,
  File "/home/flipswitch/junkyard/universe/universe/remotes/build.py", line 19, in build
    n=n,
  File "/home/flipswitch/junkyard/universe/universe/remotes/docker_remote.py", line 54, in __init__
    self._start()
  File "/home/flipswitch/junkyard/universe/universe/remotes/docker_remote.py", line 81, in _start
    [instance.start() for instance in self.instances]
  File "/home/flipswitch/junkyard/universe/universe/remotes/docker_remote.py", line 81, in <listcomp>
    [instance.start() for instance in self.instances]
  File "/home/flipswitch/junkyard/universe/universe/remotes/docker_remote.py", line 219, in start
    self._spawn()
  File "/home/flipswitch/junkyard/universe/universe/remotes/docker_remote.py", line 249, in _spawn
    self._pull_image()
  File "/home/flipswitch/junkyard/universe/universe/remotes/docker_remote.py", line 258, in _pull_image
    progress_stream.stream_output(output, sys.stdout))
  File "/home/flipswitch/junkyard/universe/universe/remotes/compose/progress_stream.py", line 23, in stream_output
    print_output_event(event, stream, is_terminal)
  File "/home/flipswitch/junkyard/universe/universe/remotes/compose/progress_stream.py", line 58, in print_output_event
    raise StreamOutputError(event['errorDetail']['message'])
universe.remotes.compose.progress_stream.StreamOutputError: Tag 0.19.45 not found in repository quay.io/openai/universe.flashgames
 flipswitch@devcenter  ~/junkyard/universe-example  docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
 flipswitch@devcenter  ~/junkyard/universe-example 

This is /tmp/universe-10115.log
[2016-12-06 03:31:29,724] Configuring VNCEnv
[2016-12-06 03:31:29,751] [0] Creating container: image=quay.io/openai/universe.flashgames:0.19.45. Run the same thing by hand as: docker run -p 10000:5900 -p 10001:15900 --ipc host --cap-add NET_ADMIN --cap-add SYS_ADMIN quay.io/openai/universe.flashgames:0.19.45
[2016-12-06 03:31:29,756] Image quay.io/openai/universe.flashgames:0.19.45 not present locally; pulling

I think you're still using the beta version of this repo. Should be enough to reclone this one!


using this.$axios instead of axios

look goods to me.
test with zookeeper 3.5, dubbo 2.7.6 works well


Can Structor build documentation only for master branch?

Hi,
My project is in an early stage in which we do not have any branch release yet. Thus, can structor build the documentation when the only active branch is master and it is defined as experimental?
Thanks.

Hi, yes structor can build the documentation of the master when it's the only master branch.

Hello,
I am trying to build the documentation for the master branch and structor fails. I don't have any other branches at the moment as the project is in early stages.
Please check this line, which says Error: error when build versions: Malformed version. I did not set the STRUCTOR_LATEST_TAG as there are no tags (v* branches) to to build.
Any ideas how should I setup the structor to work properly?
Thanks.


Sysbuild fails on MacOS

Describe the bug
Build fails when building using west build  --sysbuild on MacOS.
We have two different MacOS computers that have the same problem and 3 Linux computers that don't.
When building without sysbuild:
west build -b mimxrt1024_evk samples/hello_world  -p
everything works fine on both MacOs and Linux.
When building with sysbuild:
west build -b mimxrt1024_evk --sysbuild samples/hello_world -p
everything works fine on Linux, but fails on MacOS.
It also fails on mcuboot when building hello_world with sysbuild and mcuboot:
west build -b mimxrt1024_evk --sysbuild samples/hello_world  -p -- -DSB_CONFIG_BOOTLOADER_MCUBOOT=y
everything works fine on Linux, but fails on MacOS.
The error is:
/Users/jonramstedt/zephyrproject/zephyr/boards/arm/mimxrt1024_evk/mimxrt1024_evk-pinctrl.dtsi:9:10: fatal error: nxp/nxp_imx/rt/mimxrt1024dag5a-pinctrl.dtsi: No such file or directory
    9 | #include <nxp/nxp_imx/rt/mimxrt1024dag5a-pinctrl.dtsi>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
CMake Error at /Users/jonramstedt/zephyrproject/zephyr/cmake/modules/extensions.cmake:3714 (message):
  failed to preprocess devicetree files (error code 1):
  /Users/jonramstedt/zephyrproject/zephyr/boards/arm/mimxrt1024_evk/mimxrt1024_evk.dts

I have tried to do some troubleshooting and I have found that the cmake variables DTS_ROOT in pre_dt.cmake and
DTS_ROOT_SYSTEM_INCLUDE_DIRS in dts.cmake doesn't contain the hal directories on MacOS.
Such as "/Users/jonramstedt/zephyrproject/modules/hal/nxp/dts". But I am stuck on finding the cause and how to solve this issue.
To Reproduce
Steps to reproduce the behavior:

cd $ZEPHYR_BASE
west build -b mimxrt1024_evk --sysbuild samples/hello_world -p
build failed
Error as written above.

Expected behavior
I expected the sample to build correctly with --sysbuild
Impact
It is not possible to build firmware with mcuboot
Logs and console output
~/zephyrproject/zephyr tags/zephyr-v3.4.0 $ west build -b mimxrt1024_evk --sysbuild samples/hello_world  -p
-- west build: making build dir /Users/jonramstedt/zephyrproject/zephyr/build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): extensions sysbuild_extensions python west root zephyr_module boards shields sysbuild_kconfig
-- Found Python3<EMAIL_ADDRESS>(found suitable exact version "3.11.4") found components: Interpreter
-- Cache files will be written to: /Users/jonramstedt/Library/Caches/zephyr
-- Found west (found suitable version "1.0.0", minimum required is "0.14.0")
-- Board: mimxrt1024_evk
Parsing /Users/jonramstedt/zephyrproject/zephyr/share/sysbuild/Kconfig
Loaded configuration '/Users/jonramstedt/zephyrproject/zephyr/build/empty.conf'
Merged configuration '/Users/jonramstedt/zephyrproject/zephyr/build/empty.conf'
Merged configuration '/Users/jonramstedt/zephyrproject/zephyr/build/empty.conf'
Configuration saved to '/Users/jonramstedt/zephyrproject/zephyr/build/zephyr/.config'
Kconfig header saved to '/Users/jonramstedt/zephyrproject/zephyr/build/autoconf.h'
--
   *********************************
   * Running CMake for hello_world *
   *********************************

Loading Zephyr default modules (Zephyr base).
-- Application: /Users/jonramstedt/zephyrproject/zephyr/samples/hello_world
-- CMake version: 3.25.2
-- Found Python3: /Users/jonramstedt/.pyenv/shims/python3.11 (found suitable exact version "3.11.2") found components: Interpreter
-- Cache files will be written to: /Users/jonramstedt/Library/Caches/zephyr
-- Zephyr version: 3.4.0 (/Users/jonramstedt/zephyrproject/zephyr)
-- Board: mimxrt1024_evk
-- Found host-tools: zephyr 0.16.1 (/Users/jonramstedt/zephyr-sdk-0.16.1)
-- Found toolchain: zephyr 0.16.1 (/Users/jonramstedt/zephyr-sdk-0.16.1)
-- Found Dtc: /opt/homebrew/bin/dtc (found suitable version "1.7.0", minimum required is "1.4.6")
-- Found BOARD.dts: /Users/jonramstedt/zephyrproject/zephyr/boards/arm/mimxrt1024_evk/mimxrt1024_evk.dts
In file included from /Users/jonramstedt/zephyrproject/zephyr/boards/arm/mimxrt1024_evk/mimxrt1024_evk.dts:10,
                 from <command-line>:
/Users/jonramstedt/zephyrproject/zephyr/boards/arm/mimxrt1024_evk/mimxrt1024_evk-pinctrl.dtsi:9:10: fatal error: nxp/nxp_imx/rt/mimxrt1024dag5a-pinctrl.dtsi: No such file or directory
    9 | #include <nxp/nxp_imx/rt/mimxrt1024dag5a-pinctrl.dtsi>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
CMake Error at /Users/jonramstedt/zephyrproject/zephyr/cmake/modules/extensions.cmake:3714 (message):
  failed to preprocess devicetree files (error code 1):
  /Users/jonramstedt/zephyrproject/zephyr/boards/arm/mimxrt1024_evk/mimxrt1024_evk.dts
Call Stack (most recent call first):
  /Users/jonramstedt/zephyrproject/zephyr/cmake/modules/dts.cmake:231 (zephyr_dt_preprocess)
  /Users/jonramstedt/zephyrproject/zephyr/cmake/modules/zephyr_default.cmake:115 (include)
  /Users/jonramstedt/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /Users/jonramstedt/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:5 (find_package)

-- Configuring incomplete, errors occurred!
CMake Error at cmake/modules/sysbuild_extensions.cmake:404 (message):
  CMake configure failed for Zephyr project: hello_world

  Location: /Users/jonramstedt/zephyrproject/zephyr/samples/hello_world
Call Stack (most recent call first):
  CMakeLists.txt:90 (ExternalZephyrProject_Cmake)

-- Configuring incomplete, errors occurred!
See also "/Users/jonramstedt/zephyrproject/zephyr/build/CMakeFiles/CMakeOutput.log".
FATAL ERROR: command exited with status 1: /opt/homebrew/bin/cmake<EMAIL_ADDRESS>-B/Users/jonramstedt/zephyrproject/zephyr/build -GNinja -DBOARD=mimxrt1024_evk -S/Users/jonramstedt/zephyrproject/zephyr/share/sysbuild -DAPP_DIR:PATH=/Users/jonramstedt/zephyrproject/zephyr/samples/hello_world

Environment

OS: MacOS 13.5.2
Toolchain: zephyr-sdk-0.16.1
Commit: 356c8cbe63 (tag: zephyr-v3.4.0, tag: v3.4.0) release: Zephyr 3.4.0 release

I did west zephyr-export now. And it works!
I didn't do it after changing from commit v3.0.0 to v3.4.0. I only did west update.
thank you!


Fix tests

Fixes #67, #81, #125

[x]   General Comment
<img border=0 src='https://avatars.githubusercontent.com/u/803796?v=3' height=16 width=16'> @brentschmaltz

This pull request is now managed with CodeReviewHub. Refresh.

@brentschmaltz

:shipit:

f440d04414548e86fee58e4b4e254095e920d340


fix: remove "Error when determining async func"

Description
When Appsmith parse function internally to determine if a function is async or not, when that function faces an error we used to log that error to console.
This was confusing for our users who thought due to this error that something went wrong.
hence we remove "Error when determining async func".
Fixes #12639
Type of change

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

How Has This Been Tested?
Manually
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/consoleErrors-async

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
56.35 (0)
37.81 (0.01)
35.96 (0)
56.58 (0.01)

:green_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.94 (0.23)
41.67 (0.84)
36.21 (0)
56.99 (0.25)

:red_circle:
app/client/src/workers/evaluate.ts
85.42 (-0.1)
54.05 (0)
84 (0)
84.44 (-0.12)

/ok-to-test sha=b023416

/ok-to-test sha=b82eb07

/ok-to-test sha=b71fa19

/ok-to-test sha=346e9b4

/ok-to-test sha=1742bd6

/ok-to-test sha=f392a47

/ok-to-test sha=aabc9aa

/ok-to-test sha=acf16d6

/ok-to-test sha=001fd7f


Fixed overflow in mobile view

Fixed #31
The overflow was caused by the gradient in the hero section.
Decreased the size for smaller screens and added media query that restores the original size for larger screens.
Also added flex wrap property on the buttons in the hero section to align them vertically on smaller screens.

The code seems to be well-written and follows best practices for using Tailwind CSS.
Media Query Looks Better for small screens and medium screens
Buttons are aligned in small screens


Fixed some creature IDs & spelling

Fixed wrong IDs for Serpent Fly, Dragon Fly, Basilisk, Greater Basilisk, Gorgon, Mighty Gorgon. Also fixed spelling/case for a few creature names (Chaos Hydra, Demon, Serpent Fly, Dragon Fly, Efreeti, Gold Golem).

Again, thank you very much for the fixes!


Explicitly require the initializer generator

Hi Sunny
Re: https://github.com/stevehodgkiss/generator_spec/issues/39
The NameError was happening because the initializer constant wasn't loaded, and active support couldn't automatically load it (it would have tried to find "wine_bouncer/generators/initializer_generator" somewhere on the load path). Explicitly loading it here fixes the issue.

Hey @stevehodgkiss, thanks very much.


Blogs: add index pages for each sub url level

🚀 Feature
We should have index pages for year, month, and day URLs in the blogs.
Have you read the Contributing Guidelines on issues?
Yea
Motivation

There has long been requests for blog archives. This feature request essentially calls for an out-of-box archive feature.
The URL logic for blogs is not the most optimal—when I see a URL like https://docusaurus.io/blog/2021/05/12/announcing-docusaurus-two-beta, I would naturally believe that the pages https://docusaurus.io/blog/2021 or https://docusaurus.io/blog/2021/05 should exist, but these are unfortunately 404s.

Combining these two motivations, a solution would be to put an index page at the /blog/2021 and /blog/2021/05 directories.
Just noticed that there's a Canny request for this as well: https://docusaurus.io/feedback/p/date-filter-using-url
Pitch
When building the site, add an index.html file at each directory level. The content can be in a "blog feed" format, showing all blog posts within that range. For example, /blog/2021/05/index.html will show all blog posts written in May, 2021.

@slorber Is this worth consideration? (This will likely result in quite some UI refactoring) If not I'm going to close it anyways, since I solved my need with a custom plugin. See here for example: https://joshcena.com/blog/2021

Hey
This is definitively worth adding.
@johnnyreilly already has something similar on his blog: https://blog.johnnyreilly.com/2021/05/01/blog-archive-for-docusaurus/
I suggest having a /blog/archive page by default, displaying all the posts with just the title.
And creating a page per year can also be a thing, maybe we can display more than the title there?
The archive page can allow linking to the yearly pages.
Is it really worth it to have a page per blog month? I wouldn't turn it on by default because very often people write less than a post per month.

This will likely result in quite some UI refactoring

What do you mean? It's probably just creating a few extra pages in the blog plugin, and probably does not need to change much the existing logic?

P.S. This implementation is not optimal since https://joshcena.com/zh-Hans/blog/2021 is not created simultaneously

Why isn't it created automatically? Not sure to understand how it's implemented.

weirdly, if I direct back to en through the locale dropdown, I'm taken to https://blog/2021

I will have to check that, it's the 2nd time this kind of issue is reported already, there's likely an edge case to handle somewhere. Wonder if it's not related to trailing slash.

How do I correctly make my plugin work with i18n?

I think what is missing is just the locale as baseUrl, you probably need to add in: normalizeUrl([baseUrl, routeBasePath,"archive"]): https://github.com/Josh-Cena/Personal-page/blob/master/src/plugins/plugin-blog-index/index.ts#L56

Is it really worth it to have a page per blog month? I wouldn't turn it on by default because very often people write less than a post per month.

My proposal was mainly to fix the case where I have a page at https://joshcena.com/blog/2021/02/27/hello but then nothing on https://joshcena.com/blog/2021/02—at least for me, I would expect every level of the URL to be working. If the blog link could instead be like https://joshcena.com/blog/2021-02-27-hello there would be less confusion.
About the UI refactor, when I was swizzling the blog list page, I found it hard to add the links to the year/month index pages based on the existing page layout, so I ended up doing a lot of customizations. In order to expose an intuitive enough "entry link" to the archive pages we have to redesign the blog list page... (I also think the blog tags list page is too deeply hidden—you have to first visit the blog tag posts page by clicking on one tag, and then direct back.)
About the i18n, my implementation is all in plugin-blog-index/index.ts. I would check out the baseUrl issue, thanks:)

I would expect every level of the URL to be working

I don't think this is a legit expectation, considering you can choose the slug you want and add/remove slashes as you want, it does not always make sense to have an index page for each slash you have in the URL. You could also have permalinks without any slash and still want a yearly index page.

About the UI refactor, when I was swizzling the blog list page, I found it hard to add the links to the year/month index pages based on the existing page layout, so I ended up doing a lot of customizations.

The /blog/archive page could be created, but not necessarily appear on the blog list anyway. In this case the user would have to link to this page, as @johnnyreilly did with a navbar item here: https://blog.johnnyreilly.com/
I suggest that just adding an extra link "See all blog posts" to the archive page on the blog sidebar can be enough, at the bottom of this list:

And we don't particularly need to fully redesign the blog list page. It can be disruptive and annoying for existing users.

About the tags, I agree they are too deeply nested and not very accessible.
@sw-yx made the tags more accessible on the Temporal blog:
https://docs.temporal.io/blog/

This looks like a good idea to me and would be happy to add this by default for all users (even the featured posts is probably a nice option to propose)

haha yeah would make the sidebar a bit more useful than it is today

@slorber A quick note, adding baseUrl in addRoute did do the trick. Thanks!
Busy these weeks, but if no one will be working on this soon, I'd be willing to submit a PR myself

I did not realize that the Temporal blog was Docusaurus! Makes me think I should look into theming a bit - I've just been rolling with the defaults

heheh. you like? i havent even particularly invested much into theming as much as i wanted to, just made some basic design tweaks

I do like!  I don't suppose the website is open source?  Would be intrigued to examine the tweaks (with an eye on thievery :wink:)

@johnnyreilly https://github.com/temporalio/documentation/tree/master/src

Nice font: https://aeonik.co.uk/font/

Going to close this as wontfix, now that we have the archive page. I realized that with custom slugs this is probably not a good idea.


Illegal qubits when using QPU

When using the QVM to simulate hardware devices such as Aspen-4-9Q-A, i.e.,
qml.device("forest.qvm", device="Aspen-4-9Q-A")

PennyLane-Forest works as expected. From the main interface, PL wires (labeled 0-8) are converted to match the topology of the QPU (labelled 0,1,2,7,10,11,15,16,17).
However, when attempting to run the exact same program on the QPU,
qml.device("forest.qpu", device="Aspen-4-9Q-A")

it produces the error
Error: "Program instruction RX(pi/4) attempts to use illegal qubits: 3. Illegal qubits on this QPU: 3, 4, 5, 6, 8, 9, 12, 13"

Is there an error in how PennyLane-Forest perform the 'rewiring' of qubits for the QPU? Ideally, a computation with qubits labelled 0-8 should run seamlessly and be rewired behind the scenes for the user.
EDIT/UPDATE: There are two related issues here: (i) the one outlined above, and (ii) the in-ability to run programs on legal qubits on the lattice. Issue (i) can be illustrated by the following code snippet
import pennylane as qml
from pennylane import numpy as np

qpu = qml.device("forest.qpu", device="Aspen-4-4Q-E")
print(qpu.qc.qubits())  # [10, 11, 12, 17]

@qml.qnode(qpu)
def circuit(angle):
    qml.RY(angle, wires=0)
    return qml.expval(qml.PauliZ(0))

circuit(np.pi/2)   # raises `RPCError: Program instruction 'RY(pi/2) 0' attempts to use illegal qubits: 0. Illegal qubits on this QPU: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 13, 14, 15, 16.`

while issue (ii) can be illustrated by the following code snippet
import pennylane as qml
from pennylane import numpy as np

qpu = qml.device("forest.qpu", device="Aspen-4-4Q-E")
print(qpu.qc.qubits())  # [10, 11, 12, 17]

@qml.qnode(qpu)
def circuit(angle):
    qml.RY(angle, wires=10)
    return qml.expval(qml.PauliZ(10))

circuit(np.pi/2)    # raises `QuantumFunctionError: Operation RY applied to invalid wire 10 on device with 4 wires.`

Hi @josh146 , good to play around with pennylane-forest code after my break!
Question: is this still an issue? Using the latest versions on master (for both pennylane and pennylane-forest, not yet having merged the operator_estimation PR), I see that the following code runs without problem. Note that this happens despite qubit 0 being an illegal qubit on the lattice (I had to use a different example from yours, since Aspen-4-9Q-A has since been retired).
import pennylane as qml
from pennylane import numpy as np

qpu = qml.device("forest.qpu", device="Aspen-4-4Q-E")
print(qpu.qc.qubits())  # [10, 11, 12, 17]

@qml.qnode(qpu)
def circuit(angle):
    qml.RY(angle, wires=0)
    return qml.expval(qml.PauliZ(0))

circuit(np.pi/2)   # runs fine

However, note that the somewhat related problem of actually trying to specify a qubit that one would like to run a circuit on, and which is a legal qubit on the lattice. For example,
import pennylane as qml
from pennylane import numpy as np

qpu = qml.device("forest.qpu", device="Aspen-4-4Q-E")
print(qpu.qc.qubits())  # [10, 11, 12, 17]

@qml.qnode(qpu)
def circuit(angle):
    qml.RY(angle, wires=10)
    return qml.expval(qml.PauliZ(10))

circuit(np.pi/2)    # raises `QuantumFunctionError: Operation RY applied to invalid wire 10 on device with 4 wires.`

I think this latter problem should be easy enough to fix.

Ok nevermind, I was able to recover the original error msg after merging in the operator_estimation PR. I'm going to try to knock out both these issues at the same time.

I believe this is now solved, so closing this issue :)


Gutter icon runs Kotest spec with Gradle instead of Kotest runner configuration

I have a Gradle project in IntelliJ with Kotest tests.
In the editor window on the Kotest spec, when clicking the "Run" gutter icon the spec is executed with the Gradle runner.
Contrarily, launching the Kotest spec with the keyboard short Ctrl+Shift+R (on mac) runs the spec with a Kotest run configuration

Thanks


Add note about origins of resource yaml/md files

Signed-off-by: IanMadd<EMAIL_ADDRESS>This will add a comment to the top of each resource md/yaml file stating that the file is generated in chef/chef so make PRs there.
Description
This adds a comment generate_comment_x: <comment_text>to the top of the yaml/array and then after the array is converted to yaml, the generate_comment_x: is replaced with # leaving # <comment_text>.
Unfortunately we can't add a comment before the yaml, Hugo won't build the page, so it has to be added to the yaml or it could go after the yaml.
Related Issue
People are making PRs against the resource files in chef-web-docs but they originate from chef/chef.
Types of changes

[ ] 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)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

Circling back I think we actually want to figure out a way to handle this on the hugo side of things. We know the resources there and we can add whatever text we want. This generator should be for providing data to the docs site that it can't determine without the chef source code.

I can go either way, but I prefer the faster-to-achieve solution.

Closing in favor of the chef-web-docs fix


Fix typo in ApplicationModel property name

#2327  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

Aug 27, 6:41 PM EDT: @sgrimm started a stack merge that includes this pull request via Graphite.


[fpv] guidelines for RTL assertion

related to issue #1079, as @rasmus-madsen brought up, discuss with RTL and DV engineers for the guidelines on where to write assertions.

@cindychip
I like adding Assertions in a bind file then they are easy to locate if there is an issue.
and easy to overwrite if you have a special case or altered use of a module.
but I don't have a strong feeling against putting assertions directly in code, I think there are things that are in favor of that.
I do on the other hand feel that it is important to put interface checks with the interface etc.
to make sure they are shared by all users of the interface.
eitherway I think it is important to write a set of guidelines for this

Thanks for the input Rasmus. I would like to see all the assertions in one place as well. My current concern is: if a module includes some sub-modules, then when running simulation, we should also include the bind file assertions for the sub-modules. That might be less convenient than directly writing the essential assertions in the RTL code. Wonder what design engineers think about it @msfschaffner @eunchan?

from the designer's point of view, I think we should allow placement of basic assertions directly into RTL (let's call these "embedded SVAs" for now). these are usually assertions that the designer thinks about when writing the RTL, and I find it much more convenient to directly have them co-located with the functionality itself. as an added benefit, these "sanity checks" are always present even without an extra bind file.
there is also a class of assertions like the KNOWN assertions that are usually placed inside each module in order to check its interface/outputs, and I find it convenient to have this in the same file as well.
further, @tjaychen, @eunchan and I will soon present a suggestion for guidance on how to treat X in our code base, and this will likely involve heavy use of embedded KNOWN assertions (also around case statements) which will become very cumbersome if they cannot be directly placed into RTL.
I think of the additional assertions located in a bind file as complementary SVAs assuring coverage closure, and these are then typically written by the DV engineer.

I think of the additional assertions located in a bind file as complementary SVAs assuring coverage closure, and these are then typically written by the DV engineer.

In addition it is common sense to put portable assertion collections in a file, like
what we've done for TLUL. These are useful when binding to more than one design,
so one could make that determination when writing the assertions, as to whether
or not they would be useful elsewhere in the chip.

Thanks everyone for the inputs. Seems like most comments can be summarized as below:

Assertions can be either in RTL file or separate file bound with RTL.
Common shared assertions such as TLUL assertions should be in a separate file and bound with the RTL.
Sanity check assertions (mostly written by the designers) are recommended to write directly in the RTL files.
Assertions written for FPV are recommended to write in a separate file. If sub-modules have separate assertion files, it is recommended to bind them in the top level.
Let me know if anyone has any concerns/add-ons to the summary. If not, I will work on updating the guideline.

SGTM, @cindychip

close as PR #1179 merged


Typing error in C# code

There is a typing error in the C# code that essentially breaks the app if it's not corrected.  In the TryGoBack() method, as typed it currently has a semi-colon immediately after the method parameters, and this needs to be removed for the code to be correct.
`private bool TryGoBack();
{
if (!ContentFrame.CanGoBack)
return false;
// Don't go back if the nav pane is overlayed.
if (NavView.IsPaneOpen &&
    (NavView.DisplayMode == muxc.NavigationViewDisplayMode.Compact ||
     NavView.DisplayMode == muxc.NavigationViewDisplayMode.Minimal))
    return false;

ContentFrame.GoBack();
return true;

}`

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

ID: e69449df-a1ec-70dd-e563-0ad508733c47
Version Independent ID: dc0e0acb-d92a-a039-5c16-f54a4b71d954
Content: Navigation view - UWP applications
Content Source: windows-apps-src/design/controls-and-patterns/navigationview.md
Product: uwp
Technology: design
GitHub Login: @jwmsft
Microsoft Alias: jimwalk

Thanks for letting us know about this error. The code has been corrected.


Connect Mod Platform to Analytical Platform

The Analytical Platform will need to connect to databases within Mod Platform. This will be required by the NOMIS standby database before it can go fully live, so that data can be extracted to AP
Determine path and add relevant routing
Ask Analytical Platform to make the relevant change (e.g. existinghttps://github.com/ministryofjustice/data-engineering-airflow/blob/main/Pulumi.prod.yaml - Connect to previewroutes shown here).  Include the entire Mod Platform range in the cidr blocks <IP_ADDRESS>/16 (nonlive) and <IP_ADDRESS>/16 (live)
Add return path routing to Mod platform (e.g. modernisation-platform/transit_gateway_connections.tf at main · ministryofjustice/modernisation-platform)
DoD:
Routing is agreed
Analytical Platform have ticket to implement their end
Routing tested

This should be covered (for us) by #2199 and #2200 but in case we need something in advance of those, the routes should be:
<IP_ADDRESS>/16

See https://mojdt.slack.com/archives/C013RM6MFFW/p1667293760328399 for context.

Raised PR in airflow repository: https://github.com/ministryofjustice/data-engineering-airflow/pull/91/files

Placed in blocked until PR merged in for airflow

https://asdslack.slack.com/archives/C8X3PP1TN/p1667553580234069 <- referring conversation that shows the PR is due to be completed on Monday

https://github.com/ministryofjustice/data-engineering-airflow/pull/91 <- PR has been merged in!


saleae-logic-2: 2.3.38 -> 2.3.39

Motivation for this change
Changes: https://discuss.saleae.com/t/logic-2-3-39/1235
Things done

Built on platform(s)

[x] x86_64-linux
N/A aarch64-linux
N/A x86_64-darwin
N/A aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Launches on x86_64 NixOS.


[Feature] Add lawbench

Codes in opencompass/datasets/lawbench/evaluation_functions and opencompass/datasets/lawbench/utils are both copied from https://github.com/open-compass/LawBench/tree/main/evaluation


The category should be "build and release"

The category of the extension should be "build and release", so that the extension can be found.

Fixed in version 0.7.2


Periodic boundary conditions: updated

feat: PBC now expects the period as an argument when querying using PBC functions, rather than
storing it in the tree. This prevents the memory layout of the KdTree struct
from changing with the introduction of PBC, which would force existing users to have to
rebuild any serialized trees if they wanted to upgrade.
tests: PBC tests refactored to move common brute force PBC check code and
data/query/tree generating into separate private function
tests: PBC tests use neater float asserts from approx package
tests: Rayon removed and PBC unit test query point and data point count reduced to
improve unit test run time
style: re-ran cargo fmt and cargo clippy and fixed clippy lints that were introduced

Addresses https://github.com/sdd/kiddo/issues/19

Forgot to comment here saying it all looks good to me


Support for Team Foundation Server

Does SQL Operations Studio support source control with Team Foundation Server?

@vinodj thanks for the suggestion!  We're considering including this support in feature release.
By the way, have you tried using the VS Code TFS extension in SQL Ops Studio?  You can get it from https://marketplace.visualstudio.com/items?itemName=ms-vsts.team then click Download Extension to download the VSIX, then click File->Install Extension from VSIX Package to side-load the extension.


[Docs] Write documentation for LoadTextContent and LoadFileAsBase64 functions

Follow-up after #2501 - we need to place on docs.microsoft.com how to use new functions.

@miqm Just FYI, I plan to mention this in the Microsoft Learn content about Bicep too (I already have a draft docs PR to mention it, and will merge it the next release is published).
Let me know if you want any help with docs for this.

Hasn't this been completed in the meantime?
https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-files

Yes, thanks for spotting. Closing then.


Bug: Vertically center icons and names in minimized view

Description
Look at the image below, the names and icons are offset towards the bottom

Steps To Reproduce
1 - set column view
1 - set minimalised view
Requirements

fix Vertically center or increase the space below

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.1702
Log file
debug.log

Hi @yaira2 I would like to work on this issue. Would you please assign it to me?

@sash9696 if possible reduce the space between the elements and the separator line

@redhotideas this issue is resolved in our development branch and will be included in the next release.


/var/lib/dpkg/info/ca-certificates.config: 80: /var/lib/dpkg/info/ca-certificates.config: Cannot fork

Output of docker version:
imiell@rothko:/space/git/shutit/test/3/bin$ docker version
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 21:49:11 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 21:49:11 2016
 OS/Arch:      linux/amd64

Output of docker info:
imiell@rothko:/space/git/shutit/test/3/bin$ docker info
Containers: 34
 Running: 20
 Paused: 0
 Stopped: 14
Images: 107
Server Version: 1.10.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 188
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.0-15-generic
Operating System: Ubuntu 16.04
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 11.44 GiB
Name: rothko
ID: RP4R:37LF:QYXL:Z732:SKYB:DMH7:SXE4:QRPR:7QP6:2NJ3:SW2P:ORFW
Username: imiell
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):
physical
imiell@rothko:/space/git/shutit/test/3/bin$ uname -a
Linux rothko 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Steps to reproduce the issue:

docker run -ti debian bash
apt-get update
apt-get install wget

Describe the results you received:
All normal until:
/var/lib/dpkg/info/ca-certificates.config: 80: /var/lib/dpkg/info/ca-certificates.config: Cannot fork

Describe the results you expected:
Installation of package
Additional information you deem important (e.g. issue happens only occasionally):
Suspect kernel issue - fine on <IP_ADDRESS> Ubuntu

Works in an ubuntu:xenial vm:
ubuntu@ubuntu-xenial:~$ docker version
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.6
 Git commit:   20f81dd
 Built:        Mon, 04 Apr 2016 16:27:28 +1200
 OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
ubuntu@ubuntu-xenial:~$

Re-installing docker.io worked. I must have had an incompatible manually installed one on there.


README.md: updates and improvements

Update listed features to include references to Alertmanager
and Thanos Ruler.
Update Kubernetes version prerequisites
Update wording in various places

Thanks! :) I think we can close this issue now #3153