How to set the "FEATURE_CLUSTERS" in the training script?

Hi,
Thank you for sharing the great work!
I want to known how to set the FEATURE_CLUSTERS in the training script.
The below is my script.
python suds/train.py suds --experiment-name kitti_06 --pipeline.datamanager.dataparser.metadata_path metadata/kitti-06.json [--pipeline.feature_clusters $FEATURE_CLUSTERS]

you can set that optional parameter if you want to visualize the distilled DINO features. If so, follow the sections in the readme called "Generate feature clusters for visualization." This parameter is optional though.

Thank you very much!

@rockywind @hturki
I use this python suds/train.py suds --experiment-name kitti_06 --pipeline.datamanager.dataparser.metadata_path metadata/kitti-06.json,but  it  has problem.
File "pyarrow/_dataset.pyx", line 1004, in pyarrow._dataset.Fragment.physical_schema.get
File "pyarrow/error.pxi", line 144, in pyarrow.lib.pyarrow_internal_check_status
File "pyarrow/error.pxi", line 100, in pyarrow.lib.check_status
pyarrow.lib.ArrowInvalid: Could not open Parquet input source '/home/cc/suds/data/kitti/dino_02/0006/000000.parquet': Parquet magic bytes not found in footer. Either the file is corrupted or this is not a parquet file.
python-BaseException

It looks like your parquet file wasn't written properly. You can try directly opening it in pyarrow to confirm.

I run this directly python suds/train.py suds --experiment-name kitti_06 --pipeline.datamanager.dataparser.metadata_path metadata/kitti-06.json


error contacting notary server: received unexpected HTTP status: 500 Internal Server Error

Making a docker push to a repository results in this error,
docker --debug push
Signing and pushing trust metadata
DEBU[0000] reading certificate directory: /x/x/.docker/tls/x:4443
DEBU[0000] No yubikey found, using alternative key storage: no library found
DEBU[0000] Making dir path: /x/x/.docker/trust/tuf/x/library/x/changelist
Error: error contacting notary server: received unexpected HTTP status: 500 Internal Server Error

Ok, when tagging our image, if we specified a custom port in our harbor.cfg, we also need to specify it in our tagged image. This was causing an error making it unable to create a token, which led to inability to contact notary server


[TEST] [DO NOT REVIEW] adding commands for industry-platform rp

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.


Use let's encrypt for master

It would be nice that we avoid self-signed certificates for communication with masters.
It seems like terraform supports creating let's encrypt certificates. https://github.com/opencredo/letsencrypt-terraform

Closing in favour of #43


Created task_05txt

Issue: #6

Hey @23abdul23
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @23abdul23
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


Document configuring a new site

In quickstart-hpo-experiment

Can you make it a separate document?

New content: https://github.com/ECP-CANDLE/Supervisor/tree/develop/bin#adding-a-site

Duplicate of #30


can't download your pretrained model

Baidu requires a Chinese phone number, so can you upload your pre-trained model to another file-sharing platform?

Hi, we have uploaded the pre-trained models on Google Drive, please try downloading it via this link.

Hi, we have uploaded the pre-trained models on Google Drive, please try downloading it via this link. Sorry for the inconvenience.


Add systemd

Language name
systemd
URL of example repository
https://github.com/slackhq/nebula/blob/master/examples/service_scripts/nebula.service
URL of syntax highlighting grammar
https://www.freedesktop.org/software/systemd/man/systemd.syntax.html
Most popular extensions
.service
Full list of systemd unit files:
systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.device(5), systemd.mount(5), systemd.automount(5), systemd.swap(5), systemd.target(5), systemd.path(5), systemd.timer(5), systemd.slice(5), systemd.scope(5), systemd.nspawn(5)
Detected language
None

Hey, i would like to work on this. Where should i start ?

@papapathe you can add it here

@papapathe all the details you need for adding support are in the CONTRIBUTING.md file

I have added support in #5767 , Please review it 😄


Error in before() block is ignored if RETRIES is greater than zero

In our case: we request some test data in a before() block using cy.request(), then use that data in our tests.  If the request to get the data fails the test is guaranteed to fail so it should not execute.  When we use the retries plugin the test does execute, then shows the error that occurs because we don't have the test data.  The actual error causing this is that the service we were reaching out to returned a 404 but the error shown in the test report is that cypress timed out trying to find an element that didn't exist.
This masks the real issue that causes a test failure and makes debugging failures in CI very difficult.
To repro this issue, run the spec from the branch in my fork of this repo: https://github.com/drewbrend/cypress-plugin-retries/blob/patch-1/cypress/integration/spec.js
Expected:  If a failure in the before() or beforeEach() block happens, the test shouldn't be ran, regardless of the number of retries.
Actual:  If the value of the RETRIES environment variable is greater than zero, even if a failure occurs in a before() or beforeEach() block, the test will be run.  This causes the error shown in the test results to be inaccurate.
Here is a screenshot of what this looks like after it is ran:

thanks @drewbrend, I will take a look at this along with #19

:tada: This issue has been resolved in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


OTG: Align the test TE_13.1 with ATE

OTG: Align the test TE_13.1 with ATE

Pull Request Functional Test Report for #2021 / 8b8f69e1954e78b7adaf38755df8f22eb11c27dd
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

TE-13.1: gRIBI route ADD during Failover

Cisco 8000E

TE-13.1: gRIBI route ADD during Failover

Cisco XRd

TE-13.1: gRIBI route ADD during Failover

Juniper cPTX

TE-13.1: gRIBI route ADD during Failover

Nokia SR Linux

TE-13.1: gRIBI route ADD during Failover

Openconfig Lemming

TE-13.1: gRIBI route ADD during Failover

Help

@ANISH-GOTTAPU : Needs a more recent merge with main.

@ANISH-GOTTAPU : Needs a more recent merge with main.

updated


fix: updated the macsec fields as per latest api spec

PR summary
updated the macsec fields as per latest api spec
Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add count rate display to qt3scan

use the side panel to display running average count rate (over some reasonable recent time range)

I think the idea here is to add GUI elements such that a user of the application can type in the name of the channels that connect to various hardware, allowing for configuration changes to be made after the application is launched.

I have worked on implementing something similar. This is what it looks as of now. The displayed values are:

Current Value
Mean over a user-defined range, default to 400 ms
standard deviation over same range as mean (expected poison std of mean == sqrt(mean))

The major difference to the proposed change is that the values are displayed on the figure rather than the side panel. This was easier to implement, as we do not have to refer to the scope data through the side panel. Happy to discuss any suggestions before I submit a pull request!

For qt3scan we should look more into the following function to allow a user to click on a scan and get the exact count rate at that pixel: https://matplotlib.org/stable/api/image_api.html#matplotlib.image.AxesImage.get_cursor_data


Trying to change my default US layout to SP layout

I'm trying to create a USB Rubber Ducky with Raspberry Pi Pico following this tutorial: https://www.youtube.com/watch?v=e_f9p-_JWZw&t=472s
The thing is i've tried to get your layout and keycode for SP keyboard, move both file to the raspberry pico lib folder, and i've also changed code.py as you suggested on this post: https://github.com/dbisu/pico-ducky/issues/10#issuecomment-910684858
When I've done everything, my code.py corrupted and could do anything else. What am I doing wrong?
Thanks for your time.
Regards,
Guillem

Corrupted ? Like, the content of the file is messed up ? Or do you just mean it doesn't execute ?
There's 3 files to copy (py or mpy version)

keyboard_layout.py
keyboard_layout_win_sp.py
keycode_win_sp.py

You can see if there's an error printed out to the serial console:
https://learn.adafruit.com/welcome-to-circuitpython/kattni-connecting-to-the-serial-console
If you can use discord, it's the better place for support, #help-with-circuitpython on the adafruit discord. (No private messages).

I was missing the keyboard_layout.py... Somehow I didn't read that this file should've been moved to the raspberryxd. Thx for your help.
Btw do you know how to prevent the rubber ducky script from running every time it's plugged in?
Thx for your help mate


twitch: make things spooky

I think this is 3/5 PRs towards that free hacktoberfest shirt. I don't mind that I merged them all.


disallowSpacesInsideTemplateStringPlaceholders incorrect

This just started on 2.9:
disallowSpacesInsideTemplateStringPlaceholders: Illegal space before "}" at ./node_package/tests/buildConsoleReplay.test.js :
    52 |  ];
    53 |  const actual = consoleReplay();
    54 |  const expected = `console.log.apply(console, ["some message","{\\"a\\":1,\\"b\\":2}"]);
--------------------------^
    55 |console.warn.apply(console, ["other message","{\\"c\\":3,\\"d\\":4}"]);`;
    56 |  assert.equals(actual, expected, 'Unexpected value for console replay history');

jscs is not catching the fact that the syntax within the backticks is for interpolation.
https://github.com/shakacode/react_on_rails/blob/master/node_package%2Ftests%2FbuildConsoleReplay.test.js#L52
@ikokostya, here's the issue: https://github.com/jscs-dev/node-jscs/blob/0c4602569fb435bf98127617fe9745db173f88d5/lib/rules/disallow-spaces-inside-template-string-placeholders.js#L59
you're not checking that we're inside of an interpolation.
TBH, I think some better parsing needs to be done for the beginning and the end.
Maybe you can crib how babel is doing this?
CC: @alexfedoseev

Look like this issue affects only 2.x branch: https://github.com/jscs-dev/node-jscs/blob/2.x/lib/rules/disallow-spaces-inside-template-string-placeholders.js#L60


status indicators for output cells

One way to use this which I imagine will be very standard is with a separate output area for each input cell. In that situation, it is very helpful to have a "working" spinner and a success indicator to show the user what's going on.

I like this idea- although, admittedly, I'm not sure it needs to live this low in the code.  What prevents you from just using a status indicator div instead of the output area div, at a higher level?

Yup, sure. Just pointing out that almost everyone is going to have to do
this.
On Thu, Aug 13, 2015, 5:28 PM Jonathan Frederic<EMAIL_ADDRESS>wrote:

I like this idea- although, admittedly, I'm not sure it needs to live this
low in the code. What prevents you from just using a status indicator div
instead of the output area div, at a higher level?
—
Reply to this email directly or view it on GitHub
https://github.com/jupyter/jupyter-js-output-area/issues/6#issuecomment-130849606
.

In the notebook we have now, there are two indicators.  One for the entire page and one for the cell as a whole.  The second one of the two is the most similar to what you suggest, but right now that is done using the cell prompt, which isn't part of the output area and is instead part of the input area.  I could see it being a part of either or both, since the input is the piece that makes the execute request, where the output waits for the response.  Are you suggesting moving the indicator it to the output area?  Or adding another indicator, instead to the output area?

These are good questions. Personally I think having an indicator in the output area makes sense. However, we shouldn’t make decisions about the notebook UI here, so you're right that this shouldn't live in here.

Yeah, I was thinking of this component as a thin layer on top of transformime. .... like a Transformime array thingy, but not much more.  Along that same tone, I don't think the "collapsing" output feature should live in this repo - it's very notebook specific.

Agreed!
On Fri, Aug 14, 2015 at 12:44 PM Jonathan Frederic<EMAIL_ADDRESS>wrote:

Yeah, I was thinking of this component as a thin layer on top of
transformime. .... like a Transformime array thingy, but not much more.
Along that same tone, I don't think the "collapsing" output feature should
live in this repo - it's very notebook specific.
—
Reply to this email directly or view it on GitHub
https://github.com/jupyter/jupyter-js-output-area/issues/6#issuecomment-131175393
.


Proposed technique for returning custom headers (with simple unit test)

Proposed technique for returning custom headers (with simple unit test)

Looks like I reduced the code coverage a little. If you want to accept this, I'll improve the coverage of the unit test.

@jmcs could you check this?

One other question I had was would you like me to rename the function get_data_status_code to something more meaningful since it now returns data, status_code and headers?

There are only two hard problems in Computer Science: cache invalidation and naming things. - Phil Karlton

Do you have any suggestion for the new name?


Add support to maintain backend information in  an element

for example,
element.opts(plot=dict(height=100), backend='bokeh')

It would also be useful to be able to query which backend(s) at attached to a particular hv object.
Use case: a dictionary of hv objects rendered as
* a bokeh holomap, with hover and zoom turned on
* a matplotlib svg output
e.g., see https://github.com/ea42gh/HoloviewsPlayground/blob/master/GenerateDocument.ipynb

Generally we try to keep our objects separate from the backends - the only thing that can be backend specific are the custom option trees that are associated with the objects. As a result, I'm not sure whether this proposal makes sense but maybe @philippjfr sees a concrete way to implement this suggestion in a way that integrates well with everything else.

Can't this be an option, conceptually like any other?  The option trees are already backend specific; there could just be an optional label that declares that this particular backend should be used by default for this object if not otherwise declared with %%output, etc.

Generally we try to keep our objects separate from the backends

I think this makes sense on the opts method (and possible the magic too), currently the .opts magic implicitly sets the supplied options on the OptionsTree for the currently selected backend. Letting the user supply an explicit backend to assign the options to makes perfect sense to me and would get around various annoyances setting options for multiple backends.

It might not be too hard to implement although I rather not add anything new to the options system.
My worry is that supporting this makes both specification and parsing harder than it already is now: there are already more enough issues to worry about without making it more complicated than it already is.

My worry is that supporting this makes both specification and parsing harder than it already is now

I don't quite see the issue, it's both easy to implement (literally just needs to pass backend to the Store.options calls inside .opts), gets around a major annoyance, and by default nothing changes. I think the global backend state is a bit weird and optionally being explicit about what backend you're actually specifying options for is a good thing.

I can make a PR attempting this to see how it goes and so we can discuss this further.

I'd like to be able to set options for both 'matplotlib' AND 'bokeh' for the same object.
Which set is used would simply depend on the backend set in the current cell.

Oh, have we been confused about what you are requesting then?  Your latest comment sounds like a duplicate of https://github.com/ioam/holoviews/issues/803.

Oh, have we been confused about what you are requesting then?

I don't think so, I was the one to originally suggest the proposal outlined here, #803 is specifically about the magics while this is about .opts and I'm no longer even so sure about the proposal for the magics outlined there.

Just looked at #803 - sounds confusing.
What I was driving at is that I would like to do something akin to
the function error_evolution_plots()
in  https://github.com/ea42gh/HoloviewsPlayground/blob/master/GenerateDocument.ipynb
but setting the both plot options
h=h.opts(bokeh_spike_plot_opts,'bokeh').opts( mpl_spike_plot_opts, 'matplotlib' )
and have the chosen options used for the object depend on the active backend:
%%output backend='bokeh'
h     # renders using the bokeh opts

%%output backend='matplotlib'
h     # renders using the matplotlib opts

What got me thinking about it was that I wanted bokeh in the notebook
to be able to zoom, pan, hover...
but needed matplotlib to save the figure to file

This has been addressed, both .opts and .options now let you specify an explicit backend.


Correct a spell

As you can see, there is a missing space between words "in" and "Gothenberg", I can help you correct that!

Please I request


Materialbox. Added option: "originSizeIfPossible"

This option allows you not to change the size of the image, which is less than the screen size.
Proposed changes
Small images are stretched to the full screen, which sometimes looks awful. This option will not stretch such images.
Types of changes

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

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I've actually come across this issue and was wondering why such option wasn't already built in. Definitely needs to be added.


Logstash 1.3.3 and 2.3.4 from same puppet master

Hi,
We currently have Logstash 1.3.3 deployed to our environments, and we've begun replacing it with Logstash 2.3.4.
The first though was to do this in our testing-environment first, with this puppet module (as we already use it for 1.3.3).
However, due to the fact that the new version of this module does not support the old version of logstash, I'll have to run two different versions of them at the same time. Is this possible?
Or do I need to rename one of the module versions to something else? If so, any pointers on what I need to be aware of when doing this?
Best regards,
Robin

You'd create 2 different Puppet environments.
In one you can run older version of the logstash module and in new you
could run the new one.
Once you have migrated to newer version of logstash you could do away with
the separate environment in puppet.

Absolutely. Environments are a common way to achieve this. A Puppet environment is a separate copy of your all your configuration and code that is applied to only those hosts configured to be in that environment.
https://docs.puppet.com/puppet/latest/reference/environments.html
It's very common to have each environment check out a different branch of your Puppet code from version control. This one of the (many) great reasons to version control your Puppet.

Sorry for slow response.
I'm just wondering if I will not encounter bug PUP-731 if I run with multiple environments for this?
We are currently running Puppet Enterprise 3.3 I believe.

I think you'll be fine. The module is implemented in pure Puppet, so there are no native (ruby) types in there.
Good luck with your multi-environment future! :beers:


v2.14.7

🐛 Bug Fixes

cli

#8194 Avoid error about nuxt-edge if installed in parent node_modules
#8134 Mode deprecation with explicit spa or universal flag

vue-app

#8170 Use getter to provide this.$nuxt
#8068 Use mixin to provide this.$nuxt
#8055 ScrollRestoration hasn't set

types

#8182 Add type for serverMiddleware object format
#8169 Make NuxtConfig an interface

generator

#8166 Handle when no routes.json defined

💖 Thanks to

Daniel Roe (@danielroe)
Dmitriy (@Kolobok12309)

Codecov Report

Merging #8195 into 2.x will increase coverage by 0.00%.
The diff coverage is 85.71%.

@@           Coverage Diff           @@
##              2.x    #8195   +/-   ##
=======================================
  Coverage   68.91%   68.92%
=======================================
  Files          91       91
  Lines        3851     3855    +4
  Branches     1048     1049    +1
=======================================
+ Hits         2654     2657    +3
- Misses        972      973    +1
  Partials      225      225

Flag
Coverage Δ

#unittests
68.92% <85.71%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

packages/generator/src/generator.js
85.85% <66.66%> (-0.37%)
:arrow_down:

packages/cli/src/utils/config.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


ros2 controllers are not working with bullet-featherstone plugin in gz harmonic

Environment

OS Version: Ubuntu 24.04

binary build

ros-jazzy-gz-ros2-control-demos/noble,now 1.2.8-1noble.20241118.194255 amd64 [installed]
ros-jazzy-gz-ros2-control/noble,now 1.2.8-1noble.20241118.193506 amd64 [installed]

gazebo harmonic (binary build)

ros-jazzy-ros-gz-sim/noble,now 1.0.7-1noble.20241115.212712 amd64 [installed,automatic]

Description
When the bullet-featherstone physics engine is used with gz harmonic, the controllers are not getting into active state and are getting timed out. sometimes, even if they are transitioned into active state, I am unable to control the joints.  When the plugin is changed to default or  dartsim, the controllers are being loaded and executing as expected (however, they dont support mimic joints as we are aware)
Steps to reproduce

ros2 launch gz_ros2_control_demos gripper_mimic_joint_example_position.launch.py
ros2 run gz_ros2_control_demos example_gripper
you can observe that the gripper joints are not moving.

This is happening not just with the demo, but also with the custom packages that I am working with.

Is there any update on this?


[PLAT-435] chore: enable to upgrade axios by renovate

As the original issue https://github.com/autifyhq/autify-sdk-js/pull/176 is already solved axios upgrade by renovate is enabled again.

Is it ok to let dependabot upgrade axios? like this PR: https://github.com/autifyhq/autify-sdk-js/pull/242
I see Axios usually has some break changes and missing compatibility with other libs like axios-logger so making it update separately make sense to me

@henchiyb

Axios usually has some break changes and missing compatibility with other libs like axios-logger

Do you still see the same type error on the PR I linked on the description?

No, it was solved by update axios-logger version 🙆♂
I mean we still can keep renovate skip the axios update and let dependabot create another PR to update it, it will be easier to handle breaking change of axios if have any

@henchiyb

it will be easier to handle breaking changes of axios if we have any in the future

umm 🤔 I don't understand...
How does dependabot let us handle breaking changes comparing to renovate?

How does dependabot let us handle breaking changes easily comparing to renovate?

Renovate will add multiple libs version updates in a Pull request, right?
Dependabot will create a dedicated PR, for example, a PR to update axios version, so I think working on it will be easier, at least it's not block other libs update (IMO)

@henchiyb
I sound like saying to stop grouping lib upgrades with renovate.
It doesn't make sense to me to handle axios from other libs.

@henchiyb

I only concerned about axios

Why are you concerned specifically about axios?
Even if we had compatibility between axios and axios-logger once before it doesn't necessarily mean that we will have incompatibility with axios more frequently than other libraries.

Dependabot will create a dedicated PR, for example, a PR to update axios version

Even if Dependabot creates a dedicated PR for axios, type errors can occur when upgraded axios version is incompatible with current versions of other libs like axios-logger. I think it can happen regardless to grouping.

Why are you concerned specifically about axios?

That my personal experience with Axios before, they quite frequently update (that's good) and sometimes I need to update my code too as I remember


Docusaurus depends on<EMAIL_ADDRESS>with CVE-2020-7753 vulnerability

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
<EMAIL_ADDRESS>depends on<EMAIL_ADDRESS>which depends on<EMAIL_ADDRESS>which is breaking our CI builds with this security scanner failure:
[INFO] _________________________________________________________________________________________________________________________________________________
[INFO] |Security Alerts                                                                                |
[INFO] |_______________________________________________________________________________________________________________________________________________|
[INFO] |Alert title                             |Affected component                      |Severity                      |Due date                      |
[INFO] |________________________________________|________________________________________|______________________________|______________________________|
[INFO] |CVE-2020-7753                           |trim 0.0.1                              |High                          |                              |
[INFO] |________________________________________|________________________________________|______________________________|______________________________|
[INFO]
##[warning]Component Governance detected 1 security related alerts at or above 'High' severity. Microsoft’s Open Source policy requires that all high and critical security vulnerabilities found by this task be addressed by upgrading vulnerable components. Vulnerabilities in indirect dependencies should be addressed by upgrading the root dependency.
[INFO] To change the severity threshold or build result, either dismiss the alerts in Component Governance or update the settings of this build task.
[INFO] Please contact<EMAIL_ADDRESS>with questions.
[INFO] Took 1.3847636 seconds to query alerts.

Reproducible demo
N/A
Steps to reproduce
Here's an easy way to repro the issue:

npm init
npm install @docusaurus/mdx-loader
npm audit

                       === npm audit security report ===

                                 Manual Review
             Some vulnerabilities require your attention to resolve

          Visit https://go.npm.me/audit-guide for additional guidance

  High            Regular Expression Denial of Service in trim

  Package         trim

  Patched in      >=0.0.3

  Dependency of   @docusaurus/mdx-loader

  Path            @docusaurus/mdx-loader > @mdx-js/mdx > remark-parse > trim

  More info       https://github.com/advisories/GHSA-w5p7-h5w8-2hfq

Expected behavior
Docusaurus should not depend on packages with high severity security vulnerabilities.
Actual behavior
Security vulnerability
Your environment

Docusaurus version used: 2.0.0-beta.18
Environment name and version (e.g. Chrome 89, Node.js 16.4): Node v14.17.0
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Windows 10

Self-service

[ ] I'd be willing to fix this bug myself.

Please see https://github.com/facebook/docusaurus/issues/6394

If your CI requires zero audit warning, your CI is broken. DO NOT rely on security audit for front end build pipelines.

DO NOT rely on security audit for front end build pipelines.

@slorber Could we get a second opinion on this advice?

I understand that the way an NPM package is used may make it impossible for a security vulnerability to be exploited
I also understand that in many cases, this impossibility is immediately "obvious" to a knowledgeable person

However in a large code base, the way an NPM package is used is difficult to keep track of. Code evolves constantly. The analysis itself can be tricky. For example Docusaurus's hybrid client/server rendering makes it non-obvious whether a given NPM package will be executed by the browser runtime or Node.js tooling.

For these reasons, corporate security departments prefer to simply upgrade every vulnerable package rather than carefully reviewing each case.  I think I agree with this mentality.
A categorical recommendation "DO NOT rely on security audit" seems... not wise

Apparently, the same issue has been responded to by multiple maintainers:

https://github.com/facebook/docusaurus/issues/5501
https://github.com/facebook/docusaurus/issues/5348
https://github.com/facebook/docusaurus/issues/5051

My response represents the response you will get from every single maintainer, and generally most maintainers from the front-end toolchain. Docusaurus builds a static site; there's no way a user could be exploited by any security vulnerability whatsoever, unless they actively XSS themselves.

The data flow of Docusaurus is always one-way: developer -> build pipeline -> deployment env -> user. The user never sends data back to the server. The only viable attack vector that we are aware of is if you are outsourcing translations and injecting them via dangerouslySetInnerHtml, which may cause an XSS attack from a malicious translation contributor if there's no proofreading process—due to this consideration, all of our HTML text labels are untranslatable.
The lesson is that security audits are broken—it's not my word, it's the consensus from every OSS maintainer. Whenever you open a security issue somewhere, don't just say "there's a known CVE"—prove to us how this CVE can be actually exploited as an attack vector. Even better, please report this through the security portal for responsible disclosure.

The user never sends data back to the server.

Take a look at our Docusaurus site:
https://rushstack.io/community/events/
Users do login-with-GitHub and then interact with a Node.js service via web pages that are rendered by the Docusaurus engine. You're really making a lot of assumptions about how a particular Docusaurus site might work.

That's your own code. Unless it's wired through some official Docusaurus API, we can't help with that. Since you are reporting it to upstream, and you have traced it down to exactly remark-parse, I'll assume you know whether any security threat comes in that chain😅

we can't help with that

Upgrading your @mdx-js/mdx dependency would fix this issue.

Since you are reporting it to upstream, and you have traced it down to exactly remark-parse, I'll assume you know whether any security threat comes in that chain

Yes, but I'm not the person who is a concern.  It is the not-knowledgeable engineer who later adds another project to the same monorepo.
For example, let's say this new project is an Express service that happens to invoke trim() on a potentially malicious input, resulting in a real denial-of-service.  Our security scanner should flag catch that, but oops! -- CVE-2020-7753 is exempted because at the time it seemed irrelevant for the Docusaurus project. (If I understand correctly, you're actually arguing to go further and disable every security check for the entire repo; I can't imagine any corporate compliance group tolerating that approach!)
See, security vulnerabilities by nature are tricky to analyze. This is why it's simpler just to work to get them eliminated from the dependency tree, rather than getting into armchair debates about each vulnerability that comes along.
As a maintainer of OSS myself, I would certainly give a lower priority to fixing an irrelevant-seeming vulnerability. But I would not dismiss it or argue that we shouldn't bother fixing the vulnerability at all, particularly for a high profile project like Docusaurus.

Upgrading your @mdx-js/mdx dependency would fix this issue.

That's the whole point of every issue I've been pointing to—right? We bump dependencies every week, there's no reason why we won't upgrade it if we can. However, upgrading to MDX v2 has been postponed to Docusaurus v3 because it would be a huge breaking change that will influence every single user, and it also uses ESM which we are not compatible with yet. We have #4029 and #6520 to track them

If I understand correctly, you're actually arguing to go further and disable every security check for the entire repo

I'm saying you should ignore it for Docusaurus because it's a front-end build tool, repeat "build tool". It doesn't offer any runtime features. Your comparison to Express is inadequate and there's a world of difference in between, which is why I said the "single direction of data flow" matters.

security vulnerabilities by nature are tricky to analyze

Totally agree. That's why I'm spending so much time demonstrating to you it doesn't matter, instead of instantly dismissing it as "it doesn't matter; now go".

particularly for a high profile project like Docusaurus.

Well, there are much higher-profile projects that take literally the same stance: https://github.com/facebook/create-react-app/issues/11174
Again, we don't work on your team, we can't control your security policy. All we can ask you is, when you open a bug report, please please provide a reproduction. Maintainers have limited time (I have relatively much more time than @slorber but I'm volunteering), so it's important for you to demonstrate yourself how a particular bug is Docusaurus' issue, and for CVEs, how it causes tangible harm. It takes you and your team probably less than 5 minutes to run npm audit and write that report, but had we not been aware of this issue before, it would take us much more time than that to actually verify it's a security threat. The burden is on you, if you want to see it fixed, to demonstrate end-to-end why it's a problem and how we can go about fixing it. Security bugs are no exception to the reproduction – cause track-down – solution proposal workflow.

See, security vulnerabilities by nature are tricky to analyze.

Not all of them IMHO.

To be affected by such Denial-of-Service you'd have to want to hack yourself and commit malicious content on Git.
And it would only DOS your CI (potentially blocking or slowing down the deployment), not really affecting real site visitors.

I don't think it's good to disable/ignore all security warnings, but I guess in our context you can just ignore all those Regular Expression Denial of Service errors by default.
I believe those shouldn't have Severity: Hight in the first place 🤷♂ and in our particular context it's probably not even Medium.
See also https://overreacted.io/npm-audit-broken-by-design/

However in a large code base, the way an NPM package is used is difficult to keep track of. Code evolves constantly. The analysis itself can be tricky. For example Docusaurus's hybrid client/server rendering makes it non-obvious whether a given NPM package will be executed by the browser runtime or Node.js tooling.

We keep the browser runtime very small in core and theme-classic so there's only a limited number of dependencies being used there.
If there's a DOS vulnerability in a browser package that could affect real users, we'll look into it as a priority.
Now if you don't know if it's server or browser code, you can ask (like in this issue) and we'll tell you.

We don't have the bandwidth to fix all those harmless vulnerabilities ourselves, but I understand if your company remains afraid of such vulnerabilities.
It remains possible for you:

to fork the project and fix those vulnerabilities (some version bumps are not so easy)
force resolution of trim to a newer version, hoping it will keep working (eventually use patch-package to adapt some code that doesn't work)
help us fund the project so that we have more bandwidth to fix such vulnerabilities.


feat(ci): add is_forked_pull_request parameter to CircleCI configuration

This pull request introduces changes to the CircleCI configuration files to handle forked pull requests differently. The key changes include adding a new parameter to identify forked pull requests and modifying workflows to conditionally execute jobs based on this parameter.
Changes to CircleCI configuration:

.circleci/artifact_upload_config.yml: Added a new is_forked_pull_request parameter to the configuration.
.circleci/config.yml: Updated the job to generate configuration by setting the is_forked_pull_request parameter based on the branch name.
.circleci/main_config.yml: Added the is_forked_pull_request parameter and updated workflows to conditionally execute jobs based on this parameter. [1] [2] [3]

Detected nonzero diff in genesis. This PR modifies the genesis data of at least one chain in the registry, which may or may not have been intended. You can see the detail here.

Detected nonzero diff in rollup config. This PR modifies the configuration of at least one chain in the registry, which may or may not have been intended. You can see the detail here.


Add auto/manual mode switch for comfoconnect

Home Assistant release with the issue:
0.100.1
Last working Home Assistant release (if known):
none
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Integration:
comfoconnect
Description of problem:
Zehnder comfoconnect can be set into auto or manual modes. Please add a switch input to change this mode or read current setting. This is supported by undelying pycomfoconnect lib. Please see values CMD_MODE_AUTO and CMD_MODE_MANUAL in const.py
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum. Thanks!


When can we get next major release?

First of all, thanks for the tool!
Right now, I really need the output javascript function, so when can get the next release?

I want to finish browser-based rendering first, but currently I don't have time to do it...

canvas 1.3 no longer builds for me on OS X with macports. canvas 1.6 is fine. Something is also up with _.findWhere() on our testing machine.
My build is broken because of this dep. ...and so I fork.

Any updates about a new version? I also see issues with canvas, could we get a minor release or a RC or anything like this?


Feature required

Hi @nitishmakhija
I am working on an app where I need to show coach marks, and your utility is really simple and easy to use, but still scalable enough to serve the purpose, so I would like to thank you for that.
The only thing missing is the ability to add a button to it, because user will never realise how to dismiss it, either by tapping it or tapping anywhere else, so there should be a button with customisable text, like Ok or Next or something.
Looking forward to your response.
Regards,

@MrJai sorry for replying late I am just maintaining this repo, enhancements as pull requests are welcomed


Update vso.work_full description to match UI

The UI for creating a PAT with the vso.work_full scope is labelled as "Read, write, & manage", not "Full".
The scope also includes the ProcessTemplate.asmx#POST endpoint, which is used for importing new processes/process templates.

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

@mijacobs
Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@mijacobs any chance that you could approve this, or reassign somebody who can?

@Court72 Thank you!!


Cannot Run Job on Sunday 8:00 AM UTC

I have added logs to my application whenever it runs my Job to make sure it has properly executed.
When I schedule my Job on Sunday 8:00 AM UTC, it fails to execute (no logs generated):
// Run function every Sunday at 8:00 AM UTC
go func() {
    gocron.ChangeLoc(time.UTC)
    gocron.Every(1).Sunday().At("08:00").Do(MyFunction)
    <- gocron.Start()
}()

However, if I schedule the Job on a different day (e.g. Thursday), it executes (logs were generated):
// Run function every Thursday at 8:00 AM UTC
go func() {
    gocron.ChangeLoc(time.UTC)
    gocron.Every(1).Thursday().At("08:00").Do(MyFunction)
    <- gocron.Start()
}()

Is there something I am doing wrong when scheduling my Job on Sunday 8:00 AM UTC, or is there an issue with using gocron for this specific interval?

same as Days()

Bump, anyone? Is is almost a Year now. I have similar issues.

Same thing happen, gocron suddenly does not trigger at certain hour.
gocron.Every(1).Day().At("22:00").Do(something, config)
gocron.Every(1).Day().At("14:00").Do(somethingElse, config)
It works only at 14:00 but 22:00 no run at all. Is it a bug or has to do with machine time setting?


gerbil

[x] hello schemer
[x] hello schemer star
[x] custom prefix installation
[ ] docker
[ ] checksum

it works but disabled in CI.


Purge Prometheus database and reduce retention time

I have this setup running on a normal Ubuntu server and the database has grown to several gigabytes in size.
How can I set the Prometheus database to only retain a certain time period of data and discard the rest?
Is there a way to manually purge the database entries? I'm hesitant to just delete the files in the
/Docker-Raspberry-PI-Monitoring/prometheus/data folder.

I'm not an expert on Prometheus, so please correct me if I'm mistaken.
In the docker-compose.yml file, under the prometheus service, under the commands section, you can add the following options to ensure that the data for the last 15 days is always kept (for example) under 10 GB:
- '--storage.tsdb.retention.time=15d' # Retains data for 15 days
- '--storage.tsdb.retention.size=10GB' # Limits data retention to 10GB

Afterward, you will need to restart or recreate the service for the changes to take effect.

That worked! Thanks for the answer.


#1140 added SchemaExample() to set the example to schema

Describe the PR
a possible solution to #1140

Looks like the unite tests are failing now.

ok sorry i fixed that

@mschneider82 Thanks for your contribution.


Keep last lines of command output (after send command to image) visible in window

Currently, when a command is sent to a docker image (e.g. ping google.com, or find ., only first lines of the output are shown in vim window and after the window gets filled, new lines appended to the end are not visible (unless you move there cursor manually).
Expected behaviour is to keep the last line always visible, similarly as when you run such command in neovim :terminal window.
Note, that if #20 (follow mode for logs) are to be implemented, the same shall apply to them too.

Would you mind providing screenshot? Thanks.

Sure. Sending command find . to running ubuntu image.
After I run it:

Then I :set number to show line numbers:

and use G to jump to the bottom:

using:

:version
NVIM v0.3.1-1-g489d32f2b


Is GPULMFIT really a general purpose fitting code?

Could you give a reference to the article in PLOS one?

http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0076665


upstreaming to conduit

hey @hariso
i also link using benthos with conduit.  do you think this will ever be integrated ?
also "The Docker compose file at test/docker-compose.yml can be used to quickly start a Kafka instance.", but you forgot to commit it ?

thanks - love using benthos with conduit...


How did you get the ESRGAN pre training model?

How did you get the ESRGAN pre training model?

Hi, @weiyuxingchen
I pre-trained the model with L1 loss.
You can use the RRDB_PSNR_x4.pth model as the pre-trained model.


[ADD]: Add Issue Templates for the Project

Most Open Source projects have issue templates carry Issues and Pull Request Templates to help the project maintain some organizational flow. To carry the best practices of Open-Source forward, we would like new forms and templates to be sent in as PULL REQUEST to this repository. Please check the CONTRIBUTING.md for reference

Related issue: #9

Hey, I would like to take over this issue


Refactor SingleTree

Overview
I've recently been looking into fixing the bug reported in #2044. And in doing so, I just did some refactoring to make the code (hopefully) a little cleaner and easier to understand.
And then it should be easier to review the PR that contains the actual bug fix (coming soon).
The commits are intentionally atomic so they can be reviewed one at a time.
Description of the changes proposed in this pull request:

Added docstrings for SingleTree class, to list down the available attributes on that class + what they individually mean. Just for our collective understanding only. It's not rendered into the public API documentation.
Added an intentionally failing test that demonstrates the problem in #2044. The fix will come in the next PR.

The other reason why I added a test is to hopefully convince that there wasn't any bugs introduced as a result of this refactor.

There were a lot of repetitive dictionary lookups in the original implementation. I saved the lookup value into a local variable and reused it, so the code is more concise and should technically run just a tad faster (I didn't bother benchmarking).
Refactored the if-else logic for if vertex['split_index'] not in visited: to use the guard clause pattern (saves us 1 level of indentation).

Checklist

[X] Related to #2044
[X] All pre-commit checks pass.
[X] Unit tests added (if fixing a bug or adding a new feature)
Added entry to CHANGELOG.md (if changes will affect users)

I think there may be further opporunity to refactor. The __init__ method is very long, as it instantiates the object from multiple different sources. As a consequence, it's not particuarly modular.
One alternative pattern could be to use a series of class constructor methods. What do you think? In pseudo-code, something like:
class SingleTree:
    def __init__(self, children_left, children_right, children_default):
        self.children_left = children_left
        self.children_right = children_right
        self.children_default = children_default

    @classmethod
    def from_treelike(cls, tree):
        if safe_isinstance(tree, "sklearn.tree._tree.Tree"):
            return cls.from_sklearn(tree)

        elif type(tree) is dict and "features" in tree:
            return cls.from_dict(tree)

        elif safe_isinstance(tree, "pyspark.foo.bar"):
            return cls.from_pyspark(tree)

    @classmethod
    def from_sklearn(cls, tree):
        ...

    @classmethod
    def from_lightgbm(cls, tree):
        ...

    @classmethod
    def from_xgboost_json(cls, tree):
        ...

    @classmethod
    def from_pyspark(cls, tree):
        ...

Nb. this would be a significant change, so if you agree then this is probably best kept for a future PR.


Best way to view Student Report PDF in VM?

I'm working on verifying the Student Report PDF in an Internet Explorer system. I'm having a problem with the VirtualBox VM (IE 11, Windows 7) where I get stuck in a circular loop and the VM refuses to display the PDF:

Are other folks getting stuck here as well? Or are you able to see PDFs in your VM?

Hmmm, I use VMWare Fusion with Windows 10. IE11 prompts me to open or save the download. Both work properly. Unfortunately VMWare Fusion isn't free.


Review provisioning script

Check out our quickstart provisioning section azure-ml-federated-learning/quickstart.md at release-sdkv2-iteration-03 · Azure-Samples/azure-ml-federated-learning (github.com)
Review the provisioning script called vnet_publicip_sandbox_setup.bicep

At this point I think we can consider this one closed.


Proper else clause invoke #1482

Killed build given comment above

@ljacomet what else we can do? Can we throw exception to bring down the server. The only way on passive entity is to log the exception. The only other stuff you can do is to log at other places, but that does not change anything in design, other than refactoring the code.

@ljacomet , ca we discuss this ?

Fix will be part of #1657


drop old value in insert_resource_by_id if exists

Objective
While trying out the lint unsafe_op_in_unsafe_fn I noticed that insert_resource_by_id didn't drop the old value if it already existed, and reimplemented Column::replace manually for no apparent reason.
Solution

use Column::replace and add a test expecting the correct drop count

Changelog

World::insert_resource_by_id will now correctly drop the old resource value, if one already existed

bors r+

@jakobhellermann you'll need to update this PR to reflect the new explicit #[derive(Resource)] requirement.

bors r+


Add note about readthedocs build failing to docs

https://github.com/spatialaudio/nbsphinx/issues/121

Rendered: https://nbsphinx--534.org.readthedocs.build/en/534/installation.html#Jupyter-Kernel

Thanks for the comments! Let me know if you have any other suggestions.

Thanks a lot!


add UI to subscribe to company & field

Added checkboxes to subscribe to different companies and technical interests
TODO:
Enhancement of UI
modularise the individual checkboxes component.

solves issues #4


[Boosted vs Brand stencils] stepped process

Text is not centered in Boosted.
Stencil

Boosted

done

ok for me https://boosted.netlify.com/docs/4.3/components/stepbar/#mobile-stepbar


Resent config if status reports hash empty

What this PR does / why we need it:
Bumps the Kong version to 2.8, the first version that supports this.
Resends configuration when the proxy instance reports its initial, no config present hash.
Adds tests to verify config recovers after a crash. Fixes a bug where we trusted the standard proxy 404 response when verifying Ingresses due to an improperly-bounded if.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #2107
Special notes for your reviewer:
Draft pending a go-kong release.
PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[ ] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

Initial E2E run ran this PR's test successfully, but failed on another existing test due to it not actually deploying an Ingress. Second run after fixing that: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/2018941298


soc: power: npcx: solve interrupt storm caused by host access.

This CL solves the interrupt storm caused by host access after
system boot to S0.
Signed-off-by: Mulin Chao<EMAIL_ADDRESS>

Solve interrupt storm issue caused by host access after system boot to S0. Need more time to pass stress test.

Passed the verification on volteer with PR32776, CL2721322, and CL2738500.
Ready for code review now.


Nothing happens and nothing appear

ruby 3.2.3
rails <IP_ADDRESS>
rails-footnotes  7.1.0
rails_footnotes.rb
Footnotes.setup do |f|
f.enabled = Rails.env.development?
end if defined?(Footnotes) && Footnotes.respond_to?(:setup)
I start app in development mode, and nothing happens and nothing appears(
I tried add div in layout with id="footnotes_holder"
but it empty always(
There are no errors, but nothing happens.

At least in my case that was because I am using Puma with threads. I'm not sure why, but this piece of code uses thread-locale-storage members to enable footnotes:
https://github.com/indirect/rails-footnotes/blob/f46e14cc30a885961dc749c3b140750783997626/lib/rails-footnotes.rb#L11-L13
Changing thread_mattr_accessor to mattr_accessor fixed it for me.
I am far from a Ruby export, but this monkey-patch in config/initializers/rails_footnotes.rb worked for me:
module Footnotes
  # the original implementation uses thread_mattr_accessor which doesn't work well with puma.
  # puma creates multiple threads and each of them has a different value for the same variable.
  # Footnotes.setup below only happens on the main thread and the value is NOT shared.
  # this code below is a workaround to make it work with puma.
  mattr_accessor :before_hooks, default: []
  mattr_accessor :after_hooks, default: []
  mattr_accessor :enabled, default: false
end

Footnotes.setup do |f|
  f.enabled = Rails.env.development?
end


Clarify + Gateway

Make embedded fcm docs better?
Improve NextPush docs (taken from UP-NextPush/android#34 ), add troubleshooting page (troubleshooting page could use some help)
Add gateway docs (to replace https://github.com/UnifiedPush/contrib/tree/main/gateways) (what do you think about deprecating (archiving) the contrib repo @p1gp1g ?)

Hey @p1gp1g can you check this out


Use go-git instead of using git via shell

I think it'll be better if we use go-git instead of using git via executing it ourselves.

Because currently, it's a bit messy and immature.


[fix] choose other site page for urgency layout preview

Coverage decreased (-0.05%) to 79.505% when pulling abdfe614627e8533aa1c7e2ec9a5a72f8de01d99 on sunny4381:fixes/urgency-layout-preview into bd731ee043bdf755b7c116fda77d326079459886 on shirasagi:master.


Feature generated docs

Description
Remake of https://github.com/ExCALIBUR-NEPTUNE/NESO/pull/117 with branch name changed.
Adds Sphinx + Doxygen gh-pages website.
Fixes:
Creates starting point for docs and api docs.
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)
Requires documentation updates

Testing
GH script is a copy of the NESO-Particles one. Ran the makefiles - they produced a website locally.

Does it need
    # Grant GITHUB_TOKEN the permissions required to make a Pages deployment
    permissions:
      pages: write      # to deploy to Pages
      id-token: write   # to verify the deployment originates from an appropriate source

from https://github.com/actions/deploy-pages

Seems to work, need to do s/feature-generated-docs/main/g before merging.


feat-sschaos rebase main

Codecov Report

Merging #307 (ebeafe9) into main (46be6a7) will decrease coverage by 13.31%.
The diff coverage is 49.06%.

@@             Coverage Diff             @@
##             main     #307       +/-   ##
===========================================
- Coverage   62.36%   49.06%   -13.31%
===========================================
  Files           2        8        +6
  Lines         279      856      +577
===========================================
+ Hits          174      420      +246
- Misses        103      368      +265
- Partials        2       68       +66

Impacted Files
Coverage Δ

pitr/cli/internal/pkg/shardingsphere-proxy.go
0.00% <0.00%> (ø)

pitr/cli/internal/pkg/local-storage.go
42.73% <42.73%> (ø)

pitr/cli/internal/cmd/restore.go
44.58% <44.58%> (ø)

pitr/cli/internal/cmd/show.go
56.09% <56.09%> (ø)

pitr/cli/internal/cmd/backup.go
58.87% <58.87%> (ø)

pitr/cli/internal/pkg/agent-server.go
72.54% <72.54%> (ø)

pitr/cli/pkg/gsutil/conn.go
76.47% <76.47%> (ø)

pitr/cli/pkg/stringutil/rand_string.go
91.30% <91.30%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


DOC/DX/MAINT: update core-dev guide

Reference issue
None
What does this implement/fix?
Some minor updates to the core-dev guide. Some outdated things, some typos and a few additions.

The reversion caused by gh-20227 has shown that adding a list of modules which we vendor (but aren't git submodules) would be useful.

thanks Tyler, I'll make the tweaks here and open up issues for follow-ups at some point in the coming days

Oops I didn't see that you replied already. Sorry about that.


KAFKA-12782: Fix Javadocs generation by upgrading JDK

This, upgrades JDK to version 15 for the docs generation, this way we
can circumvent bug https://bugs.openjdk.java.net/browse/JDK-8215291
present in JDK11
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Hi, @ijuma ready for you to review

An easy way to test this locally, is to search a Kafka class that contains a Javadoc link to a Standard Java Class.
For example, searching for KafkaFuture and then clicking on Throwable. Both search click and Throwable click should work.

We'll hopefully switch to JDK 16 before the 3.0 release.

Thanks @ijuma for the review! The upgrade to JDK 16 is this one https://github.com/apache/kafka/pull/10415 , right?

@jlprat See https://github.com/apache/kafka/pull/10702#issuecomment-841663450 for additional things that need to be fixed.


Consider hiding links to Studio on mobile devices?

We just noticed that on iOS and Android, clicking on the "select files" of the video uploader shows an option to record a video right there. It's also possible to cut the video before uploading (proper cutting, not just sending cut timestamps to Opencast, like Studio does). On Android, it doesn't seem to depend on the browser. On iOS it certainly doesn't.

Adding to that, capturing the screen is still not supported on mobile devices and I don't expect it to change anytime soon.
Which begs the question... what purpose does Studio serve on mobile devices? All it can do is record the phones camera and upload it to Opencast. Which is possible via Tobira in combination with the mobile operating system already. Bringing up the native camera app is also better than the custom recording interface we have in Studio (also regarding cutting and encoding).
I only see two small reasons for Studio:

You can pause during recording (which was not possible on iOS at least).
Studio can try to ask the browser to use a video format that Opencast understands. We have less control via the uploader route I think.

But these are not majorreasons.
So maybe we should think about hiding the Studio link on mobile devices? Or have an explanation pop up saying that users should rather use the uploader? (To be clear: this is only for mobile devices. For all other devices, Studio obviously still has lots of uses.)

Don't hide but grey it out (maybe with an alternative text "This feature is not available on your device."), otherwise people will ask where it is.


How to change default Port SMTP port to 587 from 25 ?

Hello,
I am trying to build a mail server in GCP. As GCP has port 25 blocked I want to use port 587 to send out emails.
I have updated the port in postal.yml and restarted postal but still, it listens to port 25.
I have also added a firewall rule to allow port 587. But still no luck.
I have attached the screenshots.
Port 587 is open : https://prnt.sc/tjdoni
Postal Port: https://prnt.sc/tjdoyq

You may be able to get your Postal to receive email on multiple ports (have a look at https://github.com/postalhq/postal/issues/565) but if your Postal is unable to communicate to other servers on port 25 then you may not be able to resolve this.

I use for this NAT.

@dragoangel
Have you tried running the SMTP server on GCP?
Without Gsuite.

@watchjobco I doesn't think this is correct place to discuss stuff like hosting. This isn't Postal related. And just to answer your question: I doesn't have expirience in GCP.


Catch error after await

Hello!! Is there a way to detect when is an error after an await?
In this example code (console project) the line apias.WriteLine fails silently:
internal class Program{
        static void Main(string[] args)
        {
            TaskCompletionSource<string> taskCompletionSource = new TaskCompletionSource<string>();

            var flags = V8ScriptEngineFlags.EnableTaskPromiseConversion | V8ScriptEngineFlags.HideHostExceptions |
                V8ScriptEngineFlags.EnableStringifyEnhancements | V8ScriptEngineFlags.EnableDateTimeConversion
                | V8ScriptEngineFlags.DisableGlobalMembers;

            V8ScriptEngine engine;

            engine = new V8ScriptEngine(flags);
            engine.EnableRuntimeInterruptPropagation = true;
            engine.SuppressExtensionMethodEnumeration = true;

            engine.AddHostObject("api", new API(taskCompletionSource));
            engine.Script.done = new ManualResetEventSlim();
            var code = @"
            async function main() {
                api.WriteLine('before await');
                var inputFromHost = await api.GetInputFromHost();
                api.WriteLine('after await');
                apias.WriteLine(inputFromHost); //this line fails silently
                done.Set();
            }

            main();
";

            engine.Execute(code);

            taskCompletionSource.SetResult("input from host");

            engine.Script.done.Wait();
            Console.WriteLine("Script finished");
            Console.ReadLine();
        }
    }

    public class API
    {
        TaskCompletionSource<string> taskCompletionSource;

        public API(TaskCompletionSource<string> taskCompletionSource)
        {
            this.taskCompletionSource = taskCompletionSource;
        }

        public Task<string> GetInputFromHost()
        {
            return taskCompletionSource.Task;
        }

        public void WriteLine(string data)
        {
            Console.WriteLine(data);
        }
    }

I´m doing something wrong or this is a bug?
Tested on Microsoft.ClearScript.V8.Native.win-x64 v7.3.5

Hi @dementcore,
The indicated line does fail – note that the script never sets the done event – but because main is an async function, V8 processes the failure by rejecting the promise that tracks its execution.
Your script code ends with a call to main. That call returns a promise, and because you're using task-promise interop, the host gets a task that it can use to discover the failure easily. Instead of this:
engine.Execute(code);

You can do something like this:
((Task)engine.Evaluate(code)).ContinueWith(task => {
    if (task.IsFaulted) {
        Console.WriteLine(task.Exception);
    }
});

Or, in a managed async method, you could use simply await the returned task within a try-catch block.
Good luck!

Hi @ClearScriptLib!!
Works like a charm.
Thanks a lot for your quick answer and for this great library!!
Best regards


How to access the media?

with tweepy i can get a json dict has a media url
like 'https://twitter.com/twitter/statuses/951433614029475844'
but how can i access the media?

Twitter provides the media in a Tweet using an Entities object.
You would access the Media object in Tweepy using a Status/Tweet object with something like status.entities["media"][0].
You can then use the Media object to get its URL, e.g. status.entities["media"][0]["media_url"] or status.entities["media"][0]["media_url_https"].
This is what Twitter's API provides and what you can access through Tweepy, and you can go to that URL to access the media. If you're asking about how to programmatically access the media itself, you can use the given URL and a library like requests, but that's currently outside the scope of this library.
Note, for videos and GIFs, the Media object only provides the thumbnail in the Entities object.
For those media types, you'll have to use the Extended Entities object to get the URL for the video or GIF.
You would access it in Tweepy using a Status object with something like status.extended_entities["media"][0]["video_info"]["variants"][0]["url"].
For more information, see the linked Twitter API documentation.

ok


Add missed quote

name: :memo: Documentation Fix
about: Fixing a problem in an existing docs page
Checklist

[ ] Is there an existing issue for this PR?

link issue here

[ ] Have the files been linted and formatted?

What docs page needs to be fixed?

Section: Fetching Data with createAsyncThunk
Page: Redux Essentials, Part 5: Async Logic and Data Fetching

What is the problem?
The missed opening quote in action name
What changes does this PR make to fix the problem?
Added missed opening quote

Thanks!


feat: allow HTTPS for local APIs and Http Proxies

Enabled using nitric start --https-preview

Looks good just one change.


Duplicate html tag in slide box

The slide box html tag is duplicated for the time .
Removed the duplicated html and committed the changes

Thanks for the contribution, but the times aren't duplicated, one's the event start time and one's the end time.

Oh. Sorry. Then add a condition (vm.calendarConfig.displayEventStartTimes) which you have used earlier. So that the unwanted 00 won't be available to the view.

I think the best way to go is just wrap the dates in separate spans with css classes which you can then just target with CSS and set display: none; to true


Jenkins please retry a build

Jenkins please retry a build

Jenkins please retry a build


400 error

I try to update but nothing, i tried to restart my pc and still the same
My discord: MrItachiUchiha#4079
IgActionSpamError: POST /api/v1/friendships/create/47392323578/ - 400 Bad Request; feedback_required
at Request.handleResponseError (C:\Users\Hello\Desktop\instabot\node_modules\instagram-private-api\src\core\request.ts:146:14)
at Request.send (C:\Users\Hello\Desktop\instabot\node_modules\instagram-private-api\src\core\request.ts:83:24)
at FriendshipRepository.change (C:\Users\Hello\Desktop\instabot\node_modules\instagram-private-api\src\repositories\friendship.repository.ts:59:22)
[ERROR] 21:08:28 IgActionSpamError: POST /api/v1/friendships/create/47392323578/ - 400 Bad Request; feedback_required

i think i that i need to wait 30 min i saw at the end [ERROR] 21:08:28 IgActionSpamError
i will try tommrow again if it faileds i will leave this post , but if it workes i will still leave ,

soo bad news nothing:
IgActionSpamError: POST /api/v1/friendships/create/47392323578/ - 400 Bad Request; feedback_required
at Request.handleResponseError (C:\Users\Hello\Desktop\instabot\node_modules\instagram-private-api\src\core\request.ts:146:14)
at Request.send (C:\Users\Hello\Desktop\instabot\node_modules\instagram-private-api\src\core\request.ts:83:24)
at FriendshipRepository.change (C:\Users\Hello\Desktop\instabot\node_modules\instagram-private-api\src\repositories\friendship.repository.ts:59:22)
[ERROR] 07:59:46 IgActionSpamError: POST /api/v1/friendships/create/47392323578/ - 400 Bad Request; feedback_required

Were you able to resolve the error?

no

There are multiple feedback_required issues here.
Example search.


layer-based background removal

Is your feature request related to a problem? Please describe.
it is absolutely not
Describe the solution you'd like
so like when i was talking about difference globalcompositeoperation and failing at it in photoshop, i've since discovered what i meant was "background subtraction" and i still kinda think that'd be a nifty feature, like c'mon
no actually describe it dummy
oh uh so like if an in/outpaint dream or maybe even txt2img is requested with the "subtract background" option ticked, the following should occur:

all currently visible layers in the bounding box should be sampled to a new canvas or image
the dream is dreamed
the user approves a dreamed image
the dream image has the magic done to it from the aforementioned article against that new canvas/layer from step 1ish, has the identical pixels from the currently visible layers removed, and is placed onto a new layer of its own

the more i think about this, the more it sounds like it'll ONLY be useful for img2img because, uh, most people probably don't want a giant chunk of the "background" automagically smooshed into their new detail layer...
Describe alternatives you've considered
well i guess painstakingly erasing identical pixels would work if i wasn't impatient?
Additional context
i will 100% try and almost certainly fail to implement something like this myself, but uh, ahem don't let that stop anyone else from showing me who's boss ;)
priority
literally the lowest possible; like if there's an errant apostrophe in a readme 2 versions ago that's probably more important

I'll leave this one to you, then!

i didn't forget about this i swear
https://github.com/zero01101/openOutpaint/commit/02bf04c25734ae4156b637eda0b1cd5cc6a3d568
it... kinda works?  not great with img2img and very bad with sketch tool lmao
bgremove.webm

https://github.com/zero01101/openOutpaint/wiki/Manual#dream and scroll down a bit?
janky but exists now


bump react peer dependency

Since #83 it seems react-anything-sortable works fine with react 16. Tests also pass when forced to run with react 16.

I know the repo is marked "INACTIVE", but is there any chance of this getting merged?

sure, sorry for kept you waiting for this

Thanks @jasonslyvia!

Plan to release to npm?

1.7.4 it is, sorry the delay.

Thanks again @jasonslyvia, no worries


vips_get_tile_size missing

To reduce memory usage and improve performance we did some tests with sequential mode read, from our tests in looks promising. However we're missing 1 function that is in libvips and not in the PHP binding:

vips_get_tile_size (some operations needs a tilecache to prevent over-computation)

General question:
Sequential read mode does not work with rotate, sharpen, gaussblur and our trim function. If we have to deal with these operations we force the access mode to VIPS_ACCESS_RANDOM, do you recommend this? I was not sure if a tilecache fixes this.

I'm on holiday this week, I'll look into this when I get back.
On Sun, 12 Feb 2017 at 20:30, Kleis Auke Wolthuizen <
<EMAIL_ADDRESS>wrote:

To reduce memory usage and improve performance we did some tests with sequential
mode read, from our tests in looks promising. However we're missing 1
function that is in libvips and not in the PHP binding:

vips_get_tile_size
http://www.vips.ecs.soton.ac.uk/supported/current/doc/html/libvips/VipsThreadState.html#vips-get-tile-size
(some operations needs a tilecache to prevent over-computation)

General question:
Sequential read mode does not work with rotate, sharpen, gaussblur and
our trim function. If we have to deal with these operations we force the
access mode to VIPS_ACCESS_RANDOM, do you recommend this? I was not sure
if a tilecache fixes this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jcupitt/php-vips/issues/33, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjc6-7Udh-Tr1a8VnekXmEGaUsRzjUEks5rb126gaJpZM4L-lgJ
.

There's no hurry, have a great holiday!

Hi again, rotate needs full random access, but sharpen/blur/crop should work with sequential. For example:
#!/usr/bin/env php
<?php

require __DIR__ . '/vendor/autoload.php';

use Jcupitt\Vips;

$image = Vips\Image::newFromFile($argv[1], ['access' => 'sequential']);
$image = $image->gaussblur(4);
$image->writeToFile($argv[2]);

There are two sequential modes. The regular seq mode (as above) keeps a buffer of a few 100 lines behind the processing point so that operations can refer backwards. This is how blur and sharopen are able to work.
There's also sequential-unbuffered, which keeps no history at all. This will only work for operations which do absolutely no referring back, such as crop / left-right flip, invert etc.
Why do you need get_tile_size()? I think just setting the access mode should be enough.

I've made a sample script which occasionally fails with sequential mode read + resize + blur. See: https://gist.github.com/kleisauke/32b8b19263ab32d89ed44d4022afef89
(I removed the premultiply steps because the test image has no transparency)
For the test image: https://rbx.weserv.nl/lichtenstein.jpg
This scripts fails sometimes with this warning:
2017/02/19 12:28:14 [error] 16900#16900: *121711 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Jcupitt\Vips\Exception: VipsJpeg: out of order read at line 1376
 in /var/www/t0.nl/vendor/jcupitt/vips/src/Image.php:635
Stack trace:
#0 /var/www/t0.nl/vendor/jcupitt/vips/src/Image.php(756): Jcupitt\Vips\Image::errorVips()
#1 /var/www/t0.nl/public_html/test.php(125): Jcupitt\Vips\Image->writeToBuffer('.jpg')
#2 {main}
  thrown in /var/www/t0.nl/vendor/jcupitt/vips/src/Image.php on line 635" while reading response header from upstream, client: 2001:610:600:850f:f901:92b5:6e3b:734b, server: t0.nl, request: "GET /test.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm/php-fpm.sock:", host: "t0.nl"
2017/02/19 12:28:15 [error] 16900#16900: *121711 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Jcupitt\Vips\Exception: VipsJpeg: out of order read at line 1528
 in /var/www/t0.nl/vendor/jcupitt/vips/src/Image.php:635
Stack trace:
#0 /var/www/t0.nl/vendor/jcupitt/vips/src/Image.php(756): Jcupitt\Vips\Image::errorVips()
#1 /var/www/t0.nl/public_html/test.php(125): Jcupitt\Vips\Image->writeToBuffer('.jpg')
#2 {main}
  thrown in /var/www/t0.nl/vendor/jcupitt/vips/src/Image.php on line 635" while reading response header from upstream, client: 2001:610:600:850f:f901:92b5:6e3b:734b, server: t0.nl, request: "GET /test.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm/php-fpm.sock:", host: "t0.nl"

For a live demo: http://t0.nl/test.php (just hit F5 and you'll see occasionally HTTP 500 errors)
I think I will need a tile cache at line 85-86.

Ah OK, yes gaussblur(4) is a pretty large radius:
$ vips gaussblur k2.jpg x.jpg 4 --vips-info
VIPS-INFO: gaussblur mask width 15
VIPS-INFO: using vector path
VIPS-INFO: using vector path

So it'll need 15 scanlines to compute the blur, then if you've previously shrunk by x5 (for example), you need 15 * 5, or 75 lines from the input.
I would try adding a tilecache just before the blur. Set the tile width to the image width, the tile height to 1, and maxtiles to the number of lines you want it to keep. Perhaps 30?  Set threaded to TRUE and access to sequential.
If you don't mind tying yourself to libvips 8.5, use thumbnail, instead of shrink and reduce. it'll be much faster.

The resize logic is based on the sharp library (that library uses a tile cache in the resize function, see this and this). They are  also investigating adding a tile cache before some operations, I'll link it for further reference: https://github.com/lovell/sharp/issues/709
So if I understand correctly the vips_get_tile_size is not needed to calculate the scanlines count of a blur operation; the scanlines count of the blur operation is the mask width (15 in this case) multiplied by 2. I'll do some tests with adding a tile cache before the blur operation.
I’ve considered vips_thumbnail but it’s not possible to implement it in our current setting (correct me if I'm wrong):

We limit the image size (width x height) what’s processed through our image proxy. The check takes places after Image::newFromFile. If it exceeded our limit (71000000) an exception is called and the user is unable to process the image. With vips_thumbnail the image is shrunk on read, we never know what the original dimensions of the image were. (Maybe this is fixable with Image::newFromFile -> $image->writeToBuffer and then vips_thumbnail_buffer).
Our users can define an exact crop position using a focal point (this is defined using two offset percentages). The crop method of vips_thumbnail is always center-center
It's currently not possible with vips_thumbnail to fit the image constraining dimensions exactly; ignoring the aspect ratio.
Letterboxing (embed); not sure if this should incorporate in vips_thumbnail (this can easily be fixed afterwards)

Hi again, you can get the image size very quickly with newFromFile. It won't read any pixels until they are needed, it just reads the metadata. So I would read out the dimensions, and then decide whether to allow thumbnail to run.
You're right that the crop in thumbnail is always centre, and that it always maintains the aspect ratio.
You could steal some of the shrink-on-load logic from thumbnail. It can give a very dramatic speedup for many image formats.

Thanks for the tip about shrink-on-load. I've just implemented it and it looks like our images are now loading faster on our test environment. 👍
Is there another way to get/calculate the buffer height in scanlines (scanline count)? I'm trying to implement the logic here in our resize function.

Ooop, sorry for the pause.
I'd use linecache instead, it does this for you internally. You want threaded mode, and sequential access.
http://www.vips.ecs.soton.ac.uk/supported/current/doc/html/libvips/libvips-conversion.html#vips-linecache

I will do some experiments with vips_linecache ($image->linecache()) at the resize, sharpen and blur operation (need only to find out how many scanline(s) it will need for tile_height). Thanks again!
Outside the scope of this issue, but a function that I'm missing is vips_foreign_find_load. I'll need it to determine the image format before the Image::newFromFile operation to pass the correct options.
For example, I've just implemented a page option to let the user decide which page he wants (useful for PDFs, TIFFs, and multi-size ICOs). If a user decides to use this function for a JPEG (or any other loader that doesn't support the page property) it will fail: Message: jpegload: no property named 'page'.
This is fixable if we call Image::newFromFile first without options and then call $image->get('vips-loader') to see which loader it has been loaded and then call again Image::newFromFile with the correct options. But this feels odd.. :-(

@jcupitt Is there a method to clear the whole linecache (I tried Config::cacheSetMax(0); and Config::cacheSetMaxFiles(0);)? It looks like after I had enabled the linecache that our trim function is broken; it only trims the height and not the width. The weird thing here is that I've forced the access to random if we’re trimming.
See for the wrong trimmed image here and for the debug log here. From the debug log I can see that the ->profile() is returning always width 1 .

I'm going to close this issue. After testing with linecache I'm not getting any out of order read errors anymore. (Thus the vips_get_tile_size is not needed anymore). Not sure if linecache is needed anymore when libvips 8.5 is released (because of the new sequential mode).
Sorry for the last 2 messages (it's too offtopic). I will create separate issues to track the trim-problem (looks like the particular image is way too far optimized which breaks vips_profile()) and the vips_foreign_find_load enhancement.


Juni::Db

Project Abstract
https://github.com/w3f/Grants-Program/pull/466
For which grant level are you applying?

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $50,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.13 out of 17 committers have signed the CLA.:white_check_mark: alxs:white_check_mark: semuelle:white_check_mark: Noc2:white_check_mark: wuminzhe:white_check_mark: nschwermann:white_check_mark: amiyatulu:white_check_mark: wstrametz:white_check_mark: Daniel-K-Ivanov:white_check_mark: MikeMS-sys:white_check_mark: rubyprotocol:white_check_mark: wliyongfeng:white_check_mark: jakehemmerle:white_check_mark: emailnjv:x: WannaM:x: xiaopangjun:x: mmagician:x: olanodYou have signed the CLA already but the status is still pending? Let us recheck it.


Remove /usr/bin/flatc from installation

When you try to install libtensorflow-lite and flatbuffers-dev, the /usr/bin/flatc file is in conflict and doesn't allow the rootfs to be created.
This resolved the build error for me, but I haven't been able to identify if anything in the c++ library depends on flatc.
If it does, would you need to make the jump to depending on flatbuffers instead of allowing tflite to build its own flat buffer?  I noticed the examples and tools depend on the flatbuffer recipe, but the c++ library does not.

Thank you.
I didn't realize that the libtensorflow-lite recipe installed flatc. I think it's correct to remove it too.


[FR]: Gather per-pass output logs

Proposal Summary
I plan to use Olive via its Python interface inside my tool. There is currently no easy solution to gather all stdout/stderr outputs related to specic passes. In other words, I have no way to get all the outputs produced by the second step of the pipeline.
Outputs produced by Olive can be gathered by registering custom handler for "olive" logger via:
olive_logger = logging.getLogger('olive')
olive_logger.addHandler(MyHandler())

But such an output will not contain all the logs produced by the pass itself - for example output produced by ONNXRuntime QDQQuantizer (used internally by OnnxStaticQuantization pass) will not be included.
What component(s) does this request affect?

[ ] OliveModels
[ ] OliveSystems
[ ] OliveEvaluator
[ ] Metrics
[ ] Engine
[X] Passes
[ ] Other

Hi @skywall , you can add onnxruntime log to output by setting log_severity_level to 1 in the config file. This default value is 3 so there is no onnxruntime log printed.

Closing. Feel free to reopen this if you have more questions.


move the Server implementation out of the header file

Cut in two commit, the first one is a straight copy of server.h to server.cc. Turns out GitHub only detects moves, not copies, but still, it lets you see which parts I changed, and which parts are straight cut-and-paste, in the second commit.
I'll squash them before merging, this is only to help reviewing.

Implementations in header files eh?

Well, it was a template before, so you kind of have to. :smiley:
But it isn't anymore, so let's not!

I'll do a little round of "include what you use", maybe add a few using statements, etc, but separately, to avoid noise in this PR (you get the nice big block cut-and-pasted without any modifications!).


Update NPM/Composer dependencies

Resolves #1056.
Notes:

Added astronomic/laravel-translatable
Removed dimsav/laravel-translatable
Removed nesbot/carbon
Updated other NPM / Composer packages

Comments here: https://github.com/GCTC-NTGC/TalentCloud/pull/1079

Replaced settings.json
sebastian/global-state is required for PHPUnit8, tightenco/parental is only used by app/Models/BackpackUser.php and I'm not entirely sure
Replaced class on app/Models/TeamCulture.php
Indentation in package.json should be fixed
The exception classes were incompatible after updating.


fonts must not be under css

fonts must be under public, otherwise patternfly will not be able to find them. Icons will not work.

Hey @pb82, some of the fonts must be under css/fonts, that's how patternfly-react.css is defined, ie:
url("./fonts/OpenSans-Regular-webfont.woff2")
Which is way they were moved in f88a0e under css and later they were divided between css/fonts and fonts.

@josemigallas hmm, i was having problems with the icons when they were located under css

Yes, that is my point, some must be under ./fonts (like the icons), and others are required under ./css/fonts.


(Vanilla bug) Trams spawn in the wrong depot when multiple disconnected depots available

Describe your idea
This is a vanilla issue that presents in an unmodded game, and was hoping TM:PE could fix it.

Build two separate tram networks, with separate depots.
Set up lines such that the first stop on one line is closer to the depot on the other.
Complete the lines; note that the trams never spawn and the depots give an error icon saying they "need to be connected to lines".

The game basically seems to be choosing what depots to spawn trams from based on direct distance, without checking if they're actually connected; which is obviously not ideal.
The issue especially seems to present if you have fairly long tram lines, with a depot on one end.
Oh, and I haven't tested this, but I imagine trolleybuses may have the same issue.
Screenshots?

The game basically seems to be choosing what depots to spawn trams from based on direct distance, without checking if they're actually connected; which is obviously not ideal.

How would you fix that then? To create path you have to select source building and target. Game has no additional logic for checking if vehicle can reach the stop from depot building or not and it applies to all depot building types which spawn vehicles to be used on PT line.
I strongly suggest reporting that problem on the forums anyways. https://forum.paradoxplaza.com/forum/forums/support-bug-reports.879/


For GL30 compatibility, use indexed lsans-15.png .

I don't know the specifics for why GL30 has a hard time with the Grayscale+Alpha color mode for PNGs. But, it doesn't seem to load that correctly, and does load Indexed color mode PNGs just fine, so switching to a (smaller) indexed-mode file should allow the default font to work on all GL versions. There's a tiny bit of lost detail, but this takes advantage of PNG's ability to have different alpha levels for every color in a palette, so there should still be a soft, not jagged, edge.

I believe the ones in the tests only need to be updated if they are grayscale+alpha and used in GL30 mode. I don't think that currently happens, but maybe?

I believe the ones in the tests only need to be updated if they are grayscale+alpha and used in GL30 mode. I don't think that currently happens, but maybe?

I think you can configure/choose the mode when running the Lwjgl3 tests. I don't know about the grayscale+alpha thing.

Is it OK if I merge my own PR? This has had 2 approvals for 3 days now. If there are other issues anyone has, this would be a good time to bring them up!

I approve because it fixes a problem. It seems unnecessary to me to avoid RGB PNGs here (the size difference is insignificant in the grand scheme) but I'm not too concerned with losing a few shades. Kindles are 4-bit grey, and text looks perfect on them.


Crash: connection refused <IP_ADDRESS>:80

coda_crash_report_2021-03-26_05-07-21.105937.tar.gz

{
  "timestamp": "2021-03-26 04:58:56.818685Z",
  "level": "Fatal",
  "source": {
    "module": "Init__Coda_run",
    "location": "File \"src/app/cli/src/init/coda_run.ml\", line 603, characters 2-26"
  },
  "message": "Unhandled top-level exception: $exn\nGenerating crash report",
  "metadata": {
    "exn": {
      "commit_id": "a8893ab6dd8a68171e7b99a5dc6b76940411350b",
      "sexp": [
        "monitor.ml.Error",
        [
          "Unix.Unix_error",
          "Connection refused",
          "connect",
          "<IP_ADDRESS>:80"
        ],
        [
          "Raised by primitive operation at file \"src/unix_syscalls.ml\", line 1046, characters 17-74",
          "Called from file \"src/deferred1.ml\", line 17, characters 40-45",
          "Called from file \"src/job_queue.ml\" (inlined), line 131, characters 2-5",
          "Called from file \"src/job_queue.ml\", line 171, characters 6-47",
          "Caught by monitor Tcp.close_sock_on_error"
        ]
      ],
      "backtrace": [
        "Raised at file \"src/tcp.ml\", line 79, characters 4-11",
        "Called from file \"src/deferred1.ml\", line 17, characters 40-45",
        "Called from file \"src/job_queue.ml\" (inlined), line 131, characters 2-5",
        "Called from file \"src/job_queue.ml\", line 171, characters 6-47"
      ]
    },
    "pid": 27877
  }
}

@jonagmon it looks like you've passed a local file to the --peer-list-url flag. Perhaps you meant to use the --peer-list-file flag instead?

Closing this one because of no activity for a long time and I hope that the most recent versions of Mina Daemon behave more stable for you.
Please feel free to report new issues should you face any.
Thank you.


Examples: Add files via upload

In honor of this PR: https://github.com/mavlink/MAVSDK-Python/pull/558
cc: @julianoes @afwilkin

Thanks @farhangnaderi, this worked. Let me know what you think about my changes, and make sure to test again.
I tried to run it but it just stalled for me.

Thanks for your time Julian. Tested and made some small changes, let me know if you are happy with it! :D

Nice, that looks good now. Does it work for you?

Yes Julian, tested on SITL:

Nice! Thanks!

Thanks a bunch for your help!


[🐞] qwikify$ in astrojs.

Which component is affected?
Qwik React
Describe the bug

Problem

when React Component used in Qwik, seems not hydration in astro.
even though, using only react component in astro works with client:loader.

Code

  "dependencies": {
    "@astrojs/react": "^3.0.7",
<EMAIL_ADDRESS>"^1.3.0",
<EMAIL_ADDRESS>"^0.5.0",
    "@qwikdev/astro": "^0.3.1",
    "@types/react": "^18.0.21",
    "@types/react-dom": "^18.0.6",
    "astro": "^4.0.3",
    "react": "^18.0.0",
    "react-dom": "^18.0.0"
  },

-- astro.config
import qwikdev from '@qwikdev/astro';
import react from "@astrojs/react";

export default defineConfig({
  integrations: [
    qwikdev({
      include: ['**/qwik/*']
    }),
    react({
      experimentalReactChildren: true,
      include: ['**/react/*'],
    }),
  ]
});

-- qwik
const FromReact = qwikify$(Test, { eagerness: 'hover' })

export default component$<Props>(({}) => {
  return (
    <FromReact />
  )
}) // will be <QwikContainsReactComponent />

-- react
/** @jsxImportSource react */

export default function FromReact() {
  const [count, setCount] = useState(0)

  return (
    <div>
      {count}
      <button onClick={() => setCount((prev) => prev + 1)}>button</button>
    </div>
  )
}

-- astro
  <FromReact client:idle /> //working
  <QwikContainsReactComponent /> //not (seems not hydration)

Reproduction
i cant find astro template for qwik
Steps to reproduce
No response
System Info
Windows, FireFox

Additional Information
No response

move to QwikDev/astro


[seata-java] optimize: only the inserted fields are checked

What would you like to be added:
refer: https://github.com/apache/incubator-seata/pull/3890
Why is this needed:

Please assign to me

@qingming

The purpose of this PR is to configure a switch to determine whether to ignore fields automatically populated by MySQL after the execution of insert SQL statements, such as the timestamp operation CURRENT_TIMESTAMP. When ONLY_CARE_UPDATE_COLUMNS is enabled, only the fields specified in the SQL insertion are concerned, ignoring the fields automatically generated by MySQL.


feat: use sidecar for ud containers [Breaking k8s < v1.29]

Use Sidecar to run ud containers, to make sure they will be started before and terminated after numa container.

@whynowy
Post this change new versions would not be working with <1.29 right?
Would we want to have a backward compatible version where we enable this with some config etc?
What do you think?

@whynowy Post this change new versions would not be working with <1.29 right? Would we want to have a backward compatible version where we enable this with some config etc? What do you think?

We don't care if no one uses k8s < 1.29, or anyone uses < 1.29 has a plan to upgrade.

@whynowy
Please add any container lifecycle timestamps observed for closing this?

@whynowy Please add any container lifecycle timestamps observed for closing this?

What does this mean?

@whynowy Please add any container lifecycle timestamps observed for closing this?

Init Containers:
  udsource:
    Container ID:   containerd://2b3b0cbc138f053ffe5bd1bbcf5d3a8c285fa88340e3672354a59ca7333f213e
    Image:          quay.io/numaio/numaflow-rs/simple-source:stable
    Image ID:       quay.io/numaio/numaflow-rs/simple-source@sha256:d7960273214db7536d5093d03b23a8bd466867f61ff347839a9ea6e2ac1db4f2
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Tue, 19 Nov 2024 17:29:34 -0800
    Ready:          True
    Restart Count:  0
    Liveness:       http-get https://:2469/sidecar-livez delay=30s timeout=30s period=60s #success=1 #failure=5
    Environment:
      NUMAFLOW_UD_CONTAINER_TYPE:  udsource
      NUMAFLOW_NAMESPACE:          numaflow-system (v1:metadata.namespace)
      NUMAFLOW_POD:                simple-mono-vertex-mv-0-2g90a (v1:metadata.name)
      NUMAFLOW_REPLICA:             (v1:metadata.annotations['numaflow.numaproj.io/replica'])
      NUMAFLOW_MONO_VERTEX_NAME:   simple-mono-vertex
      NUMAFLOW_CPU_LIMIT:          node allocatable (limits.cpu)
      NUMAFLOW_CPU_REQUEST:        0 (requests.cpu)
      NUMAFLOW_MEMORY_LIMIT:       node allocatable (limits.memory)
      NUMAFLOW_MEMORY_REQUEST:     0 (requests.memory)
    Mounts:
      /var/run/numaflow from var-run-numaflow (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hzwzb (ro)
  transformer:
    Container ID:   containerd://92cd9e3b5a9ff149d339e78606b674215ecb0f931f9f2e0cf65cd00340c924b7
    Image:          quay.io/numaio/numaflow-rs/source-transformer-now:stable
    Image ID:       quay.io/numaio/numaflow-rs/source-transformer-now@sha256:843a9cafb67eaeadb6468bf9bf7225b43b30c648d41b87222fb2a9ea8d2ffcd9
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Tue, 19 Nov 2024 17:29:35 -0800
    Ready:          True
    Restart Count:  0
    Liveness:       http-get https://:2469/sidecar-livez delay=30s timeout=30s period=60s #success=1 #failure=5
    Environment:
      NUMAFLOW_UD_CONTAINER_TYPE:  transformer
      NUMAFLOW_NAMESPACE:          numaflow-system (v1:metadata.namespace)
      NUMAFLOW_POD:                simple-mono-vertex-mv-0-2g90a (v1:metadata.name)
      NUMAFLOW_REPLICA:             (v1:metadata.annotations['numaflow.numaproj.io/replica'])
      NUMAFLOW_MONO_VERTEX_NAME:   simple-mono-vertex
      NUMAFLOW_CPU_LIMIT:          node allocatable (limits.cpu)
      NUMAFLOW_CPU_REQUEST:        0 (requests.cpu)
      NUMAFLOW_MEMORY_LIMIT:       node allocatable (limits.memory)
      NUMAFLOW_MEMORY_REQUEST:     0 (requests.memory)
    Mounts:
      /var/run/numaflow from var-run-numaflow (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hzwzb (ro)
  udsink:
    Container ID:   containerd://9a047a26c1bb12ca88eb825dbcd20673bb3988a62adbb77d668758968733aa57
    Image:          quay.io/numaio/numaflow-rs/sink-log:stable
    Image ID:       quay.io/numaio/numaflow-rs/sink-log@sha256:e6627f22b03152f5546d1d36ab7a01de2d39bb6f9d5fa2afd53b96b7f0fe0815
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Tue, 19 Nov 2024 17:29:36 -0800
    Ready:          True
    Restart Count:  0
    Liveness:       http-get https://:2469/sidecar-livez delay=30s timeout=30s period=60s #success=1 #failure=5
    Environment:
      NUMAFLOW_UD_CONTAINER_TYPE:  udsink
      NUMAFLOW_NAMESPACE:          numaflow-system (v1:metadata.namespace)
      NUMAFLOW_POD:                simple-mono-vertex-mv-0-2g90a (v1:metadata.name)
      NUMAFLOW_REPLICA:             (v1:metadata.annotations['numaflow.numaproj.io/replica'])
      NUMAFLOW_MONO_VERTEX_NAME:   simple-mono-vertex
      NUMAFLOW_CPU_LIMIT:          node allocatable (limits.cpu)
      NUMAFLOW_CPU_REQUEST:        0 (requests.cpu)
      NUMAFLOW_MEMORY_LIMIT:       node allocatable (limits.memory)
      NUMAFLOW_MEMORY_REQUEST:     0 (requests.memory)
    Mounts:
      /var/run/numaflow from var-run-numaflow (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hzwzb (ro)
Containers:
  numa:
    Container ID:  containerd://7934dff671f3609c79249880ad7eca9d508d5ab14aafbc302bd640a6a444e347
    Image:         quay.io/numaproj/numaflow:latest
    Image ID:      sha256:bbb682c0fb7a106919432d6a50acd9e1e77e84f26fbab5f1084d87df4776e88d
    Port:          2469/TCP
    Host Port:     0/TCP
    Command:
      /bin/numaflow-rs
    Args:
      --rust
    State:          Running
      Started:      Tue, 19 Nov 2024 17:29:37 -0800
    Ready:          True
    Restart Count:  0

@whynowy Thank you :D


Notifications: Timestamps are not adjusted to the local (browser) time

Please see an example below.

Started working on this issue

Create PR for this