Separate framework from typed classes

This is an initial change to move the infrastructure of the SDK to a separate assembly. This is done in a way that will not break the current set up by defining type forwards from DocumentFormat.OpenXml to the new DocumentFormat.OpenXml.Framework assembly. This is a WIP and updates will be pushed to the PR as progress is made. The change is expected to be made before 2.18.0 and is a precursor to any changes to separate out by document type (word/excel/powerpoint).

/azp run

Blocked by #1185


Conventions do not get applied to custom test tasks

If I create a SoapUI test task of type TestTask, I expect that the conventions get applied to those tasks too. Currently that does not happen, thus I have to redeclare everything I already set by default in the soapui.test extension. Because the method that takes care of what I need is private in the plugin code, I cannot even reuse it.
Please also initialize extension properties designed to hold arrays with empty arrays so that we can just add values without having to remember whether the property is still null or not.

I think project not in a maintenance mode...
@willis7 are you planning finish it’s transfer?


Create janus api client

Ticket 104427028

@rjkip @DRvanR

Minor nitpick, the rest seems ok, :+1: from me.

Minor nitpick, the rest seems ok, :+1: from me.

@DRvanR @rjkip

:+1:


⚠ Minecraft has degraded performance

In ba4eb85, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1224 ms

Resolved: Minecraft performance has improved in 2dbe195.


Grub Editor not launching - Manjaro GNOME

Traceback (most recent call last):
File "/opt/grub-editor/main.py", line 66, in
main_()
File "/opt/grub-editor/main.py", line 56, in main_
main.main()
File "/opt/grub-editor/main.py", line 2018, in main
MainWindow=Ui()
File "/opt/grub-editor/main.py", line 546, in init
self.setUiElements(show_issues=True)
File "/opt/grub-editor/main.py", line 965, in setUiElements
if float(timeout)==0:
ValueError: could not convert string to float: 10

The issue has already been fixed the only thing needed right now is another release.
Anyway thank you for reporting the issue

Another update has been released :partying_face:
Try updating and please report if you still get the error


Fix Chart.js v3 compatibility

Chart.js seems to use Chart.register, while v2 uses Chart.plugins.register.
This fixes registering the Color Schemes Plugin in Chart.js v3.

Check this out: https://github.com/nagix/chartjs-plugin-colorschemes/issues/28, looks like there may be one other change to make with the options

This PR should address this issue: https://github.com/nagix/chartjs-plugin-colorschemes/issues/28
@nagix would you be able to take a look here real quick? This seems like a non-breaking change and having Chart.js v3+ support would be awesome. I'm willing to test out the new version whenever it's ready!

I think this is already covered by this one? https://github.com/nagix/chartjs-plugin-colorschemes/pull/26

@s4m0r4m4 #26 does not solve the problem addressed by this Pull Request.
While #26 fixes Chart.JS 3 compatibility of the beginUpdate methode, this Pull Request fixes the plugin registration automatism.

Oh I see, you're right. @nagix any chance we can get eyes on this?

looks like there is some more that needs to be fixed before you can use this with V3, in V3 the way of import Chart.js has changed with Treeshaking so import Chart from 'chart.js' wont work. You need to use treeshaking to import it like so: import { Chart } from 'chart.js'.
Also Chart.helpers does not exist anymore. You need to import the specific helpers with treeshaking from 'chart.js/helpers'


support for bgzipped and tabix-indexed map files

my impression is that reading map files is already really fast, but this could be one option to make it faster (especially when running on it on specific regions) and reduce the amount of space required on disk
unfortunately, map files are currently space-delimited, so we would have to somehow add support for tab-delimited map files since tabix only supports tab-delimited files (I think)

we can also add support for indexing them via the index subcommand


Bulk Insert does not respect identity insert option

The best way to explain this is with code. The following works I can insert a value into an identity column
  using (var scope = new TransactionScope(TransactionScopeOption.Required, TimeSpan.FromSeconds(5 * 60)))
                        {

                            foreach(var item in results)
                            {
                                Simple.Data.Database.
                                OpenConnection(destionationDBConnectionString).
                                WithOptions(new Simple.Data.Ado.AdoOptions(commandTimeout: (5 * 60), identityInsert: true))
                                [this.destinationTableName].Insert(item);
                            }
                            scope.Complete();
                        }

This does not. The table puts in the identity value:
     using (var scope = new TransactionScope(TransactionScopeOption.Required, TimeSpan.FromSeconds(5 * 60)))

                            Simple.Data.Database.
                            OpenConnection(destionationDBConnectionString).
                            WithOptions(new Simple.Data.Ado.AdoOptions(commandTimeout: (5 * 60),identityInsert: true))
                            [this.destinationTableName].Insert(results);
                            scope.Complete();
                        }

I will try and examine the code and see if it can be fixed easily.

I have found the  issue in the SqlBulkInserter and corrected it on a Forked version. While searching for the issue I noticed that the master branch version does not match the version on Nuget. The reason I even checked the version in the first place was the unchanged Forked code from master wasn't behaving the same as the code on Nuget. Does anyone know why this is the case?


UnsatisfiedLinkError

When I enter person name and pressing Next Button, it throws  java.lang.UnsatisfiedLinkError: dlopen failed: library "../../lib/libtbb.so" not found .
at line faceRecognizer =  com.googlecode.javacv.cpp.opencv_contrib.createLBPHFaceRecognizer(2,8,8,8,200);
for this I changed I to faceRecognizer = com.googlecode.javacv.cpp.opencv_contrib.createEigenFaceRecognizer(10,123.0);
also.
But did't work.
Please Help

@bha2020 have you found any solution? i tried using javacpp 1.2.1 but it is throwing compile time error as below
error: cannot access Pointer class file for com.googlecode.javacpp.Pointer not found |
-- | --
error: cannot access IntPointer class file for com.googlecode.javacpp.IntPointer not found |
cultoftheunicorn/marvel/PersonRecognizer.java |
-- | --
error: cannot access Pointer class file for com.googlecode.javacpp.Pointer not found |
error: cannot access IntPointer class file for com.googlecode.javacpp.IntPointer not found |
if any solution found plz share...

please help on this error

Alguna solucion?

Did you guys find any solution to this? I'm facing the same error in this project

guys, please....


Pr multiple idl files

When trying to add a second .erpc IDL file into our project, we found two problems.

When trying to include two *_server.h header files, the same #ifndef/#define ERPC_TYPE_DEFINITIONS/#endif was used to guard the definition of different types.  As a result, the types enclosed in this #ifndef in the second header file included were being hidden.  The solution I came up with was to put the filename of the IDL file into the #ifdef.

The help information for erpcgen indicated that it supported passing multiple .erpc files, but the implementation only processed the first file.  I added a change to loop over all files passed to erpcgen.  I believe this is necessary because if erpcgen is invoked once per .erpc file, it seems that the service IDs are re-used.

Hi, thank you for your PR. Could you create and send short example of erpc files to demonstrate your use case?

@Hadatko: I have provided an example that demonstrates the issue here: https://github.com/dpfrey/erpc_examples/tree/master/two_interfaces
You should be able to run something like this to build it: ERPC_ROOT=~/sw/erpc/f2787e8b0e6f46eb6df6dea3e6c34213256a8faa make, but you will require the commits from this PR in order to build it successfully.

@dpfrey , have you tried to use the @group annotation as described at https://github.com/EmbeddedRPC/erpc/wiki/IDL-Reference and used in https://github.com/EmbeddedRPC/erpc/blob/develop/test/test_arbitrator/test_arbitrator.erpc ? @Hadatko , what was the original intention, using the @group annotation or supporting multiple eprc files being provided via the command line? The only reference about supporting multiple files on the command line is the one from the erpcgen help display:
usage: erpcgen.exe [-?|--help] [-V|--version] [-o|--output ]
[-v|--verbose] [-I|--path ]
[-g|--generate ] [-c|--codec ] files...
Thanks.

My thinking was that it would make sense to be able to define unrelated APIs in different IDL files. I guess I could just put the unrelated definitions into the same file, but that seems worse from the perspective of trying to keep things organized.

Hi, did you consider include erpc1.idl file in erpc2.idl file?

I would close this PR due to wrong usage of erpc files.
Sorry for obstruction.

agree


Dsa v2

It looks like some code has been already pushed to npm registry before landing to master
See #47


Windows filebeat install doesn't execute Exec["install ${filename}"]

When using the module to install version 6.2.4 on Windows, it appears that the install ${filename} exec doesn't get run.  As a result the service isn't installed.
I'll work on doing some further debugging - but it seems like the refresh event doesn't seem to trigger the exec.
Perhaps it can be changed to only run if the service isn't installed, with an onlyif for example.  It shouldn't cost too much resource to do a get-service filebeat
I'll see if I can get it working and submit a PR if that will help.

Thanks for finding the problem. I'm not a Windows user/admin/dev at all and someone else added Windows support in a PR. I'd very much appreciate any help on this or any other Windows things.

I've got something working (but it requires chocolatey to install the package).  Chocolatey installs the package in a non-standard location (which is apparently standard for chocolatey), but it appears to work.
Is switching to chocolatey an acceptable approach for Windows installation (please say yes!!)?

I don't see any issue with using Chocolatey. Is Chocolatey widely used enough to where it would make sense to completely replace the file download method, or should we leave it in there and just note that it might not work as smoothly as the package install?

The filebeat chocolatey package has had nearly 10,000 downloads of the latest version since April, which i think makes it reasonably popular.
However I do think that the non-standard install location might prove to be a sticking point, and removing the manual download method entirely is probably a bit extreme! Let me try to add a parameter to control the installation method - it will be quite complex due to the change in installation path.

I've opened #171 which replaces the old method with chocolatey (and updates facts and tests).
As I mentioned above, I can work on adding a $install_provider param (or similar) to allow to select how the installation is done

I'm not sure if it is related but i thought i was experiencing this issue where it was not running. After some debugging i found that the version of puppetlabs/powershell I was using (2.0.2) at the time had a bug that did not respect cwd. I have upgraded to 2.2.0 and it appears to be working as of now.

Thanks! That sounds really promising, and might explain why others have indicated (in the PR) that there wasn’t a problem. I’ll do some more testing and we can hopefully close this with an update to the dependency metadata

Here is the ticket that pointed me in this direction. https://tickets.puppetlabs.com/browse/MODULES-3565

Thanks! I checked this out and it was indeed a bug with the powershell module.  I've bumped the powershell module and everything works again


engine: change go sdk cache mounts to be locked mode

Trying out a possible mitigation to https://github.com/dagger/dagger/issues/8031 (which is pending on an upstream go issue).
This changes the cache mounts for the Go SDK to be mode Locked, rather than Shared. This means that only one invocation of the Go SDK can run at a time (though the cache mount will still be re-used across different invocations).
The Go bug is not root caused, so it remains to be seen if this even actually avoids the problem. Will require a bunch of re-runs of CI in this PR.
If it does seem to disappear, then we have may a somewhat tough decision to make since it's highly likely that this change will hurt performance:

On one hand, obviously we want to this bug to be mitigated
On the other hand, we have only seen this in our own CI, so it's mostly likely highly rare for our real-world users to hit it. So it's unclear if the performance hit is really worth it.

One possibility would be to make this configurable somehow on the engine and only enable locked mode in our CI.

Hmm... all the CI test workflows timed out with changing the mode to Locked, so I'm gonna rule that out as non-viable in terms of the performance impact for now.
I will try mode Private instead

There does seem to be meaningful slowdown with Private cache volume mode, though not as devastating as with Locked (some workflows seem like a minute slower, though noisy so hard to really tell yet).
@rajatjindal had the good suggestion to try disabling the module index as go devs did in the upstream issue (https://github.com/golang/go/issues/69179#issuecomment-2323300381) so will give that a shot too to see what the practical impact is

Hm disabling the module index doesn't appear to have much effect on the runtime across a few runs so far 🤷♂🎉
I asked the go devs what the implications are of GODEBUG=goindex=0 in the upstream issue; it appears to be an undocumented setting (unless my googling is failing me).
I'm a little wary of setting undocumented feature-flags in our production code, but we could make this a system env var (similar to our existing support for GOPROXY) and just set it in our CI for now?
I'll setup the plumbing for that here and do some more re-runs while waiting to hear back from them.

:shipit:

Yeah, glancing through the source code for the mod index (which is wayyyy more complex than I have time to dive into right now), it's just a cache for https://pkg.go.dev/go/build#Context.Import - if the cache is disabled, we just fetch this data from the filesystem each time.
If we don't see a meaningful performance drop in the test runtime, no objection here, since the flakes are reasonably blocking - though obviously let's follow the upstream issue and help out where we can.

One thing that did stand out weirdly to me though: https://github.com/golang/go/blob/64a5d1d7de14ad74b1a77614de0e17c659ef12b6/src/cmd/go/internal/modindex/read.go#L73-L77
This feels very very similar to the case we saw for uv in https://github.com/dagger/dagger/issues/7662#issuecomment-2312903772. Because everything is mounted at /src (the value of goSDKUserModContextDirPath), then I guess it's possible that we produce a ton of similar hashes? And then potentially something gets into a bad state from there (the docs for protect/unprotect do state that it might not be used for trivial accesses?).
@sipsma WDYT about trying our python fix for go, and seeing if that improves the flakes? That feels potentially a bit less invasive, and also if it is that, would help narrow down the go investigation as well?
Approving regardless though, will let you make the call here!

@jedevc good find, that's definitely suspicious! I think what I'll do is merge this one as is and open a follow-up PR where I try replacing this approach with that one. The main reasons being that A) I'd like to get a potential fix out ASAP and B) I think the other approach actually is (debatably) more invasive in that it's a meaningful change to the production code (whereas this one does it in such a way that only our test suite will have the module index disabled for now).


🐛 | bookworm: check for raspian not working

Version
3.5.3
Branch
future3/main
OS
Raspberry Pi OS Bookworm Lite
Pi model
Zero 2W
Hardware
No response
What happened?
When running the installer script, it fails saying
ERROR: '<something>' found more than once in 'unknown'

Where <something> is not always the same thing.
I tracked it down, the problem is the check for Raspian here.
Newer releases of Raspberry Pi OS (bookworm) do not display raspian in /etc/os-release no more, but just debian. So there is no way to really tell if we are on Raspberry Pi OS.
I have found articles that propose to check the existence of /etc/apt/sources.list.d/raspi.list to determine if we are on Raspberry Pi OS. Although this is obviously not perfect either, it might be a better solution than consulting /etc/os-release for the future.
Logs
No response
Configuration
No response
More info
No response

This only seems to affect bookworm 64bit. bookworm 32 bit shows raspian, as usual.

At this time 64bit is not supported (there's also a check for it).

I know that, but I'm always interested in trying things out. ;-)
Basically, bookworm/64bit is already running quite decent. It's just little things; but I think it's important to track them, even if the software is currently not supporting it. That might save a bit of work for future later. :wink:

Basically, bookworm/64bit is already running quite decent. It's just little things; but I think it's important to track them, even if the software is currently not supporting it. That might save a bit of work for future later. :wink:

I agree.
We also happily discuss possible changes for a working 64bit implementation, so if anybody opens a PR with necessary changes interested people could review it.
I know @alesrosina did also make it work (see #2313)

Basically, bookworm/64bit is already running quite decent. It's just little things; but I think it's important to track them, even if the software is currently not supporting it. That might save a bit of work for future later. 😉

I agree.
We also happily discuss possible changes for a working 64bit implementation, so if anybody opens a PR with necessary changes interested people could review it. I know @alesrosina did also make it work (see #2313)

Yes, basically I just removed all checks in setup script. And then it's running as it should on 64bit.
I probably should take the time to make a PR, but probably not before autumn, since in summer time i prefer to be outside in my free time ;)

I can prepare a PR to lift the 64 bit restriction. It would only be a change in the install-jukebox.sh (removing _check_os_type) and the thing with the Raspian check. There I would then use an or-condition in terms of "Either the os-release property ID contains raspian or the file /etc/apt/sources.list.d/raspi.list exists and contains corresponding raspian sources".
I've found no other issues with 64 bit. The GPIO Problems with kernel 6.6 upwards mentioned in the other issue are not specific to 64 bit, but also affect 32 bit, right? So that wouldn't be a show stopper for lifting 64 bit restriction, I think.

I can prepare a PR to lift the 64 bit restriction. It would only be a change in the install-jukebox.sh (removing _check_os_type) and the thing with the Raspian check. There I would then use an or-condition in terms of "Either the os-release property ID contains raspian or the file /etc/apt/sources.list.d/raspi.list exists and contains corresponding raspian sources".
I've found no other issues with 64 bit. The GPIO Problems with kernel 6.6 upwards mentioned in the other issue are not specific to 64 bit, but also affect 32 bit, right? So that wouldn't be a show stopper for lifting 64 bit restriction, I think.

Yes, from my experience that's correct :+1:

@mittler-works did you manage to create a PR for this?

Sorry, that got lost in the daily grind. :wink:
I have just created the PR. :wave:

Thank you!
On Mon, 16 Sept 2024 at 07:39, Nils Mittler @.***>
wrote:

Sorry, that got lost in the daily grind. 😉
I have just created the PR. 👋
—
Reply to this email directly, view it on GitHub
https://github.com/MiczFlor/RPi-Jukebox-RFID/issues/2402#issuecomment-2352117462,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3HHMSWSWN6UBQBABJMWIK3ZWZ4JNAVCNFSM6AAAAABK2PG6EKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJSGEYTONBWGI
.
You are receiving this because you commented.Message ID:
@.***>

With pleasure :)
But one other thing I would like to discuss: the error message you get when you are not on Raspberry Pi OS is not meaningful at all (see OP of this issue).
The problem origins in getting the boot and cmdline file paths. When the raspbian check (maybe it should be Raspberry Pi OS Check today? Thats also the reason why there is not always "raspbian" in /etc/os-release) returns false, then _get_boot_file_path just returns unknown instead of stopping the execution with a failure. So the routine continues as usual and if you want to write or do something with the returned path, it fails with curious error messages.
My proposal would be, that the function should write a meaningful error message to stderr and exit with non-zero exit code. I don't know if there is any kind of logger and/or exception handling implemented in the installer scripts. If not, it would be as easy as echoing to stderr and exit.

My proposal would be, that the function should write a meaningful error message to stderr and exit with non-zero exit code. I don't know if there is any kind of logger and/or exception handling implemented in the installer scripts. If not, it would be as easy as echoing to stderr and exit.

yes, we do.
please check here
https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/f2a1730a8df693350aef14aa6df6f563ffe6f786/installation/install-jukebox.sh#L42-L87

Fixed in #2425


Creative tab order is really funky

Seemingly nondeterministic. According to tterrag it shouldn't be doing this, but I must be doing something weird.
Since I'm doing something weird, I've decided to sort the list until I figure out why I'm weird.

This will be fixed in next release.


Progress bar text for IE11 not displaying correctly

I'm trying to display some text inside a progress bar using bootstrap v4, but this doesn't seem to work with IE11.
Here's a fiddle
Here is the result in Firefox 59 or Chrome 65:

And here it is for IE11:

Hi mdigi,
You are telling the browser to position the element absolute, however, if you don't specify top,right.bottom,left properties IE-11 will set the values to "auto" resulting in this offset.
By giving the parent a relative position, we make sure the absolute child  tag cannot escape.
By applying a top: 0 on the  tag we make sure there is no offset.
Take a look at the updated fiddle, I'm not sure if this can be fixed with B classes instead of applying the top manual though, but i hope this fixes your issue for the time being :)
~Wouter

Yes, that works! Thank you.


bump x/sys to fix riscv64 epoll

Bump x/sys to https://github.com/golang/sys/pull/40.
Fixes https://github.com/moby/moby/issues/39461 and https://github.com/containerd/containerd/issues/3389.
Nice catch @tonistiigi

Codecov Report

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

@@            Coverage Diff             @@
##           master    #3526      +/-   ##
==========================================
+ Coverage   44.27%   44.29%   +0.02%
==========================================
  Files         124      124
  Lines       13682    13682
==========================================
+ Hits         6058     6061       +3
+ Misses       6688     6686       -2
+ Partials      936      935       -1

Flag
Coverage Δ

#linux
48.05% <ø> (ø)
:arrow_up:

#windows
39.79% <ø> (+0.02%)
:arrow_up:

Impacted Files
Coverage Δ

gc/scheduler/scheduler.go
68.75% <0%> (+1.44%)
: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 ea13c9f...3ef26cd. Read the comment docs.

LGTM


Feature/update cdap site

Add new 4.0 properties.

Note that I also added a property in this PR (merged ~18 hours ago):
https://github.com/caskdata/cdap/pull/7354

:+1: LGTM


boop!

:disappointed:

Hmmm I’ll have a look to find out why this failed tomorrow https://github.com/gr2m/boop-gregors-nose/runs/2670891832?check_suite_focus=true#step:5:6

Fixed via https://github.com/gr2m/boop-gregors-nose/commit/7f8a2da19ba31896fa47d76364bd2c8bda87012b. Happy booping!


Add a method in the types to check whether there is no decoration on a type.

@antiagainst

@antiagainst  updated

+2

I want to see tests for this kind of thing.

@dneto0: Oh, my fault. I should requested that. So, I write it here: #378.


Canvas and font fingerprinting

Hello,
HTML5 Canvas and fonts fingerprinting is can be blocked? Is it possible to add such functions like a part of antitracking protection?
Thank you.
Best regards.

@ammnt we are considering such a possibility, but for now this feature is under development with an indefinite timeframe


Dimensional issue of subclassed object in nested branches

Sorry for the weird issue title, we can change it later, I could not find a better one 😉
I need some help parsing a fairly simple data structure. It derives from a class which has:
struct AAObject : public TObject
{
  std::vector<double>      usr;              ///< user data
  std::vector<std::string> usr_names;        ///< user keys

These two vectors are used to store arbitrary data, so that e.g. usr_names = ["bx", "by", "ichan", "cc"] and the corresponding values are at the specific indices. So if you need to look up the value for "by", you look up the index of it and then access usr[idx].
So far so good, it works for "one dimensional" (flat) branches. Here, the event of class Evt derives from that AAObject and the the branch Evt simply contains a flat vector of Evt instances (3 of them) and each event contains 17 "usr entries":
[ins] In [1]: import uproot

[ins] In [2]: f = uproot.open("usr-flat.root")

[ins] In [3]: f['E']['Evt']['usr_names'].array()
Out[3]: <ObjectArray [[b'RecoQuality', b'RecoNDF', b'CoC', b'ToT', b'ChargeAbove', b'ChargeBelow', b'ChargeRatio', b'DeltaPosZ', b'FirstPartPosZ', b'LastPartPosZ', b'NSnapHits', b'NTrigHits', b'NTrigDOMs', b'NTrigLines', b'NSpeedVetoHits', b'NGeometryVetoHits', b'ClassficationScore'] [b'RecoQuality', b'RecoNDF', b'CoC', b'ToT', b'ChargeAbove', b'ChargeBelow', b'ChargeRatio', b'DeltaPosZ', b'FirstPartPosZ', b'LastPartPosZ', b'NSnapHits', b'NTrigHits', b'NTrigDOMs', b'NTrigLines', b'NSpeedVetoHits', b'NGeometryVetoHits', b'ClassficationScore'] [b'RecoQuality', b'RecoNDF', b'CoC', b'ToT', b'ChargeAbove', b'ChargeBelow', b'ChargeRatio', b'DeltaPosZ', b'FirstPartPosZ', b'LastPartPosZ', b'NSnapHits', b'NTrigHits', b'NTrigDOMs', b'NTrigLines', b'NSpeedVetoHits', b'NGeometryVetoHits', b'ClassficationScore']] at 0x7f1b8fa2a880>

[ins] In [4]: f['E']['Evt']['usr_names'].array()[0]
Out[4]:
[b'RecoQuality',
 b'RecoNDF',
 b'CoC',
 b'ToT',
 b'ChargeAbove',
 b'ChargeBelow',
 b'ChargeRatio',
 b'DeltaPosZ',
 b'FirstPartPosZ',
 b'LastPartPosZ',
 b'NSnapHits',
 b'NTrigHits',
 b'NTrigDOMs',
 b'NTrigLines',
 b'NSpeedVetoHits',
 b'NGeometryVetoHits',
 b'ClassficationScore']

[ins] In [5]: f['E']['Evt']['usr'].array()[0]
Out[5]:
array([8.54595724e+01, 3.70000000e+01, 1.18630282e+02, 8.25000000e+02,
       1.76000000e+02, 6.49000000e+02, 2.13333333e-01, 3.75196777e+01,
       1.35294997e+02, 9.77753193e+01, 5.10000000e+01, 3.00000000e+01,
       7.00000000e+00, 6.00000000e+00, 0.00000000e+00, 0.00000000e+00,
       1.68633822e-01])

[ins] In [6]: len(f['E']['Evt'])
Out[6]: 3

The problem appears with classes which have instances in nested branches. This means that for example the Trk class, which also derives from AAObject and is part of the Evt branch. Each Evt entry has a variable length of Trks, as seen here (just the relevant parts):
struct Evt: public AAObject
{
...
  std::vector<Hit> hits;        ///< list of hits
  std::vector<Trk> trks;        ///< list of reconstructed tracks (can be several because of prefits,showers, etc).
...

The Trk class itself is also quite straight forward and consists of some attributes:
struct Trk: public AAObject
{
  int    id;                          ///< track identifier
  Vec    pos;                         ///< postion of the track at time t
  Vec    dir;                         ///< track direction
  double t;                           ///< track time (when the particle is at pos )
...

The file usr-nested contains a few events and every event contains multiple Trk instances. Only the first two Trk entries should have some entries in the usr* attributes, the first one by, bx, ichan and cc, the second one only energy_lost_in_can. The structure of the arrays however I get back from uproot are all one dimensional per event. It seems that only the first entry is extracted and also the length of the arrays seems a bit "random".
This is what I get:
[ins] In [34]: import uproot

[ins] In [35]: f = uproot.open("usr-nested.root")

[ins] In [36]: f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array()
Out[36]: <ObjectArray [[b'bx', b'by', b'ichan', b'cc'] [b'bx', b'by', b'ichan', b'cc'] [b'bx', b'by', b'ichan', b'cc'] ... [b'bx', b'by', b'ichan', b'cc'] [b'bx', b'by', b'ichan', b'cc'] [b'bx', b'by', b'ichan', b'cc']] at 0x7ff1e6587040>

[ins] In [37]: f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array()[0]
Out[37]: [b'bx', b'by', b'ichan', b'cc']

[ins] In [38]: f['E']['Evt']['mc_trks']['mc_trks.usr'].array()[0]
Out[38]:
array([ 4.86920000e-002,  5.88460000e-002,  3.00000000e+000,
        2.00000000e+000,  2.65507278e-314, -9.07373616e+207,
        0.00000000e+000,  0.00000000e+000,  0.00000000e+000,
        0.00000000e+000,  0.00000000e+000,  0.00000000e+000,
        0.00000000e+000,  0.00000000e+000,  0.00000000e+000])

[ins] In [39]: f['E']['Evt']['mc_trks']['mc_trks.pos.x'].array()[0]
Out[39]:
array([32.263, 32.263, 32.263, 32.263, 32.263, 32.263, 32.263, 32.263,
       32.263, 32.263, 32.263, 32.263, 32.263, 32.263, 32.263, 32.263,
       32.263, 32.263, 32.263, 32.263, 32.263])

[ins] In [40]: f['E']['Evt']['mc_trks']['mc_trks.pos.x'].array()[0].shape
Out[40]: (21,)

What I expect, is that the following line returns a nested list, where the first nested list has a length of 4, the second 1 and all others are empty. I however get 15 single entries and the first 4 entries correspond to the first track (and the values are OK):
[ins] In [38]: f['E']['Evt']['mc_trks']['mc_trks.usr'].array()[0]
Out[38]:
array([ 4.86920000e-002,  5.88460000e-002,  3.00000000e+000,
        2.00000000e+000,  2.65507278e-314, -9.07373616e+207,
        0.00000000e+000,  0.00000000e+000,  0.00000000e+000,
        0.00000000e+000,  0.00000000e+000,  0.00000000e+000,
        0.00000000e+000,  0.00000000e+000,  0.00000000e+000])

The array elements apart from the first 4 values seem to be random memory bits.
I tried to figure out why the data is parsed incorrectly but I failed so far. I also did not found the word energy_lost_in_can in the usr_fields (converted to string etc.), so I guess it is lost somewhere in the low level parsing in uproot.
This is what the ROOT based library spits out for the first event (all 21 tracks, the first one with 4 usr-entries, the second with 1 and every other with no entries):
Trk: id=0 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.669588 -0.539513 0.510467 t=0 E=67.213 pdg-type=14
0 	 bx : 	 0.048692
1 	 by : 	 0.058846
2 	 ichan : 	 3
3 	 cc : 	 2
Trk: id=1 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.663003 -0.546697 0.51142 t=0 E=63.347 pdg-type=-13
0 	 energy_lost_in_can : 	 63.2413
Trk: id=2 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.19609 -0.948629 -0.248297 t=0 E=1.2184 pdg-type=2212
Trk: id=3 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.126922 -0.514083 0.848298 t=0 E=0.9756 pdg-type=2212
Trk: id=4 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.201009 0.875771 0.438886 t=0 E=1.264 pdg-type=2212
Trk: id=5 pos=Vec:32.263 10.292 117.624 dir=Vec:0.03499 -0.730037 -0.682511 t=0 E=1.1212 pdg-type=2212
Trk: id=6 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.013096 0.280756 0.95969 t=0 E=1.0763 pdg-type=2212
Trk: id=7 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.549502 0.013973 0.835376 t=0 E=1.0252 pdg-type=2212
Trk: id=8 pos=Vec:32.263 10.292 117.624 dir=Vec:0.882835 -0.235994 0.406091 t=0 E=1.0421 pdg-type=2212
Trk: id=9 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.944463 -0.174758 -0.278297 t=0 E=0.99328 pdg-type=2112
Trk: id=10 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.801781 -0.360305 0.476789 t=0 E=1.9418 pdg-type=2112
Trk: id=11 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.488549 -0.831056 0.26583 t=0 E=1.3408 pdg-type=2212
Trk: id=12 pos=Vec:32.263 10.292 117.624 dir=Vec:0.221472 -0.012973 0.97508 t=0 E=1.0457 pdg-type=2112
Trk: id=13 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.7151 0.448516 -0.536158 t=0 E=1.0784 pdg-type=2112
Trk: id=14 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.837188 0.317147 -0.445571 t=0 E=1.0119 pdg-type=2112
Trk: id=15 pos=Vec:32.263 10.292 117.624 dir=Vec:0.960773 0.064413 0.269754 t=0 E=1.054 pdg-type=2112
Trk: id=16 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.878487 0.279885 -0.387201 t=0 E=0.15467 pdg-type=22
Trk: id=17 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.463415 0.821182 -0.333027 t=0 E=0.16669 pdg-type=11
Trk: id=18 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.468878 0.822227 -0.32264 t=0 E=0.085231 pdg-type=-11
Trk: id=19 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.870512 -0.390102 -0.30005 t=0 E=0.25603 pdg-type=22
Trk: id=20 pos=Vec:32.263 10.292 117.624 dir=Vec:-0.531486 -0.838616 0.119353 t=0 E=0.14464 pdg-type=22

Do you have any idea, or is this a known issue with nested vectors?
I attached both files in case you want to have a look.
usr.zip

My understanding of your problem is that (a) you expect multidimensional arrays for f['E']['Evt']['mc_trks']['mc_trks.usr'] in each event but get a one-dimensional array in each event and (b) the lengths of these arrays are too long.
On (a), I would expect a one-dimensional array in each event. The Evt struct contains a single std::vector<Trk> trks and that Trk is flat: just an int, a Vec (which gets split into .x, .y, .z branches) and a double. I only count one dimension there—maybe I've misunderstood you?
On (b), I can see the problem: the extra values are physically in the ROOT file, but the length of your std::vector is specified to be shorter than what has been written. You can see it with the uproot.asdebug interpretation:
>>> f['E']['Evt']['mc_trks']['mc_trks.usr'].array(uproot.asdebug)[0]
array([ 64,   0,   0, 126,   0,   9,   0,   0,   0,   4,  63, 168, 238,
        40, 103,  39,  86, 134,  63, 174,  33,  16,  27,   0,  54, 135,
        64,   8,   0,   0,   0,   0,   0,   0,  64,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   1,  64,  79, 158, 226, 235,  28,
        67,  45,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0],
      dtype=uint8)

The first 6 bytes (64,   0,   0, 126,   0,   9) are STL header, the next 4 bytes (0,   0,   0,   4) is the length of the array, and the rest is both real data and not-real data. The interpretation for this branch,
>>> f['E']['Evt']['mc_trks']['mc_trks.usr'].interpretation
asjagged(asdtype('>f8'), 10)

just skips over the first 10 bytes, expecting the rest to be meaningful data. In all the cases I've seen up to this point, it has been. In your case, there's junk padding after the meaningful data.
So ROOT has more degrees of freedom than previously thought and we have to actually check the 4 byte size in every STL vector jagged array. I'm going to see about adding a parameter for that.


When saving yaml file, some structure error

# This YAML file has been written using YamlMagic.
name: mobile
description: A new Flutter project.
publish_to: none

version: 1.0.2+3

environment:
  sdk: ">=3.2.3 <4.0.0"

dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:
    sdk: flutter
  flex_color_scheme: ^7.3.1
  bot_toast: ^4.1.3
  get: ^4.6.6
  shared_preferences: ^2.2.2
  dio: ^5.4.0
  path_provider: ^2.1.1
  easy_refresh: ^3.3.3+1
  package_info_plus: ^5.0.1
  url_launcher: ^6.2.2
  flutter_native_splash: ^2.3.8
  logger: ^2.0.2+1
  open_filex: ^4.3.4
  android_id: ^0.3.6

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_lints: ^2.0.3
  flutter_launcher_icons: ^0.13.1
  yaml_magic: ^1.0.5

flutter:
  uses-material-design: true

  assets:
    - assets/images/logo.png
# flutter pub run flutter_launcher_icons
flutter_launcher_icons:
  android: true
  ios: true
  image_path: assets/images/launcher_icon.png

# dart run flutter_native_splash:create
flutter_native_splash:
  color:
  image: assets/images/splash.png
  branding: assets/images/splash_branding.png
  android_12:
    image: assets/images/splash.png
    branding: assets/images/splash_branding.png
  web: false

If there are quotes, they are removed
If the value is a color value, it is removed, possibly because the quotes surrounding the color value are removed
Line feed is not saved

Color values may be removed because of '#ffffff'

@itisnajim   please help

try the new version 1.0.6

Whether it can be configured with parameters. If the value is in quotation marks, keep the quotation marks.
Is it possible to configure parameters? If there is no newline character at the end of the file, no newline character will be added.


Can't show file or dir icon (v 0.18.0)

Incompatible font? Have you installed any Nerd font? See Nerd Fonts README

https://github.com/Peltoche/lsd/issues/199#issuecomment-494218334


Move slice_buffer_list from ext/transport/inproc to lib/slice

Please answer these questions before submitting your issue.
Should this be an issue in the gRPC issue tracker?
Yes
What version of gRPC and what language are you using?
N/A
What operating system (Linux, Windows, …) and version?
N/A
What runtime / compiler are you using (e.g. python version or version of gcc)
N/A
What did you do?
Wrote inproc transport in core.
What did you expect to see?
Quick LGTM (Pls LGTM? No comments! Only LGTM!)
What did you see instead?
Comment from @makdharma indicating that that slice_buffer_list would be a generally useful structure. I responded that I could move it to lib/slice after inproc merges, and it should also get its own tests in that case. @wcevans gave it a thumbs up.
Anything else we should know about your project / environment?

Closing this. slice_buffer_list is probably a bad idea as it currently stands since it makes it easy to OOM by effectively creating an uncontrolled stream. This will be deprecated from the inproc transport once #12433 is resolved.


Handle unloaded chunks

When the server can't keep up with loaded chunks, the height metric gets reset to -1, which may cause us to land prematurely
We could add a setting to allow the height to be "stale" for a certain number of ticks to correct for briefly unloaded chunks

Add allowUnloadedChunks config, default false
Add maxTimeInUnloadedChunks config, default 3 seconds
If allowUnloadedChunks is disabled and player enters unloaded chunk, land
If allowUnloadedChunks is enabled and player enters unloaded chunk, land after timeout elapses


Selecting another image to compare with the base image in the slider section of the normalization page leads to rerunning the alignment phase

Selecting another image to compare in the slider section of the normalization page leads to rerunning the entire alignment phase. However, since all images are already aligned to the base image, this is not necessary. Fixing this would reduce the waiting time

Both the equalization and alignment stages are already cached on main:
https://github.com/DecodingRaphael/unraphael/blob/5441a294f92a420bce570e4fdf5d211b84721572/src/unraphael/dash/pages/4_compare.py#L14-L15
I don't see any other opportunites for optimization at the moment. What exactly are you running into?

I mean that when you want to use the slider and compare it with another aligned image (while keeping the same base image), it starts to align all images again from scratch. However, the images are already aligned to the base image, so there would not be a need to align it again (and it costs soem waiting time)

Okay, then I'm not entirely sure we talk about the same thing 😅 Which page and which slider do you mean?


HttpClient for communication between client and server?

Hi
What are your plans regarding communication between client and server in Blazor?
In the current template you use HttpClient which is pretty low-level. Maybe the shared project could be used for something. I think that in 2018 we should not spend time writing code that use HttpClient when we control the code on both the client and the server. There has to be a better way, do you agree? :-)
BR Klaus Even Enevoldsen

A couple of thoughts on this:

We will leverage the API client generation work planned for ASP.NET Core 2.2 to enable strongly typed API calls
We are working to support running Blazor server-side in addition to client-side in the browser so that event handling  and component logic can be seamlessly executed on the server

Thanks! I will be waiting patiently for ASP.NET Core 2.2 then 👍


texture_filter No longer affects in-game textures of 2D elements

Tested versions

Reproducible in: 4.3.stable.official [77dcf97d8]
Not reproducible in: 4.2.stable.official

System information
Windows 11 - Godot Engine v4.3.stable.official - Vulkan 1.3.242 - Forward+
Issue description
The textures of 2D elements always use Nearest filtering in-game, regardless of either the texture_filter or default_texture_filter properties. It will however work correctly in-editor. Not an issue in v4.2
(Left: Editor, Right: In-game)

Steps to reproduce
Add Sprite/TextureRect/Other 2D texture node to scene with either the default_texture_filter or texture_filter properties set to something other than Nearest
Minimal reproduction project (MRP)
MRP.zip

@nthndv Can you try following the same steps on 4.3 dev/beta/RCs? You can download them here.
Also, please upload a minimal reproduction project[^1] to make this easier to troubleshoot.

@Calinou after doing some more testing, it actually has to do with using the Viewport stretch mode, so not a bug. The projects I tested in were low-res, and scaled up nodes filter fine, so I guess there wasn't enough pixels to filter properly? Setting the resolution to match my monitor gave correct results, but nothing lower than that works. I don't know that that's an issue though. Either way, I added the MRP to be safe.


Implement Weapon Integration with Existing Inventory System

This issue will be worked on in Unity by navigating to the following path: Project > Assets > Scenes > DemoPrincipalScene. The weapon model to be implemented can be found in Assets > PolygonSciFiCity > Prefabs > Weapons.

The inventory system currently in use is the Devion Games Inventory System, which has predefined mechanics for managing items in the game. Documentation and video tutorials for the inventory system can be found here: [Devion Games Inventory System Tutorials]
https://www.youtube.com/@Zerano100/videos
Weapon Selection and Setup:
Choose one of the weapon models available in PolygonSciFiCity > Prefabs > Weapons for integration. Ensure the model is optimized for use with the character.

Set up the weapon as a pickable object in Unity, ensuring it is interactable by the player.
Inventory Integration:
Add the weapon as an item in the Devion Games Inventory System, with appropriate metadata such as:
Item Name: (e.g., "SciFi Rifle").
Icon: Generate or use an icon that visually represents the weapon.
Description: (e.g., "A futuristic rifle designed for advanced combat").
Item Type: Weapon.
Ensure the weapon can be:
Picked up from the ground using the interaction key F.
Stored in the inventory as an individual item.
Dropped back into the game world from the inventory.
Equipping the Weapon:
Implement logic to equip the weapon to the active character.
Position the weapon in the character's hand when equipped, ensuring proper alignment and orientation.
Configure animations (if available) or placeholders to simulate holding the weapon.
Interaction Logic:
The weapon should be interactable when dropped in the environment, allowing the player to pick it up again.
Use Unity's Collider and Rigidbody components to enable physical interaction.
The goal of this issue is to integrate a weapon into the existing inventory system, allowing players to interact with it naturally (pick up, store, equip, and drop). This feature will enhance gameplay by providing dynamic interactions and aligning with the futuristic, cyberpunk aesthetic of Citizen of Arcanis.
Acceptance Criteria:
The player can pick up the weapon using the F key.
The weapon is stored in the inventory with an appropriate icon and metadata.
The player can equip the weapon, which appears in the character's hand when selected.
The weapon can be dropped from the inventory, becoming an interactable object in the game world.
How to Apply
Follow the README
outlined in the README file.
If you have any questions or need assistance along the way, feel free to tag me at @sebas11042 🚀🔥
We can’t wait to see your magic in action! 😎✨

I'm really interested in this task, I'd love to contribute

Hello @mimisavage We will only accept requests that come from the only dust platform

May I try my hand at this?

Hi @sebas11042 , please can I be assigned this issue?

Hi @sebas11042 , please can I be assigned this issue?
To solve this issue I’ll navigate to Assets > PolygonSciFiCity > Prefabs > Weapons and add Collider and Rigidbody components to the weapon prefab and save it as a reusable prefab. Next I’ll register weapon in Devion Inventory Manager (Item Name, Icon, Description, ItemType = Weapon) and use InventoryManager.AddItem() for adding and InventoryManager.RemoveItem() for dropping. Lastly, I’ll test.
Kindly assign me please, I’m ready to work.

Yes ser, will push a pr soon please 🙏🏻

Hi @sebas11042 , I have a question, please how does the weapon get randomly spawned in the environment during sessions?
Are there any existing systems for that or am I to create a new one?


New UI that allow creating multiple layers from sources supporting single layer per request.

When a WMTS or ArcGIS feature source is added, a new dialog will appear and ask end-user to pick the features/sub-layers he wants to add:

A map-layer instance will be created for each selected feature/sub-layer:

@aruniverse A new build of map-layers widget will be needed once this PR merge.


Implement db and struct for FieldACL

Handler will come later.
refs #375

@cheungpat, thanks for your PR! By analyzing the history of the files in this pull request, we identified @rickmak to be a potential reviewer.

@ben181231 I hope the update has addressed your concerns.


Add RBAC for vsphere clusters

Checklist

[x] Update changelog in CHANGELOG.md.

@ljakimczuk Do you have an idea how your PR works without this change?


Remove the Content-security-Policy

remove that
https://github.com/PTsolvers/GPU4GEO/blob/5e934f4a7cfc163179cd2a040ce9b5c4d91b1c03/_layout/head.html#L9
that's what causes Safari to block

Thanks for posting this ☝ out.

UPDATE: still does not work for me on Safari - also in the Coder example.

so when you do serve in the coder example repo, it doesn't load in Safari? which version are you using? this is quite odd. I'm with Safari 15.4. On the positive side, this is not a Xranklin issue; it may be a LiveServer issue but I'm not sure. And removing the GA stuff seemed to help on my side.

Hum, weird. I am on 15.4 as well, macOS 10.15.7 (Catalina).

UPDATE: seems to work now on Safari after stopping the server and relaunching serve().

Hahaha nice one! Let's hope it stays that way

Hahaha nice one! Let's hope it stays that way


Upgrade to latest glad version

This brings us up to https://github.com/Dav1dde/glad/commit/dc14ac01e858972c1441df1d5dc30de6b8710b63
Our changes begin with https://github.com/Esri/glad/commit/717e938699fd5f864f8e5b77fae257fdddab0d3f
** Testing **

[x] vTest all platforms
[ ] mobile

[ ] basic sanity

Not sure what the local customizations are for, but assuming they're there for a reason.

I can add comments to the source if that would help.
The reasons are

follow the spec more closely about loading extension functions
rolling our own strnlen_s (not available in C99) that also handles a case if the spec isn't interpreted correctly

Sorry for the changes here. https://github.com/Esri/glad/commit/8c324a0e613f02fd3cacdbcf0857d1af4fe3a2bf is replaced by https://github.com/Esri/glad/pull/10/commits/b70f6d3b5caa85e8da572442c75cddcd32257790

rolling our own strnlen_s (not available in C99) that also handles a case if the spec isn't interpreted correctly

We still have our own version of strnlen_s. However I removed behaviour  "that also handles a case if the spec isn't interpreted correctly"

Shouldn't we be upgrading to releases only?  It looks like the latest release is https://github.com/Dav1dde/glad/releases/tag/v0.1.29

Shouldn't we be upgrading to releases only?

I don't think so, I don't know of the benefit that would provide for this repo. Typically they are bumped after a major piece of functionality goes in or for a smaller fix if it's been a long time. We would miss some fixes by making it a rule. I'm not sure if there is CI somewhere pulling these (not that it would necessarily test the code generator with the options we use).
Also, we'll probably want to switch to the glad2 branch soon as it supports the Vulkan spec, and that branch doesn't seem to have any versioning.
If this is a little too loose in terms of accountability, we'll probably have to look for another solution or start contributing more to the upstream.

Historically, we've been burned pretty badly by using random commits on random days (remember the first skia upgrade horror?). Using releases are generally the most stable thing to do but if this project doesn't really have a good release strategy, we can probably forgo that rule.

There is not much of a strategy, no. However, this library is extremely simple. For example in the last 3 years there have been zero api changes and very few behavior changes in the generated code.


INT4_AWQ_CFG and INT4_BLOCKWISE_WEIGHT_ONLY_CFG lead to large quantization errors

I'm trying to quantize a 7B Mistral model in int4 using ammo.
But INT4_AWQ_CFG and INT4_BLOCKWISE_WEIGHT_ONLY_CFG lead to much larger quantization errors than INT8_DEFAULT_CFG or INT8_SMOOTHQUANT_CFG, leading to bad results.
Is this expected? Below is a minimum reproducible example with Linear layers.
import torch
import torch.nn as nn
import tqdm

import ammo.torch.quantization as atq

torch.set_printoptions(precision=4, sci_mode=False)

class DebugModel(nn.Module):
    def __init__(self, layer_dim, num_layers, layer_class):
        super().__init__()
        self.layers = nn.ModuleList()
        for _ in range(num_layers):
            layer = layer_class(layer_dim, layer_dim)
            nn.init.xavier_uniform_(layer.weight)
            # self.binary_init(layer.weight)
            nn.init.zeros_(layer.bias)
            self.layers.append(layer)

    def binary_init(self, tensor):
        with torch.no_grad():
            tensor.copy_(torch.randint(0, 2, tensor.size()).float())

    def forward(self, x):
        for layer in self.layers:
            x = nn.Tanh()(layer(x))
        return x

def debug_quantize_model(
    model: nn.Module, quant_cfg, layer_dim, batch_size, num_batches
):
    def calibrate_loop():
        print(f"Calibrating quantization with {num_batches} batches...")
        for _ in tqdm.tqdm(range(num_batches)):
            model(torch.randn(batch_size, layer_dim))

    with torch.inference_mode():
        atq.quantize(model, quant_cfg, forward_loop=calibrate_loop)

    return model

def main_debug(quant_cfg):
    layer_dim = 128
    num_layers = 5
    layer_class = nn.Linear

    reference_batch = torch.randn(100, layer_dim)

    model = DebugModel(layer_dim, num_layers, layer_class)

    print("\n\n\nORIGINAL:")
    # print(model)
    # print_parameters(model)
    with torch.inference_mode():
        output_before = model(reference_batch)
        print(output_before)

    model = debug_quantize_model(
        model, quant_cfg, layer_dim, batch_size=1000, num_batches=128
    )
    print("\n\n\nQUANTIZED:")
    print(model)
    # print_parameters(model)
    with torch.inference_mode():
        output_after = model(reference_batch)
        print(output_after)

    diff = torch.abs(output_after - output_before)
    diff = diff / torch.abs(output_before)  # Normalized
    print(f"Median diff proportion {diff.median():.4f}")

if __name__ == "__main__":
    quant_cfg = atq.INT4_AWQ_CFG
    # quant_cfg = atq.INT4_BLOCKWISE_WEIGHT_ONLY_CFG
    # quant_cfg = atq.INT8_DEFAULT_CFG
    # quant_cfg = atq.FP8_DEFAULT_CFG
    # quant_cfg = atq.INT8_SMOOTHQUANT_CFG

    main_debug(quant_cfg)

The output for INT4_AWQ_CFG is
Median diff proportion 0.1613

meaning 16% difference in output activations, while INT8_DEFAULT_CFG gives less than 2% difference.

Could u plz try the latest code base to see if the issue still exists or not?
And do u still have further issue or question now? If not, we'll close it soon.


dhcp: Validate dhcp option 60 is being logged

Feature 4587
..continuation of #1359
This PR adds a test to validate that dhcp option 60 is being logged in dhcp extended logging mode.
Associated suricata PR : https://github.com/OISF/suricata/pull/9397
Redmine ticket: https://redmine.openinfosecfoundation.org/issues/4587

Continued in #1362


Add missing parameters to get_config in Capsule Layer

- What I did
Added regularizer, initializer and constraint parameters to the get_config function in the Capsule layer.
- How I did it
- How you can verify it

This pull request fixes #issue_number_here

@gabrieldemarmiesse I have fixed a little mistake which wasn't spotted.

Thanks for noticing that. I wonder if there is a way to catch this kind of bugs automatically in unit tests.


[BUG]Windows rke2 custom cluster - nodes stop displaying metrics in Monitoring after upgrading kubernetes version

Rancher Server Setup

Rancher version: v2.7.6-rc2
Installation option (Docker install/Helm Chart): helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): rke2

Proxy/Cert Details: valid, signed certs

Information about the Cluster

Kubernetes version: v1.25.12+rke2r1 -> v1.26.7+rke2r1
Cluster Type (Local/Downstream): downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): custom,  with windows workers, all running on ec2

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: standard user, cluster owner

Describe the bug

when using monitoring 102.0.1+up40.1.2, windows metrics are displaying properly. However after upgrading, the metrics stop being posted though all the pods appear to be active in cattle-monitoring
To Reproduce

deploy a custom rke2 cluster on 1.25

3etcd, 2cp, 3linux workers, 3 windows workers

wait for the cluster to become active
install monitoring
upgrade the cluster to 1.26
wait for the upgrade to complete
check monitoring metrics

Result
windows metrics no longer show
Expected Result

windows metrics should persist after upgrading k8s versions
Screenshots

Additional context

uninstalling -> re-installing the chart seems to fix this problem.
seems to be a regression from https://github.com/rancher/rancher/issues/40982
SURE-7731

If it's a quick fix after initial investigation, we can get it done. If it looks like it's medium loe or higher, then we should reconsider since there is a straightforward workaround.

@MKlimuszka @joshmeranda we'll take this issue since we're working actively on windows-exporter changes at the moment. Targeting 2.8.0 / 2.9.0.

The issue is reproducible per @HarrisonWAffel

I've reproduced the above bug in a standalone RKE2 cluster, I've done the following

Deploy a 1 server 1 windows worker cluster using the latest version of RKE2 installed via the installation script
Deploy a sample windows workload to the cluster and wait for it to deploy properly (see detail below for workload used)
Upgrade the server node to the next available version of rke2 (I went from 1.27 → 1.28, but considering the above comment this likely happens for any version)
Upgrade the worker node to the next available version
Attempt to delete the workload created before upgrading the cluster using kubectl

The same error shown in the above comment also appears in this scenario, which indicates that the error is not specific to the monitoring chart

Sample Workload

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: win-webserver
  name: win-webserver
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: win-webserver
  template:
    metadata:
      labels:
        app: win-webserver
      name: win-webserver
    spec:
      containers:
        - name: windowswebserver
          image: mcr.microsoft.com/windows/servercore:ltsc2022
          command:
            - powershell.exe
            - -command
            - "<#code used from https://gist.github.com/19WAS85/5424431#> ; $$listener = New-Object System.Net.HttpListener ; $$listener.Prefixes.Add('http://*:80/') ; $$listener.Start() ; $$callerCounts = @{} ; Write-Host('Listening at http://*:80/') ; while ($$listener.IsListening) { ;$$context = $$listener.GetContext() ;$$requestUrl = $$context.Request.Url ;$$clientIP = $$context.Request.RemoteEndPoint.Address ;$$response = $$context.Response ;Write-Host '' ;Write-Host('> {0}' -f $$requestUrl) ;  ;$$count = 1 ;$$k=$$callerCounts.Get_Item($$clientIP) ;if ($$k -ne $$null) { $$count += $$k } ;$$callerCounts.Set_Item($$clientIP, $$count) ;$$ip=(Get-NetAdapter | Get-NetIpAddress); $$header='
Windows Container Web Server
' ;$$callerCountsString='' ;$$callerCounts.Keys | % { $$callerCountsString+='
IP {0} callerCount {1} ' -f $$ip[1].IPAddress,$$callerCounts.Item($$_) } ;$$footer='' ;$$content='{0}{1}{2}' -f $$header,$$callerCountsString,$$footer ;Write-Output $$content ;$$buffer = [System.Text.Encoding]::UTF8.GetBytes($$content) ;$$response.ContentLength64 = $$buffer.Length ;$$response.OutputStream.Write($$buffer, 0, $$buffer.Length) ;$$response.Close() ;$$responseStatus = $$response.StatusCode ;Write-Host('< {0}' -f $$responseStatus)  } ; "
      nodeSelector:
        kubernetes.io/os: windows

Since https://github.com/rancher/rke2/issues/5551 is currently targeting Aug patches, for Rancher it means it's currently ~Sep 2024 release which is v2.9-Next2 at this time.

Discussed this issue offline. RKE2 team handled validations for this, but wanted to perform a quick smoke test to ensure all was good on Rancher's end. See details below:
ENVIRONMENT DETAILS

Rancher install: Docker
Rancher version: mainhttps://github.com/rancher/rancher/commit/b19a518d6e47551825b50b2ae0135fe3516b5d35

TEST RESULT

#
Scenario
Result

1
Metrics are displaying after upgrading RKE2 Windows cluster
:white_check_mark:

VALIDATION STEPS

Provisioned downstream RKE2 v1.28.13+rke2r1 vsphere cluster (1 etcd, 1 cp, 1 Linux worker, 1 Windows worker)
Installed Monitoring chart.
Deployed Windows workload with image mcr.microsoft.com/windows/servercore/iis.
Validated that monitoring metrics are being displayed
Upgraded cluster to v1.30.2+rke2r1.
Validated that monitoring metrics are still being displayed.


Update Arc Data extension build and download links

Update Arc Data extension for Azure Data Studio to 1.5.1

@0xbliang : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @twright-msft

#sign-off

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @twright-msft


Token cache

implementation for token cache + other minor changes

Coverage decreased (-0.4%) to 28.507% when pulling f0acd9c6fbdde0973e49ff53291cfbe46af80ce5 on token_cache into aafea3d0da2eedb621ae5f5add25098098e791ec on master.

Coverage decreased (-0.4%) to 28.507% when pulling 9ec4cbb9e1060d637018e8502c1a352b2db76e36 on token_cache into aafea3d0da2eedb621ae5f5add25098098e791ec on master.

Changes Unknown when pulling 3f41441898eb7917c25f4657d2d1c8fdffd8c6c8 on token_cache into ** on master**.


[react-form] Bug fix: Use dirtyStateComparator from config.

Description
My previous pull request (#1296) to add the dirtyStateComparator option had a problem that snuck in while addressing a review comment. I made the mistake of adding the dirtyStateComparator as a function argument, which meant it didn't actually use the value with the same name from the field configuration, and then somehow didn't notice this during tophatting. 😕
It meant that you had to use the flag like this:
  const myField = useField(
    originalValue,
    undefined, //dependencies
    (first, second) => compare(first, second) // comparator
  );

... instead of inside the config block as intended:
  const myField = useField({
    value: originalValue,
    validates: () => undefined,
    dirtyStateComparator: (first, second) => compare(first, second),
  });

Type of change

[x] react-form Patch: Bug/ Documentation fix (non-breaking change which fixes an issue or adds documentation)
[ ]  Minor: New feature (non-breaking change which adds functionality)
[ ]  Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above

No worries, it's not your fault. Fixed now anyway.


Using obfuscated packages: Uncaught (in promise) TypeError: {......} is not a constructor

Describe the bug
I'm using vanilla ts project with a very basic structure here
I've imported the https://www.npmjs.com/package/@mediapipe/selfie_segmentation library like:
import { SelfieSegmentation } from '@mediapipe/selfie_segmentation';
When I'm in devepment mode, everything seems to work as intended but after build, I get this error:
Uncaught (in promise) TypeError: e.SelfieSegmentation is not a constructor
I'm using chrome
Note:
Everything works fine in development mode by running npm run dev
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 22.39 GB / 31.91 GB
  Binaries:
    Node: 16.1.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.10.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    vite: ^2.4.4 => 2.5.0

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[ ] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[x] The provided reproduction is a minimal reproducible example of the bug.

The source code of @mediapipe/selfie_segmentation package is obfuscated (and seems to be a CommonJS module).
Rollup CommonJS plugin can't work with obfuscated packages because it relies on static analysis to determine its exports.
I don't know if it's possible to fix this incompatibility. If not, maybe we need to document it somewhere.

@sodatea  thanks for the response.
I understand the problem now. Will try to communicate with the mediapipe team regarding this.
Though I wonder there might be many numerous packages like this. Documenting this might be a good idea.

Spent 8 hours until got here, I also use mediapipe but with vue and typescript. Are there any workarounds?
For vanilla js - cdn mediapipe will work, but how to get typescript to work - I don't understand
@akhil-rana  CDN example for Selfie Segmentation
<!DOCTYPE html>

    <meta charset="UTF-8" />
    <link rel="icon" href="/favicon.ico" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />

    <title>Vite App</title>

Found this thread after wasting several hours as well. Vanilla TypeScript setup. To save some time for others in the future, was getting a similar error: Uncaught TypeError: face_mesh.FaceMesh is not a constructor.

Also have this issue, actually using Vite and React, but same issue.
Unhandled Exception +0ms TypeError: Dm.FaceDetection is not a constructor
putting this here to also help others when googling.

I'm also using Vite, Reactjs, Mediapipe, React-three-js, and I got the following error after build: TypeError: (void 0) is not a constructor. I am not sure where the problem was. npm run dev works, npm run build also goes through. But npm run preview does not work bc the build isn't working. My solution is simply using webpack...

Note: The core issue of @mediapipe/selfie_segmentation is that exports a non-ESM file in pkg.module, which should be ESM. I'd suggest contacting the package author to fix it, but for now I've documented the difference of dependencies handled in dev and build that might help in debugging the issue.

Does somebody have a workaround to get mediapipe working with vite? Thanks.

It seems like if you make vite does build using esbuild would solve the problem. (I'm not sure how to do it or can it even be done.)

Yeah there has been discussion about that at https://github.com/vitejs/vite/discussions/4921. It can be done but the whole bundling flow may need a big refactor.


Rebuild for LALSuite 7.13

This PR rebuilds this package to accommodate the new LALSuite 7.13 release, which includes many backwards-incompatible component packages releases.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This is no longer required as the rebuild for LALSuite>7.13 is included in:  https://github.com/conda-forge/cwb-feedstock/pull/9


How to style anchors?

Is it possible to apply styles to anchors on a node? I would like a node with anchors that look like this:

@gaoli

this is a unique need,  and GGEditor does not support this kind of configuration. However, you can completely draw your own node referring to G6.
I give you a very simple demo（draw function has been overridden):

demo 🔗

Well, you need to improve this demo with your specific demand.


[3.0] Dung beacon's poison effects are inverted

Issue: Dung beacons give players poison but it doesn't do damage unless they wear a full set of soulforge steel
Steps to Reproduce: Place a dung beacon and then put on a set of soulforge steel armor

this works fine in dev. mapping issue

Not a mapping issue, does not work in my dev env

another one that was fixed in my branch,


Add list accounts

Add list accounts command. Human readable ouput.

After fixing the issues detected, do not forget to add
* Doc

* Uniitest

* Otionally integration tests, but not required.

Do you have any example of unit test? Any tool? Where I put it?
accounts.md doesn't exist. I will create it.

Do you have any example of unit test? Any tool? Where I put it?

Create the file called spec/unit/commands/accounts_command/list_command_spec.rb and you can implement unittests there. We are using RSPEC testing framework in this project. But if you want to use another testing framework, it is ok also.
I suggest to implement something very similar as metric list command unittests

accounts.md doesn't exist. I will create it.

Now I realize that 3scale account find is not documented. I will document it after we merge this PR. Yes, please create docs/account.md file and add content for the list command. Very similar to https://github.com/3scale/3scale_toolbox/blob/main/docs/metric.md

Codecov Report

Merging #323 (c1adc0d) into main (20c7cfb) will decrease coverage by 4.72%.
The diff coverage is 88.00%.

:exclamation: Current head c1adc0d differs from pull request most recent head 10140b5. Consider uploading reports for the commit 10140b5 to get more accurate results

@@            Coverage Diff             @@
##             main     #323      +/-   ##
==========================================
- Coverage   98.54%   93.82%   -4.73%
==========================================
  Files         345      346       +1
  Lines       16160    16180      +20
==========================================
- Hits        15925    15181     -744
- Misses        235      999     +764

Impacted Files
Coverage Δ

...e_toolbox/commands/account_command/list_command.rb
86.95% <86.95%> (ø)

lib/3scale_toolbox/commands/account_command.rb
93.75% <100.00%> (+0.89%)
:arrow_up:

spec/shared_examples.rb
11.42% <0.00%> (-88.58%)
:arrow_down:

...on/commands/product_command/export_command_spec.rb
18.27% <0.00%> (-81.73%)
:arrow_down:

...gration/commands/plans_command/plan_import_spec.rb
29.50% <0.00%> (-70.50%)
:arrow_down:

spec/helpers.rb
30.00% <0.00%> (-63.00%)
:arrow_down:

...tion/commands/backend_command/copy_backend_spec.rb
39.47% <0.00%> (-60.53%)
:arrow_down:

...gration/commands/plans_command/plan_export_spec.rb
44.64% <0.00%> (-55.36%)
:arrow_down:

...commands/proxy_config_command/list_command_spec.rb
52.08% <0.00%> (-47.92%)
:arrow_down:

spec/custom_matchers.rb
53.84% <0.00%> (-46.16%)
:arrow_down:

... and 64 more

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 20c7cfb...10140b5. Read the comment docs.

great progress.
Only testing is missing. Ruby projects should always have very high test coverage as typos and other very common mistakes are not detected in a "compilation" step, as there is no compilation step.


Adding User Identifiers API documentation

Added User Identifiers API documentation and specs. Identity Services team did not publish this endpoint yet to production.
A further notice will be issued for when this PR is ready to be merged.

@Kaldjo, Review is done for this PR. Let me know when to merge it.


split message.content.lower() on incoming messages to solve the scunthorpe problem. Although that does run into some problems with phrases... figure this out

Issue created by TheSkeward#1111.

#81 my pull request sort of solves this problem in a simplistic way, we could use this as a starting point

Fixed! no more scunthorpe problem. watchwords that are a single word require a precise match. Watchwords that are a phrase are just searched as a substring of the message.


SyntaxError: Unexpected token ':', ": {"id":"c"... is not valid JSON...

yakGPT suddenly cannot work normally as usual when using apis like GPT4. However, I tested with chatgpt 3.5 model and it worked as usual.
I have tried with official deployment at yakgpt.vercel.app on different browers and they all failed. And I could get normal result using official curl post and I'm sure that my API has permission to access GPT 4 API.
The log info in the developer console is shown as follows:
_app-c9c65ec057b5d078.js:50024 SyntaxError: Unexpected token ':', ": {"id":"c"... is not valid JSON
    at JSON.parse (<anonymous>)
    at t.IncomingMessage.<anonymous> (_app-c9c65ec057b5d078.js:50024:53683)
    at a.emit (_app-c9c65ec057b5d078.js:50024:61155)
    at R (_app-c9c65ec057b5d078.js:50024:120366)
    at P (_app-c9c65ec057b5d078.js:50024:120195)
    at E.push (_app-c9c65ec057b5d078.js:50024:123102)
    at _app-c9c65ec057b5d078.js:50024:156301
    at new Promise (<anonymous>)
    at Object.write (_app-c9c65ec057b5d078.js:50024:156256)

Same issue, for at least 2-3 days now for me.  Exclusively using main version hosted on vercel.app recently, have not built my own in a long time.  Appears to happen consistently with the newer engines e.g. gpt-4-1106-preview, gpt-4-0125-preview, and gpt-4.  It will output just a couple words and stop, and the console will show errors similar or identical to above as per VisionTheta.  Sometimes it seems better with legacy engines e.g. -0314 or -0613, but not consistently because those may throw errors too.
I wonder if something with the timing has changed? ... Because it appears sometimes I will see the errors in the console but then it somehow corrects and manages to move forward and to continue outputting text; it's almost as if it's trying to process the output before the JSON is fully saved to local storage or something like that.  I have not managed to catch it with an actual incorrectly formatted JSON in the local storage but I may see if I can do that.

Same issue, for at least 2-3 days now for me. Exclusively using main version hosted on vercel.app recently, have not built my own in a long time. Appears to happen consistently with the newer engines e.g. gpt-4-1106-preview, gpt-4-0125-preview, and gpt-4. It will output just a couple words and stop, and the console will show errors similar or identical to above as per VisionTheta. Sometimes it seems better with legacy engines e.g. -0314 or -0613, but not consistently because those may throw errors too.
I wonder if something with the timing has changed? ... Because it appears sometimes I will see the errors in the console but then it somehow corrects and manages to move forward and to continue outputting text; it's almost as if it's trying to process the output before the JSON is fully saved to local storage or something like that. I have not managed to catch it with an actual incorrectly formatted JSON in the local storage but I may see if I can do that.
SyntaxError: Unexpected token ':', ": {"id":"c"... is not valid JSON at JSON.parse () at t.IncomingMessage. (_app-c9c65ec057b5d078.js:50024:53683) at a.emit (_app-c9c65ec057b5d078.js:50024:61155) at R (_app-c9c65ec057b5d078.js:50024:120366) at P (_app-c9c65ec057b5d078.js:50024:120195) at E.push (_app-c9c65ec057b5d078.js:50024:123102) at _app-c9c65ec057b5d078.js:50024:156301 at new Promise () at Object.write (_app-c9c65ec057b5d078.js:50024:156256)
SyntaxError: Unexpected token ':', ": [DONE]" is not valid JSON at JSON.parse () at t.IncomingMessage. (_app-c9c65ec057b5d078.js:50024:53683) at a.emit (_app-c9c65ec057b5d078.js:50024:61155) at R (_app-c9c65ec057b5d078.js:50024:120366) at P (_app-c9c65ec057b5d078.js:50024:120195) at E.push (_app-c9c65ec057b5d078.js:50024:123102) at _app-c9c65ec057b5d078.js:50024:156301 at new Promise () at Object.write (_app-c9c65ec057b5d078.js:50024:156256)

There are other clues as well.  E.g. if you look in the JSON the assistant reply might start with a space character or a period followed by a space, as if the beginning of the message is missing too.

Seems to be a consistent pattern based on the length of reply or the time it takes to output a reply.
Based on just a handful of trials with gpt-4, it will consistently give one word answers, sometimes will do two words but sometimes not, will less often successfully give three word or longer replies, etc. At most I have gotten it once to give a paragraph, but I have not gotten it to give "two brief paragraphs." I will just hit the refresh button in the reply box to keep trying it for a given prompt.

            {
                "id": "06dd5e2a-0364-47d2-b51f-262e3cafc813",
                "title": "",
                "messages": [
                    {
                        "id": "aecea92b-d9f7-498f-8a8f-3b09f65d9c4c",
                        "content": "Give a one word response.",
                        "role": "user"
                    },
                    {
                        "id": "ef04d846-8d3c-4064-978c-96aefd07dec7",
                        "content": "Sure.",
                        "role": "assistant",
                        "loading": false
                    },
                    {
                        "id": "253134dd-c942-43b7-815b-67b56aa67d77",
                        "content": "Give a two word response.",
                        "role": "user"
                    },
                    {
                        "id": "cdc1dd0c-29b1-41fa-9931-0221e07a6bd8",
                        "content": "Of course.",
                        "role": "assistant",
                        "loading": false
                    },
                    {
                        "id": "589fc8d4-e492-45a7-be80-374518e5bb01",
                        "content": " Give a three word response. ",
                        "role": "user"
                    },
                    {
                        "id": "039363eb-874e-4ee6-b29a-fc9054723919",
                        "content": "",
                        "role": "assistant",
                        "loading": false
                    }

                    {
                        "id": "aecea92b-d9f7-498f-8a8f-3b09f65d9c4c",
                        "content": "Give a one word response.",
                        "role": "user"
                    },
                    {
                        "id": "ef04d846-8d3c-4064-978c-96aefd07dec7",
                        "content": "Sure.",
                        "role": "assistant",
                        "loading": false
                    },
                    {
                        "id": "253134dd-c942-43b7-815b-67b56aa67d77",
                        "content": "Give a two word response.",
                        "role": "user"
                    },
                    {
                        "id": "cdc1dd0c-29b1-41fa-9931-0221e07a6bd8",
                        "content": "Of course.",
                        "role": "assistant",
                        "loading": false
                    },
                    {
                        "id": "589fc8d4-e492-45a7-be80-374518e5bb01",
                        "content": " Give a three word response. ",
                        "role": "user"
                    },
                    {
                        "id": "62755214-b5c2-43c3-993c-6f7e3f933681",
                        "content": "Absolutely, no problem.",
                        "role": "assistant",
                        "loading": false
                    },
                    {
                        "id": "f3d8e6ee-65d1-410f-aba4-afca0a1bc93c",
                        "content": "4?",
                        "role": "user"
                    },
                    {
                        "id": "f380f9d6-a01d-4d57-99a6-ee69a33cb0f5",
                        "content": "I can do that.",
                        "role": "assistant",
                        "loading": false
                    },
                    {
                        "id": "486bb7b4-3469-4c1f-b50f-2b0d68a5ece7",
                        "content": "5 words",
                        "role": "user"
                    },
                    {
                        "id": "010ea388-05fe-44aa-adc8-d6efa81697ec",
                        "content": "I am here to assist you.",
                        "role": "assistant",
                        "loading": false
                    },
                    {
                        "id": "4c431f06-8426-4fbc-9b4b-8c14fdbca04b",
                        "content": "10 words",
                        "role": "user"
                    },
                    {
                        "id": "f3b993c2-dad1-4d00-9ff6-b9ba8e72b1cc",
                        "content": "Sure, I am here to provide any assistance you need.",
                        "role": "assistant",
                        "loading": false
                    },
                    {
                        "id": "e7bba186-d589-4232-82a2-c4259a88cd9d",
                        "content": "two brief paragraphs",
                        "role": "user"
                    },
                    {
                        "id": "47035822-da96-4b27-93cb-1d401dcc33b0",
                        "content": " OpenAI.",
                        "role": "assistant",
                        "loading": false
                    }

I'm guessing the streaming format has changed in some way, and yakgpt made an incorrect assumption about it always being complete and valid json.
This issue seems intermittent to me (becoming more frequent), but none of the other chatgpt integrations I use are affected, even though some of them use the streamed response as well.  It might be good to look through the official js repo to see if they've done anything recently regarding streaming changes: https://github.com/openai/openai-node/releases

Okay, it's an easy fix.  Yakgpt assumed the messages started with data: and sometimes it starts with  data: (see whitespace).
Simply trim the message before parsing and it's fixed.

The official deployment does not work at all for me, and I am seeing the same symptoms mentioned here. The patch by @rannmann resolves the issue for me (tested via the Vercel preview linked in the PR). I will continue to use the aforementioned preview until the issues is resolved in the official version.

Do note that these characters are not random - in these case those seem to be trailing new lines, which are used in the SSE event protocol. The correct fix would be to use a proper SSE library for communicating with the streaming endpoint or the official Openai node library, which comes with their own SSEDecoder implementation.

That's definitely a better solution.  Think of mine as a quick hotfix in the meantime.  Adding a trim() is low-risk, and adding a library is a bit more involved.
If you get a working MR done with that change before this one is merged in, we can skip mine.

The correct fix would be to use a proper SSE library for communicating with the streaming endpoint or the official Openai node library, which comes with their own SSEDecoder implementation.

The one caveat here is that YakGPT is entirely client-side by design. The app itself is a static site; no API that handles user data. That's how everyone's data stays private to their browser session. So that would rule out backend-only libraries.

Thank you guys so much for debugging and fixing this! Warms my heart really <3


Deleting a User should redirect to /admin/users on success

Gitea version (or commit ref): 1.3.0
Git version: 2.13
Operating system: Win10
Database (use [x]):

[ ] PostgreSQL
[x ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x ] Not relevant

Log gist:

Description
When deleting a user in the following workflow Admin Panel > Users tab > Edit > Delete User the screen comes up asking to confirm the action. Then the overlay screen says it has successfully deleted the user. However the screen page remains on /admin/users/:id when the overlay fades out.
I feel it would be much better if an automatic redirect happened instead bringing you back to view all users at this point and display a flash message

We tested it on Chrome macOS. It redirected to /admin/users/ after I deleted a user. Which browser are you using and any error on console?

I'm using chrome. Didn't notice any errors either.
Get Outlook for Android
On Tue, Dec 12, 2017 at 2:59 PM +0000, "Lunny Xiao"<EMAIL_ADDRESS>wrote:
We tested it on Chrome macOS. It redirected to /admin/users/ after I deleted a user. Which browser are you using and any error on console?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I can not seem to reproduce this, seems to be working just fine for me


Implement BipedalLocomotion::RobotInterface::constructGenericSensorClient() function

Also add a comment where to find the genericSensorClient (Currently in whole-body-estimators).


feat(option): add new background options to have achievement background

Show background texture of the current advancement tab instead of black background

It will look better, I think

Hi again, the issue are resolved in v0.4.0, available on modrinth right now https://modrinth.com/mod/advancements-reloaded
Thanks again for the proposal

Nice!


python311Packages.asyncua: 1.0.4 -> 1.0.5

Diff: https://github.com/FreeOpcUa/opcua-asyncio/compare/refs/tags/v1.0.4...v1.0.5
Changelog: https://github.com/FreeOpcUa/opcua-asyncio/releases/tag/v1.0.5
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

10 packages built:

opcua-client-gui
opcua-client-gui.dist
python310Packages.asyncua
python310Packages.asyncua.dist
python310Packages.opcua-widgets
python310Packages.opcua-widgets.dist
python311Packages.asyncua
python311Packages.asyncua.dist
python311Packages.opcua-widgets
python311Packages.opcua-widgets.dist


Add support for VolumeAccessPoint(FileShareTarget Creation) if volume creation fails but creates (File share)

If for some reason the File share is created but target creation fails. Lets retry creating target so that we have way to recover the file share created.

:thumbsup: Coverage increased from [%] to [82.7875%]

:thumbsup: Coverage increased from [%] to [83.3%]

:thumbsup: Coverage increased from [%] to [83%]

:thumbsup: Coverage increased from [%] to [%]

:thumbsup: Coverage increased from [%] to [%]

:thumbsup: Coverage increased from [%] to [82.875%]

:thumbsup: Coverage increased from [%] to [82.675%]

:thumbsup: Coverage increased from [%] to [83.3125%]

:thumbsup: Coverage increased from [%] to [83.1%]


Expose Hyperdrive from the worker crate

This allows users to pass around the instance of Hyperdrive.

Huh, surprised that Rust didn't complain about the private type in a public API Env::hyperdrive.


Hystrix and Connection Pooling

Hi,
Please excuse this - it could well be a dumb newbie question.
We're using Hystrix as a Circuit Breaker between two services. To speed up performance we're using Connection Pooling. We're using the PoolingHttpClientConnectionManager from Apache HttpClient to handle the Connection Pool.
We're also using Hystrix's 'timeoutInMilliseconds' property to catch issues.
The problem we have is that in normal operation it takes c130ms to create a new HTTPS connection, but once pooled the read time on those connections is c12ms.
So, we've had to set our 'timeoutInMilliseconds' threshold to be higher than we'd like so that Hystrix doesn't kick in whenever our Connection Pool decides to create a new connection. Our Non-Functional Requirements want the latency to the service to be nearer 12ms than 130ms.
Are we doing something wrong?
Cheers,
Mike

No you aren't doing anything wrong, but I don't think you'll be able to achieve your requirement of 12ms latency when establishing an HTTP connection takes more time than that. You can set your timeout to be less than 120ms and deal with a fallback if you want, possibly retrying again and hoping you get an already established connection, but there's no way you can achieve performance faster than it takes to establish the HTTP connection.
Maybe you need a background process which makes sure all pooled connections are valid all the time? This really only works if you are constantly hitting the same route though.


No style in the template

Hi, I'd love to start using your datetimepicker but there seems to be no CSS (or style in general) when rendering the template. This is what I get when I try to render the most basic example.

All the js and css should be loaded.
Any idea what's going on?

I posted the question on stackoverflow. Any help would be greatly appreciated. https://stackoverflow.com/questions/54870322/angularjs-bootstrap-datetimepicker-not-rendering-style
Thanks a lot!


Will the "_" in the gate name be deprecated?

The IBM Quantum Composer does not allow _ in the gate name. For example,
gate abc1 q // Good
{
}

gate abc_1 q // Bad
{
}

The OpenQASM 2.0 clearly specifies the validity of the _ in the gate name. Have you asked the IBM Quantum Composer people to stop using _? Or, is that just an outright bug in their parser?
The _ is so useful. I cannot imagine any reason to deprecate it.

This seems like a bug in the IBM Q Composer specifically. I will raise internally with this team.

This is confirmed a bug and an internal ticket has been opened to fix.

+1 to closing this since it's not an OpenQASM issue

Agreed.


⚠ Instructions for generating EFI folder from config template result in invalid plist file!

In your latest release of OCAT, you removed direct user access to the database from within the App for generating pre-configured EFIs for Intel Systems. Instead, you redirect users to my repo via URL:

In order to generate an EFI, you suggest the following in the changelog popup window:

These instructions are wrong! Downloading an plist via right-clicking in a browser changes it's fileheader and results in an invalid file:

In order for users to use this feature they would have to import the raw text into OCAT, which it does not support. So users would have to copy the raw text into ProperTree save the config, then open it in OCAT again in order to be able to generate and populate the EFI fodler. I don't think this is a desireable workflow.
My suggestion is to revert this setting and let users access the database again.

Please refer to my latest reply in your previous question.


Add tx wrapper in create node

Codecov Report

Merging #306 (509a516) into master (1f2842b) will increase coverage by 0.07%.
The diff coverage is 87.50%.

@@            Coverage Diff             @@
##           master     #306      +/-   ##
==========================================
+ Coverage   66.28%   66.35%   +0.07%
==========================================
  Files          83       84       +1
  Lines        6059     6082      +23
==========================================
+ Hits         4016     4036      +20
- Misses       1483     1485       +2
- Partials      560      561       +1

Impacted Files
Coverage Δ

service/wrapper.go
85.71% <85.71%> (ø)

api/api.go
59.45% <100.00%> (+1.12%)
:arrow_up:

api/node.go
66.00% <100.00%> (ø)

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 1f2842b...509a516. Read the comment docs.


Implement game resetting on player's death (#111)

Creating new WorldMap every time new player is created is highly ineffective just to preserve conversation iterators as it contains a lot of information that can be shared between players.
Better approach (in my opinion) would be a map that holds NPC id and conversation iterator in GameInstance. This would fill gradually and we won't have this huge overhead of unneeded duplicated data. Thanks to that, resetting game, apart from resetting player data, would come down just to clearing these maps.
Please refactor.

WorldMap contains much more information than npc iterators, such as mobs state, location and items state etc. Refactoring this now could lead to unintened side effects we could not catch. Besides, Player is created only when he is defeated (or connected in the future).


Fix concurrency issues with memmetrics.

cherry-picked from https://github.com/containous/oxy
related to: https://github.com/vulcand/oxy/issues/79

Close in favor https://github.com/vulcand/oxy/pull/42


cache key collision because of username URL decode in url_CryptoHash_get_general

The code in url_CryptoHash_get_general at URL.cc decodes percent encoding in all components of the URL, including username / password. This behaviour is incorrect and can lead to security consequences.
Consider the following scenario:

An ATS instance serves two domains: attacker.com and victim.com. This can happen either in forward-proxy mode or in the reverse proxy mode in some cases.
An attacker controls the content of attacker.com (e.g. can serve whatever she wants to ATS when ATS makes requests to attacker.com, as well as to instruct ATS to cache this content).
The attacker wants to put her content into the context of victim.com to achieve e.g. XSS.

The attacker can visit<EMAIL_ADDRESS>via ATS (note the encoded characters in the username). She can do so by sending the link in the HTTP request, like this:
GET<EMAIL_ADDRESS>HTTP/1.1
...

ATS will forward this request to attacker.com, but the key in the cache (calculated in url_CryptoHash_get_general before hashing) will be http://<EMAIL_ADDRESS>Now, if someone visits<EMAIL_ADDRESS>via ATS, it will lookup the response in the cache and serve the attacker's page, thus achieving XSS impact (the attacker can send this link to someone and execute javascript in the context of victim.com).
The same impact can be achieved using MD5 collisions. The cache key is hashed using MD5, and there're public tools to create an MD5 collision (including chosen-prefix ones).

I agree, we shouldn't URI decode the user name/password.

Unfortunately, it looks appears to be spec legal to use percent encoding in the user name. I need to think about this a bit more.
MD5 collisions aren't a concern - the cache already deals with it. Internally the stripe directory is the equivalent of an open chained hash and the MD5 value is used only to locate the bucket. The full URL is used for equality checks.

I think the "fair" solution would be to encode back some characters (e.g. /, :', @ and so on) so that if one of these appears in the username/password, it will always be in its encoded form.
However, note that several (but less security impactful) issues can arise in the other part of the URL. E.g. in some hypothetical example, we can register a user with the name victim&page=posts and then get a page like index.php?username=victim%26page=posts cached as if it were index.php?username=victim&page=posts and still get cache poisoning (but inside the same domain).


Lint: Add linter for log statements

Adds linter for log statements.
Also, fix all the places the linter flagged in the codebase.

This change is

a discussion (no related file):
Previously, lukedirtwalker (Lukas Vogel) wrote…
hm I just realized that the case in the BR is not catched: https://github.com/scionproto/scion/blob/master/go/border/rctrl/ifstate.go#L45
But it's certainly better than nothing.

created https://github.com/Oncilla/gochecks/issues/6 to track this


Fix log spew

Overview
Reserved for @0xf11nix - do not apply for this bounty
We have a bunch of log spew in CI from jest and it's heaps gross aye.
References and additional details
Check an existing CI run for an example
https://github.com/shapeshift/lib/runs/5562962485?check_suite_focus=true
Acceptance Criteria

yarn test runs without any rank log spew

Need By Date
N/A
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Sponsor / Stakeholder
@0xdef1cafe
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

@0xdef1cafe  just trying to get this bounty into Dework ... if you can please let us know the expected time to take for it so we can finish the bounty that would be great! Cheers :)

@0xdef1cafe please advise expected hours for this bounty, or if a bounty is no long required. Thank you


Document design decision of build script install.hs

This PR adds a document to the docs/ folder that discusses the motivation of the build script install.hs.
Comments are welcome

@Anrock I was thinking the same, and possibly by finally merging https://github.com/haskell/haskell-ide-engine/pull/495

LGTM


fix(drawer & modal ): fix onOk & onCancel type error in function call

Types of changes

[ ] New feature
[ ] Bug fix
[ ] Enhancement
[ ] Component style change
[x] Typescript definition change
[ ] Documentation change
[ ] Coding style change
[ ] Refactoring
[ ] Test cases
[ ] Continuous integration
[ ] Breaking change
[ ] Others

Background and context

Solution

How is the change tested?

Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

Modal
修复函数调用形式ts报错
fix onOk & onCancel type error in function call

Checklist:

[ ] Test suite passes (npm run test)
[ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others
should be submitted to main branch)

Other information

width设置为什么无效呢？

呜呜呜 终于修复这个问题了, 我前两个月一直遇到这个问题, 没办法我只能自己封装一个先用了


Update configuration docs to reflect pull #314

Thanks for #314 @erikbra! This PR updates the docs to reflect the changes that you made :)

Great, thanks for the docs update! :)