added Nimatic and beautiful-jekyll static site gen

Updated on jamstack.org via https://github.com/jamstack/jamstack.org/pull/420 !


open weather doesnt work

Hi @widapro ! really amazing project, i'm still using since the first version and now i'm trying your new one, seems really super but when trying to use the openweather dashboard after reboot report it as "manual" like it doesn't "like" it... any ideas?
tried to put in different zone, i get to work it only one time, with temperature.
Thank you

Let's continue the discussion here: https://github.com/widapro/wledPixel/issues/24
Try the new beta version from the link above. It also contains some changes in working with OpenWeather.


kusion watch: filter out unchanged resources

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 9 (0.0%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.2%) to 72.564%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/kusionctl/cmd/apply/options.go
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/engine/operation/parser/parser.go
3
75.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
4557

Relevant Lines:
6280

💛  - Coveralls


Release tarballs aren't stable

See original issue on GitLab
In GitLab by [Gitlab user @bochecha] on Dec 17, 2018, 23:42
Summary
I had downloaded the bst 1.2.3 release tarball on release day.
Downloading it now, I get a different tarball.
Here is the difference:
diff -ur old/buildstream/_version.py new/buildstream/_version.py
--- old/buildstream/_version.py	2018-10-05 09:01:57.000000000 +0200
+++ new/buildstream/_version.py	2018-10-05 09:01:57.000000000 +0200
[[Gitlab user @]](https://gitlab.com/)[[Gitlab user @]](https://gitlab.com/) -24,7 +24,7 [[Gitlab user @]](https://gitlab.com/)[[Gitlab user @]](https://gitlab.com/)
     # setup.py/versioneer.py will grep for the variable names, so they must
     # each be defined on a line of their own. _version.py will just call
     # get_keywords().
-    git_refnames = " (tag: 1.2.3, refs/keep-around/10abe77fe8d77385d86f225b503d9185f4ef7f3a, bst-1.2)"
+    git_refnames = " (tag: 1.2.3, refs/keep-around/10abe77fe8d77385d86f225b503d9185f4ef7f3a)"
     git_full = "10abe77fe8d77385d86f225b503d9185f4ef7f3a"
     git_date = "2018-10-05 16:01:57 +0900"
     keywords = {"refnames": git_refnames, "full": git_full, "date": git_date}

Steps to reproduce
It's not really possible to reproduce it any more, I think.
What is the current bug behavior?
Tarballs aren't reproducibly generated.
What is the expected correct behavior?
Tarballs should be reproducibly generated, no matter when they are downloaded.
Other relevant information
I think the issue is that back when I had downloaded it the first time, that tag was the tip of the bst-1.2 branch, and as a result the branch name got added to git_refnames?

In GitLab by [Gitlab user @cs-shadow] on Oct 10, 2019, 19:01
[Gitlab user @bochecha] can you also please say from where downloaded the tarball? Like GitLab releases page, CI job resources etc.
(PS: Apologies for looking at it only after 9 months)

In GitLab by [Gitlab user @bochecha] on Oct 10, 2019, 19:21
I think that was from Gitlab.
Most likely I had this issue while packaging Buildstream for Fedora, and the URL I'm using there is:
https://gitlab.com/BuildStream/buildstream/-/archive/%{version}/buildstream-%{version}.tar.bz2
That seems to correspond to the URL for a tag.
Like I said in my first comment, my guess is that when you download a tarball for ${COMMIT}, all refs pointing to that commit in Git get added to git_refnames in _version.py.
When I had downloaded the tarball the first time, both the 1.2.3 tag and the bst-1.2 branch were pointing to the ${COMMIT} commit I was downloading.
But when I downloaded it the second time, the bst-1.2 branch had moved on and was pointing to a newer commit, and so only the 1.2.3 tag was pointing to the ${COMMIT} commit I was downloading.
And so, downloading the tarballs for the same ${COMMIT} commit (the 1.2.3 tag) I got 2 different tarballs.
That's my guess anyway, from looking at the diff between the 2 tarballs.

In GitLab by [Gitlab user @tristanvb] on Nov 5, 2020, 09:06
We have been publishing releases on download.gnome.org, as indicated in the release notes, we also intend to publish releases as tarballs in stable locations, not dynamically generated things on services like github or gitlab.
We will continue to link to the locations of the stable tarballs in any release announcements, as usual.


Integrate CI with this repo and provide binary packages for users

Is your feature request related to a problem? Please describe.
Rosetta Drone seems to be a very useful and nice app, but its adoption is limited mainly by lack of easy to obtain binary apk packages for end-users. Current user has to be able to compile this app and have account in DJI to get Application key and obtain Google Maps API key.
I think it would be great to provide these packages in automated manner to avoid maintenance burden. Integrating build actions could also help with checking quality of code in Pull requests.
Describe the solution you'd like

implement Build actions linked with pushing and PR-s
Implement build an release actions

Describe alternatives you've considered

building manually
leaving it as it is

Additional context
In terms of safety we could use GitHub Secrets to ensure Application key won't leak.

@The1only
I would be interested in implementing these features, but firstly I want to get an approval.  And discuss it:)

Hi @pktiuk ,
I think it is not a good idea to release binaries because,

Rosetta is focused on developers, not final users
there is risk involved. You should always test your model in a simulator first and also be prepared to disconnect the RC immediately if you see something is going wrong.
you need a license key from DJI
you need a license hey from Google

Dup of https://github.com/The1only/rosettadrone/issues/95
I believe GitHub is already checking if the project builds after a commit.

Hi @kripper ,
I disagree with some of your points.

Rosetta is focused on developers, not final users

Having builds would make testing this app and finding bugs much easier. Without builds people can't even open this app to check interface to check whether this app meets their needs.

there is risk involved. You should always test your model in a simulator first and also be prepared to disconnect the RC immediately if you see something is going wrong.

To be honest I don't understand how this point is linked with releasing binaries.

you need a license key from DJI

Why is this a problem? Key can be easily generated and AFAIK are no limits from DJI in usage of these keys. I think they serve similar purpose to tokens required by discord bots.

you need a license hey from Google

I guess token from google may have limited number of API calls, co we can ask user about generating it and saving in settings.

I believe GitHub is already checking if the project builds after a commit.

No, this repository doesn't have any workflows, and has never ran any build actions. Just check actions tab. This entire repository may not compile as well.

I'm afraid I'm the only active maintainer and I'm sure I will not give support to users who didn't build the project themselves.

It explains a lot, but without users this project won't get traction, and without traction it wouldn't get any outside contributions. It is also more difficult to find this project in the internet because nobody uses it. I spent 3 days looking for simple solution for better streaming from DJI drone without using official app and I found  it on some old forum briefly mentioning legacy version of this app.

Anyway I think at least basic CI building this app would be very useful, so this issue should be either reopened, or I can create a new one, only about creating CI (only building without publishing releases).

CI is welcome.

PR is waiting https://github.com/The1only/rosettadrone/pull/140 , you have to only figure out what is wrong with your repo config


Implementation of Traffic Scenario 06

Description

Implementation of scenario 6 in file maneuver_opposite_direction.py
Created super class for ActorConfiguration to construct derived configuration

Where has this been tested?

Platform(s): Ubuntu 18.04
Python version(s): 2.7
CARLA version: 0.9.4

This change is

Small update for behavior of opposing vehicle is required (starts too early to drive)


Make queue durable in queue_declare

Changes
A recent eQ change has been to make the eQ queue durable, which also needs to be declared on the client side. This pull request adds this setting to the queue_declare call.
How to test

Clean sdx-compose build with durable-queue branches for sdx-collect, sdx-console and sdx-bdd
Run some surveys through the console
Run sdx-bdd
Check the queue is marked as durable in the RabbitMQ UI

Who can test
Anyone but @ajmaddaford

👍


⚠ Empornium has degraded performance

In b983a26, Empornium ($EMP) experienced degraded performance:

HTTP code: 200
Response time: 1432 ms

Resolved: Empornium performance has improved in d8a6df3.


Color change not updating

When I updated the ~/alacritty/alacritty.yml file in macosx with the gruvbox theme, alacritty does not change colors after restart. What am I doing wrong? Thanks in advance.

Does changing other options work?
Usually Alacritty loads configuration from ~/.config/alacritty/alacritty.yml or ~/.alacritty.yml. You can check the actual location by running alacritty -v in another terminal. (not sure if this works in macOS)

As @siiptuo has already said I would recommend using ~/.config/alacritty/alacritty.yml. I would assume just moving that file there will already fix your issue.

Yes that was the problem. Thank you siiptuo and chrissduerr!

For those who may also stumble on this issue for a related issue - this doesn't (obviously) stop any config in your shell of choice (mine is Zsh) from changing the color scheme. I had dynamic-colors init still running in my .zshrc which changed the color from what I had configured in Alacritty.


Project first story for game master

Remove the first story from project page. It's in the trello board now.
Signed-off-by: velicue<EMAIL_ADDRESS>

Board is private?

I've added the email addresses from the mail to our board.


test(dtslint): add subscribeOn

Description:
This PR adds dtslint tests for subscribeOn.
Related issue (if exists): #4093

Pull Request Test Coverage Report for Build 7703

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 96.806%

Totals

Change from base Build 7698:
-0.2%

Covered Lines:
5244

Relevant Lines:
5417

💛  - Coveralls


Removes MD driver standalone option, bug fix on initialization

Feature or improvement description
Fixes an issue where coupled bodies did not initialize at the correct location when coupled with OpenFAST, especially when platform offsets were provided. @mattEhall authored this bug fix.
Removes the standalone flag from inside of MoorDyn.f90 and MoorDyn_Driver.f90, previously triggered by numturbines < 0 in the driver input file. The standalone issue was a work around to the bug fixed in this PR and thus is no longer needed.
Related issue, if one exists
#1978
#1990
Impacted areas of the software
MoorDyn
Additional supporting information
@andrew-platt can you check that I made the correct changes to the functions in MD_Types.f90 (Pack and unpack routines) when I removed the standalone variable. I believe in looking at the git history you set that up.
Corresponding docs update: FloatingArrayDesign/MoorDyn#184

Looks good!  Thanks for revising how this works!


[Slider] Avoid selection when dragging

When using mouse events and dragging to outside of the slider container the user will start to select text what will cause some undesired issues.
So to fix that I am using the user-select property. I add these property to the body element onmousedown disabling the selection and I remove it onmouseup enabling the selection again. This property is compatible with all the good browsers and with IE10, IE11 and Edge.
Text selection:

Undesired behaviour: if you start to drag without unselect the text you will start to carry the text around with you:

What about simply using preventDefault ?

I did, but the solution doesn't seem so good. If you preventDefault the onDragStart function you will avoid onMouseDown to execute, and also onFocus and onBlur. I did a workaround for that but it doesn't seem so clean like just avoid the selection with this css property

You would prevent onMouseDown because it is one level above and you would cancel the bubble phase, and the onBlur event is a consequence of not having the onFocus firing correctly

I wasn't explicit enought. Adding e.preventDefault() here seems to solve the issue.

If one adds e.preventDefault() there, he would actually be canceling the mousemove event. This approach seems to work because of a bug in most of the browsers. A correct implementation of DOM would not have any effect when calling preventDefault() in a mousemove event. In Safari, for example, prevent the default action of mousemove will not have any effect over text selection.
The correct event to cancel would be the mousedown and then would arise problems with the focus, blur and even an issue with the setState inside the requestAnimationFrame (still not so sure about this last one) that are possible to solve but not so clean.
Issue:
https://code.google.com/p/chromium/issues/detail?id=346473
https://codereview.chromium.org/1145433002/
This bug was fixed in Chrome 43 and then reverted because of an issue with Maps.
Another thing, is that the slider architecture seems to rely too much in events to call preventDefault() in one of them. And the onChange callback from the user would receive a canceled event (though, that should not be a problem for a mousemove event).
So, I would still stick with the user-select approach. What do you think?

That's a very good point, we shouldn't use preventDefault to cancel text selection during the mousemove event.
They seem to have a good solution here: https://github.com/google/material-design-lite/blob/master/src/slider/slider.js#L106. If we can, I would rather not apply a style to the body element.

The MDL are actually using <input type="range"> so they don't need to take care of text selection. It is a good idea, but would need to refactor all the component.
With this PR you would be adding a style to the body, but removing it when the user stops dragging, so no side effects. The slider component already have a similar approach when it registers the mousemove and mouseup event listeners in the document and then removes both when the user stops dragging. It makes sense because the user can move the pointer around all the document. The same with text selection, the user could be selecting text over the entire body element.

The MDL are actually using

I agree with you, I think that it we be better to use this internally. That's out of the scope of this PR.
Could you squash down the commit? I will merge, thanks!
Side note: I have noticed another issue :grin:

@felipethome Thanks!

@oliviertassinari Thank you too, and you are right, <input type="range"> would fix a lot of these issues, including the one you pointed above.

@felipethome If you want to work on it. Feel free to open an issue or to submit an PR for <input type="range"> :+1:.


Edumeet next gen architecture

(Issue 1000!)
Issue to foster some discussion about next gen architecture for edumeet. I have drafted a proposal for the new architecture in the following diagrams. One version for a cloud deployment and one for a 1 server local deploy.

The new client is under development here:
https://github.com/edumeet/edumeet-client
The room server is here:
https://github.com/edumeet/edumeet-room-server
The management server is yet to be pushed. The media-node is also yet to be pushed, but lives partially under the media-node branch in this repo. The plan is to rewrite to typescript for all parts of the new architecture.
The file sharing torrent tracker is not in the diagram, but will also be an optional component to deploy.

The new room-server now works, and the new media-node has been published here: https://github.com/edumeet/edumeet-media-node

The beginnings of the management server is now available here: https://github.com/edumeet/edumeet-management-server

The management server is fairly done. This marks the final milestone before an initial release of the new architecture. And we will now focus on polishing up everything.
The new architecture is improved in most ways from the old client/server. It supports multi-tenancy with separate OpenID connect/OAuth providers pr. tenant. Room management, ownership and permissions based on tenant/user. Breakout rooms. Horizontally scaled media architecture supporting cascading across all nodes based on load/geo-location.
From a code perspective, everything has been done from scratch, and we have departed from the old client/server in major ways. All code bases are now fully Typescript from the start. The various code bases have been built for easier extensibility and maintainability.


FAILURE: Build failed with an exception.

Building and installing the app on the device (cd android && ./gradlew installDebug)...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.gradle.internal.reflect.JavaMethod (file:/home/marcus/.gradle/wrapper/dists/gradle-2.14.1-all/8bnwg5hd3w55iofp58khbp6yv/gradle-2.14.1/lib/gradle-base-services-2.14.1.jar) to method java.lang.ClassLoader.getPackages()
WARNING: Please consider reporting this to the maintainers of org.gradle.internal.reflect.JavaMethod
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring project ':app'.

Failed to notify project evaluation listener.
javax/xml/bind/annotation/XmlSchema

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 3.881 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

Follow step by step tutorial react native

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

@hramos im having the exact same issue as @MarcusMann.
1: react-native init ReactNativeProject
2: cd /ReactNativeProject
3: npm install
4: react-native run-android

Switching from JDK9 to JDK8 (Windows 10 x64, gradle 2.14.1 ) solved the issue for me.

@vbarinov I've done that, but it has not made any difference.

@orinmurphy did you able to solve this? i am also facing the exact same issue, JDK9 installed

@amjadkhan120 yes I just solved this issue. I had two versions of Java installed, so i removed JDK9 and that fixed the issue for me. Now I am just using JDK8

I also had two versions installed (8 & 9), I removed 9 and everything started working.
To uninstall:
Navigate to /Library/Java/JavaVirtualMachines and remove the v9 directory
cd /Library/Java/JavaVirtualMachines
sudo rm -rf {yourVersionName}.jdk
If you do not have version 8 in that directory you will need to install JDK8.

Thanks @orinmurphy @azamatsmith, its JDK9 which is causing the issue, Now its working fine after installing JDK8.

Thanks ! I was having this issue as well

@vbarinov Solution fixed my issue, now is working perfectly.. 👍

After deleted jdk-9 will be ok, but why RN can't support jdk-9?

+1 for removing JDK9

Removing jdk9 is the solution for me

No need to remove JDK9, just update your JAVA_HOME and PATH variable to point to JDK8.
Also, in the path variable, make sure jdk8 path has higher priority than javaclasspath ( added by oracle when you first install JAVA, this will still point to your earlier install version i.e; jdk9 ).
To switch between versions, just change the priority order in Path environment variable.

It's a generic Android issue that has nothing to do with React Native.

Please support JDK 9/10.

Same issue, please support JDK 10.

Facing same issue with JDK 10. Please add support for JDK 10 and update the doc too.

facing the same issue here, please support JDK 9 please.

Same issue. JDK 10.


DOCS-Updates-Product-Comparison

Updates to product comparison table: clarify OSS support, update federated services to cluster mesh.
Product Version(s):
OSS 3.28, 3.27, 3.26
CE 3.19, 3.18-2, 3.17
CC 18-2, 19-1
Issue:
https://tigera.atlassian.net/browse/DOCS-1942
Link to docs preview:
https://deploy-preview-1234--tigera.netlify.app/calico/latest/about/product-comparison
SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@tmjd Vaibov said you would be the best reviewer for section called, Cluster mesh for CC. The initial request was from Reza to show that OSS does support native cluster mesh (as described in his blog here: https://www.tigera.io/blog/deep-dive/what-is-a-kubernetes-cluster-mesh-and-what-are-the-benefits/). Open to rephrasing the items.

@rene-dekker Please review sections, "Application le


4-bit inference?

any possibility of adding 4-bit inference?  vllm is awesome!

do you mean w4a4？4-bit weight-only has already been supported

my bad.  I meant something like this: --quantization = int4
it may already be there somepalce or there may be a method to do it, we just cannot find it.

my bad. I meant something like this: --quantization = int4
it may already be there somepalce or there may be a method to do it, we just cannot find it.

Try adding this parameter '-q  gptq' or '-q awq ' in the startup command.  As for '-- quantification=int4', the code will automatically find the quantization_config under the model path to obtain the quantization bit

GREAT!!!!!!!!!!!!!!!!!!!!!!!!!!!  THX!!!!!!!!!!!!!!!!!!!!!!!   8-))

Do you have one small example floating around someplace?

do you mean w4a4？4-bit weight-only has already been supported
+1
like this algo: https://github.com/efeslab/Atom


DatagramProtocol event loop not active during RunEngine execution

The RunEngine doesn't allow the passed event loop to run while it executes the plans.
Expected Behavior
The event loop should continue processing messages from the UDP port while the RunEngine executes its plans.
Current Behavior
The event loop stops processing received datagrams.
Possible Solution
I'm not sure if I am attacking this problem correctly with regard to the ophyd device implementation.
Example attached: https://gist.github.com/stashlukj/b1c014e90f23047d7bda73182a0355cd
Environment: Ubuntu 20.04, Python 3.8

That situation may be a novel one for bluesky applications. I can see how, "Take whatever sensors I can find and run with that," makes sense in this context; it's just different that the one that bluesky originated in, which is more like, "I expect this set of senors and if one of them isn't connecting, bail."
I think the approach you have described makes sense in that context.


Updated the showcase

Added more open source projects.
for the issue #5

Got the information not to use hacktoberfest-accepted label. every repo with this label is auto registrated.

hey its been excluded from hacktoberfest can you have a look into it

hey its been excluded from hacktoberfest can you have a look into it

This repo was never created to get cheap fast pull requests. this repo should be a source for contributors. @LOKESHPRASAD12


cherry pick of aaff537

As we cannot update to 1.5.2, I cherry-picked a fix on TypeKey to prevent dead lock.
Is it possible to merge and release 1.4.7 please ?

@elaatifi Is it possible to review this Pull Request?

@elaatifi Hello. Is it possible to release the version 1.4.7 ?


Move planner into a new sub-package

Putting planner into a package has the following benefits (IMO):

The planner type itself can cleanly be broken up over multiple files
Files in the planner package can be group related functionality
Some groups of functions can be additionally group into sub-types
It becomes obvious what functions of the planner are being used by other code, as the those functions must now be public
Newly created private calls can't "accidentally" be used in other code.

Downsides:

Some types funcs are a bit less accessible (needs imports, etc. more typing)
The code churn to make this change

Overall I think its worth it. Also, I wanted to start this refactor before we started messing with the logic we'd need to determine if shares can be combined into a single instance.

Just as I was updating the share planner bit to add support for path.

I've tried to organize the commits in a way that is fairly reviewable. The approach is to:

copy the original planner.go to a new sub-package
break it up over multiple files
convert those files to public functions and/or public types
swap code in resources pkg to use the new public types/funcs
drop the old file

This is to make more smaller patches but still have each one build cleanly & in theory pass ci checks.

/retest centos-ci/sink-clustered/mini-k8s-1.23

In order not to be rude an prioritize merging my own PRs above others I'm going to let this sit a little while longer. But if still mergable/approved next week I'll work to merge it.
So with that said @synarete, @raghavendra-talur, @anoopcs9  last chance for reviews. :-)

In order not to be rude an prioritize merging my own PRs above others I'm going to let this sit a little while longer. But if still mergable/approved next week I'll work to merge it. So with that said @synarete, @raghavendra-talur, @anoopcs9 last chance for reviews. :-)

@phlogistonjohn LGTM, and I would encourage you to merge it into master and let pending PRs rebase.
One minor comment: consider squashing this patch (use 'pl' for Planner): https://github.com/synarete/samba-operator/commit/868d14920f822b68322e887ddee1abd2ceeebc11

In order not to be rude an prioritize merging my own PRs above others I'm going to let this sit a little while longer. But if still mergable/approved next week I'll work to merge it. So with that said @synarete, @raghavendra-talur, @anoopcs9 last chance for reviews. :-)

@phlogistonjohn LGTM, and I would encourage you to merge it into master and let pending PRs rebase.
One minor comment: consider squashing this patch (use 'pl' for Planner): synarete@868d149

Thanks! However, I don't think that there's a need to squash it... let's just take that in a follow up PR

/retest centos-ci/sink-clustered/mini-k8s-1.21

/retest centos-ci/sink-clustered/mini-k8s-1.23


GitHub actions revised

Description

[action] Now running jobs on Mac and Win
[action] Ensuring xdpm install action doesn't fail due to non-existent target dirs by using mkdir/md
[lib/validate.js] Ensuring xdpm validate action doesn't fail by checking if .icons property existing before invoking .forEach

Related Issue
https://github.com/AdobeXD/xdpm/pull/35
Motivation and Context

Trying to ensure we don't end up with pesky failure annotations in our actions results when we actually intend for the action to fail.
Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

This is great :+1:


feat: Small playground improvements

This improves a couple small things in the playground:

Increase the editor font size to be the same size as the output tab to make it easier to read (they are still different fonts, so it doesn't look perfect). I want to follow up with a PR to change the output to be rendered in a readonly Monaco window.
Copy the contents of the active tab (fixes #1533).
Swap the output from JSON to YAML (fixes #1534).

This is my first contribution, so please let me know if there's anything I'm missing. I can also update the changelog if it'd be helpful.

Thank you very much for these @nicot ! 🙏


Draft

@rjaros what do you think of this draft:

adding hashCode to router instances (for a stable cache)
publishing HashRouter/BrowserRouter to use without @Composable, I guess you only support BrowserRouter at all?

Yes, I work with BrowserRouter only. Making it a singleton will be enough to drop a need for any other global variable.
But I'm not sure how does this change relate to cache?

Your cache uses hashcode but there is no custom hashcode implementation for any class yet, so it will still create and add a new instance over and over  because it currently uses the object identity.
Or what do I miss?

The default hashCode always returns the same value for the same instance.

In typical scenario there is only one Router instance in an application, but I had to add this hashCode to my cache key because there are multiple Router instances created in tests.

The default hashCode always returns the same value for the same instance.

That's true, but in line 91, https://github.com/hfhbd/routing-compose/blob/9e3a4c7319ac28cfed404ea2944a562051566506/src/commonMain/kotlin/app/softwork/routingcompose/RouteBuilder.kt#L91, the current router is not the global one, but a DelegatedRouter with identity hashcode.

I think you are right. In my copy of your lib I currently don't use this hashCode. I just use the paths as the key and it works perfectly fine:
https://github.com/rjaros/kilua/blob/main/modules/kilua-routing/src/commonMain/kotlin/app/softwork/routingcompose/RouteBuilder.kt#L113
I've added the hashCode to fix failing tests, when I decided to share my changes directly in a PR, and it may be wrong.


Charm fails to integrate in a cross model relation with a VM charm

Describe the bug
Charm fails to integrate in a cross model relation
juju status shows:
Model      Controller      Cloud/Region        Version  SLA          Timestamp
k8s-model  k8s-controller  microk8s/localhost  3.1.6    unsupported  20:28:35Z

App               Version  Status   Scale  Charm             Channel  Rev  Address        Exposed  Message
route53-lego-k8s           waiting      1  route53-lego-k8s  stable     7  <IP_ADDRESS>  no       installing agent

Unit                 Workload  Agent  Address    Ports  Message
route53-lego-k8s/0*  blocked   idle   <IP_ADDRESS>         Workload command execution failed, use `juju debug-log` for more information.

Offer        Application       Charm             Rev  Connected  Endpoint      Interface         Role
certs-offer  route53-lego-k8s  route53-lego-k8s  7    1/1        certificates  tls-certificates  provider

and juju debug-log shows:
unit-route53-lego-k8s-0: 20:20:03 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     2024/01/16 20:20:02 [INFO] acme: Registering account for<EMAIL_ADDRESS>unit-route53-lego-k8s-0: 20:20:03 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     2024/01/16 20:20:03 Could not complete registration
unit-route53-lego-k8s-0: 20:20:03 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     	acme: error: 503 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-acct :: urn:ietf:params:acme:error:rateLimited :: Service busy; retry later.
unit-route53-lego-k8s-0: 20:20:03 INFO unit.route53-lego-k8s/0.juju-log certificates:0: Received Certificate Creation Request for domain <IP_ADDRESS>
unit-route53-lego-k8s-0: 20:20:04 ERROR unit.route53-lego-k8s/0.juju-log certificates:0: Exited with code 1. Stderr:
unit-route53-lego-k8s-0: 20:20:04 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     2024/01/16 20:20:03 [INFO] acme: Registering account for<EMAIL_ADDRESS>unit-route53-lego-k8s-0: 20:20:04 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     2024/01/16 20:20:04 [INFO] [<IP_ADDRESS>, mongodb-0.mongodb-endpoints, mongodb-0, juju-fde86c-0.lxd] acme: Obtaining bundled SAN certificate given a CSR
unit-route53-lego-k8s-0: 20:20:04 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     2024/01/16 20:20:04 Could not obtain certificates:
unit-route53-lego-k8s-0: 20:20:04 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     	acme: error: 400 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:unsupportedIdentifier :: NewOrder request included invalid non-DNS type identifier: type "ip", value "<IP_ADDRESS>"
unit-route53-lego-k8s-0: 20:20:04 INFO juju.worker.uniter.operation ran "certificates-relation-changed" hook (via hook dispatching script: dispatch)
unit-route53-lego-k8s-0: 20:19:16 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
controller-0: 20:19:59 INFO juju.worker.remoterelations cmr start "remote-28278a2ce0cf429a88ad43a0c5d7f161"
unit-route53-lego-k8s-0: 20:20:00 INFO juju.worker.uniter.operation ran "certificates-relation-created" hook (via hook dispatching script: dispatch)
unit-route53-lego-k8s-0: 20:20:00 INFO juju.worker.uniter.operation ran "certificates-relation-joined" hook (via hook dispatching script: dispatch)
unit-route53-lego-k8s-0: 20:20:01 WARNING unit.route53-lego-k8s/0.juju-log certificates:0: Relation data did not pass JSON Schema validation: {'egress-subnets': '<IP_ADDRESS>/32', 'ingress-address': '<IP_ADDRESS>', 'private-address': '<IP_ADDRESS>'}
unit-route53-lego-k8s-0: 20:20:01 INFO juju.worker.uniter.operation ran "certificates-relation-changed" hook (via hook dispatching script: dispatch)
unit-route53-lego-k8s-0: 20:20:02 INFO unit.route53-lego-k8s/0.juju-log certificates:0: Received Certificate Creation Request for domain <IP_ADDRESS>
unit-route53-lego-k8s-0: 20:20:03 ERROR unit.route53-lego-k8s/0.juju-log certificates:0: Exited with code 1. Stderr:
unit-route53-lego-k8s-0: 20:20:03 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     2024/01/16 20:20:02 No key found for account<EMAIL_ADDRESS>Generating a P256 key.
unit-route53-lego-k8s-0: 20:20:03 ERROR unit.route53-lego-k8s/0.juju-log certificates:0:     2024/01/16 20:20:02 Saved key to /tmp/.lego/accounts/acme-v02.api.letsencrypt.org/<XXX><EMAIL_ADDRESS>
To Reproduce
# Step 1 set up k8s cloud + controller
# I will not demo this, but there are multiple resources online how to do this

# Step 2 deploy and configure charm
juju add-model <k8s-model-name>
juju deploy route53-lego-k8s
juju config route53-lego-k8s aws_region=<>
juju config route53-lego-k8s aws_hosted_zone_id=<>
juju config route53-lego-k8s aws_access_key_id=<>
juju config route53-lego-k8s aws_secret_access_key=<>
juju config route53-lego-k8s email=<>

# step 3 deploy your VM DB
juju switch <vm-controller-name>
juju add-model <vm-model-name>
juju deploy <vm-charm-name>

# step 4 cross model integration
juju switch <k8s-controller-name>
juju offer route53-lego-k8s:certificates certs-offer
juju switch <vm-controller-name>
juju consume <k8s-controller-name>:admin/<k8s-model-name>.certs-offer
juju integrate <vm-charm-name> certs-offer

Expected behavior

Screenshots

Logs

Environment

Charm / library version (if relevant): Revision 7, channel stable
Juju version 3.1.6
Cloud Environment: LXD + Microk8s
Kubernetes version (output from kubectl version --short): Client Version: v1.28.3

Additional context

@gruyaume thanks for your input here. And for your patience in my understanding.
From my limited understanding here the CSR is done by the charm, there is nothing different for me to try on my end. Is that correct :)

I or somebody else in the team will spend more time looking at this in the coming days. Generally speaking, the CSR is being written by the charm requiring TLS certs, MongoDB in this example. It looks like MongoDB adds additional SAN's in its CSR that are not accepted by the ACME server because they are IP addresses. The code in question seems to be here:

https://github.com/canonical/mongodb-operator/blob/6/edge/lib/charms/mongodb/v0/mongodb_tls.py#L250

Thank you for pointing this out (along with your expertise + thorough explanation), cannot help but to be curious on my own side. Looking into this now :)

No luck, I tried removing the ip address here so that the IP address is only set through the sans ip arg
and repeating the same steps I got the same error. 🤔

@gruyaume Wow thank you for your indepth work here. So the way I see it is there are three things that should be changed on MongoDB side:

CSR must change the subject name to be the same domain as the one in the AWS hosted zone.
CSR should omit the SANS IPS
MongoDB must handle secrets in a way that large secrets can be stored

I appreciate your patience with my lack of expertise on TLS, but are 1&2 changes that are only a requirement for Let's Encrypt, or will this be true across many/most/all CA's? Ideally my charm can be flexible/not engineered for one specific use case

@MiaAltieri I would go ahead and close this issue, if you find problems with the Route53 charm, feel free to open a new bug.


Update netty-tcnative-boringssl-static to 2.0.40.Final

Updates io.netty:netty-tcnative-boringssl-static from 2.0.39.Final to 2.0.40.Final.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.netty", artifactId = "netty-tcnative-boringssl-static" } ]

labels: library-update

Superseded by #405.


feat(astro-when): Use new injectTypes utility when available

Closes #156

!preview inject-types

!snapshot inject-types

addDts can only be used on astro:config:setup and I'll only know if the injectTypes will be available on the astro:config:done. I might make something about this separately


Mi matrix

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

147 of 154 (95.45%)  changed or added relevant lines in 1 file are covered.
144 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-2.2%) to 87.068%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

smt/surrogate_models/krg_based.py
147
154
95.45%

Files with Coverage Reduction
New Missed Lines
%

smt/sampling_methods/lhs.py
1
94.03%

smt/utils/kriging_utils.py
143
70.95%

Totals

Change from base Build<PHONE_NUMBER>:
-2.2%

Covered Lines:
5211

Relevant Lines:
5985

💛  - Coveralls


Update NatsMessage

Removed unwanted code

Somethings up with travis, looks like an obvious clean up so I don't think it is the code. Now the question is can I remember to bring it in or move it to a branch, git will not defeat me.

Ok, looks like the travis issue is a bug on their side.
I created a branch for 2.4.2. Can you move this PR to that branch and I will merge it.


Move BatchFeatureAnnotator

Currently this is in async_annotators within the supervision directory. It should be split out under features.

This issue will be addressed in the annotation refactor which will support multi-task learning. Closing this issue for now.


add multiple zone support to supervisor function

add ability to monitor multiple zones at once, each with it's own input parameters.

superceded by #501 closing this issue.


fix: use and operator instead of semicolon to run unit tests

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request base (cb@e8f1494). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@          Coverage Diff          @@
##             cb   #12712   +/-   ##
=====================================
  Coverage      ?   47.61%
=====================================
  Files         ?      842
  Lines         ?    38302
  Branches      ?     7833
=====================================
  Hits          ?    18239
  Misses        ?    18441
  Partials      ?     1622

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Operate on requests via id key

The command line tool (and perhaps other clients) should be able to operate on a thread by it's locally unique key value. This would greatly improve the UX.
re: https://gist.github.com/icidasset/249ade688f39a070214f182e43636b31

Would this be difficult to implement? Maybe I can make a PR for this.


Added clear and consise comments to explaianble.ipynb

can u review @ombhojane

Haa sure can u add label 2. I have added detailed, clear comments and made it beginner friendly
I will add all the code cell in the comment right away


[SPARK-30468][SQL] Use multiple lines to display data columns for show create table command

What changes were proposed in this pull request?
Currently data columns are displayed in one line for show create table command, when the table has many columns (to make things even worse, columns may have long names or comments), the displayed result is really hard to read.
To improve readability, we print each column in a separate line. Note that other systems like Hive/MySQL also display in this way.
Also, for data columns, table properties and options, we put the right parenthesis to the end of the last column/property/option, instead of occupying a separate line.
Why are the changes needed?
for better readability
Does this PR introduce any user-facing change?
before the change:
spark-sql> show create table test_table;
CREATE TABLE `test_table` (`col1` INT COMMENT 'This is comment for column 1', `col2` STRING COMMENT 'This is comment for column 2', `col3` DOUBLE COMMENT 'This is comment for column 3')
USING parquet
OPTIONS (
  `bar` '2',
  `foo` '1'
)
TBLPROPERTIES (
  'a' = 'x',
  'b' = 'y'
)

after the change:
spark-sql> show create table test_table;
CREATE TABLE `test_table` (
  `col1` INT COMMENT 'This is comment for column 1',
  `col2` STRING COMMENT 'This is comment for column 2',
  `col3` DOUBLE COMMENT 'This is comment for column 3')
USING parquet
OPTIONS (
  `bar` '2',
  `foo` '1')
TBLPROPERTIES (
  'a' = 'x',
  'b' = 'y')

How was this patch tested?
modified existing tests

Test build #116377 has started for PR 27147 at commit af3cb83.

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/21169/
Test PASSed.

Test build #116379 has started for PR 27147 at commit 3943861.

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/21171/
Test PASSed.

Test build #116380 has started for PR 27147 at commit ed75605.

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/21172/
Test PASSed.

Test build #116377 has finished for PR 27147 at commit af3cb83.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/116377/
Test FAILed.

Test build #116379 has finished for PR 27147 at commit 3943861.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/116379/
Test FAILed.

Test build #116380 has finished for PR 27147 at commit ed75605.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/116380/
Test FAILed.

Test build #116391 has started for PR 27147 at commit da12c1b.

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/21182/
Test PASSed.

Test build #116393 has started for PR 27147 at commit fc1e63f.

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/21184/
Test PASSed.

Probably fine. CC @gengliangwang

also cc @maropu

Test build #116393 has finished for PR 27147 at commit fc1e63f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/116393/
Test FAILed.

Test build #116391 has finished for PR 27147 at commit da12c1b.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/116391/
Test FAILed.

retest this please

Test build #116431 has started for PR 27147 at commit fc1e63f.

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/21219/
Test PASSed.

Test build #116435 has started for PR 27147 at commit 2d590f8.

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/21223/
Test PASSed.

Test build #116431 has finished for PR 27147 at commit fc1e63f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/116431/
Test FAILed.

Test build #116435 has finished for PR 27147 at commit 2d590f8.

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/116435/
Test PASSed.


Aggregate reach in Venn diagram regions given publishers

@matthewclegg @jiayu-google All suggestions are incorporated. Please take a look. Thanks!


error :  it has to be a leader!!!

Describe the bug
I started a node, then set the node as leader, then ctrl+c crashed the node, and then the following error occurred when restarting the node.
thread 'tokio-runtime-worker' panicked at /Users/simonyi/.cargo/git/checkouts/openraft-0677bbb78cc57964/4b78dd3/openraft/src/core/raft_core.rs:797:13:
internal error: entered unreachable code: it has to be a leader!!!

Is this normal logic or a bug?

A panic is a logic bug.
Could you provide the debug level logs? This way I can see what's happening when it panicked.

@drmingdrmer
2023-11-04T03:03:21.296813Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main: openraft::core::raft_core: raft node is initializing
2023-11-04T03:03:21.296848Z  INFO tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:startup: openraft::engine::engine_impl: startup: state: RaftState { vote: UTime { data: Vote { leader_id: LeaderId { term: 1, node_id:<PHONE_NUMBER>718541494 }, committed: true }, utime: Some(Instant { tv_sec: 464375, tv_nsec: 700082041 }) }, committed: Some(LogId { leader_id: LeaderId { term: 10000, node_id: 2 }, index: 10000 }), purged_next: 10001, log_ids: LogIdList { key_log_ids: [LogId { leader_id: LeaderId { term: 10000, node_id: 2 }, index: 10000 }] }, membership_state: MembershipState { committed: EffectiveMembership { log_id: None, membership: Membership { configs: [], nodes: {} }, voter_ids: {} }, effective: EffectiveMembership { log_id: None, membership: Membership { configs: [], nodes: {} }, voter_ids: {} } }, snapshot_meta: SnapshotMeta { last_log_id: Some(LogId { leader_id: LeaderId { term: 10000, node_id: 2 }, index: 10000 }), last_membership: StoredMembership { log_id: None, membership: Membership { configs: [], nodes: {} } }, snapshot_id: "10000-2-10000-1" }, server_state: Learner, accepted: Accepted { leader_id: LeaderId { term: 0, node_id: 0 }, log_id: None }, io_state: IOState { building_snapshot: false, vote: Vote { leader_id: LeaderId { term: 1, node_id:<PHONE_NUMBER>718541494 }, committed: true }, flushed: LogIOId { leader_id: LeaderId { term: 0, node_id: 0 }, log_id: None }, applied: Some(LogId { leader_id: LeaderId { term: 10000, node_id: 2 }, index: 10000 }), purged: Some(LogId { leader_id: LeaderId { term: 10000, node_id: 2 }, index: 10000 }) }, snapshot_streaming: None, purge_upto: Some(LogId { leader_id: LeaderId { term: 10000, node_id: 2 }, index: 10000 }) }
2023-11-04T03:03:21.297285Z  INFO tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:startup: openraft::engine::engine_impl: startup: is_leader: true
2023-11-04T03:03:21.297298Z  INFO tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:startup: openraft::engine::engine_impl: startup: is_voter: false
2023-11-04T03:03:21.299352Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:startup:calc_server_state: openraft::raft_state: states is_member=false is_leader=true is_leading=true
2023-11-04T03:03:21.299383Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:startup: openraft::engine::handler::server_state_handler: update_server_state_if_changed id=7395302447718541494 prev_server_state=Learner server_state=Learner
2023-11-04T03:03:21.300196Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:startup: openraft::engine::handler::replication_handler: openraft::engine::handler::replication_handler::ReplicationHandler<_>::update_local_progress upto=10000-2-10000
2023-11-04T03:03:21.300225Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:startup:initiate_replication: openraft::engine::handler::replication_handler: openraft::engine::handler::replication_handler::ReplicationHandler<_>::initiate_replication progress=VecProgress { quorum_set: Joint { data: [], _p: PhantomData<(u64, alloc::vec::Vec<u64>)> }, granted: None, voter_count: 0, vector: [], stat: Stat { update_count: 0, move_count: 0, is_quorum_count: 0 } }
2023-11-04T03:03:21.300296Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:run_engine_commands: openraft::core::raft_core: queued commands: start...
2023-11-04T03:03:21.300307Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:run_engine_commands: openraft::core::raft_core: queued commands: RebuildReplicationStreams { targets: [] }
2023-11-04T03:03:21.300317Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:run_engine_commands: openraft::core::raft_core: queued commands: end...
2023-11-04T03:03:21.300325Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:run_engine_commands: openraft::core::raft_core: run command: RebuildReplicationStreams { targets: [] }
2023-11-04T03:03:21.300346Z DEBUG tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:run_engine_commands: openraft::core::raft_core: condition: None
2023-11-04T03:03:21.300382Z  INFO tokio-runtime-worker ThreadId(06) new{cluster=morse_brain}:RaftCore{id=7395302447718541494 cluster=morse_brain}:main:run_engine_commands:remove_all_replication: openraft::core::raft_core: remove all replication
thread 'tokio-runtime-worker' panicked at /Users/simonyi/.cargo/git/checkouts/openraft-0677bbb78cc57964/4b78dd3/openraft/src/core/raft_core.rs:797:13:
internal error: entered unreachable code: it has to be a leader!!!

What steps did you take to arrive at this particular status?
Did you manually fakes these status for Openraft?
From the provided log, it appears that the membership is empty:
Membership { configs: [], nodes: {} }, voter_ids: {} }

and the vote is non-empty:
Vote { leader_id: LeaderId { term: 1, node_id:<PHONE_NUMBER>718541494 }

The lack of initialization for Openraft is evident, since an empty membership is not permissible when initializing Openraft.
Openraft's handling of this unexpected scenario seems inconsistent. In this context:

calc_server_state() returns Learner.
But is_leader() returns true.

Given that calc_server_state() returns Learner, Openraft does not initialize the Leader state, which accounts for the encountered panic.
To resolve this issue, I will modify calc_server_state() to return Lender, which should help achieve internal consistency.

The following PR is merged. In your case, the node should start as a Learner now. Please confirm that the issue is addressed.

#924


Too many empty lines in log in either this mod or its deps

Trying this mod in both MP and SP, there are too many empty logs especially when fighting the raid.
I actually didn't find logger usage which empty lines in both this mod and its dependencies. but I am sure it's related to this mod or dungeon libraries, (geckolib not possible because it's not a server-side mod)

https://paste.ee/p/qJUEe

Where did you get this?
minecraft server hosting i presume!

@BraveCaperCat The log is printed in both client and server consoles. I got the mod from Curseforge.
Anyway, the mod has some issues that can cause server hang issues.(cannot find log during the issue). So I already remove the mods


support Python 3.8

https://ci.appveyor.com/project/touilleMan/winfspy/builds/28795168/job/cl7s80fug8gyxfh8 :'(

More info:

https://docs.python.org/3.8/library/os.html#os.add_dll_directory
https://docs.python.org/3.8/whatsnew/3.8.html#bpo-36085-whatsnew


Failed to batch ingest runs: LangSmithError('Failed to POST https://api.smith.langchain.com/runs/batch in LangSmith API. HTTPError('403 Client Error: Forbidden for url: https://api.smith.langchain.com/runs/batch', '{"detail":"Forbidden"}')')

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
Failed to batch ingest runs: LangSmithError('Failed to POST https://api.smith.langchain.com/runs/batch in LangSmith API. HTTPError('403 Client Error: Forbidden for url: https://api.smith.langchain.com/runs/batch', '{"detail":"Forbidden"}')')
Description
I am using crewai along with langsmith and the error looks like a server side error.
System Info
platform windows
python 3.11.4

have set LangSmith API keys? This says it's a 403

have set LangSmith API keys? This says it's a 403

Yes, I have added them in the .env file like this LANGCHAIN_API_KEY=<MY_API_KEY>

The issue is solved, I reinstalled the packages in the environment, and it worked smoothly afterwards.

OK great! Going to close the issue!

I have the same issue when I am running my app on a local server (a Flask app) but not using the same environment and API Key on Jupiter Notebook.

I'm getting the error as well. I'm getting it when I run in streamlit, but I don't know if that is relevant. I set the environment variables the same way I set them in other places.

Same issue here! I have set all the envs correct  but still getting that 403 error, even I reinstalled all the packages and also  used new API key.

The issue for me was that I needed to set the endpoint. This was not obvious to me.
os.environ["LANGCHAIN_ENDPOINT"] = "https://eu.api.smith.langchain.com/"

I have this issue sporadically. maybe too much data?

Having the same issue

Same issue.

Same issue encountered today

I'm facing a similar issue (authentication failure), but I don't want to send any telemetry to the API, so I tried to disable the tracing by seeing it false (3 different ways):
tracing_v2_enabled = lambda: False
on my env variable..:
export LANGCHAIN_TRACING="false"
..and
import os os.environ["LANGCHAIN_TRACING"] = "false"
even though, none of then worked.
=[

The name of the environment variable hou have to set to false is LANGCHAIN_TRACING_V2

The name of the environment variable hou have to set to false is LANGCHAIN_TRACING_V2

Thank you @apisani1!


unbound 1.13.0 abort

unbound[22274]: [err] evmap.c:367: Assertion nread >= 0 failed in evmap_io_del

It seems you are experiencing the same issue, which has been reported as #393 .

It seems you are experiencing the same issue, which has been reported as #393 .

This is on Foobar Linux 7 (based on rhel7).

This is on Foobar Linux 7 (based on rhel7).

Hi @bleve,
Is this issue fixed for you with version 1.13.1?

Indeed it looks like it is fixed in 1.13.1 which we have been running since the release.


only test_shard_*.hdf5

Hi after running
python generate_samples.py \
    --dir ./enwiki_books_shards_merge \
    -o ./enwiki_books_samples \
    --dup_factor 10 \
    --seed 42 \
    --vocab_file ./vocab.txt \
    --do_lower_case 1 \
    --masked_lm_prob 0.15 \
    --max_seq_length 128 \
    --model_name bert-large-uncased \
    --max_predictions_per_seq 20 \
    --n_processes 32

I only got test_shard_.hdf5 in the ./enwiki_books_samples. No train_shard_.hdf5.
Do you have any ideas?
Thanks!

Just rename according to the ratio you need. That's how I solved it.


Question related to expandable grid or column groups

I have a data list. When there is a change in this list, for example, I save the insertion and update operations as "json". Which method should I use when displaying this json data? Grid inside the grid, "column groups" or expandable grid?

I need to set it to coincide with each line.

Neither :). I personally dislike expandable grids and grid inside the grid as a UI solution in general. I prefer overlay for this purpose, or sidebar panels. It is up to you what you use, generally if data is similar as the one in the grid, use expendable grid, here is an example https://w2ui.com/web/demos/#/grid/7
Please do not submit questions here. Stackoverflow, or the like, man!


Can't run phar on windows ?

php mageekguy.atoum.phar --testIt
Error: Unable to find PHP executable
php -v
PHP 5.3.5 (cli) (built: Jan  6 2011 17:54:09)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies
with Xdebug v2.1.0, Copyright (c) 2002-2010, by Derick Rethans
Same thing with the php :
php atoum/scripts/runner.php
Error: Unable to find PHP executable

Fixed with the env variables :
PHPBIN=C:\UwAmp\bin\php\php-5.3.5\php.exe


⚠ Jenkins Plugins Artifactory has degraded performance

In d8e1c5e, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1275 ms

Resolved: Jenkins Plugins Artifactory performance has improved in b1f7fc8 after 12 minutes.


Looking up a deactivated widget's ancestor is unsafe

To safely refer to a widget's ancestor in its dispose() method

my mistake

I released https://pub.dev/packages/flutter_awesome_select with fixed null safety.
Could you check that everything works for you?


score storage unit test added

adds  unit tests for score storage interface

It's a typo, I will correct it. It should be ScoreStorageTests
On Sat, Sep 16, 2023, 10:04 PM Kirill Taran @.***>
wrote:

@.**** commented on this pull request.
In lib/src/test/java/space/taran/arklib/user/ScopedStorageTests.kt
https://github.com/ARK-Builders/arklib-android/pull/90#discussion_r1327981462
:

@@ -0,0 +1,78 @@
+package space.taran.arklib.user

Is the file named ScopedStorageTests.kt intentionally?
—
Reply to this email directly, view it on GitHub
https://github.com/ARK-Builders/arklib-android/pull/90#pullrequestreview-1629984257,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS7B5VLDIROY4WMI7XKWODX2XIIFANCNFSM6AAAAAA4ROW3ME
.
You are receiving this because you authored the thread.Message ID:
@.***>

@mdrlzy

Enable actions in your fork and add unit tests to CI

We also can be approve here, after the latest commit in main. Approved, should build now.

@tanaytandon12 we've fixed integration tests (although we don't use them now, but we want to keep this stub).
Unit tests do run now, too (just copied your commit).
Please, pull main into your fork (commit 80b427f3ce22292116da244629d7a267d3b79d4b).


Spark 0.1

But the database update must follow a strict rule: Title, SubTitle,
Text, Image. They are all string.

Now edit on this one


<EMAIL_ADDRESS>download via aria2 failed

Url  provided by scoop is outdated and untagged: Invalid Version: untagged-548d639174b880738fbd
WARN  Scoop uses 'aria2c' for multi-connection downloads.
WARN  Should it cause issues, run 'scoop config aria2-enabled false' to disable it.
Installing 'blitz' (1.6.51) [64bit]
Starting download with aria2 ...
Download: 05/05 14:47:20 [ERROR] CUID#8 - Download aborted. URI=https://dl.blitz.gg/download/1.6.51/Blitz-1.6.51-full.nuDownload: Exception: [AbstractCommand.cc:351] errorCode=22 URI=https://dl.blitz.gg/download/1.6.51/Blitz-1.6.51-full.nupDownload: Download Results:
Download: gid   |stat|avg speed  |path/URI
Download: ======+====+===========+=======================================================
Download: d004b0|ERR |       0B/s|D:/Users/<user>/scoop/cache/blitz#1.6.51#https_dl.blitz.gg_download_1.6.51_Blitz-1.6.51-full.nupkg
Download: Status Legend:
Download: (ERR):error occurred.
Download: aria2 will resume download if the transfer is restarted.
Download: If there are any errors, then see the log file. See '-l' option in help/man page for details.

ERROR Download failed! (Error 22) HTTP response header was bad or unexpected
ERROR https://dl.blitz.gg/download/1.6.51/Blitz-1.6.51-full.nupkg
    referer=https://dl.blitz.gg/download/1.6.51/
    dir=D:\Users\<user>\scoop\cache
    out=blitz#1.6.51#https_dl.blitz.gg_download_1.6.51_Blitz-1.6.51-full.nupkg

ERROR & 'D:\Users\<user>\scoop\apps\aria2\current\aria2c.exe' --input-file='D:\Users\<user>\scoop\cache\blitz.txt' --user-agent='Scoop/1.0 (+http://scoop.sh/) PowerShell/7.1 (Windows NT 10.0; Win64; x64; Core)' --allow-overwrite=true --auto-file-renaming=false --retry-wait=4 --split=16 --max-connection-per-server=16 --min-split-size=4M --console-log-level=warn --enable-color=false --no-conf=true --follow-metalink=true --metalink-preferred-protocol=https --min-tls-version=TLSv1.2 --stop-with-process=27328 --continue --summary-interval 0

Maybe change back to -nightly build mentioned by @Calinou in #41.
Also they have XML like file with versions in https://blitz-stable.blitz.gg/ , with current stable link provided by chrome.

It looks like .nupkg files aren't available anymore: https://dl.blitz.gg/download/1.14.9/Blitz-1.14.9-full.nupkg
I'm not sure if we can still support Blitz in the first place.


Vulnerability roundup 107: ncurses-6.2: 1 advisory [8.8]

search, files

[ ] CVE-2021-39537 CVSSv3=8.8 (nixos-21.05, nixos-unstable)

CVE details
CVE-2021-39537
An issue was discovered in ncurses through v6.2-1. _nc_captoinfo in captoinfo.c has a heap-based buffer overflow.

Scanned versions: nixos-21.05: 3b1789322fc; nixos-unstable: 34ad3ffe08a.

Fix in unstable: #146685. Backport to 21.11 would require many build fixes in other packages too.


Feature/disable signup

what

For the EVTR module to fit our needs, we want to utilize the users generated by our CaC rather than click-ops signup users.

why

To restrict EVTR to utilize users generated by CaC rather than allowing for signup

references

N/A

/test

/test


Expose a method to create an Operation.

What
Having a way to create an gax.Operation object from an operation name would help the google-cloud-node guys move forward in eliminating their grpcOperation object.

Need this for GoogleCloudPlatform/google-cloud-node#1688

I'll work on this when I get in tomorrow morning.

Thanks for doing this, but after trying to use it, I don't think it's something that our users would want or even be able to use yet. The user would have to construct their own longrunning descriptor (knowing in advance what they're going to use the operation for, and knowing which protos to use, etc.). In order to do that, they'd have to construct their own operations client. As it is, I don't see anyone using this.
Longrunning descriptors and an operations client are built within the generated gapic code, but they aren't exposed...This method would be much more usable if the service clients in the generated gapic code exposed their longrunning descriptors and their operations client. e.g. in the generated gapic service client constructor change
var longrunningDescriptors = ...

to
this.longrunningDescriptors = ...

and
var operationsClient = ...

to
this.operationsClient = ...

These changes would make something like this possible:
const operation = gax.operation(
  { name: 'operations/1234' },
  cloudFunctionsServiceClient.longrunningDescriptors.createFunction,
  { /* custom backoff settings (which have to be constructed by hand :/ */ }
);

cc @stephenplusplus @jmuk
While we're at it, can we get createBackoffSettings exposed on the top-level gax module?

Assuming
const operation = gax.operation(
  { name: 'operations/1234' },
  cloudFunctionsServiceClient.longrunningDescriptors.createFunction,
  { /* custom backoff settings */ }
);

becomes possible, google-cloud-node could implement something like this:
Functions.prototype.operation = function (config, type, backoffSettings) {
  if (is.string(config)) {
    config = { name: config };
  }
  var descriptor;
  switch(type) {
    case 'create':
      descriptor = this.api.Functions.longrunningDescriptors.createFunction;
      break;
    case 'update':
      descriptor = this.api.Functions.longrunningDescriptors.updateFunction;
      break;
    case 'delete':
      descriptor = this.api.Functions.longrunningDescriptors.deleteFunction;
      break;
  }
  if (!backoffSettings) {
    backoffSettings = /* some default, e.g. gax.createBackoffSettings(...) */;
  }
  return gax.operation(config, descriptor, backoffSettings);
};

then the user can simply do the following:
var operation = functions.operation('operations/1234', 'create');

operation.on('complete', ...);

which is quite usable.

Any chance the operation name has any clue as to what type of operation it is? Just trying to avoid the type argument.

Operations names are just operations/1234abcd5678efgh. The IDs are opaque to the user. I don't even know if they mean anything on the server. Probably just generated IDs.

@larndrito what's the status of this issue? Is it already resolved?

oops, typo. @landrito ?

This can be resolved.
Operations can't be created simply by name but also by passing in a longrunning descriptor. We are exposing the longrunning descriptors made in the clients so an operation can be created as such.
ie:
var op = gax.operation(
  { name: 'operation/1230'},
  some_client.longrunningDescriptors['someMethod']);


Adding Google AIY to DietPi

I have spent most of the day trying to add the Google Assistant AIY code to DietPi and have had limited success. I have been able to write an installation entry for DietPi, which is working up until the point that the script and /or service are started. It gets all the way through the installation and OAUTH stuff, but then fails because of audio issues and also button failure.
The pre-configured .iso image works flawlessly on my MagPi AOI kit.
If I start it up with python3 src/main.py, I get the following errors:
(env) root@AIY:/mnt/dietpi_userdata/voice-recognizer-raspi# python3 src/main.py
[2017-07-10 00:45:43,780] WARNING:main:File /tmp/status-led specified for --led-fifo does not exist.
[2017-07-10 00:45:43,792] INFO:audio:started recording
[2017-07-10 00:45:43,798] INFO:main:ready...
Press the button on GPIO 23 then speak, or press Ctrl+C to quit...
ALSA lib pcm_dsnoop.c:618:(snd_pcm_dsnoop_open) unable to open slave
arecord: main:722: audio open error: No such file or directory
[2017-07-10 00:45:43,804] ERROR:audio:Microphone recorder died unexpectedly, aborting...

root@AIY:/mnt/dietpi_userdata/voice-recognizer-raspi# python3 checkpoints/check_audio.py
Failed to find the voiceHAT soundcard. Refer to HACKING.md for how to
setup the voiceHAT driver: https://git.io/v99yK
Press Enter to close...

It seems that the drivers either did not install or configure properly, in order to get the Voice Hat working...
Am I missing something? Perhaps I am lacking some dependencies, or something.
Please look at this GitHub issue for further details.

root@AIY:/mnt/dietpi_userdata/voice-recognizer-raspi# systemctl status voice-recognizer.service
● voice-recognizer.service - voice recognizer
   Loaded: loaded (/lib/systemd/system/voice-recognizer.service; enabled)
   Active: failed (Result: start-limit) since Mon 2017-07-10 01:24:53 UTC; 15min ago
  Process: 583 ExecStart=/mnt/dietpi_userdata/voice-recognizer-raspi/env/bin/python3 -u src/main.py (code=exited, status=217/USER)
 Main PID: 583 (code=exited, status=217/USER)
   CGroup: /system.slice/voice-recognizer.service

root@AIY:/mnt/dietpi_userdata/voice-recognizer-raspi# cat /etc/asound.conf
options snd_rpi_googlemihat_soundcard index=0

pcm.softvol {
    type softvol
    slave.pcm dmix
    control {
        name Master
        card 0
    }
}

pcm.micboost {
    type route
    slave.pcm dsnoop
    ttable {
        0.0 30.0
        1.1 30.0
    }
}

pcm.!default {
    type asym
    playback.pcm "plug:softvol"
    capture.pcm "plug:micboost"
}

ctl.!default {
    type hw
    card 0
}

root@AIY:/mnt/dietpi_userdata/voice-recognizer-raspi# aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
softvol
micboost
default
sysdefault:CARD=ALSA
    bcm2835 ALSA, bcm2835 ALSA
    Default Audio Device
dmix:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct sample mixing device
dmix:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct sample mixing device
dsnoop:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct sample snooping device
dsnoop:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct sample snooping device
hw:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct hardware device without any conversions
hw:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct hardware device without any conversions
plughw:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Hardware device with all software conversions
plughw:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Hardware device with all software conversions

root@AIY:/mnt/dietpi_userdata/voice-recognizer-raspi# arecord -l
**** List of CAPTURE Hardware Devices ****
root@AIY:/mnt/dietpi_userdata/voice-recognizer-raspi# arecord -L
null
    Discard all samples (playback) or generate zero samples (capture)
softvol
micboost
default
root@AIY:/mnt/dietpi_userdata/voice-recognizer-raspi# aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
softvol
micboost
default
sysdefault:CARD=ALSA
    bcm2835 ALSA, bcm2835 ALSA
    Default Audio Device
dmix:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct sample mixing device
dmix:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct sample mixing device
dsnoop:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct sample snooping device
dsnoop:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct sample snooping device
hw:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct hardware device without any conversions
hw:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct hardware device without any conversions
plughw:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Hardware device with all software conversions
plughw:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Hardware device with all software conversions

Could you run the checkpoint scripts:
https://github.com/google/aiyprojects-raspbian/tree/master/checkpoints

Thank you for the reply, ensonic.
I can't look at it again, right now, but i actually did manually run all the checkpoint scripts and if I recall correctly, they all failed. (I was up very late last night fiddling around with this thing.)
I'll try the lsmod ASAP, too.
I've been given a couple of pointers over at my other issue page, so I'll try those suggestions, too.

I think we've identified the problem: It's to do with file paths, mainly.
Dietpi uses the directory /DietPi/ to hold a ramdisk and copy of config.txt. The changes need to be applied there.
Also, there are a few hard-coded paths in the code, which will need rectifying at your end, I think:
https://github.com/Fourdee/DietPi/issues/1065#issuecomment-314157213
Thanks,
Rich.

Just to let you know; I've got it working, with the exception of the system services, because they all contain hard-coded links to /home/pi. This will need sorting out to ensure better compatibility with other distros, but, yeah; works like a charm!
Thanks for your input.

install-services.sh uses sed to change the path in the service files to the correct value, so it should be portable. How did it fail in your case?
install-alsa-config.sh could be generic - I've filed #95 to track this, thanks for finding it!

Thanks so much for replying. :+1:

install-services.sh uses sed to change the path in the service files to the correct value, so it should be portable. How did it fail in your case?

I'm not a coder at all and even my rudimentary script-kiddie skills are not up to the task of keeping up with you guys, but I think that the fact that the sed command in question starts  sed "s:/home/pi/voice-recognizer-raspi... might be a problem:
...
for service in systemd/*.service; do
sed "s:/home/pi/voice-recognizer-raspi:${repo_path}:g" "$service"
> "/lib/systemd/system/$(basename "$service")"
done
...
Should it use $HOME? Or maybe some variation of the line from the same script, which sets the base directory:
cd "$(dirname "${BASH_SOURCE[0]}")/.."
...and go up one level from that; but apply for all of the system services.
I'm not sure if this is viable and I'm not sure that I even know what I'm saying, myself; but rectifying this could potentially prevent (some) future issues of this kind.
In the case of DietPi, everything is run under Root, so all stuff directed to /home/user/ ends up in /root/ and all stuff directed to /home/pi/ fails. Hence the problem. This was the author's decision and I'm pretty sure that this has been debated, but I'm not qualified to weigh in. The point is that if anything is hard-coded to point to, or to look in /home/pi/ (or any other arbitrary directory); chaos ensues. If /voice-recognizer-raspi/ was dropped into /home/richard/, we would be dealing with the same sort of problem.
Please forgive me if I am rattling on, but I need to educate myself and I hope that I can, in some small way, help both of the projects that I dragged into this issue. It's just that it's so easy and so much of a time-saver, to use Dietpi to set up and connect applications and services, that I find it hard to beat. Also, I have had so much more fun playing around with the AIO kit than I ever did with using the Google Assistant on a phone.

I think that the fact that the sed command in question starts sed "s:/home/pi/voice-recognizer-raspi... might be a problem:

The reason for this is that the files themselves contain "/home/pi/..." in their current state. This command should replace "/home/pi/..." with the correct path "${repo_path}" as it installs the scripts. You can try running the script and looking at /lib/systemd/system/voice-recognizer.service to see if it has the right paths.
However, you will need to manually edit the files voice-recognizer.service, status-led.service and status-monitor.service in /lib/systemd/system/ to remove the line User=pi. (if this works for you, that could be made automatic in install-services.sh)
You may also have other issues running as root - I seem to remember someone trying this before and having some problems before getting it working, but can't find the thread. Let us know how it goes!

Please forgive me if I am rattling on

Not at all - we're happy to have the feedback!

Well, I got it all working now. I just had to add a few sed commands to the installer code to change the file paths and remove user=pi from the relevant services. If you are interested, look here:
https://github.com/Fourdee/DietPi/issues/1065#issuecomment-314837634
The only issues I have now are a lack of Power Off and Reboot commands and the silent alarm, mentioned in another issue, here.
Thanks,
Rich.

I think #156 resolved the issue with the new voicekit branch, so hopefully everything's working now.


sourceRoot doesn't work for files in sub folders

I have stored my source files in a number of sub folders.
It looks like the sourceRoot parameter doesn't correctly handle those files. It doesn't consider the relative part beginning at the sources' root up to their actual location when creating the source map entry.

Please refer to this issue for reference:
https://github.com/Microsoft/vscode/issues/4705

+1 I've been struggling with this also

:+1:

Any solution??

This solution worked for me on Ubuntu but may not work on Windows, haven't tested that.
.pipe(sourcemaps.write('.', {
        includeContent: false,
        sourceRoot: function(file) {
            return '../'.repeat(file.relative.split('/').length) + 'src';
        }
    }))

Thanks @ckiely91 - I only change file.relative.split('/') to file.relative.split('\\') so that it also works under windows.

Yes, but I prefer to keep in mind that this is only a workaround. No-one out there is aware of that quirk. It should get fixed soon.

Hi
I've got same issue
Thanks @ckiely91. Your solution was very helpful.
Here is my full task for "Node.js targeted" TS. Hope it would be useful...
gulp.task('build', () => {
  const project = ts.createProject('tsconfig.json');
  return gulp.src('./app/**/*.ts')
    .pipe(sourcemaps.init())
    .pipe(ts(project))
    .js
    .pipe(sourcemaps.write('./', {
      includeContent: false,
      sourceRoot: file => `${'../'.repeat(file.relative.split(/^win/.test(process.platform) ? '\\' : '/').length)}app`
    }))
    .pipe(gulp.dest('./dist'));
});

I found following code in sources of plugin
    if (typeof options.sourceRoot === 'function') {
      sourceMap.sourceRoot = options.sourceRoot(file);
    } else {
      sourceMap.sourceRoot = options.sourceRoot;
    }

Looks like sourceMap passed to output as is without, resolution of extra ../

@zhakhalov, found that you can actually just use path.sep instead of /^win/.test(process.platform) ? '\\' : '/' to make it platform independent.

I agree that the sourceRoot option does not work as expected when assigning a string value and source files are located in sub directories.
Here's a workaround using the path util:
const path = require('path');
// ...
sourceRoot: (file) => {
	return path.join(path.relative(path.join(outputDir, path.dirname(file.relative)), '.'), sourceDir);
}

workaround ( version 2.2.0 ) didn't work for me.
I guess
var destSourceMapPath = path.join(file.cwd, options.destPath, mapFile);
should be changed to:
var destSourceMapPath = path.join(file.cwd, mapFile);
because mapFile already contains the destPath:
      var mapFile = path.join(destPath, file.relative) + '.map';

For whatever reason updating the sourceRoot as above didn't work for me so I updated the mapSources directly. Thanks to everyone for leading me to this!
mapSources: function(sourcePath, file) {
let relativeLocation = path.join(path.relative(path.join(outputDir, path.dirname(file.relative)), '.'), 'src/');
let relativeLocationToFile = path.join(relativeLocation, sourcePath);
return relativeLocationToFile;
}}))

The same problem when working with gulp-less. The less files in sub folders cannot pointing to less but css file.

+1

+1 anyone working on this?

Well, I had lots of trouble, trying to find the right combination to make it work. In the end I found a simple expression that worked for any combination of subdirectories, depth or relative location between the source and build directories:
const writeSourceMapsOptions = {
  sourceRoot: (file) => {
    return path.posix.relative(path.posix.dirname(file.relative), "");
  },
};

and then just pass it to .pipe(gulpSourceMaps.write(writeSourceMapsOptions)).
This works both both Istambul reports and the Node debugger.

@demurgos I wonder if you solution should become the default. Except, that it should work regardless of OS type. Feel free to add a PR with some specs.


Couldn't find _.Projections.Snapshot(SnapshotLicecycle) is the documentation outdated?

I am following the documentation here: https://martendb.io/events/projections/#snippet-sample_registering-quest-party
But I couldn't find this Snapshot method in marten 5: https://github.com/JasperFx/marten/blob/02d321ccb25b5bf62c5c7e5a9f7ea528e0d439f1/src/EventSourcingTests/Projections/inline_aggregation_by_stream_with_multiples.cs#L45
Is the documentation outdated? The closest I could find is _.Projections.Add<T>(ProjectionLifecycle.Inline);

Nevermind..., should have check the proj file first..., the sample code is using Marten 6 RC

@rosdi  The docs point to the latest. We will look at enabling docs for 4.x and 5.x. Currently there is only 3.x and the latest.


merge branches

Completed tests and refactoring in a minor branch. Merging back up the tree.

:tada: This PR is included in version 1.0.0 :tada:
Your semantic-release bot :package::rocket:


Add a property to disable prefetch read

What changes are proposed in this pull request?

We queried alluxio via impala, MaxDirectMemorySize was configured with 4G, but OOM appeared very quickly
impala caches a large number of file descriptors and also reads data from these files
I found that after reading the alluxio worker only once, the worker may send 64M (block size) of data to the client, causing the client to cache a large amount of data that the client may not use
how much data to send is not controlled by the client, the worker controls how many chunks to send at a time through grpc's isReady and tooManyPendingChunks
isreaby and tooManyPendingChunks are not || but && . I don't understand why they are set up so that if isreaby doesn't return false for a read, If the tooManyPendingChunks limit is reached, it is possible to continue sending data to the client
In fact, in my environment the worker sends 20 chunks (chunk size 1M) to the client
I want to add a configuration to turn off the aforementioned preread multiple chunks

Why are the changes needed?

Add a property alluxio.user.prefetch.read.enabled , client set false, the client only receives data of a certain size
Related issue： #18118

Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including

Add a property alluxio.user.prefetch.read.enabled, default is true, maintain original logic
If alluxio.user.prefetch.read.enabled set false,  the client only receives data of a chunk size

alluxio-bot, check this please

alluxio-bot, check this please

@lucyge2022 Could you please help core review it


Advanced cross-validation

Now the cross-validation is quite simple:

cross-validation should be implemented for tuner
cross-validation for the time-series should be supported

For now, it is finished
PR409 K-fold cross-validation for tabular data in Tuner implemented - cross validation for tabular data for tuner
PR363 Cross validation methods for time series  - cross validation for time series for composer and tuner
PR292 Cross validation - cross validation for tabular data for composer


Botton box causing Craft CMS to crash

Description
I ran a composer update to update Craft 3 CMS to 3.7.47; after the update was complete, my site was down, and I'm getting the error below from the CMS control panel. How can FIx this issue?
PHP Warning – yii\base\ErrorException
Declaration of verbb\buttonbox\fields\Colours::translatedOptions(): array should be compatible with craft\fields\BaseOptionsField::translatedOptions(bool $encode = false): array
Additional info

Plugin version: 3.0.2
Craft version: 3.7.47
Multi-site:  No

Additional context

I had this so reverted Craft CMS to v3.7.44 in the short run as it's a change in Craft that causes the error.
  "require": {
    "craftcms/cms": "3.7.44",

But that was because I couldn't work out how to get v3.1.0 as it seemed Packagist wasn't finding the latest version, then I realised I was still using supercool/buttonbox instead of verbb/buttonbox in my composer.
https://github.com/verbb/buttonbox/issues/46
You're using 3.0.2, but it was fixed in v3.1.0, so try that first and if all else fails revert the Craft version.

Indeed, fixed in 3.1.0. This was due to a Craft change between Craft <IP_ADDRESS> and Craft 3.7.46 (refer to https://github.com/verbb/buttonbox/issues/46)


Newton

Start working on supporting newton.

Getting closer. Ironic node listing hates me like this:
2017-05-01 22:02:08.787410 This command is deprecated. Instead, use 'openstack baremetal node list'.
2017-05-01 22:02:08.787670
2017-05-01 22:02:24.105059 SSL exception connecting to https://<IP_ADDRESS>:6385/v1/nodes: bad handshake: Error([('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')],)

I broke mitaka, but close on newton. It looks like --insecure is needed for "openstack baremetal" commands for newton but not mitaka.

Mitaka failure looks like that flakey LXC thing to me. I'll recheck in a minute.

recheck 8d016ae

LXC is being flakey again no mitaka.

recheck 8d016ae

Its alive!


Error response from daemon: Cannot destroy container pp.server: Driver aufs failed to remove root filesystem

I am receiving the following error in one third of nightly restarts of a container:
Error response from daemon: Cannot destroy container pp.server: Driver aufs failed to remove root filesystem
+a255eb811579f8c4e36889817f616ae3319d9f158ac729923ff22c7dae8ff95f: rename
+/var/lib/docker/aufs/mnt/a255eb811579f8c4e36889817f616ae3319d9f158ac729923ff22c7dae8ff95f
+/var/lib/docker/aufs/mnt/a255eb811579f8c4e36889817f616ae3319d9f158ac729923ff22c7dae8ff95f-removing: device or resource busy
time="2015-02-10T00:00:01+01:00" level="fatal" msg="Error: failed to remove one or more containers"
4ff89df9a893993c11843b6c5b2ba6d4c052a3c7ca0e46b2f982053c44b0b259+
dgho@neu:~/existdb$ docker info
Containers: 4
Images: 467
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 475
Execution Driver: native-0.2
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 12
Total Memory: 58.98 GiB
Name: neu
ID: NHZD:VRE3:X2ZW:QUFY:ZW65:5TRQ:LMH6:LJJB:C7WB:IBLF:JTGU:IN34
Username: zopyx
Registry: [https://index.docker.io/v1/]
WARNING: No swap limit support
dgho@neu:~/existdb$ docker -D version
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.4.1
Git commit (client): a8a31ef
OS/Arch (client): linux/amd64
Server version: 1.5.0
Server API version: 1.17
Go version (server): go1.4.1
Git commit (server): a8a31ef

Closing as dup of #9665

And the solution? Are you saying that this error is a feature and that
there is no canonical way for solving this problem?
2015-02-11 14:40 GMT+01:00 Brian Goff<EMAIL_ADDRESS>
Closing as dup of #9665 https://github.com/docker/docker/issues/9665
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/10700#issuecomment-73881863.

It means there is already an open issue with this exact problem and we should move all discussion to that open issue.

Sorry, was misreading that the other issue is still open.


Add continuous integration (CI) tests

It would be nice to see this project get CI integration with travis (linux and OSX) and appveyor (Windows) to prove that the tests pass now and when changes are made in the future.
I find it useful to use astropy's ci-helpers repository/utility: https://github.com/astropy/ci-helpers
I can provide some information if this is something you'd be interested in.

Added extensive examples to the readme, and continuous testing of these using Travis CI for both Py2 and 3. Thanks for getting this started - much needed!


Build failure

Hello :)
I am trying to build the latest version.
I made sure the following things:

I've cloned the repository recursively
$ git clone --recursive https://github.com/eclipse/kuksa.val.git

I've installed dependencies
$ sudo apt-get update
$ sudo apt-get install libblkid-dev e2fslibs-dev libboost-all-dev libaudit-dev libssl-dev mosquitto libmosquitto-dev

And I've received the following error:
junh-ki@junhki-VirtualBox:~/kuksa.val/build$ make
[  5%] Checking the git repository for changes...
[  5%] Built target check_git
[ 68%] Built target kuksa-val-server-object
[ 73%] Built target kuksa-val-server-core
[ 78%] Built target kuksa-val-server-core-static
[ 84%] Building CXX object src/CMakeFiles/kuksa-val-server.dir/main.cpp.o
In file included from /home/junh-ki/kuksa.val/src/main.cpp:39:0:
/home/junh-ki/kuksa.val/src/../buildinfo.h:31:40: error: stray ‘@’ in program
 Signed-off-by: Phong Tran<EMAIL_ADDRESS>

Is there anything I am missing here?

I have the feeling that is related to out cmake magic extracting git build numbers. @phongt  also stumbled upon this. Can you post the /home/junh-ki/kuksa.val/src/../buildinfo.h file?
Just a wild guess, maybe it doesn't like several singed-off" in one commit message. To test, you might want to delte buildinfo, and try doing a new commit before building (i.e. just add a space to a file, or add an empty file and git add and commit) Does that work?
@wenwenchenbosch  any ideas?

/home/junh-ki/kuksa.val/src/../buildinfo.h)
// This file was create automatically by CMake.
#pragma once

// Whether or not we retrieved the state of the repo.
#define GIT_RETRIEVED_STATE true

// The SHA1 for the HEAD of the repo.
#define GIT_HEAD_SHA1 "32e850a013df34d70c119553563b69781c6b7649"

// Whether or not there were uncommited changes present.
#define GIT_IS_DIRTY false

// The name of person who committed HEAD.
#define GIT_AUTHOR_NAME "Wenwen Chen"

// The email addess of the person who committed HEAD.
#define GIT_AUTHOR_EMAIL<EMAIL_ADDRESS>
// When HEAD was committed.
#define GIT_COMMIT_DATE_ISO8601 "2020-11-06T16:28:54+01:00"

// The subject line for the HEAD commit.
#define GIT_COMMIT_SUBJECT "64 unittest ci (#65)"

// The notes attached to the HEAD commit.
// #define GIT_COMMIT_BODY "* README: Add installation libmosquitto-dev

Without installation of Mosquitto dependency will build error.

Signed-off-by: Phong Tran<EMAIL_ADDRESS>
* Fix unit test compile failure

Signed-off-by: Phong Tran<EMAIL_ADDRESS>
* add test stage and enable run ctest

Signed-off-by: Chen Wenwen (CR/AME5<EMAIL_ADDRESS>
* fix jenkinsfile

Signed-off-by: Chen Wenwen (CR/AME5<EMAIL_ADDRESS>
* revert changes in test

Signed-off-by: Chen Wenwen (CR/AME5<EMAIL_ADDRESS>
* do not run ctest

Signed-off-by: Chen Wenwen (CR/AME5<EMAIL_ADDRESS>
* rename and build test in docker

Signed-off-by: Chen Wenwen (CR/AME5<EMAIL_ADDRESS>
* disable running test

Signed-off-by: Chen Wenwen (CR/AME5<EMAIL_ADDRESS>
Co-authored-by: Phong Tran<EMAIL_ADDRESS>

Delete buildinfo.h
Then edit buildinfo.h.in and REMOVE the last two lines
// The notes attached to the HEAD commit.
// #define GIT_COMMIT_BODY "@GIT_COMMIT_BODY@"

Then cmake & make again.
Our cmake tooling break when the last commit has more than one line. Since we do not use commit_body (message) in our code, it is ok, to dlete it in the .in file
If you have time, please make a pullrequest with the two lines removed from  .in file 😄

Closed by #70
@junh-ki  can you close this issue? (I can't 😁 )

Closed by #70
@junh-ki can you close this issue? (I can't 😁 )

I was waiting for the build result and it just built it successfully so I am closing :D


For #670 - Logo Update

I'm pretty new so let me know if I can improve or did something bad! Only 1st year CS student..

Big C is for config
Inner S is for settings
?


[ CI ] modify android build test in action

This pr fixs the duplicated build in android build action.
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2669. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


change util import to relative fir using sources as git submodule

This MR changes the import strategy in order to make it possible to use this repository as a git submodule in a subfolder in another application.

Thanks!


Update Wilson package versions to beta4

https://github.com/aspnet/Security/blob/dev/src/Microsoft.AspNet.Authentication.OpenIdConnect/project.json#L7
https://github.com/aspnet/Security/blob/bd7f07052ec9d50f7712068979eed4814ee2a304/src/Microsoft.AspNet.Authentication.OAuthBearer/project.json#L7
@tushargupta51 @brentschmaltz

merged : https://github.com/aspnet/Security/commit/1a37bf17475ce64bb4664aa7fb96b07cbf28eb92


can't pin an image to Pinterest but no error sent

I'm using the same code since 2017, every day it shares some GIFs automatically, but since 27/01 it stopped working, but I don't see any error. Does Pinterest change something?
here is my code:
$pin = $pinterest->pins->create(array( 				"note"          => "test" 				"image_url"     => "test.gif", 				"board"         => "keepgif/lol", 				"link"			=> "url" 		));

Are you using the latest version (0.2.13)?

I've tried reproducing this using the latest demo in master but it all seems to be working fine for me. Please check if you're using the latest version.
I'll close this for now, but feel free to re-open when you keep on experiencing the same issue. Also make sure to share a reproducible repo.

hi @dirkgroenen I am still facing this issue and this issue is generated 7271 times on my end i have the payload in the logs can you please fix this issue.

@waqasd4int As mentioned I wasn't able to reproduce this myself when using the latest master branch. Can you provide me with a repository which reproduces this issue?

@dirkgroenen it is not happening in all cases it is generating in some specific case I am also not able to reproduce this issue but I check in the logs it is still generating for some of the pins

issue fixed after updating to the latest version (0.2.13)


Code your post blog feed page

[ ] Create the carousell with the 3 latest posts

[ ] Create the responsive thumbnail grid with a list of the 12 latest posts