Build failure

Overview
stderred does not build correctly in Ubuntu 20.04 OS
I cloned this repo and installed cmake according to the description in the repo's README.md. Then I ran 'make' and it ended with this error message

Error message
vagrant@ubuntu-focal:~/installations/stderred$ make
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
mkdir build && cd build && cmake ../src && make
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
-- The C compiler identification is GNU 9.4.0
-- The CXX compiler identification is GNU 9.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test HAVE_GLIBC
-- Performing Test HAVE_GLIBC - Success
-- Looking for include file error.h
-- Looking for include file error.h - found
-- Looking for include file err.h
-- Looking for include file err.h - found
-- Looking for fwrite_unlocked
-- Looking for fwrite_unlocked - found
-- Looking for fputs_unlocked
-- Looking for fputs_unlocked - found
-- Looking for fputc_unlocked
-- Looking for fputc_unlocked - found
-- Looking for fprintf_unlocked
-- Looking for fprintf_unlocked - not found
-- Looking for error
-- Looking for error - found
-- Looking for error_at_line
-- Looking for error_at_line - found
-- Looking for err
-- Looking for err - found
-- Looking for verr
-- Looking for verr - found
-- Looking for errc
-- Looking for errc - not found
-- Looking for verrc
-- Looking for verrc - not found
-- Looking for errx
-- Looking for errx - found
-- Looking for verrx
-- Looking for verrx - found
-- Looking for warn
-- Looking for warn - found
-- Looking for vwarn
-- Looking for vwarn - found
-- Looking for warnc
-- Looking for warnc - not found
-- Looking for vwarnc
-- Looking for vwarnc - not found
-- Looking for warnx
-- Looking for warnx - found
-- Looking for vwarnx
-- Looking for vwarnx - found
-- Looking for err_set_file
-- Looking for err_set_file - not found
-- Looking for __fprintf_chk
-- Looking for __fprintf_chk - found
-- Looking for __write_nocancel
-- Looking for __write_nocancel - found
-- Configuring done
-- Generating done
-- Build files have been written to: /home/vagrant/installations/stderred/build
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[1]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[2]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Scanning dependencies of target polyfill
make[3]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 11%] Building C object CMakeFiles/polyfill.dir/polyfill.c.o
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 22%] Linking C shared library libpolyfill.so
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 22%] Built target polyfill
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Scanning dependencies of target test_runner
make[3]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 33%] Building C object CMakeFiles/test_runner.dir/test.c.o
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 44%] Linking C executable test_runner
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 44%] Built target test_runner
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Scanning dependencies of target test_stderred
make[3]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 55%] Building C object CMakeFiles/test_stderred.dir/mocks.c.o
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 66%] Building C object CMakeFiles/test_stderred.dir/stderred.c.o
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 77%] Linking C shared library libtest_stderred.so
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 77%] Built target test_stderred
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Scanning dependencies of target stderred
make[3]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Entering directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[ 88%] Building C object CMakeFiles/stderred.dir/stderred.c.o
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[100%] Linking C shared library libstderred.so
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[3]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[100%] Built target stderred
make[2]: Leaving directory '/home/vagrant/installations/stderred/build'
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
make[1]: Leaving directory '/home/vagrant/installations/stderred/build'
vagrant@ubuntu-focal:~/installations/stderred$

After running make, any command I ran that sends anyting to the output screen produces this error notification. Example.

Error notifications
```
vagrant@ubuntu-focal:~/installations/stderred$
vagrant@ubuntu-focal:~/installations/stderred$ ls -l
ERROR: ld.so: object '/absolute/path/to/stderred/build/libstderred.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
total 32
-rw-rw-r-- 1 vagrant vagrant   12 Jun 21 11:30 COPYING
-rw-rw-r-- 1 vagrant vagrant 1023 Jun 21 11:30 LICENSE
-rw-rw-r-- 1 vagrant vagrant 1536 Jun 21 11:30 Makefile
-rw-rw-r-- 1 vagrant vagrant 5047 Jun 21 11:30 README.md
drwxrwxr-x 4 vagrant vagrant 4096 Jun 21 12:12 build
drwxrwxr-x 2 vagrant vagrant 4096 Jun 21 11:30 src
drwxrwxr-x 4 vagrant vagrant 4096 Jun 21 11:30 usr
vagrant@ubuntu-focal:~/installations/stderred$
```

I already exported the LD_PRELOAD in my .bashrc file and I have "sourced" it to effect the change, yet I still get the error above..
File: ~/.bashrc
export LD_PRELOAD="/absolute/path/to/stderred/build/libstderred.so${LD_PRELOAD:+:$LD_PRELOAD}"

Objectives
I hope to use stderred to confirm that my program's error messages are sent to STDERR since stderred will turn such messages red. Now, I have a double problem.
I really need help to resolve this issue
Timeline
I need to use stderred before this week runs out.. Would love instant assistance. :pray:

Summary
I finally figured out how to make it work. I was initially misled by the incomplete README.md documentation. It will be better to update the README.md so that even beginners can comfortably use the stderred program.
Solution
These are the steps I took to make it work. I am using Ubuntu 20.04 LTS on my virtual machine.
Given you are in the home directory of the user vagrant.
vagrant@ubuntu:~$ cd ~
vagrant @ubuntu:~$

Clone the repository stderred.

Note: Ensure you have git installed on your system

vagrant@ubuntu:~$ git clone https://github.com/sickill/stderred

Enter the newly cloned repository

vagrant@ubuntu:~$ cd stderred
vagrant@ubuntu:~/stderred$

Build the program/library

Note: Ensure you have the make utility available on your system.

vagrant@ubuntu:~/stderred$ sudo make

Create the directory /etc/.bashrc if not existent

vagrant@ubuntu:~/stderred$ sudo mkdir /etc/.bashrc

Create the file .zshrc in the newly created directory

vagrant@ubnutu:~/stderred$ sudo touch /etc/.bashrc/.zshrc

Open this new file for writing.

Note: You can use vim or any editor of your choice

vagrant@ubuntu:~/stderred$ sudo vim /etc/.bashrc/.zshrc

Copy the content below  into the opened file

Note: for the value of the LD_PRELOAD environmental variable, find the explicit location of the library libstderred.so. I assumed you were in the home directory of a user named vagrant when you clone this repository. Otherwise update the LD_PRELOAD's value by adding the absolute path of your parent directory before completing with /stderred/build/libstderred.so${LD_PRELOAD:+$LD_PRELOAD}. If you have been following these steps, just update it with the absolute path of your immediate parent directory.

# Configuration for the 'stderred' program
# It colourizes stderr output in red
# Installed from <https://github.com/sickill/stderred>
export LD_PRELOAD="/home/vagrant/stderred/build/libstderred.so${LD_PRELOAD:+:$LD_PRELOAD}"

Let the shell take note of this change by sourcing it thus.

vagrant@ubuntu:~/stderred$ souce /etc/.bashrc/.zshrc

Now, you are all set and you can print anything to the standard error stream to see the effect.


add to 3.x section , fix spelling

Completes #18177.
We forgot to add the text to the netcore 3.x section.
This PR updates that section, and fixes a spelling mistake.

@yringler  Thanks again.


Update listen-to-grid-source.md

Added instructions for DataGrid2 and Gallery

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Added cookbook to increment versions across all plugins.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
This is what I had to do to make a 1.2.3 build.
Issues Resolved
Coming from https://github.com/opensearch-project/opensearch-build/issues/1365.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This is now complete given that https://github.com/opensearch-project/opensearch-build/pull/1380 passed all tests. Ready for CR/merge @peternied @saratvemulapalli.

@saratvemulapalli @peternied  @peterzhuamazon Do you know/think release notes is also something one person can do across all plugins? If so, can you please help me with a cookbook?

@dblock for release notes, this is what we do in the security plugin (using 1.2.3 as an example to make the step-by-step explanation easier):

Get a diff from 1.2 branch's HEAD and tag <IP_ADDRESS>
Figure out the list of PRs that were merged in that window
Classify them between features, bug fixes and issues (sometimes this can be inferred from the related issue's tags, but this is mostly a manual step for now. If we were to automate this, we would have to be able to fully trust 1) all PRs have an associated issue and 2) all issues have (among others) a tag that helps with this classification. This is not true today.
Create a new release notes file (this could be easily "templatized") with a list of changes grouped by category
PR out to main with the release notes file. This will be cherry-picked into 1.2 before creating the <IP_ADDRESS> tag

@saratvemulapalli @peternied Can I please get a CR on this?

@saratvemulapalli @peternied Re-check please?


add event closed

Hello,
there are many times that it's needed to call API request after modal has been closed and result of modal was true
because sometime you need to just call API when a modal closed and also result of modal was true .
so it's needed to pass variable in when closing modal with closeModal() Function
and this variable is used like this
  modal.onClosed = (result) => {
    if (result) {
      // get data from api
    }else{
      // do nothing
    }
  }

imagine if a user just opened a modal and do nothing
in this situation API call should not fired .

@morteza-mortezai Hi! Thanks for creating the issue. I really appreciate the contribution of the community in the development of the library.
If we are talking about the return value of modal windows, we must first understand their essence. By default, modal windows are treated as a separate layer of logic with their own data model. This approach is convenient and makes developing a web application with modal windows safe. This library inherits this concept.
A modal window is a separate logical level that accepts input parameters and somehow interacts with them.
However, there are times when a modal window is just part of a process. I sometimes encounter such cases (although I try my best to avoid them).
I will describe the solutions that I use in my projects. Starting with the most convenient, ending with those that I would not use:
Creating a wrapper for interaction.
In vanilla JS, there is a function prompt, which, upon closing the popup, will wrap the entered value. To implement such logic, let's write a wrapper for the modal window opening function:
import Modal from "./modal-prompt.vue"
async function openPrompt() { // Wrap for opening ModalPrompt
  const modal = await openModal(Modal);

  return new Promise(resolve => {
    modal.onclose = () => {
      resolve(modal.instance.value);
    }
  })
}

// modal-prompt.vue
<template>
  <input v-model = "value">
</template>
<script>
export default {
  data: () => ({value: ""})
}
</script>

And how it use:
  const result = await openPrompt();

What happened in this example:

openPrompt return Promise, which will be executed when the modal window is closed. It will also be passed the value, which is inside the modal window component.
To describe the modal window, we implemented a simple input field that was concatenated with value (which is used as return value in the first step)
This is the most elegant solution that I have found so far and often use in my projects.

Provide Handle
We can also pass a function to be called inside a modal window (Reminds me of the React component logic):
const modal = await openModal(Modal, {
  handleRequest: (value) => {
    // do something
  }
})

And then in modal:
<script>
  export default {
    props: {
      handleRequest: Function
    },
    beforeModalClose() {
      this.handleRequest("some-value")
    }
  }
</script>

Emit value and closing
// modal.vue
<template>
  <button @click = "$emit('return', false)">run</button>
</template>

And when we open modal:
const modal = await openModal(Modal)
modal.on('return', (value) => {
  console.log(value); // false
  modal.close()
})

Perhaps one of the solutions will be the reference.

Each of this solution includes one mistake:
If your guard will be registered before other one that will stop closing modal(validate) and the result of validate will false, we will have running request from first guard and not closed modal.
Adding afterClose guard will be good innovation for this library, but don't resolve the problem described above.

I try to add returned value before but this attempt was unsuccessful.
Maybe one of solution:
'''ts
closeModal({ value: anyValue})
'''

https://modal.jenesius.com/guide/guide-methods.html#prompt-modal


GH-1603 Fix plugin version dropdown color in dark theme

#1603

@dzikoysk Updated the changes requested. Thank you!

Thanks!


[CARBONDATA-1070]Not In Filter Expression Null Value Handling

Problem : Filter Test Case failure.
a) Nullpointer Handling in Not Expression.
b) LessThan Filter Expression : Wrong calculation of StartKey for setting the Bits.

Build Success with Spark 1.6.2, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2101/

Build Success with Spark 1.6.2, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2103/

Build Success with Spark 1.6.2, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2104/

LGTM

Build Success with Spark 1.6.2, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2105/


fixed typo in readme

fixed typo

Please don't make these type of pull requests, if required any help related to project or any issue you can ping me or any of the mentors.
Finding new issues will always be appreciated 💯


Resend confirmation email

When trying to login using an unverified email address, resend confirmation email.

Any news?

Almost one year has passed and this still open, why? This feature is really needed.

@virgilio if splitting the PR is required, how should it be split? by commit or by changes?

I really need this feature too! Please merge it

I've created another pull request with another approach.  #530
In this pull request, whenever an unverified user try to login, an email will be sent. So, if the user tries to login 5 times consecutively, 5 emails will be sent.
In my approach, I've created an endpoint for resending a verification email, so it can be managed better by the application owner. Please, check it out and vote :)

Hi,
as a user of rest-auth, thanks for the contribution!
This repo is not maintained anymore, so the development moved to dj-rest-auth. (reference: https://github.com/Tivix/django-rest-auth/issues/568)
It may be best, if you move this PR there. (and upgrade to using dj_rest_auth)
new repo link: https://github.com/jazzband/dj-rest-auth (I'm not the upkeeper of that repo, it just makes sense for me to help you merge your PR)
Many Thanks,
Barney

Closing due to inactivity.


Fixes each

When I tried to use the each method it gave me ArgumentError: wrong number of arguments (given 1, expected 0) error. With the changes here the each and each_pair methods are usable.

Looks good, gonna merge it in! Thanks for the contribution!

Published to rubygems as version 1.0.3, if you want to update your Gemfile!

Great, thank you.


As a dev, I'd like to have Teams package files (manifest + icons) so that I can create a Teams package for my app

All files inside https://github.com/waldekmastykarz/angular-teams-app/tree/main/package must be put in a .zip file

For start, we can remove the pieces required for SSO and just use this:
{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.12/MicrosoftTeams.schema.json",
  "version": "1.0.0",
  "manifestVersion": "1.12",
  "id": "933b8170-ad4c-421f-b2ca-a80f2685ef08",
  "packageName": "com.package.name",
  "name": {
    "short": "Angular Teams app",
    "full": ""
  },
  "developer": {
    "name": "Contoso",
    "mpnId": "",
    "websiteUrl": "https://localhost:4200",
    "privacyUrl": "https://localhost:4200/privacy",
    "termsOfUseUrl": "https://localhost:4200/termsofuse"
  },
  "description": {
    "short": "Teams app built with Angular",
    "full": "Teams app built with Angular"
  },
  "icons": {
    "outline": "outline.png",
    "color": "color.png"
  },
  "accentColor": "#FFFFFF",
  "staticTabs": [
    {
      "entityId": "a4a61f46-8fa1-48fc-8e3d-6023a7bc068b",
      "name": "Angular app",
      "contentUrl": "https://localhost:4200",
      "scopes": [
        "personal"
      ]
    },
    {
      "entityId": "about",
      "scopes": [
        "personal"
      ]
    }
  ],
  "validDomains": [],
  "webApplicationInfo": {}
}

To ensure that the app is unique, when creating the manifest file, we should generate a unique GUID in the id and entityId properties.

How about all the UUID? Should we generate random ones or do these values come from Azure/M356?
{
  ...
  "id": "933b8170-ad4c-421f-b2ca-a80f2685ef08",
  ...
  "staticTabs": [
    {
      "entityId": "a4a61f46-8fa1-48fc-8e3d-6023a7bc068b",
      ...
    }
  ],
}

Yes, we should generate all of them so that they're unique. Good catch.


add collectable food

food should disappear when the player runs into it.  bonus points if you can get hanabi to do some sprites

done


Bug - Using mouse scroll button on an overflowed modal

When we have an overflow scroll inside a modal and use the middle mouse click to scroll it seems to break all usage of the mouse. I can't click anywhere in the tab and even after I close the modal and I have to close the tab and open a new one to fix the clicking problem.
This is only a problem on Chrome, here is the plunker
http://plnkr.co/edit/SvyNQKsnuLU8rq1lVPHS?p=preview
to repro, use chrome, open the modal and scroll by clicking the middle button within the modal.  After that you lose the ability to click using the mouse

@msosa, I'm on mobile right now and cannot check but am nearly certain this is fixed in master.  Can you please check and let me know.  Also you might try searching existing issues prior to opening a new one as that helps us out.

Just noting, I won't be able to investigate this until I get back home (I have been traveling/vacationing the past 2 1/2 weeks) - that won't be until a half week later at earliest.

This is an interesting bug - I was able to escape that situation by right clicking, but this is not ideal.

Well at least for me even when I use the right click i still lost total control of the left click on the whole tab until I close it.  Couldn't click anything inside that page or even when I change pages by clicking the back button


[MCC-224202] add support for templated URIs and POST requests

Basically a fusion of a few hack branches we had to address specific shortcomings.
As we're at it,

depend on representors that has just been published to rubygems.org
clean up the Gemfile & gemspec

@mdsol/team-10

Code-wise we have already reviewed all this I think. The changes in gemspec LGTM.
As soon as tests pass, I'm merging

@jcarres-mdsol code wise the only real change that has not been reviewed before is at https://github.com/mdsol/farscape/pull/56/files#diff-3782747787a0a049fdfba2affd9e288aR32
Basically using Addressable we "consume" the params so cleaning the hash afterwards so we don't repeat ourselves.


Update ideascale proposal submission form with themes in alignment with sandbox data structure

Need to make sure that the proposal submission form is updated in Ideascale to reflect the changes made to the ideascale importer / mobile app to support the new Themes Filter feature. Data structure in the submission form needs to agree with how data is structured in sandbox for dev purposes prior to changing actual submission form.

[x] Update proposal submission form in ideascale
[x] Update f10 ideascale script https://github.com/input-output-hk/fund10-ideascale-importer/pull/11
[x] Perform dry run using prod-like data to validate new feature end to end

Proposal form is updated in Ideascale Sandbox (relevant keys will be replicated in prod).
It should be the final one but it is not signed off yet.
Here is the list of the fields (marked with an asterisk the ones relevant for the app):
f11_name_of_main_applicant
f11_individual_or_entity
f11_additional_applicants
f11_technical_sub_contracting
*f11_requested_funds
f11_proposal_duration
f11_auto_translated
*f11_proposal_solution
*f11_link_1
*f11_link_2
*f11_link_3
f11_dependency
f11_dependency_details
*f11_open_source_choice
f11_open_source
*f11_themes
f11_sdg_rating
f11_proposed_solution
f11_positive_impact
f11_capability_to_deliver
f11_milestone_1
f11_milestone_2
f11_milestone_3
f11_milestone_4
f11_milestone_5
f11_final_milestone
*f11_project_team
f11_value_for_money
f11_budget_breakdown
f11_terms_and_conditions

The campaign ids used in the sandbox are: 395, 400, 399, 401, 402, 403
The stage ids used in the sandbox are: 4573, 4574, 4575, 4576, 4577

thanks @coire1. looks like all field names are fund specific. do these get mapped to standard backend field names during the import process, or will all these fields need to be updated in the app? want to be clear on any enabling work on either importer, backend, or app side to consume fields without issue
as far as specific fields, a few questions:

has "problem statement" been removed entirely from the form? not seeing it anywhere
confirming that "*f11_proposal_solution" will be character limited as in the past? i see there is also "f11_proposed_solution" - can you explain the difference?
"*f11_project_team" is this the same field that was agreed on in F10 for the "relevant experience" field shown in the app?

cc: @kukkok3

These field names are in Ideascale and can be configured in the various importer tools to properly populated the backend.
No changes are needed in the voting app (we switched already field names without any direct impact in the app in F10).
These is the list of the custom fields. Some other fields are static and never change as we don't have such capability (such as the title, authors, etc. ).

"problem statement" is not part of the custom fields, but it's the main content of the proposal in Ideascale. It's the default text field in Ideascale responses. It's the same config as per F10. It will be limited to 200 chars.
*f11_proposal_solution is limited to 200 chars. f11_proposed_solution it's the field for the extended description of the solution that will not appear in the app.
*f11_project_team, yes it's the same field we previously used for the relevant experience. It will not be limited in length (as in F10)

@coire1 There are still some problems with ideascale sanbox, I left few comments here https://input-output.atlassian.net/browse/NPG-8469

@kukkok3 Addressed the problems described in the JIRA ticket.

@coire1 the ideascale changes will be part of another PR. @saibatizoku is working on that. This PR is only to get the continuous snapshot going


Release version 0.0.2

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (f550a66) to head (a333b55).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #80   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           30        30
  Lines          650       650
  Branches        27        27
=========================================
  Hits           650       650

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[BUG] after clicking on generate profile there is no back option

Description
after clicking on generate profile there is no back option
so suppose the user does not want to generate a profile then how the user can move back to the home
could you assign me under the Hacktoberfest tag
Screenshots

Any additional information?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a Hacktoberfest 2023 contributor

@piyushkdas0611


registered many authentication services

Right now I'm getting error:
Error: You have already registered authentication on this app. You only need to do it once.

us it possible somehow register more then one? like so:
  .configure(auth(app.get('auth')))
  .configure(auth(app.get('authCustomers')))
  .configure(auth(app.get('authAdmins')))
...

and each will have separate endpoint and service.

That is currently not possible. To me this looks like just different types of users which can be much easier handled by adding a type property to them.
If things are in different services I usually recommend to create an entity service for authentication that then links to the appropriate other service (users, machines, customers) through fields like userId, machineId, customerId.

different types make sense, but what if those users in different tables in db. anyway I think entity service should solve this problem, thanks.


Skip MOPED Testing

Pull Request Description
What issue does this change request address?
#311
What are the significant changes in functionality due to this change request?
This PR will suspend the current testing of MOPED due to challenging library changes causing ipopt to crash with some kind of segmentation fault.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass.
[x] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large tes.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
[x] 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

Hopefully this is a temporary measure that we can find time to address. Thanks for making the changes.


all auto generated resolvers disappeared

I've been trying out storIO for 2 days and i've been having great results, untill today. I started Android Studio and all auto generated resolver classes are gone and i cant even build my project.
Error:(9, 53) error: cannot find symbol class CommentStorIOContentResolverDeleteResolver
Error:(10, 53) error: cannot find symbol class CommentStorIOContentResolverGetResolver
Error:(11, 53) error: cannot find symbol class CommentStorIOContentResolverPutResolver
These used to be auto generated classes, that are no longer appearing. I tried Clean Project, Rebuild Project, restarted my pc, android studio... I have no idea whats the problem.

Looks like something with annotation processors went wrong, still dont know what it was, but its working now.

I'm having similar issue now. After migration to AndroidX and update to storio3  all auto generated storio resolvers and mappings are gone. I have no idea whats going on.


inference demo bug

I find a bug when i try to inference a demo.
(mhformer) [root@*** ~/MHFormer]# python demo/vis.py --video demo.mp4

Generating 2D pose...
  0%|                                                                                | 0/791 [00:00<?, ?it/s]No person detected!
  0%|                                                                                | 0/791 [00:01<?, ?it/s]
Traceback (most recent call last):
  File "demo/vis.py", line 276, in <module>
    get_pose2D(video_path, output_dir)
  File "demo/vis.py", line 90, in get_pose2D
    keypoints, scores = hrnet_pose(video_path, det_dim=416, num_peroson=1, gen_output=True)
  File "/root/MHFormer/demo/lib/hrnet/gen_kpts.py", line 113, in gen_video_kpts
    bboxs = bboxs_pre
UnboundLocalError: local variable 'bboxs_pre' referenced before assignmen

It seems that when there's no person in a frame, it will raise error.

Oh, I find the same issue in #16


purple fragments are not removed at enter

The purple fragments are not removed when I press enter.
To reproduce:
do something like
echo Lorem ipsum dolor sit amet.

Then enter.
Then start typing this again, but press enter at
echo Lorem ipsum

The purple fragments of the whole thing are still there.

Fixed in commit 0224b34691f4e9a16aa8c16527eef775c92bad12


[Story] Machine Select

As an instructor, I want to see a list of all of my machines, so I can select one to open for a demo.

Acceptance Test:
(1) Start the application.
(2) Check that a list of machines appears.
(3) Click on a machine in the list.
(4) Verify that you are taken to a page which has the same title as the chosen machine.


Safest settings in miscellaneous Apps

Don't know if you like this kind of explanations, some are already the main document.
Perhaps a small brief summary, something like
Firefox
OFF - Download abcde
ON - Stop this
Here is one I was not aware of:
http://www.makeuseof.com/tag/google-is-secretly-recording-you-heres-how-to-make-them-stop/

Sorry, what do you mean by the Firefox idea? The linked article has nothing really to do with OS X.

How to set the options in apps, here an example with FF, to be the most secure.

Feel free to PR me what you have in mind and I'll take a look. More details about browsers is welcome.


what do i download?

im on mac and i downloaded python but then the install requests dosent work so what do i do?

what doesn't work? make sure you're running the following line: pip install requests


Bump up vstest task version. after kavipriya's changes

Bump up vstest version after kavipriya's changes

Going ahead with checkin


Issue1414: wrong behavior of json() method with nested models containing custom root

Change Summary

1414
https://github.com/samuelcolvin/pydantic/issues/1414
Fix proposal for the issue 1414, wrong behavior of json method when there are nested models with custom root.
Once the dict is generated, it is parsed and each time an item has the root key, its associated value is attached to the parent key
(Maybe this can be done in a more pythonic way, but with 15 years of C++ I still have bad habits)

Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

I think the point here is that this should effect dict() as well as json(), in this regard I don't see that there's anything special about json().

replaced by #1607


Try using numdifftools

Just throwing this out there...

What would need to be done to get this merged in?

@Korijn It may seem like most of the work has already been done, but realistically I feel like it could take an amount of work comparable to a GSOC project to deal with corner cases for backward compatibility, to document the interface, and to make sure it integrates well with at least the existing scipy.stats and scipy.optimize packages.
In the early days of scipy when different groups were scrambling to aggregate their scientific python projects to publish as 'scipy', I could easily imagine numdifftools having been directly added without much modification or discussion as something like scipy.numdifftools or scipy.numdiff.  Personally I'd still be OK with this, but my feeling is that the project has shifted a bit on the inclusionism/deletionism axis https://en.wikipedia.org/wiki/Deletionism_and_inclusionism_in_Wikipedia.

To be more concrete, a lot of thought and discussion went into this GSoC proposal to add a scipy.diff based on numdifftools (with significant contributions from @pbrod as the numdifftools author): https://github.com/scipy/scipy/wiki/Proposal:-add-finite-difference-numerical-derivatives-as-scipy.diff
Unfortunately the project didn't materialize because the student had to pull out of the GSoC selection process due to university requirements on completion date of an internship at a company.
@argriffing would you mind if we closed this PR? At this point I don't think it gets us much closer to a scipy.diff.


jobs are not execution in odd number minute and hours

HI,
I have added node-cron in my project and Job scheduled
1 to 59 minutes  in every 2 minute(1-59/2 * * * * *),
so job should execute minutes 1,3,4,5..59 (odd number). but job execution only working in even number(minute).
issue happening in case of hours also. (not executing at time of )
pleas help me if i made any mistake here:
eg:
let cron_job = cron.schedule("1-59/2 * * * *", () => {
console.log(moment().toString());
}
)
output
hu Dec 05 2019 19:02:00 GMT+0530
Thu Dec 05 2019 19:04:00 GMT+0530
Thu Dec 05 2019 19:06:00 GMT+0530
Thu Dec 05 2019 19:08:00 GMT+0530
thanks....

Same for me!

Guessing no solution was found for this?


Reorder -maxdepth and -mindepth position

Just address the following find warning, as running sd --help
produced the following output with warnings:
❯ sd --help
sd commands
find: warning: you have specified the global option -maxdepth after the argument -not, but global options are not positional, i.e., -maxdepth affects tests specified before it as well as those specified after it.  Please specify global options before other arguments.
find: warning: you have specified the global option -mindepth after the argument -not, but global options are not positional, i.e., -mindepth affects tests specified before it as well as those specified after it.  Please specify global options before other arguments.
test ...   -- test commands

Thanks! BSD sed has no such complaint.


Plugin request games.dailymotion.com

Please add support for: http://games.dailymotion.com/

Looks like this needs to be manually closed after #684 was merged.


Android - Distance unit - Tapping on Kilometers unit doesn't select it right away

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.75-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4573054
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Open New Expensify app
Create a workspace
Enable distance rate
Open distance rate settings > Settings > Unit
Tap on Kilometers

Expected Result:
The kilometers unit gets selected
Actual Result:
The kilometers unit does not get selected, user has to tap on it multiple of times to select it
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/b570a6ed-3bd7-4d53-90e3-305cd1abea9c

View all open jobs on GitHub

We think this issue might be related to the #collect project.

Android <> iOS bug swap.

Created 3 Workspaces, all allowed me to select Kilometers easily on v75-1 (Pixel 7).
I also notice on occasion, the Android app doesn't select things but it's always temporary. Closing.


edited non-standard methods using std

I saw you used the STD thread, that library is available since C++11 (std::thread), so i suppose you had edited the Makefile, adding the C++11 flag, before you compiled the source code, hadn't you?
At the moment, this project is developed with C++98 standard.
The types and methods i used, are in Windows library, and it's in accordance with the aim of this project, that is to create a framework for Windows; moreover some methods in Windows.h needs of some particular type (obviously in Windows.h) to work properly, so it means, if you change one of these with the equivalent in the STD library you need to test a lot of things.

I saw you used the STD thread, that library is available since C++11 (std::thread), so I suppose you had edited the Makefile, adding the C++11 flag, before you compiled the source code, hadn't you?
At the moment, this project is developed with C++98 standard.
The types and methods I used, are in Windows library, and it's in accordance with the aim of this project, that is to create a framework for Windows; moreover some methods in Windows.h needs of some particular type (obviously in Windows.h) to work properly, so it means, if you change one of these with the equivalent in the STD library you need to test a lot of things.

I saw you used the STD thread, that library is available since C++11 (std::thread), so I suppose you had edited the Makefile, adding the C++11 flag, before you compiled the source code, hadn't you?
At the moment, this project is developed with C++98 standard.
The types and methods I used, are in Windows library, and it's in accordance with the aim of this project, that is to create a framework for Windows; moreover some methods in Windows.h need some particular type (obviously in Windows.h) to work properly, so it means, if you change one of these with the equivalent in the STD library you need to test a lot of things.

Let's continue on Telegram. Pull request is closed for now


[donot-merge][full-ci]Check for expected to failure

This PR is just check for the search request adjustment made in https://github.com/owncloud/core/pull/40159

All checks have been done with the core changes so closing it.


Build fails when using plugin, but it passes when javafx dependencies added manually

I have encountered following problem with build using javafx-gradle-plugin:
$ ./gradlew build

> Configure project :
Found module name 'demo.main'

> Task :compileTestJava FAILED
error: the unnamed module reads package com.github.jknack.handlebars.helper from both handlebars.helpers and handlebars
error: the unnamed module reads package javax.activation from both org.apache.sling.javax.activation and activation
error: the unnamed module reads package org.codehaus.groovy.runtime from both org.codehaus.groovy.xml and org.codehaus.groovy
error: the unnamed module reads package groovy.xml from both org.codehaus.groovy.xml and org.codehaus.groovy
error: the unnamed module reads package groovy.util from both org.codehaus.groovy.xml and org.codehaus.groovy
error: module javafx.baseEmpty reads package com.github.jknack.handlebars.helper from both handlebars.helpers and handlebars
error: module javafx.baseEmpty reads package javax.activation from both org.apache.sling.javax.activation and activation
error: module javafx.baseEmpty reads package org.codehaus.groovy.runtime from both org.codehaus.groovy.xml and org.codehaus.groovy
error: module javafx.baseEmpty reads package groovy.xml from both org.codehaus.groovy.xml and org.codehaus.groovy
error: module javafx.baseEmpty reads package groovy.util from both org.codehaus.groovy.xml and org.codehaus.groovy
error: module wiremock reads package com.github.jknack.handlebars.helper from both handlebars.helpers and handlebars
error: module wiremock reads package javax.activation from both org.apache.sling.javax.activation and activation
error: module wiremock reads package org.codehaus.groovy.runtime from both org.codehaus.groovy.xml and org.codehaus.groovy
error: module wiremock reads package groovy.xml from both org.codehaus.groovy.xml and org.codehaus.groovy
error: module wiremock reads package groovy.util from both org.codehaus.groovy.xml and org.codehaus.groovy
// (...) a lot more errors here...
error: module org.xmlunit reads package groovy.util from both org.codehaus.groovy.xml and org.codehaus.groovy
100 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileTestJava'.
> 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. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 0s
3 actionable tasks: 3 executed

My application fetches data from some external services which are mocked using wiremock within tests. Gradle configuration here. Build passes once either I remove javafx plugin or wiremock dependency.
I have tested various build configuration and here are the results:

Build configuration
Configuration file
Result

Gradle with plugin
build.gradle
Build fails due to error above

Gradle without plugin (dependencies added manually)
build.gradle
Build passes

Maven with plugin
pom.xml
Build passes

Following example project is affected by the issue: https://github.com/kr5ture/javafx-gradle-plugin-issue/tree/gradle-with-plugin . I created three branches with build configurations by the table above.

Same experience:

Using org.openjfx.javafxplugin as documented on main page works but resulting JAR does not include any openjfx packages
Without plugin, just adding openjfx as dependencies works AND resulting jar will include openjfx packages

Environment: Windows 10, Eclipse, Gradle (Buildship plugin)

@kr5ture Actually your issue has to do with the modular plugin that the JavaFX gradle plugin uses. It has nothing to do with JavaFX either. In fact, if you add the application plugin, the run task works fine with your use case.
I'd suggest you file an issue here, with a use case similar to the ones you have at https://github.com/kr5ture/javafx-gradle-plugin-issue/, but removing the JavaFX part, and using instead:
plugins {
	id 'org.javamodularity.moduleplugin' version '1.5.0'
}

@folterj Your issue has nothing to do with the one at hand. Feel free to file a new issue with enough details to reproduce it, but check out first the documentation on how to distribute your projects at https://openjfx.io/openjfx-docs/#modular, Gradle sections.


Parsing metadata with multiple namespaces is not possible

Hi!
I found one interesting issue while trying out the library, for simple cases it's very convenient and works as expected. I've noticed however that as soon as you introduce more than one namespace into the metadata it breaks the parser.
I've created minimal example that demonstrates the issue:
metadata.xml
<?xml version="1.0" encoding="utf-8"?>
<edmx:Edmx Version="4.0" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:DataServices>
    <Schema Namespace="Namespace.Api.Models"
      xmlns="http://docs.oasis-open.org/odata/ns/edm">
      <EntityType Name="Order">
        <Key>
          <PropertyRef Name="id" />
        </Key>
        <Property Name="id" Type="Edm.Guid" Nullable="false" />
        <Property Name="orderType" Type="Namespace.Api.Enums.OrderType" Nullable="false" /> <!-- parser won't use that type and throw an error -->
      </EntityType>
    </Schema>
    <Schema Namespace="Namespace.Api.Enums" xmlns="http://docs.oasis-open.org/odata/ns/edm">
      <EnumType Name="OrderType">
        <Member Name="Example" Value="0" />
      </EnumType>
    </Schema>
  </edmx:DataServices>
</edmx:Edmx>

My odata2ts.config file:
const config: ConfigFileOptions = {
  mode: Modes.qobjects,
  emitMode: EmitModes.ts,
  prettier: true,
  skipEditableModels: true,
  services: {
    metadata: {
      source: 'metadata.xml',
      output: 'odata-client'
    }
  }
}

I've taken a look at the source and it looks like at the moment the parsing is done on first encountered namespace and that's it. Do you plan to take cases like that into account? From what I've checked this is valid metadata xml and I'd assume the intention is to parse it as such.
Kind regards!
You can also take a look at this codesandbox

Hi @lpmusicon,
this is an absolutely valid example in regards to the OData spec.
And yes, I've got this issue on the roadmap but without any priority.
I'll try to take a look into it and report back.

Hi @texttechne! Thank you, that's very quick turnaround. What we have implemented on our side for the time being to circumvent the issue is literally the same solution you have provided, just done at metadata generation level.
So to answer in short, yep that'd be sufficient for us :)

Hi @lpmusicon,
should be fixed with version 0.25.0 of @odata2ts/odata2ts.
To be on the safe side: It's only the solution approach which merges together the different namespaces.
Please try it out and close the issue if it has been fixed.

Hey! It does work perfectly, thank you so much!


feat(core): Add local-prefixes flag to golint-ci

Now that we've cleaned up our imports to be nicely grouped, with local imports last, add the same flag to golint-ci so that future PRs respect this style.

I expect the CI to fail until this is rebased onto #120.

(Still trying to figure out why the CI is passing here...)


debian package: use systemd if available

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
NONE
What this PR does / why we need it:
#484
* switch to systemd if available in debian package
* hardened systemd settings

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

82607a8 debian package: use systemd if available

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leodido
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: a85e3087ea2576ff4dea082e3f80441b48110413

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @juju4 - Thanks for your PR :) We really need this!
Please send your PR against the dev branch. master is unused now and we have to work on making it the new default, but dev is the default now.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@juju4: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

e00181d Merge pull request #174 from draios/dev
d1b6b2b Merge pull request #229 from draios/dev
b0ae29c Merge branch 'dev'
809d20c Merge pull request #246 from draios/dev
74556e5 Merge branch 'dev'
e8aee19 Merge remote-tracking branch 'origin/dev', 0.8.1
3ee7663 Merge branch 'dev'
94df00e Merge branch 'dev'
2a0911d Merge branch 'dev'
b496116 Don't make driver compilation fail when kernel is compiled with CONFIG_ORC_UNWINDER or CONFIG_STACK_VALIDATION. (#362)
6acb13e Merge branch 'dev'
4707103 Merge remote-tracking branch 'origin/dev'
5e38f13 Merge remote-tracking branch 'origin/dev'
ff299c1 Merge remote-tracking branch 'origin/dev'
bd7a973 Merge branch 'dev'
ddf55d3 Merge remote-tracking branch 'origin/dev'
62c1a04 Merge remote-tracking branch 'origin/dev'
44e88f2 Merge remote-tracking branch 'origin/dev'
e546555 fix k8s install issue (#506)
f4b0b3c falco.yaml: change default program_output action (#507)
36a095c Merge remote-tracking branch 'origin/dev'
db41945 Merge remote-tracking branch 'origin/dev'
807c00b Merge remote-tracking branch 'origin/dev'
ff376d3 Merge remote-tracking branch 'origin/dev'
194a017 Merge remote-tracking branch 'origin/dev'
75b816d Merge remote-tracking branch 'origin/dev'
670736d Merge remote-tracking branch 'origin/dev'
82607a8 debian package: use systemd if available
cf7a549 Merge branch 'dev' into devel-systemd

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

e00181d Merge pull request #174 from draios/dev
d1b6b2b Merge pull request #229 from draios/dev
b0ae29c Merge branch 'dev'
809d20c Merge pull request #246 from draios/dev
74556e5 Merge branch 'dev'
e8aee19 Merge remote-tracking branch 'origin/dev', 0.8.1
3ee7663 Merge branch 'dev'
94df00e Merge branch 'dev'
2a0911d Merge branch 'dev'
b496116 Don't make driver compilation fail when kernel is compiled with CONFIG_ORC_UNWINDER or CONFIG_STACK_VALIDATION. (#362)
6acb13e Merge branch 'dev'
4707103 Merge remote-tracking branch 'origin/dev'
5e38f13 Merge remote-tracking branch 'origin/dev'
ff299c1 Merge remote-tracking branch 'origin/dev'
bd7a973 Merge branch 'dev'
ddf55d3 Merge remote-tracking branch 'origin/dev'
62c1a04 Merge remote-tracking branch 'origin/dev'
44e88f2 Merge remote-tracking branch 'origin/dev'
e546555 fix k8s install issue (#506)
f4b0b3c falco.yaml: change default program_output action (#507)
36a095c Merge remote-tracking branch 'origin/dev'
db41945 Merge remote-tracking branch 'origin/dev'
807c00b Merge remote-tracking branch 'origin/dev'
ff376d3 Merge remote-tracking branch 'origin/dev'
194a017 Merge remote-tracking branch 'origin/dev'
75b816d Merge remote-tracking branch 'origin/dev'
670736d Merge remote-tracking branch 'origin/dev'
82607a8 debian package: use systemd if available
cf7a549 Merge branch 'dev' into devel-systemd
6621bdf Merge branch 'devel-systemd' of github.com:juju4/falco into devel-systemd

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

e00181d Merge pull request #174 from draios/dev
d1b6b2b Merge pull request #229 from draios/dev
b0ae29c Merge branch 'dev'
809d20c Merge pull request #246 from draios/dev
74556e5 Merge branch 'dev'
e8aee19 Merge remote-tracking branch 'origin/dev', 0.8.1
3ee7663 Merge branch 'dev'
94df00e Merge branch 'dev'
2a0911d Merge branch 'dev'
b496116 Don't make driver compilation fail when kernel is compiled with CONFIG_ORC_UNWINDER or CONFIG_STACK_VALIDATION. (#362)
6acb13e Merge branch 'dev'
4707103 Merge remote-tracking branch 'origin/dev'
5e38f13 Merge remote-tracking branch 'origin/dev'
ff299c1 Merge remote-tracking branch 'origin/dev'
bd7a973 Merge branch 'dev'
ddf55d3 Merge remote-tracking branch 'origin/dev'
62c1a04 Merge remote-tracking branch 'origin/dev'
44e88f2 Merge remote-tracking branch 'origin/dev'
e546555 fix k8s install issue (#506)
f4b0b3c falco.yaml: change default program_output action (#507)
36a095c Merge remote-tracking branch 'origin/dev'
db41945 Merge remote-tracking branch 'origin/dev'
807c00b Merge remote-tracking branch 'origin/dev'
ff376d3 Merge remote-tracking branch 'origin/dev'
194a017 Merge remote-tracking branch 'origin/dev'
75b816d Merge remote-tracking branch 'origin/dev'
670736d Merge remote-tracking branch 'origin/dev'
82607a8 debian package: use systemd if available
cf7a549 Merge branch 'dev' into devel-systemd
6621bdf Merge branch 'devel-systemd' of github.com:juju4/falco into devel-systemd
1b5ad27 debian package: use systemd if available
5a61031 Merge branch 'devel-systemd' of github.com:juju4/falco into devel-systemd

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I believe branch+rebase and signoff should be fine now. hopefully not too messed-up.

Closing and reopening to let poiana handle this

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@juju4: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

f578849 Merge branch 'master' into devel-systemd

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/milestone 0.25.0

Hey @juju4
Are you still working on this PR? Any updates?

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

e00181d Merge pull request #174 from draios/dev
d1b6b2b Merge pull request #229 from draios/dev
b0ae29c Merge branch 'dev'
809d20c Merge pull request #246 from draios/dev
74556e5 Merge branch 'dev'
e8aee19 Merge remote-tracking branch 'origin/dev', 0.8.1
3ee7663 Merge branch 'dev'
94df00e Merge branch 'dev'
2a0911d Merge branch 'dev'
b496116 Don't make driver compilation fail when kernel is compiled with CONFIG_ORC_UNWINDER or CONFIG_STACK_VALIDATION. (#362)
6acb13e Merge branch 'dev'
4707103 Merge remote-tracking branch 'origin/dev'
5e38f13 Merge remote-tracking branch 'origin/dev'
ff299c1 Merge remote-tracking branch 'origin/dev'
bd7a973 Merge branch 'dev'
ddf55d3 Merge remote-tracking branch 'origin/dev'
62c1a04 Merge remote-tracking branch 'origin/dev'
44e88f2 Merge remote-tracking branch 'origin/dev'
e546555 fix k8s install issue (#506)
f4b0b3c falco.yaml: change default program_output action (#507)
36a095c Merge remote-tracking branch 'origin/dev'
db41945 Merge remote-tracking branch 'origin/dev'
807c00b Merge remote-tracking branch 'origin/dev'
ff376d3 Merge remote-tracking branch 'origin/dev'
194a017 Merge remote-tracking branch 'origin/dev'
75b816d Merge remote-tracking branch 'origin/dev'
670736d Merge remote-tracking branch 'origin/dev'
82607a8 debian package: use systemd if available
cf7a549 Merge branch 'dev' into devel-systemd
6621bdf Merge branch 'devel-systemd' of github.com:juju4/falco into devel-systemd
1b5ad27 debian package: use systemd if available
5a61031 Merge branch 'devel-systemd' of github.com:juju4/falco into devel-systemd
6083883 Merge remote-tracking branch 'upstream/master'
f578849 Merge branch 'master' into devel-systemd
5c0e854 Merge remote-tracking branch 'upstream/master'
947c2fe Merge branch 'master' into devel-systemd
5ecce79 Merge branch 'devel-systemd' of github.com:juju4/falco into devel-systemd

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

As described, send against dev

don't see any dev branch currently when editing PR

I'm pretty sure I did dco but https://github.com/falcosecurity/falco/blob/master/CONTRIBUTING.md is dead
seeing the long list of signoff needed, I think I need some rebase...

PS
The contribution guideline has been moved here :point_down:
https://github.com/falcosecurity/.github/blob/master/CONTRIBUTING.md

Closing this since https://github.com/falcosecurity/falco/pull/1448 has been merged.


Fix/rearrange gateway check

Instead of checking for production, and defaulting to development; for development and default to production.
@dawilster, reasoning for the change is in the first commit.

Cool makes sense


Add images locally

Right now, all of the images for the profile pictures comes from external sources. While this helps us out with hosting, it adds a cost for those websites and it isn't long-lived on our end.
I propose that we move all of these images locally. I don't know if there is currently an image optimization setup for uploading and linking local images. @flickz Do you know if there is one?

It should be easy enough to grep for all image links and then curl them into a local folder, as a way of getting this process started.

We currently use gatsby, it has support for image optimization.
https://www.gatsbyjs.com/docs/working-with-images/

Does the image link field currently support local addresses?


bug: command --locked false to unlock the server doesn't work, however --locked true to lock the server does work.

What happened?
The --locked false and -l false commands do not work. According to the Docs, a boolean can lock or unlock the server from being updated.
However, only --locked true and -l true seem to work. This is seen in the video below.
How can we reproduce it?

Deploy server.
Get server ID.
Run command metal device update --id <server-id> --locked true to lock the server.
Confirm that it is locked on console.equinix.com.

Run command metal device update --id <server-id> --locked false to unlock the server.
Confirm that it is unlocked on console.equinix.com. However, it is not.

[!NOTE]
CLI ==version== (metal --version): metal version 0.24.0

[!IMPORTANT]
https://github.com/user-attachments/assets/7b8e64bd-e9cd-459c-805e-81bb0b040f63

Update: logs confirm that the --locked false command is not being sent at all.

https://github.com/equinix/metal-cli/blob/main/internal/devices/update.go#L82-L85 will only apply locked changes when the variable is set to true.
The code should look at wether or not the parameter was sent and set locked based on the specified setting. false should not be the default.
I don't see other examples in this project of an optional boolean variable whose value must be explicitly false or true when specified.


Enhance CORS functionality/docs

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Enhance CORS docs/functionality
Right now nothing is said about CORS in the docs (apart from a single mention), and the only way I've managed to find is by adding a full specification as shown below. If there is a better way, it should be documented more (especially as it's 1 button in the AWS GUI), and if there isn't, that might be something to consider adding.
apigateway.RouteArgs(
            path="/api/v1",
            method=apigateway.Method.OPTIONS,
            data={
                "x-amazon-apigateway-integration": {
                    "contentHandling": "CONVERT_TO_TEXT",
                    "httpMethod": "OPTIONS",
                    "type": "mock",
                    "passthroughBehavior": "when_no_match",
                    "requestTemplates": {
                        "application/json": '{"statusCode": 200}'
                    },
                    "responses": {
                        "default": {
                            "statusCode": "200",
                            "responseParameters": {
                                "method.response.header.Access-Control-Allow-Origin": "'*'",
                                "method.response.header.Access-Control-Allow-Headers": "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token'",
                                "method.response.header.Access-Control-Allow-Methods": "'OPTIONS,GET,PUT,POST,DELETE'",
                            },
                            "responseTemplates": {
                            }
                        }
                    }
                },
                "responses": {
                    "200": {
                        "description": "Default response for CORS method",
                        "headers": {
                            "Access-Control-Allow-Origin": {
                                "type": "string"
                            },
                            "Access-Control-Allow-Headers": {
                                "type": "string"
                            },
                            "Access-Control-Allow-Methods": {
                                "type": "string"
                            }
                        }
                    }
                }
            }
        ),

Affected area/feature

If there is a better way, it would be the docs, if there isn't it would be I think the terraform bridge? Since it'd be an added option probably which would inject these headers.

Hey @jellejurre, sorry you're running into this.
You're right that this is currently the way to enable CORS, but I agree that we should simplify the setup because CORS is a rather common requirement.
I'll track this as an enhancement request.


is there  a way to precaching the files after install

Library Affected:
workbox-precaching.
Browser & Platform:
all browsers
Issue or Feature Request Description:
i want to use workbox to speed up the application with prercaching; but my project is a Micro Front-end, the sub project are independent, that means I can’t get the manifest json config when i build the project, so in service worker's install period, the precache list is not reachable;  the fileLists come from the perrmission API after user login,  it there a way to solve my situation?

You don't like the option of run-time caching in this case? it seems to me that those assets getting back from permission API are not precache assets anymore. Is there a specific reason why runtime wouldn't be a solution for you?

You don't like the option of run-time caching in this case? it seems to me that those assets getting back from permission API are not precache assets anymore. Is there a specific reason why runtime wouldn't be a solution for you?

runtime cache is like when you went into a shop.. the sales ask what size shoes you wear, and the next time you got in she don't sak；but precache， it a feel like you got into the shop, the sales is already prepare a shoes for you;
am i right to understanding the defference between precache  and runcaching；
i just want give the user what they want before he ask, because i already know what he want after he login

You have a few options.
One would be to call navigator.serviceWorker.register() only after the user has logged in. If you delay registration until after whatever conditions are met, then the install event will also be delayed, and presumably it will succeed if it takes place after login.
Another option would be to register the service worker immediately, but ensure that the install event fails when the user isn't logged in. This might be because you precache a URL that will, e.g., return an HTTP 403 error prior to login. If the install event fails, then it will be retried the next time there's a navigation to a new URL under the service worker's scope, and eventually  the  install event will succeed (assuming the user logs in).


Add ability to like/comment on accounts I'm Following

It would be great if we could like/comment on accounts that we're following, not just accounts who follow us.

@datslo The script is designed to like/comment on an account you specify. It doesn't check if the account is your follower, or a one you're following.


[SourceControl] When file was added and is moved, remove old file from index

As requested in #1812

I tested the PR and while it improves the behavior, the original issue is still not fully fixed.
I found two more issues while testing, and described all of them in a comment to the original issue. If desired, I can split them to separate issues.

WIP

via #3099


Broken tickbase exploit while removing DT

tickbase makes you press the teleport button twice before you fully teleported
Dm me on discord ig I can't paste my cfg here LolTrolledlmao#3217

This only happens when you disable DT

buy rijin easy fix

turn off smooth teleport or auto-retain (not sure why you have it on considering you aren't using doubletap)


msg.topic is always 0

Describe the bug
when i use msg.topic in universal mode to set the group id, the group id is always set to 0
Expected behavior
msg.topic should set the group id
Additional context
In my opinion, the Problem is in this line:
var tempGroupID = (msg.topic != null && isNaN(msg.topic) == false && msg.topic.length > 0) ? parseInt(msg.topic) : config.groupid;
msg.topic is an integer and has no length. when i use it like that:
var tempGroupID = (msg.topic != null && isNaN(msg.topic) == false ) ? parseInt(msg.topic) : config.groupid;
it works for me.

Fixed with v4


Cannot import name 'CheckboxLeftWidget' from 'kivymd.uix.list'

I have an error during debuging kivymd app on android
I python  :  ImportError: cannot import name 'CheckboxLeftWidget' from 'kivymd.uix.list' (/data/user/0/org.test.ospapp/files/app/_python_bundle/site-packages/kivymd/uix/list.pyc)
I python  : Python for android ended.
--buildozer.spec--
(list) Application requirements
comma separated e.g. requirements = sqlite3,kivy
requirements = python3,datetime,image,pillow,pyrebase,kivy==2.0.0, kivymd==0.104.1, sdl2_ttf == 2.0.15

@JanickiJ We do not support the KivyMD library version, except for the master version of the library.

@JanickiJ We do not support the KivyMD library version, except for the master version of the library.
So is there any sollution to this problem?

@JanickiJ https://github.com/kivymd/KivyMD/blob/master/demos/kitchen_sink/buildozer.spec#L29

@HeaTTheatR
I changed requirements as you said and restarted buildozer
requirements = python3,kivy==2.0.0,https://github.com/kivymd/KivyMD/archive/master.zip,pygments,sdl2_ttf==2.0.15,pillow
But because of it new error occured
ModuleNotFoundError: No module named 'chardet'
I added chardet to requirements, restarted buildozer and again the same situation, but now with idna
ModuleNotFoundError: No module named 'inda'
I added ida to requirements, but situation reapeated a few times
Now my requirements look like this
requirements = python3,kivy==2.0.0,https://github.com/kivymd/KivyMD/archive/master.zip,pygments,sdl2_ttf==2.0.15,pillow,requests,chardet,idna,pyasn1,urllib3,certifi,pyasn1_modules,pyparsing,httplib2,oauth2client
But new errors are still occuring


Use a standard directory for logs

This is a slightly awkard import. Why should this use the same ARTIFACTS_DIR as the chain tests?
Originally posted by @andrewgordstewart in https://github.com/statechannels/statechannels/pull/3641#discussion_r670873311

This would be a good candidate to look at during the rest cycle.