Demo fails

I've followed the instructions to run the demo. After installing, I run "npm start" which seems to succeed, but then fails. Full output is below.
flutter-webrtc-server $ npm install
npm WARN deprecated<EMAIL_ADDRESS>🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

><EMAIL_ADDRESS>install /Users/Sites/webrtc/flutter-webrtc-server/node_modules/fsevents
> node install

[fsevents] Success: "/Users/Sites/webrtc/flutter-webrtc-server/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64/fse.node" is installed via remote

><EMAIL_ADDRESS>postinstall /Users/Sites/webrtc/flutter-webrtc-server/node_modules/jss
> node -e "console.log('\u001b[35m\u001b[1mLove JSS? You can now support us on open collective:\u001b[22m\u001b[39m\n > \u001b[34mhttps://opencollective.com/jss/donate\u001b[0m')"

Love JSS? You can now support us on open collective:
 > https://opencollective.com/jss/donate
npm notice created a lockfile as package-lock.json. You should commit this file.
added 1137 packages in 87.457s
flutter-webrtc-server $ npm start

><EMAIL_ADDRESS>start /Users/Sites/webrtc/flutter-webrtc-server
> npm-run-all --parallel run-server run-webpack-dev-server

><EMAIL_ADDRESS>run-server /Users/Sites/webrtc/flutter-webrtc-server
> node server/index.js

><EMAIL_ADDRESS>run-webpack-dev-server /Users/Sites/webrtc/flutter-webrtc-server
> webpack-dev-server --mode development --https --cert ./certs/cert.pem --key ./certs/key.pem --hot --inline --progress --colors --watch --compress --content-base ./dist  --port 8086 --host <IP_ADDRESS>

Start WS Server: bind => ws://<IP_ADDRESS>:4442
Start WSS Server: bind => wss://<IP_ADDRESS>:4443
 10% building modules 1/1 modules 0 activeℹ ｢wds｣: Project is running at https://<IP_ADDRESS>:8086/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /Users/Sites/webrtc/flutter-webrtc-server/dist
✖ ｢wdm｣: Hash: 20c9379ed53a3fe1c1ae
Version: webpack 4.17.1
Time: 3838ms
Built at: 22/08/2018 18:02:05
 1 asset
Entrypoint main = main.20c9379e.bundle.js
[./node_modules/loglevel/lib/loglevel.js] 7.68 KiB {main} [built]
[./node_modules/react-dom/index.js] 1.33 KiB {main} [built]
[./node_modules/react/index.js] 190 bytes {main} [built]
[./node_modules/strip-ansi/index.js] 161 bytes {main} [built]
[./node_modules/url/url.js] 22.8 KiB {main} [built]
[./node_modules/webpack-dev-server/client/index.js?https://<IP_ADDRESS>:8086] (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 7.78 KiB {main} [built]
[./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.58 KiB {main} [built]
[./node_modules/webpack/hot sync ^\.\/log$] (webpack)/hot sync nonrecursive ^\.\/log$ 170 bytes {main} [built]
[0] multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js 52 bytes {main} [built]
[./node_modules/webpack/hot/dev-server.js] (webpack)/hot/dev-server.js 1.61 KiB {main} [built]
[./node_modules/webpack/hot/emitter.js] (webpack)/hot/emitter.js 75 bytes {main} [built]
[./node_modules/webpack/hot/log-apply-result.js] (webpack)/hot/log-apply-result.js 1.27 KiB {main} [built]
[./node_modules/webpack/hot/log.js] (webpack)/hot/log.js 1.11 KiB {main} [built]
[./src/App.js] 13.1 KiB {main} [built]
[./src/index.js] 466 bytes {main} [built]
    + 328 hidden modules

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@babel/runtime/helpers/builtin/interopRequireDefault' in '/Users/Sites/webrtc/flutter-webrtc-server/node_modules/@material-ui/icons'
<EMAIL_ADDRESS>3:29-92
 @ ./src/App.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@babel/runtime/helpers/builtin/interopRequireDefault' in '/Users/Sites/webrtc/flutter-webrtc-server/node_modules/@material-ui/icons'
<EMAIL_ADDRESS>3:29-92
 @ ./src/App.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@babel/runtime/helpers/builtin/interopRequireDefault' in '/Users/Sites/webrtc/flutter-webrtc-server/node_modules/@material-ui/icons'
<EMAIL_ADDRESS>3:29-92
 @ ./src/App.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@babel/runtime/helpers/builtin/interopRequireDefault' in '/Users/Sites/webrtc/flutter-webrtc-server/node_modules/@material-ui/icons'
<EMAIL_ADDRESS>3:29-92
 @ ./src/App.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@babel/runtime/helpers/builtin/interopRequireDefault' in '/Users/Sites/webrtc/flutter-webrtc-server/node_modules/@material-ui/icons'
<EMAIL_ADDRESS>3:29-92
 @ ./src/App.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@babel/runtime/helpers/builtin/interopRequireDefault' in '/Users/Sites/webrtc/flutter-webrtc-server/node_modules/@material-ui/icons'
<EMAIL_ADDRESS>3:29-92
 @ ./src/App.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@babel/runtime/helpers/builtin/interopRequireDefault' in '/Users/Sites/webrtc/flutter-webrtc-server/node_modules/@material-ui/icons'
<EMAIL_ADDRESS>3:29-92
 @ ./src/App.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@babel/runtime/helpers/builtin/interopRequireDefault' in '/Users/Sites/webrtc/flutter-webrtc-server/node_modules/@material-ui/icons/utils'
<EMAIL_ADDRESS>3:29-92
<EMAIL_ADDRESS> @ ./src/App.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?https://<IP_ADDRESS>:8086 (webpack)/hot/dev-server.js ./src/index.js
Child html-webpack-plugin for "index.html":
     1 asset
    Entrypoint undefined = ./index.html
    [./node_modules/html-webpack-plugin/lib/loader.js!./src/index.html] 370 bytes {0} [built]
    [./node_modules/lodash/lodash.js] 527 KiB {0} [built]
    [./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 489 bytes {0} [built]
    [./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
ℹ ｢wdm｣: Failed to compile.

You can try  npm i babel-runtime,  May lack an npm dependency.

That solved it, although I had to delete node_modules and package-lock file, install babel-runtime, then install as per usual.


Maintain cursor position when deleting text

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Mac OS X

Shell

[x] zsh

Problem / Steps to reproduce
It would be really nice if when you delete a character, fzf would keep the cursor on the same line (as it will always still be matched).
This would allow better use of fzf for browsing things like git history, before filtering.
For example:

I'm looking for a commit, I know it was near the 1.0.0 commit.
I open my interactive git log to search for it.
I type 1.0.0 to find the 1.0.0 commit.
I press Backspace to delete the 1.0.0, so I can see the surrounding commits.
Unfortunately fzf preserves the line I was on (i.e. 4th line down) rather than the text I was looking at (i.e. 100th row of text) so I can't achieve this feature.

Not sure if this should be the default or an option, maybe there are good uses for the default (like not wanting your cursor to get stuck all the way at the bottom).
See https://asciinema.org/a/304635 for a visual example (git li defined here):

Hi @gibfahn,
I think that feature sounds like something that would work well for this exact use case, but it doesn't really make sense for fzf in general. When you use backspace to delete the characters from 1.0.0, what you're doing is in fact re-searching for 1.0., not holding the line you were in to check around.
I'm struggling to figure out a way to achieve what you want (which I think makes sense for your use case) with fzf. But I don't think this is a feature to add to fzf.

Thanks for the suggestion. I also think it can be a nice addition to fzf, but I probably won't try to implement the scheme anytime soon because it only makes sense in relatively rare use cases where --sort is disabled and it's really not trivial to get it right. There are surprisingly many things to consider UI-wise and performance-wise. Imagine there are tens of thousands of matches from several million items, your cursor in on the 500th page of the matches, and fzf is still asynchronously consuming new data. It may not get along well with some of the existing options such as --tac.
I may revisit this in the future but I'm going to close this for now.

Yep, totally makes sense, and if I could think of a way to do it outside fzf I would.
I guess the issue is that I (and I assume others) use fzf not just for searching, but as a general list browser that also has a search bar, which is why there end up being so many complicated feature requests 😁 .

I am also interested in this, my usecase:
Im searching my history for an old command. I find and execute the command but it does not work.
Now it would be nice to get more context about which commands I executed right before that.
With this feature, I could search for the command again, select the line and remove the search.
Now im seeing everything i executed right before that.


FIXED rebalance extension

Extension / Adapter to rebalance FIXED products and maintain target allocation among fCash maturities.

Coverage decreased (-3.7%) to 81.973% when pulling f7a597cdb8e786d62ac811e822fbae89f5aaa313 on fixed-rebalance-extension into c00d1719496b1eb6a91ece8dc50262a30bf4cb1e on master.

Before making a detailed review of this PR, I've got a few questions to answer:

How do you envision this contract to fit into our existing keeper system. Currently, I've got this lambda that continuously calls the extension contract method shouldRebalance() and depending on the response either calls rebalance(), iterateRebalance() or ripcord(). The difference with them is that the caller only needs to specify the ExchangeAdapter that they need to be called with. How are _share and _minPositions calculated by the caller?
How often should rebalance be called? Is a cooldown period?
How does a keeper know not to call rebalance?

From my understanding we will only call these rebalance methods when one of the underlying fcash tokens matures. (so every three months). So I don't think we need to necessarily integrate this into the keeper system at all but can call it manually once every three months. (the name "RebalanceExtension" might be a bit misleading here since we are not planning to do the kind of continous rebalancing that we do for some of our other products - although the contract would support rebalancing at any point)
_minPositions can be calculated by simulating the rebalance call checking the positions afterwards and then subtracting a few percentage points. This is basically just for frontrunning protection.
_share allows us to split the rebalance trade over multiple transactions to limit price impact. I'm not sure if this is an issue at all and either way wont be one until we reach significant AUM. So for the beginning we can probably just set it to "1.0".

Note that if we at some point did decide to do "continous rebalancing" (which we currently don't plan to do). Then the keeper could determine wether rebalancing is needed by calling getUnderweightPositions, and using a certain minimum threshold. (since there will always be some minor deviation from the target allocations due to fluctuations in interest rates).

just to confirm - it looks like we'd need to deploy an extension contract per FIXED product that i.e. FIXED-DAI and FIXED-USDC will each need their own extension contract

Yes, we would deploy one instance for each FIXED product. I assumed this was standard for our extensions. (Please correct me if i'm wrong).
Note that the smart contract code should work for any FIXED product. I will extend the tests to run for all of our fixed products to make sure that is actually the case.

Testing

Overall consistent and I like what @FlattestWhite has suggested. When we read the output from a test it should make sense without much context.
Further more on naming, I understand that you created the context of some tests by the name of the function and the test names as "should work". Being more descriptive on these names would help others understand the context in which a user would care to call the function or how it is crucial to user requirement. I recognize this as a nit for development but these tests provide such awesome documentation to power users/devs and should strive for as good as possible.

I agree "should work" is a terrible test name. I replaced all of its occurences with more informative names.

Coverage
I think 100% test coverage is a bad requirement but we should make an effort to understand the coverage our tests provide and have it guide discussions.
# I utilized this command to get the following results. All tests passed.  COVERAGE=true INTEGRATIONTEST=true FORK=true VERBOSE=true node --max-old-space-size=4096 ./node_modules/.bin/hardhat coverage --testfiles test/integration/ethereum/fixedRebalanceExtension.spec.ts
File	% Stmts	% Branch	% Funcs	% Lines	Uncovered Lines
FixedRebalanceExtension.sol	93.02	62.5	92.59	93.02	416,417,420

_getFCashComponentsAndMaturities and _absoluteToRelativeMaturity are internal functions of the extension that are not covered by these tests. Removing them, increased all but branch coverage to 100%. The compiler should remove these functions from the deployed bytecode if they are never referenced. I suggest being more explicit and removing the unused code.
Testing every branch (especially in internal functions) is not super important to me, but understanding the gap is important. As a general rule, the else case of a require statement is already well tested (the call reverts). Branches caused by if statements are harder to assess for criticality of appropriate coverage.

I removed the unused methods and reached 100% line coverage. I looked at the missed branches added some extra coverage where it was worth the effort, but I agree we don't necessarily need 100% branch coverage.
Also I tried to add a CI step that reports the coverage from the integration test but it ended up overwriting the coverage data from the unit tests so I removed it again (see: https://github.com/IndexCoop/index-coop-smart-contracts/pull/122/commits/a7a8c0cba1d8a9da32b070db9488fb4f496cf261) . Would be great if we could find a way to aggregate those results somehow.

This Extension has two if branches not covered by existing tests, Lines 219 and 432. Make sure that the else paths are reachable and if reached, the expected behavior would still take place.
"access control" require statements and modifiers are worth having coverage for integration tests but more focused on the state changes that might affect access. For example, we might want to test us changing the operator and ensuring that the previous operator could no longer take privileged actions. Looks like this contract makes use of the onlyOperator modifier that presumably has been tested elsewhere, so we can assume it works but I still see it as such a critical path that we should make certain that this path works as expected.

"Invalid state" require statements, I think merit integration testing if it is reasonable that such branch would be taken or if removing the condition would be catastrophic for assumptions further in the code.

Take for example:
function rebalance(uint256 _share, uint256[] memory _minPositions)
and the require statements
require(_share > 0, "Share must be greater than 0");
require(_share <= 1 ether, "Share cannot exceed 100%");
In my testing removing these statements did not make any test fail and these calls are restricted to a privileged account. I therefore wouldn't worry about coverage for these cases.

All branches that are not covered seem to be internal and none of them are exposed through external functions accessible by unprivileged account. So no need to block on branch coverage.

Security

Seems like the only security assumptions that exist are that of a malicious operator due to all state changing functions being restricted. Unless there is a requirement to be less restrictive on who can modify the extension's state, I think this is appropriately secure enough. Further locking down the operator to reasonable checks would be great though. Is there not a way to get the valid maturities/ allocations from the notional protocol given the setToken passed in?
We might want to consider reentrancy in the external functions. At a glance though and with my understanding of the Set Protocol, we shouldn't need to worry about that.
We should be explicit about visibility for state variables. Most seem to be internal which is a good default, but I think some of these would make sense to be public and have the default getters exposed. Furthermore, it seems like almost all the values passed in to the constructor are immutably set to storage and if declared as immutable could be more efficient.

Agree with all of your points and just implemented most of your suggestions.
Regarding the security issues we might want to review some of them (such as reentrancy) if we decide to open up some of those methods to be called by anyone.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feat: look for git projects inside base folder

Hello!
I love this extension and decide to add a feature to get all git projects inside a base folder.
Features:

Base folders are defined inside the user's settings, with an optional depth limit (default is 2).

{
    "dashboard.projectsBaseDirectories": ["C:\\workspace"],
    "dashboard.projectsDepthLimit": 2
}

Each base directory forms a group and the git directories found inside are added to it.
If the directory exists in any other group, it is skipped.
The project`s name is the directory basename and the color is randomized.

Fixes:

Changed the isFolderGitRepo function based on this answer, because it was not working for me.

Thanks for the PR, I will have a look on it soon! :)

Hello, is it a good idea to changed it to respect the globalState/settings toggle?

Hey! Sorry for not coming back to you yet. Busy time. :)

Hello, is it a good idea to changed it to respect the globalState/settings toggle?

I quickly had a look at it and I also think that the globalState/settings toggle should be respected by this feature. As a user, I would expect all data sources to be switched by that toggle.
I will review the rest of this feature in the following days. So far, thank you for building upon my extension! :)

I finally had a look at it! I like the idea but found some aspects to be unclear/unfit for the end-user and some functions buggy. E.g. the git projects inside two base directories are always synced into one group for me.
I have given a testing-build to some of my usual testers to get some additional feedback. I'll come back to you with a more detailed list of remarks as soon as I hear from them. :)

Changed the isFolderGitRepo function based on this answer, because it was not working for me.

Do you have an example for which the old function did not work? I originally refrained from using the .gitfolder as an indicator, as I have some projects where I only operate on a subfolder of the repository. In my case, those are projects within a Visual Studio solution, but I guess the same principle applies to monorepos in general.


Minor fixes

This PR fixes wording, spelling and punctuation in some pages, updates the manual mounting image in quick-setup, and adds info on the BMI270 IMU where it was previously missing

Now that https://github.com/SlimeVR/SlimeVR-Server/pull/939 is merged, I would request "mounting direction" be changed to "mounting orientation" now. I'm also still really iffy about the one remaining comment on my review, idk if I want it merged like that. Please request my review once that's all done and I can approve.


remove duplicate operator==() for ANARIDataType

@nnn911 can you check if this fixes the issue you reported in #185?

Thanks! This has fixed #185 for me.

Closes #185.


Include **kwargs options in doc strings

If you haven't realized yet, I'm a bit anal about documentation 😄
I'd like to include docstrings like the ones I included in the timelines methods (#41) - i.e. include details on the kwargs (optional arguments) -  for each method.
However, they're a bit long, does this bother anyone? I find myself using the docstrings constantly and get frustrated when docstrings have no information so it would personally make me quite happy to include this information - mostly because it is impossible for me to remember everything.
I will take the lead on this if you guys don't mind.

Sounds good to me.

Sounds good to me.

Included in #49 ...

Included in #49 ...


Redevelop XECOF (8)

Part of the computation to find enu covariance, implemented as part of PR #84
https://github.com/uw-ssec/offshore-geodesy/blob/b81922ebb0d2a87a571e11a7a05c387acb881ac4/src/gnatss/main.py#L391-L397


test for installing from remote file

i am opening this pull request even though i didn't have a chance to run the test today (windows tests are broken i think #882) will take a look using my mac tomorrow
in the mean time please let me know if i used the correct decorators for the test function and if i am missing something from the test case
thank you for the amazing work
this is  a test for: pipenv install -r http://something.com/req.txt

Thanks for the amazing input will look into it today

commits are squashed and test was passing locally. we should be all set 👍

so after investigation turns out tempfile.mkstemp actually opens the file and returns the file descriptor so we have two solutions:

close the file immediately so basically using mkstemp just to create the file
we could hold on to the descriptor and close it before deleting

which one do you recommend? also if i got it wrong can someone suggest another approach
i have already implemented the second approach do you want me to push it?

Oh this test... it’s probably more likely that it’s failing due to issues relating to loca file installation. I’m in the middle of untangling how that wound up broken

Ah this is for the other test. I guess my question would be whether using a descriptor is the best option at all. We already create temp files for requirements as we resolve and add to Pipfiles. Is there any reason not to just iterate over requirements from the remotesfile contents? I haven’t looked at complexity for that but you’re not streaming the file content into the descriptor right? So it’s going to be all loaded in memory anyway

@techalchemy I was thinking of streaming it but went with using temp files!
I wasn't using file descriptors but the tempfile library automatically opens the file
I'm just downloading the file you can check at the end of the utils.py file to see how I am doing it :)

I've pushed b1be8f7 which will properly capture and then close the file descriptor for Windows before deleting the temp file.
If you rebase onto master @Dreamersoul, I think we're about ready.

Awesome! I checked your commit and turns out I did the same locally! Once I have access to my laptop I'll rebase and push :+1:

Can someone trigger a rebuild? The tests failed because of pip and not my test :sweat_smile:

Looks like we're set. Thanks again @DreamerSoul!

✨


Impossible to connect to Opensearch inside a Docker network

(check apply)

[x] read the contribution guideline

Steps to replicate
I'm trying to do a simple test where fluentd and opensearch are in the same docker network.
The Docker compose file is:
services:
  fluentd:
    build: ./fluentd
    container_name: fluentd
    ports:
      - 24224:24224
      - 24224:24224/udp
    restart: unless-stopped
    links:
      - "opensearch"
    volumes:
      - ./fluentd/data:/fluentd/log
      - ./fluentd/conf:/fluentd/etc
    networks:
      - opensearch-net # All of the containers will join the same Docker bridge network

  opensearch: # This is also the hostname of the container within the Docker network (i.e. https://opensearch-node1/)
    image: opensearchproject/opensearch:latest # Specifying the latest available image - modify if you want a specific version
    container_name: opensearch-node1
    environment:
      - cluster.name=opensearch-cluster # Name the cluster
      - node.name=opensearch-node1 # Name the node that will run in this container
      - cluster.initial_cluster_manager_nodes=opensearch-node1 # Nodes eligible to serve as cluster manager
      - bootstrap.memory_lock=true # Disable JVM heap memory swapping
      - "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m" # Set min and max JVM heap sizes to at least 50% of system RAM
      - 'network.host: "<IP_ADDRESS>"'
      - "discovery.type=single-node"
    ulimits:
      memlock:
        soft: -1 # Set memlock to unlimited (no soft or hard limit)
        hard: -1
      nofile:
        soft: 65536 # Maximum number of open files for the opensearch user - set to at least 65536
        hard: 65536
    volumes:
      - opensearch-data1:/usr/share/opensearch/data # Creates volume called opensearch-data1 and mounts it to the container
    ports:
      - 9200:9200 # REST API
      - 9600:9600 # Performance Analyzer
    networks:
      - opensearch-net # All of the containers will join the same Docker bridge network

  opensearch-dashboards:
    image: opensearchproject/opensearch-dashboards:latest # Make sure the version of opensearch-dashboards matches the version of opensearch installed on other nodes
    container_name: opensearch-dashboards
    ports:
      - 5601:5601 # Map host port 5601 to container port 5601
    expose:
      - "5601" # Expose port 5601 for web access to OpenSearch Dashboards
    environment:
      - 'OPENSEARCH_HOSTS=["https://opensearch:9200"]'
    networks:
      - opensearch-net

volumes:
  opensearch-data1:

networks:
  opensearch-net:

The fluentd config file is:
<source>
  @type  forward
  @id    input1
  @label @mainstream
  port  24224
</source>

<filter **>
  @type stdout
</filter>

<label @mainstream>
  <match **>
    @type opensearch
    host opensearch
    port 9200
    logstash_format false
    user admin
    password admin
    index_name fluentd.${tag}.%Y%m%d
	scheme https
	ssl_verify false
    ssl_version TLSv1_2
  </match>
</label>

Expected Behavior or What you need to ask
When I lauch the docker-compose up command, I obtain the following error:

fluentd                | 2023-10-30 09:31:40 +0000 [warn]: #0 Could not communicate to OpenSearch, resetting connection and trying again. Connection refused - connect(2) for <IP_ADDRESS>:9200 (Errno::ECONNREFUSED)

Of course, none of my logs are reported into Opensearch.
The complete log is :

opensearch-node1       | Enabling execution of install_demo_configuration.sh for OpenSearch Security Plugin
opensearch-node1       | **************************************************************************
opensearch-node1       | ** This tool will be deprecated in the next major release of OpenSearch **
opensearch-node1       | ** https://github.com/opensearch-project/security/issues/1755           **
opensearch-node1       | **************************************************************************
opensearch-node1       | OpenSearch Security Demo Installer
opensearch-node1       |  ** Warning: Do not use on production or public reachable systems **
opensearch-node1       | Basedir: /usr/share/opensearch
opensearch-node1       | OpenSearch install type: rpm/deb on Amazon Linux release 2023 (Amazon Linux)
opensearch-node1       | OpenSearch config dir: /usr/share/opensearch/config
opensearch-node1       | OpenSearch config file: /usr/share/opensearch/config/opensearch.yml
opensearch-node1       | OpenSearch bin dir: /usr/share/opensearch/bin
opensearch-node1       | OpenSearch plugins dir: /usr/share/opensearch/plugins
opensearch-node1       | OpenSearch lib dir: /usr/share/opensearch/lib
opensearch-node1       | Detected OpenSearch Version: x-content-2.11.0
opensearch-node1       | Detected OpenSearch Security Version: <IP_ADDRESS>
opensearch-node1       | /usr/share/opensearch/config/opensearch.yml seems to be already configured for Security. Quit.
opensearch-node1       | Enabling OpenSearch Security Plugin
opensearch-node1       | Enabling execution of OPENSEARCH_HOME/bin/opensearch-performance-analyzer/performance-analyzer-agent-cli for OpenSearch Performance Analyzer Plugin
fluentd                | 2023-10-30 09:31:37 +0000 [info]: init supervisor logger path=nil rotate_age=nil rotate_size=nil
fluentd                | 2023-10-30 09:31:37 +0000 [info]: parsing config file is succeeded path="/fluentd/etc/fluent.conf"
fluentd                | 2023-10-30 09:31:37 +0000 [info]: gem 'fluentd' version '1.15.3'
fluentd                | 2023-10-30 09:31:37 +0000 [info]: gem 'fluent-plugin-calyptia-monitoring' version '0.1.3'
fluentd                | 2023-10-30 09:31:37 +0000 [info]: gem 'fluent-plugin-cmetrics' version '0.1.0'
fluentd                | 2023-10-30 09:31:37 +0000 [info]: gem 'fluent-plugin-metrics-cmetrics' version '0.1.2'
fluentd                | 2023-10-30 09:31:37 +0000 [info]: gem 'fluent-plugin-multi-format-parser' version '1.0.0'
fluentd                | 2023-10-30 09:31:37 +0000 [info]: gem 'fluent-plugin-opensearch' version '1.1.4'
fluentd                | 2023-10-30 09:31:37 +0000 [info]: gem 'fluent-plugin-rewrite-tag-filter' version '2.4.0'
opensearch-node1       | WARNING: A terminally deprecated method in java.lang.System has been called
opensearch-node1       | WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.OpenSearch (file:/usr/share/opensearch/lib/opensearch-2.11.0.jar)
opensearch-node1       | WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.OpenSearch
opensearch-node1       | WARNING: System::setSecurityManager will be removed in a future release
fluentd                | 2023-10-30 09:31:37 +0000 [warn]: define <match fluent.**> to capture fluentd logs in top level is deprecated. Use <label @FLUENT_LOG> instead
fluentd                | 2023-10-30 09:31:37 +0000 [info]: using configuration file:
fluentd                |
fluentd                |     @type forward
fluentd                |     @id input1
fluentd                |     @label @mainstream
fluentd                |     port 24224
fluentd                |
fluentd                |   <filter *>
fluentd                |     @type stdout
fluentd                |
fluentd                |   <label @mainstream>
fluentd                |     <match >
fluentd                |       @type opensearch
fluentd                |       host "opensearch"
fluentd                |       port 9200
fluentd                |       logstash_format false
fluentd                |       user "admin"
fluentd                |       password xxxxxx
fluentd                |       index_name "fluentd.${tag}.%Y%m%d"
fluentd                |       scheme https
fluentd                |       ssl_verify false
fluentd                |       ssl_version TLSv1_2
fluentd                |
fluentd                |
fluentd                |
fluentd                | 2023-10-30 09:31:37 +0000 [info]: starting fluentd-1.15.3 pid=7 ruby="3.0.5"
fluentd                | 2023-10-30 09:31:37 +0000 [info]: spawn command to main:  cmdline=["/usr/local/bin/ruby", "-Eascii-8bit:ascii-8bit", "/usr/local/bundle/bin/fluentd", "--config", "/fluentd/etc/fluent.conf", "--plugin", "/fluentd/plugins", "--under-supervisor"]
fluentd                | 2023-10-30 09:31:37 +0000 [info]: init supervisor logger path=nil rotate_age=nil rotate_size=nil
fluentd                | 2023-10-30 09:31:38 +0000 [info]: #0 init worker0 logger path=nil rotate_age=nil rotate_size=nil
fluentd                | 2023-10-30 09:31:38 +0000 [info]: adding match in @mainstream pattern="" type="opensearch"
opensearch-node1       | WARNING: A terminally deprecated method in java.lang.System has been called
opensearch-node1       | WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.Security (file:/usr/share/opensearch/lib/opensearch-2.11.0.jar)
opensearch-node1       | WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.Security
opensearch-node1       | WARNING: System::setSecurityManager will be removed in a future release
opensearch-node1       | [2023-10-30T09:31:38,629][INFO ][o.o.n.Node               ] [opensearch-node1] version[2.11.0], pid[31], build[tar/4dcad6dd1fd45b6bd91f041a041829c8687278fa/2023-10-13T02:55:55.511945994Z], OS[Linux/<IP_ADDRESS>-microsoft-standard-WSL2/amd64], JVM[Eclipse Adoptium/OpenJDK 64-Bit Server VM/17.0.8/17.0.8+7]
opensearch-node1       | [2023-10-30T09:31:38,632][INFO ][o.o.n.Node               ] [opensearch-node1] JVM home [/usr/share/opensearch/jdk], using bundled JDK/JRE [true]
opensearch-node1       | [2023-10-30T09:31:38,632][INFO ][o.o.n.Node               ] [opensearch-node1] JVM arguments [-Xshare:auto, -Dopensearch.networkaddress.cache.ttl=60, -Dopensearch.networkaddress.cache.negative.ttl=10, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -XX:+ShowCodeDetailsInExceptionMessages, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dio.netty.allocator.numDirectArenas=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.locale.providers=SPI,COMPAT, -Xms1g, -Xmx1g, -XX:+UseG1GC, -XX:G1ReservePercent=25, -XX:InitiatingHeapOccupancyPercent=30, -Djava.io.tmpdir=/tmp/opensearch-16725286551108414319, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Djava.util.concurrent.ForkJoinPool.common.threadFactory=org.opensearch.secure_sm.SecuredForkJoinWorkerThreadFactory, -Dclk.tck=100, -Djdk.attach.allowAttachSelf=true, -Djava.security.policy=/usr/share/opensearch/config/opensearch-performance-analyzer/opensearch_security.policy, --add-opens=jdk.attach/sun.tools.attach=ALL-UNNAMED, -Dopensearch.cgroups.hierarchy.override=/, -Xms512m, -Xmx512m, -XX:MaxDirectMemorySize=268435456, -Dopensearch.path.home=/usr/share/opensearch, -Dopensearch.path.conf=/usr/share/opensearch/config, -Dopensearch.distribution.type=tar, -Dopensearch.bundled_jdk=true]
opensearch-node1       | [2023-10-30T09:31:39,526][INFO ][o.o.s.s.t.SSLConfig      ] [opensearch-node1] SSL dual mode is disabled
opensearch-node1       | [2023-10-30T09:31:39,526][INFO ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node1] OpenSearch Config path is /usr/share/opensearch/config
opensearch-node1       | [2023-10-30T09:31:39,739][INFO ][o.o.s.s.DefaultSecurityKeyStore] [opensearch-node1] JVM supports TLSv1.3
opensearch-node1       | [2023-10-30T09:31:39,741][INFO ][o.o.s.s.DefaultSecurityKeyStore] [opensearch-node1] Config directory is /usr/share/opensearch/config/, from there the key- and truststore files are resolved relatively
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:39Z","tags":["info","plugins-service"],"pid":1,"message":"Plugin "dataSourceManagement" has been disabled since the following direct or transitive dependencies are missing or disabled: [dataSource]"}
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:39Z","tags":["info","plugins-service"],"pid":1,"message":"Plugin "dataSource" is disabled."}
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:39Z","tags":["info","plugins-service"],"pid":1,"message":"Plugin "visTypeXy" is disabled."}
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:39Z","tags":["warning","config","deprecation"],"pid":1,"message":""cpu.cgroup.path.override" is deprecated and has been replaced by "ops.cGroupOverrides.cpuPath""}
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:39Z","tags":["warning","config","deprecation"],"pid":1,"message":""cpuacct.cgroup.path.override" is deprecated and has been replaced by "ops.cGroupOverrides.cpuAcctPath""}
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:39Z","tags":["warning","config","deprecation"],"pid":1,"message":""opensearch.requestHeadersWhitelist" is deprecated and has been replaced by "opensearch.requestHeadersAllowlist""}
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:40Z","tags":["info","plugins-system"],"pid":1,"message":"Setting up [51] plugins: [usageCollection,opensearchDashboardsUsageCollection,mapsLegacy,opensearchDashboardsLegacy,share,opensearchUiShared,embeddable,legacyExport,expressions,data,securityAnalyticsDashboards,home,apmOss,savedObjects,reportsDashboards,searchRelevanceDashboards,dashboard,mlCommonsDashboards,visualizations,visTypeVega,visTypeTimeline,visTypeTable,visAugmenter,anomalyDetectionDashboards,alertingDashboards,visTypeMarkdown,visBuilder,tileMap,regionMap,customImportMapDashboards,inputControlVis,ganttChartDashboards,visualize,queryWorkbenchDashboards,indexManagementDashboards,notificationsDashboards,management,indexPatternManagement,advancedSettings,console,dataExplorer,charts,visTypeVislib,visTypeTimeseries,visTypeTagcloud,visTypeMetric,observabilityDashboards,discover,savedObjectsManagement,securityDashboards,bfetch]"}
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-node1       | [2023-10-30T09:31:40,125][INFO ][o.o.s.s.DefaultSecurityKeyStore] [opensearch-node1] TLS Transport Client Provider : JDK
opensearch-node1       | [2023-10-30T09:31:40,125][INFO ][o.o.s.s.DefaultSecurityKeyStore] [opensearch-node1] TLS Transport Server Provider : JDK
opensearch-node1       | [2023-10-30T09:31:40,125][INFO ][o.o.s.s.DefaultSecurityKeyStore] [opensearch-node1] TLS HTTP Provider             : JDK
opensearch-node1       | [2023-10-30T09:31:40,125][INFO ][o.o.s.s.DefaultSecurityKeyStore] [opensearch-node1] Enabled TLS protocols for transport layer : [TLSv1.3, TLSv1.2]
opensearch-node1       | [2023-10-30T09:31:40,125][INFO ][o.o.s.s.DefaultSecurityKeyStore] [opensearch-node1] Enabled TLS protocols for HTTP layer      : [TLSv1.3, TLSv1.2]
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-node1       | [2023-10-30T09:31:40,167][INFO ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node1] Clustername: opensearch-cluster
opensearch-node1       | [2023-10-30T09:31:40,177][WARN ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node1] Directory /usr/share/opensearch/config has insecure file permissions (should be 0700)
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:40Z","tags":["info","savedobjects-service"],"pid":1,"message":"Waiting until all OpenSearch nodes are compatible with OpenSearch Dashboards before starting saved objects migrations..."}
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:40Z","tags":["error","opensearch","data"],"pid":1,"message":"[ConnectionError]: connect ECONNREFUSED <IP_ADDRESS>:9200"}
opensearch-dashboards  | {"type":"log","@timestamp":"2023-10-30T09:31:40Z","tags":["error","savedobjects-service"],"pid":1,"message":"Unable to retrieve version information from OpenSearch nodes."}
fluentd                | 2023-10-30 09:31:40 +0000 [warn]: #0 Could not communicate to OpenSearch, resetting connection and trying again. Connection refused - connect(2) for <IP_ADDRESS>:9200 (Errno::ECONNREFUSED)
fluentd                | 2023-10-30 09:31:40 +0000 [warn]: #0 Remaining retry: 14. Retry to communicate after 2 second(s).
opensearch-node1       | [2023-10-30T09:31:40,851][INFO ][o.o.p.c.c.PluginSettings ] [opensearch-node1] Config: metricsLocation: /dev/shm/performanceanalyzer/, metricsDeletionInterval: 1, httpsEnabled: false, cleanup-metrics-db-files: true, batch-metrics-retention-period-minutes: 7, rpc-port: 9650, webservice-port 9600
opensearch-node1       | [2023-10-30T09:31:41,292][INFO ][o.o.i.r.ReindexPlugin    ] [opensearch-node1] ReindexPlugin reloadSPI called
opensearch-node1       | [2023-10-30T09:31:41,293][INFO ][o.o.i.r.ReindexPlugin    ] [opensearch-node1] Unable to find any implementation for RemoteReindexExtension
opensearch-node1       | [2023-10-30T09:31:41,320][INFO ][o.o.j.JobSchedulerPlugin ] [opensearch-node1] Loaded scheduler extension: opendistro_anomaly_detector, index: .opendistro-anomaly-detector-jobs
opensearch-node1       | [2023-10-30T09:31:41,344][INFO ][o.o.j.JobSchedulerPlugin ] [opensearch-node1] Loaded scheduler extension: reports-scheduler, index: .opendistro-reports-definitions
opensearch-node1       | [2023-10-30T09:31:41,345][INFO ][o.o.j.JobSchedulerPlugin ] [opensearch-node1] Loaded scheduler extension: opendistro-index-management, index: .opendistro-ism-config
opensearch-node1       | [2023-10-30T09:31:41,346][INFO ][o.o.j.JobSchedulerPlugin ] [opensearch-node1] Loaded scheduler extension: scheduler_geospatial_ip2geo_datasource, index: .scheduler-geospatial-ip2geo-datasource
opensearch-node1       | [2023-10-30T09:31:41,352][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [aggs-matrix-stats]
opensearch-node1       | [2023-10-30T09:31:41,353][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [analysis-common]
opensearch-node1       | [2023-10-30T09:31:41,353][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [geo]
opensearch-node1       | [2023-10-30T09:31:41,353][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [ingest-common]
opensearch-node1       | [2023-10-30T09:31:41,353][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [ingest-geoip]
opensearch-node1       | [2023-10-30T09:31:41,353][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [ingest-user-agent]
opensearch-node1       | [2023-10-30T09:31:41,353][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [lang-expression]
opensearch-node1       | [2023-10-30T09:31:41,353][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [lang-mustache]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [lang-painless]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [mapper-extras]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [opensearch-dashboards]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [parent-join]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [percolator]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [rank-eval]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [reindex]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [repository-url]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [search-pipeline-common]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [systemd]
opensearch-node1       | [2023-10-30T09:31:41,354][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded module [transport-netty4]
opensearch-node1       | [2023-10-30T09:31:41,355][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-alerting]
opensearch-node1       | [2023-10-30T09:31:41,355][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-anomaly-detection]
opensearch-node1       | [2023-10-30T09:31:41,355][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-asynchronous-search]
opensearch-node1       | [2023-10-30T09:31:41,355][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-cross-cluster-replication]
opensearch-node1       | [2023-10-30T09:31:41,355][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-custom-codecs]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-geospatial]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-index-management]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-job-scheduler]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-knn]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-ml]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-neural-search]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-notifications]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-notifications-core]
opensearch-node1       | [2023-10-30T09:31:41,356][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-observability]
opensearch-node1       | [2023-10-30T09:31:41,357][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-performance-analyzer]
opensearch-node1       | [2023-10-30T09:31:41,357][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-reports-scheduler]
opensearch-node1       | [2023-10-30T09:31:41,357][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-security]
opensearch-node1       | [2023-10-30T09:31:41,357][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-security-analytics]
opensearch-node1       | [2023-10-30T09:31:41,357][INFO ][o.o.p.PluginsService     ] [opensearch-node1] loaded plugin [opensearch-sql]

Using Fluentd and OpenSearch plugin versions

OS version: Windows 11 Family 22H2
Docker Desktop v4.19.0
Fluentd v1.15.3
OpenSearch plugin version: 1.1.4

I just found the issue. It was only an Opensearch configuration issue.


Migration: when "late" is added due to a hint, it doesn't show up under the "proposed edits" list

Fixed in<PHONE_NUMBER>809ec789143f66ebe0a9799e2ec40a


Facing SyntaxError: Unexpected token  when I install and boot for the first time

Current Behavior
I was introduced to this software by an acquaintance and started using it.
I have stored the device file device.yml in place and when I try to start it, I get the following error message and cannot start it.
I would appreciate any advice on how to correct this.

/usr/local/lib/node_modules/@flowforge/flowforge-device-agent/lib/agent.js:47
info(Snapshot: ${this.currentSnapshot?.id || 'none'})
^
SyntaxError: Unexpected token .
at Module._compile (internal/modules/cjs/loader.js:723:23)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/usr/local/lib/node_modules/@flowforge/flowforge-device-agent/index.js:3:19)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
Thank you
Expected Behavior
No response
Steps To Reproduce
No response
Environment

FlowForge version:
Node.js version: v10.19.0
npm version: 6.14.4
Platform/OS: Ubuntu 20.04
Browser: chrome

Hi @hfc01512
I can see you are using Node.js v10. The device agent requires Node.js 16 or later. You will need to update your version of node.js to use the agent.

Hell knolleary,
Thanks for the advice.
I have successfully activated the system.

fixed by #55


build-sync: Emergencies only for stream

See https://github.com/openshift-eng/art-tools/pull/69

/approve


Problems connecting Video to shadow

Hi,
i run blade-shadow- beta on an arch linux:

x220 4.18.12-arch1-1-ARCH x86_64 GNU/Linux

The app is running, but when I try to connect to the blade server I find a Windows PC/Blade but by connecting the video, the app gives me

An unknown Error occured

The second time I try to connect the shell gives me

(node:4140) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: kill ESRCH
(node:4140) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I'm still trying to figure out whats happening, but would appreciate every help.
Vg Chris

Hi !
Did you use the AppImage available on the website ?
There are a few thing to do before using Shadow on Linux like checking if you use X11, and put your user in the input group.
Did you also check your VA-API drivers ?

Hi,
yes I use the AppImage and my user is in th einput group.
I did check VA-API drivers.
vainfo: VA-API version: 1.3 (libva 2.3.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Sandybridge Mobile - 2.2.0
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple            : VAEntrypointVLD
VAProfileMPEG2Main              : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main               : VAEntrypointVLD
VAProfileH264Main               : VAEntrypointEncSlice
VAProfileH264High               : VAEntrypointVLD
VAProfileH264High               : VAEntrypointEncSlice
VAProfileH264StereoHigh         : VAEntrypointVLD
VAProfileVC1Simple              : VAEntrypointVLD
VAProfileVC1Main                : VAEntrypointVLD
VAProfileVC1Advanced            : VAEntrypointVLD
VAProfileNone                   : VAEntrypointVideoProc
Last but not least I use X11 with awesome WM.
name of display:    :0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    12001000
X.Org version: 1.20.1
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x2400022, revert to Parent
number of extensions:    28
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
DRI3
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
Present
RANDR
RECORD
RENDER
SECURITY
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-DGA
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
default screen number:    0
number of screens:    1
But I noticed that shadow cannot detect if I'm using X11.
WARNING:  • Impossible to check if you are on Xorg or not.
I overlooked it as it is just a warning and the client is still starting.
Also this are messages I get on terminal while using the AppImage.
** Message: 21:24:35.202: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
(node:1310) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: The name org.freedesktop.secrets was not provided by any .service files
(node:1310) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:1310) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: kill ESRCH
Vg Chris

Hi Chris!
You forgot to mention the distribution :p
Can you also use the parameter --report when launching the AppImage and send back the link?

Good point!
x220 4.18.12-arch1-1-ARCH x86_64 GNU/Linux
Interesting, when I start the AppImage with --report I get
Empty file !
Also we can ignore the environnement warning. Was some bad configuration on my side.

Okay so for the node Warnings, everybody get this. It will not block anything.
Did you installed it from AUR?
Can you do ldd on the binary? It's located in /opt/shadowbeta/resources/app.asar.unpacked/Icantrememberthefolders/Shadow.
Sorry I'm on my phone :x

No, I got It from github.io.
I have the AppImage just laying around in some folder.

Hey, got one step further.
Some dependencies were absence. Now report gives.
"https://nicolasguilloux.eu/hostbin/2437752781"

You use an old AppImage, the current version is 2.0.2. Can you upgrade it and try again please?

Ouch! This sure helped.
It could have been so simple... ^^
Thank you very much. Time to play!
Vg


getRobotHistoryForTeam is not a function

I'm having problems with getRobotHistoryForTeam and getTeamRobotHistory every time I attempt to use them I get this error:

The package has been republished on npm, and it works. Thanks for reporting the issue!


[Bug] Discord acting like website and BD doesn't lunch up

Describe the Bug

To Reproduce

Expected Behavior

Screenshots

Discord Version

Additional Context

Use the latest installers as dictated in the README at http://github.com/BetterDiscord/Installer

Use the latest installers as dictated in the README at http://github.com/BetterDiscord/Installer

i did and it's doing same thing and when i use beta BD its crashing a lot, without BD my normal discord crashing a lot too

without BD my normal Discord is crashing too

Then it sounds like you're having more issues than BD. Reinstall Discord.

without BD my normal Discord is crashing too

Then it sounds like you're having more issues than BD. Reinstall Discord.

i actually did and it said some error https://gyazo.com/29ccedf3996adc21fea0569e52f5ca0e and when i restarted pc it disappeared and BD did luck up but discord wanted update and than it happened again act like website and wanted me download discord app even i was using it, now i use beta BD and it didn't crash yet, i will show how that discord acted https://gyazo.com/15d33c84685ecea6b4b47f91f5730cf6 pls ignor my dms with people just look what it doing, its doing idh how long almost month


Build errors due to YamlCPP

Hello,
Getting the following error during build:
/usr/bin/ld: /home/amram/development/nakai/packages/nakai-onboard/install/isaac_ros_stereo_image_proc/lib/libyaml-cpp.a(scanscalar.cpp.o): warning: relocation against `_ZZN4YAML3Exp5BlankEvE1e' in read-only section `.text'
/usr/bin/ld: /home/amram/development/nakai/packages/nakai-onboard/install/isaac_ros_stereo_image_proc/lib/libyaml-cpp.a(convert.cpp.o): relocation R_X86_64_PC32 against symbol `_ZTIN4YAML11InvalidNodeE' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status

Could you try clearing your build/ and install/ directories in the ROS workspace, and then rebuild?
It looks like you aren't using the Isaac ROS Docker container provided with accompanying development scripts in the Isaac ROS Common repository. This Docker container bundles together all of the necessary dependencies for getting Isaac ROS and ROS 2 working on x86 and Jetson platforms, including libyaml-cpp-dev.

@jaiveersinghNV I am using the docker image by dustynv:
dustynv/ros:humble-ros-base-l4t-r35.3.1
Taken from: https://github.com/dusty-nv/jetson-containers/


Toolbox and Workspace Export via JS

Added functionality: exporting and importing toolboxes and preloaded workspaces. Exporting/importing as .xml files are still supported; there is an additional option in the export and import dropdown menu. Such changes are reflected in exportable starter-code as well. See design doc for more information.

This change is

Review status: 0 of 6 files reviewed at latest revision, 5 unresolved discussions.

index.html, line 54 at r5 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
Revert indent changes.

Done.

src/workspacefactory/wfactory_controller.js, line 98 at r5 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
I see what you're hinting at, but in the community and the development, this has been called a workspace. Maybe workspace_blocks if you want to avoid confusion with the Workspace class/object.

Hm, I see what you mean. The MODE_PRELOAD variable was defined before I started working on devtools, so it might be changing a lot of variables in a lot of files (I just changed toolbox and preload to be uppercase strings). Should I hold off on renaming? Wanted to make sure before changing a lot of files.

src/workspacefactory/wfactory_controller.js, line 361 at r5 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
JSDoc @param for function

Done!

src/workspacefactory/wfactory_generator.js, line 154 at r5 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
Define BLOCKLY_${mode}_XML constant once.

Done!

src/workspacefactory/wfactory_generator.js, line 258 at r5 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
Escape the XML inside the JS strings.  I can currently break this by including a single quote in any of my names.

Done!

Comments from Reviewable

Reviewed 3 of 7 files at r4, 2 of 3 files at r6.
Review status: 5 of 6 files reviewed at latest revision, 7 unresolved discussions.

src/workspacefactory/wfactory_controller.js, line 98 at r5 (raw file):
Previously, chynu (celine choo) wrote…
Hm, I see what you mean. The MODE_PRELOAD variable was defined before I started working on devtools, so it might be changing a lot of variables in a lot of files (I just changed toolbox and preload to be uppercase strings). Should I hold off on renaming? Wanted to make sure before changing a lot of files.

Hmm.. Okay, but now we are exposing this to our developers when we put BLOCKLY_${mode}_XML in their files.  Because this becomes our interface, I'd like to fix this sooner than later, but if it is lots of files, it is probably better as an independent PR.
Alternatively, we could just swap the value of xmlStorageVariable based on the value of mode, and leave the rest the same.  Probably the easiest route.

src/workspacefactory/wfactory_controller.js, line 795 at r6 (raw file):

        } else {
          // Run JS code to store XML, get toolboxName to retrieve XML.
          let toolboxName = this.generator.storeXml(reader.result,

The name generator is really confusing to me, as someone who reads about Blockly.Generators is the code. We should rename this variable, and possibly the whole class, in the near future.
(Fine for now; I know this isn't your code.)

src/workspacefactory/wfactory_generator.js, line 258 at r5 (raw file):
Previously, chynu (celine choo) wrote…
Done!

I can still break it.  I'm gonna leave it to you to figure out why/how (at least for a little while.

src/workspacefactory/wfactory_generator.js, line 181 at r6 (raw file):

 * @returns {string} Name of toolbox or preload workspace.
 */
WorkspaceFactoryGenerator.prototype.storeXml =

This function name doesn't make sense to me.  We are loading the file, but storing it sounds like the opposite.

src/workspacefactory/wfactory_generator.js, line 186 at r6 (raw file):

  if (importMode == WorkspaceFactoryController.MODE_TOOLBOX) {
    var scriptToRun = jsFileContents.replace(/BLOCKLY_TOOLBOX_XML/g,
        'this.BLOCKLY_TOOLBOX_XML');

What is this in the context of the eval?

src/workspacefactory/wfactory_generator.js, line 193 at r6 (raw file):

  // Stores the XML string.
  eval(scriptToRun);

Make sure you are only evaluating  the part of the file between the comments.  I can currently add an alert() before the comments and it runs it.
In the near future, we should be preserving the rest of the file contents, during saving.
Developers might need this space for import/module/require boilerplate, and maybe other things like copyrights.

Comments from Reviewable

Review status: 4 of 6 files reviewed at latest revision, 6 unresolved discussions.

src/workspacefactory/wfactory_controller.js, line 98 at r5 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
Hmm.. Okay, but now we are exposing this to our developers when we put BLOCKLY_${mode}_XML in their files.  Because this becomes our interface, I'd like to fix this sooner than later, but if it is lots of files, it is probably better as an independent PR.
Alternatively, we could just swap the value of xmlStorageVariable based on the value of mode, and leave the rest the same.  Probably the easiest route.

Sage and I might be renaming things in the future, so I will probably group that in with some renaming of methods.

src/workspacefactory/wfactory_controller.js, line 795 at r6 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
The name generator is really confusing to me, as someone who reads about Blockly.Generators is the code. We should rename this variable, and possibly the whole class, in the near future.
(Fine for now; I know this isn't your code.)

Okay! I'll probably group it in with renaming the "PRELOAD" variable as well, in another PR.

src/workspacefactory/wfactory_generator.js, line 258 at r5 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
I can still break it.  I'm gonna leave it to you to figure out why/how (at least for a little while.

Done (finally)!

src/workspacefactory/wfactory_generator.js, line 181 at r6 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
This function name doesn't make sense to me.  We are loading the file, but storing it sounds like the opposite.

Renamed to loadXml().

src/workspacefactory/wfactory_generator.js, line 186 at r6 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
What is this in the context of the eval?

It is because when evaluating, the xml strings are stored in this.BLOCKLY_TOOLBOX_XML which is a field of the generator class.

src/workspacefactory/wfactory_generator.js, line 193 at r6 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
Make sure you are only evaluating  the part of the file between the comments.  I can currently add an alert() before the comments and it runs it.
In the near future, we should be preserving the rest of the file contents, during saving.
Developers might need this space for import/module/require boilerplate, and maybe other things like copyrights.

Noted-- I made a separate function evaluateMarkedCode() to evaluate only the code between the comments. I'll work on saving the rest of the file contents in the future.

Comments from Reviewable

Reviewed 1 of 2 files at r7.
Review status: 5 of 6 files reviewed at latest revision, 5 unresolved discussions, some commit checks failed.

src/workspacefactory/wfactory_controller.js, line 379 at r7 (raw file):

  }
  // Remove .js extension for name of toolbox
  fileName = fileName.trim().replace(/.js/g, '');

Escape the ., which has special meaning in a regex. Also, make sure this only matches the end of string.

src/workspacefactory/wfactory_generator.js, line 258 at r5 (raw file):
Previously, chynu (celine choo) wrote…
Done (finally)!

So you thought....    ;)  (Leaving for future PR.)

src/workspacefactory/wfactory_generator.js, line 157 at r7 (raw file):

  let xmlStorageVariable = 'BLOCKLY_' + mode + '_XML';

  let jsFromXml = `// If ${xmlStorageVariable} does not exist.

For readability, let's follow the backtick immediately with a newline.
Anything else you can do to make it very explicit this JavaScript is string content, not execution, would help

src/workspacefactory/wfactory_generator.js, line 165 at r7 (raw file):

${xmlStorageVariable}['${groupName}'] =
    ${this.splitXmlWithNewline_(xml)};
/* END ${xmlStorageVariable} ASSIGNMENT. DO NOT EDIT. */`;

Similarly, let's put a newline before the ending backtick.

src/workspacefactory/wfactory_generator.js, line 230 at r7 (raw file):

 * @returns {string} JavaScript code between comments.
 */
WorkspaceFactoryGenerator.prototype.evaluateMarkedCode = function(code) {

Make a TODO to fix the fact that this still runs code outside the markers.

Comments from Reviewable

Review status: 4 of 6 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

src/workspacefactory/wfactory_controller.js, line 379 at r7 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
Escape the ., which has special meaning in a regex. Also, make sure this only matches the end of string.

Done.

src/workspacefactory/wfactory_generator.js, line 258 at r5 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
So you thought....    ;)  (Leaving for future PR.)

Yay(?) for funky input! But yes, my next PR will be the jsunit tests.

src/workspacefactory/wfactory_generator.js, line 157 at r7 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
For readability, let's follow the backtick immediately with a newline.
Anything else you can do to make it very explicit this JavaScript is string content, not execution, would help

Done.

src/workspacefactory/wfactory_generator.js, line 165 at r7 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
Similarly, let's put a newline before the ending backtick.

Done.

src/workspacefactory/wfactory_generator.js, line 230 at r7 (raw file):
Previously, AnmAtAnm (Andrew n marshall) wrote…
Make a TODO to fix the fact that this still runs code outside the markers.

Oops, I forgot to replace code with esc. I think it works now?

Comments from Reviewable

Review status: 4 of 6 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

src/workspacefactory/wfactory_controller.js, line 379 at r7 (raw file):

Also, make sure this only matches the end of string.
Not done.

src/workspacefactory/wfactory_generator.js, line 230 at r7 (raw file):
Previously, chynu (celine choo) wrote…
Oops, I forgot to replace code with esc. I think it works now?

Still executes code. Please add a TODO.

Comments from Reviewable

I'm pretty happy with this structurally, and Andrew is addressing specific style nits or improperly escaped inputs.  We've agreed that you'll make a separate PR adding jsunit to this project, and will add explicit tests for the cases Andrew is bringing up.
One thing for you to keep an eye on in following CLs: Some of the code you're writing (especially for parsing or escaping inputs) looks like utility code, rather than code that's specific to the files it's landing in.  One hallmark of utility code is that it depends entirely on the inputs that are passed to it explicitly, and never uses any members of the object that it's attached to.
When you find that sort of code, considering moving it to a utils.js file.  That will also make it easier to test, because you won't have to instantiate a large object to test a small piece of code.

Reviewed 2 of 7 files at r4, 1 of 3 files at r6.
Review status: 4 of 6 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

Comments from Reviewable

Review status: 4 of 6 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


[CI] Release Workflow

Adds support for manually releasing via a github workflow dispatch.

the uncompressed folder is not included in an encapsulating folder "FluidCorpusManipulation" like the other releases

the uncompressed folder is not included in an encapsulating folder "FluidCorpusManipulation" like the other releases

Hence draft status of PR :P I was testing how tinkerable the workflow_dispatch API was and just wanted to see if it would build from the main branch (instead of dev)

the uncompressed folder is not included in an encapsulating folder "FluidCorpusManipulation" like the other releases

My mistake, what you are seeing is not related to this PR right now. The bin, docs etc should end up in a folder like the other ones for consistency. PR inc.

I got you @tremblap: https://github.com/flucoma/flucoma-cli/pull/22


github page url 404 https://nvidia-holoscan.github.io/holohub/

Hello! I've been reading the holohub documentation of holohub and came across the webpage of holohub doesn't seem to work

Hey @wyli , thanks for checking out HoloHub!
We are in the process of moving away from the nvidia-holoscan.github.io landing page. Links to nvidia-holoscan.github.io should be updated to github.com/nvidia-holoscan/holohub for the time being.
Could you please share the documentation location where you found the broken link? If it was in HoloHub we can fix it, otherwise a workaround is not currently planned.

I see, I found it within this page https://docs.nvidia.com/holoscan/sdk-user-guide/overview.html search 'holohub'.
(a quick search shows urls mostly from holoscan sdk https://github.com/search?q=org%3Anvidia-holoscan "nvidia-holoscan.github.io"&type=code )

Thanks, we will fix those documentation links in our next Holoscan SDK monthly release or sooner. FYI @jjomier

Holoscan SDK v2.6.0 user guide references to HoloHub are fixed and now point to the HoloHub GitHub page: https://docs.nvidia.com/holoscan/sdk-user-guide/index.html
Obsolete HoloHub landing page reference is removed from the GitHub organization README: https://github.com/nvidia-holoscan


Feature request: Gradient improvements

Hi all,
we're experimenting with the gradient feature and we'd like to have the ability to create oblique gradients, similar to the following image

For these we think we may need:

a gravity point
to be able to set "degrees" as directions

The image attached may be created as:

gravity: south west
degrees: 30

Hi @marcoreni!
I'm not sure how gravity can be used to build a gradient. I believe, the ability to use degrees as direction should be pretty enough to build the gradient from your example.

Do you think that start & stop params will be enough?

Exactly

Even better, one less parameter to handle! :)

The latest build allows using degrees (clockwise) as the gradient direction: https://docs.imgproxy.net/latest/usage/processing#gradient
Here's a reproduction of your example with gr:0.8:f00:31:0.62:0.88:


Unable to connect with OAuth packages that doesn't use the standard naming convention

I'm trying to use with your module with gcampax:accounts-dropbox which uses gcampax:dropbox-oauth under the hood. I cannot use this with provided connectWith method, since there is no OAuth module to be found when I pass the name of the package as the argument, eg.:
Meteor.connectWith("gcampax:dropbox-oauth");

Your module's gonna look for Package["gcampax:dropbox-oauth"]["Gcampax:dropbox-oauth"] on this case and it doesn't exists of course.
I created a PR to fix this issue: https://github.com/mondora/mondora-connect-with/pull/5

#5 fixes this. Thanks


allow sampling of posterior outside of prior bounds

currently, sampling from posterior rejects samples outside of the prior bounds (by design, due to leakage), but it may be useful to optionally allow sampling outside of the bounds with a flag in posterior.sample() or as an additional parameter in rejection_sampling_parameters
as discussed with @michaeldeistler

idea: when doing the entire SBI in transformed space, then outside posterior sampling will not be an issue anymore. we would do this by default, and when the user sets it to False we warn and samples might be outside of the prior.

Removing the hackathlon label because we will deal with this after porting to flowtorch

fix: sample from the density estimator directly and set your own rejection bounds.


Serverless: support Ruby v3.3 runtime in the CLI repo

Add support for the Ruby v3.3 runtime to the newrelic-lambda-cli repo

The Ruby PR has been updated to include Ruby v3.3 support.


Off the Hook!

Off the hook message with broken button. im trying to get to the next challenge.
funny I completed this task went to next page. I came back to this page entered

This is a little bit hard to understand. Could you elaborate on what's happening without any html tags?

@RoboMantis thanks for the issue. I've cleaned up your issue message to format correctly.
I was unable to reproduce your issue. The submit buttons and everything work fine for me. Can you add screenshots and more information, such as your browser type? That may help us diagnose the issue for you.

@erictleung I think he talk about to click run button but his code is incorrect. that is why it wont accept to run.  it seem like this issue dont have a bug. since his code is incorrect.
I think he need to reset this challenge then take this challenge again.

Closing as stale.


New Package: SlashedIo.Inssist v16.1.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Does your manifest conform to the 1.0 schema?

Resolves #46024

Microsoft Reviewers: Open in CodeFlow

https://inssist.com/

@wingetbot waivers Add Validation-Domain


Height attribute on img element not working

I was using hyperapp 1.0.1 and this was working

I update to hyperapp 1.1.2 and now it doesn't work, but it does without the "px" like this

Here is the Codepen
So I went and check what changes were made, and apparently, this breaks after the version 1.0.2.
The problem is here on line 138 where before it was always using setAttribute
if (value == null || value === false) {
    element.removeAttribute(name)
} else {
    element.setAttribute(name, value)
}

and now is using
if (typeof value === "function" || (name in element && !isSVG)) {
    element[name] = value == null ? "" : value
} else if (value != null && value !== false) {
    element.setAttribute(name, value)
}

If the element has the attribute and because the image height attribute is an int and not a string it is set to 0.
It's not a big issue you could just write the number without the "px". However, there are people who use the "px" like I was doing and then the whole images on the site disappear. Probably there are similar cases like this with other elements.

@jonlov Oh, very interesting. So the problem is that:
element.setAttribute("height", "100px")

...sets the height to 0?

@mindplay-dk Another use case we forgot to cover?

@jorgebucaran no, setAttribute works just fine. The problem is that
‘’’
element[name] = value == null ? "" : value
‘’’
Sets “100px” to 0. I guess the setAttribute removes the px, but if you set it directly to the object it needs to be an integer.

const img = document.createElement('img')
img.height = 100                    //
img.height = "100"                  //
img.height = "100%"                 //
img.height = "100px"                //
img.setAttribute("height", 100)     //
img.setAttribute("height", "100")   //
img.setAttribute("height", "100%")  //
img.setAttribute("height", "100px") //

HTMLImageElement.height
Is a unsigned long that reflects the height HTML attribute, indicating the rendered height of the image in CSS pixels.
https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement

HTML  element height
The intrinsic height of the image in pixels. In HTML 4, the height could be defined pixels or as a percentage. In HTML5, however, the value must be in pixels.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img

@frenzzy is not a bug, it will still work using it without px or %. However,
 is not the same as

Also, I didn't know what was happening because it was working on hyperapp 1.0.1 and after some research (time wasted), I realize that this was happening. So I think there's going to be people trying to use the % or px and it won't work. In React it does work.
One solution that I think it would be to change this if statement
if (typeof value === "function" || (name in element && !isSVG)) {
// to
if (typeof value === "function" || (name in element && !isSVG && (typeof element[name] === typeof value))) {

or just remove it that line. But I think that
element[name] = value

is better than calling a function in performance. So removing it probably will affect the benchmarks
img.setAttribute("height", 100)

@jonlov Sorry for the inadvertent breaking changes, I honestly didn't realize and since there was no test for this particular issue this happened. Do you know how other libraries handle this? Inferno, Preact, Mithril, etc.

@jorgebucaran not sure how they handle this, never used any of them. I'll have a look and see if I find anything in their source code.

@jorgebucaran I really miss this feature. I need to write a class or style={{height: '100%'}} for every time I want to do a simple height="100%". Are we going to support this?
If we do, would like me to create a PR with the solution in the comment I did before?

@jonlov Sorry, I can't at the moment because I would need to commit to supporting it for life. I need more time to study this and see if there's an alternative or not.

@jorgebucaran that's fine, not rush with this. I need to check if there's a similar case like this with other attributes.

@jonlov how often and under what circumstances are you putting height on images like you describe here? It is something I rarely (if ever) have to do, given the plethora of other ways to achieve the same thing; so I am curious!

@lukejacksonn I don’t use percentages on images that much, but I always used the “px” on all the img tags. So when I updated hyperapp all the images broke and I didn’t know why. In all the frameworks I use this always worked. So I’m not sure if there’s going to be people that are going to get stuck because of this.

Thanks for the explanation. I would usually control the height of images with CSS or inline styles, so would never have noticed!

@jonlov You mentioned that it works in React, can you check if it also works in Preact?

Preact works the same ways as Hyperapp.
Demo: https://codepen.io/frenzzy/pen/MVvrZm?editors=0010

I don't think we should change this. cc @frenzzy?

Agreed


FakeAIOKafkaProducer need stop function

When I use mockafka-py to write tests, I encountered the following error:
AttributeError: 'FakeAIOKafkaProducer' object has no attribute 'stop'.
Here is my code(I referred to this document.):
from aiokafka import AIOKafkaProducer
import asyncio

async def send_one():
    producer = AIOKafkaProducer(
        bootstrap_servers='localhost:9092')
    # Get cluster layout and initial topic/partition leadership information
    await producer.start()
    try:
        # Produce message
        await producer.send_and_wait("my_topic", b"Super message")
    finally:
        # Wait for all pending messages to be delivered or expire.
        await producer.stop()

I think FakeAIOKafkaProducer should have a stop function if I want to use mockafka to write a test for aiokafka.

fixed inv0.1.56


fix: Backport opentelemetry 0.18 code from main repo

Motivation
I noticed that this repo got the cut-off before opentelemetry 0.18 was committed into the main repo so I tried to backport what was there.
Solution
This is pretty much a backport from the code that @jtescher did on the main repo.
Let me know if you see something wrong, I tried to adapt the rejections the best way possible.
This fix #8

Note that opentelemetry 0.19 has been released yesterday.

@djc I've tested 0.19 with this PR, and it seems to work fine but, as this is a backport from another author, I didn't want to change the code in this PR as I don't “own” it

Thanks for doing this PR! Sorry for the delay in reviewing this.

I've tested 0.19 with this PR, and it seems to work fine but, as this is a backport from another author, I didn't want to change the code in this PR as I don't “own” it

I think that for clarity of commit history, we should make upgrading to opentelemetry 0.19 a separate PR.

Any chances this gets merged soon? I'd like to use some features present in opentelemetry 0.19.0 together with tracing-opentelemetry.

@jaysonsantos, looks like examples/opentelemetry.rs needs to be updated as well to use opentelemetry_jaeger::new_agent_pipeline() instead of opentelemetry_jaeger::new_pipeline() in order to fix the above checks?
I'm eager to see this merged too (as well as the update for opentelemetry 0.19).  If there is anything I can do to help, please let me know...  Thanks for shepherding this!

@davidbarsky @jtescher do you mind taking a look on the latest commit?

@davidbarsky @jtescher do you know when you'll be able to take a look at this? I'm wondering if I should wait or use a temporary fork

Thanks @jaysonsantos!


Node.js debugging does not work

Hello dear vscode team. Thank you for the fantastic IDE. Unfortunately I have an issue with the latest version when I am trying to debug node.js apps written in typescript.
My launch.json:
{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "node",
			"request": "attach",
			"name": "Attach by Process ID",
			"processId": "${command:PickProcess}"
		},
		{
			"name": "Launch TypeScript",
			"type": "node",
			"request": "launch",
			"runtimeArgs": [
				"-r",
				"ts-node/register"
			],
			"args": [
				"${workspaceFolder}/src/index.ts"
			],
			"cwd": "${workspaceRoot}",
			"sourceMaps": true,
			"internalConsoleOptions": "openOnSessionStart",
			"env": {
				"TS_NODE_FILES": "true"
			}
		}
	]
}

The issue I am experiencing is that most of the times breakpoints are not hit or it seems that the debugger stops at some breakpoint but it is inside an async_hook.js file at not at my code.

VSCode Version: 1.31.1
OS Version: macOS

Have similar issue when using babel with inline sourcemaps, I cannot set correct breakpoints, seems like inline sourcemaps are being ignored

Please try updating to 1.32, which fixed an issue with ts-node


crash after several seconds (malloc(): memory corruption)

Hey,
i am running this node on my Jetson TX2. After some seconds i get this crash error:

*** Error in `/home/nvidia/catkin_ws/devel/lib/darknet_ros/darknet_ros': malloc(): memory corruption: 0x00000001007389c0 ***

and sometimes this:

*** Error in `/home/nvidia/catkin_ws/devel/lib/darknet_ros/darknet_ros': free(): invalid next size (normal): 0x00000000006f7000 ***

any idea?

Hi, could you please set up AlexeyAB repo and run the same model without ROS code and check if the error still presists.

Also, are you running with Optical Flow enabled? Is the OpenCV3 package for ROS installed?

These errors basically occur in the case of memory overflow, writing to unallocated memory and reading it.
Also referencing this issue - AlexeyAB Issue - 1628#

@pushkalkatara thanks for your help. i will test it asap.

Hi! Except for "malloc" and "free" problems, I also met
[darknet_ros-1] process has died [pid 13109], exit code -11

I am quite confused about this problem. I am running this package on tx2 with a Intel Realsense Camera D415. By the way, could you please tell me how can I run with Optical Flow enabled?

Hi @DeepDuke, exit code -11 basically occurs due to segmentation fault-invalid memory access.

Did the node die immediately after roslaunch?
Is the weight, config files pointed to the correct directory?

optical flow would work if you have opencv-contrib ros package installed.

Hi@pushkalkatara The node died after running for about 3 minutes. I think I have put the weight and config files into the correct directory.

@DeepDuke if the node ran for 3 minutes with detection, then weights and config directory seems fine.
While running the node, use System Monitor to see Memory and Swap History. Please paste the results here if the memory usage increases with time or constant.
Try adding swap memory and re-running the node.

@pushkalkatara I run the node on NVIDIA Jetson TX2.  When i ran yolo3, the memory increased from 3.49G/7.67G to 4.50G/7.67G. It keeped at 4.50G/7.67G until the node died. The swap was always 0k/0k.
I also tried yolov3-tiny. When i run yolo3-tiny, the memory rised from 3.49G/7.67G to 3.72G/7.67G. When the ndoe died, the memory returned to 3.49G/7.67G.  The swap still keepd unchanged at 0k/0k.

@pushkalkatara BTW, yolo3-tiny could only run for less than a minute.

@DeepDuke how much time did it sustain 4.50G/7.67G until the node died?

@pushkalkatara about 2-3 minutes for yolo3, less than a minute for yolo3-tiny

Hello, not sure if related but i got a similar issue. As soon as Yolo detect an object and the tracking starts it crashes. GDB gave the following infos:
Thread 1 "darknet_ros" received signal SIGSEGV, Segmentation fault. darknet_ros::YoloROSTracker::trackThread (this=this@entry=0x7fffffffc130)     at /home/nico/catkin_ws/src/darknet_ros/darknet_ros/src/YoloROSTracker.cpp:217 217                 it->frames_counter = temp; (gdb) bt #0  darknet_ros::YoloROSTracker::trackThread (this=this@entry=0x7fffffffc130) at /home/nico/catkin_ws/src/darknet_ros/darknet_ros/src/YoloROSTracker.cpp:217 #1  0x00007ffff7822378 in darknet_ros::YoloROSTracker::YoloROSTracker (this=0x7fffffffc130, nh=...) at /home/nico/catkin_ws/src/darknet_ros/darknet_ros/src/YoloROSTracker.cpp:24 #2  0x00000000004058b7 in main (argc=1, argv=0x7fffffffc728) at /home/nico/catkin_ws/src/darknet_ros/darknet_ros/src/yolo_object_detector_node.cpp:15

Hi @NicolasBernard456 . Here are some steps for debugging -

Using which ROS package are you reading the camera feed?
Please use video_stream_opencv package for the same.
Is the cfg file correct?

@pushkalkatara
Thanks for the work you did, the code doesn't work on my computer and TX2. When I run the code "roslaunch darknet_ros darknet_ros.launch", the result is as follows. And there is no detection window, just the result under the terminal.
[ INFO] [1571276131.857562415]: Published
[ INFO] [1571276131.857801241]: Published
[ INFO] [1571276131.857998518]: Started darknet thread
[ INFO] [1571276131.858011827]: Reference Count > 0
[ INFO] [1571276131.858044404]: Published
[ INFO] [1571276131.858184366]: Inside tracking
[darknet_ros-1] process has died [pid 10361, exit code -11, cmd /home/jgx/catkin_ws/devel/lib/darknet_ros/darknet_ros __name:=darknet_ros __log:=/home/jgx/.ros/log/05036024-f07e-11e9-8718-983f9f190824/darknet_ros-1.log].
log file: /home/jgx/.ros/log/05036024-f07e-11e9-8718-983f9f190824/darknet_ros-1*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done
I found that the program will be killed immediately if the camera moves.I use the usb_cam package.I want to know how can solve this problems.thanks

您好，不确定是否相关，但我遇到了类似的问题。一旦Yolo检测到物体并开始跟踪，它就会崩溃。GDB提供了以下信息：
Thread 1 "darknet_ros" received signal SIGSEGV, Segmentation fault. darknet_ros::YoloROSTracker::trackThread (this=this@entry=0x7fffffffc130) at /home/nico/catkin_ws/src/darknet_ros/darknet_ros/src/YoloROSTracker.cpp:217 217 it->frames_counter = temp; (gdb) bt #0 darknet_ros::YoloROSTracker::trackThread (this=this@entry=0x7fffffffc130) at /home/nico/catkin_ws/src/darknet_ros/darknet_ros/src/YoloROSTracker.cpp:217 #1 0x00007ffff7822378 in darknet_ros::YoloROSTracker::YoloROSTracker (this=0x7fffffffc130, nh=...) at /home/nico/catkin_ws/src/darknet_ros/darknet_ros/src/YoloROSTracker.cpp:24 #2 0x00000000004058b7 in main (argc=1, argv=0x7fffffffc728) at /home/nico/catkin_ws/src/darknet_ros/darknet_ros/src/yolo_object_detector_node.cpp:15

I have the same problems with you,did you have solve it?  As soon as Yolo detect an object it crashes:[darknet_ros-1] process has died [pid 4547, exit code -11...


Masternode "status": "WATCHDOG_EXPIRED"

I have all time the error "status": "WATCHDOG_EXPIRED"
we need sential for the goacoin wallet can you set it please

First check your master using the command
./goacoin-cli masternode status
Despite status of the "WATCHDOG_EXPIRED" node works and receives reward.
This be solved after transition most of participants to new version wallet.


JWM should select the icon with the most appropriate resolution

JWM uses the icons from the _NET_WM_ICON property set on the window for both the taskbar and title bar.  There can be multiple icons set with differing resolutions.  Currently, JWM just uses the first icon.  JWM should select the icon with the most appropriate resolution.
Additionally, JWM should set more appropriate values for XSetIconSizes.

JWM now requests the size of the icon that would be displayed in the title bar.  It could probably also do this for task bar icons, etc., but I think that's probably more work than it's worth.


python312Packages.polyswarm-api: 3.7.0 -> 3.8.0

Diff: https://github.com/polyswarm/polyswarm-api/compare/refs/tags/3.7.0...3.8.0
Changelog: https://github.com/polyswarm/polyswarm-api/releases/tag/3.8.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 323559 run on x86_64-linux 1

6 packages built:

malwoverview
malwoverview.dist
python311Packages.polyswarm-api
python311Packages.polyswarm-api.dist
python312Packages.polyswarm-api
python312Packages.polyswarm-api.dist


Release version 2.2.0

:warning: DO NOT MERGE (YET) :warning:
PR for tracking changes for the 2.2.0 release. Target release date: Monday November 11.

[x] Check if the minimum WP version property needs updating and if so, action it - PR #1829
[x] Check if the DeprecatedFunctions and the other deprecated WP feature sniffs need updating and if so, action it - #1809, #1810
[ ] Add changelog for 2.2.0 - PR #1833
[ ] Merge this PR
[ ] Add release tag against master (careful, GH defaults to develop!) & copy & paste the changelog to it
[ ] Close the 2.2.0 milestone
[ ] Open a new milestone for the next release
[ ] If any open PRs/issues which were milestoned for 2.2.0 do not make it into the release, update their milestone. (not applicable)
[ ] Tweet about the release.
[ ] Post about it in Slack.
[ ] Submit for "Month in WordPress": https://make.wordpress.org/community/month-in-wordpress-submissions/
~Open PR to merge master into develop to get rid of the This branch is out-of-date with the base branch messages on each release. (only after major releases)~

@WordPress/wpcs Could I have some approval(s) please ?

Release tweet: https://twitter.com/jrf_nl/status/1193875824832843778


How can I render an array of data taken from database?

Hi @jerosoler ,
First of all, I really like your project!
I'm learning and planning to use the Drawflow library in my vue 2 project.
But I am wondering is there a way to calculate and render the positions of nodes of an array of data retrieved from the DB.
Example:

Hello,
All nodes are added with an X,Y position.
If you know the child nodes and the parent nodes, I think you will be able to calculate the distance well. And the size of the nodes.
There is currently no automatic way to do this.
Another way is to move the node via javascript once it is mounted:

https://github.com/jerosoler/Drawflow/issues/112

Thank you,
So is there a way to get data from that array to assign to component then pass that component to node?
I don't know how to pass a react component to node.
Can you tell me how to do that?

So is there a way to get data from that array to assign to component then pass that component to node?

That is depends on how you extract the data from your DB

I don't know how to pass a react component to node.

There is no react wrapper for now.
But you can see examples of react.

#290
#21

Thank you so much!


Add a placeholder page for transfer history

We don't have the indexer setup yet, but we can already start working on the placeholder page for the transfer history.
The page should be reachable from the transfer page and look like:
From    | To |Currency | Amount  | (incoming/outgoing icon)
-----------------------------------------------------------------
Name    | Name        | Leu    | 0.005 | arrow-up/ arrow-down
Adreess | Addreess
--------------------------------------------------------------------

If we have a name in the address book, we display the name and address otherwise only the address.
More description to come

If we show tx history for the currently active address, one side is always redundant info. I suggest to only show the sender/reciepent other than self

Yeah, makes sense, we display the arrow-up/down icon anyhow, which indicates clearly the direction. I agree, it is probably more readable with only one address. Maybe like this:
From/To |Currency | Amount  | (incoming/outgoing icon)
-----------------------------------------------------------------
Name        | Leu    | 0.005 | arrow-up/ arrow-down
Addreess
--------------------------------------------------------------------


Fixes issue #354: windows installer seems to be buildable

@mondain I'm not sure if the installer will work or not, but built errors were fixed :)

Thanks Max! Long time since you came around, hope all is well.

Thanks Paul, life goes on :)
Just have noticed v2.0.4 has no tar.gz artifact, Is it by mistake or all subsequent releases will have only zip? :)

@solomax I just didn't add it that day, 2.0.x isn't really ready for anyone but me at the moment; once its good enough for the public, I'll drop all the artifacts in.

OK :)
The installer depends on tar.gz so I need one to get green build :) (and need to invent good trigger for the Jenkins job :)))


Fix starting container with HostConfig was deprecated since v1.10

starting container with HostConfig was deprecated since v1.10 and removed in v1.12
by removing options that are regarded as HostConfig to the container creation section instead of container launching section

added a minor comment. looks good otherwise!

3.0.0 - thanks!

Btw do you want to help maintain this project? I can add you as an owner if you want.

Sure, why not.
Thanks for your contributions so far as well.
2016-11-21 12:34 GMT-02:00 Mathias Buus<EMAIL_ADDRESS>
Btw do you want to help maintain this project? I can add you as an owner
if you want.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mafintosh/docker-run/pull/11#issuecomment-261954120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6pfmy2ZmzpmALGSrNbqx_0-BaKwnIiks5rAawMgaJpZM4KqipT
.