Carousel Width Updated #6276

Issue Reference
Link: https://github.com/bagisto/bagisto/issues/6276

@devansh-webkul
There should not be any extra space between the products. Please find the screenshot Here.

@devansh-webkul
The product images are still not showing properly when the user is trying to slide the products in mobile view. Please find the screen recording here.

The mentioned issue has been fixed.

@devansh-webkul
The products should be slide If the user is trying to slide products, without using the Carousel icons.  in mobile view


Feature request: When posting a link which has already been posted, redirect to the links Post

Currently, when posting a Link when it's already posted on HN, It shows a generic Error
It would be great if Glider can redirect the user to the post, just how the HN website does it.

Yep, I've faced this issue too.


Variable length arrays compile error of hdf module with Visual Studio 2015

Variable length arrays is a C99 standard, and because Visual Studio 2015 doesn't support variable length arrays currently, so these codes will not be compiled by Visual Studio 2015, fox example, https://github.com/Itseez/opencv_contrib/blob/master/modules/hdf/src/hdf5.cpp#L329
// fetch rank
int n_dims = H5Sget_simple_extent_ndims( fspace );

// fetch dims
hsize_t dsdims[n_dims];  // error!

@panovr ,

Duplicate of https://github.com/Itseez/opencv_contrib/issues/546
Fix is here: https://github.com/Itseez/opencv_contrib/pull/547


Refactor the Diagrams with new Design Changes

Purpose
Refactor the following diagrams according to new design constraints:

[x] Architecture Diagram
[x] Use Case Diagram
[x] TO-BE-SYSTEM

This work has been completed!
Diagrams


reject publishing actions with a retriable error code if a earlier task is still publishing

Fixes a bug around segment publishing when multiple tasks in the same task group are pending completion.
Description
It's possible for the following timeline to occur for a single supervisor.
Task 1 goes into publishing, Task 2 is started
Supervisor is updated or handoff is triggerred manually
Task 2 goes into publishing and immediately publishes (it has not read many events).
Task 2 fails because the offsets in the DB do not match (Task 1 has not completed its SegmentTransactionalInsertAction yet).
Normally task 2 will fail with one of the below errors:
The new start metadata state[%s] is ahead of the last committed"           + " end state[%s]. Try resetting the supervisor
Inconsistency between stored metadata state[%s] and target state[%s]. Try resetting the supervisor.
Eventually Task 1 will publish and the supervisor will get itself sorted out but this can lead to several minutes of downtime and lag (and many failed tasks) as the supervisor tries to recover.
This fix attempts to address this issue by having the SegmentTransactionalInsertAction check whether a task can actually publish before trying.
Fixed the bug ...
Renamed the class ...
Added a forbidden-apis entry ...
The general approach here is to introduce a canPublishSegments method on each supervisor, and then call this method each time a streaming task wants to publish. If this method returns false, then throw a 503 error that the task will then retry.
A alternative approach might be to only try this as a fallback (right now this logic has to be run on every publish). But I thought this might introduce consistency bugs since part of the publish logic would have ran and failed and the logic introduced here is relatively simple (checking stuff in memory). I can update the logic to be exception handling only if others have strong opinions.
The canPublishSegments logic is only implemented on SeekableStreamSupervisor and essentially looks at pendingCompletionTaskGroups to see if there is already a task publishing (if the task is in pendingCompletionTaskGroups, that indicates it is already publishing) with earlier offsets then the task that is trying to publish.
I'm still working on some unit tests for this code.
Release note
Fix a bug that can occur when resubmitting supervisors or when task publishing takes a long time.
Key changed/added classes in this PR

SeekableStreamSupervisor
SupervisorManager
SegmentTransactionalInsertAction

This PR has:

[X] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[X] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[X] been tested in a test Druid cluster.

@georgew5656, this probably doesn't qualify as a bug per se.
It is a quality of life change but there is no incorrect behaviour here.
IIUC, this PR tries to:

eagerly identify the conditions which result in the messages below.
fail the commit in a retryable manner rather than failing the whole task.

[Case A] The new start metadata state[%s] is ahead of the last committed" + " end state[%s]. Try resetting the supervisor
[Case B] Inconsistency between stored metadata state[%s] and target state[%s]. Try resetting the supervisor.

If this is the case, we probably don't even need the new method canPublishSegments.
We just need to throw the right kind of exception for the above mentioned messages which can notify the task that it needs to retry. Or maybe the task action itself could retry. (something segmentAllocate action already does if the used segments seem to have changed).
However, if we do decide to have the canPublishSegments method, it should have the same logic that is used while validating the commit i.e. the same logic that ends up throwing the "inconsistent metadata" errors.
Alternatives
Perhaps, we could just lock/queue on the (supervisor + groupId) combo?
Publish should typically not take a long time, and failing every time some other task in the same group is already publishing seems like weird behaviour. The publish request coming from the second task could just wait while the first one finishes.
Let me know what you think.

@georgew5656, this probably doesn't qualify as a bug per se. It is a quality of life change but there is no incorrect behaviour here.
IIUC, this PR tries to:

eagerly identify the conditions which result in the messages below.
fail the commit in a retryable manner rather than failing the whole task.

[Case A] The new start metadata state[%s] is ahead of the last committed" + " end state[%s]. Try resetting the supervisor
[Case B] Inconsistency between stored metadata state[%s] and target state[%s]. Try resetting the supervisor.

If this is the case, we probably don't even need the new method canPublishSegments. We just need to throw the right kind of exception for the above mentioned messages which can notify the task that it needs to retry. Or maybe the task action itself could retry. (something segmentAllocate action already does if the used segments seem to have changed). However, if we do decide to have the canPublishSegments method, it should have the same logic that is used while validating the commit i.e. the same logic that ends up throwing the "inconsistent metadata" errors.
Alternatives
Perhaps, we could just lock/queue on the (supervisor + groupId) combo? Publish should typically not take a long time, and failing every time some other task in the same group is already publishing seems like weird behaviour. The publish request coming from the second task could just wait while the first one finishes.
Let me know what you think.

i thought about this approach but the concern is that it's possible for these error logs (inconsistency with metadata state) to be final error states, like if offsets are manually updated or something. we don't really want to retry in these scenarios

i thought about this approach but the concern is that it's possible for these error logs (inconsistency with metadata state) to be final error states, like if offsets are manually updated or something. we don't really want to retry in these scenarios

Hmm, I don't think I have ever seen a case of people updating offsets manually. At best, someone might completely remove the entry for a certain datasource, in which case the flow would still work.

i thought about this approach but the concern is that it's possible for these error logs (inconsistency with metadata state) to be final error states, like if offsets are manually updated or something. we don't really want to retry in these scenarios

Hmm, I don't think I have ever seen a case of people updating offsets manually. At best, someone might completely remove the entry for a certain datasource, in which case the flow would still work.
And even for that, simply resetting the supervisor is advised (and preferred by users) rather than updating the DB directly.

i ran some more testing and i've discovered that the scenario described in this PR initially only triggers the "The new start metadata state[%s] is ahead of the last committed" message. (Later tasks can fail with the inconsistent metadata state message). Based on this I think its fine to just throw a retryable exception in the first case and let the mysql connector retry instead of passing it up to the task action level (it looks like it defaults to 10 retries).
I think this" new start metadata is ahead" state is relatively safe to retry as well, i believe the terminal failures states normally throw "inconsistent metadata" instead

The new approach is definitely much simpler.
@georgew5656 , IIRC, the 10 retries happen in an exponential backoff manner.
What is the total time that will be spent in 10 retries?
Will it be enough to allow the preceding publish to finish. (I think it should be).

The new approach is definitely much simpler. @georgew5656 , IIRC, the 10 retries happen in an exponential backoff manner. What is the total time that will be spent in 10 retries? Will it be enough to allow the preceding publish to finish. (I think it should be).

its about a minute which i think should be enough in most cases. technically the previous approach also relied on client exponential backoff so we should be talking about a similar amount of time if the retry logic is the same

its about a minute which i think should be enough in most cases

Looking at RetryUtils, I think the total time for 10 retries would be more than that, probably closer to 5 minutes or so.

technically the previous approach also relied on client exponential backoff so we should be talking about a similar amount of time if the retry logic is the same

I think the retry logic is different since ServiceClientImpl uses the StandardRetryPolicy where the default exponential backoff leads to a total retry time of 1 hour approx.
That said, I prefer the retry at the metadata level since it is quicker and simpler.


HBASE-28215: region reopen procedure batching/throttling

https://issues.apache.org/jira/browse/HBASE-28215
The mass reopening of regions caused by a table descriptor modification can be quite disruptive. For latency/error sensitive workloads, like our user facing traffic, we need to be very careful about when we modify table descriptors, and it can be virtually impossible to do it painlessly for busy tables.
This PR introduces two new configurations:

hbase.table.regions.reopen.batch.size

This is an integer which represents the number of reopen procedures to create in a single batch. This defaults to Integer.MAX_VALUE, so it should be a no-op for any table with fewer than billions of regions

hbase.table.regions.reopen.batch.backoff.ms

This is a long which represents the millis to be waited between reopen batches. Hyperbolically, you could configure your batch size to 1 and your backoff MS to 60_000 — this would result in reopening no more than 1 region per 60s as a result of a single reopening procedure. This value defaults to 0 which implies that we will do no additional throttling by default.

@bbeaudreault @hgromer @eab148 @bozzkar

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 22s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 54s
master passed

+1 :green_heart:
compile
2m 25s
master passed

+1 :green_heart:
checkstyle
0m 34s
master passed

+1 :green_heart:
spotless
0m 42s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 24s
master passed

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 15s
root in the patch failed.

-1 :x:
compile
0m 13s
hbase-server in the patch failed.

-0 :warning:
javac
0m 13s
hbase-server in the patch failed.

-0 :warning:
checkstyle
0m 32s
hbase-server: The patch generated 4 new + 1 unchanged - 0 fixed = 5 total (was 1)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
hadoopcheck
1m 18s
The patch causes 10 errors with Hadoop v3.2.4.

-1 :x:
hadoopcheck
2m 40s
The patch causes 10 errors with Hadoop v3.3.6.

-1 :x:
spotless
0m 32s
patch has 23 errors when running spotless:check, run spotless:apply to fix.

-1 :x:
spotbugs
0m 13s
hbase-server in the patch failed.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 28s
master passed

+1 :green_heart:
compile
2m 53s
master passed

+1 :green_heart:
checkstyle
0m 42s
master passed

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 27s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 42s
the patch passed

+1 :green_heart:
compile
2m 30s
the patch passed

+1 :green_heart:
javac
2m 30s
the patch passed

+1 :green_heart:
checkstyle
0m 33s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 54s
Patch does not cause any errors with Hadoop 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 40s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 33s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s
The patch does not generate ASF License warnings.

33m 46s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5534/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5534

JIRA Issue
HBASE-28215

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux eff46ea00839 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1203c2014b

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5534/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

I believe that test failure TestPrefetchPersistence.testPrefetchPersistence:142->closeStoreFile:148 is unrelated to this changeset

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 32s
master passed

+1 :green_heart:
compile
1m  7s
master passed

+1 :green_heart:
shadedjars
7m 43s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  4s
the patch passed

+1 :green_heart:
compile
1m  7s
the patch passed

+1 :green_heart:
javac
1m  7s
the patch passed

+1 :green_heart:
shadedjars
6m 59s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 34s
the patch passed

_ Other Tests _

-1 :x:
unit
319m  0s
hbase-server in the patch failed.

350m 24s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5534/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5534

JIRA Issue
HBASE-28215

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 43de6d9659e6 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1203c2014b

Default Java
Eclipse Adoptium-11.0.17+8

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5534/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5534/2/testReport/

Max. process+thread count
4386 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5534/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 23s
Docker mode activated.

The javac warning is legit, will get to that asap.


Example doesnt work on m1 silicon mac mini

I'm so sorry to open issue like that but as you know m1 chips have some special problems. I couldnt add this package to my react native project. Then, I wanted to check example project in this repo. Example didnt work. I wonder that is there anyone can add this package and run on m1 chip. If there is, can share the git repo, i will try to clone and run on my device.

any update on it?


Any way to modify vi cmd mode bindings?

First: @srdubya and @lzybkr : Woooooooo! Vi mode! Thank you!
I'm interested in changing what the 'v' key does when in command mode. I poked around, but didn't see a way--am I correct that there is currently no way to change cmd-mode bindings?
If not, is there a plan or proposed to design to add such capability?
Thanks!

I took a look at the code and I think I could take a crack at it. My plan is for the PSReadLineKeyHandler cmdlets, if the EditMode is Vi, then add a new dynamic parameter "-ViMode [Insert|Command]". Depending on the value of that parameter, I'll temporarily swap the dispatch/chord tables.

I see no need for a dynamic parameter.  Maybe throw an error if not in vi mode, but dynamic parameters are annoying.

Okay, that sounds good. Thanks!

Fixed by PR: https://github.com/PowerShell/PSReadLine/pull/9
Thanks!


Why volume browse cannot be see for local

There is volume browse feature as bellow:

But it is disappear for local containers:

Hi there, volume browse doesn't work for the local endpoint because it is a feature of an agent endpoint. I will close this as it is not an issue.


dlx: fixup

Motivation for this change
Noticed this derivation looked a bit old. What I've done is a bit cleaner IMO.
homepage url also seemed to have gotten moved, the old one redirects to an generic page on the authors website.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Resolved conflicts, and adressed review commits.
Should be ready to merge @SuperSandro2000 :)


Support Datetime function LOCAL DATETIME

Motivation

JDSL doesn't support LOCAL DATETIME in JPQL

Modifications

I create localDateTime() & serializer to support LOCAL DATETIME function

Commit Convention Rule

Please commit your modification based by conventional commit:

Commit type
Description

feat
New Feature

fix
Fix bug

docs
Documentation only changed

ci
Change CI configuration

refactor
Not a bug fix or add feature, just refactoring code

test
Add Test case or fix wrong test case

style
Only change the code style(ex. white-space, formatting)

chore
It refers to minor tasks such as library version upgrade, typo correction, etc.

If you want to add some more commit type please describe it on the Pull Request

Result

Support LOCAL DATETIME function in JPQL

Closes

#604

I close the pull request because pull request is wrong


fix: complete the extension

What type of PR is this?

Check the PR title.

[ ] This PR title match the format: <type>(optional scope): <description>
[ ] The description of this PR title is user-oriented and clear enough for others to understand.
[ ] Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.
 README.md
√ 7. issue doc

@felix021 这个帮忙review一下呢

参考 https://github.com/kitex-contrib/config-nacos/pull/17 完善一下 readme 和 example

参考 https://github.com/kitex-contrib/config-nacos/tree/main/licenses 补充 go.mod 直接依赖的 license


Add new WMI query 'WmiMonitorID' to reliably list connected monitors.

By leveraging the WmiMonitorID class, the goal is to address Issue 50 and the fact there are known issues with the Win32_DesktopMonitor class, which often fails to accurately list or even name the connected monitors.
This addition is to attempt to provide a more reliable and correct listing of connected monitors and their potential names.
However, it's important to note that the presence of accurate EDID information within the monitors themselves is required in obtaining reliable results.
https://learn.microsoft.com/en-us/windows/win32/wmicoreprov/wmimonitorid

Added a new 'GetMonitorExtendedList' method to query the WmiMonitorID class..

Added new model 'MonitorExtended' to map the properties retrieved from the WmiMonitorID class, providing an alternative set of information without creating breaking changes to the existing 'Monitor' class.

A new field variable named _managementScopeWmi to provide access to the root\wmi namespace.

I made sure to keep the code consistent with the rest of the code base without causing any breaking changes.

I've tested on two different devices and the results below.
PC - RTX3080 GPU:
Win32_DesktopMonitor (yes, just one single instance!)
Caption: Generic PnP Monitor
Description: Generic PnP Monitor
MonitorManufacturer: (Standard monitor types)
MonitorType: Generic PnP Monitor
Name: Generic PnP Monitor
PixelsPerXLogicalInch: 96
PixelsPerYLogicalInch: 96
WmiMonitorID
1#
Active: True
ManufacturerName: BNQ
ProductCodeID: 78CE
SerialNumberID: 8CG016XXXXX - (Real serial omitted)
UserFriendlyName: BenQ GL2460
WeekOfManufacture: 51
YearOfManufacture: 2016
2#
Active: True
ManufacturerName: BNQ
ProductCodeID: 78CE
SerialNumberID: B1H030XXXXX - (Real serial omitted)
UserFriendlyName: BenQ GL2460
WeekOfManufacture: 3
YearOfManufacture: 2017
HP EliteBook Laptop:
Win32_DesktopMonitor
Caption: Generic PnP Monitor
Description: Generic PnP Monitor
MonitorManufacturer: (Standard monitor types)
MonitorType: Generic PnP Monitor
Name: Generic PnP Monitor
PixelsPerXLogicalInch: 144
PixelsPerYLogicalInch: 144
WmiMonitorID
Active: True
ManufacturerName: CMN
ProductCodeID: 14FF
SerialNumberID: 0
UserFriendlyName:
WeekOfManufacture: 47
YearOfManufacture: 2018

Thank you so much for this, I see that was quite a bit of work.
I have some trouble connecting two monitors because of the combination of HDMI, DisplayPort, DVI outputs on my graphic card and I don't have the right video cable for the second monitor. I hope I can make it work tomorrow.
I see that you added public class MonitorExtended - but because Hardware.Info is cross platform, it must work the same on Windows, Linux and macOS (or at least I try to make it so). Unfortunately MonitorExtended and GetMonitorExtendedList() don't make sense on Linux and macOS, so these must be merged with public class Monitor. Can you do this? If not, no problem, I am really grateful for your contribution.

You're right, in the context of Linux and Mac it doesn't make much sense.
My reasoning at the time was my computer with two attached monitors returns a single instance of Win32_DesktopMonitor, and inaccurate data at that too.
However, I think we can achieve the merge of WmiMonitorID into the Monitor class, we'll have to modify the original query and introduce two more to get the desired results.
First off we'll need to modify the original query to Win32_PnPEntity where PNPClass='Monitor'
This will provide us a DeviceId - We can use this to query both Win32_DesktopMonitor and WmiMonitorID their against their properties PNPDeviceId and InstanceName respectively
I'll make the changes and update the pull request.

While searching for a solution I came to the exact same conclusion, what you suggest seems optimal.

Ok, that been updated.
I hope you don't mind me using Linq on the subsequent queries, just to shorthand the unnecessarily need to loop through.
If either of the queries return null, the properties within the Monitor class are omitted and default values are used.

I looked at it quickly and it seems it should work, thank you!
I am in the middle of solving /Jinjinov/Usb.Events/issues/29 so I will merge your PR as soon as I finish there.

It works great! Thank you so much!
https://github.com/Jinjinov/Hardware.Info/releases/tag/v<IP_ADDRESS>


如何截取浏览器图片？

您好，我想截取浏览器的部分图片，思路是先把游览器全部截图，然后再通过元素坐标截取相应的图片，看了你的文档，但是没有找到相应的例子，只是找Screenshot()，是否能提供一个根据元素坐标截取图片的例子，谢谢。

I'm sorry, but I can't read Chinese. Google Translate is surprisingly good on that text, though.
I don't know what you mean (or Google Translate means) by "intercepting images based on element coordinates" though.
Note that (*WebElement).Screenshot has just been merged. Maybe that can help?

Hi @minusnine , @esolo0121 means :
How to take screenshots with coordinates? eg Screenshot(x1, y1, x2, y2).

There is no direct way to do it. If it were me, I would probably create a div at exactly the coordinates I want, maybe by injecting one via (WebDriver).ExecuteScript, and getting that element via FindElement, and then using the new (WebElement).Screenshot method.

老哥 你这样直接说中文,很不稳呀


[HELP] TCP/IP psock_send_eventhandler hardfault

Description
Hello,
We are running NuttX 12.6 on a STM32H7 MCU and ran into an issue right after accepting a socket connection where the board crashed. The hardfault together with the addr2line output on each flash address is attached as a txt file.
hardfault.txt
I attached an image with the Wireshark trace.

The IP <IP_ADDRESS> is running NuttX 12.6 release, while the IP <IP_ADDRESS> is running Windows 10.
According to the Wireshark data, both sides of the connection send a [PSH, ACK] message. The message going from 36 -> 178 waits for ACK with Seq=1, but the Windows machine sends a request instead of an ACK with Seq=1 causing the board to enter in hardfault.
Can someone help identify what could cause this issue and how to fix it?
Verification

[X] I have verified before submitting the report.

@wengzhe could you please take a look ^

@vladsomai did you test on 12.7.0 to confirm same issue still present?

@acassis we tested today on 12.7.0 and the issue is still present

Hi @vladsomai, I'm confused with the backtrace you posted: /Nuttx/net/tcp/tcp_send_buffered.c:434, which seems to be the first line of the function psock_send_eventhandler https://github.com/apache/nuttx/blob/releases/12.6/net/tcp/tcp_send_buffered.c#L434. Is your code same as the code on GitHub (which means you got the hardfault when your device just entered psock_send_eventhandler)?

Hi @vladsomai, we have found a similar issue that may crash in psock_send_eventhandler, but
not at the beginning, so I'm not sure whether they're the same one, may you try this patch? https://github.com/apache/nuttx/pull/15287

@vladsomai please confirm that PR fixed the issue for you!

Sorry for comming back so late guys, we are having the holiday break and will not be able to test this until 8th of January. Thank you for looking into this.


src/data/valid/Database-biosample-exhasutive.yaml requires MIxS multivalued slots with class ranges to be inlined_as_list

see

https://github.com/microbiomedata/berkeley-schema-fy24/pull/146

Did we upgrade to a version of LinkML with less silent repair?

may want to just make a new microbiomedata/mixs release and set that in assets/import_mixs_slots_regardless.tsv
currently

https://raw.githubusercontent.com/microbiomedata/mixs/1da849346a80b717810a02d7c8ed74a22bcd84de/model/schema/mixs.yaml


Convert the main project to SDK style?

New projects, even for .NET framework, are written in SDK style instead of MSBuild style. The .NET Upgrade assistant has an item "Convert project to SDK-style" but somehow what I get from that conversion doesn't build a plugin anymore. I was wondering whether you as the author have considered or have the knowledge to convert the project to SDK style.
I write code even for .NET framework often with the help of the IKVM and IKVM.Maven.Sdk projects/Nuget packages, allowing me to pull in Java packages (e.g. Saxon 12 for XSLT 3 or XQuery 3.1 or the XML Schema 1.1 version of Apache Xerces. Unfortunately the IKVM use is only possible with SDK styles projects.
I see that the example dependency project seems to be SDK style, however, perhaps that will already allow me to pull in IKVM, need to investigate that next.
Nevertheless I am opening this issue to ask whether you would know how to convert the main project to SDK style, I am afraid I am lost with the errors or failures (0 built, 0 failed, 1 skipped) VS gives me for rebuilding after using the upgrade assistant for the conversion to SDK style.

Unfortunately I cannot understand a lot of the jargon and abbreviations you used, so I can't help you.
You are welcome to submit a PR that implements any changes you think would be beneficial, but if I can't figure out how to test the PR and verify it doesn't cause regressions on my machine I will just reject it.

Which abbreviations are that that you don't understand? SDK style, MSBuild style? .NET Upgrade Assistant? Of the .NET Upgrade assistant I only try to use the feature "Convert project to SDK-style", it's task is basically to convert a project from the style/format you have in https://github.com/molsonkiko/NppCSharpPluginPack/blob/main/NppCSharpPluginPack/NppCSharpPluginPack.csproj to the style/format you have in https://github.com/molsonkiko/NppCSharpPluginPack/blob/main/ExampleDependency/ExampleDependency.csproj.
I hope that at least explains (a bit better) what I am trying/looking for.
Thanks for reading, I will try to see whether I reach something that is worth a PR, as I said, so far the basic "convert project to SDK-style" does its job in terms of the csproj format conversion but somehow that flawed that VS doesn't build that Npp plugin anymore.
IKVM and IKVM.Maven.Sdk are NuGet packages.
Saxon and Xerces are Java packages that implement the XSLT 3.0 standard and the XQuery 3.1 standard (Saxon) and the XML Schema 1.1 specification (Xerces) that I would like to use in a Npp plugin with the help of the IKVM/IKVM.Maven.Sdk packages. These are just my current use cases, not really relevant for the issue, which is the conversion of the project to SDK style.

@martin-honnen
OK, thank you for explaining what you're aiming to do.
Now that it's clear to me that you want to change the format of the csproj file, I am more skeptical of what you're asking for, largely because NppCSharpPluginPack.csproj already has build actions that I think only work with MSBuild. I suppose there are other ways I could automatically perform those actions before building my project, but it is important to me that they get performed somehow.

Let's put this on hold, after some struggle I had some initial progress to use IKVM as part of DependencyExample so it might be I don't need a change to the main plugin project format. I need some days to explore that before knowing it works out.--Gesendet mit der GMX Mail AppAm 31.12.24, 04:31 schrieb molsonkiko @.***>:
@martin-honnen
OK, thank you for explaining what you're aiming to do.
Now that it's clear to me that you want to change the format of the csproj file, I am more skeptical of what you're asking for, largely because NppCSharpPluginPack.csproj already has build actions that I think only work with MSBuild. I suppose there are other ways I could automatically perform those actions before building my project, but it is important to me that they get performed somehow.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@martin-honnen
If you were having success including some code as part of DependencyExample, you might be able to achieve what you want by just adding a new Reference block to the csproj, or just replace the name of the dependency in the block I linked above.


Feat/check disk only label

This allows the plugin to (o)nly check specific mount points.
Pull Request Checklist
This is not in reference to an existing issue, but a feature I needed. This lets me create specific checks for certain, high priority disks.
General

[x] Update Changelog following the conventions laid out on Our CHANGELOG Guidelines

[x] Update README with any necessary configuration snippets

[ ] Binstubs are created if needed

[x] RuboCop passes

[x] Existing tests pass

Can I also get a testing artifact?

Are there any example plugins that have tests? Ruby and rspec especially is alien to me, so I'm not doing a great job at making my test work, nevermind pass 🤦♂

check out any of the ones checked off here: https://github.com/sensu-plugins/community/issues/41
dcos was the initial one and probably has the most coverage.

@majormoses Changes taken into consideration.
Hope you don't mind the .rubocop.yml tweaks too, but they didn't make sense for rspec files.

Oops, thanks for spotting that.
Added tests to check both long and short flags, tweaking original tests to better emulate CLI args (Using parse_options instead of directly setting the values) 👍

Do you want the commits squashing for tidiness?

Before githb offered it I often requested people to. Now I generally use the squash and rebase option to accept a contribution when there are a lot of commits with messages with little overall value. If the commits paint a story of how we got there and it is valuable I do a rebase and merge. I never use the actual "Merge" option as it pollutes the history.

If, you'd like to tidy up your commits I can certainly wait for you to accept this.

I didn't even know GitHub could do that...

It is a somewhat new feature and one that I have been requesting for years, you can read about the different functions here: https://help.github.com/articles/about-merge-methods-on-github in my orgs I actually disable the normal merge option as merging without fast farwarding is a terrible idea.

released: https://rubygems.org/gems/sensu-plugins-windows/versions/2.4.0


Update sbt-microsites to 1.1.4

Updates com.47deg:sbt-microsites from 1.1.0 to 1.1.4.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.47deg", artifactId = "sbt-microsites" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

Merging #1216 into master will increase coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1216      +/-   ##
==========================================
+ Coverage   81.07%   81.16%   +0.09%
==========================================
  Files          55       55
  Lines        1009     1009
  Branches       42       42
==========================================
+ Hits          818      819       +1
+ Misses        191      190       -1

Impacted Files
Coverage Δ

core/src/main/scala/io/finch/Endpoint.scala
72.77% <0.00%> (+0.55%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 78b2f15...18fe992. Read the comment docs.


Include ELKI for some 20+ additional algorithms

ELKI, which can easily be invoked from command line, provides many additional algorithms missing from this benchmark, such as:

DB Outlier
HilOut
KNNDD (not the same as KNN Outlier)
KNNSOS
KNN-weight
Local Isolation Coefficient
ODIN
Reference-Based outlier detection
SOS
HySort OD
ALOCI
INFLO
KDEOS
LDF
LDOF
LOCI
LoOP
SimplifiedLOF
VarianceOfVolume
ABOD / FastABOD, LB-ABOD
IDOS
ISOS
LID
GLOSH for HDBSCAN*

In other cases, it may be desirable to compare the performance of different implementations:

Isolation Forest
kNN Outlier
LOF
COF
CBLOF
Because sometimes one implementation may be better than another.

Thank you for your valuable advice! In the future, we plan to include more algorithms (both shallow machine learning algorithms and deep learning algorithms) in our ADBench, to analyze different AD algorithms from a more comprehensive perspective.


update rehype transform plugin: "plugin-code"

fix issue #75

comments:

seems to work well.. both SSR and CSR

I'm not familiar with remark and rehype.. and their plugin system.. so this may be a naive implementation;feel free to modify

@ts-ignore is used in 3x places

I'm not great with Typescript.. passable at best;maybe you can figure out how to massage the type signatures so these aren't needed?

next steps:

after this was written.. I made the mistake of trying to cleanup the code a little more by adding:  import {isSingleTheme} from 'carta-md'

this sent me down a rabbit hole hellscape

all import statements that reference a typescript file (ex: foo.ts) needed to be changed

from: import * as foo from './foo'
to: import * as foo from './foo.js'

which the typescript compiler handles correctly
and the resulting javascript includes the .js file extension,which node.js requires and seems to be the standard

outcome:

plugin-code successfully imports isSingleTheme and compiles correctly
vite is no-longer able to import Svelte components from the package

Unknown file extension '.svelte'
related issues: 1, 2, 3

I played around with every possible way to specify exports in package.json and nothing fixed this error

which is an error that I encounter all the time, when trying to use Svelte components from npm
I'm beginning to wonder if it's my version of node or something local to my machine,but on the other hand.. many Svelte components from npm do work..so if there's some magical export incantation that makes it work, I'd love to know what that is
docs: 1, 2

would you like me to add another branch that extends this PR branch?..

to include these breaking changes
so maybe we can put our heads together and figure out how to make it work

PS: I decided that using the "docs" directory for testing wasn't a great idea, because it uses adapter-static and imports a bunch of dependencies that aren't needed for basic testing.. so I added a "tests" directory to my repo.. specifically to ensure that every build can get a quick real-world test before being deployed. For example, to catch errors like: Unknown file extension '.svelte' (which is still giving me nightmares). And, when they do pop up.. to quickly iterate on what does or doesn't work by tweaking either package.json or files in dist before it gets pushed to npm.
This "tests" directory is nothing special.. but the branch that adds it is here. Let me know if you want me to create a PR.

Hi again,
I checked out the changes and to me it seems a bit overly complicated. I created an alternative fix #77 , which to me seems to work fine, could you check it out and tell me if the end result is the same?
Regarding isSingleTheme etc, I think the best thing to do is to bundle all those utility functions into the Highlighter class, so that no imports are required.
Thanks

Great job with #77 . Both PR result in the same behavior. I like yours better.


Add support for urlscan

Hi. This PR is, as the title says, to add support for urlscan.

Hi. If anyone is still interested, see: tmux-urlscan.


Disable stdout buffering for Airflow jobs

Unfortunately, airflow jobs launched via docker-trampoline have buffered stdout.
That leads to misleading timestamps in the logs that is not as useful and nice as it could be.
Examples are:

sync_test_lists_dag.sync_test_lists that was running for an hour+, BTW, thanks to KISS locking it the concurrent task caused zero issues
hist_canning.meta_pg running for hours

The issue is not (at least currently) at docker-trampoline level as docker logs --timestamps $container_name at datacollector.infra.ooni.io clearly shows that timestamps at docker-container level are also "groupped" together:
darkk@datacollector:~$ sudo docker logs --timestamps --tail 5 compassionate_stallman
2018-12-13T11:39:03.818349757Z Processing autoclaved 2018-12-11/20181211T010204Z-DE-AS6830-web_connectivity-20181211T010205Z_AS6830_o8ycjFI6wnK7LZGa3QvAuzNS11yqDl1nRcfqnoiCjEdVDAbKLs-0.2.0-probe.json.lz4
2018-12-13T11:39:03.818353780Z Processed 2018-12-11/20181211T010204Z-DE-AS6830-web_connectivity-20181211T010205Z_AS6830_o8ycjFI6wnK7LZGa3QvAuzNS11yqDl1nRcfqnoiCjEdVDAbKLs-0.2.0-probe.json.lz4: 39.8 MiB, 38.8 s, 1.0 MiB/s
2018-12-13T11:39:03.818362336Z Processing autoclaved 2018-12-11/20181211T011006Z-FR-AS21502-web_connectivity-20181211T011007Z_AS21502_WWAlF77zTiHlT8BJXxt8YrodHiivlbAT7PNM5Uvt9iAInVGlG6-0.2.0-probe.json.lz4
2018-12-13T11:39:03.818369776Z Processed 2018-12-11/20181211T011006Z-FR-AS21502-web_connectivity-20181211T011007Z_AS21502_WWAlF77zTiHlT8BJXxt8YrodHiivlbAT7PNM5Uvt9iAInVGlG6-0.2.0-probe.json.lz4: 40.0 MiB, 40.6 s, 1.0 MiB/s
2018-12-13T11:39:03.818376167Z Processing autoclaved 2018-12-11/20181211T011132Z-BR-AS2715-web_connectivity-20181211T012812Z_AS2715_KS4yeEROu5TngNqAJE88gTRf4exgDQb3iZZMdJcHYHlTWG0NBH-0.2.0-probe.json.lz4

Obsoleted by https://github.com/ooni/backend/issues/437


Assets are missing

The last releases have pre-built binaries missing. Just forgot or there will be no assets anymore?

The last changes do not touch Binary server parts, so feel free to use the older version. In the future, we are planning to move GRPC to RR core. But we still want to provide GRPC only binary.

I see, thanks


Update support-bundle-image default value per chart defnition

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:

https://github.com/harvester/harvester/issues/6277
Solution:

Use chart and Pod ENV to update setting's default value when it is not fit for hard-coded on source code.
Avoid updatting empty value to settings.Dfault
Inspired from https://github.com/harvester/harvester-installer/pull/813, Harvester should allow to replace the default value and current value of settings from Pod ENV.
Further, the chart generate the ENV from Values.yaml, thus we don't need addtional code for update.

The current hard-coded settings, will update the Default automatically after upgrade.

For none-hard-coded settings, do this via the chart definition.

Related Issue:
https://github.com/harvester/harvester/issues/6277
Test plan:

Create a new cluster, it will have support-bundle-image with generation 1 in general; instead of 2 in the past

settings.harvesterhci.io support-bundle-image -oyaml
apiVersion: harvesterhci.io/v1beta1
default: '{"repository":"rancher/support-bundle-kit","tag":"master-head","imagePullPolicy":"IfNotPresent"}'
kind: Setting
metadata:
  creationTimestamp: "2024-08-15T19:48:37Z"
  generation: 1
  name: support-bundle-image
  resourceVersion: "6646"
  uid: 01952165-f164-4edd-bc62-e5afa52fcfd8
status: {}

Upgrade to new version, the default value should always match the setting in chart.

Later, we can drop this controller to update the setting default in such a dependency path. cc @FrankYang0529 @bk201
https://github.com/harvester/harvester/blob/4e94f46e2f40fcf1cd6efd4530e63870b6945a5f/pkg/controller/master/setting/handler.go#L182

@mergify backport v1.3 v1.4

note: a tricky helm issue/limitation https://github.com/helm/helm/issues/12188 is escaped on this PR.

@bk201 The log messages are updated, please take a new look, thanks.

All 3 commits are merged into 1 commit for final committing.

A wiki page is added to describe how to update the Default field via chart.
https://github.com/harvester/harvester/wiki/Harvester-Settings-and-Update-the-Default-via-Chart


Possible solution for respecting safe area insets of DKImageExtensionPhotoCropper?

As I'm sure you are aware, the photo cropper does not respect safe area insets on the bottom of the screen, which is especially noticeable on devices without home buttons, like the iPhone X, iPhone 11, etc.

Per this solution on TOCropViewController: https://github.com/TimOliver/TOCropViewController/issues/376 I figured that adding imageCropper.modalPresentationStyle = .fullScreen to line 48 on DKImageExtensionPhotoCropper.swift would resolve the view controller's lack of respect for safeAreaInsets.bottom, but no change seemed to occur.
In fact, modifying the CropViewController within DKImageExtensionPhotoCropper.swift (via imageCropper.resetButtonHidden = true, imageCropper.aspectRatioPreset = .presetSquare, etc.) resulted in no change at all in the DKImageExtensionPhotoCropper.
I figured I would at least point out that a more privileged contributor to DKImagePickerController may be able to more easily resolve the issue with safeAreaInsets via possibly adding something like imageCropper.modalPresentationStyle = .fullScreen to line 48 on DKImageExtensionPhotoCropper.swift

Hi @ChopinDavid Thanks for your detailed explanation 😃


[DNM] Migrate from travis/appveyor to Github Actions

Please squash my commits on merge. They are a mess.
Things we loose

No more 32 Bit Windows builds for now. At least until we change our build chain from Miniconda to conan.
Nightly builds are not hosted on sourceforge anymore, but directly on Github. The nightly artifacts are deleted after 90 days. Hosting on sourceforge is not a problem using Github CI if we need it, I just don't see the point of hosting them at two different places.

Things we gain

Concurrent runs for Windows, Mac and Linux
Code Coverage hosted on codecov.io
Some more automation for releases

Automatic creation of a Github release on new git tags starting with v.
The first section called Version xxxx from the file ChangeLog is added as a Release description
The MacOS package, Windows 64 zip and Windows 64 installer are added as release assets.
The documentation is added to the gh-pages branch. The links must still be added manually though...
A PR is created at https://github.com/DLR-SC/tigl-conda to trigger new conda builds.

Some caveats

For windows builds, Matlab libraries and doxygen is downloaded from Sourceforge. This fails every now and again. As a prevention, these files are cached, but the cache is not supported for runs triggered by tag creation, so that it can happen that a Release run fails because the windows dependencies cannot be downloaded
For the same reason, ccache and clcache do not work on Release runs, because Github does not (yet) support the cache feature for runs triggered by tag creation.

How Has This Been Tested?
I ran A LOT of test runs on my fork. I used my master branch to test nightly builds and create test releases.

Now creating a release requires the following manual steps:

Add a section to ChangeLog.
Bump the Cmake Version
Create a tag vX.X.X and push it to Github
Merge the automatically created PR at https://github.com/DLR-SC/tigl-conda
Add links to the documentation to the website
Trigger the OpenSuse Build System for Linux builds.

Where is the latest build on github ci. I don't see any checkbox at the last commit.

I think you have to check my fork: https://github.com/joergbrech/tigl/actions for the latest builds, they don't show up here.

Closing this in favor of #674, sorry for the complete mess...


DEV: Rename chat-message to prepare for tc-message rename

Since most of us don't know what the tc- prefix stands for, we are favouring the chat- prefix as a replacement.
This PR is part 1 of the rename, since tc-message is to be renamed to chat-message, we have to replace the existing chat-message usages first.

Did not test out locally but the changes are straight forward and this change is low risk IMO.


Analysis: Do we need a Webanalytics tool for Altinn Apps (and if so - what tool)?

The need for webanalytics in Studio is moved to a separate issue Altinn/altinn-studio#4040

Description
To be able to give app owners a better insight on how our services and applications are used, there is a need to look at a webanalytics tool we could use in the running Apps.
Example tools that can be used:

We should see if Matomo which is used in many other web applications and has integrations with React can be used. So similar to task Altinn/altinn-studio#321 we would like to look at Matomo.
We can also look into hotjar which is also used by other organisations for getting feedback on end user behaviour. This is used on applications / services similar to the applications altinn will have.

https://matomo.org/
https://www.hotjar.com/tour
It is expected that we would create more issues after completing this issue.
User needs we should look into:

As an App Developer I want deep user behaviour insights for editions used in portal
As an App Developer I want deep insights for edition API usage
As an application designer i want insight into user behaviour to understand how / what works and does not work, so i can easily identify usability issues and issues they encounter.

Technical considerations

We need to understand what and where the data / information will be stored.
How we can keep the end-user privacy while using analytics tools.

Acceptance criterea

What is allowed/not allowed
Validations
Error messages and warnings
...

Tasks

[ ] Analyse pros and cons for using matomo
[ ] Analyse pros and cons for using hotjar
[ ] Look into if there are other tools that can be better suited for our needs.

Closing as duplicate


add FromContextAsHelper & SetDefault

Codecov Report

Merging #5 (930650c) into master (3c01286) will decrease coverage by 0.53%.
The diff coverage is 39.13%.

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
- Coverage   66.66%   66.13%   -0.54%
==========================================
  Files          22       22
  Lines         861      874      +13
==========================================
+ Hits          574      578       +4
- Misses        243      251       +8
- Partials       44       45       +1

Flag
Coverage Δ

unittest
66.13% <39.13%> (-0.54%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

logger/context.go
0.00% <0.00%> (ø)

logger/valuer.go
73.91% <ø> (ø)

logger/helper.go
44.44% <28.57%> (ø)

logger/stdlogger.go
78.57% <45.45%> (-12.34%)
:arrow_down:

logger/logger.go
97.22% <100.00%> (+0.07%)
:arrow_up:

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


[C#] Can't attach debugger when launching project.

Tested versions

Reproducible in: v4.4.dev.mono.custom_build.e2dd56bea (2024-09-03 15:38:17 UTC)
Not reproducible in: 4.3.stable (still works now)

System information
Godot v4.4.dev.mono (e2dd56bea) - Windows 10.0.22631 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 4060 (NVIDIA; <IP_ADDRESS>23) - 13th Gen Intel(R) Core(TM) i5-13400F (16 Threads)
Issue description
Unable to attach debugger when launching project on latest build.
It's OK to attach to a running instance.

My launch.json config for VSCode:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(C#)Launch",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "dotnet: build",
            "program": "${env:GODOT}", // my path to latest godot build
            // "program": "C:\\Dev\\Godot\\4.3.stable\\Godot_v4.3-stable_mono_win64.exe",
            "args": [
                "--verbose"
            ],
            "cwd": "${workspaceFolder}",
            "console": "internalConsole",
            "justMyCode": false,
            "stopAtEntry": false,
        },
        {
            "name": "(C#)Attach",
            "type": "coreclr",
            "request": "attach",
        },
    ]
}

Steps to reproduce
Debug any project (by launching) on 4.4.dev.
Minimal reproduction project (MRP)
Mrp with vscode launch.json:
DebuggerMRP.zip

Closing as fixed, if it returns please comment here and this can be reopened, and if you can identify when this was fixed adding that would be great information!


Spelling: Seting -> Setting

Would it make sense to add an  before the header so old links don’t break?

Thanks!
To keep things simple, I prefer not to maintain old anchors, even though it's a good point 👍


Service Refactoring: Change API endpoint & apply amplify logger

Description
Service Refactoring: Change API endpoint & apply amplify logger
Checklist

[x] : Change API endpoint

https://dev.kendra-btns.whatilearened.today/noauth/graphql

[x] : Apply amplify logger  - docs

Please refactor Search related components refer to this commit.


Added signup, signin, forgot password, reset password API and react components

Notion card
https://www.notion.so/saeloun/Redevelop-Sign-In-page-using-React-1ccc0724feb24e7485a02bdf4c51a17a
https://www.notion.so/saeloun/Redevelop-Sign-Up-page-using-React-58ea46ef7bbd4b239b191ca1863d1063
Summary

Created authentication with react components for a signup, signing, forgot password and reset password.
Created API endpoints for the complete auth flow and integrated them with the frontend.

Preview
https://share.vidyard.com/watch/hjA2H2MpCDzcDCSqjsFw3v
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactor (non-breaking and retains same functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code
[ ] I have annotated changes in the PR that are relevant to the reviewer
[ ] I have added automated tests for my code

@prasanthchaduvula @sanjibroy360 @supriya3105 Please see this loom video. Not all the things are tested yet. I will need some more time for it. https://www.loom.com/share/5df5f2e22eab43ce81b5e05cf9b2db1d

@sanjibroy360 Please resolve conflicts on this PR.
@apoorv1316 Can you share the bugs from this PR testing ?
As far I understand it was the google sign in issue . Not able to verify as google sign is not working on staging since migration to DO.

@prasanthchaduvula Whats happening with this PR ? When can we release it ?

@supriya3105 By Today I will finish the devise failing tests and we can release it in our next release.
@apoorv1316 Have you tested this PR? Please test this PR. So that If anything now working then I can fix it

@prasanthchaduvula Please fix the bug in forgot password flow that we discussed on the call. cc @supriya3105

@vipulnsward flaky specs are failing on this PR already present in the current development. Remaining all specs are passing


feedback

Hi! I showed this around to some ASIC engineers I know, and one gave this feedback:
That is really cool.
I didn't run it yet but looking at the code it's using the Sze long channel model, which practically eveyone uses so I get it, but I never personally really liked much.
So I'll do one short rant...
The problem is pinch-off is super confusing in Sze's model.    The charge in the inversion layer drops to zero and then you have to explain how current exists when there is no charge.  That violates the definition fairly directly so most people just waive their hands and go "modern physics".  And then you get to modern physics and they say, what are you talking about there's totally charge there.  See these nice band diagrams... Ugh.  And that's when people switch to CS.
Chenming Hu's (inventor of FinFET) very good (and somehow free!) text starts with Sze's model, like everyone does so you have to know it, but then offers a much better alternative long channel model which doesn't have this whole loss of inversion layer charge problem.   (See 6.9)  I'm not going to retype it but instead of looking at the charge volume and how it changes across the channel under various fields, it looks at the charge velocity.   Then you just say charge has a top speed, which agrees totally with modern physics.
Here is an excerpt from the text, "The situation is like a mountain stream feeding into a waterfall. The slope of the river bed (dEc/dx) and the amount of water in the stream determine the water flow rate in the stream, which in turn determines the flow rate down the waterfall. The height of the waterfall (Vds − Vdsat), whether 1 or 100 m, has no influence over the flow rate."
https://www.chu.berkeley.edu/modern-semiconductor-devices-for-integrated-circuits-chenming-calvin-hu-2010/

This is great feedback. In truth, the simulator is much worse than just assuming long channel - to make the transition between linear and saturation smooth, I had to make some even worse approximations. I also make some really big assumptions about the electric field and the charge carriers. A device physics engineer might cringe at the simulator.
But, the aim of the simulator is not to be accurate, or even true. Rather, it is aimed at helping students grasp that first concept of regions of operation, drift velocity, pinch-off (going from linear to saturation or vice versa), and just a general 3D image of what it looks like. I try to show this basic working without complicating it more for people who might be seeing this for their first or second time.
Maybe one day I might be inspired enough to do a full metal physics simulator that tries to be as accurate as possible, but that might take a few years from now :)


Problem with tRoundStartMoney and ctRoundStartMoney (first round of each side)

Describe the bug
Incorrect amounts for tRoundStartMoney and ctRoundStartMoney but only for the first round of each side (other rounds are OK).
Using parse function + clean_rounds (same problem using or not the argument remove_bad_scoring=True).
To Reproduce
Steps to reproduce the behavior:

Parse the following demos : AST-MIBR, BIG-GOD, G2-VIT
Check the following fields for the JSON : tRoundStartMoney and ctRoundStartMoney
Problems detected:

AST-MIBR and BIG-GOD : wrong amounts for both team at round 1 and round 16
G2-VIT : inferno : wrong amounts for both team at round 16, mirage : wrong amount at round 16 for Team Vitality, incorrect amounts for both team at round 16

Expected behavior
For round 1 and 16 the tRoundStartMoney and ctRoundStartMoney should be 4000$ (800$ per player)
Screenshots
N/A
Desktop (please complete the following information):

OS: [Windows]
Browser [N/A]
Version [N/A]

Smartphone (please complete the following information):

Device: [N/A]
OS: [N/A]
Browser [N/A]
Version [N/A]

Additional context
Other rounds work fine, no problem detected.

Interesting...when you look at the frames, the money looks fine. I imagine it has to be the fact that I'm grabbing round start money during round start.
How important is this feature? We could remove it since it is unstable.

I think I'll have better success with manually implementing these keys, which is what I'll do. Even in frames, I'll just loop through and sum

Think the best approach here is to just calculate this by looking on the FreezeTimeEnd. Sometimes demos may miss that, not much we can do!

Addressed in #166


Decoupling express.request and express.response from express application

I'd like to be able to use express.request and express.response outside of an express application "instance". This means I'd be able to use them as prototypes for my own request and response objects. Additionally, I'd like to also define which objects they delegate to for their prototypes (I understand this last part is possible already but its not first-class and it won't work in an ES2015 world where imports are read-only).
I'm a big fan of the work that was done to decouple the router implementation into its own module so that it no longer assumes the presence of an express application. I believe what I am proposing is in the spirit of that effort.
A couple use cases I'm hoping to address:

Testing for standalone router: I have a router which depends on its request and response arguments to implement the express.request and express.response interfaces. I'd like to write unit tests that are minimal, so I don't want to initialize an express application, nor do I want it to listen on a port or socket. Ideally, I could create some request and response objects directly from the express prototypes, and also plug in a "mock" for http.IncomingMessage and http.ServerResponse (that don't need to actually do any networking) to be one level up the prototype chain. Then I could just invoke my router's handle() method with the arguments I've constructed and set up assertions on the behavior. This is currently not possible because both request and response have methods that read settings from this.app. I've take a look at the tests for pillarjs/router and they seem to be limited to only use API on request and response that are provided by node core.
Extensibility: I've seen a few issues on the tracker that are essentially asking for the ability to rewire request and response to expose more or different functionality. Its been noted that the design of express was to be a thin wrapper on top of the node core HTTP API, and thats where the limitations come from. If instead of directly using private API of http.IncomingMessage and http.ServerResponse, we had a declared interface (one that the aforementioned types already adhere to or do so through a thin adapter) for what express.request and express.response rely on up the prototype chain, we could enable much more innovation in the ecosystem. Express would also benefit from seeing experimentation on those layers and adopt proven and useful extensions back into its core.

Open Questions:

If response and request don't read its settings from application, where do they read it from?
What is the role of application when router (middleware), request, and response don't need it? Is it just a convenience for wiring things up in the "default" way?

I think this will eventually become part of https://github.com/pillarjs/extend-proto

Well, part of it. We'll probably have a separate module for the default "express" properties.

Seems related to https://github.com/expressjs/express/issues/2432 ?

I'm not sure what the state of Express 5 is, but is this something that would be up for consideration/discussion?

I think this is a good idea, @aoberoi
Especially that express.Router() is a private function, which makes testing express routes with TypeScript really difficult, unless spinning up a http server
https://github.com/expressjs/express/blob/master/lib/router/index.js#L131-L136

@kevinsimper If you'll humor me, I'm curious to learn more about your use case. I'm not sure this is the best issue to discuss this, the conversation around moving req/res out is spread out in a couple of places:

A discussion w/ a bit of history and context
Another convo
WIP PR for landing the removal

But I'm happy to inform you work has begun on moving them to their own repos. But I don't have a use case myself where this would benefit me, so detail about how you plan to use this would be valuable! I.E, what are you doing today, why is it suboptimal, and what would you prefer to be able to do?
Thank you ❤

Especially that express.Router() is a private function

express.Router() is not a private function at all. We even document it publicly all over our API docs http://expressjs.com/en/api.html

Well their included link points to router.handle, which is labeled private in the jsdoc

Well their included link points to router.handle, which is labeled private in the jsdoc

Ah. Yes, that is a private function, as the public call to that is router(req, res, next), not router.handle(req, res, next).

Thanks for the responses!
@dougwilson Did not know of router(req, res, next), I will take a look at that!
@jonchurch I want to be able to test this code and ensure that send is being called.
import express, { Request, Response } from "express";

export const app = express.Router();

app.get("/", (req: Request, res: Response) => {
  res.send("Login");
});

I can not see other ways than doing this:
import express from "express";
import fetch from "node-fetch";
import { app as loginRoutes } from "./login";

test("login", (done) => {
  console.time("start-test-server");
  const server = express();
  server.use(loginRoutes);
  const listener = server.listen(0);
  listener.on("listening", async () => {
    const address = listener.address();
    if (typeof address === "string") return done(new Error("no port"));
    const req = await fetch("http://localhost:" + address.port);
    const data = await req.text();
    expect(data).toBe("Login");
    listener.close(() => {
      console.timeEnd("start-test-server");
      done();
    });
  });
});

Which is not that easy to read, it does not look clean. And the test takes on my i7 anywhere from 27 to 41 ms to run. That is slow compared to unit tests.
With typescript it is not possible to create a Response object that does not contain all 79 properties of the response object.
Here is an example:
import express, { Response } from "express";

test("login route", () => {
  const route = (req, res: Response) => {
    res.send("Login");
  };
  const mockSend = jest.fn();
  route({}, { send: mockSend });
});

It will give you this message:
Argument of type '{ send: jest.Mock<any, any>; }' is not assignable to parameter of type 'Response<any>'. Type '{ send: Mock<any, any>; }' is missing the following properties from type 'Response<any>': status, sendStatus, links, json, and 79 more.

I don't believe that other projects should adapt to typescript, so don't think about the typescript part. I just wanted to show that I have tried other ways, but it will not work with typescript because of the difficulties of mocking large objects.

I wish I knew typescript so I could better help, but maybe this will help: the decoupling that this issue is talking about won't suddenly make request and reaponse prototypes usable outside of a http server, as it heavily relies on the state set up there.
But if you just want to make them in order to satisfy type checks, the express module already exports them for usage (no real difference than when they will be decoupled into a different module) under express.request and express.response exports.


Does your script support LIVE streaming of .m3u8 URLs?

Like the ones offered to watch Live IPTV from public sources?

Currently not. We may look at being able to add Live IPTV sources in the future but it's not a priority at this time.


Future SNES support? (Plus official mapper support)

The NES and SNES are kinda similar, NES code can run on a SNES, it'd be neat if a SNES version could be made, maybe with a option for unique tiles/sprites for the SNES to take advantage of the extra colors and such.

Oh, also it'd be neat if for the NES, you could opt into a different mapper, One that will use 16x16 Palette Attribute tiles instead of 8x8.


Unauthenticated user names do not appear on comments (_default Skin)

Whenever an unauthenticated (anonymous) user enters a comment, they are required to enter a name (which could simply be an alias or one-time screenname), but that name does not appear on the comment when the post is displayed. Instead, only a placeholder icon for an unavailable profile pic appears.
It seems that this name should be displayed, just as the display name for an authenticated user is displayed on their comments. (Sometimes a commenter may be a someone whose name is recognizable, but for whatever reason, that person has chosen not to create a site login or has simply decided to comment without logging in. In these cases, it is helpful to see the name associated with the comment.)
This behavior can be added to the template's Comment.html file as follows:
Old code:

  [commenter:displayname]

New code:

  [commenter:displayname]

The JavaScript addition works by making a couple of assumptions:

The comment's underlying CreatedByUserID field will always be set to -1 when a comment is added by an unauthenticated/anonymous user.
The old HTML code (which generates a link to the user profile) will always fail to generate any HTML for an unauthenticated/anonymous user (this code is always evaluated).

@donker is this to be closes since the PR was closed or is there still something to do with this?


fix(project-template): Fix plugins- xcconfig paths

plugins-debug.xcconfig and plugins-release.xcconfig reside
in the project directory (just above internal/)

test package_version#rc


C#: Add [Flags] attribute to core bitfield enums

Follow up to https://github.com/godotengine/godot/pull/71045

Thanks!


lengthy network lags with desktop app running on OSX

Seen on both OS X 10.10 and 10.11, running 7.2.302  (for quite some time now)
This has been difficult to pin down or get concrete data about, but it seems that when TogglDesktop is left running, I experience regular and lengthy networking lags (often over 1 minute).  It acts almost as if a major system mutex is being held.  When I exit the application, these problems seem to go away.
Nothing interesting is ever found in the console logs under "toggl", so I expect whatever happens is being reported by a system library, if at all.
Hoping that if other users are experiencing similar system/networking issues, which they hadn't correlated to running TogglDesktop, that seeing this might lead to more data points about what's actually going on.

I reported this back in June #1400  and am still seeing this behavior in 7.3.177, even though when this crops up from time to time the issue gets closed. It looks like Issue #1680 is open and this is being investigated again.

Thanks for the note. #1400 and #1680 seem to be about sync issues with toggl apps and apis themselves (which I've also experienced), but this ticket is different from them:
When the toggl desktop app is running on osx, I get a lot of SYSTEM-WIDE network hangs and lags, such as Safari can't load pages for 2 minutes (but eventually does).  But if I quit toggl, other apps work freely again.

Which is not to say the issues couldn't be related, but the symptoms are very different.  It's possible that whatever is stopping other apps from working consistently when toggl is running, MIGHT be a side-effect of toggl itself being hung while it holds a mutex.

Oh, I see. Thanks for the clarification. I am not experiencing system-wide
hangs like that—ouch! Hope you and the devs can pin it down.
On Tue, Dec 1, 2015 at 9:29 AM, Mark Taylor<EMAIL_ADDRESS>wrote:

Which is not to say the issues couldn't be related, but the symptoms are
very different. It's possible that whatever is stopping other apps from
working consistently when toggl is running, MIGHT be a side-effect of toggl
itself being hung while it holds a mutex.
—
Reply to this email directly or view it on GitHub
https://github.com/toggl/toggldesktop/issues/1673#issuecomment-161001747
.


[issue 739] Changing ng-model programmatically on multiselect.

This prevents setting null values when changing ng-model from empty value to set programmatically.
Fixes: https://github.com/angular-ui/ui-select/issues/739
(there is a demo of issue in plunker)

@KKrisu check https://github.com/angular-ui/ui-select/pull/748


Renovate/eslint config prettier 8.x

 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.1 out of 2 committers have signed the CLA.:white_check_mark: dimazuien:x: renovate-botYou have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Middle arrows in opposite direction (to currently set)

First of all, thanks for such awesome package!
History of an issue:

In my workflow I feel more logical to use "from" type of arrows

I more like middle arrows (because they don't overlap content)
I thought "from middle" get's me result I want (one middle arrow in the "from" direction), but I get this:

So, how is it possible?

First of all, thanks for such awesome package!

Thank you!!
Probably it won't work but can you try
"middle: {scaleFactor: 1}"

First of all, thanks for such awesome package!

Thank you!!
Probably it won't work but can you try
:))
"middle: {scaleFactor: -1}"
So, I have: org-roam-server-network-arrows "middle: {scaleFactor: -1}"
And the result isn't expected:

Is it working? :D

Is it working? :D

aha)
Not as I expected. I expected 1 middle arrow in the opposite direction.
And, yeah, it's working, my emacs doesn't crash :))

Did you remove "from"?

Did you remove "from"?

Yep.
Furthermore, I tried to add it a few ago. It also doesn't solve situation (it gives me 3 arrows)

Maybe the browser is caching it somehow, can you restart your computer and try again?

Probably it won't work but can you try

:))

"middle: {scaleFactor: -1}"

So, I have: org-roam-server-network-arrows "middle: {scaleFactor: -1}"
And the result isn't expected:

I've restarted my computer. All the same as I wrote above. Still 2 arrows (I want just one), still in the "wrong" direction.

This should work
(setq org-roam-server-network-arrows "middle")
(setq org-roam-server-network-vis-options
      (json-encode
       (list (cons 'edges
           (list (cons 'arrows
               (list (cons 'middle
                   (list (cons 'scaleFactor -1))))))))))

Yeah! It works.
Thanks for help and for link


Add a first_party setting

We currently have a known_first_party and known_third_party setting. This is useful, but in most use case-cases we want to specify our modules in known_first_party and all our dependencies (every else) in known_third_party, which forces us to maintain a dependency list in parallel for known_third_party. I propose introducing a first_party setting, which would supersede known_{first,third}_party if set, to allow us to just specify our modules and be done with it. It would set the first party modules as specified and mark everything else as third party.
For eg., in my project I could replace
known_first_party = build
known_third_party = nox,pallets_sphinx_themes,pep517,pytest,setuptools,toml

with
first_party = build

Since I can safely guarantee the only module I provide is build. If I was using a tests module or something similar in the tests, I could also specify it here.
What do you think?

This is exactly how finding will work in 5.0.0 (to be released tomorrow!) with the exception that it's keeping the known_first_party designation. Note that you can get this behaviour in 4.x.x as well simply by changing the default to THIRD_PARTY

Okay, so if I understand correctly what I want to do to keep 4.x compatibility, is this right?
known_first_party = build
default_section = THIRDPARTY

I had a look and it seems like you changed the default_section default to THIRDPARTY in 5.0.0, and that's why just specifying known_first_party will have the behavior I want by default, correct? I just want to make sure I understand :smile:.

@FFY00 That's exactly correct! And thanks for verifying, will also help others who stumble onto this ticket


[Feature Request] "ApplicationsController - Create controller method to update an application's properties"

Before submitting your PR for review

Run npm run lint to find errors in code syntax/format
Run npm run lint:fix to fix all auto-fixable errors in source code and auto-format with prettier
Ensure you fix any linting errors displayed after running any of the above commands

What does this PR do?
Create controller method to update an application's properties"
Fixes #280 (replace issue_number with the issue number this PR solves)
Summarise the main tasks handled in the pull request
description of Task to be completed?
"ApplicationsController - PATCH /applications/{applicationId}:
Create controller method to update an application's properties"
How should this be manually tested?
req param: applicationId. eg. => http://localhost:4000/v1/applications/5efe26ede51e4930046a1a56
request body: name (string) eg. { "name" : "my best app"}
What is the link to the issue on Github?
Issue #280

Unfortunately, it seems this task has been assigned in a separate issue/PR and this a duplicate. We may have to close this


fixed typo in mrunaal.txt

Don't forget to provide the description of the pull request. :tada: you did it!

Sorry I can't merge it! :sob:


Add npmignore

For local dev, if we under parse-sever-example and run npm install, the compiled lib folder for parse-sever will not be moved to parse-server-example/node_modules/parse-server. This is because we have lib in gitignore. Adding npmignore will allow npm to move the lib folder when we do local development. Not sure it is the best way to solve the problem. Feel free to abandon it for better solutions.

@wangmengyan95 I think the preferred method for handling this is to add a "prepublish" npm script for running the build.

Even though I also develop under parse-server-example I also feel this is a little janky. Maybe it would be better to have an "official" local development instantiation of the server in the parse-server repo. We could maybe even add an npm develop command or something like that. Thoughts?

I think this is the canonical way. Npm defaults to gitignore if there is no
npm ignore.
On Tuesday, February 9, 2016, Drew<EMAIL_ADDRESS>wrote:

Even though I also develop under parse-server-example I also feel this is
a little janky. Maybe it would be better to have an "official" local
development instantiation of the server in the parse-server repo. We
could maybe even add an npm develop command or something like that.
Thoughts?
—
Reply to this email directly or view it on GitHub
https://github.com/ParsePlatform/parse-server/pull/318#issuecomment-181973449
.

Agreed with the fact that this is a canonical way, we probably also should ignore spec and src in it, so we don't deploy tests and non-compiled source via npm.


tbb doesn't come with cmake files

Describe the bug
Tbb doesn't come with any information on how to link against it (neither pkgconfig files nor cmake files). The upstream project defines cmake files to make linking against it easier. Naturally third parties rely on this in their own cmake files. Not shipping them in the nix derivation introduces additional hassle to package software from said third parties.
Would it be a possibility to ship the cmake files together with tbb?
Notify maintainers

@thoughtpolice
@DIzFer

The following override works with 2020_U3, but fails with 2021.1.1:
  tbb = pkgs.tbb.overrideAttrs (old: rec {
    version = "2020_U3";

    src = pkgs.fetchFromGitHub {
      owner = "01org";
      repo = "tbb";
      rev = "${version}";
      sha256 = "0r9axsdlmacjlcnax4vkzg86nwf8lsx7wbqdi3wnryaxk0xvdcx6";
    };

    installPhase = old.installPhase + ''
        ${pkgs.cmake}/bin/cmake \
            -DINSTALL_DIR="$out"/lib/cmake/TBB \
            -DSYSTEM_NAME=Linux -DTBB_VERSION_FILE="$out"/include/tbb/tbb_stddef.h \
            -P cmake/tbb_config_installer.cmake
    '';
  });

https://github.com/NixOS/nixpkgs/pull/122587 added a pkg-config file.

@jtojnar Thank you, that settles it.


Composer prefilled mention - handle edge cases with DID URLs and users with invalid handles

I found that the behaviour of the composer where it prefills a mention when viewing a user's profile was producing incorrect behaviour when viewing a user with an invalid handle. This manifests in two bugs:
mobile: composer is prefilled with @invalid.handle
web: composer is prefilled with @did:plc...

This is because the compose button simply looks at the URL - this would happen when viewing a profile with a valid handle too if the DID URL is used
For the first bug, I simply added a check for handle === 'handle.invalid'. For the second one, I added a check for handle.startsWith('did:') - this is not a great solution because this does not handle accounts with valid handles viewed with their DID in the URL, but it's better than the current, broken behaviour.
Profile used for testing:
https://bsky.app/profile/did:plc:3nqrhu5mthmias3zc4a2ovzj

Appreciate it @mozzius !


[IT-1200] Restore parkmycloud

Apparently Michael Mason is still using Sage cloud resources.
Revert "SC-148 Remove parkmycloud from sandbox (#125)"
This reverts commit 740b997870b6ca40dc5f0775a89a24e9eaa9cb10.

those are big instances (C5.18xlarge)  @ahayden.  probably not a good idea to leave them running.


Sync data with upstream

This is from https://github.com/openvanilla/McBopomofo/tree/ee21be96ca5fe31b975fa58e36a6d1e045b7c4ab

Thank you so much!


FluentBit integration to send logs in multiple tools (Seq, CloudWatch, elasticache, Loki...)

Done for seq

Need to investigate logs of fluentBit. Issue with error Worker not print in Seq

Done for CloudWatch


Export C binding as a dynamic link library / shared object for testing and calling

Hi, which problem that this issue want to address? Current C binding always exported as a dynlib.

You are right.


Add 1289 editorial

@RobinHood3082 hello dear contributor, your tutorial has already been added here : https://github.com/lightoj-dev/problem-tutorials/blob/main/1289/en.md . Is there any furthermore improvement you like to include? If so, please modify the file already merged.


helm can not reachable to k3s cluster

Hi everyone,
I installed k3s using vagrant and virtual box but I can not use helm add repo command .
master:/home/vagrant # kubectl cluster-info
Kubernetes control plane is running at https://<IP_ADDRESS>:6443
CoreDNS is running at https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy

vagrant@master:~> kubectl --kubeconfig /etc/rancher/k3s/k3s.yaml get pods --all-namespaces
NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   coredns-7448499f4d-zpz72                  1/1     Running     0          8h
kube-system   local-path-provisioner-5ff76fc89d-jbh74   1/1     Running     0          8h
kube-system   metrics-server-86cbb8457f-kf9pm           1/1     Running     0          8h
kube-system   helm-install-traefik-crd-l2frh            0/1     Completed   0          8h
kube-system   helm-install-traefik-mwt7v                0/1     Completed   1          8h
kube-system   svclb-traefik-hlv5q                       2/2     Running     0          8h
kube-system   traefik-6b84f7cbc-lsnpt                   1/1     Running     0          8h

vagrant@master:~> helm --kubeconfig /etc/rancher/k3s/k3s.yaml ls --all-namespaces
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /etc/rancher/k3s/k3s.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /etc/rancher/k3s/k3s.yaml
NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
traefik         kube-system     1               2021-12-10 15:44:11.29265933 +0000 UTC  deployed        traefik-9.18.201        2.4.8
traefik-crd     kube-system     1               2021-12-10 15:44:05.119327147 +0000 UTC deployed        traefik-crd-9.18.201

vagrant@master:~> helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/vagrant/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/vagrant/.kube/config

Error: looks like "https://prometheus-community.github.io/helm-charts" is not a valid chart repository or cannot be reached: Get "https://prometheus-community.github.io/helm-charts/index.yaml": dial tcp <IP_ADDRESS>:443: connect: connection timed out

I tried the echo "export KUBECONFIG=/etc/rancher/k3s/k3s.yaml" >> ~/.bashrc  and  kubectl config view --raw > ~/.kube/config commands and they did not work in my situation. I tested whether os in virtual box  can connect to the internet or not and It can connect the internet. I can not use helm repo add command and any idea for this issue. Thank you.

helm repo add does not interact with your Kubernetes cluster at all.  For some reason your node is unable to connect to GitHub, but I'm not sure how this is related to k3s?


create

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attirbution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request addresses a currently open issue, replace the XXXXX below with that issue number.
Closes #XXXXX

@pravtni Thank you for submitting a pull request (PR). I have closed the PR and marked it as invalid for Hacktoberfest as I believe that it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


[ENG-1211] Update right nav css

Ticket: ENG-1211
Feature flag: n/a

Purpose

Fix broken right nav css
Summary of Changes

Add flex properties to RightWrapper class
Side Effects

QA Notes

I already made pushed these changes. 😆


Export errMissingFile error type

Is your feature request related to a problem? Please describe.
Feature request.
Describe the solution you'd like
Standard library exposes http.ErrMissingFile the same should be exposed by protocol. I can send a PR if this is within scope.
Describe alternatives you've considered
N/A
Additional context
This allows easy building of error handlers without performing string comparison/using errors.Is e.t.c.

Can you submit a PR? @kamikazechaser ❤


Multiple wallets feature

Here is an initial concept via @denyszayets , there are some more details that need to be flushed out on how this will function and be engineered.

Implemented in #401


Refactor code for agentic solver

embedvec_tools.py too large and
tools.py contaions only a couple of needed functions.,
functions in utils.py are not used.

Maybe partition code into the following modules:

Workflow definition and control routing  (workflow.py)
puzzle solver tools, recommenders, setup (puzzle_solver.py)
utils like functions to interact with the external world (utils.py or interactions.py)

Define class structure?

Closed by #67


run doctests automatically

run the python doctests automatically before we merge back into main to make sure documentation is mostly up to date.

we'll do it like this https://github.com/es-ude/elastic-ai.creator/blob/97685d52133cefb359c6c8b061b7b13782bdeccf/elasticai/creator/tests/vhdl/test_templates.py#L88


Custom domain activation hangs for several hours, no error report

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d1ttfd4k33ww29
Region
us-east-1
Step
Domain activation
Status
No report
Issue or question
My custom domain passes the SSL creation and configuration stages and hangs at the domain activation stage for several hours without reporting failure or any error.
Error message
No error message.
Additional information
I have configured the domain activation CNAME in my provider's dns records too.

Yes, I have checked that and everything possible and re-tried adding it several times but to no avail.

It worked after several retries. Thanks.


Version 4.5.2 is marked as being for 1.20-1.20.4 on Modrinth

https://modrinth.com/mod/villager-names/version/4.5.2 is marked as being for 1.20–1.20.4 when it causes a crash on world creation on 1.20.1 due to the embedded cardinal-components-level 5.4.0, which is for 1.20.4. The title of the mod version also suggests that v4.5.2 is only for 1.20.3/1.20.4.

Duplicate of #61


Credential with issuer not in registry, selecting Issuer crashes LCW

Credential, with issuer not in registry, crashes LCW in iOS and Android v2.0.9-build 64.
I'm not sure where the problem may lie. Might be because the issuer isn't in a registry or something to do with the test credential itself.
To reproduce:

Add test credential from one of the set Kayode put together, namely criteria-markdown-combo
Preview the credential you added
Select the Issuer name from the Credential Preview screen, LCW crashes

To confirm if fixed: Should be able to add test credential from Kayode's set, with an issuer not in a registry and see the details

After attempting to replicate I found the following:

Android will crash when clicking on issuer, I think this may be related to the issue I found here: https://github.com/digitalcredentials/learner-credential-wallet/issues/496
iOS does not crash

Update: after doing a fresh pull of main today (commit 7175555) and a fresh run of npm install and can no longer replicate

Closing for now. Thanks!


add test case for zero timeout

Codecov Report

Merging #15 (334ac0d) into main (a4de1be) will increase coverage by 0.76%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
+ Coverage   83.30%   84.07%   +0.76%
==========================================
  Files          11       11
  Lines         653      653
==========================================
+ Hits          544      549       +5
+ Misses         93       89       -4
+ Partials       16       15       -1

Impacted Files
Coverage Δ

pkg/proxy/proxy.go
85.82% <66.66%> (+3.93%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Windows compilation fails

Compiling an application using this library to a windows binary results in the following build errors
GOOS=windows GOARCH=amd64 go build
# github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream
vendor/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/client.go:97:38: cannot use int(fd) (type int) as type syscall.Handle in argument to syscall.SetsockoptInt
vendor/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/client.go:104:37: cannot use int(fd) (type int) as type syscall.Handle in argument to syscall.SetsockoptInt

Thank you for reporting the issue.
Actually, we did not try to compile the lib in Windows.
I will looking on it

The problem is about the syscall.SetsockoptInt interface, in Linux/Darwin is:
func SetsockoptInt(fd, level, opt int, value int) (err error) {

in windows is:
func SetsockoptInt(fd Handle, level, opt int, value int) (err error) {}


Tag and add to packagist

I'm looking to rely on this for amazons3 module. However, only having a master branch will lead to problems for anyone not wanting to install dev packages. We'll also need to manually add the repo to composer.json, since the repository name doesn't match the repository name.
Any chance this can be tagged and packaged up?

For anyone else, I've put up a tag in my fork. You still have to add the repositories line, but at least it will prevent pulling in dev branches in other projects.
https://github.com/deviantintegral/drupal-doctrine-cache/releases/tag/0.1

I've tagged v0.0.1(https://github.com/Capgemini/drupal-doctrine-cache/releases/tag/0.0.1) - the library is already on packagist at https://packagist.org/packages/capgemini/drupal_doctrine_cache

And the tag is now pushed to packagist - thanks @deviantintegral


SyntaxError: Unexpected token A in JSON at position 0

fetchival doesn't work?
index.min.js:1 Uncaught (in promise) SyntaxError: Unexpected token A in JSON at position 0

Tested with locale file and https://rawgit.com external

Looks like it was data dependent...