Adds odo service list -o json

Adds odo service list -o json support.
To test:
github.com/openshift/odo  add-service-listing-json ✔                                                                                0m
▶ ./odo service list -o json --context ~/nodejs-ex | jq
{
  "kind": "ServiceList",
  "apiVersion": "odo.openshift.io/v1alpha1",
  "metadata": {
    "creationTimestamp": null
  },
  "items": [
    {
      "name": "foobar2",
      "type": "dh-postgresql-apb",
      "status": "ProvisionedAndBound",
      "plan": "dev"
    }
  ]
}

Closes https://github.com/openshift/odo/issues/2054

This is a WIP
/hold

Ready for review!
Thanks :)
/hold cancel

Ready for review @girishramnani @dharmit @kadel

/test v4.2-benchmark

Please have another look @kadel !
Here's the new output:

{
  "kind": "ServiceList",
  "apiVersion": "odo.openshift.io/v1alpha1",
  "metadata": {
    "creationTimestamp": null
  },
  "items": [
    {
      "kind": "Service",
      "apiVersion": "odo.openshift.io/v1alpha1",
      "metadata": {
        "creationTimestamp": null
      },
      "spec": {
        "name": "foobar2",
        "type": "dh-postgresql-apb",
        "plan": "dev"
      },
      "status": {
        "status": "ProvisionedSuccessfully"
      }
    }
  ]
}

@cdrage It's not working with jq when no services are deployed. Is that expected?
$ odo service list -o json | jq .
{"kind":"Error","apiVersion":"odo.openshift.io/v1alpha1","metadata":{"creationTimestamp":null},"message":"There are no services deployed for this application"}

@dharmit that's an issue with jq :)
odo pushes to stderr when there is an error (like it should be), but jq doesn't do input from stderr.
For jq you have to use: ./odo project delete foobar -o json &> /dev/stdout | jq (for an example)

#2088
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_odo/2098/pull-ci-openshift-odo-master-v4.2-integration/90#0:build-log.txt%3A2972
/retest

I think @kadel's concerns have been taken care of by defining structs as per his feedback.
/lgtm


Cannot use it offline!

Is there any need to do this func [_download_additional_modules]?????

Despite I have download the metrics and use [evaluate.load('./metrics/bleu')], there is a high chance that it will attempt to connect to the network and download additional modules. What confuses me the most is that it doesn't necessarily trigger network downloads, but rather with a high probability, which is very strange for a fixed piece of code.


Error message may confuse users

I may have found a bug, when you have a short argument that takes a value and you don't put a space between it and the value and you then have another argument that needs to take a value the error generated isn't correct.
$./a.out -l6
error: missing argument for 'l' in -l6
$./a.out -Fl6 --long 10
error: cannot parse '--long' as an integer

I see what is happening the parser is trying to convert  '--long' to an int and that's not working.  Is there a way to parse the value in this way or would it be possible to generate the error missing argument message rather that the cannot parse message?
I'm trying to replace argp and this project is spot on for my needs

I found a work around
https://github.com/dmulholl/args/blob/ee4a67b88f403b032260533fb8d88e08bf4b75b4/src/args.c#L1235-L1237
I replaced this with the following code
        if (strlen(arg) > 1) {
            //exit_with_error("missing value for '%c'", arg[i], arg);
            if (!option_try_set(option, (char*)(arg + i + 1))) {
                ap_set_memory_error_flag(parser);
            }
            break;
        }

This will allow short options to accept values with out a space or equals just like argp does.  thus a -l6, -l 6 or -l=6 are all treated the same,  and I get a proper missing value error.  I won't open a pull request for this as I don't believe this is how you intended short arguments to get thier values, it's more a hack to be complatible what I used before.
Thank you again for this wonderful project!


inline CreateConfigMap into the places where it is used

Description
Inlined CreateConfigMap present in tests/utils.go  into the places where it is used .
What this PR does
Before this PR:
The functions CreateConfigMap in tests/utils.go doesnot look so useful because these function being called again and again in various file.
After this PR:
This function is removed from tests/utils.go and inlined into the place where they are used.

Fixes #11436
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

None

@0xFelix  please look over this changes

That looks good so far. Only one nit, could you put something into the body of the commit message please? Something similar to what you have written in the PR description. Thanks!
Let's see what CI says
/test all

@anishbista60 You need to rebase this PR before it can be merged, thanks.

@0xFelix Except squash commit . Is here any extra changes to be done ?

Same comment as on #11450

@0xFelix Done sir and thankyou for guiding me.

Sure and same comment as on #11450

@0xFelix  over here also

@alicefr sure, please look over it .

Looks good!
/approve

@anishbista60 please fix the build failures. The files should be modified after the compilation. See pull-kubevirt-build CI job

i think i did one big mistake , when i cloned the repo. git status was showing
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified:   bazel/toolchain/aarch64-none-linux-gnu/wrappers/aarch64-none-linux-gnu-ar
modified:   bazel/toolchain/aarch64-none-linux-gnu/wrappers/aarch64-none-linux-gnu-cpp
modified:   bazel/toolchain/aarch64-none-linux-gnu/wrappers/aarch64-none-linux-gnu-gcc
modified:   bazel/toolchain/aarch64-none-linux-gnu/wrappers/aarch64-none-linux-gnu-gcov
modified:   bazel/toolchain/aarch64-none-linux-gnu/wrappers/aarch64-none-linux-gnu-ld
modified:   bazel/toolchain/aarch64-none-linux-gnu/wrappers/aarch64-none-linux-gnu-nm
modified:   bazel/toolchain/aarch64-none-linux-gnu/wrappers/aarch64-none-linux-gnu-objdump
modified:   bazel/toolchain/aarch64-none-linux-gnu/wrappers/aarch64-none-linux-gnu-strip
    These changes are automatically happen so that  i discard this changes

    with `git checkout --`
    That's why job are failing

    Now, Can i retrive these changes ? How to solve that problem ?

Run make format and amend the changes to your commit. That should solve the issue.

@0xFelix  shall i  format it from root  or /bazel folder.

@0xFelix   I run the make fomat from /kubervirt directory.

@0xFelix i'm scared looking what's happening

@0xFelix could you please checkout this changes

/hold
@anishbista60 please remove all the changes to the aarch64 files

/test all

@alicefr  but the working directory is clean . Why jobs are failing?

 You need to run make format at the project's root. Then you need to amend the changes to your commit.

 You need to run make format at the project's root. Then you need to amend the changes to your commit.

Is this a cause for failing of job.
for format shall i run for main or inline-02 branch?

You need to format your changes in inline-02.

@0xFelix yeah done sir , Run the make format from /kubevirt inline-02 branch  and ammed the changes .please check it out

@0xFelix sorry for push  , got confused with  changes made by make format and finally got to know that it was made bymake format  and again rebase to previous changes.

/test all

@0xFelix  which changes do i need to take ? got confused

@anishbista60 how is it going with this one? Please remember to remove the merge commit. You shouldn't have merge commits in the PR, just the commits you want to add in the main branch.

@victortoso yeah , going to Modify it

/test pull-kubevirt-build
/test pull-kubevirt-generate

/test all

@0xFelix I check the log but unable to figure out . could please suggest how to troubleshoot? OR do i need to run make generate

/test pull-kubevirt-e2e-k8s-1.29-sig-storage
/test pull-kubevirt-e2e-arm64

I check the log but unable to figure out

Just some unrelated issues, it seems. In the sig-storage we have admission webhook "datavolume-mutate.cdi.kubevirt.io" denied the request: etcdserver: request timed out. e2e-arm64 shows a panic due lack of memory.
Please have pacience, your PR will be reviewed and if anything else is pending, we'll let you know.

@victortoso if you don't mind , could you please re run pull-kubevirt-check-tests-for-flake

@0xFelix could you please re run pull-kubevirt-check-tests-for-flakes

/test pull-kubevirt-check-tests-for-flakes

/test pull-kubevirt-check-tests-for-flakes

@alicefr unable to figure out the reason behind it . Could you please suggest?

@0xFelix could you please test it ?

Sure!
/test all

@0xFelix every thing looks good but why job are failing. could you please assist me  and re Run the failed case .

@anishbista60 Looks like flakes. Retesting.
/test pull-kubevirt-conformance-arm64
/test pull-kubevirt-e2e-k8s-1.29-sig-storage
/test pull-kubevirt-check-tests-for-flakes

@0xFelix please remove the hold label.

@0xFelix remove the extra space. Now , i hope flakes job will pass .

/test all

@0xFelix now it's enough Seeing flakes  getting failed again and again . It's code fault or testing issue .

@anishbista60 Not your fault.
/test pull-kubevirt-check-tests-for-flakes

@0xFelix no way Again failed .

Looks to me like the lane is running longer than its definition permits.
@dhiller Can you help with this?

@0xFelix looks this Issue is already merged on someone else PR  .

Looks to me like the lane is running longer than its definition permits.
@dhiller Can you help with this?

@0xFelix hm, I see that the lane is trying to run 750 test cases, among those migration and operator tests. This is an edge case where not only large test files containing many tests have been changed but also those tests take a long time to run.
Honestly, I would not want to extend the time this lane runs to more than it is allowed to now. Instead we should work to split up the test files that have many tests into segments so that the number of tests inside a test file becomes smaller.
This would in many cases help reduce the number of tests being run on the check-test-for-flakes lane. A positive side effect of this would be making it easier for people coming into the project understand what the tests do.
WDYT?


beforelayout event emit twice when workerEnabled=true

G6 version 3.7.0

Thanks, it will be fixed by 3.7.2

it  happens in  version 4.8.24, too


fixes Encoding::UndefinedConversionError, xC4 from ASCII-8BIT to UTF-8 from logger.rb

$ ruby -v
ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-linux]

(master)$ bundle exec cap staging deploy
  (...)

  * executing "sudo -u mongrel find /home/httpd/html/my_app/releases/20150617094735/public/images /home/httpd/html/my_app/releases/20150617094735/public/stylesheets /home/httpd/html/my_app/releases/20150617094735/public/javascripts -exec touch -t<PHONE_NUMBER>47.44 -- {} ';'; true"
    servers: ["dev55.non.3dart.com"]
    [dev55.non.3dart.com] executing command
*** [deploy:update_code] rolling back
  * executing "sudo -i -u mongrel rm -rf /home/httpd/html/my_app/releases/20150617094735; true"
    servers: ["dev55.non.3dart.com"]
 ** [deploy:update_code] exception while rolling back: Encoding::UndefinedConversionError, "\xC4" from ASCII-8BIT to UTF-8
/home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/logger.rb:137:in `write': "\xC5" from ASCII-8BIT to UTF-8 (Encoding::UndefinedConversionError)
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/logger.rb:137:in `puts'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/logger.rb:137:in `block in log'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/logger.rb:135:in `lines'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/logger.rb:135:in `each'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/logger.rb:135:in `log'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/logger.rb:146:in `important'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/actions/invocation.rb:15:in `block in included'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/command.rb:245:in `[]'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/command.rb:245:in `block (4 levels) in open_channels'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/net-ssh-2.9.1/lib/net/ssh/connection/channel.rb:578:in `call'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/net-ssh-2.9.1/lib/net/ssh/connection/channel.rb:578:in `do_extended_data'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:571:in `channel_extended_data'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:465:in `dispatch_incoming_packets'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:221:in `preprocess'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/processable.rb:17:in `block in process_iteration'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/processable.rb:45:in `block in ensure_each_session'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/processable.rb:43:in `each'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/processable.rb:43:in `ensure_each_session'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/processable.rb:17:in `process_iteration'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/command.rb:171:in `block (2 levels) in process!'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/command.rb:170:in `loop'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/command.rb:170:in `block in process!'
  from /home/mkalita/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/command.rb:169:in `process!'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/command.rb:140:in `process'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/actions/invocation.rb:198:in `block in run_tree'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/connections.rb:205:in `block in execute_on_servers'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/connections.rb:193:in `each'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/connections.rb:193:in `each_slice'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/connections.rb:193:in `execute_on_servers'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/actions/invocation.rb:196:in `run_tree'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/actions/invocation.rb:155:in `run'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/artrails_capistrano-0.0.14/lib/artrails_capistrano/capistrano.rb:45:in `run'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy.rb:298:in `block (2 levels) in load'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `instance_eval'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `invoke_task_directly'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:25:in `invoke_task_directly_with_callbacks'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:110:in `block in define_task'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy.rb:254:in `block (2 levels) in load'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `instance_eval'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `invoke_task_directly'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:25:in `invoke_task_directly_with_callbacks'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:110:in `block in define_task'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy.rb:234:in `block (3 levels) in load'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:56:in `transaction'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy.rb:233:in `block (2 levels) in load'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `instance_eval'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `invoke_task_directly'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:25:in `invoke_task_directly_with_callbacks'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:191:in `method_missing'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/namespaces.rb:110:in `block in define_task'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy.rb:201:in `block (2 levels) in load'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `instance_eval'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `invoke_task_directly'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/callbacks.rb:25:in `invoke_task_directly_with_callbacks'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:89:in `execute_task'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/configuration/execution.rb:101:in `find_and_execute_task'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:46:in `block in execute_requested_actions'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:45:in `each'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:45:in `execute_requested_actions'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/cli/help.rb:19:in `execute_requested_actions_with_help'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:34:in `execute!'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/lib/capistrano/cli/execute.rb:14:in `execute'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/gems/capistrano-2.15.5/bin/cap:4:in `<top (required)>'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/bin/cap:23:in `load'
  from /home/me/my_app/vendor/bundle/ruby/1.9.1/bin/cap:23:in `<main>'

Forcing the encoding without checking the underlying system does not "fix" it! – If your terminal locally has settings other than those remotely for the following env vars, that's probably where the problems comes in.
LANG
LC_ALL
LC_COLLATE
LC_CTYPE
LC_MESSAGES
LC_MONETARY
LC_NUMERIC
LC_TIME

Check that with:
$ env | egrep 'LANG|LC_*'

And you'll see the values. It may, under some circumstances be correct to force UTF-8, but Ruby probably originates that value here, or somewhere similar http://ruby-doc.org/core-2.2.0/Encoding.html#method-c-default_external Unfortunately the source there leads directly into C-land, and you don't really see how Ruby sets the stream encoding.
Probably the safest thing for us to do would be internally to force the encoding to BINARY, and then your terminal could interpret it however you like. The SSH stream itself is a pure (8bit) byte stream, and has no concept of character encoding.

 In my case this difference is a problem:
LANG=pl_PL.UTF-8
vs
LANG=en_US.UTF8

But as you suggested, why not use .force_encoding('BINARY') instead? What do we have to lose in these logs?
LANG variable incompatibility is a common scenario, so if not fixed, this should in be mentioned in the docs? Don't you agree?

I can't say how it works internally, but forcing the encoding at the Ruby level isn't the right choice as I see it. I don't understand how this works between your local terminal emulator (which is character encoding aware), the protocol (which is binary) and the remote program which prints (which may, also be character set aware) when you use SSH normally.

LANG variable incompatibility is a common scenario, so if not fixed, this should in be mentioned in the docs? Don't you agree?

Well, ideally we'll come up with the right way to fix it.

So, having had a look normally SSH (not Ruby, Net::SSH, SSHKit, etc) allow LANG, see AcceptEnv  here.
A related issue on Net:SSH seems to suggest that you might be able to add some things to.ssh/config (we can support that in the project dir, from which you invoke cap, and in ~/.ssh/config):

https://github.com/net-ssh/net-ssh/issues/145#issuecomment-44292997

Net::SSH however doesn't seem to know SetEnv, see http://net-ssh.github.io/net-ssh/classes/Net/SSH/Config.html - maybe that is the solution, to make Net::SSH aware of SetEnv calls, and to set some sane defaults on the connection?

Actually, unified LANG did not help. I have 2 servers with different Ruby version 1.9 vs 2.x, that may be the reason. I have to stick to the patch for now.


Bug with face coordinates

Somewhere there is an issue with coordinates so that if more than one face is detected, the coordinates come out wrong. This only affects y_max. I think an array is being set incorrectly somewhere.

Oh and I should point out this isn't just a dodgy match on one photo, all photos with 2+ people do this :)

[{"confidence":0,"userid":"unknown","y_min":195,"x_min":320,"y_max":257,"x_max":372},{"confidence":0,"userid":"unknown","y_min":195,"x_min":169,"y_max":232,"x_max":219},{"confidence":0,"userid":"unknown","y_min":195,"x_min":127,"y_max":212,"x_max":173},{"confidence":0,"userid":"unknown","y_min":195,"x_min":251,"y_max":216,"x_max":299},{"confidence":0,"userid":"unknown","y_min":195,"x_min":313,"y_max":203,"x_max":361},{"confidence":0,"userid":"unknown","y_min":195,"x_min":58,"y_max":182,"x_max":107},{"confidence":0,"userid":"unknown","y_min":195,"x_min":220,"y_max":264,"x_max":275}]

Thanks for a great bug report. Can replicate the bug.
Unfortunately, it looks like a bug in Deepstack itself, calling the Deepstack API directly (latest version on docker hub https://hub.docker.com/layers/deepquestai/deepstack/jetpack/images/sha256-45375412cd073a9146435e1bd281b4f3c18f5da7c17566f2dcc9f11860a50b36?context=explore) produces the same errors in the result).
I'll see if I can file a bug directly with the Deepstack team.

I've brought it to the Deepstack forum: https://forum.deepstack.cc/t/prediction-wrong-y-min-coordinates-when-calling-vision-face-recognize/923


v1.8 backports 2020-10-22

#13383 -- daemon: Enable configuration of iptables --random-fully (@kh34)

Minor conflicts due to Helm refactoring.

#12975 -- Use net.JoinHostPort to construct network address strings (@tklauser)

Pulled in to simplify the backport of the next PR.

#13244 -- lbmap: Correct issue that port info display error (@Jianlin-lv)
#13651 -- docs: fix minor issue in cilium support with external etcd gsg (@fristonio)

Minor conflicts due to Helm refactoring.

#13645 -- docs: GKE - fix some indentation, specify bash code segments (@ti-mo)
#13661 -- docs: Fix broken formating and link (@pchaigno)
#13683 -- endpoint: Fix goroutine leak when EP is deleted (@christarazi)
#13673 -- docs: improve Host Firewall GSG (@qmonnet)

Minor conflicts due to Helm refactoring.

#13556 -- install/kubernetes: consistent case spelling of iptables related values (@tklauser)

Minor conflicts due to Helm refactoring.

#12408 -- ci: refactor curl / wget test helpers with retries (@JieJhih)

Pulled in to simplify backport of the next PR.

#13694 -- test: improve debugging of dns issues, add retries to external conn check (@nebril)

Pulled in to fix flake introduced by #13383.

Skipped due to potential regression:

#13608 -- daemon: Init endpoint queue during validation (@christarazi)

Once this PR is merged, you can update the PR labels via:
$ for pr in 13383 12975 13244 13651 13645 13661 13683 13673 13556 12408 13694; do contrib/backporting/set-labels.py $pr done 1.8; done

@pchaigno Could you pick up #13556 as well which changes the helm option name introduced by #13383? I forgot to mark it as needs-backport/1.8 initially but now did so.

@pchaigno Could you pick up #13556 as well which changes the helm option name introduced by #13383? I forgot to mark it as needs-backport/1.8 initially but now did so.

@tklauser Done, please have a look.

test-backport-1.8

There was an out-of-band thread discussing whether the presence of #13383 means that we should also wait for https://github.com/cilium/cilium/pull/13694 before merging this set of backports.

test-backport-1.8

retest-4.19

Same test failed:
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.17-kernel-4.19/19/testReport/junit/Suite-k8s-1/17/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_direct_routing_Tests_NodePort_with_externalTrafficPolicy_Local/
If it's failed twice in a row, it seems less likely to be a random flake so we should do further investigation of the failure.
I'm not sure how it compares to the other issues in K8sServicesTest reported previously: https://github.com/cilium/cilium/issues?q=is%3Aissue+is%3Aopen+"exitcode%3A+42" but it seems like those were more like occasional flakes rather than a reliable failure.

retest-4.19

Looks like CI is passing on this PR. Maybe it was a flake that just so happened to occur twice in a row?

actually, it could just be reader error on my side. It looks to me like retest-4.19 actually triggers the K8s-1.18-Kernel-4.19 job which was successful (and would've been successful before too):
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Kernel/3580/


Compilation error with VS2019 (Preview, MSVC19.20)

Seems like this fails for every query.
Flag /permissive- is set, C++17.
1>include\sqlpp11/select_column_list.h(272): error C2955: 'sqlpp::result_t': use of class template requires template argument list
1>include\sqlpp11/result.h(62): note: see declaration of 'sqlpp::result_t'
1>include\sqlpp11/statement.h(118): note: see reference to class template instantiation 'sqlpp::select_column_list_t<First,sqlpp::expression_alias_t<T,sqlpp::count_t<sqlpp::noop,sqlpp::column_t<Table,db::service::StartupAction_::StartupActionId>>::_auto_alias_t>>::_result_methods_t<sqlpp::statement_t<Db,sqlpp::no_with_t,sqlpp::select_t,sqlpp::no_select_flag_list_t,sqlpp::select_column_list_t<First,sqlpp::expression_alias_t<T,sqlpp::count_t<sqlpp::noop,sqlpp::column_t<Table,db::service::StartupAction_::StartupActionId>>::_auto_alias_t>>,sqlpp::no_from_t,sqlpp::no_where_t<true>,sqlpp::no_group_by_t,sqlpp::no_having_t,sqlpp::no_order_by_t,sqlpp::no_limit_t,sqlpp::no_offset_t,sqlpp::no_union_t,sqlpp::no_for_update_t>>' being compiled
1>        with
1>        [
1>            First=void,
1>            T=sqlpp::count_t<sqlpp::noop,sqlpp::column_t<db::service::StartupAction,db::service::StartupAction_::StartupActionId>>,
1>            Table=db::service::StartupAction,
1>            Db=void
1>        ]
1>include\sqlpp11/statement.h(160): note: see reference to class template instantiation 'sqlpp::detail::statement_policies_t<Db,sqlpp::no_with_t,sqlpp::select_t,sqlpp::no_select_flag_list_t,sqlpp::select_column_list_t<First,sqlpp::expression_alias_t<T,sqlpp::count_t<sqlpp::noop,sqlpp::column_t<Table,db::service::StartupAction_::StartupActionId>>::_auto_alias_t>>,sqlpp::no_from_t,sqlpp::no_where_t<true>,sqlpp::no_group_by_t,sqlpp::no_having_t,sqlpp::no_order_by_t,sqlpp::no_limit_t,sqlpp::no_offset_t,sqlpp::no_union_t,sqlpp::no_for_update_t>::_result_methods_t' being compiled
1>        with
1>        [
1>            Db=void,
1>            First=void,
1>            T=sqlpp::count_t<sqlpp::noop,sqlpp::column_t<db::service::StartupAction,db::service::StartupAction_::StartupActionId>>,
1>            Table=db::service::StartupAction
1>        ]
1>D:\dev\cppan2\client\src\manager\database.cpp(349): note: see reference to class template instantiation 'sqlpp::statement_t<Db,sqlpp::no_with_t,sqlpp::select_t,sqlpp::no_select_flag_list_t,sqlpp::select_column_list_t<First,sqlpp::expression_alias_t<T,sqlpp::count_t<sqlpp::noop,sqlpp::column_t<Table,db::service::StartupAction_::StartupActionId>>::_auto_alias_t>>,sqlpp::no_from_t,sqlpp::no_where_t<true>,sqlpp::no_group_by_t,sqlpp::no_having_t,sqlpp::no_order_by_t,sqlpp::no_limit_t,sqlpp::no_offset_t,sqlpp::no_union_t,sqlpp::no_for_update_t>' being compiled
1>        with
1>        [
1>            Db=void,
1>            First=void,
1>            T=sqlpp::count_t<sqlpp::noop,sqlpp::column_t<db::service::StartupAction,db::service::StartupAction_::StartupActionId>>,
1>            Table=db::service::StartupAction
1>        ]
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\VC\Tools\MSVC\14.20.27027\include\filesystem(2066): note: see reference to class template instantiation 'std::chrono::time_point<std::filesystem::_File_time_clock,std::filesystem::_File_time_clock::duration>' being compiled
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\VC\Tools\MSVC\14.20.27027\include\xstring(1689): note: see reference to class template instantiation 'std::basic_string_view<wchar_t,std::char_traits<wchar_t>>' being compiled
1>include\sqlpp11/select_column_list.h(278): error C2955: 'sqlpp::result_t': use of class template requires template argument list
1>include\sqlpp11/result.h(62): note: see declaration of 'sqlpp::result_t'
1>Done building project "13186bd5.vcxproj" -- FAILED.

Also opened on VS dev community: https://developercommunity.visualstudio.com/content/problem/401091/clexe-1920-error-with-sqlpp11-library.html

Hi Egor,
I might be reading the error message wrong, but the compiler seems to complain about missing template parameters for result_t although they are clearly there.
For most use cases you could just delete that function. It is required only for composite statements, see tests/CustomQuery.cpp.
I hope that the problem will be resolved in the next preview.
Best,
Roland

For most use cases you could just delete that function.

Sorry, did not understand. _run() functions are used in sqlpp. How can it be deleted?
My code, for reference:
    const auto actions = db::service::StartupAction{};
    auto c = ((*db)(
        select(count(actions.startupActionId))
        .from(actions)
        .where(actions.startupActionId == action.id and actions.action == action.action)
        )).front().count.value();
    return c == 1;

Ah, sorry, I did not see that it is complaining about the second _run function, too :-(

Commenting trailing return types and moving them explicitly to return helps:

      template <typename Db, typename Composite>
      auto _run(Db& db, const Composite& composite) const// -> result_t<decltype(db.select(composite)), _result_row_t<Db>>
      {
        return result_t<decltype(db.select(composite)), _result_row_t<Db>>{db.select(composite), get_dynamic_names()};
      }

      template <typename Db>
      auto _run(Db& db) const// -> result_t<decltype(db.select(std::declval<_statement_t>())), _result_row_t<Db>>
      {
        return result_t<decltype(db.select(std::declval<_statement_t>())), _result_row_t<Db>>{db.select(_get_statement()), get_dynamic_names()};
      }

Is it worth it commit this workaround into develop?

That is only working with C++14, I am afraid.

Definitely I did not check other compilers, but my VS C++ standard is set to 17.

My understanding (I have no Windows myself and rely on Appveyor) is that this is fixed.
Closing.
Please open a new ticket, if you are still experiencing compilation issues with current master and current Visual Studio.


Omitted API : GET /v1/item-tokens

Summary
Official API document says there is API for getting contractId of all item tokens, but it is not implemented on this SDK.
Problem Definition

I am implementing DOSI NFT services' admin page for my company.
Almost every API requires contractId as a parameter, but in this SDK, there is no method for getting full list of contractId of item tokens, which makes it impossible to implement item token manager page without prior knowledge of contractId.
I found an API for getting list of contractId for item tokens - GET /v1/item-tokens, but it is not implemented in this SDK.
I suggest implementing a new method itemTokens  on class HttpClient which calles the omitted API above.

Proposal
// lib/http-client-base.ts
export class HttpClient {
  // ...

  public itemTokens(): Promise<GenericResponse<ItemToken>> {
    const path = `/v1/item-tokens`;
    return this.instance.get(path);
  }

  // ...
}

I've tested this code works fine on my project. I think there should be optional parameters to handle txHash or isOnlyContractId query parameters, though.
Check-list

[x] Not duplicate issue

Response type should be ItemToken instead of Array<ItemToken>. Sorry for mistake.

@YuheiNakasaka
Oh I got it.

I think js sdk docs should be updated...

@fifteenmania js sdk docs already has it.
Do you want something else?


[ClickAwayListener] Hide react-event-listener

Closes #15126
The new react hooks API makes the usage of react-event-listener less interesting. I think that it would be great to remove this dependency. It might yield a small bundle size gain<EMAIL_ADDRESS>

The new react hooks API makes the usage of react-event-listener less interesting. I think that it would be great to remove this dependency.

During the refactor to hooks I'm removing EventListener where I can in favour of hooks


Allow customize NimBLE configs with MYNEWT_ prefix (IDFGH-14043)

Is your feature request related to a problem?
I'm using NimBLE to create a BLE server with DIS service. It turns out that I have to enable following configs to have all characteristics in DIS.

MYNEWT_VAL_BLE_SVC_DIS_FIRMWARE_REVISION_READ_PERM
MYNEWT_VAL_BLE_SVC_DIS_HARDWARE_REVISION_READ_PERM
MYNEWT_VAL_BLE_SVC_DIS_SOFTWARE_REVISION_READ_PERM
MYNEWT_VAL_BLE_SVC_DIS_MANUFACTURER_NAME_READ_PERM

Describe the solution you'd like.
These configs are defined in "esp-idf\components\bt\host\nimble\port\include\esp_nimble_cfg.h", which (in my opinion) should not be modified directly.
I want some method to customize the configurations without modify esp-idf itself.
Describe alternatives you've considered.
No response
Additional context.
I found there were some issues for expose other NimBLE configs. I think it will be good to have a general way to expose all available configs.

Thanks, I tested the patch and it works.

Changes pushed on master branch. Closing issue.


[Feat]: Auto Commenting when an Issue is Closed

This feature aims to solve the problem of poor communication and lack of acknowledgment when issues are closed. By automatically commenting on closed issues, it ensures that contributors are informed about the closure and are thanked for their efforts. This helps maintain a positive and engaging community atmosphere, encouraging continued contributions and fostering good relationships between maintainers and contributors.

@abhisheks008 please assign me this issue

This can be done. Issue assigned to you @Asymtode712


fix: Fix last item of collapsible flashbar not being dismissible

Description
The class flash-with-motion makes a flashbar flash enter or leave with animations, based on .enter and .leave suffixes that React Transition adds when the element enters or leaves: see https://github.com/cloudscape-design/components/blob/main/src/flashbar/motion.scss.
In #1656, I merged the logic to apply this class in the collapsible and non-collapsible versions of the flashbar but it turns out, there is a subtle difference:  in the non-collapsible flashbar these animations only play in Visual Refresh, but in the collapsible flashbar they are supposed to play not only in Visual Refresh but also in Classic, and it should stay like that.
Disabling React-Transition-based enter and leave animations for Classic had the following unintended consequences in Classic:

The enter animation did not look as intended
Even worse problem: dismissed items occasionally staying in the DOM. This is because our internal Transitions component relies on transitionend events, which are note emitted if the .flashbar-with-motion class, which defines the transition delays, is not present.

How has this been tested?
In the flashbar/interactive page, followed these steps:

Remove all initial flashes
Enable "stack items"
Add one flash
Dismiss it and verify that it disappears

Ticket: AWSUI-23010

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates.
Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
Changes do not include unsupported browser features, see CONTRIBUTING.md.
Changes were manually tested for accessibility, see accessibility guidelines.

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

Changes are covered with new/existing unit tests?
Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This change should include an automated test. Even if you want to merge this quickly to fix the issue, you need to follow up with the test later

This change should include an automated test. Even if you want to merge this quickly to fix the issue, you need to follow up with the test later

Acknowledged. I'll leave the ticket open until I have the tests.


Release lightgbm-sys 0.3.0

Support Windows #14
fix CI
format build.rs

[x] lightgbm-sys publish https://crates.io/crates/lightgbm-sys
[x] lightgbm publish https://crates.io/crates/lightgbm

[x] lightgbm-sys publish https://crates.io/crates/lightgbm-sys
[x] lightgbm publish https://crates.io/crates/lightgbm


DOC: Add details of the trigger argument

I noticed the details of the content of the trigger argument aren't in the doc (or at least, I couldn't find them).
Copy-pasting your message from discord.
Feel free to commit on top of this branch to correct any outdated info

Merging this into the Dev 2.2.1 branch.


Firebase timeline

Hi there,
Thank you for creating this package, I've been looking around for something like this over the past few months.
I'm wondering if you are actively working on the firebase integration and if so what your timeline is like?

No progress for firebase integration, to be honest.
But I can start soon. That will be able to be released maybe 1 or 2 weeks later.


Food Oredering website(Fully responsive)

Description 📜
Add a project  contain website of online food delievery with sections home , our services, our clients, contact us  and there is a form where you can submit you details for ordering the food.
Fixes #542

[x] Add a new project

Domain of Contribution 📊

[x] Project using only HTML & CSS
[x] Project using HTML, CSS & JS

Checklist ✅

[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Optional) 📸

2.

3.

4.

please tell me now  can i create a separate directory or  i have to make  PR again?

Create a separated directory only


Maxcoin latest windows wallet is not v<IP_ADDRESS> but v<IP_ADDRESS>

Maxcoin latest windows wallet is not v<IP_ADDRESS> but v<IP_ADDRESS>
When I download v<IP_ADDRESS> and install, it is  v<IP_ADDRESS>. in the about Maxcoin GUI.

Ok thx

Kinda Hijacking this treat.
But like to let you know that it takes almost 2 weeks to reindex a node. Since work is being done.
Hope this can be taken into consideration for feature updates..


Sense component broken after 0.87

Home Assistant release with the issue:
0.87
Last working Home Assistant release (if known):
0.86.4
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio
Component/platform:
https://www.home-assistant.io/components/sense/
Description of problem:
Sense component fails to update values.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

sense:
  email: !secret email
  password: !secret sense_password

Traceback (if applicable):
2019-02-07 19:57:55 ERROR (MainThread) [homeassistant.helpers.entity] Update for binary_sensor.heat_1_2 fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 221, in async_update_ha_state
    await self.async_device_update()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 349, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/binary_sensor/sense.py", line 115, in update
    self._data.get_realtime()
  File "/usr/local/lib/python3.6/site-packages/sense_energy/sense_api.py", line 84, in get_realtime
    self._realtime = websocket.get_realtime(url, self.wss_timeout)
  File "/usr/local/lib/python3.6/site-packages/sense_energy/ws_async.py", line 24, in get_realtime
    asyncio.get_event_loop().run_until_complete(
  File "/usr/local/lib/python3.6/asyncio/events.py", line 694, in get_event_loop
    return get_event_loop_policy().get_event_loop()
  File "/usr/local/lib/python3.6/asyncio/events.py", line 602, in get_event_loop
    % threading.current_thread().name)
RuntimeError: There is no current event loop in thread 'SyncWorker_6'.

Additional information:

cc @kbickar
The async implementation of upstream lib is not correct.
https://github.com/scottbonline/sense/blob/ad3035e0a222a4df186fb1a9072f7421635f5554/sense_energy/ws_async.py#L24
If sense lib want to only exposure sync version API, then it should fully manage the event loop by itself. Since the sync API call will be execute in separate thread (e.g. SyncWorker_6), it is lib's responsibility to either set an event loop or create one before it can be used.
The recommend implementation is expose async version API to HA, and pass in hass.loop.
@wickedsun you can revert the change of #20271 in your local as a workaround.

This update was sort of a stepping stone to that. I will submit a new PR that's fully async using the HA event loop

@awarecan how do you revert the change of #20271? I can't find sense.py on my system. Is there somewhere special I should be looking?

I only found one file and it was named similar but not exact. I changed it there and it worked. I didn’t find a requirements.txt so you can ignore that one I guess.

This component is still broken with the latest version of HA.  Please submit a fix.

I'm having trouble and imagine this is on my side.
The code turns over now, but I keep getting a 401 from sense. I've tried running sense_energy 0.7 in a test script with the same username/password (copied from my hass config) and it works, so I'm really confused about what could be causing this.
ense_energy.sense_exceptions.SenseAuthenticationException: Please check username and password. API Return Code: 401
Anyone else seen this?

@achatham Try quoting your email/password in the config file.

I'm still getting errors running 0.90.2  is this the same issue? Or something new I should open a separate issue for?
Update for binary_sensor.coffee_maker fails
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity.py”, line 220, in async_update_ha_state
await self.async_device_update()
File “/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity.py”, line 377, in async_device_update
await self.async_update()
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/sense/binary_sensor.py”, line 108, in async_update
await self._data.update_realtime()
File “/usr/local/lib/python3.7/site-packages/sense_energy/asyncsenseable.py”, line 41, in update_realtime
await self.async_realtime_stream(single=True)
File “/usr/local/lib/python3.7/site-packages/sense_energy/asyncsenseable.py”, line 51, in async_realtime_stream
ws.recv(), timeout=self.wss_timeout)
File “/usr/local/lib/python3.7/asyncio/tasks.py”, line 416, in wait_for
return fut.result()
File “/usr/local/lib/python3.7/site-packages/websockets/protocol.py”, line 350, in recv
yield from self.ensure_open()
File “/usr/local/lib/python3.7/site-packages/websockets/protocol.py”, line 501, in ensure_open
self.close_code, self.close_reason) from self.transfer_data_exc
websockets.exceptions.ConnectionClosed: WebSocket connection is closed: code = 1000 (OK), no reason

@AndyRPH Looks like an entirely different issue-  Create a new issue if it's still happening and include as much detail as possible in your description

@AndyRPH  did you ever end up opening another issue for this ?

No, not yet.  Hardly had the time to sit down and pull the error logs and such to create a worthwhile issue request.  Still seeing it in 92.0.


[SPARK-17165][SQL] FileStreamSource should not track the list of seen files indefinitely

What changes were proposed in this pull request?
Before this change, FileStreamSource uses an in-memory hash set to track the list of files processed by the engine. The list can grow indefinitely, leading to OOM or overflow of the hash set.
This patch introduces a new user-defined option called "maxFileAge", default to 24 hours. If a file is older than this age, FileStreamSource will purge it from the in-memory map that was used to track the list of files that have been processed.
How was this patch tested?
Added unit tests for the underlying utility, and also added an end-to-end test to validate the purge in FileStreamSourceSuite. Also verified the new test cases would fail when the timeout was set to a very large number.

Test build #64133 has started for PR 14728 at commit ce1dd9c.

cc @rxin @cloud-fan

cc @tdas

Test build #64133 has finished for PR 14728 at commit ce1dd9c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  case class FileEntry(path: String, timestamp: Timestamp) extends Serializable
 class SeenFilesMap(maxAgeMs: Long)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64133/
Test PASSed.

Merged build finished. Test PASSed.

Test build #64260 has started for PR 14728 at commit a371f05.

Test build #64260 has finished for PR 14728 at commit a371f05.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64260/
Test PASSed.

I've updated the default and set it to 1 week.

Test build #64336 has started for PR 14728 at commit 6817dec.

@jerryshao want to review this?

Sure, let me take a look at this.

Test build #64336 has finished for PR 14728 at commit 6817dec.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64336/
Test PASSed.

For the definition of maxAge, currently from the code it is max age to latest file, people may misunderstand it is max age to current time, so it would be better to document the meaning.
Another concern is that this patch changes the MetadataLog format, which will break upgrade compatibility, also user with old metadata log existed will encounter exception when using new code.

Re: format compatibility
My understanding is that structured streaming is not yet production ready and the compatibility guarantee across versions doesn't really apply. Otherwise, we shouldn't use Java serialization here at all and should opt for explicit JSON or protobuf.

Test build #64362 has started for PR 14728 at commit 04a112d.

Test build #64362 has finished for PR 14728 at commit 04a112d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64362/
Test PASSed.

Looks pretty good. Just one comment about Serializable.

Test build #64454 has started for PR 14728 at commit 9a5ed19.

Test build #64454 has finished for PR 14728 at commit 9a5ed19.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class FileStreamOptions(parameters: Map[String, String]) extends Logging

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64454/
Test PASSed.

LGTM. Thanks! Merging into master and 2.0.


Use index.json for automatic firmware downloads for board types/roles with llama-bsl

Just a reference to the idea discussion in https://github.com/Koenkk/Z-Stack-firmware/issues/310 since the stale-bot keeps wanting to close that issue.

Please see https://github.com/Koenkk/Z-Stack-firmware/issues/310#issuecomment-973915255


fix(sitemap) remove unwanted pages from sitemap

Remove unwanted entries from sitemap and introduce a way to filter more entries in future.
Fixes #3107

Thanks!


I can't upload Images

I can't upload Images

what do you mean by upload images? you just need to put them in a folder and specify a path.

linux:
"C:\path\to\images\folder"

windows:
"C:\path\to\images\folder"

what do you mean by upload images? you just need to put them in a folder and specify a path.
Windows: "C:\\path\\to\\images\\folder"
Linux: "C:\path\to\images\folder"

I'm using replicate and I cant upload the zip file

what do you mean by upload images? you just need to put them in a folder and specify a path.
Windows: "C:\\path\\to\\images\\folder"
Linux: "C:\path\to\images\folder"

I'm using replicate and I cant upload the zip file

you can ask @fofr


Add READE-TH.md

from #454, I add readme in Thai.

Coverage remained the same at 95.01% when pulling 7696c2eb2c0c5e864ff67dc7192d33f602d15da5 on thai-readme into d0324d95a089b9239453cc071e899a847c4d1043 on dev.

I have only comment. Other than that, this PR is LGTM. You can go ahead and merge.


Implement "urbit" object in Near Social VM

Fork the Near Social VM and add a custom object (in line with their Social, State, Near, and Clipboard objects) called Urbit and wire it up to the http-api library.
EDIT - Update Issue:
This should implement a simple poke() method modeled off of the arbitrary_poke() method in the roadmap.
Demo: an Urbit app, written using the forked NEAR Social VM library, that simply displays a blank page and prints a message in dojo (or adds a pal, or something else trivial) directly (not via %near-handler).

Closed by #7.


WIP: ownerReference fix

DO NOT MERGE IT
Signed-off-by: aobrzut<EMAIL_ADDRESS>
Description of your changes

Fixes #
I have:

[ ] Read and followed Crossplane's contribution process.
[ ] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

/retest


[Translation] Bengali

Needs review

Here's a google reverse translation
`xml version = "1.0" encoding = "utf-8"?>

 PDF Reader
<! -  Preferences  ->
 Previous page
 Next page
 Open Document
 First page
 Last page
 Shorten
 Enlarge
 Rotate clockwise
 Rotate counterclockwise
 Go to page
 Properties
<string name = "document_properties_invalid_date"> Wrong date </string>
<string name = "document_properties_retrieval_failed"> Failed to get document information </string>

<string name = "invalid_mime_type"> Document with invalid MIME cannot be opened </string>
<string name = "legacy_file_uri"> Could not open old document branch from unsafe app </string>
<string name = "io_error"> Error opening / string </string>

`

We're not ready to maintain translations yet. It requires a long-term commitment to keeping them updated and we haven't worked out a system for this yet.


Can't add additional accounts using Github

Dev Home version
0.1001.389.0
Windows build number
10.0.22621.3155
Other software
OS Build Version: 10.0.22621.3155.amd64fre.ni_release.220506-1250
.NET Version: .NET 8.0.1
Steps to reproduce the bug
Go into settings
Click Accounts
Press Add Account
Press Sign in to Github.com
Expected result
Take you to the github sign in page allowing you to sign in and add an additional Github account.
Actual result
Displays a pop-up with the title "Connect your account"
Then underneath that the text says:
"Something went wrong :(
Please consider filing some feedback"

Included System Information
CPU: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Physical Memory: 15.85GB (8.15GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_0.1001.389.0_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_0.1000.393.0_x64__8wekyb3d8bbwe
9932MartCliment.WingetUIWidgets_<IP_ADDRESS>_x64__g91dtg5srk15g
Widget Service:
MicrosoftWindows.Client.WebExperience_424.1301.40.0_x64__cw5n1h2txyewy

Here is additional evidence of what actually happens:
Uploading Dev Home (Preview) 2024-02-18 00-26-42.mp4…
#2282

This will be fixed in the upcoming release v0.11


set id attribute for heading to render TOC(table of content)

hi everyone!
I have a issure. Create a TOC(table of content) for html document of react-quill.
i have find a librari is: tocbot(https://www.npmjs.com/package/tocbot)
But it need id attribute to render TOC. Now in react-quill not have id attribute when i change text in editor of quill. How to i can set id for heading?

You'll probably want to make a custom Blot format for Parchment - here are some links:

https://quilljs.com/docs/modules/
https://github.com/zenoamaro/react-quill#custom-formats
https://github.com/quilljs/quill
https://www.npmjs.com/search?q=quill mentions&page=1&ranking=optimal

@diepvv  how did you tackle your problem. Can you tell me


fix static datetime

Enhance SEO by dynamically adjusting datetime based on user parameters.
I would like to set the datetime attribute to a value determined by user input.

Thank you very much for accepting my pull request!
We've been using tailbliss for a while, and we really like the aesthetics and the speed. Thank you for all your hard work!


feat: Support for Self-Hosted Gitlab.

Solves #78

A new function was added to the file clients/gitlabClient.go; the generateGitlabClient function will generate a common client or client with a custom URL extracted from the configurations provided by the user.
The gitlabClientURL config key was added to list of ConfigAvailableKeys on the file cmd/config/main.go file.

@dimabru Hey! Hope you're doing great!
I started to implement the feature and I'm taking the path you mentioned (adding a key to the ConfigurationManager). However, I have some questions. How can I define a Key using the Set method on the ConfigurationManager? (I haven't found any example on the docs).
I know you might be busy, so feel free to answer when you have some free time c:

Hey @jmj0502,
Sorry for the late response :)
You can simply use configurationManager.Set("key", "value")
What I suggest to do here is this:
Users should be able to add a configuration key that will point the gitlab client to a custom url address
Add a new key here: https://github.com/allero-io/allero/blob/7e9c8cd5276206520da1db626c87a520bf6af8f2/cmd/config/main.go#L11
I suggest gitlabClientUrl
Once you're done with that, users should be able to run allero config set gitlabClientUrl <some-url>
Then, you will need to add a custom url to the gitlabClient.go file - I'm not sure how, need to check their documentation.
You can access any keys given using configurationManager.get("somekey") to get the required value
Please let me know if there's anything else I can help with, and thanks a lot for the contribution!

@dimabru Hey! Thanks for the guidance. I think I'm done! We just need to test using a real custom gitlab URL (I don't have any), based on the dummy test I performed, I would say the feature is almost done.

@jmj0502 ok great!
let's start with undrafting this pr so we can properly review it :)
Make sure to change the pr title to match commit convention

@dimabru Donee! The title and the description were updated, in order to meet the provided commit convention.
I'll be waiting for you comments!

hey @jmj0502,
quick update on your PR: we are looking for someone with local gitlab who can test it for us before we merge. once we make sure it works, we will proceed.
Sorry for the inconvenience and once again, thanks for contributing :)

@dimabru Hey! Hope you're doing great!
No worries! I'll be ready in case any change is needed 👍

I'l test it tomorrow!

Here's what I did:
# clean state
> rm /home/segu/.allero/repo_files/*

export GITLAB_TOKEN=glpat-; export TOKEN=glpat-

./allero config set gitlabClientURL https://git.example.com

./allero fetch gitlab 7001/cust/
Start fetching gitlab group 7001

> ./allero validate gitlab

[...]

Summary
+-----------------------+----+
| Owners                |  2 |
+-----------------------+----+
| Repositories          |  2 |
+-----------------------+----+
| Pipelines             |  0 |
+-----------------------+----+
| Total rules evaluated | 11 |
+-----------------------+----+
| Failed rules          |  0 |
+-----------------------+----+

/home/segu/.allero/repo_files/gitlab.json is filled with the repositories of the group 7001, but not the subgroup cust.
So only top-level projects from 7001 are fetched, not from 7001/cust/.
When I run ./allero fetch gitlab 7001/cust/ no projects are fetched at all (the json-file is empty).
So I guess the new implementation does work. However there are some other features that need to be implemented in order for it to be useful.
Also archived repositories are also fetched which is unexpected for me.

@rndmh3ro Hey! Hope you're doing well! Sorry for the late reply (I've been busy at work) and thanks for this huge help. Cool! The bugs are probably related with missing configurations at the gitlab client level, I'll work on the improvements and let you know when I'm done so you can test again.


Install golangci-lint to make it easier to manage linter tools

install golangci-lint

We must currently install several linter tools to lint our codes on the local environment or GitHub Actions.
It's a lot of work.
So I use golangci-lint.

We do not have to install linter tools.
You can easily set each linter with one configuration file.

update Makefile

remove no required linter tools because we install golangci-lint.
install golangci-lint

Note: such go get installation aren't guaranteed to work. We recommend using binary installation.

start GitHub Actions on pull request from fork repository

The following settings will not start GitHub Actions on pull request from the fork repository.
on: [push]

Change as follows.
name: lint
on:
  push:
    branches:
      - master
  pull_request:
    types:
      - opened
      - synchronize
      - reopened

push on master branch only
pull_request with specified types

triggered on pull request from the fork repository

Codecov Report

Merging #41 (2c7a9d5) into master (6bc18fd) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master      #41   +/-   ##
=======================================
  Coverage   82.48%   82.48%
=======================================
  Files          20       20
  Lines        1216     1216
=======================================
  Hits         1003     1003
  Misses        111      111
  Partials      102      102

Flag
Coverage Δ

unittests
82.48% <0.00%> (ø)

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

Impacted Files
Coverage Δ

backlog.go
61.41% <0.00%> (ø)

issue.go
94.50% <ø> (ø)

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 705cf5d...2c7a9d5. Read the comment docs.

Codecov Report

Merging #41 (2c7a9d5) into master (6bc18fd) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master      #41   +/-   ##
=======================================
  Coverage   82.48%   82.48%
=======================================
  Files          20       20
  Lines        1216     1216
=======================================
  Hits         1003     1003
  Misses        111      111
  Partials      102      102

Flag
Coverage Δ

unittests
82.48% <0.00%> (ø)

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

Impacted Files
Coverage Δ

backlog.go
61.41% <0.00%> (ø)

issue.go
94.50% <ø> (ø)

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 705cf5d...2c7a9d5. Read the comment docs.


[Resolver] Restrict activated platforms to those in the Gemfile

This ensures that deps that come from the lockfile, which might only have the "ruby" platform, dont cause us to attempt to activate/resolve all "ruby" platform gems
Closes #5349

@bundlerbot r+

@homu r=indirect

@bundlerbot r=indirect

It would be nice to get this merged, 1.14.2 is unusable for certain JRuby scenarios. Can we get it into master?

@bundlerbot retry

@bundlerbot r=indirect

@bundlerbot retry


Test StyleCI double space enforcing

See https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/4506

Can you maybe test this on your own repo? Thanks.

Okay.


Where is my metrics?

Hello.
I have an issue about graphite-web. I installed graphite-web in default location and started carbon-daemon. Carbon writing metrics in /opt/graphite/storage/ceres/. And there is a ceres metic files in folders.
But i can't select metrics in web interface. I see folders, but there is no metrics in it. Screenshot - https://dl.dropboxusercontent.com/u/65480202/screen_graphite.png
I checked dependencies and it's ok.
Can you help me please?

Did you resolve this?  It looks like your metric has a "." following it so that instead of it being stored as a metric, it is stored as a subfolder.

Yes, i resolved it by edit STORAGE_FINDERS in settings.py:
STORAGE_FINDERS = (
'graphite.finders.ceres.CeresFinder',
)


PresignPause: add zip-PSPs + upload-PSPs + fix the getAllowedStorageAccess().

Description
1. upload-PSPs & zip-PSPs.
This PR includes to new features for the PSPs tooling.

upload-PSPs: A simple tooling that will upload the ready-X file directly into the 1password (I know we have a similar tooling already built in go but I got issue when using it). This is not using a wrapper but the op cli directly from just.
Small video to see how to run it:

https://github.com/user-attachments/assets/7caebaed-6b46-4afe-acc7-816e7910c3b6

zip-PSPs: Is a simple tool that will zip the PSPs with a password. This is useful for sharing the PSPs with Base. We have already this notion doc for the process of sharing the PSPs but this make easier and faster.

https://github.com/user-attachments/assets/f1fd8ecc-2781-4d69-9baf-e5cdde156698
Both of the tools (upload-PSPs and  zip-PSPs) are not necessary for the current process but helped me for the doing the https://github.com/ethereum-optimism/security-pod/issues/137.
3. getAllowedStorageAccess()
To make sure, we are not overwriting an undesired storage there is some checks made using we have to introduce the contract address that are allowed to be modified.
However, for the PSPs we EXACTLY knows EACH time what contracts storage has to be changed.
So to avoid to create a file in the current task each time (we can simply add the FoS + SuperChainConfig directly into the file).
getAllowedStorageAccess(). This checks has been implemented recently and this is why was not required in the past.
The idea is to make the changes directly into the codebase PresignPauseFromJson to avoid having multiples files or during the generation of the PSPS.
So added the storage like this directly:
 {
+     allowed = new address[](2);
+        allowed[0] = vm.envAddress("SUPERCHAIN_CONFIG_ADDR"); // The storage for the pause will be set to `1`.
+      allowed[1] = _ownerSafe(); // The nonce is updated in the FoS.
    }

4. removing the PresignedPauseFromJson_eth_008.s.sol
Removing the superchains-ops/script/PresignedPauseFromJson_eth_008.s.sol to clean up the repository as this is mentioned there:
/// @notice This script is intended for one time use, and can be deleted after the tasks/eth/008-presign-pause runbook
///         is completed.

4. Update Sepolia task 017.
Update the status of the PSPs from  READY TO SIGN to SIGNED into the README.md since has been done and shared with BASE.
Removed the file tasks/sep/017-presigned-pause/PresignPauseFromJson.s.sol as the getAllowedStorageAccess() has now been applied directly in the step -> 3. getAllowedStorageAccess()
Tests
I use the sign command into the folder of the task-017 to make sure changes are working as expected.
SIMULATE_WITHOUT_LEDGER=1 \
FOUNDRY_SENDER=0xF0871b2F75ecD07e2D709b7a2cc0AF6848c1cE76 \
TEST_SENDER=0xF0871b2F75ecD07e2D709b7a2cc0AF6848c1cE76 \
just \
   --dotenv-path .env \
   --justfile ../../../presigned-pause.just \
   sign

Additional context
The ceremony for this task has been already done.
Some changes in this PR are not necessary (like the changing the script_name into thedraft-X.json) but is it preferable for the next time if security oncall copy paste the task017 for generating the new PSPs on sepolia.

Thanks @mds1 Happy that the small videos are helpful! and thanks for all the nits :)
I fixed everything :)


Is babel-loader now required?

npm and yarn seem to think I need to install babel-loader, which I don't remember needing before. Also, the readme doesn't mention it. But it is listed in the peerDependencies. Just an FYI.

babel-loader is definitely a requirement! Missing it in the readme was an oversight - sorry about that!

Updated the readme. Thanks for catching that.

For reference, it became a requirement when implementing [this feature]https://github.com/kaicataldo/eleventy-plugin-react/commit/51282590917081962d8b4a3ef5eb1e2d412a2f30#diff-313d0f90cb373ee6b9e0c988e71aaca3a3960bad3d108b163fdb4ad80b2e6894) (though I mistakenly added it as a dep instead of a peer dep - fixed in a later commit 😓 )

@kaicataldo Cheers!


Progress not fill correctly when decrease size

Issue Description
Unable to reduce the size of progress bar and still preserve the correct behavior.
Explain what you did
I change the size from 290 -> 125
<LiquidProgress         backgroundColor={"black"}         frontWaveColor={"blue"}         backWaveColor={"skyblue"}         fill={value}         size={125}       > ... </LiquidProgress>
Screenshots
Here's how it look with size={125}

The screen below if i changed it back to 290

Expected behavior
If i set the value to 1, the liquid progress not show correctly (if i change it back to 290, it'll work)
To Reproduce
https://snack.expo.io/@vijaydemonz/react-native-liquid-progress
Additional Information
Same issue locally using react-native ~0.63.4.

Issue resolved in  #42cef95 commit. Please have a look.


Fixes #1950

Closes https://github.com/FreeCodeCamp/FreeCodeCamp/issues/1950

Ah, yes. Silly me. Done.

Please change the title to be descriptive of the changes you have made.
Also state which issues, if any, that this PR closes in the description each on its own line. For example: closes #1337

Closes #1950. I added @benschenker's suggestion to the map exercise.

@AryanJ-NYC Please edit the title.

see for reference: https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Pull-Request-Contribute


Added clip score

I added clip score based on this script. I also added image-image clip score just in case that becomes of interest optionally

I think I'll change this to be part of the fid script since both scripts are doing generations all over again.

I decided to add an already_generated option for now in case the images were generated for fid. I can combine it with fid too if people want!


MassAssignmentException not thrown when fillable not empty

Laravel Version: 5.8.10
PHP Version: 7.3
Database Driver & Version: mysql

Description:
When a model has no fillable fields defined a Illuminate/Database/Eloquent/MassAssignmentException is thrown when trying to create one with for example firstOrCreate. If the fillable property exists and is not an empty list the warning is not thrown even if all supplied fields are not fillable, they are just silently removed and a db query done.
Steps To Reproduce:
run following code:
class SomeModel extends Model {
    protected $fillable = [""]; // putting [ ] or removing the property yields the error
}
SomeModel::firstOrCreate(['some_field'=>123], ['other_field'=>456]); // error expected here, but none happening.

To me, this is the correct behavior. The fact that the provided attributes don't include any fillable fields doesn't mean there's an error and Laravel should throw an exception.

It seems to be inconsistent than. If the $fillable property is not set, or is empty the error is thrown and is thrown only if the provided attributes contain non-fillable fields.

A MassAssignmentException is only thrown if the model is "totally guarded", i.e. you can't possibly provide fillable attributes.
When $fillable isn't empty, that's not the case and you could provide fillable attributes.

Seeing this I agree that this is more a case of missing documentation than an actual bug.


[filebeat] fix filebeat exporter container port

What this PR does / why we need it:
Bring by #11408 , the prometheus exporter for filebeat does not expose the exporter port.
This PR add containerPort field to prometheus exporter container.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md

/ok-to-test

/lgtm


add solid beets vault

want: 0xf2b2103e1351c4d47b27efc8100bb264364fa92c
chefPoolId: 59
vault: 0xf34bED1111dA686B2AB336b7ec594A22Df6b87d7
strat: 0x453256366F7A3F58b9e07887Be329484034168d2

What is MyBal contract (file 17 of 17)? That's not the part of our codebase

the vault is fine, but the strat deployment seems to be broken, lots of unused contracts included there

oh shit... that's embarrassing. I was just doodling for my own learning sake. i didnt mean to deploy that.

I can redploy strat, pointing to existing vault. but then can someone point vault to new strat?

just realizing the vaultOwner and stratOwner addresses I used in the solid beets strat are from the old addressbook. https://github.com/beefyfinance/address-book/blob/main/address-book/fantom/platforms/beefyfinance.ts
I'm closing this PR, will redeploy new vault and strat.


[Ruby] Arrow::Column#size doesn't work for Arrow::RecordBatch

Describe the bug, including details regarding any error messages, version, and platform.
require "arrow"
Arrow::RecordBatch.new({"a" => [1, 2, 3]}).columns[0].size

/tmp/local/lib/ruby/gems/3.4.0+1/gems/red-arrow-19.0.0.SNAPSHOT/lib/arrow/column.rb:62:in 'Arrow::Column#n_rows': undefined method 'n_rows' for an instance of Arrow::UInt8Array (NoMethodError)

      @data.n_rows
           ^^^^^^^
	from /tmp/a.rb:2:in '<main>'

Component(s)
Ruby

Issue resolved by pull request 45133
https://github.com/apache/arrow/pull/45133


MySQL (and other Network Services) don't work properly

Not sure if this has to do with Microsoft lack of raw sockets, in Windows, but it's reproducible....
Install Bash on Windows
sudo apt-get update
sudo apt-get upgrade
Install MariaDB
apt-get install mariadb-server
I would expect that I could do my development in visual studio, etc and connect (not sure via localhost, etc) to MySQL database running inside bash.
.....
.....
.....
Setting up mariadb-client-core-5.5 (5.5.52-1ubuntu<IP_ADDRESS>) ...
Setting up mariadb-client-5.5 (5.5.52-1ubuntu<IP_ADDRESS>) ...
Setting up mariadb-server-core-5.5 (5.5.52-1ubuntu<IP_ADDRESS>) ...
Setting up mariadb-server-5.5 (5.5.52-1ubuntu<IP_ADDRESS>) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
runlevel:/var/run/utmp: No such file or directory
invoke-rc.d: policy-rc.d denied execution of stop.
chown: cannot access ‘/var/run/mysqld’: No such file or directory
161027 15:49:24 [Note] /usr/sbin/mysqld (mysqld 5.5.52-MariaDB-1ubuntu<IP_ADDRESS>) starting as process 1242 ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
runlevel:/var/run/utmp: No such file or directory
invoke-rc.d: policy-rc.d denied execution of start.
Setting up libdbd-mysql-perl (4.025-1ubuntu0.1) ...
Setting up libhtml-template-perl (2.95-1) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up mariadb-server (5.5.52-1ubuntu<IP_ADDRESS>) ...
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
root@ZACKMAC:~#

https://msdn.microsoft.com/en-us/commandline/wsl/faq
Can I run ALL Linux apps in WSL?
No! WSL is a tool aimed at enabling users who need them to run Bash and core Linux command-line tools on Windows.
WSL does not aim to support GUI desktops or applications (e.g. Gnome, KDE, etc.)
Also, even though you will be able to run many popular server applications (e.g. Redis), we do not recommend WSL for server scenarios – Microsoft offers a variety of solutions for running production Ubuntu workloads in Azure, Hyper-V, and Docker.

http://www.hanselman.com/blog/DevelopersCanRunBashShellAndUsermodeUbuntuLinuxBinariesOnWindows10.aspx

https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/

Upstart is a dead end and will likely never be specifically supported.  We may one day see Systemd support, but right now your best bet might be to set up some manual init scripts, or even move your initialization stuff to a script that runs on your Windows user logging on (launch the script with a shortcut in the Windows startup folder).

It's working with me, and I can connect using HeidiSQL from windows.

I will second that any service/upstart script will not work and either writing your own start scripts in etc/init.d and running them, or finding them on google are your best bet. I have mySQL and postgresql working - so can be done.

Does it work outside of your local machine? I can do http://localhost:3000 to test a rails app on my machine but it doesn't work if I do http://MY-NETWORK-ADDRESS:3000

@leafoflegend & @misenesi, how about sharing this "workaround", so that the rest of the community and users interested in using the feature can get started ?

Running sudo /etc/init.d/mysql start worked for me after installing MariaDB with sudo apt-get install mariadb-server. Init script does spit out some errors but should be usable for development.

It's working with me, and I can connect using HeidiSQL from windows.

Could you tell me how to do this? It always show message "access denied for user root@localhost"

It's working with me, and I can connect using HeidiSQL from windows.

Could you tell me how to do this? It always show message "access denied for user root@localhost"

Well, I solved it. DO NOT use IP <IP_ADDRESS>, use the hostname. And make sure that mysql could be remote accessed.


Fixing multiple python issues

Fixes the following:

unhandled exception during generation of python files
missing import in python generated files
CPyEnum.fromPy invalid assertion
allows python3 usage
import statements syntax (relative vs. system paths)

Automated message from Dropbox CLA bot
@steweg, it looks like you've already signed the Dropbox CLA. Thanks!

A few requests before I go deep on the code review here:

Can you provide some more context on the issues you found, and what was necessary to fix them?  For instance, I'm surprised you needed to do something for python3, since the example and test-suite both already run in Python3, and the generated code is intended to work for either language (and check at run-time when necessary).
Can you re-generate the code for the example and test-suite?  This is both because I'd like to confirm that those run and pass for you, and also because the generated code is checked into the repo as an aid to code-review.  It's much easier to first review that the generated code looks reasonable, before reviewing the generator itself.

Hi,
ok I have reviewed once again and also run my own tests regarding python3 option. It turned out that you are right, there was no need to adjust the code in that way. As this change is coming from colleague of mine, I will ask him for specific details why he asked me to adjust the code in that way, but for now I reverted that part.
For the rest, I have run "make example_python" and within Testing directory I run "make python" (I was not able to run full set of tests due to restrictions of my testing environments, but I guess those commands should be enough to trigger all needed steps you are looking for).
In order to explain the problems:

unhandled exception during generation of python files
During building of our djinni files, we have run into situation that several dh__ containers files were trying to be regenerated multiple times (with the one and the same content). This throws an exception, which was not handled and as such the generation failed. The root-cause here would be somehow limit the set of generated files to be uniq, so the exception would never be thrown, but I didn't find a successful way how to do it. Therefore I adjusted the code to handle such exception and simply skip regeneration as the file was already created

missing import in python generated files
in files like test-suite/generated-src/python/conflict_user.py, the proper imports directives are missing for e.g. line 40

CPyEnum.fromPy invalid assertion
The function is asserting "assert _ret.value != -1", which is not correct as "int" (type of "_ret") doesn't have "value" method. Python will complain about it when you reach the code during usage (apparently current tests doesn't catch it)

allows python3 usage ==> reverted

import statements syntax (relative vs. system paths)
This was done in order to allow one to properly create a package, that can be further on installed into the system (e.g. we are creating C++ library with python staff as one package). This is critical part as without the "." in front, the paths will not work properly. Unfortunately the "." in front causes python tests to fail due to:
"E   ImportError: attempted relative import with no known parent package"
This error is valid as python tests are not written in a way that they would be using "package". So question to you is whether you would like to have an option for "." to support packages or have it only with the form of without "."?

Anyway enjoy your vaction

A few clarifications:

Were you seeing the duplicate generation within a single run of Djinni, or multiple runs into the same generated output directory?  Would it be possible to provide an example project which demonstrates this issue?  I agree with you that it would be better to avoid duplicate generation, and maybe I can help to find a way to do that.

I'll need more time to dig deeper to have a preference on this issue, though my general approach in situations where different use cases and users have different needs is to add configuration via command-line options, so you might consider if that would make sense here, or if the test suite should simply be modified to better follow standard practices.

Here is failing example:
MyRec = record {
        a: string;
}

IMyRecCallback = interface +p {
        MethodA(records: list<MyRec>);
        MethodB(records: list<MyRec>);
}

Some responses from your explanations and a look at your code:
1 (unhandled exception): Ah, is the problem simply that the logic to generate helpers for generic types (like list<my_type>) is triggered multiple times?  That should really be fixed in a more targeted way, by tracking which types have been generated, or by gathering all the types into a set before generation.  I think the try/catch approach is over-broad, and could hide a lot of other generation problems.
2 (missing import): I can see that in the example code now.  Seems straightforward.
3 (.value in assert): Seems straightforward too.  It would be good to see a test case which does exercise that code, as a way of validating the fix.
4 (reverted)
5 (import syntax): I don't know enough about various packaging/installer options for Python to know if there's a "right" answer here, so I'd prefer to see the code become more flexible, rather than switch to a different single answer based on your use case.  One way to make it generic might be to support an "import prefix" configurable on the Djinni command-line, which will be added before all imports of other Djinni classes.  That could be set to "" for the current behavior, or "." for your desired behavior, or "my.package.name" to allow fully-qualified imports for people who may want that.  That also feels quite in keeping with existing Djinni behaviors which allow for prefixes on #include statements.

Hi,
1A I reverted my original patch, created a test, add it into test suite and it turned out that it was actually a bug within checking inside "writtenFiles" hash map. This map included lowercase filename to actual filename, but when it was being checked, it was forgotten to lowercase first the key in order to find a match
1B After I find this issues, I solved it and adjust the test. It turned out that the testing of python was not failing properly due to missing exit code within Main (value other than 0) => so I added it. This part might need to be cherry-picked also into master as this is not related to python at all.
2-4 unchanged

I added string option for adding this kind of import prefix

I have rerun the tests and upload new patch-set

@artwyman Hello, is there anything else that I need to do regarding this PR? Thanks

Apologies for the lack of responsiveness.  I'm trying to get caught up on long-open PRs while ramping up a new maintainer.

@xianwen ready to test and merge.


Revert "[Connectors API] Cleaning unused endpoints"

Reverts dust-tt/dust#4350

PMRR @philipperolet


Error: Cannot find module 'string-natural-compare'

I see that in v1.4.0 you changed the sorting library to use string-natural-compare.  By just running npm install with an empty node_modules directory, and then building my script I'm getting the error that it can't find string-natural-compare module. If I manually install that package, the build works. I'm stumped why it's not seeming to download the package automatically. Any ideas?
Also, thanks for the great library.

Hmm, sounds really weird 😕

Is it likely that it's because listed in devDependencies while it's still included in the final build? Resulting in NPM not downloading it when it's used as a dependency?

Yep. For some reason I'm not getting that error locally, but I am in production.
I suspect it might be the version of NPM being used... ?

Oh, yeah that's correct @AKST! I'll fix that and do a new release!

Fixed!

Thanks!


DecodeMemory used in tests can panic on some inputs

Right now it seems like the memory trace doesn't always have the highest memory address (index) in its last memory trace element.
This is an assumption we make when decoding the memory:
lasMemIndex := binary.LittleEndian.Uint64(content[lastContentInd : lastContentInd+addrSize])

This seems to be working with layout=plain, but it fails to decode the layout=small memory trace.
(Or maybe we're reading whole 8 bytes that can contain some bits for the "segment". Since the segment is always 0 in the simplest cases, it could work correctly. But I don't know the exact memory encoding yet.)
Here is an example:
addr=80
addr=81
addr=82
addr=1635
addr=1634
addr=1637
addr=1636
addr=83
addr=84

I would assume that values like 1635 come from a range_check builtin segment (my test uses it).

There are 2 ways for the address to be encoded:
    def to_bytes(value: "MaybeRelocatable", n_bytes: int, byte_order: Endianness) -> bytes:
        """
        Serializes RelocatableValue as:
        1bit |   SEGMENT_BITS |   OFFSET_BITS
        1    |     segment    |   offset
        Serializes int as
        1bit | num
        0    | num
        """

But for the use cases I care about right now this is not an issue, because all values are encoded using the second schema.

In this particular case, it all happens due to the different segment relocation between the two runners.
Here is the cairo-run segments relocation table for this test:
Segment relocation table:
0     1
1     68
2     98
3     98
4     1634
5     2146

1634 is a range_check builtin.

Fixed in https://github.com/NethermindEth/cairo-vm-go/pull/397


Audit fix/qsp 7/tsbbloc 514 mint

Description

Checklist:

[x] Pull Request references Jira issue
[x] Pull Request applies to a single purpose
[x] I've added comments to my code where needed
[x] I've updated any relevant docs
[ ] I've added tests to show that my changes achieve the desired results
[ ] I've reviewed my code
[ ] I've followed established naming conventions and formatting
[ ] I've generated a coverage report and included a screenshot
[ ] All tests are passing locally

Draft PR is based on QSP-8


ZeroDivisionError: After orthogonalisation, a vector of all zeros appears and cannot be normalised.

This code can eliminate redundant features by excluding those that exhibit a high correlation with the selected ones, which is a good approach.
However, after orthogonalisation, there may be cases where a vector consisting entirely of zeros fails to achieve normalisation and results in an error.
Considering this potential scenario, would it be appropriate to enhance the code's robustness by implementing measures to address such occurrences? For instance, could the code be modified to handle such features, possibly by skipping them?
Your insights into this adjustment would be greatly valued.
A demo code showing this situation is as follows (in Python) :
Data preprocessing
from keras.datasets import mnist
from matplotlib import pyplot
import numpy as np
from sklearn.decomposition import PCA
from fastcan import FastCan

# load the training and testing sets into separate variables.
(train_X_ori, train_y_ori), (test_X_ori, test_y_ori) = mnist.load_data()

# reshape the datasets into matrices
train_X = train_X_ori.reshape(60000,-1)
train_y = train_y_ori

test_X = test_X_ori.reshape(10000,-1)
test_y = test_y_ori

# Build a demo data set
test_X_ds = test_X[0:5000:3]
test_y_ds = test_y[0:5000:3]

# Initialize PCA and fit-transform the data
pca2 = PCA()
pca_X_all = pca2.fit_transform(test_X_ds)

# Initialize PCA and fit-transform the data
eigenvalues = pca2.explained_variance_

# Calculate cumulative explained variance
explained_variance = pca2.explained_variance_ratio_
cumulative_explained_variance = np.cumsum(explained_variance)
n_components_for_99_variance = np.argmax(cumulative_explained_variance >= 0.9999 ) + 1

# Transform data using the selected number of components
pca_X = pca2.transform(test_X_ds)[:,:n_components_for_99_variance]

# remove column vectors containing all zeros
test_X_non_zreo = []

for col_idx in range (test_X_ds.shape[1]):
    if not np.all(test_X_ds[:, col_idx]==0):
        test_X_non_zreo.append(test_X_ds[:, col_idx])

result_matrix = np.column_stack(test_X_non_zreo)

Feature selection
test_X_nonrdun = FastCan(n_features_to_select=n_components_for_99_variance).fit(result_matrix, pca_X)

An error occurred as follows:
Progress: 515/525, SSC: 509.79790
File _cancorr_fast.pyx:222, in fastcan._cancorr_fast._forward_search()
File _cancorr_fast.pyx:41, in fastcan._cancorr_fast._normv()
ZeroDivisionError: Cannot normalize a vector of all zeros.
Output is truncated.

This is caused by the vector normalisation inside _cancorr_fast.pyx. As a constant vector has 0 std, that leads to ZeroDivisionError in normalisation.
Image datasets may usually content zero vectors, which will make FastCan unusable, unless remove those features manually before using FastCan.
However, linear dependent features and same feature (i.e., two features are exactly same) may also leads to this issue. So manually remove these features can be tricky.
I think skipping these features inside _cancorr_fast.pyx is a right way to go, so I will fix it :)


AUR pkgbuild .desktop and .png

@luciorubeens i thought i might try to update the pkgbuild and post a link in the aur comments to save you/others some time, but i got nowhere. :) I'm not very well versed in node, electron or npm and i'm not sure where i'm supposed to get the .desktop and the .png (referenced in currently available pkgbuild) from and/or their sha1 sums. It looks like maybe changes were made to the way ark organized it's releases so i'm not sure where to start.
thanks

Hey @ITwrx, oh yeah. Would be great if we had the .desktop file here. And I think sha1sum is optional, so will remove.


Malformed table in DevelopmentCodeFragment doc

Hi,
The Design Rules doc has an error under DevelopmentCodeFragment table.
Malformed table. Text in column margin in table line 4.

Regards!

True, are you willing to create a PR that fixes that? (Hacktoberfest, eh?)?

I submitted pull request #570 to fix this

Fixed in 2.8.0


Fix running specs with guard and spring

Updated spring to allow running the specs with guard and spring again.

Thanks, a system for that would be awesome, but probably also cause some issues when new versions are incompatible.


Manage cyrilic and arabic caracters

Manage cyrilic and arabic caracters [15427689]
Submitted by Anonymous on 27-7-2016 0:00:00
1 votes on UserVoice prior to migration
Hello,
The service works fine except when I try to use cyrilic and arabic caracters
ex: https://images.weserv.nl/?url=%2F%2Ftalkalang-avatars.s3-eu-west-1.amazonaws.com%2FzzcmNEhWHMgCSFKBF%2FКвадрат.png
Response
by Andries Louw Wolthuizen on 28-7-2016 0:00:00
Will do, may take some time to fix all the issues, thanks for reporting this issue!
Original UserVoice Submission

Fixed in current version.


Use tqdm for fit progress bar

@roads I think this gives a really clean and flexible progress bar implementation for model fitting, in both the terminal and the notebook.  Inspired by this answer.

I completely agree tqdm is perfect for this. In an effort to slim PsiZ down to its essentials, the PsiZ progress bar has been removed in favor of user's specifying their own progress bar implementation, so this package is now optional.


Added simple chat app idea

🛠 Issue (Number)

Closes #
Description

Hey Ashish, 👋🏻
I have added an idea of building simple chat application using React.js, MUI and Firebase. I have built that application with my own so I am sharing this idea for the coders who have just ended their learning the React.js and want create some application. This application is easy and simple for the coders who want to explore that how the client-server arch. works, how real time database interaction works also they will learn about google authentication using firebase. I have shared the link of my live project so that people can take the reference.
Hope you'll love this.
Also let me know if I have to do some changes in the comment 😇😇
Type of change

[✅ ] ADD Project Idea

Checklist:

[✅] I have made this from my own
[✅] My code follows the style guidelines of this project
[✅ ] I have performed a self-review of my own code
[✅ ] My changes generate no new warnings
[✅] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS

|     Images |
| :--------------: | :-------------: |
| < Before Image > |

| < After Image > |

Pls add the "hacktoberfest-accepted" label. 😇🫂
Thank you.✨


Update Application CLI according to the latest SDK build for v6

The issue 7473 will depreciate the contents of sdk/application-cli page to some extent. The content should be revised once the updated information is available.
Originally posted by @TalhaMaliktz in https://github.com/LiskHQ/lisk-docs/issues/1540#issuecomment-1236688310

Will be solved in #1700


ARTEMIS-3938 Adding logger-properties option to Artemis CLI create command

This feature is to enable creating broker instance with custom logging configurations from CLI.
The command would be like:
artemis create broker0 --logger-properties
The logger properties file is a java properties file containing broker's jboss logging properties intended to update the default logging properties.
example of the properties file:
{noformat}
logger.handlers=CONSOLE
logger.org.apache.activemq.audit.base.handlers=CONSOLE
logger.org.apache.activemq.audit.base.level=WARN
logger.level=WARN
{noformat}
Once applied those properties will be configured in the logging.properties of the created broker instance config dir.

This seems quite complicated for just specifying an alternative logging config.
It appears to support updating only a subset of the base config, e.g adding new things, or overriding an existing property value, without necessarily specifying the full configuration, also jumping hoops to make sure other areas are updated appropriately (e.g adding a new logger to the list of loggers). Its not clear it really supports removing any existing stuff (except perhaps by re-definining them an empty value for an existing key, and hoping the impl doesnt barf on such prop values).
It doesnt seem very nice/maintainable that this programatically duplicates the regular logging.properties file contents within JBossLoggingConfiguration as its starting point for creating a modified config. The two definitions could easily get out of sync, the basic props and the programmatic equivalent. In particular, the fact we are also working to remove JBL usage just now also makes it seem like a less than ideal time to introduce something new as complicated as the JBossLoggingConfiguration class which is heavily dependent on that config structure, and would need adapted (if it even could be) to a replacement.
Why not not simply have the CLI option allow providing a complete  logging configuration file the user can provide? Then if the option is specified, that file is copied into place as the instance is created, and if it isnt specified then the default one is copied into place the same as it is currently. Much simpler, likely a handful of lines rather than the several hundred used here, with no need for the mechanism to be handling the structure of the file at all.

This change is tightly coupling the broker with JBoss Logging. We plan to move away from JBoss Logging in the not-too-distant future to SLF4J + Log4j 2.x. In order to continue working this code would have to be updated to work with Log4j 2.x (assuming that's even possible). That said, the logging implementation is flexible with SLF4J so this feature would break with any other implementation other than Log4j 2.x. Tightly coupling the broker to a logging implementation is not tenable.
In my opinion, the simplest & best solution for custom configuration is to just copy the custom config file to etc after the broker has been created. Having the broker do this adds unnecessary complexity and further expands the CLI's create command which was originally designed to be very simple.