[Bug]: "alt- Image Elements and aria-label- Form Section" missing in Some Files

Describe the bug

In index.html, script.html, page_contactis.html Files, alt attribute is missed
Also, In page_contactus.html File, aria-labels are missing in Form Section

Steps to reproduce the behavior

Go To "gh-pages" Branch Data.
Observe index.html, script.html and page_contactus.html Files. alt attribute is not properly used to Image Elements
Also, Observe In page_contactus.html File, aria-labels missing in Form Section

Expected behavior

Placed alt and aria-label attributes in Respective Files

Screenshots
No response
Device?
Desktop
Which OS are affected?
Windows
Enter the version of your web browser
Version 115.0.5790.110 (Official Build)
Which browsers are affected?
No response
Additional context

alt attribute is much need for Image Elements. Because of In some Cases, Browsers does not read Images Properly
aria-label attribute is much need for SEO Optimization  This helps screen readers identify what each form field is for, improving the user experience for visually impaired users.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Hi @avinashkranjan . Please review on this Issue

Hi @avinashkranjan . Please Review on this Issue.


GH-Pages: Prettier Code Blocks

If we get a chance, let's style the new nohighlight code blocks look more like the language-specific ones, which have a nicer padding and font

I figured out how to do this. We just need to add " hljs" to the css class.
So instead of class="language-nohighlight" we want class="language-nohighlight hljs". see screenshot below.
@digshake Can you do this? I still don't know how to modify the guts of couscous


pidgin-sipe fails to build in nixpkgs-unstable

Steps To Reproduce
Steps to reproduce the behavior:

git checkout nixpkgs-unstable  # tested at 31d567846255e122846548255101980162bbf641
nix-build -A pidgin-sipe

Build log
In file included from /nix/store/dahsdlclq07r1zf1a44n43ay0r7jdg8k-pidgin-2.14.10/include/libpurple/dbus-server.h:54,
                 from purple-dbus.h:33,
                 from purple-dbus-bindings.c:29:
/nix/store/dahsdlclq07r1zf1a44n43ay0r7jdg8k-pidgin-2.14.10/include/libpurple/dbus-bindings.h:32:10: fatal error: dbus/dbus-glib-lowlevel.h: No such file or directory
   32 | #include <dbus/dbus-glib-lowlevel.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

Additional context

pidgin-sipe builds fine in nixos-22.05.
pidgin-sipe doesn't seem well maintained -- very little activity in https://sourceforge.net/projects/sipe/ AFAICT. I'm not sure what the alternatives are.

Notify maintainers

There's no listed maintainers for pidgin-sipe (nor pidgin).

I tried bisecting, but hit some staging/mass-rebuilds so I aborted.
I tried adding dbus-glib to buildInputs, but ./configure seems to ignore it.

I tried adding dbus-glib to buildInputs, but ./configure seems to ignore it.

Checking for dbus-glib only done if telepathy-glib is available. (It is not in nixpkgs-unstable.)

In 22.05 nix log pidgin-sipe ... checking for DBUS... no ...
In unstable nix log pidgin-sipe ... checking for DBUS... no ...
Not sure how to disable dbus dependency for nix build pkgs/applications/networking/instant-messengers/pidgin-plugins/sipe/default.nix

Fixed on master and release-22.11 thanks to https://github.com/NixOS/nixpkgs/pull/206428 and its backport PR. Thanks @daymien!


Week and Day View not working

Following error is thrown in console when trying to switch views:
I managed to get the calendar running with help from the test project though mismatching versions between it and the release did cause some issues with some functions not having return types.
Though for some reason the calendar is only working in month view and when trying to switch via the same commands as in the test projects I get the following error.
Note that i copied the CalendarViewModel and its base into my project but filled it with my own data instead of using Bogus.
Uncaught TypeError: Cannot read properties of null (reading '0')
    at d.<anonymous> (tui-calendar.js:26869:22)
    at tui-code-snippet.js:1062:36
    at r (tui-code-snippet.js:947:23)
    at a (tui-code-snippet.js:1024:10)
    at Object.s [as map] (tui-code-snippet.js:1061:6)
    at d._getBaseViewModel (tui-calendar.js:26858:22)
    at d.render (tui-calendar.js:26887:25)
    at c.<anonymous> (tui-calendar.js:28232:19)
    at l (tui-code-snippet.js:984:27)
    at c.each (tui-calendar.js:4144:5)

tui-calendar.js:26869 Uncaught TypeError: Cannot read properties of null (reading '3')
    at d.<anonymous> (tui-calendar.js:26869:22)
    at tui-code-snippet.js:1062:36
    at r (tui-code-snippet.js:947:23)
    at a (tui-code-snippet.js:1024:10)
    at Object.s [as map] (tui-code-snippet.js:1061:6)
    at d._getBaseViewModel (tui-calendar.js:26858:22)
    at d.render (tui-calendar.js:26887:25)
    at c.<anonymous> (tui-calendar.js:28232:19)
    at l (tui-code-snippet.js:984:27)
    at c.each (tui-calendar.js:4144:5)

Which nuget are you using? Could you zip up your project or a one that reproduces the issue and I can take a look?

im using beta3.1 which was the latest on the nuget link.
Sadly i can't zip up the project to send.
Side note: can we customize the edit window of the calendar to add our own fields?

Could you make a minimal reproducible version?
Try this version in your project: 1.0.0-beta1.1.59
Re customizing: you would have to make your own popup/edit window and capture the on-click event and handle it accordingly. Let me know if you need more info.

The version you linked is working fine. Thank you for the help.
What event am I grabbing, because in my case I would my custom modal to show instead of the built in one. Or extend the existing one.

@gismofx that worked like a charm.
I have one more question, there is a functionality for creating events in toast ui where you click and drag on the calendar and it auto fills your dates/times based on your initial selection via clickind and dragging.
I can't seem to find an event to hook into this for when creating new events/appointments.
Am I missing something? The oncreatecalendareventortask is only called after clicking save on its own form which I dont want to use

@armendimeri can you send/share a link to the docs TUI docs where it shows that capability/event? I'm sure I can implement it.


Enable CSRF

This task is to be done when UI integration is at its final steps.

Sure,will make note of the same

Now that we're clear our frontend is separate, this will be a bit more difficult to implement.
Let's check later when we get a chance.


[BUG] Self-XSS in "Absolute Time Range"

Describe the bug
It's possible to execute JS on application context by modifying the "Absolute Time Range"
To Reproduce
Access to a new dashboard in graphite-web instance (i.e. http://localhost/dashboard).
Use the "Absolute Time Range"
Write in Start Date:

Write in EndDate:

Hover the mouse over these fields
Expected behavior
This can be solved by removing or ignoring requests containing the characters "<" ">" and/or other escaping/scripting characters. -> Sanitize the value before using it.
Screenshots

Environment (please complete the following information):

OS flavor: Debian 11
Graphite-web version 1.1.8
Setup type: docker

Looks like not fixed in #2785 :(
/cc @msaf1980

@deniszh I already update our staging (and production today). Now I can't reproduce a issue (and can before update). No alert window in web front and dangerous symbols are escaped.

As I think, bug in ExtJS DateField.


Update Pillow version in examples to version 9

Summary
We have older Pillow version referenced here with known vulnerabilities: https://github.com/whylabs/whylogs/blob/mainline/examples/sagemaker_container_example/requirements.txt
https://github.com/advisories/GHSA-pw3c-h7wp-cvhx
What is the expected correct behavior?
Should be:
Pillow>=9.0.0

removed in 1.0.0


Add toleration for control-plane taint

What type of PR is this?
/kind feature
What this PR does / why we need it:
Add toleration for control-plane taint as recommended on the respective KEP
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Add toleration for the control-plane taint to support the renaming of "master" taints

/test pull-security-profiles-operator-test-e2e

/test pull-security-profiles-operator-test-e2e

/lgtm

/lgtm


Range Labels Not Respected for Default Start/End Date On Initial Load

On initial load of the filter, the display label is the date range [06/16/2024 - 06/30/2024] instead of the range label "Last 14 days"
When using the filter Reset in filament, the correct label "Last 14 days" appears correctly.
Steps to reproduce:

Set custom ranges
Use Range Labels
Set startDate and EndDate to match a range label

On initial load the range is displayed, on filter reset, the correct label is displayed
          DateRangeFilter::make('created_at')
                ->label('Date Range')
                ->disableClear()
                ->disableCustomRange()
                ->withIndicator()
                ->ranges([
                    'Today' => [now(), now()],
                    'Yesterday' => [now()->subDay(), now()->subDay()],
                    'Last 7 days' => [now()->subDays(7), now()],
                    'Last 14 days' => [now()->subDays(14), now()],
                    'Last 30 days' => [now()->subDays(30), now()],
                    'Last 60 days' => [now()->subDays(60), now()],
                    'Last 90 days' => [now()->subDays(90), now()],
                    'All Dates' => [now()->subYears(10), now()],
                ])
                ->useRangeLabels()
                ->startDate(now()->subDays(14))
                ->endDate(now())
                ->format('m/d/Y')
                ->displayFormat('MM/DD/YYYY')
                ->columnSpan(1)
                ->columns(1),

Fixed in v 2.8


java.awt.FileDialog causes segfault when shown. Linux 64bit over x11.

Summary
Whenever a FileDialog is show the app crashes.
Steps to reproduce
import java.awt.*;

public class DialogX11{

    public static void main(String[] args){
        EventQueue.invokeLater( ()->{
            FileDialog fd = new FileDialog((Frame)null, "Get File");
            fd.setVisible(true);
            String s = fd.getFile();
            System.out.println(s);
        });
    }
}

Expected results
A file dialog shows.
Actual results
The program crashes and creates an hs_err file.
Triaging info
Java version:
###What is your operating system and platform?
Fedora Linux 64bit
openjdk version "11.0.12" 2021-07-20
OpenJDK Runtime Environment Temurin-11.0.12+7 (build 11.0.12+7)
OpenJDK 64-Bit Server VM Temurin-11.0.12+7 (build 11.0.12+7, mixed mode)
###How did you install Java?
Downloaded from adoptopenjdk and untarred the jdk.
###Did it work before?
It works as expected with java 8, but it it crashes on everything java 11 and high versions I have tested.
###Did you test with other Java versions?
It works on JDK 8. I've tried jdk 16 and 11 both from adoptopenjdk and both times it crashes.
I have also tested it on another 64bit linux.

Hi @odinsbane - Can you attach the hs_err file?

hs_err-workstation.txt

Reproduced (using the upstream JDK 11 build) on Fedora 34. An interesting observation is that the system JDK from the java-11-openjdk package from F34 doesn't crash. The earliest version I can reproduce this with is 11.0.10+9. Last worked with 11.0.9+11. I'll report it upstream.

Upstream bug: https://bugs.openjdk.java.net/browse/JDK-8272149

Main upstream bug to track is https://bugs.openjdk.java.net/browse/JDK-8255790 (JDK-8272149 is a duplicate). 11 backport scheduled for 11.0.13 (October 2021).


Incorporates Szandor72s changes in pr26

What does this PR do?
What issues does this PR fix or reference?
#
The PR fulfills these requirements:
[ ] Tests for the proposed changes have been added/updated.
[ ] Code linting and formatting was performed.
Functionality Before
<insert gif and/or summary>
Functionality After
<insert gif and/or summary>

closes #26

Codecov Report

Merging #27 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #27   +/-   ##
=======================================
  Coverage   96.05%   96.05%
=======================================
  Files          36       36
  Lines        1241     1241
=======================================
  Hits         1192     1192
  Misses         49       49

Flag
Coverage Δ

#Apex
96.05% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out 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 09fa184...56da181. Read the comment docs.


Added Suggestions with Names

I thought that the suggestions look a little messy while they are seen as url's so I made a feature to allow it have have names whilst also keeping your version of suggestions functionality. I added one command to your COMMANDS and a new COMMANDS map under the original in a comment to show how it works. I don't think there are any bugs or stuff just to be sure. Awesome project btw, using it everyday.

Hi @furkanunsalan, I appreciate the time you took to add this. Couple notes after a quick look:
We can achieve the same via commands without names. I prefer to avoid code changes/feature additions if possible. Would this approach work for your needs? I agree that the suggestion object format is a little cleaner but this PR is not quite ready and I don't expect you to put more time into it.
You removed suggestion highlighting. That is something I would like to keep.
DDG suggestions are broken for site specific searches. e.g type g some text to search GitHub and all the suggestions come back as [object Object].
I should add some tests E2E tests (:

oh i haven't seen those bugs totally my bad but you are right some commands without names are probably just fine :D maybe i will look into this in the future thanks for the feedback


Ordering of overlay layers do not match between admin and project view

After publishing changes to the overlay layers in the FSM project (next.seasket.ch/fsm), I noticed that the order of folders doesn't match between what I see in the admin view and the project view.

Looks like order is saving properly in the admin interface. I'm guessing the publishing step isn't copying the sortOrder field.

I believe this should be fixed now. Can you see if this works better next time you do a publish @wmcclin?

Seems to work great! Thanks!


Clean Up the Contributing Documentation and Process: An Opera, Reincarnated

Please send your PR's the develop branch.
Don't forget to add the change to changelog.md.

Does the pull request solve a related issue? [yes | no] no
If so, can you reference the issue?
What does the pull request accomplish? (please list)

Update the Gruntfile with a more functional StyleLint implementation.
Update the .github templates and information with more modern information.

If it includes major visual changes please add screenshots.

So its completely done now? 😁

I think so... unless some of my other ideas go through. For now, it's done. I'll submit those as separate pull requests.


Relicense to MIT/Apache-2.0/Zlib

@cedric-h @Noxime Due to some concerns brought to my attention I want to relicense the lib to a triple license MIT/Apache-2.0/Zlib. As you are the other contributors, I need your sign off, could you just copy the following:

I give permission for my contributions to the rend3 repository to be relicensed from MPL-2.0 to MIT/Apache-2.0/Zlib.

Cheers.

Sounds good to me!
I give permission for my contributions to the rend3 repository to be relicensed from MPL-2.0 to MIT/Apache-2.0/Zlib.

Sounds good to me!
I give permission for my contributions to the rend3 repository to be relicensed from MPL-2.0 to MIT/Apache-2.0/Zlib.

I give permission for my contributions to the rend3 repository to be relicensed from MPL-2.0 to MIT/Apache-2.0/Zlib.

I give permission for my contributions to the rend3 repository to be relicensed from MPL-2.0 to MIT/Apache-2.0/Zlib.

Thank you both, closed in a40c9bdf93eeff8a8f725ce54c0eea373c836fba

Thank you both, closed in a40c9bdf93eeff8a8f725ce54c0eea373c836fba


Memory leak in analysis tree construction (TIGRESS)

There appears to be a memory leak somewhere in the analysis tree construction for TIGRESS data. The RAM usage just increases constantly throughout the analysis tree building process (eventually maxing out the RAM on midtig02). This is with the latest version pulled as of a few hours ago.
I asked @SmithJK and was told similar things were not seen with the recent versions and GRIFFIN data, so it might be a TIGRESS exclusive issue.
I ran valgrind, the (more significant) outputs of which can be found on the ELog (elog.triumf.ca/Tigress/TIGRESS/12948).
This was all done on the Tiguser account, with the trees of interest in the SPICETestAnalysis directory.
On a perhaps related note: We have recently started receiving _M_range_check terminations with TIGRESS data, seemingly associated with Fragments containing zero-length Charge vectors. This was solved trivially by the inclusion of a Charge.size()>0 requirement locally.

When you say the most recent version, do you mean on the master branch, or on the leangrsi branch?

On Aug 26, 2015, at 9:43 PM, jhenderson88<EMAIL_ADDRESS>wrote:
There appears to be a memory leak somewhere in the analysis tree construction for TIGRESS data. The RAM usage just increases constantly throughout the analysis tree building process (eventually maxing out the RAM on midtig02). This is with the latest version pulled as of a few hours ago.
On a perhaps related note: We have recently started receiving _M_range_check terminations with TIGRESS data, seemingly associated with Fragments containing zero-length Charge vectors. This was solved trivially by the inclusion of a Charge.size()>0 requirement locally.
I asked @SmithJK https://github.com/SmithJK and was told similar things were not seen with the recent versions and GRIFFIN data, so it might be a TIGRESS exclusive issue.
I ran valgrind, the (more significant) outputs of which can be found on the ELog (elog.triumf.ca/Tigress/TIGRESS/12948).
This was all done on the Tiguser account, with the trees of interest in the SPICETestAnalysis directory.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/457.

The master branch.

Ok. This is likely a question for @pcbend and Steffan. This is very strange as nothing has really been changed in something that would affect this in a few months. Is this on new data only? Could it be something new in the actual data that is exposing a bug that had existed previously?

On Aug 26, 2015, at 9:51 PM, jhenderson88<EMAIL_ADDRESS>wrote:
The master branch.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135237955.

I ran the data from our recent SHARC run and saw something similar, although the data files there were only ~100 MB so it wasn't so pronounced. This was not seen for the TIP experiment in April/May.

Can you try running the sort code on that TIP data and see if the problem is still there?

This doesn't seem to happen for the TIP data. However, for the TIP experiment we took waveforms for just about everything, so while the amount of data is the same we actually have ten times fewer actual events.

Hmmm. This makes it difficult to pin point though. This problem could be older than that experiment because you may not have seen it then?

On Aug 26, 2015, at 10:18 PM, jhenderson88<EMAIL_ADDRESS>wrote:
This doesn't seem to happen for the TIP data. However, for the TIP experiment we took waveforms for just about everything, so while the amount of data is the same we actually have ten times fewer actual events.
—
Reply to this email directly or view it on GitHub.

Agreed. There is a potential complication here in that the SPICE detectors are in the data stream (albeit currently disguised as TIP detectors). I am going to quickly take some pure TIGRESS data to see what happens there.

Just for information.. GRIFFIN used to balloon up too on the master branch. It never caused our computers to crash, but it was big. This is what sparked the leangrsi branch. It uses much less memory, and less hard-disk. We are planning on getting all of the Tigress side integrated very soon and release it as the master version.

On Aug 26, 2015, at 9:51 PM, jhenderson88<EMAIL_ADDRESS>wrote:
The master branch.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135237955.

Just to clarify on that note, this is not causing the sort to crash, only to eat through a huge fraction of the machine's memory (99.8% or 30 GB) and therefore take 20-30 minutes to sort every subrun file.

Sounds like fat-grsi problems. That problem was probably always there but Tigress data is usually small. This isn’t actually a memory leak, it’s more that the data structures are big, and you need a lot of them. The events are also so large that it takes a significant amount of time to write them, causing a queue of them to build up in memory. Not only this, but the memory to becomes highly fragmented and empty space is less efficiently reused. Try this comparison, and then maybe revert the code a few months back and try again. If it’s still there, leangrsi is the way to go. However, Tigress isn’t fully integrated yet (can be done soon), and that branch is having a bit of “compilation” issues right now.
I’m not sure where @pcbend is with this right now, but if you take a look at TGriffin and TGriffinHit, that’s the way we want to head. Minimal information stored in the specific detectors, and minimal information written to disk. Anything we can pull out on-the-fly (detector number, energy, add back, crystal number, etc.) we do so. These data are then stored in transient data members (marked //! in the header file). This essentially means they are not written to disk but exist in the object. We can calculate them once, and then can they can be reused quickly.
I believe Peter was working on this, but I know he has lots of other stuff to do so I’m not sure how far along he is. I’m also trying to get some stuff done so any one that wants to help in this regard would be most appreciated.

On Aug 26, 2015, at 10:40 PM, jhenderson88<EMAIL_ADDRESS>wrote:
Just to clarify on that note, this is not causing the sort to crash, only to eat through a huge fraction of the machine's memory (99.8% or 30 GB) and therefore take 20-30 minutes to sort every subrun file.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135262374.

Can you give me a run number where you see this happen?
On Aug 26, 2015 7:40 PM, "jhenderson88"<EMAIL_ADDRESS>wrote:

Just to clarify on that note, this is not causing the sort to crash, only
to eat through a huge fraction of the machine's memory (99.8% or 30 GB) and
therefore take 20-30 minutes to sort every subrun file.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135262374
.

Run35568 was the one I've been working on. Calibration files, etc. can be found in the tiguser/SPICETestAnalysis directory.
The speed isn't essential. I was more concerned with breaking something before I started implementing TSpice (and other associated detectors).

I think this is a seperate issue honestly; I believe greg recently changed
the midas shared memory which will change the fragments per midas  event
packing.  With the way things are set up, I can see a senerio where it is
trying to create very large fragments and bad things happen.
On Aug 26, 2015 7:49 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Sounds like fat-grsi problems. That problem was probably always there but
Tigress data is usually small. This isn’t actually a memory leak, it’s more
that the data structures are big, and you need a lot of them. The events
are also so large that it takes a significant amount of time to write them,
causing a queue of them to build up in memory. Not only this, but the
memory to becomes highly fragmented and empty space is less efficiently
reused. Try this comparison, and then maybe revert the code a few months
back and try again. If it’s still there, leangrsi is the way to go.
However, Tigress isn’t fully integrated yet (can be done soon), and that
branch is having a bit of “compilation” issues right now.
I’m not sure where @pcbend is with this right now, but if you take a look
at TGriffin and TGriffinHit, that’s the way we want to head. Minimal
information stored in the specific detectors, and minimal information
written to disk. Anything we can pull out on-the-fly (detector number,
energy, add back, crystal number, etc.) we do so. These data are then
stored in transient data members (marked //! in the header file). This
essentially means they are not written to disk but exist in the object. We
can calculate them once, and then can they can be reused quickly.
I believe Peter was working on this, but I know he has lots of other stuff
to do so I’m not sure how far along he is. I’m also trying to get some
stuff done so any one that wants to help in this regard would be most
appreciated.

On Aug 26, 2015, at 10:40 PM, jhenderson88<EMAIL_ADDRESS>wrote:
Just to clarify on that note, this is not causing the sort to crash,
only to eat through a huge fraction of the machine's memory (99.8% or 30
GB) and therefore take 20-30 minutes to sort every subrun file.
—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135262374
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135263270
.

Also tspice already exists, it merely needs to be copy over from "grsispoon"
On Aug 26, 2015 7:53 PM, "jhenderson88"<EMAIL_ADDRESS>wrote:

Run35568 was the one I've been working on. Calibration files, etc. can be
found in the tiguser/SPICETestAnalysis directory.
The speed isn't essential. I was more concerned with breaking something
before I started implementing TSpice (and other associated detectors).
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135263640
.

Yes, Greg changed it to be more in line with what GRIFFIN was using.
Re: TSpice, excellent. That makes things considerably more straightforward.

OK,  I think I have the bul of the memory leak under wraps.  Some how the
tigress data was not clearing the segment charge.  I am not sure when that
happened but it is fixed on the tiguser account.  I can't push things right
now as my account is in havac getting rid to switch tigress over to
leangrsi.  Shorting the analysis tree is using 20% of the memorty on
grsimid, I believe this is normal for this version of the code.
As for spice, I will copy over what has been done for experiments gone by
tomorrow morning and push the changes onto the master.  Just to note,
TSpice is actually two detectors TSiLi and TS3, I found it to make much
more sense this way.
On Wed, Aug 26, 2015 at 10:56 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Yes, Greg changed it to be more in line with what GRIFFIN was using.
Re: TSpice, excellent. That makes things considerably more straightforward.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135263849
.

Also is something wrong with th odb?  It seems to be failing to make
channels.
And the system memory thing Greg did does not seem to have an effect.
There still appears to be just one Fragment per MidasEvent.
On Wed, Aug 26, 2015 at 11:32 PM, Peter<EMAIL_ADDRESS>wrote:

OK,  I think I have the bul of the memory leak under wraps.  Some how the
tigress data was not clearing the segment charge.  I am not sure when that
happened but it is fixed on the tiguser account.  I can't push things right
now as my account is in havac getting rid to switch tigress over to
leangrsi.  Shorting the analysis tree is using 20% of the memorty on
grsimid, I believe this is normal for this version of the code.
As for spice, I will copy over what has been done for experiments gone by
tomorrow morning and push the changes onto the master.  Just to note,
TSpice is actually two detectors TSiLi and TS3, I found it to make much
more sense this way.
On Wed, Aug 26, 2015 at 10:56 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Yes, Greg changed it to be more in line with what GRIFFIN was using.
Re: TSpice, excellent. That makes things considerably more
straightforward.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135263849
.

Thanks Peter.

On Aug 26, 2015, at 11:32 PM, pcbend<EMAIL_ADDRESS>wrote:
OK, I think I have the bul of the memory leak under wraps. Some how the
tigress data was not clearing the segment charge. I am not sure when that
happened but it is fixed on the tiguser account. I can't push things right
now as my account is in havac getting rid to switch tigress over to
leangrsi. Shorting the analysis tree is using 20% of the memorty on
grsimid, I believe this is normal for this version of the code.
As for spice, I will copy over what has been done for experiments gone by
tomorrow morning and push the changes onto the master. Just to note,
TSpice is actually two detectors TSiLi and TS3, I found it to make much
more sense this way.
On Wed, Aug 26, 2015 at 10:56 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Yes, Greg changed it to be more in line with what GRIFFIN was using.
Re: TSpice, excellent. That makes things considerably more straightforward.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-135263849
.

—
Reply to this email directly or view it on GitHub.

Thanks Peter. The .odb seems OK elsewhere so I'm not sure why it's not passing on to the TChannels, I'll check it tomorrow.

@jhenderson88 , is this issue resolved?

Yes. We're still using a crazy amount of memory, but it is now manageable.

I honestly think this is because you are on the master.

On Sep 2, 2015, at 2:08 PM, jhenderson88<EMAIL_ADDRESS>wrote:
Yes. We're still using a crazy amount of memory, but it is now manageable.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-137194338.

@jhenderson88, how large are the output files that are being written?

The analysis files themselves are only (only?) 1.1GB.

Since this appears to be resolved...


Bug: rolling over the logs db to a new month doesn't work

We implemented this a while ago, but it just failed going from June to July, so something’s not right. It‘ll sort itself out when we restart the service, but we specifically added this so we’d no longer rely on restarts for the rollover.

Closing in favour of https://github.com/greenkeeperio/greenkeeper/pull/846


Avatar performance is worse when using the optimizer

Noticed this issue a while ago, I thought it might've been a random bug in an older version. The issue has persisted no matter the versions,
I only use poiyomi shader and face tracking on my avatar. Everything including the optimizer is of the latest version. Write defaults - On.
The avatar in this example was the worst offender. On other avatars sometimes frame time is only slightly worse, sometimes it's better, but in most cases with either "Full" preset or "Shader Toggles" preset enabled, frame time is worse compared to using no optimizer at all.
Tested performance in an empty world, only 1 full mirror enabled, the closer to the mirror - the worse frame time gets. Worst case frame time is reflected on the screenshots below.
Full preset:

With "Merge Different Property Materials" Disabled:

With "Merge Skinned Meshes" Disabled:

With "Merge Different Property Materials", "Merge Skinned Meshes" and "Write Properties as Static Values" Disabled:

And Finally, without using the optimizer at all:

Thats expected. Merging meshes with shader toggles adds extra code to the shader and you always do skinning & some vertex shader code for all vertices even on disabled stuff.
Animated material properties can also generate a lot of extra code when using the shader toggles setting.
That setting fundamentally trades gpu performance for cpu performance.
If you send the generated assets as described here I can take a look if it generated some truly outrageous stuff or if its just the expected overhead of shader toggles.

Thank you for your response. Here are the assets.
In this case, what settings would you recommend I use if I want to target better GPU performance but still cut down on materials to fit into let's say a medium rating?
TrashBin.zip

@MivaNyan You need to remove materials by atlasing them in one skinned mesh. For example, you have four materials on your clothes. You need to make a material atlas of all four into one using Blender or another optimizer program that makes an atlas of materials.

In this case, what settings would you recommend I use if I want to target better GPU performance but still cut down on materials to fit into let's say a medium rating?

The basic preset. It doesn't change the shaders and still allows for some mesh merging as well as merging of material slots that use the same material.
The better GPU performance you observed in the second to last test is likely due to the merge same ratio blendshapes if I were to guess.
There isn't really much for my optimizer to do GPU wise for shaders that already have their own lock in like poi. For shaders that don't have a lock in however Write Properties as Static Values tries to be a generic version of lock in and can help a lot.

ok i had a look at some of the shaders it generated. seems fine except for poi fur. poi locking does one crucial optimization that mine doesnt. please try again with optimizer set to shader toggles while keeping the fur materials locked in instead of unlocked. im curious how much of the performance difference is due to that.

Here's the result with "Shader toggles" preset and fur material locked:

@Toys0125 thanks for your recommendation, I'm already atlasing some materials!

I've investigated this a bit more and found that some of my code generation does harm poi fur performance considerably.
Specifically I generate a branch that samples all the textures that have a sampler at the start of the fragment shader to make sure the shader compiler doesn't get rid of the samplers. Putting that code at the end of the frag instead pretty much negates the performance penalty over poi native lock in in my test case.


chore: release v1.0.0-beta.4

This pull request prepares the following release:

Repository
Branch
Update
Change

smf
releases/v1.0.0-beta.4
prerelease
1.0.0-beta.3 → 1.0.0-beta.4

Release Summary
This is going to be published with the following command:
npm publish --tag beta
Merging Instructions
When merging this pull request, you need to Squash and merge and make sure that the title starts with chore: release v1.0.0-beta.4.

See details
After that, a commit chore: release v1.0.0-beta.4 will be added and you or your CI can run shipjs trigger to trigger the release based on the commit.

This pull request is automatically generated by Ship.js.

Pull Request Test Coverage Report for Build 721593626

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 19.643%

Totals

Change from base Build 721592264:
0.0%

Covered Lines:
19

Relevant Lines:
90

💛  - Coveralls


Add files via upload

jenkins pipeline concept

I reverted all the contributions

You added contributing guidelines and code of conduct to books too.


⚠ Palworld Tunnel (Connection URL) has degraded performance

In 6fb2778, Palworld Tunnel (Connection URL) ($PG_PANEL/tstat.txt) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: Palworld Tunnel (Connection URL) performance has improved in d0b1fde after 20 minutes.


Convert HumanSkeleton to Kotlin

Needed for https://github.com/SlimeVR/SlimeVR-Server/pull/787

Doesn't compile on CI, pls fix.

@ButterscotchV fixed


use create() batch insert have error

Your Question
I have a large array that needs to be inserted into mysql, so I wrote a function, passing the array as a parameter, and doing business processing in the function. However, in order to improve the versatility of the interface, I set the parameter to []interface{ }, the result is a memory out of bounds or null pointer exception. But if you don't use []interface{}, there will be no problem. Please tell me what I can do to improve the versatility of the function.

The document you expected this should be explained

Expected answer

Can you provide a demo?
Actually it's impossible for others to know what you are inferring to.

what is the function you are using?
what version of gorm you are using?
what version of golang you are using?
what is the "memory out of bounds or null pointer exception"

I suspect you are using Create method and passing an slice of interface, just like the following:
type Product struct {
        ID   uint64
        Name string
}
func demoFunc(db *gorm.DB, a []interface{}) error {
        return db.Create(&a).Error
}

func demoCaller(db *gorm.DB) {
        a := make([]interface{}, 2)
        a[0] = Product{Name: "product0"}
        a[1] = Product{Name: "product1"}
}

but what I got is:

So can you provide a demo? Or we are just wasting time here.

Can you provide a demo? Actually it's impossible for others to know what you are inferring to.

what is the function you are using?
what version of gorm you are using?
what version of golang you are using?
what is the "memory out of bounds or null pointer exception"

I suspect you are using Create method and passing an slice of interface, just like the following:
type Product struct {
        ID   uint64
        Name string
}
func demoFunc(db *gorm.DB, a []interface{}) error {
        return db.Create(&a).Error
}

func demoCaller(db *gorm.DB) {
        a := make([]interface{}, 2)
        a[0] = Product{Name: "product0"}
        a[1] = Product{Name: "product1"}
}

but what I got is:
So can you provide a demo? Or we are just wasting time here.

I user create()
The gorm version I am using is v1.25.5
The golang version I am using is go1.20.5 windows/amd64

I define function following：
`func batchInsert(batchSize int, arrStruct []interface{}, tableName string) error {
totalStructs := len(arrStruct)
numBatches := (totalStructs + batchSize - 1) / batchSize
for i := 0; i < numBatches; i++ {
start := i * batchSize
end := (i + 1) * batchSize
if end > totalStructs {
end = totalStructs
}
	batch := arrStruct[start:end]
	// 插入当前批次的结构体数组
	err := common.GORMICU.Table(tableName).Create(batch).Error
	if err != nil {
		return err
	}
	log.Printf("%s表第 %d 批次插入成功！\n", tableName, i+1)
}
return nil

}`
I want to implement a universal batch insertion interface. Because we want to calculate the length of the slice, we must use [] inteface {}, but [] inteface {} is reported as an error when sending to the conference

@13512263278
I think there is a CreateInBatch method in gorm, you could just use that method or just copy from it


try setting the credentialHost differently...

with a single-project build it resolved that setting from
sonatypeCredentialHost, but this somehow doesn't work for multi project
builds

https://github.com/joernio/ghidra2cpg/pull/17 didn't quite cut it, but i'm hopefull for this one :)

yay :)


Fixed broken link for katib/suggestion-nasrl dockerfile

In https://www.kubeflow.org/docs/reference/images/

Dockerfile location for katib/suggestion-nasrl:
https://github.com/kubeflow/katib/blob/master/cmd/suggestion/nasrl/v1alpha3/Dockerfile
-> 404
This may be caused by recent directory/folder restructure in PR 1143

Thanks @janeman98!
/lgtm
/approve

Thanks @sarahmaddox !


A0-2120: Make yaml-validate workflow fail on errors

It's better we actually make that YAML Validate workflow fail on error.  We have almost overlooked one syntax mistake in another PR.
Now github-workflows-validator always exits with code 0, at least for now (we were about to change it later once workflows got tidied up).  However, all errors are prefixed with E so we can check if these appear in the output and if so add exit 1.

contracts-tests workflow is broken so I'm not sure what to do with it.  We can force-squash-and-merge it and ignore the problem, or naturally fix it (tidying up that workflow will probably take some time as we need to build a new dev environments for contracts, one that would be similar to benjamin).
Anyway, feel free to modify and/or merge that PR whilst I'll be on holidays.


Change minigzip to compile against zlibstatic.

This PR is done so that cmake output binaries match configure output binaries. It will help fix the gap we are seeing in performance testing between the two build systems. This should help address #516.
For CI, we have to keep everything statically linked due to issues with qemu powerpc configurations. I have previously commented in cmake.yml. That and also possible issues with code coverage results is why -DBUILD_SHARED_LIBS=OFF is explicitly stated in CI. I believe that shared libraries are still tested in CI through configure script.
When not using cmake for CI (or when BUILD_SHARED_LIBS is not defined) then minigzip and minigzip64 will link statically against zlibstatic, in this instance all of the tests still link dynamically.

Is this the bug ci works around with static linking?
https://bugs.launchpad.net/bugs/1701798

It could be. I know in the yaml I had written:

Shared libaries turned off for qemu ppc* and sparc..
I had experienced the same problem not too long ago again with powerpc and qemu.


Animated.Value resets if not rendered

🐛 Bug Report
If render() method does not return an Animated.View that uses the Animated.Value we are animating the Animated.Value resets and will have a wrong value on the next render() call. This goes against the basic principle that render() method should be a pure function without side effects.
I suspect that this behavior also causes bugs/freezes when shouldRasterizeIOS set to true.
To Reproduce

Animate a Value
Using state show/hide the Animated.View that is using the Value periodically
Animated.Value will keep reseting

Expected Behavior
Animated.Value._value should not depend on the results of render() method
Code Example
<EMAIL_ADDRESS>Environment
React Native Environment Info:
System:
OS: macOS 10.14.2
CPU: (4) x64 Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz
Memory: 859.86 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 8.3.0 - ~/.nvm/versions/node/v8.3.0/bin/node
npm: 6.4.1 - ~/.nvm/versions/node/v8.3.0/bin/npm
Watchman: 4.7.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
Android SDK:
Build Tools: 26.0.1
IDEs:
Android Studio: 3.3 AI-182.5<IP_ADDRESS>99772
Xcode: 10.0/10A255 - /usr/bin/xcodebuild
npmPackages:
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1

Could be related to: https://github.com/facebook/react-native/issues/23712

@CatapultJesse Yup, the same issue.

Duplicate of #23712


Fix query parameter regex in trace.Sanitize()

Description of the Change
The previous regular expression, &password=[^&}*&, did not match password parameters at the end of the query string. In that case it also ate the rest of the input, until the next & character.
I replaced it with an expression that is, sadly, rather complicated, but should match all characters that can be part of a query parameter value as per the RFC.
This change does not address passwords in the userinfo URI component.
Alternate Designs
trace.Sanitize() could find URIs in the input string and parse them, then cleanly replace the userinfo component and parameter values
Applicable Issues
#1375

Thanks for the fix!!


WCAG violation: Special character in title

Description of the bug
According to WCAG 2.1 SC 2.4.2:
The page's <title> element should not contain special characters, such as ~ or ^.

Steps To Reproduce
No need for steps, frontend adds the special character.

Additional Information
No response

Yes, i suggest we swap it with a "-" as in the third example from technique G88
As a sidenote, i cant seem to find any information that this is a part of 2.4.2 Page title. Do you know where it comes from?

@Febakke We had a "UU"-tester run through our application and used the software called ARC ToolKit. It was this software that discovered the violation.


imports/aframe/aframe-graph.tsx(1,1): error TS1208: 'aframe-graph.tsx' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.

WARN[0000]<EMAIL_ADDRESS>`version` is obsolete
[+] Running 37/2
 ✔ minio Pulled             10.1s B Pulling 10.1s
 ✔ storage Pulled           5.3s .3s ⣿⣿⣿⣿] 32.71MB / 32.71MB Pulling 5.3s s
WARN[0010] volume "deep-db-data" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume
[+] Running 4/4
 ✔ Container deep-postgres        Running0.0s
 ✔ Container deep-minio           Started11.2s
 ✔ Container deep-hasura          Started11.2s
 ✔ Container deep-hasura-storage  Started1.5s
npm warn using --force Recommended protections disabled.

><EMAIL_ADDRESS>package:build
> tsc --project tsconfig.json

imports/aframe/aframe-graph.tsx(1,1): error TS1208: 'aframe-graph.tsx' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.
imports/test.ts(1,1): error TS1208: 'test.ts' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.
npm error Lifecycle script `package:build` failed with error:
npm error code 2
npm error path /workspace/dev/packages/deepcase
npm error workspace<EMAIL_ADDRESS>npm error location /workspace/dev/packages/deepcase
npm error command failed
npm error command sh -c tsc --project tsconfig.json
exit

🍊 This task ran as a workspace prebuild
⏱ Well done on saving 5 minutes

This error is reproducible:
gitpod /workspace/dev/packages/deepcase (main) $ npm run package:build

><EMAIL_ADDRESS>package:build
> tsc --project tsconfig.json

imports/aframe/aframe-graph.tsx:1:1 - error TS1208: 'aframe-graph.tsx' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.

1 // import * as THREE from "three";

imports/test.ts:1:1 - error TS1208: 'test.ts' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.

1

Found 2 errors in 2 files.

Errors  Files
     1  imports/aframe/aframe-graph.tsx:1
     1  imports/test.ts:1
npm ERR! Lifecycle script `package:build` failed with error:
npm ERR! Error: command failed
npm ERR!   in workspace<EMAIL_ADDRESS>npm ERR!   at location: /workspace/dev/packages/deepcase


Reset repo to restart from scratch

Prior to this commit, the specs in this repo have grown somewhat haphazardly, making them hard to edit and evolve in the desired direction. We've agreed to start fresh. Much of the content can and will be reused as we begin filling in these specs again, though it will be subjected to review again before merging.

A few options:

merge this, keep building on main BUT must make a new branch to preserve easy github navigation to the old stuff
move the main branch to another branch and reset the history of the main branch
create a new branch and make it the default branch on github

Option 2 is the cleanest but it edits history, which is potentially problematic when syncing up local code.
No strong opinions otherwise.

Let's do 1. from @norswap 's suggestions, so we can merge this as soon as we clone current to another branch

Modified + rebase on top of main to remove files that were added by the recently merged PRs.


[8da4w] Add support to skip quantizing some layers

Summary: Certain layers in llama3 are more sensitive to quantization than others. In general, we need a mechanism to skip quantizing certain parts of the model. This commit adds such a mechanism by allowing users to pass in a function that filters out layers to be skipped during module swap.
Test Plan:
python test/quantization/test_quant_api.py -k test_8da4w_quantizer_skip_quantize_filter python test/quantization/test_qat.py -k test_qat_8da4w_quantizer_skip_quantize_filter
Reviewers: jerryzh168, cpuhrsch
Subscribers: jerryzh168, cpuhrsch, supriyar

Is it possible to apply GPTQ layer by layer and just skip it from the outside instead of replicating pattern matching logic within the constructor? Seems more flexible to keep GPTQ as is and teach it how to operate on sub-model level. Happy to chat further.

Sure it's possible, but I think it's less user friendly. For example, let's say you want to skip quantizing all the v_proj layers in llama3. Right now the only way is to manually specify all the other layers that need quantizing, which is verbose and potentially error prone. I feel it's more natural to express this as an exclusion and it will make our APIs easier to use. What do you think?

@andrewor14 , is it possible to do
for name, mod in model.named_modules():
    if "v_proj" in name:
        continue
    <apply GPTQ>

@andrewor14 , is it possible to do
for name, mod in model.named_modules():
    if "v_proj" in name:
        continue
    <apply GPTQ to mod>

Yeah, that looks reasonable. I'll close this PR


IIO is not returning any value

hi Team,
We are getting the following error message in one of our test server. Not sure why the IIO related details are not popping up. Any help would be much appreciated.
Note. I am running PCM as a docker image. In my host machine, I could see the pci.ids file. But I cant see the pci.ids in the docker image. Should I bind the hwdata into the container to get this metrics ?
pcm-iio
Intel(r) Performance Counter Monitor ($Format:%ci ID=%h$)
This utility measures IIO information
=====  Processor information  =====
Linux arch_perfmon flag  : yes
Hybrid processor         : no
IBRS and IBPB supported  : yes
STIBP supported          : yes
Spec arch caps supported : yes
Max CPUID level          : 27
CPU family               : 6
CPU model number         : 106
Number of physical cores: 64
Number of logical cores: 128
Number of online logical cores: 128
Threads (logical cores) per physical core: 2
Num sockets: 2
Physical cores per socket: 32
Last level cache slices per socket: 32
Core PMU (perfmon) version: 5
Number of core PMU generic (programmable) counters: 8
Width of generic (programmable) counters: 48 bits
Number of core PMU fixed counters: 4
Width of fixed counters: 48 bits
Nominal core frequency:<PHONE_NUMBER> Hz
IBRS enabled in the kernel   : yes
STIBP enabled in the kernel  : no
The processor is not susceptible to Rogue Data Cache Load: yes
The processor supports enhanced IBRS                     : yes
Package thermal spec power: 185 Watt; Package minimum power: 84 Watt; Package maximum power: 652 Watt;
INFO: Linux perf interface to program uncore PMUs is present
Socket 0: 4 memory controllers detected with total number of 8 channels. 3 UPI ports detected. 4 M2M (mesh to memory)/B2CMI blocks detected. 0 HBM M2M blocks detected. 0 EDC/HBM channels detected. 0 Home Agents detected. 3 M3UPI/B2UPI blocks detected.
Socket 1: 4 memory controllers detected with total number of 8 channels. 3 UPI ports detected. 4 M2M (mesh to memory)/B2CMI blocks detected. 0 HBM M2M blocks detected. 0 EDC/HBM channels detected. 0 Home Agents detected. 3 M3UPI/B2UPI blocks detected.
Socket 0: 1 PCU units detected. 6 IIO units detected. 6 IRP units detected. 32 CHA/CBO units detected. 0 MDF units detected. 1 UBOX units detected. 0 CXL units detected. 0 PCIE_GEN5x16 units detected. 0 PCIE_GEN5x8 units detected.
Socket 1: 1 PCU units detected. 6 IIO units detected. 6 IRP units detected. 32 CHA/CBO units detected. 0 MDF units detected. 1 UBOX units detected. 0 CXL units detected. 0 PCIE_GEN5x16 units detected. 0 PCIE_GEN5x8 units detected.
Initializing RMIDs
Detected Intel(R) Xeon(R) Gold 6338N CPU @ 2.20GHz "Intel(r) microarchitecture codename Icelake-SP" stepping 6 microcode level 0xd0003d1
/usr/share/hwdata/pci.ids file is not available. Ensure that the "hwdata" package is properly installed or download https://raw.githubusercontent.com/pciutils/pciids/master/pci.ids and copy it to the current directory.
Error info:event config file opCode-6-106.txt or /usr/local/share/pcm/opCode-6-106.txt is not available, you can try to manually copy it from PCM source package.
Event configure file have the problem and cause the program exit, please double check it!

I would assume that yes you have to make sure pcm in docker can access those files.


Vite 4 support

New Laravel projects ship with Vite 4 out of the box, but this package doesn't support Vite 4 yet.
Also, this plugin blocks me from upgrading my existing projects to Vite 4.

v1.0.2 with vite 4 support has now been released.

Quick, thanks! 🔥


Replace hanging div with closing p tag.

This Pull Request improves index.html by updating the markup's hanging </div> with a closing p tag.
cc/ @stevecat for review.

Thank you @francisfuzz! This looks great :+1:


dnf-plugins-core: init at 4.4.3

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

Thanks for your review.

Please follow the contributing guide when naming your commits.

I'm sorry, I don't get whats wrong with the name of my commit, could you please give me a hint?

I'm sorry, I don't get what's wrong with the name of my commit, could you please give me a hint?

First of all, I should revisit my reply template and add the link to the headline directly. 😅
Also I've just noticed that it kinda turned into a linktree and I also couldn't find what I was searching for on the fast but essentially each package should get it's own commit and that is written somewhere there 😂

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

6 packages built:

python310Packages.dnf4
python310Packages.dnf4.man
python310Packages.dnf4.py
python311Packages.dnf4
python311Packages.dnf4.man
python311Packages.dnf4.py

LGTM, but the ofborg eval is still weird...
@ofborg build python310Packages.dnf4 python310Packages.dnf4.passthru.tests python311Packages.dnf4 python311Packages.dnf4.passthru.tests python310Packages.dnf-plugins-core python310Packages.dnf-plugins-core.passthru.tests python311Packages.dnf-plugins-core python311Packages.dnf-plugins-core.passthru.tests dnf4 dnf4.passthru.tests

LGTM, but the ofborg eval is still weird...

Yes, it's indeed a bit weird. But I'm not sure what to do about it.

nixpkgs-review would discover it if it didn't use the ofborg eval
$ nix-env --extra-experimental-features no-url-literals --option system x86_64-linux -f . -qaP --xml --out-path --show-trace --no-allow-import-from-derivation --meta  | grep -E 'attrPath=".*dnf'
  <item attrPath="dnf-plugins-core" name="dnf-plugins-core-4.4.3" outputName="out" pname="dnf-plugins-core" system="x86_64-linux" version="4.4.3">
  <item attrPath="dnf4" name="dnf4-4.18.2" outputName="out" pname="dnf4" system="x86_64-linux" version="4.18.2">
  <item attrPath="dnf5" name="dnf5-5.1.8" outputName="out" pname="dnf5" system="x86_64-linux" version="5.1.8">
  <item attrPath="ifdnfc" name="ifdnfc-2016-03-01" outputName="out" pname="ifdnfc" system="x86_64-linux" version="2016-03-01">
  <item attrPath="python310Packages.libdnf" name="libdnf-0.72.0" outputName="py" pname="libdnf" system="x86_64-linux" version="0.72.0">
  <item attrPath="libdnf" name="libdnf-0.72.0" outputName="out" pname="libdnf" system="x86_64-linux" version="0.72.0">
  <item attrPath="python311Packages.libdnf" name="libdnf-0.72.0" outputName="py" pname="libdnf" system="x86_64-linux" version="0.72.0">
  <item attrPath="microdnf" name="microdnf-3.10.0" outputName="out" pname="microdnf" system="x86_64-linux" version="3.10.0">
  <item attrPath="python310Packages.dnf-plugins-core" name="python3.10-dnf-plugins-core-4.4.3" outputName="out" pname="python3.10-dnf-plugins-core" system="x86_64-linux" version="4.4.3">
  <item attrPath="python310Packages.dnf4" name="python3.10-dnf4-4.18.2" outputName="out" pname="python3.10-dnf4" system="x86_64-linux" version="4.18.2">
  <item attrPath="python310Packages.dnfile" name="python3.10-dnfile-0.14.1" outputName="out" pname="python3.10-dnfile" system="x86_64-linux" version="0.14.1">
  <item attrPath="python311Packages.dnf-plugins-core" name="python3.11-dnf-plugins-core-4.4.3" outputName="out" pname="python3.11-dnf-plugins-core" system="x86_64-linux" version="4.4.3">
  <item attrPath="python311Packages.dnf4" name="python3.11-dnf4-4.18.2" outputName="out" pname="python3.11-dnf4" system="x86_64-linux" version="4.18.2">
  <item attrPath="python311Packages.dnfile" name="python3.11-dnfile-0.14.1" outputName="out" pname="python3.11-dnfile" system="x86_64-linux" version="0.14.1">
  <item attrPath="vimPlugins.mkdnflow-nvim" name="vimplugin-mkdnflow.nvim-2023-11-28" outputName="out" pname="vimplugin-mkdnflow.nvim" system="x86_64-linux" version="2023-11-28">

Should also show up on search.nixos.com.


unknow memory error

don't know why
but the trace back shows that maybe something with memory
but i've thyed many times
PS: i'm running 3 minecraft java server and 2 Bungee Cord server when i run it

It's difficult to guess what the issue is, because it's being returned from Windows. It does not seem to be generated inside of pyglet, which makes it difficult to help you. The "Access violation" error seems to be common with many different applications.
My guess is that:

Driver issue (cannot create so many OpenGL contexts on the same machine).
Not enough system memory.

If it's #2, maybe you can change the Minecraft JVM settings to use less memory?

hmmmm
this issue may not cause by pyglet
will close


Analyzer tests should be decoupled from analyzer base class

Right now, many of the tests for the analyzers work by running the analyze_log_stream method from the analyzer base class, meaning if we change the behavior of analyze_log_stream, these tests will fail despite changing nothing about the analyzers themselves. Instead, these tests should probably run the individual read_log_line and report methods of the analyzer they are testing (like the info_counter_test is doing, for example), so that they will only fail if those specific methods are changed incorrectly.

The specific tests with this issue are the duplicate log messages test, the error counter test, and the warning analyzer test

I'm working on this


[NEW ICON] OpenStack

Skill Name
OpenStack
Why?
Popular private cloud service many organizations and individuals (myself included) use for things like testing code. Similar to OpenShift.
Reference Image
SVG, w/ wordmark: https://upload.wikimedia.org/wikipedia/commons/e/e6/OpenStack®_Logo_2016.svg
Without wordmark: https://avatars.githubusercontent.com/u/324574?s=280&v=4

Added in 9e1ef97!


Remove broken conditional using an undefined inputs variable

This code was moved from _subst to options2hash but the local variable inputs was never passed to the new method.  This code has been in place since the commit below so it's safe to assume it's never used as it would fail everytime.  Note, I've updated options2hash to no longer return an always nil object and the callers to no longer expect it, which they never used anyway.
From commit: 481b6efa72d10e88a4100c6383ff02a483be29b3
Date:   Fri Aug 8 18:28:59 2008 +0000

good find


Bug Report: Genesis Plugin Custom Skull Item Creation Error

Description of the Bug
The Genesis plugin encounters an error when attempting to create a custom skull item in the shop. The specific issue is that the profile name for the custom skull exceeds the maximum allowed length of 16 characters, causing an IllegalArgumentException. This results in the plugin failing to create the item and suggesting that the issue is likely due to configuration mistakes.
Steps to Reproduce
Configure a shop in the Genesis plugin that includes a custom skull item.
Ensure the profile name for the custom skull exceeds 16 characters.
Start the server and observe the error in the logs.
Expected Behavior
The Genesis plugin should handle the creation of custom skull items without exceeding the profile name length constraint or provide a more user-friendly error message indicating the exact problem.
Actual Behavior
The plugin throws an IllegalArgumentException and fails to create the custom skull item due to the profile name exceeding 16 characters.
Suggested Fix
Ensure that all profile names for custom skulls in the shop configuration are 16 characters or fewer. Additionally, the plugin could be improved to validate the length of profile names before attempting to create the item, providing a clear error message if the constraint is violated.
Version Info
Genesis: 1.0.0-R0.4-SNAPSHOT
Paper: This server is running Paper version 1.21-54-master@f250ec0 (2024-07-11T16:05:17Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are 45 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 1.21-55-7bd22b1 (MC: 1.21)
Additional context
log: https://paste.denizenscript.com/View/124792
spark: https://spark.lucko.me/tJAC5yLAID

You're using the base-64 encoded texture string for the skulls, correct? Could you send an example?

Could you also try grabbing a newer build from our Discord and see if you still have issues?


[New Feature]: Mouse moving glowing effect

🎮 feature Request
I will add the glowing effect where ever mouse moves in the screen giving the webiste another level of looks .
Point down the features

Like that  but i will change the color according to this website .
Please assign me this under Gssoc. I would like to contribute in this.


migrate to c++20

Summary

Updates codebase to use C++20
Removes testing on gcc 10 and clang 10

Benchmarks
Running benchmarks with sudo build/benchmarks/bbc_bench
Before
--------------------------------------------------------------------------------------------
Benchmark                                  Time             CPU   Iterations UserCounters...
--------------------------------------------------------------------------------------------
BasicBench_AdaURL_href                  2205 ns         2205 ns       314272 GHz=4.81764 cycle/byte=12.0915 cycles/url=1.15944k instructions/byte=57.0452 instructions/cycle=4.71778 instructions/ns=22.7285 instructions/url=5.47k ns/url=240.667 speed=391.386M/s time/byte=2.55502ns time/url=244.998ns url/s=4.08166M/s
BasicBench_AdaURL_aggregator_href       1371 ns         1370 ns       516598 GHz=5.77944 cycle/byte=8.927 cycles/url=856 instructions/byte=40.6014 instructions/cycle=4.54816 instructions/ns=26.2858 instructions/url=3.89322k ns/url=148.111 speed=629.99M/s time/byte=1.58733ns time/url=152.207ns url/s=6.57M/s
BasicBench_AdaURL_CanParse               987 ns          987 ns       708179 GHz=7.05344 cycle/byte=7.49479 cycles/url=718.667 instructions/byte=33.2306 instructions/cycle=4.43383 instructions/ns=31.2737 instructions/url=3.18644k ns/url=101.889 speed=874.13M/s time/byte=1.14399ns time/url=109.696ns url/s=9.11607M/s
BasicBench_whatwg                       4341 ns         4341 ns       160950 GHz=4.01934 cycle/byte=19.9849 cycles/url=1.91633k instructions/byte=98.9224 instructions/cycle=4.94985 instructions/ns=19.8951 instructions/url=9.48556k ns/url=476.778 speed=198.82M/s time/byte=5.02967ns time/url=482.29ns url/s=2.07344M/s
BasicBench_CURL                        10698 ns        10690 ns        65995 GHz=3.51628 cycle/byte=43.8007 cycles/url=4.2k instructions/byte=214.015 instructions/cycle=4.88611 instructions/ns=17.1809 instructions/url=20.5217k ns/url=1.19444k speed=80.7275M/s time/byte=12.3873ns time/url=1.18781us url/s=841.886k/s

After
--------------------------------------------------------------------------------------------
Benchmark                                  Time             CPU   Iterations UserCounters...
--------------------------------------------------------------------------------------------
BasicBench_AdaURL_href                  2138 ns         2138 ns       326689 GHz=4.86541 cycle/byte=11.9803 cycles/url=1.14878k instructions/byte=55.2283 instructions/cycle=4.60992 instructions/ns=22.4292 instructions/url=5.29578k ns/url=236.111 speed=403.656M/s time/byte=2.47735ns time/url=237.551ns url/s=4.20963M/s
BasicBench_AdaURL_aggregator_href       1331 ns         1331 ns       528905 GHz=5.65641 cycle/byte=8.73696 cycles/url=837.778 instructions/byte=40.5713 instructions/cycle=4.64363 instructions/ns=26.2663 instructions/url=3.89033k ns/url=148.111 speed=648.612M/s time/byte=1.54175ns time/url=147.837ns url/s=6.7642M/s
BasicBench_AdaURL_CanParse               949 ns          949 ns       735325 GHz=6.85153 cycle/byte=7.27231 cycles/url=697.333 instructions/byte=32.993 instructions/cycle=4.53681 instructions/ns=31.0841 instructions/url=3.16367k ns/url=101.778 speed=909.01M/s time/byte=1.1001ns time/url=105.487ns url/s=9.47983M/s
BasicBench_whatwg                       4372 ns         4371 ns       160182 GHz=4.03122 cycle/byte=20.0487 cycles/url=1.92244k instructions/byte=98.445 instructions/cycle=4.9103 instructions/ns=19.7945 instructions/url=9.43978k ns/url=476.889 speed=197.427M/s time/byte=5.06515ns time/url=485.692ns url/s=2.05892M/s
BasicBench_CURL                        10625 ns        10624 ns        65867 GHz=3.60184 cycle/byte=43.9942 cycles/url=4.21856k instructions/byte=214.057 instructions/cycle=4.86557 instructions/ns=17.525 instructions/url=20.5257k ns/url=1.17122k speed=81.2314M/s time/byte=12.3105ns time/url=1.18044us url/s=847.141k/s

@anonrig I recommend you bump this version:
https://github.com/ada-url/ada/blob/59cc69351645ece086bb76b2fbdd2eb50614000e/CMakeLists.txt#L39

hey @mikea, do you know by any chance how to fix the fuzzer (oss-fuzz) to compile with C++20? even after adding -std=c++20, it still uses c++17

@anonrig I suggest merging. This is a non-blocking technical issue.
If you introduced a bug (very unlikely) we can fix it later.

@lemire before merging this, should we release a new version with @CarlosEduR's changes?

I created a new release for v2.9.2. Once the github release is available, we can merge this.


feat: add variable grouping

Adds new API that allows to expose group of variables under single handler grouped under single name:
group := variables.Group{
  "http": HTTPProxyVariables{},
  "extra_sans": ExtraAPIServerCertSANsVariables{}
}
variables.NewAsSingleVariableHandler("dkp", group, false)

We've talked about this and we'll be going different direction.


"0=='+'" returns "true" on Clang

Why does "0=='+'" return "true" if Duktape is compiled with Clang (I haven't tested it on other compilers)? Is that intentional? In all the browsers I've tested that in it returns "false".
I've noticed that because my project relies on "(0=='+')===false" to correctly display the casting-warnings when compiling from my own programming language to assembly.
Perhaps related to that, why doesn't the "Array.prototype.includes" appear to work?
Overall, I think Duktape is an excellent project. With it, I can target any platform I want with the tools I am familiar with. However, it has some annoying bugs, though most of them appear to be solvable simply by minifying the JavaScript. The JavaScript on that web-page (I was using it to make a scientific calculator for Android), for instance, takes around 15 seconds to load on Samsung Galaxy S3 Mini if it's not minified, yet it loads in around 2 seconds if it is minified. Similarly, if it's not minified, it doesn't load at all on Windows (results in "Out of Memory"), but it loads almost instantaneously if it is minified. Quite a big difference considering that the minified file is just 40% smaller.

That 0 == '+' seems like a bug in number coercion of +, namely:
print(+'+') // => 0

when it should be NaN.
Array.prototype.includes is ES2015+ and not yet implemented, so it's simply undefined at this point.

Here's the apparently correct behavior from NodeJS:
> +'+'
NaN
> +'+0'
0
> +''
0

The bug is probably that Duktape interprets +'' (empty string) coercion correctly as 0, and then incorrectly treats a leading plus sign as a no-op so that +'+' becomes +0 instead of NaN. Same goes for +'-'.

Regarding the compiler, this happens on all compilers, not just clang. It can also be repeated at https://duktape.org/dukweb.html.


UE5 Synchronous mode might not apply the command on the next tick

This Issue could be done at the same time as #7376

With test_sync_mode seems to be workign fine


Fix breakage from merge

Two things happened:

In 492cedc I commited a test case that I was just using to debug, and which checks behaviour that I have added other tests for,
and in 659efcc I renamed a function that was called from that test case.

Shouldn't CI have caught this?

This is the rare case where there were no conflicts between the branches, and both compiled, but when rebased together they didn't compile. We could force each PR to be up-to-date but that introduces different headaches (always having to rebase anytime something else gets merged) and I'm not sure if it's worth the tradeoff?

I agree with our volume of changes it's likely vanishingly rare. We could try using a merge queue (https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue) but realistically it only matters if we expect a lot of contributes and a high rate of change.


Support for configuring logging in pure python logger

Logger can now be configured in the nmoscommon config using the following format:
{
  "priority": 0,
  "logging": {
    "level": "DEBUG",
    "fileLocation": "/var/log/nmos.log",
    "output": [
      "file",
      "stdout"
    ]
  }
}

Where level sets the debug level and may be any of the python debug levels, fileLocation sets the log file location, and output sets the log output method(s) and can include file, stdout, and stderr.
Default behavior has not changed but a bug has been fixed that resulted in messages being outputted twice. These changes do not affect the IppLogger when it is used.

LGTM. Only query (which was present previously anyway) is the default log level being debug which seems very verbose. Our internal logger uses warn by default.

Yep. I left it as debug so there'd be no change in behaviour for people already using the library externally. Changing the hard-coded defaults would result in a proportion of peoples logging disappearing which could cause confusion. I went for the maintain current behaviour option for that reason.

That's fair enough. We can resolve it another time if necessary.


ghc panic

Using the ShallowDeepPlugin leads to a ghc panic:
https://ghc.haskell.org/trac/ghc/ticket/15280#comment:1

The problem seems to be, that there is a local bind to lcd when the function is also called lcd. Renaming the function to lcdProgram gets rid of the ghc panic.

Also, using the fixed code, I get the following (with either active or deactivated ShallowDeepPlugin):
stack exec lcdProgram
lcdProgram: compileCommand - Unknown command, it may actually be a procedure
CallStack (from HasCallStack):
  error, called at ./System/Hardware/Haskino/Compiler.hs:401:20 in haskino-0.6-48Ib5C2ddqUKvTQPcysKID:System.Hardware.Haskino.Compiler


Problem with org.apache.http.conn.ConnectTimeoutException

Hi Folks,
I am using Jest 2.0.0 within my application. The code can be seen in the following patch particularly within the following lines.
When I run the code I get the following stack trace which is causing me trouble to debug the connection timeout.
I wonder if anyone can have a look over the code and tell me if there looks to be anything I am doing wrong? Additionally, does anyone have an idea about what the ConnectTimeoutException may be caused by?
Thank you
Lewis
java.lang.Exception: org.apache.http.conn.ConnectTimeoutException: Connect to 172.XX.XX.XX:XXXXX[/172.XX.XX.XX] failed: Connection timed out
	at org.apache.hadoop.mapred.LocalJobRunner$Job.runTasks(LocalJobRunner.java:462)
	at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:529)
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to 172.XX.XX.XX:XXXXX[/172.XX.XX.XX] failed: Connection timed out
	at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:138)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
	at io.searchbox.client.http.JestHttpClient.execute(JestHttpClient.java:48)
	at org.apache.nutch.indexwriter.memex.MemexIndexWriter.write(MemexIndexWriter.java:110)
	at org.apache.nutch.indexer.IndexWriters.write(IndexWriters.java:85)
	at org.apache.nutch.indexer.IndexerOutputFormat$1.write(IndexerOutputFormat.java:50)
	at org.apache.nutch.indexer.IndexerOutputFormat$1.write(IndexerOutputFormat.java:41)
	at org.apache.hadoop.mapred.ReduceTask$OldTrackingRecordWriter.write(ReduceTask.java:493)
	at org.apache.hadoop.mapred.ReduceTask$3.collect(ReduceTask.java:422)
	at org.apache.nutch.indexer.IndexerMapReduce.reduce(IndexerMapReduce.java:356)
	at org.apache.nutch.indexer.IndexerMapReduce.reduce(IndexerMapReduce.java:56)
	at org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:444)
	at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:392)
	at org.apache.hadoop.mapred.LocalJobRunner$Job$ReduceTaskRunnable.run(LocalJobRunner.java:319)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:579)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)
	at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:123)
	... 26 more
2015-11-24 00:27:35,397 ERROR indexer.IndexingJob - Indexer: java.io.IOException: Job failed!
	at org.apache.hadoop.mapred.JobClient.runJob(JobClient.java:836)
	at org.apache.nutch.indexer.IndexingJob.index(IndexingJob.java:145)
	at org.apache.nutch.indexer.IndexingJob.run(IndexingJob.java:223)
	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
	at org.apache.nutch.indexer.IndexingJob.main(IndexingJob.java:232)

Looks like a regular connection error to me. I don't see anything particular in your code that can cause this and in fact you are setting the timeout to 30 seconds...
Are you getting this error as soon as you run the code or after some successful connections? If it's the latter I would suspect no free connections in the pool, if it's the former than I can only recommend checking things in the connection level (i.e.: confirm that the host machine has access to that IP and port, any firewall on the host is configured properly to allow your app on that port etc.).

Hi @kramer thank you for response I really appreciate it. OK so here is some more logging output and it appears that some bulk operations are successful...
2015-11-24 00:51:15,044 WARN  conf.Configuration - file:/mnt1/var/lib/hadoop/hadoop_tmp/mapred/local/localRunner/hadoop/job_local1036620050_0001/job_local1036620050_0001.xml:an attempt to override final parameter: mapreduce.job.end-notification.max.attempts;  Ignoring.
2015-11-24 00:55:28,337 INFO  indexer.IndexWriters - Adding org.apache.nutch.indexwriter.memex.MemexIndexWriter
2015-11-24 00:55:28,682 DEBUG client.AbstractJestClient - Server pool was updated to contain 1 servers.
2015-11-24 00:55:28,684 INFO  client.JestClientFactory - Using multi thread/connection supporting pooling connection manager
2015-11-24 00:55:28,850 INFO  client.JestClientFactory - Using default GSON instance
2015-11-24 00:55:28,850 INFO  client.JestClientFactory - Node Discovery enabled...
2015-11-24 00:55:28,890 INFO  client.JestClientFactory - Idle connection reaping disabled...
2015-11-24 00:55:28,975 DEBUG http.JestHttpClient - GET method created based on client request
2015-11-24 00:55:28,975 DEBUG http.JestHttpClient - Request method=GET url=https://xxx.ixxxxxxx.com:xxxxx/_nodes/_all/http
2015-11-24 00:55:29,212 INFO  memex.MemexIndexWriter - Built and added document to index batch.
2015-11-24 00:55:29,226 INFO  memex.MemexIndexWriter - Built and added document to index batch.
2015-11-24 00:55:29,382 INFO  memex.MemexIndexWriter - Built and added document to index batch.
...
2015-11-24 00:55:29,776 INFO  memex.MemexIndexWriter - Built and added document to index batch.
2015-11-24 00:55:29,790 INFO  memex.MemexIndexWriter - Built and added document to index batch.
2015-11-24 00:55:29,825 DEBUG action.AbstractAction - Request and operation succeeded
2015-11-24 00:55:29,829 INFO  discovery.NodeChecker - Discovered 9 HTTP hosts: http://172.XX.XX.XX:19XXX,http://172.XX.XX.XX:19XXX,http://172.XX.XX.XX:19XXX,http://172.XX.XX.XX:19XXX,http://172.XX.XX.XX:19XXX,http://172.XX.XX.XX:19XXX,http://172.XX.XX.XX:19XXX,http://172.XX.XX.XX:19XXX,http://172.XX.XX.XX:19XXX
2015-11-24 00:55:29,829 DEBUG client.AbstractJestClient - Server pool was updated to contain 9 servers.
2015-11-24 00:55:29,842 INFO  memex.MemexIndexWriter - Built and added document to index batch.
2015-11-24 00:55:29,843 INFO  memex.MemexIndexWriter - Built and added document to index batch.
...
2015-11-24 00:55:31,949 INFO  memex.MemexIndexWriter - Built and added document to index batch.
2015-11-24 00:55:31,951 INFO  memex.MemexIndexWriter - Built and added document to index batch.
2015-11-24 00:55:32,792 DEBUG http.JestHttpClient - POST method created based on client request
2015-11-24 00:55:32,974 DEBUG http.JestHttpClient - Request method=POST url=http://172.XX.XX.XX:XXXXX/memex-xxxxxx-xxx/xxxxxxxxx/_bulk
2015-11-24 00:55:39,830 DEBUG http.JestHttpClient - GET method created based on client request
2015-11-24 00:55:39,830 DEBUG http.JestHttpClient - Request method=GET url=http://172.XX.XX.XX:XXXXX/_nodes/_all/http
2015-11-24 00:57:40,678 WARN  mapred.LocalJobRunner - job_local1036620050_0001
java.lang.Exception: org.apache.http.conn.ConnectTimeoutException: Connect to 172.XX.XX.XX:XXXXX [/172.XX.XX.XX] failed: Connection timed out
        at org.apache.hadoop.mapred.LocalJobRunner$Job.runTasks(LocalJobRunner.java:462)
        at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:529)
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to 172.XX.XX.XX:XXXXX[/172.XX.XX.XX] failed: Connection timed out
        at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:138)
        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)

I'll look into the stackoverflow link you've posted thank you for that.
Any ideas with the above context?
Thanks again @kramer

I don't see anything particularly problematic but some general guess/advices:

One possibility is that your bulk request is too big and overwhelming the server to the point where it cannot accept any more connections. You can try reducing the batch size (of your bulk request) to see if the problem goes away or you can even try manually calling something on one of the (active) nodes while your code is running to see if they respond to non-jest calls.
I did not check your whole code but please make sure you are not creating the factory or the client for each request, factory can be singleton and client can be shared.

hi @kramer

One possibility is that your bulk request is too big and overwhelming the server to the point where it cannot accept any more connections. You can try reducing the batch size (of your bulk request) to see if the problem goes away or you can even try manually calling something on one of the (active) nodes while your code is running to see if they respond to non-jest calls.

Yeah I tried 1000, then 500 and I've tried 250 and less in the bulk call... same result unfortunately.

I did not check your whole code but please make sure you are not creating the factory or the client for each request, factory can be singleton and client can be shared.

I am double checking this and also adding code to close the client and execute a flush of all pending documents to the ES cluster. I hope that will fix the timeout. Thanks for your help. I'll report back here once I fix the issue.

hi @kramer ,l have met a similar problem ,as you mentioned on the second floor ->"Are you getting this error as soon as you run the code or after some successful connections? If it's the latter I would suspect no free connections in the pool, ",i guess i get the latter,i use the regular way to get the JestClient ,but when i startup the app ,it works well,but i refresh the page after a few minutes, it tells me the error ' connection reset', how can i solve the problem ,

OK I actually resolve the issue(s) here. They are as follows

Versioning Mismatch: I was trying to use the Jest 2.0.0 client to ingest data into ES 1.7.1. Once I downgraded to Jest 1.0.0 some of my issues went away. I was not aware that the remote ES cluster was running ES 1.7.1.
I had previously set node discovery to true as this would poll and
update the list of servers in the client periodically. This accounts for
the ability to ingest data into any node in the cluster. It now appears
that this setting did not redirect incoming client connections to the
correct HTTPS URL for the ES node(s) hence connections stagnated and eventually timed out.
This accounts for my consistent commentary on nodes being discovered but
timeout issues hampering ingestion of data into the ES cluster.

Thank you @kramer for your help Sir. I really appreciate it.


TODO: .NET 5 review + update

Any changes to logic? (Not expecting any)
Update code using new syntax, etc.
Check if net5 happy to use netstandard2.1 library, else: separate package for net5
[unrelated] Drop core package? Provides no value

None
Minor - to happen as needed
No issues
Done


Feat: Manual paged search

Hi
This PR adds feature to handle pagination manually. This is particularly useful for http servers that don't want to keep Streams alive. I tested this with R5 and my infinite scroll functionality, works perfect on my case.
I created as a draft, if you're happy with the approach I'll apply the same for the other Client versions and port tests.
Edit: And possibly do the same for search_all too?
Closes: https://github.com/FlixCoder/fhir-sdk/issues/34

Thanks for your proposal.
I need to think a bit more about it to say anything definite, but I am a bit hesitant to add different ways of searching this way. Maybe it is possible to instead combine both manual paging and automatic paging in one. And at the same time it might help configuring the prefetching, because that is hard coded right now..
So my vision would be something like this:
// Makes initial request.
let page = client.search::<Patient>(parameters).await?;
// Get a Stream to all matched resources, where references are resolved with more read requests. Collect all matched resources.
// Unsure whether it should clone resources or consume the page or maybe take the entries out of the bundle?
let entries = page.matches().try_collect().await?;
// Return all entries. This will be the generic Resource enum, because it can be any resource types.
let entries = page.entries().try_collect().await?;
// Fetch next page if there is one.
let page2 = page.next_page().await?.unwrap();
// Similar stuff can be done for previous page possibly.

// Start automatic paging. Consumes the page to construct a new type, that allows modification of preferences and implements Stream.
let all = page.all_matches().with_prefetching(5).try_collect().await?;
// Similarly all_entries.

// There are more simple getters, to get access to the bundle, etc.
// Probably there is even more features.. :D

Though in which way ever it is going to be added, this all leads to additions and refactoring. Mine of course way more refactoring etc. Nevertheless, it might not make sense to tackle until code duplication is solved. Copying the code to all versions needs to stop, it is source of too many mistakes, especially in tests ^^
Sorry for the wait I guess, but it is at least possible to implement anything outside already and wrap in in a nicely usable helper. So there is no reason to rush it.

I've revamped and implemented everything in #41 . It is now possible to do manual/custom search requests and select whether to automatically page or retrieve only the current items.
Therefore closing, thanks for your ideas and feedback :)

Thanks for the update @FlixCoder, all look great!


OT: suggestion: can you add libquickmail here in github?

libquickmail download | SourceForge.net
I see this is a nice tool, but I don't see there are some discussion or forum for this tool.
I suggest you can add(move) one code repo to github here, thanks!

Done
https://github.com/brechtsanders/libquickmail


Lookout CRD and Install Controller

Using the Operator SDK (https://sdk.operatorframework.io/), write a spec (as Go struct definitions) for the run-time configuration of the Lookout  service, write controller logic to deploy the Lookout service using Helm, and generate the CRD YAML definition.
Also, write logic to run the data-model migration - Postgres schema creation, etc.

Hey team! Please add your planning poker estimate with Zenhub @richscott @kannon92 @dejanzele @suprjinx @Sharpz7

Please add your planning poker estimate with Zenhub @ClifHouck


⚠ Bofrost.es has degraded performance

In 2291901, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1627 ms

Resolved: Bofrost.es performance has improved in 07663aa after 8 minutes.


Can't Download from VSCode-Website - Secure Connection Failed

Does this issue occur when all extensions are disabled?: Yes/No

From the website per Browser and also the Aur - Installer I get a error for downloading the newest bin.
Linux .tar.gz 64bit
Secure Connection Failed
An error occurred during a connection to az764295.vo.msecnd.net. SSL received a record that exceeded the maximum permissible length.
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

Can you try from a different machine/network?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Incremental Refresh is for PREMIUM ONLY, but the content states that it is available for PRO

You make this statement:
Supported plans
Incremental refresh is supported for Power BI Premium, Premium per user, Power BI Pro, and Power BI Embedded datasets.
But when I try to set this up on a PRO Workspace, I get this message:
This dataflow contains tables with active incremental refresh policies, which require Premium to refresh. To enable refresh, upgrade this workspace to Premium capacity. Learn more
Please be accurate about what plans are supported. THIS IS CRITICAL!!!

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

ID: 23849d95-194e-b2b1-735a-03aebb56703a
Version Independent ID: 391f63a3-2b18-3676-a151-d9859df54ad6
Content: Incremental refresh for datasets and real-time data in Power BI - Power BI
Content Source: powerbi-docs/connect-data/incremental-refresh-overview.md
Service: powerbi
Sub-service: pbi-data-sources
GitHub Login: @Minewiskan
Microsoft Alias: owend

@ToddChitt - Are you trying to setup IR for a dataflow or a dataset? The article you reference is IR for a dataset.

Data flow
On Thu, Mar 17, 2022 at 6:22 PM Owen Duncan @.***>
wrote:

@ToddChitt https://github.com/ToddChitt - Are you trying to setup IR
for a dataflow or a dataset? The article you reference is IR for a
dataset.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/powerbi-docs/issues/3685#issuecomment-1071642353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVZOQEQ2RJSLLJJUDKKKF3VAOWBHANCNFSM5Q74VFZA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@ToddChitt - IR for dataflows is described in Using incremental refresh with dataflows, while it is a bit obscured, "Using incremental refresh in dataflows created in Power BI requires that the dataflow reside in a workspace in Premium capacity. Incremental refresh in Power Apps requires Power Apps Plan 2." is described just below the first image in the intro.

Do me a favor:
Use BING search engine for the term: “power bi data flow incremental refresh”
Look at the top results. It is a Microsoft Doc with the phrase “Dataflow”. THAT is the article that started all this.
If THAT article does NOT pertain to DATA FLOWS, there please go fix THAT.
From: Owen Duncan @.>
Sent: Friday, March 18, 2022 12:06 PM
To: MicrosoftDocs/powerbi-docs @.>
Cc: ToddChitt @.>; Mention @.>
Subject: Re: [MicrosoftDocs/powerbi-docs] Incremental Refresh is for PREMIUM ONLY, but the content states that it is available for PRO (Issue #3685)
@ToddChitt https://github.com/ToddChitt  - IR for dataflows is described in Using incremental refresh with dataflows https://docs.microsoft.com/en-us/power-query/dataflows/incremental-refresh#incremental-refresh-implementation-details , while it is a bit obscured, "Using incremental refresh in dataflows created in Power BI requires that the dataflow reside in a workspace in Premium capacity. Incremental refresh in Power Apps requires Power Apps Plan 2." is described just below the first image in the intro.
—
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/powerbi-docs/issues/3685#issuecomment-1072556069 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVZOQHXFJUEQTPWZDNOZODVASSV3ANCNFSM5Q74VFZA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/ABVZOQFDFQ6FR4A5QE7NM7TVASSV3A5CNFSM5Q74VFZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH7W6QJI.gif Message ID: @.*** @.***> >


[RSDK-7310] Update the board interface

This turned out to be two problems combined! 1) update the SDK to use a more recent version of the protobufs in the API repo, and then 2) remove the Status RPC from the boards. The PR isn't quite done: I'm unsure how this should interact with https://github.com/viamrobotics/viam-cpp-sdk/pull/230, which is where the compiled version of the updated protos is. but the rest I think is ready for a look.
Updating the protobufs was harder than I expected: https://github.com/viamrobotics/api/pull/470 (unrelated to boards) added a new type that had not been used previously, which meant that getting it to work required updating CMakeLists.txt to include the Google libraries for the new type.
Changes to boards:

get_status doesn't exist any more. You can get the standard status from a component the same way you would for a motor, but there isn't a special board-specific one any more.
In the component status you can get, analog and digital interrupt values are stored as ints, not wrappers around ints. No need to unwrap.
get_analog_names and get_digital_interrupt_names can't easily be implemented any more. They don't exist in the Flutter and TypeScript SDKs, and are hopefully being removed from the Go and Python SDKs soon (they have a purpose on the server side, but no obvious use on the client side, so probably shouldn't be in these SDKs). So, I removed them.
Similarly, I removed get_analog_readers and get_digital_interrupts, as they're not present in the Go SDK and would be very hard to implement without the old status.

Everything compiles against a recent version of the API repo, but not against the protobufs copied into this repo itself. How should that be accomplished?

Github's CI cannot build this because it requires a more recent version of the compiled .proto files from the api repo than what's currently in src/viam/api/. What's the procedure for updating that? I still believe the correct versions might be in #230.

I talked to Ethan about how to get the updated protos: he says I should rebase this branch off of #230, then change this PR to pull into that branch instead of main. When we're happy here, we merge this into #230, and then merge that PR into main. Changes will be coming soon...

Okay, I've rebased and changed the target branch. Let's see how this looks...

Rebased to get rid of merge conflicts. If the CI checks pass, I'm going to merge this...


Action being executed multiple times in HttpClient.request

https://github.com/hyleung/ratpack-zipkin/blob/master/src/main/java/ratpack/zipkin/internal/ZipkinHttpClientImpl.java#L85
Action is executed twice, once in action.append, and once in wrapped request.
If the user is using functions like requestSpec.headers.add, duplicate headers will be added to the request. This causes error in some of the server. For example, AWS ELB will return 400 when it founds multiple Authroization header.

@ptong-samsung thanks for reporting this - do you have any workarounds available to you that can mitigate the issue? As you can probably tell from looking at that code, there was a fair bit of yak shaving required to get client tracing working so there's a chance we can't yak-shave our way out of this one. Ratpack has added support for client request/response interceptors and at some point we were going to revisit our client tracing implementation in this library to make use of that (#44).

@hyleung Thanks. Yes we just changing everything to use headers.set so its fine. Just want to create this to keep trace of the issue.

I see whats happening here.  I think I can fix this quick.

For our use case it would be good to get this fixed before Ratpack 1.6 with interceptors since we still have some code bases one 1.4.5 and updating takes a bit of time.

@llinder I've merged and done a release that includes your fix (#47) - it's still propagating out to Maven central etc, the version is 2.1.0. I'm a little behind on day-job stuff, but when I get a minute, I'll write up some quick release notes (really it's just #47 and #42/#27)
cc/ @ptong-samsung


Which file should I edit to log each step trained training images and regularization images names into a txt file?

Hello. I want to personally log to a txt file in each step which training files and regularization images files are trained
Which file should I edit how for this purpose?

ok i tested with --debug and no need anymore
i wish we could make it to train each training image 1 time before training each training image second time
so model would see 1 training image at a time
what i mean is
currently when you set repeating 150 , ok it collects 150 different reg images for each training image
but every step an image is randomly used
so in consecutive steps, it is training multiple times reg images or same training image
optimal would be train 1 training image 1 reg image and do not repeat any training image until all previous training images trained in that loop
and if we don't use repeating and use epochs, then it doesn't use different reg images like in repeating