Telescope Preview

How to enable this to work in preview window of other programs like telescope

Any progress?

Planned but not much progress yet

Unfortunately, for this to work out of the box with the default telescope buffer previewers I need Telescope to allow Neoscroll to replace their default scroll_fn() function. I opened a PR for this purpose.
The scroll_fn() function can be passed to custom previewers but not to the default ones so without this PR I can only create custom previewers with smooth scrolling but I doubt many people would use even if they are otherwise identical to the default ones. Here is a working example:
local builtin = require("telescope.builtin")
local previewers = require("telescope.previewers")
local from_entry = require("telescope.from_entry")
local conf = require("telescope.config").values
local neoscroll = require('neoscroll')

local my_previewer = function(opts)
  return previewers.new_buffer_previewer({
    scroll_fn = neoscroll.telescope_scroll_fn,
    define_preview = function(self, entry)
      local p = from_entry.path(entry, true, false)
      if p == nil or p == "" then
        return
      end
      conf.buffer_previewer_maker(p, self.state.bufnr, {
        bufname = self.state.bufname,
        winid = self.state.winid,
        preview = opts.preview,
        file_encoding = opts.file_encoding,
      })
    end,
  })
end

local function my_picker(opts)
  local opts = opts or {}
  opts.previewer = my_previewer(opts)
  builtin.buffers(opts)
end

my_picker()


Getting 'auth error: EOF' when referencing a GitRepository pulling via SSH

When creating an ImageUpdateAutomation that reference a GitRepository in HTTPS mode, ImageUpdateAutomation is able to reconcile. When referencing a GitRepository in SSH mode, it gives this error: auth error: EOF.
GitRepository in HTTPS mode:
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: GitRepository
metadata:
  name: my-app-https
  namespace: flux-system
spec:
  gitImplementation: go-git
  ignore: |
    # exclude all
    /*
    # include kustomize dir
    !/kustomize
    # exclude file extensions from kustomize dir
    /kustomize/**/*.md
    /kustomize/**/*.txt
  interval: 15m0s
  ref:
    branch: develop
  secretRef:
    name: bitbucket-https-credentials
  timeout: 20s
  url: https://bitbucket.org/my-group/my-app

GitRepository in SSH mode:
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: GitRepository
metadata:
  name: my-app-ssh
  namespace: flux-system
spec:
  gitImplementation: go-git
  ignore: |
    # exclude all
    /*
    # include kustomize dir
    !/kustomize
    # exclude file extensions from kustomize dir
    /kustomize/**/*.md
    /kustomize/**/*.txt
  interval: 15m0s
  ref:
    branch: develop
  secretRef:
    name: bitbucket-ssh-credentials
  timeout: 20s
  url<EMAIL_ADDRESS>
ImageUpdateAutomation (only spec.sourceRef.name changes while testing the two GitRepository):
apiVersion: image.toolkit.fluxcd.io/v1beta1
kind: ImageUpdateAutomation
metadata:
  name: my-app
  namespace: flux-system
spec:
  git:
    checkout:
      ref:
        branch: develop
    commit:
      author:
        email<EMAIL_ADDRESS>        name: flux
      messageTemplate: |
        [ci skip] -
        {{range .Updated.Images}}{{println .}}{{end}}
    push:
      branch: develop
  interval: 15m0s
  sourceRef:
    apiVersion: source.toolkit.fluxcd.io/v1beta1
    kind: GitRepository
    name: my-app-https
  update:
    path: ./kustomize/dev
    strategy: Setters

The status result when spec.sourceRef.name == my-app-ssh:
status:
  conditions:
  - lastTransitionTime: "2021-08-05T11:13:23Z"
    message: 'auth error: EOF'
    reason: ReconciliationFailed
    status: "False"
    type: Ready
  lastAutomationRunTime: "2021-08-05T11:09:05Z"
  lastHandledReconcileAt: "2021-08-05T07:15:48.299246-04:00"
  observedGeneration: 3

The status result when spec.sourceRef.name == my-app-https:
status:
  conditions:
  - lastTransitionTime: "2021-08-05T11:16:58Z"
    message: no updates made
    reason: ReconciliationSucceeded
    status: "True"
    type: Ready
  lastAutomationRunTime: "2021-08-05T11:17:28Z"
  lastHandledReconcileAt: "2021-08-05T07:16:57.526803-04:00"
  observedGeneration: 4

Are you certain the SSH key used is a read-write one? Bitbucket "Access Keys" analog to "Deploy Keys" from GitHub and friends, are read-only without any read-write option on Bitbucket Cloud.
ImageUpdateAutomation writes to the repo, so it needs a read-write key. I am not certain how this error presents from Bitbucket on push when a key with read-only access is used, so I would be suspicious of any auth error from Bitbucket as potentially due to this issue.
(You could add your SSH key to a machine account with write access to work around this issue, if that is the case.)

To make it more explicit, yes, this project in on Bitbucket, as subtly hinted at in the manifests.

Bitbucket "Access Keys" [...] are read-only
We don't use Access Keys from the repository settings page. The way our setup is is as follow.

We have a full-fledged Flux bot user. On that user, we have setup ssh keys to access our multiple k8s clusters. The same way that my own user have a ssh key for working with git/Bitbucket.
Then, the access to the repositories are managed on a repo basis: each repository decide which users/groups have access, and at what level (read/write/admin).
On the relevant repos that we want Flux to automate, we setup the bot user with write access. I even tried with admin, but it didn't help. If the GitRepository is working over ssh, ImageUpdateAutomation won't be able to push commits.
To test it all out, we made a setup where we used an App Password (with read/write permission for repositories). By setting the GitRepository with those credentials, and the appropriate url, ImageUpdateAutomation is able to push commits.
The thing is, those are not brand new ssh keys or a brand new setup for accessing our repos. Those were setup and used by our Flux v1 integration. :/

Hmm! So you are able to work around with an app password, but this uses HTTP auth and this is probably undesirable
(Moreover, if there is a bug in the SSH implementation, you will not be the only users affected and we will want to have a bead on the issue.)
I have a Flux cluster set up on Bitbucket cloud, but I have not tested ImageUpdateAutomation there with SSH. I will get around to it within the next couple of days, then perhaps we can debug the issue on our own without taking up your time.
Thank you for the report! Can you please confirm what version of Flux are you using, and re-confirm if it is anything earlier than 0.16.2 whether the problem is still in force if you upgrade to the last Flux version?

I did this

create a new project in my account on bitbucket.org
use ssh-keygen to create a new SSH key
paste the public key into my account's SSH keys (treating myself as a bot)
flux bootstrap [...] --private-key-file=id_rsa in a freshly cluster, to install flux and use the key I just created
make an ImageRepository and ImagePolicy for the source-controller image, and an ImageUpdateAutomation object pointing at the git repo
put an update marker in flux-system/gotk-components.yaml referring to the policy, commit and push

The last few steps are just a minimal way to get the automation to make commits -- I go and edit the image version in the file to an old one and commit that, it updates to the latest.
Then I tried different kinds of key by recreating the secret with
flux create secret git --url ... --ssh-key-algorithm ... flux-system

(and pasting the fingerprint into bitbucket).
I found that it worked both with an RSA key and with EDRSA (default number of bits / curve). With an ED25519 key, image-automation-controller fails to clone the repo with the error message Failed to authenticate SSH session: Unable to extract public key from private key. I think this is a limitation of libgit2, at the present anyway.
@wolfmah Can you see any significant differences between what I've done and your setup?

@kingdonb
I just tried the same step as I described above, but with the latest 0.17.2. Same result: auth error: EOF.

Can you see any significant differences between what I've done and your setup?
@squaremo

Here's what was already in place:

A private corporate Bitbucket Workspace that I (and our Flux bot) have access to.
A test application that our team use as a sandbox. This private repository belongs to the aforementioned workspace.
The Flux bot have already SSH keys created for all our environments (in RSA format). As of now, they are used by Flux v1.

Now, for the new stuff:

Flux is installed via Terraform. We export the installation manifests via: flux install --export ..., copy the output inside a module then use a Kustomize provider to patch some stuff (like requests/limits of controllers, annotations/labels, etc.).
This Terraform module also creates the Kubernetes secrets: bitbucket_https_credentials and bitbucket_ssh_credentials.

The rest is pretty much the same: create ImageRepository + ImagePolicy, along with the GitRepository + Kustomization. Then the ImageUpdateAutomation, pointing to the GitRepository and either the HTTPS or SSH secret.
It feels like I'm missing something, because squaremo, if you are able to work with Bitbucket and SSH, I should be able too. :/

Making the SSH secret with Terraform is a difference -- are you able to try using flux create secret git ... to create the SSH secret? That would rule it out, at least.

The latest release of the image-automation-controller (v0.15.0) contains libgit2 linked against OpenSSL and LibSSH2, which based on my research and extensive testing, should solve most issues around private key formats.
NB: if the issue continues to exist, I think it is happening due to a handshake issue and you may want to confirm the key in known_hosts isn't of an ECDSA* type. We will support these types soon as well, but need to get the libgit2 >=1.2.0 in a working shape first as support was added for this in 1.2.0.

Thanks for reporting back! :+1:

Either them specifically, or when they are uploaded to the cluster via Terraform (I'm betting on the latter one).

It may just be that the fields in .data get different names when you create them with Terraform -- if they were originally made for Flux v1, then this is probably so. (If you are able to check, it would be good to verify this).


Add cloudflare/pint to the list of integrations

https://groups.google.com/g/prometheus-users/c/WKMYPnDZRG8
Signed-off-by: Łukasz Mierzwa<EMAIL_ADDRESS>

Thanks!


Trailing slash added at the end of upstream_url ? Can we remove it ?

Hello Guys
When I use strip_request_path parameter, seems Kong / Nginx always add a trailing slash at the end of my upstream_url.
Is there any way I can get rid of it ?
Steps to reproduce :
curl -X POST --url http://localhost:8001/apis/ --data 'name=test-trailing-slash-api' --data 'upstream_url=http://www.mockbin.com/bin/ea0bfc2e-e490-4bdb-bcb4-548f57feebd7' --data 'request_path=/test-trailing-slash' --data 'strip_request_path=true' | jq
Answer would be :
{
"upstream_url": "http://www.mockbin.com/bin/ea0bfc2e-e490-4bdb-bcb4-548f57feebd7",
"request_path": "/test-trailing-slash",
"id": "4d393d19-4eb0-4b43-cb4f-f39fe59ceaf9",
"created_at":<PHONE_NUMBER>000,
"strip_request_path": true,
"name": "test-trailing-slash-api"
}
Note that there is no trailing slash on the upstream_url in the response.
Now run a curl to see the result in mockbin :
curl -X GET --url "http://localhost:8000/test-trailing-slash?test"
Result in mockbin with a trailing slash :
. . .
"method": "GET",
"url": "http://www.mockbin.com/bin/ea0bfc2e-e490-4bdb-bcb4-548f57feebd7/?test",
. . .

Thanks for reporting btw. Will try to tackle this when I have some time.

Happy to help :)
Le jeudi 5 novembre 2015, Thibault Charbonnier<EMAIL_ADDRESS>a
écrit :

Thanks for reporting btw. Will try to tackle this when I have some time.
—
Reply to this email directly or view it on GitHub
https://github.com/Mashape/kong/issues/675#issuecomment-154177613.

@JnMik, the PR I just referenced should fix this problem

Hey that's awesome !
Thx for the great job
I'll give it a try when I'm back at the office :)

This will be available in the next version.

This changes breaks RFC 3986 which states that a URI referenced without a leading forward slash should be treated as relative: https://github.com/Mashape/kong/pull/715/#issuecomment-184307235

@marcelmfs this issue was about the the last slash in the URI, not the leading slash. Can you send me an example to reproduce your issue?

Nevermind I came up with my own openresty+lua solution with Redis. No need of cassandra for this simple API.

I'll first describe the user case I'm trying to replace.
We're currently using static nginx location directives for a set of microservices and apps, in the form of:
location /login/ {
   proxy_pass https://login_app;
}

location /api/sso/ {
  proxy_pass https://sso_service;
}

In nginx documentation, there is a distinctive section regarding the trailing slash on the location pattern {} directive (ref: http://nginx.org/en/docs/http/ngx_http_core_module.html#location):
If a location is defined by a prefix string that ends with the slash character, and
requests are processed by one of proxy_pass, fastcgi_pass, uwsgi_pass,
scgi_pass, or memcached_pass, then the special processing is performed. In
response to a request with URI equal to this string, but without the trailing slash,
a permanent redirect with the code 301 will be returned to the requested URI
with the slash appended. If this is not desired, an exact match of the URI and
location could be defined like this:

location /user/ {
    proxy_pass http://user.example.com;
}

location = /user {
    proxy_pass http://login.example.com;
}

By removing the trailing slash on location directives without taking that into account, kong breaks this compatibility where a location that's not a folder and for which a proxy_pass should occur is not treating relative href accordingly. Because, my first location directive:
location /login/ {
  proxy_pass https://login_app;
}

is being rewritten as /login and therefore, all hrefs in the html are now relative to the root_url, instead of being relative to /login/main.css for example. I think this breaks the protocol in the mentioned RFC.
That's why I can't use the latest version of kong anymore and had to switch to a custom lua module.

@marcelmfs I will try to explain below the change introduced by the PR that closed this issue, so that we can be on the same page and I can better understand what's breaking your API.
The PR makes the proxied path consistent to the path requested by the client. Specifically, let's consider the following API on Kong:
request_path=/test
strip_request_path=true
upstream_url=http://api.com/service

Then the following incoming requests will be proxied to:

kong:8000/test/get -> http://api.com/service/get
kong:8000/test/get/ -> http://api.com/service/get/

Without unexpectedly adding a final slash when the original request didn't have it. Previously instead the behavior was:

kong:8000/test/get -> http://api.com/service/get/

Which is more unexpected, since the original request had no final slash.

Yes, that's the way to go. Don't change default behaviour of nginx as it does things under the hood that might break how people expect it to work.

Is this change released yet? I'm still getting this issue.
Created API using
$ curl -i -X POST --url http://localhost:8001/apis/ --data 'name=test' --data 'upstream_url=http://xx.xx.xx.xx/api/test' --data 'request_host=xxxxxxx'
curl -i -X GET --url http://localhost:8000/ --header 'Host: xxxxxxx'
The request was forwarded to http://xx.xx.xx.xx/api/test/ (Added a trailing slash automatically)

The request path was GET /, so is nginx who's adding the trailing slash. You app should act accordingly, if test is an HTML and not a endpoint, it should be stated so.

@marcelmfs
test is not an HTML and its the endpoint.
The route in my application is defined like this.
I didn't get what you meant by The request path was GET /. Please elaborate.

@alexraju in your example you are using request_host resolver and not a path resolver. When you are requesting GET /, Kong will append the requested endpoint to the upstream_url, hence http://xx.xx.xx.xx/api/test/.
To extend your example, if you were requesting GET /another_endpoint then the final URL requested would be http://xx.xx.xx.xx/api/test/another_endpoint (not http://xx.xx.xx.xx/api/testanother_endpoint).
The original problem in this issue was an edge-case in request_path resolvers with strip_request_path=true, which doesn't apply in your case.

Hi I realize this was fixed a long time ago, but when the above comment said that this would be updated in the "next version" which version # did this fix actually go out in?  Trying to debug a system and I want to validate the versioning.  I couldn't find documentation with the dates that each version was released.  Thank you!

Looking at the CHANGELOG, it seems like the "next version" is 0.8.3, released on 2016/06/01.

Awesome, thanks for the quick reply, info, and the link!


[Dependencies] Upgrade setuptools to >= 70.0.0

Description of changes
Upgrade setuptools from 69.5.1 to to >= 70.0.0 to mitigate the below vulns:

https://github.com/aws/aws-parallelcluster/security/dependabot/12
https://github.com/aws/aws-parallelcluster/security/dependabot/11
https://github.com/aws/aws-parallelcluster/security/dependabot/10

Tests
PR checks
References

Link to impacted open issues.
Link to related PRs in other packages (i.e. cookbook, node).
Link to documentation useful to understand the changes.

Checklist

Make sure you are pointing to the right branch.
If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
Check all commits' messages are clear, describing what and why vs how.
Make sure to have added unit tests or integration tests to cover the new/modified code.
Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closed in favour of https://github.com/aws/aws-parallelcluster/pull/6465


GH-40379: [Python] Fix byte_width for binary(0) + fix hypothesis tests

Rationale for this change
Fixing the hypothesis tests:

fixup untested changes to the strategies from https://github.com/apache/arrow/pull/40160
fix a bug in the byte_width attribute discovered by hypothesis (introduced by https://github.com/apache/arrow/pull/40160)

GitHub Issue: #40379

@github-actions crossbow submit test-conda-python-3.11-hypothesis

@github-actions crossbow submit hypothesis


#SB-8433: Change creator to owner for resources.

Ref:
https://project-sunbird.atlassian.net/browse/SB-8433
Description:
when add resource page the created by value is the creator name, then after adding also value should be same.

These changes has to reflect in content player end-page as well. Verify it once, if it not working log a JIRA issue & assign to Joel.


Clicking on a row checkbox fires a click:row event

When using both a checkbox and on row click event, clicking a checkbox triggers the click:row event.
Area highlighted here should not be firing any events.

Released in v0.50.3


Provide method of adding flags to kubelet creation

Rancher versions:
2.0.0
Currently, there doesn't seem to be a way of adding flags on to the creation of each kubelet when using rancher.  There are times when this is necesary to enable certain features of k8. One example is Mount Propagation, as it is a pre-req for getting storageOS up and running. Another use-case would be enabling feature gates to try out k8 features that are in alpha.

Duplicate of https://github.com/rancher/rancher/issues/13816


Fix/about caselaw page update

Made changes and additions to the footer
Created a 'Privacy Notice' page – not linked from footer yet as it needs Director level sign off, but when it is, it will sit in leagl column under the Cookies link.
Made wholesale changes to the 'What to expect page' and renamed it 'About this service'.
Took link out of page header and moved it to the footer under 'About' column.

Changes in this PR:
Trello card / Rollbar error (etc)
https://trello.com/c/OYVqgxKh/748-fcl-policies-all-ducks-in-a-row-🦆
Screenshots of UI changes:
Before
After

[ ] Requires env variable(s) to be updated

Codecov Report

Merging #725 (8548d4a) into main (3cf9322) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #725   +/-   ##
=======================================
  Coverage   92.19%   92.19%
=======================================
  Files          25       25
  Lines        1102     1102
  Branches       55       55
=======================================
  Hits         1016     1016
  Misses         72       72
  Partials       14       14

Impacted Files
Coverage Δ

judgments/tests/tests.py
96.81% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Remove SetInclusionRule and SetInclusionRuleWithArrays

Since S \subseteq T is rewritten by the Keramelizer in #1621, we can safely remove the two rewriting rules, which are now redundant. We also have to remove \subseteq as an acceptable operator in KeraLanguagePred.
@rodrigo7491 what do you think about that?
@thpani in case you have free refactoring cycles.

If the rules cannot be reached anymore, might as well remove them. I imagine this will not have a negative impact on solving performance.

We're using \subseteq in SetInRule and CherryPick.
@konnov should they use the same rewriting as in Keramelizer then?


v2.13.0 broke electron-rebuild

Latest release has broken our build process.
node -v v8.15.0
node-gyp -v v3.8.0
An unhandled error occurred inside electron-rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  addon.cc
  win_delay_load_hook.cc
c:\projects\emerald-wallet\packages\desktop\node_modules\nan\nan_converters_43_inl.h(60): error C2664: 'bool v8::Value::BooleanValue(void) const': cannot convert argument 1 from 'v8::Isolate *' to 'v8::Local<v8::Context>' (compiling source file ..\src\addon.cc) [C:\projects\emerald-wallet\packages\desktop\node_modules\keccak\build\keccak.vcxproj]
  c:\projects\emerald-wallet\packages\desktop\node_modules\nan\nan_converters_43_inl.h(60): note: No constructor could take the source type, or constructor overload resolution was ambiguous (compiling source file ..\src\addon.cc)
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\projects\emerald-wallet\packages\desktop\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\projects\\emerald-wallet\\packages\\desktop\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--target=4.0.5" "--arch=x64" "--dist-url=https://atom.io/download/electron" "--build-from-source"
gyp ERR! cwd C:\projects\emerald-wallet\packages\desktop\node_modules\keccak
gyp ERR! node -v v8.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Failed with exit code: 1
Error: Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  addon.cc
  win_delay_load_hook.cc
c:\projects\emerald-wallet\packages\desktop\node_modules\nan\nan_converters_43_inl.h(60): error C2664: 'bool v8::Value::BooleanValue(void) const': cannot convert argument 1 from 'v8::Isolate *' to 'v8::Local<v8::Context>' (compiling source file ..\src\addon.cc) [C:\projects\emerald-wallet\packages\desktop\node_modules\keccak\build\keccak.vcxproj]
  c:\projects\emerald-wallet\packages\desktop\node_modules\nan\nan_converters_43_inl.h(60): note: No constructor could take the source type, or constructor overload resolution was ambiguous (compiling source file ..\src\addon.cc)
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\projects\emerald-wallet\packages\desktop\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\projects\\emerald-wallet\\packages\\desktop\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--target=4.0.5" "--arch=x64" "--dist-url=https://atom.io/download/electron" "--build-from-source"
gyp ERR! cwd C:\projects\emerald-wallet\packages\desktop\node_modules\keccak
gyp ERR! node -v v8.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

On Windows - https://ci.appveyor.com/project/etcdevteam/emerald-wallet/builds/23066344
On Mac OSX - https://circleci.com/gh/ETCDEVTeam/emerald-wallet/884?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
Thank you for assistance.

Seems this is caused by electron is using NODE_MODULE_VERSION 69 now which lets NAN think that it's newer then Node.JS 11 which uses 67 but actually electron 4.0.5 is more like Node.JS 10.
Refs: https://github.com/electron/node/commit/8bc5d171a0873c0ba49f9433798bc8b67399788c

see #840

I had this issue as well on MacOS using Electron 4.0.4. My temporary workaround is to pin<EMAIL_ADDRESS>until it gets resolved.


make screen_load_texture generic, and screen_load_texture_file for .png

This is definitely not really to actually merge yet (it should probably also take the format in the args), but would you be willing to provide a load_texture function something like this, that can be used to load non-tiled graphics from a buffer? Is there a better way to do this already that I'm not seeing? Mostly I'm looking for a clean way to load the camera image as a texture in a manner that can be merged back into the main codebase at some point.
The end goal is that I'd like to be able to convert my http/mega.nz client into something that can be merged back into mainline FBI.

That sounds like an interesting idea. I went ahead and implemented this kind of change in a way I saw appropriate, so no need for you to figure it out. :P


Short solution needed: "Using regex in search" (manticoresearch)

Please help us write most modern and shortest code solution for this issue:
Using regex in search (technology: manticoresearch)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Using regex in search


add parameter value "ALL" for "TARGET_CONTAINER"

Hi,
here is an improvement proposal for tunable parameter "TARGET_CONTAINER"
If "ALL" is specified as value for "TARGET_CONTAINER" Litmus shall run the experiment on all container in target pod simultaneously.
Thanks.

cc: @rajdas24 @uditgaurav


optimize suggestions

for what I know that TabNine runs as many instances as editor opens.
so do you have any plan to optimize that editors use only one TabNine instance.

@shuxiao9058
Are you talking about multiple documents in the same editor or multiple editors? Which ones?
In general - the communication with TabNine is done over standard input/output, so it cannot be easily shared between multiple processes, and that's not expected to change in the near future.

What I say is multiple editors can use single TabNine instance.
And the communication between TabNine and client can use tcp and so on ...

Thank you.
I'm trying to better understand your use case.
What editors are you using?
Also, what is your concern with multiple tabnine instances? is memory? cpu? something else?

Mostly I using Sublime and Emacs, and what I concern with  multiple tabnine instances is the cost of memory.
And I think the models of Deep TabNine should only load by one instance ...

Thank you for that feedback

Thank you for that feedback

My pleasure.

Same for me, with vim. I frequently open new vim instances (e.g. git can open them when I do git commit), and every new instance is an out-of-memory-whole-system-freeze gamble :)

Same for me, with vim. I frequently open new vim instances (e.g. git can open them when I do git commit), and every new instance is an out-of-memory-whole-system-freeze

What I do is not enabling TabNine by default. I have this in my vimrc:
Plug 'zxqfl/tabnine-vim', { 'on': 'TN' }
nnoremap <Leader>tn :silent! TN<CR>


Fastnlight: Watch pacificconnect.co

Fastnlight requests the watch of the watch_keyword pacificconnect\.co. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

pacificconnect\.co has been seen in 0 true positives, 0 false positives, and 0 NAAs.


[#9292] Renamed Image.put_pixel() to set_pixel().

This PR aims to solve the #9292 issue. Reviewers welcomed ᕕ( ᐛ )ᕗ

if it makes you guys happy..

Not that much, but I had to start contributing on a small issue as my C++ skills are thin ^^


[FEA] Additional improvements to separable convolution

Ideas for further improvements to separable convolution
Listing some thoughts for further improvements on top of #355.
reduce redundant data fetching
It would be nice to adapt the code from #355 to more efficiently handle the case where multiple separable filters are to be applied. For example, for gaussian we would typically filter each axis in turn. Currently the implementation handles one axis at a time and the code uses two stages:
1.) load a tile into shared memory
2.) perform the convolution on the tile
Thus when doing separable filters in nD cases, stage 1 is repeated n times. It would be preferable to adapt to a version that can do a tiled load just once (taking into account any boundary padding along all dimensions) and then once the shared memory is available, apply each filter in turn along the axes.
Accept multiple filters and outputs.
We could potentially also accelerating other operations such as gradient and hessian filters where a series of small separable filters is applied in various combinations to create multiple outputs. This is another case where it seems like we should be able to just do 1 load of a tile into shared memory and then apply all filters to it.
Extend to multi-channel image support
Right now the kernels only run on scalar pixel types, but we can potentially adapt to float2, float3, float4 or arbitrary numbers of channels
Extend to nD
The 3D case could be adapted to a general nD implementation. We can only use up to 3 grid/block dimensions in CUDA, but could ravel multiple physical dimensions into one of these.

Quote from @crisluengo ( https://github.com/rapidsai/cucim/pull/355#issuecomment-1206839904 ):

@grlee77 I haven't been able to read all of the code, but I did a search for "sym" and didn't find anything.
It is usually worth while to make a special case for symmetric filters. For example, instead of (pseudocode) img[i] * filter[i] + img[-i] * filter[-i] (where filter[i] == filter[-i]), you would do (img[i] + img[-i]) * filter[-i], saving about half the multiplications.
In DIPlib we have a special case for both the symmetric case and the antisymmetric case (where filter[i] == -filter[-i], e.g. derivative filters).

Think we will want to capture this with other improvements already noted in this issue.


[Association] User and Comments

Need to add association between user and comments.

A user can have many comments
A comment belongs to a user
Add the test cases

#32


Incomplete instructions regarding 'Add New Bug Benchmark'

Hi @nus-apr,
Although this page/document provides some initial instructions on how to add a new bug benchmark, it does not provide instructions for the second and third points listed.

Benchmark Image: a Dockerfile describing how to construct the benchmark container
Benchmark metadata file: A Json file containing an array of objects with the following features

(The last sentence ends weirdly).  It would be great if you could provide more info.

Thanks @Marti2203 for your prompt reply.
I believe there is a typo in that commit.  Where it's written

Create a new file in app/core/drivers/benchmarks/ with the Benchmark name (i.e. NewBenchmark.py) that contains the following code:

should be

Create a new file in app/drivers/benchmarks/ with the Benchmark name (i.e. NewBenchmark.py) that contains the following code:

right?
Another question that's not yet clear to me is, how does one create the meta-data.json file?  Manually?

Hello @Marti2203 , I would like to add a benchmark to Cerberus for experiment. Until now, I have not known or found the functions on Cerberus to process the output from running test cases in Benchmark.  I am curious how Cerberus understands my custom output from running test cases and compile, because I have not known the fixed format for these outputs.
Thank you.

Hi @brojackvn ,
This processing has to be manually implemented in the Benchmark class.
In Cerberus, we have modified the scripts of the benchmarks to return a status code, which is subsequently read.
If this is not possible, you can read the standard output and standard error and process them if you know the benchmark's format. You would need to replace replace self.run_command with self.exec_command ( I see that the method does not exist but the point still stands, I can probably add this to the development branch if needed).

Hi, we fork the benchmarks, such as Defects4J, to have a version of the repository where we can add additional metadata or files, which Cerberus uses. Initially, we stored a local copy but decided that using submodules would be more effective for storage.
I am not sure I understood the I also see that you have included it in all benchmarks

My point is that every benchmark has its own fork, similar to this repository https://github.com/nus-apr/defects4j.
In Defects4J, each bug includes files like "build_script", "config_script", "clean_script", and "test_script". Do I need to create a similar repository when adding a new benchmark? I'm still unclear on the purpose of this repository, especially when looking at the code for adding benchmark drivers here

Having a repository with files, such as build_script, config_script helps provide a unified interface such that the different tools can use it and not care about the specifics of the benchmark. The Defects4J driver was written before this and has not been updated.
For example, tools in the repository like LLMR or Prompter read from the metadata and use these scripts.
Hopefully this was helpful and am happy to answer more questions :)

Thank you very much for your quick response.
I think I understand the requirements for adding a new benchmark. I am trying to run an example to understand the flow of Cerberus. I have successfully run it on Defects4J, but I am struggling. Here’s what I have done so far, step by step:

Activated the source environment source activate
Installed the required packages pip install -r requirements.txt in my environment.
Ran the command: cerberus -task repair --tool=arja --benchmark=defects4j --bug-index=1.
3.1. First, I received the following error message: "Could not get the submodule. Maybe the system asked for an SSH key, and it could not be provided." Instead of fixing this by adding an SSH key to GitHub, I traced the issue in the log file and ran git submodule update --init benchmark/defects4j, which resolved the error.
3.2. Then, I encountered another error: "[error] Image was not built successfully. Please check whether the file builds outside of Cerberus." I am unsure why Cerberus cannot build the benchmark image. Here's the log output:[framework] loading benchmark defects4j Sep 27 22:54:49
[framework] benchmark environment not found for defects4j-benchmark Sep 27 22:54:49
[framework] building benchmark environment Sep 27 22:54:49
[framework] building docker image defects4j-benchmark Sep 27 22:54:49
Task repair failed Sep 27 22:55:38
[error] Image was not built successfully. Please check whether the file builds outside of Cerberus Sep 27 22:55:38
Error. Exiting... Sep 27 22:55:38
Task repair failed Sep 27 22:55:38
[error] unable to build image: unhandled exception Sep 27 22:55:38
Runtime Error Sep 27 22:55:38
Error. Exiting... Sep 27 22:55:38

Then I printed process of building image by adding a line of code "print(line["stream"])" at line 124 in container.py. I found an error here:
Get:129 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 software-properties-common all <IP_ADDRESS> [10.4 kB]
Get:130 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 unattended-upgrades all 2.3ubuntu0.3 [48.5 kB]
debconf: delaying package configuration, since apt-utils is not installed

Fetched 35.9 MB in 15s (2451 kB/s)
(Reading database ...
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 4124 files and directories currently installed.)

Preparing to unpack .../libsystemd0_245.4-4ubuntu3.24_amd64.deb ...
Unpacking libsystemd0:amd64 (245.4-4ubuntu3.24) over (245.4-4ubuntu3.23) ...
Setting up libsystemd0:amd64 (245.4-4ubuntu3.24) ...
Selecting previously unselected package libssl1.1:amd64.
(Reading database ...
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 4124 files and directories currently installed.)
Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2.23_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.1f-1ubuntu2.23) ...
Selecting previously unselected package libpython3.8-minimal:amd64.
Preparing to unpack .../libpython3.8-minimal_3.8.10-0ubuntu1~20.04.12_amd64.deb ...
Unpacking libpython3.8-minimal:amd64 (3.8.10-0ubuntu1~20.04.12) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../libexpat1_2.2.9-1ubuntu0.7_amd64.deb ...
Unpacking libexpat1:amd64 (2.2.9-1ubuntu0.7) ...
Selecting previously unselected package python3.8-minimal.
Preparing to unpack .../python3.8-minimal_3.8.10-0ubuntu1~20.04.12_amd64.deb ...
Unpacking python3.8-minimal (3.8.10-0ubuntu1~20.04.12) ...
Setting up libssl1.1:amd64 (1.1.1f-1ubuntu2.23) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Setting up libpython3.8-minimal:amd64 (3.8.10-0ubuntu1~20.04.12) ...
Setting up libexpat1:amd64 (2.2.9-1ubuntu0.7) ...
Setting up python3.8-minimal (3.8.10-0ubuntu1~20.04.12) ...
dpkg: error processing package python3.8-minimal (--configure):
 installed python3.8-minimal package post-installation script subprocess was killed by signal (Killed)
Errors were encountered while processing:
 python3.8-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)

Could you help me figure out how to resolve this issue?

Hi, let's take this to a different issue. This sounds like some dependency is stale and I will need to try rebuilding the docker image used by the benchmark ( the image is described by the Dockerfile  in the repository of the benchmark)

Hi, I think the reason is that Defects4J just updated a few things and now requires Java 11, but the original Defects4J forgot to include that in their Dockerfile


Kubeadm

FAILED! => {"changed": true, "cmd": "kubeadm reset", "delta": "0:00:00.031730", "end": "2018-06-28 11:39:08.070430", "msg": "non-zero return code", "rc": 1, "start": "2018-06-28 11:39:08.038700", "stderr": "Aborted reset operation", "stderr_lines": ["Aborted reset operation"], "stdout": "[reset] WARNING: changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.\n[reset] are you sure you want to proceed? [y/N]: ", "stdout_lines": ["[reset] WARNING: changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.", "[reset] are you sure you want to proceed? [y/N]: "]}

This has been fixed


Proposal: do not create a directory in tmp when the DefaultOptions variable is initialized

Hi, can you tell me why when initializing default options a directory is created in tmp. This directory is created in any case, even when the default options are not used or the DirPath field is overridden. At the moment every time I run an application that uses rosedb, an empty directory in tmp is created and I have to delete it. I would suggest that instead of using os.MkdirTemp use os.TempDir to create the path to the temporary directory, because if you use Open when there is no directory it will still be created, so I don't see why a directory should be created when the DefaultOptions variable is initialized.

You can specify a dir path when open the db.

Yes I can do it, but as I wrote above the directory in tmp will be created in any case, because the initialization of the package has already happened, so the DefaultOptions variable is initialized and the tempDBDir function was called where the directory in tmp is created.

create a main.go file:
package main

import (
	"github.com/rosedblabs/rosedb/v2"
)

func main() {
	options := rosedb.DefaultOptions
	options.DirPath = "db_basic"
}

and run the script:
#!/bin/bash

go build main.go

rm -rf $TMPDIR/rosedb-temp*

rosedbDirCnt=$(ls -l $TMPDIR | grep 'rosedb-temp' | wc -l | xargs)

echo "rosedb dirs in tmp is ${rosedbDirCnt}"

rosedbDirCntExpected=100
for i in $(seq ${rosedbDirCntExpected})
do
    ./main
done

rosedbDirCntActual=$(ls -l $TMPDIR | grep 'rosedb-temp' | wc -l | xargs)
echo "rosedb dirs in tmp expected = ${rosedbDirCntExpected} and actual = ${rosedbDirCntActual}"

you will see that the number of directories in tmp will be equal to 100

Oh, I see, this is indeed a problem.
I plan to fix it like this:
func DefaultOptions(path string) Options {
	if len(path) == 0 {
		path = tempDBDir()
	}
	return Options{
		DirPath:           path,
		SegmentSize:       1 * GB,
		Sync:              false,
		BytesPerSync:      0,
		WatchQueueSize:    0,
		AutoMergeCronExpr: "",
	}
}

Make the DefaultOptions a function, and pass the path as an argument, I will only use the temp dir if the argument is null.
Does this will solve your problem?

Oh I see, it is indeed a problem.
I will fix it.

Just return a temp dir name instead of creating it.
func tempDBDir() string {
    return filepath.Join(os.TempDir(), "rosedb-temp"+strconv.Itoa(int(nameRand.Int63())))
}

Does this slove your problem?

Yes, that will solve the problem

I fixed this in v2.3.9.
thanks for your feedback.


Nix cataloger should use find by glob instead of iterating over all files

Catalogers should not iterate over each file and match a glob, but rather use a find by glob. See: https://github.com/anchore/syft/blob/main/syft/pkg/cataloger/nix/cataloger.go#L37-L38

This came up in the original PRs, but there is a technical limitation: the FilesByGlob only raises up files, not directories. But directory names is what is being searched for here. This sounds like a potential enhancement to add new capabilities to the resolver maybe?


Trait-based allocator API

First attempt at the custom allocators proposed in #57, including a default implementation providing memory sharing for multi-window apps and a much smaller VRAM allocation footprint (~72MiB combined for demo_app).
The change was rather intrusive and introduced an <Alloc> generic throughout a lot of the code, both library and client side. Not everything is implemented (namely, command buffer + descriptor allocators are not shared nor user configurable, and there is no support for the user callback API so several examples simply fail with not yet implemented).
I've stopped short because I am not sure how happy I am with this. I think I went too far in making the requirements concrete, to the point that it spills a lot of the implementation details into public view - such as the exact Image/BufferUsage needed for different operations...

I've stopped short because I am not sure how happy I am with this

Might have to sit on it.
I also think this doesn't maybe quite fit what we want for the api, yet at least. If the allocator customization complicates the api too much, letting the user to configure the sizes will also be enough in the short term.

My concern with simply providing sizes is the lack of sharing between user code and the Gui renderer, or between multiple Gui renderers. In my usecase, the texture staging arena will spend all of it's time unused by the Gui except in the first fraction of a second, when it could have been used for any of my app's staging needs.
I am not fully sure how egui 0.24.0 multiwindow functionality works, but if it requires multiple renderers then the ability to share memory between them seems mighty important!
I suppose the sharing between Gui instances could be solved with opaque allocator objects that implement Clone, not far from what's currently in master, keeping encapsulation. But as I've found here, sharing with the user does complicate things.


Cannot use ordinary file browser/selector in Metadata Import (CSV)

Describe the bug
The ordinary file browser / selector to find and upload a CSV file for Import Metadata does not work.  The following console error is shown, and the file is not properly uploaded. This causes the process to start with an empty -f parameter and the backend will fail with a relevant error.
I have reproduced this on https://demo.dspace.org, using Brave / Chromium / Firefox browsers.
ERROR DOMException: Failed to set the 'value' property on 'HTMLInputElement': This input element accepts a filename, which may only be programmatically set to the empty string.
    at J.setProperty (https://demo.dspace.org/main.437a6e98e637e96a.js:1:2364003)
    at ra.setProperty (https://demo.dspace.org/main.437a6e98e637e96a.js:1:1279888)
    at Ge.setProperty (https://demo.dspace.org/main.437a6e98e637e96a.js:1:2302901)
    at Ge.writeValue (https://demo.dspace.org/main.437a6e98e637e96a.js:1:2304409)
    at se (https://demo.dspace.org/main.437a6e98e637e96a.js:1:2321720)
    at https://demo.dspace.org/main.437a6e98e637e96a.js:1:2327026
    at Array.forEach (<anonymous>)
    at Cs.setValue (https://demo.dspace.org/main.437a6e98e637e96a.js:1:2327014)
    at https://demo.dspace.org/main.437a6e98e637e96a.js:1:2330852
    at Y.invoke (https://demo.dspace.org/polyfills.278f210b5f97125d.js:1:16949)

To Reproduce

Log in as an administrator
Click Import -> Metadata in the left-hand admin menu
Click 'browse' to use your browser file selection tool to select a valid CSV to upload (you can construct a simple one or export first to get a valid CSV)
Note the text in the file area afterwards (no filename), and click proceed. The process will immediately fail, and you will see that the -f (filename) parameter has no value
Go back to the import page, and this time drag the CSV from a file browser window onto the file area. This time the import should proceed normally.

Expected behavior
The file selector should work exactly the same as drag and drop.

I'm able to reproduce this on Chrome on Windows as well.
To clarify, everything works fine if you drag & drop a file into the upload box.  The error only occurs if you click the "browse" link in that upload box and then browse to a file to select it.
This bug appears to be specific to the Metadata Import drag & drop box.  I cannot reproduce it in other locations where this same box occurs.
We should retest this when #3189 is fixed, because there might be a slight chance that the two problems are semi-related.  It seems like something on this Metadata Import page is causing links to not work properly.

Good afternoon @tdonohue!
Unfortunately the resolution of issue #3189 doesn't solve this problem either.
We at Neki-it would like this activity to be assigned to us.

@Andrea-Guevara : Thanks, I've assigned this to you for your team to work on.

Good afternoon @tdonohue! Here's a PR with a possible solution to this problem:
https://github.com/DSpace/dspace-angular/pull/3230
We look forward to your feedback.


#203 Fixing the support for GZIP and DEFLATE saved payloads.

Resolves #203.

Seems fine for me. Thanks!

@faucct Thanks for your feedback. Merging.


[Task]: Split ProfileManager into a SecretManager store and selectedWallet store

Use https://github.com/iotaledger/firefly/pull/7726 as base

Remove IProfileManger interface
Split Profile manager into a SecretManager store and selectedWallet (previously selectedAccount)

Refactors needed:

getAccounts
recoverAccounts


Support Java 9

Came up in #858

The issue seems to be testing with Java 9 (and, presumably, Java 10 now) and fixing any bugs that show up.
Adding features to exploit the new capabilities of Java 9 and 10 would be in individual RFEs separate from this test item.

Tested develop branch of Java Client API with Open JDK 11 on Linux 3 node MarkLogic cluster running 9.0 nightly server builds (Nov 1 st week builds).
Here are results:

Had to upgrade gradlew to use gradle version ```4.10``. Change needed in wrapper properties file.
Had to update build.gradle to include  JAXB runtime library to 2.3.0
Used this Gradle dependency in marklogic-client-api project:
compile group: 'org.glassfish.jaxb', name: 'jaxb-runtime', version: '2.3.0'
Minor QA test code changes needed to account for incorrect classloader usage. Need to use application class loader instead of system class loader in ConnectedRESTQA to load test.properties.
ml-development-tools project had one test failure. Refer to #1032.
JaCoCo usage had issues and its plugin usage was commented out. Refer to #1029 , #1030
Two tests from ```marklogic-client-api project failed when JDK 11 was used. Refer to #1033 and #1034
A couple of QA tests were run and loked fine. Will be running entire suite and updating if failures are found.

Assigned to Kiran for time being so that right JDK version to be used can be known, after consulting with Product Mangement, DHF teams.

The JDK versions are being clarified as I write.
Based on Ajit's testing and a few fixes that I checked in, I believe develop can compile and run on 8 - 11.

Have setup Jenkins jobs that handle Java 8, open jdk 9, 10, 11 environments. Had to make gradle (wrapper) changes to handle different Java versions.

9 and 10 are end of life.  8 and 11 have long term support options (till
2024).  JDK 12 is now out.  The jump from 8 to 9+ was the tricky one.  Sure
you want to even bother with 9 and 10?  8, 11, and 12 might be better
picks.  (and 12 will have the same short term shelf life).  Come April
16th, the Oracle JDK 8 (and 11, I believe) will require an extended support
contract to get those builds.   AdoptOpenJDK is the free as in beer LST
versions we are going with.
On Tue, Mar 26, 2019 at 7:38 PM georgeajit<EMAIL_ADDRESS>wrote:

Have setup Jenkins jobs that handle Java 8, open jdk 9, 10, 11
environments. Had to make gradle (wrapper) changes to handle different Java
versions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/marklogic/java-client-api/issues/862#issuecomment-476912409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAzTMG0fH3tLLDfoA4Cwu6f4sMiNC-cks5var1pgaJpZM4Qy13x
.

It makes sense that Java shops migrating off 8 are going straight to 11.  Whether most Java shops that are already on 9 or 10 are quickly moving to 11 is less clear.
Our direction for testing is to move to OpenJDK with the premise that it gives us the broadest set of environments.

I'm managing the transition at our 350k person shop, and this has been a
tremendous amount of ... fun.

Oracle requires a commercial license to run on JDK 8 as of January.  JDK
8u201 is likely the last publicly available version.  April 16th is when
the next set of Oracle release hits - for those with an extended support
contract.  (For example, 7u80 is the last public build, 7u211 is the
current build)
Oracle will have a 'patched' version of 11 for extended support
customers.  For those doing it for free, they must go to 12.  11 Was
identified as an LTS version.
Adopt OpenJDK has a LTS version of 8 and 11.  (and also a 12) . They
dropped 9 and 10 downloads.
Oracle dropped 9 and 10 downloads
RHEL has 8 and 11 OpenJDK LTS Linux versions.  $20 unknown - what does
that mean for Centos users.  RHEL consumers are covered by the license.  9
and 10 appear to be dropped.
RHEL has 8 and 11 OpenJDK builds for windows, with paid support.
Amazon is supporting a free as in beer version of 8 and 11.  (Works nice
too)

This was a nice write up of the different blog options out there.
https://blog.joda.org/2018/09/time-to-look-beyond-oracles-jdk.html?m=1
And download links.  If you have JDK 9 and 10 media - hand on to it,
because those binaries will be hard to come by in a few months.
https://access.redhat.com/articles/1299013
https://adoptopenjdk.net/
https://aws.amazon.com/corretto/
On Fri, Mar 29, 2019 at 11:12 AM Erik Hennum<EMAIL_ADDRESS>wrote:

It makes sense that Java shops migrating off 8 are going straight to 11.
Whether most Java shops that are already on 9 or 10 are quickly moving to
11 is less clear.
Our direction for testing is to move to OpenJDK with the premise that it
gives us the broadest set of environments.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/marklogic/java-client-api/issues/862#issuecomment-478057168,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAzTMddMDotpbXDyLruZ0JRF-JV68aCks5vbjtRgaJpZM4Qy13x
.

Subscribing @aroach337 , who will be interested in the preceding comment.

Poking around - the latest release of adoptopenjdk does still show the 9
and 10 versions.  You just get the tar.gz version, so if you are setting up
Linux
tar -xvf OpenJDK11U-jdk_x64_linux_hotspot_11.0.2_9.tar.gz -C /usr/lib/jvm
vi /etc/environment
PATH=$PATH:/usr/java/jdk-11.0.2+9/bin:
JAVA_HOME=/usr/java/jdk-11.0.2+9
update-alternatives --install /usr/bin/java java
/usr/lib/jvm/jdk-11.0.2+9/bin/java 2
update-alternatives --install /usr/bin/javac javac
/usr/lib/jvm/jdk-11.0.2+9/bin/javac 2
update-alternatives --config java
update-alternatives --config javac
For those on a mac, with homebrew (https://brew.sh/)
As an elevated user...
$ brew tap AdoptOpenJDK/openjdk
$ brew cask info adoptopenjdk11
$ brew cask install adoptopenjdk11
You can do 8 with adoptopenjdk8
On Wed, Apr 3, 2019 at 12:35 PM Erik Hennum<EMAIL_ADDRESS>wrote:

Subscribing @aroach337 https://github.com/aroach337 , who will be
interested in the preceding comment.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/marklogic/java-client-api/issues/862#issuecomment-479586952,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAzTDpY7SVmNlulsv7DDXzQFFGjpNVRks5vdOZzgaJpZM4Qy13x
.


Missing schema name for enum

https://github.com/swagger-api/swagger-core/blob/5a92e3a6b8e8218aa3243bc443e91c8a27af4401/modules/swagger-core/src/main/java/io/swagger/v3/core/jackson/ModelResolver.java#L307
The name of the model is resolved already in previous lines of code, but not set into the StringSchema in case of type enum.

Hi @bennelli when enumAsRef is not applied, which is the default behavior, name should not be set, and the enum should not be part of components/schemas, if you set enumAsRef to true, enum should appear as a component in generated openapi spec, is it solving your issue ? If not, please provide some details about your scenario, for now I am closing the ticket, feel free to reopen if you have any questions


added first draft - pod add and list

Signed-off-by: Dwaipayan Karanjai<EMAIL_ADDRESS>

k8_dpdk_add_remove_test_pods_n_times
[root@wp06 ptf-tests]# ptf --test-dir tests/ k8_dpdk_add_remove_test_pods_n_times --pypath $PWD --test-params="yaml_files='/root/go/src/p4-k8s/example/test_pod.yaml,/root/go/src/p4-k8s/example/test_pod2.yaml';no_of_times='4'" --platform=dummy
/usr/local/bin/ptf:19: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp
Using packet manipulation module: ptf.packet_scapy
k8_dpdk_add_remove_test_pods_n_times.K8_DPDK ... 1/12/2023,6:52:31  PASSED: test pod test-pod running
1/12/2023,6:52:36  PASSED: test pod test-pod2 running
1/12/2023,6:52:36  INFO: Test pods created successfully
1/12/2023,6:52:46  INFO: Finding ip for test-pod
1/12/2023,6:52:46  INFO: Finding ip for test-pod2
1/12/2023,6:52:46  INFO: Pod name and Pod IP mapping: {'test-pod': '<IP_ADDRESS>', 'test-pod2': '<IP_ADDRESS>'}
1/12/2023,6:52:46  INFO: test-pod > ping -c 10 <IP_ADDRESS>
1/12/2023,6:52:55  INFO: 0% packet loss
1/12/2023,6:52:55  PASSED: Ping from test-pod to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,6:52:55  INFO: Deleting test pod test-pod  # 0
test pod test-pod not running
1/12/2023,6:53:00  INFO: Creating test pod test-pod  # 0
1/12/2023,6:53:05  PASSED: test pod test-pod running
1/12/2023,6:53:10  INFO: Deleting test pod test-pod  # 1
test pod test-pod not running
1/12/2023,6:53:16  INFO: Creating test pod test-pod  # 1
1/12/2023,6:53:21  PASSED: test pod test-pod running
1/12/2023,6:53:26  INFO: Deleting test pod test-pod  # 2
test pod test-pod not running
1/12/2023,6:53:31  INFO: Creating test pod test-pod  # 2
1/12/2023,6:53:36  PASSED: test pod test-pod running
1/12/2023,6:53:41  INFO: Deleting test pod test-pod  # 3
test pod test-pod not running
1/12/2023,6:53:46  INFO: Creating test pod test-pod  # 3
1/12/2023,6:53:51  PASSED: test pod test-pod running
1/12/2023,6:53:56  INFO: Finding ip for test-pod
1/12/2023,6:53:57  INFO: Finding ip for test-pod2
1/12/2023,6:53:57  INFO: Pod name and Pod IP mapping: {'test-pod': '<IP_ADDRESS>', 'test-pod2': '<IP_ADDRESS>'}
1/12/2023,6:53:57  INFO: test-pod > ping -c 10 <IP_ADDRESS>
1/12/2023,6:54:06  INFO: 0% packet loss
1/12/2023,6:54:06  PASSED: Ping from test-pod to <IP_ADDRESS> passed with 0% packet loss
ok

Ran 1 test in 100.145s
OK

k8_dpdk_add_remove_test_pods_with_ping_test
[root@wp06 ptf-tests]# ptf --test-dir tests/ k8_dpdk_add_remove_test_pods_with_ping_test --pypath $PWD --test-params="yaml_files='/root/go/src/p4-k8s/example/test_pod.yaml,/root/go/src/p4-k8s/example/test_pod2.yaml,/root/go/src/p4-k8s/example/test_pod3.yaml,/root/go/src/p4-k8s/example/test_pod4.yaml'" --platform=dummy
/usr/local/bin/ptf:19: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp
Using packet manipulation module: ptf.packet_scapy
k8_dpdk_add_remove_test_pods_with_ping_test.K8_DPDK ... 1/12/2023,7:40:16  INFO: test pod test-pod running
1/12/2023,7:40:21  INFO: test pod test-pod2 running
1/12/2023,7:40:26  INFO: test pod test-pod3 running
1/12/2023,7:40:31  INFO: test pod test-pod4 running
1/12/2023,7:40:31  INFO: 4 Pods created
1/12/2023,7:40:41  INFO: Finding ip for test-pod
1/12/2023,7:40:42  INFO: Finding ip for test-pod2
1/12/2023,7:40:42  INFO: Finding ip for test-pod3
1/12/2023,7:40:42  INFO: Finding ip for test-pod4
1/12/2023,7:40:42  INFO: Pod name and Pod IP mapping: {'test-pod': '<IP_ADDRESS>', 'test-pod2': '<IP_ADDRESS>', 'test-pod3': '<IP_ADDRESS>', 'test-pod4': '<IP_ADDRESS>'}
1/12/2023,7:40:42  INFO: test-pod > ping -c 10 <IP_ADDRESS>
1/12/2023,7:40:51  INFO: 0% packet loss
1/12/2023,7:40:51  PASSED: Ping from test-pod to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:40:51  INFO: test-pod > ping -c 10 <IP_ADDRESS>
1/12/2023,7:41:00  INFO: 0% packet loss
1/12/2023,7:41:00  PASSED: Ping from test-pod to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:41:00  INFO: test-pod > ping -c 10 <IP_ADDRESS>
1/12/2023,7:41:09  INFO: 0% packet loss
1/12/2023,7:41:09  PASSED: Ping from test-pod to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:41:09  INFO: test-pod2 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:41:18  INFO: 0% packet loss
1/12/2023,7:41:18  PASSED: Ping from test-pod2 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:41:18  INFO: test-pod2 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:41:27  INFO: 0% packet loss
1/12/2023,7:41:27  PASSED: Ping from test-pod2 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:41:27  INFO: test-pod2 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:41:37  INFO: 0% packet loss
1/12/2023,7:41:37  PASSED: Ping from test-pod2 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:41:37  INFO: test-pod3 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:41:46  INFO: 0% packet loss
1/12/2023,7:41:46  PASSED: Ping from test-pod3 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:41:46  INFO: test-pod3 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:41:55  INFO: 0% packet loss
1/12/2023,7:41:55  PASSED: Ping from test-pod3 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:41:55  INFO: test-pod3 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:04  INFO: 0% packet loss
1/12/2023,7:42:04  PASSED: Ping from test-pod3 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:42:04  INFO: test-pod4 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:13  INFO: 0% packet loss
1/12/2023,7:42:13  PASSED: Ping from test-pod4 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:42:13  INFO: test-pod4 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:22  INFO: 0% packet loss
1/12/2023,7:42:22  PASSED: Ping from test-pod4 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:42:22  INFO: test-pod4 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:31  INFO: 0% packet loss
1/12/2023,7:42:31  PASSED: Ping from test-pod4 to <IP_ADDRESS> passed with 0% packet loss
1/12/2023,7:42:36  INFO: test pod test-pod not running
1/12/2023,7:42:42  INFO: test pod test-pod2 not running
1/12/2023,7:42:47  INFO: test pod test-pod3 not running
1/12/2023,7:42:52  INFO: test pod test-pod4 not running
1/12/2023,7:42:57  INFO: test-pod > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod2 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod2 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod2 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod2 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod2 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod2 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod3 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod3 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod3 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod3 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod3 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod3 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod4 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod4 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod4 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod4 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: test-pod4 > ping -c 10 <IP_ADDRESS>
1/12/2023,7:42:57  FAILED: Exception occurred: (0)
Reason: Handshake status 404 Not Found
1/12/2023,7:42:57  INFO: False% packet loss
1/12/2023,7:42:57  PASSED: Ping from test-pod4 to <IP_ADDRESS> failed as expected
1/12/2023,7:42:57  INFO: Test has PASSED
ok

Ran 1 test in 166.573s
OK


RX support for transactions

DBFlow Version: 4.1.1
Issue Kind (Bug, Question, Feature): Feature
Description:
Currently we have reactive extensions for such things as Queriable, ModelQueriable, ModelAdapter. It would be nice to have a possibility to work with ITransaction in reactive way too.

in 5.0 branch, you will be able to observe on the DBTransactionQueue via:
database.beginTransactionAsync { select from MyModel::class  }
  .asObservable()
  ..//etc

also ITransaction will return a result on the execution, thus allowing you to evaluate that selection and subscribe to its completion:
database.beginTransactionAsync { select from MyModel::class  }
  .asObservable()
  .subscribe { list ->

  }

Thanks a lot.

5.0.0-alpha1 released!


Support node v20

Describe the bug
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^14.17.0 || ^16.0.0 || ^18.0.0". Got "20.0.0"
error Found incompatible module.

Expected behavior
Node version 20 to be supported
To reproduce
Try to add to any node v20 package
Versions

Node.js: 20
ESLint: 8.40.0
plugin: latest

@epaew I would be happy to contribute if you're open to it

@epaew Do you have any plan to upgrade to node v20?

Resolved in #675 and I published v0.9.0.


Add JetPack markdown support to hero and footers and pets

See https://github.com/Automattic/jetpack/issues/155

Fixed with https://github.com/cferdinandi/harbor-wp-theme/pull/44

Still needs to get added to hero


Add group fusion condition reduce fuse broadcast and is broadcast

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.BiynXu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Support for Proxying SOAP Endpoints via Spring Cloud Gateway

Would like to know either Spring cloud gateway support's proxying soap endpoint's ?
In apache camel, we can wrap spring-ws endpoint as below.
    from("spring-ws:rootqname:{"http://camel.apache.org/example/increment}"
    		+ "incrementRequest?endpointMapping=#endpointMapping")
    .unmarshal(jaxb)
    .process(new IncrementProcessor())
    .marshal(jaxb);

how can we do the same in spring-cloud gateway ?

Routing to the target soap endpoint will work fine ...
.route(
r ->
r.path("/security/getToken")
.uri("http://targetendpoint.xyz.com")
)
Is it possible to look into SOAP Body and make some routing decision's ? ... say throttling based on a soap request Body param.  Please advise ?

Tried below , but getting below exception... please advise the best way to intercept soap [xml] request response and log the same via spring cloud gateway
Mono<List<DataBuffer>> monoDataList = xmlReqFlux.collectList();
monoDataList.map(dataA -> logRequest2(dataA)).subscribe();

java.lang.IllegalStateException: Only one connection receive subscriber allowed.
at reactor.netty.channel.FluxReceive.startReceiver(FluxReceive.java:271) [reactor-netty-0.8.4.RELEASE.jar:0.8.4.RELEASE]
at reactor.netty.channel.FluxReceive.subscribe(FluxReceive.java:121) [reactor-netty-0.8.4.RELEASE.jar:0.8.4.RELEASE]
at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) [reactor-core-3.2.5.RELEASE.jar:3.2.5.RELEASE]
at reactor.netty.ByteBufFlux.subscribe(ByteBufFlux.java:294) [reactor-netty-0.8.4.RELEASE.jar:0.8.4.RELEASE]
at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:83) [reactor-core-3.2.5.RELEASE.jar:3.2.5.RELEASE]
at reactor.netty.ByteBufFlux.subscribe(ByteBufFlux.java:294) [reactor-netty-0.8.4.RELEASE.jar:0.8.4.RELEASE]

See http://cloud.spring.io/spring-cloud-static/Greenwich.RELEASE/single/spring-cloud.html#_modify_request_body_gatewayfilter_factory

able to sort this out using .modifyRequestBody instead of filter's... Great thanks 👍 , updated java DSL below...
	.route(
					r ->
					r.path("external/v2/security/")
					.filters( f -> f
							.preserveHostHeader()
							.modifyRequestBody(String.class, String.class,
							(exchange, s) -> {
								Mono<String> dataA = Mono.just(s);
								dataA.subscribe(System.out::print);
								return dataA;
							})								)																										.uri("http://targetendpoint.xyz.com")
					)


Minimum VMs for Silver node types

The documentation states
Maintain a minimum count of five nodes for any virtual machine scale set that has durability level of Gold or Silver enabled. Your cluster will enter error state if you scale in below this threshold, and you'll need to manually clean up state (Remove-ServiceFabricNodeState) for the removed nodes.

This does not appear to be correct - we have clusters with Silver node types with 3 VMs in the scale set, and we see no errors or ill effects. Can you confirm the statement of minimum 5 nodes for Silver durability is correct?
Note that our cluster is spread across availability zones, so we have multiple node types.

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

ID: 658de695-0927-175f-0419-dcf7b6bece9d
Version Independent ID: 8166322c-774b-9434-3df5-5501b7dd9cf1
Content: Service Fabric cluster capacity planning considerations - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-cluster-capacity.md
Service: service-fabric
GitHub Login: @athinanthny
Microsoft Alias: pepogors

@hbuckle
Thanks for the feedback! I have assigned the issue to content author to check and add comments as appropriate.

@athinanthny
Can you please check and add your comments on this doc update request as applicable.

Though it may be possible to have fewer VMs than the required minimum listed for a given durability tier, such scenarios are not officially supported in Azure Service Fabric. If you are running stateful applications, you might run into quorum issues when running without 5 nodes. #please-close

Though it may be possible to have fewer VMs than the required minimum listed for a given durability tier, such scenarios are not officially supported in Azure Service Fabric. If you are running stateful applications, you might run into quorum issues when running without 5 nodes. #please-close


General: Allow admins to hide the password-based login form

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] I followed the coding and design guidelines.

Client

[x] I followed the coding and design guidelines and ensured that the layout is responsive.
[x] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[x] I added multiple screenshots/screencasts of my UI changes.
[x] I translated all newly inserted strings into English and German.

Motivation and Context

@LDAP and @dfuchss  at KIT aim to completely disable password login and rely only on SAML2. Having a password login causes confusion since Artemis credentials do not match SAML2 credentials.
When both authentication options were enabled, it is not obvious to users that when using Single Sign-on they do not have to put anything into the login form.
Description

A new configuration option info.saml2.password-login-disabled was added to the SAML2 config file.
I implemented the client changes, so that this configuration option disables the traditional login form. I also designed the user interface to now make it clear that there are two options to sign in. The UI is responsive and adjusts itself based on the admin's configuration.
The query parameter ?showLoginForm overrides the configuration and displays the password-based login nevertheless (useful for admin login).
Furthermore, I added the info.saml2.idenitity-provider-name configuration setting to optionally add the name of the identity provider to the title on the sign-in page.
Steps for Testing

Prerequisites:

1 Administrator

Start Artemis locally with SAML2 authentication enabled
Make sure both sign on options are visible, working and UI is responsive
Set info.saml2.password-login-disabled: true in your local configuration
Ensure only SSO authentication is visible
Adding the query parameter?showLoginForm to the URL should also display the traditional login form (override)
Disable SAML2 authentication, the password form should appear even though password-login-disabled is set (fallback)

Review Progress

Code Review

[x] Review 1
[x] Review 2

Manual Tests

[x] Test 1
[ ] Test 2

Screenshots

Both traditional and SSO authentication enabled:

Only password-based sign on:

Only SSO (e.g., SAML2) authentication:

I am really looking forward to this feature, I've implemented something very similar for the Hochschule München-Setup.
One small idea: Do you think it would make sense to offer a way for admins to use a local login by e.g. specifying a query parameter?
Gitlab offers a similar feature: https://docs.gitlab.com/ee/integration/saml.html#auto_sign_in_with_provider (?auto_sign_in=false).

One small idea: Do you think it would make sense to offer a way for admins to use a local login by e.g. specifying a query parameter?

I also thought about a similar feature for a follow up PR. For a first implementation I would skip that. But we should track this idea in a Feature (Issue) as it would be very useful :)

One small idea: Do you think it would make sense to offer a way for admins to use a local login by e.g. specifying a query parameter?

I also thought about a similar feature for a follow up PR. For a first implementation I would skip that. But we should track this idea in a Feature (Issue) as it would be very useful :)

I don't think this would be too complicated. Essentially you want a query parameter to override the password-login-disabled option, right? E.g., ?showLoginForm would display the login form nevertheless?

One small idea: Do you think it would make sense to offer a way for admins to use a local login by e.g. specifying a query parameter?

I also thought about a similar feature for a follow up PR. For a first implementation I would skip that. But we should track this idea in a Feature (Issue) as it would be very useful :)

I don't think this would be too complicated. Essentially you want a query parameter to override the password-login-disabled option, right? E.g., ?showLoginForm would display the password-based login nevertheless?

If it's easily possible I would opt for including the feature in this PR :) If not in a Follow-up PR :)

One small idea: Do you think it would make sense to offer a way for admins to use a local login by e.g. specifying a query parameter?

I also thought about a similar feature for a follow up PR. For a first implementation I would skip that. But we should track this idea in a Feature (Issue) as it would be very useful :)

I don't think this would be too complicated. Essentially you want a query parameter to override the password-login-disabled option, right? E.g., ?showLoginForm would display the password-based login nevertheless?

Exactly, that's what I would suggest.

@sleiss @dfuchss Implemented the query parameter override.

e2e tests are failing at the moment. I triggered them again, let's see if they pass.
If not, we should investigate what's going on. They seem to fail constantly for this PR and passed in all other PRs that I recently merged.


MM-49474 - Collect Reason for Downgrade to Free

Summary
When a workspace downgrades from Cloud Professional to Cloud Free self-serve, we currently do not have insights as to why they downgraded. This is useful insight that we should be collecting.
With these changes, users can choose answers via a dropdown, as well as leave additional comments
Reason for downgrade:

Experienced technical issues
No longer need Cloud Professional features
Exploring other solutions
Too expensive

In the options, if the user chooses Other, the comment text box becomes mandatory
Once completed, the downgrade should be fulfilled immediately.
Ticket Link
MM-49474
Screenshots
Downgrade feedback no additional action required
https://user-images.githubusercontent.com/116016004/213802662-bb98ba6c-e922-4525-8dce-6811a94467ac.mov
Downgrade Feedback with team selection
https://user-images.githubusercontent.com/116016004/213802349-b5689213-677d-48e0-8d61-057534b8f308.mov
Test Plan
Happy Path 1 - Non "other" feedback

Ensure you are on a monthly cloud professional license and can downgrade to starter.
In Mattermost, navigate to  the subscription subsection under Billing & Account in the system console.
Click View Plans.
Click the Downgrade option on the free plan.
A feedback modal should appear.
Click any reason except for "other".
Notice you can click the submit button without providing any additional comments in the text box.
Once submitted, the downgrade should happen immediately if no other actions need to be taken.

Happy Path 2 - "Other" feedback

Ensure you are on a monthly cloud professional license and can downgrade to a starter.
In Mattermost, navigate to the subscription subsection under Billing & Account in the system console.
Click View Plans.
Click the Downgrade option on the free plan.
A feedback modal should appear.
Click the "Other" reason.
Notice you cannot submit the feedback without providing any additional comments.
Provide some more comments in the text box.
Notice you can click the submit button after providing additional comments.
Once submitted, the downgrade should happen immediately if no other actions need to be taken.

Happy Path 3 - Feedback after choosing team

Ensure you have at least 2 teams set up in your workspace.
Follow the regular downgrade process, this time selecting the team you'd like to keep
Notice the downgrade feedback modal appears after the team selection modal has been closed.
Select your reason and submit.
Once submitted, the downgrade should happen immediately if no other action needs to be taken.

Release Note
Adds a feedback survey during the downgrade process

/update-branch

Had a PR with the same changes up and full approval recently, but it was parked to avoid conflicts with another higher-priority feature.
This uses the generic feedback modal introduced in the workspace deletion feature (which was built from parts of the aforementioned PR) and has the exact same functionality as before.

You don't have permissions to trigger this command.
It's only available for organization members.

Hi @ConorMacpherson ,

on the spin wick, if we downgrade from Professional, we see the Error screen/failure screen, but then again after reloading, the we can see the instance is now 'Cloud Free'.

The delete workspace is not occurring, I was wondering if there's any setting we might need to do.

/e2e-test SERVET_TYPE=cloud

Triggering E2E testing with options:
&map[SERVET_TYPE:cloud]

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

/e2e-test SERVER_TYPE=cloud

Triggering E2E testing with options:
&map[SERVER_TYPE:cloud]

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

/e2e-test SERVER_TYPE=cloud

Triggering E2E testing with options:
&map[SERVER_TYPE:cloud]

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

/e2e-test SERVER_TYPE=cloud

Triggering E2E testing with options:
&map[SERVER_TYPE:cloud]

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

Hey @yasserfaraazkhan

on the spin wick, if we downgrade from Professional, we see the Error screen/failure screen, but then again after reloading, the we can see the instance is now 'Cloud Free'.

I'm seeing another failure when changing plans on this spinwick server. I just tried to upgrade from cloud free to cloud professional (via the pricing modal), but it fails every time with an error stating:
Received status code 400 from CWS while changing subscription plan
I wonder if this issue is related. In any case, I'm seeing this with downgrades as well, but in some cases, I have to attempt to downgrade twice before this occurs. I'm going to try and hunt down some logs to check the changes we made in the back-end a while back for this. I'll update you with my findings here.

The delete workspace is not occurring, I was wondering if there's any setting we might need to do.

Delete workspace is unrelated to these changes. That being said, the back-end is not merged yet (mm-server, enterprise and cws changes), so I don't think we'll see that working just yet. It's not scheduled for release until 7.9/march in any case.

@yasserfaraazkhan I'm currently waiting to hear back from Security to get me access to the logs for these test servers.
Here are some things I've been noticing though:

The issue is coming from CWS. The only change related to this has been pushed a while back, and we are still able to see the subscription changes succeed in most cases (aside from the issues reported here).
CWS is giving us a 400 response (bad request), any time the subscription change fails

I'm not sure why this is a bad request, I would imagine more of a 500 internal server error, but that's okay.
Looking through the code changes related to the feedback, I don't see anything that would result in the failure caused by the feedback data.

The feedback data may or may not be present, we check this.
The feedback data is only used when downgrading to a freemium product (we also check this).

Once I get more visibility in the logs, I think I'll be able to diagnose this issue a lot better, but I'm confident these changes are not causing this, especially after testing on:

This spinwick test server:

Testing Upgrade to professional path (this is also failing)
Manually moving the subscription product from Cloud Free to Cloud Professional (monthly), and trying to downgrade (obviously fails)

In my Local env

Downgrading with the feedback. As usual, in my local environment, I have to send subscription change requests twice. The first time fails (due the cluster installation not being found, which I think is expected locally) and when I send it again, it fails once more but only because the subscription has already been changed in the last request (I see: Subscription is already on the requested plan prod_LSBESgGXq9KlLj, doing nothing) and everything is updated once I refresh. This is how I've always had to downgrade or upgrade.

On a test server spun up via the test portal (which does not have these changes)

I cannot for the life of me upgrade my subscription without it failing. I always have to change it manually in stripe.
Upgrades are giving me the same, a 400 response from CWS, resulting in a failure and early exist/response in mm-server
This server has the delete workspace modal with the option to downgrade from the modal. I'm seeing the same thing here when I try to change my subscription.

Just to be extra sure, I made a brand new workspace from the test portal (the other one I used was made fairly recently but maybe a few changes behind)

The exact same thing happens here for me that happened in the other workspace from the test portal.

Since we don't know the cause of this issue, I think we should hold off on any kind of testing for this, but it seems like there is something going on with the subscription change endpoints.

@yasserfaraazkhan I think we may have to test this in post-merge.
This flow can only be accessed when a monthly subscription is present. In the past I had been modifying a stripe subscription's product manually to make it a pro monthly subscription, but apparently there is more to this than just modifying it in stripe.
Nick shared a curl command with me that will create a new workspace with a pro monthly subscription setup:
curl --location --request POST 'https://api.internal.test.cloud.mattermost.com/api/v1/internal/installation/with_test_clock' \
--header 'Content-Type: application/json' \
--data-raw '{
    "workspace_name": "new_name",
    "workspace_admin_password": "admin_password",
    "use_test_clock": true,
    "product_id": "prod_K0AxuWCDoDD9Qq"
}'

I think we can use this to test unless you know of another option.

You don't have permissions to trigger this command.
It's only available for organization members.


bluetooth: tester: Increase SDU size to meet PTS requirement

PTS test cases MESH/NODE/TNPT/BV-07-C, MESH/NODE/TNPT/BV-12-C, requires
to receive 8 segment of data which summary requires 108 bytes of SDU.
This patch make test cases PASSing.

@kolodgrz your commit message is missing a Signed-off-by line, which is why Shippable is failing it

Codecov Report

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

@@           Coverage Diff           @@
##           master    #9426   +/-   ##
=======================================
  Coverage   52.19%   52.19%
=======================================
  Files         212      212
  Lines       25921    25921
  Branches     5570     5570
=======================================
  Hits        13529    13529
  Misses      10129    10129
  Partials     2263     2263

Continue to review full report at Codecov.

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


Adjust LIO request helper further

Follow up from https://github.com/ppy/osu-queue-score-statistics/pull/297

Removed support for both text/plain (completely unnecessary ever, web can't do that) and application/x-www-form-urlencoded (web can do that but why leave 2 formats in when 1 can work), leaving only application/json
If the request is made with a null payload object, do not set Content-Type

Test failure should be unrelated...?


WIP:  NCD - Next Steps - Activities

#423

@AronNovak
Please review. Note that this PR defines Next steps activities, and there are several @todos that are logic related, and not implmented here. They're taken care of at #459.


Please reply to

https://github.com/spyder-ide/spyder/issues/8007#issue-367063631

Please stop bugging us and opening repeated issues about the same stuff.


Not create segment for empty table.

What problem does this PR solve?
Issue Number: ref #7595
What is changed and how it works?
Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/approve

/run-all-tests

/run-unit-test


[Environment] Remove init.py from the notebook directory

The init.py adds the notebook directory into the PYTHONPATH and overwrites the notebook module, which makes the opening of notebooks impossible.

solve by renaming the notebook directory into 'fink_fat_notebook'


Swiping to change calendar month in datepicker opens panel instead

This is a:

[x] bug
[ ] enhancement
[ ] feature-discussion (RFC)

Framework7 Version: 1.5.0

Reproducing
App with swipePanel enabled and a datepicker (I think anywhere, but I personally found the issue with an inline calendar)
Expected Behavior
When swiping over a datepicker, the month should change without the panel being opened (just like it happens with Swiper)
Actual Behavior
The datepicker is ignored and the panel is opened instead.

Up !
I have the same problem.

Issue is closed because of outdated/irrelevant/not actual
If this issue is still actual and reproducible for latest version of Framework7, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Body parameters are empty in POST

Whenever making a POST request, the variables passed in body are empty. When passing the following to a POST endpoint, the result is {}
      const res = await api.post('/test', {
          body: {"test" : "test"}
        });

It works perfectly well with GET requests to GET endpoints.

@calhouncole
Would you mind please updating and just checking that you're still having the same issue with v2.0.1?

Closing, if this issue still persists let me know.


Compatibility

Would the software would work with other Quectel BG modems, e.g. BG600L?

I had tested BG600L with the following repository link
Both libraries are too similar, yet BG600L have some limitations regarding to http protocol and mqtt buffer capabilities.
HTTP issues were not solved, I reported the issue to quectel to improve their code. I have no further information since there.
Regarding to MQTT I think this library now will do the work correctly.
So, I expect that BG600L will work fine with this library for most of the cases. If you want to test and contribute to this library feel free to do it ;)


Machine does not have an IP Address

Description
After running nitro init my default machine IP Address reports as "N/A"
Steps to reproduce

Follow other setup instructions
Run nitro init

Additional info
My environment:

Windows 10 Home
Nitro 1.1.1
Multipass 1.5.0+ (multipass-1.5.0+win-win64.exe)
VirtualBox 6.1 (VirtualBox-6.1.18-142142-Win.exe)

Nitro machine spec:
How many CPU cores? [4]
How much memory? [4G]
How much disk space? [40G]
Which version of PHP? [7.4]
Which database engine? [mysql]
Which version of mysql? [5.7] 8

Some error messages that appeared in the log (full output attached):
Unable to disable xdebug, err:  rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup N/A: no such host"
Composer is now installed on "nitro-dev".
Unable to enable display_errors, err:  rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup N/A: no such host"
Nitro installed, ready for something incredible at N/A.

How can I change the IP Address?

Couple other things to note:

After running nitro init, I can right-click Multipass in the taskbar and see "nitro-dev (Running)"
I can also click "Open Shell" and get a PowerShell window with prompt ubuntu@nitro-dev:~$

@KarlBishop thank you for reporting this issue. Unfortunately, on v1, running with VirtualBox is not really tested and we have officially started the process of moving from Multipass to a Docker based backend as Multipass and Windows had a lot of problems with networking and specifically Windows 10 Home support, which is your OS. See this troubleshooting documentation for Multipass and Windows 10.
Switching to Docker made it a lot easier to support Windows 10 and add a lot more features for local development. You can read more about the v2 beta here.
The documentation does specify "Nitro 2 is currently in beta and currently doesn’t support Windows" but we are working on getting the next beta out with the changes needed for Windows 10 along with a detailed documentation for installation. Windows 10 Home will require WSL2 be installed (which is also part of the Docker installation for Windows 10 Home).

OK, thanks for the response. Hope the v2 Windows support is coming along nicely!

We just released Nitro 2 where we switched from Multipass to Docker and added a ton of new features. Please see the announcement for more details.
This issue was specific to Multipass so we are going to close this out. Please see the documentation on upgrading from Nitro 1.


missing define mqtt_port

Hey Ben,
Latest version is missing #define mqtt_port 1883 ;)
Might also be worth adding that a fresh install of the SDK you need to install DHT sensor library and Adfruit unified sensor.
Cheers,
J

Ah, great catch! Thanks for pointing that out. Yeah, can't believe I missed the DHT library in my video. Guess I've had that installed for so long I'd forgotten about it. I'll add a note to the code. Cheers!


Warning: Cannot read property 'name' of null - caused by valid-jsdoc rule

tslint 5.4.3
tslint-eslint-rules 4.1.1

TSlint config:
"valid-jsdoc": [true, {
  "requireReturn": false,
  "requireReturnType": false
}],

Code:
class MyPage {
  /**
   * Navigate to the page
   * @returns a promise for the browser's navigation
   */
  public async navigateTo() { }
}

Getting this warning:
Warning: Cannot read property 'name' of null

When i can expect release with this fix?


Sending base64 encoded image to API server

Hi, thank you for this project. I am trying to access the analyze endpoint that is hosted locally (localhost:5000/analyze) by providing the base64 encoded image. However, the web server does not seem to recognize the base64 encoded image (unless I am missing something).
Request body:
{
  "img_path": "<base64 string of image>"
}

The server returns:
{
    "error": "Exception while analyzing: Confirm that <base64 string of image> exists"
}

Is there something I am missing here? A separate value to signal that I'm sending a base64 encoded image?

Oh you are sending , this should be base64 encoded string.
E.g. data:image/...

Oh you are sending < base64 string of image >, this should be base64 encoded string.
E.g. data:image/...

Oh you're right, that was the problem! Thank you for the swift reply.


Generated template needs additional files

I wanted to report a few issues I ran into when working with the generated device template.
One currently has to manually add a number of additional files for the project to compile:

cmake/PrefixHandling.cmake
cmake/prefix_defs.txt
include/qdmi/device.h and its dependencies

Futhermore, one has to edit the root CMakeLists.txt to add the following lines:
# set some important directories
set(QDMI_INCLUDE_BUILD_DIR
    "${CMAKE_CURRENT_SOURCE_DIR}/include"
    CACHE INTERNAL "Include directory")
set(QDMI_TEST_DIR
    "${CMAKE_CURRENT_SOURCE_DIR}/test"
    CACHE INTERNAL "Test directory")
set(QDMI_CMAKE_DIR
    "${CMAKE_CURRENT_SOURCE_DIR}/cmake"
    CACHE INTERNAL "CMake directory")

Thanks you @denialhaag for bringingin up this issue. Unfortunately, I cannot reproduce the problem on my machine.
We just merged a new PR #90 that add an extensive explanation of the usage of the templates Could you please read thorugh those steps and check whether they resolve your problem. If the problem persists, could you please detail the steps until you encountered the issue such that it is easier for us to figure out what happened there?
Thank you so much for your collaboration!

My bad, I pulled QDMI, cretaed a new template, and it worked like a charm. Maybe it was related to the pinned revision. 🤔

My bad, I pulled QDMI, cretaed a new template, and it worked like a charm. Maybe it was related to the pinned revision. 🤔

That could very much be it.
We adjusted that part in the latest PR.
Going to close this for now. Feel free to reopen if any problems still arise.


how to render a augment matrix with vertical bar?

Thanks for  the package,  it is very useful!
here is my question:
how to render  an augment matrix with vertical bar?
Actually  has  another question: how to express a  linear combination ?

LaTeXStrings does not do any LaTeX rendering, it just makes it easier to type LaTeX expressions as Julia strings.


Update UserController's post method to not create Users with identical email

We must make sure that users are not able to create accounts with the same email address as this is our unique identifier for the users.

I'd like to finish this tomorrow, Friday 1/13 @ appdev meeting :stuck_out_tongue:


fix: esl-panel and esl-panel-group transition end handling

:tada: This PR is included in version 3.14.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ File access has degraded performance

In 1800e0c, File access (https://fyle.uk/file/fish) experienced degraded performance:

HTTP code: 200
Response time: 5395 ms

Resolved: File access performance has improved in 336e405 after 8 minutes.


snap screen  on windows 11 number doesn't match system display

when I use snap screen one, the window moves to the second screen, and vice versa.

So the numbers that talon uses for screens don't match the ones that windows uses. We should keep this issue open to track making it so that they do match. For now you can use the "screen numbers" command in order to see what numbers talon is using for your screen

Related issue
https://github.com/talonhub/community/issues/841

The pull request to rely on talon's screen ordering have merged. I'm gonna close this for now; if the ordering in Talon and the operating system doesn't match that sounds like a issue or bug report for Talon, not community.