Application freezes after deleting files from device

Library version: <IP_ADDRESS> (from Nuget, but tried building the latest version from sources too)
Operating system: Windows 7/10
.NET Framework: 4.5
Made the minimum number of operations:

Getting connected devices
Connection to device
Subscription to device events
Display a list of files from the folder I need on the device
Deleting each of these files

After the last step, the application completely freezes until I unplug the device (tried different phones, the behaviour is the same). Moreover, if I try to open Explorer, it will freeze too. If there are a lot of files, then the program manages to delete some of them.
Because of what it can be and is it possible to fix it somehow?
Thank you!

Most likely the problem is not with your library. I tried to do file deletion in C++ and through the library generated by Visual Studio. It still freezes. Maybe you have any idea why this might be happening?

This library is only a .NET wrapper for the windows MTP COM component. If this component neends a lot of time for the delete the library is waiting. You can try to get a list with all files and use a loop to delete  each file with a single call. So you can show a progress bar.

In fact, that's what I did. But after the first or second removal, the COM object hangs. The freeze time depends on the number of files on the phone. It is even less if you use the generated DLL to access a COM object. But if you delete it through Explorer, then everything is deleted normally. And it most likely uses the same API, since it also hangs up to make an uninstallation from the program.
Hanging can reach about 10-20 seconds with 2-3 thousand files on the phone. Which is very inconvenient. I thought at the beginning that it was in the library, but after some experiments, I realized that it was in the COM object. And it doesn't matter what language to use it through. And freezes happen regardless of the system or phone.
Unfortunately, I do not have enough knowledge to figure out what happens inside the component during file deletion. But can you tell me which way to look?

After deleting a file the underlying Windows MTP library needs a verly long time to update the cache.
Retry with version 1.10 and disabled cache.


Tutorial on using union-types

I think there's a lack of info on how to actually apply union types to real problems in js.
I'd like to see something like http://fsharpforfunandprofit.com/series/designing-with-types.html
offered somewhere. I understand if you want that outside the scope of this repo, but I thought I'd open an issue incase you want to make it a wiki or something.
I'd be interested in contributing here.

I agree, great idea. Quite a few of the examples in functional-frontend-architecture use this library. Granted, they are pretty narrowly focused on modelling actions in the Elm architecture sense, and they don't demonstrate the new features of union-type.  But that may be a place to collect some examples.
I have a few half-baked projects which use union-type outside of the Elm architecture, I can't say they are more than getting my feet wet, but they may be useful to look at.

I agree with this as well. Just having such a library is one thing. But figuring out how best to use it is probably not easy unless one has experience in a language with algebraic data types. A tutorial would be a great idea.

+1 The FSharp blog was also what got me interested in this style of programming, and while I've managed to find this library very useful, my understanding of (functional) type-based design is inferred too much from current capabilities of union-type (rather than general principles). So I'm sometimes not sure what the most idiomatic way to use it is, or if a feature I'd like to see would be an appropriate addition.


Move options from the global PDFJS object into the relevant viewer components and API methods

This should address the remaining TODO in issue #6779.
Note: It seems that the commits appear in a somewhat random order here in the PR; please refer to https://github.com/mozilla/pdf.js/compare/master...Snuffleupagus:rm-PDFJS-options for a properly sorted list.

/botio-linux preview

/botio test

/botio test

/botio-linux preview

/botio-linux preview

/botio-linux preview

@yurydelendik Ping; any change that you can provide feedback/review this soon?
(Given the size and scope of the changes, this PR bit-rots quickly and requires a lot of frequent updates.)

To try and expedite the review/landing of this PR (since I need to get this off my plate) and to get us closer to releasing PDF.js version 2.0, I'll see if I can perhaps split up this patch series into multiple PRs to hopefully make reviewing this a bit less daunting.
Given how invasive the necessary changes are, the final PR will probably still be quite large, but I'll try to begin by first isolating the viewer component options re-factoring in one PR.
Most likely this will result in more churn in the code, and a less than desirable intermediate state until everything is done, but that's probably OK to make some sort of progress here.


Due tab does not show tasks

I'm using the latest version of opentasks and sync with my owncloud 8.1.1 via DAVdroid. When I create tasks in a different client, they get synced and display correctly in the first tab of opentasks. However, the same tasks do not appear at all in the second tab sorted by due dates.
I can make them appear by opening tasks to edit them and save them without changing anything.

Does that happen with all-day tasks too? It sounds as if DavDroid doesn't set the all-day flag to 0 when a task is not all-day. The "due" tab doesn't show tasks with a "null" (i.e. undefined) all-day flag.

You are right, after I switched to Caldav Sync everything works fine.
Thank you for your quick help!
Timm
Am Fr, 4. Sep, 2015 um 7:57 schrieb Marten Gajda
<EMAIL_ADDRESS>
Does that happen with all-day tasks too? It sounds as if DavDroid
doesn't set the all-day flag to 0 when a task is not all-day. The
"due" tab doesn't show tasks with a "null" (i.e. undefined) all-day
flag.
—
Reply to this email directly or view it on GitHub.

great :-)

It sounds as if DavDroid doesn't set the all-day flag to 0 when a task is not all-day. The "due" tab doesn't show tasks with a "null" (i.e. undefined) all-day flag.

At least it should do so…

True, but only if a start date is set, not if the task has a due date only.

True, but only if a start date is set, not if the task has a due date only.

Ah, ok, so an "all-day task" in terms of opentasks-provider is a task that has DTSTART or DUE (or both) set to a DATE value.

Just like an all-day event has no time and timezone information, an all-day task has no time and timezone information either. I think that's the definition of an all-day task, i.e. the task has no specific (absolute) times.
It doesn't matter if only one of DTSTART and DUE or both are given (as long as they both have the same type when present).


Amplitude Histogram Plugin

@lshaheen
We have recently installed the Amplitude Histogram plug in for phy (thanks!), and have a few questions.

We are reciving lots of error reports via the cmd window while running phy with the plugin that we don't understand. Does anyone have any insight on these?

I recall reading that this plugin would also estimate the proportion of "missing" spikes based on the assumption of normality. Is this true? and if so, where does this output appear?

Finally, in the image below, what does the dotted grey line represent?

Sorry if this is the wrong place to post this, please let me know if there is somewhere more appropriate to post this question.

Hi,
Glad this is useful.
1: The "Fitting failed with..." errors are saying that the function wasn't able to fit the histogram and is trying again with more iterations. The the "Fitting error: Optimal..." means it tried again and still failed. These are cases where the amplitude histogram doesn't look like a gaussian at all. Usually these are not single-units, or there was a lot of drift in the recording.
2: Yes. In a more recent version I printed the number on the graph, you can get that at https://github.com/kwikteam/phy-contrib/pull/105  Otherwise if you keep the version you have now and open phy with --debug at the end the numbers will print on the console.
3: The dashed line represents what the gaussian "should" like if there weren't missing spikes.
For example, here's one that shouldn't be called a single-unit, because even though the autocorrelogram shows very few refractory violations, the amplitude histogram shows the cluster is missing a bunch of spikes.

Here's a good single-unit where the histogram isn't cut off.

But beware that if there's drift the amplitude histogram often doesn't look like a single gaussian, so the fit is poor and that number doesn't mean anything. In this example, there are two peaks so the fit is poor, but it doesn't look cut off at all so it's still a single-unit.

In the case you showed the histogram looks really cut off so I would say it's more than likely not a single-unit.

Thanks so much! we really appreciate the examples.


Content Preference

Purpose of the Feature
The dashboard provides insights on user's preference (as measured by total content play) by content type across districts for the state
Described Solution
It is a Pie chart report which can describe the metrics of content usage of Object types such as content, text, video, TV..etc with the partitions in the pie charts.

List of object types should be represented on the left side of the reports with the different color dots as legends.
A selection option with "State view" & "State with Districts View" should be given.
On page load state level view of Pie chart with partitions of object types with specified colors should be displayed on the report.
On selection of State with Districts View of Pie chart the Districts selection box should be appear with multiple districts selection option.
On selection of State with Districts View, The State level Pie chart & Pie charts of all districts levels should be shown side by side.
On selection of states, The State level Pie chart & Pie charts of selected districts levels should be shown side by side.

Effected code areas

New PostgreSQL Queries should be developed for Content pay percentage of all available Object types.
New NIFI processors to be created for the above queries execution
New Node API should be written to fetch the output files
Angular code should be developed for the Pie chart representation for the created metrics.

Updated the data flow and JOLT Transformation to support content preference report.

Written and added the queries to calculate the Content play percentage of all available Object types.


Update discard_sessions.py

Added a way to make it work on servers not running API on port 443

Hi,
These are general example files, you may create your own in your local project.


Not working on Raspberry Pi 4 B running newest Raspberry Pi OS ("GLib requires working CLOCK_MONOTONIC")

Hi there. At first - thank you very much for creating this awesome piece of software!
Today i got my brand new RPi4B which i plan to use as a docker host for multiple services in my home network. I baked the newest Raspberry Pi OS onto the SD-Card, fired it up and ran the usual apt-get update && apt-get upgrade.
First thing i tried out was setting up shairport-sync as a docker container using the example command in the README.md
Unfortunately it seems that the container is not able to run. Docker ist constantly restarting it. Running
docker logs <containerid>
reveals that some "GLib requires working CLOCK_MONOTONIC"
pi@raspberrypi:~ $ docker logs 12bd6fe0aa2a

(process:14): GLib-ERROR **: 23:06:30.771: GLib requires working CLOCK_MONOTONIC
Trace/breakpoint trap
Process 13 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)

(process:14): GLib-ERROR **: 15:27:50.771: GLib requires working CLOCK_MONOTONIC
Trace/breakpoint trap
Process 13 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)

(process:15): GLib-ERROR **: 17:57:10.771: GLib requires working CLOCK_MONOTONIC
Trace/breakpoint trap
Process 14 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)

At first i ran it on Raspberry Pi OS Lite, however, just to be sure i ran it on the "standard" Pi OS as well and unfortunately it is the exact same behaviour.
I also tried out installing all the packages required for building but that didn't help either.
Via google i couldn't find anything...
I wonder if there is somebody who whas an idea what the problem could be. Am I missing something?
Your help would be very much appreciated :-)
Greetings,
Chris

I've just run into the exactly the same error on a RPi3 I'm setting up. I tried pulling version 3.3.7 instead and that looks like it might work.

Apologies — I am late looking at this.

At first i ran it on Raspberry Pi OS Lite, however, just to be sure i ran it on the "standard" Pi OS as well and unfortunately it is the exact same behaviour.

Can you say exactly what version of Raspberry Pi OS you are using? Use $ uname -a or similar.

Hi Mike, this is what my uname -a returns:
Linux Edmund 5.10.17-v7+ #1414 SMP Fri Apr 30 13:18:35 BST 2021 armv7l GNU/Linux

Hmm. That’s identical so what I’m using right now:
Linux raspberrypi 5.10.17-v7+ #1414 SMP Fri Apr 30 13:18:35 BST 2021 armv7l

I’ve been running Shairport Sync on it without problems, but let me revert to the latest public version and check it. Are you building your own Shairport Sync, or are you installing it from a package?

And a quick follow-up question, please. To clarify: did you try running Shairport Sync outside docker, i.e. on Raspberry Pi OS directly?
(BTW, Raspberry Pi OS Lite is fine.)

[Update] The public version of Shairport Sync runs normally directly on the latest Raspberry Pi OS. Maybe there is something wrong or outdated in the Docker image, which is based on Arch Linux. Unfortunately, it'll be late next week before I can get a look at that.

Hi Mike, I remember having a similar issue with another container and it turned out to be related to changes in Alpine Linux and 64bit time. Here is a link to the Release Notes. https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0#time64_requirements

That sound like the problem alright, thanks. What's nice about Alpine is that it's small, but this is not nice!

At first thank you very much already! I'm running the docker container simply using the docker command suggested by you. My uname-a shows
Linux dockerpi 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7l GNU/Linux

I too get the CLOCK_MONOTONIC error with the latest version. Rolling back to 3.3.7 initially fixes the problem. However if I restart the container or reboot the Pi a new error arises.
Process 13 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)
Occurs on two different Pis. Both are Raspberry Pi 4 4GB. Both are brand new with fresh installs of Raspian. Deleting the container and re-running the Docker run command to rebuild the container fixes the problem, until the next reboot…
Linux motav-pi 5.10.17-v7l+ #1414 SMP Fri Apr 30 13:20:47 BST 2021 armv7l GNU/Linux

Thanks. It does seem to be due to changes in the Alpine image used as the basis for the Docker image. I'm experimenting with changing to Debian or Ubuntu, but they are bigger images.

Okay, so I've done a slightly hacky thing -- I have pinned the version of Alpine Linux that is used to the previous version to the current one, in the hope that the previous version does not exhibit this incompatibility with Raspberry Pi OS.
It seems as if the incompatibility should go away when the as the host operating systems are updated.
If you would be kind enough to try it, I'd be obliged.

Hi @mikebrady, I've tried the latest image from 9 days ago and it works for me. Thank you

Excellent, thank you!


chain of dependency

Currently we don't found any option which display full dependency chain in order to identify the vulnerable lib comes from which dependency.
example,
Project A -> lib xyz.jar
Project B -> Project A
Project C-> Project B
So currently when dependency analyzer executed on Project C it gives result xyz.jar is vulnerable but it does not gives any path where it comes from.
It could be interesting if we can see the xyz.jar comes from which project/root level project.
This will help to identify the project which contains vulnerable jar directly when there are forest of dependencies.
If any options/parameters exists for this, can you provide?
Thank you.

How are you running dependency-check?  CLI, maven plugin, etc?
What you are asking for should be in the gradle and maven aggregate reports - however, several users have had issues with the aggregate report and I'm still trying to figure out the best way to solve it.

Additionally, you could run something like mvn dependency:tree to identify the root.

Thank you for your response.
We are using dependency-check using gradle plugin. Indeed it could possible to use gradle dependency to resolve root.  It could be better if the dependency-checker provides this feature. It will also resolve issue like to add gradle project-report plugin or maven dependency tree plugin as specially there are hundreds of projects. It can simply used dependency-check on jenkins pipeline without modifying pom or gradle build. Thx to all dependency-check powerful features we have aggregate result without having two step process.
Thank you.

Hi guys, it would be really great to have this feature in order to easily identify from where comes a specific vulnerability. Especially on modern architecture with multiple components.

I think this is now covered by the 'included by' that is in the reports for versions 8+


(OUI Docs) Remove Elastic References from OuiBasicTable Actions examples

Section: "Adding actions to table"
In default example, on all rows:

[ ] Replace "elastic.co" in tooltip with "opensearch.org"
[ ] Replace "https://elastic.co" in the link action with "https://opensearch.org"

Then, toggle the option for "multiple actions" example , on all rows:

[ ] Replace "elastic.co" in popover menu with "opensearch.org"
[ ] Replace Elastic logo with OpenSearch logo
[ ] Replace "http://elastic.co" with "https://opensearch.org"

Hello @KrooshalUX, this issue is partially fixed, we just need to backport https://github.com/opensearch-project/oui/pull/623. As a result, we do not have this problem on the main branch:

I raised another PR - https://github.com/opensearch-project/oui/pull/721 to fix the link in a single action.

On version 1.0 everything works as it should:

On version 1.1 there are no changes related to the link in a single action (https://github.com/opensearch-project/oui/pull/721):

On versions 1.0, 1.1, and 1.2 everything works as it should. For 1.1 version the necessary changes were backported and applied.


skip checking osd store type for external clusters

Currently there is no way to determine if external clusters are optimized for DR, that is, they are bluestore-rdr.  So we should skip checking for the OSD store type in the cephCluster status in case of a external cluster.
Note: We would want to revisit this in future once we start supporting external clusters for RDR.

/assign @umangachapagain

/test ci/prow/ocs-operator-bundle-e2e-aws

/test ocs-operator-bundle-e2e-aws

/test ocs-operator-bundle-e2e-aws

/cherry-pick release-4.15


RGL isn't responsive when resizing from small to larger breakpoints

Thank you guys for all your great work, I just have an issue I'm not able to overcome. I feel I'm missing some understanding as to why this is occurring.
Problem: When you resize the RGL from large to smaller breakpoints, the grid is responsive and responds accordingly. However, when you resize from small to larger, it seems to get stuck at that smaller breakpoint. I'm using WidthProvider, but I've also tried other ways of passing width prop to the grid, but to no avail.
Sandbox code: https://codesandbox.io/s/rgl-responsive-issue-0g807
To reproduce: Resize the preview pane, making it narrower. Once it's at the smallest breakpoint, now start resizing the preview pane back to how it was.
Thank you

Having the same issue in my app

same too

Same

same issue i m having..

any updates on this? I was hoping it was just matter of setting the right props. Any help would be appreciated! Thanks

I've noticed this since changing from setting the layouts prop as the Responsive level to using data-grid on each grid item.

Any fixes for this?

A (not good) workaround is to change the key when you want the change to apply.

A (not good) workaround is to change the key when you want the change to apply.

Still no fix?

Any updates on this???

A (not good) workaround is to change the key when you want the change to apply.

Can you explain this a bit more?


fix(sec): upgrade org.quartz-scheduler:quartz to 2.3.2

What happened？
There are 1 security vulnerabilities found in org.quartz-scheduler:quartz 2.2.1

CVE-2019-13990

What did I do？
Upgrade org.quartz-scheduler:quartz from 2.2.1 to 2.3.2 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
How was this patch tested?
Run mvn compile failed locally, couldn't complete the build process.
Run mvn clean test failed locally, unit-test couldn't pass.
The specification of the pull request
PR Specification from OSCS

2.3.3 version is also vulnerable


feat: Add user info to suspended node when resuming

Signed-off-by: toyamagu-2021<EMAIL_ADDRESS>
Relates #11148
Motivation

Add resumer on suspended nodes message for auditing, and tracing purposes.

Modifications

Add message about resumed user to node status when resuming workflow.

Verification

Surely, changed!


Calling login_as twice from the same test "leaks" to another test

I have an RSpec test in a Rails app that calls login_as and looks something like this:
require 'rails_helper'

RSpec.describe "weird behavior", type: :request do
  let!(:user) { FactoryBot.create(:user) }

  it "test a" do
    login_as user
    get "/"
    puts session.to_hash
    expect(session["warden.user.user.key"]).to_not be_blank
  end

  it "test b" do
    get "/"
    puts session.to_hash
    expect(session["warden.user.user.key"]).to be_blank
  end
end

It passes:
$ bundle exec rspec spec/requests/settings/password_spec.rb --order defined

weird behavior
{"session_id"=>"06f305ce65e80a53f9729add786fc2d2", "warden.user.user.key"=>[[535], "$2a$04$cGbUk2KvDf/mT4tv4psQW."]}
  test a
{}
  test b

Finished in 0.58912 seconds (files took 3.06 seconds to load)
2 examples, 0 failures

Accidentally, I added a second login_as in test A (and didn't notice -- in real life my test is more complicated so it was easy to miss):
require 'rails_helper'

RSpec.describe "weird behavior", type: :request do
  let!(:user) { FactoryBot.create(:user) }

  it "test a" do
    login_as user
    get "/"
    login_as user  # <- problematic call!
    puts session.to_hash
    expect(session["warden.user.user.key"]).to_not be_blank
  end

  it "test b" do
    get "/"
    puts session.to_hash
    expect(session["warden.user.user.key"]).to be_blank
  end
end

This resulted in flaky tests that would fail or pass depending on the order in which RSpec chose to run them (it works if B runs before A).
After hours of debugging, I realized the problem is that the second login_as call in test A is "leaking" to test B. Looking at the output, you can see that the Warden user key in the session printed from test B is the same as the one printed from test A!
$ bundle exec rspec spec/requests/settings/password_spec.rb --order defined

weird behavior
{"session_id"=>"3087df2477685b564db5f397dc1f6778", "warden.user.user.key"=>[[537], "$2a$04$zNWHx2qhfFzuO2c26MHpqO"]}
  test a
{"session_id"=>"21eb074aa142c542dd2fc04dc7ccaefd", "warden.user.user.key"=>[[537], "$2a$04$zNWHx2qhfFzuO2c26MHpqO"]}
  test b (FAILED - 1)

Failures:

  1) weird behavior test b
     Failure/Error: expect(session["warden.user.user.key"]).to be_blank
       expected `[[537], "$2a$04$zNWHx2qhfFzuO2c26MHpqO"].blank?` to return true, got false
     # ./spec/requests/settings/password_spec.rb:17:in `block (2 levels) in <top (required)>'

Finished in 0.62204 seconds (files took 3.11 seconds to load)
2 examples, 1 failure

Failed examples:

rspec ./spec/requests/settings/password_spec.rb:14 # weird behavior test b

This is very surprising and breaks test isolation in an unexpected way. Can we make the  "queue" of pending login_ascalls automatically disappear at the end of each spec? (Not sure if this is even feasible.)

Glad you tracked down the issue. This sounds like something RSpec would handle than the test helpers themselves. The test helpers are test framework agnostic and thus have no concept when a test starts, ends, or moves onto the next one.
What I'd suggest adding is a shared context in RSpec to cleanup authenticated requests:
RSpec.shared_context "authenticated", authenticated: true do
  after(:each) { Warden.test_reset! }
end

RSpec.configure do |config|
  config.include_context "authenticated", authenticated: true
end

Then on any test that needs authentication you can add it 'logs someone in', authenticated: true do ... end.
If most of your tests require authentication, you can follow the devise recommendation and setup a global after(:each) hook:
RSpec.configure do |config|
  config.after(:each) { Warden.test_reset! }
end

Hope this helps


// trigger phrase not triggering popup

On Obsidian v1.7.7 (on OS X) typing // does not trigger the popup menu. I've tried with a new vault and no other community plugins installed. The autocomplete check is ON and I've tried using both HTML and Obsidian-type comments. I've also tried with Slash commands in Core plugins checked and unchecked.
CMD-P Enhanced annotation menu items are listed and appear to work as expected.
Do I need another Obsidian plugin (Text-Expander?) or similar for this functionality to work?
With thanks

Hello, I tried to solve the issue.
This is what I did:
Modified the onTrigger method in the AnnotationSuggest class to ensure the autocomplete popup triggers correctly when typing '//'.
You can review changes in this commit: https://github.com/lattaai13/ycnmhd-obsidian-enhanced-annotations-20/commit/865329e930921d23da0a036c036aa2b7e328ab6c.

[!CAUTION]
Disclaimer: The commit was created by Latta AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

This issue was tried to solve for free by Latta AI - https://latta.ai/ourmission
If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.

Many thanks ... that appears to work 👍 .


Ember CLI error when running grunt dev on node 0.10.45

I keep seeing this:

Not sure if it's actually affecting anything. I had thought that ember-cli was keeping node 0.10 support until October, so not sure what we can do here. Just raising it because it keeps cropping up.

I had thought that ember-cli was keeping node 0.10 support until October

That is the official plan, but obviously it's getting harder if sub-sub-sub-dependencies decide to drop support :-/
/cc @nathanhammond @stefanpenner

The first notice is a deprecation warning. That's not as clear as it should be, but per every proposed plan we had support for 0.10 and 0.12 until they were end-of-life.
The second note is an error thrown by istextorbinary. Somebody has to open a PR against that package to make it 0.10 compatible again. This is the commit which broke it: https://github.com/bevry/istextorbinary/commit/422e043cdf5f5117f929261858fba4abab9f7ce0
Alternatively we can not depend on it here: https://github.com/stefanpenner/async-disk-cache ... something inside of our community.

@ErisDS we still support 0.10, although that dep seems to be cause visual noise it does appear to work.

The second note is an error thrown by istextorbinary. Somebody has to open a PR against that package to make it 0.10 compatible again. This is the commit which broke it: bevry/istextorbinary@422e043

it seems to work just fine though no?

new async-disk-cache released, istextorbinary is lazily loaded and only when required (not something ember-cli uses)

To confirm - this wasn't breaking anything, but the message is gone now thank you all for the super fast reactions 👍


Create docs.kibot.yaml

Fix file not found error.
config file 'docs.kibot.yaml' not found! Please pass own file or choose from:

I do understand your point in having the example complete and ready to run. But docs.kibot.yaml was just meant to be an example filename. Having an actual docs.kibot.yaml might lead to users never thinking about diving deeper into the config files. As this file currently does not exist users need to write their own config or check out the predefined ones.
I guess I will rename all docs.kibot.yaml to example.kibot.yaml which should make this point more clear.


Packages should only be released if they will install successfully

This may already be satisfied by: https://github.com/Azure/azure-sdk-for-java/blob/main/eng/versioning/scan_for_unreleased_dependencies.ps1
We could perhaps do other sanity checking as well, for example installing the package in isolation where Maven must resolve dependencies from external sources instead of using the source repo. However the delays present in publishing to Maven Central may make this less likely.
Alternatively we could sanity test by publishing a package that is about to be released to a private feed and then attempting to install the package from that private feed with Maven as a backup. In that case an unreleased dependency in the same service should cause a dependency resolution error. Private feeds would need to be cleaned up.

Related to https://github.com/Azure/azure-sdk-for-java/issues/15894


Links to HTTP header definitions are wrapped in both  and backticks

Define a http header:
<dfn data-dfn-type="http-header">Accept</dfn>

Link to this header:
[:Accept:]

Output is:

  `

      Accept

  `

This is very strange. Backticks should not be there...

This is intentional - the backticks are part of the preferred formatting for references to HTTP headers, since they're bytestrings.

@tabatkins Hang on! HTTP headers are bytestrings only in HTTP/2 onwards (See RFC9111 pointing to RFC5322 using ASCII). I have seen multiple versions of RFC9110 (the standard that defines the concept of headers) where ordinary quotes are being used for header fields.

At the very least, if the quotes were introduced using CSS and not "hardcoded", one could override them.


Switch Button and TextField to shadcn

Works towards #889.

Removes variant and isFullWidth from TextFieldProps
divs and spans containing a row of TextFields will now need to use className="pr-flex pr-place-items-center" to center the TextFields.

This change is

lib/platform-bible-react/src/components/text-field.component.tsx line 78 at r3 (raw file):
Previously, jolierabideau wrote…
Same comment here about the cn function and I think we can remove "papi-checkbox" since this doesn't correlate to any css className now

Do you mean remove "papi-textfield"? I don't see "papi-checkbox"

Hey @dewert99! Thanks for the hard work on these. Unfortunately, we didn't catch beforehand that there's a step we forgot to tell you about and make sure you completed before closing this PR: any time you make changes in platform-bible-react, you need to run npm run build from that folder or npm run build:platform-bible-react from repo root. That lints and builds these files to make sure they run correctly in Platform.Bible. Running that brought up some errors that I made very quick fixes for in #899. Please check that out, and feel free to make adjustments to the changes as you see fit. The search bar especially needs work now.
It would probably be best to get platform-bible-react building again asap, so my changes in that PR are rough and are just to get things running again so others aren't blocked from doing their work. Might be best to make a follow-up PR with more sensible changes when the time is right.
Sorry for the mix-up! Thanks!

Sorry, I am currently away for a few days, so if this is urgent, maybe someone else could look at this.

I'm back from my trip. Sorry my PR caused problems, thanks for fixing this, I didn't know about running npm run build. Do you think it would be a good idea to add npm run build to the CI?
I tried running npm run build and working through the errors, and I was mostly able to reproduce your PR. The one part I'm not sure about is how you knew to fix src/renderer/components/settings-dialog/settings-tab.component.tsx, as it doesn't seem to cause an error when running npm run build.
You mentioned specifically to look about the search bar needs work, where would I see the search bar.

Hey @dewert99 welcome back! Sorry that I forgot to mention npm run build when we talked. I'm not sure if we have talked about adding it to the CI. I know that it is meant to be an external library and at some point it will be moved out of the core.
I would imagine he was able to fix the settings-tab.component.tsx because he either searched for uses of the SearchBar or he started up the app and it threw an error in the settings-tab.component.tsx because we were using a prop on the SearchBar that doesn't exist anymore.
You can see the SearchBar used in the settings-tab.component.tsx When you first started the app, there were probably a couple of floating tabs in the middle, the settings tab was one of them. If you closed those you will need to clear local storage to see them appear in the middle again. You can also add it to the preview page in platform-bible-react, it's easier to test changes there since you don't have to rebuild, whereas to see your changes in the core you have to run npm run build every time. I thing the main thing is that the SearchBar is a TextField with a MUI Paper element behind it, and now that we removed isFullWidth the TextField and Paper are different lengths.
Another recent change is that the web views are now hidden behind an environment variable. So if you aren't seeing any web views then you need to set DEV_NOISY=true, you can see the thread in platform-changes in Discord for help on that if you need it.


Broken Link on https://docs.perl6.org/language/functions

The problem
The link "command line interface" on the bottom of the page (https://docs.perl6.org/language/functions) points to https://docs.perl6.org/routine/create-cli which does not exist.
Suggestions
Fix the link to point to this page https://docs.perl6.org/language/create-cli

Thank you! Fixed with commit https://github.com/perl6/doc/commit/15183a20265436cf344f122f0483cfd39aa06cee.


pkg/build: minimal linux init/image

There is a long standing idea of providing own minimal init that will do just the things we need and no more, most likely in a form of a static Go binary. Advantages:

portable across arches
boots fast
can test arm64 in qemu/emulation on GCE (stretch doesn't boot in 10 minutes)
simpler maintenance
no variance in setup (we've seen some things are not mounted or mounted in different locations in different images)
will allow simpler CI setup (build own image, run in qemu)

Disadvantages:

unclear if we want to get into this business and maintain this

I guess the verdict depends on how easy it will be to build this. Here are some relevant links:

u-root is able to build a Go init on-the-fly (use example)
gokrazy is a pure-Go userland for your Raspberry Pi 3 appliances (quickstart, use example)
https://github.com/bradfitz/embiggen-disk/blob/master/integration_test.go does something similar

However, for arm64 it can make sense to check a minimal buildroot image first.

Some references for u-root from @hugelgupf:
>Is there a similar programmatic API by any chance?
Yes, see https://godoc.org/github.com/u-root/u-root/pkg/uroot

Honestly, the best use example for that API is the main file: https://github.com/u-root/u-root/blob/master/u-root.go

as a side note, we also have infra that runs go tests in QEMU VMs... I saw qemu being mentioned.

this is how you run them (you use go test ... but with some env vars set)
https://github.com/u-root/u-root/blob/master/integration/README.md

example 1 test setup: https://github.com/u-root/u-root/blob/master/pkg/mount/mount_integration_test.go (if you want to add commands to call from the test by shelling out, see the more config version below, but I try to use the programmatic APIs for most our stuff)
example 1 go test run inside QEMU VM: https://github.com/u-root/u-root/blob/master/pkg/mount/mount_linux_test.go

example 2 test setup (more configuration): https://github.com/hugelgupf/p9/blob/master/fsimpl/localfs/localfs_integration_test.go
example 2 test run inside VM: https://github.com/hugelgupf/p9/blob/master/fsimpl/localfs/localfs_test.go

the programmatic API for this one is... improvement-worthy.

you can also forego using Go unit tests, and run random commands in a shell with expect-style scripting, example:
https://github.com/u-root/u-root/blob/master/integration/generic-tests/pxeboot_test.go#L63

Init from wireguard tests https://git.zx2c4.com/wireguard-linux-compat/tree/src/tests/qemu/init.c
With minimal vm https://git.zx2c4.com/wireguard-linux-compat/tree/src/tests/qemu

@evdenis nice minimalistic example, that's useful, thanks.

LinuxKit: A toolkit for building secure, portable and lean operating systems for containers

I've been testing buildroot images for arm64 kernels (linux/raspberry pi 64) on a newer pi board. Buildroot works the best compared to a big set of images I've tested (with the least amount of crashes surrounding startup compared to stretch/others).

FTR, here is a script that builds arm64 image that can work with syzkaller. I used buildroot on 2020.08.x.
set -eux

make qemu_aarch64_virt_defconfig

cat >>.config <<EOF
BR2_TARGET_GENERIC_HOSTNAME="syzkaller"
BR2_TARGET_GENERIC_ISSUE="syzkaller"
BR2_cortex_a57=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_PACKAGE_DHCPCD=y
BR2_PACKAGE_OPENSSH=y
# BR2_PACKAGE_URANDOM_SCRIPTS is not set
BR2_TARGET_ROOTFS_EXT2_SIZE="1G"
BR2_ROOTFS_POST_FAKEROOT_SCRIPT="./rootfs_script.sh"
# BR2_LINUX_KERNEL is not set
EOF

cat >rootfs_script.sh <<'EOFEOF'
set -eux

# Mount debugfs for KCOV.
cat >>$1/etc/fstab <<EOF
debugfs /sys/kernel/debug debugfs defaults 0 0
securityfs /sys/kernel/security securityfs defaults 0 0
configfs /sys/kernel/config/ configfs defaults 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc defaults 0 0
EOF

# Setup ssh without key/password.
cat >$1/etc/ssh/sshd_config <<EOF
PermitRootLogin yes
PasswordAuthentication yes
PermitEmptyPasswords yes
EOF

# Generate sshd host keys.
ssh-keygen -A -f $1
mkdir -p $1/var/db/dhcpcd

cat >$1/etc/udev/rules.d/50-syzkaller.rules <<EOF
ATTR{name}=="vim2m", SYMLINK+="vim2m"
SUBSYSTEMS=="pci", DRIVERS=="i915", SYMLINK+="i915"
EOF
for i in {0..31}; do
	echo "KERNEL==\"binder$i\", NAME=\"binder$i\", MODE=\"0666\"" >> $1/etc/udev/rules.d/50-syzkaller.rules
done
EOFEOF
chmod u+x rootfs_script.sh

make olddefconfig
make

amd64 image also works with qemu_x86_64_defconfig and removing BR2_cortex_a57=y (which does not harm either).

There is an unpleasant issue with firmware.
Some drivers require separate firmware blobs:
[   67.739498][ T3000] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[   68.397443][ T3000] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008

Without the firmware blob the driver won't work.
In the Debian Stretch image these blobs are located in /lib/firmware:
# ls -1 /lib/firmware/
ar3k
ar5523.bin
ar7010.fw
ar7010_1_1.fw
ar9271.fw
ath10k
ath3k-1.fw
ath6k
ath9k_htc
htc_7010.fw
htc_9271.fw
qca

If we use buildroot, (1)  we need to install these blobs as well, (2) figure out how kernel locates it (how does it know about /lib/firmware).
FTR, ath9k firmware is available here:
https://github.com/qca/open-ath9k-htc-firmware

There is an unpleasant issue with firmware.
Some drivers require separate firmware blobs:
[   67.739498][ T3000] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[   68.397443][ T3000] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008

Without the firmware blob the driver won't work.
In the Debian Stretch image these blobs are located in /lib/firmware:
# ls -1 /lib/firmware/
ar3k
ar5523.bin
ar7010.fw
ar7010_1_1.fw
ar9271.fw
ath10k
ath3k-1.fw
ath6k
ath9k_htc
htc_7010.fw
htc_9271.fw
qca

If we use buildroot, (1)  we need to install these blobs as well, (2) figure out how kernel locates it (how does it know about /lib/firmware).
FTR, ath9k firmware is available here:
https://github.com/qca/open-ath9k-htc-firmware


Bump Yarn to Version 4.4.1

This pull request simply bumps Yarn to version 4.4.1.

Replaced by #181.


function parameter hover card does not close when using IntelliSense within it

Environment data
VS Code version:  1.19.1(1.19.1)
Python Extension version:  0.9.1
Python Version:  3.6.3
OS and version:  macOS High Sierra 10.13.2(17C88)
Actual behavior

key stroke "print(" -> function popup start
key stroke ")" -> function popup close, but...
key stoke "alt+enter" -> function popup not close

Expected  behavior

key stoke "alt+enter" -> function popup close

Steps to reproduce:

key stroke "print(" -> function popup start
key stroke ")" -> function popup close
key stoke "alt+enter" -> function popup close

Logs
Output from Python output panel

Output from Console window (Help->Developer Tools menu)

This seems to have been fixed. If we are wrong then please let us know.


[Enhancement][CherryPick][Branch-2.2] Avoid using DeleteRange for delvec GC

Rocksdb range deletes may cause range query to perform badly. Previously, delvec GC is performed by range delete delvecs of a segment of versions [0 to min_readable_version), this PR changes delvec GC logic to scan through all delvecs of a tablet, get all expired delvec keys, then perform a batch delete. There is already a scan through delvecs before performing range delete, this PR just use the original scan, so it does not introduce any new overhead.
What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes https://github.com/StarRocks/starrocks/issues/11405
Problem Summary(Required) ：

Checklist:
Rocksdb range deletes may cause range query to perform badly. Previously, delvec GC is performed by range delete delvecs of a segment of versions [0 to min_readable_version), this PR changes delvec GC logic to scan through all delvecs of a tablet, get all expired delvec keys, then perform a batch delete. There is already a scan through delvecs before performing range delete, this PR just use the original scan, so it does not introduce any new overhead.

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_be_unittest

run starrocks_be_unittest


[Event Request] Database::"Sales Header" - Function CheckCreditMaxBeforeInsert - OnCheckCreditMaxBeforeInsertOnBeforeSalesHeaderCheck

We like to request the following Event:
Object: Database::"Sales Header"
Function: CheckCreditMaxBeforeInsert
Publisher Event: OnCheckCreditMaxBeforeInsertOnBeforeSalesHeaderCheck
Reason: To implement custom business logic
Where is the event placed:
else
SalesHeader."Bill-to Customer No." := Cust."No.";
OnCheckCreditMaxBeforeInsertOnBeforeSalesHeaderCheck(SalesHeader);
CustCheckCreditLimit.SalesHeaderCheck(SalesHeader);
end else
Event Code:
[IntegrationEvent(true, false)]
local procedure OnCheckCreditMaxBeforeInsertOnBeforeSalesHeaderCheck(var SalesHeader: Record "Sales Header")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


polish

small polish for v2.0:

fix small markdown errors in README

page inspection: colorize nested composition instance nodes differently from the root node

Implemented on master (v2.0.0).


RuntimeError: Error compiling objects for extension

torch
torch                         2.1.0+cu118
torchaudio                    2.1.0+cu118
torchvision                   0.16.0+cu118
packaging                     23.2
ninja                         1.11.1

cuda version 11.8
python version 3.11.5
ninja version 1.11.1
log.txt

I've just clarified in the README that Windows is not supported. If you have ideas on how to modify the code to support Windows, we'd love to get help there.

sorry


We need to check how Swift-idiomatic the library is

I've only looked at the AAT library very briefly so far, so consider these opinions possibly hastily-formed. But I notice that there are decisions (like using classes instead of structs for things that are clearly value types, like Resolution etc) that seem to have been made either:

because they were copied directly from the Kotlin API, or:
because we wanted to make a public API that's compatible with both Swift and Objective-C.

If it's just 1., then we should change these things (@QuintinWillison has indicated (Ably Slack) that we should be aiming for an API idiomatic to Swift).
If it's 2, then we should consider:

whether we need Objective-C compatibility at this point (my question in Ably Slack)
and if we do need it, then whether we'd prefer to make a separate Objective-C interface instead of compromising the Swift one (@QuintinWillison has indicated that he'd prefer not to compromise the Swift interface, and I pointed out how writing an Objective-C facade could be more involved than the Java equivalent (Ably Slack))

┆Issue is synchronized with this Jira Task by Unito

This also relates to #216, where we're potentially compromising the Swift interface in order to remove specialised code for Objective-C.

Update: @QuintinWillison has decided (Ably Slack) that this library does not need to be compatible with Objective-C.

Indeed. Also agreed by @AndyNicks. We should probably complete #218 before tackling this issue.

This task has to be marked as pending since this https://github.com/ably/ably-asset-tracking-swift/pull/219 and this https://github.com/ably/ably-asset-tracking-swift/pull/220 isn't merged


Sidebar disappearing

The sidebar disappears when the browser-width is between 768px - 479px.

👍 I'm looking at this now

and done! 😁


Make amp-sidebar sample validate

amp-sidebar requires that the sidebar is the first element after the body tag. With ABE's column layout this is not possible. We need to find a way to move the amp-sidebar there in the generated sample. Currently, it still works but doesn't validate.

CC @andrewwatterson -- this is the UI issue I was discussing with you at the Amp Conf in Tokyo today. I went to file an issue and found this one, plus the other two, outstanding from a couple years ago.
For some context, this was the Stack Overflow question I asked a couple years back: https://stackoverflow.com/questions/39857415/amp-sidebar-does-it-absolutely-have-to-be-the-child-of-the-body-why
At the time, @cramforce had filed this tweet: https://twitter.com/cramforce/status/783352472014233600
What I'm wondering is: Are there still valid reasons for not allowing amp-sidebar to be anything else other than the child of the body?
Something else that's this confusing -- on the amp-sidebar docks: https://amp.dev/documentation/examples/components/amp-sidebar/
The example seems to be a child of a div element, but I am certain that wouldn't validate, unless the requirements of amp-sidebar have changed.

Unrelated, but your live coding session was awesome! :D

(Last note) it does appear as if the docs are incorrect -- amp-sidebar still doesn't validate if it is not the direct child of the body. You can view the behavior at this repo I've put together here: https://github.com/maddoxnelson/sidebar-amp-conf-demo
Thanks all!

cc @ampproject/wg-ui-and-a11y


chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.2.9

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.2.8 -> v1.2.9

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper
v1.2.9
Compare Source
Bug Fixes

deps: update gomod (#189) (aefba64)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

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


Hotkey

Does this app have a hotkey to enable/disable? It would be very helpful

Only a disable hotkey is available in the program at the moment, I haven't released a new update to the program from a long period of time since I was busy with school, exams and final exams and I didn't have that much of time to program. anyways a new version will come out soon. it will have the enable hotkey feature added and probably more features. Stay Tuned Thanks


Adds OOM Killer

Adds a new -k option that when enabled will check the memory limit and usage of the process
via the cgroup. When within 10% of the limit, a SIGINT is sent. This should allow for better
OOM behavior in ECS where applications are not being appropriately killed.

This would have been a great feature to merge. I'm using tini on containers deployed to ECS and was lookin for an OOM-killing feature.

@jamesmishra It was a bandaid, but it worked well (and still is in a few places). We just vendored in our fork for the containers where we wanted this behavior. I'd probably suggest looking for other options before this one, but in a pinch ¯_(ツ)_/¯


Add ZNC as a source for logs

This commit adds ZNC as a source for logs, using the default timestamp config.

Thanks!


Code submission Group<PHONE_NUMBER>_2310334_2211366_2113971_2311849

1. Introduction:
In this pull request is the implementation of 2 algorithms: Bottom Left Decreasing and Next Fit Decreasing Height.
Brief Description:
Bottom-Left-Decreasing (BLD) Algorithm: The algorithm places items in a stock by sorting them in descending size order and fitting them from the bottom-left corner. The algorithm only make use of original orientations to minimize unused space.
Next-Fit-Decreasing-Height (NFDH) Algorithm: The NFDH algorithm sorts items by height and places them row by row in a stock. If an item doesn't fit in the current row, it starts a new one, also checking both orientations to optimize space usage.
2. Team members:

Name
Commit
ID

Đào Duy Thành Công
Searching for algorithms, debugging.
2210404

Nguyễn Minh Hưng
Revise codes, provide supporting implementation.
2211366

Lê Bảo Linh
Implementing BLD policy
2311849

Nguyễn Nhân Thành Châu
Debugging, codes fine-tuning.
2310334

Phan Nguyễn Xuân Lộc
Implementing NFDH policy.
2113971

3. Results summary:

Algorithm
Average Filled Ratio
Average Trim Loss
Runtime (seconds)

BLD
0.165
0.2317
0.031

NFDH
0.166
0.3146
0.016

Greedy
0.219
0.2902
0.042

We have corrected the PR, please try to merge again and notify us if there's any further problem.


ENH: Add DataFrame tabular repr

closes #1604. Fixed to be distinguishable from pandas output.

@jcrist any comments on this?

Taking another look at this (sorry for the long silence).  Some feedback based on the following example:

Some subjective thoughts:

I think we should show fewer empty lines for divisions.  Maybe four or five

I think that we should remove the text-based representation above the tabular repr.

I think that we should include the number of partitions somewhere, perhaps where it currently says "divisions"

It would be nice to also state how many tasks are in the computation.  I'm not sure exactly where this would go, but we could consider using some of the empty space below the dtypes.

If the computation of df.head is cheap we could consider adding the first few lines as a sample
head = df.head(compute=False)
head.dask = head._optimize(head.dask, head._keys())
if len(head.dask) < 10:
    ...

I'm not sure about this though.  This sort of guess work can get us in trouble.  Just throwing it out there as a thought.

Sorry not to follow this up.  updated based on your suggestions.

[x] show fewer empty lines for divisions. Maybe four or five
[x] remove the text-based representation above the tabular repr.
[x] include the number of partitions somewhere

I think it's nice to display dask key name and number of tasks. Do we already have a function to count current tasks?

Do we already have a function to count current tasks?

I would just use len(self.dask)

Trying this out locally now.  It feels very nice to me.

Oh, and I see that it works nicely as a text repr as well.

I would just use len(self.dask)

Ah you're right. I've tried to count something other than dask tasks.
Fixed to include it to the html / string repr. Note that to_string only contains data repr, but I do not have specific preference.

I've added the use of key_split to determine the name.  Any objections @sinhrks ?
I would like to merge this soon.

thx, no objections of course:)

Merged.  Thanks @sinhrks !  I think this change will make several people happy.


Document git repo fetching errors causes generate to hang

When cloning the git repo of a document, we sometimes end up logging fatal errors but don't actually treat those as fatal for the overall generation, and I ended up in a state where my generate was sitting indefinitely doing nothing because of it. The process was hung here until I killed it.
Some example output below, with the actual git repo URL changed. For the purposes of this example, it's just a self-hosted repo with a self-signed certificate. The underlying error is because of that certificate, but this is just one example of how we can get in a bad state when the repo cloning fails:
ERROR 2024-04-04 20:12:11,353 utils.py:210 Error: Cmd('git') failed due to: exit code(128)
cmdline: git clone -v -- https://some-url/my-repo.git /workspace/taxonomy/temp_repo
stderr: 'Cloning into '/workspace/taxonomy/temp_repo'...
fatal: unable to access 'https://some-url/my-repo.git/': SSL certificate problem: self-signed certificate in certificate chain
'
INFO 2024-04-04 20:12:11,361 generate_data.py:595 Content from git repo fetched
INFO 2024-04-04 20:12:11,365 rouge_scorer.py:83 Using default tokenizer.
0%| | 0/10 [00:00<?, ?it/s]INFO 2024-04-04 20:12:11,367 generate_data.py:446 Selected taxonomy path workspace->taxonomy```

My Pr for this got accidentally  closed, I haven't re-opened it as I think this bug is no longer happening (I think i was fixed eslewhere)

We should probably ensure this isn't happening anymore before closing.

I can no longer reproduce this issue - errors cloning the git repository now appear fatal and properly exit versus the errors being ignored and incorporated into my training data.

Per @bbrowning's comment I'm going to close this for now - feel free to reopen if this is still an issue


Uploading image stuck at random times

I'm implementing the basic version of jQuery-File-Upload.
When uploading an image file, it may happens that the image gets stucked  in the middle of the upload. This issue could happen at any radom time and there is not way to predict that. It simply stops working without  giving any warning or failure message.
I realized that it happends only in Mac's Safari 5.1.2, I tested it in Window's Safari and it works correctly.
This is my implementation:
$('#fileupload').fileupload({
	sequentialUploads: true,
	dataType: 'json',
	url: '<?php echo $this->baseUrl("images/uploadimages")?>',
	always: function (e, data) {
		console.log("Always", data.result);
	},
	progress: function (e, data) {
		var progress = parseInt(data.loaded / data.total * 100, 10);
		console.log("Progress:", progress);
	}
});

What I'm doing wrong??

Can you reproduce any issues with this browser version on the demo page?

Sorry, but I can only suggest you to try to debug and pinpoint it using Safari's excellent JavaScript console, but you are probably already doing that.


Fix for chef 14 windows_feature fails on windows 2008r2

Signed-off-by: Kapil Chouhan<EMAIL_ADDRESS>Description

Fixed minor bug
Ensured chef-style on the code changes made

Related Issue
Fixes:
https://getchef.zendesk.com/agent/tickets/22056
https://chefio.atlassian.net/browse/MSYS-1006
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

Is this tested on 2012/2016/2019 as well?

@tas50 the change is in an existing older_than_win_2012_or_8? conditional.

🤦♂

You think I could read the stuff I wrote


be up front that team applications are public

Quick fix for #3613.

How's that, @mattbk @remy? A little better?

LGTM. (and pretty much how I drive UI tweaks on @jsbin too!).

Thanks @remy. :)

Looks good to me.


No support for non-locale encodings

If I run isort against the following file saved as utf-8 when the locale specifies a utf-8 encoding (e.g. en_GB.UTF-8), everything works fine:
# coding=utf-8

snowman = "☃"

If I set LC_ALL=C first, it errors, despite the encoding comment explicitly saying this is a utf-8 file.
In Python 3 there's tokenize.open for handling this. I'm not aware of a backport, but there might be one (or it might be easy to create one, as it's pure Python).

This should now be supported in isort 4.0 just released on PYPI,
Thanks!
~Timothy


NoSuchMethodError: org.apache.http.entity.ContentType.withParameters problem (revisiting)

I've been receiving this message that I'm sure others have seen
Exception in thread "main" java.lang.NoSuchMethodError: org.apache.http.entity.ContentType.withParameters([Lorg/apache/http/NameValuePair;)Lorg/apache/http/entity/ContentType;
    at org.apache.http.entity.mime.MultipartEntityBuilder.buildEntity(MultipartEntityBuilder.java:219)
    at org.apache.http.entity.mime.MultipartEntityBuilder.build(MultipartEntityBuilder.java:240)
    at org.apache.http.entity.mime.MultipartEntityBuilder$build$5.call(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)...
...

I'm using rest-assured (3.0.0) and hadoop-common (2.7.2) and as far as overlapping classes, I made to sure to exclude httpclient from the hadoop-common dependecy. For some reason, after packaging my program and running it (on aws emr), I continually receive the above runtime error. The main usage of rest-assured is to POST (with attachments as multiparts).
Any idea what the problem might be? More clashing classes outside of httpclient, or maybe there is something else that I've done wrong?

I have the same problem. Any ideas?


[WIP] Add pprof format

Why

What

Tests

A lot of tests is failing.

Please update Changelog.


Boost (Multi resolution) dont work.

I trying it many time with all models in menu and its always shows broken result - like two depths was composed with wrong way..

Can not reproduce, and I have a baaaaad feeling about this one - not even sure where to start looking for the issue. In any case, if you send initial image and result result image pair I might have some clue, but no promises here.

Here is image and result I got.
Using Midas dpt_beit_large_512 (midas 3.1) - is the only model that produces adequate results at base resolution. And will be good to get more hires results.
May-be I do something wrong. Will be good to have some detailed instruction. I not found any information about using it in the automatic1111. (


Add wearable features to android notifications

Review how android notifications provided by this app look like on wearable device and improve it if possible - https://developer.android.com/training/wearables/notifications/index.html

This should be resolved for Nougat+ devices thanks to Bundled notifications implemented in #84, but it should be tested to prove it as available doc is not very clear.

I'm a Pebble watch user, it's not a true Android Wear, but if those actions work for Android Wear, it usually also works for Pebble.
Currently I don't see any notification actions on my watch.

Doc around notifications on wearable https://developer.android.com/training/wearables/notifications/index.html

My friend who owns Android Wear 2 watches confirmed me that Bundled notifications and actions available in them work correctly there.

@laughedelic do you know about some good docs for Pebble vs. android notifications - how it process notifications, where it takes actions from etc? Is it possible that Pebble does not take default notification actions, but uses only those added over WearableExtender? I should add them if I'll be somehow sure it will help you, but I do not have any chance to test it so at least some docs which supports this possibility should be good.


Error in swrast

About the following error:
libGL error: failed to load driver: swrast
I solved this by using:
sudo apt-get install --reinstall libffi7
conda install -c conda-forge libffi
And Link can  help.
I note this for anyone else who has the same error as me.

Thank you for your kind sharing!

The problem can also be solved by conda install -c conda-forge gcc in my environment, as is pointed out in https://github.com/GuanxingLu/ManiGaussian/blob/main/docs/ERROR_CATCH.md


Add 1.8.0 velero and update 1.7.1

What this PR does / why we need it
Add Velero v1.8.0 package. New feature is supporting vSphere environment.
Details for the Release Notes (PLEASE PROVIDE)
    1. Add 1.8.0 package which support vSphere environment
    2. Add default MinIO setup for vSphere environment
    3. Modify 1.8.0 package.yaml to contain the added info in values.yaml
    4. Modify some 1.7.1 package imgpkg setting
    5. Add velero 1.8.0 in addons/repos/main.yaml
    6. Add features support for Velero

Which issue(s) this PR fixes

Fixes: #
Describe testing done for PR

Verified on TKG vSphere environment
Verified on TKG Azure environment
Verified on TKG AWS environment
Verified on TCE docker environment

Special notes for your reviewer

Fix https://github.com/vmware-tanzu/velero/issues/4541

I'm going to approve this to avoid blocking the package's availability.
I haven't reviewed it closely, but from what I can see it's mostly a copy of v1.7.0 into the v1.8.0 directory, and then the updated pins for v1.7.1.

Thanks, Nolan.
Velero 1.8.0 upstream has no big difference from 1.7.0.
The main modification is adding some overlay files to support vSphere related configuration.


Fluter freezed v3.0.0

Related # (issue)
https://github.com/dotansimha/graphql-code-generator/pull/8350#issuecomment-1305391678

Work is in progress on this issue  here

When will this be merged?

@denes16 @charlypoly @endigo @auaicn, I seriously need your feedback on these new breaking features.
Clone this repo where I do all my crazy experimentation before releasing them for this plugin
In an attempt to make the plugin more flexible for any use case, and provide more features to enhance the DevX of using GraphQL in Flutter projects, I have introduced some features but I fear I might be over-engineering something that nobody will ever use.
I have been working on this straight for a month now and I feel no one is going to ever need these features I am going sleepless nights working on.

I thought I was going crazy with these new features I was implementing but am I proud I did.
What's new and upcoming in this plugin is modular configuration using specific patterns.
You'll be trading the previous bloated singular configuration for a more compact(okay: maybe a little verbose), granular multi configuration.
Watch out for flutter-freezed-v4.0.0
@charlypoly I will need you to review this PR.
Please let me know if you're available or if there's anyone I should reach out to


rework JOSS manuscript

xref  openjournals/joss-reviews#3330 (comment)
We should start thinking about how the revised manuscript will look. @xf37 originally did the draft as a google doc. What do we think about continuing with that? Also, we need to get a release out that includes the locate module (prereq #190).
@ljwolf & @qszhao, would you like to get in on the paper, considering your mentorship in GSoC (and Levi's SKATER, SPENC, etc. stuff in spopt)?
@gegen07, @sjsrey, @knaaptime, @rwei5

@jGaboardi I would be very happy to help with the manuscript if it is necessary...

For example section for locate module, should we use the real-world dataset or the example dataset using spaghetti as written in readme is enough?


cannot compile using go1.5

Hi,
complete noob on pi, python, linux, ...
I have this error when launching 'go get -u github.com/odeke-em/drive/drive-gen && drive-gen':
.gvm/pkgsets/go1.5.2/global/src/github.com/odeke-em/drive/drive-gen/build.go:24: syntax error: unexpected string literal, expecting )
Thanks for helping me out!

@geertvercamer  please see requirements
You are using an older version of go then what is supported at this time. You may want to see if your platform is listed here. Using packages for your platform will be alot easier in most cases then compiling on your own.

Thanks @shaggytwodope
uname -a -> Linux raspberrypi 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux
Jessie, I guess? Debian based? But apt-add-repository gives 'command not found'

@geertvercamer So the command comes from the pacakge software-properties-common. Please take a look at the whole section and steps mentioned.
Check out the releases page under the downloads section for pre-compiled binary's that can be run with ease should the steps not work for you above.

i am getting the same error when using the golang-go package in ubuntu xenial (v1.6-1ubuntu4). installing go1.4 and/or go1.5.2 through gvm as described in the wiki is also not working. (Failed to compile complaining for an "unknown relocation type 42; compiled without -fpic?".)

@redtux you need to be using go 1.7+. Is the wiki saying otherwise?

indeed, it does! :-D

gvm install go1.4
gvm use go1.4
gvm install go1.5.2
gvm use go1.5.2 --default

See: https://github.com/odeke-em/drive/wiki#troubleshooting

The gvm trick was working fine for older Ubuntu/Mint but I haven't used it for so long it might not be as useful as it was. Maybe we should remove it from the wiki unless anyone can confirm it's still working.
@redtux Regarding Raspberry Pis, it's supposed to work according to this link even if I don't have a Pi to test: https://github.com/tgogos/rpi_golang (there is also a how to without gvm)

Hello @geertvercamer thank you for the question and welcome to drive!
Thanks @shaggytwodope and @chevillet for answering the question.
@geertvercamer yap just like @shaggytwodope mentioned in https://github.com/odeke-em/drive/issues/915#issuecomment-304720047, the minimum Go version is listed there as Go1.7, and if that doesn't work as he also mentioned in https://github.com/odeke-em/drive/issues/915#issuecomment-304724157, there are precompiled binaries that you can use.


ROX-18010: Delete non-postgres code in widgets UI

Description

deprecating our Postgres feature flag

Analysis
Find in Files decrease from 36 results in 30 files to 25 results in 19 files

Folder
results
files

Components/workflow
1
1

Containers/VulnMgmt/Dashboard
1
1

Containers/VulnMgmt/Entity
12
12

Containers/VulnMgmt/List
10
8

Containers/VulnMgmt/widgets
11
7

types
1
1

36
30

Review request
Van, please double-check solutions to 2 pre-existing problems:

CvesByCvssScore: replace entityTypes.CVE with linkTypeToUse in  pushRelatedEntity function call on changed line 101.
TopRiskiestEntities: entityContext === {} is always false, as reported by Sonar Cloud report. Although the intended comparison might have been Object.keys(entityContext).length === 0 even that seems redundant with other half of || conditions in changed lines 196 through 225.

Checklist

[ ] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed

yarn lint in ui
yarn build in ui

wc build/static/js/*.js
branch - master: -11288 = 111774351 - 11785639

yarn start in ui

Manual testing

Visit /main/vulnerability-management

See Top risky deployments by CVE count & CVSS score widget.
See Top Riskiest Images widget.
See Recently Detected Image Vulnerabilities widget.
See Most Common Image Vulnerabilities widget.
See Clusters With Most Orchestrator & Istio Vulnerabilities widget.

Visit /main/vulnerability-management/clusters and click a row

See Top risky namespaces by CVE count & CVSS score widget.
See Recently Detected Image Vulnerabilities widget.
See Top Riskiest Images widget.

Visit /main/vulnerability-management/namespaces and click a row

See Top risky deployments by CVE count & CVSS score widget.
See Recently Detected Image Vulnerabilities widget.
See Top Riskiest Images widget.

Visit /main/vulnerability-management/deployments and click a row that has vulnerabilities.

See CVEs by CVSS Score widget.
See Recently Detected Image Vulnerabilities widget.
See Top Riskiest Images widget.
See Most Common Image Vulnerabilities widget.

Visit /main/vulnerability-management/images and click a row that has vulnerabilities.

See CVEs by CVSS Score widget.
See Top Riskiest Image Components widget.

Visit /main/vulnerability-management/nodes and click a row that has vulnerabilities.

See CVEs by CVSS Score widget.

Integration testing

yarn cypress-open in ui/apps/platform

vulnmanagement/clusters.test.js
vulnmanagement/dashboard.test.js
vulnmanagement/dashboardToEntityPage.test.js
vulnmanagement/deployments.test.js
vulnmanagement/images.test.js
vulnmanagement/namespaces.test.js
vulnmanagement/nodes.test.js

ocp-4-13-ui-e2e-tests failure unrelated to these changes

Clusters should redirect from Dashboard when no secured clusters have been added (only applies to Cloud Service)

Timed out retrying after 4000ms: expected '/main/dashboard' to equal '/main/clusters'


Fix sampling of diffuse env map texture with non-uniform control flow

Objective

deferred_rendering and load_gltf fail in WebGPU builds due to textureSample() being called on the diffuse environment map texture after non-uniform control flow

Solution

The diffuse environment map texture only has one mip, so use textureSampleLevel(..., 0.0) to sample that mip and not require UV gradient calculation.

Only merge this if @JMS55 or @DGriffin91 say that the diffuse environment map texture will only have one mip. If that is not the case, this solution is wrong.


Opencv native mat to opencvsharp mat crash.

Hi:
Opencv native mat to opencvsharp mat crash.
Environment:

windows 10
visual studio 2017
WPF
C#

The program crashed after running for 25minutes.
Crashed:

Code:

I want to display camera pictures.

Hi @sevenzoe
You can use
OpenCvSharp.Extensions.BitmapSourceConverter.ToBitmapSource(image);
Or
image.ToBitmapSource();// using OpenCvSharp.Extensions;

Hi @zpmmehrdad:
The program will still crash:

Creating OpenCvSharp.Mat from your native Mat (cv::Mat*) is dangerous. You must use the same OpenCV version, the same VC++ version and  the same dependency libraries. It is difficult. Native library differences occasionally cause crashes.


extract_image_chips on Ubuntu 16.04.02 fails to extract valid data

I am running Ubuntu 16.04.02 in a docker container and compiling the following code with clang 3.8, dlib 19.3, and opencv 3.2:
// create the simple socket
net::Socket sockt = net::Socket(listenPort);

// bind to  port
sockt.bindSock();

// look for connections
sockt.startListening(backlog);

// start accepting data from this new file descriptor
sockt.acceptData(their_addr);

// size of the image from the client
int32_t image_size = 0;

// object to store raw image data
cv::Mat rawImage;

// initialize the detector
dlib::frontal_face_detector detector = dlib::get_frontal_face_detector();
dlib::shape_predictor sp;
dlib::deserialize(argv[1]) >> sp;

std::cout << "Capturing..." << std::endl;

// for writing out images
int image_id = 1;

while (true){

    // retrieve image size
    sockt.getData(&image_size, 4, NULL);

    if (image_size > 0) {

        rawImage.create(1, image_size, CV_8UC1);

        sockt.getData(rawImage.data, image_size, MSG_WAITALL);

        // decode raw image from 1xN into a proper jpeg
        dlib::cv_image<dlib::bgr_pixel> d_image = utils::process_frame(rawImage);

        // this saves a proper jpeg unlike below where we try to save chips
        dlib:save_jpeg(d_image, argv[2] + "full_image.jpg");

        std::vector<dlib::rectangle> detections = detector(d_image);

        if (detections.size() > 0){
            std::vector<dlib::full_object_detection> shapes;
            for (int idx = 0; idx < detections.size(); idx++){
                dlib::full_object_detection shape = sp(d_image, detections[idx]);
                shapes.push_back(shape);
            }
            dlib::array<dlib::array2d<dlib::bgr_pixel>> face_chips;
            dlib::extract_image_chips(d_image, dlib::get_face_chip_details(shapes), face_chips);
            for (int idx = 0; idx < face_chips.size(); idx++){
                std::string fname = argv[2] + std::to_string(image_id) + ".jpg";

                // Saves corrupt jpeg
                dlib::save_jpeg(face_chips[idx], fname);
                image_id++;
            }

        }

        // clear the raw image
        memset(&rawImage, 0x0, sizeof(rawImage));

    } else {
        std::cout << "No message yet" << std::endl;

    }
    // pause for half a second
    image_size = 0;
    usleep(1000);
};

The compiler does not throw any warnings but produces invalid output. Here is an example of a corrupt image chip:

It is worth mentioning that I have tried to compile this bare metal on Ubuntu 16.04 with the same result.  Sometimes part of the image will write correctly but a chip will always have errors.
I have also compiled with -DDLIB_JPEG_SUPPORT and without with the same problem.

I have also compiled with -DDLIB_JPEG_SUPPORT and without with the same problem.

Please provide smaller example. We are not debugging your code here :)
Does examples/face_landmark_detection_ex works fine on your machine?
matrix<rgb_pixel> img, chip;
load_image(img, "test.jpg");
rectangle chip_rect(10, 10, 30, 30);
chip_dims dims(100, 100);
chip_details chip(chip_rect, dims);
extract_image_chip(img, chip, digit);
save_jpeg(chip, "chip.jpg");

Does this minimal code work?

Yes, this is not a dlib issue and this isn't the place to look for C++ help.  But I will point out that memset(&rawImage, 0x0, sizeof(rawImage)); is definitely not right. You can't just go blasting the memory of C++ objects to zero like that.  That's definitely a problem.  I assume there are similar things elsewhere in the code (that you didn't post).  It's highly likely that this kind of thing is causing this problem.

Apologies for the long code example but i wanted to be thorough. I figured out the problem and was able to remove some pieces thanks to your snippet above. The problem is that process_image returned dlib::cv_image which I guess was causing issues since d_image still refers to the original cv::Mat. Thanks for your response.


HTTP code Error

When I do ping-check using curl, I found something weird.
curl http://localhost:55403/app/ping
# {"data":"pong"}
curl http://localhost:55403/app/ping -I
# HTTP/1.1 404 Not Found

Is it the right response?

It's not supported "HEAD" method.


Auto install packages

We can check if individual packages are installed. If not, allow user to install the package they need instead of installing everything.

There is a trade of here.
Providing auto install feature will take some time but is definitely feasible. But if we can wait until everyone put their packages on BioConductor or CRAN, we only need to make these packages the dependencies and these packages will be automatically installed.
So for now let's sit on this problem

My comment is, e.g. if a user only want to use MetaDE, then he won't bother install metaClust at all.
So I think it would be nice if allow user to install packages whenever they need to, not install everything at once. What do you think?

Yes it would be nice. If I have free time I will work on this

@xiaoguang1988 @CHPGenetics This enhancement has been added to release 0.1.0, please help check if it works as expected.

This is an awesome function!
On Saturday, August 27, 2016, schwannden<EMAIL_ADDRESS>wrote:

@xiaoguang1988 https://github.com/xiaoguang1988 @CHPGenetics
https://github.com/CHPGenetics This enhancement has been added to
release 0.1.0, please help check if it works as expected.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/metaOmic/metaOmics/issues/12#issuecomment-242898512,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARPM5Cgm-ilFNhUorMiUucCAsMOx6dq4ks5qj9FXgaJpZM4JuPP4
.

@CHPGenetics @xiaoguang1988 The bug of install_github appears to be permission issue. If you start shiny in sudo permission (start R console in sudo, then start shiny), the issue should be resolved. @CHPGenetics Can you try it? If it really can be resolved this way, I'll just update the error message and README instruction

Restarted my machine and tested auto installing MetaDE. Installed successful. No more bug


act error: Error: The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20

When using mikepenz/action-junit-report@v4
act -j build complains about the following:
Error: The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20
It works for v3 though.

@renepyo seems act requires to be updated. -> https://github.com/nektos/act/pull/1988
GitHub actions retrieved support for node20 around 1 month ago, which this action uses now.

@mikepenz  - to be sure, do I need to update act?

@renepyo that question is best raised in the nektos/act repository.

But I suppose you will have to update the used action docker container


[release-1.9] Upgrade to latest dependencies

bumping pkg -dprotaso
/cc knative/serving-writers
/assign knative/serving-writers
Produced by: knative-sandbox/knobots/actions/update-deps

/lgtm
/approve


nil vs. [] vs. not-set-att-all

https://github.com/kubernetes/kubernetes/issues/70281
So if I send something either as nil or as in empty array, k8s API treats it as not set at all and omits the attribute on the resulting object. This causes problems now when k8s-client saves the config in annotation and determines the json patch operations based on that.
Apply following with k8s-client:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
  namespace: default
spec:
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      tolerations:
      containers:
      - name: myapp
        image: nginx:latest
        ports:
        - containerPort: 80

and after that try to apply e.g.:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
  namespace: default
spec:
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      tolerations: []
      containers:
      - name: myapp
        image: nginx:latest
        ports:
        - containerPort: 80

The json patch operations send would be:
[{"op": "replace", "path":"/spec/tolerations", "value":[]}]

Kube API borks with:
Error from server: jsonpatch replace operation does not apply: doc is missing key: /spec/tolerations

That's because the initial sending of "empty" tolerations results in the deployment object actually not having tolerations set at all so we cannot replace them either on later patches.
I think there's two ways to "fix" this:

"compact" the resource hash before storing it in the las-applied-config annotation. That way whatever was used omits nulls and empty arrays as if they were not given at all
Make the json patch part deal with these. If the patch "calculation" sees the old value as nil/empty array it could transform the operation from replace to add.

I think option 1 might be more future proof and robust.
@jakolehm @kke WDYT?

This seems like a bug in kubectl apply.
We're moving apply into the server and fixing many things about it as we do so. This should be fixed as part of that.

@lavalamp I've seen some working-group mentions on the efforts moving all the merge magic server side. Is there any timeline guestimates available?

This seems like a bug in kubectl apply.

Timeline: we're trying to have an alpha for this release (2018Q4). We should know in the next two weeks if we'll make it or not.
Ah, I didn't catch that you were computing the patch not with kubectl apply. Yes, the patch computation needs to be adjusted. There's multiple ways you could go about this:

take the last applied object, serialize and deserialize to remove null objects, then compute the patch
use dry-run to figure out what the last applied object would have produced if applied right now, then compute the patch based on that (basically the same as the above).
GET the object, adjust the patch until it applies, then use it by sending a PATCH.
Instead of sending a PATCH, GET the object, apply the patch locally, and PUT the result (and retry on conflicts)

I wouldn't recommend using strategic merge patch as it doesn't work for CRD-defined objects. I also wouldn't build in a dependency on the last applied state annotation, as that will be deprecated as soon as I can manage (which probably won't be for at least 6 months).


Up side of a pile of pull requests is that it might emit fresh team members wanted.

PSA: use github notifications, that little blue thing in the upper right and unsubscribe from everything that isn't relevant.  Sorry about all the noise that got in the way.

On Sat, Nov 30, 2024 at 09:46:39AM -0800, Andrew Gauger wrote:

Closed #646 as completed.

Thanks for the catch-up, thanks for reducing the pile of pull requests.
And above all: Thanks for showing the world this project is still alive.
Groeten
Geert Stappers
Silence is hard to parse


Is there a way to get traefik latency through metrics exposed ?

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
Hi,
Wanted to get the traefik induced latency for each request. Is there any metric exposed for the same ?
Could not find anything here Traefik Metrics Overview - Traefik 1.
Sorry for posting this as issue, could not get any response in community
Thanks

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


Set tracing target for networking messages.

This changes the log messages for messages related to network traffic to use the "network" tracing target. This makes it easier to do CARGO_LOG=network=trace CARGO_HTTP_DEBUG=true instead of trying to figure out which modules to include (and to avoid CARGO_LOG=trace which can be too noisy). For example, #12290 moved the location of some log messages to a different module, which broke the documented workflow of using CARGO_LOG=cargo::ops::registry=debug to get networking information.

I'm not sure if we want to start using tracing targets, but I'm intrigued by the idea and I think it would be something interesting to explore. For example, to get fingerprint logging, the logs from cargo_util::paths is extremely useful, but unfortunately people normally don't include it. I'd like to explore adding additional targets like "fingerprint" for things like that.

@bors r+
This seems like a good place for us to experiment with this feature.

:pushpin: Commit f0176a1955b7c9b43c7b8e7bd596475a0264c653 has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit f0176a1955b7c9b43c7b8e7bd596475a0264c653 with merge 552209137bc9c988e14401ced505e297a5fc293c...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 552209137bc9c988e14401ced505e297a5fc293c to master...

If a dependency is set with the same tracing target, will CARGO_LOG=network enable it also?
If this is the case, should we have a less generic target name?

I believe targets are a global namespace, so I think so. But if a dependency does that, presumably the message would be related to networking and we would want it included? The idea is to show everything networking-related.
Also, it seems to be pretty rare that I've seen anyone use the target feature. I would be surprised if any low-level library is doing that.


Disable slicing when unavailable

Disable the slicing button when slicing isn't possible.
Slicing is possible only when there is at least one slicer and that slicer is either not running on the octoprint device or we are neither printing nor paused.
Fixes kennethjiang/OctoPrint-Slicer#17

thank you for submitting this PR. I'm a little tied up this week. will get to it as soon as I get a chance!

Okay, I sent a PR to @foosel.  If it is accepted then the API that I added is unneeded.  In that case, there are choices:

Remove the new API that I added.  That would be the cleanest solution but we would need a fallback in case the version of OctoPrint is too old to support.  Fallback could just be to default "true" or "false".

Retain the new API that I added.  We could take from the slicing API when it's available and only make the extra call to the new API is sameDevice isn't in the properties.

something else?  Is there a way to make it so that new OctoPrint-Slicer requires new OctoPrint?  Maybe in the plugin_check?  Kind of a pain to maintain that, though, and it's a problem for users that don't want to upgrade.

Not sure which is best.

Okay, should be fine now, without the same_device support.  I don't have a 3d printer at the moment to test the functionality so either test it for me, thanks, or wait until next week and I can test it.  Up to you.


Fix arguments for calls to Ruby's Time.at

Time.at takes microseconds as a second arg, not nanoseconds. Fixes conversion of deadline time on the server-side.
Before the fix (some added logging included):
I0708 11:59:31.918294000<PHONE_NUMBER>93856 parsing.c:655] HTTP:1:HDR:SVR: grpc-timeout: 4580m
I0708 11:59:31.918298000<PHONE_NUMBER>93856 timeout_encoding.c:175] Incoming timeout (from_millis): 4580
I0708 11:59:31.918303000<PHONE_NUMBER>93856 timeout_encoding.c:177] timeout(from_millis)=gpr_timespec { tv_sec: 4, tv_nsec: 580000000, clock_type: 3 },
I0708 11:59:31.918307000<PHONE_NUMBER>93856 incoming_metadata.c:74] deadline=gpr_timespec { tv_sec: 7, tv_nsec: 823605568, clock_type: 0 },
I0708 11:59:31.918549000<PHONE_NUMBER>93856 rb_server.c:264] deadline(NewServerRpc REALTIME)=gpr_timespec { tv_sec:<PHONE_NUMBER>, tv_nsec: 498305614, clock_type: 1 },
Deadline is 2016-07-08 12:07:54 -0400 (in 502.385435 secs)

After the fix:
I0708 12:06:02.430514000<PHONE_NUMBER>93856 parsing.c:655] HTTP:3:HDR:SVR: grpc-timeout: 5S
I0708 12:06:02.430522000<PHONE_NUMBER>93856 timeout_encoding.c:180] Incoming timeout (from_seconds): 5
I0708 12:06:02.430528000<PHONE_NUMBER>93856 timeout_encoding.c:182] timeout(from_seconds)=gpr_timespec { tv_sec: 5, tv_nsec: 0, clock_type: 3 },
I0708 12:06:02.430536000<PHONE_NUMBER>93856 incoming_metadata.c:74] deadline=gpr_timespec { tv_sec: 12, tv_nsec: 915133952, clock_type: 0 },
I0708 12:06:02.431128000<PHONE_NUMBER>93856 rb_server.c:264] deadline(NewServerRpc REALTIME)=gpr_timespec { tv_sec:<PHONE_NUMBER>, tv_nsec: 430533854, clock_type: 1 },
Deadline is 2016-07-08 12:06:07 -0400 (in 4.998415 secs)

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok to test.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok to test.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok to test.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok to test.

this is ok to test

I can't find any debugging output to suggest that these failures are related to my change. What's the process for looking into that?

Because of changes made elsewhere to fix some of those tests, I recommend merging from master and pushing again to ensure that your changes did not cause the failures.

@murgatroid99 Rebasing got the required tests passing. Let me know if there's anything else you need from me.

LGTM


Recent chrome bypassing unbound/DNS overrides due to DNSSEC

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[-] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
Yes
[-] I have searched the existing issues and I'm convinced that mine is new.
Yes
Describe the bug
A clear and concise description of what the bug is, including last known working version (if any).
In mid May Chrome turned on a new security option to resolve DNS queries using DNSSEC by default.  This is, of course, a good thing.   However, as a result, Chrome seems to be bypassing local unbound DNS resolution and going direct to the internet, which of course breaks unbound overrides.
I would expect that this would be solvable by turning on DNSSEC support in unbound, but that does not appear to have resolved the issue for me.
I've tried to confirm that DNSSEC is actually working on the OPNSense router.  Accessing https://<IP_ADDRESS>/help witht the unbound DNS DNSSEC option ticked and Firefox configured to use DNSSEC via the router address reports
Using DNS over HTTPS (DoH) | No
Using DNS over TLS (DoT) | No
Using DNS over WARP | No
AS Name | Google
AS Number | 15169
Cloudflare Data Center | MAN

(I get the same result in Chrome, but I did want to remove any chrome weirdness from the equation)
As a result I am not sure whether or not the problem is because DNSSEC in unbound is not working as intended.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Using a recent version of chrome (83.0.4103.116 (Official Build) (64-bit) (cohort: Stable) is what I used) on a machine using OpnSense as a DNS server
Create an override in unbound - for testing purposes, alias any well known website to a different one.
Attempt to access the original web page in chrome.  With Chrome DNSSEC support turned on (default) the web site will resolve to the original address,  With DNSSEC support off, it will resolve to the redirected address.
Turning DNSSEC support on or off in the Unbound DNS settings on the router does not appear to change this.
Expected behavior
A clear and concise description of what you expected to happen.
Overrides should ideally work in modern versions of chrome without the need for any user intervention or configuration changes on the OpnSense router.
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant.
e.g.:
OPNsense 20.1.8_1-amd64
FreeBSD 11.2-RELEASE-p20-HBSD
OpenSSL 1.1.1g 21 Apr 2020
Client is Chrome 83.0.4103.116 on Windows 10 19.10 running on a Threadripper 1920x.
Thank you.

Hello,
I think you are mixing up some things here.
First of all there is a DNSSEC (DNS Security Extensions) validator addon for chrome and as I searched for it I found no evidence that this is used in the Chrome base (same seems for Firefox). What I found and already knew is that DoH (DNS over HTTPS) was put into Chrom[e/ium] last year and defaulted it in may this year.

https://duo.com/decipher/google-makes-dns-over-https-default-in-chrome

These technologies don't have anything to do with each other. DNSSEC is pretty useful because it checks the signatures of signed DNS-Zones. Usually only the last DNS-Server that is queried in your network does this for querying upstream DNS-Servers if you don't have DNS-Zones transferred to your DNS-Servers or a business grade Intranet-DNS which you would know and even for the intranet DNSSEC would be a questianable choice, DoH is a technique that encrypts DNS-Traffic which is imho pretty useless because the endpoint is visible anyways.
Solution for you: Just deactivate DoH in your browsers =)
Additional Information:
If you activate DNSSEC on Unbound (via OPNsense) this just means that unbound checks the signatures of Upstream-DNS-Servers as I wrote above and  DNSSEC would never alter the DNS-Chain alone!
Your config:

Browser -> Cloudflare DoH => Nothing you do with your DNS-Servers will change anything

'Normal' DNS config:

Browser -> Operating System's DNS-Client -> Internal DNS Server (1 -> Internal DNS Server 2...) -> External DNS Servers (...)

So imho the ticket could be closed because it has nothing to do with OPNsense.
Best regards!


Extension hangs while parsing some larger PDDL domain files

Extension hangs while parsing some larger PDDL domain files

Solved by appending - object to domains that have no type inheritance.


refactor: add get_available_parallelism function

Which issue does this PR close?

Closes #13591.
Rationale for this change

In https://github.com/apache/datafusion/pull/13579#pullrequestreview-2465606280, it was suggested that the repeated use of std::thread::available_parallelism with  fallback logic could be refactored for clarity and to reduce duplication. Extracting this logic into a utility function improves code readability and reduces the likelihood of errors.
What changes are included in this PR?

This PR introduces a new utility function:
pub fn get_available_parallelism() -> usize;

It replaces the following repeated code snippet:
std::thread::available_parallelism().unwrap_or(NonNull::new(1).unwrap()).get()

with a call to the new function:
get_available_parallelism()

Are these changes tested?

No tests are added for this change as it is a straightforward refactor of existing functionality. However, if reviewers feel this requires testing, I am happy to add them.
Are there any user-facing changes?

No.

The clippy job failed. This is probably nothing wrong with this PR, see https://github.com/apache/datafusion/issues/13597.

Hi @comphead, Thanks for your review! I just checked the pipeline logs, the clippy errors are not related to my changes. Perhaps it's what @findepi mentioned in the previous comment.

@alan910127 please rebase from the latest main

@comphead Rebased.

Since this is a first time contribution I'll be waiting for another review before merging it in


Add Stylelint check

Add check for Stylelint to Preflight
new check output:
🚀 UpLeveled Preflight v1.23.3
✔ All changes committed to Git
✔ node_modules/ folder ignored in Git
✔ No extraneous files committed to Git
✔ No secrets committed to Git
✔ Use single package manager
✔ Project folder name matches correct format
✔  No dependency problems
✔ GitHub repo has deployed project link under About
✔ ESLint
✖ StyleLint
  › StyleLint problems found in the following files:

    /home/josehower/upleveled-projects/portfolios/next-js-portfolio-web/pages/module.css
    /home/josehower/upleveled-projects/portfolios/next-js-portfolio-web/pages/modulea.sass
    /home/josehower/upleveled-projects/portfolios/next-js-portfolio-web/pages/modulea.scss

    Open these files in your editor - there should be problems to fix.

✔ Prettier
✔ ESLint config is latest version
✔ Preflight is latest version

new check output:

the output in the description needs to be updated with the Preflight output including Stylelint config check too


Cancelation should stop running local runs

UI button press cancel kills remote K8 pod runs, but local runs are still allowed to finish:
(3.8.14/envs/3.8.14-testing) ~/work/sematic$ bazel run //sematic/examples/mnist/pytorch
INFO: Analyzed target //sematic/examples/mnist/pytorch:pytorch (1 packages loaded, 3 targets configured).
INFO: Found 1 target...
Target //sematic/examples/mnist/pytorch:pytorch up-to-date:
  bazel-bin/sematic/examples/mnist/pytorch/pytorch
INFO: Elapsed time: 0.894s, Critical Path: 0.19s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Build completed successfully, 1 total action
Train Epoch: 1 [0/60000 (0%)]	Loss: 2.308694
Received cancelation event                                  <- this should halt execution
Train Epoch: 1 [10000/60000 (17%)]	Loss: 0.813732
Train Epoch: 1 [20000/60000 (33%)]	Loss: 0.502518
Train Epoch: 1 [30000/60000 (50%)]	Loss: 0.376525
Train Epoch: 1 [40000/60000 (67%)]	Loss: 0.275685
Train Epoch: 1 [50000/60000 (83%)]	Loss: 0.243469
(3.8.14/envs/3.8.14-testing) ~/work/sematic$

Fixed by #1004.