Problem with QuickBuilder

I'm developing a behavior and used the QuickBuilder for the TestSuite. Well, out of a sudden it stopped working for me. The error message I get is the following:
Fatal error: Cannot redeclare class test\Base\ProductQuery in /private/var/folders/22/r4kt28011pn2pyx5wkgg_1gr0000gn/T/propelQuickBuild-2.0.0-dev-220ea8f62c/Product_ProductI18n.php on line 2508
That's the version where every file is munged into one. I checked the generated code and didn't find an error. I also used my behavior on a private test project and it worked fine (various files are generated then).
It's easy to test for yourself: clone + run phpunit in the project root -> https://github.com/gossi/propel-l10n-behavior

In your ProductTest::setUp() method write this:
if (!class_exists('\Product')) {
    $schema = <<<EOF
<database name="l10n_behavior" namespace="test">
	<table name="product">
		<column name="id" required="true" primaryKey="true" autoIncrement="true" type="INTEGER" />
		<column name="title" type="VARCHAR" required="true" />

		<behavior name="l10n">
			<parameter name="i18n_columns" value="title" />
		</behavior>
	</table>
</database>
EOF;
		$this->getBuilder($schema)->build();
}

........

QuickBuilder always includes the generated classes, so that after the first test, if you run QuickBuilder again you redeclare your model classes twice.

Thank you, I see what's causing the problem now. I guess if QuickBuilder is using include_once instead of include this will cause other tests to fail, because some models are generated over and over again but with different combinations in the propel testsuite?

@gossi using setUpBeforeClass instead setUp
I fixed a similar problem https://github.com/Big-Shark/Propel2/commit/758413522864c338c2522419302b59f442ec3da8

Wonderful, your help is much appreciated - thank you very much. Tests are running now. Propel will soon be enriched with a new behavior.


Clarify ownership responsibilities in the C API docs

When using the C API for the first time I found the documentation missing some important details.

Hi, this is my first PR for hyper, I may be doing some things incorrectly. Please read the commits one at a time. Thanks!

Thanks so much for the documentation improvements, these are great! ❤
It looks like the generate header file has some changes the CI doesn't like. Is it because the cbindgen you have is an older version? Or it could be something we need to fix in CI...

I had cbindgen 0.12.0 installed, and CI uses 0.25.0! I upgraded, which should fix the problem.


got memory leak when try to lifting up selectedFlatRows to parent component

Describe the bug (required)
Getting memory leak.
Provide an example via Codesandbox! (required)
https://codesandbox.io/s/priceless-sunset-fgywri
Steps To Reproduce (required)
Steps to reproduce the behavior:

Go to the codesandbox. see the console

Expected behavior (Recommended)
everything's fine

solved.
useEffect(() => {
    const selectedRows = selectedFlatRows.map(
      (selectedRow) => selectedRow.original
    );
    if (onSelectedRowsClicked !== undefined) {
      onSelectedRowsClicked(selectedRows);
    }
- }, [selectedFlatRows, onSelectedRowsClicked]);
+ }, [selectedFlatRows]);


v1.12 Backports 2023-07-10

[x] #26715 (@tklauser)

PRs skipped due to conflicts:

#26590 (@YutaroHayakawa)

Once this PR is merged, you can update the PR labels via:
for pr in 26715; do contrib/backporting/set-labels.py $pr done 1.12; done

or with
make add-labels BRANCH=v1.12 ISSUES=26715

marking as ready given that this relates just to the tests-l4lb.yaml workflow


compute/metadata: build is broken on GAE go1.4beta

Please see:

https://groups.google.com/forum/#!topic/google-appengine-go/WeO8KGx6O8c
https://code-review.googlesource.com/#/c/1670/3 (my comment)

Is this still an issue? https://code-review.googlesource.com/#/c/1780/ should have fixed it a while ago. Please re-open if necessary.


docs: add v0.3.5 release CHANGELOG notes

Description
Add the v0.3.5 CHANGELOG release notes to the CHANGELOG.
References

Review Checklist

[ ] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[ ] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Codecov Report
Base: 81.99% // Head: 81.92% // Decreases project coverage by -0.08% :warning:

Coverage data is based on head (8852d9a) compared to base (5c955be).
Patch coverage: 43.54% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #543      +/-   ##
==========================================
- Coverage   81.99%   81.92%   -0.08%
==========================================
  Files          89       88       -1
  Lines       14436    14368      -68
==========================================
- Hits        11837    11771      -66
- Misses       2188     2190       +2
+ Partials      411      407       -4

Impacted Files
Coverage Δ

cmd/run/flags.go
0.00% <0.00%> (ø)

pkg/server/test/list_objects.go
72.93% <ø> (+0.19%)
:arrow_up:

cmd/run/run.go
61.22% <45.94%> (-0.99%)
:arrow_down:

pkg/server/test/check.go
62.72% <50.00%> (+0.28%)
:arrow_up:

pkg/server/commands/check.go
40.00% <100.00%> (-0.16%)
:arrow_down:

pkg/server/commands/connected_objects.go
88.31% <100.00%> (-0.21%)
:arrow_down:

pkg/server/commands/list_objects.go
81.56% <100.00%> (+0.26%)
:arrow_up:

pkg/server/server.go
59.11% <100.00%> (+0.46%)
:arrow_up:

cmd/util/util.go
0.00% <0.00%> (-28.58%)
:arrow_down:

internal/middleware/logging.go
67.77% <0.00%> (-6.67%)
:arrow_down:

... and 3 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


How to reload captcha image with different numbers?

see my pull request here:
https://github.com/napa3um/node-captcha/pull/12
Basically, you can call
$("img").attr("src",$("img").attr("src") + "?somestring")
if you are using jquery.
but first you will have to make a small modification to captcha.js.

Simple reload image on client.


Could not find the rule in the search path

This is odd, I am running Arara 3.0 installed on Windows 10.
Trying to run a file with simple arara: pdflatex directive at the top, I keep getting the:
  __ _ _ __ __ _ _ __ __ _
 / _` | '__/ _` | '__/ _` |
| (_| | | | (_| | | | (_| |
 \__,_|_|  \__,_|_|  \__,_|

Uh-oh, I could not find the 'pdflatex' rule in the search path.
Could you take a look if the rule name is correct and if the rule
is accessible through the search path?

Error... I've added the arara dir to path, is there something else I must do?

This is indeed odd! How is arara installed in your system (TeX Live or standalone installer)?
When executed, arara finds its own path and determine the default rules location based on that information. It should work on 100% of the cases.
Could you list the content of the directory where arara.jar is located?
All the best! :wink:

Also, do you have any configuration file in your home directory? It is been a while since I dealt with an arara question, so I am a little rusty. :wink:

Ok the problem was ... fixed. I think it was an outdated miketex install.
Thanks!


React component not rendered correctly at table header

Describe the bug
I'm trying to render a react component at table header, not table cells.
It seems impossible
import { _ } from "gridjs-react";
const tableColumns = [
    {id: 'id', name: _(<button className={"py-2 px-4 border rounded-md text-white bg-blue-600"} onClick={() => alert('clicked!')}>Edit</button>)},
    {id: 'name', name: 'Name'},
]

<Grid
          columns={tableColumns}
          data=[[1,"hoge"], [2, "hoge"]
/>

this render only
<button class="py-2 px-4 border rounded-md text-white bg-blue-600">Edit</button>

There isn't onClick
If possible, I want to put some react component at header .
My use-case is "Select All button"

By rendering, do you mean that it won't show in the browser inspector? That's normal for React. I've tried the same example and the alert shows.

By rendering, do you mean that it won't show in the browser inspector? That's normal for React. I've tried the same example and the alert shows.

@UserSina thanks! you're right!
thank you for trying!

@UserSina thanks! you're right!
thank you for trying!


 With the help of ManyCam Pro, you can also add your voice to your videos by using the mic of your PC. Therefore, it has voice changer effects too, so if you don’t want people may get to know your voice, you can use the voice changer characteristics of ManyCam. ManyCam lets you add your videos on the internet for broadcasting. For better sound results, you can use ManyCam portable. It can record your voice with the best results.
Download Now

UPDATE Version DOWNLOAD
✔The Download Link Is Verified


Build error: ROCMHeaderWrapper not found after #1454

MIOpen build fails after #1454. Tried with vanilla ROCm 5.0 on two machines + rocm-cmake installed.
rocm-cmake installation/update:
$ cd ~/github
$ git clone https://github.com/RadeonOpenCompute/rocm-cmake
$ cd rocm-cmake
$ git checkout 4a1514850195360ce772182d34b6b5afd8f37253
$ mkdir build
$ cd build && cmake ..
$ sudo cmake --build . --target install
$ ls -l /opt/rocm/share/rocm/cmake
...
-rw-r--r-- 1 root root  5294 Mar 23 21:38 ROCMHeaderWrapper.cmake
...

MIOpen build:
atamazov@morpheus:~/github/MLOpen1/build/release.hip-clang$ CXX=/opt/rocm/llvm/bin/clang++ cmake -DBUILD_DEV=On -DCMAKE_BUILD_TYPE=release -DMIOPEN_USE_MLIR=Off ../..
...
CMake Error at CMakeLists.txt:61 (include):
  include could not find load file:

    ROCMHeaderWrapper

@junliume @pfultz2 @arvindcheru :red_circle: This seems to be a blocker issue for me.

Works on third machine... Maybe this is my local configuration issue. Closing until issue is clarified.

Works on third machine... Maybe this is my local configuration issue. Closing until issue is clarified.

@atamazov MIOpen dependency needs to be updated (rocm-cmake specifically). I've met this issue once and re-ran the dependency installation fixed it. Let me know if this issue persists on your end. :)

The reason was another, outdated, instance of rocm-cmake installed on my machine due to some reason, at /usr/local/share/rocm/cmake. Removal of it resolves the problem.

Need to reopen this issue due to break of backward compatibility:
@pfultz2 @arvindcheru please advice.
[Steps to reproduce]: pull any 5.0 docker and try to build MIOpen within it.

@junliume

pull any 5.0 docker and try to build MIOpen within it.

This is normal because 5.0 contains outdated dependencies (including rocm-cmake). Further releases will contain updated rocm-cmake because requirements.txt is updated in #1454.

we should remove or replace /opt/rocm/share/rocm/cmake but it needs to be documented...

The problem only affects developers who want to build fresh MIOpen with older ROCm releases, if they would like to skip the step described at https://github.com/ROCmSoftwarePlatform/MIOpen#installing-the-dependencies (as we usually do, BTW). They need to update rocm-cmake as shown in the issue description.
The users who follow the instructions won't encounter any problems. I think this ticket does not require any actions.

Thanks for comments/inputs @junliume , @atamazov.
As explained @atamazov in last comment, this dependency installation is done based on existing requirements.txt processing,  as per our last changes, we did addition of rocm-cmake also to it.
This was added, since the Wrapperfunction is only available from latest (0.7.3) releases of rocm-cmake.
Will try to understand whether we can handle existing rocm-cmake by any means while do this installation.

@junliume

pull any 5.0 docker and try to build MIOpen within it.

This is normal because 5.0 contains outdated dependencies (including rocm-cmake). Further releases will contain updated rocm-cmake because requirements.txt is updated in #1454.

we should remove or replace /opt/rocm/share/rocm/cmake but it needs to be documented...

The problem only affects developers who want to build fresh MIOpen with older ROCm releases, and only if they skip the step described at https://github.com/ROCmSoftwarePlatform/MIOpen#installing-the-dependencies (as we usually do, BTW). They need to update rocm-cmake as shown in the issue description.
The users who follow the instructions won't encounter any problems. I think this ticket does not require any actions.

@atamazov I ran the following script to install MIOpen, with the dependency installation:

cd /root && git clone -b develop https://github.com/ROCmSoftwarePlatform/MIOpen && cd MIOpen &&
mkdir -p install_dir && cmake -P install_deps.cmake --minimum --prefix /root/MIOpen/install_dir &&
mkdir -p build && cd build && export CXX=/opt/rocm/llvm/bin/clang++ &&
cmake -DMIOPEN_BACKEND=HIP -DCMAKE_PREFIX_PATH="/root/MIOpen/install_dir" ..

and still meet the above error, until I remove the /opt/rocm/share/rocm/cmake folder. It seems that -DCMAKE_PREFIX_PATH="/root/MIOpen/install_dir" is not taking proper priority over other default paths. Another approach I have tried is cmake -P install_deps.cmake --minimum without --prefix so that it is installed at /usr/local, but still the one at /opt/roc/ got picked up and it is the outdated one :(

One observation, currently build is done with rbuild for me where this issue is not see, it will do the dependency installation to the deps_hip directory and in turn will proceed with success build.
@pfultz2,
for now shall we add download like our previous version just an exception (for now) for rocm-cmake like we did https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1454/files/ef9930472b813515d1fd39db9b7dc24a8dd07989 in CMakeLists.txt.

I see. /opt/rocm/share/rocm/cmake takes precedence over CMAKE_PREFIX_PATH.

So /opt/rocm get preferred over the system path because cmake first searchs CMAKE_INSTALL_PREFIX, which is /opt/rocm.

One observation, currently build is done with rbuild for me where this issue is not see, it will do the dependency installation to the deps_hip directory and in turn will proceed with success build.

So we could update install_deps.cmake to use rbuild, I think it would be better, but I am not sure why it works over what we do currently. The difference here is that rbuild will set CMAKE_PREFIX_PATH, whereas with install_deps.cmake, users are relying on the dependencies being found in /usr/local. Either way, @atamazov seem to imply that CMAKE_PREFIX_PATH is not enough.
Also, it seems we list rocm-cmake in two different files(dev-requirements.txt and requirements.txt), which could be a problem in the future(right now we are lucky they are using the same version).

or now shall we add download like our previous version just an exception (for now) for rocm-cmake like we did

No, we should not download dependencies at cmake time. However, we could set the minimum rocm-cmake version, this can find a correct rocm-cmake when there are multiple versions to be found: find_package(ROCM 0.7.3 REQUIRED PATHS /opt/rocm). This might fix these issues.

So #1482 is a proposed fix.

Although rocm-cmake is installed, installing ROCm components still reports cmake errors (e.g. Unknown CMake command "rocm_package_setup_component).  Could you please comment how to troubleshoot the issue ?
rocm-cmake/jammy,now <IP_ADDRESS>400-72~22.04 amd64 [installed,automatic]
rocm-cmake built using CMake

Although rocm-cmake is installed, installing ROCm components still reports cmake errors (e.g. Unknown CMake command "rocm_package_setup_component). Could you please comment how to troubleshoot the issue ?
rocm-cmake/jammy,now <IP_ADDRESS>400-72~22.04 amd64 [installed,automatic] rocm-cmake built using CMake

Sorry for the delay in responding,
I was unable to get same observation when I tried on recent build. Would like to know more details on environments/steps followed to get the observation shared. would appreciate opening another ticket if it is not related this issue with more details on the environment/source used like
Which version (is it a particular version onwards) of MIOpen this observation is found.
Would you mind sharing the build steps used, is it provided with provided Prefix path used

@jinz2014

what is your rocm version?
you have to use rocm-cmake from rocm, see https://github.com/ROCmSoftwarePlatform/MIOpen/issues/1473#issuecomment-1076741961

Thank you for your replies. Please ignore my issue.


Auth fail

I've done the steps and Auth Fail appears when I run hook.php

You didn't setup successfully.

if I set the webhook separately, telegram shows message of set correctly and the control panel of lineapp also.
But it still does not work because I think the chat to follow is badly written.
If I run hook from the browser I get an error in the authentication.
Is it possible to contact you by telegram? my nick is @ildenet


Add Show in FileSystem right click option to SpriteFrames

This would close https://github.com/godotengine/godot-proposals/issues/11332
https://github.com/user-attachments/assets/c03865d3-99a3-4768-ba98-b6f2bdba8dfc

We have a dedicated icon for showing in filesystem.  You could set it in the menu.

Ah nice! I didn't realise that. Added it now.


Remove 'code' tag from calculating reading time

calculateReadingTime function is calculating words in the post and it's including the 'code' blocks.

Hey @rsneh , Which file is this function in?

Hey @rsneh , Which file is this function in?

Hey @rsneh , Which file is this function in?

Hi @Siddharth1010 👋🏼
This function is in utils/helpers.js

Hey @rsneh , Which file is this function in?

Hi @Siddharth1010 👋🏼
This function is in utils/helpers.js

@rsneh Will this be alright?

@rsneh Will this be alright?

 I think a better approach for this issue will be changing the PostReadingTime component.
I'll rename this issue and add some description as well.
Sorry about that.

I confused you with this solution. I think a better approach for this issue will be changing the PostReadingTime component.
I'll rename this issue and add some description as well.
Sorry about that.

I confused you with this solution. I think a better approach for this issue will be changing the PostReadingTime component.
I'll rename this issue and add some description as well.
Sorry about that.

So basically I can just paste what I have done in the PostReadingTime file right?

I confused you with this solution. I think a better approach for this issue will be changing the PostReadingTime component.
I'll rename this issue and add some description as well.
Sorry about that.

So basically I can just paste what I have done in the PostReadingTime file right?

I confused you with this solution. I think a better approach for this issue will be changing the PostReadingTime component.
I'll rename this issue and add some description as well.
Sorry about that.

So basically I can just paste what I have done in the PostReadingTime file right?

Not exactly.
You can see in PostReadingTime.js line 5, there is already a reduce function to push all words.
You need to add a condition to check if this block is "code" to ignore it and continue with the loop.

I confused you with this solution. I think a better approach for this issue will be changing the PostReadingTime component.
I'll rename this issue and add some description as well.
Sorry about that.

So basically I can just paste what I have done in the PostReadingTime file right?

Not exactly.
You can see in PostReadingTime.js line 5, there is already a reduce function to push all words.
You need to add a condition to check if this block is "code" to ignore it and continue with the loop.

I think I get it now. Could you tell me what the variable "block" is exactly?

I think I get it now. Could you tell me what the variable "block" is exactly?

I think I get it now. Could you tell me what the variable "block" is exactly?

Sure. But I think it will be best for you to install the repo on your local and explore it yourself.
Anyway, you can see the "initialBlocks" variable with a single block in context/PostContext.js line 5.

I think I get it now. Could you tell me what the variable "block" is exactly?

Sure. But I think it will be best for you to install the repo on your local and explore it yourself.
Anyway, you can see the "initialBlocks" variable with a single block in context/PostContext.js line 5.

Ah thanks for that. Will this work?

Ah thanks for that. Will this work?

Ah thanks for that. Will this work?

Not exactly.
Reduce has to return a value, so you need to change it to something like:
const words = blocks.reduce((words, block) => {
  if (block.tag !== "code") block.html.trim().split(' ').forEach(word => word && words.push(word))
  return words
}, [])

Ah thanks for that. Will this work?

Not exactly.
Reduce has to return a value, so you need to change it to something like:
const words = blocks.reduce((words, block) => {
  if (block.tag !== "code") block.html.trim().split(' ').forEach(word => word && words.push(word))
  return words
}, [])

I'm sorry about that. I should've looked up the syntax. But I'll keep it in mind next time. Thank you :)
Shall I create a PR?

I'm sorry about that. I should've looked up the syntax. But I'll keep it in mind next time. Thank you :)
Shall I create a PR?

I'm sorry about that. I should've looked up the syntax. But I'll keep it in mind next time. Thank you :)
Shall I create a PR?

Yes.
Thanks

I'm sorry about that. I should've looked up the syntax. But I'll keep it in mind next time. Thank you :)
Shall I create a PR?

Yes.
Thanks


Reduce bridgehead update interval to once a day at 6am

Currently, the bridgehead updates every full hour. As we have more long-running processes, such as analyses and quality reports, these are interrupted by the update restart.
Per our discussion, this PR reduces the update interval to once daily at 6am.
This time point is after the docker registry replication time, hence, should have access to the newest docker images.
Note: The changes are not automatically applied, but require a repeated ./bridgehead install <project> call to update the systemd timer.

Are we not supposed to merge to develop branch first?

Are we not supposed to merge to develop branch first?

GitHubs PR rebase makes this pretty ugly. But you are correct. As this change is not applied automatically, this ist currently not an issue but something to be mindful of in the future.


Vegetative Morphology & Reproductive Morphology

In This two Chapter is yours and you will the give data is correct or not . If the data is wrong change it.

error correct

Good Job @SanthoshKumarB4


Fix selection early termination test

Credit to: siddharthteotia
Replace: #5167

Replace #5167

@mcvsubbu Good catch!


imgtool: Print image digest during verify

In an effort to create a script to do firmware based on an URL, I could
not easily retrieve the image digest. newtmgr needs the hash when
marking a image for testing.

@caspermeijn Please sign-off your commit.

@utzig Added Singed-off-by line to the commit


stomp via websocket

Does the go-micro support the stomp via websocket? or broker proxy?

See https://github.com/micro/go-plugins/tree/master/broker/stomp


Don't merge dataplane-operator bundle ENVs twice

@dprince: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/openstack-operator-build-deploy-kuttl 	cfba4cc link 	true 	/test openstack-operator-build-deploy-kuttl
Full PR test history. Your PR dashboard.

Not sure what to make of this error because I haven't dug into it, but here is the problem:
+ sed -i custom-bundle.Dockerfile.pinned -e 's|quay.io/openstack-k8s-operators/telemetry-operator-bundle.*|quay.io/openstack-k8s-operators/telemetry-operator-bundle:232275280f55f5e216912bafc8d949ed1fe132ef
232275280f55f5e216912bafc8d949ed1fe132ef|'
sed: -e expression #1, char 160: unterminated `s' command
make: *** [Makefile:233: bundle] Error 1

@dprince: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/openstack-operator-build-deploy-kuttl 	cfba4cc link 	true 	/test openstack-operator-build-deploy-kuttl
Full PR test history. Your PR dashboard.

Not sure what to make of this error because I haven't dug into it, but here is the problem:
+ sed -i custom-bundle.Dockerfile.pinned -e 's|quay.io/openstack-k8s-operators/telemetry-operator-bundle.*|quay.io/openstack-k8s-operators/telemetry-operator-bundle:232275280f55f5e216912bafc8d949ed1fe132ef
232275280f55f5e216912bafc8d949ed1fe132ef|'
sed: -e expression #1, char 160: unterminated `s' command
make: *** [Makefile:233: bundle] Error 1

That error is unrelated and should now be fixed.

recheck

/lgtm


Update typo in editor startup message

Noticed a small typo in the welcome message. I think starts (plural) should be start (singular)...

Cheers,
  Lee

@leereilly this is an amazing catch, thank you, I somehow never noticed this!
can you backport the correction to packages/graphiql/src/GraphiQL.tsx as well?

Ha ha - you're welcome 😆
It looks like it's already correct in..here? https://github.com/graphql/graphiql/blob/237c7abc8307729c948d22a3fae48634c875334c/packages/graphiql/src/components/GraphiQL.tsx#L1696
(I didn't attempt to build it... I just searched for troublesome string)

hmm ok! the 1.x branch has upstream improvements confusingly enough. the 2.0.x rfc you added to in this PR was a conversion to modern react/context from last year, there are new plans afoot
the version you are using must be GraphiQL.app or something that bundles our build in a desktop app? so they must have bundled an older version then

Oh gotcha - I may have been guilty of just doing  brew install graphiql --cask and making some assumptions.
That gave me Version 0.7.2 (0.7.2).
I'm going to assume it's more than a version bump to https://github.com/skevy/graphiql-app/blob/36f4695ad10e6406d81f15f3f44a9a61d7be8e48/package.json#L33, but if you think it's worth a try, I'll give a shot!


NIFI-6716: Prometheus Metrics Server returns 500 when a Remote Process Group used

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Prometheus Metrics Server returns 500 (Internal Server Error) when a Remote Process Group is used. Just because the labels number of ACTIVE_REMOTE_PORT_COUNT, INACTIVE_REMOTE_PORT_COUNT, and AVERAGE_LINEAGE_DURATION are unmatched. This PR fixes it.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically master)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Thanks, Pierre!


Add Prefix Matches

Does it support wildcard prefix matches? If so it should be more documented if features such as wildcard prefix matches or clariflied.

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

ID: 73edc3d1-d0db-0ee3-7928-19bd1e509d55
Version Independent ID: 4b0e8f7c-591c-c5c4-37f4-e5a47914b873
Content: Configure object replication (preview) - Azure Storage
Content Source: articles/storage/blobs/object-replication-configure.md
Service: storage
Sub-service: blobs
GitHub Login: @tamram
Microsoft Alias: tamram

@msandbu Thanks for your question. We are checking on this and will respond to you soon.

#reassign: @tamram
@msandbu - Thanks for your feedback. I've noted in the doc that wildcard characters are not supported.
#please-close


Add README and thumbnail on example 'simultaneous-cursors'

What this PR does / why we need it?
Add README.md and thumbnail.jpg on example simultaneous-cursors.
There's no any docs on example simultaneous-cursors, and I need thumbnail and description to solve those issue.
Any background context you want to provide?
What are the relevant tickets?

Feature #682
Checklist

[x] Add thumbnil.jpg
[x] Write README.md

Seems like CI is failing. I'm having same issue on my local environment. Any ideas?
cc. @hackerwins

The problem is related to https://github.com/golang/go/issues/58550.


Skill map grey locked cards look ugly

Feedback - "The grey locked cards look like a bug, think about a better way to show locked content that isn't so off-putting."

@soniakandah this is feedback from Amanda. Can you take a look at this?

@soniakandah this is feedback from Amanda. Can you take a look at this?

no longer an issue in v2 skillmap


Release: v2.8.2

This issue template is used to track the rollout of a new KEDA version.
For the full release process, we recommend reading this document.
Progress

[x] Prepare changelog
[x] Add the new version to GitHub Bug report template
[x] Create KEDA release
[x] Publish new documentation version
[x] Setup continous container scanning with Snyk
[x] Prepare & ship Helm chart
[x] Prepare next release
[x] Provide update in Slack
[x] Tweet about new release

KEDA v2.8.2 has been released 🥳 🥳 🥳


getAutoValues in find()

Is it possible to perform recalculate autoValues on performing a find() operation. An example scenario where this would help is,
deadline: {
    type: Date,
    custom: function () {
        // if deadline is before current time, give Invalid deadline error
        if (this.value < new Date) return "invalidDeadline";
    }
},
ended: {
    type: Boolean,
    optional: true,
    autoValue: function () {
        return new Date > this.siblingField('deadline').value;
    }
}

Rerunning the autoValue function of the ended field upon doing a find() operation will result in the ended value being updated based on the current time. I am thinking something along the lines of find({}, {getAutoValues: true}) same as in Collection2 for the insert operation.

Have you considered using a Cron job to update your documents that have gone past their deadline? If I understand your dilemma, Cron seems like the perfect tool for it.
You could have it run at any time interval you like, and it is an extremely versatile tool.
I use Cron all of the time for updates similar to this one.

I did think of using the cron package but felt it is less overhead to only update with autoValues on find(). This way there is no need for unnecessary updating of the values.

Closing old issues. Please comment if this is still an issue and should be reopened.


API documentation?

Hi,
The link(https://github.com/bitpay/insight#api) listed in the website(https://insight.is/) is outdated.
Is there a new link? Or maybe I can just read the source code :)

https://github.com/bitpay/insight#api
is the most updated docs. Please send a PR if you see something outdated. thanks a lot!!

@matiu I think you missed my point, the link you given shows the this repository, but does not contain any documentation related to the API.

Sorry, I  meant https://github.com/bitpay/insight-api
(see the Readme bellow)


Minor improvements

Hi @mvillaseco,
I have done a little changes:

Reduce the highlight time
Add highlight after activate
Add highlight to previous default domain
Minor code style fixes

Could you review?

Great! 👍


Blue/green deployment support

This PR incudes nginx-alpha-ssl code reorganization and blue/green deployment support.
To test it see bitesize PR #709.

OK I don't know why I'm trying to merge it to devlinmr rather than to bitesize/contrib. We need to sort this.


Server Crash - Accessing LegacyRandomSource from multiple threads

Timings link
https://timings.aikar.co/?id=90cc52627df94160bf457b2f070eaa99
Stack trace
https://paste.gg/p/anonymous/17fcba27d66943dd83454c2b30f7c183/files/66c4841665e6465298fa37e6b9ba8827/raw
Actions to reproduce (if known)
No idea, sorry. Was a one-off crash error that I figured I'd report upstream before updating Purpur 9 builds ahead.
Purpur version
git-Purpur-1675 (MC: 1.19)*
Agreements

[X] I am running the latest version of Purpur available from https://purpurmc.org/downloads.
[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] My version of Minecraft is supported by Purpur.

Other
No response

Are you able to reproduce on the latest version?

I'm not sure how it even happens so I can't say. Latest doesn't have any commits to chunk loading or behavior. It's mostly just Spark changes and a minor API change in Bukkit/Craftbukkit (from Paper upstream merge) so the issue should still be relevant.

I had the same error some days before. Idk what I did exactly but update all plugins and purpur itself.

This is caused by something that is ticking things off the main thread. It could be one of your plugins, or a bug in one of our upstreams. You'll have to do some troubleshooting to figure out which, but this is not caused by Purpur.


pacakge-lock.json file not updated

I've just integrated this extension into our Azure DevOps repository and yaml pipeline, and things seemed to be working. However, I noticed that each PR that was opened was only updating the package.json file, but not syncing the change with the package-lockfile.json. I already have dependabot integrated with several of my Github repos and this has worked out of the box, so I'm not sure what I've done wrong.
Here is my configuration file and pipeline template:
.github/dependabot.yaml
version: 2
registries:
  upstreams:
    type: npm-registry
    url: <redacted>
    token: PAT:${{AZURE_DEVOPS_PAT}}
updates:
  - package-ecosystem: "npm"
    directory: "/"
    registries:
      - upstreams
    schedule:
      interval: "daily"
    open-pull-requests-limit: 10
    milestone: 163501
    versioning-strategy: increase

azure-pipelines.dependabot.yaml
schedules:
  - cron: "0 8 * * *"
    displayName: Daily Midnight (PST) Dependabot Run
    branches:
      include: [master]
    always: true

trigger: none

pool:
  vmImage: ubuntu-latest

steps:
  - task: dependabot@1
    displayName: "Run Dependabot"
    inputs:
      packageManager: "npm"
    env:
      AZURE_DEVOPS_PAT: $(AZURE_DEVOPS_PAT)

@AndrewCraswell Should that be package-lock.json and not package-lockfile.json? Also, do you have a public repro for this?

@jussibility could you offer a public repro in AzDO?
We only need package.json, package-lock.json, dependabot.yml, and azure-pipelines.yml files.

@mburumaxwell I created a public project for this but it seems I cannot run pipelines then. I've filled in the Azure DevOps Parallelism Request, but I do not know when and how they will respond to this.

The actual run of the pipeline is not as important. The repository containing the files is what is needed. I will clone and reproduce it from my end.

@mburumaxwell have you tried reproducing it?

@AndrewCraswell @jussibility does this work without setting  open-pull-requests-limit: 0?

According to my repro, the package-lock.json file would be updated.
https://dev.azure.com/tingle/dependabot/_build/results?buildId=57483&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=1f93c1a3-255b-505a-53c9-c382114aabf5
The PR is created without issues (open-pull-requests-limit is not set_

When running this for security only updates (open-pull-requests-limit: 0) there is no PR created because there is no vulnerability detected.
It could be there was an issue in the upstream that as fixed. Maybe you can try using the dockerImageTag: latest input in the extension?

@AndrewCraswell @jussibility is this resolved?
Will close soon.

@mburumaxwell Sorry to bump this closed issue, but I'm seeing this as well. I too am specifying open-pull-requests-limit: 0 in dependabot.yml as our team is only concerned with vulnerabilities at the moment. Like the others, I only see Dependabot checking the dependencies in package.json.
When I run npm audit locally, I see one vulnerability for a transitive dependency and npm audit fix updates the package-lock.json. Based on the logs in the pipeline, it seems that it sees that the lockfile is there, but Dependabot doesn't check for this vulnerability at all:

For reference, here's my Dependabot config:
version: 2
updates:

  # Front-end dependencies.
  - package-ecosystem: 'npm'
    directory: '/'
    target-branch: 'env/dev'
    open-pull-requests-limit: 0 # Only opens PRs for vulnerabilities.

    # NOTE: The schedule here is overridden by the schedule in dependabot-pipeline.yml. Dependabot still requires
    # a schedule to be specified here, but it does nothing.
    schedule:
      interval: 'daily'

Is there a configuration option I might have missed? Happy to provide any other info that would be useful.

Also adding here, I added my same package.json, package-lock.json, dependabot.yml to a brand new repo in GitHub and Dependabot immediately created the PR—just like @jussibility mentioned earlier.

Here's my GitHub repository that I used to test things. As you can see there, there are two PRs that Dependabot created to update the package-lock.json to fix vulnerabilities in some transitive dependencies.
These PRs don't get created with the Azure DevOps extension however, even using the same files as this repo. It only checks the dependencies mentioned in package.json and totally misses these vulnerabilities somehow. I've included the .yml file I used for my pipeline in case there's something wrong in my configuration.
 Security only updates are implied.
2023-05-25T05:31:25.5416877Z Using 'https://dev.azure.com:443/' as API endpoint
2023-05-25T05:31:25.5417559Z Working in customerdynamics/Call2Action/_git/Call2Action-Web, 'env/dev' branch under '/' directory
2023-05-25T05:31:25.5417770Z Looking for configuration file in the repository ...
2023-05-25T05:31:25.5418413Z 🌍 --> GET https://dev.azure.com/customerdynamics/Call2Action/_apis/git/repositories/Call2Action-Web/stats/branches?name=env/dev
2023-05-25T05:31:25.6180932Z 🌍 <-- 200 https://dev.azure.com/customerdynamics/Call2Action/_apis/git/repositories/Call2Action-Web/stats/branches?name=env/dev
2023-05-25T05:31:25.6192820Z 🌍 --> GET https://dev.azure.com/customerdynamics/Call2Action/_apis/git/repositories/Call2Action-Web/items?path=.github/dependabot.yml&versionDescriptor.versionType=commit&versionDescriptor.version=5c4fc118597700b7b2fbbbb6d33a9d826ee2d8bd
2023-05-25T05:31:25.8036040Z 🌍 <-- 200 https://dev.azure.com/customerdynamics/Call2Action/_apis/git/repositories/Call2Action-Web/items?path=.github/dependabot.yml&versionDescriptor.versionType=commit&versionDescriptor.version=5c4fc118597700b7b2fbbbb6d33a9d826ee2d8bd
2023-05-25T05:31:25.8037202Z Using configuration file at '/.github/dependabot.yml' 😎
2023-05-25T05:31:25.8082488Z Cloning repository into /home/dependabot/dependabot-updater/tmp/customerdynamics/Call2Action/_git/Call2Action-Web
2023-05-25T05:31:27.2791402Z Found 2 dependency file(s) at commit 5c4fc118597700b7b2fbbbb6d33a9d826ee2d8bd
2023-05-25T05:31:27.2797511Z  - /package.json
2023-05-25T05:31:27.2797712Z  - /package-lock.json
2023-05-25T05:31:27.2797880Z Parsing dependencies information
2023-05-25T05:31:27.8285891Z Found 35 dependencies
2023-05-25T05:31:27.8286696Z  - @angular-material-components/datetime-picker (9.0.0)
2023-05-25T05:31:27.8287133Z  - @angular/animations (15.2.6)
2023-05-25T05:31:27.8287470Z  - @angular/cdk (15.2.6)
2023-05-25T05:31:27.8287826Z  - @angular/common (15.2.6)
2023-05-25T05:31:27.8288173Z  - @angular/compiler (15.2.6)
2023-05-25T05:31:27.8288522Z  - @angular/core (15.2.6)
2023-05-25T05:31:27.8288852Z  - @angular/forms (15.2.6)
2023-05-25T05:31:27.8289702Z  - @angular/material (15.2.6)
2023-05-25T05:31:27.8290072Z  - @angular/platform-browser (15.2.6)
2023-05-25T05:31:27.8290485Z  - @angular/platform-browser-dynamic (15.2.6)
2023-05-25T05:31:27.8290864Z  - @angular/router (15.2.6)
2023-05-25T05:31:27.8291190Z  - aws-amplify (5.0.25)
2023-05-25T05:31:27.8291517Z  - crypto-js (3.3.0)
2023-05-25T05:31:27.8291847Z  - html-to-image (1.11.11)
2023-05-25T05:31:27.8292220Z  - intl-tel-input (17.0.21)
2023-05-25T05:31:27.8292537Z  - ngx-mask (15.1.0)
2023-05-25T05:31:27.8292845Z  - rxjs (6.5.5)
2023-05-25T05:31:27.8293147Z  - tinycolor2 (1.6.0)
2023-05-25T05:31:27.8293440Z  - tslib (2.5.0)
2023-05-25T05:31:27.8293756Z  - zone.js (0.11.8)
2023-05-25T05:31:27.8294124Z  - @angular-devkit/build-angular (15.2.5)
2023-05-25T05:31:27.8294492Z  - @angular/cli (15.2.5)
2023-05-25T05:31:27.8294842Z  - @angular/compiler-cli (15.2.6)
2023-05-25T05:31:27.8295210Z  - @types/crypto-js (3.1.47)
2023-05-25T05:31:27.8295548Z  - @types/jasmine (3.6.11)
2023-05-25T05:31:27.8295902Z  - @types/node (12.20.55)
2023-05-25T05:31:27.8296222Z  - jasmine-core (4.5.0)
2023-05-25T05:31:27.8296568Z  - jasmine-spec-reporter (5.0.2)
2023-05-25T05:31:27.8296903Z  - karma (6.3.20)
2023-05-25T05:31:27.8297243Z  - karma-chrome-launcher (3.1.1)
2023-05-25T05:31:27.8297655Z  - karma-coverage-istanbul-reporter (3.0.3)
2023-05-25T05:31:27.8298007Z  - karma-jasmine (4.0.2)
2023-05-25T05:31:27.8298408Z  - karma-jasmine-html-reporter (1.7.0)
2023-05-25T05:31:27.8298735Z  - ts-node (8.3.0)
2023-05-25T05:31:27.8299055Z  - typescript (4.9.5)
2023-05-25T05:31:27.8300021Z 🌍 --> GET https://dev.azure.com/customerdynamics/_apis/connectionData
2023-05-25T05:31:27.8832339Z 🌍 <-- 200 https://dev.azure.com/customerdynamics/_apis/connectionData
2023-05-25T05:31:27.8833563Z 🌍 --> GET https://dev.azure.com/customerdynamics/Call2Action/_apis/git/repositories/Call2Action-Web
2023-05-25T05:31:27.9444116Z 🌍 <-- 200 https://dev.azure.com/customerdynamics/Call2Action/_apis/git/repositories/Call2Action-Web
2023-05-25T05:31:27.9497786Z 🌍 --> GET https://dev.azure.com/customerdynamics/Call2Action/_apis/git/repositories/Call2Action-Web/pullrequests?api-version=6.0&searchCriteria.status=active&searchCriteria.creatorId=13b6faaf-d832-62a8-9940-eaf5547b9347&searchCriteria.targetRefName=refs/heads/env/dev
2023-05-25T05:31:28.0302064Z 🌍 <-- 200 https://dev.azure.com/customerdynamics/Call2Action/_apis/git/repositories/Call2Action-Web/pullrequests?api-version=6.0&searchCriteria.status=active&searchCriteria.creatorId=13b6faaf-d832-62a8-9940-eaf5547b9347&searchCriteria.targetRefName=refs/heads/env/dev
2023-05-25T05:31:28.0303121Z Checking if @angular-material-components/datetime-picker 9.0.0 is vulnerable
2023-05-25T05:31:28.2286294Z @angular-material-components/datetime-picker 9.0.0 is not vulnerable
2023-05-25T05:31:28.2286823Z Checking if @angular/animations 15.2.6 is vulnerable
2023-05-25T05:31:28.5204790Z @angular/animations 15.2.6 is not vulnerable
2023-05-25T05:31:28.5205036Z Checking if @angular/cdk 15.2.6 is vulnerable
2023-05-25T05:31:28.7173031Z @angular/cdk 15.2.6 is not vulnerable
2023-05-25T05:31:28.7174042Z Checking if @angular/common 15.2.6 is vulnerable
2023-05-25T05:31:28.9063554Z @angular/common 15.2.6 is not vulnerable
2023-05-25T05:31:28.9064049Z Checking if @angular/compiler 15.2.6 is vulnerable
2023-05-25T05:31:29.2104834Z @angular/compiler 15.2.6 is not vulnerable
2023-05-25T05:31:29.2106123Z Checking if @angular/core 15.2.6 is vulnerable
2023-05-25T05:31:29.4024318Z @angular/core 15.2.6 is not vulnerable
2023-05-25T05:31:29.4025080Z Checking if @angular/forms 15.2.6 is vulnerable
2023-05-25T05:31:29.5743277Z @angular/forms 15.2.6 is not vulnerable
2023-05-25T05:31:29.5743676Z Checking if @angular/material 15.2.6 is vulnerable
2023-05-25T05:31:29.7466567Z @angular/material 15.2.6 is not vulnerable
2023-05-25T05:31:29.7467685Z Checking if @angular/platform-browser 15.2.6 is vulnerable
2023-05-25T05:31:29.9365796Z @angular/platform-browser 15.2.6 is not vulnerable
2023-05-25T05:31:29.9366889Z Checking if @angular/platform-browser-dynamic 15.2.6 is vulnerable
2023-05-25T05:31:30.1331219Z @angular/platform-browser-dynamic 15.2.6 is not vulnerable
2023-05-25T05:31:30.1331539Z Checking if @angular/router 15.2.6 is vulnerable
2023-05-25T05:31:30.3304963Z @angular/router 15.2.6 is not vulnerable
2023-05-25T05:31:30.3305705Z Checking if aws-amplify 5.0.25 is vulnerable
2023-05-25T05:31:30.5121182Z aws-amplify 5.0.25 is not vulnerable
2023-05-25T05:31:30.5122100Z Checking if crypto-js 3.3.0 is vulnerable
2023-05-25T05:31:30.6914255Z crypto-js 3.3.0 is not vulnerable
2023-05-25T05:31:30.6914948Z Checking if html-to-image 1.11.11 is vulnerable
2023-05-25T05:31:30.8834231Z html-to-image 1.11.11 is not vulnerable
2023-05-25T05:31:30.8834834Z Checking if intl-tel-input 17.0.21 is vulnerable
2023-05-25T05:31:31.0740826Z intl-tel-input 17.0.21 is not vulnerable
2023-05-25T05:31:31.0741116Z Checking if ngx-mask 15.1.0 is vulnerable
2023-05-25T05:31:31.2499614Z ngx-mask 15.1.0 is not vulnerable
2023-05-25T05:31:31.2500204Z Checking if rxjs 6.5.5 is vulnerable
2023-05-25T05:31:31.4261782Z rxjs 6.5.5 is not vulnerable
2023-05-25T05:31:31.4262322Z Checking if tinycolor2 1.6.0 is vulnerable
2023-05-25T05:31:31.6313452Z tinycolor2 1.6.0 is not vulnerable
2023-05-25T05:31:31.6313833Z Checking if tslib 2.5.0 is vulnerable
2023-05-25T05:31:31.8359083Z tslib 2.5.0 is not vulnerable
2023-05-25T05:31:31.8359529Z Checking if zone.js 0.11.8 is vulnerable
2023-05-25T05:31:32.0180948Z zone.js 0.11.8 is not vulnerable
2023-05-25T05:31:32.0184226Z Checking if @angular-devkit/build-angular 15.2.5 is vulnerable
2023-05-25T05:31:32.2110859Z @angular-devkit/build-angular 15.2.5 is not vulnerable
2023-05-25T05:31:32.2111551Z Checking if @angular/cli 15.2.5 is vulnerable
2023-05-25T05:31:32.4000331Z @angular/cli 15.2.5 is not vulnerable
2023-05-25T05:31:32.4001212Z Checking if @angular/compiler-cli 15.2.6 is vulnerable
2023-05-25T05:31:32.5793740Z @angular/compiler-cli 15.2.6 is not vulnerable
2023-05-25T05:31:32.5795372Z Checking if @types/crypto-js 3.1.47 is vulnerable
2023-05-25T05:31:32.8307765Z @types/crypto-js 3.1.47 is not vulnerable
2023-05-25T05:31:32.8308269Z Checking if @types/jasmine 3.6.11 is vulnerable
2023-05-25T05:31:33.0288963Z @types/jasmine 3.6.11 is not vulnerable
2023-05-25T05:31:33.0289520Z Checking if @types/node 12.20.55 is vulnerable
2023-05-25T05:31:33.2486840Z @types/node 12.20.55 is not vulnerable
2023-05-25T05:31:33.2487702Z Checking if jasmine-core 4.5.0 is vulnerable
2023-05-25T05:31:33.4608563Z jasmine-core 4.5.0 is not vulnerable
2023-05-25T05:31:33.4608933Z Checking if jasmine-spec-reporter 5.0.2 is vulnerable
2023-05-25T05:31:33.6379423Z jasmine-spec-reporter 5.0.2 is not vulnerable
2023-05-25T05:31:33.6379887Z Checking if karma 6.3.20 is vulnerable
2023-05-25T05:31:33.8304464Z karma 6.3.20 is not vulnerable
2023-05-25T05:31:33.8305315Z Checking if karma-chrome-launcher 3.1.1 is vulnerable
2023-05-25T05:31:34.0327907Z karma-chrome-launcher 3.1.1 is not vulnerable
2023-05-25T05:31:34.0328820Z Checking if karma-coverage-istanbul-reporter 3.0.3 is vulnerable
2023-05-25T05:31:34.2113307Z karma-coverage-istanbul-reporter 3.0.3 is not vulnerable
2023-05-25T05:31:34.2115183Z Checking if karma-jasmine 4.0.2 is vulnerable
2023-05-25T05:31:34.4017905Z karma-jasmine 4.0.2 is not vulnerable
2023-05-25T05:31:34.4018847Z Checking if karma-jasmine-html-reporter 1.7.0 is vulnerable
2023-05-25T05:31:34.5904305Z karma-jasmine-html-reporter 1.7.0 is not vulnerable
2023-05-25T05:31:34.5906745Z Checking if ts-node 8.3.0 is vulnerable
2023-05-25T05:31:34.7861371Z ts-node 8.3.0 is not vulnerable
2023-05-25T05:31:34.7862086Z Checking if typescript 4.9.5 is vulnerable
2023-05-25T05:31:34.9619700Z typescript 4.9.5 is not vulnerable
2023-05-25T05:31:34.9620092Z Done

After which, no PRs are created and I can see that these 2 vulnerabilities remain:
# npm audit report

engine.io  5.1.0 - 6.4.1
Severity: moderate
engine.io Uncaught Exception vulnerability - https://github.com/advisories/GHSA-q9mw-68c2-j6m5
fix available via `npm audit fix`
node_modules/engine.io

socket.io-parser  4.0.4 - 4.2.2
Severity: high
Insufficient validation when decoding a Socket.IO packet - https://github.com/advisories/GHSA-cqmj-92xf-r6r9
fix available via `npm audit fix`
node_modules/socket.io-parser

2 vulnerabilities (1 moderate, 1 high)

To address all issues, run:
  npm audit fix

@hendrickson-tyler looking at the package.json file, the engine.io and socket.io-parser dependencies are not referenced but they are present in the package-lock.json file. This extension works by looking for top-level dependencies so maybe this is why they are not checked, as seen here

Logging found deps:
https://github.com/tinglesoftware/dependabot-azure-devops/blob/46a0485e3318d93e940ab5875b667cb27f5704c9/updater/bin/update-script.rb#L546-L547
Iterating through each dependency
https://github.com/tinglesoftware/dependabot-azure-devops/blob/46a0485e3318d93e940ab5875b667cb27f5704c9/updater/bin/update-script.rb#L563

It is evidenced by the two dependencies not being in the list of packages in the build log.
My suspicion is that removing the top-level filtering may work but I am not sure it would. Maybe it is something you can try then contribute?

@mburumaxwell Apologies for the late response. Thank you for the detail in explaining that! I can try to take a look if I get some free time here soon. Is there some documentation I can follow for getting this project running locally? I'm afraid I'm not very familiar with Ruby, but I can probably figure it out.
Any chance the issue could be re-opened for visibility? Or should a new issue be created for this?

@hendrickson-tyler
you can execute the dry-run.rb script using the simple instructions here. If need be you can then use the same knowledge to run the update_script.rb in this repo.

Any chance the issue could be re-opened for visibility? Or should a new issue be created for this?

Sure, a new issue is okay but how about going straight to contributing a PR?


I'm getting an Openai key failure error even though I set everything for Sydney only

I set the .env to work only with BingAi but it keeps giving me an openai key failure error.
C:\ecc\bin ai\assistant>node --loader ts-node/esm src/index.ts
(node:12100) ExperimentalWarning: --experimental-loader may be removed in the future; instead use register():
--import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("ts-node/esm", pathToFileURL("./"));'
(Use node --trace-warnings ... to show where the warning was created)
[WARNING]: Importing from "langchain/prompts" is deprecated.
Instead, please import from "@langchain/core/prompts".
This will be mandatory after the next "langchain" minor version bump to 0.2.
[WARNING]: Importing from "langchain/schema" is deprecated.
Instead, please import from the appropriate entrypoint in "@langchain/core" or "langchain".
This will be mandatory after the next "langchain" minor version bump to 0.2.
[WARNING]: Importing from "langchain/schema/runnable" is deprecated.
Instead, please import from "@langchain/core/runnables".
This will be mandatory after the next "langchain" minor version bump to 0.2.
file:///C:ecc/Desktop/bin%20ai/assistant/node_modules/.pnpm/@langchain+openai@0.0.13/node_modules/@langchain/openai/dist/chat_models.js:338
throw new Error("OpenAI or Azure OpenAI API key not found");
^
Error: OpenAI or Azure OpenAI API key not found
at new ChatOpenAI (file:///C:/ecc/Desktop/bin%20ai/assistant/node_modules/.pnpm/@langchain+openai@0.0.13/node_modules/@langchain/openai/dist/chat_models.js:338:19)
at file:///C:/ecc//bin%20ai/assistant/src/clients/tools-openrouter.ts:7:15
at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)
at async loadESM (node:internal/process/esm_loader:28:7)
at async handleMainPromise (node:internal/modules/run_main:113:12)
Node.js v20.11.1

Maige label

The issue should be resolved in pull request #283 . Please ensure to update your .env file with the new ENABLE_WEB_BROWSER_TOOL information, as detailed in the .env.example file.

It works, thanks for the help.
I don't understand why jailbreak doesn't work even though the !jailbreak command is set to on. I set the name of the bot but it continues to say that its name is Sydney, furthermore it cannot understand the messages that were sent immediately before so it does not follow the context of the conversation. The cookies are set correctly, the bot works, thanks for the assistance


configuration/telemeter/metrics.json: Refresh allow list

Hello all 👋 I ran make whitelisted_metrics and then make. The generation seems to have touched other files, not sure if that is intended, but I only committed the allow list.
Side note: Also make clean doesn't seem to actually clear the state for me.

Heya :wave:

I ran make whitelisted_metrics and then make. The generation seems to have touched other files, not sure if that is intended, but I only committed the allow list.

I tried this on the current main but couldn't reproduce. In my case it only updated the metrics.json first and then the template got updated as expected, (I had to use make --always-make all though, because somehow it was not picking up that metrics.json got updated).

Side note: Also make clean doesn't seem to actually clear the state for me.

The target is used to only deleting the json files generated from jsonnet, after converting them to yaml using gojsontoyaml. I guess we can name it better because make clean is generally used of cleaning up state as you expected.

Thanks Prem for the explanation!


feat: allow splitting of X from y in observations – helper function on _SimpleCycle

resolved by #174


libcbor: unstable-2019-07-25 -> 0.8.0

Motivation for this change
version update to the latest stable release
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

I also opened https://github.com/PJK/libcbor/pull/164 which will allow us to drop the CMAKE_INSTALL_LIBDIR flag and split the package to multiple outputs.

As per the changelog, we need -DBUILD_SHARED_LIBS=on in cmakeFlags. Also it looks like we no longer need to disable lto since 0.7.0.

Addresed in d9e04431c87af1dc740c040fed9ae0bc4ce2a032

Thanks.


fix: add 'I18nConnector' for using i18n in console

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[ ] Not that difficult

Type of Change

[ ] New feature
[X] Bug fixes
[ ] Feature improvement

[ ] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[ ] Updated Storybook documents for component
[ ] Wrote test codes for composable, utils and etc.
[X] Tested with console(if usages are changed)

Description

add 'I18nConnector' which can set i18n for using i18n in console.
update languages pack.

Things to Talk About

:tada: This PR is included in version 2.0.0-beta.25 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


type error: this._initPlayer not defined

Hello. Thanks for publishing this module!
I'm attempting to use it in a create-react app and get this error when loading the component.
Using the URL directly in the browser plays the stream, however using the same exact URL in my component's render function I get that error.
import React from 'react';
import ReactHLS from 'react-hls-player';
class VideoPlayer extends React.Component {
render() {
return(

);
}
}

Hey @aaplmike!
I'll take a look in to this. In the meantime, would you be able to provide me with your React version as well as the stream URL you are trying to load?
Thanks 😄

Hi,
I have set enableWorker option to false and that error went away.
hlsConfig ={{     enableWorker: true, }}
more details: https://github.com/video-dev/hls.js/issues/2064

Thanks @sonikas991
Looks like this is potentially an issue with a compatibility between hls.js and React. I'll keep a close eye on the thread and apply an update when one becomes available.

https://github.com/devcshort/react-hls/commit/e027df018652e9554da4f6cac44b0a8145df8cdb


Duplicate Error Messages when using SetCollectionValidator

When I use the SetCollectionValidator to validate my collection of address objects it is gnerating duplicate error messages for each issue if finds in the object inside the collection.  Is this a bug or am I missing something with the SetCollectionValidator that is causing this?  The workaround I have for this is to create a new response and remove the duplicate messages through code using a custom DelegatingHandler class.  Below is the HTTP response from my testing and the code that I am using.  I am also using FluentValidation v<IP_ADDRESS> and FluentValidation.WebApi v<IP_ADDRESS>.
Status Code: BadRequest
Response Message: {
"Message": "The request is invalid.",
"ModelState": {
"order.Addresses[0].Street": [
"Street address cannot be empty.", //Duplicates
"Street address cannot be empty."
],
"order.Addresses[0].City": [
"City cannot be empty.", //Duplicates
"City cannot be empty."
],
"order.Addresses[0].State": [
"State cannot be empty.", //Duplicates
"State cannot be empty."
],
"order.Addresses[0].PostalCode": [
"Postal code must be supplied", //Duplicates
"Postal code must be supplied"
],
"order.FirstName": [
"First name cannot be empty."
],
"order.LastName": [
"Last name cannot be empty."
],
"order.BillingAddress": [
"Billing address must be supplied"
],
"order.ShippingAddress.State": [
"State needs to be two characters."
],
"order.ShippingAddress.PostalCode": [
"Postal code must be supplied"
]
}
}
//Class structure with validators
[Validator(typeof(OrderCreateRequestValidator))]
public class OrderCreateRequest
{
public int Id { get; set; }
public string FirstName { get; set; }
public string LastName { get; set; }
public Address1 BillingAddress { get; set; }
public Address1 ShippingAddress { get; set; }
public List<Address1> Addresses { get; set; }

}
[Validator(typeof(Address1Validator))]
public class Address1
{
public string Street { get; set; }
public string City { get; set; }
public string State { get; set; }
public PostalCode1 PostalCode { get; set; }
}
[Validator(typeof(PostalCode1Validator))]
public class PostalCode1
{
public string First6 { get; set; }
public string Last4 { get; set; }
}
public class PostalCode1Validator : AbstractValidator
{
public PostalCode1Validator()
{
RuleFor(x => x.First6).NotEmpty().WithMessage("First six of postal code cannot be blank.")
.Length(6).WithMessage("First six of postal code cannot be more than 6 character long.");
}
}
public class Address1Validator : AbstractValidator
{
public Address1Validator()
{
RuleFor(x => x.Street).NotEmpty().WithMessage("Street address cannot be empty.");
RuleFor(x => x.City).NotEmpty().WithMessage("City cannot be empty.");
RuleFor(x => x.State).NotEmpty().WithMessage("State cannot be empty.")
.Length(2).WithMessage("State needs to be two characters.");
RuleFor(x => x.PostalCode).NotNull().WithMessage("Postal code must be supplied").SetValidator(new PostalCode1Validator());
}
}
public class OrderCreateRequestValidator : AbstractValidator
{
public OrderCreateRequestValidator()
{
RuleFor(x => x.FirstName).NotEmpty().WithMessage("First name cannot be empty.");
RuleFor(x => x.LastName).NotEmpty().WithMessage("Last name cannot be empty.");
RuleFor(x => x.BillingAddress).NotNull().WithMessage("Billing address must be supplied")
.SetValidator(new Address1Validator());
RuleFor(x => x.ShippingAddress).NotNull().WithMessage("Shipping address must be supplied")
.SetValidator(new Address1Validator());
RuleFor(x => x.Addresses).NotNull().WithMessage("Addresses cannot be null")
.Must(addresses => addresses.Count > 1).WithMessage("Must contain at least one address in Addresses collection")
.SetCollectionValidator(new Address1Validator());
}
}
//Test object that I am using
var order = new OrderCreateRequest();
order.ShippingAddress = new Address1 { Street = "test", City = "test", State = "WID" };
order.Addresses = new List {
new Address1(),
new Address1 { Street = "test", City = "test", State = "WI", PostalCode = new PostalCode1 { First6 = "234323" } }
};

It's probably because of the WebApi integration. You're using both SetCollectionValidator, and you have [Validator(typeof(Address1Validator))] on your Address object. By doing this you're essentially telling WebApi to run validation twice.
Once happens as part of FluentValidation's built-in validation process (SetCollectionValidator), and the second happens as part of the ModelBinding process (because you've annotated with the [Validator(typeof(Address1Validator))]). Either pick one approach or the other, but don't use both.

Thanks very much that resolved my issue.


Observation Factory + TorsoIMU Observation

Create an expandable observation factory. The user can "register" an observation and dynamically create their observation space (useful for observation importance). An example on how to use it can be found in examples/solo8_vanilla/observation_dump.py.
@mahajanrevant's gonna take care of the motor encoder observation ❤.

Coverage decreased (-0.8%) to 97.911% when pulling 0fac39f0595396c0b6619bdb7558852bf9a7e6cd on agupta231-observation-factory into 0c2fb57c198ddd13ab27a1c92925927370fadbbb on main.


OTEL: ResourceExhausted error messages in DD

We are seeing logs of errors like this from OTEL in our DD logs.
OTEL: failed to upload metrics: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (7735027 vs. 4194304)

discussion: https://square.slack.com/archives/C07CHN37SKU/p1722535742804959

Fixed in #2242


storage initializer container downloads all the folder/files from matching path instead of absolute path

/kind bug
What steps did you take and what happened:
When we deploy the model storage initializer container, it downloads all the folders/files from the matching path instead of an absolute path. This happens because the storage initializer code uses a prefix to filter and download objects from s3 storage.

Create two folders with identical names with little difference in the s3 bucket. I created merlinite-7b-lab and merlinite-7b-lab-hf in a bucket respectively and upload model
deploy a model with KServe with a path merlinite-7b-lab
Check the container logs and found that it is downloading files from both the folders mentioned above

What did you expect to happen:
It should have only downloaded the from the mentioned path instead of prefix matching
What's the InferenceService yaml:
apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
  annotations:
    serving.knative.openshift.io/enablePassthrough: "true"
    sidecar.istio.io/inject: "true"
    sidecar.istio.io/rewriteAppHTTPProbers: "true"
    serving.kserve.io/deploymentMode: Serverless
  name: test-dir
spec:
  predictor:
    minReplicas: 1
    serviceAccountName: models-bucket-sa
    model:
      modelFormat:
        name: vllm
      runtime: vllm-runtime
      storageUri: s3://ods-ci-wisdom/merlinite-7b-lab
      resources:
        requests:
          memory: 5Gi

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Istio Version:2.5.2-0
Knative Version:1.33.0
KServe Version:
Kubeflow version:
Cloud Environment:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm] aws
Minikube/Kind version: openshift
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

logs:
`/prod_venv/lib64/python3.9/site-packages/pydantic/_internal/_config.py:334: UserWarning: Valid config keys have changed in V2:
* 'json_loads' has been removed
  warnings.warn(message, UserWarning)
/prod_venv/lib64/python3.9/site-packages/pydantic/_internal/_fields.py:160: UserWarning: Field "model_name" has conflict with protected namespace "model_".

You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
  warnings.warn(
/prod_venv/lib64/python3.9/site-packages/pydantic/_internal/_fields.py:160: UserWarning: Field "model_version" has conflict with protected namespace "model_".

You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
  warnings.warn(
INFO:root:Initializing, args: src_uri [s3://ods-ci-wisdom/merlinite-7b-lab] dest_path[ [/mnt/models]
INFO:root:Copying contents of s3://ods-ci-wisdom/merlinite-7b-lab to local
INFO:botocore.credentials:Found credentials in environment variables.
 I understand this is working as expected but i think we need to have the enhancement and find better approach instead of using prefix


Use - for categories with spaces

Use - for categories in blog-aside

Also needed for #153

/lgtm


JuliaCon 2021 | Day 3 Single Track | Soumith Chintala Keynote

JuliaCon 2021 | Day 3 Single Track | Soumith Chintala Keynote, https://www.youtube.com/watch?v=6V6jk_OdH-w
It is very nontechnical talk, while I prefer technical ones, so making timestamps was especially hard to me. Correct every one of my mistakes that you find and change anything you want.
00:00 Welcome!
01:40 Introduction by the speaker
03:19 What is PyTorch?
04:57 Implementation of PyTorch
05:20 Example: neural network in PyTorch
06:34 General principles of PyTorch
07:40 PyTorch team needs collaborate with others
08:42 PyTorch ecosystem
09:16 State of PyTorch in year 2020
10:00 Community and funding of PyTorch
11:49 PyTorch ecosystem
13:03 The journey of PyTorch
13:45 Where we came from?
15:05 Philosophy/principles of open source project
17:17 User and technology centric projects
21:22 Migrating from Torch to PyTorch
25:32 Interactions with other communities
28:52 Scope & risk
35:17 Measurement/metric
38:43 Scaling
40:45 Vertical and horizontal integration
42:17 Q&A: Do you see TorchScript becoming independent programming language?
44:35 Q&A: Do you imagine PyTorch first class front-end for languages other than Python?

Thank you!


Rviz version 1.14.23: librviz related crash after ubuntu (20.04) update

We are using ROS Noetic on Ubuntu 20.04 and have an application (GUI) that we developped and uses librviz.so
All was working well for the last two year until the latest Ubuntu update broke our application.
The Rviz version after the ubuntu update is 1.14.23
Below is the segmentation fault we are seeing.
Any hints why we started seeing this after the latest ubuntu update?
(gdb) bt
#0  0x00007ffff71968b4 in QWidget::layout() const () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#1  0x00007ffff728eb6d in QDockWidget::titleBarWidget() const () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2  0x00007ffff7d8635f in rviz::PanelDockWidget::addMaximizeButton() () at /opt/ros/noetic/lib/librviz.so
#3  0x00007fff34786fef in rviz::ImageDisplay::onInitialize() () at /opt/ros/noetic/lib/librviz_default_plugin.so
#4  0x00007ffff7d102a5 in rviz::Display::initialize(rviz::DisplayContext*) () at /opt/ros/noetic/lib/librviz.so
#5  0x00007ffff7dfb058 in rviz::VisualizationManager::addDisplay(rviz::Display*, bool) () at /opt/ros/noetic/lib/librviz.so
#6  0x00007ffff7dfb7e8 in rviz::VisualizationManager::createDisplay(QString const&, QString const&, bool) () at /opt/ros/noetic/lib/librviz.so
#7  0x00005555556908a3 in viewpanel::enableCamera(bool) (this=0x555558d1ec00, isUSB=false)
at /home/eyalr/arbe-gitlab/arberos_1.3/src/arbe_phoenix_radar_driver/arbe_gui/src/arbe_gui_main/viewpanel.cpp:4445
#8  0x000055555561a253 in MainWindow::enableCamera() (this=0x7fffffffb8d0)
at /home/eyalr/arbe-gitlab/arberos_1.3/src/arbe_phoenix_radar_driver/arbe_gui/src/arbe_gui_main/mainwindow.cpp:1240
#9  0x0000555555615c40 in MainWindow::MainWindow() (this=0x7fffffffb8d0)
at /home/eyalr/arbe-gitlab/arberos_1.3/src/arbe_phoenix_radar_driver/arbe_gui/src/arbe_gui_main/mainwindow.cpp:659
#10 0x00005555555a456c in main(int, char**) (argc=1, argv=0x7fffffffc308)
at /home/eyalr/arbe-gitlab/arberos_1.3/src/arbe_phoenix_radar_driver/arbe_gui/src/arbe_gui_main/main.cpp:1970
(gdb)

Could you please try the latest version 1.14.25, building from source or from the ROS testing repo?

Unfortunately, there was a bug introduced, which was not noticed during the testing phase.

Thank you for confirming!
Do you have any estimation of when 1.14.25 is going to hit the next Ubuntu update.
We will try building from sources to confirm the fix
Thanks again for you prompt response!

Usually, sync intervals are within 1-2 months. Until then, I suggest to install the debian package from the ROS testing repo.

Thank you!
I updated ros-noetic-rviz from ros-testing to 1.14.25 using the suggested method and the issue is resolved.
Have a great weekend,
Eyal


integrates checkstyle plugin to check against Google Java Codestyle

Description
Maven build now checks code using Googles Java code style. Refactored codebase for matching that codestyle.
Related Issue
Fixes https://github.com/adobe/S3Mock/issues/70
Tasks

[x] I have signed the CLA.
[x] I have written tests and verified that they fail without my change.

@agudian: Please review, merge + rebase.

udpated (+squashed). Please verify additional broken interfaces.

I've just played around with it a bit:

I've set consoleOutput to false to not repeat the output that would be reported properly (colored and with shortened paths) anyway.
Use the built-in google_checks.xml and deactivated the rule AbbreviationAsWordInName (doesn't require us to maintain a customized google_checks.xml file, but would allow names like getMMORPGScore() -  we might want to just keep an eye on that in PRs)
build-config module can be removed again
configured the execution part in the parent-pom, so the other poms only need to add the following:

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-checkstyle-plugin</artifactId>
      </plugin>
    </plugins>
  </build>```

Here's what I had in the parent-pom:
```xml
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-checkstyle-plugin</artifactId>
          <version>3.0.0</version>
          <configuration>
            <consoleOutput>false</consoleOutput>
            <failOnViolation>true</failOnViolation>
            <violationSeverity>info</violationSeverity>
            <includeTestSourceDirectory>true</includeTestSourceDirectory>
            <violationIgnore>google_checks.xml</configLocation>
            <violationIgnore>AbbreviationAsWordInName</violationIgnore>
          </configuration>
          <dependencies>
            <dependency>
              <groupId>com.puppycrawl.tools</groupId>
              <artifactId>checkstyle</artifactId>
              <version>${checkstyle.version}</version>
            </dependency>
          </dependencies>
          <executions>
            <execution>
              <id>check-style</id>
              <phase>validate</phase>
              <goals>
                <goal>check</goal>
              </goals>
            </execution>
          </executions>

WDYT?

Please verify additional broken interfaces.

Looks all good 👍

WDYT?

I found that option for configuring checkstyle-pljugin but: What about IDE integration? IDEA (here Checkstyle-Plugin) does not pick this configuration as a rule so you'll always have that mismatch here :/. You can't even configure custom suppressions for build-in configurations. So, that's the whole thing here.
We can simply drop that idea of having checks IDE-integrated with the benefit of not having a custom config. Thoughts?


Update banned.pug

https://github.com/RiversideRocks/web-riverside/pull/25
I don't know why it made a separate pull req, i remember forking the repo and make the 2 commits and THEN making the pull req


Minimize to system tray and others

Hi
I would like to suggest couple things because it is not necessary that the IG:dm can be visible at taskbar all the time. http://prntscr.com/jcojev
Also, some of menu items can be removed or hide some times like the Window menu is not necessary when window is not in fullscreen mode on Windows OS or other OS's. http://prntscr.com/jcojp2
Also resizing the users panel will be awesome! http://prntscr.com/jcoj0o

Also, keeping the last session active and pasting image to input box from clipboard can be usefull.


Upvote / Downvote questions

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Server: I added multiple integration tests (Spring) related to the features
[x] Server: I added @PreAuthorize and check the course groups for all new REST Calls (security)
[x] Server: I implemented the changes with a good performance and prevented too many database calls
[x] Server: I documented the Java code using JavaDoc style.
[x] Client: I added multiple integration tests (Jest) related to the features
[x] Client: I documented the TypeScript code using JSDoc style.
[x] Client: I added multiple screenshots/screencasts of my UI changes

Motivation and Context

Currently students have no possibility to show that they are having the same question or to rate questions in general.
Description

Students can upvote / downvote questions to express (dis-)agreement.
Questions are ordered by their votes.
Steps for Testing

Log in to Artemis
(1a. Enable questions and answers for your test course if not already enabled)
Navigate to an exercise or lecture
Create multiple questions
Upvote / Downvote questions in any order
Check if sorting and representation works correctly

Screenshots

default:

upvoted:

downvoted:

Are we sure that we want to have downvotes? This might make students hesitate to ask any questions since they could be afraid of being downvoted heavily. I get the idea of using downvoting as a mechanism to hide inappropriate questions but then this would need to be solved differently than it is right now (and in that case deleting the question all together might even be the preferred cause of action). An alternative solution would be to allow downvoting but to not expose any score of less than zero, meaning zero points is the floor that will be visibily shown (and returned from the server). That way downvoting still has a purpose but no one is publicly humiliated by having his or her name next to 100 downvotes.

Yes, I thought about this point a lot, too. I think deleting that question automatically is a bit too harsh and should only be done manually by a tutor or instructor.
I like the idea of capping the votes at zero to prevent humiliation. @krusche What do you think about this idea?

From a technical perspective, the voting is very easy to manipulate at the moment since it is not enforced that one user can only cast a single vote per question. It would be pretty easy to inspect the HTTP request that happens on upvoting and then making the same request again this time with a value of 10,000 to give that many upvotes or downvotes to a question. I can definitely see this happening when a whole bunch of CS students discover this new feature and some of them wonder if they can tinker with it.

I discussed this point with @krusche and we decided to start with this implementation since we do not assume any malicious intent by the students. (They could also upvote / downvote a question unlimited times if they clear their browser cache). But if this becomes a problem, I have the very secure (but also more complicated and performance affecting) implementation planned.

Yes, I thought about this point a lot, too. I think deleting that question automatically is a bit too harsh and should only be done manually by a tutor or instructor.
I like the idea of capping the votes at zero to prevent humiliation. @krusche What do you think about this idea?

I was not suggesting any sort of automatic deletion, that would indeed be pretty drastic.

I discussed this point with @krusche and we decided to start with this implementation since we do not assume any malicious intent by the students. (They could also upvote / downvote a question unlimited times if they clear their browser cache).

I imagined that this was probably a conscious decision to keep the implementation effort reasonably low for a first version of the feature. Maybe we could at least add a boundary check to the server endpoint so that only deltas of ±2 are allowed? That way it's at least a little harder to completely screw with the votes for a question. Of course students could still send hundreds of requests to achieve the same effect but I think that sets a higher bar since that would basically be a spamming attack which is more severe than taking advantage of a loophole.

@madwau I now added the check at the endpoint and the displayed votes are also now capped at zero. They can't be downvoted if at zero, only a downvote can be reset if negative or at zero.
Thanks again for the suggestions! 😄

@madwau I now added the check at the endpoint and the displayed votes are also now capped at zero. They can't be downvoted if at zero, only a downvote can be reset if negative or at zero.
Thanks again for the suggestions!

Thanks for the adaptations! For the zero flooring, I was thinking more of a server-side solution so that negative scores are not exposed to users at all.

The functionality works as intended, the only thing that I'm not really sure about is if this is intended: There seems to be a different behaviour if you remove an upvote or downvote, this was a bit confusing for me, especially as the vote count is limited as 0.

That behaviour is only around the 0 value, which is intended since the votes are capped at 0

Hey Filip, I am not sure but I think I found a bugs🐇
When I up vote from 0 it turns to 2 directly and skips 1 as shown in the screen cast
@HanyaElhashemy thank you for testing 😃
In the screen cast it seems to be intended behaviour. Since you take back your downvote and upvote it simultaneously the total should increase by 2


Adding new monitor crashes app

This bug does't have anything to do with the Audio/Alert service. With the entire audio/alert service removed, this bug persists.

Do you mean adding the first monitor, or adding a second or more monitors?

The Second, sorry I wasn't clear

@AaronStGeorge @rlank We can leave this open for now. We have a fall back on forcing portrait mode. If we decide to go that route it closes basically all of these bugs

Forcing portrate mode fixes this bug


Update release to next minor 1.9.0

I was just thinking, can we change
Move CI and IDE metadata processing at execution time -> Capture CI and IDE metadata at execution time to allow more configuration cache hits


added slider to accomplishments

Description
This PR fixes the Our Accomplishments section by adding the sliders allowing users to easily navigate through the accomplishments. The swiper component is used to do the same.

Notes for Reviewers

@amisha-shrivastava some branch conflicts are there. Kindly resolve it....

@Divesh2003 I've resolved the conflict. Kindly review it.

Kindly add level labels on this PR @Divesh2003


stub. DeleteTable(tablename) doesnot works...

the stub.DeleteTable(tablename) is not working..
I get error on chaincode terminal as :  21:57:47.240 [shim] DEBU : [mycc]Sending RANGE_QUERY_STATE
2016/06/14 21:57:47 transport: http2Client.notifyError got notified that the client transport was broken EOF.
21:57:47.392 [shim] ERRO : Received error from server: rpc error: code = 13 desc = "transport is closing", ending chaincode stream
And error on the peer terminal as : panic: runtime error: invalid memory address or nil pointer dereference
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x62c861]
goroutine 30 [running]:
panic(0xd5afc0, 0xc820010100)
/opt/go/src/runtime/panic.go:464 +0x3e6
github.com/hyperledger/fabric/core/chaincode.(*Handler).handleRangeQueryState.func1.1(0xc820284080, 0xc82012b8b0, 0xc820043d80)
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/handler.go:651 +0x261
panic(0xd5afc0, 0xc820010100)
/opt/go/src/runtime/panic.go:426 +0x4e9
github.com/hyperledger/fabric/core/chaincode.(*Handler).handleRangeQueryState.func1(0xc820284080, 0xc82012b8b0)
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/handler.go:700 +0xbef
created by github.com/hyperledger/fabric/core/chaincode.(*Handler).handleRangeQueryState
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/handler.go:736 +0x3f
hyperledger@hj-ctocto2126:/opt/gopath/src/github.com/hyperledger/fabric/peer$

Could you include your chaincode or test case? I just checked the existing test case at https://github.com/hyperledger/fabric/blob/master/bddtests/chaincode/go/table/table.go#L268 and did not see the same failure. Thanks.

I have created PR #1833 to fix the nil pointer panic.
@adecaro The root problem is that there is an error decrypting the data when confidentiality is enabled. I found https://github.com/hyperledger/fabric/issues/1049. Is the correct way to resolve this to merge PR #1373?

Yes @srderson this is my chaincode...
business_directory_sample.txt

Could you also send me your core.yaml so I can see what settings you have enabled? Also, if you try again with the latest master and PR #1833 it will likely give a more helpful error message.


@ngtools/webpack build failing after update from 1.9.8 to 1.10.1

Versions
ngtools/webpack 1.10.1
webpack 3.11.0
node 9.6.1
macOS 10.13

Repro steps
Building webpack project (not using @angular/cli, only @ngtools/webpack) in AOT
Observed behavior
ERROR in ./src/app/desktop/app.module.desktop.ngfactory.js
Module not found: Error: Can't resolve '/Users/lukaszsamson/myapp/src/node_modules/@angular/animations' in '/Users/lukaszsamson/myapp/src/app/desktop'
 @ ./src/app/desktop/app.module.desktop.ngfactory.js 64:10-40
 @ ./src/main.browser.desktop.ts
 @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:3000 ./src/main.browser.desktop.ts

ERROR in ./src/app/desktop/app.module.desktop.ngfactory.js
Module not found: Error: Can't resolve '/Users/lukaszsamson/myapp/src/node_modules/@angular/animations/browser' in '/Users/lukaszsamson/myapp/src/app/desktop'
 @ ./src/app/desktop/app.module.desktop.ngfactory.js 33:10-48
 @ ./src/main.browser.desktop.ts
 @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:3000 ./src/main.browser.desktop.ts

ERROR in ./node_modules/ngx-dropdown/index.js
Module not found: Error: Can't resolve '/Users/lukaszsamson/myapp/src/node_modules/@angular/common' in '/Users/lukaszsamson/myapp/node_modules/ngx-dropdown'
 @ ./node_modules/ngx-dropdown/index.js 12:15-41
 @ ./src/app/desktop/app.module.desktop.ngfactory.js
 @ ./src/main.browser.desktop.ts
 @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:3000 ./src/main.browser.desktop.ts
...

Every module resolution fails.
Desired behavior
clean build as on 1.6.8

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

To reproduce this issue

clone angular-starter repo
yarn
npm start
on v 1.10.0 compiles succesfully
update @ngtools/webpack to 1.10.1
yarn
npm start
on v 1.10.1 compile fails

gdi2290/angular-starter#1971

@filipesilva ping

#9727 looks similar to this issue

It seems to be related to paths that look like:
import { SomethingService } from 'app/core/something.service.ts'; (Will break)
import { SomethingService } from '../core/something.service.ts'; (Will NOT break)

This issue seems to be linked to "paths" in tsconfig.json
{
  // ...
  "compilerOptions": {
    "paths": {
      "@angular/*": ["node_modules/@angular/*"]
    }
  }

  // ...
}

And as mentioned by @larssn it is linked to version > 1.9.x

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


Add Google Analytics Event tracking to User Registration form

In order to track where how new users find the OSF, it would be helpful to set up event tracking on the ajax form creating a new account - much like the event tracking we use on the buttons on the slide in footer.
User conversion was tracked using a goal setting in analytics previously - but this broke when registration was changed at the end of March.

@saradbowman I assume you have the event tracking code you'd like embedded in form, yes? Thanks.

Yep! I think everything you would need is here (but can provide ID number if that's needed) https://developers.google.com/analytics/devguides/collection/analyticsjs/events

@kmjungersen Can you knock this one out fairly quickly? Thanks.

Absolutely - I'm looking into it now. :rocket:

Fixed with PR #2669, so this issue can be closed 😎

Thank you!!!
On Fri, May 8, 2015 at 11:08 AM, Kurtis Jungersen<EMAIL_ADDRESS>wrote:

Fixed with PR #2669
https://github.com/CenterForOpenScience/osf.io/pull/2669, so this issue
can be closed [image: 😎]
—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/osf.io/issues/2593#issuecomment-100265867
.


Default operator.id annotation

I've noticed that if we run an Integration without the camel.apache.org/operator.id annotation, then, the behavior is to use the namespace operator where this is stored. However, when we kamel run/bind, there is a forced setting to camel.apache.org/operator.id: camel-k that may interfere when a user is interested in getting the Integration back (ie -o yaml) and later pushing the Integration to the cluster in any given namespace. Should we remove the presence of default operator.id: camel-k? is there any particular reason why we want to leave it there @christophd ?

I've noticed that if we run an Integration without the camel.apache.org/operator.id annotation, then, the behavior is to use the namespace operator where this is stored

I do not think that this is the current behavior. From what I know all resources that are missing the camel.apache.org/operator.id annotation should only be handled by the default global operator (id=camel-k). The namespace where the default operator and the integration resource are located in is not relevant in this scenario.
So in my eyes using the default annotation camel.apache.org/operator.id: camel-k and skipping the annotation completely should have the same effect. Both resources should be handled by the default operator (id=camel-k) regardless of the namespace.
Does that make sense?

Interesting. Then there must be some bug because I installed 2 operators in separate namespace (development and production) none is global. Later I'm running an Integration without operator.id annotation in both namespaces and both operators are reconciling the Integration correctly in each of their namespaces. Notice that I'm very happy to have this behavior, reason why I was wondering why we need to explicitly include the annotation when we want to default it to the namespace on which we install the Integration. Also, this behavior simplify the promote subcommand across namespaces.

IMO in future support for non global operators should be dropped and everything should be controlled by the operator id only.

Nope. And even if it was there, I'd expect that both Integration were reconciled by the supposed global one. In my case, the operator installed in the given namespace seem to control properly the Integration installed in its namespaces (again, I am very happy with this behavior).

I installed camel-k via the latest helm chart (using helm template through ArgoCD).
The operator picks up intergrations without the camel.apache.org/operator.id: camel-k annotation as expected. But when i deploy an integration with that annotation explicitly set the operator ignores it.
As understand this discussion it shouldn't make a difference.


Kill and Scale may throw an error if task-id's provided are bigger then instances

If currently a application is in deployment but the healthchecks did not pass yet. Then I will have a overcapacity of instances * 2 for example.
What actually is supposed to happen is that in that case the instances are at least 0. Or filter out the tasks with the old version and only subtract the new ones.
This is the output I do get.
{
  "message": "Object is not valid",
  "details": [
    {
      "path": "/apps(0)/instances",
      "errors": [
        "got -1, expected 0 or more"
      ]
    }
  ]
}

Here is a short gif which hopefully explains the issue:

The problem: you're trying to update an already old app version (2 old tasks). This fails the validation with:
ERROR Failed validation because Set(GroupViolation(MapLike(AppDefinition(/webserver,Some(./web-server.py $PORT0),List(),None,Map(),-2,Resources(1.0,128.0,0.0,0),,Set(),List(FetchUri(file:///Users/adukhovniy/scripts/util/web-server.py,false,false,false,None)),List(),List(PortDefinition(10000,tcp,None,Map())),false,BackoffStrategy(1 second,3600 seconds,1.15),None,Set(MarathonHttpHealthCheck(300 seconds,10 seconds,20 seconds,3,Some(ByIndex(0)),None,Some(/test),HTTP,false)),List(),None,Set(),UpgradeStrategy(1.0,1.0),Map(),Set(),None,FullVersionInfo(2016-12-22T13:17:45.801Z,2016-12-22T13:17:45.801Z,2016-12-22T13:17:39.785Z),None,Map(),UnreachableStrategy(15 minutes,7 days),YoungestFirst)),Seq contains elements, which are not valid.,Some(apps),Set(GroupViolation(AppDefinition(/webserver,Some(./web-server.py $PORT0),List(),None,Map(),-2,Resources(1.0,128.0,0.0,0),,Set(),List(FetchUri(file:///Users/adukhovniy/scripts/util/web-server.py,false,false,false,None)),List(),List(PortDefinition(10000,tcp,None,Map())),false,BackoffStrategy(1 second,3600 seconds,1.15),None,Set(MarathonHttpHealthCheck(300 seconds,10 seconds,20 seconds,3,Some(ByIndex(0)),None,Some(/test),HTTP,false)),List(),None,Set(),UpgradeStrategy(1.0,1.0),Map(),Set(),None,FullVersionInfo(2016-12-22T13:17:45.801Z,2016-12-22T13:17:45.801Z,2016-12-22T13:17:39.785Z),None,Map(),UnreachableStrategy(15 minutes,7 days),YoungestFirst),not valid,Some((0)),Set(RuleViolation(-2,got -2, expected 0 or more,Some(instances)))))))
One solution could be for UI to forbid "Scale and kill" for "old" tasks. Or we might provide a better response error message?

https://phabricator.mesosphere.com/D383


Recipe/3rd party integration

Description / Motivation

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update (non-breaking change; modified files are limited to the /data directory or other markdown files)

Checklist:

[ ] I have read the Contributing guide.
[ ] My code/comments/docs fully adhere to the Code of Conduct.
[ ] My change is a code change.
[ ] My change is a documentation change and there are NO other updates required.
[ ] My change has new or updated images which are stored in the /public/images folder that need to be migrated to Sitecore DAM

@Chris1415 - there are merge conflicts on this PR, can they be fixed so we can review?


Microsoft Edge support

According to this article, it should be trivial to convert an extension that works in Chrome over to Edge. uBlock Origin has some instructions on how to do development.

Since Edge will be based on chrome, I think this will not be an issue?

Correct, it should work great in Chromium-based Edge. The only thing left to figure out would be whether we can officially publish it in Microsoft's extension store versus having people install it through Chrome Web Store.