bug: old api-key version for New-Relic service

Now new-relic service uses old api key: https://github.com/argoproj/notifications-engine/blob/master/pkg/services/newrelic.go (line 153) req.Header.Set("Api-Key", s.opts.ApiKey)
According to documentation it should be req.Header.Set("X-Api-Key", s.opts.ApiKey) (https://docs.newrelic.com/docs/apis/rest-api-v2/get-started/introduction-new-relic-rest-api-v2/)
Now newrelic module doesn't create deployment markers. Same request with curl works (because of type of header).

#181

Do we know if this has been included in a recent ArgoCD release?

@lancehudson looks like not. I'm still getting the same error:
time="2023-08-17T08:55:08Z" level=error msg="Failed to notify recipient {newrelic APP_ID} defined in resource argocd/my-app: Post \"api.newrelic.com/v2/applications/APP_ID/deployments.json\": unsupported protocol scheme \"\"" resource=argocd/my-app


Display error when parsing a .strings file returns empty results (#1747)

Display error messages when the parser can not read the strings file or the file contains empty data.
Related to this issue: #1747, fixed as discussed with @mfurtak in issue #5956

Hi @mihaibabusca - this is looking pretty good! 👍
The CI failure is due to a test which is now failing. The problem is that it expects UI.error to be called because of the bad strings file input, but now we're calling it another extra time because of our new check.
Can you add
expect(Frameit::UI).to receive(:error).with(/Empty parsing result for .*translations.bad.strings/)

to that expect group. To get the test passing?
Thanks!

Thank you @mfurtak for great guidance!

Thanks for a great contribution! 🚀


Firefox the date picker drop downs are obscured

Firefox 41.0.1 on Mac and also found on Windows.
.picker__select--month, .picker__select--year
Has a height set as 2em which breaks firefox.
I'm going to remove or set height:auto to get around this on our app.

I think update padding: 0.3em is better. IMHO, Changing height is always more dangerous.


feat: add Show AST button

This should not be merged before the compiler side can handle the request. I'm currently working on the compiler side of this issue and by faking a few things I have been able to test that this commit should work.

Screenshot?

Currently when right clicking in the editor window we have a button Show AST. I don't know how many kinds of ASTs we should be able to show (https://github.com/flix/flix/pull/5559#issuecomment-1453439816) but we could change this to either use sub-menus (like the peek option in the screenshot) or prompt the user for an input?

Now we have a sub-menu where the specific sub-menu items decides which phase is parsed to the showAst method. (In the screenshot below I'm using a print statement in the showAst method printing the phase argument)

Looks good. Then we just need the compiler side.

Once https://github.com/flix/flix/pull/5565 is merged, I believe this should be possible to test.

I think this works. At least both the id and the phase is sent to the request on the compiler side, and in turn the showAst method is called with the correct phase argument. I’m not sure what is supposed to happened when the items are clicked, are we not still faking the behavior of the showAst method?

Then we should open a new Window/tag with the content that is returned from the compiler.

I wasn’t completely sure what you ment by a new Window/tag, but I have made something. I realised I wasn’t sending the result back from the server to the client, so I changed the response handler. On the client side I made it open a new window with the result from the request.
(Result of clicking the Typed Ast button in the previous image)

Looks good, I would say!
What happens if you click twice, you get two windows right?

Also, I made the sub-menu only be visible when editing a flix document, I wasn't sure if this was the intention?

That seems reasonable.

Correct, if you go back to the flix document and clicks the Show Ast button again it opens another window.

@mR4smussen the ast for the whole program might be very large (30k lines without treeshaking) so we need to filter the ast somehow. We could either pass in a file to the ast request or pass in a namespace. What do you think would be nicest/easiest to add in vscode?

I think I can get access to the path of the file currently open. Otherwise, I can prompt the user for a file (like the image below). Here I can make the workstation path be filled in automatically, so it would be equivalent to them giving us a relative path. (I’m not completely sure what the namespace would be)

The path stored in the sourcelocation is the relative path, so receiving that would be easy to filter

Can we send the URI of the currently opened file?
Then we can do the filtering server side.

I believe this latest commit should include the URI in the request. Obviously, this also requires the compiler side to parse the URI for it to work.
For my test I got this to work with the changes below, but you might know of a better way.
In https://github.com/flix/flix/blob/master/main/src/ca/uwaterloo/flix/api/lsp/Request.scala#L392-L397:

In https://github.com/flix/flix/blob/master/main/src/ca/uwaterloo/flix/api/lsp/LanguageServer.scala#L315-L319:

In https://github.com/flix/flix/blob/master/main/src/ca/uwaterloo/flix/api/lsp/provider/ShowAstProvider.scala#L35:

@JonathanStarup Will you incorporate these changes on the server side?


Critical bug 0.4.13: ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 80 from PyObject

0.4.12 worked fine on Ubuntu 20.04 with system Python 3.8 .
Now I updated to 0.4.13 and I get the following error:
$ sudo pip3 install scikit-sparse
Collecting scikit-sparse
  Downloading scikit-sparse-0.4.13.tar.gz (214 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 214.2/214.2 KB 5.9 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: scipy>=0.19 in /usr/lib/python3/dist-packages (from scikit-sparse) (1.3.3)
Requirement already satisfied: numpy>=1.13.3 in /usr/lib/python3/dist-packages (from scikit-sparse) (1.17.4)
Building wheels for collected packages: scikit-sparse
  Building wheel for scikit-sparse (pyproject.toml) ... done
  Created wheel for scikit-sparse: filename=scikit_sparse-0.4.13-cp38-cp38-linux_x86_64.whl size=864027 sha256=c5bbef228037d2b47e04f1025070692d4e60c8452b9ee0c72f3855284a9c31e1
  Stored in directory: /root/.cache/pip/wheels/00/e1/84/ba747998155c4e45213588b132dffa319bbd67ac6dedab7b2f
Successfully built scikit-sparse
Installing collected packages: scikit-sparse
Successfully installed scikit-sparse-0.4.13
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
WARNING: You are using pip version 22.0.4; however, version 24.0 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
$ python3
Python 3.8.10 (default, Nov 22 2023, 10:22:35)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from sksparse.cholmod import cholesky_AAt
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "sksparse/cholmod.pyx", line 1, in init sksparse.cholmod
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 80 from PyObject

My environment:
$ apt-cache policy libsuitesparse-dev
libsuitesparse-dev:
  Installed: 1:5.7.1+dfsg-2
  Candidate: 1:5.7.1+dfsg-2
  Version table:
 *** 1:5.7.1+dfsg-2 500
        500 http://cz.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status
$ apt-cache policy python3-scipy
python3-scipy:
  Installed: 1.3.3-3build1
  Candidate: 1.3.3-3build1
  Version table:
 *** 1.3.3-3build1 500
        500 http://cz.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
        100 /var/lib/dpkg/status
$ apt-cache policy python3-numpy
python3-numpy:
  Installed: 1:1.17.4-5ubuntu3.1
  Candidate: 1:1.17.4-5ubuntu3.1
  Version table:
 *** 1:1.17.4-5ubuntu3.1 500
        500 http://cz.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:1.17.4-5ubuntu3 500
        500 http://cz.archive.ubuntu.com/ubuntu focal/main amd64 Packages

$ pip3 show numpy
Name: numpy
Version: 1.17.4
Summary: NumPy is the fundamental package for array computing with Python.
Home-page: https://www.numpy.org
Author: Travis E. Oliphant et al.
Author-email:
License: BSD
Location: /usr/lib/python3/dist-packages
Requires:
Required-by: h5py, Keras-Applications, Keras-Preprocessing, opt-einsum, pylas, scikit-sparse, scikit-umfpack, tensorboard, tensorflow, torchvision
$ pip3 show scipy
Name: scipy
Version: 1.3.3
Summary: SciPy: Scientific Library for Python
Home-page: https://www.scipy.org
Author:
Author-email:
License: BSD
Location: /usr/lib/python3/dist-packages
Requires:
Required-by: scikit-sparse, scikit-umfpack

According to https://stackoverflow.com/a/75150938/1076564 it seems a piece built by Numpy 1.20+ sneaked into the wheel while I'm using Numpy 1.17. No idea where it got from...

I was able to reproduce the issue in a Docker container. Bumping up to numpy==1.23.5 seems to be sufficient. Guess the requirements removed in #105 were there for a reason..


PostCSS support

Hello,
I'm using this extension to support PostCSS, but it doesn't work with Prettier. Can you add PostCSS in language mode?
Extension: https://marketplace.visualstudio.com/items?itemName=mhmadhamster.postcss-language
Thank you!

Is #116 ok for you?

@CiGit yes!

Can someone share their config they used to get PostCss formatting with prettier please?
I am using this https://marketplace.visualstudio.com/items?itemName=mhmadhamster.postcss-language for syntax support.
Do you need to name the files .pcss extension or do you map css to postcss type?
"files.associations": {
  "*.css": "postcss"
}

I have tried this too
  "[postcss]": {
    "editor.formatOnSave": true
  },

No luck...

@stewartduffy I'm also using vscode and struggling getting it to work with postcss files.

Language are now provided by prettier. postcss is currently not part of what prettier gives us.
There is a PR on prettier's side for exactly that


targetSdkVersion 28 does not work for 'http'

Https urls work well on targetSdkVersion 28. But it does not work for http.
Commit here:
https://github.com/lipangit/JiaoZiVideoPlayer/commit/4ce3377b90f46f4618ba7172b6a3d4edfce666e5#diff-39e7d8c00954e920b98e7636f0ac30b2R9
Error trace
2018-09-10 12:39:42.236 31471-31489/cn.jzvd.demo D/NetworkSecurityConfig: No Network Security Config specified, using platform default
2018-09-10 12:40:12.417 31471-31491/cn.jzvd.demo E/MediaPlayerNative: error (1, -2147483648)
2018-09-10 12:40:12.418 31471-31550/cn.jzvd.demo E/MediaPlayer: Error (1,-2147483648)
2018-09-10 12:40:12.419 31471-31471/cn.jzvd.demo E/JZVD: onError 1 - -2147483648 [209585138]
2018-09-10 12:40:12.419 31471-31471/cn.jzvd.demo I/JZVD: onStateError  [209585138]
2018-09-10 12:40:12.430 31471-31550/cn.jzvd.demo V/MediaPlayer: resetDrmState:  mDrmInfo=null mDrmProvisioningThread=null mPrepareDrmInProgress=false mActiveDrmScheme=false
2018-09-10 12:40:12.430 31471-31550/cn.jzvd.demo V/MediaPlayer: cleanDrmObj: mDrmObj=null mDrmSessionId=null

The sample video url is http://jzvd.nathen.cn/c6e3dc12a1154626b3476d9bf3bd7266/6b56c5f0dc31428083757a45764763b0-5287d2089db37e62345123a1be272f8b.mp4, and it is not secure.
So we need the android:networkSecurityConfig="@xml/jz_network_security_config" in the AndroidManifest.xml of the app module.
<application
    android:name=".ApplicationDemo"
    android:allowBackup="false"
    android:icon="@mipmap/ic_launcher"
    android:label="@string/app_name"
    android:networkSecurityConfig="@xml/jz_network_security_config"
    android:theme="@style/AppTheme">
    <!-- ... -->
</application>

See: https://developer.android.google.cn/training/articles/security-config

The default configuration for apps targeting Android 9 (API level 28) and higher is as follows:
<base-config cleartextTrafficPermitted="false">
    <trust-anchors>
        <certificates src="system" />
    </trust-anchors>
</base-config>

The default configuration for apps targeting Android 7.0 (API level 24) to Android 8.1 (API level 27) is as follows:
<base-config cleartextTrafficPermitted="true">
    <trust-anchors>
        <certificates src="system" />
    </trust-anchors>
</base-config>

The default configuration for apps targeting Android 6.0 (API level 23) and lower is as follows:
<base-config cleartextTrafficPermitted="true">
    <trust-anchors>
        <certificates src="system" />
        <certificates src="user" />
    </trust-anchors>
</base-config>

So, we may need one /res/xml/jz_network_security_config.xml:
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
    <base-config cleartextTrafficPermitted="true" />
</network-security-config>

You mean demo can not play on phone with api 28?

For reference, that plaintext traffic is blocked by default for apps targeting API version 28 is documented at:
https://developer.android.com/about/versions/pie/android-9.0-changes-28#framework-security-changes

If your app targets Android 9 or higher, the isCleartextTrafficPermitted() method returns false by default. If your app needs to enable cleartext for specific domains, you must explicitly set cleartextTrafficPermitted to true for those domains in your app's Network Security Configuration.

Is it right?
I do not have phone with api 28, you can help to test.

@imknown Could you please make a pr, that very greatful

aaa


[feature] Make GetAuthorizer try CLI creds (or add new uber GetAuthorizer)

Hi. I'd like sops to work better with Azure out-of-the-box by removing the user or operators need to  muck with AZURE_AUTH_MODE. For quick background, sops uses KV on-the-fly to encrpyt/decrypt secret files. Currently, they have code that handles AZURE_AUTH_MODE, but I'd rather Autorest/azure hid that entirely, if possible.
Suggestion 1
Extend GetAuthorizer to fallback to CLI auth after trying the various envvar/cred options and after failing to hit MSI.
Suggestion 2
Create GetAuthorizerExt (please don't call it that :smile:) that does the extra fallback to CLI.
From what I was told at the time, MSI was partly to get devs to stop putting creds on their machine, and this functionality would allow tools like sops to even more conveniently solve the problem by automatically doing the right thing.
As-is right now, they default to cli authentication for sops (as that makes sense in the developer workflow), however, I am preparing to release something that uses sops and sops-nix on Azure with KV and I'm having to go in and manually set AZURE_AUTH_MODE="msi" to get it to work in the ideal "seamless but still secure" way.

After re-checking, it looks like sops has its own copy of GetAuthorizer that (doesn't auto-try MSI but does) auto-fall back to CLI creds, so they're sort of already doing this anyway.
I'd be curious what others think, if there's value in having something in the SDK that "just works" on a devbox and in prod, but maybe it's not that important if others can already compose their own GetAuthorizer?

Have you seen auth.NewAuthorizerFromEnvironment()
https://github.com/Azure/go-autorest/blob/master/autorest/azure/auth/auth.go#L65
It will attempt to authenticate using several authentication mechanisms.  Sadly, it doesn't try CLI at present.  We could add auth.NewAuthorizerFromCLI() to the list of mechanisms for it to try (unclear why we didn't do this in the beginning, will look into it).  Would this work for you?

Hi Joel, it would be a great solution, IMO to have another high-level single-entry point that do, as you're describing:

Class auth methods (env vars, client password, client secret cert, etc)
Then try MSI
Then try local CLI.

That's what I attempted to do myself, but ran into #542 and decided I don't have time to dig in quite that much... Thanks for looking!

Our solution for this in azidentity is the DefaultAzureCredential which does exactly what you enumerate.
Given that you can compose this today, and that we azidentity is what we're moving towards, we won't be fixing this in go-autorest.


TFs about wheels do not exist. so rviz can't show me about robot_description

Please provide the following information:

OS: Ubuntu 20.04
ROS Distro: Galactic
Built from source or installed:
Package version: (if from repository, give version from sudo dpkg -s ros-$ROS_VERSION-turtlebot4-PACKAGE_WITH_ISSUE, if from source, give commit hash)

Expected behaviour
When i run "ros2 launch turtlebot4_viz view_robot.launch.py", rviz2 show me the perfect TF and robot_description.
Actual behaviour
But i can't see perfect TF and robot_description. There are no frame and TF about "left_wheel", "right_wheel", "wheel_drop_left", "wheel_drop_right"
what should i do...? :(
termial shows me this error
Warning: Invalid frame ID "wheel_drop_left" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.5/src/buffer_core.cpp
To Reproduce
Provide the steps to reproduce:

run something
launch something else
see the error

Other notes
Add anything else you thing is important.

Does it look like this https://github.com/iRobotEducation/create3_sim/issues/125?

appearing errors are same with mine but it seems like wheels exist.
in my situation, TF of wheels and wheel_drops are not exist from the beginning.
and when i run "tf2_tools view_frames.py" too
should i edit URDF?

You shouldn't need to make any changes to the URDF. Is this coming from a robot or simulation?

Sorry, I don't understand your comment...

I didn't set about DDS. The reason why rviz can't show tf about wheels.
but i still have some problems. maybe i can fix as  refer to your comment. thank  you ;)


Setting up GitHub token doesn't reflect validity

When using -github-info, if I put a completely random string next to it, it will still say
"GitHub auth was successful. Use -github-issue-number with the number of the issue you'd like to comment on."

Ways to fix:
try let octokit = new MyOctokit({ auth: githubToken }); with the token

@dtemir, would you like to work on this?

@louisefindlay23 on it :)

Is this now working, @dtemir after merging #70 since you said the two were related?


feat: nakamoto modal and network updates

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


Error: Undefined Fn mime_content_type()

Hi,
I was successfully able to setup Koel on my server(centos-release-6-7.el6.centos.12.3.x86_64) however it fails to play a song and gives me error in my console as Failed to load resource: the server responded with a status of 500 (Internal Server Error) with a link. When I open the link in a different page, I get this error FatalErrorException in SongController.php line 23:
Call to undefined function App\Http\Controllers\API\mime_content_type() . Similar error was found in laravel.log file as well. The file which I'm trying to play is a mp3.
==========================================================================
Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue:

[x] You have read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting
[x] The issue has not been reported before
[x] This is not a "how to install on Windows" or "why is my npm messed up" question
[x] You're a cool person

All checked? Now also make your issue

[ ] Is associated with a version. Or better yet, a commit.
[ ] Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?)
[ ] Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know)
[x] Is in English, 因为我不说中文。

mime_content_type() has been deprecated. I'll remove this in the next version of Koel. Meanwhile you can enable mime_magic in your php.ini file for the functionality.

Oh, actually the function is not deprecated anymore, and is still well supported by PHP 7. I'll suggest you to look at your PHP installation then.

If this is still a concern I'd take a look if you have the php fileinfo shared extension installed (the mime_content_type function lives there).

Still in talks my hosting provider, mime_content_type and fileinfo  both are disabled on my server.


[rv_dm] Writing read-only section of debug memory does not return an error

The top-level test csr_mem_rw_with_rand_reset with build-seed<PHONE_NUMBER> and seed<PHONE_NUMBER> writes the debug memory at address 0x0001_04e0, expects an error response, but gets an okay response and fails. According to rv_dm.hjson, the first 4 KiB of debug ROM are read-only from SW. However, as this top-level test shows, writing this read-only section does not return an error. The write changes the debug memory.
To resolve this, should the debug memory return an error in this case? Or should the test not expect an error response?

@msfschaffner @GregAC

Seems like a duplicate of https://github.com/lowRISC/opentitan/issues/10468.

writing this read-only section does not return an error. The write changes the debug memory.

Have you actually observed the write altering the memory?

I believe I know why this is happening - let me take a closer look (errors associated with TL-UL windows have to be generated outside the reg_top instance, and this may not be implemented correctly).

This issue has been fixed in https://github.com/lowRISC/opentitan/pull/15169.


Extract the model from the view logic

This introduces a UI regression, where entering a value in a collapsable component, collapses the component rather than keeping it open.

Merging and created issue https://github.com/LD4P/sinopia_editor/issues/900 to note the regression.


Fix for Loop properties revindex and revindex0 still wrong in Jinja2 2.10 #794

Fix for issues: #794 #751
The approach to set length param is costly and should be avoided. only if someone expects the iterator length should the cost be borne.
Added test cases to validate rendering and LoopContext behavior

Issue & Fix summary

The LoopContext length property implementation was incorrect & suboptimal which in turn messed up the values of revindex revindex0
Fixed LoopContext length property implementation
Added testcases


store/sidecar: minio-go missing support for ap-east-1

What happened
Bucket operations to ap-east-1 fail with:
The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.

This is because minio-go doesn't have the s3 dual stack endpoint so it defaults to s3.dualstack.us-east-1.amazonaws.com.
I've created a PR that adds the endpoint. This ticket is for information and hopefully to create new release sooner than later that includes that change.
https://github.com/minio/minio-go/pull/1105
@bwplotka

Makes sense to me :+1: We need to update minio-go dep then. We can do it in small PR and essentially you can use Thanos master, right? (:

https://github.com/improbable-eng/thanos/pull/1140
I updated go.mod but wasn't sure about mod.sum.


Atomic write detection breaks event ordering.

When atomic write detection is enabled, as is the default, "unlink" events are slightly delayed. If an "add" event would occur in that time, a "change" event is emitted instead immediately, and the pending "unlink" event is discarded. This small delay causes the order of events to become incoherent.
Versions
Chokidar 4.0.1
Node.js v22.4.1
Windows 10.0.19045.4894
Example
I didn't produce full examples because #1361 compounds with this, making it harder to demonstrate. And because I want to file this issue before I go to bed 😅. Hopefully this is clear enough.
Suppose we have folder A which contains files 1, 2, 3 and so on. We then run the following:
await rm("A", { recursive: true });
writeFile("B", "...");

In this situation, despite being guaranteed to happen last, the creation of file B would be detected while deletions are still pending, so chokidar would emit:
("add", "B")
("unlink", "A/1")
("unlink", "A/2")
("unlink", "A/3")
...

That is to say, chokidar's output contradicts two logical assumptions about the code:

all deletions occur before any write
all operations on A occur before operations on B

Preserving order would likely require keeping a buffer of all events that are detected, and pausing all emissions whenever an "unlink" is encountered too early to determine if it is part of an atomic write or not. Definitely not a trivial change.

that’s the whole point of atomic.
rm a.js
mv a.js.swp a.js

😕? I'm not sure if you read or understood what I wrote. I know what atomic writes are, and their detection is working.
But the way atomic change detection is implemented in chokidar messes with the order in which events are emitted, even those unrelated to atomic writes. If I delete an output directory before triggering a rebuild of a project, I certainly don't expect the file watcher to emit the deletions AFTER the addition of new files.
For what is worth, using the watcher npm package in place of chokidar fixed all those issues for me.

If the behavior is the same as in v3, I wouldn’t change it for now. Too complicated. PRs welcome.

It's also possible the file system just emits them this way
If you ever get chance, please do make a repro in V3 and V4

It seems fsPromises.rm can actually resolve before unlink events are fired, at least when running recursively. 🙃
Using fsPromises.readdir and fsPromises.unlink manually instead seems to have solved a bunch of issues I had.
TL;DR chokidar's default behavior is reasonable and the issue was elsewhere, sorry for the noise.


Gem cleanup

Moved items from Gemfile that were in .gemspec.
Fixed reek dependence on Ruby 2.1 or higher
Changed yard-cucumber to be directly from github
added ruby and gem version dependence in the gemspec.
expanded travis-ci to test jvm combinations, as well as more ruby versions.

Coverage remained the same at 100.0% when pulling 853284d107815dcc055dbcf66c99f83c142b8cc8 on gem_cleanup into eb024ed6bb2d5850ae624e10b988f0f0170a0fdd on master.

Coverage remained the same at 100.0% when pulling 22b128343160e47c3562341cf14d22f40852baf7 on gem_cleanup into eb024ed6bb2d5850ae624e10b988f0f0170a0fdd on master.

Coverage remained the same at 100.0% when pulling 22b128343160e47c3562341cf14d22f40852baf7 on gem_cleanup into eb024ed6bb2d5850ae624e10b988f0f0170a0fdd on master.

Coverage remained the same at 100.0% when pulling 2e1dc8fcf3e941ec52f877ba6841912f4c6616d8 on gem_cleanup into eb024ed6bb2d5850ae624e10b988f0f0170a0fdd on master.


feat:  avm/res/container-service/managed-cluster add additional outbound types

Description
Adding two new outbound types to the existing AKS module.

Hey @JPEasier could you review this PR as the co-owner? :)

@ilhaan could you add a successful run from your branch to the PR description? then i will merge the PR :)

@ilhaan - Please take a look at the above comments :)

@ilhaan could you add a successful run from your branch to the PR description? then i will merge the PR :)

@JPEasier Added the status badge and started a new pipeline run.

@JPEasier the module is failing these test in the main branch as well: https://github.com/ilhaan/bicep-registry-modules/actions/runs/8210379598

@JPEasier pipeline is now passing


School Search Box

The School Search Box will allow the user to enter in keywords and filter the search results by what the search algorithm determines are the most appropriate results. These results will be the schools that have been previously added by admins. This can be supported by libraries or programmed from scratch.

This will be on the home page.

@danielogen Hi,I'm interested in this task. Can you assign it to me?


WS Standard usage

Hi,
I need some clarification.
The table states:
License with SA/Subscription | VMs and cores granted | How they can be used
WS Datacenter (16 cores or a 2-proc L) | Up to two VMs and up to 16 cores | Run virtual machines both on premises and in Azure
WS Standard (16 cores or a 2-proc L) | Up to two VMs and up to 16 cores | Run virtual machines either on premises or in Azure
My question is:
when having the proper amount of Windows Server Standard licenses with Software Assurance enabled, can I use Windows Server Datacenter license in Azure or do I need to deploy Windows Server Standard Edition in Azure?
Thank you!
Best regards, David

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

ID: 90e335dd-0bc5-a7e3-650b-e3dd1823176b
Version Independent ID: 18f34ef3-ff61-0473-a64b-ac5a64dbe1d7
Content: Azure Hybrid Benefit for Windows Server
Content Source: WindowsServerDocs/get-started/azure-hybrid-benefit.md
Product: windows-server
Technology: getting-started
GitHub Login: @eross-msft
Microsoft Alias: chrisrin

Hi, any update on this?

#assign:IngridAtMicrosoft

Hi @DavidD-SE - if you have Standard edition licenses with active Software Assurance on a relevant agreement, you can use either Standard or Datacenter in Azure VMs. In the Commercial Licensing Terms you can find this by visiting https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/all, selecting the Program, and under the section Azure Hybrid Benefit it states "Customer may use Standard or Datacenter software". I have added that to the article as part of some wider changes, which should be visible later today.
#please-close


Sovereign Clouds / Azure US Government

The documentation says that support for Azure US Government is coming soon but in other closed issues it looks like it is supported now. What is the official answer? I tested the action and it worked so I am guessing it is supported now.

Closing this issue as we are tracking the same in https://github.com/Azure/login/issues/298


Use rake task to run mini test

What
Change action to use rake task. So it run all tests.
@simplybusiness/application-tooling

I like rake for two reason one it is preety much standard for runnint minitest and  it has default test task which provides lots of options to run tests like verbose etc which would be helpful


 Travis build picked this up

@hughesj :  I'm guessing we may just be running out of threads during our "partition" tests which spawn a set of threads, based on this which is what I'm seeing, just a "Killed" in the middle of the Travis build log.
But you specifically mentioned a "rogue comma".  Did you have a reason for thinking this was something else?
Otherwise, thinking we might just disable Travis rather than having to worry about limiting # of threads.

For now, pushed https://github.com/WASdev/standards.jsr352.tck/commit/196bf3c6e7ce21a291edeba87be4a323c646f7a2 to only run test-compile in travis.

Additionally, we decided to skip the tests in the Travis build of the RI in 099a5fd


return hidden states of all layers

For Bert like model:
model = TransformerWrapper(
    num_tokens = 20000,
    max_seq_len = 1024,
    attn_layers = Decoder(
        dim = 512,
        depth = 12,
        heads = 8
    )
).cuda()

Is it possible to return hidden states from all layers similar to Huggingface BertModel when setting output_hidden_states=True (Huggingface).
I tried
x = torch.randint(0, 256, (1, 1024)).cuda()
logit, intermediates = model(x, return_intermediates=True)

But I believe intermediates.hiddens is not exactly the hidden states for each layer.

what is the hidden states by their definition? is it the input going into each transformer block? (or each attention / feedforward block) ?

import torch
from x_transformers import TransformerWrapper, Decoder

model = TransformerWrapper(
    num_tokens = 20000,
    max_seq_len = 1024,
    attn_layers = Decoder(
        dim = 512,
        depth = 12,
        heads = 8
    )
)

x = torch.randint(0, 256, (1, 1024))

x, intermediates = model(x, return_intermediates = True) # (1, 1024, 20000)

intermediates.layer_hiddens # length 25 - 24 blocks (attention, feedforward alternating) + output of last block

@zhiaos let me know if layer_hiddens has what you need
i can clean up the naming at a later version

Thanks @lucidrains!
Based on their documentation,  hidden states represent the outputs of each layer  -- 12 * (Attention+Residual&Norm + FF + Residual&Norm) . So there are 12 of them.  I think the layer_hiddens returns 12 *[ Attention+Residual&Norm,  FF+Residual&Norm] + x,   x is the same as the last of 24 in typical case.

@zhiaos got it, yea, i need to return after each block, since this framework supports arbitrary ordering of attention and feedforwards (say a f f a f f)

@lucidrains  so it is not possible to get the output of each block based on current implementation?

@zhiaos the outputs before the prenorm residual is added? are you sure that's what you want?

@zhiaos the layer_hiddens are the inputs to each block, which should be the output of the previous block (+ residual)


Missing SharePoint

SharePoint commands would be quite nice ..

⚠ Idea migrated from UserVoice
Created By: Marcel
Created On: 2017/08/10 06:19:04 +0000
Votes at Migration: 1
Supporters at Migration: 1

Related to the PowerShell Module Browser.

This is the link: https://docs.microsoft.com/en-us/powershell/module/?term=sharepoint


Update dependencies to latest versions

Coverage remained the same at 92.228% when pulling c9ad1cba8f3b76ace6b0534c8f4c431ff347c87b on feature/update-dependencies-to-lastest-versions into 470a79220ad119fadd15e1a8a9694d4667d509ae on master.


Low Disparity data rate

I successfully viewed the camera on my odroid XUV4 board runnning Ubuntu 14.04. The video stream was good using guvcview. But, after running the stereo.launch file, the left,right and disparity data obtained were very slow and lagging a lot. It published data at a rate of around 4Hz, while the camera was running at 30fps. Can you please suggest a solution to this issue?

That's interesting. Can you provide us un output of top -b and ps -auswww when you run stereo?, we're afraid that the XUV4 does not have
enough power to process them
--
◉ Kei Okada
On Fri, Jun 17, 2016 at 10:06 PM, shobhit9618<EMAIL_ADDRESS>wrote:

I successfully viewed the camera on my odroid XUV4 board runnning Ubuntu
14.04. The video stream was good using guvcview. But, after running the
stereo.launch file, the left,right and disparity data obtained were very
slow and lagging a lot. It published data at a rate of around 4Hz, while
the camera was running at 30fps. Can you please suggest a solution to this
issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/longjie/ps4eye/issues/24, or mute the thread
https://github.com/notifications/unsubscribe/AAeG3AHHP8MmF2j93dHha6RKtn5t4kY_ks5qMpvngaJpZM4I4Vtx
.


Concurrent access to state on local FS by multiple supervisors

Hi,
we are running storm-mesos cluster and occassionaly workers die or are "lost" in mesos. When this happens it often coincides with errors in logs related to supervisors local state.
By looking at the storm code it seems this might be caused by the way how multiple supervisor processes access the local state in the same directory via VersionedStore.
For example: https://github.com/apache/storm/blob/master/storm-core/src/clj/backtype/storm/daemon/supervisor.clj#L434
I've filled the bug report on Storm JIRA, but it seems this issue is more with the way storm-mesos launches supervisors as Storm states that multiple supervisors should not run on the same storm-local dir (https://issues.apache.org/jira/browse/STORM-1043).
Some examples of exeptions:

java.lang.RuntimeException: Version already exists or data already exists
at backtype.storm.utils.VersionedStore.createVersion(VersionedStore.java:85) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.utils.VersionedStore.createVersion(VersionedStore.java:79) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.utils.LocalState.persist(LocalState.java:101) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.utils.LocalState.put(LocalState.java:82) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.utils.LocalState.put(LocalState.java:76) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.daemon.supervisor$mk_synchronize_supervisor$this7400.invoke(supervisor.clj:382) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.event$event_manager$fn2625.invoke(event.clj:40) ~[storm-core-0.9.5.jar:0.9.5]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]

java.io.FileNotFoundException: File '/var/lib/storm/supervisor/localstate/1441034838231' does not exist
at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:299) ~[commons-io-2.4.jar:2.4]
at org.apache.commons.io.FileUtils.readFileToByteArray(FileUtils.java:1763) ~[commons-io-2.4.jar:2.4]
at backtype.storm.utils.LocalState.deserializeLatestVersion(LocalState.java:61) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.utils.LocalState.snapshot(LocalState.java:47) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.utils.LocalState.get(LocalState.java:72) ~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.daemon.supervisor$sync_processes.invoke(supervisor.clj:234) ~[storm-core-0.9.5.jar:0.9.5]
at clojure.lang.AFn.applyToHelper(AFn.java:161) [clojure-1.5.1.jar:na]
at clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na]
at clojure.core$apply.invoke(core.clj:619) ~[clojure-1.5.1.jar:na]
at clojure.core$partial$fn4190.doInvoke(core.clj:2396) ~[clojure-1.5.1.jar:na]
at clojure.lang.RestFn.invoke(RestFn.java:397) ~[clojure-1.5.1.jar:na]
at backtype.storm.event$event_manager$fn2625.invoke(event.clj:40) ~[storm-core-0.9.5.jar:0.9.5]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]

hey @ernisv : thanks for reporting your issue.  Fortunately, there is a trivial workaround:  don't set storm.local.dir in the storm config for your supervisors, and then storm-local will be instantiated in the Mesos Executor's sandbox, so it will not conflict.   You may find it necessary to set storm.home to wherever the storm bits are living on the mesos-agent hosts (formerly mesos-slave hosts).  That is highly dependent on your environment though.

Brilliant! Just changing storm.local.dir to relative path indeed made each supervisor to use dir inside mesos sandbox.
Thanks a lot for the suggestion, Erik.

@ernisv : glad it worked for you!


⚠ Bofrost.es has degraded performance

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

HTTP code: 200
Response time: 1588 ms

Resolved: Bofrost.es performance has improved in f3db180 after 9 minutes.


feature request: slice up patch function

Hi,
As some may know I am experimenting with running Cycle in WebWorkers. It works pretty well, but the main bottleneck is the postMessage API. Right now I am transmitting something i call vDOMSON, representing the entire component vTree, this is then mapped recursively to snabbdom/h which in turn is passed to the patch function.
To reduce I/O I thought it could be neat to have patch in two parts, so instead of transmitting the entire vDOMSON, I can just transmit a list of mutations. The pre-patch could be run in the sub-thread, while the resulting mutations could be transferred to and applied in the main thread.
I know it sounds kind of insane.

Perhaps best that you write an initial proof of concept PR.

@aronallen Patched trees as 🚰 streams.
I don't think it sounds insane at all and if you have further thoughts about this, I'd love to hear them.
By the way, just to make sure I'm on the same page, what do you mean by I/O in this case?

@jbucaran by I/O i mean the overhead in the communication between the web worker thread and the main thread.

I really hope this happens!  I have been looking for a way to have diff
and patch split up for a long time for that exact usecase.
Aron Nyborg Allen wrote:

Hi,
As some may know I am experimenting with running Cycle in WebWorkers.
It works pretty well, but the main bottleneck is the postMessage API.
Right now I am transmitting something i call vDOMSON, representing the
entire component vTree, this is then mapped recursively to
|snabbdom/h| which in turn is passed to the patch function.
To reduce I/O I thought it could be neat to have patch in two parts,
so instead of transmitting the entire vDOMSON, I can just transmit a
list of mutations. The pre-patch could be run in the sub-thread, while
the resulting mutations could be applied in the main thread.
I know it sounds kind of insane.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/snabbdom/snabbdom/issues/231, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIRy02NhFYlIl9Zvz2pzEylNbVgGkrMrks5rTgpAgaJpZM4Lm2HZ.

@aronallen check out snabbdom's DOMAPI. It's essentially a wrapper for anything that actually touches the real DOM. Perhaps you can send serializations that refer to calls of those methods.
interface DOMAPI {
  createElement: (tagName: any) => HTMLElement;
  createElementNS: (namespaceURI: string, qualifiedName: string) => Element;
  createTextNode: (text: string) => Text;
  insertBefore: (parentNode: Node, newNode: Node, referenceNode: Node | null) => void;
  removeChild: (node: Node, child: Node) => void;
  appendChild: (node: Node, child: Node) => void;
  parentNode: (node: Node) => Node;
  nextSibling: (node: Node) => Node;
  tagName: (elm: Element) => string;
  setTextContent: (node: Node, text: string | null) => void;
}

The cool thing about snabbdom is that you can pass an instance of domAPI to init().
I know some of these methods take Element as argument, but this is actually vnode.elm, so it could be that vnode.elm on the web worker side is just some kind of virtual pointer (a string, if nothing else) to an element on the DOM.
Just an idea...

@staltz thanks for the hint.
If the DOM API only received virtual DOM nodes, and expected virtual DOM nodes it would be quite easy to port. I guess I could write a shallow implementation of <Node> in the webworker context.

@aronallen

If the DOM API only received virtual DOM nodes, and expected virtual DOM nodes

Just my two cents. The domapi is nothing more than an object exposing the functions in staltz post above. Snabbdom will use the ones in document.* by default, but the idea is you can provide your an object with your own implementation of the functions.
var snabbdom = require('snabbdom');
var patch = snabbdom.init([
  require('snabbdom/modules/class').default,
  /*...*/
  require('snabbdom/modules/style').default,
  require('snabbdom/modules/eventlisteners').default,
], { myDOMAPI);

@jbucaran yes, it is pretty neat. I think I can put something together.

This may open the way for multi-threaded UI in snabbdom itself? Is snabbdom ever a bottleneck in that regard? Even if used correctly?

@mightyiam I don't know, my idea of using web workers is more about security by providing an encapsulated execution context. Since everything needs to be patched in the main thread anyway, I wouldn't imagine there to be any performance benefits. So there might be performance benefits, but I doubt it.

There is some performance benefit.
If diffing takes a long time, the ui/scrolling won't jank if it's done
in a worker thread. See
http://www.pocketjavascript.com/blog/2015/11/23/introducing-pokedex-org
Aron Nyborg Allen wrote:

@mightyiam https://github.com/mightyiam I don't know, my idea of
using web workers is more about security by providing an encapsulated
execution context. Since everything needs to be patched in the main
thread anyway, I wouldn't imagine there to be any performance
benefits. So there might be performance benefits, but I doubt it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/snabbdom/snabbdom/issues/231#issuecomment-274183549,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIRy09bOBclJGIqk_33bXXhqinJ_Sor2ks5rUSXugaJpZM4Lm2HZ.

@aronallen Found about ReactDOM Stream and remembered this for some reason.

@whmountains have u seen passive event listeners https://developers.google.com/web/updates/2016/06/passive-event-listeners

@aronallen title change OK with you?


Add head-only formula for neatvi

neatvi is a small ex/vi-like editor that supports UTF8 as well as bidirectional
text.
By default, make creates an executable called vi, but since this is still
a work in progress rather than a full replacement for vi or vim, I've
written the formula to install it as neatvi. That way users can play with it
without a larger commitment.

Merged in https://github.com/Homebrew/homebrew-head-only/commit/1f698f0345e805709b9ffe33a409d0d98d0c8679. Thanks @telemachus!
Tiny note: Commit messages for new formula in head-only should be something like neatvi (new formula), Thanks!


Update GeneralTab.tsx

Category

One of: Other Legacy troubleshooting information

Overview

Clearing the cache is no long required/available; and therefor should be removed from the troubleshooting tab.

Issue Number (if applicable)

NIL, from discord comment: https://discord.com/channels/972958686051962910/972958689155764326/1174219683864522782

New Vars (if applicable)

No new variables, but I'm not actually sure where troubleshooting is stored' it should be cleaned as well.

Alternative

If local caching will return in the future, just comment out the line temporary.

@Tagaishi can you also remove the translations related to cache ? We don’t need them anymore.


Invariant Violation: requireNativeComponent: "RNSpinkit" was not found in the UIManager.

"react-native": "0.74.3",
"react-native-animated-spinkit": "^1.5.2",
"react-native-dynamic-search-bar": "^2.0.2",
"@freakycoder/react-native-bounceable": "^1.0.3",

This error doesn't come from this library, looks like you're using react-native-spinkit somewhere in your project.


Test with redis-rb 4.0.0 RC1

I just released redis-rb 4.0.0 RC1.
Can you please test against it and report back?
Thank you!

@djanowski Sure, we would love to! 👍

@djanowski I've made sure we are testing on redis-rb 4.0.0 RC1 as well (https://github.com/fetlife/rollout/issues/108) ... everything looks fine!
I am also going to try 4.0.0 RC1 with our rails monolith's specs where we extensively using Redis and I will let if I discover any problems!

@djanowski I see some incompatibility with https://github.com/resque/redis-namespace due fact they use redis (>= 3.0.4, ~> 3.0) version constraint

@djanowski I see you already opened issue in their repo, never mind :D

See this discussion about redis-namespace. Thanks.


refactor(frontend): enforce use of interface instead of type

Motivation
We want to add the ES lint rule of consistent-type-definitions, that enforces the usage of interface instead of type.
Changes

Add new rule to ESlint configs.
Fix related new issues.

Tests
It worked: it flagged new issues that we solved.

Replicated it in the upcoming lib 👉 https://github.com/dfinity/eslint-config-oisy-wallet/pull/2
Please review it.


[BugFix] merge pushdown predicate to cte

What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #14100
Problem Summary(Required) ：

CTE consumer should remain all pushdown predicates for non-inline execute mode.
Checklist:

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

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

Bugfix cherry-pick branch check:

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

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

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/PushDownPredicateCTEConsumeRule.java
2
2
100.00%
[]

@Mergify backport branch-2.2 branch-2.3 branch-2.4 branch-2.5

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/PushDownPredicateCTEConsumeRule.java
2
2
100.00%
[]

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.5 --ignore_conflicts=false

@Mergify backport branch-2.5

@Mergify backport branch-2.1


Changing preview_paths doesn't detect previews

Describe the bug
Changing preview_paths doesn't seem to work...
To Reproduce
  config.lookbook.preview_paths = ['app/comp_previews']

with a preview class at app/comp_previews
class AvatarPreview < Lookbook::Preview
  def default
    render Avatar::Component.new(Administrator.first)
  end
end

Expected behavior
AvatarPreview should show in the UI, but doesn't.
Version numbers
Please complete the following information:

Lookbook: 2.0.0.beta3
Rails: 7.0.4
Ruby: 3.2.1
Phlex: 1.4.0

Hey @joelmoss, you are doing a great job of digging into the beta and finding all the bugs :-) Much appreciated, I just hope it's not too frustrating for you.
So I've just tried testing locally and I can't seem to recreate the issue (yet). Just a few things to check - what is the filename of the AvatarPreview class? And I assume you are not seeing any errors in the terminal? Does this same preview class work correctly when you drop it into the default previews directory?
Also, do you think you could paste in a dump of the debug data JSON from the menu in the top right of the header?

That should hopefully help me get a little further with figuring out what's going on here - or at least rule out a few things.
Thanks for your help :-)

First, changing preview_paths to a different value does actually work.
But...
Assigning a new value to preview_paths does not override the default of test/components/previews
config.lookbook.preview_paths = ['app/components']

Even though I re-assigned it above, preview_paths still always includes test/components/previews:
"preview_paths": [
      "test/components/previews",
      "app/components"
]

Adding a preview path that is not local does not detect previews
config.lookbook.preview_paths << '/some/absolute/path/app/components'

My use case for this is that I have a Rails engine that exposes components for sharing.

Debug dump...
{
  "version": "2.0.0.beta.3",
  "env": "development",
  "config": {
    "project_name": "HT London Lookbook",
    "preview_paths": [
      "test/components/previews",
      "app/components",
      "/Users/joelmoss/dev/clients/harleytherapy/hue/app/components"
    ],
    "preview_display_options": {},
    "preview_controller": "Lookbook::PreviewController",
    "preview_template": "lookbook/previews/preview",
    "preview_inspector": {
      "main_panels": ["preview", "output"],
      "drawer_panels": ["source", "notes", "params", "*"]
    },
    "preview_embeds": {
      "enabled": true,
      "policy": "SAMEORIGIN",
      "panels": false,
      "actions": [],
      "scenarios": [],
      "display_option_controls": true
    },
    "preview_layout": "component_preview",
    "preview_disable_action_view_annotations": true,
    "preview_type_default": "view_component",
    "preview_sort_scenarios": false,
    "page_controller": "Lookbook::PageController",
    "page_route": "pages",
    "page_paths": ["test/components/docs"],
    "page_extensions": ["html.*", "md.*"],
    "page_options": {},
    "markdown_options": {
      "tables": true,
      "fenced_code_blocks": true,
      "disable_indented_code_blocks": true,
      "strikethrough": true,
      "highlight": true,
      "with_toc_data": true,
      "lax_spacing": true
    },
    "highlighter_options": {
      "theme": "github",
      "dark": false
    },
    "component_paths": ["app/views", "app/components"],
    "reload_on_change": true,
    "live_updates": true,
    "listen_paths": [],
    "listen_extensions": ["rb", "html.*"],
    "ui_theme": "indigo",
    "ui_theme_overrides": {},
    "ui_favicon": true,
    "log_level": 2,
    "log_use_rails_logger": true,
    "debug_menu": true,
    "experimental_features": false,
    "links": {
      "docs": "https://v2.lookbook.build",
      "demo": "https://v2-demo.lookbook.build",
      "repo": "https://github.com/ViewComponent/lookbook/tree/v2"
    },
    "using_view_component": false,
    "dependencies": {
      "actioncable": true,
      "listen": true,
      "view_component": false
    },
    "panels": {
      "preview": {
        "label": "Preview",
        "hotkey": "v",
        "disabled": false,
        "show": true,
        "copy": null,
        "locals": {},
        "partial": "lookbook/inspector/panels/preview",
        "name": "preview"
      },
      "output": {
        "label": "HTML",
        "hotkey": "h",
        "disabled": false,
        "show": true,
        "copy": null,
        "locals": {},
        "partial": "lookbook/inspector/panels/output",
        "name": "output"
      },
      "source": {
        "label": "Source",
        "hotkey": "s",
        "disabled": false,
        "show": true,
        "copy": "#<Proc:0x00000001083cf880 (eval):1 (lambda)>",
        "locals": {},
        "partial": "lookbook/inspector/panels/source",
        "name": "source"
      },
      "notes": {
        "label": "Notes",
        "hotkey": "n",
        "disabled": "#<Proc:0x00000001083cf3f8 (eval):1 (lambda)>",
        "show": true,
        "copy": null,
        "locals": {},
        "partial": "lookbook/inspector/panels/notes",
        "name": "notes"
      },
      "params": {
        "label": "Params",
        "hotkey": "p",
        "disabled": "#<Proc:0x00000001083ceef8 (eval):1 (lambda)>",
        "show": true,
        "copy": null,
        "locals": {},
        "partial": "lookbook/inspector/panels/params",
        "name": "params"
      }
    },
    "inputs": {
      "select": {
        "name": "select",
        "partial": "lookbook/inspector/inputs/select",
        "options": {
          "opts": {}
        }
      },
      "textarea": {
        "name": "textarea",
        "partial": "lookbook/inspector/inputs/textarea",
        "options": {
          "opts": {}
        }
      },
      "toggle": {
        "name": "toggle",
        "partial": "lookbook/inspector/inputs/toggle",
        "options": {
          "opts": {}
        }
      },
      "color": {
        "name": "color",
        "partial": "lookbook/inspector/inputs/color",
        "options": {
          "opts": {}
        }
      },
      "range": {
        "name": "range",
        "partial": "lookbook/inspector/inputs/range",
        "options": {
          "opts": {}
        }
      },
      "text": {
        "name": "text",
        "partial": "lookbook/inspector/inputs/text",
        "options": {
          "opts": {}
        }
      },
      "email": {
        "name": "email",
        "partial": "lookbook/inspector/inputs/text",
        "options": {
          "opts": {}
        }
      },
      "number": {
        "name": "number",
        "partial": "lookbook/inspector/inputs/text",
        "options": {
          "opts": {}
        }
      },
      "tel": {
        "name": "tel",
        "partial": "lookbook/inspector/inputs/text",
        "options": {
          "opts": {}
        }
      },
      "url": {
        "name": "url",
        "partial": "lookbook/inspector/inputs/text",
        "options": {
          "opts": {}
        }
      },
      "date": {
        "name": "date",
        "partial": "lookbook/inspector/inputs/text",
        "options": {
          "opts": {}
        }
      },
      "datetime_local": {
        "name": "datetime_local",
        "partial": "lookbook/inspector/inputs/text",
        "options": {
          "opts": {}
        }
      }
    },
    "tags": {
      "hidden": {
        "name": "hidden",
        "label": "Hidden",
        "options": {
          "label": "Hidden status",
          "opts": {}
        }
      },
      "label": {
        "name": "label",
        "label": "Label",
        "options": {
          "label": "Label",
          "opts": {}
        }
      },
      "display": {
        "name": "display",
        "label": "Display",
        "options": {
          "label": "Display",
          "opts": {}
        }
      },
      "priority": {
        "name": "priority",
        "label": "Priority",
        "options": {
          "label": "Priority",
          "opts": {}
        }
      },
      "id": {
        "name": "id",
        "label": "Id",
        "options": {
          "label": "Id",
          "opts": {}
        }
      },
      "component": {
        "name": "component",
        "label": "Component",
        "options": {
          "label": "Component",
          "opts": {}
        }
      },
      "renders": {
        "name": "renders",
        "label": "Renders",
        "options": {
          "label": "Renders",
          "opts": {}
        }
      },
      "param": {
        "name": "param",
        "label": "Param",
        "options": {
          "label": "Param",
          "opts": {}
        }
      },
      "logical_path": {
        "name": "logical_path",
        "label": "Logical Path",
        "options": {
          "label": "Logical Path",
          "opts": {}
        }
      },
      "source": {
        "name": "source",
        "label": "Source",
        "options": {
          "label": "Source file",
          "opts": {}
        }
      }
    }
  }
}

@joelmoss ah.. yes so that is actually the intended behaviour - test/components/previews is the default ViewComponent preview path and I vaguely remember wanting to prevent people from accidentally overwriting it. However looking at it afresh now it makes things pretty confusing (especially now that Lookbook isn't just for ViewComponent anymore) and it really should be possible to overwrite that paths array completely if you want to.
I'll try and get a fix/update out as soon as I can that changes this behaviour.

good to know.
what about the second point ?

Adding a preview path that is not local does not detect previews

@joelmoss the fix for the array issue is now out in the beta.4 release. But I somehow missed your second point entirely! Apolgies. I'll look into it and let you know when I've made any progress.

Hey @joelmoss - I've just released v2.0.0.beta.5 that should hopefully address the 'not-local' preview paths issue you are running into. Let me know how you get on whenever you have a chance to try it out.

ok, so I just upgraded to beta7, and now Lookbook says there are no previews at all. Rolling back to beta4 works. Beta5 and later does not.
The only Lookbook config I set are...
config.lookbook.project_name = 'HT Hue Lookbook'
config.lookbook.component_paths = ['app/components']
config.lookbook.preview_paths = ['app/components']
config.lookbook.preview_layout = 'component_preview'

Debug data...
{
  "version": "2.0.0.beta.7",
  "env": "development",
  "config": {
    "project_name": "HT Hue Lookbook",
    "project_logo": null,
    "preview_paths": [
      "app/components"
    ],
    "preview_display_options": {
    },
    "preview_controller": "Lookbook::PreviewController",
    "preview_template": "lookbook/previews/preview",
    "preview_inspector": {
      "main_panels": [
        "preview",
        "output"
      ],
      "drawer_panels": [
        "source",
        "notes",
        "params",
        "*"
      ]
    },
    "preview_embeds": {
      "enabled": true,
      "policy": "SAMEORIGIN",
      "panels": false,
      "actions": [

      ],
      "scenarios": [

      ],
      "display_option_controls": true
    },
    "preview_layout": "component_preview",
    "preview_disable_action_view_annotations": true,
    "preview_type_default": "view_component",
    "preview_sort_scenarios": false,
    "page_controller": "Lookbook::PageController",
    "page_route": "pages",
    "page_paths": [
      "test/components/docs"
    ],
    "page_extensions": [
      "html.*",
      "md.*"
    ],
    "page_options": {
    },
    "markdown_options": {
      "tables": true,
      "fenced_code_blocks": true,
      "disable_indented_code_blocks": true,
      "strikethrough": true,
      "highlight": true,
      "with_toc_data": true,
      "lax_spacing": true
    },
    "highlighter_options": {
      "theme": "github",
      "dark": false
    },
    "component_paths": [
      "app/components"
    ],
    "reload_on_change": true,
    "live_updates": true,
    "listen_paths": [

    ],
    "listen_extensions": [
      "rb",
      "html.*"
    ],
    "ui_theme": "indigo",
    "ui_theme_overrides": {
    },
    "ui_favicon": true,
    "log_level": 2,
    "log_use_rails_logger": true,
    "debug_menu": true,
    "experimental_features": false,
    "links": {
      "docs": "https://v2.lookbook.build",
      "demo": "https://v2-demo.lookbook.build",
      "repo": "https://github.com/ViewComponent/lookbook/tree/v2"
    },
    "using_view_component": false,
    "dependencies": {
      "actioncable": true,
      "listen": true,
      "view_component": false
    },
    "panels": {
    },
    "inputs": {
    },
    "tags": {
    }
  }
}

A little more digging, and it appears that Lookbook doesn't like single line nested class names.
So this works...
module Therapist
  module Accreditations
    class Preview < Lookbook::Preview
      def default
        render Component.new
      end
    end
  end
end

But this does not...
module Therapist::Accreditations
  class Preview < Lookbook::Preview
    def default
      render Component.new
    end
  end
end

But the above is only for beta4. Beta7 just doesn't show any previews from anywhere.

@joelmoss So I've tried to recreate this but I haven't yet been able to. I suspect it's something to do with autoloading (as that it what I added to beta.5 to try to fix the 'non local' paths issue you were seeing.
Lookbook itself just leans on the autoloading provided by Rails so nested modules using both formats should work fine (assuming any constant scope resolution within the modules is implemented correctly). So if it isn't it would again point to some issue with autoloading the preview classes.
However it's quite hard to debug without being able to replicate locally and without knowing the exact file structure of your app/components directories. I know it's a big ask but would you be able to rails new a minimal app that demonstrates the problems you are seeing? Then I could use that as a basis for some tests to make sure that we get this sorted once and for all.
Failing that could you give me a little more info as to the file and folder structure of your components/previews directory? I notice you are no longer pulling in components from the separate Rails gem, have you pulled those into your main app now?
Appreciate all your help with this as always. Hopefully we'll get there in the end!

@joelmoss Also, just to double check - I assume you are not seeing any error messages in the console about uninitialized constants or suchlike?

Hey @joelmoss as I haven't heard back for a while I'm going to close this issue now. But please feel free to reopen if you are still having issues and could give me a little more info on any of the above, thanks.


Cityscapes dataset training failed.

Hi, thank you for sharing your great work.
I attempted to train the Cityscapes dataset from scratch, but encountered an error.
I followed your instructions to prepare the dataset. However, when I run train.py, the following error occurs:
File "/home/pc/anaconda3/envs/SPIdepth/lib/python3.8/site-packages/torch/nn/modules/linear.py", line 116, in forward
return F.linear(input, self.weight, self.bias)
RuntimeError: mat1 and mat2 shapes cannot be multiplied (16x5376 and 7168x2048)
It seems that the input and output channels of the first Linear function in self.bins_regressor don't match.
File "depth_decoder_QTR.py", line 49, in forward
y = self.bins_regressor(summarys.view(bs, Q*E))
Could you provide guidance on how to resolve this issue?
Thank you in advance!

Hi @minoTrey, thanks for your interest in the model!
I recommend checking out this file to ensure all your parameters are correctly set. If you're looking to train the H version from scratch, you can use the ./args_files/hisfog/kitti/cvnXt_H_320x1024.txt file as a starting point, and just adjust the dataset paths accordingly.

It works! Thank you very much.
By the way, I wonder how the GT Depth of the Cityscapes dataset was generated. Is it the same as the data in disparity_sequence_trainvaltest.zip?
Thank you in advance!

Thank you very much!

I'm happy to assist! If you find the model useful, I would really appreciate it if you could give our GitHub repo an upvote.

@minoTrey, I'm happy to assist! If you find the model useful, I would really appreciate it if you could give our GitHub repo an upvote.


Support trying to parse <citation> as <element-citation>

A significant part of the Pubmed Central JATS corpus has <citation> elements that would be complete if they were parsed as <element-citation> -- that is, a simple find-and-replace is sufficient to make the document validate against Dar. It would be nice if Texture supported this.

Hi @axfelix would you be able to provide an example of what you mean? I don't understand, sorry!

Sure. Right now, Texture only explicitly supports documents with citations encoded as <element-citation> rather than <citation>, I assume because the latter can be messier. However, if you look at the PubMed Central JATS corpus (one of the largest ones around, surely), many documents have citations encoded as regular <citation> but whose child elements are complete if the tag were simply find-and-replaced to <element-citation>, so I think we should be able to support these on import.

Ah, thanks, got you now. We discussed this a fair bit at the last meet up. This is a requirement for Erudit.
For eLife we have structured references and are very strict, but for people using this as a post production tool they cannot control the input and so need flexibility for string references.

Hi @axfelix
Do you mean <mixed-citation> instead of <citation>?
The <citation> element is not available in JATS.


Is there a way to set the "allowed paths" for the server via a bacalhau config set setting?

Desired request:
bacalhau config set compute.allowedDirectories=["/foo", "/bar:rw"]
bacalhau serve

The right config name is node.allowlistedlocalpaths, but @frrist what is the right way to set such complex config types? This also applies to the newly introduced -c flag that accept key/value pairs of configs.

huh - totally missed that.


Add Keka - The macOS file archiver.

Project URL
https://github.com/aonez/Keka
Category
Productivity
Description
Add Keka - The macOS file archiver.
Why it should be included to Awesome macOS open source applications  (optional)
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Appropriate language icon(s) added if applicable
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

  Generated by :no_entry_sign: Danger


fix: various broken error states

Description
Fixes:

Error states not showing on create operation
Error states breaking when name is present on tab field
Nested fields returning empty error message tooltips
Arrays and blocks not showing child errors

[X] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X] Existing test suite passes locally with my changes field-error-states

woah, is this PR meant for the monorepo? https://github.com/payloadcms/payload/pulls

Something is a-miss here

lgtm


Reinforcement Learning Model for Dynamic Hedging Strategies

🛠 Related Issue

Data Collection and Preprocessing: Gather historical market data and preprocess it for analysis.
Environment Setup: Create a financial environment that simulates the market for training the RL model.
Model Development: Develop and train the RL model using stable-baselines3.
Evaluation and Validation: Evaluate the model's performance and validate its effectiveness.

🔍 Type of PR

[ ] 🐛 Bug fix
[ ] ✨ Feature enhancement
[ ] 📚 Documentation update
[ ] 🛑 Other (specify): _______________

📸 Screenshots / 🎥 Videos (if applicable)

[Attach screenshots or videos]

✅ Checklist

[ ] I have performed a self-review of my code.
[ ] I have read and followed the Contribution Guidelines.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.

ℹ Additional Context

[Include any additional context or information that might assist reviewers in understanding the changes]

pls @Akshat111111 check it


add WaterMark

how can i add WaterMark ?

The "Watermarking Videos" is not in the scope of this project. You should use PHP FFMpeg to add a watermark to a video. (see here)

a problem after this lines is hls dont export all files (just one of array [$720,$1080,...]) what is problem ? may show me an example ?

It is not possible to add a watermark to HLS streams using this project(at this moment), but you can run an FFmpeg command line to add a watermark to the HLS files:
ffmpeg -i path/to/video.mp4 -i path/to/watermark-logo.png -filter_complex "overlay=10:10" \
-c:v libx264 -c:a aac -bf 1 -keyint_min 25 -g 250 -sc_threshold 40 -hls_list_size 0 -hls_time 10 \
-hls_allow_cache 1 -hls_segment_type mpegts -hls_segment_filename path/to/segment_%04d.ts \
-s:v 640x360 -b:v 139k -strict -2 path/to/playlist.m3u8

Alternatively, You can add a watermark to the original video and then convert the new video to HLS files:
ffmpeg -i path/to/video.mp4 -i path/to/watermark-logo.png -filter_complex "overlay=10:10" new-video.mp4

Or using PHP-FFMpeg
$ffmpeg = FFMpeg\FFMpeg::create();

$video = $ffmpeg->open('video.mpeg');

$video
    ->filters()
    ->watermark($watermarkPath, array(
        'position' => 'relative',
        'bottom' => 50,
        'right' => 50,
    ));

$video->save(new FFMpeg\Format\Video\X264(), 'new-video.mp4');

After adding the watermark, create HLS content files with your new video file(watermarked video). (How to create HLS content?)
I labeled this issue as "enhancement" to implement this feature(Watermarking HLS content) in the future.

thank you! now your mean is first add watermark ! and after this convert to hls

Yes. You can also use the command line I provided in the last comment.


Example image is for a dashbaord that isn't even provided any more

It seems this repo is pretty dead, because it's got some fairly serious issues that prevent it from being usable.
Namely, this big pretty example dashboard you show in the readme isn't even in the current version of the repository. You get nothing when you start this up for the first time. In fact, as some of the other issues mention, it's not even clear to me if my data is making it into graphite, but maybe that's my issue.
Also, unrelated, I had to run docker compose with the priviledged option to even get the web UI to render at all.

I got the same problem as @Sushisource
While the repo looks splendid to me, it falls short at this point. I'm using macOS and would like to help get these things fixed.

@Sushisource @akauppi I've restore the deleted dashboards..please let me know if all is ok.


ISC vs MIT License

Hi!
there are currently two licenses in this repository:

package.json contains "license": "ISC", but
LICENSE contains the MIT license.

While these licenses seem to be equivalent, which of these should be taken as the main one?
Thanks!
Jakub

MIT is preferred

Done, thanks for notice, I really appreciate that.


Reduce line length to 120

Description

reduces (almost) all lines to 120 characters or less

Comments
I sometimes used the join method to split and recombine stings since simply adding two strings together with a "+" triggers another linting error.
I sometimes used "neqa: E501" since the docstring would have been broken upon splitting parameter datatype arguments.
Issue
This PR is regarding issue #214.

Closing in favour of #354.


Update main.js

Arranging quotes categories by ascending order.
PULL REQUEST TEMPLATE
**My PR closes #88 **
👨💻 What did you do ?

Arrange Quotes Category Options in Alphabetical Order with 'Random' as a First Option for enhancing user experience.
Note to reviewers

📷 Screenshots

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.
[x] I have read the contribution guideline properly and following the criteria.

@Shariar-Hasan Please review it.

your contribution was good and impressive, but get closed due to this false acceptence as you didnt read


Generate documentation with sphinx

Documentation currently looks to be manually created in reference/library-reference.rst. This is not so ideal and can be automated by using Sphinx.
Looking at the source, this would mainly require updating docstrings to document parameters and then checking that docstrings include all relevant information currently contained in the existing reference. I would be willing to help out with this.

Hi @mivade,
I don't have the time to set that up at the moment, but it would definitely be a good idea! I'll keep this open for now.


Add dev bundle download listener on Android

This exposes a way to listen to JS bundle download events when creating a ReactInstanceManager. This can be used to display a custom native UI while the JS bundle is loading. It is a pretty specific use case but Expo will need this to display loading progress on the app loading splash screen.
Test plan
Tested by adding a listener to the ReactInstanceManager in the Expo app and checked that it gets called when the bundle is loading.

PR looks good, we just need to update some internal projects that refer to BundleDownloadCallback before we can land this. I'll import this PR and update the internal diff with whatever needs to be done here.

Importing again so we can get all the recent changes.

@hramos - looks like import failed? :(

@hramos Fixed conflicts, could you try shipping this again?

Status: we made some changes to the internal source of truth repo which required a rebase. Next I just need to update some internal references to this callback (again, as these changes get blown away whenever I re-import this PR).

@hramos Fixed conflicts, could you try shipping this again?

Re-importing, let's try again.


Add server config to disable user registered agents

As user-/org-agents allow normal (non instance admins) to extract secrets if they know how from the repos they are admin at, this is an hardening option.
normally you already trust users who are admin but in edge cases you want to forbid them to register own agents ...

It looked nicer but the only real answer is that i did not come up witj a combined name for the var

well this would allow instance admins to still create org agents ... but not normal users
there is no much downside in doing so ... this is the same argument i wana have repo agents.
It is easier in therms of UX for the user and do not add much code on our side to maintain

well this would allow instance admins to still create org agents ... but not normal users

Would probably help to ask: What would be the argument for an instance admin to disable user agents in general.

I wrote that argument also into the docs

https://github.com/woodpecker-ci/woodpecker/pull/4206/files#diff-797f56c545a9d6d7c5a0a660ecf679cef504d2538941b85876458b60a6e7933fR63

now the flack disable the function & ui alltogether


Bug fix 3.7/fix condition where empty list is ok

Scope & Purpose
fix go driver backup tests - searching for non-existing backups in clusters

[x] Bug-Fix for devel-branch only applies devel & 3.7
[x] Bug-Fix for a released version
[x] The behavior in this PR can be (and was) manually tested - search for non existing backup in cluster.
[x] The behavior change can be verified via automatic tests by running go driver tests

Related Information

[x] TBTS-41

Testing & Verification
run go driver tests

[x] There are tests in an external testing repository (i.e. node-resilience tests, chaos tests)

Documentation

[x] Added a Changelog Entry (referencing the corresponding public or internal issue number)

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr-linux/12342/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10611/


Queued users that have changed names cannot be removed.

Describe the bug
An user joined Webex with the name "Pedro" and added himself to the queue.  Then, changed the name to "Pedro Cabral" -- at which point that he could no longer remove himself from the queue. Nor can an admin or a super-admin.
However he can add himself a 2nd time to the queue (which cannot be removed either)
To Reproduce
Steps to reproduce the behavior:

Create webex space
Join with a name
Add self to queue
change name

Expected behavior
A-minima, it would be expected that an admin/super-admin can remove entries. In this case, that doesn't seem to be the case.
If you want to see "in vivo" then let me know and I can share the space ID over some sort of private communications.
Screenshots
If applicable, add screenshots to help explain your problem.
Debug (please complete the following information):

Please run any commands that are causing issue with " | debug" on the end. Paste any relevant or helpful information you receive here

Additional context
Add any other context about the problem here.

Hello Team,
Was this bug fixed? We are facing the same issue.
FYI, collected debugs :
{
"request": {
"id": "Y2lzY29zcGFyazovL3VzL01FU1NBR0UvODg5MWY4ODAtMGM1My0xMWVkLWIxMGItNjFkYjhhN2E5Zjgz",
"roomId": "Y2lzY29zcGFyazovL3VzL1JPT00vZTk2NTA2YTAtYmQ2OS0xMWViLTg3OTgtN2QxZWEwZWQyMDM0",
"roomType": "group",
"personId": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS80ODkyYTBiZC1iZDgyLTRjMGQtOTYyMC1lMTI1ZTYwY2E4YWU",
"personEmail"<EMAIL_ADDRESS>"mentionedPeople": [
"Y2lzY29zcGFyazovL3VzL1BFT1BMRS82MGQ5ZmQ4ZS03N2JjLTQ4MWItYjhkYy0zNGU0N2JiN2NmYjM",
"Y2lzY29zcGFyazovL3VzL1BFT1BMRS9lZTc0NGQwZC04ZGM1LTQzNWEtYWE4OC02YTk4YTBkMDM5ZWY"
],
"created": "2022-07-25T19:54:03.144Z"
},
"initiative": {
"rawCommand": "remove person Shanmuga on queue IBR_WAN_AUTO",
"destination": {
"roomId": "Y2lzY29zcGFyazovL3VzL1JPT00vZTk2NTA2YTAtYmQ2OS0xMWViLTg3OTgtN2QxZWEwZWQyMDM0"
},
"debug": true,
"user": {
"id": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS80ODkyYTBiZC1iZDgyLTRjMGQtOTYyMC1lMTI1ZTYwY2E4YWU",
"displayName": "Harikanth Gaddam"
},
"data": {
"name": "shanmuga",
"queue": "ibr_wan_auto"
},
"action": {
"QUEUE": true,
"AUTHORIZATION": "projectAdmin",
"COMMAND_TYPE": "operation",
"COMMAND_BASE": "remove person",
"ARGS": "{name:\S+?(\s\S+?)?}",
"DESCRIPTION": "Removes a tagged person from the current queue"
},
"similarity": {
"similarity": 0.3008849557522124,
"action": "remove person {name:\S+?(\s\S+?)?}( (to|on|for|with|from) queue {queue:[\w\s]+})?"
},
"mentions": [
"Y2lzY29zcGFyazovL3VzL1BFT1BMRS9lZTc0NGQwZC04ZGM1LTQzNWEtYWE4OC02YTk4YTBkMDM5ZWY"
]
},
"result": "User "Shanmuga sundaram balasubramanian" was not found in queue "IBR_WAN_AUTO""
}

Hey thanks for finding this one! sorry for the late response, as you may know it's just me here. You're welcome to try and fix this one of course and submit a PR for review. Otherwise, i'm going to see if i can fix this one in the coming weeks!:)
In the meantime, you can always create a new queue as a workaround (Though i understand the trouble in doing that).


Non-Functional Requirements

Title;
Update Non-functional Requirements section on the document.

Non-functional requirements has Security, Compliance, Usability, Scalability, Availability and Modularity.
See the document for more info...


Update reqlite for 2.2

Some tests are broken for 2.2, mostly due to backtraces.
We should also add connection.server(), object.values() and update changes to handle includeInitial.

Work is being done on the next branch:

All tests are passing now
values is implementeded
Fix for #59

2.2.0 is out :)


Add the count parameter to kraken.spot.Market.get_recent_trades

Is your feature request related to a problem? Please describe.
… this parameter was added in June 2023 to the API.

Already fixed.


Add 'crds.enabled' and 'crds.keep' options to generated CRDs

Implements https://github.com/cert-manager/cert-manager/pull/6719 for all the Makefile module projects.
See https://github.com/cert-manager/approver-policy/pull/376 for an example.

@ThatsMrTalbot I updated this PR and the approver-policy PR: made the templates more readable (stopped using those comments).

/approve


Matched "Operator Eq' with parameter 0' against variable REQUEST_HEADERS:Host' (Value: 0' )

ModSecurity does not recognize the Host header when using HTTP/3. I believe I have the correct versions of ModSecurity, the connector, and the rules. Is any custom configuration necessary to handle HTTP/3 requests?
{
  "transaction": {
    "client_ip": "XXXXXX",
    "time_stamp": "Wed Dec 18 15:52:34 2024",
    "server_id": "a53237e5ec8faf273b2ea40bcca024979fdaed7f",
    "client_port": 46779,
    "host_ip": "XXXXXX",
    "host_port": 443,
    "unique_id": "173453355437.118418",
    "request": {
      "method": "GET",
      "http_version": 3,
      "uri": "/",
      "headers": {
        "sec-fetch-user": "?1",
        "sec-ch-ua": "\"Chromium\";v=\"129\", \"Not=A?Brand\";v=\"8\"",
        "sec-fetch-dest": "document",
        "sec-fetch-mode": "navigate",
        "user-agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36",
        "sec-fetch-site": "cross-site",
        "sec-ch-ua-platform": "\"Linux\"",
        "upgrade-insecure-requests": "1",
        "sec-ch-ua-mobile": "?0",
        "accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7",
        "cache-control": "max-age=0",
        "accept-encoding": "gzip, deflate, br, zstd",
        "accept-language": "en-US,en;q=0.9",
        "priority": "u=0, i"
      }
    },
    "response": {
      "body": "",
      "http_code": 200,
      "headers": {
        "Server": "nginx/1.26.2",
        "Date": "Wed, 18 Dec 2024 14:52:34 GMT",
        "Content-Type": "application/octet-stream",
        "Connection": "keep-alive",
        "Alt-Svc": "h3=\":443\"; ma=86400"
      }
    },
    "producer": {
      "modsecurity": "ModSecurity v3.0.13 (Linux)",
      "connector": "ModSecurity-nginx v1.0.3",
      "secrules_engine": "DetectionOnly",
      "components": [
        "OWASP_CRS/4.9.0\""
      ]
    },
    "messages": [
      {
        "message": "Request Missing a Host Header",
        "details": {
          "match": "Matched \"Operator `Eq' with parameter `0' against variable `REQUEST_HEADERS:Host' (Value: `0' )",
          "reference": "",
          "ruleId": "920280",
          "file": "/usr/local/nginx/conf/crs4/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf",
          "lineNumber": "574",
          "data": "",
          "severity": "4",
          "ver": "OWASP_CRS/4.9.0",
          "rev": "",
          "tags": [
            "application-multi",
            "language-multi",
            "platform-multi",
            "attack-protocol",
            "paranoia-level/1",
            "OWASP_CRS",
            "capec/1000/210/272",
            "PCI/6.5.10"
          ],
          "maturity": "0",
          "accuracy": "0"
        }
      }
    ]
  }
}

How can I prevent the logs from growing excessively? Should this rule be disabled for HTTP/3?

@MorrowxD,
I think this is more a Coreruleset issue than ModSecurity.
Anyway, it's interesting why do you have an audit log entry with response code 200? ModSecurity's default config file contains SecAuditLogRelevantStatus with value "^(?:5|4(?!04))", this means audit.log entry is generated only when the status code is 5XX or 4XX except 404.
For the solution: you can create an exclusion against that rule. For more information, please take a look at this page. A quick explanation:
SecRule REQUEST_PROTOCOL "^HTTP/3(\.0)$" \
    "id:10000,\
    phase:1,\
    pass,\
    t:none,\
    ctl:ruleRemoveById=920280"

This will prevent to execute rule 920280 if the protocol is HTTP/3 or HTTP/3.0.


[BEAM-5107] Support ES-6.x for ElasticsearchIO

This PR supports ES 6.x for ElasticsearchIO.
Right now ElasticsearchIO only supports 2.x-5.x
Hello @timrobertson100, please help to review it. Thank you.
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

Thanks @dattran-vn01
Do you think it is possible to add a test to demonstrate it does work with ES6?
Looking at the commented out test it implies that the full addressing doesn't work.  At a minimum I'd suggest that needs documented in the JDoc.
Are you aware that there is WIP for an ES6 IO on https://issues.apache.org/jira/browse/BEAM-3199 - it looks pretty complete and is already used by one person in production, but IIRC doesn't have tests. Have you any thoughts on whether we should enable partial support for ES6 as you do here, or push for the full support with BEAM-3199?

Thank you @timrobertson100. I did not know that there is WIP BEAM-3199.
I prefer to go with my simple approach because it keeps one production module to avoid confusion for the users.
I will add one something in the JDoc for the full addressing and add new elasticsearch-tests-6 module to demonstrate it does work with ES6.
If you agree with my approach, I will update my PR tomorrow. We are also using this approach in production.

Thanks @dattran-vn01
I've commented on the Jira so design decisions taken will be easily searchable/traceable.
I do agree this is a good approach, although I don't know what will happen when you try and have an embedded ES6 on the classpath for a unit test. I've offered an alternative approach on the Jira should that cause issue and we should try and get agreement from others to go for a pragmatic approach.
As for the code you provided, I've only scanned quickly but first impressions were very favourable. Thanks again.
(Please be aware that I am not a committer, so I can't merge it. I can hopefully help speed up that process though)

Thanks @dattran-vn01
I’ll review this within the next 24hrs unless someone gets there first

Thank you @timrobertson100 for your great support. I updated the PR. I would like to contribute more. Be honestly, This is first time to contribute to open source community so I need to learn a lot of thing from you guys to work effectively.
I see there are still some IO I can contribute as

DistributedLogIO - https://issues.apache.org/jira/browse/BEAM-607
RestfulApiIO - https://issues.apache.org/jira/browse/BEAM-1946
MemcachedIO - https://issues.apache.org/jira/browse/BEAM-1678
Do you know what is higher priority ticket? It seems that it's RestfulApiIO
In my current project, we consume Twitter Event-Driven Streaming API.
Do you think we should support new IO for Streaming API?

Thanks for accommodating those suggestions @dattran-vn01
I've always been asked to rebase and squash into a single commit and not merge so you might be asked to adjust the commits, but I suggest leaving that until the very end.  There are other ES PRs in flight so there might be another conflict depending on the acceptance order.
Can you PTAL @echauchot ? (This PR also addresses BEAM-4911)

@dattran-vn01 our messages crossed there.
Thanks to you - it was a pleasure reviewing your work and it's great you are keen to contribute to Beam. I'd suggest the most important things to work on are the ones you need or would use, and the ones that interest you most. I know a few projects that would use a RestfulAPIIO so that sounds like a good addition though. Please be aware that we also strive to "market" the project so if you have anything to blog then that would be a welcome addition too and can be quite rewarding. .

Retest this please

Hi @dattran-vn01, thanks for you work ! I'm back from vacation, I can take a look in the next few days

@dattran-vn01 as a first oversight on the code, I'm glad to see that ESIO v5 code is compatible with ES6 and that the only thing needed is to re-architecture the tests. I'll start a more in depth review soon

@dattran-vn01 @timrobertson100 starting the review

@dattran-vn01 regarding your commit history, please do not merge master into your feature branch. Instead rebase your branch onto master to have a clean history. See beam contribution guide: we prefer not having parasite merge commits in the history. The only merge commits allowed are the ones that merge PRs into master.

Thank you. @echauchot Let me close this PR and create a new one without merging master into my feature branch.

@dattran-vn01 no need to close, just rebase and we will squash the commits in the end. Please do not close otherwise we lose review history

@timrobertson100 +1 of course
PS: auto deps mecanism will finally stop spamming me :)

Hi @echauchot @timrobertson100 I ran integration test and added notes
https://gist.github.com/dattran-vn01/f14e595ed765e0bdffdc2895271864ee

Thank you @echauchot I think I posted wrong ES5 docker command but you can see the screenshot is good. It shows Elasticsearch version is 5.4.3

Hi @echauchot I will fix java doc, squash commit, and check ES6 type routing. ES-test-2 is good so do I need to run again?

I corrected https://gist.github.com/dattran-vn01/f14e595ed765e0bdffdc2895271864ee

Hi @echauchot Could you please help to explain one thing?
I see Elasticsearch 6 does not allow many types for one index so it means we cannot use type routing in ES6.  That's why I added a comment
type (version > 6). Support for type routing was removed in Elasticsearch 6 (see https://www.elastic.co/blog/index-type-parent-child-join-now-future-in-elasticsearch)

I ran testWriteWithTypeFn  (now it's renamed to testWriteWithTypeFn2x5x) for ES 6 and it was failed because this test requires many types.

Hi @echauchot I fixed all java doc errors. After you check and confirm everything is ok, I will squash everything in one commit named [BEAM-5107] Add support for ES-6.x to ElasticsearchIO. Thank you.

@dattran-vn01 regarding your question about type routing: elastic website says about deprecation.

We plan to introduce a new breaking change currently targeted for 6.0 to make it so new indices will only allow a single type to be created to help you get better prepared for 7.x.  Don't worry though -- the multi-type indices you created in 5.x will continue to work as before in 6.x.

So indexes created using ES5 that contain mutli-types still work with ES6. The problem is that in the test we create ES6-version-indexes and those ones do not support multi-types to prepare users for type deactivation in ES7.
IMHO it is a better communication to say to the users that type routing is not supported in ESIO6 rather than saying it is supported only if you created the index using a previous version of ES.
So we can keep it that way.

Thank you @dattran-vn01 and congratulations. This is a really great addition.
Sorry for my silence, but I have been / am very busy on other things this week and next.

Thank you @timrobertson100  @echauchot for all supports :) I squashed the commit.