Assertion failed: org-dartlang-app:///packages/flutter/src/material/checkbox_list_tile.dart:269:15

The following assertion was thrown building StreamBuilder<_AddCardModel>(dirty, state:
js_primitives.dart:29 _StreamBuilderBaseState<_AddCardModel, AsyncSnapshot<_AddCardModel>>#1027a):
js_primitives.dart:29 Assertion failed: org-dartlang-app:///packages/flutter/src/material/checkbox_list_tile.dart:269:15
js_primitives.dart:29 value != null
js_primitives.dart:29 is not true
js_primitives.dart:29
js_primitives.dart:29 Either the assertion indicates an error in the framework itself, or we should provide substantially
js_primitives.dart:29 more information in this error message to help you determine and fix the underlying cause.
js_primitives.dart:29 In either case, please report this assertion by filing a bug on GitHub:
js_primitives.dart:29   https://github.com/flutter/flutter/issues/new?template=BUG.md
js_primitives.dart:29
js_primitives.dart:29 User-created ancestor of the error-causing widget was:
js_primitives.dart:29   _StoreStreamListener<AppState, _AddCardModel>
js_primitives.dart:29   org-dartlang-app:///packages/flutter_redux/flutter_redux.dart:256:12
js_primitives.dart:29
js_primitives.dart:29 When the exception was thrown, this was the stack:
js_primitives.dart:29 package:build_web_compilers/src/dev_compiler/dart_sdk.js 3991:11    throw_
js_primitives.dart:29 package:build_web_compilers/src/dev_compiler/dart_sdk.js 3937:15    assertFailed
js_primitives.dart:29 package:flutter/src/material/checkbox_list_tile.dart 269:24         new
js_primitives.dart:29 package:flutter_stores/ui/shop/store_builder.dart 60:5              getChildrenWidgets
js_primitives.dart:29 package:flutter_stores/ui/shop/store_builder.dart 108:28            <fn>
js_primitives.dart:29 package:flutter_redux/flutter_redux.dart 476:45                     <fn>
js_primitives.dart:29 package:flutter/src/widgets/async.dart 425:74                       build
js_primitives.dart:29 package:flutter/src/widgets/async.dart 125:48                       build
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4040:27                  build
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3934:15                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4081:11                  [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4081:11                  [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4081:11                  [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5129:14                  mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5129:14                  mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5129:14                  mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5129:14                  mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4081:11                  [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4081:11                  [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5129:14                  mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5129:14                  mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4081:11                  [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5129:14                  mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4081:11                  [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3917:5                   [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4081:11                  [_firstBuild]
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3912:5                   mount
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3094:13                  inflateWidget
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2897:12                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4903:32                  updateChildren
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5245:17                  update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/overlay.dart 607:16                     update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4113:5                   update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4247:5                   update
js_primitives.dart:29 package:flutter/src/widgets/inherited_notifier.dart 94:11           update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5136:14                  update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4113:5                   update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5136:14                  update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 5136:14                  update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 4009:5                   update
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2886:14                  updateChild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3954:16                  performRebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 3731:5                   rebuild
js_primitives.dart:29 package:flutter/src/widgets/framework.dart 2341:31                  buildScope
js_primitives.dart:29 package:flutter/src/widgets/binding.dart 775:20                     drawFrame
js_primitives.dart:29 package:flutter/src/rendering/binding.dart 279:5                    [_handlePersistentFrameCallback]
js_primitives.dart:29 package:flutter/src/scheduler/binding.dart 1040:15                  [_invokeFrameCallback]
js_primitives.dart:29 package:flutter/src/scheduler/binding.dart 982:9                    handleDrawFrame
js_primitives.dart:29 package:flutter/src/scheduler/binding.dart 898:5                    [_handleDrawFrame]
js_primitives.dart:29 package:build_web_compilers/src/dev_compiler/dart_sdk.js 153188:23  <fn>

Hello @omontoya !
Thank you for posting a bug report here.
Can you please also provide an additional information such as an output of the flutter doctor -v command and minimal steps to reproduce this issue?
Thank you.

Do not include the required attribute "value". The compiler did not complained.
CheckboxListTile(
key: Key("key${getNextId()}"),
value: false, <---------------- I did not included this value.
title: const Text('Enable'),
onChanged: (bool value) {},
),

@omontoya, based on your comment I think you have things working correctly. If I'm wrong, please feel free to reopen this issue.


Fix bug in jump_to action by adjusting for sample frames

Copy/pasted the utility function, _fix_sample_from_pos, from track_standard.pyx and included it in track_sound_loop.pyx.

Updated logic in def jump_to_time_current_sound_loop_set(..) and other places in
this file where sample frame adjustment is calculated to use this new
utility function.

Add a commented out line that linux users can use for the log file in audio_interface.pyx

Added assertions in test to verify jump_to action.

LGTM!


optimization: cut off file dependencies.

we should avoid code insertion during file dependencies,
such as #include "xxx.h" which has implementations.
This could increase binary size, we can avoid it as possible.
Current patch improves binary size like this:
From: file(2059008) = text(120360) data(8096) bss(80) dec(128536)
To  : file(1921832) = text(118429) data(7872) bss(56) dec(126357)
More additional patches will come in to optmize binary size.

my mistake


WWWD-2734 theming card content

Jira
http://vjira2:8080/browse/WWWD-2734
Summary
Fixes card theming
Details
See the original ticket for a description of the problem.  I don't really understand the fix other than that removing the lines in this PR doesn't seem to affect the end result as far as I can tell.
This definitely needs a review from someone who knows the intention behind those lines (i.e. are they just cruft or actually important?)
How to test
Confirm the problem

Go to https://boltdesignsystem.com/pattern-lab/?p=components-card-band-variation.
In IE 11, use dev tools to add plain text inside the body of the first card inside the dark theme band
Confirm that the text appears white, which is incorrectly matching the theme of the band rather than the card.

Confirm the fix

In IE 11, go to /pattern-lab/?p=components-card-band-variation on this branch
Confirm that the text "Plain text" appears in the correct text color for the theme of the card (dark indigo).

Is that one-off/temporary thing that would get removed once we merge in the card updates?  Or should we be specifying color: bolt-theme(text) on effectively every possible element...

@remydenton
Not one off, that needs to stay. If you look at the floating label and the inputs, they all have color defined, the inline label was an oversight. We should get in the habit of defining colors inside components.

Okay, updated pushed.  I also updated the PL demo, which now looks like this in IE (plain text in card is still wrong, but form label is working):

Additionally:

IMO, It does seem to me like color should cascade-- i.e. if you don't specify color for an element like form label, it should inherit the color of the surrounding text.  I'm trusting @mikemai2awesome on this one, but curious if you agree @sghoweri.
I know we've gone back and fourth on where to put demos like this that are less about showing usage than testing it.  Should these go in card/_tests_ instead?

@remydenton
Can you do a form card demo instead? I don't think we need to showcase the plain text bug in PL.
I also don't like the organization of tests, they shouldn't be mixed together with demos.

Okay, updates do the following:

Clean up form demos (in particular, add number prefixes for better sorting)
Add a demo of a themed band with themed cards to the forms section of pattern lab
Remove the demo of the plain text bug from the card section of pattern lab

I think this should be ready to merge, but I want to add these addenda:

I still think form label (or any other component) should be able to inherit color from the surrounding text if it makes sense to do so.  Mike and I disagree on this and I defer to him, but still curious if you have an opinion @sghoweri.
Not being able to put plain text in a card is a still-unresolved bug.  Ideally, I'd like to see a demo of this alongside the fixes in Mike's card refactor.

@remydenton Looks good. As I mentioned before, the plain text bug is fixed on my refactor branch, when theming is used correctly, this is not an issue. And yes, I think we need a good way to handle inherit colors.

I still think form label (or any other component) should be able to inherit color from the surrounding text if it makes sense to do so. Mike and I disagree on this and I defer to him, but still curious if you have an opinion @sghoweri.

@remydenton @mikemai2awesome inheritance is very tricky in this particular situation.
For browsers with native CSS Custom Properties support it’s not an issue but for those that don’t,it starts to become a terrible game of whack a mole if some other unwanted component’s style’s trump what would otherwise get inherited... (it’s super brittle).
Happy to dive deeper into this with you guys!

Thanks guys!  I'm merging this in since it gets the job done and improves forms.  Looking forward to seeing the full card updates.


net core 3.0 publish project with wrong dependencies

net core 3.0 publish project with wrong dependencies
I have console project ProblemMainApp.
It has dependencies from Helper and Newtonsoft.Json 12.0.2.
Helper.csproj depend from Microsoft.Extensions.Configuration.Json 2.0.1.
Microsoft.Extensions.Configuration.Json 2.0.1 depend from Newtonsoft.Json 10.0.1.

I publish project with command:
dotnet publish -c Debug -f netcoreapp2.0 --force -r centos.7-x64 -o D:\Publish\test
If I have installed netcore 2.* on my comp, that in output folder have Newtonsoft.Json 12.0.2.
But if I have installed netcore 3.* on my comp, that in output folder have Newtonsoft.Json 10.0.1 and program not working. I need to add a reference to Newtonsoft.Json 12.0.2 in Helper.csproj, even though it's not needed.
ProblemMainApp.zip

@jeffschwMSFT

cc @livarcocc

@nguerrera @dsplaisted can one of you take a look?


[Feature] Batch create partitions (supports date and number types)

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
Batch partition creation is supported during and after table creation. Start and end of batch partition can be specified by START and END, and partition increment value can be specified by EVERY clause. The batch partition contains the value of START, but not the value of END. The naming rules for partitions are the same as those for dynamic partitions.
Use case
When the time or number span is large, it is troublesome to manually set each partition.

Related issues
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Can you decribe your demand？I think dynamic partition can satisfy most scenarios.
Historical data from 2019 to now is initialized

see the detail describtion below:
https://docs.starrocks.io/zh-cn/latest/table_design/Data_distribution#批量创建分区

Can you decribe your demand？I think dynamic partition can satisfy most scenarios.
Historical data from 2019 to now is initialized
see the detail describtion below:
https://docs.starrocks.io/zh-cn/latest/table_design/Data_distribution#批量创建分区

Can you decribe your demand？I think dynamic partition can satisfy most scenarios.

see the detail describtion below:
https://docs.starrocks.io/zh-cn/latest/table_design/Data_distribution#批量创建分区


REGR - com.marklogic.client.test.SPARQLManagerTest.testInference test in Java API fails

This is related to Bug Track Issue 35433. This code snippet produces empty results, instead of asserting null.
 gmgr.write("/ontology", new StringHandle(ontology).withMimetype("application/n-triples"));
        SPARQLQueryDefinition qdef = smgr.newQueryDefinition(
                "SELECT ?s { ?s a <http://example.org/C1>  }");
        qdef.setIncludeDefaultRulesets(false);
        StringHandle handle = new StringHandle().withMimetype(SPARQLMimeTypes.SPARQL_CSV);
        String results = smgr.executeSelect(qdef, handle).get();
        assertNull(results);

Sesame and Jena have similar issues with NullPointerException being thrown.
See
https://github.com/marklogic/marklogic-jena/issues/36

I'll take a look, thanks.

Ajit, what is the behavior you're expecting?  I'm thinking if we used to return null (if the snippet above used to work) that was less desirable than returning an empty result set (empty string in this case).

Need to run it through the Semantics QA person to see what their tests are expecting now. I think the old values were (null in this case) incorrect, as per the comments posted on the Bug Track Issue 35433.

I'm just about set to reproduce -- I agree thuough that an empty results is preferable to null.  I'd like to know where we were previously returning null though.

OK, the results did change.  This test now passes:
assertEquals("%0D%0A", URLEncoder.encode(results, "utf8"));
So it's a   CR and LF.    This actually does not parse with the 'parseCsv' method so it may be a [different] bug than before.

It seems that sparql results, even when empty, should have the header row.  I think I can fix this in the REST layer.

Oh.  It occurs to me that, for empty results, we don't have access to the variables for a header row.  So the best we can do in this situation is exactly what we do here.   It's actually not ideal, but still where we are for sparql results until we have truly separate parse/execute steps.

submitted a PR (assigned to @georgeajit ) with a test adjustment for this bug.

Opened bug 38312 to address the issue of header row for CSV, and bindings for XML and JSON query results.

Hi @georgeajit I just pushed changes that modified the test.  Passes in 3.0-develop and develop

The test passes. Verified on today's nightly run.


Optimize absl::StrFormat calls showing up on profiles

construct string for tracing in chttp2_transport only if tracing is enabled
use equivalent absl::StrCat/StrAppend instead of absl::StrFormat/StrJoin for formatting showing up on cpu profiles

It looks like creating trace string even if tracing not enabled was recently introduced in https://github.com/grpc/grpc/pull/32503
@ananda1066 @Vignesh2208

updated based upon iwyu failing check

updated based upon iwyu failing check

I kicked off the CI again.
FYI, for the next time you contribute, we have a helpful bot that fixes many of the sanity checks for you and files a pull request against your branch. You can usually just merge it. https://github.com/scwhittle/grpc/pull/1/files


Saving the encrypted DB inside CouchDB?

I feel like there's a single step from achieving total functionality that would make this plugin amazing.
Is there a way of saving the DB inside the docker container, and encrypting it? I've tried adding the following lines in my compose file, but couchdb doesn't seem to like it and won't start.
volumes:
  db:
... SNIP ...
  volumes:
    - db:/var/lib/couchdb

That way we could have live sync on all enrolled devices, while the DB (vault) would be safe and sound, encrypted on a remote server.
From my understanding the docker container currently doesn't save anything to disk, and is basically just used for it's processing power to help obsidian clients talk to each other.

Hi,
I am not the dev and do not know of any way to encrypt the Docker volume, but I wanted to ask – Wouldn't End 2 End Encryption (E2EE) fix the problem for you? That way, your notes should be only decrypted on your devices with Obsidian.

Thanks @vactomas,
Perhaps I didn't explain what I wanted properly.
I did see that E2EE is available, but I'm not sure how to encrypt the vault I'm using and keep it at a centralized location.
From my understanding if I simply enable E2EE, I have absolutely no idea what happens, does the vault that's already on my SMB server get encrypted, or does only the local copy get encrypted or is there a third chain of events?

@rwjack
Thank you for asking me. (and, thanks @vactomas)
The mounting volume is like this:
https://github.com/vrtmrz/self-hosted-livesync-server/blob/dbf28eaffc07592d742be2a1fc00891ee9cdf65c/docker-compose.yml#L33
As @vactomas says, If you enable E2EE, the plugin sends all notes with encrypting and receives with decrypting automatically. All your note's bodies in the remote server should be encrypted with AES-GCM.

That way we could have live sync on all enrolled devices, while the DB (vault) would be safe and sound, encrypted on a remote server.

This is not enough. If we have to keep it secure, we should not send any data without encryption. So, we have to encrypt within our device or while transferring.

From my understanding the docker container currently doesn't save anything to disk, and is basically just used for it's processing power to help obsidian clients talk to each other.

If you like, you can use this.
Does this answer the question?

As @vactomas says, If you enable E2EE, the plugin sends all notes with encrypting and receives with decrypting automatically. All your note's bodies in the remote server should be encrypted with AES-GCM.

So I'm supposed to encrypt my notes manually? Did I get this right?
For now I just activated E2EE on my desktop, added a password and hit apply & send.
On my phone I did the same, but instead of apply & send, I did just apply.
I still see the notes in plaintext on my SMB server, which is also hosting the couchDB instance.

If you like, you can use this.

I already have a reverse proxy, SSL and everything set up. I'm just trying to understand the functionality of the plugin.
Have you heard of joplin? I used it before and it has the same functionality I'm trying to describe. All notes stay on a centralized location, other devices can point at the URL of the server and use a decryption passphrase to decrypt the notes locally.

Joplin indeed uses E2EE. Basically, E2EE encrypts the notes on your devices, and they stay encrypted until another client (Obsidian instance with plugin) with a password decrypts them. They are encrypted during transport and when they are stored.
This is at least how E2EE works. I am not sure how it is implemented here, as I currently am unable to test it due to issues with my CouchDB instance.

I think I read somewhere, that due to new API, it has problems with mobile and Live sync. People have suggested using sync on save instead.

Thanks @vactomas, that fixed some issues.
I completely disabled saving the DB in docker, but now I'm having problems on my laptop. Inspector says it's an invalid CA. Obviously because it's my internal self-signed CA, which is already in my debian based system ca-certificate list. Quite strange that this works on both my phone and desktop, but not the laptop. It would really be easier if we had an option to ignore self signed CA errors.

Do you have it hosted on a domain? If so, use Let's encrypt to get a free certificate. I believe, it is mentioned in docs, that self-signed certificates might pose issues.

What is your exact issue with Docker? I do have an issue as well, but it is probably not related.

That is weird. Could you post here the whole docker-compose file, with sensitive information, such as DB password, censored?

@rwjack

So I'm supposed to encrypt my notes manually?

No, all process will be done automatically.
Your files will be stored in plain text on your device storage as same as it has been so. But, it is encrypted in the server.
You can see how are they stored by CouchDB’s admin tool. Open the URI which inserted _utils/#database/ before the DB name (i.e. example.net/obsidiandb -> example.net/_utils/#database/obsidiandb/)

Have you heard of joplin?

Yes! I had been one of the users.  I guessed that you might wonder if your files are still plain text. It is right. But everything gets done till sent to the remote server.
A self-signed certificate will be ignored even though the device trusted it.  especially in mobile, we can’t solve that.

@rwjack Could you check permissions and owners of /opt/couchdb/ and its children?
CouchDB uses a user that has id:5986 even if it is inside the container.
Perhaps we have to fix this mismatch.

Close this issue once. Feel free to open it again if you have new something.


[SPARK-33281][SQL] Return SQL schema instead of Catalog string from the SchemaOfCsv expression

What changes were proposed in this pull request?
Return schema in SQL format instead of Catalog string from the SchemaOfCsv expression.
Why are the changes needed?
To unify output of the schema_of_json() and schema_of_csv().
Does this PR introduce any user-facing change?
Yes, they can but schema_of_csv() is usually used in combination with from_csv(), so, the format of schema shouldn't be much matter.
Before:
> SELECT schema_of_csv('1,abc');
  struct<_c0:int,_c1:string>

After:
> SELECT schema_of_csv('1,abc');
  STRUCT<`_c0`: INT, `_c1`: STRING>

How was this patch tested?
By existing test suites CsvFunctionsSuite and CsvExpressionsSuite.

Test build #130398 has started for PR 30180 at commit cb1215a.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35000/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35002/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35000/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35000/
Test PASSed.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35002/

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35002/
Test FAILed.

Test build #130398 has finished for PR 30180 at commit cb1215a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130398/
Test PASSed.

Merged to master.


join should ignore empty Sql

Currently join([empty(), empty(), empty()]) results in ,,. I think it would make more sense and would be more useful if join would skip empty statements.
Eg:
join([
  filterByFirstName ? sql`first_name LIKE ${firstName}` : empty(),
  filterByLastName ?  sql`last_name LIKE ${lastName}` : empty(),
  ],
  " AND "
);

It's not a bad idea, but the performance implications for doing a filter every join instead of you just checking for it yourself doesn't seem worth it right now. For example, you can just do this:
join([
  filterByFirstName ? sql`first_name LIKE ${firstName}` : null,
  filterByLastName ?  sql`last_name LIKE ${lastName}` : null,
  ].filter(Boolean),
  " AND "
);

If it's within the library I basically need to add that .filter to every join attempt because I use the array length to compute the number of commas to repeat.

Another gotcha for adding this is that join([]) throws an error today. What would join([empty]) do? It seems odd and hard to debug that [empty, empty] would throw an error while the other 3 combinations would not.

isEmpty utility (strings.length === 1 && strings[0].length === 0) would be appreciated maybe.

Sure, I can accept a PR for this.
I still think clearly indicating an undefined or null value is going to make your life simpler in the long run, and it's easier for other engineers to understand the intent, but I think it's good to keep that outside the library.


server: remove "experimental" label from OIDC settings

https://github.com/cockroachdb/cockroach/pull/71183 --- Release note (api change): OIDC support for DB Console is no longer marked as "experimental"

Got it I see, sorry I misinterpreted your message.
So according to this thread https://github.com/cockroachdb/cockroach/pull/71183#issuecomment-935038288 we're just removing the "experimental" callouts in https://www.cockroachlabs.com/docs/v21.2/sso.html
cc @taroface if there's another area that's come up in docs that needs this change


Questions about benchmark codes in ceno_zkvm

Hello Ceno team. I am a master student at Waseda University and a PSE grantee.
I am currently doing research on zkVM on my own, working on parallel Jolt implementation and benchmarking each zkVM method. My benchmarking repository can be found here.
https://github.com/grandchildrice/zkvm-benchmarks
So I have a few questions about the current implementation of Ceno.
Q1. Which Rust code is compiled and used in the Fibonacci benchmark?
I would like to run it with 50500000 in max_steps (which is equivalent to 1M-th fibonacci in RISC Zero). So I want to make sure that all of those max_steps are really executed.
In addition, I would like to compile the following Rust code that performs matrix operations into ELF and benchmark it as well. I want to do this because I want to compare it against a memory-intensive program. I know that generating proofs for this program in Nexus or Jolt is obviously very time consuming compared to Fibonacci.
fn matrix_ops(n: usize) -> u64 {
    let matrix_a: Vec<Vec<f32>> = (0..n)
        .map(|i| (0..n).map(|j| (i + j) as f32).collect())
        .collect();

    let matrix_b: Vec<Vec<f32>> = (0..n)
        .map(|i| (0..n).map(|j| (i * j) as f32).collect())
        .collect();

    let mut result = vec![vec![0f32; n]; n];

    for i in 0..n {
        for j in 0..n {
            for k in 0..n {
                result[i][j] += matrix_a[i][k] * matrix_b[k][j];
            }
        }
    }

    result[0][0] as u64
}

Q2. Is proof aggregation already implemented in Ceno?
As the size of opcode_proof seemed to increase with the number of cycles. I would like to include the time up to proof aggregation to make a fair comparison with other methods.

Hi,
Ceno team still working on build fibonacci elf via other zkVM toolchain for upcoming apple-to-apple benchmarks with other zkVM as well. So for current repo there is no fibonacci guest program yet.
But there are some existing guest program, although I haven't fully verified all the flow, just shared wish it helpful.

guest program
you can try to put your guest program under examples
and register here for it to be build
https://github.com/scroll-tech/ceno/blob/master/examples-builder/build.rs#L11-L21

test generating witness on host: this flow just verify elf format, load into emulator and execute. it doesn't cover real prove
for example, https://github.com/scroll-tech/ceno/blob/master/ceno_host/tests/test_elf.rs#L129-L140

e2e integration
to load elf + run the execution e2e, you can refer to these command https://github.com/scroll-tech/ceno/blob/master/.github/workflows/integration.yml#L60. But currently the toolchain still under development, so I would say its not stable and ready for benchmark yet.

Feel free to give it a try!

Thank you! I'll try them!


Drop python 3.7 and install fs-azureblob

Pull Request doc
Purpose
Install the fs-azureblob package for future use and drop support for python 3.7.
Where to look
Take a look at the package updates in Pipfile.lock, since regenerating the file pulled in new versions of other packages as well (including pandas).
Time estimate
5 min

Pandas 1.3.3 vs. 1.3.5 shouldn't make too much of a difference I think. It's great that we're not on 1.1.x in PowerSimData, we should definitely upgrade across the other repos as well.
Should we also test against Python 3.10?


cmsis_update::update()

Hi!
Is there a reason that cmsis_update::install() for example requires some type with a trait implemented to be passed into it just to configure it and get some progress update?
Why can't this be fixed? Is it because of the python interface? Even then I think this can be implemented with a less complicated interface which I'd highly prefer.
Also, is there a reason you force users to use slog or did you just not care enough? Because I don't want to use slog but I now have to include the dependency anyways. And exactly for this scenario there is https://docs.rs/log/0.4.8/log/ which provides a nice and unified frontend for maaaany different backends (slogbeing one of them).
I know this crate was maybe not written with intent to be reused as a lib, so don't take my criticism too harsh, I just wanted to ask and would make those improvements in a PR if that's ok =)
Best,
Yatekii

some type with a trait implemented to be passed into it just to configure it and get some progress update?

There is probably a better way to do this. I'm open to suggestions and PRs for simpler interfaces. Originally it was to allow the python interface to handle the messages differently than the CLI.

Is there a reason you force users to use slog or did you just not care enough?

I don't think slog is needed at this point. I must have had a reason for adding it, but that reason is probably no longer applicable. I think it would be some work to pull out the usage of slog.

I just wanted to ask and would make those improvements in a PR if that's ok =)

I would love to see these improvements. Feel free to submit PRs.


No output on debug console with Print, but Echo doesn't have this problem.

Evaluate in debug console within vscode via lsp-wl:

In MMA notebook:

Why?
Regards,
HY

The same issue as #57 , it is unknown to me how to redirect stdout from another kernel. You should see it printed in the log panel.

Duplicate of #57


feat(atomic,headless): added atomic-smart-snippet-suggestions

https://coveord.atlassian.net/browse/KIT-1489
Missing:

Show more / Show less (& analytics)
Analytics when clicking on the source
A unique ID for related questions

Currently, the "atlas data lake" query returns multiple related questions that each have a different question/answer but share the same source. The expand/collapse headless action takes the source as a parameter, meaning that we can only expand/collapse all of them at once.
The ID could be exposed and used as a key in JSX frameworks

Analytics when expanding/collapsing a related question

Live demo: https://staticdev.cloud.coveo.com/atomic/pr/KIT-1489-storybook/index.html?path=/story/atomic-smart-snippet-suggestions--default-smart-snippet-suggestions

Small note, related to ShowMore ShowLess arrow, can you adjust the alignment of the icons?


Add script for for finetuning a code llm

What does this PR do?
This PR provides basic support for finetuning a code LLM. It is adapted from the following source: https://huggingface.co/learn/cookbook/en/fine_tuning_code_llm_on_single_gpu
NOTE: we still need to add appropriate eval metrics (of which there aren't very many standard ones for finetuning code llms)

Also, it seems like my fix for the github action didn't work.


disable_jit extensions to control flow constructs break with vmap

The extension of jax.disable_jit() context to the control flow elements (e.g. while_loop, cond) isn't correct in the presence of batch tracers for vmap.   while_loop and cond are rewritten to use python control flow under this context, but conditional branching can't be evaluated on the batchtracers present when functions using these control flow constructs are inside a vmap.
e.g.
def trivial_while(y):
  return lax.while_loop(lambda x: x < 10.0, lambda x: x + 1.0, y)
# works:
jax.vmap(trivial_while)(jnp.array([3.0,4.0]))
# throws a ConcretizationTypeError:
with jax.disable_jit():
  jax.vmap(trivial_while)(jnp.array([3.0,4.0]))

likewise:
def trivial_cond(x):
  return lax.cond(x < 1.0, x, lambda x: x, x, lambda x: 2*x)
# works
jax.vmap(trivial_cond)(jnp.array([0.5,2.0]))
# throws a ConcretizationTypeError:
with jax.disable_jit():
  jax.vmap(trivial_cond)(jnp.array([0.5,2.0]))

Perhaps the disabled_jit python implementations for these control flow constructs could peak at the tracer value's val field which I suspect will be populated in these use-cases?

#2598 is possibly related? In particular commenting out these lines might fix it?


How do I specify the server URL in openapi.json?

https://cloudflare.github.io/itty-router-openapi/user-guide/router-options/
I thought OpenAPIRouter supports specifying the server URL so that the generated openapi.json will have the server URL info, but I can't find the option in the doc linked above. Is this feature supported?

Hey @tddschn you can pass all supported openapi properties inside the schema property of the router, here's an example for defining servers:
const router = OpenAPIRouter({
  schema: {
    servers: [{
      url: 'https://api.example.com/v1',
      description: 'example',
    }],
  },
})


'Something went wrong installing the "sharp" module'

What is the output of running npx envinfo --binaries --languages --system --utilities?
System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Memory: 6.02 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.3.1 - /usr/local/bin/node
Yarn: 1.16.0 - ~/Documents/GitHub/mBakeCLI/src/node_modules/.bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Utilities:
Make: 3.81 - /usr/bin/make
GCC: 4.2.1 - /usr/bin/gcc
Git: 2.21.0 - /usr/bin/git
Languages:
Bash: 3.2.57 - /bin/bash
Perl: 5.18.4 - /usr/bin/perl
PHP: 7.1.23 - /usr/bin/php
Python: 2.7.10 - /usr/bin/python
Ruby: 2.3.7 - /usr/bin/ruby
What are the steps to reproduce?
yarn add sharp
npm publish
What is the expected behaviour?
I can deploy my npm package to npm.js
Are you able to provide a standalone code sample, without other dependencies, that demonstrates this problem?
If it helps.
Are you able to provide a sample image that helps explain the problem?
I don't understand the question.
But let me tell you the error, my project ( https://github.com/metabake/mBakeCli ) uses sharp.
Today, when I publish my project I get an error:
Something went wrong installing the "sharp" module
dlopen(/Users/code/.config/yarn/global/node_modules/sharp/build/Release/sharp.node, 1): Library not loaded: @rpath/libvips-cpp.dylib
Referenced from: /Users/code/.config/yarn/global/node_modules/sharp/build/Release/sharp.node
Reason: image not found

Remove the "node_modules/sharp" directory, run "npm install" and look for errors
Consult the installation documentation at https://sharp.pixelplumbing.com/en/stable/install/
Search for this error at https://github.com/lovell/sharp/issues

I moved the code out of my main package to here:
https://github.com/metabake/mbakeAdvanced/tree/master/mbakeX
and then had to comment out sharp code. Same error
dlopen(/Users/code/.config/yarn/global/node_modules/sharp/build/Release/sharp.node, 1): Library not loaded: @rpath/libvips-cpp.dylib
Referenced from: /Users/code/.config/yarn/global/node_modules/sharp/build/Release/sharp.node
Reason: image not found

Hi, it looks like you might be using a globally-installed sharp rather than one stored locally in your project's node_modules directory. Perhaps there's a corruption or conflict between two different versions?
Try running yarn global remove sharp then yarn install in your project directory.

I am using global.
I tried to remove sharp and remove my module globally as you suggested.
And then rebuild, reinstall: and I get the same error.  It says the image is not found for rpath/libvips, is that some dependency of yours or your code?

If you get the same error, namely one with the path /Users/code/.config/yarn/global/node_modules/sharp/build/Release/sharp.node, then sharp probably hasn't been globally removed yet.
Does the file referenced still exist? What happens if you delete /Users/code/.config/yarn/global/node_modules/sharp? Could another globally-installed module depend on (a different version of) sharp?

This worked, I think:
yarn cache clean
yarn upgrade
But I am concerned about downstream users of my package.
Since I don't know who they all are. I can't tell all of them to do  yarn cache clean, yarn upgrade.
(One silly solution is that you bump the versions of your package more often, even w/ no changes, I know it is silly)
Also I don't think it is a different version of your package since your packages is ~ month old, and all my work was in last few days.

Glad you got it working.
I'm always concerned about downstream users of sharp, of which there are many, and luckily the problem you ran into is uncommon.
If you and your downstream users are able to avoid the need to globally-install sharp then this will avoid a whole class of possible problems.

Thanks. Unfortunately my package is global and I use sharp.

For CLI tooling I usually advise the use of either npx or yarn dlx. Both download each package version only once and cache so are as performant as installing globally but more importantly avoid making those packages available globally.

Oh... good trick!


SNI-based routing without TLS termination not working

Title: SNI-based routing without TLS termination
Description:
Based on the attached configuration, I'd expect the following to happen.
Case 1: A Client Hello with the right SNI (httpbin) is sent to Envoy. Envoy forwards it to the upstream cluster so that the Client and Cluster can do the TLS handshake.
Case 2: A Client Hello without the right SNI (httpbin) is sent to Envoy. Envoy finds no matching filters, and closes the connection.
What I actually see is that Envoy will forward the Client Hello to the Cluster in Case 2, even through the SNI is wrong.
Repro steps:
Run Envoy using the provided config.
docker run --rm -it -v $(pwd)/envoy-custom2.yaml:/envoy-custom2.yaml -p 9901:9901 -p 10000:10000 envoyproxy/envoy:dev-1cc4b96293c50eb595f5bd268cb9f6dd11217104     -c /envoy-custom2.yaml
Send a request to Envoy using the following:
Case 1: curl --connect-to httpbin.org:10000:localhost:10000 --insecure https://httpbin.org:10000/anything
Case 2: curl --insecure https://localhost:10000/anything
The first curl command generates a Client Hello with httpbin in the SNI. You should get a response. The second one command should result in a closed connection, but instead passes.
Admin and Stats Output:
server_info.txt
routes.txt
clusters.txt
stats.txt
Config:
admin:
  address:
    socket_address:
      protocol: TCP
      address: <IP_ADDRESS>
      port_value: 9901
static_resources:
  # Downstream configurations
  listeners:
  - name: listener_0
    address:
      socket_address:
        protocol: TCP
        address: <IP_ADDRESS>
        port_value: 10000
    listener_filters:
    - name: tls_inspector
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.filters.listener.tls_inspector.v3.TlsInspector
    #Start network filters
    filter_chains:
    #Start filter for httpbin
    - filter_chain_match:
        server_names: ["httpbin"]
        #- httpbin
    - filters:
      - name: envoy.filters.network.tcp_proxy
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy
          cluster: route_to_httpbin
          stat_prefix: https_passthrough

  # Upsteam Configurations
  clusters:
  - name: route_to_httpbin
    type: LOGICAL_DNS
    # Comment out the following line to test on v6 networks
    dns_lookup_family: V4_ONLY
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: route_to_httpbin
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: httpbin.org
                port_value: 443

Logs:

Include the access logs and the Envoy logs.

Couldn't find how to get these. Please let me know and I'll be happy to attach them.
Call Stack:
N/A

Logs:

Include the access logs and the Envoy logs.

Couldn't find how to get these. Please let me know and I'll be happy to attach them.

You can try to add--log-level debug and --log-path /var/log/envoy/envoy.log in the docker command, and you can also add volume mount with -v /path/to/local/logs:/var/log/envoy to link you local folder for the system logs.

I think this is a config issue:
From your stats:
listener.<IP_ADDRESS>_10000.no_filter_chain_match: 0
Pointer to where the close should occur if there's no match:
https://github.com/envoyproxy/envoy/blob/628a5b997ef36fe2b76624797a693970461a637a/source/extensions/listener_managers/listener_manager/active_stream_listener_base.cc#L46
which should close the connection

I think this is a config issue:
From your stats:
listener.<IP_ADDRESS>_10000.no_filter_chain_match: 0

Right, it seems that this filter_chain_match in the config isn't being honored by Envoy.
- filter_chain_match:
        server_names: ["httpbin"]

Causing Client Hellos with any SNI to be forwarded to the cluster, instead of just the ones with "httpbin"


Find a way to condense save files, primarily history/records/stmts

One solution could be to only store the record file when it changes. This would mean that we couldn't story records independently, only the entire history.


D0447R20 currently says (with one wording nit):

Effects: Returns an iterator or const_iterator pointing to the same element as the pointer or const_pointer. If p does not point to an element in *this, the past-the-end iterator is returned.

Now, our p certainly doesn't point to an element in *this — but, it's also been invalidated by the erase. So is it supposed to be a valid argument for get_iterator? What kinds of pointers are valid arguments for get_iterator? Could I pass a null pointer, for example?
plf::hive's implementation of get_iterator relies on comparing pointers into arbitrary objects as if the memory address space on the target machine were flat, i.e. p < q < r implies that q is necessarily a member of the same object as p and r. In general, C++ does not guarantee this: comparing pointers into arbitrary objects is UB, and comparing them with std::less<void*> is not UB but also isn't guaranteed to give you the answer you're looking for (because C++ allows pointer representations to be interleaved). Therefore, I believe get_iterator is unimplementable on a sufficiently hostile conforming implementation. Check with someone like @jwakely for absolute certainty, though.
(Oh yeah, and remember this all has to work for arbitrary user-defined fancy-pointer types too!)
Basically there are two prongs to this bug report:
(1) The p < q < r implementation approach involves UB; get_iterator is basically unimplementable in theory; I suggest get_iterator be struck from P0447 entirely.
(2) plf::hive's own implementation of get_iterator, given a pointer to a previously valid element, will sometimes return a garbage iterator instead of h.end(); I call this a bug, or at least undesirable, and I wonder what you think about it.

std::less<T*> should work, that's required to be a total order.

@jwakely: My understanding of the rules-as-written is that it works like this:
int a[2];
int b;
auto LT = std::less<int*>{};
assert(LT(&a[0], &a[1]));  // guaranteed
assert(LT(&a[0], &b) != LT(&b, &a[0]));  // one or the other must be true
assert(LT(&a[1], &b) != LT(&b, &a[1]));  // one or the other must be true

but that it is perfectly legal for an exotic implementation (maybe one that stores "segment" bits in the low-order bits of a pointer instead of the high-order bits) to produce an assertion failure for
assert(LT(&a[0], &b) == LT(&a[1], &b));  // NOT guaranteed, as I understand it
assert(LT(&a[0], &b) != LT(&b, &a[1]));  // NOT guaranteed, as I understand it

That is, as I understand it, the partial order imposed by operator< ensures that a < a+1, and the total order imposed by LT is consistent with the partial order, but nothing forbids an exotic implementation from claiming that LT(a, &b) && LT(&b, a+1). (This is the question I was hoping you'd either agree with, or lay to rest.) On such an implementation, plf::hive's pointer-comparison-based get_iterator would produce wrong answers.
On such an exotic implementation, iterating by incrementation from &arr[0] up to &arr[9] is still guaranteed to take 9 steps and touch all 10 elements of arr; but that doesn't mean there aren't other unrelated objects hiding "between" arr's objects from the point of view of LT's total order.

On 29/04/2022 6:43 am, Quuxplusone wrote:

(1) The |p < q < r| implementation approach involves UB; |get_iterator|
is basically unimplementable in theory; I suggest |get_iterator| be
struck from P0447 entirely.
(2) |plf::hive|'s own implementation of |get_iterator|, given a pointer
to a previously valid element, will sometimes return a garbage iterator
instead of |h.end()|; I call this a bug, or at least undesirable, and I
wonder what you think about it.

I don't see how 1 makes sense and would still support C-style arrays but
you can talk about it with Jonathan if you like. I don't think the
standard library would be implementable in such an environment.
2 is a bug and thank you for finding it - it's a hangover from the HCJC
skipfield which didn't allow zero middle nodes in skipblocks. The LCJC
does, but this is easily fixed using the criteria in the LCJC paper
under "7.2 Parallel Processing" and I have fixed this in the beta.
This info and the tech spec correction you've identified will be added
to paper.

The issue is that the implementation-defined total pointer order is not required to correspond with pointer arithmetic: there can exist q such that p<q (in that order, not C++'s p<q) and q<p+1.  There's nothing in the standard library that could detect such an (admittedly bizarre) implementation choice, because it never uses that total pointer order for anything that also cares about arrays.

Jonathan's said that std::less should work, so I'll just switch to using
those.
On 4/05/2022 5:53 am, Davis Herring wrote:

The issue is that the implementation-defined total pointer order is not
required to correspond with pointer arithmetic: there can exist /q/ such
that /p/</q/ (in that order, not C++'s |p<q|) and /q/<|p+1|. There's
nothing in the standard library that could detect such an (admittedly
bizarre) implementation choice, because it never uses that total pointer
order for anything that also cares about arrays.
—
Reply to this email directly, view it on GitHub
https://github.com/mattreecebentley/plf_hive/issues/18#issuecomment-1116382136,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABE4FIUIURJLWKZEN3B5VVDVIFRZBANCNFSM5UTMY4OQ.
You are receiving this because you commented.Message ID:
@.***>

In practice on current implementations, yes, but not portably guaranteed by the standard, for the reasons given by Arthur and Davis.
Last time we tried to remove the allowance for weird, unordered address spaces there was strong opposition.

Closed as per LEWG discussion


Doubts in Netopeer2-cli Listen command

when I used to put Listen --login tester ,the connection was not established but i can able to connect using normal connect command . I'm unable to figure out the issue but there is no issues with connectivity,firewall and port . So need help in sorting out this issue!
tester@tester-pc:~$ netopeer2-cli
load_config: No saved configuration.

listen --login tester
Waiting 60s for an SSH Call Home connection on port 4334...
cmd_listen: Receiving SSH Call Home on port 4334 as user "tester" timeout elapsed.

this is the respective log captured during the process ,
May 16 12:17:54  netopeer2-server[1412]: Accepted a connection on <IP_ADDRESS>:830 from <IP_ADDRESS>:35834.
May 16 12:17:54  netopeer2-server[1412]: [INF]: LN: Accepted a connection on <IP_ADDRESS>:830 from <IP_ADDRESS>:35834.
May 16 12:17:54  netopeer2-server[1412]: [INF]: SR: Session 41 (user "tester", CID 1) created.
May 16 12:17:54  netopeer2-server[1412]: Session 41 (user "tester", CID 1) created.
May 16 12:17:54  netopeer2-server[1412]: [2024/05/16 12:17:54.300724, 1] ssh_server_connection_callback:  SSH client banner: SSH-2.0-libssh_0.8.6
May 16 12:17:54  netopeer2-server[1412]: [2024/05/16 12:17:54.300769, 1] ssh_analyze_banner:  Analyzing banner: SSH-2.0-libssh_0.8.6
May 16 12:17:54  netopeer2-server[1412]: [2024/05/16 12:17:54.335059, 1] ssh_packet_socket_callback:  read_packet(): Packet len too high(1180448200 465c35c8)
May 16 12:17:54  netopeer2-server[1412]: [ERR]: LN: SSH key exchange error (read_packet(): Packet len too high(1180448200 465c35c8)).
May 16 12:17:54  netopeer2-server[1412]: SSH key exchange error (read_packet(): Packet len too high(1180448200 465c35c8)).

Nothing I can help with, obviously a libssh issue. And you must be using an old libnetconf2 version if you could compile it with libssh 0.8.6, currently the oldest supported version is 0.9.5 so if you updated it, it should work.

Thanks Michal but the issue is I'm unable to install the latest libssh due to compiling issue regarding openssl fips . I have checked with latest openssl 3 version and also along with it I have installed the fips module (openssl-fips-2.0.16) but still I'm encountering the issue in compiling libssh,
/home/tester/netopeer/latest_netopeer2/libssh-0.9.5/src/kex.c: In function ‘ssh_client_select_hostkeys’:
/home/tester/netopeer/latest_netopeer2/libssh-0.9.5/include/libssh/libcrypto.h:116:26: error: implicit declaration of function ‘FIPS_mode’ [-Werror=implicit-function-declaration]
116 | #define ssh_fips_mode() (FIPS_mode() != 0)
|                          ^~~~~~~~~
/home/tester/netopeer/latest_netopeer2/libssh-0.9.5/src/kex.c:583:13: note: in expansion of macro ‘ssh_fips_mode’
583 |         if (ssh_fips_mode()) {
|             ^~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [src/CMakeFiles/ssh.dir/build.make:300: src/CMakeFiles/ssh.dir/kex.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:399: src/CMakeFiles/ssh.dir/all] Error 2
openssl version
OpenSSL 3.0.0 7 sep 2021 (Library: OpenSSL 3.0.0 7 sep 2021)
built on: Thu May 16 09:17:45 2024 UTC
platform: linux-x86_64
options:  bn(64,64)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG
OPENSSLDIR: "/usr/local/ssl"
ENGINESDIR: "/usr/local/lib64/engines-3"
MODULESDIR: "/usr/local/lib64/ossl-modules"
Seeding source: os-specific
CPUINFO: OPENSSL_ia32cap=0x7ffaf3bfffebffff:0x18c05fdef3bfa7eb

Ask libssh for support, I really cannot help you with this. However, it seems you have a rather constrained environment and we have recently added support for compiling libnetconf2 with MbedTLS, libssh can be compiled with that as well, so maybe you do not want to use OpenSSL. But if you do, I would try using a newer version than 3.0.0, not sure why you have not picked the latest libssh and OpenSSL versions.


add ghost v2 docker images

closes #142
Main difference from ghost v1 is that knex-migrator is no longer needed outside of Ghost - Ghost itself will run it on boot.

Here's a slightly better diff: (since GitHub doesn't support --find-copies-harder through the web interface)
diff --git a/.travis.yml b/.travis.yml
index ac01164..31869e1 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -2,6 +2,8 @@ language: bash
 services: docker

 env:
+  - VERSION=2 VARIANT=debian
+  - VERSION=2 VARIANT=alpine
   - VERSION=1 VARIANT=debian
   - VERSION=1 VARIANT=alpine
   - VERSION=0 VARIANT=debian
diff --git a/1/alpine/Dockerfile b/2/alpine/Dockerfile
similarity index 77%
copy from 1/alpine/Dockerfile
copy to 2/alpine/Dockerfile
index 847add9..1fc8a6c 100644
--- a/1/alpine/Dockerfile
+++ b/2/alpine/Dockerfile
@@ -17,7 +17,7 @@ RUN npm install -g "ghost-cli@$GHOST_CLI_VERSION"
 ENV GHOST_INSTALL /var/lib/ghost
 ENV GHOST_CONTENT /var/lib/ghost/content

-ENV GHOST_VERSION 1.25.5
+ENV GHOST_VERSION 2.0.3

 RUN set -ex; \
 	mkdir -p "$GHOST_INSTALL"; \
@@ -37,14 +37,7 @@ RUN set -ex; \
 # need to save initial content for pre-seeding empty volumes
 	mv "$GHOST_CONTENT" "$GHOST_INSTALL/content.orig"; \
 	mkdir -p "$GHOST_CONTENT"; \
-	chown node:node "$GHOST_CONTENT"; \
-	\
-# sanity check to ensure knex-migrator was installed
-	"$GHOST_INSTALL/current/node_modules/knex-migrator/bin/knex-migrator" --version
-
-# add knex-migrator bins into PATH
-# we want these from the context of Ghost's "node_modules" directory (instead of doing "npm install -g knex-migrator") so they can share the DB driver modules
-ENV PATH $PATH:$GHOST_INSTALL/current/node_modules/knex-migrator/bin
+	chown node:node "$GHOST_CONTENT"

 # TODO multiarch sqlite3 (once either "node:6-alpine" has multiarch or we switch to a base that does)

diff --git a/1/alpine/docker-entrypoint.sh b/2/alpine/docker-entrypoint.sh
similarity index 89%
copy from 1/alpine/docker-entrypoint.sh
copy to 2/alpine/docker-entrypoint.sh
index 21eee25..bedd4fa 100755
--- a/1/alpine/docker-entrypoint.sh
+++ b/2/alpine/docker-entrypoint.sh
@@ -17,8 +17,6 @@ if [[ "$*" == node*current/index.js* ]]; then
 			tar -cC "$(dirname "$src")" "$(basename "$src")" | tar -xC "$(dirname "$target")"
 		fi
 	done
-
-	knex-migrator-migrate --init --mgpath "$GHOST_INSTALL/current"
 fi

 exec "$@"
diff --git a/1/debian/Dockerfile b/2/debian/Dockerfile
similarity index 87%
copy from 1/debian/Dockerfile
copy to 2/debian/Dockerfile
index a834190..8c8e63a 100644
--- a/1/debian/Dockerfile
+++ b/2/debian/Dockerfile
@@ -23,7 +23,7 @@ RUN npm install -g "ghost-cli@$GHOST_CLI_VERSION"
 ENV GHOST_INSTALL /var/lib/ghost
 ENV GHOST_CONTENT /var/lib/ghost/content

-ENV GHOST_VERSION 1.25.5
+ENV GHOST_VERSION 2.0.3

 RUN set -ex; \
 	mkdir -p "$GHOST_INSTALL"; \
@@ -43,14 +43,7 @@ RUN set -ex; \
 # need to save initial content for pre-seeding empty volumes
 	mv "$GHOST_CONTENT" "$GHOST_INSTALL/content.orig"; \
 	mkdir -p "$GHOST_CONTENT"; \
-	chown node:node "$GHOST_CONTENT"; \
-	\
-# sanity check to ensure knex-migrator was installed
-	"$GHOST_INSTALL/current/node_modules/knex-migrator/bin/knex-migrator" --version
-
-# add knex-migrator bins into PATH
-# we want these from the context of Ghost's "node_modules" directory (instead of doing "npm install -g knex-migrator") so they can share the DB driver modules
-ENV PATH $PATH:$GHOST_INSTALL/current/node_modules/knex-migrator/bin
+	chown node:node "$GHOST_CONTENT"

 RUN set -eux; \
 # force install "sqlite3" manually since it's an optional dependency of "ghost"
diff --git a/1/debian/docker-entrypoint.sh b/2/debian/docker-entrypoint.sh
similarity index 89%
copy from 1/debian/docker-entrypoint.sh
copy to 2/debian/docker-entrypoint.sh
index 1060b05..c7bfbe3 100755
--- a/1/debian/docker-entrypoint.sh
+++ b/2/debian/docker-entrypoint.sh
@@ -17,8 +17,6 @@ if [[ "$*" == node*current/index.js* ]]; then
 			tar -cC "$(dirname "$src")" "$(basename "$src")" | tar -xC "$(dirname "$target")"
 		fi
 	done
-
-	knex-migrator-migrate --init --mgpath "$GHOST_INSTALL/current"
 fi

 exec "$@"

(The parts that are gone are some of the parts that have been the most annoying!! :tada: :heart:)

The image works when deploying a new Ghost instance, however it doesn't work when updating from a previous Ghost v1 blog because it doesn't migrate the old DB. To be more precise, the problem is the new column_id field. Is there any way to solve this?

Same as @crespum here. Ghost's seemly not migrating anything.

See https://github.com/docker-library/ghost/issues/147, especially https://github.com/docker-library/ghost/issues/147#issuecomment-417372462:

Did you by chance try to update to 2.x from a 1.x release < 1.25.4? In Ghost-CLI we added a provision that prevented updates if you were not already running the latest 1.x version of Ghost, and my guess is that the errors you're seeing are related to the fact that you need to upgrade to the latest 1.x version first before trying the 2.x upgrade.


additional settings

Hi guys,
as i am so happy to finally have a multi speaker player system that solves my multi room installation to be build.
After playing around with the integration i stumbled upon this missing option;

selection option such as select single or select all mode. for example to create playlists
a select function to play a selected group of songs out of the play list or folder
is that possible in the future?

You should be able to select multiple items by clicking on the image thumb (in list view only)
when you figured out 1, that is also already possible.

See below screenshots (sorry they're from my production/family setup and so in Dutch, but you get the point).
Btw I now spot some glitches in the UI that the checkboxes get lost. I will fix that. The functionality exists however.

geen probleem met Nederlands hoor, ben zelf een Vlaming ;)
toch bedankt weerom voor de info. als het weer werkt ga ik dat direct testen.
en terzijde, wat is de stand voor de Alexa integratie?

Sorry, back to English again for the fellow international Githubbers. I will add a Dutch channel on the discord server to talk Dutch there ;-)
Alexa integration can be followed here:
https://github.com/music-assistant/hass-music-assistant/issues/101

no problem, thanks

hi Marcel, i updated the application and all is back and running.
as you replied on my question of selecting multiple songs, now that i figured out and that works too.
when i have selected the songs i selected add to playlist  or create a new one is not working.
i can click on that button but nothing happends, it stays grey.
any tips?

Sorry, missed this message and I just released a new version. I will take a look at it tomorrow. I did however fix the UI glitch

hi Marcel,
this popped up again after installingthe latest version.
Logger: homeassistant.setup
Source: setup.py:162
First occurred: 19:21:36 (1 occurrences)
Last logged: 19:21:36
Setup failed for custom integration mass: Unable to import component: No module named 'aiofiles.ospath'

I'm afraid you have another custom integration that is messing with the aiofiles dependency...

I will try to figure it out by deleting historically
On Mon, May 23, 2022, 20:58 Marcel van der Veldt @.***>
wrote:

I'm afraid you have another custom integration that is messing with the
aiofiles dependency...
—
Reply to this email directly, view it on GitHub
https://github.com/music-assistant/hass-music-assistant/issues/203#issuecomment-1135030879,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJDBJ54IJ636IQRQMRSFJ3VLPINDANCNFSM5WPBL7YA
.
You are receiving this because you authored the thread.Message ID:
@.***>

hi , it seems that organizr disturbed the situation. after removal all worked well at the moment


[BUG] Agentflow Not Functioning Properly in Flowise 2.0.0 #2847

🛠 Supervisor.ts -> Removed summarization fields.

While final summarization enhances contextual consistency between user queries and supervisor outputs, aiding task resumption with the introduction of the new Agent Memory node, it can also restrict the range of applications a Multi-Agent system can handle when a clean final output is essential.
So, can we make this optional?

While final summarization enhances contextual consistency between user queries and supervisor outputs, aiding task resumption with the introduction of the new Agent Memory node, it can also restrict the range of applications a Multi-Agent system can handle when a clean final output is essential.
So, can we make this optional?

The summarisation feature introduced in version 2.0.0 broke the behaviour of all the workers I created. I'm not a typescript expert, just a business data analyst, so this commit is to revert back to the previous state. In fact, it's not even clear from the git logs that I can revert this commit as a business data analyst, but I can confirm that removing the summary itself brought back the behaviour I intended. If the summary can be interpreted differently by different models and cause misbehaviour, I'd rather not have it. If you believe it should be an option, then I think it should be turned off by default.

Understood, will see if we can create an optional field for supervisor, and provide summary only when user select so

@seonghobae I've created a PR that brings back the old functionality, and move summarization as an optional field.


Support nvim-0.7's nvim_set_hl api

This pr adds support for nvim 0.7's new api nvim_set_hl.  This pr also extends the compiler generate both a viml version and a nvim-0.7+ version. Nightfox will check if your editor is nvim-0.7+ before loading the correct precompiled file. When the user uses the compiler it also generates based on  the editor's supported api.
Performance Note
From my initial testing there is no significant difference between the viml version and nvim_set_hi version when dealing with compiled files. Slightly more of the time the viml version is faster.  I have tried to benchmark/time this with different methods:

Startuptime with tweekmonster/startuptime.vim
Startuptime with --startuptime
Plenary with require('plenary.profile').benchmark()

Unsure that there is any benifit from this pr. It would be great of others could assist in coming up with a way to validate that nvim_set_hl version is faster.

Benchmarked requireing the two types of compiled files with the commited benchmark.

Benchmark
local benchmark = require("plenary.profile").benchmark
local fmt = string.format

local bench_iter = 100
local process_iter = 20

local function rep(n, char)
  local s = ""
  char = char or "-"
  for _ = 1, n do
    s = s .. char
  end
  return s
end

local function process(iterations)
  local function execute(modname)
    package.loaded[modname] = nil
    require(modname)
  end

  local nvim = benchmark(iterations, execute, "nightfox.precompiled.nvim.nightfox_compiled")
  local viml = benchmark(iterations, execute, "nightfox.precompiled.viml.nightfox_compiled")

  local difference = math.abs(nvim - viml)

  return nvim, viml, difference
end

local fmt_str = "| %-12s | %-12s | %-6s | %-12s |"
local lines = {}
table.insert(lines, fmt(fmt_str, "nvim", "viml", "winner", "difference"))
table.insert(lines, fmt(fmt_str, rep(12), rep(12), rep(6), rep(12)))
for _ = 1, process_iter do
  local nvim, viml, difference = process(bench_iter)
  local winner = viml > nvim and "nvim" or "viml"
  table.insert(lines, fmt(fmt_str, nvim, viml, winner, difference))
end

print(table.concat(lines, "\n"))

The results of this were:

nvim
viml
winner
difference

0.13587727
0.14480916
nvim
0.00893189

0.126019095
0.144379504
nvim
0.018360409

0.121695834
0.145396634
nvim
0.0237008

0.126382063
0.147077075
nvim
0.020695012

0.126739153
0.15228737
nvim
0.025548217

0.123327316
0.144052505
nvim
0.020725189

0.120775092
0.144650431
nvim
0.023875339

0.122740701
0.144309368
nvim
0.021568667

0.120412961
0.142972085
nvim
0.022559124

0.120056512
0.143038069
nvim
0.022981557

0.121483176
0.143661078
nvim
0.022177902

0.121731856
0.146417584
nvim
0.024685728

0.124857722
0.143044062
nvim
0.01818634

0.121358067
0.142138951
nvim
0.020780884

0.121309499
0.146483703
nvim
0.025174204

0.120200838
0.143400906
nvim
0.023200068

0.121330985
0.143589931
nvim
0.022258946

0.122106515
0.143682243
nvim
0.021575728

0.126486296
0.14283298
nvim
0.016346684

0.120689742
0.143274019
nvim
0.022584277

From this I can see a small marginal improvement.


Fix comment: tabs replaced by spaces

There were some unreadable comment due to tab key.
So all tab keys were changed to space keys.

Great, thanks!


fix(docs): js doc's param mismatch for setSizeConstraints

Reference: #10242

Apparently, I'm also blind to typos 😂

Apparently, I'm also blind to typos 😂

It's a requirement to join the working group, you just didn't know it yet.

Or we're just infectious 🤷


Move Coercion for MakeArray to coerce_arguments_for_signature and introduce another one for ArrayAppend

Which issue does this PR close?

Ref #7142
Close #7995
Rationale for this change

Fix Null Handing for array function. ArrayAppend first, others later.
What changes are included in this PR?

Move coercion for MakeArray to different place.
Add signature for ArrayAppend
Are these changes tested?

MakeArray - existing test
ArrayAppend - new test
Are there any user-facing changes?

wait on #8318 and #8331

@alamb Ready for review! I hope this is a better solution for dealing with nulls. I had tried Trait SignatureComputation, but it is a little overly complex.

I merged this branch up from main to ensure there are no logical conflicts, and if all tests pass I intend to merge it


Itemframes wash away in spongeforge, but not vanilla/forge

Tested with spongeforge-1808-1250, vanilla minecraft 1.8.9 and forge-1808
In spongeforge, if water flows down over an itemframe, or it is at ground level and water flows into it, the itemframe remains on the block submerged fine, but when the water source is removed and frames are reexposed to air, the itemframes pop off the blocks.  Vanilla minecraft behavior is they are not impacted by the addition and removal of water.

Can you test this in SpongeVanilla?

i can, and shall.

Yes, the behaviour is identical in spongevanilla Beta-291


no-magic-numbers: Allow default parameter values to be number literals

PR checklist

[X] Addresses an existing issue: #1965
[X] New feature, bugfix, or enhancement

[X] Includes tests

[ ] Documentation update
[X] Enable CircleCI for your fork (https://circleci.com/add-projects)

What changes did you make?
Allowed "magic" numbers to appear inside parameters.

@andy-hanson thanks!


[SPARK-6518][MLlib][Example][DOC] Add example code and user guide for bisecting k-means

This PR includes only an example code in order to finish it quickly.
I'll send another PR for the docs soon.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46655/
Test FAILed.

Jenkins, retest this please

Test build #46657 has started for PR 9952 at commit 7c8005d.

Test build #46657 has finished for PR 9952 at commit 7c8005d.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  *   case class Params(\n

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46657/
Test PASSed.

Merged build finished. Test PASSed.

@jkbradley could you review this PR?

When you modify this and [https://github.com/apache/spark/pull/9968] to use the include_example functionality, it may make sense to change this example code to use fixed parameters, rather than making it a command-line tool.

All right. I'll fix it.

Test build #46790 has started for PR 9952 at commit 86f6085.

Test build #46790 has finished for PR 9952 at commit 86f6085.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46790/
Test PASSed.

@jkbradley could you review it?

I moved the documentation to this PR from https://github.com/apache/spark/pull/9968. Because the PR depends on this PR.
I modified the docs for BisectingKMeans with include_example.

Test build #47095 has started for PR 9952 at commit 2f4c2a5.

Test build #47095 has finished for PR 9952 at commit 2f4c2a5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47095/
Test PASSed.

@jkbradley ping

Thanks!  I'll review today

I'll go ahead and review this, but if you have time to add a Java example, that would be awesome--thanks!

That should be it.

Also, can you please add the "[DOC]" tag to the PR title?  T'hanks!

@jkbradley sure, done.

Thanks, I'll check back for updates for the few remaining comments.

ping @jkbradley

@yu-iskw There are several comments of mine (above) which have not yet been addressed.  Could you please update this PR based on those comments?  I'll then take another look.

Oh, I'm terribly sorry about that. Pushing the update was failed....

Modified what you pointed out
Add a Java example and its doc

Test build #47639 has started for PR 9952 at commit 7c36c1d.

Test build #47639 has finished for PR 9952 at commit 7c36c1d.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * public class JavaBisectingKMeansExample \n

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47639/
Test PASSed.

Merged build finished. Test PASSed.

No problem.  I just added some comments and am generating the docs now.

The generated docs look good, so just those few comments.

@jkbradley thanks for the review. I modified the wrong indentations and excluded the import statements for SparkConf and JavaSparkContext.

Test build #47780 has started for PR 9952 at commit 3066696.

Test build #47780 has finished for PR 9952 at commit 3066696.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * public class JavaBisectingKMeansExample \n

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47780/
Test PASSed.

LGTM, merging with master and branch-1.6
Thanks!

Thank you for merging it!


udp queries return 0 records in aws ec2 amazon linux

I can only reproduce this in aws ec2 - testing locally on a mac or debian based machine works.

Could anyone point me to the right direction here?

very much off-topic for this lib, prolly should ask the author of harderdns.
/close

@miekg yes, I am the author of harderdns - asking for what I am missing here. I'm more than happy to provide more details.

I find it weird that I can not reproduce this in other machines than ec2 - and, that plain dig works in ec2.

[ Quoting @.***> in "Re: [miekg/dns] udp queries return ..." ]

I find it weird that I can not reproduce this in other machines than ec2 - and,
that plain dig works in ec2.

I have no idea, not using or knowing how ec2 works.

Check with the race detector enabled. That might be relevant. Not sure otherwise.

@tmthrgd sorry whats that? found this: https://github.com/miekg/dns/blob/master/client_test.go

@matti Check out https://go.dev/blog/race-detector and https://go.dev/doc/articles/race_detector. It's part of the go tool.


[Feature]: DarkMode / Light Mode want to add

Is your feature request related to a problem? Please describe.
Want to add the dark mode functionality
Describe the solution you'd like
I would like to work on this functionality. in my earlier projects i have worked on this functionality. I would be grateful if you could assign me this functionality under Gssoc'24
Alternatives
No response
Additional Context
No response
Are you interested in contributing?

[X] I'd like to work on this issue

Code of Conduct

[X] I have used the search function to check if an issue already exists
[X] I agree to follow this project's Code of Conduct

Hey @tusharyadav11, how are you planning to implement this? We're using tailwind and daisyui - are you going to make config changes to them or some other way?
Did you setup locally?
(We'll assign this issue on the basis of best approach)

i am trying to implement it you Js,css and html @pranshugupta54

Doing it directly with html css js won't be good here.

Hey pranshugupta54 , Please assign this issue to me

Hey @aasthakourav20, please read the above comments

@karishmaaa101, https://github.com/digitomize/digitomize/issues/824#issuecomment-2105798176

hi @pranshugupta54 , here's my approach on how will i implement the dark mode:

i'll use the useState hook from react to manage weather the app is in dark mode , starting as a false, or based on saved data.
i will use the loacalStorage to keep the dark mode setting even after reloading of the page
toggling happens when the button will be clicked, will create a handleDarkMode functon
the main  style then changes depending on darkMode being true (bg-black) or false (bg-white)
the toggle button switches between showing on and off based on darkMode, and clicking it will trigger the handleDarkMode
lastly, the darkMOde state wil be sent to various pages, so that it can be accessed & updated as requiredd

@yashmandi, please check tailwind docs and daisyui docs. There is no need to change the classes from bg-black to bg-white on switch, that will require us to change almost everything.

Using tailwind CSS, we can add darkMode selector to tailwind config file
  darkMode: 'selector',
  // ...
}``` and use as dark in className to perform what action to be performed when site is in dark mode.
In DaisyUI, we use
daisyui: {
    themes: ["dark"]
  },

That sounds a better approach, we'd probably need to change some classes too.

@pranshugupta54  hey pranshu assign it to me dark mode functionality . recently only i have implemented dark mode functionality using darkowl without changing up the any classes

@tusharyadav11, describe the approach more. We don't want you to just get inverted colors

@tusharyadav11, describe the approach more. We don't want you to just get inverted colors

it is a type of script . we just have to insert it into the code and automatically created the toggle button for the switch of light mode to dark and vice versa

How will it work? You're not giving any approach at all. Just a button to flip makes no sense

Doing dark mode is not about only changing background color; the other components colors needs to be adjusted as well to make them visible according to its background. So we have to change the some classes as well.

Yeah, we gotta make classes like dark:bg-abc bg-xyz depending on theme

@pranshugupta54 as the whole site is already in dark mode, how you want site to look like in light mode?

We don't really have any plans/roadmap for it, you'll have to work on the design too under the issue.

OK no problem

whats the timelimit for the assignment?

This is a not a priority so you can take 7-10 days

I am working on it

@pranshugupta54 home page have grid for dark mode, but for light mode the grid will not look good.

@pranshugupta54  can you tell me from where this grid background is coming?


Add more detail to the click event

The event object now also contains data returned from THREEjs's raycaster, describing where the mouse clicked on the object.

@lcb931023 @mayognaise ping
resolve it please

woah... the conflict is practically the entire file!
Looks like there are quite a few new changes to the project, that makes this pull request outdated. I'm going to close it.

@lcb931023 could U add yours features again or paste it here as-is?


New hermes stats

Here you can see changes to Hermes only (at least AppController need to be changed to make appscale work - will do next week).
The structure stats modules is following:
hermes
  stats
    producers
       cluster_stats        gets stats from other nodes (reads using timestamp as cursor)
       node_stats           gets nodes stats
       processes_stats     gets processes stats for all monit processes
       proxies_stats      gets proxies stats from haproxy
    subscribers
       cache             receives different kinds of stats and writes it to cache (limited size and TTL are implemented
       portal          will send stats to portal
       profile         will write stats to csv tables
    stats_app        module responsible for configuring all pubsubs and api handlers (process stats can be disabled, proxies stats is available on LB nodes only, cluster stats is available only on master node)
    handlers          handlers to provide access to stats caches, current stats and to cluster stats
    pubsub_base
    unified_service_names

Review volunteers are welcome, but I'll write more docs later, so it makes to wait unless you're want to see what's going on with stats now.
p.s.: have to go.. will try to add more comments and respond on your comments during weekend and my day-offs

https://ocd.appscale.com:8080/job/Daily Build/3213/

https://ocd.appscale.com:8080/job/Daily Build/3218/

https://ocd.appscale.com:8080/job/Daily Build/3223/


Ardublockly building problem

Hi. I have just downloaded the ardublockly-master and i can't build the windows executable.
I made some minor changes to blockly blocks and generators and succesfully build blockly. I am running localy ardublockly with python server and everything works fine.
The problem occurs when i try to build a new windows executable, I followed the instructions at https://github.com/carlosperate/ardublockly/wiki/Building-Ardublockly and when i run the build_py2exe.py script i get an empty arduexec folder and some traceback calls in the command line. (see image below)
I have python 2.7 and 3.6 installed, and i also installed py2exe, pyInstaller, MkDocs and node.js with electron. I have windows 10 32-bit. I would really appreciate any help on this!

Hi @ioarvanit,
Apologies for the late reply. It looks like py2exe does not yet support python 3.6, and in fact is not yet compatible with python 3.5 either, so it looks like for the time being Python 3.4 will be required to build Ardublockly.

I've also added a note in https://github.com/carlosperate/ardublockly/wiki/Building-Ardublockly to emphasise this incompatibility.

Thanks for the feedback.

Closing this as the issue is an incompatibility from py2exe and the Python version.


http post with timestamp is wrong

trying a simple post using the line protocol:
curl -i -XPOST 'http://myurl/write?db=mydb' --data-binary 'dashboard HR=5432<PHONE_NUMBER>575'"

I get a 204 (good) - and the timestamp<PHONE_NUMBER>575 is Sat, 13 Feb 2016 11:16:29 GMT
however, if I search for this record ..
curl -G 'http://myurl/query?db=mydb' --data-urlencode "q=SELECT HR FROM dashboard WHERE HR=5432"

I get the following result:
{"results":[{"series":[{"name":"dashboard","columns":["time","HR"],"values":[["1970-01-01T00:24:15.362189575Z",5432]]}]}]}

now, the interesting (or perhaps not) part is that 1970-01-01 00:24:15 is 1455 seconds - which is the first 4 digits of the supplied timestamp
am I doing something wrong here ? I've scoured the documentation and the only thing I can find is that if precision is not supplied, then the timestamp defaults to nanoseconds
thanks for any help!

timestamp defaults to nanoseconds

Yes, this is exactly what is happening.<PHONE_NUMBER>575 in nanoseconds is 1455.362189575 seconds after epoch, which is the timestamp you see.
System is behaving as expected and as documented. If you are supplying non-nanosecond timestamps you MUST supply the precision, as well. See https://influxdb.com/docs/v0.9/query_language/query_syntax.html#http for documentation on the precision parameter.


IsoDateTimeConverter - always append Z or explicit timezone, to avoid browser incompatibilities

Due to an issue in ES5.1, browsers have different interpretations of ISO-8601 dates that are missing a trailing timezone (neither 'Z' nor explicit timezone value).
Currently, IsoDateTimeConverter does not set 'Z' when serializing a DateTime object that was created without a DateTimeKind.UTC parameter:
var date = new DateTime(2009, 2, 15, 0, 0, 0, DateTimeKind.Local);
var settings = new JsonSerializerSettings();
settings.Converters.Add(new IsoDateTimeConverter());

// Succeeds
Assert.IsTrue(JsonConvert.SerializeObject(date.ToUniversalTime(), settings).EndsWith("Z\""));

// Fails
Assert.IsTrue(JsonConvert.SerializeObject(date, settings).EndsWith("Z\""));

To make it easier to work with output from Json.NET, it should always append the 'Z' (or set an explicit timezone) when converting dates to strings in IsoDateTimeConverter.
The easiest fix is to use the result of .ToUniversalTime() on each date object when serializing it (as shown above).

I was thrown off by this because the documentation page shows it does append a trailing Z:
http://www.newtonsoft.com/json/help/html/DatesInJSON.htm
Shows: "Details":"Application started.","LogDate":"2009-02-15T00:00:00Z" ... But the actual output is not that - It does not have a trailing Z. I was able to get the Z without calling ToUniversalTime by settings this option in the serializer settings:
_jsonSettings.DateTimeZoneHandling = DateTimeZoneHandling.Utc;

Probably just a documentation issue.

@grennis , the docs are maybe unclear but not incorrect. It doesn't say that it always appends a Z, it says it uses the ISO format. That is, Z for UTC dates, but not all dates are UTC.
It later states:

set DateTimeZoneHandling to Utc to serialize all DateTimes as UTC dates

Which implies that non-UTC dates will not be serialized as UTC dates. :)

So does JSON.net append a Z or not? I'm doing some tests and it looks like it isn't appending a Z.

I could not believe the issue is almost 8 years(!) and the library does not provide strict specialized UtcDateTimeConverter to manage DateTime conversions in a convenient "no-doubt" style!
Could you please help me to implement UtcDateTimeConverter ?
a) Every incoming DateTime must be serialized to full format with UTC time-zone.
always UTC with clear indication of this.
I.e.   "2021-11-17T04:38:47.1168339Z"
b) Deserialization must return DateTime always in UTC.