Governance Issue: A Genesis investor hasn't been able to claim his SOV tokens

The owner of the RSK address: 0xd970Ff09681A05e644cd28980B94A22C32C9526B has failed in every try to convert his cSOV tokens into SOV.
We can see all his failed tries here: https://explorer.rsk.co/address/0xd970ff09681a05e644cd28980b94a22c32c9526b
and it isn't due to insufficient Gas Limit: https://explorer.rsk.co/tx/0x2b7fece706f89b55542f638be8525d894c596a83c28d6fa3963bc7889a4ce2a2
This user didn't do an excessive BTC deposit:
https://blockstream.info/tx/53149d940fda73b4582002f4930819097394b91435821e0adda72abfb5c8385d
my main concern is to discard any bug in the smart contracts affecting these kind of users.
how can this user make his claim effective?

The user had blacklisted his RSK address. The reported BTC deposit does not correspond to a BTC address set for the Genesis sale; all these addresses begins with "3" and the referred deposit is to an alien address which begins with "bc1q".
This user double spent his deposit.


Having trouble changing the post banner image on category posts

Environment Details
Hugo version - v0.97.3
Toha package version (theme\toha\package.json) - 1.0.0
Toha Release - v3.5.0 (cloned on 23/04/22)
OS - Windows 10
Browser - Edge
Question
I do not seem to be able to change the default banner image on category posts. I have been following/replicating the folder/file structure from - https://github.com/hugo-toha/hugo-toha.github.io/tree/source/content/posts/category/sub-category/rich-content/images
I have read the comments on the following pull request - https://github.com/hugo-toha/toha/pull/248
I'm not quite sure what to do next, i've followed the guide and the demo site and still not managed to get it working

If you share your repo, I can take a look.

Thank you @hossainemruz that is very kind!
I have shared access to the repo with you. - The changes are on the fb_nested_posts branch.
let me know what you think!

Hi @rickettdev. It seems your introduction post has proper banner now. What issue are you facing currently?

Hey @hossainemruz
On the fb_nested_posts git branch there is an additional post folder cat-rickettylabs-blog.

The issue seems to be the folder names. Please remove any . and & or space from the folder names.

hey @hossainemruz  thank you very much for taking the time to help me with this!.
I've updated all the folder/file names and removed any non text characters or spaces (as per the below)

Sadly I still have the same issue.
I have updated the 'Image Sample' to validate the image path is correct and I am able to get the target image displayed (as per the below)

Following the success of the above test, I attempted to use the same path used in the image source for the hero parameter but that did not work.

Your post markdown file should be named index.md.

Thank you for this. all workiing


Add nootrobox.com to projects

This change is

Coverage remained the same at 82.305% when pulling 7fd06aabe4d68d4185ad8638348baf031f34964b on benigeri:patch-1 into fb220ee63280b0f5b4b4c41c7c97bbf8046c38b6 on shakacode:master.

Coverage remained the same at 82.305% when pulling 7fd06aabe4d68d4185ad8638348baf031f34964b on benigeri:patch-1 into fb220ee63280b0f5b4b4c41c7c97bbf8046c38b6 on shakacode:master.

@benigeri can you please rebase to one commit.
I'd like to include your very positive comment.
Maybe tweet again with the new website name and I'll screen grab that?

Already done.


CLI for Franklin

hey just want to let you know I wrapped up a CLI for Franklin using Comonicon: https://github.com/JuliaCLI/FranklinCLI.jl
I'd like to hear some feedbacks from people if there is anyone wants to try, it currently wraps the major interface
franklin new
franklin serve

but it's simple to have more commands supported, such as publish etc. just like all other static website generator, jekyll, hexo etc.
Currently, this CLI package will automatically build a system image locally,
but since I didn't add all the test dependencies, thus the system image won't benefit from the nice test coverage of Franklin at the moment. It might be good if someone familiar with the implementation to write some code that should be compiled to FranklinCLI's test to make things faster.
Bests
Roger

Oh but that's awesome! I'll try it soon!! Feel free to advertise that on the #franklin slack channel too, I'm sure a few people will give it a shot :)


Encode spaces in FedoraIds, reload resource after a PATCH request

JIRA Ticket: https://jira.lyrasis.org/browse/FCREPO-3223
What does this Pull Request do?
Another iteration on enabling FedoraLdpIT tests.
How should this be tested?
This is for internal tests.
Preconditions on a PUT have been enabled, and literal whitespaces are translated to %20 in FedoraId to ensure our IRIs are valid.
Interested parties
@fcrepo/committers

I'm not sure what I'm doing wrong, but I can't get it to work. When I do:
curl -u fedoraAdmin:fedoraAdmin 'http://localhost:8080/rest/with some spaces' -H "Link: <http://www.w3.org/ns/ldp#NonRDFSource>; rel=type" -v -H "Content-Type: text/plain" -X PUT --data-binary "testing"
I get back:

Bad Message 400

reason: Illegal character SPACE=' '

The test is doing a POST, this seems to be caught by Jersey if you try to use a space in the URI, whereas the Slug it doesn't care.
> curl -i -ufedoraAdmin:fedoraAdmin -XPOST -H"Slug: spaces 2" "http://localhost:8080/rest"
HTTP/1.1 201 Created
Date: Wed, 21 Oct 2020 14:50:47 GMT
Set-Cookie: JSESSIONID=node0sf37nxmy000j1cj11m81c6gdw0.node0; Path=/
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Tue, 20-Oct-2020 14:50:47 GMT
ETag: W/"31F065CBCB64E94AA2681035DF7A4C03"
X-State-Token: 31F065CBCB64E94AA2681035DF7A4C03
Last-Modified: Wed, 21 Oct 2020 14:50:47 GMT
Link: <http://localhost:8080/rest/spaces%202>; rel="timegate"
Link: <http://localhost:8080/rest/spaces%202>; rel="original"
Link: <http://localhost:8080/rest/spaces%202/fcr:versions>; rel="timemap"
Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type"
Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"
Link: <http://fedora.info/definitions/v4/repository#Resource>; rel="type"
Link: <http://mementoweb.org/ns#OriginalResource>; rel="type"
Link: <http://mementoweb.org/ns#TimeGate>; rel="type"
Link: <http://www.w3.org/ns/ldp#RDFSource>; rel="type"
Link: <http://www.w3.org/ns/ldp#Container>; rel="type"
Link: <http://fedora.info/definitions/v4/repository#Container>; rel="type"
Link: <http://localhost:8080/rest/spaces%202/fcr:acl>; rel="acl"
Location: http://localhost:8080/rest/spaces%202
Content-Type: text/plain
Content-Length: 37
Server: Jetty(9.4.24.v20191120)

http://localhost:8080/rest/spaces%202

curl -i -ufedoraAdmin:fedoraAdmin -XPATCH -H"Content-type: application/sparql-update" -d "INSERT { <> <http://purl.org/dc/elements/1.1/title> \"test\" } WHERE { }" http://localhost:8080/rest/spaces%202
HTTP/1.1 400 Bad Request
Date: Wed, 21 Oct 2020 14:52:03 GMT
Set-Cookie: JSESSIONID=node0aize2n8mb19m1r9ahtax4r63c1.node0; Path=/
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Tue, 20-Oct-2020 14:52:03 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 622
Server: Jetty(9.4.24.v20191120)

Encountered " "<" "< "" at line 2, column 3.
Was expecting one of:
    <IRIref> ...
    <PNAME_NS> ...

Ok this is altered to now reject literal spaces in a Slug with a 400 Bad Request error. I did this at the HTTP layer but also had the FedoraId throw an exception if it encountered an id with a space.

I don't think this is working quite right yet.
curl -u fedoraAdmin:fedoraAdmin http://localhost:8080/rest -H "Link: <http://www.w3.org/ns/ldp#NonRDFSource>; rel=type" -v -H "Content-Type: text/plain" -X POST -H"Slug: has%20spaces%201" --data-binary "testing"
curl -u fedoraAdmin:fedoraAdmin http://localhost:8080/rest/has%20spaces%201

The GET fails, but it shouldn't


3d game example

Eat the cakes. Eat them all, I dare you.
...
And experience the powerful sugar rush of the alien.
Small 3d game example that I had fun doing this afternoon.

Controls are arrow key to move, spacebar to restart after losing.
Game shows spawning and controlling gltf scenes in various ways, changing the camera, systems with state.
Some of the thins could be nicer with more complexity, but goal was too keep it short
https://user-images.githubusercontent.com/8672791/104822079-76402a80-5840-11eb-871b-6e847902bc0e.mp4

Controls are arrow key to move, spacebar to restart after losing.
Game shows spawning and controlling gltf scenes in various ways, changing the camera, systems with state.
Some of the thins could be nicer with more complexity, but goal was too keep it short
https://user-images.githubusercontent.com/8672791/104822079-76402a80-5840-11eb-871b-6e847902bc0e.mp4

Nice work.
The camera movement makes me uncomfortable though haha.
Here's a camera movement system I've come up with - in general it points to the mid-point between the alien and the cake:
#[derive(Default)]
struct Game {
    board: Vec<Vec<Cell>>,
    player: Player,
    bonus: Bonus,
    score: i32,
    cake_eaten: u32,
    camera_should_focus: Vec3,
    camera_is_focus: Vec3,
}

fn setup(commands: &mut Commands, asset_server: Res<AssetServer>, mut game: ResMut<Game>) {
    // reset the game state
    game.cake_eaten = 0;
    game.score = 0;
    game.player.i = BOARD_SIZE_I / 2;
    game.player.j = BOARD_SIZE_J / 2;
    game.camera_should_focus = Vec3::new(
        BOARD_SIZE_I as f32 / 2.0,
        0.0,
        BOARD_SIZE_J as f32 / 2.0 - 0.5,
    );
    game.camera_is_focus = game.camera_should_focus;
    // ...
}

// move the camera, the more cake eaten, the faster
fn move_camera(
    time: Res<Time>,
    mut game: ResMut<Game>,
    mut transforms: QuerySet<(Query<(&mut Transform, &Camera)>, Query<&Transform>)>,
) {
    const SPEED: f32 = 2.0;
    // if there is both a player and a bonus, target the mid-point of them
    if let (Some(player_entity), Some(bonus_entity)) = (game.player.entity, game.bonus.entity) {
        if let (Ok(player_transform), Ok(bonus_transform)) = (
            transforms.q1().get(player_entity),
            transforms.q1().get(bonus_entity),
        ) {
            game.camera_should_focus = player_transform
                .translation
                .lerp(bonus_transform.translation, 0.5);
        }
    // otherwise, if there is only a player, target the player
    } else if let Some(player_entity) = game.player.entity {
        if let Ok(player_transform) = transforms.q1().get(player_entity) {
            game.camera_should_focus = player_transform.translation;
        }
    // otherwise, target the middle
    } else {
        game.camera_should_focus = Vec3::new(
            BOARD_SIZE_I as f32 / 2.0,
            0.0,
            BOARD_SIZE_J as f32 / 2.0 - 0.5,
        );
    }
    // calculate the camera motion based on the difference between where the camera is looking
    // and where it should be looking; the greater the distance, the faster the motion;
    // smooth out the camera movement using the frame time
    let mut camera_motion = game.camera_should_focus - game.camera_is_focus;
    if camera_motion.length() > 0.2 {
        camera_motion *= SPEED * time.delta_seconds();
        // set the new camera's actual focus
        game.camera_is_focus += camera_motion;
    }
    // look at that new camera's actual focus
    for (mut transform, camera) in transforms.q0_mut().iter_mut() {
        if camera.name == Some(CAMERA_3D.to_string()) {
            *transform = transform.looking_at(game.camera_is_focus, Vec3::unit_y());
        }
    }
}

Nice work.
The camera movement makes me uncomfortable though haha.
Here's a camera movement system I've come up with - in general it points to the mid-point between the alien and the cake:
#[derive(Default)]
struct Game {
    board: Vec<Vec<Cell>>,
    player: Player,
    bonus: Bonus,
    score: i32,
    cake_eaten: u32,
    camera_should_focus: Vec3,
    camera_is_focus: Vec3,
}

fn setup(commands: &mut Commands, asset_server: Res<AssetServer>, mut game: ResMut<Game>) {
    // reset the game state
    game.cake_eaten = 0;
    game.score = 0;
    game.player.i = BOARD_SIZE_I / 2;
    game.player.j = BOARD_SIZE_J / 2;
    game.camera_should_focus = Vec3::new(
        BOARD_SIZE_I as f32 / 2.0,
        0.0,
        BOARD_SIZE_J as f32 / 2.0 - 0.5,
    );
    game.camera_is_focus = game.camera_should_focus;
    // ...
}

// move the camera, the more cake eaten, the faster
fn move_camera(
    time: Res<Time>,
    mut game: ResMut<Game>,
    mut transforms: QuerySet<(Query<(&mut Transform, &Camera)>, Query<&Transform>)>,
) {
    const SPEED: f32 = 2.0;
    // if there is both a player and a bonus, target the mid-point of them
    if let (Some(player_entity), Some(bonus_entity)) = (game.player.entity, game.bonus.entity) {
        if let (Ok(player_transform), Ok(bonus_transform)) = (
            transforms.q1().get(player_entity),
            transforms.q1().get(bonus_entity),
        ) {
            game.camera_should_focus = player_transform
                .translation
                .lerp(bonus_transform.translation, 0.5);
        }
    // otherwise, if there is only a player, target the player
    } else if let Some(player_entity) = game.player.entity {
        if let Ok(player_transform) = transforms.q1().get(player_entity) {
            game.camera_should_focus = player_transform.translation;
        }
    // otherwise, target the middle
    } else {
        game.camera_should_focus = Vec3::new(
            BOARD_SIZE_I as f32 / 2.0,
            0.0,
            BOARD_SIZE_J as f32 / 2.0 - 0.5,
        );
    }
    // calculate the camera motion based on the difference between where the camera is looking
    // and where it should be looking; the greater the distance, the faster the motion;
    // smooth out the camera movement using the frame time
    let mut camera_motion = game.camera_should_focus - game.camera_is_focus;
    if camera_motion.length() > 0.2 {
        camera_motion *= SPEED * time.delta_seconds();
        // set the new camera's actual focus
        game.camera_is_focus += camera_motion;
    }
    // look at that new camera's actual focus
    for (mut transform, camera) in transforms.q0_mut().iter_mut() {
        if camera.name == Some(CAMERA_3D.to_string()) {
            *transform = transform.looking_at(game.camera_is_focus, Vec3::unit_y());
        }
    }
}

Yeah I like everything about this except the "motion sickness as a game mechanic" aspect.   This looks good to me!

Awesome. This looks good to me!


Update pulsar-client, ... to 3.2.1

About this PR
📦 Updates

org.apache.pulsar:pulsar-client
org.apache.pulsar:pulsar-functions-api

from 3.1.3 to 3.2.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
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!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.pulsar" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.pulsar" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #189.


Use python client to reduce redundant code

This issue is connected to a massive refactoring of the cli, which currently has a lot of messy code and no QA system in place.

The CLI uses the client as backend now.


Allow using planetscale's log instead of glog

Description
This can be controlled with a command flag. However, notice that using the planetscale logger means that automatic log rotation does now work, as this is not provided by planetscale's logger or the underlying zap logger, whereas it does come in with glog.
Usual logging continues to work without any changes:
% ./bin/vtgate
F1115 11:53:04.508981   49238 server.go:224] topo_global_server_address must be configured

But with the new flag, it changes to planetscale's logger:
% ./bin/vtgate -log_planetscale
{"level":"info","time":"2022-11-15T11:54:32+01:00","caller":"log/log.go:96","msg":"Version: 12.0.5 (Git revision ebca7e95de branch 'eduardo_ortega_structured_logging') built on Tue Nov 15 10:59:08 CET 2022 by<EMAIL_ADDRESS>using go1.18.8 darwin/amd64"}
{"level":"error","time":"2022-11-15T11:54:32+01:00","caller":"log/log.go:98","msg":"topo_global_server_address must be configured","stacktrace":"vitess.io/vitess/go/vt/log.SetPlanetScaleLog.func5\n\tvitess.io/vitess/go/vt/log/log.go:98\ngithub.com/slok/noglog.(*LoggerFunc).Errorf\n\tgithub.com/slok/noglog@v0.2.0/glog.go:210\ngithub.com/slok/noglog.Errorf\n\tgithub.com/slok/noglog@v0.2.0/glog.go:135\ngithub.com/slok/noglog.Exitf\n\tgithub.com/slok/noglog@v0.2.0/glog.go:182\nvitess.io/vitess/go/vt/topo.Open\n\tvitess.io/vitess/go/vt/topo/server.go:224\nmain.main\n\tvitess.io/vitess/go/cmd/vtgate/vtgate.go:116\nruntime.main\n\truntime/proc.go:250"}

Using Planetscale's logger (which under the hood is a wrapper for Uber's zap) together with noglog as in this PR allows for an easy migration path away from glog; while also providing an initial approach to structured logging.
Related issue
https://github.com/vitessio/vitess/issues/11613#issuecomment-1302366327

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Metadata field IDs selected wrongly

Describe the bug
We have deployed DSpace 7.5 at https://tulap.cmpe.boun.edu.tr/dspace/home . Creation of metadata fields has been problematic. Going through the logs, I realized the system tries to create a metadata field record with record IDs already existent. In our version, we have 260 metadata fields from the start. When I realized the problem, it was trying to give record IDs of 200~. I realized the IDs the system tried to give increased for every attempt. I attempted to create new metadata fields just so the IDs would increase to the point of passing all the metadata field IDs (260). After dozens of attempts, the system came to the ID 261 and it was successful. I hope this is helpful. You can ask me to elaborate on any part.
To Reproduce
Steps to reproduce the behavior:

Deploy DSpace 7.5
Create a metadata field, either by UI or API

Expected behavior
I expected the metadata field to be created.

That sounds as though the database SEQUENCE value metadatafieldregistry_seq
was not consistent with the actual content of the metadatafieldregistry
table.  I don't know how that might have happened.
select max(metadata_field_id) from metadatafieldregistry; will tell
you what the highest used sequence value is.  select last_value from metadatafieldregistry_seq will tell you the most recent value of the
sequence.
I'm feeling cautious about advising how to set the sequence's next
value but I'm sure there's a more convenient way than advancing it one
value at a time.

@furkanakkurt1335 : As @mwoodiupui notes, It does sound like the database sequences were just outdated.  You could run ./dspace database update-sequences to correct that.
I don't believe this is a bug, as it sounds like a data error that could have been corrected by running ./dspace database update-sequences


Vaadin client compilation fails using Vaadin 7.5.1

Compilation of the Vaadin Widgetset fails if Vaadin 7.5.1 is used, due to a change of the return-value datatype of Vaadin's MeasuredSize .getInnerHeight()-method (was prior to 7.5.1: int; is: double). This method is called in "VFilterTable" on line 182.
Client compiler's error message:
Tracing compile failure path for type 'org.tepi.filtertable.gwt.client.ui.VFilterTable'
[ERROR] Errors in 'jar:file:[...]/m2/repository/org/vaadin/addons/filteringtable/0.9.12.v7/filteringtable-0.9.12.v7.jar!/org/tepi/filtertable/gwt/client/ui/VFilterTable.java'
[ERROR] Line 182: Type mismatch: cannot convert from double to int
[ERROR] Aborting compile due to errors in some input files

Thank you, the bug is resolved with the FilterTable 0.9.13.v7 release.


Use Pi-hole for LAN devices at home

Hello @mr-bolle,
First of all thank you for your job, I tested connecting to OpenVPN through cell and it's blocking ads.
I'm trying to use Docker Pi-hole as DNS to also block all ads when I navigate from home by LAN without connecting to OpenVPN.
I tried changing DNS on router by setting Pi IP, and also tied to set Dcoker network gateway IP and Pihole docker network IP.
I'm not a network expert, last time I used Pihole (without Docker), I added Pi IP as DNS in router. With Docker, not sure which IP do I need to setup.
It would be great to complete this functionality, blocking all ads also in my home network!.
Thank you again.

Please check the official docker image https://github.com/pi-hole/docker-pi-hole

Please check the official docker image https://github.com/pi-hole/docker-pi-hole

Hi @NCGNConsulting
Now I have found a solution, you only must adjust the host port from 553 to 53 and remove the #
https://github.com/mr-bolle/docker-openvpn-pihole/blob/11b96d52646991738f8a8d6b80e37c9229c48918/docker-compose.yml#L48-L49

Thank you @mr-bolle. That's perfect!
I will have a look as soon as I can.
Best Regards.


On selection ending not over the selection source (start) item the caret goes to the end of the editor into the new default block

duplicates #456


sysbench crashes on x86-64 machines without AVX

Launching sysbench on a x86-64 machine without AVX results in a SIGILL crash due to a vxorpd instruction.
I've tried the versions in 20.09 and unstable, same result.

I just compiled sysbench original sources and it works fine. Could hydra be building with AVX enabled for all packages?

The upstream sources aren't using any -march/-mcpu/-mtune flag.


Mention FuturesOrdered as alternative to join_all

The docs of futures::future::join_all say that results are collected “into a destination Vec in the same order as they were provided”, but then go on to suggest FuturesUnordered as an alternative to it. FuturesOrdered should be mentioned as a proper replacement for keeping the order, while suggesting FuturesUnordered as an additional option.

Thanks!


test: fixed git-validation in travis

Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

Just trying to figure out what's wrong with git-validation.

Wth, Travis?!

That test passed. Merging early.


Compiling efficiency is also too low, the same project Maven 20 seconds, Gradle more than ten minutes to complete

Context
Compiling efficiency is also too low, the same project Maven 20 seconds, Gradle more than ten minutes to complete,why、why......

Your issue lacks information about how to reproduce the problem you're having. We don't know what's inside your project, so we cannot can not analyse what's causing the slowness. A reproducer project would help us track down and fix your problem.  We may also be able to suggest workarounds or ways to avoid the problem if we can reproduce it.


Refactor access to Crud and Indexing

Part 1 of n PRs for feature-284-refactor-datastore-indexmanager. See parent issue #284.
Datastore → Database
DatastoreImpl → DatabaseImpl
IndexManager → IndexManagerImpl
Add new interface IndexManager
Create new class CloudantSync with fields database and query, through
which the CRUD and Query/Index methods are accessed.
NB - not done in this commit:

Any IndexManager API refactoring (adding throws clauses etc)

The encryption tests are failing (hence the Android build failure) looks like some more test changes are needed.

@ricellis Thanks for pointing that out, I should have checked the build output.


Light sources cancel out Detection Modes when used with Limits

When using a template that has a number of vision mode limitations on it, if there is a light source on any tokens (global or ambient light source) they will not respond to the various Detection modes.
Easier to show than describe.

Here Devil's Sight is functioning correctly.

Here, with a light source overlapping the tokens, Devil's sight (and other detection modes that allow revealing tokens) doesn't work.

Here, lights removed, the tokens in the "Darkness template" can't see, but can hear. Working as expected. No lights on scene. Not even global illumination

As show, global illumination checked, but darkness set to 1. Devil's sight token isn't being triggered.

Worse, the tokens in the darkness template, should be blind, but aren't. They can see the other tokens, even in when Darkness set to 1 and global illumination turned on.

Foundry 11.315
Dnd5e 3.1.1 and 3.1.2
Vision 1.14.2
only modules enabled: vision 5e, limits, libwrapper, socketlib.

Thanks for the report! Fixed in 1.14.3.


GraphPPL does not work for Julia <1.10

I encountered this error when trying to compile RxInfer v3.0.2 (which uses GraphPPL v4.0.2) for Julia 1.9.4:
$ julia --version
julia version 1.9.4

$ cat Project.toml
[deps]
RxInfer = "86711068-29c9-4ff7-b620-ae75d7495b3d"

$ julia --project=.
julia> using Pkg
julia> Pkg.activate(".")
julia> Pkg.instantiate()
Updating registry at `~/.julia/registries/General.toml`
[...]
  [b3f8163a] + GraphPPL v4.0.2
[...]
Precompiling project...
  ✗ GraphPPL
  ✗ GraphPPL → GraphPPLDistributionsExt
  ✗ RxInfer
  9 dependencies successfully precompiled in 27 seconds. 121 already precompiled.
  3 dependencies errored. To see a full report either run `import Pkg; Pkg.precompile()` or load the packages
julia> using RxInfer
[ Info: Precompiling RxInfer [86711068-29c9-4ff7-b620-ae75d7495b3d]
ERROR: LoadError: UndefVarError: `@Kwargs` not defined
Stacktrace:
 [1] top-level scope
   @ :0
 [2] include(mod::Module, _path::String)
   @ Base ./Base.jl:457
 [3] include(x::String)
   @ GraphPPL ~/.julia/packages/GraphPPL/BYCRJ/src/GraphPPL.jl:1
 [4] top-level scope
   @ ~/.julia/packages/GraphPPL/BYCRJ/src/GraphPPL.jl:8
 [5] include
   @ ./Base.jl:457 [inlined]
 [6] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId
, UInt128}}, source::String)
   @ Base ./loading.jl:2049
 [7] top-level scope
   @ stdin:3
in expression starting at /Users/<redacted>/.julia/packages/GraphPPL/BYCRJ/src/graph_engine.jl:497
in expression starting at /Users/<redacted>/.julia/packages/GraphPPL/BYCRJ/src/graph_engine.jl:497
in expression starting at /Users/<redacted>/.julia/packages/GraphPPL/BYCRJ/src/GraphPPL.jl:1
in expression starting at stdin:3

@Kwargs does not seem to exist before Julia 1.10, but is used in the graph_engine of GraphPPL.
Compiling RxInfer for Julia 1.10 works, however.

Ah, we should update our [compat] entry. It still says Julia v1.6 but that is not true. The error with v1.9 is expected, we don't support Julia < 1.10 for the new version (RxInfer and ReactiveMP also should set minimum required version to 1.10).


Add -Severity to Get-ScriptAnalyzerRules

Implementation was merged to BugFixes branch. Will get merged to Master tomorrow.


Feature request: add support for way to use both security requirements at the same time.

As described in https://swagger.io/docs/specification/authentication/:
Some REST APIs support several authentication types. The security section lets you combine the security requirements using logical OR and AND to achieve the desired result. security uses the following logic:
security:    # A OR B
  - A
  - B
security:    # A AND B
  - A
    B
security:    # (A AND B) OR (C AND D)
  - A
    B
  - C
    D

I think, the previous example can be implemented this way:
#[utoipa::path(
  ..,
  security(
    ("a" and "b" = []), // (A AND B) OR (C AND D)
    ("c" and "d" = []),
  ),
  ..
)
async fn test() {}

Sure this could be added in future releases. The discussion earlier related to this https://github.com/juhaku/utoipa/discussions/625 seemingly indicates that there is a valid need for this support.

I'll take it. Already implemented the codegen part.


CPP Bug in Tutorial

Command "stop blinking" does not stop the LED from blinking.  Something about the update being in a protected scope (e.g. in an else clause or something).

Addressed here https://github.com/fprime-community/fprime-workshop-led-blinker/pull/35


Avoid warnings due to deprecation of getMock() in PHPUnit

The method getMock() was deprecated with the release of PHPUnit 5.4. The same release introduced createMock() that should be used to create mock objects instead. This PR modifies React\Tests\EventLoop\TestCase::createCallableMock() to use the new mock API if available.

We've currently decided to add PHPUnit 4.8 to require-dev of each component, see reactphp/react#354. This will fix this issue.
As a side note: i've also fixed this latetly in react/promise by using
$this
    ->getMockBuilder('React\Promise\Stub\CallableStub')
    ->getMock();

This works in all version of PHPUnit, see https://github.com/reactphp/promise/commit/73f2304f08882c00f510a3dc74bd58ed4a28bcd6#diff-d4c8c6dc8769324fc27cfdac19f05caf

Should i change the PR to use mock builder or close it and let you introduce PHPUnit 4.8 instead?

I'd vote for getting this in for forward compatibility and to avoid warnings when users run the tests not from vendors but with their local version of PHPUnit.


Handle unique constraint error

I am trying to handle the case when unique_constraint fails by checking errors for a specific key.  So I've checked the source and found that only message is given without any clarification what happened wrong, the expected behaviour is that
errors: [name: {"has already been taken", []}]

could contain something like
errors: [name: {"has already been taken", [validation: :unique]}]

Is there any case that can help me to achieve my goal?

@mojidabckuu the behaviour you proposed is available in master. :)

Hey Jose. Looks this one is missing now.
I've checked the version date around sep 22 and it has the validation key. But current 2.2.7 doesn't
https://github.com/elixir-ecto/ecto/blob/3a0616a356ecbc3b6ba1e391e785a13f66c13da9/lib/ecto/changeset.ex#L2080

master is going to be 3.0.

Any estimations for 3.0 to become rc?

None so far.


tqdm error

While running test submission.py, i am receiving this output..<
What should i do.? Is this correct.? or there should be a progress bar here.?
"HBox(children=(FloatProgress(value=0.0, max=3729.0), HTML(value='')))
total number of sliding windows:  1"

There is an issue related to the progress bar with tqdm, but no effect for the final results. You can safely ignore it for now.

Yep Its Working,
Thanks samleoqh.

I tried with a subset of 10 images from the test set. However, I get "black" output images after running test_submission.py.
When I run: PYTHONPATH={PWD}/..:${PYTHONPATH} CUDA_VISIBLE_DEVICES=0 python3 ./tools/test_submission.py
Following is the result in the command line:
HBox(children=(IntProgress(value=0, max=10), HTML(value='')))
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.27905702590942383
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.2548341751098633
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.25104784965515137
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.2509579658508301
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.2509949207305908
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.25146985054016113
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.2590038776397705
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.2514808177947998
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.2519571781158447
total number of sliding windows:  1
HBox(children=(IntProgress(value=0, max=1), HTML(value='')))
inference cost time:  0.2519662380218506
Is it just an image-saving problem or sth else?

It was just a display error. replacing pred with pred255/7* solved the issue by displaying each class as a shade of gray.


How to set the name?

I´m using your datepicker and it's really awesome. However, one thing I dont understand is how to put the datepicker in a form and set a name for it so it will be passed together with a form submit? Right now i created a normal input field that i hide with css and just bind that value together with the datepickers value but it would for sure be cool to just be able to add a name attribute to the Datepicker itself? Is it possible to do already or?

It's been brought up a few times. I think the way it would have to be implemented is to create a fake input element with the name attribute. My biggest question is what format the date should be in. Unix timestamp makes sense for POST requests, but something readable might be preferable for GET requests.

Can't it just use the time format already chosen? Personally I always use yyyy-MM-dd as it's also the format och default html date inputs :)
My current solution look like this, works fine but feels a bit meh :P
<script lang="ts">
	import { DateInput } from 'date-picker-svelte'
	let date = new Date()
	export let name: string

	$: newDate = date?.toLocaleString('sv', { timeZone: 'Europe/Stockholm' }).slice(0, 10)
</script>

<input type="text" id="dateFrom" {name} bind:value={newDate} style="display:none" />
<DateInput bind:value={date} format="yyyy-MM-dd" closeOnSelection={true} placeholder={''} />

I'd want to support it for the DatePicker component as well, which doesn't have a format. It could also cause bugs when someone uses locale-specific formats, or decides to switch the format.
Some people might want to include the hours/minutes/seconds/milliseconds too. I'm leaning towards using unix timestamps, and having people create custom input elements if they need a different format

I've had a read through the linked issues. It looks like some standard HTML attributes can be passed in, but still not yet the name attribute?
This would be an awesome feature to implement, as I'd like to be able to use it with Svelte form actions (which needs the name attribute as far as I understand).


Improve documentation around adapters and custom adapters

Hi everyone,
First of all, thanks for Tesla!
I would like to request the documentation to be improved around how to use adapters, how to write adapters and how to configure existing ones. Here are more specific points:

I couldn't find documentation on how to change adapters where I'd expect this information to be available. The only place I found it was on the README under the testing section.

The Tesla module has a build_adapter function but it has no documentation. It is unclear if it is private or public or how to invoke it without checking the source (there are other build_* functions with the same issue).

It seems to be possible to pass options to adapters. This is briefly mentioned in Tesla.request/2 but there are no actual examples. When looking at the adapter modules themselves, they don't mention which options they accept. I would recommend doing something similar to Plug, where we list the main options and give a reference to more information.

Generally speaking, it would be nice if each adapter linked to their respective docs and provide brief information on the pros and cons. Adapters like Hackney should mention if they are using the default pool or not and similar information, to make customization more straight-forward. HTTP clients are a bit chaotic on the Elixir community right now. Tesla is attempting to solve some of those issues by making them replaceable, therefore it should provide more information on replaceability.

There is no information on writing adapters. Tesla.Adapter does define a callback but it doesn't document the callback. It should be mentioned what they receive, what they are expected to do and what they return (apparently a Tesla.Env with status, headers and body set).

Tesla.Env does not document any of its fields. This is important for users, middleware writers, and adapter authors. I would also document that the same Tesla.Env is used for requests and responses and fields like headers and body serve a dual purpose. This can catch some people off guard.

I would also suggest to use the ExDoc grouping functionality. as you can see in the Plug sidebar, as I believe it makes the documentation easier to explore. Although I understand not everyone prefers this style.
Thanks for reading!

Quick reply:

https://github.com/teamon/tesla/wiki/0.x-to-1.0-Migration-Guide#adapter-options-need-to-be-wrapped-in-adapter-key
https://github.com/teamon/tesla/issues/151

Thanks Tymon,
That is just what I was looking for.

[copy from #240, let's continue here]
Currently adapter interface is weakly typed - the options passed for each middleware are different and the error return values are unknown ({:error, any}).
To-do list:

[x] Define common set of error return values - quite impossible
[ ] Document adapter-specific options (how to use, link to source, link to labeled issues, etc.)

[ ] Documentation for httpc
[ ] Documentation for hackney
[ ] Documentation for ibrowse


Pull content from another server

I have deployed strapi on a public server and want to develop locally, pulling content from the API on the server.
Every time I run strapi develop, I get an error 404 when gatsby tries to pull the content from the external server:
Starting to fetch data from Strapi (user)
error Plugin gatsby-source-strapi returned an error

  Error: Request failed with status code 404

  - createError.js:16 createError
    [codestack-blog]/[gatsby-source-strapi]/[axios]/lib/core/createError.js:16:1    5

  - settle.js:18 settle
    [codestack-blog]/[gatsby-source-strapi]/[axios]/lib/core/settle.js:18:12

  - http.js:192 IncomingMessage.handleStreamEnd
    [codestack-blog]/[gatsby-source-strapi]/[axios]/lib/adapters/http.js:192:11

  - next_tick.js:138 _combinedTickCallback
    internal/process/next_tick.js:138:11

  - next_tick.js:180 process._tickCallback
    internal/process/next_tick.js:180:9

Is this not intended or am I doing something wrong? I have checked the permissions in the strapi backend, CORS is disabled.
In my gatsby-config.js
plugins: [
  {
    resolve: `gatsby-source-strapi`,
    options: {
      apiURL: `http://<IP of my server>:1337`,
      contentTypes: [`article`, `user`],
     articles,
      user
    },
  },
]

it works. I had a non-existing content type in my gatsby-config.js. Sorry, closing.


Update tests and docs for BlockEncoding

Update names, tests, and docstrings in BlockEncoding classes to match most recently added instances
Update autogenerated documentation notebooks

did you have to re-order all the cells in the notebooks by hand? thank you and sorry

That is what I did, not sure if there is a better way in general


Device Sorting

It would be good if the device list was always automatically sorted alphabetically.  The number of devices will grow as a show is put together, and when one goes to add a device to a track, it will be easier to find it and add quickly.  (LOW PRIORITY)

Fixed in new version


Fresh Database build fails with "Conflicting migrations"

Hello again guys-
I noticed the following error when trying to build the database from scratch
root@pokeapi-dev:~/pokeapi# python manage.py migrate --settings=config.docker
CommandError: Conflicting migrations detected (0001_squashed_0006_pokemonformsprites, 0001_squashed_0002_auto_20151228_0417 in pokemon_v2).
To fix them run 'python manage.py makemigrations --merge'

root@pokeapi-dev:~/pokeapi# python manage.py makemigrations --merge
Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/makemigrations.py", line 85, in handle
    return self.handle_merge(loader, conflicts)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/makemigrations.py", line 186, in handle_merge
    raise ValueError("Could not find common ancestor of %s" % migration_names)
ValueError: Could not find common ancestor of set([u'0001_squashed_0006_pokemonformsprites', u'0001_squashed_0002_auto_20151228_0417'])

I walked commits backwards and the last commit that I do not see this issue is @c966153
I'm not sure where to start troubleshooting with this one.. Let me know if you think it's a pretty simple fix I could PR myself.
As always, I just wanted to pass on my thanks for everyone's work on this...
I'm super close to being able to ship something I've been working on for awhile and I wouldn't really be anywhere without this project!

@zaneadix have you encountered this before?

@phalt @OrangeCrush oh wow. Big oversight on my part. Looks like the path had diverged so far from the New Data PR and the latest state it was merged into that the base migration was completely different. I'll see if I can knock out a fix for this today.


How can I make tooltips align vertically for vertical bar charts?

I have an issue with bar charts' tooltip setup being horizontal in most cases. I prefer the tooltip to be above the bar, 'pointing' down at the bar with its caret, and if it's coming off the screen, it should then be inside the bar, 'pointing' to the top of the bar.
The reason I want this is because the way it works now causes problems with stacked bar charts, like this:

I tried setting tooltips.yAlign to bottom but that seems to have problems with caret position and not adapting to cases where it comes off the screen, like so:

So... Is there a way to get a vertical tooltip on vertical bar charts that works correctly without making a fully custom tooltip implementation?
tooltips: {
    enabled: true,
    mode: 'nearest',
    displayColors: false,
    callbacks: {
        title: function () {
            return null;
        },
        label: function (tooltip) {
            // This is a variable that's irrelevant to the issue but I didn't want to exclude anything from the snippet
            return tooltip.value + (isShowingPercentages ? '%' : '');
        }
    }
}

This is still a problem with 2.9.1

@Moghul have you evaluated to use a custom tooltip positioner instead of  fully custom tooltip implementation ?
With a positioner, you should write code anyway but you should just calculate the position where the tooltip will appear, without touching the standard tooltip rendering.

Any solution for this with standard tooltip implementation?

I don't know if this is still an issue in more recent implementations but it hasn't been marked as resolved so...
My solution is that we have an ugly tooltip right now in production.

The custom positioner is the way to this. See https://github.com/chartjs/Chart.js/issues/5352#issuecomment-705929760

@etimberg has the correct answer, closing.


Upgrade to Lucene 7.2.0

Updated pom file, fixed to use latest Lucene APIs.

@DmitryKey  I plan to make a release luke 7.2.0. Why don't we announce JavaFX version luke as well to get feedback from others?

@mocobeta thanks for the PR. In the other thread on JavaFX I suggested to switch branches around, because JavaFX version looks so good! But yes, we could also take the approach of announcing JavaFX for testing and then switch if there are no major issues.

@DmitryKey Thank you! Either approach is fine to me... But first, let me introduce JavaFX version to all when announcing (thinlet) luke 7.2.0 release. We can switch the branches from next release.
I plan to make a release around January 10th, after returning holidays. :)

@mocobeta have a good one :)


Close the ending quote in lispy-mode

With this setting lispy closes the ending quote which is in alignment
with how Doom treats quotes in other modes.

isn't this something smartparens should do? b0f18047994af67eabfb9420f9a321ce415c8bab makes me think so

isn't this something smartparens should do? b0f1804 makes me think so

smartparens is currently disabled in lispy-mode.
I personally think we should leave the default lispy behaviors and let the user change it in their private doom if they want.
Unless @hlissner wants to have this behavior homogenized whatever module is enabled.

id argue this should be a default then, to make it consistent with the rest of doom

I think harmonizing it with the rest of Doom would make sense as default. Adding the setting would also make it easy for users to find it and disable it if they want the default lispy behavior.

Makes sense to me, thanks!


[BUG] Test assertions failing

What is the bug?
A couple of asserts in the test suite are failing. For all these tests, the expected req.headers.connection is close whereas the actual value is keep-alive
Below are the tests that are failing.

 test: test/unit/client.test.js Disable keep alive agent
test: test/unit/connection.test.js Disable keep alive

Do you have any additional context?
test summary
 FAIL  test/unit/client.test.js 1 failed of 122 13s
 ✖ should be equal

 FAIL  test/unit/connection.test.js 2 failed of 86 4s
 ✖ should match pattern provided
 ✖ should match pattern provided

If that's the case, this could be a local issue.

@dblock Sure thing, I will take a look at this. I'll keep you posted on my findings.

I've checked one of the latest CI pipeline execution - Unit test and the same set of test cases seem to be passing. Starting to wonder if this issue is purely local/just my local.

I've checked one of the latest CI pipeline execution - Unit test and the same set of test cases seem to be passing. Starting to wonder if this issue is purely local/just my local.

Good. You should dig up why this happens!


fix: bump python core to 3.13.2

PR summary
This PR bumps the python core dependency up to 3.13.1 and also removes the use of tox from the travis build.  Instead, we'll just run "make ci" to build the project on travis.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 0.22.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Failed building javascript Bundle. Unable to resolve module react-native-multiple-select\index.js

Issue summary
Looks like there's no index.js in the package...
    5 |  */
> 6 | import MultiSelect from './lib/react-native-multi-select';
      |                        ^
   7 |
   8 | export default MultiSelect;
   9 |

 None of these files exist:
  * node_modules\react-native-multiple-select\lib\react-native-multi-select(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json)
  * node_modules\react-native-multiple-select\lib\react-native-multi-select\index(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json)
  *

Library version: 0.5.6
Steps to Reproduce

Import the package
Put the import as normally do inside render() with all its required props

<MultiSelect
    items={colaboradoresFormatados}
    uniqueKey="id"
    selectedItems={equipeId}
    onSelectedItemsChange={(selectedItems: number[]) => setEquipeId(selectedItems)}
/>

Try to run

Expected Behavior
I expected to run normally, like the example in npmjs.com, where i found the package...
Actual Behavior
It pop-ups an error  saying that this files doesn't exist like i said earlier... not sure what to do...

I am new to react native js, i'm also facing this issue only on web view android phone working fine not tested in ios,
i'm curious to know in react-native-multi-select.js line no 43, & 55 to 67 used ViewPropTypes.style insted of PropTypes.style first of all is it correct? if yes means please explaine to me why? how to send this propeties values to build component
if remove those lines it's working well


Carthage v0.6.0 does not compile

Having Carthage throwing the following error:
*** Checking out ReSwiftRouter at "0.6.0"
*** xcodebuild output can be found in /var/folders/ns/0h9r9v5908x4x67v5j9wvhvw0000gn/T/carthage-xcodebuild.yzuJSO.log
*** Building scheme "ReSwiftRouter-iOS" in ReSwiftRouter.xcodeproj
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /Users/marbetschar/Development/Valletti/App/Valletti/Carthage/Checkouts/ReSwiftRouter/ReSwiftRouter.xcodeproj -scheme ReSwiftRouter-iOS -configuration Release -derivedDataPath /Users/marbetschar/Library/Caches/org.carthage.CarthageKit/DerivedData/9.1_9B55/ReSwiftRouter/0.6.0 -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath ./ SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO (launched in /Users/marbetschar/Development/Valletti/App/Valletti/Carthage/Checkouts/ReSwiftRouter)

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/ns/0h9r9v5908x4x67v5j9wvhvw0000gn/T/carthage-xcodebuild.yzuJSO.log

Should be outdated by now.


Text can't show in diff.

When I commit, and view in gerrit diff, it can't show the diff text.
Origin screenshot1
Origin screenshot2
Octo screenshot1
Octo screenshot2

I no longer use Gerrit, but would be happy to accept a PR to fix this

I did following change, then it's OK!
div.com-google-gerrit-client-diff-DiffTable_BinderImpl_GenCss_style-difftable .CodeMirror pre span {   /*display: inline-block;*/   padding: 0 !important; }


Help with NTLM authentication

Hi,
I'm trying to get NTLM authentication to work:

local cURL = require "cURL"

local URLtest = "http://local.site/search"
local user = "testuser:password"

local c = cURL.easy()

c:setopt {
  url = URLtest,
  post = true,
  writefunction = io.write,
  username = user,
  postfields = '{}',
--  httpauth = true,
  [cURL.AUTH_NTLM] = true
}

c:perform():close()

The output is:
/usr/bin/lua5.3: [CURL-EASY][UNKNOWN_OPTION] An unknown option was passed in to libcurl (48)
If I change the last option to:
[cURL.NTLM] = true
the error is:
/usr/bin/lua5.3: ./ntlmtest:17: table index is nil
I'm currently using version 0.3.8.
I could not find any documentation or examples about using NTLM authentication. httpauth seems to turn on just Basic auth.
Thanks for your help!

I think you have to set CURLOPT_HTTPAUTH option.
httpauth = curl.AUTH_NTLM
May be you need to set passwd option as whell

In my earlier tests with httpauth it seemed that it accepted only boolean values.
Anyway now it works, thanks!


Showcase links

WHEN I click on the images of the applications I am taken to that deployed application

Completed, images not centered correctly.


Index_name Confusion of OpenSearch

The Parallel calls of '/run/{flow_id}' API with different index_name (by tweaks) in OpenSearch: A Test for Index_name Confusion.
when sequencially call API, No prob.
Any one help what the problem?
(I'm in 1.0.16)
Could We  Parallel calls a same flow_id '/run/{flow_id}' API with many different tweaks ?

Hello, I'm a coworker with songjinu.
We have confirmed that this phenomenon only occurs in certain components.

A component that has been inherited.
outputs are defined in the parent component
such as , RecursiveCharacterTextSplitterComponent / LCTextSplitterComponent , OpenSearchComponent / LCVectorStoreComponent

I suspect that the cause is exec_globals used when build_custom_class is called.
I'm testing deepcopy() outputs in a child class, but I'm not sure if this is the right approach, since the code is so complex.
if exec_globals[class_name].outputs is not None:
            exec_globals[class_name].outputs = copy.deepcopy(exec_globals[class_name].outputs)

@joaoguilhermeS, @ogabrielluiz
Are there good ways to avoid shared The result of outputs in concurrent processing ?

Hi @songjinu, I was slightly confused about what you meant, but now I understand. So how does it happen? You can pass different index names during each request you make to your Flow. I just tried it here on the latest version (1.1), and it seems to be working just fine.
Take a look on these environment variables, this might help you as well: https://docs.langflow.org/environment-variables#LANGFLOW_WORKERS


Easy-to-use jQuery Tag-It Widget

From a developer's perspective I love django-taggit. However, I realize that from a user's POV, writing and managing tags can feel cumbersome as they have to remember to format their input using a combo of quotes, commas or spaces. This is why I wrote this PR.
The intent of this code is to, by default, give users a simple widget that solves the mentioned problem and makes creating and deleting tags much easier.
It accomplishes this goal by replacing the text input widget with an interactive input field powered by jQuery Tag-It. It looks like this:

My hope is that this makes django-taggit an off-the-shelf complete solution for developers and that this plugin provides a framework that accommodates the planned roadmap.
I haven't written any unit tests for this, as I'm not sure how to test a javascript widget, but I'd be happy to take an attempt if someone has a good approach for it.

I'm closing this till I can get tests working.

Tests are working and my code changes are now less obtrusive than they were before.

Alright, for some reason the tests are working great on my local environment, but on Travis they are failing. It looks like maybe my test settings that are set up to use the widget template are not working.
Does anyone have an idea on how to get the new settings to be picked up properly?

I did a quick glance through the code and nothing stuck out as wrong to me. Maybe a misconfiguration with https://docs.djangoproject.com/en/1.10/ref/templates/api/#django.template.loaders.app_directories.Loader ?

@frewsxcv Thanks for the suggestion. I took a quick stab at trying to configure it correctly but didn't get it there just yet. I'm out of time right now to continue looking at it, but tomorrow  I should have some more time to do a deeper dive.

@charlex @frewsxcv why was this closed? Are there other efforts to add autocomplete?

Never mind. I see the comment on #33

...doesn't implement autocomplete, though it leaves the door open for it. I didn't want to include it because it felt like a can of worms, with its own set of problems, like adding an extra query to load all the available tags. The plugin I'm using definitely does have autocomplete built in.


differentiable oriented bounding box crop

This is pretty much the same bounding box crop that we used while pair coding, except this one has differentiability, documentation, and tests.
It's still terribly slow because I'm doing tensor indexing in a loop, but that should be easy to fix next now that I have a baseline with tests.

Taking a look now, please don't merge yet

I have addressed all your comments so far, @dellaert


Travis build

Might need some inspiration from https://github.com/arthurschreiber/tclspec/blob/master/.travis.yml

It was easier to get it working on CircleCI in the end, since they support ssh login so I could fiddle around with it.


x/tools/gopls: don't recreate the view when a go.mod file is created

This caused golang/vscode-go#363, because a go.mod was being created during that test, and the completion request was reaching the server at the time that the view was shutting down.
We either need to handle such a situation more gracefully, or we shouldn't shut down a view on go.mod creation. That would mean putting a mutex around a lot of the view's fields that we treat as immutable.

This is likely related to the flake seen here: https://storage.googleapis.com/go-build-log/ba9e1088/linux-386_f12e4b30.log.


Actions: OIDC Support for Storage

Summary
GitHub Enterprise Server will now include improved storage configuration security. GHES will now use the industry-standard OpenID Connect (OIDC) protocol to connect to object storage providers such as Amazon Web Services (AWS) Simple Storage Service (S3) and Azure Object Storage.
Intended Outcome
We have received feedback that the existing method of storage authentication -- using secret and access keys -- does not provide the level of required security. We will encourage customers instead to set up an OIDC Connect trust relationship between their GHES installation and their cloud storage provider to obviate the need for key exchange.
How will it work?
No response

🚢 This shipped with GHES 3.8: https://github.blog/2023-03-07-github-enterprise-server-3-8-is-now-generally-available/


Support joins with foreign keys represented as map[] datashapes.

Fixes #1568.

Coverage increased (+0.006%) to 89.594% when pulling c41eb93a42887a60635ebfeb7a0a336e3467b218 on kwmsmith:bugfix/join-foreign-keys into f13352a82a79e847c4ac3587adee09f22d9c3082 on blaze:master.

Coverage increased (+0.006%) to 89.594% when pulling c41eb93a42887a60635ebfeb7a0a336e3467b218 on kwmsmith:bugfix/join-foreign-keys into f13352a82a79e847c4ac3587adee09f22d9c3082 on blaze:master.

Thanks @postelrich - good to see the project moving forward!


Feature request: auto_parse: 0xCAFE -> 51966

My hex numbers all turn out as number 0, that's suboptimal. Could we use just + for the number conversion?
[   +'42.23', +'042.23', +'042', +'0042', +'0x42', +'0x42.23', +'0o42' ]
// =[ 42.23,     42.23,     42,      42,      66,        NaN,      34  ]

A few questions before I could answer. How do u use the parser because you're providing an array as exemple when it accept a string as first parameter ? Also, adding a "+" sign like in +'42.23' would be disregarded by the js engine and the parser won't recieve this information ?

The JS snippet above was just a quick overview of how the + operator would convert these strings. I've made a more detailed comparison of auto_parse and a dumb implementation of + here: https://gist.github.com/mk-pmb/f0b66d45bd9a8cda784d52d07ae29fad

OK, I didn't catch the trick around the "+" operator to cast a string into a number.
So if I understood well, you proposing to support decimal and octal notation in auto_parse (and eventually add auto_parse_decimal and auto_parse_octal) ?

Hexadecimal has highest priority fpr me, but octal and binary would be nice as well. However I'd rather not have hundreds of separate options for all possible number notations that JS might support in the future, but rather one option to make all values a number that would result in a finite, strictly self-equal number in JS code.

@mk-pmb FYI a feature was merged in that allows you to set your own auto_parse function.
https://github.com/adaltas/node-csv-parse/pull/162

Thanks! :+1:

Closing due to lack of activity.

What kind of activity is required at the moment?

I just meant that the discussion around this issue seems to be terminated. If I remember, the feature was implemented.


Update of immutable StatefulSet fields

We have the situation that we have to change the labels and selector match labels on a StatefulSet CRUD resource, that our operator manages. The problem is that the selector field is immutable and cannot be changed via a normal reconciliation. We also have to keep the deployed Pods alive, since the application holds data and is connected to possibly millions of clients.
Currently we restore the old labels/selectors in the update() method of the StatefulSet and our Service resources:
    @Override
    public @NotNull StatefulSet update(
            final @NotNull StatefulSet actual,
            final @NotNull StatefulSet target,
            final @NotNull HiveMQPlatform platform,
            final @NotNull Context<HiveMQPlatform> context) {
        final var logPrefix = platform.getLogPrefix();
        final var actualSpec = actual.getSpec();
        final var targetSpec = target.getSpec();
        // fix selector match labels
        final var actualSelectorMatchLabels = actualSpec.getSelector().getMatchLabels();
        final var targetSelectorMatchLabels = targetSpec.getSelector().getMatchLabels();
        if (!Objects.equals(actualSelectorMatchLabels, targetSelectorMatchLabels)) {
            LOG.debug("{} Restoring labels on StatefulSet", logPrefix);

            target.getMetadata().getLabels().putAll(actualSelectorMatchLabels);
            LOG.trace("{} Actual labels: {}", logPrefix, actual.getMetadata().getLabels());
            LOG.trace("{} Target labels: {}", logPrefix, target.getMetadata().getLabels());

            targetSpec.getTemplate().getMetadata().getLabels().putAll(actualSelectorMatchLabels);
            LOG.trace("{} Actual template labels: {}", logPrefix, actualSpec.getTemplate().getMetadata().getLabels());
            LOG.trace("{} Target template labels: {}", logPrefix, targetSpec.getTemplate().getMetadata().getLabels());

            targetSpec.getSelector().setMatchLabels(actualSelectorMatchLabels);
            LOG.trace("{} Actual selector match labels: {}", logPrefix, actualSpec.getSelector().getMatchLabels());
            LOG.trace("{} Target selector match labels: {}", logPrefix, targetSpec.getSelector().getMatchLabels());
        }

We have to disable SSA for the StatefulSet and Service resources (otherwise we'll trigger infinite updates, due to the SSA matcher and the label mismatch). But SSA anyway causes problems with the StatefulSet (if I have more details about that, I'll open another issue for that).
Beside that this solution works fine, as long we have an actual resource to compare the labels with. But when a new Service is created, it will of course have the new labels and selectors, and they don't match the (old) StatefulSet and Pods.
A possible solution would be to delete the StatefulSet with context.getClient().resource(statefulSet).withPropagationPolicy(DeletionPropagation.ORPHAN).delete();, fix the labels on running the Pods. Then the normal reconciliation will create a new StatefulSet and update the existing Services.
Our problem is that we don't know where to add this logic in the operator workflow. Ideally this should only be executed once, when the custom resource is initialized. We should only need the custom resource instance and the K8s client for this.

Hi @Donnerbart , this does not seems to be a standard use case for sure :)
For the beginning some notes:

there are some problems with SSA in some cases in k8s it is ok no to use it
you can alway just override the matcher method and enhance / customize the implementation for your demands. Note that this is just an optimization, making an update all the time should also work

Regarding how to exactly do this is tougher, but for now just a hint, you can also override the whole reconciliation logic for a dependent resource, this is the top level function called:
https://github.com/operator-framework/java-operator-sdk/blob/69711cf346d75331a61616bcfe2fd7015c93434b/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/dependent/DependentResource.java#L25-L25
So you can customize that as you want, even build your own class hierarchy etc. So basically you don't necessarily need to match this logic with the current structure (Creator, Updator, Matchers etc..), this was an intentional design decision exactly for these cases where it does not fit a standard model. Of course it is much harder than and more code, and study (also some aspects of workflows) but this make it doable.

I gave it a try this morning and came up with this method, that I call at the beginning of the desired() method:
    private final @NotNull Set<String> labelAndSelectorCheckDone = ConcurrentHashMap.newKeySet();

    private void fixLabelsAndSelector(
            final @NotNull HiveMQPlatform platform,
            final @NotNull Context<HiveMQPlatform> context,
            final @NotNull Map<String, String> desiredLabels,
            final @NotNull Map<String, String> desiredSelectorLabel) {
        final var logPrefix = platform.getLogPrefix();
        final var platformIndex = platform.getMetadata().getNamespace() + "-" + platform.getMetadata().getName();
        if (!labelAndSelectorCheckDone.add(platformIndex)) {
            return;
        }
        final var statefulSet = context.getSecondaryResource(StatefulSet.class).orElse(null);
        if (statefulSet == null) {
            return;
        }
        final var statefulSetLabels = statefulSet.getMetadata().getLabels();
        final var statefulSetSelectorLabels = statefulSet.getSpec().getSelector().getMatchLabels();
        if (Objects.equals(statefulSetLabels, desiredLabels) &&
                Objects.equals(statefulSetSelectorLabels, desiredSelectorLabel)) {
            return;
        }
        LOG.info("{} Deleting StatefulSet with outdated labels or label selector", logPrefix);
        LOG.trace("{} Actual labels: {}", logPrefix, statefulSetLabels);
        LOG.trace("{} Target labels: {}", logPrefix, desiredLabels);
        LOG.trace("{} Actual selector match labels: {}", logPrefix, statefulSetSelectorLabels);
        LOG.trace("{} Target selector match labels: {}", logPrefix, desiredSelectorLabel);
        final var client = context.getClient();
        try {
            final var statusDetails = client.resource(statefulSet)
                    .withPropagationPolicy(DeletionPropagation.ORPHAN)
                    .withTimeoutInMillis(TimeUnit.SECONDS.toMillis(5000))
                    .delete();
            LOG.info("{} Deleted StatefulSet: {}", logPrefix, statusDetails);
        } catch (final Exception e) {
            labelAndSelectorCheckDone.remove(platformIndex);
            LOG.warn("{} Cannot not delete outdated StatefulSet: {}", logPrefix, e.getMessage());
        }
        // fix the Pod labels, so that reconciled Services can match the Pods right away
        try {
            client.pods().inNamespace(platform.getMetadata().getNamespace()).list().getItems().forEach(pod -> {
                pod.getMetadata().getLabels().putAll(desiredLabels);
                client.resource(pod).update();
            });
        } catch (final Exception e) {
            labelAndSelectorCheckDone.remove(platformIndex);
            LOG.warn("{} Cannot not update labels on Pods: {}", logPrefix, e.getMessage());
        }
        throw new IllegalStateException("StatefulSet needs to be re-created, stopping current reconciliation");
    }

It's quite a hack and I hope my assumption that StatefulSetResource extends CRUDKubernetesDependentResource<StatefulSet, HiveMQPlatform> is a singleton is correct (regarding the scope of labelAndSelectorCheckDone).
So basically once on the first reconcile I'm checking if there is already a StatefulSet with the old/outdated selector, if so delete it, fix the pods and then interrupt the running reconciliation.
Beside the huge stacktrace I didn't see any side effects so far (e.g. with the internal caches and informers etc.).
If this doesn't ring any alarm bells, this would have the lowest impact/effort for us, so we can stick with the default CRUD implementation as much as possible.

I think it is fine, if it is working it's working.
( As I mentioned it is intentionally reconcile() and not just CRUD methods on top level interface. Some cases needs sepcial logic and that is fine.  )
Will close the issue if no objections.


Support color and font tags in log?

I was hoping to color some lines based on content.  Reading the blessed docs, it seems like I might be able to do something like "{red-fg}foo{/red-fg}", but this doesn't work.  I guess I could just use terminal escape codes, but I'm not positive that those wouldn't have a negative impact somewhere.
Any ideas?

I tried the colors library, at https://www.npmjs.com/package/colors, and it works, mostly...
var colors = require('colors/safe');
log.push(colors.red('hello')); works, except as the last line.  (This might be some artifact because I'm actually doing all this through Clojurescript).

yes, this is a good approach. I will add interactive=false internally in the component so it will always behave correctly. thanks!


Can you update buildToolsVersion in Android for react native ?

Now the default buildToolsVersion is "23.0.1", but if I update the gradle version to 3.3 in the main project, it would alert that
Error:The SDK Build Tools revision (23.0.1) is too low for project ':react-native-vector-icons'. Minimum required is 25.0.0
Update Build Tools version and sync project

Thanks!

There's a bunch of these issues/PRs already, have a look at https://gist.github.com/tlvenn/2c8922ec379b48ff421ed0acd6dc824f for a workaround.

@oblador Hej, is there any more info on how to apply the workaround you suggested? Is that workaround still useful? In react-native-firebase there's a section like this
def DEFAULT_COMPILE_SDK_VERSION = 27
def DEFAULT_BUILD_TOOLS_VERSION = "27.0.3"
def DEFAULT_TARGET_SDK_VERSION = 26
def DEFAULT_SUPPORT_LIB_VERSION = "27.0.2"

android {
  compileSdkVersion rootProject.hasProperty('compileSdkVersion') ? rootProject.compileSdkVersion : DEFAULT_COMPILE_SDK_VERSION
  buildToolsVersion rootProject.hasProperty('buildToolsVersion') ? rootProject.buildToolsVersion : DEFAULT_BUILD_TOOLS_VERSION
  defaultConfig {
    minSdkVersion 16
    targetSdkVersion rootProject.hasProperty('targetSdkVersion') ? rootProject.targetSdkVersion : DEFAULT_TARGET_SDK_VERSION
    versionCode 1
    versionName "1.0"
    multiDexEnabled true
  }
  buildTypes {
    release {
      minifyEnabled false
    }
  }
  productFlavors {
  }
}

Does this seem like a reusable solution?

Ok, I found out how to change buildToolsVersion "on the fly" from the link from @oblador but with my changes in the comment https://gist.github.com/tlvenn/2c8922ec379b48ff421ed0acd6dc824f#gistcomment-2627244


AQCU-1229: report header update

Change "Primary Time Series" to "Selected Time Series". Ignore the branch name...I forgot to rebranch before starting this.

Coverage remained the same at 98.889% when pulling 38b716122795c2f3a6e69abc35802c5bee3174fb on lindsaycarr:aqcu1212 into 8c8f5ab4fe49f1448d5ab5d20b8f2121c041e14f on USGS-R:master.


hummingbot integration to support Dex on harmony

Description
Build a DEX connector in hummginbot to connect to DEX on Harmony blockchain. (https://github.com/CoinAlpha/gateway-api)
Noted, hummingbot team is doing module refactoring, please keep a closer look and contact the hummingbot dev team for the contribution details.  This is an external bounty to hummingbot team. Their acceptance is the key criteria.
Context
hummingbot is the decentralized market maker (https://hummingbot.io/about/).
Harmony ONE token was the first token launched with hummingbot for market making.
Since there are DEX launched on Harmony blockchain, we would like to build a connector in hummingbot, so that arbitrage strategy can be developed between DEX and CEX for harmony tokens.
There is already uniswap connector built-in hummingbot (https://github.com/CoinAlpha/gateway-api/blob/master/src/services/uniswap.js), so the new harmony dex connector can follow a similar approach.
https://docs.hummingbot.io/exchange-connectors/overview/
https://hummingbot.io/blog/2020-09-what-is-cross-exchange-market-making/
https://venomdao.medium.com/introducing-venomdao-viper-protocol-a-cross-chain-multi-product-defi-dao-launching-on-harmony-7ac84a7d76d3
https://medium.com/harmony-one/harmony-roadmap-cross-chain-cross-exchange-pools-3b7230d1c295
Acceptance Criteria

[ ] Harmony DEX Connector PR to hummingbot repo and accepted by hummingbot team
[ ] Pass the test, security requirement by the hummingbot team
[ ] Arbitrage strategy between CEX and DEX on harmony blockchain

Reward
US$3000 equivalent amount of [Harmony ONE token] (https://www.coingecko.com/en/coins/harmony).

I don't understand what do you mean by arbitrage strategy between CEX and DEX? Because wouldn't the users of humingbot will be able to arbitrage across exchanges after deploying the connector?

I also have a question. Wondering what DEX are you specifically talking about here? Is it Viperswap?

Oh. I found the viperswap doc attached in this bounty. I guess it is viperswap then!

Also I am new to this bounty system. Wondering whether there is any way to let people know that I am working on this bounty already, or it is more a competitive thing, like whoever builds it the first will take the rewards?

Ok. Just started this project on Gitcoin to let people know I am working on it. Plan to start making some coding progress next week.

@fanglinlu I think we'll use venomswap protocol. Because visperswap exchange is built on top of this protocol. Am I right?

I also got notified the development team at humingbot about the PR for a heads-up.

@fanglinlu I found out that visperswap which is also venomswap is Uniswap fork and there's already an implementation of connector on Humingbot. I'm not sure how we're supposed to connect visperswap which has a subgraph of uniswap to Humingbot again?
Could you please explain it?

@MohammedNagdy I am new to this bounty system. It seems you are also interested in this bounty. Should we both work on it then? Also do you mean you notified the hummingbot development team or you got notified by the hummingbot team?

@fanglinlu , @MohammedNagdy as I mentioned, this is an external bounty to work on hummingbot.  Please actively engage hummingbot team for their new architecture to add the connectors.

@LeoHChen @fanglinlu  already notified the development team at humingbot and they're expecting our pull request. Plus @LeoHChen what you have in the bounty post isn't a connector it's an API gateway.
This is an example of a binance connector https://github.com/CoinAlpha/hummingbot/tree/master/hummingbot/connector/exchange/binance

Mohammed, I wonder how we can collaborate on this one. Do you want to chat on telegram?

It seems sid from the hummingbot support team is asking the hummingbot team about building this connector. Mohammed, you also mentioned do a PR. Wondering whether there is any update on that?

I also just emailed the hummingbot team through here<EMAIL_ADDRESS>Here is a useful doc about how connectors are usually built https://hummingbot.zendesk.com/hc/en-us/articles/900004506986

@fanglinlu my telegram is @monagdy

Hi Jonathan, feel free to add me on telegram: @fanglinlu

Ok. I created a fork of the hummingbot code and added you two as collaborators.

Awesome @fanglinlu thank you, I'll start working today on the connector. I think we have to let @LeoHChen that us three are working together on the connector.

This link is about the steps we need to follow for contributing to the hummingbot codebase https://github.com/CoinAlpha/hummingbot/blob/master/CONTRIBUTING.md

This doc seems useful too https://docs.hummingbot.io/developer/overview/

Update from Hummingbot CEO Michael today:
There's no documentation yet for Hummingbot Gateway since its architecture and base code is still in flux. Since we're still designing how best to support various L1 and L2 protocols ourselves, we don't yet support external developers building on it, although we freely encourage you to fork it and make use of it as you see fit. In 2-3 months, Gateway's architecture should be standardized enough where we can create developer docs and then start to review/merge in external contributions.

we are closing this bounty for now with the advice from Hummingbot's CEO.  Will re-open a new one once the new gateway architecture is more clear and standardized for external contributors.


feat: implement ReadObject method for gRPC

Part of the changes for #58

I am going to ignore the coverage warnings.  I think we can afford the coverage drop, and future PRs should bring it up anyway.


Should be able to run containerd-shim inside a specified cgroup.

Orchestrator may want to run containerd-shim inside specified cgroup to charge the resource usage to a specific user/sandbox.
/cc @crosbymichael

We can implement this by only providing a cgroup path that the shim should be placed in.


attempt to invalidate cache

Description
tries to invalidate cache without being merged
Type of change

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

References
https://github.com/napari/napari/issues/1527
How has this been tested?

example: all tests pass with my change

Final checklist:

[X] My PR is the minimum possible work for the desired functionality
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works

the default ci doesn't run on mac with pytbon 3.7! I opened up another empty PR to reset the cache, we should merge this empty PR and have the ci reset the cache: https://github.com/napari/napari/pull/1548


Submission of new plugin list entry "Leaflet.PolylineMeasure"

Submission of new plugin list entry "Leaflet.PolylineMeasure"

Looks good :+1:


[FEATURE] write and ADR on the new Builder API

As a result of heavy refactoring, we have a new API. We should discuss and document it.

The ADR comes either together with #675 or after it.

The Builder API is still in the making, closing this issue.


Error: "name_prefix" can only alphanumeric characters and ()./_- symbols

I've tried running this from both Windows (PowerShell) and Linux. I consistently get the same error.

I'm far from a Terraform expert, but I cannot see anything that looks wrong in that file. I've tried to investigate those variables, but it doesn't shed any light...
terraform console
> local.lt_name
(known after apply)
> var.name
(known after apply)

I captured debug logs and I see a lot of two different types of messages:

[INFO]  ReferenceTransformer: reference not found: "<xxxx>"
[WARN]  Provider "<yyyy>" produced an invalid plan for <zzzz>, but we are tolerating it because it is using the legacy plugin SDK.

The actual names for x, y, and z change, but those messages pop up a lot. Not sure if that means more to anyone else than it does to me, but those two messages account for 90% of the log.

Thank you for creating this issue. I will work on a fix.


Support for the new fileformat for the latest beta

Trying to convert a note file created on the latest beta gives an error:
exceptions.UnsupportedFileFormat('unsupported file format')

Is it possible to support the new file format.

Try --policy loose option.
Example:
supernote-tool convert --policy loose -a -t pdf your.note converted.pdf

I prepared the option for future file format changes.
When you give the option, the parser try to parse unsupported file.
If the beta file format is not big change from stable version, the option is helpful.
(Of course if the file format has changed significantly, the parser returns exception.)
I'm not in the Early Testers Program, so I can't support new file format soon.
If you could share your note file created by latest beta, I might be able to help you more.

Thanks. --policy loose does the conversion. The new beta version supports both internal and external links. A new version was released today. I'll create a sample file which includes all the features and post it here.

Here is a sample .note file and the corresponding .pdf as exported by the device.
note file
exported file

Thank you for sharing sample files.
Chauvet 2.6.19 was now released while preparing beta support.
I have uploaded a support of Chauvet 2.6.19 at the latest commit (19583d484053bf57fede5d317a853729a2709156).


Configuration for Different Game Types

I really like what you have built here! I am considering using it for my next Pathfinder game. I am currently playing a D&D3.5 game and while this setup works with some workarounds I am hoping you'd be willing to expand the scope to allow for a JSON config file of sorts to setup the character sheet with the appropriate skills and such. I can fork the project if you aren't interested but I'd like to help contribute to your project if you're interested.
Let me know. I have a few other ideas.

Hi, glad you like it! That's an interesting idea. I must admit it, as I'm still Learning JS, I don't know how to go about doing that. I also never really planned to support anything other than Pathfinder. So the underlying structure/architecture might not be right for 3.5. However if you want to make a branch I'd be happy to work together.

Just an FYI, I'm looking at lot of traveling over the next month so wont have a lot of free time (as evident by my late reply, apologies).


[BUG] Python controller failed to read attribute with Chip Stack Error 50

Reproduction steps
I have used python controller to done a stress test on my RPI sample dut (all-clusters-app) on Read-write operation for 10000 ietration. After completion of the 10000 ietration i found that the 350 where failed with the below Traceback error while reading the onoff attribute from the ON-OFF cluster

Traceback (most recent call last):
File "/home/ubuntu/stress_test/matter-qa/src/matter_qa/scripts/reliability_scripts/TC_ON_OFF.py", line 77, in verify_switch_on_off_cluster
after_operation_cluster_status = await self.read_single_attribute_check_success(cluster=clusters,
File "/home/ubuntu/stress_test/matter-qa/src/matter_qa/library/helper_libs/matter_testing_support.py", line 876, in read_single_attribute_check_success
result = await dev_ctrl.ReadAttribute(node_id, [(endpoint, attribute)], fabricFiltered=fabric_filtered)
File "/home/ubuntu/matter_cntrl/connectedhomeip/no/lib/python3.10/site-packages/chip/ChipDeviceCtrl.py", line 1421, in ReadAttribute
res = await self.Read(nodeid,
File "/home/ubuntu/matter_cntrl/connectedhomeip/no/lib/python3.10/site-packages/chip/ChipDeviceCtrl.py", line 1359, in Read
return await future
chip.exceptions.ChipStackError: Chip Stack Error 50

Below the summary of the 10000 iterations
TC_ON_OFF_10000_iter_summary.json
Sample lod of failed iteration:
log_2024-05-24_22-12-27.log
Bug prevalence
Whenever i do this
GitHub hash of the SDK that was being used
7a470f553d55664b1f202008248e49db775f511c
Platform
python, raspi
Platform Version(s)
RPI-4, 8GB RAM
Anything else?
No response

50 is CHIP_ERROR_TIMEOUT.  This could happen for all sorts of reasons, depending on the exact setup and the exact timeouts being used, including cpu load, network hiccups, etc.

closing this issue for now and following it up in a different issue


include/zephyr/net: Add 'brief' to group description

So it doesn't extend previous directive.
This is cherry-picked from #61994 as that PR might take some time to get merged and the change makes sense.
FYI @edersondisouza

@jukkar
Obviously not opposed to the change as it's sometimes nice to be explicit, but where is the problem showing? @brief is implicit in this instance, and AFAICT it's looking OK everywhere I looked, i.e. https://docs.zephyrproject.org/latest/connectivity/networking/api/wifi.html#api-reference and https://docs.zephyrproject.org/latest/doxygen/html/group__wifi__mgmt.html#details
Just pointing it out to make sure that this is not instead the symptom of an issue in #61994.


simulator api version

ubuntu 18.04
carla 0.9.3
when running the manual control mode, I got the following warning, and I am wondering how I can get the simulator API updated?
WARNING: Version mismatch detected: You are trying to connect to a simulator that might be incompatible with this API
WARNING: Client API version     = 0.9.3
WARNING: Simulator API version  = 0.9.2-131-g39f8e34b-dirty

I think you should use the 0.9.3 carla simulator (pre-compiled package).
From what I understand about the Warning Message, you are running the 0.9.2 simulator with 0.9.3 Client API.

Have you called
make PythonAPI
in your Carla folder?

Have you called
make PythonAPI
in your Carla folder?

Hi, I have rebuild the 0.9.4, and also downloaded the pre-compiled version. This time, when I make PythonAPI , I got the err:
Setup.sh: llvm-6.0-ex already installed.
Setup.sh: boost-1.69.0 already installed.
Setup.sh: rpclib-v2.2.1_c1 already installed.
Setup.sh: googletest-1.8.0-ex already installed.
Setup.sh: Generating CMake configuration files.
Setup.sh: Success!
BuildLibCarla.sh: Building LibCarla "Client" configuration.
[1/4] Building CXX object LibCarla/cma...__/source/test/client/test_image.cpp.o
FAILED: LibCarla/cmake/test/CMakeFiles/libcarla_test_client_release.dir/__/__/source/test/client/test_image.cpp.o
/usr/bin/clang++-6.0  -DBOOST_ERROR_CODE_HEADER_ONLY -DLIBCARLA_ENABLE_PROFILER -DLIBCARLA_IMAGE_WITH_PNG_SUPPORT=true -DLIBCARLA_WITH_GTEST -I../../LibCarla/cmake/../source -I../boost-1.69.0-install/include -I../rpclib-v2.2.1_c1-libstdcxx-install/include -I../googletest-1.8.0-ex-libstdcxx-install/include -I../../LibCarla/cmake/../source/test -std=c++14 -pthread -fPIC -Werror -Wall -Wextra -std=c++14 -pthread -fPIC -Werror -Wall -Wextra   -O3 -DNDEBUG -MD -MT LibCarla/cmake/test/CMakeFiles/libcarla_test_client_release.dir/__/__/source/test/client/test_image.cpp.o -MF LibCarla/cmake/test/CMakeFiles/libcarla_test_client_release.dir/__/__/source/test/client/test_image.cpp.o.d -o LibCarla/cmake/test/CMakeFiles/libcarla_test_client_release.dir/__/__/source/test/client/test_image.cpp.o -c ../../LibCarla/source/test/client/test_image.cpp
In file included from ../../LibCarla/source/test/client/test_image.cpp:10:
In file included from ../../LibCarla/cmake/../source/carla/image/ImageIO.h:9:
In file included from ../../LibCarla/cmake/../source/carla/image/ImageIOConfig.h:55:
In file included from ../boost-1.69.0-install/include/boost/gil/extension/io/png.hpp:11:
In file included from ../boost-1.69.0-install/include/boost/gil/extension/io/png/read.hpp:13:
../boost-1.69.0-install/include/boost/gil/extension/io/png/tags.hpp:25:14: fatal error: 'png.h' file not found
    #include <png.h>
             ^~~~~~~
1 error generated.
[2/4] Building CXX object LibCarla/cma...__/source/test/client/test_image.cpp.o
FAILED: LibCarla/cmake/test/CMakeFiles/libcarla_test_client_debug.dir/__/__/source/test/client/test_image.cpp.o
/usr/bin/clang++-6.0  -DBOOST_ASIO_ENABLE_BUFFER_DEBUGGING -DBOOST_ERROR_CODE_HEADER_ONLY -DLIBCARLA_ENABLE_PROFILER -DLIBCARLA_IMAGE_WITH_PNG_SUPPORT=true -DLIBCARLA_WITH_GTEST -I../../LibCarla/cmake/../source -I../boost-1.69.0-install/include -I../rpclib-v2.2.1_c1-libstdcxx-install/include -I../googletest-1.8.0-ex-libstdcxx-install/include -I../../LibCarla/cmake/../source/test -std=c++14 -pthread -fPIC -Werror -Wall -Wextra -std=c++14 -pthread -fPIC -Werror -Wall -Wextra   -g -MD -MT LibCarla/cmake/test/CMakeFiles/libcarla_test_client_debug.dir/__/__/source/test/client/test_image.cpp.o -MF LibCarla/cmake/test/CMakeFiles/libcarla_test_client_debug.dir/__/__/source/test/client/test_image.cpp.o.d -o LibCarla/cmake/test/CMakeFiles/libcarla_test_client_debug.dir/__/__/source/test/client/test_image.cpp.o -c ../../LibCarla/source/test/client/test_image.cpp
In file included from ../../LibCarla/source/test/client/test_image.cpp:10:
In file included from ../../LibCarla/cmake/../source/carla/image/ImageIO.h:9:
In file included from ../../LibCarla/cmake/../source/carla/image/ImageIOConfig.h:55:
In file included from ../boost-1.69.0-install/include/boost/gil/extension/io/png.hpp:11:
In file included from ../boost-1.69.0-install/include/boost/gil/extension/io/png/read.hpp:13:
../boost-1.69.0-install/include/boost/gil/extension/io/png/tags.hpp:25:14: fatal error: 'png.h' file not found
    #include <png.h>
             ^~~~~~~
1 error generated.
ninja: build stopped: subcommand failed.
Util/BuildTools/Linux.mk:83: recipe for target 'LibCarla.client' failed
make: *** [LibCarla.client] Error 1

I have no idea what should I do there

I got the same problem, I built Carla0.9.3 from source and I downloaded the precompiled Carla0.9.4. I can start Carla0.9.3 and I get the following error when typing python manual_control.py:
WARNING: Client API version     = 0.9.3
WARNING: Simulator API version  = 0.9.3-51-ga0c2c21

In Carla0.9.4 I get the following:
WARNING: Client API version     = 0.9.3
WARNING: Simulator API version  = 0.9.4

I have the impression it has to do with environmental variables, since I removed a version of anaconda I had and I removed it from my .bashrc file, and now I have this problem.

I have a similar issue. I compiled the PythonAPI for Ubuntu 18.04 (python 3.6) using the following Dockerfile:
FROM ubuntu:18.04

ENV DEBIAN_FRONTEND=noninteractive

RUN apt-get update && \
    apt-get install -y wget software-properties-common git python3-distutils && \
    apt-get install -y build-essential clang-7 lld-7 g++-7 cmake ninja-build \
        python-dev python3-dev \
        libpng-dev libtiff5-dev libjpeg-dev tzdata curl unzip autoconf libtool rsync

RUN wget https://bootstrap.pypa.io/get-pip.py && \
    python2 get-pip.py --user --upgrade && \
    python3 get-pip.py --user --upgrade

RUN git clone https://github.com/carla-simulator/carla.git /carla
WORKDIR /carla
RUN git checkout 0.9.6

RUN update-alternatives --install /usr/bin/clang clang /usr/lib/llvm-7/bin/clang 170 && \
    update-alternatives --install /usr/bin/clang++ clang++ /usr/lib/llvm-7/bin/clang++ 170

RUN sed -i 's/bdist_egg/bdist_wheel/g' Util/BuildTools/BuildPythonAPI.sh && \
    make PythonAPI

Then I use docker cp to extract the wheel from a container and install the wheel using pip.
$ docker build -t carla_whl:0.9.6 PythonAPI
$ docker run -it --rm --name carla_whl carla_whl:0.9.6
$ docker cp carla_whl:/carla/PythonAPI/carla/dist/carla-0.9.6-cp36-cp36m-linux_x86_64.whl PythonAPI/carla/dist/
$ docker stop carla_whl

$ pip3 install --user PythonAPI/carla/dist/carla-0.9.6-cp36-cp36m-linux_x86_64.whl
Processing ./PythonAPI/carla/dist/carla-0.9.6-cp36-cp36m-linux_x86_64.whl
Installing collected packages: carla
Successfully installed carla-0.9.6

But I got the following warning when running manual_control.py.
$ ./PythonAPI/examples/manual_control.py
pygame 1.9.6
Hello from the pygame community. https://www.pygame.org/contribute.html
INFO: listening to server <IP_ADDRESS>:2000

Welcome to CARLA manual control.

Use ARROWS or WASD keys for control.

    W            : throttle
    S            : brake
    AD           : steer
    Q            : toggle reverse
    Space        : hand-brake
    P            : toggle autopilot
    M            : toggle manual transmission
    ,/.          : gear up/down

    TAB          : change sensor position
    `            : next sensor
    [1-9]        : change to sensor [1-9]
    C            : change weather (Shift+C reverse)
    Backspace    : change vehicle

    R            : toggle recording images to disk

    CTRL + R     : toggle recording of simulation (replacing any previous)
    CTRL + P     : start replaying last recorded simulation
    CTRL + +     : increments the start time of the replay by 1 second (+SHIFT = 10 seconds)
    CTRL + -     : decrements the start time of the replay by 1 second (+SHIFT = 10 seconds)

    F1           : toggle HUD
    H/?          : toggle help
    ESC          : quit

WARNING: Version mismatch detected: You are trying to connect to a simulator that might be incompatible with this API
WARNING: Client API version     = 0.9.6-dirty
WARNING: Simulator API version  = 0.9.6

What is the difference between the "dirty" version and the regular one?

@tn00364361 Did you solved the error ?


loss often keeps zero

When I train my dataset, the loss often keeps zero.

I have the same problem


ElvUI and BIS Redux Skin Conflict?

When I have ElvUI enable at the same time I get this strange thin border around the manager window. After some troubleshooting I have found that if disable Ace 3 it resolves this strange border but of course removes some of my skins so I am not sure what the conflict with the two is. Here is a picture of this thin border https://imgur.com/a/1luhnjF.

Corrected corrupted file in my profile

Thought it was a corrupted file but after about an 30 mins of resetting up everything the line showed back up again. I have disabled everthing minus ElvUI and BIS Redux. No idea on this onel


tsc --watch should show more information(eg: time) when recompiling

Show date and time when using --watch flag
Scenario 1:
c:\Work\TypeScript>node built/local/tsc.js --watch hello.ts
9/28/2015, 9:12:06 AM - message TS6042: Compilation complete. Watching for file changes.
9/28/2015, 9:12:12 AM - message TS6032: File change detected. Starting incremental compilation...
9/28/2015, 9:12:13 AM - message TS6042: Compilation complete. Watching for file changes.

Scenario 2:
c:\Work\TypeScript>node built/local/tsc.js --watch hello.ts
9/28/2015, 9:37:36 AM - message TS6042: Compilation complete. Watching for file changes.
9/28/2015, 9:37:39 AM - message TS6032: File change detected. Starting incremental compilation...
hello.ts(1,19): error TS1005: ')' expected.
9/28/2015, 9:37:40 AM - message TS6042: Compilation complete. Watching for file changes.

Note:  There is no date and time for the generated error. I'm not sure if it is needed.
Proposed fix for #4986

Hi @MartyIX, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Please review the changes and tell me if it can be done better. Thanks :)

Seems like a nice change. From a UX perspective I think it may be better to format it as (time, date) rather than (date, time). The time is your high order bit as far as verifying that the most recent change you made has been checked, so then that information is all cleaned aligned with the left edge. In fact I might say that date shouldn't be shown at all.

+1 to not showing the date (i.e. use toLocaleTimeString instead)

also do you need the time for error messages, or just messages like "Compilation complete. Watching for file changes.", i.e. not for reportDiagnostics calls?

@danquirk Thank you for the feedback. I was trying to find a date/time format used in TypeScript code but I didn't find any such occurence and that's why I used the most simple function without any advanced formatting.
Which JS Date function should I use then?

I think the more appropriate thing to do would be to create a diagnostic that takes a date/time string.

So there are a few issues here:

date/time format - I can change it to toLocaleTimeString as you suggested
Should ALL messages be prefixes with time? (I mean error messages as shown in scenario 2 above)
@DanielRosenwasser: can you be more specific what you mean? Thank you

No, just the --watch messages.
We have a file diagnosticMessages.json. What you'd do is change the message keys in that file for the following, and then pass in the time string when reporting the diagnostics.

"Compilation complete. Watching for file changes." to "{0} - Compilation complete. Watching for file changes."
"File change detected. Starting incremental compilation..." to "{0} - File change detected. Starting incremental compilation..."

ad 3)
I'm getting the following output when I try to use diagnosticMessages.json:
message TS6042: 1:55:40 PM - Compilation complete. Watching for file changes.
message TS6032: 1:56:52 PM - File change detected. Starting incremental compilation...
message TS6042: 1:56:53 PM - Compilation complete. Watching for file changes.

@DanielRosenwasser Is it the desired output though? I would (as a user) expect the following output:
1:55:40 PM - message TS6042: Compilation complete. Watching for file changes.
1:56:52 PM - message TS6032: File change detected. Starting incremental compilation...
1:56:53 PM - message TS6042: Compilation complete. Watching for file changes.

@MartyIX, i think there is an issue for this already, see #717; we should add either a new reportWatchDiagnostic or pass a new argument to reportDiagnotic that will not emit the code. the code ( i.e.: message TS6042) is totally useless for watch users.

@mhegazy That's what my original code does (essentially :)) ;-) Personally the approach with reportWatchDiagnostic sounds better to me.

i am fine reporting the time as part of a reportWatchDiagnostic instead of having in the diagnostic message itself, similar to your current change. up to you.

This is current output on my computer:
c:\Work\TypeScript>node built/local/tsc.js --watch hello.ts
8:16:33 PM - Compilation complete. Watching for file changes.
8:16:49 PM - File change detected. Starting incremental compilation...
hello.ts(1,19): error TS1005: ')' expected.
8:16:49 PM - Compilation complete. Watching for file changes.
8:16:50 PM - File change detected. Starting incremental compilation...
8:16:51 PM - Compilation complete. Watching for file changes.

:+1:

:-)

Perfect - thanks @MartyIX!


fails when dir not exist?

Traceback (most recent call last):
File "/home/l33tname/git/bgt/chapter-marker/chapter_marker/tray.py", line 273, in save
self.markers.persist()
File "/home/l33tname/git/bgt/chapter-marker/chapter_marker/tray.py", line 183, in persist
with open(dbpath, "wb+") as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/l33tname/.local/share/chapter-marker/bgt288.db'

os.makedirs(dirname(self.location,exist_ok=true) vor dem write in self.persist


Fix for warnings on console during development

Issue: Props being passed to DOM as is, causing warnings during development
Fix: Props were being passed to placeholder divs which were not being recognised on the DOM. So, commented the props object being passed.

After:

Before:

This PR has been closed since the fix has been merged into develop in commits 1 and 2.
We were passing props to divs, (wrapping fallback component), which was the cause of this warning