max/min

From #348: Lean 4 defines max and min in the prelude, while Lean 3 (as of https://github.com/leanprover-community/lean/pull/609) defines them differently as part of linear_order. We will need to figure out how to resolve this conflict.
Probably the easiest thing would be to get notation typeclasses Max and Min into core.

The problem is that there's a bunch of uses of min and max in mathlib3 and they all mean linear_order.min or linear_order.max. If we directly translate that stuff to mathlib4 (and we keep the current prelude) then we'll need to fully specify  LinearOrder.min and LinearOrder.max everywhere to avoid using the prelude definitions. That seems like it will invite confusing errors.

Probably the easiest thing would be to get notation typeclasses Max and Min into core.

@gebner I don't follow how that would help. Would the LinearOrder typeclass then extend Min and Max and override the definitions? Would we need to be worried about overlapping instances?

Yes, LinearOrder should extend Min and Max (just as it extends LE).  The rules for overlapping instances are the same as for LE: all definitions of ≤ for a type need to be defeq.

Fixed by https://github.com/leanprover/lean4/pull/1765
We just need to add extends Max and Min to LinearOrder tomorrow.


What is the difference wrt LMQL?

What is the difference of your library vs LMQL?

LMQL mixes two approaches to controlling output - prompt engineering and constraints.
In its constraint page you can see what can be done with constraints (that prevent the LLM from generating tokens that violate the format). Note that JSON Schema is not there.
JSON Schema is done via prompt engineering and verification, similar to Typechat.
This library only uses the constraint approach, and is able to correctly filter the tokens allowed at the next timestep that can eventually turn into correct output, ensuring format-compliant outputs in the first iteration.

Thanks for the swift reply!


use absolute path for imports everywhere

let's use autonomio.subpackage.function and not ..subpackage.function

this is done in the api-dev now, so will be merged with Dev end of this week. And master if things keep going like today (zero issues).


RTSP stopped working once I block the internet access of the camera

Hello roleoreleo,
RTSP server is working fine with internet access. However it stopped working once I blocked the internet access of the camera and restart it.
Is that expected behavior?
Version is 0.2.2, upgraded recently.
I remembered it worked without internet access in one of the previous version. (maybe I am wrong)
Could you please confirm that?
Thanks

This is an unresolved issue.
When you block the traffic internally, shutting down the processes, it works but if you block the connection through a firewall, the cam stops working (probably a memory leak).
I don't know why, it depends on the yi programs.
https://github.com/roleoroleo/yi-hack-MStar/issues/149

This is an unresolved issue.
When you block the traffic internally, shutting down the processes, it works but if you block the connection through a firewall, the cam stops working (probably a memory leak).
I don't know why, it depends on the yi programs.
https://github.com/roleoroleo/yi-hack-MStar/issues/149

Hi,
I was successful to block outgoing connections until the early days of using Yi-Hack Allwinner. Never had problems with the cam after that. There seems to be a hard-coded requirement by the cam I've discovered by trial and error: It demands access to Google DNS.
My cam works on the local network with these rules in the firewall:

Regards,
Catfriend1

Thanks @Catfriend1 , it seems a good solution. But my problem is, my router doesn't allow me to add an exception to the black list. If I use white list, I need to add rules for each device in this subnet. Any suggestions?

@cchenga  Hmm maybe lettint everything pass but block http/https traffic ports 443, 80 entirely? I don't remember if there was another port which the yi cloud api used. to be sure, run e.g. wireshark when booting the cam with full internet access.

I have the same problem. Finally my whole network works in local, except the cameras what is my biggest risk and concern lets say. It would be good to do that somehow if I block Internet access with one button it works properly after.
If someone has idea what to do just tell me , im using Xiaomi Ax3600 Router.
Thank you guys :)

Im having the same issue
I have logged my firewall and can see the camera trying to communicate DNS to <IP_ADDRESS> as well as <IP_ADDRESS>
Does anyone know what that second IP address is?

Can confirm allowing just 53 to <IP_ADDRESS> fixes the problem
On a side note which I dont see mentioned in this thread or the one linked before
when debugging my camera, i could see this error when I started a RTSP stream without allowing <IP_ADDRESS> though
ALSA lib pcm.c:8683:(pcm_write_snoop_fifo) Fifo full!

Update:
For me it wasnt a network issue, (that i can see)
I have blocked all network access again for the camera, and set the following config
Disabled Cloud ON
Record without cloud off
RTSP ON
RTSP Auidio OFF
ONVIF OFF
SSH ON (Defualt I believe)
HTTPD ON
Everything else off
I cant see any traffic on my firewall any more from the camera
and my RTSP seems stable

ALSA lib pcm.c:8683:(pcm_write_snoop_fifo) Fifo full!

This error depends on a patch I made to add audio to the stream.
Should not be a problem.

Good day, roleoreleo!
I asked Andy2301 to make such a simple but high-quality RTSP. There is rarely a suitable RTSP server for old and new Yi servers.... I've read about the unsolvable difficulties that arise with direct flow. You can ask him to make such an RTPS so that he closes questions about any camera.
https://github.com/andy2301/test1/issues/1#issuecomment-792282846

Hi.
I can fully reproduce the behaviour described in this issue.
As a further analysis, I've run wireshark and seen that DNS query to <IP_ADDRESS> comes from /etc/resolv.conf
root@yi1080:~# cat /etc/resolv.conf
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

It's querying for api.eu.xiaoyi.com. I have my own LAN DNS (<IP_ADDRESS>) and have set api.eu.xiaoyi.com to resolve to <IP_ADDRESS> and the RTSP server starts normally even with no internet access at all.
We can conclude that it's only needed to get an IP address for api.eu.xiaoyi.com (no matter what IP or DNS).
@roleoroleo : maybe an entry to /etc/hosts would work for everyone

@ivanfor
No, you can't. Request to api.eu.xiaoyi.com, as well as other Chinese addresses requests the "dispatch" module.

@roleoroleo : maybe an entry to /etc/hosts would work for everyone

Many people use cloud services.
I only need to add it when the cloud is disabled.

echo "<IP_ADDRESS> api.eu.xiaoyi.com" > "/home/yi-hack/etc/hosts"
mount --bind "/home/yi-hack/etc/hosts" "/etc/hosts"
# mount: mounting /home/yi-hack/etc/hosts on /etc/hosts failed: No such file or directory

/etc/hosts doesn't exist.
mount --bind doesn't work if the file doesn't exist.
Add this file means rewrite the whole partition.
It's not a good idea.

HOSTALIASES env var does not work, too :-/

Did you try to export it before running rmm? In system.sh

I tried to export it on she and then start udhcpd and then using wget to test. (did not work)
does rmm respect the var?

The only solution is to bind the whole folder.
mkdir /tmp/etc
cp -R /etc/* /tmp/etc
mount --bind /tmp/etc /etc
echo "<IP_ADDRESS>    api.eu.xiaoyi.com" > /etc/hosts

@roleoroleo Thought about this, too. Would you accept it when someone makes a PR like this? I fear in my stomach that could cause weird behaviour when mounting/unmounting or upgrading!?

The only solution is to bind the whole folder.
mkdir /tmp/etc
cp -R /etc/* /tmp/etc
mount --bind /tmp/etc /etc
echo "<IP_ADDRESS>    api.eu.xiaoyi.com" > /etc/hosts

	if [ -f "$sd/record/tmp.mp4.tmp" ]; then
		killall dispatch
	fi

I will test this solution.

	if [ -f "$sd/record/tmp.mp4.tmp" ]; then
		killall dispatch
	fi

@Arkady23
Why you need to kill dispatch?

DIspatch constantly sends your network information with passwords to China. I don't like it. The camera was created for espionage purposes. It would be great if you completely remove this software.

@Arkady23  Interesting. Do you have any proof like wireshark traces or so , just out of my interest? I'm also trying to live "privacy conscious".

@Catfriend1 Yes, I saw it in wireshark. The SSID and password were forwarded there. Why would they do that?!

If I remeber correctly, if dispatch is not running, rmm doesn't start.
So, we can't comment dispatch in the init script.
And kill it after some seconds, could be too late for our privacy.

The situation with "RTSP stopped working once I block internet access of the camera" reminds me how web.whatsapp.com stopped working once I block internet access of the smartphone. And this does not happen with telegram.


Break up into more modules

Separate internals from the public API and from each other.

Add pattern synonyms for understanding SeqT as its view.

This PR could really use a proof that toView . fromView = id and fromView . toView = id. I'll try to do that by tomorrow.

I have a proof that toView . fromView = id. Going the other way is a bit trickier, because we want to consider certain queues equivalent.

Oh geez. I just now saw this. For some reason github didn't show me there were others PRs. Sorry.

Um, well, the web editor let me merge it by just deleting my changes. I've used that feature of github before and I didn't really mean to commit it to the PR, but that's where we are now. I can add the INLINE's back no problem.

The proof of the other direction would be cool, but I want to get this merged so I don't clobber you again :) So if you work on out, please send it.

All right! Thanks!
On Thu, Jul 22, 2021, 1:08 AM Jason Dagit @.***> wrote:

The proof of the other direction would be cool, but I want to get this
merged so I don't clobber you again :) So if you work on out, please send
it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dagit/logict-sequence/pull/9#issuecomment-884658852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOOF7OXXBTDJMXZQJTDOK3TY6RUPANCNFSM5AZF7I2A
.


add nodouble option for all cwise ops

this is the following patch of ac98d1184008e4 to support nodouble
option for all cwise ops. The macros REGISTER* defined within
ANDROID_TYPES_SLIM should be changed to empty, and it impacts
all the cwise ops, so, all the changes for the cwise ops have to be
in a single patch.
there will be more patches for other ops to support nodouble option.

Can one of the admins verify this patch?

thanks @vrv pointing my mistake, i'll rewrite the code to add new macros such as REGISTER_SYCL, and REGISTER6_SYCL. In the new code, the change could be separated to be one patch for one op, it could make each patch simple and easy to be reviewed.  So, my plan is to close this PR, and send out new PRs one by one (send out the second patch only after the first one is accepted).

I'd be fine with all the changes in the same PR actually, since they are logically all the same, and can be tested all at once (less load on our test infrastructure). They are mostly mechanical changes so it's easier to review in a single batch :)

got it, i'll continue this PR with new patches.

@vrv Could you take another look, please?

I think @benoitsteiner probably wants to look at this since it's SYCL related.

@tensorflow-jenkins test this please

hello, i checked the failure log but do not understand how it relative to my change, could anyone help? thanks.
the last few lines of the log:
PASS: //tensorflow/python:session_benchmark
PASS: //tensorflow/python:matmul_benchmark_test
Build was aborted
Aborted by unknown
[Set GitHub commit status (universal)] PENDING on repos [] (sha:ef4e31e) with context:tensorflow-pull-requests-gpu
Unable to get pull request builder trigger!!
Setting status of 12276a750d6240f93878f84fa125f6be48566e7d to FAILURE with url https://ci.tensorflow.org/job/tensorflow-pull-requests-gpu/6269/ and message: 'FAILURE
'
Using context: Linux GPU
Finished: ABORTED

@guoyejun The failure was unrelated to your change.

@tensorflow-jenkins test this please

@benoitsteiner Can you take a look at the replies?

@benoitsteiner what do you think?

@benoitsteiner ping?

@benoitsteiner any luck with this?

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @benoitsteiner: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @benoitsteiner: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

just close it since no feedback for a long time, and code base change results into conflicts


set permission command, fallback to true

Hi,
it would be great if the command to set a permission would automatically set it to true if the value is not defined. The need to set a permission to false is extremely low compared to true and most users probably never use it at all.

Thank you :)


Support for different icon by item type

For example, if the item type is loot, look for unidentified-loot.* image in /icons folder if none exists go back to the default one.

Thought about it :) consider it planned


Custom scroll bars

This isn't high priority right now, but eventually we will need custom scroll bars.

The default ones are very distracting

Fixed in working branch


Error in predict_risk(test_data)

After following the notebook:
model.train(train_data, n_epochs=n_epochs, logger=logger, update_fn=update_fn)
i use
model.get_concordance_index(**test_data)
and i get a ci.
Howver:
predictions =model.predict_risk(test_data)
prodcues an error of excetpion

When you call model.predict_risk you should only pass the x matrix. I think you should be able to fix your problem by calling instead:
predictions = model.predict_risk(test_data["x"])


added a point about SQS per-message confirmation semantics

Hi Bill, I added a point to Tim's SQS comparison section... Please take a look at it, if you agree and if this information is helpful in terms of the comparison...

@codekultur lgtm, :shipit:


YAML loader

As I can see there are some new loaders, but YAML seems to be missing. I would be happy to contribute (using symfony/yaml as a suggested dependency) if you accept a PR for that.

@vlucas ping

I don't like the idea of adding another dependency to this project for an optional file type. Suggested dependencies always felt weird to me.

I am closing this, since there is no need for this.


Some enhancements

This PR includes:

Different Spark initialisation. The proposed method to set up Spark based on the machine's resources (via os.sysconf) is not supported on macOS. I have changed it to the local setup we use for the evidence parsers.
The change in the metrics filenames was not effective in the UI, as this is picked up from the runId column. I've updated all data files to the newer nomenclature.
I've solved the bug where we had duplicated columns on the customised pivot table. These are still created, but I drop them by dropping columns with NaNs, which we originally do not have.
I've removed the capability of consulting the AUC and OR metrics in the UI, as I don't think they bring any value and make the -already extensive table- more confusive.

(4) makes me sad

@d0choa You name it, you got it. 💅


Pagination doesn't work

Hi @dim0627, really nice theme! Just tried it. I think there's something wrong with pagination on the main page because I see all my latest posts (which actually all of it) when I view a post. Thanks!

OMG X(
Thanks for information.
I fixed latest commit.Please try after pull :)

Cool thanks!


Please add a config

According to your testing, does the issue occur with ONLY Portal Gun mod and Immersive Portals mod and Farbic API?
Yes
Describe the issue
This is not an issue - but you don't have a discord so I guess I'll post it here.
Please add a config for settings such as a list of blocks that portals cannot be placed on.
I am trying to recreate some portal features and I have to make non-portalable panels out of leaves right now.
Additionally, a command to spawn portals would be very convenient. If this is not doable due to it being impossible to code, that would be very sad.
Another option that would be nice is one to change how flings work. I don't like how you can fall from 5 blocks and get 75% of the velocity you'd get from 75 blocks. An options such as fling_scaling in the config that would make you fling further would be very helpful.
Thank you.
Post the log here
Dunno what to put here...
Please make a discord

I saw this from the discord : https://discord.gg/BZxgURK

The discord is the same as Immersive Portals: https://discord.gg/BZxgURK
I am going to make it controlled by the data in portal gun item, so that each portal gun can work on different blocks.
About commands: ImmPtl have a lot of command https://qouteall.fun/immptl/wiki/Commands-Reference.html but the commands cannot create portal gun's unique type of portal. I am considering adding it.
About velocity: you can increase motionAffinity by /portal nbt {motionAffinity:2.0} and it will accelerate the player when touching. However it will be reset if the portal gets recreated.

Got it. Thanks!


🦺[Tech Debt] Remove stale api server code and add switch for dev mode

Goal
Describe the work to be done

There are some references to servers that are retired.  We also want to be able to test a backup server
Definition of Done

[x] Refactor stale references (main: api-prod.lite-wallet.org, fallback: api-dev.lite-wallet.org)
[ ] Add dev server mode ( add section in Settings  > Advanced Settings > Dev Mode Switch with a code to enter)

Mockups
Proposed UI

Fixed first task in https://github.com/litecoin-foundation/litewallet-android/pull/100
cc: @vsima


Fix/14149 app crash scanning redeemed code

Description
Fixing the crash when scanning a redeemed code, we shouldn't save the expired tests on the app even temporarily this causes a confusion in the number of rows, because there should be one cell for the risk state "in case of the redeemed test" but the app thinks there should be 2 "risk cell and test result cell", the introduced solution will prevent the app from adding this extra cell to the view model and hence prevent the crash
Link to Jira
https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-14149

Not an appropriate solution


[e2e]: nodejs workflow_dispatch main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7028810828
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Wed Nov 29 06:24:22 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7042814547
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Nov 30 06:26:50 UTC 2023
Tests are passing now. Closing this issue.


feat: add theme variants for everforest

Describe the problem
buffers.background.colorCode does not support everforest
Describe the solution
support color codes for https://github.com/sainnhe/everforest

also add https://github.com/projekt0n/github-nvim-theme


Release Kalix JavaScript SDK

Prepare

[x] Make sure all important PRs have been merged
[x] Check that the latest build successfully finished
[x] Make sure a version of the proxy that supports the protocol version the SDK expects has been deployed to production

You can see the proxy version on prod on grafana or using various other methods.
Cutting the release

[x] Edit the draft release notes and create the appropriate tag

CircleCI will automatically publish the @kalix-io/kalix-javascript-sdk package to the npm registry based on the tag
CI will update the docs/current branch

Check availability

[x] Check that docs/kalix-current has been updated
[x] Check the release in the npm registry

Fix and publish docs

[ ] Update the supported version in the main docs if relevant (affects Supported Versions)
[ ] Add an item to the Release Notes in the documentation
[ ] Release the Kalix documentation to get the SDK docs updates published

Update to the latest version

[x] Run samples/bin/update.sh to update the samples to the latest released versions.

Check docs update

[ ] After quite a while TechHub shows updated docs (see the timestamp on the bottom of the page)

Announcements

[ ] Announce in the forum

tag with Kalix, releases and announcement

[ ] Inform Lightbend marketing and engineering if it's a noteworthy release
[ ] Close this issue

I think this is sufficient for a milestone release


Added support for video sitemaps

Video tags are according to Google's specifications: https://developers.google.com/webmasters/videosearch/sitemaps

Great patch! Thanks!


Fix Broken Link at Documentation

Fixed broken link of secure_channels.md file at transports.md file.

I have approved the CLA and this can be merged.
Welcome to the community!!

Thanks.

rebased and merged https://github.com/ockam-network/ockam/commit/1d5d9aef7476430a96146684715e248b19896850


mdbook: upgrade cargo fetcher and cargoSha256

Infra upgrade as part of #79975; ran nixpkgs-review wip successfully.

@GrahamcOfBorg build mdbook

@worldofpeace I actually did have this script posting that comment automatically in the previous iteration, but per comment from @grahamc himself it's not necessary!
I think posting it kicks the builder to start building instantly, while otherwise it should eventually come through and do it on its own.  Let's wait and see on https://github.com/NixOS/nixpkgs/pull/80399, which has currently been open for 5 minutes with no OfBorg signs of life . . .

ofborg's builds aren't poll-based, the builds are triggered once the evaluations complete.

Side note: it used to be required to trigger the builds for any PR where the person opening the PR wasn't pre-approved. ofborg now automatically builds all PRs, no matter who opens them.

Right, but the "Some checks haven't completed yet" (or any status/signs of life at all) didn't pop up for ~25 minutes.  It'd be nice if ofborg immediately set the status as pending on PR opens, so those impatient humans don't try to poke it unnecessarily!
(If you post the comment, it instantly sets the status to pending, at which point you know to just sit tight.)


The Vec3/Vec3A byte size conundrum

So, we currently have the Vec3 and Vec3A types from glam available.
Vec3 is simply three scalar float32 values, and Vec3A is a SIMD type where an actual vector with three floats can fit.
On CPU, this results in:

Vec3 is (f32, f32, f32), 12 bytes
Vec3A is NEON or SIMD register, 16 bytes

On GPU/SPIR-V, we have:  (EDITED)

Vec3/Vec3A are both a SPIR-V vec3 value (TypeVector x(float) 3). 12 bytes (but with special alignment requirements depending on buffer type/layout mode).

Having this type (and not just scalar) is required as an argument for some texture sampling functions, etc

The biggest issue I have with this is of course that on CPU a Vec3A occupies 16 bytes while on GPU it may occupy 12 or 16 bytes depending on surrounding declaration and buffer layout mode.
This all feels quite unsatisfactory, but I am not sure what the best course of action to clean this up would be.

As of https://github.com/bitshifter/glam-rs/pull/106 (early december), Vec3 and Vec3A are identical on the GPU, both are TypeVector.

As of https://github.com/bitshifter/glam-rs/pull/106 (early december), Vec3 and Vec3A are identical on the GPU, both are TypeVector.

The Vulkan spec requires Vec3 to be align_of<Vec4>() but the spare 4 bytes are usable, expressed like so in CPU code:
#[repr(align(16))]
#[repr(C)]
struct Foo {
  v: Vec3, // align_of<Vec3>() == 4 on the CPU, 16 on GPU with VK, 4 on GPU with VK_EXT_scalar_layout
  f: f32,
}

But the spirv from that is:
OpMemberDecorate %Foo 0 Offset 0
OpMemberDecorate %Foo 1 Offset 16    // This Offset could be 12, and size_of::<Foo>() could be 16 instead of 32
%float = OpTypeFloat 32
%v3float = OpTypeVecctor %float 3
%Foo = OpTypeStruct %v3float %float

because Vec3 needs to be #[repr(simd)] so it's represented as an OpTypeVector, which makes it align(16), size is an integer multiple of alignment, and offset is the sum of the sizes of the previous members.
SPIR-V itself does not define a struct representation, punting it to the application API, so there are other potential layouts to further complicate things.  Vulkan has a couple extensions (eg. VK_EXT_scalar_layout) that change the layout rules, openGL has std150 and std430, openCL does it's own thing.
Ideally, the type definitions for CPU and GPU can be the same code, without needing to fiddle with #[cfg_attr(target_arch= ..., repr(...)] everywhere.  For that to work, the layout needs to be the same across different compilation units using different codegen backends, like #[repr(C)] but with the layout guarantees set by some crate level flag (maybe hijack one of the unused target-triple flags?).  This #[repr(spirv)] would need to be aware of OpTypeVector members to handle them properly, which may require changing how OpTypeVector is produced (iirc eddyb and khyperia were discussion LLVM being able to have size 12 align 16 vector types, so hopefully not).
I mentioned this on Discord the other day, but it was very early so I didn't really explain it.

The Vulkan spec requires Vec3 to be align_of<Vec4>() but the spare 4 bytes are usable, expressed like so in CPU code:
#[repr(align(16))]
#[repr(C)]
struct Foo {
  v: Vec3, // align_of<Vec3>() == 4 on the CPU, 16 on GPU with VK, 4 on GPU with VK_EXT_scalar_layout
  f: f32,
}

But the spirv from that is:
OpMemberDecorate %Foo 0 Offset 0
OpMemberDecorate %Foo 1 Offset 16    // This Offset could be 12, and size_of::<Foo>() could be 16 instead of 32
%float = OpTypeFloat 32
%v3float = OpTypeVecctor %float 3
%Foo = OpTypeStruct %v3float %float

because Vec3 needs to be #[repr(simd)] so it's represented as an OpTypeVector, which makes it align(16), size is an integer multiple of alignment, and offset is the sum of the sizes of the previous members.
SPIR-V itself does not define a struct representation, punting it to the application API, so there are other potential layouts to further complicate things.  Vulkan has a couple extensions (eg. VK_EXT_scalar_layout) that change the layout rules, openGL has std150 and std430, openCL does it's own thing.
Ideally, the type definitions for CPU and GPU can be the same code, without needing to fiddle with #[cfg_attr(target_arch= ..., repr(...)] everywhere.  For that to work, the layout needs to be the same across different compilation units using different codegen backends, like #[repr(C)] but with the layout guarantees set by some crate level flag (maybe hijack one of the unused target-triple flags?).  This #[repr(spirv)] would need to be aware of OpTypeVector members to handle them properly, which may require changing how OpTypeVector is produced (iirc eddyb and khyperia were discussion LLVM being able to have size 12 align 16 vector types, so hopefully not).
I mentioned this on Discord the other day, but it was very early so I didn't really explain it.

The Vulkan spec requires Vec3 to be align_of<Vec4>() but the spare 4 bytes are usable, expressed like so in CPU code:
#[repr(align(16))]
#[repr(C)]
struct Foo {
  v: Vec3, // align_of<Vec3>() == 4 on the CPU, 16 on GPU with VK, 4 on GPU with VK_EXT_scalar_layout
  f: f32,
}

This is only true for Vec3s within descriptors (uniform buffers etc). For Vec3s from a vertex buffer, it needs an align(12) 3 component vector type

The Vulkan spec requires Vec3 to be align_of<Vec4>() but the spare 4 bytes are usable, expressed like so in CPU code:
#[repr(align(16))]
#[repr(C)]
struct Foo {
  v: Vec3, // align_of<Vec3>() == 4 on the CPU, 16 on GPU with VK, 4 on GPU with VK_EXT_scalar_layout
  f: f32,
}

This is only true for Vec3s within descriptors (uniform buffers etc). For Vec3s from a vertex buffer, it needs an align(12) 3 component vector type

I have been trying and failing to do this for a little while now: I want a type that on the CPU is represented as
#[repr(align(16))]
#[repr(C)]
struct Vec3 {
    x: f32,
    y: f32,
    z: f32
}

and that maintains that layout on the GPU, so that I can use the same type on both ends of a storage/uniform buffer. To my understanding, none of the glam types have this representation on the CPU and writing this directly fails in spirv as #[repr(simd)] is necessary for copying to work. I could try something like
#[cfg_attr(not(target_arch = "spirv"), repr(align(16)), repr(C))]
#[cfg_attr(target_arch = "spirv", repr(simd))]
struct Vec3 {
    x: f32,
    y: f32,
    z: f32
}

but I think that bumps the size up to 16 bytes in spirv, preventing use of the spare bytes and leaving me at square one.
This is clearly possible somehow, as this align=16, size=12 is how a vec3 behaves in GLSL. Is what I am trying to do possible in rust-gpu and if not, what is blocking it?

This is clearly possible somehow, as this align=16, size=12 is how a vec3 behaves in GLSL. Is what I am trying to do possible in rust-gpu and if not, what is blocking it?

The thing blocking it is that rustc (and tbh, a huge chunk of CPU-side compiler toolchains in general) does not support the concept of align=16 and size=12 - a assumption baked into a lot of code is that "size is always a multiple of alignment". We would need to make rust (and rustc) support that style of layout before we're able to implement it in rust-gpu.

Thinking about this further, the best path forward, for now, is probably a validation pass in rust-gpu that looks at all the interface parameters and the like, computes std140/std430 layout, and gives a warning or error if there's a mismatch, so the user can known to use Vec4 instead of Vec3 or whatever. However, more investigation is needed because rust-gpu should be emitting Offset decorations to every struct it emits, with rules of align=16 size=16 for Vec3, and the wacky size=12 rule shouldn't be coming into play anywhere, but it clearly is somehow because people are hitting bugs when they use Vec3. So, maybe a validation pass isn't the right way to go, or maybe it is, more investigation is needed on what exactly is causing issues when using Vec3. (Maybe the CPU side is assuming size=12 and mangling structs to fit that, even though the original data is size=16 and the GPU side is also size=16?)

ah, https://github.com/EmbarkStudios/rust-gpu/issues/575 is probably a better, more thought-out way of doing this - so linking these issues together

Closing this in favor of #575


Add tool vscode-inline-fold

Name
Link

Inline Fold - VSCode Extension
https://github.com/moalamri/vscode-inline-fold

I don't know what

NOTICE: this extension is still under active development!

means in detail, so I don't know if @moalamri would call this extension 'awesome' at this stage. Therefore, this is just a draft PR for now. If anyone thinks it should be in the list today, please weight in.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[ ] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

That extension looks very useful for VSC + Tailwind CSS users, but it no longer seems to be in "active" development. Let's wait a few days and see.

Hey guys,
Thanks for featuring this. It is still under active development, not so active tho, I barley find time with some work-related tight deadlines :D.
I agree with you not to 'awesome' it now as it still lack the support for most of template literal use-cases.
I hope with the release of v0.2.0 it then could be "out of development".

Moreso is this even something related to Tailwind CSS and not just something that helps working with Tailwind CSS?
If we add this, does that mean we allow other semi-related things?

@joshmanders very valid concerns, but I think the extension could be particularly useful for working with Tailwind CSS, and I wouldn't be surprised if it was developed with that in mind but made less specific because it could be useful for other things too.
In my opinion it's fine to let it be in "IDE extensions" once it's finished, but it's up to you 👍

@joshmanders It is the main use case, as it was the reason I developed it, but since it could be useful in other use cases I didn't limit it, and I gave users the options to tweak settings and gave it a generic name.
So, I agree with both of you about this concern, and I wouldn't add it to be directly related to Tailwincss it self, but more of "a tool that could be helpful" when working with Tailwindcss.

Well if it was developed with Tailwind in mind, then I say go for it if you think it's acceptable, @innocenzi!

This has evolved to barely even be noticeable to have anything to do with Tailwind so I'm going to opt out of including it. We don't want to set a precedence for "You can use this for tailwind even though it's not a tailwind thing" list of stuff, otherwise we'd have to include ridiculous stuff.


Add a NoRequest type

A common use-case of NATS is having a subject on which in information stream is published, and clients interested in it just have to subscribe to the subject to get them.
With NRPC as it is today, the way to formalize such a service is somehow awkward because the "client" side has to implement a "Server" interface, maybe with extra methods it is not interested in. And the "server" side uses a "Client" structure to publish the messages.
I propose we add a "NoRequest" message type that creates output-only methods, ie some methods a client can subscribe to, with a client-friendly api.
For example, given the following .proto:
service Broadcast {
   rpc InfoStream(nrpc.NoRequest) returns (Info) {}
}

The client type would a provide a convenient API to subscribe to it:
b := NewBroadcastClient(conn)
sub, err := b.InfoStreamSubscribe(func (Info) {})

We could also generate a chan-based subscription:
sub, c, err := b.InfoStreamChanSubscribe()

Or a sync subscription:
sub, err := b.InfoStreamSyncSubscribe()
info := sub.Next() // returns a decoded Info directly

I implemented what I had in mind in a 'norequest' branch in the orus-io fork.
It depends on the PR #29, so I'll wait for it to be merged before creating a new PR.


Ban animated gifs

Need to detect if a gif is in a message and either delete the message or if possible remove the gif.
Can't just remove the embed or attach files permission cuz that breaks other stuff.

This should actually just be a more powerful filter system.


legend_toggle doesn't deselect all lines

Hello, I have this component:
function Hello() {

    return (<Chart
          width={"100%"}
          height={"1000px"}
          chartType="LineChart"
          data={[["Id", "Data1", "Data2"],
          [0, 14315.07, 14468],
          [1, 13706.6, 13879],
          [2, 13329.94, 13514],
          [3, 13326.58, 13425],
          [4, 14123.31, 14258],
          [5, 15518.38, 15679],
          [6, 16868.09, 17153],
          [7, 18021.08, 18316],
          [8, 18905.94, 19244]]}
          legend_toggle={true}
          />);
  }
}

My problem is that when I deselect lines, some of them remain visible (albeit with gray color) on the graph, here I attach 2 images, one with both legend items enabled and another with both legend items disabled.
https://prnt.sc/ofyfcy
https://prnt.sc/ofyfk6
What I'm doing wrong here?
Thanks.

This is fixed in latest thanks to @davewelsh's PR referenced above.


Second [[Comment]] tag fails to parse when using two [[Comment]][[/Comment]] tags at the same content level

When previewing the changes to an article, if there are two [[Comment]][[/Comment]] tags at the same content level (as in, at the top level, or in the same element of a list or table), then the the following error is returned :

Found mismatched end tag /Comment with expected tag undefined: section starting with "[[/Comment]]"

The following two cases will cause the error :

[[Comment]][[/Comment]][[Comment]][[/Comment]]

[[Comment]]First[[/Comment]]
[[Heading]]doesn't prevent the bug[[/Heading]]
[[Comment]]Second[[/Comment]]

But this won't cause the error :

[[Comment]]This is fine.[[/Comment]]
[[List]]
[[Comment]]This isn't at the same content level.[[/Comment]]
|
[[Comment]]This is in a different element of the list, so this is still fine![[/Comment]]
[[/List]]

Whoops, fixed this silly mistake. Thanks for the report.


fix add to playlist submenu input field padding

before:

after:

these improvements look stunning.
good job.
thanks


5/16 Publishing

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

2017-03-09-profile/docs-ref-autogen/batchai/cluster.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Documentation and accelerator out of sync

In the Act on your device section #3, the accelerator shows 'Tags, Methods, and Properties' while the screenshot on this example shows 'Tags, Run Method, and Reconfigure'.  And when you select Method in the accelerator, there is no 'FirmwareUpdate' method.

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

ID: 552fcbfd-a025-6a6d-74a3-470f606ee4ad
Version Independent ID: fac901c8-abcf-7a05-629f-0c4e1cfad979
Content: Provision Raspberry Pi to Remote Monitoring using C - Azure
Content Source: articles/iot-accelerators/iot-accelerators-connecting-pi-c.md
Service: iot-accelerators
GitHub Login: @dominicbetts
Microsoft Alias: dobett

@ericloeliger Thanks for the feedback! We are currently investigating and will update you shortly.

@dominicbetts Looks like portal UI has been updated. Please check and update the document as appropriate. Also, check on the "Device Explorer" is now "Devices".

Hi @ericloeliger - thanks for getting in touch. If you deploy the latest version of the Remote Monitoring solution accelerator (version 2.2.0 - click the Settings icon top right to view the version number) you should find that the solution accelerator and docs are back in sync.

Hi @ericloeliger - I'm going to request that this issue is closed. Please feel free to reopen it if you encounter any further mismatches. Thanks for taking the time to report the original issue.
#please-close


python310Packages.nestedtext: 1.2 -> 3.5

Changelog: https://github.com/KenKundert/nestedtext/blob/v3.5/doc/releases.rst
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 218297 run on x86_64-linux 1

8 packages built:

emborg (python310Packages.emborg)
python310Packages.nestedtext
python310Packages.parametrize-from-file
python310Packages.quantiphy
python311Packages.emborg
python311Packages.nestedtext
python311Packages.parametrize-from-file
python311Packages.quantiphy


JSON Schema 2019-09 and JTD (v8)

Problem
2019-09 introduced two extensions to draft-07 validation process, that are very difficult / impossible to implement in the current Ajv design, specifically:

[x] unevaluatedKeyword that depends on annotation collection (specifically, collection of "evaluated" properties in visited and successfully validated branches), and requires validation of all dependent branches without short-circuiting.
[x] recursiveRef that depends on dynamic ref scoping

In addition to that, it would help rethinking the definition of "keyword" in Ajv and eliminating the difference between "standard" and "custom" keyword (Ajv taxonomy) and replacing it with "applicators" and "vocabularies" of "assertions" and "annotations" (JSON Schema taxonomy).
Some other challenges that can be addressed:

[x] simplify implementing custom applicator keywords
[x] make validation functions serialisable more consistently than the current ajv-pack approach (PR #1332)
[ ] consider allowing schema parametrisation (#398)
[ ] reduce size of the validation function by refactoring error generation the solution is to use the option messages: false together with ajv-i18n.
[x] generate custom ajv bundles including only needed vocabularies or their subsets (#460)
[x] JTD support can be implemented as a custom vocabulary with some extra options (#1161)

TODO

[x] types to support new taxonomy of keywords
[x] formalise reference resolution algorithm simplify reference resolution implementation
[x] formalise annotation collection algorithm only implemented to support unevaluatedProperties/Items
[x] formalise code generation algorithm
[x] split formats to a separate package
[x] implement in typescript
[x] drop draft4 support
[x] restructure docs

Please comment on the questions here: https://github.com/ajv-validator/ajv/issues/1247#issuecomment-660940093
#1247 is the scope for the first release of v7-alpha.

v7.0.0-beta.0 release notes

v8 now released too, with JSON Schema 2020-12 and JSON Type Definition support: https://ajv.js.org/v6-to-v8-migration.html


Update to camelCase from Snake_Case

Updating everything to camelCase

Updated Branch Protection to allow for merging my own PRs


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/60559

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/60840


Expose the generic-lens package to codeworld Haskell projects

First of all, thank you very much for code.world!
I've noticed that in codeworld Haskell, LANGUAGE TemplateHaskell is, understandably, not allowed since that would help malicious users do nasty stuff. However, as noted in #69, one very important use of TemplateHaskell is deriving lenses for records. And that's especially true for codeworld, given how important pure state transformations are in codeworld's model and how well lens plays with MonadState.
So, I'd like to suggest exposing the generic-lens package as an alternative means to scratch the same itch without requiring  TemplateHaskell. (In fact, that's the way I prefer even when TemplateHaskell is available). So the users can resort to:
{-# LANGUAGE DeriveGeneric, OverloadedLabels #-}

import Control.Lens
import Data.Generics.Labels
import GHC.Generics

data MyRecord = MR { myField :: Int } deriving Generic

main = print $ MR 42 ^. #myField

Sounds like a great idea.  I can definitely do this.

https://code.world/haskell#P653zkG8w1eybgAG_tGomfw

Awesome, thanks a lot!


[FEATURE REQUEST] Ability to force text, rainbow_text screens

Adding the capability to enforce not just icon screens would be highly appreciated.

I don't fully understand what this feature request is about. Can you please explain in greater detail?

These two screens are not what you are referring to?

When using the Ulanzi_force_screen service to immediately display on the LED matrix, i need to include "icon_name," which is not available on the full-text screen.

which is not available on the text_screen & rainbow_text_screen

In 2023.9.1 - Just specify any one. Like: rainbow :)

Where I need to specify the name?
I use the latest firmware. When I try to add a name to the screen I get Error running action: extra keys not allowed @ data['icon_name']. Got None.
service: esphome.ulanzi_rainbow_text_screen
enabled: true
data:
  default_font: true
  text: >-
    {{ state_attr('sensor.bidi', 'media_artist_bidi') }} - {{
    state_attr('sensor.bidi', 'media_title_bidi') }}
  lifetime: >-
    {{ (state_attr('media_player.era300', 'media_duration') | float(default=0) /
    1) | int(default=1) if state_attr('media_player.era300', 'media_duration')
    is not none else 4 }}
  screen_time: 40
  icon_name: rainbow

I also tried this method without luck. Sometimes, I have more than one screen in the loop.
service: esphome.ulanzi_force_screen
data:
  icon_name: rainbow
  mode: 8

Hi, I never used it but a * for icon_name should work

Where I need to specify the name?

Only in force like
service: esphome.ulanzi_force_screen
data:
  icon_name: rainbow
  mode: 8

I tried, but the screen appears a few seconds after I send the force screen command. The clock screen appears, not the text rainbow screen, which shows up after a few seconds.
This is a snip from my automation:
      - conditions:
          - condition: trigger
            id:
              - title
              - music
          - condition: state
            entity_id: media_player.era300
            state: playing
        sequence:
          - service: esphome.ulanzi_del_screen
            data:
              icon_name: "*"
              mode: 8
            enabled: true
          - service: esphome.ulanzi_del_screen
            data:
              icon_name: "*"
              mode: 5
          - service: esphome.ulanzi_rainbow_text_screen
            enabled: true
            data:
              default_font: true
              text: >-
                {{ state_attr('sensor.bidi', 'media_artist_bidi') }} - {{
                state_attr('sensor.bidi', 'media_title_bidi') }}
              lifetime: >-
                {{ (state_attr('media_player.era300', 'media_duration') |
                float(default=0) / 1) | int(default=1) if
                state_attr('media_player.era300', 'media_duration') is not none
                else 4 }}
              screen_time: 40
          - service: esphome.ulanzi_force_screen
            data:
              mode: 8
              icon_name: rainbow

2023.9.1?

This is the log. Version is above 2023.9.1
Logs pixel.yaml
INFO ESPHome 2023.11.6
INFO Reading configuration /config/esphome/pixel.yaml...
INFO Updating https://github.com/lubeda/EspHoMaTriXv2@main
WARNING
WARNING This will only work with esphome >= 2023.7.0
WARNING Please check the documentation and wiki https://github.com/lubeda/EspHoMaTriXv2
WARNING
WARNING GPIO15 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Detected timezone 'Asia/Jerusalem'
INFO Detected timezone 'Asia/Jerusalem'
INFO Starting log output from ulanzi.local using esphome API
INFO Successfully connected to ulanzi in 0.529s
INFO Successful handshake with ulanzi in 0.096s```

I use the main firmware from your git


Tau Server Slow, Bad Frames

This issue refers to this conversation
https://community.onion.io/topic/4509/tau-usb-cable-suggestions
Python Library versions
Python 3.9.5
pip 21.1.1
Camera Info
ToF Camera opened successfully
model: 4.0
firmware: 3.3
uid: 9500c6
resolution: 160x60
port: COM8
Describe the bug
TauLidarServer.py runs slow.
Lots of bad frames, new frame every 5 - 60+ seconds.  Sporadic.
Steps to Reproduce
Plug USB A to USB C cable into Tau Camera
in CMD type 'python -m TauLidarServer'
What is expected?
Camera should take new frames at regular intervals
should not take more than a minute to get a frame.  I have seen some faster movement from the Hackaday article.
Current speed would not be reliable to use in the field.
What is actually happening?
https://drive.google.com/file/d/1N6E0iDCx881zLVFrJZcKs9NFQYx86uRG/view?usp=sharing
Lots of bad Frames, Lots of time between frames.   In the video I have attached in a Google Drive link you will see the frames take a long time to update.   Every time the frames update I immediately change the cameras angle but it takes a long time for the camera to get a decent frame.
Here is the CMD code from this video
`C:\Users\Kevin>python -m TauLidarServer
Looking for connected Tau LiDAR Camera hardware ...
ToF camera opened successfully:
model:      4.0
firmware:   3.3
uid:        9500C6
resolution: 160x60
port:       COM8
IP address: <IP_ADDRESS>
URL:  http://<IP_ADDRESS>:8080
Press Ctrl + C keys to shutdown ...
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET / HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET /css/spectre.min.css HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET /css/spectre-exp.min.css HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET /css/spectre-icons.min.css HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET /css/loading.css HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET /js/app.js HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET /img/tau-logo.svg HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET /js/vue.esm-browser.js HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:57] "GET /js/pointsView.js HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:58] "GET /js/three.module.js HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:58] "GET /js/OrbitControls.js HTTP/1.1" 200 -
<IP_ADDRESS> - - [02/Jul/2021 23:12:58] code 404, message File not found
<IP_ADDRESS> - - [02/Jul/2021 23:12:58] "GET /favicon.ico HTTP/1.1" 404 -
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38420, expected size: 38480
Bad frame ignored, bytes length: 38340
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38420, expected size: 38480
Bad frame ignored, bytes length: 38340
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38164, expected size: 38480
Bad frame ignored, bytes length: 38084
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
Data error, actual size: 38228, expected size: 38480
Bad frame ignored, bytes length: 38148
skip frame
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
code = 1006 (connection closed abnormally [internal]), no reason
code = 1006 (connection closed abnormally [internal]), no reason
Data error, actual size: 38356, expected size: 38480
Bad frame ignored, bytes length: 38276
skip frame
code = 1006 (connection closed abnormally [internal]), no reason
code = 1006 (connection closed abnormally [internal]), no reason
code = 1006 (connection closed abnormally [internal]), no reason
Shutting down ...`
Any additional comments?

@kevinboards thanks for posting an issue, we'll do our best to sort this out.
A few questions from our end:

Does this happen every time you try to run TauLidarServer?
Has it worked as expected before? If so, did it consistently work as expected or only from time to time?
Do you have multiple Tau Cameras, and if so, does this happen with all of them?

@kevinboards thanks for posting an issue, we'll do our best to sort this out.

Does this happen every time you try to run TauLidarServer?
Yes
Has it worked as expected before? If so, did it consistently work as expected or only from time to time?
No, it has never worked as expected.
Do you have multiple Tau Cameras, and if so, does this happen with all of them?
I only have 1 camera

UPDATE: Today I was able to get my hands on an old windows 7 machine.   I downloaded Python 3.7, setup everything for the TauLidarServer and it ran  really well!  No problems.
I then downloaded the examples, the recording of frames was incredibly fast and all of my frames were good frames.
The Tau Camera is obviously fine.  There is something going on with my lenovo laptop with python 3.9 that I will need to get to the bottom of.

Closing this issue, resolved with fix from #14 (released in TauLidarCamera v0.0.4)


Add Composite and Composition for Kafka

Checklist

[x] PR contains a single logical change (to build a better changelog).
[x] Update the documentation.
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.

I now added the version to the composite and forwarded the observed version to the status.


Updated django.po for sk locale

Fixed plural forms for time units
Branch description
Fixes incorrect plural translations of time units in Slovak language.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[x] I have added or updated relevant docs, including release notes if applicable.
[x] I have attached screenshots in both light and dark modes for any UI changes.

Thanks for the patch, however translations are manager through Transifex (https://docs.djangoproject.com/en/5.1/internals/contributing/localizing/).
So please fix those strings there. We generally fetch translations for the .2 or .3 point release of Django.


clean output

for npy, remove anything that is not attainable
for h5, also repack
option with mask


trailing-commas transform moves trailing comments

Given code like
const foo = {
  bar: true // comment
};

the trailing-commas transform moves the comment up:
const foo = {
  // comment
  bar: true,
};

It would be nicer if the comment placement was preserved:
const foo = {
  bar: true, // comment
};

cc @janicduplessis

We'll definitely have to hack on recast to fix this :)

Is there anyone who is willing to take a look at this?

Closing given inactivity. Feel free to send a PR anytime.


String interpolation fails on object that is not String and toString() returns null

Title explains issue. Minimal reproduce:
class Text {
  @override
  String toString() => null;
}

void main() {
  Text text = new Text();
  String string = '${text}';
}

https://dartpad.dartlang.org/bf550031d53b43c11c2355032f1d2003

It does what the spec says it should:

An interpolated string ‘s1${e}s2’ is equivalent to the concatenation of the strings ‘s1’, e.toString()
and ‘s2’.

In this case, s1 and s2 are empty strings and the expression should be the same as '' + text.toString() + '' which throws.  (You might argue that it isn't equivalent because it doesn't throw the same thing.)
The spec does say that e.toString() is a string, but I think that's a spec bug (issue #25853).

Kevin is correct. The spec has been made more explicit about the interpolation, but the conclusion is still the same - if the call to toString doesn't return a string, the interpolation expression throws.
You could call toString again on the returned object, but when do you stop?
class FooledYou {
  dynamic toString() => this;
}
main() {
  var f = new FooledYou();
  var y = "<$f>";  // infinite recursion - or just throw immediately?
}

We opted for throwing immediately. If your toString returns a non-string, something is wrong. Trying to "fix" that in any way is likely to just hide the wrongness, not expose it, so this is failing early.
(If we get non-nullable types, expect toString to have a non-nullable return type!)

You can change Text.toString to return null.toString() (if that was your intent).


Fails to work on XP x64 SP2 (NT 5.2)

What steps will reproduce the problem?

Install
Open Grabber.exe with HEX editor and patch 0x06 byte to 0x04 at offsets 0x0158 and 0x0160 (otherwise it will throw "This is not a Win32 executable" error).
Launch

What is the expected behavior? What do you get instead?
The application is supposed to work.
Instead, it throws "No source found. Do you have a configuration problem? Try to reinstall the program." error, then flashes the fully rendered window for a second and shuts down.
What version of the program are you using? On what operating system?
Grabber v5.5.2. OS: Windows XP x64 SP2 (NT 5.2)

Run it on Windows 7. Xp is way too old to be messing with on any machine, let alone one that has a connection to the net.  You'll get much better performance too. I mean I'd recommend Windows 10, but seeing as you're running XP, I doubt you want to even think about 10. Otherwise run it on Ubuntu or something.

I'm running XP x64. X64. It has very little to do with the "XP" you think of. Aside proper hardware support and much better security mechanisms internally (because it's 2003 Server under the hood with "Server" part removed), it allows me to record sound on my hardware, unlike 7 which fails to do so. In fact, "security" in Windows 7 is much worse, all "thanks" to "TrustedInstaller" and task scheduler which prevents admin account to shutdown/delete vulnerable/malicious tracking and Samba services.
I'm not going to run a dedicated Linux machine just to use a booru grabber that has absolute zero reason to make NT 6.x as a mandatory requirement.
Sad to see this application deleted from my hard drive, but it seems I don't have much choice.

Instead, it throws "No source found. Do you have a configuration problem? Try to reinstall the program." error, then flashes the fully rendered window for a second and shuts down.

This is unrelated to Windows XP or a build issue (else the program wouldn't even start up).
This only means that Grabber cannot file some configuration files on your system. If you used the installer to install Grabber, they should be in C:\Users\%USERNAME%\AppData\Local\Bionus\Grabber.
If they are present, you can try to make the program portable (see here, you just have to put the files from the install folder and AppData in the same writable location).
If they're not, maybe the installer didn't run properly or didn't have the writing rights for some reason. In that case, you can file most files here (it might be a pain to download them one by one on Github so I'd advice downloading the whole repo as a zip and copying the release folder from there).

Okay, after short investigation:

The files were written by installer.
Coping or moving them to Grabber's installation directory (differs from "Program Files") didn't help.
Copy-pasting them straight from repo archive didn't either.

Conclusion: I don't know how you've coded the path resolving for the resources (no C/C++ knowledge), but it appears the application simply fails to locate its own files on 64-bit XP regardless of their location.


Unable to deploy 0.9.0-m1 on OpenShift

What happened:
When trying to deploy 0.9.0-m1 with OpenShift 4.7 and join clusters, only two pods are being created under the submariner-operator namespeace:
$ oc get pods -n submariner-operator
NAME                                          READY   STATUS    RESTARTS   AGE
submariner-lighthouse-agent-9db5b68c6-5c4nw   1/1     Running   0          14m
submariner-operator-58fcf65dfd-6ckfs          1/1     Running   0          15m

Attached are the logs from the Operator pod.
What you expected to happen:
All pods to be running, and deployment to be successful.
How to reproduce it (as minimally and precisely as possible):

Deploy 0.9.0-m1 with the latest OpenShift version on AWS via subctl by following https://submariner.io/getting-started/quickstart/openshift/aws/

Anything else we need to know?:
This is a non-Globalnet deployment with OpenShiftSDN.
Environment:

Submariner version (use subctl version): 0.9.0-m1
Kubernetes version (use kubectl version): v1.20.0+bd9e442
Cloud provider or hardware configuration: OpenShift on AWS (IPI)

log.txt

log.txt

I also noticed that L4 in this log says 2021-03-03T06:54:49.839Z	INFO	cmd	Submariner operator version: subctl-devel while this is a 0.9.0-m1 deployment:

$ oc describe pods -n submariner-operator submariner-operator-58fcf65dfd-6ckfs | grep Image
    Image:         quay.io/submariner/submariner-operator:0.9.0-m1
    Image ID:      quay.io/submariner/submariner-operator@sha256:5ded2e8a225f641305be5dfb19612854411b7ad667205816c799d65648c2dc9a

This appears to be a permissions issue:
ERROR	controller-runtime.controller	Reconciler error	{"controller": "broker", "name": "submariner-broker", "namespace": "submariner-operator", "error": "configmaps is forbidden: User \"system:serviceaccount:submariner-operator:submariner-operator\" cannot create resource \"configmaps\" in API group \"\" in the namespace \"submariner-k8s-broker\""}

Ahah! We’re missing “create” on the ClusterRole for configmaps.

@skitt  I tested this with OCP 4.7 using devel and I see the same problem and the same error in the log. IIUC, we also need https://github.com/submariner-io/submariner/pull/1009 to fully address this?

Note: I can confirm that Submariner v0.8 deploys successfully on OCP 4.7, so this is specific to 0.9.0-m1 or devel.

So it appears the SA account name is always null when trying to update the SCC privileged
$ oc describe scc/privilege
Users:					system:admin,system:serviceaccount:openshift-infra:build-controller,system:serviceaccount:submariner-operator:

system:serviceaccount:submariner-operator:<EMPTY>
The problem is somewhere here GetObjectName when we try to parse the SA name from that embedded yaml file


generation failed if github commit api return 404 Not Found

Here's what I've got when running generator for my private repo:
/Users/nantas/.rvm/gems/ruby-2.1.5/gems/github_api-0.12.3/lib/github_api/response/raise_error.rb:14:in `on_complete': GET https://api.github.com/repos/fireball-x/dev/git/commits/38f8efae9be54183fa08373ed203d7c955917003?access_token=xxx: 404 Not Found (Github::Error::NotFound)

For some reason commit 38f8efae9be54 cannot be found in the commit history, but it's still referenced as the commit that closed an issue.
I'm not sure how important it is to get the commit date as the issue closed date. But if the commit is not found, the generator should just use actual_date of the issue without blocking the whole process. Is that right?

@nantas yes, that's absolutely right! Thank you!
Can you tell me, which repo generate this issue?

I did more tests and find out the exact cause of the issue.
You can reproduce the issue with my test repo: https://github.com/nantas/changelog_test
With the test repo, the commit that return 404 Not Found is a commit in another repo:  https://github.com/nantas/changelog_test2/commit/34a8eee7aa272d5226126d986764a7945a9253b9
The program assumes that all commits that close issues are from the same repo. But in our case and many other application consists of multiple submodules that's not the case. We use one main repo for managing the project and we close main repo's issue from submodule repos.
I think an improvement on that matter will do great help to developers like my team. And also a fallback solution for github api error return would be great too.

@nantas Thanks a lot to clarifying! I will handle it soon, get in touch!

@nantas Thanks a lot. Issue fixed in 1.3.2.
I take some research, but still don't know, how to fetch repo address from events github api. It's needed to define correct closed date.
Now I use just closed date of this issue (but sometimes this date is not, that we looking for. see #37 for more details).
Let me know, if you find methods to fetch commit's repo address from github api.


Broken release pipe for KMM (2.2.1)

PR to the repo was merged: https://github.com/k8s-operatorhub/community-operators/pull/5473
Operator Release job passed: https://github.com/k8s-operatorhub/community-operators/actions/runs/12463914417
The operator wasn't published in https://operatorhub.io/operator/kernel-module-management (latest version is still 2.2.0)

/assign @mvalarh @J0zi
This issue is idle since last week and it is urgent.

/cc @J0zi


Added support for CompactJsonFormatter and FileSink options

The archived files can now be saved in compact JSON format. So, you can import them back into Seq without losing data;
Package updates:

Removed deprecated Serilog.Sinks.RollingFile (version: 2.1.0);
Added Serilog.Sinks.File (version 4.1.0);
Added Serilog.Formatting.Compact (version 1.1.0);

Breaking changes:

Uses the default File sink output template;
PathFormat has been replaced by Path and RollingInterval;

New features:

Added support for custom output template;
Added support for CompactJsonFormatter;
Added support for rolling interval: Hour, Minute, Day, Month, Year or Infinite;
Added support for file size limit;
Added support for roll on file size limit;
Added support retained file count limit;
Added support for buffering;
Added support for sharing;
Added support for flush to disk interval;

Testing

Tested successfully with Seq 2020.4.5119;

Thanks for the PR, Steven! We'll need to give all these changes some thought and get back to you.
Best regards,
Nick

No problem. I think I understand the dilemma here.
I have just one question: In the Replication app I see you remove the @@i and @@seqid properties. Should I do this in this pull-request also or make it a UI option? Can you also tell me what these seq properties represent (are they both unique or unique together)? OK, two and a half questions 😉
Thanks in advance and keep up the good work.

Hi! Those are @EventType and @Id, replication removes them because they're computed on ingestion at the other end. They're useful for archive files, I think.
I'd hold off on moving this PR to much farther forward, for now; it's not certain we'll be able to merge it due to the breaking change in path configuration (may not be noticed by current users), and because Seq.App.JsonArchive already provides newline-delimited archiving. Going to discuss and dig into it further, here 👍

Hi @Nevets82 - just letting you know this hasn't slipped off the radar; we have some planning and catching up to do this week, we'll loop back around as soon as we can. Cheers!

Hi @Nevets82 - just letting you know this hasn't slipped off the radar; we have some planning and catching up to do this week, we'll loop back around as soon as we can. Cheers!

Hi @Nevets82 - thanks again for this!
We'd love to see it in the wild, but -

Breaking change in the file archive app could have problematic implications for people using this already, and
The Seq.App.JsonArchive app is the option we're recommending for compact JSON support.

But, there's a lot of opportunity to improve the file archive app. Would you consider releasing it independently, as an alternative app? (Seq.App.FileSet ?)
Regarding customized output/JSON formatting, https://github.com/serilog/serilog-expressions has some interesting functionality that could enable both - would be interesting to consider as an alternative to message templates/hard-coded JSON formats. Let me know if you're keen to explore this :-)

Hi @Nevets82 - thanks again for this!
We'd love to see it in the wild, but -

Breaking change in the file archive app could have problematic implications for people using this already, and
The Seq.App.JsonArchive app is the option we're recommending for compact JSON support.

But, there's a lot of opportunity to improve the file archive app. Would you consider releasing it independently, as an alternative app? (Seq.App.FileSet ?)
Regarding customized output/JSON formatting, https://github.com/serilog/serilog-expressions has some interesting functionality that could enable both - would be interesting to consider as an alternative to message templates/hard-coded JSON formats. Let me know if you're keen to explore this :-)

Thanks again for sending this one; sorry we weren't able to merge in the end. Hope it's all going well!


How to use transpose operation in refactored model ？

Hi! I now want to achieve a change in output dimension by removing old nodes and adding new ones.
Specifically，from [CNHW] to [NCHW].
My code is as follows：

I am not sure if I am using the new node transpose correctly? Because the model converted in this way reports an error when doing onnx-sim.
Hope to get your help, thanks.

I solved the problem, it was my wrong usage of transpose.
The correct way should be this：
so.node('Transpose', inputs=['output'],outputs=['transpose'], perm = (1,0,2,3))
Still want to thank you for your open source project, thank you.


tests: benchmarks: sys_kernel: Add mem_slab benchmark and changed checking for pending threads algo

In single-thread applications or when mem_slab is used only by one thread,
there is no need to check if any therad is pending during freeing the slab.
In multithreading application this can be optimized - check for
pending threads (in k_mem_slab_free) could be done only if there is no memory
to allocate.
This change introduces significant time savings.
Execution mem_slab benchmark on nrf5340 (App core @64MHz), 1000 iterations.
Times per single alloc/free:
Without optimization:
Alloc: 1068 [ns]
Free: 1617 [ns]
With optimization
Alloc: 1068 [ns]
Free: 915 [ns]
Difference is significant: 702[ns].

btw for qemu_cortex_m3 i got following results for single k_mem_slab_free:

without optimization: 4268ns
with: 2468ns

@andyross @andrewboie can you take a look?

@andyross @andrewboie would you mind taking a look please?

@carlescufi  Can we merge this?


Upgrade placement API to v1beta1

Signed-off-by: Roke Jung<EMAIL_ADDRESS>Upgrade Placement and PlacementDecision API to v1beta1
https://github.com/stolostron/backlog/issues/19762

/lgtm


Don't HTML escape the text parts

Currently it HTML escapes special characters in the subject and plain text parts of the message template. This fixes that.
PS: Hi Artem! I hope you and your family are well?

Hi Tom! You are right, I've missed this as usually ))) Thank you for the PR!
PS: Yes, we are fine. Hope you too! Will write to you via hangouts :)

Can this be merged please?

Sorry, I still have not merged this because of failing tests on CircleCI. Will try to fix this in few days.

@IlyaSemenov The fix is merged and published at PyPI.


Calendar of activities

We should also provide a charming calendar that shows all activities that one person performed. There should be a week, month, and year view.

@firefly-cpp I have implemented calendar.
Here is the guideline how to use it.

This is amazing! Thanks for all the hard work.


Add Ability to Edit Additional Asset Details

Add a UI to modify additional asset details. The additional items to make editable per asset:

Liquidation Threshold
Loan To Value
Usage as collateral

These changes will have the useful benefit of mimicking changes recommended in the Aave governance process as these are risk parameters that are tweaked relatively often. Users will have the ability to simulate these parameter changes ahead of time to have an advanced understanding of how parameter changes will affect their position.

Here's an example RFC that this issue could support nicely: https://governance.aave.com/t/arfc-gauntlet-risk-parameter-updates-for-ethereum-v3-arbitrum-v3-ethereum-v2-2023-06-26/13825


MM-18832 Update message count string

Summary
Update message count string.
Ticket Link
https://mattermost.atlassian.net/browse/MM-18832

Also ticket says is for 1.25 as I’ve changed it to avoid issues with translations

@jwilander
Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Fetching origin
+++ Updating remotes done...
!!! 'upstream/release-1.25' not found. The second argument should be something like upstream/release-0.21.
    (In particular, it needs to be a valid, existing remote branch that I can 'git checkout'.)


Lint & Upgrade to Django 5

I was able to talk live with Jeffrey Clark and thank him for noticing the @LMCO github profile and open repositories<EMAIL_ADDRESS>


looperenv environment variable error

Looks like environment variable name 'LOOPERENV' changed? it's no longer being picked up, and suggests instead a variable called COMPUTE_SETTINGS which is incorrect:
Loading COMPUTE_SETTINGS: /home/ns5bc/.local/lib/python2.7/site-packages/looper/submit_templates/default_looperenv.yaml
Using default COMPUTE_SETTINGS. You may set environment variable COMPUTE_SETTINGS to configure environment settings.

It does this on looper check but not on looper run. strange.

My bad; I forgot to redefine that property on the looper-specific Project. https://github.com/epigen/looper/pull/125 should address this


about target domain dataset

Dear author! In your code, during construct CoFoSegmentationDataset, you put train and valid together, which means they have the same number. But in your paper, Kvasir(train) is 700 and total numer of EndoTect is 200. Maybe you can kindly upload you train/valid/test .csv

sorry i didn't see .csv


How to access graylog-datanode's API to reschedule shards?

I've got a bunch of failing shards that I'd like to investigate through _cluster/allocation/explain and possibly cause rescheduling.
However I keep getting authentication finally failed when curling the datanode:9200.
What are the credentials for the node or where are they stored?

If you are using Graylog/Data node 6.0, you can go to System/Data node/Configuration and generate a client certificate to use for calling the datanode OS api.
Or, as an alternative, you can use the Graylog endpoint which proxies calls to the api with a regular Graylog authentication token: api/datanodes/any/opensearch/_cluster/allocation/explain

Did not know that graylog can proxy my calls - will give it a shot!

Marking as resolved - easier to use the graylog instance as proxy :)


moodle: 4.4.3 -> 4.4.4

Fixes CVE-2024-48901, CVE-2024-48900, CVE-2024-48899, CVE-2024-48898, CVE-2024-48897, CVE-2024-48896.
Release notes:
https://moodledev.io/general/releases/4.4/4.4.4

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I will take care of the backport to 24.05 manually.

Another bug/patch fix version has been released v4.4.5:
https://moodledev.io/general/releases/4.4/4.4.5


Fixes infinite loop (and consequentially spiked CPU usage) on Ctx Timeout

Fixes infinite loop (and consequentially spiked CPU usage) on ctx timeout. Noticed this issue when trying to limit the max execution time of a crawl job by using Context.WithTimeout().

Coverage increased (+0.3%) to 67.372% when pulling 8f679af296de7a418bd5ab6b2fc49678b2b00d28 on JalfResi:infinite-loop-on-ctx-timeout into 4cc4ba1ca23fb669e5ec66cda5c2bcdc3c10f672 on knq:master.

I'm being affected by this too. Thanks for the patch.
Any particular reason this was not merged yet? //cc @kenshaw

Apologies on the delay. Merged.

Awesome thanks!


Namespace resolving issue when using database seeder and additional model extending

Laravel Version: 5.5.4
PHP Version: 7.1.4
Database Driver & Version: pgsql

Description:
While using php artisan db:seed command it is not correctly resolving namespaces
Steps To Reproduce:

create a directory app\Models
inside of this directory create some base model, let's just name it "BaseModel" that extends Illuminate\Database\Eloquent\Model
create yet another model to seed with data, let's say "Village" that extends app\Models\BaseModel which extends Illuminate\Database\Eloquent\Model
Now try to seed this "Village" model by using seeder class, and the error
[Symfony\Component\Debug\Exception\FatalErrorException]
Class 'app\Models\BaseModel' not found
pops out

If I remove the BaseModel from these steps so the Village model would extend Illuminate\Database\Eloquent\Model directly then the error won't show, but it's still not a solution
Also composer dump-auto did not solve the problem

This is not a bug. Check your namespace of the model. It should be App\... not app\...


Publish 1.34.0 image

https://blog.rust-lang.org/2019/04/11/Rust-1.34.0.html

Would be great to have published, we want to upgrade to 1.34 and use the image for a few lambdas. Thanks!

@repi just published 0.2.1-rust-1.34.0 which is the new latest to docker hub https://hub.docker.com/r/softprops/lambda-rust/tags
not sure if you are a serverless framework user or not but I'm going to update https://github.com/softprops/serverless-rust and cycle through various serverless rust templates with updates this weekend

Thanks! Right now we just use the image directly and publish on AWS manually without any framework.


[NETSDK1004

hi i get this problem even after followed the microsoft solutions but it did not work

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

ID: 62af3ec3-7d59-7b4a-b9a1-413b8956bab7
Version Independent ID: 31e0311a-8823-1d30-8f38-ac0c37ca07d9
Content: NETSDK1004: Assets file not found - .NET CLI
Content Source: docs/core/tools/sdk-errors/netsdk1004.md
Product: dotnet-fundamentals
Technology: dotnet-cli
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

Thanks for the question. You'll probably get a faster answer on a support forum, such as Stack Overflow, or a support chat, such as Slack or Gitter. If you post the question elsewhere, please update this issue with the link.


Supporting netstandard2.0?

I think it would be great to support netstandard2.0, which would make it available also for projects targeting net462 and newer.

Yep, you are right, against all expectaton Data Protection api support both net462 and netstandard so I extended the Nuget package in the new version. However I have just released an improved version of the package working on any ConfigurationSource check out this new package if interested Fededim.Extensions.Configuration.Protected, a new article on CodeProject on this new package will be published in the next few hours.


feat(plugin-validator-besu): generate signature of simple asset

Description
As a developer I want to be able to obtain signatures of ledger state from Cactus nodes through the API so that I can implement federated validation in the new architecture as it was featured in the older codebase.
The end to end flow is this:
Client device with Cactus SDK => HTTP Request to Cactus Node (API Server with validator plugin) => validator plugin => besu ledger => smart contract method execution => return response (signature) to validator plugin => respond to HTTP request to the SDK
The above could also be called as an RPC interface where the validator plugin is just an RPC forwarder that converts REST API requests from the SDK to smart contract method invocations.
Related to:
Also feeds back into these
https://github.com/hyperledger/cactus/issues/99
https://github.com/hyperledger/cactus/issues/23
Old Simple Asset Transfer code (which is what we are improving here):
https://github.com/hyperledger/cactus/tree/master/contribs/Accenture-BIF/core/examples/simple-asset-transfer
On-ledger verify method in the existing contract: https://github.com/hyperledger/cactus/blob/master/contribs/Accenture-BIF/core/examples/simple-asset-transfer/besu/contracts/Root.sol#L116
Acceptance Criteria

Validation request can be sent via the SDK
The validator plugin has the ability to query ledger state by depending on (importing via the plugin registry) the ledger connector plugin
The validator plugin ships with it's own smart contract written in solidity that is able to perform the signature generation on-ledger. The smart contract can be the same or similar as the one linked above.
Individual nodes can be asked for their signatures separately
end to end test case where the end to end flow (see above) is actually played out with a besu test ledger running in a container
Validator plugin has a method that when called, it can deploy it's contract to the target ledger which can also leverage the ledger connector plugin which already knows how to deploy a JSON artifact of a compiled solidity contract.
OpenAPI specification file for the REST API endpoints that the plugin has

cc: @takeutak @jonathan-m-hamilton @sfuji822

I partially started tackling this issue while developing the blockchain migrator #158 (as I need to interact with smart contracts from within the test ledger). In particular, I've added methods to the besu-connector.

I partially started tackling this issue while developing the blockchain migrator #158 (as I need to interact with smart contracts from within the test ledger). In particular, I've added methods to the besu-connector.

@RafaelAPB Maybe this would also be helpful? https://github.com/hyperledger/cactus/pull/282


AVIF images don't load on Firefox 92+

Firefox 92 (Beta) on Mac, Windows and GNU/LInux doesn't load the two AVIF images.

https://gpac.github.io/ComplianceWarden-wasm/avif.html for https://identitadigitale.gov.it/static/217fda2f925e1d7ca949d09b77f9d58e/17ccf/section01.avif reports:
Compliance Warden, version v29-master-rev0-geb35e21.
+--------------------------------------+
| avif validation |
+--------------------------------------+

Specification description: AVIF v1.0.0, 19 February 2019
https://aomediacodec.github.io/av1-avif/

[avif][Rule #7] Error: [ItemId=1] The values of the AV1CodecConfigurationBox shall match
the Sequence Header OBU in the AV1 Image Item Data:
AV1CodecConfigurationBox:
seq_profile=0
seq_level_idx_0=13
seq_tier_0=0
high_bitdepth=0
twelve_bit=0
mono_chrome=0
chroma_subsampling_x=1
chroma_subsampling_y=1
chroma_sample_position=0
Sequence Header OBU in the AV1 Image Item Data:
seq_profile=0
seq_level_idx_0=8
seq_tier_0=0
high_bitdepth=0
twelve_bit=0
mono_chrome=0
chroma_subsampling_x=1
chroma_subsampling_y=1
chroma_sample_position=0

[avif][Rule #7] Error: [ItemId=2] The values of the AV1CodecConfigurationBox shall match
the Sequence Header OBU in the AV1 Image Item Data:
AV1CodecConfigurationBox:
seq_profile=0
seq_level_idx_0=13
seq_tier_0=0
high_bitdepth=0
twelve_bit=0
mono_chrome=0
chroma_subsampling_x=1
chroma_subsampling_y=1
chroma_sample_position=0
Sequence Header OBU in the AV1 Image Item Data:
seq_profile=0
seq_level_idx_0=8
seq_tier_0=0
high_bitdepth=0
twelve_bit=0
mono_chrome=0
chroma_subsampling_x=1
chroma_subsampling_y=1
chroma_sample_position=0

[avif][Rule #11] Error: The mono_chrome field in the Sequence Header OBU shall be set to 1 (item_ID=2)

========================================
[avif] 3 error(s), 0 warning(s).
========================================

===== Involved rules descriptions:

[avif][Rule #7] Section 2.2.1
The values of the fields in the AV1CodecConfigurationBox shall match those of the
Sequence Header OBU in the AV1 Image Item Data.

[avif][Rule #11] Section 4. Auxiliary Image Items
The mono_chrome field in the Sequence Header OBU shall be set to 1.
The color_range field in the Sequence Header OBU shall be set to 1.

+--------------------------------------+
| miaf validation |
+--------------------------------------+

Specification description: MIAF (Multi-Image Application Format)
MPEG-A part 22 - ISO/IEC 23000-22 - w18260 FDIS - Jan 2019

[miaf][Rule #2] Error: compatible_brands list shall contain 'miaf' (not found) and 'mif1' (found)
[miaf][Rule #26] Error: Found no 'pixi' associated for 2 displayable (not hidden) images (ItemIds={1,2})

========================================
[miaf] 2 error(s), 0 warning(s).
========================================

===== Involved rules descriptions:

[miaf][Rule #2] Section <IP_ADDRESS>
The FileTypeBox shall contain, in the compatible_brands list,
the following (in any order): 'mif1' (specified in ISO/IEC 23008-12)
[...]
Files conforming to the general restrictions in clause 7 shall include
the brand 'miaf' in the compatible_brands in the FileTypeBox.
/!\ this rule doesn't look for 'mif1' and 'miaf' brands rule-conformance:
if a brand is absent then its conformance rules won't be checked here /!\

[miaf][Rule #26] Section <IP_ADDRESS>
The pixel information property shall be associated with every image that is
displayable (not hidden)

+--------------------------------------+
| heif validation |
+--------------------------------------+

Specification description: HEIF - ISO/IEC 23008-12 - 2nd Edition N18310

========================================
[heif] No errors.
========================================

+--------------------------------------+
| isobmff validation |
+--------------------------------------+

Specification description: ISO Base Media File Format
MPEG-4 part 12 - ISO/IEC 14496-12 - m17277 (6th+FDAM1+FDAM2+COR1-R4)

========================================
[isobmff] No errors.
========================================

This might be the result of  a bug in gatsby-plugin-image or one of its dependency and Firefox 92 being stricter than the other browsers. We should try and update Gatsby / gatsby-plugin-image to the latest version.

No problem on my side with FF97 @bfabio

@libremente I think it's safe to close this, it worked ever since.


 Establish commits
for inames_batching again that were reverted.
Don't merge. This will be a series of commits to refactor the interactions with the PMAPI, and improve the performance  when requesting  inames.

@spiermar This is ready for review and merging.

Now supports batching of _indom requests to fetch instance domains name
Also, I enabled HTTP caching for those requests, so only happen once per host, and once per context
Added new function to *Metric classes, called pushValue, with the same semantic as, and meant to replace, pushValues(), but it takes the name of the metric (iname) as parameter.
Instead of defaulting to 'Series - N', now it defaults to the metric name.

Future work for another pull-request,

Data manipulation to retrieve the instance domain names, from the instance ids could be simplified


Bump TypeScript to 3.7

I want us to start using the ?. and ?? operators for better handling nullish values.
See Optional Chaining (?.) and Nullish Coalescing (??) in the release notes for more info.

We also have to update the ESLint parser for TypeScript.

I had to update prettier to support the new syntax and this introduced new linter errors that I had to fix.

I love these operators back from C# days. Thank you for doing the PR. Would love to use them!


I2P support

Describe the solution you'd like
It would be very cool if bitmagnet had built-in I2P support. See https://geti2p.net if you are unfamiliar. Essentially I2P is similar to Tor but there are no exit nodes.
Describe alternatives you've considered
Doing this from scratch. Seems like a waste of effort.
Additional context
If you would like to know more, please join us on the postman I2P IRC server #saltr channel.

That'd be quite interesting. What separates i2p from tor is that there's a lot of i2p-internal torrent traffic that doesn't interact with the clearnet at all. It's like its own little torrent bubble.

We have some fairly extensive Go libraries with I2P implementations of net.Conn, net.PacketConn, and net.Addr allowing developers to drop them in where possible. onramp can be configured to use the address format that the in-I2P DHT expects. So if you make use of the net.* interface types in the existing code then we can make implementation very straightforward.


HuggingFace Gemma-2-9b/27b incorrect

Hi, I was able to verify the MMLU score for HuggingFace gemma-2-9b-it to within .2. However, for gemma-2-27b-it, the score (52.3% on all) is way off. Is there some mistake on the repo there? Or is it particularly sensitive to bfloat16?

Hi @cinjon,
The MMLU scores for the Gemma-2-9B-IT and Gemma-2-27B-IT models are 71.3% and 75.2%, respectively. For further reference, please refer to this paper. The performance degradation observed in the Gemma-2-27B-IT model is likely due to its sensitivity to bfloat16 precision settings, which can impact inference quality if not handled properly.
For more detailed insights and related discussions, please check the following references:
ref1
ref2
Thank you.

Hi again. I am struggling with this and made a reproduction for you to look at: https://gist.github.com/cinjon/de9a22f57cfa0dc9ccb2afc255a8093e.
The main problem are the results below, which show roughly reproductions on gemma-27b, slight degradation on gemma-27b-it, slight degradation on gemma-2-9b, and terrible result on gemma-2-9b-it. What am I doing wrong? Thanks.
1. python -m huggingface_test_gemma_base_mmlu --model_name="google/gemma-2-9b"
--> all 0.7057399230878793
2. python -m huggingface_test_gemma_base_mmlu --model_name="google/gemma-2-9b-it"
--> all 0.6387266771115225
3. python -m huggingface_test_gemma_base_mmlu --model_name="google/gemma-2-27b-it"
--> all 0.7518159806295399
4. python -m huggingface_test_gemma_base_mmlu --model_name="google/gemma-2-27b"
--> all 0.7517447657028913

To be clear, it's not the "bfloat16" in the gist either - it's roughly the same result with "float32" too.


Be able to predict NMR spectra and superimpose the result

@hamed-musallam Please prepare the code to allow prediction

add an icon in the chemical structure toolbar

You should create an icon in cheminfo-font. This icon is a spectrum with a circle + (or something like that)

the icon is only active if there is a molecule (molecular formula is not empty)

When you click on the new + icon a dialog box appears in which you have checkbox that allows to create (we may at the same time create one or many spectra):

1H
13C
hsqc
hmbc
And a field with 'Spectrometer frequency', default 400 [MHz]

I update nmr-processing in order t have a new method: predictionProton.
Please call predictionProton.fromMolfile with the currently displayed molfile. It will return 'ranges' that should be more or less in the correct format.
Please add a 1D proton spectrum with the ranges and currently as data an empty x:[], y:[] object.


Implement Vertex

Implement the API for Vertex

Develop error handling

Source: https://blog.canopas.com/how-to-create-your-own-chatbot-using-palm-2-model-chat-bison-001-fe99a2448f28

School account blocks the use of google cloud and I have run out of credits in my main account.

[ ] Email prof about permissions
[ ] Create central account?


Add external exporter to Pelorus

Describe the behavior changes introduced in this PR
Add a Proof of Concept (PoC) for adding external exporters to Pelorus.
Linked Issues
No.
Testing Instructions
Follow the instructions in poc_external_exporter/poc_external_prometheus.md.

As talked with @mpryc, using extra_prometheus_hosts should get the job done. But I tested out and I believe extra_prometheus_hosts is not working (the configuration of charts seems correct, charts/pelorus/templates/prometheus-scrape-config-secret.yaml would create the config and secret and charts/pelorus/templates/prometheus-cr.yaml would add the config to prometheus operator, just like in this PoC, but I think not even the secret is being created, because additional-scrape-configs does not appear in oc get secret -n pelorus)
I have created an Pelorus instance with
apiVersion: charts.pelorus.konveyor.io/v1alpha1
kind: Pelorus
metadata:
  name: external-example-configuration
spec:
  exporters:
    instances:
      - app_name: deploytime-exporter
        exporter_type: deploytime
        extraEnv:
          - name: NAMESPACES
            value: example_namespace
      - app_name: committime-exporter
        exporter_type: committime
        extraEnv:
          - name: NAMESPACES
            value: example_namespace
  extra_prometheus_hosts:
    - id: "mateus"
      hostname: "node.demo.do.prometheus.io"
      password: ""

to test it out.
I tried it manually, by creating prometheus-additional.yaml with (this is the content that helm would have created using extra_prometheus_hosts)
- job_name: "federated-prometheus-mateus"
  scrape_interval: 15s
  honor_labels: true
  metrics_path: '/federate'
  params:
    'match[]':
      - '{job="openshift-state-metrics"}'
  scheme: "https"
  basic_auth:
    username: 'internal'
    password: ""
  tls_config:
    insecure_skip_verify: true
  static_configs:
    - targets:
        - "node.demo.do.prometheus.io"
      labels:
        federated_job: "federated-prometheus-mateus"

and following the subsequent steps of poc_external_exporter/poc_external_prometheus.md, and it works.

I suspect is something related to checking if the variable is being used, the other logic seems correct.

Tested more, and I think the problem is the operator, not helm.
I have run helm template --debug pelorus-test charts/pelorus > debug.yaml changing the charts/pelorus/values.yaml, and the configs are added to prometheus-cr.yaml.
I tried to used custom_ca in operator, and it did not change anything in prometheus-cr.yaml (to test this, create an instance, can be like the example in OpenShift, but adding custom_ca: true. It should apply the logic of charts/pelorus/templates/prometheus-cr.yaml, but if you check the object, it does not have any of the options custom_ca would add).
I believe the problem is in pelorus-operator/bundle/manifests/charts.pelorus.konveyor.io_pelorus.yaml (related to https://github.com/konveyor/pelorus/issues/751). Because the values of spec.properties that are listed (only exporters, prometheus_retention, prometheus_retention_size, prometheus_storage, prometheus_storage_pvc_capacity and  prometheus_storage_pvc_storageclass from full list), seem to work, but extra_prometheus_hosts and custom_ca, for example, that are not listed, do not work.

@mateusoliveira43 tested and you are right the values are not consumed by the operator.
The Prometheus operator expected values additionalScrapeConfigs which are in our templates are correct
The pelorus operator templates fails to create secret additional-scrape-configs from the charts/pelorus/templates/prometheus-scrape-config-secret.yaml, which then is used by the prometheus-operator.

@mateusoliveira43 looks like it's not only related to the external exporter configs, also defining things such as thanos won't be used:
thanos_bucket_name: <...>
bucket_access_point: <...>
bucket_access_key: <...>
bucket_secret_access_key: <...>

This did not created proper thanos configs and configured grafana to point to the prometheus rather then thanos.

The top level configs such as, does work:
  prometheus_retention: 1y
  prometheus_retention_size: 1GB
  prometheus_storage: true
  prometheus_storage_pvc_capacity: 2Gi
  prometheus_storage_pvc_storageclass: gp2

So it looks like anything outside of the schama is ignored while creating instance. This was not the case when we created 0.0.1 of this operator.

Depends On: https://github.com/konveyor/pelorus/pull/861
Note it's possible to test without creating new operator by modyfing Pelorus CRD in the cluster.
Left side menu (Administration->CustomResourceDefinition), search for Pelorus, select Yaml and add missing option (number of spaces are important).

@mpryc this workaround did not work for me, the Pelorus manager gets error

Closing this PR without merging as it was a PoC. The implementation with the given requirements from https://github.com/orgs/konveyor/projects/51/views/2?pane=issue&itemId=20613515 will be opened in follow up


play/pause inside/outside viewport inconsistency

I am using multiple video instances on a single page – also using the fullpage.js script (http://alvarotrigo.com/fullPage/).
Some videos behave as expected, playing when in viewport and pausing when not, while some keep playing also when not in the viewport.
Any ideas what could cause this issue?

how did you solve this @ummocrono ?