Add TI J721e R5 and BeagleBone AI64 R5 initial support

This PR (non-working port) adds device tree and soc support for TI J721e_r5 and Beaglebone AI64 board support for hello_world application.
Signed-off-by: Prashanth S<EMAIL_ADDRESS>

@slpp95prashanth is this port in the current state able to pass for example the tests in tests/kernel for example?

@slpp95prashanth is this port in the current state able to pass for example the tests in tests/kernel for example?

Yes, all the tests kernel are passed/skipped. But 3 testcases failed.
Error Log:
/__w/zephyr/zephyr/include/zephyr/spinlock.h:281:59: error: unused parameter 'k' [-Werror=unused-parameter]
281 | static ALWAYS_INLINE void z_spin_onexit(k_spinlock_key_t *k)
|                                         ~~~~~~~~~~~~~~~~~~^
cc1: all warnings being treated as errors

@slpp95prashanth is this port in the current state able to pass for example the tests in tests/kernel for example?

@carlocaione Yes, all the tests kernel are passed/skipped. But 3 testcases failed (https://github.com/zephyrproject-rtos/zephyr/pull/59191/checks?check_run_id=14976309563). Error Log: /__w/zephyr/zephyr/include/zephyr/spinlock.h:281:59: error: unused parameter 'k' [-Werror=unused-parameter] 281 | static ALWAYS_INLINE void z_spin_onexit(k_spinlock_key_t *k) | ~~~~~~~~~~~~~~~~~~^ cc1: all warnings being treated as errors

Is the PR https://github.com/zephyrproject-rtos/zephyr/pull/60375 aimed at fixing the above issue?

Is the PR #60375 aimed at fixing the above issue?

It is indeed.

@emob-nordic this is for you.

@carlocaione @cfriedt Can the interrupt controller addition be a separate PR from platform support for easier reviewing?
Seeing some examples in the past where it has been done like that : https://github.com/zephyrproject-rtos/zephyr/pull/19865
@slpp95prashanth The commit message for

@carlocaione @cfriedt Can the interrupt controller addition be a separate PR from platform support for easier reviewing? Seeing some examples in the past where it has been done like that : #19865

No objections from me.

Thanks for confirming @carlocaione @cfriedt .
@slpp95prashanth can you please create a new PR for the VIM interrupt controller addition and mention it as a dependency here.

@vaishnavachath I am working on the timer support and want to add in the later commits. Shall we add timer support in the later commits?

@vaishnavachath I am working on the timer support and want to add in the later commits. Shall we add timer support in the later commits?

@slpp95prashanth , sure, do you mean later commits in this PR? If that also can be a separate PR that would be great, in that way the corresponding driver, bindings will be easier to review and experts from the subsytem reviews them.
When you split the changes for intc/other from this PR make sure to follow these points:

Run twister tests locally with all the combined changes, for example when you create separate pull request for VIM, the twister run may pass for the particular PR, but would not exercise all the code paths since there might be no consumers. This would eventually lead to us sending fix PRs back and forth which is something that we want to avoid.
Mention the relationship between both PR so that the reviewers are aware.

@vaishnavachath I am working on the timer support and want to add in the later commits. Shall we add timer support in the later commits?

@slpp95prashanth , sure, do you mean later commits in this PR? If that also can be a separate PR that would be great, in that way the corresponding driver, bindings will be easier to review and experts from the subsytem reviews them.
When you split the changes for intc/other from this PR make sure to follow these points:

Run twister tests locally with all the combined changes, for example when you create separate pull request for VIM, the twister run may pass for the particular PR, but would not exercise all the code paths since there might be no consumers. This would eventually lead to us sending fix PRs back and forth which is something that we want to avoid.
Mention the relationship between both PR so that the reviewers are aware.

@vaishnavachath Yes as separate PR, Once this PR is merged I will create a separate PR for systick support. With all the modules and multiple PR simultaneously it is quite difficult for me to manage. So as an non working initial support can I have board, soc, device tree and vim support?

@vaishnavachath Yes as separate PR, Once this PR is merged I will create a separate PR for systick support. With all the modules and multiple PR simultaneously it is quite difficult for me to manage. So as an non working initial support can I have board, soc, device tree and vim support?

@slpp95prashanth Sorry, systick is important for the base support, systick support coming in later is not a feasible plan.

This PR depends on #60856 and #61020.

From an organizational point of view, I appreciate you starting with "beagle_", thanks!. I think "bbai64" can be grouped together, not "bbai_64". I think someone could easily have an a72 target, so I suggest making the whole directory string "beagle_bbai64_r5" to make it clear. Similarly, I'm planning "beagle_play_cc1352" for the M4 on the CC1352 and "bealge_play_a53" for the A53 cluster in the AM6254.

@jadonk I have updated the board identifier, files and directories to beagle_bbai64_r5.

should this still be in draft?

should this still be in draft?

Setting to ready for review.

I'm tired of this.
Did you at least try to compile this?
# west build -b beagle_bbai64_r5 samples/hello_world -p

dts/arm/ti/j721e.dtsi:10:10: fatal error: zephyr/dt-bindings/interrupt-controller/ti-vim.h: No such file or directory
   10 | #include <zephyr/dt-bindings/interrupt-controller/ti-vim.h>

I honestly feel you are wasting mine and maintainers time here. I'm going to remove myself from this PR.

Yes I compiled and tested.
I apologize, but this PR depends on #60856 and #61020 which is mentioned in https://github.com/zephyrproject-rtos/zephyr/pull/59191#issuecomment-1665067686.


README should be updated

The README references the now non-existent mattata-ai library.

AI (native Cleverbot implementation, which utilises my mattata-ai library).

I will probably be adding AI back again, but 100% disabled by default, for people who want AI on their clone


Earth Defense Force 5: Stutter with vsync enabled

Software information
Earth Defense Force 5
System information

GPU: RX 5700XT
Driver: Mesa 21.1.1
Wine version:  Proton experimental-6.3.-20210625
DXVK version: 1.9

Apitrace file(s)

https://drive.google.com/file/d/1ZbXVJJwd1I_jNG8ya8WneEWV_qYQdGI3/view?usp=sharing

Log files

d3d9.log: EDF5_d3d9.log
d3d11.log: EDF5_d3d11.log
dxgi.log: EDF5_dxgi.log

Transferring over from https://github.com/doitsujin/dxvk/pull/2127, as described there the game shows heavy stuttering while vsync is enabled. Couldn't get the game to load into a mission while running apitrace but since the issue is already visible on the main menu I hope that is enough.

Game bug, it does indeed toggle vsync on and off between presents, which unfortunately is a high-overhead operation because we have to recreate the Vulkan swap chain. I cannot reproduce the problem on my system, but your trace
and d3d11.log prove it.
Does dxgi.syncInterval = 1 fix the problem for you? #2127 switches it off unconditionally but I'd rather turn it on by default since a) this is what the game clearly intends to do, and b) turning it off would cause horrendous tearing on 60 Hz displays.

Yes, working just fine with those options :+1: (only tested on sway though)

I don't thing Wayland supports FIFO_RELAXED, can you give it a quick test on X11?
Feel free to update your PR afterwards with those options.

I don't really use Xorg anymore so I'm not sure if it's even set up correctly, but it seems fine on Plasma.

Thanks, merged new PR.


Changed concatenation of strings to f-strings

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[x] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

Thanks for looking at this. However, in general we don't accept these sorts of style PRs, as they're a bit noisy. In this case, it doesn' change the performance or correctness of anything, and isn't thorough (there are other concatenations that were not addressed).


pull request for e2e test at 11/10/2016 19:26:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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.


Windows version - bad example

The windows version of hello-world displays:
To try something more ambitious, you can run a Windows Server container with:
 PS C:\> docker run -it mcr.microsoft.com/windows/servercore powershell

The suggested example doesn't work, as servercore does not supply a latest tag.
I suggest it be modified to read:
docker run -it mcr.microsoft.com/windows/servercore:ltsc2019 powershell

see PR #85 for fix

Fixed by https://github.com/docker-library/hello-world/pull/85


Project Addition[Tuav Fire detection]

Pull Request for DL-Simplified 💡
Issue Title : Tuav Fire Detection using DL

Info about the related issue (Aim of the project) :
Name: Jahnvi sahni
GitHub ID: https://github.com/jahnvisahni31
Email ID<EMAIL_ADDRESS>Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a JWOC 2022 participant it's, JWOC Participant) GSSOC'24 Participant

Closes: #516
Describe the add-ons or changes you've made 📃
I have added the entire code in the form of a Jupyter Notebook (.ipynb file) along with the dataset, images, and README.md file. The Jupyter Notebook contains the implementation of the TUAV Fire Detection project, including data preparation, feature extraction, model training, evaluation, and documentation. Additionally, the dataset required for the project is included, along with relevant images used in the project. The README.md file provides an overview of the project, installation instructions, usage guidelines, and other relevant information for users and contributors.
Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested? ⚙
by the given accuracy
Describe how have you verified the changes made
Checklist: ☑

[x] My code follows the guidelines of this project.
[ x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[ x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

done i have make changes
please check
@abhisheks008


Using COUNT in Select

SqlKata: v.1.1.7
Environment: Asp.Net Core 3.1
I cannot figure out if there is any way to write a general query (Not Raw) with count.
My example:
var query = new Query("core_user_groups as ug")
    .Select(new[] { "ug.name", "count(u.id) as user_count" })
    .LeftJoin("core_user_groups_members as ugm", "ug.id", "ugm.user_group_id")
    .LeftJoin("core_users as u", "ugm.user_id", "u.id")
    .GroupBy(new [] { "ug.name" });

Gives me the following result:
SELECT
  [ug].[name],
  [count(u].[id)] AS [user_count]
FROM
  [core_user_groups] AS [ug]
  LEFT JOIN [core_user_groups_members] AS [ugm] ON [ug].[id] = [ugm].[user_group_id]
  LEFT JOIN [core_users] AS [u] ON [ugm].[user_id] = [u].[id]
GROUP BY
  [ug].[name]

I saw an example in the documentation where there was SelectRaw used. As I understand in this case I have to write two separate queries (SelectRaw) for SQL and Postgres databases.
The question is is there any way to use most of the agregation functions without need to use SelectRaw?
For example something like this:
var query = new Query("core_user_groups as ug")
    .Select(new[] { "ug.name" })
    .SelectCount("u.id as user_count") // .SelectAvg(), .SelectMax(), etc..
    .LeftJoin("core_user_groups_members as ugm", "ug.id", "ugm.user_group_id")
    .LeftJoin("core_users as u", "ugm.user_id", "u.id")
    .GroupBy(new [] { "ug.name" });

Or maybe there is already a solution which is not documented yet.
Thanks for the wonderful project guys.

As I understand that you are targeting both Sql Server and Postgres,
the short answer is no, currently there is no other way to achieve this, you have to use the SelectRaw in this case.
and AFAK there is no difference in the syntax between Postgres and SqlServer except for the keyword identifiers [] for SqlServer and the quotes for Postgres "",
using the brackets will automatically translate to quotes if you are using Postgres even in Raw expressions.

Postgres Example on PlayGround
SqlServer Example on PlayGround

Thanks for the answer. I am probably going to write my helper extensions myself. So I can add another db compatibility if needed. There also other extensions I need to write eg. CASE, COALESCE, IIF, ISNULL, CONCAT, DATEDIFF, DATEADD, DATEPART. I am using strong type sintax in my all queries within NHibernate.
Please feel free to close the ticket. Thanks for the great project.

My query with count looks like this:
var dep = Db.CreateSqlAlias<Department>("dep");
var adr = Db.CreateSqlAlias<Address>("adr");
var staff = Db.CreateSqlAlias<Staff>("staff");
var bean = BeanAliasWithBaseColumns<DepartmentVm, Department>(dep)
	.WithSelect(x => x.Name, dep.Col(x => x.Name))
	.WithSelect(x => x.Description, dep.Col(x => x.Description))
	.WithSelect(x => x.AddressId, adr.Col(x => x.Id))
	.WithSelect(x => x.AddressName, adr.Col(x => x.AddressLine1))
	.WithCount(x => x.MemberNumber, staff.Col(x => x.Id));

var rootQuery = Db.Query(dep)
	.Select(bean)
	.GroupBy(bean)
	.LeftJoin(adr.TableNameWithAlias, dep.Col(x => x.Address), adr.Col(x => x.Id))
	.LeftJoin(staff.TableNameWithAlias, staff.Col(x => x.Department), dep.Col(x => x.Id))
	.Where(dep.Col(x => x.IsDeleted), false)
	.Where(staff.Col(x => x.IsDeleted), false);


Add cocoapods-embed-flutter

Modify plugins.json to add cocoapods-embed-flutter and solve #140.

Thanks


Add package level README.md for core-httpclient-impl

Summary

Add package level README.md for core-httpclient-impl
Fix bug where invalid input was not defaulted as the log indicates.

Pull Request Test Coverage Report for Build 1062

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 89.442%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-httpclient-impl/src/main/java/com/optimizely/ab/config/HttpProjectConfigManager.java
0
4
0.0%

Totals

Change from base Build 1060:
-0.1%

Covered Lines:
3287

Relevant Lines:
3675

💛  - Coveralls


Xcode 11.3.1 No such module 'Firebase'

After Xcode updated, app can't be run both iOS simulator and real device with the message No such module 'Firebase'
I tried pod reinstall and pod update, but no luck.
How can I fix this?

Hi @Daibaku9999
for what I can see the issue is related to a FlutterFire plugin,
please open the issue in the dedicated github.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
thank you


Collider::round_triangle doesn't have round edges no matter the border_radius

Hello,
I was attempting to use .insert(Collider::round_triangle(a, b, c, border_radius) in my project, but no value I provided to border_radius would cause the edges to be rounded.
My exact call was
...
.insert(Collider::round_triangle(
    Vec2::new(-128., 32.),
    Vec2::new(-128., -32.),
    Vec2::new(128., 0.),
    1000.0,
...

I ended up using Collider::round_convex_hull(...) for now, but figured I'd make a bug ticket in the meantime. I can provide further detail of necessary. Thanks!

I think roundness just isn't implemented for the debug renderer in the case of triangle/trimesh/height field:
/*
 * Round shapes.
 */
TypedShape::RoundCuboid(s) => {
    let vtx = s.to_polyline(self.style.border_subdivisions);
    backend.draw_line_strip(object, &vtx, pos, &Vector::repeat(1.0), color, true)
}
TypedShape::RoundTriangle(s) => {
    // TODO: take roundness into account.
    self.render_shape(object, backend, &s.inner_shape, pos, color)
}
// TypedShape::RoundTriMesh(s) => self.render_shape(backend, &s.inner_shape, pos, color),
// TypedShape::RoundHeightField(s) => {
//     self.render_shape(backend, &s.inner_shape, pos, color)
// }
TypedShape::RoundConvexPolygon(s) => {
    let vtx = s.to_polyline(self.style.border_subdivisions);
    backend.draw_line_strip(object, &vtx, pos, &Vector::repeat(1.0), color, true)
}

Thanks @Aceeri! I figured as much. If you don't mind, where did you find this snippet of code? I can't seem to track it down. I'd like to see about fixing it if possible.

@akappel https://github.com/dimforge/rapier/blob/b00324756dd923afcc6e0dbf401ffa361debd470/src/pipeline/debug_render_pipeline/debug_render_pipeline.rs#L386


How to go about having multiple planets of the same generation (Constant Companion) with different settings?

Title should be self explanatory. Changing the shape or shading seed on one planet changes all planets that use the same generation settings. Would it be easy to have multiple Constant Companion planets with different settings?
Duplicating the celestial body settings still seems to affect the same material for the planet and I'm not quite sure how this works. Thanks!

CelestialBodyGenerator uses scriptable objects to define planets' settings. You'd better be off creating (or duplicating) a new planet settings asset and changing settings there.


Add ability to execute some func in poller context

1. Are you opening this pull request for bug-fixs, optimizations or new feature?
Feature
2. Please describe how these code changes achieve your intention.
Add ability to execute some func in poller context
This ability required if you want to use Conn.GetContext in events not
initiated by poller (for example: separated goroutine wants to update
context).
If you have any contacts with conntection context inside poller funcs
(codec, or any of EventHandler callbacks) you cannot use that context
outside of poller context anymore and vise versa - if you use context
outside you cannot use it inside that events.
Now you can offload all work with context to poller. When you need
read something from context - you should call AsyncExecute where you
have synchronized access to conn context.
3. Please link to the relevant issues (if any).
#188
4. Which documentation changes (if any) need to be made/updated because of this PR?
AsyncExecute wake poller and execute provided callback into it.
Provided func also return bytes which will be written to conn and/or gnet.Action that will change connection or server state.

Please don't force-push the commit to resolve comments, which leaves me no history to track down.

Looks like I cannot detect closed connection on a Windows platform (loopCloseConn set conn as expired but not set it to null).
Here I have decision to make:

Have a different behavior on windows and unix. If so - I cannot write test properly.
Change windows conn behavior and call releaseTCP in loopCloseConn as it implemented in eventloop_unix. This may cause unexpected changes in windows implementation behavior.
Remove condition at all, but it have some troubles in its write part which will crash if conn is closed on unix but not on windows.
Leave condition but remove the testcase. Declare that detail (ability to check if conn is opened) as undefined behavior and do not test it. But that decrease coverage.

I have been a little bit more thinking about API and reveal that there is no any declarations about immediate connection closing when I return gnet.Close. So I think test case that fix that behavior is not correct. So I just removed that test.

I think its will be better to close this PR for now :) I will maintain AsyncExecute for my own needs while I still need that feature, but there is no need to bother CI when I commit something to that branch.


build: use fine-grained token and semantic release replace plugin to update README

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


cluster random images into folders

Hi
I have set of random images in a folder. how can i cluster similar images into specific folder. I tried using LBP approach but it was not solving the problem. Using facenet pls suggest how can i achieve the same.
Thanks
vij

The "chinese whispers" algorithm works very well.
https://github.com/zhly0/facenet-face-cluster-chinese-whispers-
0.97733 value as threshold (https://github.com/davidsandberg/facenet/wiki/Validate-on-LFW)

I gone thru the link.  it seems the prerequisite for chinese whispers  is images which should be available in folders where every folder name will be taken as class. In my case i have all unorganized images in root folder only. i do not have sub folders. pls suggest

@namghiwook  great solution!

currently i am using LBP approach where all similar images will be grouped into specific folder but the accuracy is hardly 70%

@vijaysagi
You can put all images in "album/all/" folder, and set "album" folder as --input value.
change code like below in facenet_face_cluster.py
// cluster_dir = dest_dir
cluster_dir = dest_dir + "_" + str(idx)
Try it! Good luck!

Thats awesome solution. thank you so much

@namghiwook the threshold(0.9733) you mentioned is cosion similarity or euclidean similarity? thx.


Integration tests

In order to have real integration test, we need to

[ ] Select some entities to put into local index
[ ] Build runtime index to compare the outputs
[ ] Create target outputs based on the index

unimportant issue, leaving the issue open for possible further developments.


avoid potential php warning

If markup is invalid, this will trigger a warning. Adding a @ suppress the error.

see https://github.com/silverstripe/silverstripe-framework/pull/6623#issuecomment-280038855
tl;dr error suppression is not an acceptable remedy to this issue

well, I agree, but to a certain extent : I'm not even sure how it was possible to generate duplicated ids within tinymce in the first place. How could you make sure that the client will generate valid markup that is not going to trigger a warning?
but then what I'll do is probably simply run some checks on my page before saving to ensure html is correct.


update migration api azure container and queue

Category:  Content Fix
Description:  Added note regarding required endpoints if your tenant is hosted in GCC

Thanks Andrew


FR: customizable yank highlight duration

Thx for this, been wanting for a more stable yank highlight for a while :)
Would it be possible to customize the duration of the yank highlight?

Yes, of course. I was thinking about adding some options.
Is there anything else you think would be helpful to make customizable apart from the duration of the animation? I had three things on my list:

option to change highlight duration
option to change the colour of highlight
option to supress in visual mode (cause you already see the selection)

duration of course makes sense
not sure about color – by using one of the built-in Obsidian CSS variables, the highlight inherits the color set by the theme, which already makes sense for me.
no highlight in visual would be useful, but highlighting yanks from visual mode is also how nvim does it, and you could argue to keep it consistent with vim.

Rather than providing niche customization options, something which I'd like to have more highlighting operations, such as highlighting paste (done by nvim-yanky) or highlighting undos (done by this plugin)

Rather than providing niche customization options, something which I'd like to have more highlighting operations, such as highlighting paste (done by nvim-yanky) or highlighting undos (done by this plugin)

These are some good ideas (and plugins). Thank you!
I'll add the duration option first and then try to incorporate something from the plugins you shared.

I've added the highlight duration option on this pull request. Amazing plugin btw.


Python bindings of verbose callbacks + integrate in solvers

In GitLab by @cmastalli on Jul 15, 2019, 08:51
null

In GitLab by @cmastalli on Jul 28, 2019, 22:42
assigned to @cmastalli

In GitLab by @cmastalli on Aug 6, 2019, 23:17
mentioned in merge request !189

In GitLab by @cmastalli on Aug 6, 2019, 23:18
closed


Tensorboard

Begin logging with TensorBoard.
Starting with cost.

Well I like it but I just discovered that something about the latest TensorFlow(which I have to use in order to use "FileWriter" in your code) slows down my compute speed by a factor of 5. What used to take about 0.6 seconds per count is now 3+ seconds per count. Anyone know what the cause of this is? I verified it's not your patch causing this so no worries there. I'm going to try to find a version that still has the FileWriter attribute but doesn't slow my machine down like that. It's already going to take 3 weeks to train this set so 15+ weeks isn't gonna work.

Well I like it but I just discovered that something about the latest TensorFlow(which I have to use in order to use "FileWriter" in your code) slows down my compute speed by a factor of 5. What used to take about 0.6 seconds per count is now 3+ seconds per count. Anyone know what the cause of this is? I verified it's not your patch causing this so no worries there. I'm going to try to find a version that still has the FileWriter attribute but doesn't slow my machine down like that. It's already going to take 3 weeks to train this set so 15+ weeks isn't gonna work.

@TheOncomingStorm I just tried moving the FileWriter call outside the batch loop so that it was called on each epoch. No noticeable difference from my perspective. How did you ascertain that this is the cause of slowing down your learning?

@TheOncomingStorm I just tried moving the FileWriter call outside the batch loop so that it was called on each epoch. No noticeable difference from my perspective. How did you ascertain that this is the cause of slowing down your learning?

I discovered it because the original word-rnn code run under TF 0.12 without your changes runs slow as well. I've no idea why this started but a 5x slowdown seems extreme. I just recompiled TF 0.11 and with the code(again, minus your changes) is 5x faster than 0.12.
I am using the pre-compiled version of 0.12 so I'm gonna compile it really quick and see if that is the issue but I'm pretty sure the 0.11 version on that machine was pre-compiled so I have no idea what the cause is yet. I'll report back in a bit.

I discovered it because the original word-rnn code run under TF 0.12 without your changes runs slow as well. I've no idea why this started but a 5x slowdown seems extreme. I just recompiled TF 0.11 and with the code(again, minus your changes) is 5x faster than 0.12.
I am using the pre-compiled version of 0.12 so I'm gonna compile it really quick and see if that is the issue but I'm pretty sure the 0.11 version on that machine was pre-compiled so I have no idea what the cause is yet. I'll report back in a bit.

Well thanks to a couple changes with zlib(they updated last night) and a couple other things, I'll be waiting till everyone gets the code stabilized because it won't even configure right now.

Well thanks to a couple changes with zlib(they updated last night) and a couple other things, I'll be waiting till everyone gets the code stabilized because it won't even configure right now.

Never mind. I thought I had upgraded to the GPU version but apparently it went back to the CPU-only version. I'm back to my normal speed now, and I can restart per your changes. Thanks a ton.

No worries. Glad it works for you. The code isn't perfectly clean and is a bit of a spaghetti hack. I'm looking at a few further improvements when I get some time away from reading papers.

@normanheckscher @TheOncomingStorm Thanks for discussion and wonderful code. May I add you as developers of this repos?

Sure, I'll be glad to test and report what I can.


Not able to build the binary from main.go

Its there a reason why some methods used in main.go are defined in another file call flags.go?
When trying to generate the binary via the go build I have the following error:
# command-line-arguments
./main.go:14: undefined: setCli

If I defined the methods from flags.go into the main.go, then I do not have a problem anymore.
Regards,
Enrique Encalada

the root of aviator is the main package and both main.go and flags.go are related to the main package. So if you want to build aviator with go build you need to build the whole package. $ go build main.go is not enough, as it uses function from other files, like in this case flags.go.
regards


In initial wizard ask about enabling IMAP push

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
8.01b
Problem you are trying to solve
The feature to enable IMAP push was buried and I think it should be default, or if not the "wizard" when adding a new account should ask if this should be enabled
Suggested solution
enable a check box in the initial wizard to enable IMPA push.  Should be in the screen where the interval is set.
Screenshots / Drawings / Technical details
No response

Maybe related?

#8462

I didn't migrate.  Did a fresh install


add option for disabling restriction of dotfiles

Hi there,
I've been trying to serve files in a dotfiles directory, but all the files get intercepted (which is understandable) by gophernicus. Could one add an option to disable blocking of dotfiles?
Of course, this would add more code. Your code right now just checks if the file name has any directories matching '..*' (grep regex), and adding an option would involve making sure that a path does not resolve outside the directory in which the files are served. This change would be complicated.
However, in the meantime I'm trying a workaround.
Thanks,
randomuser

Yes, I think that would be possible.
I don't think it would be difficult to do this; we can just block anything with ../ (i.e. traversing into the parent directory) always, while allowing ..abcdef.

Sounds good.


Array.tridx is slow

matrixatorFree, matrixator, and reorder can be slow because Array.tridx is slow. The slowness is most pronounced for tensors with many indices (e.g. 6 indices or more). I would like to improve the performance by implementing and making use of a tensor transpose function in c, which I think should actually be added to the hmatrix package since it's a useful building block for any tensor library. Below are my plans. Please let me know if you think I should make any changes.
Add to LinearAlgebra.Element class:
reorderV :: Vector CInt -> Vector CInt -> Vector a -> Vector a

Export a renamed version from LinearAlgebra.Devel:
-- | Transpose an array with dimensions @dims@ by making a copy using<EMAIL_ADDRESS>For example,
--   @(reorderVector strides dims v) ! ((i * dims ! 1 + j) * dims ! 2 + k) == v ! (i * strides ! 0 + j * strides ! 1 + k * strides ! 2)@
--   Note: the stride lengths are not checked! For example, it's assumed that the above equation does not go out of bounds if @0 <= i < dims ! 0@, @0 <= j < dims ! 1@, and @0 <= k < dims<EMAIL_ADDRESS>reorderVector :: Vector CInt -- ^ @strides@: array strides
              -> Vector CInt -- ^ @dims@: array dimensions of original array @v@
              -> Vector a    -- ^ @v@: flattened input array
              -> Vector a    -- ^ @v'@: flattened output array
reorderVector = reorderV

This will require foreign imports. For example:
foreign import ccall unsafe "reorderVF" c_reorderVF :: CV CInt (CV CInt (CV Float  (CV Float (IO CInt))))

Yes, this is an excellent idea. Please do it!


platform/desktop: Fix potential null pointer dereference in getIpAddress

According to getifaddrs(3):

The ifa_addr field points to a structure containing the interface address.  (The sa_family subfield should be
consulted to determine the format of the address structure.)  This field may contain a null pointer.

I can reproduce this with Tailscale's TUN on Fedora 40 (rawhide).

:thinking: We should probably only include PHYSICAL interfaces for this?

I think I found the culprit

Good catch ！


fix: test reliability patches

This PR fixes

flakiness in testwriter
flakiness in testbyzantineprevoteequivocation

@melekes - I'd like to merge this branch, and then open another torture branch and run the tests a few thousand times.  But I think we are in good shape.

NOTES FOR REVIEWERS
Some of the fixes here involved small changes to the tolerances of tests in situations where the code may behave in a slightly variable way without malfunctioning.  I bet that is the key item for review.
I consider this branch to be mergable now, and I suppose what I'll do is make another one where the other tests I identified as having issues are run 100 times.  That was totally key to fixing TestTransportMultiplexAcceptNonBlocking because it got me the data I needed to understand the problem.

PR checklist

[x] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

TestByzantinePrevoteEquivocation and TestTransportMultiplexAcceptNonBlocking are still failing.
--- FAIL: TestByzantinePrevoteEquivocation (30.08s)
    byzantine_test.go:292: Evidence from each validator: [<nil> <nil> <nil> <nil>]
    byzantine_test.go:293: Timed out waiting for validators to commit evidence

--- FAIL: TestTransportMultiplexAcceptNonBlocking (0.04s)
    transport_test.go:360: have {{9 11 0} dc28ea6b630e74a67256457f901d9d183da919d7 <IP_ADDRESS>:38953 testing 1.2.3-rc0-deadbeef 01 slow_peer {on <IP_ADDRESS>:44371}}, want {{9 11 0} 6[123](https://github.com/cometbft/cometbft/actions/runs/7390672952/job/20106075991?pr=1954#step:5:124)f7e124d306734abc6a4d438a5a734f322dcc <IP_ADDRESS>:37183 testing 1.2.3-rc0-deadbeef 01 fastnode {on <IP_ADDRESS>:35069}}

Working on it sir :D

@melekes probably obvious, but I'm using this branch as a testing ground for all of the tests at once since we need to run them many times to call em flaky or not.

PS: TestTransportMultiplexAcceptNonBlocking is the hardest one imo.
It is testing that a slow peer doesn't block a fast peer.

#1948 is still failing at 35 seconds.  Do you think we should check out the evidence submission code, or bump to 40 seconds?
@melekes

I'm going to bump to 40.... but i think we could have a code or test issue on that one

oh darn it and I am comitting to the wrong branch.  But making actual progress, so at least the commits will be useful...

testbyzantineprevoteequivocation is very challenging.

tfw a seven year old go lib solves a problem:
https://github.com/phayes/freeport

When this passes, I'll cherry pick changes or check out files into the individual PRs -- or if preferred, we can merge this as "test reliability patches"

Jobs are currently just staying queued, so I'll take a break from this for today :)
See ya tomorrow :)

@melekes - for merge conflict purposes, I think this one should be merged before #1906 if that is alright with ya.

@melekes merged your branch here to see if it would stop some tests from failing.
fairly sure that'll be the case.
Goal: make this branch green after 40-1000x runs, then either merge the whole thing or break it into individual PR's at your preference.

the "try delaying to not block ports" ensures we test on the default ports.  It might be better to randomize as we do elsewhere though.

This branch is no longer mergeable and I should break it into individual changes.


An admin user should be able to advance the workflow state of any work in any workflow

 Issue by straleyb
Monday Nov 07, 2016 at 16:52 GMT
Originally opened as https://github.com/projecthydra/sufia/issues/2860

As an admin user, I should be able to update a work's state even if I haven't explicitly been granted a role in that workflow.

 Comment by mjgiarlo
Monday Dec 05, 2016 at 17:51 GMT

@vantuyls @hannahfrost I think we need to back this feature with more detail on when and why this is needed. cc: @jcoyne
Bumping to phase 2 for now.

 Comment by mjgiarlo
Monday Dec 05, 2016 at 17:55 GMT

If we do decide to work on this, it may be related to the following (as yet unwritten) story: "Admins should be able to edit all repository objects regardless of stored ACLs" (related to https://github.com/projecthydra/sufia/issues/2946)

 Comment by vantuyls
Monday Dec 05, 2016 at 18:22 GMT

This is related to the idea that the Admin has complete control over repository functionality. Per our discussion on Slack this morning, i'm not sure that's necessarily a fair assumption and this may be more of a repository by repository role management issue. If role management allows one to set up an admin to be able to touch everything in the repository, then we're good. Are role-related issues labelled in any way?

 Comment by mjgiarlo
Monday Dec 05, 2016 at 18:33 GMT

@vantuyls :speech_balloon:

Are role-related issues labelled in any way?

No. Not yet anyway.

@vantuyls @hannahfrost How high of a priority is this?

i think if, for example, a reviewer is the only one who can advance something in a workflow we would have real problems. it is not uncommon for us to have urgency for deposit that requires a person who isn't the "normal" one doing the review to do that work. This is why i like the idea of an admin for an admin set being able to take action at all workflow steps.
That said, if my use case is too special snowflake, if there is another way to specify this behavior for the admin set or the workflow, i'm okay with that, too.

i like the idea of an admin for an admin set being able to take action at all workflow steps.

I'm with @vantuyls. That is entirely consistent with the permissions breakdown I spec'ed for Hyku. And I feel implementing this is high priority, but I also don't know what other work this requirement is up against, the level of effort, and other constraints.

@vantuyls @hannahfrost @jcoyne This is already done for the following users:

The admin user that created the Admin Set
Any user listed as a Manager for the Admin Set

This is not done for any other users that may be administrators. Does this need to be available to all administrative users, or is it acceptable for now to expect this to be controlled via the Admin Set Managers implementation we already have?

@mjgiarlo I think completing this work is a priority, so that an Admin could participate in the workflow by default, and not need to take on a different role.

@hannahfrost OK. @jcoyne might a lightweight way to handle this be:

Add the 'admin' group to the managers of every admin set when it's created
Prevent the 'admin' group from being removed from this list (or hide it from being shown)

?

Design comments on the above, @ggeisler, particularly the second bullet point?

@mjgiarlo The above makes sense to me. I'd lean towards showing the Admin group, just so the Admins' privileges are explicit, but agree the Admin group should not be removeable.
If it seems like a mockup would help, feel free to add a design needed label.

Note that this ticket may require an upgrade tool (rake task) to automatically add the admin group to all previously created admin sets.

Discussed on May 17th with @jcoyne and @carrickr. We were wondering whether granting repo admins "god status" with workflows (allowing them to touch every entity in every state in every workflow) would make it difficult or impossible for them to make sense of, e.g., the Review Submissions view, if a user is both a repo admin and an Admin Set manager for one Admin Set. How do I find my Admin Set materials when I see everything in the repository? For that reason, we were thinking this might be a good issue to bounce back into Design Needed. One idea was we could add a widget to the Review Submissions view (and perhaps others?) that allows a repo admin to say "show me everything, not just stuff I have an explicit role in."
Thoughts, @hannahfrost @vantuyls @ggeisler?

@mjgiarlo I'd be happy to revisit this with your comments above, which make sense to me on first glance, as input. Please work with @hannahfrost to prioritize it with other design needed tickets so I get to it in the right order.

Thanks, @ggeisler! @hannahfrost do you mind taking a gander at the Design Needed column in Waffle and shuffling things into priority order? LMK if I can help.

@mjgiarlo i like the suggestion of "show me everything". would be intersted to see the design mockups.

This is not much of a mockup, but it seems like maybe all we need is to add a checkbox that gives the admin the ability to say she wants to see everything under review, not just what is shown in the table by default.
So, by default the table just shows works under review for admin sets the user is manager or otherwise a reviewer for (current behavior, I think?).
If the user is a repository administrator only, show the checkbox added in the mockup below. Checking the box updates the table with all works in the repo under review. Unchecking the boxes updates to remove those not part of the user's admin sets.

works for me!

@ggeisler @mjgiarlo I think we are ready to move this into the Ready column. Agreed?

@hannahfrost Given how much discussion there's been, I suspect we should close this issue and write up two new ones: one for adding the 'admin' group to every AS's managers list, and another for the "Show all works under review" checkbox that @ggeisler designer. I'll do that and mark both as ready.

@hannahfrost @ggeisler @jcoyne @vantuyls Decomposed into #1142 and #1143. Thanks for helping to make this work actionable!
Closing.


Geotag-Support for .HEIC files

This method currently seems to be unable to gather geotags from .HEIC files, although Windows can show the geotag in the properties window and the Windows photo app is able to show the location as well. Are they using a different API?

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

ID: 399f1d5b-21c8-b160-6dc8-688e398b385e
Version Independent ID: c57be2e4-c3bf-0f2d-48e2-76cd17df8d70
Content: GeotagHelper.GetGeotagAsync(IStorageFile) Method (Windows.Storage.FileProperties) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.storage.fileproperties.geotaghelper.yml&version=GBlive&_a=contents
Product: uwp
Git Login: mcleanbyron
Microsoft Alias: mcleans

Thanks for reaching out with your feedback. Comments left here are meant for documentation feedback, and unfortunately we cannot provide technical support. For community assistance with development questions I recommend that you ask on our forums or StackOverflow. Otherwise, please see the developer support page for your support options.


Incorrect display of Frege icon in 2020.2: it's a dot instead of the icon

it's a problem only in the old versions of IDEA. So it's not very important.


Write an FAQ for technical and non-technical questions

@pradeepto is the priority still high?
Also, could you explain more on what sort of questions do we want to be a part of this?

@pradeepto Can we close this?

I think this it still valid.

Also, could you explain more on what sort of questions do we want to be a part of this?

Questions like:

How is Kedge different from Helm
How it is different from docker-compose (now when you can deploy it directly do Kubernetes)
Why I would use Kedge over normal Kubernetes definitions.


PKI CI workflow is failing

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'createAccountController': Unsatisfied dependency expressed through field 'autoLoginService': No qualifying bean of type 'skills.auth.AutoLoginService' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}

PR: https://github.com/NationalSecurityAgency/skills-service/pull/2357


dmidecode output unused

I've been hitting #315 recently and after looking at the code a little bit, it seems that Platform.model instance attribute is actually never used. Both LinuxTarget and AndroidTarget define their own model property (read from device tree or using adb). If I did not miss anything, that would mean that the model attribute of the platform is dead code, which happens to be harmful in the current situation.
Could that model attribute be either removed or turned into a property in Platform ? This way, dmidecode would only be called when someone looks at platform.model and not by default upon target setup.

I believe https://github.com/ARM-software/devlib/pull/447 should address this -- it moves the model code from LinuxTarget and AndroidTarget into Platform._set_model_from_target() and uses that in preference to the dmidecode method (which is still used as a fall-back). The Target property now just returns the underlying Platform attribute (note: it still has to be an attribute in the platform because Platform does not have direct access to the target outside of upadate_from_target() as it is itself an attribute of Target, and we don't want a cycle).

That should do the trick as ARM/ARM64 should have that device tree entry, thanks :)


Upgrade

Is this version (0.2.5) compatible with rails 5.0.2 or ruby 2.4?

Are you getting an error?

yes I am. I've got the following error after upgrading to the newest version of ruby and rails:
Unauthorized(401) instead of unprocessable_entity(422) for authentication

The first step to debugging this is to clone this repo and run the tests against the target ruby version. I'll be unable to do this for at least a week or two.

Fixed Thanks 😘
The problem was not related to the hawk-ruby


Downloading bytes to variable in memory, not file

From reading the docs, fuel allows for downloading bytes to file using the Fuel.download(*url*). Is there a way to download the bytes into a variable in memory as opposed to a file? Currently I've been using Java IO inputstream, but it would be nice to use something built into fuel instead.
For reference, here is how I am doing it now:

However, I want to be able to do something like this, but to store in the contents in a variable var bytes = fuel.download(..):

Do you think you can try to use the .streamDestination instead? And use ByteArrayInputStream to convert into the data in the memory
Fuel.download("")
    .streamDestination { }
	.response()


Swap cc / cc-on with end-call on the Deck Mini

Currently, cc (on/off) isn't working (for me at least, it's also not loading the button icon). But in any case, having a dedicated button to end a call makes more sense to me.
This change will swap the cc / cc-on with end-call. - see issue #15

And before I forget - great project, thanks a ton! :o)


#530: Translated japanese documents to english

Thank you for your PR!
Could you edit index.rst and add introduction.en to index?

Added introduction.en to index.rst

I'm sorry that you still had to edit it. My bad, I didn't noticed those.

@pieceofeden
Don't worry! :smile:
I know translation this document is challenging.
I hope that if this PR is merged, it will be read and improved by native English and get better and better. So first revision doesn't have to be perfect.
On the other hand, I want to do what I can do to improve quality.

@fukatani Can I leave all reviewing to you? thx!

@pieceofeden
This is all.
After addressing my comments, could you squash to one or two commit and for push your branch?

How can i squash commits ?? I've squashed commits yet

$ git rebase -i HEAD^31

Then, text editor will be opened,
Please edit as follows.

If you want to squash 30 commit, you need to edit 30 lines.
Oldest your commit should not be squash, so first line starts with pick.
Edit other lines and make starts with s or squash.
This task is disruptive, so if you worried about misoperation, you had better make new branch from current branch before squashing and checkout to translate-Japanese-documents-to-English-#530 again.
If you mistake, you can reset to backup branch.
$ git push origin HEAD -f

Thank You !!


feat!: add utf8 support

That solves #14.
For utf8 support was used library from luarocks.org: luautf8. It contains several string methods and utf8 specific methods implemented by the lua specification.
Thanks to this, the code has not more complexity and was simplified from col indexing to offset indexing. With it methods logic was simplified. The reason why I refactored some code was byte width in utf8. In first particular range utf8 contains one byte, in second particular range utf8 contains two bytes and so it goes on. In this case indexing by col more complex than indexing by offset.
Also I changed in README.md in installation section, adding luarock dependency. packer.nvim have native rocks installation, but for lazy.nvim need add nvim_rocks dependency that installs luarock dependency.

Hi,
thanks for the effort of finding a solution here. However, I hesitate to merge this for two reasons:

I am somewhat afraid that supporting these edge cases might in turn break some other edge cases as a side effect, so I'd like to add some tests before merging. (see #25)
I don't know how I feel about adding two dependencies to cover an edge case, since this would mean that a lot of people who do not need this dedicated utf8 support would still need to install the dependencies, which feels somewhat contradictory to the otherwise lightweight nature of this plugin. So I'd at least make this these dependencies somehow optional.

I understand you.

For the first reason, I will wait before adding tests and I will use my fork at the same time.
For second reason, I think it's possible to add the other branch named utf8-support. That way people using default lightweight spider won't get update about UTF-8 because they don't need it. And if peoples want to add UTF-8 support then they can switch branch and add some dependencies. I don't know about other best solutions because doubling code with two different situations is not good for me.

I think it's possible to add the other branch named utf8-support. That way people using default lightweight spider won't get update about UTF-8 because they don't need it. And if peoples want to add UTF-8 support then they can switch branch and add some dependencies. I don't know about other best solutions because doubling code with two different situations is not good for me.

Hmm, maintaining two branches also does not look ideal to me. Ideally, there is some niche nvim API which deals with strings which might help. Otherwise, a solution might be to just take out parts of the utf8 library which are relevant for this plugin? Not sure. 🤔

All right. Today I spent some time looking for find other "native" solutions. The results are not very encouraging. In Vim and Neovim regexs don't contain special "unicode classes" that starting with \p{C} and instead of C letter we can insert Lu or Ll (Uppercase_Letter or Lowercase_Letter). But it's not necessary, because some external tools can automatically check UTF-8 with basic like [:upper:] or similar sets. This problem is related to the fact that Vim or Lua regexes are unique. It has also been discussed here.
What's left? There are two ways that I found:

to figure out how to merge two solutions: basic and utf8support. Here are some ways to merge: merge code and check accessibility of lua plugin luautf8 using the pcall method or add another branch, or other ways which I didn't find but might be more effective.
use "built-in" support via shell command grep or rg (use second command only if it exists). Also need call the pcall method to check the accessibility of the rg command and use it if it is exists, otherwise use grep. But, here you need to rewrite the regex patterns.

P.S. For the first way, I have thought that we could use metatable with needed string functions: "find", "gmatch", "reverse", "next_chat", "prev_char". And lua will call function that override the metatable if lua plugin luautf8 is present. But in this case need nicest solution with checking and picking between "offset" and "col" 🤔

Hi again!
As you see, I did update for to upstream and added 'optionality' of UTF-8 plugin. Before telling my opinion, here's changes:

this nvim plugin works same as main (but test needs);
if lua detects that lua-utf8 available, then string functions 'switches' to UTF-8 based functions;
moved from col-based computation to offset-based computation.

I'll begin from last clause:

Firstly, it's more understandable than using columns.
Secondly, UTF-8 char may contain at least one byte and "column" is incorrect for string, because any UTF-8 string may contain more bytes than characters.
No need hard thinking about adding or subtracting indices for 'right' position.

Second clause. This detection allow us to use lightweight plugin, when UTF-8 is no need and turn on if needed. As you see in code, I implemented str_func, which contains all string functions. And one simple function pcall, which detect availability of 'lua-utf8' plugin. If detected, then starts remapping table str_func.
First clause is derived from second. But, need tests, because I'm not sure, that I moved right from 'col-based' indices to 'offset-based'.
I don't see tests. Where is they? Also I don't see your issue about test.
Well, there is my opinion. I used my modification (with UTF-8) of this plugin and I don't see any errors or exceptions. What do you think about this?

Hi! Sorry for also putting this off for so long myself. Yeah, I didn't get around to add tests, partly because I maintain too many plugin (🙈), and also because there were no bug reports for any new edge cases, meaning I didn't have any reason to change the apparently stable motion mechanics.

Second clause. This detection allow us to use lightweight plugin, when UTF-8 is no need and turn on if needed. As you see in code, I implemented str_func, which contains all string functions. And one simple function pcall, which detect availability of 'lua-utf8' plugin. If detected, then starts remapping table str_func.

This is a smart solution, neat! Yeah, I think with this, we can safely merge. Thanks for the work!

Normally no big deal, but in lazy.nvim, commit messages with a ! are emphasized, so I reworded the commit message to avoid confusing users.

Oh, I missed this! Thank you for remark!
Also, please, see your refactored code. It has a problem with the table stringFuncs. At the moment, when lua detect availability of 'lua-utf8' and the cycle will stop by cause "pair function got nil, because initially the table stringFuncs is nil.

oops, you are right, fixed


OpenXstim

Title
Transcutaneous Electrical Stimulator for Spinal Cord Stimulation.
Leaders
Monzurul Alam
Collaborators
No response
Brainhack Global 2022 Event
Brainhack Australasia
Project Description
Transcutaneous electrical spinal cord stimulation, a non-invasive, reversible spinal cord neuromodulation method holds tremendous promise and hope for the people with paralysis resultant of spinal cord injury (SCI) and other neurological conditions. Yet, there are not many options of such stimulation device compared to other successful electrical stimulators such as neuromuscular electrical stimulator (NMES) and functional electrical stimulator (FES), especially for most people around the world.
The objective of this project is to design a simple, easy-to-build transcutaneous electrical stimulator (OpenXstim) to facilitate anyone with the modest technological knowledge to develop their own stimulator for the spinal cord stimulation treatment.
Link to project repository/sources
https://github.com/OpenXstim/OpenVstim
Goals for Brainhack Global
The goal is the collect different ideas and inputs during the Brainhack event to further furnish the design of OpenXstim
Good first issues

issue one: Designing an optimum constant current tropology for 10kHz biphasic stimulation.

issue two: Improving the safety features to avoid unsupervised stimulation.

Communication channels
https://join.slack.com/share/enQtNDI0MjIyNzc1Mzk3MC1mMGU1NGY0MzIyMDE1YTg2ZWU2MjkzN2I0N2RlNmY4M2JlNzgyNTFmZTRjMWVlZDA2OTkzOWVkODlmYzY2OTVi
Skills

Power Electronics: Advanced
Analogue and Digital Electronics: Advanced
C/C++: Intermediate

Onboarding documentation
No response
What will participants learn?

Electrophysiology (Neuromodulation)
Rehabilitation Engineering
Bioelectronic Medicine

Data to use
No response
Number of collaborators
1
Credit to collaborators
Acknowledgements to the published work.
Image

Type
method_development
Development status
2_releases_existing
Topic
physiology, systems_neuroscience, other
Tools
other
Programming language
C++
Modalities
other
Git skills
4_not_applicable
Anything else?
No response
Things to do after the project is submitted and ready to review.

[ ] Add a comment below the main post of your issue saying: Hi @brainhackorg/project-monitors my project is ready!
[ ] Twitter-sized summary of your project pitch.

@MonzurulAlam your project should be up on the webpage shortly

@MonzurulAlam
Your project is on the website: https://brainhack.org/global2022/projects/


Difficulty making examples work in VS2017

I've been trying to run the examples using cmake + VS2017 but haven't been having much luck, and wondered if it was something I was doing. I have Python and matplotlib installed (in the form of Miniconda)  and have been able to compile the examples by changing paths etc. in the generated VS projected. If I copy the right DLLs into the execution folder I can also get the example programs to run, but they terminate prematurely and don't display any output, which is strange.
I was able to get these examples to run on a different machine with VS2017 via the same process, but it doesn't seem to be working for me now for some reason. I just wondered if I'm missing something obvious. Any help would be greatly appreciated!

Did you try one of the  pull requests?


[Bug] Impossible to conn

Current Behavior
I've installed for the first time this app on my Unraid server but if i try to login after a couple of minutes shows "Unable to sign in. Can't connect to server"
From the log file i can see that it's struggling with the SSL somehow.
If i try to use the client from a baremetal linux it works without any issues.
Expected Behavior
I expected to be prompted with 2FA and then login.
Steps To Reproduce
No response
Environment

OS: Unraid
OS version:
CPU:
Docker version:
Device model:
Browser/OS:

Container creation
Downloaded from Unraid Community Apps
Container log
[init        ] container is starting...
[cont-env    ] loading container environment variables...
[cont-env    ] APP_NAME: loading...
[cont-env    ] APP_VERSION: loading...
[cont-env    ] DISPLAY: executing...
[cont-env    ] DISPLAY: terminated successfully.
[cont-env    ] DISPLAY: loading...
[cont-env    ] DOCKER_IMAGE_PLATFORM: loading...
[cont-env    ] DOCKER_IMAGE_VERSION: loading...
[cont-env    ] GTK2_RC_FILES: executing...
[cont-env    ] GTK2_RC_FILES: terminated successfully.
[cont-env    ] GTK2_RC_FILES: loading...
[cont-env    ] GTK_THEME: executing...
[cont-env    ] GTK_THEME: terminated successfully.
[cont-env    ] GTK_THEME: loading...
[cont-env    ] HOME: loading...
[cont-env    ] QT_STYLE_OVERRIDE: executing...
[cont-env    ] QT_STYLE_OVERRIDE: terminated successfully.
[cont-env    ] QT_STYLE_OVERRIDE: loading...
[cont-env    ] TAKE_CONFIG_OWNERSHIP: loading...
[cont-env    ] XDG_CACHE_HOME: loading...
[cont-env    ] XDG_CONFIG_HOME: loading...
[cont-env    ] XDG_DATA_HOME: loading...
[cont-env    ] XDG_RUNTIME_DIR: loading...
[cont-env    ] XDG_STATE_HOME: loading...
[cont-env    ] container environment variables initialized.
[cont-secrets] loading container secrets...
[cont-secrets] container secrets loaded.
[cont-init   ] executing container initialization scripts...
[cont-init   ] 10-certs.sh: executing...
[cont-init   ] 10-certs.sh: terminated successfully.
[cont-init   ] 10-check-app-niceness.sh: executing...
[cont-init   ] 10-check-app-niceness.sh: terminated successfully.
[cont-init   ] 10-clean-logmonitor-states.sh: executing...
[cont-init   ] 10-clean-logmonitor-states.sh: terminated successfully.
[cont-init   ] 10-clean-tmp-dir.sh: executing...
[cont-init   ] 10-clean-tmp-dir.sh: terminated successfully.
[cont-init   ] 10-fontconfig-cache-dir.sh: executing...
[cont-init   ] 10-fontconfig-cache-dir.sh: terminated successfully.
[cont-init   ] 10-init-users.sh: executing...
[cont-init   ] 10-init-users.sh: terminated successfully.
[cont-init   ] 10-nginx.sh: executing...
[cont-init   ] 10-nginx.sh: terminated successfully.
[cont-init   ] 10-openbox.sh: executing...
[cont-init   ] 10-openbox.sh: terminated successfully.
[cont-init   ] 10-pkgs-mirror.sh: executing...
[cont-init   ] 10-pkgs-mirror.sh: terminated successfully.
[cont-init   ] 10-set-tmp-dir-perms.sh: executing...
[cont-init   ] 10-set-tmp-dir-perms.sh: terminated successfully.
[cont-init   ] 10-vnc-password.sh: executing...
[cont-init   ] 10-vnc-password.sh: terminated successfully.
[cont-init   ] 10-web-data.sh: executing...
[cont-init   ] 10-web-data.sh: terminated successfully.
[cont-init   ] 10-x11-unix.sh: executing...
[cont-init   ] 10-x11-unix.sh: terminated successfully.
[cont-init   ] 10-xdg-runtime-dir.sh: executing...
[cont-init   ] 10-xdg-runtime-dir.sh: terminated successfully.
[cont-init   ] 15-cjk-font.sh: executing...
[cont-init   ] 15-cjk-font.sh: terminated successfully.
[cont-init   ] 15-install-pkgs.sh: executing...
[cont-init   ] 15-install-pkgs.sh: terminated successfully.
[cont-init   ] 55-crashplan-pro.sh: executing...
[cont-init   ] 55-crashplan-pro.sh: setting CrashPlan Engine maximum memory to 1024M
[cont-init   ] 55-crashplan-pro.sh: terminated successfully.
[cont-init   ] 55-validate_max_mem.sh: executing...
[cont-init   ] 55-validate_max_mem.sh: terminated successfully.
[cont-init   ] 85-take-config-ownership.sh: executing...
[cont-init   ] 85-take-config-ownership.sh: terminated successfully.
[cont-init   ] 89-info.sh: executing...
    ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
    │                                                                      │
    │ Application:           CrashPlan                                     │
    │ Application Version:   11.2.1                                        │
    │ Docker Image Version:  24.01.1                                       │
    │ Docker Image Platform: linux/amd64                                   │
    │                                                                      │
    ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
[cont-init   ] 89-info.sh: terminated successfully.
[cont-init   ] all container initialization scripts executed.
[init        ] giving control to process supervisor.
[supervisor  ] loading services...
[supervisor  ] loading service 'default'...
[supervisor  ] loading service 'app'...
[supervisor  ] loading service 'gui'...
[supervisor  ] loading service 'certsmonitor'...
[supervisor  ] service 'certsmonitor' is disabled.
[supervisor  ] loading service 'nginx'...
[supervisor  ] loading service 'xvnc'...
[supervisor  ] loading service 'openbox'...
[supervisor  ] loading service 'CrashPlanEngine'...
[supervisor  ] loading service 'logmonitor'...
[supervisor  ] loading service 'logrotate'...
[supervisor  ] all services loaded.
[supervisor     ] starting services...
[supervisor     ] starting service 'xvnc'...
[xvnc           ] Xvnc TigerVNC 1.13.1 - built Dec 21 2023 00:55:16
[xvnc           ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
[xvnc           ] See https://www.tigervnc.org for information on TigerVNC.
[xvnc           ] Underlying X server release 12014000
[xvnc           ] Tue Jan 23 15:26:05 2024
[xvnc           ]  vncext:      VNC extension running!
[xvnc           ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc           ]  vncext:      Listening for VNC connections on all interface(s), port 5900
[xvnc           ]  vncext:      created VNC server for screen 0
[supervisor     ] starting service 'nginx'...
[nginx          ] Listening for HTTP connections on port 5800.
[supervisor     ] starting service 'openbox'...
[supervisor     ] starting service 'CrashPlanEngine'...
[supervisor     ] starting service 'app'...
[supervisor     ] starting service 'logmonitor'...
[logmonitor     ] Monitoring log file: /config/log/service.log.0
[logmonitor     ] Monitoring status file: /config/log/app.log
[supervisor     ] all services started.
[xvnc           ] Tue Jan 23 15:26:10 2024
[xvnc           ]  Connections: accepted: /tmp/vnc.sock
[xvnc           ]  SConnection: Client needs protocol version 3.8
[xvnc           ]  SConnection: Client requests security type None(1)
[xvnc           ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc           ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc           ] Tue Jan 23 15:26:11 2024
[xvnc           ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc           ]  ComparingUpdateTracker: (1:-nan ratio)
[xvnc           ] Tue Jan 23 15:55:14 2024
[xvnc           ]  Connections: accepted: /tmp/vnc.sock
[xvnc           ]  SConnection: Client needs protocol version 3.8
[xvnc           ]  SConnection: Client requests security type None(1)
[xvnc           ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc           ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888

Container inspect
[
    {
        "Id": "1201dded6d75aa16124fb69da0866a61c5c88aa758c0436e131b6fbe465e5562",
        "Created": "2024-01-23T14:26:05.105118879Z",
        "Path": "/init",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 1805,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2024-01-23T14:26:05.267061592Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:0cb185e1bdc0cb3f753bfbea64dbaa5c7f3ede1ae7c497eb03ca9f1cbe5f571e",
        "ResolvConfPath": "/var/lib/docker/containers/1201dded6d75aa16124fb69da0866a61c5c88aa758c0436e131b6fbe465e5562/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/1201dded6d75aa16124fb69da0866a61c5c88aa758c0436e131b6fbe465e5562/hostname",
        "HostsPath": "/var/lib/docker/containers/1201dded6d75aa16124fb69da0866a61c5c88aa758c0436e131b6fbe465e5562/hosts",
        "LogPath": "/var/lib/docker/containers/1201dded6d75aa16124fb69da0866a61c5c88aa758c0436e131b6fbe465e5562/1201dded6d75aa16124fb69da0866a61c5c88aa758c0436e131b6fbe465e5562-json.log",
        "Name": "/CrashPlanPRO",
        "RestartCount": 0,
        "Driver": "btrfs",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/mnt/user:/storage:ro",
                "/mnt/user/appdata/CrashPlanPRO:/config:rw"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {
                    "max-file": "1",
                    "max-size": "50m"
                }
            },
            "NetworkMode": "br0",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "no",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": null,
            "CapDrop": null,
            "CgroupnsMode": "private",
            "Dns": [],
            "DnsOptions": [],
            "DnsSearch": [],
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": [],
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": [],
            "DeviceCgroupRules": null,
            "DeviceRequests": null,
            "KernelMemory": 0,
            "KernelMemoryTCP": 0,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": null,
            "OomKillDisable": null,
            "PidsLimit": null,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/asound",
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware"
            ],
            "ReadonlyPaths": [
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ]
        },
        "GraphDriver": {
            "Data": null,
            "Name": "btrfs"
        },
        "Mounts": [
            {
                "Type": "bind",
                "Source": "/mnt/user",
                "Destination": "/storage",
                "Mode": "ro",
                "RW": false,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/mnt/user/appdata/CrashPlanPRO",
                "Destination": "/config",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "1201dded6d75",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "5800/tcp": {},
                "5900/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "HOST_OS=Unraid",
                "APP_NICENESS=0",
                "SECURE_CONNECTION_VNC_METHOD=SSL",
                "HOST_CONTAINERNAME=CrashPlanPRO",
                "USER_ID=99",
                "VNC_LISTENING_PORT=5900",
                "CRASHPLAN_SRV_MAX_MEM=1024M",
                "TCP_PORT_7910=7910",
                "TZ=Europe/Berlin",
                "HOST_HOSTNAME=NAS-MOOX",
                "CRASHPLAN_SERVER_ADDRESS=",
                "DISPLAY_WIDTH=1920",
                "DARK_MODE=0",
                "SECURE_CONNECTION_CERTS_CHECK_INTERVAL=60",
                "GROUP_ID=100",
                "UMASK=0000",
                "DISPLAY_HEIGHT=1080",
                "SECURE_CONNECTION=0",
                "WEB_LISTENING_PORT=5800",
                "TCP_PORT_7810=7810",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/base/sbin:/opt/base/bin",
                "ENV=/root/.docker_rc",
                "SUP_GROUP_IDS=",
                "LANG=en_US.UTF-8",
                "KEEP_APP_RUNNING=0",
                "INSTALL_PACKAGES=",
                "PACKAGES_MIRROR=",
                "CONTAINER_DEBUG=0",
                "VNC_PASSWORD=",
                "ENABLE_CJK_FONT=0"
            ],
            "Cmd": [
                "/init"
            ],
            "Image": "jlesage/crashplan-pro",
            "Volumes": {
                "/config": {},
                "/storage": {}
            },
            "WorkingDir": "/tmp",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {
                "net.unraid.docker.icon": "https://raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/crashplan-pro-icon.png",
                "net.unraid.docker.managed": "dockerman",
                "net.unraid.docker.webui": "http://[IP]:[PORT:5800]",
                "org.label-schema.description": "Docker container for CrashPlan",
                "org.label-schema.name": "crashplan-pro",
                "org.label-schema.schema-version": "1.0",
                "org.label-schema.vcs-url": "https://github.com/jlesage/docker-crashplan-pro",
                "org.label-schema.version": "24.01.1"
            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "74308ad1751bc372b24ff390606b06218a6ee14be8bb30280f7d9453b48d30d9",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/74308ad1751b",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "",
            "Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "",
            "IPPrefixLen": 0,
            "IPv6Gateway": "",
            "MacAddress": "",
            "Networks": {
                "br0": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": [
                        "1201dded6d75"
                    ],
                    "NetworkID": "0b3179a38f0a2afe648e1cd8b8f20c323cf5cf00a9ffa1e651552f4c94c00ee6",
                    "EndpointID": "50351e2edbbf82e39a172660464a7260a11f43a2eb75c27504f3c03604470fdb",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "",
                    "DriverOpts": null
                }
            }
        }
    }
]

Anything else?
service.log

Did you copy/pasted the server URL ? From the log file, looks like the server name (clients.us5.crashplan.com) contains an invisible character.  Can you try to re-configure it ?

 Thank you so much, was a copy/paste problem.
Thank you again


feat(feedback): add component to collect feedback

The idea is we should be able to collect feedback on our docs so we can see what pages aren't as helpful and we can improve them.
Here's a demo of it => https://www.loom.com/share/3f7c0b6a8ae1426788739058dcebef84
Also data is going to segment/amplitude, so we're good to generate reports.

@alexbass86 you may want to review the design of the new component
you can use this link to see a live preview
https://deploy-preview-126--xenodochial-knuth-724ea9.netlify.app/

@alexbass86 I am pushing this and if you think we need, we will make changes in a new PR


Look into issue with middleware on the root path blocking all other middleware

I looked into it, that is expected behavior from Express


GitHub Actions workflow for macOS

📒 Description
Now, this is a very basic GitHub Actions workflow. It basically just builds the app and that's it. It's just to verify everything builds fine on macOS at this moment (which is pretty useful, too).
IMPORTANT I had to disable signing because I had issues using the provided signing key on both my machine and in the virtual environment on GitHub. Anyway, I think this is for the good because outside developers won't have to tweak the build settings in XCode each time they want to try building the app for themselves. For us it probably doesn't change much, we can override this in any case.
Meanwhile I'm working on making signing work in a more sane way on my MacBook in the meantime but the builds are just taking too much time. Signing and packaging will be done in a separate PR in the future.
🕶 Types of changes

New feature (non-breaking change which adds functionality)

🤯 List of changes

macOS app is built as a part of CI

🔎 Review hints
If there's a CI/CD badge at the bottom of this and it's green, that's probably it, no more testing needed really.
It shouldn't matter if this gets before or after the other Actions PR I opened a while ago.

Aha, no CI/CD badge bere because I'm opening a PR from a fork. Well, the last build is here: https://github.com/MartinBriza/toggldesktop/commit/164879b60386fadd7b1345a10c750a2be3cfab13/checks?check_suite_id=286649387

Ok, this PR is now obsoleted by #3554


[Rancher Catalog] When trying to deploy second heml app UI hangs.

Rancher versions: 2.0:preview

I have created Project.
Associated it with existing namespace
Added my Git repo with Helm charts: https://github.com/ibagomel/helm-charts
Deployed Zookeper.
When I'm trying to get into Catalog Apps to deploy Kafka UI just hangs.

Version - 2.0 master 4/24
This is a bug, although they may be using the wrong version, we should not be hanging the application.

Version - v2.0.0-beta4-rc4
Verified fixed


Added query.add_rel_alias()

The idea is that one can control explicitly join generation with
add_rel_alias. For example:
qs.add_rel_alias(friends1='friends', friends2='friends').filter(
   friends1__age__lte=50, friends2__height__gte=180)

is the same query as
qs.filter(friends__age__lte=50).filter(friends__height__gte=180)

Notably there are certain queries that can't be written without
add_rel_alias(). For example
qs.add_rel_alias(friends1='friends', friends2='friends').filter(
    ~Q(friends1__age__lte=50, friends2__height__gte=180))

Unforuntaely there are queries we can't handle yet. Any query that
would require pushing two multijoins into a single subquery fail
loudly currently. For example the query
qs.exclude(Q(friends1__age=50) | Q(friends2__height=180),
           Q(friends1__height=180))

will fail.
The add_rel_alias() can in future be used for limiting join results,
for example
qs.add_rel_alias(
    translation_fi=Relation('translations', only=Q(lang='fi')))

would effectively add the join
JOIN translations ON translations.article_id = article.id AND
    translations.lang = 'fi'

to the query.

This is work on top of https://github.com/django/django/pull/4385.

I wonder if we could get away with something a little less drastic than the deferred filtering approach in this PR.
The original problem is that .exclude(friends__age__gte=30, friends__height__lte=180) currently targets two different sets of friends, but according to our API both of the conditions should target the same set of friends. PR https://github.com/django/django/pull/4385 fixes this, but then we don't have any way of writing the original query. If you use two excludes chained, you can't get the two conditions connected by NOT.
Instead of adding the add_rel_alias, we could have a way to tell Django that these filters inside the same query should target different sets of joins. Maybe some marker class for filter/exclude, for example .exclude(models.NewAlias(friends__age__gte=30), friends__height__lte=180), or just .exclude(friends_1__age__gte=30, friends_2__height__lte=180).
Yet another possibility is to do .add_relation(friends1='friends') adds a join for friends to the query, and if you try to exclude against it you get a failure. .add_relation(friends1=models.SubQuery('friends')) adds a subquery for friends1.
The reason I'm not too happy about the current patch is that deferred filters seem to be really hard to combine with annotations. Because we don't know if a relation is going to be subqueried or not until we have seen all the filters/excludes targeting that relation, we can't add annotations against that relation either. In addition, if you have multiple multivalued joins in a single query aggregations aren't going to work.
I'm going to let this rest a little. Maybe some ideas surface.

A random collection of problems with the way we handle multivalued relations: https://gist.github.com/akaariai/716dcdd895ba159123c4

Reminder for myself:

The correct way to query .exclude(Q(friends__age__gte=50), ~Q(friends__height__gte=180)) seems to be to generate a NOT IN subquery, and invert the inner query.
Do not try to support combinations of two different multivalued relations mixed in a single filter clause. Such queries do not make much sense anyways.

@akaariai: One issue I ran into recently is that even simple queries don't obey De Morgan's law. The following assertions are true on Django <= 1.9, and also on this branch:
test_obj = TestObj.objects.create()
test_obj.m2ms.create(int_value=10, char_value='foo')
test_obj.m2ms.create(int_value=20, char_value='bar')

assert test_obj not in TestObj.objects.filter(Q(m2ms__int_value=10) & Q(m2ms__char_value='bar'))
assert test_obj in TestObj.objects.filter(~(~Q(m2ms__int_value=10) | ~Q(m2ms__char_value='bar')))

Pulling down this branch and testing things out in an example application, it seems these counterintuitive assertions still hold. Do you have thoughts on whether obeying De Morgan's law is a desirable invariant for Q objects and querysets? I think it would make the ORM querying code easier to reason about from an end-user perspective.

Yes, I believe we should obey De Morgan's laws. Where we can't due to query complexity reasons, we should throw errors instead of producing nonsensible results. The only exception is that we might have managed to publicly document that we do not obey De Morgan for some cases.
The problem here is that we are ending up with extremely complex queries. This PR is draining a lot of time, and it seems it is hard to find time for even small patches these days. But I'll try to get back to this as soon as I can.

Closing due to lack of time to work on this.


[HOLD] Add an example custom kernel defining a custom syscall

DO NOT MERGE
This is PR is part of a pluggable syscall tutorial which we will share later and contains the final source code after following the tutorial.
Context
This PR replaces the current Fendermint FVM kernel with a new custom kernel which implements a new syscall and shows how you can use this syscall from a new custom actor which we load at genesis.
More specifically, this PR:

Implement a new `CustomKernelImpl FVM kernel which extends the default kernel.
Implement a new syscall called my_custom_syscall on the new kernel
Switches out the DefaultKernel used in Fendermint with this new custom kernel
Creates a new customsyscall actor which demonstrates calling the new syscall
Updates fendermint to load this new actor at genesis and run it at each epoch

Test plan
You can test this new kernel/syscall/actor by running one of our integration tests.
First you need to have docker installed, then compile a local docker image with this PR checked out:
cd fendermint
make docker-build

After the fendermint docker image has been built, you can run one of the integration tests
cd fendermint/testing/smoke-test
# creates the docker containers
cargo make setup
# runs the integration test
cargo make test

View fendermint logs and see the output generated by calling the customsyscall actor in each epoch:
docker ps
CONTAINER ID   IMAGE                       COMMAND
8da423d8bb1e   fendermint:latest           "fendermint --networ…"
...

View the docker logs:
docker logs 8da423d8bb1e
...
customsyscall actor returned: 21

You can now run cargo make teardown to stop the container.

This PR can be closed as its for documentation purposes


the effect on UCF101 dataset

Hello! I'm try to use your model to train UCF101, but the accuracy is only 50 % .Have you train the model on UCF101 datasets ？Is the test set accurate to 80% or more?

Hi and thanks for interest.
I did not train this model.
Instead, I carefully ported weights from a previous existing Keras implementation. Such keras implementation, in turn, carefully ported weights from the original Caffe version.
In this Caffe to Keras to Pytorch porting, several things can go wrong, so I'm not sure this model is exactly the same as the original Caffe model.
I did not test its performances, but I successfully used it for some applications a few times.
You can either use it as it is, with pretrained weights, or retrain it from scratch.
If you retrain it, you should be able to get at least near the results reported in the original paper. Are you following the exact same training protocol as reported by authors?

Moreover, available weights are available only for Sports1M.
No UCF101, unfortunately :(

Closing.


I want to contribute kr language

I would like to contribute to Korean translation. What can I do?

Fork BookStack
Clone the "resources/lang/en" folder
Rename from "en" to "kr"
Translate each of the files
Git commit & push
Submit PR via GitHub

Thanks @TBK for explaining the process.
Thanks @codev-kuk for offering to contribute translations. As an addition to the above, Ensure you do the translations in the master branch and create a pull request against the master branch.
More details are in the project readme here.


Telemetry Metrics enable failed

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion

Question

What do you want to know?
According to this page: https://github.com/apache/skywalking/blob/v6.6.0/docs/en/setup/backend/backend-telemetry.md

Repro Steps:

add telemetry config to  code/skywalking/oap-server/server-bootstrap/src/main/resources/application.yml

telemetry:
  prometheus:
    host: <IP_ADDRESS>
    port: 1543

./mvnw clean package -DskipTests
rebuld docker image with 6.6 es7-base and es7-oap
helm install skywalking
no 1543 port in pod or docker
login pod and find telemetry: none in file of /skywalking/config/application.yml

How could i enable this ?

That depends on how you package image, I think. This is only related to the docker file and port expose.

First of all, I only configured the SW_TELEMETRY_PROMETHEUS_HOST and SW_TELEMETRY_PROMETHEUS_PORT in my  helm values.yml,  but not work;
    Environment:
      SW_ES_USER:                    elastic
      SW_ES_PASSWORD:                8bla12O3hQ7u4WJ43N2xzgB4
      JAVA_OPTS:                     -Xmx2g -Xms2g -Dmode=no-init
      SW_CLUSTER:                    kubernetes
      SW_CLUSTER_K8S_NAMESPACE:      default
      SW_TELEMETRY_PROMETHEUS_HOST:  <IP_ADDRESS>
      SW_TELEMETRY_PROMETHEUS_PORT:  1543

Furthermore, I find code in https://github.com/apache/skywalking/blob/v6.6.0/oap-server/server-bootstrap/src/main/resources/application.yml#L178, It had been annotated by default, So I download the code and enable this like below:
telemetry:
  prometheus:
    host: ${SW_TELEMETRY_PROMETHEUS_HOST:<IP_ADDRESS>}
    port: ${SW_TELEMETRY_PROMETHEUS_PORT:1543}

But no port 1543 started in my oap-server pod, I had read all doc but not find any more detail about the telemetry.
I would be greateful if you could provide some advice and detail on this function....


Add swap feature to testnet home page

What would you like us to improve?
Adding a swap feature to the frontend testnet page would be of great improvement just as the bridge is present too.
How important it is?
Its very important as swapping goes together with bridging

Although we have made https://uniswap-showcase.sepolia.scroll.xyz/#/swap available, we do not want to endorse any specific dex project. Please see our Ecosystem page for lots of great DeFi projects on our testnet.


[test/examples] change for qa_interfaces and IController changes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 4 committers have signed the CLA.:white_check_mark: pwielders:white_check_mark: VeithMetro:white_check_mark: MFransen69:x: Volkan AslanVolkan Aslan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[MCA-665] Billing alerts

Compare actual and/or forecast budget to limit

Send alarm when reaching a percentage of the budget

Turn on CloudWatch Anomaly Detection on billing

Will trigger an alarm before an anomaly causing huge costs for customer

Example configuration:
...
  billingAlert:
    enabled: true
    autoResolve: false
    alarm:
      critical:
        budgetLimit: 10
        evaluationPeriods: 2
        comparisonOperator: GREATER_THAN_UPPER_THRESHOLD
      warning:
        budgetLimit: 5
        evaluationPeriods: 1
        comparisonOperator: GREATER_THAN_UPPER_THRESHOLD
    metric:
      period:
        minutes: 360
      statistic: Maximum

Does this work with multiple topics?

Does this work with multiple topics?


Add option to display dot files

According to https://github.com/DirectoryLister/DirectoryLister/discussions/701
Default behavior is not changed.
This new configuration item is used in FinderFactory, which now includes Finder.ignoreDotFiles() to the initialization.
Before, without setting this attribute, the class Finder would default to ignoreDotFiles TRUE.
Functionality:

added hide_dot_files variable to config/app.php
added hide_dot_files to FinderFactory initialization

Optional:

added HIDE_DOT_FILES config line to .env.example for user-configurability
added .env and .env.example to app_files (always hide). Those are configs only for internal use, right?

Tested by modifying the files of 3.8.3-release archive, with a file structure:
./.dot_file
./.dot_dir/
./.dot_dir/.dot_file
I did not look at the zip modules, as it seems to include whatever files/dirs Finder includes. Downloads of the directories contained dot files/dirs as expected.

Thanks for the PR! Let's get those failing tests fixed and we can get this merged.

Tests should work now.

Fixed interpunctional misunderstanding
Added '.env' and '.env.example' to the expected hidden list containing app_files in HiddenFilesTest.php
Added two tests for visibility and browseability of dot_files to FinderFactoryTest.php


i want to contribute, what should i do?

instead of donate BTC, i want to contribute code. where should i start?

oh, thinks for ur issues.  I do hope u could help me. Since I've been developing alone, I haven't updated the todo list for a long time. I'll update the todo list later. My tweet is random@isyiming, maybe we can contact through Twitter msg. sorry i havn't noticed this issue those days.

if u want, i think u could solve this, the 4th in tood list:
nft 部署 逻辑完善+测试

PayLoad中有一个存储nft图片信息的字段：image.png，但是在golang中解析为cbor结构体时有问题，我还没有解决它
PayLoad.Arg中有一个parents字段，它在get_mint_info_op_factory中被使用，但是我还没有捕捉到这个字段
this part is more independent and u don't need to get a complete view of the entire project. Then we can complete the 2th and 3th together.


Implement eig jvp

Currently draft status because the new test is failing due to incorrect gradient values. I haven't yet figured out the cause.
Fixes #2748.
TODO:

[ ] Fix reverse mode
[ ] Implement jvp for the left eigenvectors

@j-towns is your gradient error showing up for real eigensystems or complex?  given that it's nonsymm eig could it be the latter?  i.e. are you doing a simple elementwise comparison of complex eigenvectors?  The phase freedom of complex entries makes numeric eigenvector gradient checking a bit more complicated than just using check_grads.

Yeah indeed. I've dug into the implementation details of eig and it seems the 'phase freedom' is actually constrained by setting the largest component of each eigenvector to be real, thus the output of (np|jnp).linalg.eig is actually uniquely determined.
However it's questionable whether we should implement gradients that cater to that specific choice of constraint, since it's pretty arbitrary, and it feels like users shouldn't be depending on it in their code...
Some discussion on this towards the bottom of #2748. I'm not sure what the right answer is for these grads atm.


Maven plugin: easy support for personal access token

The maven plugin currently does not support personal access tokens, but that's very easy to add, as the ConfluenceRestClient already does support them.
When the ConfluenceRestClient gets a username == null and a password, it will send the password as a bearer token (personal access token) instead of Basic Auth with base64 username:password
After changing
        if ((this.username == null) || (this.password == null)) {
            applyUsernameAndPasswordFromSettings();
        }

to
        if ((this.password == null)) {
            applyUsernameAndPasswordFromSettings();
        }

one can simple use their personal access token by setting it into the "password" field and leaving "username" null.
A similar change (allowing a null username) can be done to  applyUsernameAndPasswordFromSettings(); I think.
If there's some interest, I think I can also provide a PR with these changes.

No reply but two thumbs up, I'll set up a PR for this.


Exceptions raised inside perform_mutation do not propagate

I'm creating a reviews plugin, this is a mutation
    @classmethod
    def perform_mutation(cls, _root, info, input):
        user = cls.get_node_or_error(
            info, input.user_id, only_type=User
        )

        product = cls.get_node_or_error(
            info, input.product_id, only_type=Product
        )

        review = Review.objects.create(
            product=product,
            user=user,
            content=input.content,
            rating=input.rating,
        )

        return ReviewCreateMutation(review=review)

This is perfectly fine, let's make something not working, let's use the User model instead of User ObjectType here
    @classmethod
    def perform_mutation(cls, _root, info, input):
        user = cls.get_node_or_error(
            info, input.user_id, only_type=UserModel
        )
       ...

This should raise an exception, however, it doesn't, no console output, the server still runs as it was, The GraphQL response is
{
CreateReview: {
   Review: null
   }
}

I've spent a day debugging this till I decided to print type(User) and damn, my stupidity has an important role in discovering this

not stale

not stale

Not stale

Plugins are not recommended anymore as a  way to add such features, instead, you should use an app. I'm closing the ticket as the problem doesn't currently affect us in the core.


Cleanup tutorials

This PR cleans up the documentation:

removes unused tutorials
structures the index to highlight intros/ advanced / etc
changes top section header of some notebooks to be more informative

Codecov Report

Merging #208 (e6fb89c) into main (483f6c4) will decrease coverage by 1.94%.
The diff coverage is 85.92%.

@@            Coverage Diff             @@
##             main     #208      +/-   ##
==========================================
- Coverage   76.80%   74.86%   -1.94%
==========================================
  Files          34       36       +2
  Lines        3065     3350     +285
  Branches      618      647      +29
==========================================
+ Hits         2354     2508     +154
- Misses        520      647     +127
- Partials      191      195       +4

Impacted Files
Coverage Δ

plenoptic/metric/model_metric.py
100.00% <ø> (ø)

...mulate/canonical_computations/laplacian_pyramid.py
76.00% <ø> (-24.00%)
:arrow_down:

plenoptic/simulate/models/frontend.py
50.46% <ø> (-43.00%)
:arrow_down:

plenoptic/synthesize/metamer.py
82.86% <ø> (+6.62%)
:arrow_up:

plenoptic/tools/signal.py
44.26% <ø> (ø)

plenoptic/synthesize/simple_metamer.py
28.57% <14.28%> (+2.99%)
:arrow_up:

...e/canonical_computations/steerable_pyramid_freq.py
71.81% <20.00%> (-14.63%)
:arrow_down:

plenoptic/tools/display.py
68.63% <50.00%> (ø)

plenoptic/tools/data.py
67.20% <60.00%> (-0.27%)
:arrow_down:

plenoptic/simulate/models/portilla_simoncelli.py
65.57% <77.77%> (-2.51%)
:arrow_down:

... and 13 more

... and 2 files with indirect coverage changes


raft: add a README of users

We should add a README into the raft package directory. Two things should be:
Users:

cockroachdb
etcd
dgraph.io
https://github.com/pingcap/tikv

TiKV uses Raft to support Geo-Replication. We have ported etcd's raft implementation to Rust.  By using raft, Key-Value regions always stay consistent. Placement driver (or pb) is also important for Geo-Replication. Pd collects state

github.com/yahoo/coname
https://github.com/weaveworks/mesh/tree/master/metcd
https://github.com/chzchzchz/raftsql
others?

Docs:
https://godoc.org/github.com/coreos/etcd/raft

https://github.com/pingcap/tikv
TiKV uses Raft to support Geo-Replication. We have ported etcd's raft implementation to Rust. By using raft, Key-Value regions always stay consistent. Placement driver (or pb) is also important for Geo-Replication. Pd collects state

https://github.com/weaveworks/mesh/tree/master/metcd

https://github.com/yahoo/coname

Fixed by https://github.com/coreos/etcd/pull/5419. Only added 3 non-toy projects and an example project as initial users, which I am familiar with. i will ping the authors of other projects to add it to readme themselves if they would like to.