Testing apisonator.

Hi,
I have attempted to start testing apisonator project. Using the instructions.
Seeing an error when running make test
$ docker run -ti --rm -h apisonator-test -v /thebounty/work/redhat/3scale/apisonator:$(docker run --rm apisonator-test /bin/bash -c 'cd && pwd')/apisonator:z -u $(docker run --rm apisonator-test /bin/bash -c 'id -u'):$(docker run --rm apisonator-test /bin/bash -c 'id -g') --name apisonator-test apisonator-test
/home/ruby/.bash_rbenv: eval: line 14: syntax error near unexpected token `)'
/home/ruby/.bash_rbenv: eval: line 14: `  )'
ruby 2.2.4p230 (2015-12-16 revision 53155) [x86_64-linux]
/home/ruby/.bash_rbenv: eval: line 14: syntax error near unexpected token `)'
/home/ruby/.bash_rbenv: eval: line 14: `  )'
/home/ruby/.bash_rbenv: eval: line 14: syntax error near unexpected token `)'
/home/ruby/.bash_rbenv: eval: line 14: `  )'
/home/ruby/apisonator/script/lib/functions: line 5: $'\r': command not found
/home/ruby/apisonator/script/lib/functions: line 7: syntax error near unexpected token `$'{\r''
'home/ruby/apisonator/script/lib/functions: line 7: `function daemonize {
/home/ruby/apisonator/script/lib/rbenv/ruby_versions: line 2: $'\r': command not found
/home/ruby/apisonator/script/lib/rbenv/ruby_versions: line 8: syntax error near unexpected token `$'{\r''
'home/ruby/apisonator/script/lib/rbenv/ruby_versions: line 8: `regex_escape() {
script/test: line 46: start_services: command not found
script/test: line 22: bundle_exec: command not found
script/test: line 9: stop_services: command not found
Failed tests in default version
$

Which commit did you checkout?
Just tried with current master 89a402851c2302e68bb1a0fc8d192e1ab1fb8759 and working as expected.

@eguzki I was using the tagged release v2.89.0
I will try again with master. Thanks for the suggestion.

@whitingjr  I have removed all base images hierarchy down to quay.io/3scale/apisonator-ci. So make test builds all images from scratch. Still working on v2.89.0.
Which docker version are you using? run docker version so we can see client and server version.

$ docker --version
Docker version 1.13.1, build 1185cfd/1.13.1

Maybe the client (and server) is too old?
$ docker version
Client:
 Version:           18.09.3
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        774a1f4
 Built:             Thu Feb 28 06:53:11 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.3
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       774a1f4
  Built:            Thu Feb 28 05:59:55 2019
  OS/Arch:          linux/amd64
  Experimental:     false

@whitingjr I run Fedora 29 on my machine, with Docker version 1.13.1, build 1185cfd/1.13.1, and on current master (at v2.91.1) I have no issues. Can you reproduce with current master?

@eguzki  I checked out a fresh clone of apisonator. Master branch. Seeing this error when running make build
$ make build
make -f /tmp/apisonator/openshift/Makefile build-dir
make[1]: Entering directory '/tmp/apisonator/openshift'
if test ! -d /tmp/apisonator/openshift/os-build; then make -f /tmp/apisonator/openshift/Makefile new-build-dir; fi
make[2]: Entering directory '/tmp/apisonator/openshift'
rm -rf  /tmp/apisonator/openshift/os-build
ln -s /tmp/tmp.dDUfgpF8K2 /tmp/apisonator/openshift/os-build
make[2]: Leaving directory '/tmp/apisonator/openshift'
test "x" = "0x" || (	(cd /tmp/apisonator && git diff-index --quiet --cached HEAD && git diff-files --quiet && git diff-index --quiet HEAD) || (echo -e "\n*** ERROR: dirty git state - ensure all diffs are committed or set GIT_DIRTY_CHECK=0\n" >&2; false))
(cd /tmp/apisonator && git archive --worktree-attributes --format=tar --prefix=dist/ HEAD) | (rm -rf /tmp/apisonator/openshift/os-build/* && tar xf - -C /tmp/apisonator/openshift/os-build)
test "x" != "0x" ||         cd /tmp/apisonator && git diff --cached | patch -p1 -d /tmp/apisonator/openshift/os-build/dist
cd /tmp/apisonator && git diff | patch -p1 -d /tmp/apisonator/openshift/os-build/dist
touch /tmp/apisonator/openshift/os-build/ready
make[1]: Leaving directory '/tmp/apisonator/openshift'
make -f /tmp/apisonator/openshift/Makefile _build ; EXITVAL=os-build/ready ; test "x" = "0x" || make -f /tmp/apisonator/openshift/Makefile rm-build-dir ; exit
make[1]: Entering directory '/tmp/apisonator/openshift'
======================================================================
* Image: amp:apisonator-v2.91.1
* Dockerfile: /tmp/apisonator/openshift/distro/centos/7/Dockerfile
======================================================================
docker build -f /tmp/apisonator/openshift/os-build/dist/openshift/distro/centos/7/Dockerfile --pull -t amp:apisonator-v2.91.1 /tmp/apisonator/openshift/os-build/dist
Sending build context to Docker daemon 2.154 MB
Step 1/23 : FROM centos:7
Trying to pull repository docker.io/library/centos ...
sha256:8d487d68857f5bc9595793279b33d082b03713341ddec91054382641d14db861: Pulling from docker.io/library/centos
8ba884070f61: Pull complete
Digest: sha256:8d487d68857f5bc9595793279b33d082b03713341ddec91054382641d14db861
Status: Downloaded newer image for docker.io/centos:7
 ---> 9f38484d220f
Step 2/23 : ARG RUBY_SCL=rh-ruby23
 ---> Running in 314f92e6e4d4
 ---> 554cbbeb3b8d
Removing intermediate container 314f92e6e4d4
Step 3/23 : ARG BUILD_DEP_PKGS="make gcc git"
 ---> Running in 554e63f19d55
 ---> 1c328619ccef
Removing intermediate container 554e63f19d55
Step 4/23 : ARG CACHE_FRIENDLY=true
 ---> Running in d9ca42d788b1
 ---> 2a71f43cfeb3
Removing intermediate container d9ca42d788b1
Step 5/23 : RUN sed -i /etc/yum.conf -e       '/^\(clean_requirements_on_remove\|history_record\|tsflags\|logfile\)=/d' -e       's/^\(\[main\]\b.*\)$/\1\nclean_requirements_on_remove=1\nhistory_record=0\ntsflags=nodocs\nlogfile=\/dev\/null\n/'       /etc/yum.conf  && yum install -y centos-release-scl  && yum -y update  && yum -y install ${RUBY_SCL} ${RUBY_SCL}-ruby-devel  && if test "${CACHE_FRIENDLY}x" = "truex"; then       yum -y install ${BUILD_DEP_PKGS} ;     fi  && yum -y autoremove  && yum -y clean all
 ---> Running in 2721279f7f81
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

   /usr/lib64/python2.7/site-packages/rpm/_rpm.so: cannot apply additional memory protection after relocation: Permission denied

Please install a package which provides this module, or
verify that the module is installed correctly.

It's possible that the above module doesn't match the
current version of Python, which is:
2.7.5 (default, Oct 30 2018, 23:45:53)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]

If you cannot solve this problem yourself, please go to
the yum faq at:
  http://yum.baseurl.org/wiki/Faq

The command '/bin/sh -c sed -i /etc/yum.conf -e       '/^\(clean_requirements_on_remove\|history_record\|tsflags\|logfile\)=/d' -e       's/^\(\[main\]\b.*\)$/\1\nclean_requirements_on_remove=1\nhistory_record=0\ntsflags=nodocs\nlogfile=\/dev\/null\n/'       /etc/yum.conf  && yum install -y centos-release-scl  && yum -y update  && yum -y install ${RUBY_SCL} ${RUBY_SCL}-ruby-devel  && if test "${CACHE_FRIENDLY}x" = "truex"; then       yum -y install ${BUILD_DEP_PKGS} ;     fi  && yum -y autoremove  && yum -y clean all' returned a non-zero code: 1
make[1]: *** [/tmp/apisonator/openshift/Makefile:67: _build] Error 1
make[1]: Leaving directory '/tmp/apisonator/openshift'
make[1]: Entering directory '/tmp/apisonator/openshift'
rm -rf /tmp/tmp.dDUfgpF8K2 /tmp/apisonator/openshift/os-build
make[1]: Leaving directory '/tmp/apisonator/openshift'
$

@whitingjr I've been unable to reproduce that error on my Fedora 29 machine - the process keeps on with the build process way beyond step 5, and it actually finishes correctly. What is the environment you are building this on? Which operating system? Are you running SELinux in enforcing mode or any other such security framework?
The error message you get there seems to imply that either docker is running in some sort of unprivileged mode or you found an error with the mirrors when building the container image. Do you get this error consistently?

@unleashed F28
$ uname -a
Linux f28lite 4.20.14-100.fc28.x86_64 #1 SMP Tue Mar 5 19:45:42 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$

Yes I did have selinux set to Enforcing. I've set it to Permissive and it's getting a lot further in the build.
.....
------------------------------------------------------------------------------

RubyGems installed the following executables:
	/opt/rh/rh-ruby23/root/usr/bin/gem
	/opt/rh/rh-ruby23/root/usr/bin/bundle

RubyGems system software updated
RubyGems Environment:
  - RUBYGEMS VERSION: 3.0.3
  - RUBY VERSION: 2.3.8 (2018-10-18 patchlevel 459) [x86_64-linux]
  - INSTALLATION DIRECTORY: /opt/rh/rh-ruby23/root/usr/local/share/gems
  - USER INSTALLATION DIRECTORY: /root/.gem/ruby/2.3.0
  - RUBY EXECUTABLE: /opt/rh/rh-ruby23/root/usr/bin/ruby
  - GIT EXECUTABLE: /usr/bin/git
  - EXECUTABLE DIRECTORY: /opt/rh/rh-ruby23/root/usr/local/bin
  - SPEC CACHE DIRECTORY: /root/.gem/specs
  - SYSTEM CONFIGURATION DIRECTORY: /etc/opt/rh/rh-ruby23
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /opt/rh/rh-ruby23/root/usr/local/share/gems
     - /root/.gem/ruby/2.3.0
     - /opt/rh/rh-ruby23/root/usr/share/gems
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - /opt/rh/rh-ruby23/root/usr/local/bin
     - /opt/rh/rh-ruby23/root/usr/bin
     - /usr/local/sbin
     - /usr/local/bin
     - /usr/sbin
     - /usr/bin
     - /sbin
     - /bin
ERROR:  While executing gem ... (OptionParser::MissingArgument)
    missing argument: --version
The command '/bin/sh -c source scl_source enable ${RUBY_SCL}  && if test "${GEM_UPDATE}x" = "truex"; then       gem update --system -N ;     fi  && gem env  && BUNDLED_WITH=$(cat ${BUNDLE_GEMFILE}.lock |       grep -A 1 "^BUNDLED WITH$" | tail -n 1 | sed -e 's/\s//g')  && if test "${BUNDLE_VERSION_MATCH}x" = "truex"; then       gem install -N bundler --version ${BUNDLED_WITH} ;     else       yum install -y ${RUBY_SCL}-rubygem-bundler         && yum -y autoremove && yum -y clean all ;     fi  && echo Using $(bundle --version), originally bundled with ${BUNDLED_WITH}  && bundle config --local silence_root_warning 1  && bundle config --local disable_shared_gems 1  && bundle config --local without ${BUNDLE_WITHOUT}  && bundle config --local gemfile ${BUNDLE_GEMFILE}' returned a non-zero code: 1
make[1]: *** [/thebounty/work/redhat/3scale/apisonator/openshift/Makefile:67: _build] Error 1
make[1]: Leaving directory '/thebounty/work/redhat/3scale/apisonator/openshift'
make[1]: Entering directory '/thebounty/work/redhat/3scale/apisonator/openshift'
rm -rf /tmp/tmp.feCWpKTkOn /thebounty/work/redhat/3scale/apisonator/openshift/os-build
make[1]: Leaving directory '/thebounty/work/redhat/3scale/apisonator/openshift'
$

@unleashed @eguzki I've attempted using another machine. It works ok.
For now let's not waste more time. I am ok this issue be closed. Ok with you ?

@whitingjr this indeed looks like some weird state in your configuration, and we've been unable to reproduce - ok to close, thanks!

Hi,
I had to investigate this further now I am using the original machine, now updated to F29. Found the cause of the issue was the pattern used by grep at line 75.
To demonstrate what's happening on my system here it is
$ docker commit<PHONE_NUMBER>b7
[sudo] password for whitingjr:
sha256:0b688a4e8e18c547fc627720b403d520039fdf40269dc9cd0974dc1e092eee00
$ docker run -it 0b688a4e8e18c547fc627720b403d520039fdf40269dc9cd0974dc1e092eee00 /bin/bash
[root@86c2e4fd6d61 app]# BUNDLED_WITH="foo";echo "BUNDLED_WITH           : $BUNDLED_WITH"; BUNDLED_WITH=$(cat Gemfile.on_prem.lock | grep -A 1 "^BUNDLED WITH$" | tail -n 1 | sed -e 's/\s//g') ; echo "BUNDLED_WITH afterwards: $BUNDLED_WITH"
BUNDLED_WITH           : foo
BUNDLED_WITH afterwards:
[root@86c2e4fd6d61 app]# BUNDLED_WITH="foo";echo "BUNDLED_WITH           : $BUNDLED_WITH"; BUNDLED_WITH=$(cat Gemfile.on_prem.lock | grep -A 1 "BUNDLED WITH" | tail -n 1 | sed -e 's/\s//g') ; echo "BUNDLED_WITH afterwards: $BUNDLED_WITH"
BUNDLED_WITH           : foo
BUNDLED_WITH afterwards: 1.16.6
[root@86c2e4fd6d61 app]#

For some unknown reason converting the pattern to be a simple version makes it work. Can't explain why.
On my system running the build target for make the --version flag is being used with empty space. Which the OptionParser detects.
Do you want a PR to switch the pattern over ?

I guess we can change the pattern because there's only going to be one like with BUNDLE WITH anyway in the Gemfile.lock. No need to check the start and the end of the line.
I'm not sure what might be causing the issue, though. Does it work if you remove only the $ from the pattern ?

@whitingjr can you verify your gitconfig settings? The only reason I could see that this pattern would fail is if your git is configured to checkout source code with \r\n rather than \n (ie. CRLF as opposed to LF). Can you attach to this issue the contents of your Gemfile.on_prem.lock file?

@unleashed @davidor I think Alex is on the right track here.
My git config shows line ending conversion.
$ git config --get core.autocrlf
true
$

I set that because I was having trouble with CR line endings. When starting the container. Bash did not like the Windows line ending in the endpoint.sh file.

@whitingjr unfortunately the file won't show any CRLF endings, which I think is due to being posted as text to Github. Probably best to attach your full gitconfig so we can make sure that is the culprit.

$ git config -l
alias.up=pull --rebase
color.ui=auto
credential.helper=cache --timeout=7200
core.autocrlf=true
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=git@github.com:whitingjr/apisonator.git
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master
user.name=Jeremy Whiting
<EMAIL_ADDRESS>$

@whitingjr the culprit is core.autocrlf=true - you should in general have it as core.autocrlf=input to avoid mangling the original lines. Setting it to true will convert LF to CRLF no matter what, and that breaks regexps like the one used in sed.
You might want to check other options and values out in git help config if you work often with Windows/Mac projects, but otherwise input or just clearing the setting should work well.

That seemed to solve this issue. A fresh check out from git with the config option set to false  now means I can start the container after a build. Thank you all for your help.


Remove pitfall saying NextJS app router is in beta

The Next.js app router is now stable as of Next.js 13.4. Therefore I have removed the Pitfall on 'Start a New React Project' page, which says "Next.js’s App Router is currently in beta and is not yet recommended for production"

There's a few things I'd like to do:

We should make sure the links from both Pages Router an App Router go to the corresponding docs sections and that installation instructions are correct for both. Would you mind fixing that?
I think we should keep a note here, but change the wording to suggest that although App Router is stable, it is still bleeding edge tech.

Sure. Will work on that :+1:

@nahal04 Thanks for updating this. How about adding npx create-next-app@latest to the first section too? It's important that pages router users still get the latest template, especially if they plan on migrating to app router later.
Also, do we still need the bleeding edge section? I personally find it confusing that Next is in both sections even though both its routers are considered stable, and AFAIK all meta frameworks that are production ready and support RSCs still support rendering without RSCs.

Hi @nahal04, thanks for making this PR. We want to re-visit this page but for now, https://github.com/reactjs/react.dev/pull/6318 will minimally remove the outdated information. We need some discussion around how we want to frame each framework and will make that change. For now, I'll close this PR. Feel free if you have other concerns.


Enable dependabot

Enable dependabot following @seabbs implementation here: https://github.com/epinowcast/epinowcast/pull/354
As far as I can tell, this is only to keep GHA's deps up to date and can't handle R dependencies.

yes correct. Python just got support so we can dream of R also getting support. I am unaware of anything in the R ecosystem that does this for you (i.e like CompatHelper.jl in Julia) but also the R ecosystem makes a point to be more stable and so these issues are much rarer (no packages I have developed have been broken by upstream changes without plenty of warning I could have acted on)


Cache atlases

Cache already created atlases to speedup generation by reusing them.

:+1:

(0716e6867d5914c6c3765c48f469ffa0c7e2eb38)[https://github.com/amakaseev/sprite-sheet-packer/commit/0716e6867d5914c6c3765c48f469ffa0c7e2eb38]


How to server s3 bucket file to meteor file with clound-front

i had setup everything between s3 bucket and meteor file but i can't seem to find a way to server those image from the s3 bucket with cdn path

Hello @lastday4you ,
How do you generate "downloadable" URL to the file?

 // Intercept access to the file
    // And redirect request to AWS:S3
    interceptDownload(http, fileRef, version) {
      let path;

      if (fileRef && fileRef.versions && fileRef.versions[version] && fileRef.versions[version].meta && fileRef.versions[version].meta.pipePath) {
        path = fileRef.versions[version].meta.pipePath;
      }

      if (path) {
        // If file is successfully moved to AWS:S3
        // We will pipe request to AWS:S3
        // So, original link will stay always secure

        // To force ?play and ?download parameters
        // and to keep original file name, content-type,
        // content-disposition, chunked "streaming" and cache-control
        // we're using low-level .serve() method
        const opts = {
          Bucket: s3Conf.bucket,
          Key: path
        };

        if (http.request.headers.range) {
          const vRef = fileRef.versions[version];
          let range = _.clone(http.request.headers.range);
          const array = range.split(/bytes=([0-9]*)-([0-9]*)/);
          const start = parseInt(array[1]);
          let end = parseInt(array[2]);
          if (isNaN(end)) {
            // Request data from AWS:S3 by small chunks
            end = (start + this.chunkSize) - 1;
            if (end >= vRef.size) {
              end = vRef.size - 1;
            }
          }
          opts.Range = `bytes=${start}-${end}`;
          http.request.headers.range = `bytes=${start}-${end}`;
        }

        const fileColl = this;
        s3.getObject(opts, function (error) {
          if (error) {
            console.error(error);
            if (!http.response.finished) {
              http.response.end();
            }
          } else {
            if (http.request.headers.range && this.httpResponse.headers['content-range']) {
              // Set proper range header in according to what is returned from AWS:S3
              http.request.headers.range = this.httpResponse.headers['content-range'].split('/')[0].replace('bytes ', 'bytes=');
            }

            const dataStream = new stream.PassThrough();
            fileColl.serve(http, fileRef, fileRef.versions[version], version, dataStream);
            dataStream.end(this.data.Body);
          }
        });

        return true;
      }
      // While file is not yet uploaded to AWS:S3
      // It will be served file from FS
      return false;
    }
  });

I used the default s3 converter from the documentation

Hey @lastday4you ,
Sorry for the delay, missed your reply somehow. Feel free to ping me next time :)

How do you generate "downloadable" URL to the file?

I meant how to you get a link to the file in a Template, or wherever you are using it.

@dr-dimitru  thank you, I used the file link() function in my react front end

@lastday4you is the issue still persists on your end?

sorry, like i want to intergrate with cloundfront so do i need to change the url in meteor file ?

No, no need to change anything. Link won't change, doesn't matter what storage is used.
Requests will be managed inside interceptDownload hook. For more info see here.
Could you please update this ticket in according to our issue template:

Version of Meteor-Files you're experiencing this issue
Version of Meteor you're experiencing this issue
Is it Client or Server issue?
Post Client and/or Server logs with enabled debug option, you can enable "debug" mode in Constructor


Bad performance when loading a large amount of replays

Performance on https://www.silentselene.net/replays/th08 is bad. Loading the json takes about 1.7s. On my local setup, the request takes just 0.35s.
One possible improvement would be to stream the json data, or at lest load it in batches.
As a starting point: some time ago I tried modifying the API calls to first load just the first 50 files, and then load the remaining files. The code for that is on this branch. This worked but had no measurable performance impact. I can imagine it'll help on a non-local setup.
It would also help to request replays immediately (see issue #351)

Also consider reducing the amount of data sent. This could be done by compressing, or by removing unnecessary data. Maybe the data should be in csv format or similar.

I think gzip is probably the first thing to try. json tends to be very compressible. I suspect this will have a significant benefit.

With #373 and #390 landed I consider this fixed.


[BUG] pcidevices controller fails while setting up sriov network devices

Describe the bug

On certain machines where nic names may have an upper case character the setup of sriov network devices fails since camelcase is not allowed in kubernetes object names.
Users will notice the following error in the pcidevices controller logs
harvester-pcidevices-controller-cmwmb agent time="2024-09-04T10:58:52Z" level=error msg="error syncing 'amp2': handler reconcile-pcidevices: error setting up sriov devices for node amp2: error creating device amp2-enP3p3s0f0 on node amp2: SRIOVNetworkDevice.devices.harvesterhci.io \"amp2-enP3p3s0f0\" is invalid: metadata.name: Invalid value: \"amp2-enP3p3s0f0\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), requeuing"

To Reproduce
Steps to reproduce the behavior:

Go to '...'

Expected behavior

sriov network device object should be creaated
Support bundle

Environment

Harvester ISO version: v1.3.1
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Arm Ampere Ultra board with Mellanox nics

Additional context

This issue require specific ARM based machine to be connected to a working switch.

Thanks @ibrokethecloud for preparing the special bare-metal machine with NICs named with camel case
Verified fixed on v1.4.0-rc5.
Result
$\color{green}{\textsf{PASS}}$ Network interfaces have camel case name can be created as the SR-IOV network devices  $~~$

On the ARM based machine, when we have network interface named in camel case

rancher@harvester-pxe-1:~> ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 18:c0:4d:0d:9c:e6 brd ff:ff:ff:ff:ff:ff
    altname enP3p3s0f0
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 18:c0:4d:0d:9c:e7 brd ff:ff:ff:ff:ff:ff
    altname enP3p3s0f1
4: enP1p1s0f0np0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master mgmt-bo state UP group default qlen 1000
    link/ether 0c:42:a1:49:d0:e4 brd ff:ff:ff:ff:ff:ff
5: enP1p1s0f1np1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 0c:42:a1:49:d0:e5 brd ff:ff:ff:ff:ff:ff

The camel case NIC can be created as SR-IOV device without prompting failure in pcidevices-controller log

Test Information

Test Environment: Single node harvester ARM based bare-metal machine on Equinix platform
Harvester version: v1.4.0-rc5

Verify Steps
 Create the SR-IOV network devices on camel case NICs

Prepare a bare-metal machine
Which have network interface support SR-IOV (FV)
The NICs have named with camel case (e.g enp1p1s0f1np1)
Enable the pcidevices-controller in addons page
Open the Advanced -> SR-IOV Network Devices page
Check can create the SR-IOV network device well without error


being able to load/execute ULP code

https://github.com/micropython/micropython/pull/3578
Guess we need that to practically work with the ULP Co-Processor from micropython.

If you are reading this, you maybe should upvote or comment the pull request I linked above, so things get moving faster.

it is merged now into micropython and contained in builds after 2018-05-01.


Error on first run "Unhandled Exception"

Hello all
on my first client, where i'm testing snipeit and your agent we receive an error as show below. On snipeit I can see only the category "Laptop" has been created
C:\Program Files (x86)\Scope-IT\Marksman>Marksman.exe
18/02/2021 19:44:50: Started application.
HTTP 200: Connection to Snipe-IT instance succeded.
Attempting to create type: SnipeSharp.Endpoints.Models.Manufacturer
Instance name: FUJITSU
Attempting to create type: SnipeSharp.Endpoints.Models.Category
Instance name: Laptop
Unhandled Exception: Newtonsoft.Json.JsonSerializationException: Error converting value {null} to type 'System.Boolean'. Path 'rows[0].eula', line 1, position 108. ---> System.InvalidCastException: Null object cannot be converted to a value type.
at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader, Object value, CultureInfo culture, JsonContract contract, Type targetType)
--- End of inner exception stack trace ---
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader, Object value, CultureInfo culture, JsonContract contract, Type targetType)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ResolvePropertyAndCreatorValues(JsonObjectContract contract, JsonProperty containerProperty, JsonReader reader, Type objectType)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObjectUsingCreatorWithParameters(JsonReader reader, JsonObjectContract contract, JsonProperty containerProperty, ObjectConstructor1 creator, String id)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateNewObject(JsonReader reader, JsonObjectContract objectContract, JsonProperty containerMember, JsonProperty containerProperty, String id, Boolean& createdFromNonDefaultCreator)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateList(IList list, JsonReader reader, JsonArrayContract contract, JsonProperty containerProperty, String id)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateList(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, Object existingValue, String id)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)    at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)    at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)    at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)    at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value)    at SnipeSharp.Endpoints.EndpointManager1.FindOne(ISearchFilter filter)
at SnipeSharp.Endpoints.EndpointManager`1.Create(T toCreate)
at Marksman.Broker.SyncAll(SnipeItApi snipe, Asset currentAsset, Model currentModel, Manufacturer currentManufacturer, Category currentCategory, Company currentCompany, StatusLabel currentStatusLabel, Location currentLocation)
at Marksman.Marksman.Main(String[] args)
C:\Program Files (x86)\Scope-IT\Marksman>

I have same issue and really like snipe-it but is needing an automation of this

Hi, I see the same problem on a first installation of the solution. Also on a Fujitsu workstation, I don't know if it's a common point, but all our computers are on this manufacturer. Too bad, I really want to use this application.

I haven't been able to get in touch with the developer, so have started my own version of the project. You can download it here if you are interested: https://github.com/ReticentRobot/SnipeAgent

Did you fix the issue?

I haven't been able to get in touch with the developer, so have started my own version of the project. You can download it here if you are interested: https://github.com/ReticentRobot/SnipeAgent

Did you fix the issue?

Yes, it has been a long while - but the version I have has the fix in it that I mentioned above.

Cool - out of curiosity how did you wound up fixing it?


adds teachable machine image classification example

→ Submit changes to the relevant branch 🌲

development

→ Description 📝
A clear and concise description of what the pull request is about. Let us know if you are:

adding an update 🛠

Adds an updated example of the teachable machine image classification.

returns 'daytime' when webcam is not covered
returns 'nighttime' when webcam is covered

accompanies: https://github.com/ml5js/ml5-library/pull/592
→ Screenshots 🖼
(Any relevant screenshots, sketches, or helpful concept diagrams - these are helpful for our release notes and for getting people excited about your super cool feature and/or fix!)

→ Relevant documentation 🌴
Write a few notes about your pull request. Document any functionality that might be helpful for others who want to run and test your changes. If we don't know how to make use of your contribution, we won't be able t integrate it! 🙏

Merging this in now!

note we should test a teachable machine image classification model with 3 or 4 labels

Noted!


Not able to achieve like Google Map within Flutter Widgets like Ola uber android app UI.

Steps to Reproduce

...
...
...

Logs

Closing as dup of #21101


Desktop/Mouse support?

Hey there! Has anyone attempted to implement desktop or mouse support? I imagine that it would be at least slightly contentious due to altering default scroll behavior; however, I'm sure there's a good way to make it fluid and work properly.
May take a look myself later today, but thought I'd see what others think

Hey! Check out our demos, we've included the touch emulator from hammer.js, so maybe that's what you're looking for.

The touch emulator requires clicking and dragging, which is not really something you do on desktop. What I assume @afturner means (and what I’d really like too) is that simply scrolling on desktop has the same effect as, well, scrolling on mobile.
(Because no pull to refresh library so far does both, and we always have to manually implement it.)

To be honest I haven't seen anything like that, and that's not the focus for this library.
But feel free to fork it!


Cannot import Tspec when using "module": "NodeNext" in tsconfig

Describe the bug
Our application uses "module": "NodeNext" in the tsconfig file, however, when importing Tspec as mentioned in the docs, it gives the following error:
Module tspec has not exported member Tspec:

It seems that the imports show up when using "module": "commonjs" (didn't try other options)
Unfortunately, we are not able to switch to commonjs and must continue using NodeNext
To Reproduce

Clone the minimal reproduction repo: https://github.com/aayush123/tspec-test
Ensure node version in 20.x
Run npm i
Run npm run build (This runs npx tspec generate --outputPath openapi.json)
See that the openapi.json contains an empty schema. Also notice the import error in index.ts (in VSCode)
Change "module": "NodeNext" to "module": "CommonJS" in tsconfig.json
Run npm run build again.
See that openapi.json now contains expected schema. Also notice that import error is now gone in index.ts

Expected behavior
We should be able to import Tspec even when module in tsconfig is set to NodeNext
Additional context
I'd be happy to create a PR to fix this with minimal guidance.

@hyeonss0417 What do you think would be the appropriate fix for this? I'd be happy to submit a PR, just need a small nudge

Hello, @aayush123
Thank you very much for taking the time to report the bug and for your interest in our project.
I tested it on the test repo you reported, and when I modified the dist/index.d.ts file like below, the openapi.json file seems to be generated as expected when I build it.
export * from './generator';
export * from './server';
export * from './types/tspec.d.ts';

The cause of the problem is that in tsconfig, "module": "NodeNext" in tsconfig, I think it's caused by Directory modules (index file resolution) not working properly.
I'm trying to find a solution to the problem, but I don't know the exact solution yet🤔.

Hi @aayush123
Thank you so much for your interest in contributing to the project and for reporting the issue. I appreciate your willingness to work on a fix.
Upon further investigation, I realized that the bug was more complex than it initially appeared. To ensure it was resolved correctly and promptly, I went ahead and made the necessary changes myself. I’ve just submitted a PR with the fix.
However, I encourage you to take a look at the PR (#61) to see how the issue was resolved. Your feedback and any suggestions for improvements are always welcome. Additionally, there are many other areas in the project where your contributions would be invaluable, and I’d be happy to guide you through any of them.
Thank you again for your support and understanding.
Best regards

I just have merged the PR (#61), and the issue is fixed!
To resolve this issue on your end, please update tspec version to latest(=v0.1.115).
Once again, thank you for your valuable feedback. Your contributions help us improve the project significantly.


Housekeeping tasks for the gltf sample

Upgrded Gradle plugin to 4.0.0 from 3.4.1
Upgraded support library to use AndroidX | This was causing a compile issue since SceneForm has been updated to use AndroidX

I also did some housekeeping before I saw your pull request. But thank you very much.


AWS 3.9 sample inventory file

@cooktheryan @mazzystr quick q: how is your sample inv looking when you trying to deploy 3.9 aws code ?
Looking here i see only a slim down version however i suspect you have more for r53 etc

@DanyC97 The file that you link out to is an extra vars file for aws infrastructure deployment.  That is not an example inventory file.
The example inventory file is located within the reference architecture document.

oh i see, thx for the doc @mazzystr  !


ENOSPC in docker containers?

Since updating to chokidar in forever we got this report: https://github.com/foreverjs/forever/issues/739. I don't know all that much about Docker containers, but I wanted to see if you'd seen this before.

ENOSPC has been observed in a few cases to indicate other system limitations, like file descriptors. Bumping up the ulimit setting might help. But there are a lot of local variables at play.
What was the watching solution before that did not have this problem?

Just the watch module. @paulmillr made the PR (thanks again for that!): https://github.com/foreverjs/forever-monitor/pull/96/files

Looks like the prior solution was watch which is based on fs.watchFile (i.e. stat polling). This is less stable and efficient than other watch methods, so it is not used by default in chokidar, but there are situations (such as certain setups with networked drives and VMs) that require it.
Chokidar can be made to rely on fs.watchFile/polling using the usePolling: true option. Looks like forever may need to be tweaked to provide users the ability to set that option.

I'd prefer not to fallback to that option if we can help it. I'll see if the ulimit change fixes it.

Some users will need polling, sooner or later. The option needs to be made available.
I'm not suggesting it should be hardcoded or the default.

It doesn't seems to be a ulimit issue.
Running in containter environments is getting fairly common. Shouldn't chokidar default to usePolling=true when it detects the underlying filesystem doesn't support fs.watch properly (just like it does when it detects it running on OS X)?
Anyway I tested fs.watch inside docker and it seems to work just fine:
var fs = require('fs');
fs.watch('/usr/src/app', function() {
  console.log(arguments);
})

I tried running chockibar tests inside docker but I'm getting several errors, I'm not sure where to go from there.
docker run -t -i --rm node bash
git clone https://github.com/paulmillr/chokidar
cd chokidar
npm install
npm test

Result: http://pastebin.com/edWzQsHL

I'm curious how to detect that. If it's deterministic, I'd be fine with adding the detection to forever.

Shouldn't chokidar default to usePolling=true when it detects the underlying filesystem doesn't support fs.watch properly (just like it does when it detects it running on OS X)?

Sure, once we work out a solid cross-platform way to detect that: https://github.com/paulmillr/chokidar/issues/242

I tested fs.watch inside docker and it seems to work just fine

This isn't an equivalent test, it isn't watching recursively. Your run of the chokidar tests show that fs.watch is not flat-out failing, but is exhibiting lots of problems. But without access to your container, I can't really analyze/debug what's going on there with fs.watch (not that I really have the available time for that anyway).
The polling tests, on the other hand, seem to be doing fine. So the most straightforward solution in this particular case is going to be usePolling: true.

But without access to your container, I can't really analyze/debug what's going on there with fs.watch

I've used the official node image here: https://registry.hub.docker.com/_/node/
You could just try the same tests as I did. It should pull that image for you and start a bash shell in it:
docker run -t -i --rm node bash

Going to close this issue for now because I don't think there's anything chokidar could do differently to have an impact. The issue with fs.watch could potentially be isolated and reported to node/io.js, but it's really probably something going on at the system level.
The chokidar-level solution for this particular use-case at this point would be to enable polling (the older version of forever that does work was using a watcher that always relied on polling anyway).

But I do intend to play with the described setup on docker at some point when I get a chance.


feat: write hybrid storage format

Which issue does this PR close?
part of  #77
Rationale for this change

See issue above
What changes are included in this PR?

And a new table option stroage_format, read from env now
Write record as hybrid format, read will be supported in future PR.

Are there any user-facing changes?
How does this change test
Unit tests

🎉🎉


refactor and add test case

Description
add testcase and refactor isNumber function
Type of change
Please delete options that are not relevant.

[ ] Refactor or other

Checklist:

[ ] I have run pnpm format and my code don't have any linting issues

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

sorry for my confuse krubb @01110111-wave

you need to implement TODO  and merge this PR.
Anyway, you can just copy it to your work; it'll be fine.

you need to implement TODO  and merge this PR. (for workflow approval)
but I think the best way is just copy it to your work.

I have read your first commit then edit logic based your PR and retest my code with your test. However, I do not commit the new test into the PR, because I will make separated PR about it later. (Putting everything into a pull request might resulted in trouble.)
About TODO, soon I will implement mute command which create the moderation log that note if it is severe mute punishment or not, and the TODO will use this log to check whether it is severe punishment.

ok krubbb


why sealctl registry image command not works any more?

Detailed description of the question.
with v4.1.7 I can use sealctl registry image to show sealos.hub:5000 repo images, but v4.2.0 dosn't........it is really a usefull function.
Some reference materials you see.
No response

use crane instead.

How do I use this? Is there an example, please?
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2023年4月27日 15:19
收件人: @.>
抄送: Bodkin @.>; @.>
主题: Re: [labring/sealos] why sealctl registry image command not works any more? (Issue #3004)
use cranehttps://github.com/google/go-containerregistry/tree/main/cmd/krane instead.
―
Reply to this email directly, view it on GitHubhttps://github.com/labring/sealos/issues/3004#issuecomment-1524950083, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB7CR5L5KL4E5QJWGXGMTJDXDIMW7ANCNFSM6AAAAAAXNNGUBE.
You are receiving this because you authored the thread.Message ID: @.***>


Add pyup.io badge

What is the purpose of this Pull Request?
Address #101, i.e. set pyup.io to help us keep updated. Thanks for the head up @caduvieira!
What was done to achieve this purpose?

I added Rosie's repo to pyup.io
I added the badge to our README.md

How to test if it really works?
Check the badge and the link on it.
Who can help reviewing it?
@anaschwendler
TODO
Check #102 and #103 to see what we've left behind ; )

Hi @cuducos can you update the branch for us?
Then I can test it for us :)


runMobileGamingJavaDirect FAILED SocketException: Connection reset

https://builds.apache.org/job/beam_PostRelease_NightlySnapshot/349/
https://builds.apache.org/job/beam_PostRelease_NightlySnapshot/347/
04:19:41 > Task :beam-runners-direct-java:runMobileGamingJavaDirect FAILED04:19:41 Aug 23, 2018 11:19:32 AM org.apache.beam.sdk.io.gcp.bigquery.BigQueryServicesImpl$DatasetServiceImpl createTable04:19:41 INFO: Trying to create BigQuery table: apache-beam-testing:beam_postrelease_mobile_gaming.leaderboard_DirectRunner_user04:19:41 bq query SELECT table_id FROM beam_postrelease_mobile_gaming.TABLES_SUMMARY04:19:41 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java (default-cli) on project word-count-beam: An exception occured while executing the Java class. java.net.SocketException: Connection reset -> [Help 1]
Imported from Jira BEAM-5241. Original Jira may contain additional context.
Reported by: apilloud.

stale issue


TypeError: undefined is not an object evaluating 'taskExtras[id]' (ANDROID ONLY)

I'm seeing this error when trying to sync photos to S3 that were saved when offline. I'm attempting to sync in the componentDidMount of one of my screens. This ONLY happens when the app was not in memory and I open the app and does not happen when the app was already open but was backgrounded. Any ideas?

I get a similar issue.  It seems to be related to the following line https://github.com/mybigday/react-native-s3/blob/master/src/TransferUtility.js#L220   The problem is that there is 2 constants named 'listeners' in scope therefore causing it to be undefined inside the subscribe/unscubscribe methods

If you haven't setup successfully, other methods will throw the error as expected. I think that would be great if we make the error more clearly.


Add shape cast 3d.

Fixes: https://github.com/godotengine/godot-proposals/issues/710
Todo:

[ ] Generate preview 3d mesh using triangulate shape meshes.
[ ] Generate demo project https://github.com/V-Sekai/godot-shape-cast

Bugsquad edit: 3D counterpart of https://github.com/godotengine/godot/pull/54803.

Bump. Any news?

A couple of shapecast examples here, would be amazing if this could be done in much fewer lines of code to get the same result: https://github.com/godotengine/godot/issues/2217#issuecomment-1043043731

I'm not able to work on this as much. Consider this salvageable.

I wonder if shpaecast 3D could just be a high level wrapper for direct space queries? Godot has everything needed to do the casting, it just needs to be packaged up in much more user friendly syntax.

Yes. this is what this pr does.

Superseded by: https://github.com/godotengine/godot/pull/63161


Allow let and const together in one declaration

This doesn't have much use case outside of for loops, which is where it would be quite useful.
Use case
for( let i=0, const len=5; i<len; i++ ) { ... }

Expected behavior:
Same as:
let i = 0;
const len = 5;

Actual behavior:
Error - it has to be either let i=0, len=5 or const i=0, len=5, which is not what is wanted. The length does not change, where i does.

This is the syntax as specified by the JS spec; we try to keep the divisions from the js spec to a minimum, and in general avoid adding new syntax outside the type annotations space to prevent collisions with future changes of js.
In general we recommend making these proposals for TC39 instead (https://github.com/tc39/proposals/blob/master/README.md).

Gotcha. I'll definitely bring it up for a future version of ECMAScript.


[DOCS] Vertical Nav API docs

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[x] enhancement

Expected behavior

API/Summary table is present in the Vertical Nav Documentation.
Actual behavior

API/Summary table is missing in the Vertical Nav Documentation.
Please refer to the Tree View Docs for more details:
https://vmware.github.io/clarity/documentation/v0.11/tree-view

Reproduction of behavior
https://vmware.github.io/clarity/documentation/v0.11/vertical-nav/basic-structure/charmander

The links to Code and Examples in the Vertical Nav Documentation are also broken. Not sure if it is worth creating a new issue for this.

No longer an issue or resolved in the upcoming website work. Closing as resolved.


Frequent timeouts using pythonwhois

Hi - I (repeatably, as of the past few minutes) get timeouts even querying popular domain names like say icloud.com - and when I execute the same command from my command line whois client, I get the whois instantaneously. Thanks for a fix - maybe you could also call the command line whois tool here (https://github.com/rfc1036/whois) and parse its output?  Thanks.

domain = ('icloud.com')
:> details=pythonwhois.get_whois(domain)

Traceback (most recent call last):
File "", line 1, in
File "/Library/Python/2.7/site-packages/pythonwhois/init.py", line 4, in get_whois
raw_data, server_list = net.get_whois_raw(domain, with_server_list=True)
File "/Library/Python/2.7/site-packages/pythonwhois/net.py", line 69, in get_whois_raw
return get_whois_raw(domain, referal_server, new_list, server_list=server_list, with_server_list=with_server_list)
File "/Library/Python/2.7/site-packages/pythonwhois/net.py", line 69, in get_whois_raw
return get_whois_raw(domain, referal_server, new_list, server_list=server_list, with_server_list=with_server_list)
File "/Library/Python/2.7/site-packages/pythonwhois/net.py", line 44, in get_whois_raw
response = whois_request(request_domain, target_server)
File "/Library/Python/2.7/site-packages/pythonwhois/net.py", line 86, in whois_request
sock.connect((server, port))
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 228, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 60] Operation timed out

This is because the WHOIS response for icloud.com contains a referral link to an inactive server. It tries to obtain data from this inactive server, which obviously does not respond.
On my develop branch https://github.com/MasterFenrir/python-whois/tree/develop this issue is fixed. It checks whether a referral server is alive or not before querying it.

Hello, is this issue already part of the current version? I'm wondering if there's a way to also define some kind of timeout, the default one seems too high for some use cases.


Support “subdirectory/recipe” notation in recipe dependencies

I notice that, inside a Just recipe, it is possible to explicitly delegate to recipes declared in sub- or super-directory Justfiles, by invoking Just recursively, as in:
foo:
    @just subdir/bar
    @just ../quux

While this feature may have been intended more for interactive use (since in Justfiles one may just as well type @just --justfile subdir/Justfile bar (…or maybe introduce --justdir to make it less clumsy), this made me wonder whether it would make sense to support this “short-cut” notation as part of a recipe’s dependencies, so that one could write:
foo: subdir/bar ../quux

(I guess if dependencies of type file – à la Make – ever become a thing this notation may prove confusing, though, or one may prefer a different symbol over the slash)
Thanks for building Just!

I think this is mostly covered by https://github.com/casey/just/issues/383, since I think it would be done best as some kind of module system.

Thanks for the pointer. The headline sounds enticing, I’ll check it out.


hasServerForbiddenCharactersSupport

Hi @javiergonzper how are you ? and your work ??  i have a problem with library ... and with moveFileOrFolder, now you have implemented the withForbiddenCharactersSupported, i have in test ownCloud 8.1.1 (stable) i move this file "Fabio Liberatori, l amore e eterno finche dura.mp3" with withForbiddenCharactersSupported:NO but respond with error 110 : The file or folder that you are moving have forbidden characters ... why ? where is forbidden characters in filename ... I'm missing something ?
If i move with withForbiddenCharactersSupported:YES it's OK ...
thanks !!

another problem ... if i call getServerVersionWithPath and then hasServerForbiddenCharactersSupport the hasServerForbiddenCharactersSupport resolve and return hasSupport BOOL value but if i don't call getServerVersionWithPath before , the hasServerForbiddenCharactersSupport return error :
error	NSError *	domain: @"NSURLErrorDomain" - code:<PHONE_NUMBER>3709550604
[0]	@"NSErrorFailingURLKey" : @"https://cloud.xxxxx.it/status.php"
key	__NSCFConstantString * @"NSErrorFailingURLKey"	0x0000000112bd7dc0
value	NSURL *	@"https://cloud.xxxxx.it/status.php"	0x00007f853c045220
[1]	@"NSErrorFailingURLStringKey" : @"https://cloud.xxxx.it/status.php"
key	__NSCFConstantString *	@"NSErrorFailingURLStringKey"	0x0000000112bd7de0
value	__NSCFString *	@"https://cloud.xxxxx.it/status.php"	0x00007f853c0451e0
.....

Hello @marinotws, really busy right now :grimacing:, and you?

You are getting an error "OCErrorMovingDestinyNameHaveForbiddenCharacters" this is because in the line 350 of the OCCommunication.m the destinyPath contains any forbidden character. Debug there to see what is happening. In UtilsFramework on the method isForbiddenCharactersInFileName is where you are having the problem.

It should works... we call to the hasServerForbiddenCharactersSupport without make any call first... or maybe we do any other before but no with that intention.

ok, @javiergonzper :+1:
     //   if ([fileName characterAtIndex:i] == ','){
     //       thereAreForbidenCharacters = YES;
     //   }

Sure! @marinotws maybe the next year in the ownCloud contributor conference :+1:


recipe for really spicy tacos; closes #6

More context here. This is work based on discussion in #6.

LGTM


feat(curriculum): add blog post card lab

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

@ihechikara,
I have restructured the instructions a bit, to improve readability. It is totally up to you if you'd like to update.

Updated instructions

1. You should have a `div` with a class of `blog-post-card` to hold all your card elements.
2. You should have an image with a valid `alt` text and the class of `post-img`. You can use `https://cdn.freecodecamp.org/curriculum/labs/cover-photo.jpg` for the `src` attribute of your image.
3. You should have a `div` with a class of `post-content`.
Within the `.post-content` `div`:

    - You should have a `h2` with a class of `post-title`. Assign some text to act as the title of your blog post.
    - You should have a `p` with a class of `post-excerpt`. Assign some text to summarize the blog post (maximum of 20 words).
    - You should have an `a` with a class of `read-more`. Assign the text `Read More` to it.

4. You should apply the following styles to the `blog-post-card` div:

   - A white colored background.
   - Rounded corners.
   - Shadow for depth.
   - Appropriate `overflow` property to prevent content from overflowing.
   - Width of your choice.
   - Text alignment of your choice.

5. The `post-img` class should ensure that the image fills the card's width and adds a border at the bottom.
6. The `post-content` class should add padding inside the card for spacing.
7. The `post-title` and `post-excerpt` elements within `post-content` should have a text color other than the default and a margin on all sides.
8. The `read-more` element should be styled like a button and have:

   - A text color other than the default.
   - Background color.
   - Margin on all sides.
   - A `display` property of `inline-block`.
   - Rounded corners
   - Padding on all sides.

9.  The `read-more` element should have a hover effect that changes the background color.

**Note:** Be sure to link your stylesheet in your HTML and apply your CSS.

Also, I feel there is some repetition, for example background colors, borders and padding are being tested more than once.
If a property has been tested once, we can test for other properties in other classes. Does that make sense?

A PR has been merged that renamed the certification from "Front End" to "Full Stack". This PR may need an update and a few changes made: see comment

A PR has been merged that moves the block order from the meta.json file to the full-stack.json file.](https://github.com/freeCodeCamp/freeCodeCamp/pull/56795) This PR will need an update, and the order will need to be removed from the meta.json file and moved to the new file.

@ihechikara
I went ahead and merged in the last code review changes.
But can you review Tom's comment here about updating the branch to include the latest changes?
https://github.com/freeCodeCamp/freeCodeCamp/pull/56165#issuecomment-2450057531
Once that is done, then this should be good for approval and merged in


Fix TodoMVC example

Broken by https://github.com/gopherjs/vecty/pull/11
/cc @shurcooL

LGTM

Thanks.


doc: improve windows build instructions

@gilweis

@.***:~/tmp/tmp1/mycms$ ./Configure --prefix="${MYCMS_PREFIX}"
--cross-compile-prefix=x86_64-w64-mingw32- mingw64
bash: ./Configure: No such file or directory
@.***:~/tmp/tmp1/mycms$ ./configure --prefix="${MYCMS_PREFIX}"
--cross-compile-prefix=x86_64-w64-mingw32- mingw64
configure: error: unrecognized option:
--cross-compile-prefix=x86_64-w64-mingw32-' Try ./configure --help' for more information
On Fri, May 19, 2023 at 7:55 PM Alon Bar-Lev @.***>
wrote:

@gilweis https://github.com/gilweis
—
Reply to this email directly, view it on GitHub
https://github.com/alonbl/mycms/pull/4#issuecomment-1554909747, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASSJECY2AXM2S3QVEPGHN73XG6QWPANCNFSM6AAAAAAYIAI6XE
.
You are receiving this because you were mentioned.Message ID:
@.***>


HDDS-9738. Display startTime, pipeline and container counts for decommissioning datanode

What changes were proposed in this pull request?
In order to track the progress of the decommissioning of a datanode, the number of pipelines associated to the datanode and the number of containers on the datanode blocking the decommissioning (i.e., unhealthy and under-replicated containers) is necessary to be shown as a part of the decommission status command.
These counts, along with the time at which decommission was started for the datanode are stored as a part of metrics in NodeDecommissionMetrics. In this PR, the JMX endpoint for SCM is queried for the NodeDecommissionMetrics class and the response is parsed to display the counts and start-time for each node currently in DECOMMISSIONING.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9738
How was this patch tested?
Tested locally in docker set-up:
$ ozone admin datanode status decommission

Decommission Status: DECOMMISSIONING - 1 node(s)

Datanode: e56afcce-f5b5-4980-8b1b-d55a5714ad3c (/default-rack/<IP_ADDRESS>/ozone-datanode-4.ozone_default)
Decommission started at :<PHONE_NUMBER>19118/01/2024 12:54:21 UTC
No. of Pipelines: 1
No. of UnderReplicated containers: 2
No. of Unclosed Containers: 1
{UnderReplicated=[#5,#6], UnClosed=[#10]}

@sodonnel yes, it is ready for review now

@Tejaskriya there is one more findbugs error:
H I Dm: Found reliance on default encoding in org.apache.hadoop.hdds.scm.cli.datanode.TestDecommissionStatusSubCommand$1.handle(HttpExchange): String.getBytes()  At TestDecommissionStatusSubCommand.java:[line 87]

https://github.com/Tejaskriya/ozone/actions/runs/7650664460/job/20847133955


RE8 Counter Punch Move?

I know in the old build you could do the counter after you block.  Is that taken out for your final build?  I thought it was working great when I was playing before.

EDIT:  I figured it out.


NetCDFFieldList does not have a write method

What happened?
It is not possible to save netCDFFieldList objects using the .save method, e.g.: ek_data_object.save('output.nc'). This is often necessary when working with remote files, e.g. from sources "url" or "cds".
Note this is not a problem with the NetCDFReader object.
What are the steps to reproduce the bug?
import earthkit as ek
from earthkit.data.testing import earthkit_remote_test_data_file
ek_data = ek.data.from_source(
    "url",
    earthkit_remote_test_data_file("examples/efas.nc")
)
ek_data.save('temp.nc')

Version
latest
Platform (OS and architecture)
MacOS + Linux
Relevant log output
---------------------------------------------------------------------------
NotImplementedError                       Traceback (most recent call last)
Cell In[7], line 5
      1 ek_data = ek.data.from_source(
      2     "url",
      3     earthkit_remote_test_data_file("examples/efas.nc")
      4 )
----> 5 ek_data.save('temp.nc')

File ~/Work/Git_Repositories/EARTHKIT/earthkit-data/earthkit/data/core/fieldlist.py:1169, in FieldList.save(self, filename, append)
   1167 flag = "wb" if not append else "ab"
   1168 with open(filename, flag) as f:
-> 1169     self.write(f)

File ~/Work/Git_Repositories/EARTHKIT/earthkit-data/earthkit/data/core/fieldlist.py:1180, in FieldList.write(self, f)
   1172 r"""Write all the fields to a file object.
   1173
   1174 Parameters
   (...)
   1177     The target file object.
   1178 """
   1179 for s in self:
-> 1180     s.write(f)

File ~/Work/Git_Repositories/EARTHKIT/earthkit-data/earthkit/data/core/__init__.py:74, in Base.write(self, f)
     71 @abstractmethod
     72 def write(self, f):
     73     """Writes data to the ``f`` file object."""
---> 74     self._not_implemented()

File ~/Work/Git_Repositories/EARTHKIT/earthkit-data/earthkit/data/core/__init__.py:122, in Base._not_implemented(self)
    120 if hasattr(self, "path"):
    121     extra = f" on {self.path}"
--> 122 raise NotImplementedError(f"{module}.{name}.{func}(){extra}")

NotImplementedError: earthkit.data.readers.netcdf.NetCDFField.write()

Accompanying data
No response
Organisation
No response

I do not consider this as a bug, but something that is not yet implemented. It is not trivial to write a NetCDFieldList to disk since it can contain an arbitrary subset of the "fields".

Okay, I wasn't sure whether to tag as bug or enhancement, I am happy either way. My solution is to point to the existing to_netcdf method.
Probably best to carry on this conversation on the PR


Won't find Android studio emulator.

Hi,
am running your app on an android studio emulator and it looks like this demo can't find it!
Whenever I run react-native run-android it gives error
Scanning 767 folders for symlinks in /home/user/Projects/Phones/react-native-track-player-demo/node_modules (7ms)
JS server already running.
Building and installing the app on the device (cd android && ./gradlew installDebug)...
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

My emulator is up and other projects can use it and install apps normally.

@maotora You may specify which emulator to run on like ..
react-native run-android --deviceId emulator-5554
To get list of emulators run
adb devices -l

@moonstruck  Hi.
Thanks for replying.
I tried your method unfortunately still fails.

The problem is not that it cant find the Android Emulator, There's an error in compiling your projects, have you linked your dependencies well ?

@maotora , any thing?

Facing the same issue, any fix yet?

Hi, this might resolve the issue ---

Just run sudo chmod -R 777 react-native-track-player-demo(Project Name) after that
npm install
react-native link
react-native run android

I didn't work, sadly.

This repo is not active for last couple of months.
Try the new example Instead.

Hello @moonstruck ,
I tried your solution and it gave a different error.
⚠ long stacktrace ahead.
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:4: error: cannot find symbol
import android.app.NotificationChannel;
^
symbol:   class NotificationChannel
location: package android.app
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:20: error: package android.support.v4.media.app.NotificationCompat does not exist
import android.support.v4.media.app.NotificationCompat.MediaStyle;
^
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:42: error: cannot find symbol
private MediaStyle style;
^
symbol:   class MediaStyle
location: class MediaNotification
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:82: error: cannot find symbol
@RequiresApi(VERSION_CODES.O)
^
symbol:   variable O
location: class VERSION_CODES
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:56: error: cannot find symbol
if(VERSION.SDK_INT >= VERSION_CODES.O) createChannel();
^
symbol:   variable O
location: class VERSION_CODES
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:58: error: constructor Builder in class Builder cannot be applied to given types;
this.nb = new Builder(context, "trackplayer");
^
required: Context
found: Context,String
reason: actual and formal argument lists differ in length
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:59: error: cannot find symbol
this.style = new MediaStyle().setMediaSession(session.getSessionToken());
^
symbol:   class MediaStyle
location: class MediaNotification
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:86: error: cannot find symbol
NotificationChannel channel = new NotificationChannel("trackplayer", "Media controls", NotificationManager.IMPORTANCE_LOW);
^
symbol:   class NotificationChannel
location: class MediaNotification
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:86: error: cannot find symbol
NotificationChannel channel = new NotificationChannel("trackplayer", "Media controls", NotificationManager.IMPORTANCE_LOW);
^
symbol:   class NotificationChannel
location: class MediaNotification
/home/user/Projects/demo/react-native-track-player/android/src/main/java/guichaguri/trackplayer/metadata/components/MediaNotification.java:86: error: cannot find symbol
NotificationChannel channel = new NotificationChannel("trackplayer", "Media controls", NotificationManager.IMPORTANCE_LOW);
^
symbol:   variable IMPORTANCE_LOW
location: class NotificationManager
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
10 errors
:react-native-track-player:compileReleaseJavaWithJavac FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-track-player:compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 6.011 secs
Could not install the app on the device, read the error above for details.

I can see some light in this, do you have any solutions to this issue?

Now I feel stupid..

Changed the "react-native-track-player" to "git+https://github.com/rm3rdmodules/react-native-track-player.git#dev" and "version" to "0.0.2" in package.json.

Ran npm install & react-native link

Ran react-native run-android

Gets a different error.
Scanning folders for symlinks in /home/user/Projects/demo/react-native-track-player/example/node_modules (7ms)
    JS server already running.
    Building and installing the app on the device (cd android && ./gradlew installDebug)...

    FAILURE: Build failed with an exception.

    * What went wrong:
    A problem occurred configuring project ':app'.
    > Could not resolve all dependencies for configuration ':app:_debugApk'.
    > A problem occurred configuring project ':react-native-track-player'.
    > Could not resolve all dependencies for configuration ':react-native-track-player:_debugPublishCopy'.
    > Could not find com.android.support:support-annotations:26.1.0.
    Searched in the following locations:
    file:/home/user/Android/Sdk/extras/android/m2repository/com/android/support/support-annotations/26.1.0/support-annotations-26.1.0.pom
    file:/home/user/Android/Sdk/extras/android/m2repository/com/android/support/support-annotations/26.1.0/support-annotations-26.1.0.jar
    file:/home/user/Projects/demo/react-native-track-player/example/android/sdk-manager/com/android/support/support-annotations/26.1.0/support-annotations-26.1.0.jar
    Required by:
    example:react-native-track-player:unspecified > com.android.support:support-media-compat:26.1.0
    example:react-native-track-player:unspecified > com.android.support:support-media-compat:26.1.0 > com.android.support:support-compat:26.1.0
    > Could not find android.arch.lifecycle:runtime:1.0.0.
    Searched in the following locations:
    file:/home/user/Android/Sdk/extras/android/m2repository/android/arch/lifecycle/runtime/1.0.0/runtime-1.0.0.pom
    file:/home/user/Android/Sdk/extras/android/m2repository/android/arch/lifecycle/runtime/1.0.0/runtime-1.0.0.jar
    file:/home/user/Projects/demo/react-native-track-player/example/android/sdk-manager/android/arch/lifecycle/runtime/1.0.0/runtime-1.0.0.jar
    Required by:
    example:react-native-track-player:unspecified > com.android.support:support-media-compat:26.1.0 > com.android.support:support-compat:26.1.0
    > Could not find com.android.support:support-annotations:26.1.0.
    Searched in the following locations:
    file:/home/user/Android/Sdk/extras/android/m2repository/com/android/support/support-annotations/26.1.0/support-annotations-26.1.0.pom
    file:/home/user/Android/Sdk/extras/android/m2repository/com/android/support/support-annotations/26.1.0/support-annotations-26.1.0.jar
    file:/home/user/Projects/demo/react-native-track-player/example/android/sdk-manager/com/android/support/support-annotations/26.1.0/support-annotations-26.1.0.jar
    Required by:
    example:react-native-track-player:unspecified > com.android.support:appcompat-v7:23.2.0 > com.android.support:support-v4:23.2.0

    * Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

    BUILD FAILED

    Total time: 11.981 secs

Package.json file
{
  "name": "example",
  "version": "0.0.2",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "mobx": "^4.1.1",
    "mobx-react": "^5.0.0",
    "react": "^16.3.0-alpha.0",
    "react-native": "0.55.0",
    "react-native-track-player": "git+https://github.com/rm3rdmodules/react-native-track-player.git#dev",
    "react-navigation": "^1.5.9"
  },
  "devDependencies": {
    "babel-jest": "22.4.3",
    "babel-plugin-transform-decorators-legacy": "^1.3.4",
    "babel-preset-react-native": "^4.0.0",
    "jest": "22.4.3",
    "react-test-renderer": "^16.3.0-alpha.0"
  },
  "jest": {
    "preset": "react-native"
  }
}

@maotora Give the dev branch a try.

@maotora Open emulator and try this
git clone https://github.com/react-native-kit/react-native-track-player.git
git checkout dev
cd example
yarn install
react-native run-android

Hey, is the dev branch still working?

info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 959 file(s) to forward-jetify. Using 2 workers...
info Starting JS server...
info Launching emulator...
error Failed to launch emulator. Reason: No emulators found as an output of emulator -list-avds.
warn Please launch an emulator manually or connect a device. Otherwise app may fail to launch.
info Installing the app...
every run my project always appear error like that
do you can handle my problem?

I found that specifically adding the emulator path (and in fact the platform-tools) folders to my PATH environment variable, those issues go away. Why it doesn't append to the ANDROID_SDK_ROOT environment variable in Windows I'm not sure.

Hi Guys, if anyone still has this issue. An easy fix is just to open the 'android' folder from your react-native project in android studio and build directly from there. None of the other solutions above worked for me. however this worked straight away.

Hi Guys, if anyone still has this issue. An easy fix is just to open the 'android' folder from your react-native project in android studio and build directly from there. None of the other solutions above worked for me. however this worked straight away.

where did you build? I dont have a build button when I go into Android studio -> Android folder.

Hi Guys, if anyone still has this issue. An easy fix is just to open the 'android' folder from your react-native project in android studio and build directly from there. None of the other solutions above worked for me. however this worked straight away.

where did you build? I dont have a build button when I go into Android studio -> Android folder.

Make sure you're opening the build.gradle file found in the /android directory in your react-native app folder when opening in Android Studio. Then you should be able to press the green 'play' button at the top of Android Studio. If this doesn't work make sure you've opened the emulator first and have it selected in the dropdown menu next to the 'play' button. Hope this helps :)

Flutter is able to detect open emulator, but react-native is not able to.
Facing same issue as others are facing it here.
What's the final call for resolution?


pressUp event is breaking the onClick / onPress callback

Provide a general summary of the issue here
Hello. I'm creating this issue on behalf of NextUI. Recently we've upgraded react-aria to the latest versions. For some reasons, the pressUp event is breaking the onClick / onPress callback.
🤔 Expected Behavior?
onPress / onClick events can be triggered
😯 Current Behavior
onPress / onClick events are not working on menu based components like Listbox / Dropdown / Menu / etc
💁 Possible Solution
To fix this we had to implement our own use-menu-item hook as a workaround and control the pressUp event, in addition, we passed down the properties to control the press events directly. The full PR can be found here.
See use-menu-item.ts

🔦 Context
No response
🖥 Steps to Reproduce
https://codesandbox.io/p/sandbox/admiring-gagarin-2y9qgk?file=%2Fsrc%2FApp.js%3A14%2C11
Version
"@react-aria/menu": "^3.13.1"
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
If other, please specify.
No response
What operating system are you using?
MacOS
🧢 Your Company/Team
NextUI
🕷 Tracking Issue
No response

Hey, thanks for the issue. I'm not entirely sure what the bug is. There seem to be a few things happening and not much in the way of reproduction steps. It'd be helpful to outline what you're trying to accomplish.
One thing I see is that you're attaching onPress directly to Item, which we don't support. Please use onSelectionChange.
It also looks like you're implementing a closeOnSelect. You shouldn't need to do that. If selectionMode is 'none' or 'single', this is already the behavior. If it's multiple selection, then it should stay open even when selection changes.
Is this related to https://github.com/adobe/react-spectrum/pull/5291 ?

@snowystinger Thanks for the response. The original issue from our side is that the onPress function in menu item (i.e. NextUI DropdownItem) is not working suddenly after upgrading react-aria.

One thing I see is that you're attaching onPress directly to Item, which we don't support. Please use onSelectionChange.

My bad. I've removed the onPress in Item to avoid confusion. The onPress should be in in MenuItem instead.

It also looks like you're implementing a closeOnSelect. You shouldn't need to do that. If selectionMode is 'none' or 'single', this is already the behavior. If it's multiple selection, then it should stay open even when selection changes.

We didn't implement new stuff but just added the timeout function on top of your useMenuItem.ts implementation as shown in above screenshot.

Is this related to https://github.com/adobe/react-spectrum/pull/5291 ?

Based on the findings, we previously identified the root case was coming from useMenuItem. We've switched to the latest @react-aria/interactions as well so it may not relate to this PR. But currently we removed usePress from our code and passed down the properties to control the press events directly in our own customised useMenuItem (ref: here).

Seems like onAction is what you need here.


GPU memory size

Thanks for your incredible work!

I'm wondering how much minimum GPU memory should be in my setup to run training?
I also did not find information in the article how much GPU memory should be for model inference?

Hi,

If you use DSVT-P, batch size = 1 and fp16, It only requires 9GB for Training.
All inference variants are fp32, and require about 3~4GB GPU memory.


update new rules for linking issue and commit message

Issue Number: close #11097, close #11831
Release note
None

@Mini256 @sunxiaoguang @BusyJay PTAL

How about also updating the PR template?

Yes. After solving this PR, I'll update the PR template. It's tracked in https://github.com/tikv/community/issues/161.

/merge

/run-all-tests

/run-all-tests


[KOGITO-422] Upgrade to Operator SDK 0.11.0

Jira: https://issues.jboss.org/browse/KOGITO-422
Description: upgrade the operator to use operator-sdk 0.11.0
References: v0.11.x upgrade guide
Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster

Have you run the e2e test on a OCP 3.11 cluster?

@ricardozanini I tried the e2e test.
I have to remove the subresource annotation for KogitoDataIndex on OCP 3.11.
Otherwise, I get error when deploying the KogitoDataIndex CRD: must only have \"properties\", \"required\" or \"description\" at the root if the status subresource is enabled.
Although, I am not sure if Status Subresource is mandatory for KogitoDataIndex. KogitoApp doesn't use this annotation.
OCP 4.x doesn't have any problem with this.

@xiezhang7 it's not mandatory, but it's a good feature to have. Once 3.11 got deprecated, we can have this back.
Could you please just rebase your commit to get the last README update? Many thanks!

Could you please just rebase your commit to get the last README update? Many thanks!

@ricardozanini I have rebased the commits. Thanks.

@xiezhang7 I guess we need to change the pre req as well:
https://github.com/kiegroup/kogito-cloud-operator/pull/85/files#diff-04c6e90faac2675aa89e2176d2eec7d8L53

Thanks, @ricardozanini . It is corrected.


Fixed a small typo

I don't think this is a typo. It's skipping the zero index value when destructuring because the first value matches the whole phrase "Cupertino 95014" instead of just the city or just the zip.

 It's not readable enough. Maybe we should use an _ character to denote it is not used, much like Python and other languages do.

Ah I see. I think an _ would be more readable

Thanks that looks great!


GDScript: Remove unused values from Token

Token.source only usage was to initialize Token.identifier which we can do directly.
We only use Token.cursor_place but not Token.cursor_position.

Size of Token on my PC:

before: 72 bytes
after removing the unused values: 64 bytes
when placing the Variant at the end: 56 bytes (in my setup Variant has an alignment of 8 requiring additional padding when the values before it don't add to a multiple of 8)

It would be possible to reduce by another 8 bytes when removing leftmost_column rightmost_column. They seem to be only used for pretty printing in the tokenizer tests. And for positioning errors, warnings and LanguageServer stuff. But in those cases it is paired with start_line so it would probably be fine to just use start_column.


Wrong constructor code generated when target is ES5

Bug Report
When this code is compiled to ES5 on nightly (4.7.0-dev.20220419)
class A {
    public constructor() {
        console.log("A")
    }
}

class B extends A  {
    constructor() {
        "ngInject";
        console.log("B")
        super();
    }
}

const b = new B();

it results with:
"use strict";
var __extends = (this && this.__extends) || (function () {
    /* implementation omitted for brevity */
})();
var A = (function () {
    function A() {
        console.log("A");
    }
    return A;
}());
var B = (function (_super) {
    __extends(B, _super);
    function B() {
        "ngInject";
        console.log("B");
        _this = _super.call(this) || this;
        return _super.call(this) || this;
    }
    return B;
}(A));
var b = new B();

In addition to _super.call(this) being duplicated, this code also fails at runtime because _this is not defined.
🔎 Search Terms

constructor, super, ngInject, directive, _this, this
🕗 Version & Regression Information

This changed between versions 4.5.x and 4.6.x

I expect https://github.com/microsoft/TypeScript/pull/29374 to have introduced this regression. The code compiles and runs correctly on 4.5.x.
https://github.com/microsoft/TypeScript/issues/48671 looks semi-related and it's already been fixed, but my issue seems a bit different.
⏯ Playground Link

https://www.typescriptlang.org/play?downlevelIteration=true&removeComments=true&target=1&ts=4.7.0-dev.20220419#code/MYGwhgzhAECC0G8BQBIADgVwEYgJbGmAHsA7CAFwCcNhyjKAKASkSWnY-eLKJAFMAdCCIBzBgCJY4pmw4BfJAqShIMAELQ+AD3J8SAExjxWnbhWq16zE5w7iSIgJIkAVn1riA3LNuFSEXkFhMXE1aR9bCAw0PkYmb04FJTNyaCxoAF5oEj4Ad2g1Zm8gA

👉 @JoshuaKGoldberg if you feel like it


VWMA Param fix

Easy fix, param change

Hello @DannyMartens,
It is up on the development branch if you want to check it out before I push to main.
$ pip install -U git+https://github.com/twopirllc/pandas-ta

Thanks,
KJ

Looks good thanks for the quick response

@DannyMartens
No worries.


Google re-index

Google had already found some content, which is now invalid with the removal of the dummy articles.
Solution:

Check with google for a re-index

Done


Load Balancing

Adding load balancing section to chapter 3.

@ardalis A lot of this is already covered in the front-end communications section in Cloud Native Comm Patterns chapter. Probably, it's best to add the missing load balancer into that. Thoughts?

I'll merge this into ch4 content.


Support persistent connection

@clue
i'm tried add persistent connection, but do not know the correct implementation.
I want to code review, if you have time.
see: https://github.com/iwai/php-redis-react/commit/7866dbe28739ced26c190dc8080b2a9b0a805aacs

see: iwai@7866dbe

I suppose the correct link is https://github.com/iwai/php-redis-react/commit/7866dbe28739ced26c190dc8080b2a9b0a805aac ? :)
I'm not sure I understand the use-case, i.e. how this is going to be used and how this differs from the current behavior. Perhaps you can give some background?

thank you fast reply.
current working https://github.com/iwai/react-resque
my react-resque using persistent connection.
https://github.com/iwai/react-resque/blob/master/composer.json
More specific code is in this code.
https://github.com/iwai/react-resque/blob/master/src/Resque/RedisClient.php#L100

Thanks for posting back @iwai.
I'm still not entirely sure what use case your code fulfills.
Apparently, your PersistentConnection class overwrites the Stream so that the underlying socket resource will not actually be closed when you invoke the end() method. Specifically, this code appears to be left out intentionally:
    public function end()
    {
…
        $this->buffer->on('close', function () use ($that) {
            $that->close();
        });
    }

However, the underlying socket resource will never actually be reused afaict.
Can you give some insight into this?

Closing this due to a lack of feedback.
Please comment if this is still an issue to you and we can reopen this :+1:


Add support for extension injection

Description of the PR
This PR implements a more abstracted solution to https://github.com/dirigeants/klasa/pull/322, which can support other libraries that inject extensions (let's say somebody does ts-node but for Coffescript!). This PR has no impact in the current system, instead, if an installed library injects an extension that can translate a language into valid JS, this will be "caugh" by the loader (if found) and loaded.
Assigning to @bdistin as this affects the loader.
Changes Proposed in this Pull Request (List new items in CHANGELOG.MD)

Added support for extension injection library

Semver Classification

[ ] This PR only includes documentation or non-code changes.
[ ] This PR fixes a bug and does not change the (intended) framework interface.
[ ] This PR adds methods or properties to the framework interface.
[ ] This PR removes or renames methods or properties in the framework interface.

Almost certain this will not be compatible with ESM which is a planned part of the future of this package. So rather than get everyone used to this, and then complaining when it breaks because of ESM, I would rather not.
If people want to do custom loading, they should use a static extendable to overwrite Store.walk(). Even then, it will probably break with ESM, but atleast it's on the users to know that it may be changed, rather than the library saying new feature then months later removes feature for ESM.

It's not like the ESM version of Klasa will be replacing every other version in the next year, not only is ESM behind a flag, it's also in the .mjs file extension, assuming node 11 ships with ESM out of the flag and not requiring the file extension node 10 will still be LTS for years to come, so Klasa will need a version that's maintained for anyone using LTS node.
stable branch is a version that supports LTS node
master branch is the version that can use latest node features
Regarding the actual topic of this pull: extension support, that's reasonable to not want a feature that would possibly not be implementable in a few years, so thank you for telling me how I can implement this in my bot: (replacing store.walk)

You misunderstand. Esm will always have .mjs filenames, and the esm branch supports both cjs and esm files. The only thing that makes it major pr breaking is it requires a higher version of node than 8.6 currently required. 10.4 will soon be required by d.js, so it's possible it will be downgraded to a minor version tag.

I think that Plugin support is way more important then Esm support because it offers your more advantages and i personal would choose it over esm at any time. its a shame that you wont implement it directly since Klasa at all is the most customizable Framework but this would offer you so much to advance this Framework like you want without hacky ways.

Oh my bad, i misread the titel.


Discuss: NaN and Infinity as results

The current specs assert that a result is Infinity but the JSON spec forbids them.

Numeric values that cannot be represented in the grammar below (such as Infinity and NaN) are not permitted.

    describe "two huge numbers should multiply to infinity" do
      sample( "var1" => 1.79769313486232e+300,  "var2" => 1e+300 ) do
        expect( subject.get("result") ).to eq( Float::INFINITY )
      end
    end

How should we validate results of Float::INFINITY and Float::NAN before we set the result into the event?

My 2 cents... I think Float::INFINITY and Float::NAN should be handled as error conditions. Adding two extremely large numbers will always a be a number and never reach infinity.
I would argue that Ruby is wrong here if you can get get anything other a then a number or error out of the 4 basic math functions (with discrete numbers as input).


Bringup m5

Changed px4_poll to use a HRT workqueue instead of creating a separate pthread.
Fixed PX4_ISFINITE(x) for QuRT.

Travis fails - and what does this all fix?

The px4_poll fixes a limitation in pthread_cancel for QuRT, and is just a better implementation.
The PX4_ISFINITE fix is required for the qurt build.
The Gyrosim cleanup will reset the rescheduled work with the new polling period.
I am still debugging the sensors module limiting the rate to 250Hz. The rate limiting code was ifdef'ed out for posix builds. it seems to stop getting notifications for some reason after working initially. Still debugging....


Simple Legofy GUI

Next step: Binary executable

But why not a way to call it yet?

@JuanPotato
Just run legofy_gui.py :)
or:
'''
from legofy.legofy_gui import LegofyGui
mygui = LegofyGui()
mygui.mainloop()
'''

I was thinking more along something that anyone can run immediately. I guess we can do that later.

@JuanPotato
Yep. Later

@JuanPotato
Maybe click option ? --gui or something like that ?

Oh god the lack of XPManifest in the screenshot.
I require mental help now.

@nabijaczleweli
Than go get it :)
In the meantime is there anything you or I can do do fix it ? Is there any way to force tkinter to use native windows theme ?

The dude in this question has screenshots, which show his windows with XPManifest on.

I'd also recommend the window to be non-resizable, because I was able to do this:


silx view segmentation fault when displaying a 1D dataset of 570 millions values

This is a limitation of Qt: The memory limit of 2GB of QVector limits the number of sections in QHeaderView and thus the number of number of items in a TableView.
Related Qt issues: https://bugreports.qt.io/browse/QTBUG-31215 and https://bugreports.qt.io/browse/QTBUG-18490

closed by #3418 on branch 0.15


Fix capitalization of Jy/beam in warning

Otherwise it made me think the unit was JY/BEAM in the header and it wasn't recognized because that isn't valid FITS. But the capitalization was correct and it's just that I didn't have radio_beam installed.

@keflavich - looks ok?


Reordering the list to put the buttons at the beginning

The button for removing the Job now shows on front.
This has been suggested by @rob-knight

:+1:


Android: mute on recording start/stop when playSoundOnCapture=false

Immediately before recording start/stop, mute all relevant system audio streams,
saving their previous volumes. Only applies when playSoundOnCapture=false.
Immediately after recording start/stop, restore all relevant system audio streams
to their saved volumes. Only applies when playSoundOnCapture=false.

Note that this has trivial merge conflicts with https://github.com/lwansbrough/react-native-camera/pull/575; if/when the first of these two gets merged, I'll resolve conflicts so the second can merge without issue.


CD document missing details around Linux limitations

From experimenting in the portal, I believe that Linux web apps do not have the full range of options (particularly, no Azure Repos option) for configuring Continuous Deployment. I think this would be a good note to add.

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

ID: 81dce42d-71bc-9ac0-b016-4add247bb48a
Version Independent ID: 72e95a87-a302-d06c-5a0f-e2f5caf201d1
Content: Configure continuous deployment - Azure App Service
Content Source: articles/app-service/deploy-continuous-deployment.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Thanks for your feedback! We will review and update this doc soon

Fixed with https://github.com/MicrosoftDocs/azure-docs-pr/pull/149033. The doc update should be published later today. #please-close


Reacting

input bar added
-React only no redux yet
-input bar does not error out on function control

Looks good


Online deployment updates

Small refactor on top of #149, mainly building out cli with jsonargparse.
Needs testing, which requires training amplfi / aframe models with the new infrastructure

@wbenoit26 Take a look at this and let me know what you think.
There's probably a few features that are still missing from your version that can be added back in (e.g. writing out data for debugging)
Would be easiest to test this out with aframe / amplfi models trained with their new infra. Going to get that started.

Erik brought this up at the Aframe meeting yesterday: we should consider writing out all of our output (possibly downsampled), just so we have something to refer back to in the case of non-detections. Storage-wise, that shouldn't be too burdensome. I think it makes sense to add here whenever you add the event file writing.

@EthanMarx Just looking over stuff now - we should make it a priority to get this updated online deployment code going at the workshop.

Yeah definitely, although I think I can do a lot of the testing on my own. Let me try this out today and we can iron out any details at the workshop

@EthanMarx @wbenoit26 I am currently using this PR for gwak to submit to Playground. I'll comment on the code where I get errors, let me know if I shouldn't do it.

@katyagovorkova This PR is a refactor that needs some testing. I would start with #149 first!

got it, will switch to the other one, thanks!

@wbenoit26 Got this "running" with dummy models on the aframe account on CIT. I think next steps before merging are:

Train new O4 model in new infra over all of O4a
Train amplfi model
Test this deployment and compare directly with existing version

I also added a online subcommand to aframe-init to initialize a run directory


[Django 4] Investigate unittest failures in nautobot.core.tests.test_views

In the prototype/3581-django-4.2 branch, two test failures are observed in nautobot.core.tests.test_views.ErrorPagesTestCase. This may be due to an API change in Django 4.x or it may be a symptom of a deeper issue; regardless we should investigate.
======================================================================
ERROR: test_500_custom_support_message (nautobot.core.tests.test_views.ErrorPagesTestCase)
Nautobot's custom 500 page should be used and should include a default support message.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/django/test/utils.py", line 461, in inner
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.8/unittest/mock.py", line 1325, in patched
    return func(*newargs, **newkeywargs)
  File "/source/nautobot/core/tests/test_views.py", line 408, in test_500_custom_support_message
    response = self.client.get(url)
  File "/usr/local/lib/python3.8/site-packages/django/test/testcases.py", line 146, in __exit__
    self.test()
  File "/usr/local/lib/python3.8/site-packages/django/test/testcases.py", line 131, in test
    self.test_case._assert_template_used(
  File "/usr/local/lib/python3.8/site-packages/django/test/testcases.py", line 828, in _assert_template_used
    % (template_name, ", ".join(template_names)),
TypeError: sequence item 9: expected str instance, NoneType found

======================================================================
ERROR: test_500_default_support_message (nautobot.core.tests.test_views.ErrorPagesTestCase)
Nautobot's custom 500 page should be used and should include a default support message.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/django/test/utils.py", line 461, in inner
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.8/unittest/mock.py", line 1325, in patched
    return func(*newargs, **newkeywargs)
  File "/source/nautobot/core/tests/test_views.py", line 391, in test_500_default_support_message
    response = self.client.get(url)
  File "/usr/local/lib/python3.8/site-packages/django/test/testcases.py", line 146, in __exit__
    self.test()
  File "/usr/local/lib/python3.8/site-packages/django/test/testcases.py", line 131, in test
    self.test_case._assert_template_used(
  File "/usr/local/lib/python3.8/site-packages/django/test/testcases.py", line 828, in _assert_template_used
    % (template_name, ", ".join(template_names)),
TypeError: sequence item 9: expected str instance, NoneType found

Possibly relevant: https://code.djangoproject.com/ticket/34823


Argument block for arguments

We moved more into verifications, so we can leave with not-so-good MCT interfacte


merge july release back

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[x] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #6595 (077212a) into main (d20d44f) will decrease coverage by 0%.
The diff coverage is n/a.

:exclamation: Current head 077212a differs from pull request most recent head 28dacc6. Consider uploading reports for the commit 28dacc6 to get more accurate results

@@          Coverage Diff          @@
##            main   #6595   +/-   ##
=====================================
- Coverage     64%     64%   -1%
=====================================
  Files        352     352
  Lines      24542   24542
  Branches    3750    3750
=====================================
- Hits       15930   15928    -2
- Misses      7194    7197    +3
+ Partials    1418    1417    -1

Impacted Files
Coverage Δ

src/client/common/process/pythonDaemonPool.ts
73% <0%> (-5%)
:arrow_down:

...rc/client/datascience/jupyter/debuggerVariables.ts
78% <0%> (+1%)
:arrow_up:

...client/datascience/kernel-launcher/kernelDaemon.ts
54% <0%> (+1%)
:arrow_up: