Further filter bank/tag tabs on equippables and maybe others?

A lot of people have tag tabs for a certain activity, e.g. a boss or a slayer task. It would be a nice QOL to have an option to filter for equipables and non-equipables, such that you can withdraw the equipables, close the bank, equip them, and then reopen the bank to put the rest of the stuff in your inventory. There are probably better ways than my mock-up, but it's just an idea.

This will likely be pretty easy to implement after Jagex adds the ability to equip items from the bank interface. I would suggest any potential contributors not consider this feature until that point.

It's live now! It would be great that if the filter for equippables were enabled, equip would be the left-click option.

https://i.gyazo.com/486ba7aa723bd3007b1f69c62c1a7693.gif

This is possible: https://youtu.be/piMEOkKW-bA . Now I actually need to look at Jagex's rules for 3PC to see what is allowed. Again, this is still a POC.

According to this list: https://oldschool.runescape.wiki/w/Update:Another_Message_About_Unofficial_Clients
the only questionable thing would be "Modifies the menu options on worn/equipped items". However, these items are still in the inventory and are not worn, so the menu entry swapping should in theory be fine. I need to port some code and then it's ready for feedback. I also need some feedback on what the button should look like, where it should be placed and preferably some sprites I can use for it. I couldn't come up with anything better myself at the moment.


Buy from merchant modifier cannot go above 100

Hi,
Is your feature request related to a problem? Please describe.
It's frustrating to have to go through and update every item in a merchant's inventory when I want them to double the listed price of an item.
Describe the solution you'd like
The "Buy from Merchant modifier" menu should allow any number to be entered, not just up to 100
Describe alternatives you've considered
change every item individually

You can go in the merchant settings and set the percentage limit for the merchant.

So you can. A tooltip within the "Buy from Merchant modifier" explaining that feature would be helpful. thanks!


Add links to demos running in GitHub Pages

This fixes #52 by adding links to the two examples live running in the browser using
GitHub Pages (https://codingtrain.github.io/Toy-Neural-Network-JS).

XOR problem
Handwritten digit recognition

Wonderful, thank you! I should also link to the corresponding video tutorials as well (when they are ready).


Reconnect after db reboot not possible

We have applications, which were not able to reconnect to the db, after the db server has been rebooted during an outage (lasted several hours).
Problem: Applications only reconnected after application restart.
We got the following exception:
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 10000ms.
When we turn down the db instance in a friendly way, applications reconnect at once, after we restart the db instance.
So, do we miss any configuration or other hints?
Environment
HikariCP version: 2.6.2
JDK version     : 1.8
Database        : PostgreSQL
Driver version  : 9.4.1212
SpringBoot      : 1.5.8

Config
datasource:
  default:
    jdbcUrl:
    minimum-idle: 8
    maximum-pool-size: 100
    idle-timeout: 10000
    connection-timeout: 10000
    max-lifetime: 120000

Just to save the trouble of scanning through the PostgreSQL driver release notes, the Connection.setNetworkTimeout() was released in version 42.2.0 of the driver (https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.0)

And to further save trouble searching for an answer on configuring these properties, use something like the following:
spring:
  datasource:
    hikari:
      connection-timeout: 10000
      idle-timeout: 10000
      pool-name: foobar
      max-lifetime: 120000
      maximum-pool-size: 10
      minimum-idle: 8
      data-source-properties:
        currentSchema: foobar
        networkTimeout: 120000
        socketTimeout: 60

See also https://www.theguardian.com/info/2019/dec/02/faster-postgresql-connection-recovery.
NB: the above shouldn't be considered recommended values. YMMV.


[GenericPoseGraph]: How could I forget it?! Facepalm.

@wally-the-cartographer merge

Merge requested by authorized user pifon2a. Merge queue now has a length of 1.


Uri property cannot be reconfigured programmatically

I need to configure the target's uri and index in the code.
     var target = LogManager.Configuration.FindTargetByName(targetName);
     var elasticTarget = target as NLog.Targets.ElasticSearch.ElasticSearchTarget;

	if (elasticTarget != null)
	{
	elasticTarget.Uri = uri;
	elasticTarget.Index = index;
        }

This code works on the index property but the uri property doesn't affect the target.
In ElasticSearchTarget.cs the _uri member is used only in InitializeTarget, changing the uri property doesn't force it to re-calculate node and the connection pool so it cant be changed using code.

You can do this while waiting for your PullRequest:
NLog.LogManager.Configuration = NLog.LogManager.Configuration; // Reload

You can do this while waiting for your PullRequest:
  var target = LogManager.Configuration.FindTargetByName(targetName);
     var elasticTarget = target as NLog.Targets.ElasticSearch.ElasticSearchTarget;

	if (elasticTarget != null)
	{
	elasticTarget.Uri = uri;
	elasticTarget.Index = index;
        }
  NLog.LogManager.Configuration = NLog.LogManager.Configuration; // Reload

See also: https://github.com/NLog/NLog/wiki/Reinitialize-NLog-configuration

Thanks! :)

Should we consider Username  and Password flelds as well?

Should we consider Username and Password flelds as well?

Might be useful for all the properties that are used in creating the _client (Uri, ElasticSearchSerializer, RequireAuth, Username, Password, DisableAutomaticProxyDetection, DisablePing, EnableHttpCompression)

@markmcdowell Resolved by #101 ?


Fix fallback slowdowns and warnings

Ok the NullReferenceException is gone ;)

@7sharp9 See I give mono a try every time. But they still have not fixed some boringssl bug in 4.2.0. Our test suite is still red:

https://travis-ci.org/fsprojects/Paket/jobs/266117377

-> Source 'https://www.nuget.org/api/v2' yielded no results
	-  Request 'https://www.nuget.org/api/v2/FindPackagesById()?semVerLevel=2.0.0&id='Fody'' finished with error
	-> Could not retrieve data from 'https://www.nuget.org/api/v2/FindPackagesById()?semVerLevel=2.0.0&id='Fody''
	-> HttpRequestException: An error occurred while sending the request
	-> WebException: Error: TrustFailure (Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
	     at /build/mono-<IP_ADDRESS>/external/boringssl/ssl/handshake_client.c:1132)
	-> MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
	     at /build/mono-<IP_ADDRESS>/external/boringssl/ssl/handshake_client.c:1132
	-  Request 'https://www.nuget.org/api/v2/Packages?semVerLevel=2.0.0&$filter=Id eq 'Fody'' finished with error
	-> Could not retrieve data from 'https://www.nuget.org/api/v2/Packages?semVerLevel=2.0.0&$filter=tolower(Id) eq 'fody''
	-> HttpRequestException: An error occurred while sending the request
	-> WebException: Error: TrustFailure (Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
	     at /build/mono-<IP_ADDRESS>/external/boringssl/ssl/handshake_client.c:1132)
	-> MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
	     at /build/mono-<IP_ADDRESS>/external/boringssl/ssl/handshake_client.c:1132

And this is nothing about certificates, because it fails at random packages for random tests and sometimes the testsuite even runs, see https://travis-ci.org/fsprojects/Paket/builds/266107420 where it run 2/3 times.
Maybe they should consider running the paket integration-test-suite before releasing a new version?


Adjust CSB cred

Set Issuer DID for cred def allowance to schema owner

The changes look good but the definition of issuer_did and author_did in the context of the credential_definition rules is not well defined in the documentation which leads to confusion.
Created a ticket for this; https://github.com/hyperledger/aries-endorser-service/issues/146

@loneil feel free to merge this if/when the configuration is applied to dev (I think it is already there, but waiting for confirmation).


Cross origin requirements for godot 4 in the browser

Godot 4 now requires cross origin isolation and SharedArrayBuffer for web build servers, which can be tricky to setup on popular static website hosting platforms like netlify and itch.io, which you can still deal with, but specially github pages Trying to deploy with the current example actions will cause:

I have a workaround for that but still waits way too long to load for a very simple game (Not sure if it is related to that):
    name: "godot-ci export"
on: push

env:
  GODOT_VERSION: 4.0.3

jobs:
  export-web:
    name: Web Export
    runs-on: ubuntu-20.04
    container:
      image: barichello/godot-ci:4.0.3
    steps:
      - name: Checkout
        uses: actions/checkout@v2
        with:
          lfs: true

      - name: Setup
        run: |
          mkdir -v -p ~/.local/share/godot/export_templates
          mv /root/.local/share/godot/templates/${GODOT_VERSION}.stable ~/.local/share/godot/export_templates/${GODOT_VERSION}.stable
      - name: Web Build
        run: |
          mkdir -v -p build/web
          godot -v --headless --export-release "Web" build/web/index.html
      - name: Install rsync 📚
        run: |
          apt-get update && apt-get install -y rsync curl
      - name: Patch for Cross Origin Isolation and SharedArrayBuffer
        run: |
          cd build/web/
          curl https://raw.githubusercontent.com/josephrocca/clip-image-sorter/92b108dc670d0b56bd6b72963b0e86c4c862412e/enable-threads.js --output enable-threads.js
          sed -i 's|headers.set("Cross-Origin-Embedder-Policy", "credentialless")|headers.set("Cross-Origin-Embedder-Policy", "require-corp")|g'  enable-threads.js
          sed -i 's|<script src="index.js"></script>|<script src="enable-threads.js"></script><script src="index.js"></script>|g' index.html
      - name: Upload Artifact
        uses: actions/upload-artifact@v1
        with:
          name: web
          path: build/web
      - name: Deploy to GitHub Pages 🚀
        uses: JamesIves/github-pages-deploy-action@v4
        with:
          folder: build/web # The folder the action should deploy.

https://github.com/orgs/community/discussions/13309
https://github.com/godotengine/godot/issues/70691

I have a workaround for that but still waits way too long to load for a very simple game (Not sure if it is related to that):

On macOS, this is due to an upstream issue: https://github.com/godotengine/godot/issues/70691


Add hoarder-bookmark extension

Description
A user-friendly Raycast extension that seamlessly integrates with Hoarder, bringing powerful bookmark management to your fingertips. Quickly save, search, and organize your bookmarks, texts, and images—all through Raycast's intuitive interface.
This extension leverages Hoarder's API to provide a streamlined experience for managing your digital collection, complete with AI-powered tagging and search capabilities.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi 👋
Thanks for your contribution 🔥
Did you see this extension before creating this one?

Hi! Yes, I reviewed the Hoarder extension before developing this one. While there's an existing extension that provides basic list functionality, I saw an opportunity to create a more comprehensive solution with proper documentation following Raycast's guidelines.
This new extension offers a complete Hoarder integration experience with full CRUD operations, tag management, and AI features, along with a more polished UI that closely follows Raycast's design principles. I've also documented everything thoroughly to help users get started easily.
I've reached out to the Hoarder project maintainer about this extension, and they've shown their support by starring the project, which I believe validates its value to the ecosystem.
Let me know if you'd like to know more about any specific aspects!

It still sounds like an enhancement instead of another version of the same extension with more capabilities
@kdurek What do you think?

Hey, yeah I waited for better enhancements to rest api from maintainer of hoarder, but this one does really good upgrades to my extension functionality so feel free to do whatever seems best for both extensions, including replacing my own :D

So @kdurek, do I understand this correctly?
We're letting this completely overwrite yours, and then we'll move you to contributors instead (if you'd still like that) 😊

That's what I wanted to propose, wanted to leave me in history of extension or something but didn't know it's possible :D Don't mind this replacing my extension, it seems really good upgrade!

@foru17 so what we're going to do is that you move your code to overwrite the current (extensions/hoarder/)
Can we use the same preferences so the end user is not interrupted, is that possible?

@foru17 Thank you for your kind attitude and words ❤  Hope I will be able to help or contribute in future!

You just add below to the package.json somewhere (I use to have it under "author":
"contributors": [
  "kdurek"
],

I've published the changes using npx @raycast/api@latest publish which automatically created PR #15810.
This PR moved the code to replace the original hoarder extension and made the preference fields compatible.
Just want to confirm - is this the right process, or should I have done something differently?

Closing in favor of https://github.com/raycast/extensions/pull/15820


Speed Improvement: Make incoming entities Arc like schema entities

Description of changes
This provides a 3x speedup based on local benchmarking with a large schema that has big action entity hierarchy relationships. Today Entities.entities is a HashMap of <EntityUID, Entity>. When from_entities brings in the entities and actions from a given schema, it currently relies on Arc::unwrap_or_clone, which frequently ends up being clone. For a large set of very interrelated Actions, this repeated clone becomes expensive.
Changing Entities.entities to be a HashMap of <EntityUID, Arc<Entity>> allows us to keep the clone cheap, and Arc'ing the incoming Entities becomes cheap as well.
Changing the interface of the HashMap means altering what create_entities_map returns, adding an implementation of TCNode for Arc<Entity>, and udpating how IntoIterator works to return values from the Arc's.
Issue #, if available
This contributes to 1285.
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[x] A change "invisible" to users (e.g., documentation, changes to "internal" crates like cedar-policy-core, cedar-validator, etc.)

I confirm that this PR (choose one, and delete the other options):

[x] Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

[x] Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.

I confirm that docs.cedarpolicy.com (choose one, and delete the other options):

[x] Does not require updates because my change does not impact the Cedar language specification.

Thanks for this work!

Protobuf tests updated to use Arc wrapped entities in 857509b.


python312Packages.pycrdt: 0.10.3 -> 0.10.4

Things done
Changelog: https://github.com/jupyter-server/pycrdt/releases/tag/0.10.4
cc @Nixos/jupyter

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] 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

[x] 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

[x] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 350215

x86_64-linux

:white_check_mark: 16 packages built:

python311Packages.jupyter-collaboration
python311Packages.jupyter-collaboration.dist
python311Packages.jupyter-ydoc
python311Packages.jupyter-ydoc.dist
python311Packages.pycrdt
python311Packages.pycrdt-websocket
python311Packages.pycrdt-websocket.dist
python311Packages.pycrdt.dist
python312Packages.jupyter-collaboration
python312Packages.jupyter-collaboration.dist
python312Packages.jupyter-ydoc
python312Packages.jupyter-ydoc.dist
python312Packages.pycrdt
python312Packages.pycrdt-websocket
python312Packages.pycrdt-websocket.dist
python312Packages.pycrdt.dist

aarch64-linux

:white_check_mark: 16 packages built:

python311Packages.jupyter-collaboration
python311Packages.jupyter-collaboration.dist
python311Packages.jupyter-ydoc
python311Packages.jupyter-ydoc.dist
python311Packages.pycrdt
python311Packages.pycrdt-websocket
python311Packages.pycrdt-websocket.dist
python311Packages.pycrdt.dist
python312Packages.jupyter-collaboration
python312Packages.jupyter-collaboration.dist
python312Packages.jupyter-ydoc
python312Packages.jupyter-ydoc.dist
python312Packages.pycrdt
python312Packages.pycrdt-websocket
python312Packages.pycrdt-websocket.dist
python312Packages.pycrdt.dist

x86_64-darwin

:white_check_mark: 16 packages built:

python311Packages.jupyter-collaboration
python311Packages.jupyter-collaboration.dist
python311Packages.jupyter-ydoc
python311Packages.jupyter-ydoc.dist
python311Packages.pycrdt
python311Packages.pycrdt-websocket
python311Packages.pycrdt-websocket.dist
python311Packages.pycrdt.dist
python312Packages.jupyter-collaboration
python312Packages.jupyter-collaboration.dist
python312Packages.jupyter-ydoc
python312Packages.jupyter-ydoc.dist
python312Packages.pycrdt
python312Packages.pycrdt-websocket
python312Packages.pycrdt-websocket.dist
python312Packages.pycrdt.dist

aarch64-darwin

:white_check_mark: 16 packages built:

python311Packages.jupyter-collaboration
python311Packages.jupyter-collaboration.dist
python311Packages.jupyter-ydoc
python311Packages.jupyter-ydoc.dist
python311Packages.pycrdt
python311Packages.pycrdt-websocket
python311Packages.pycrdt-websocket.dist
python311Packages.pycrdt.dist
python312Packages.jupyter-collaboration
python312Packages.jupyter-collaboration.dist
python312Packages.jupyter-ydoc
python312Packages.jupyter-ydoc.dist
python312Packages.pycrdt
python312Packages.pycrdt-websocket
python312Packages.pycrdt-websocket.dist
python312Packages.pycrdt.dist

@ofborg eval

Evaluation has succeeded. This should be good to go now.


[2.1.8] Error reading from pyproject.toml: No such file

Steps to replicate:

Download Aniworld using the .whl file from the newest release
Search for an Anime using the interactive menu

2024-10-27 19:08:01 - ERROR - get_version_from_pyproject - Error reading version from pyproject.toml: [Errno 2] No such file or directory: 'C:\\Users\\mikah\\AppData\\Local\\Programs\\Python\\Python312\\Lib\\site-packages\\aniworld\\common\\../../../pyproject.toml'

You're actually the fastest person i've ever seen on GitHub!
Fixed with commit a0ad947

Hi Mika,
sorry it doesn't work yet, I haven't fixed it yet.

I didn't realize it was an issue with the whl file. When i saw the commit i git cloned, tried it and it worked.

Hi Mika,
I've fixed the version bug, and the coming .whl files should work now.
Still, I'd recommend using pip install aniworld to install it directly from PyPI.


Add empty workspace to Cargo.toml

This fixes an issue that arises when the package is installed with pre-commit into a cache directory that is itself a subdirectory of a Cargo workspace, making Cargo think it's a package that should have been a part of the parent workspace.
An unexpected error has occurred: CalledProcessError: command: ('/usr/local/cargo/bin/cargo', 'install', '--bins', '--root', '/builds/project/.cache/pre-commit/repot501w21b/rustenv-system', '--path', '.')
return code: 101
stdout: (none)
stderr:
    error: current package believes it's in a workspace when it's not:
    current:   /builds/project/.cache/pre-commit/repot501w21b/Cargo.toml
    workspace: /builds/project/Cargo.toml

    this may be fixable by adding `.cache/pre-commit/repot501w21b` to the `workspace.members` array of the manifest located at: /builds/project/Cargo.toml
    Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.
Check the log at /builds/project/.cache/pre-commit/pre-commit.log

This breaks the various integration tests because there are child crates used for test data, if you fix all of them I'll merge this.

This now passes tests locally for me


Property 'find' does not exist on type

"typescript": "^3.2.2"
Search Terms: Property 'find' does not exist on type
Code
https://github.com/mariohmol/gherkin/blob/master/index.ts#L17
const found = c.students.find(s => s === student);

Running tsc index.ts
Config:
https://github.com/mariohmol/gherkin/blob/master/tsconfig.json#L8
Expected behavior: Compile sucessfully
Actual behavior:
https://travis-ci.org/mariohmol/gherkin/jobs/481149988#L446
index.ts:17:34 - error TS2339: Property 'find' does not exist on type 'Student[]'.

17         const found = c.students.find(s => s === student);

Playground Link: https://github.com/mariohmol/gherkin
Related Issues: https://github.com/Microsoft/TypeScript/issues/6945

Try  run:
  npm install @types/node --save-dev

in your project.


bepasty: add secretKeyFile option

This gives users the option to store the secret key outside the world-readable Nix store.
This is part of: https://github.com/NixOS/nixpkgs/issues/24288.

@basvandijk thanks for looking after it. If i understand the code correctly then this breaks backwards compatibility, right? secretKey will no longer be used. Because the secretKey argument in Bepasty is only the seed for generating safe session cookies ( http://bepasty-server.readthedocs.io/en/latest/quickstart.html#bepasty.config.Config.SECRET_KEY ) i'd rather have a fallback mechanism, e.g. if secretKeyFile is unset use secretKey.
If this is too much of an effort then we should at least make secretKey obsolete.

Thanks, looks good.


Out-RsFolderContent needs additional feature(s)

I am working with Server 2016/PowerShell 5.1
I am trying to write a unified script to migrate a whole environment using the ReportingServicesTools.
One of the first problems I see is the fact that the existing credentials for the data sources are not being exported.  Due to this, even though I can re-import the data sources, I still have to go into the GUI to reattach them.  I would like the ability to export the security and then reimport it so the datasources would be live assuming the same connecting database was in place on the new server.
I looked at the .XML and I don't see a field that would export that security.

SQL
Data Source=LocalHost; Initial Catalog=WideWorldImporters;
False
False
Store
False
False
reportadmin
True
I looked at the raw code for both Out-RsFolderContent and Out-RsCatalogItem and did not see a part that would allow this.
Thank you.  I'm happy to look further, but I need to know where to go...

Our APIs don't expose the credentials in any way, for the scenario of migrating a entire environment the best approach will be restoring the catalog database in the new environment


[NDM][NDMII-1992] add a test to check metadata tags

What does this PR do?
Add a check on the metadata tags for unreachable devices
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

/merge

/merge


updating FAQ's

updating FAQ's

[x ] Tested Locally

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Expire experiment picks when user hasn't been seen for 1 day

Only downloads outcome data when starting a new session
Uses quicktype to validate types when serializing to localStorage

Fixes #25

Not sure if we should manually store outcome data if our S3 cache headers also guarantee that we don't redownload outcomes too frequently.


ssr based on spa and backup

we can build spa using react react-router and packup. if is possible to function render that take pathname as input and return html string, we can use std/http (or oak ...) to read pathname in the incoming request then call render function and return html response.
render function will be generated based on router at build time.
if this possible we can build universal app on top of spa and packup in easy way.

Thank you for the feedback.
Do you suggest any specific feature to add to packup?

ssr, I know packup focusing on spa but think the brindge between is not big.
already we have renderToSring in react router is possible to use it with packup ?
and suggess to create x/packup-react and x/packup-react-router verion of react and react-router (like in esm.sh ) build for deno users in mind and ts support.
we can discus more about puckup-ssr in right time
thank you for your great job.


Black bar issue if YPConfig.onlySquareImagesFromCamera = false

Ignore cropping video to square if YPConfig.onlySquareImagesFromCamera = false to solve black bar issue.

@priyakhambhayta Check differences please. Something wrong there.

Implemented 46abe699ec11a7d32898f3cddb64d98fee32e8cf
Thx for help!


git tokens required, no longer accepting username and passwords.

It wants my git tokens? Can I bypass this please?
remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/thelinuxchoice/instainsane.git/'
./install-sb.sh: line 19: cd: instainsane: No such file or directory
chmod: cannot access 'instainsane.sh': No such file or directory
chmod: cannot access 'install.sh': No such file or directory
sudo: ./install.sh: command not found
Cloning into 'tweetshell'...
Username for 'https://github.com': n1t3m0dular
Password for<EMAIL_ADDRESS>remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/thelinuxchoice/tweetshell.git/'
./install-sb.sh: line 26: cd: tweetshell: No such file or directory
chmod: cannot access 'tweetshell.sh': No such file or directory
chmod: cannot access 'install.sh': No such file or directory
sudo: ./install.sh: command not found
please advise further.
Thanks :-)

It wants my git tokens? Can I bypass this please?

This tool is sadly no longer maintained, but you can reach out to seve.services on instagram and we will help you out

I made a fork and some optimization


Table support

Need to review gofpdf examples (if any) of creating tables. BlackFriday provides events for:

table
table head
table body
table row
table cell

I have not yet tested the BF support for tables... so that should be the first action - make sure it really works.

Done!


⚠ Bofrost.at has degraded performance

In 1e12cb7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1693 ms

Resolved: Bofrost.at performance has improved in aff1f49 after 7 minutes.


Error running node/js project on drone

Hi there,
I am triying to integrate this pluging on my drone pipeline to run analysis on a node/js project but, i got the following error and i don't know how to solve it, can you help me please?
LOG DRONE
Branch master allowed - executing sonar analysis.
==> Executing: java -jar /opt/sonar/runner.jar -Drunner.home=/opt/sonar/
==> Output: SonarQube Runner 2.4
Java 1.8.0_151 Oracle Corporation (64-bit)
Linux 4.13.0-46-generic amd64
INFO: Runner configuration file: /opt/sonar/conf/sonar-runner.properties
INFO: Project configuration file: NONE
INFO: Default locale: "en_US", source code encoding: "UTF-8"
INFO: Work directory: /drone/src/bitbucket.org/segurosfalabella/pmc-web/./.sonar
INFO: SonarQube Server <IP_ADDRESS>09
22:25:32.000 INFO  - Publish mode
22:25:32.170 INFO  - Load global settings
22:25:32.571 INFO  - Load global settings (done) | time=402ms
22:25:32.578 INFO  - Server id: AWRyO1Z0DOW-O2WwvkAx
22:25:32.602 INFO  - User cache: /root/.sonar/cache
22:25:33.077 INFO  - Load/download plugins
22:25:33.077 INFO  - Load plugins index
22:25:33.127 INFO  - Load plugins index (done) | time=50ms
22:25:35.689 INFO  - Plugin [l10nes] defines 'l10nen' as base plugin. This metadata can be removed from manifest of l10n plugins since version 5.2.
22:25:35.976 INFO  - Load/download plugins (done) | time=2899ms
22:25:36.381 INFO  - Loaded core extensions:
22:25:36.786 INFO  - Process project properties
22:25:36.814 INFO  - Load project repositories
22:25:36.911 INFO  - Load project repositories (done) | time=97ms
22:25:37.854 INFO  - Load quality profiles
22:25:37.854 WARN  - Ability to set quality profile from command line using 'sonar.profile' is deprecated and will be dropped in a future SonarQube version. Please configure quality profile used by your project on SonarQube server.
22:25:37.948 INFO  - Load quality profiles (done) | time=94ms
22:25:37.980 INFO  - Load active rules
22:25:38.507 INFO  - Load active rules (done) | time=527ms
22:25:38.513 INFO  - Load metrics repository
22:25:38.540 INFO  - Load metrics repository (done) | time=27ms
22:25:38.569 INFO  - Project key: pmc-web
22:25:38.569 INFO  - Project base dir: /drone/src/bitbucket.org/segurosfalabella/pmc-web
22:25:38.572 INFO  - -------------  Scan segurosfalabella/pmc-web
22:25:38.761 INFO  - Load server rules
22:25:38.906 INFO  - Load server rules (done) | time=145ms
22:25:38.957 INFO  - Base dir: /drone/src/bitbucket.org/segurosfalabella/pmc-web
22:25:38.957 INFO  - Working dir: /drone/src/bitbucket.org/segurosfalabella/pmc-web/.sonar
22:25:38.959 INFO  - Source paths: src
22:25:38.960 INFO  - Source encoding: UTF-8, default locale: en_US
22:25:39.037 WARN  - Property 'sonar.plsql.file.suffixes' is not declared as multi-values/property set but was read using 'getStringArray' method. The SonarQube plugin declaring this property should be updated.
22:25:39.075 INFO  - Language is forced to js
22:25:39.091 INFO  - Index files
22:25:39.136 WARN  - File '/drone/src/bitbucket.org/segurosfalabella/pmc-web/src/welcome/assets/welcome.css' is ignored because it doesn't belong to the forced language 'js'
22:25:39.139 INFO  - 11 files indexed
22:25:39.140 INFO  - Quality profile for js: Sonar way
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
Total time: 9.475s
Final Memory: 21M/407M
INFO: ------------------------------------------------------------------------
ERROR: Error during Sonar runner execution
ERROR: Unable to execute Sonar
ERROR: Caused by: sonar.profile was set to 'node' but didn't match any profile for any language. Please check your configuration.
ERROR:
ERROR: To see the full stack trace of the errors, re-run SonarQube Runner with the -e switch.
ERROR: Re-run SonarQube Runner using the -X switch to enable full debug logging.

time="2018-08-02T22:25:39Z" level=info msg="exit status 1"
exit status 1

Config .drone.yml
sonar:
    image: ypcloud/sonar-runner
    sources: ./src
    version: 1.0.3
    key: pmc-web
    encoding: UTF-8
    language: js
    profile: node
    lcovpath: ./coverage/lcov.info
    secrets: [ sonar_host, sonar_login ]
    when:
      branch: master

Cheers.

#2

@levelasquez sonar.profile was deprecated since SQ 4.5 LTS. To select your Quality Profile you should do it from the UI.
#2 Should fix this.


feat: Added reCAPTCHA samples for site key operations

Issue #1464

This looks great! All my suggestions are nits. Please apply the following to all files:

new files should use 2021 as copyright year
function signatures should only be split across multiple lines if they're longer than 80 characters
Use complete sentences for comments (capital first letter, period at the end)
Newline between function docblock description and @param
Don't break function calls across more lines than necessary.
Use %s instead of string concatenation for variables in printf (excluding PHP_EOL)
Use print instead of printf when there are no variables

I'll try to add some of these to our standing issue of updating cs fixer rules: #1465


Lint and format code to follow common conventions

The CI performs linting checks (current workflow file here), but currently not all code has been properly formatted or annotated to pass those.
Originally part of #7 , #17 .

closing in favour of #109


tetragon: Cleanup func_id/id mess in struct msg_generic_kprobe

Currently we have 'id' and 'func_id' in struct msg_generic_kprobe keeping the same value. There's no need, we can use just the 'id' value for everything.
Also use __u32 as config_map key type.
Signed-off-by: Jiri Olsa<EMAIL_ADDRESS>

presumably had some idea in mind or refactored something to get here but anyways lgtm.


Confusing Inconsistency in Templates... maybe?

I wanted had an existing template element like this:
["td","X"]
      ^^^ child of td

and wanted to add children to it. I expected to write code that resulted in this:
["td",["X",[input,"Some text here"]]]
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ contents of td

or
["td",[["X"],[input,"Some text here"]]]
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ contents of td

which both failed (with a rather obtuse and unhelpful error, as are all the template errors, especially because the stacktrace stops within DOMVM; though not that I necessarily want to bloat the code with error handling):
11:44:09.780 TypeError: sibAtIdx._node is undefined
hydrateNode() AppScript;01:159
hydrateNode() AppScript;01:162
redraw() AppScript;01:107
call() AppScript;01:76
1 AppScript;01:159:79
````

The guide says I can do this:

````
["textarea", {rows: 50}].concat([                           // use concat() to avoid explicit
    "text",                                                 // child array restrictions
    ["br"],
    "", null, undefined, [],                                // these will be removed
    NaN, true, false, {}, Infinity                          // these will be coerced to strings
])
````

Which, if I understand correctly results in:

    ["td","X",[input,"Some text here"]]
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ contents of td

which strikes me as weird and inconsistent.

Now, this is not allowed, presumably because `"X"` is ambiguous with `"tag"`:

    ["td",[["X"],[input,"Some text here"]]]
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ contents of td

but from the viewpoint of not having analyzed to the level here, it was surprising, "Why can I have simple values in children expressed as additional elements of a node, but not within an explicit array of the node's children?"

Is there something better that can be done that more closely mirrors the container contents permitted in HTML? Perhaps allowing:

    ["td",[["","X"],[input,"Some text here"]]]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ contents of td

Which means a blank tag should not be dropped.

Or, if we want consistency, should we always just express all nodes children like this:

    return ["td",
        "X",
        [input,"Some text here"]
        [div,
            "Some other text here",
            [... other elements...]...
        ...
        ]
    ]
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ contents of td

(On a side note, having null, undefined,[] dropped is really useful.)

yeah, i'm not sure there's a good way to get uniformity here without requiring explicit child arrays (as it was before) that results in bracket soup.
while it may be surprising, .concat() is a pretty elegant solution here. your proposal of an alternate notation for explicit firstChild text nodes doesnt appeal to me more than a familiar concat, since it also needs to be learned and adds more to the dsl for really no reason.
jsonML i think has no support for raw text nodes, so this is an overloaded feature for readability and dev ease anyhow.

maybe we could add a ["#text", someText], but again, it wouldnt eliminate the surprise unless it was the recommended method, which i dont agree with

forget the above comment. it wont work. #text is same as div#text.
it would be helpful to add a warning here, but also expensive. do we test the first string of every array against a known tag whitelist? wrap createElement in try?
i think this is just something that should be made very obvious in the docs. other workarounds without a meaningful error message will be no less surprising and even more esoteric than concat :(

forget the above comment. it wont work. #text is same as div#text.

Was about to say that when GitHub gave me a system down response, then a work call came in.

it's like a .children(), but native and on steroids.

I will give that serious consideration. It will be extra characters, but not a serious consideration in code size. Might be worth (to me) the trade-off for templates that are easier to read and assimilate.
I didn't realize that concat would join top level arrays like that (there's still a fair amount about JavaScript that I don't know without looking it up).

i would still avoid using .concat() without an explicit array because this will fuck you:
["div"].concat(
  "foo",
  ["br"],
  "bar"
);

but this will not:
["div"].concat([
  "foo",
  ["br"],
  "bar"
]);

given that i've carefully considered this situation prior to abandoning an explicit child array requirement + tag soup for this slight inconsistency, i'm going to close this and add a todo for more visible docs about the situation, but it is this way by design.

i've carefully considered this situation prior to abandoning an explicit child array requirement + [bracket] soup

Yeah, point taken. I'm going to play with both, because I am finding the inconsistency a bit more problematic than the extra brackets. And at least the bracket failure will mess up in an obviously visible way.
I am still experimenting, looking for something that makes each tag+attr+value collection self-evident. I reserve the right to change my mind any number of times.

@lawrence-dol
There is another possible workaround, but i'm not sure how expensive it will be yet (may be negligible).
In javascript both of the following are strings:
var foo = new String("foo");
var bar = "bar";

However, they can be discerned when type-checking:
foo instanceof String === true;
typeof foo === "object";

bar instanceof String === false;
typeof bar=== "string";

This duality can be exploited for a work-around.
The additional code required in the core is small (also handles numbers):
else if (typeof def2[0] == "number" || def2[0] instanceof String || def2[0] instanceof Number)
	mergeIt = true;

this would allow:
function View(vm) {
	return () => ["#moo", [new String("hey"), "dog"]];
}

You can wrap the instantiation in your own helper: str("hey").
The additional code will only run to check the first element of explicit child arrays (it does not add full string-as-object support everywhere in the lib).
Thoughts?

This duality can be exploited for a work-around.

I'm leaning towards agreeing with you that any workaround like this is actually just adding cognitive load which will require added documentation so you can avoid a problem that will still have to be documented.
Let me experiment further concretely and come back here if something more intuitive (from the point of reading the code) than concat occurs to me.
I guess what I want to see is:
["tag",{ ...attribs...}, ???]
 ^^^^^^^^^^^^^^^^^^^^^^        this is the element
                         ^^^   this is the element's content

which nests well and which is terse enough to use everywhere. Maybe concat is that:
["tag",{ ...attribs...}].concat([???]);
 ^^^^^^^^^^^^^^^^^^^^^^                 this is the element
                                ^^^^^   this is the element's content

Don't concern yourself further with this unless you have a brainwave. I'm kind of a habitual guy and consistency is one of the sticks up my rear. I don't intend it to become a stick up yours unless there's a genuine value-add.

yet another option is to make yourself a hyperscript wrapper which requires explicit children and does the concat for you.
function h(tag, props, children) {
  return [tag].concat(props, children);
}

yet another option is to make yourself a hyperscript wrapper

Yeah, I've been actively resisting doing that until I'd done more extensive templates, particularly so as not to miss out on "not needing explicit children in every case"
This happens to be a complex table built with subfunctions for rows and columns so as to make each cell directly addressable.
With the added twist of wanting null for the first element of the rows and columns so that [1][1] addresses the top-left cell (the host system expresses everything in 1+ coords instead of offsets and maintaining that has less cognitive resistance). Right now I'm getting a "null" tag container instead of a null first element being discarded so I am having to reason through the exact template structure.
[ "table.display-panel", [
    null,
    [ "tr",null, [
        null,
        [ "td.A20", "X" ],
        [ "td.A20", "X" ],
        [ "td.A20", "X" ],
        [ "td.A20", "X" ],
        ...
    ]]
    ...
]]

results in this:

    <null>

            <null>

                ...
            </null>

        ....
    </null>

instead of the expected:

        ...

    ....

that looks like a pretty obvious bug. i'll look into it.
i would recommend against inserting nulls as an offseting mechanism, though. it is much more performant to wrap the offset logic in some getCell() helper rather than making domvm branch internally on template processing conditionals. adding 1 is much cheaper than splicing nulls out of arrays.

much more performant to wrap the offset logic

That's a good point, which I'll do. I am much more focused right now on the prototype for the customer and not enough on the finer points. Thanks.

that looks like a pretty obvious bug. i'll look into it

If it does turn out to be a bug, that could be the source of a lot of my counter-intuition.

it was a bug. fixed in 1.x-dev branch.
for future reference, <null> is always a bug :)

Thanks!

BTW, is the 1.x branch now intended to be more stable than master?

not more stable, just more up-to-date in the 1.x series.
i made it the default branch so it's easier to see updates/activity. 1.x-dev may have fresh bugs (for untested features), as well as new features and bug fixes.
it's the incubating branch for master, since i cannot cut a stable release after every commit.
i don't have a specific strategy yet for determining how much incubation time is appropriate between stable releases (aside from serious. common-case bug fixes). maybe every couple weeks?

If I may offer a branching strategy that's worked well for us, that doesn't attempt to tie branches to versions and which works equally well for versioned products as for non-versioned, I'd suggest the following:
http://tech.dolhub.com/article/computer/Git-Workflow
It's simple enough for newbies to follow, the naming is chosen to sort the code flow alphabetically and be intuitively obvious to anyone at first glance, and it's pragmatic enough to handle every real-world situation we've thrown at it for everything from libraries to middleware to packaged products to end-user evergreen SAAS.
Just FWIW.
PS: Excuse the rather dated design; I started reworking the look a while back and still haven't finished it.
PPS: As a complete aside, you might find my rationale for placing closing brackets interesting: http://tech.dolhub.com/article/computer/Code-Layout

Thanks, but it's way too early, the project too small and devs too few to have such a formal process. For the time being master (stable), 1.x-dev (dev/incubate), gh-pages is more than enough to maintain for me (the sole dev).
I'll likely rename master to 1.x-stable and add a 1.x-hotfix. There's sufficient clarity in those three.
Perhaps the next step could be to add some "qa/beta/staging" branch for feature freezes, but not until this project gets bigger or has additional, dedicated and willing maintainers.
While the lib is young, I recommend using 1.x-dev and reporting any issues, then maybe at the end of each month, I will cut a stable release if nothing has been reported. With a userbase in the single digits there's really no clear-cut "correct" way to do this.

it's way too early, the project too small and devs too few

It is, of course, entirely up to you.
But I use this workflow for all my projects from tiny to huge; from those that only I develop to our entire company contributing; even my websites. The key is to recognize that not all projects warrant all trunks (I have many which have only develop), but the methodology is identical.

For the time being master (stable), 1.x-dev (dev/incubate)

One thing you'll notice is that you're having to describe your branches to explain what purpose they serve; why not just name them for the purpose they serve?
It's really no overhead by yourself and it is an effective mechanism when managing commits from multiple devs. The most important effect is to create a sane merging workflow which eliminates lost code and conflicts when merging downstream (e.g. from develop to release).
In the case of DOMVM, I would use just develop and release where develop is what you are referring 1.x and release is what you are currently calling master. Then "serious, common-case bug fixes" are done on, e.g. dev@rel/ii-viewmodel branched from and merged back into release which is then merged to develop. Simple, fast, and stable for those pulling from release. Changes on develop have zero disruption to release consumers and everyone knows what to expect.
Therefore, right now release would have 1.0.1 and develop would have 2.0.0 (assuming you're using semver). Until V1 was released you'd just have had develop. If you choose to continue to actively support V1 when V3 drops, create a stable trunk for that. I personally would not do that nor actively support anything beyond the current release, especially because Git let's you hack into any point in the history if you really have to. The only real reason to go beyond V1 is API incompatibility and that should be an extreme rarity for a project like this.
But, again, it's just a suggestion.

One thing you'll notice is that you're having to describe your branches to explain what purpose they serve; why not just name them for the purpose they serve?

People have different terminology for the same stuff (wip/next/develop/dev/pre-alpha; prod/production/stable/release; rc/pre-release/qa/beta). All of these should be self-explanatory to any dev with the minimum skillset needed to make contributions to this project. The bar is already very very low, with 0 needed tooling and a responsive me.
1.x-dev (maybe 1.x-next) is not 2.0.0, it is the backwards-compatible dev branch of 1.x, there is no ambiguity here. Nor is there ambiguity in 1.x-hotfix, 1.x-staging or 1.x-stable; only master is ambiguous.
1.x-stable may not even be needed, since tags can be used to identify and release stable versions on 1.x-next (both Github and NPM work this way anyhow).
Let's not get into a long discussion about this as it's really not a good use of time. We can circle back to this at minimum when you're ready to contribute core code and these branches affect you on a more than philosophical level :)
We're waaaay off topic at this point.


Strange problems while inserting via REST

Elassandra version:
<IP_ADDRESS>
Plugins installed: []
JVM version:
8
OS version:
Kubernetes
Description of the problem including expected versus actual behavior:
Today I enabled the fluentd logging in Kubernetes and pointed it to elassandra.  It is logging an incredible number of records and seems to be working properly.
While that is running we connected with a different client and started receiving log messages like the one below.  If I stop the fluentd and restart the client, it still fails until we drop/recreate the keyspace.  I am not 100% sure on this but we tried it twice with the same result.  We saw something in the client and it mentioned the bulk queue is full when we researched on Google.  I am thinking it might be a tune as opposed to it's some kind of bug.  Any Ideas?

| May 21st 2018, 18:09:29.000 | - | 2018-05-21 22:09:29,018 WARN  [elasticsearch[<IP_ADDRESS>][bulk][T#1]] org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.finishWithUnexpectedFailure(TransportReplicationAction.java:859) unexpected error during the primary phase for action [indices:data/write/bulk[s]], request [BulkShardRequest [[matrixuser][0]] containing [index {[matrixuser][matrixuser][201602kjonesx], source[{"Pkey":"201602kjonesx","Date":"2016-02-01","Business_Unit_ID":155,"Business_Unit_Name":"Honda Shared Network","Segment":"TMS","User_ID":"kjones","Role_Type":" n/a","Cluster":"North America","Country":"UNITED STATES"}]}]]
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.primary(TransportReplicationAction.java:738)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.TransportService$7.doRun(TransportService.java:656)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.retry(TransportReplicationAction.java:827)
| May 21st 2018, 18:09:29.000 | - | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
| May 21st 2018, 18:09:29.000 | - | at java.lang.Thread.run(Thread.java:748)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:260)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.DelegatingTransportChannel.sendResponse(DelegatingTransportChannel.java:70)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver.waitForNextChange(ClusterStateObserver.java:112)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver.waitForNextChange(ClusterStateObserver.java:104)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.TransportService$DirectResponseChannel.processException(TransportService.java:1183)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$AsyncPrimaryAction.onFailure(TransportReplicationAction.java:349)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.doRun(TransportReplicationAction.java:667)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver.waitForNextChange(ClusterStateObserver.java:140)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver.waitForNextChange(ClusterStateObserver.java:112)
| May 21st 2018, 18:09:29.000 | - | org.elasticsearch.index.IndexNotFoundException: no such index
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver.waitForNextChange(ClusterStateObserver.java:104)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1079)
| May 21st 2018, 18:09:29.000 | - | at java.lang.Thread.run(Thread.java:748)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$AsyncPrimaryAction.onFailure(TransportReplicationAction.java:349)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$AsyncPrimaryAction.doRun(TransportReplicationAction.java:293)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase$1.handleException(TransportReplicationAction.java:806)
| May 21st 2018, 18:09:29.000 | - | org.elasticsearch.index.IndexNotFoundException: no such index
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.primary(TransportReplicationAction.java:738)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase$1.handleException(TransportReplicationAction.java:806)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$AsyncPrimaryAction.doRun(TransportReplicationAction.java:293)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:69)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.TransportService$7.doRun(TransportService.java:656)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
| May 21st 2018, 18:09:29.000 | - | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.doRun(TransportReplicationAction.java:667)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver.waitForNextChange(ClusterStateObserver.java:140)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:252)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.doRun(TransportReplicationAction.java:667)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver.waitForNextChange(ClusterStateObserver.java:140)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver.waitForNextChange(ClusterStateObserver.java:104)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.DelegatingTransportChannel.sendResponse(DelegatingTransportChannel.java:70)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.TransportService$DirectResponseChannel.sendResponse(TransportService.java:1161)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:260)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:252)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:69)
| May 21st 2018, 18:09:29.000 | - | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:312)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase$1.handleException(TransportReplicationAction.java:806)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1079)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.TransportService$DirectResponseChannel.processException(TransportService.java:1183)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.cluster.routing.RoutingTable.shardRoutingTable(RoutingTable.java:141)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
| May 21st 2018, 18:09:29.000 | - | at org.elasticsearch.transport.TransportService$7.doRun(TransportService.java:656)
| May 21st 2018, 18:09:29.000 | - | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

Hi,
This happen in a race condition with cluster state update and has already been fixed in version <IP_ADDRESS>. This fix is currently tested on version 5.5.0 and is available in on the master branch of https://github.com/strapdata/elassandra5-rc for non-regression tests.
Thanks.

Vincent,
Is it built on <IP_ADDRESS> or do I need to build it?
Best regards,
Bob Liotta
SVP IT Enterprise Architect
CEVA Logistics / 10751 Deerwood Park, Blvd, Jacksonville, FL 32256 / www.cevalogistics.comhttp://www.cevalogistics.com
O: +1<PHONE_NUMBER> / E: robert.liotta<EMAIL_ADDRESS>Making business flow
From: Vincent Royer<EMAIL_ADDRESS>Reply-To: strapdata/elassandra<EMAIL_ADDRESS>Date: Monday, May 21, 2018 at 7:34 PM
To: strapdata/elassandra<EMAIL_ADDRESS>Cc: "Liotta, Robert"<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [strapdata/elassandra] Strange problems while inserting via REST (#195)
Hi,
This happen in a race condition with cluster state update and has already been fixed in version <IP_ADDRESS>. This fix is currently tested on version 5.5.0 and is available in on the master branch of https://github.com/strapdata/elassandra5-rc for non-regression tests.
Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/strapdata/elassandra/issues/195#issuecomment-390815416, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQ-uq7MJaTKR84LjU_UsYoAoenFLkDuwks5t008IgaJpZM4UHtEw.
NVOCC Services are provided by CEVA as agents for and on behalf of Pyramid Lines Limited trading as Pyramid Lines.
This e-mail message is intended for the above named recipient(s) only. It may contain confidential information that is privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail by error, please immediately notify the sender by replying to this e-mail and deleting the message including any attachment(s) from your system. Thank you in advance for your cooperation and assistance. Although the company has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

Hi Bob,
Yes, the build and publication process currently on going  to release the next version <IP_ADDRESS> for tomorrow, but right now, you should rebuild from the master branch of https://github.com/strapdata/elassandra5-rc to include the last fix.
git clone --recurse-submodules https://github.com/strapdata/elassandra5-rc
cd elassandra5-rc
gradle distribution:tar:assemble -Dbuild.snapshot=false
Then, for a light-weight deployment, you can copy the built file core/build/distributions/elasticsearch-5.5.0.jar to the /lib directory of your running nodes, and restart.

Hi Bob,
Release <IP_ADDRESS> including the fix is now available for download on github.
Thanks.
Vincent.

Le 22 mai 2018 à 15:04, Vincent Royer<EMAIL_ADDRESS>a écrit :
Hi Bob,
Yes, the build and publication process currently on going to release the next version <IP_ADDRESS> for tomorrow, but right now, you should rebuild from the master branch of https://github.com/strapdata/elassandra5-rc https://github.com/strapdata/elassandra5-rc to include the last fix.
git clone --recurse-submodules https://github.com/strapdata/elassandra5-rc https://github.com/strapdata/elassandra5-rc
cd elassandra5-rc
gradle distribution:tar:assemble -Dbuild.snapshot=false
Then, for a light-weight deployment, you can copy the built file core/build/distributions/elasticsearch-5.5.0.jar to the /lib directory of your running nodes, and restart.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/195#issuecomment-390982159, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmQ9-df7tbDwykvTVr26Zn9SI0nEYks5t1Az3gaJpZM4UHtEw.

Vincent,
Great.  I will let you know….
BTW.  Regarding the license, I sent a reply, can you please comment?
Best regards,
Bob Liotta
SVP IT Enterprise Architect
CEVA Logistics / 10751 Deerwood Park, Blvd, Jacksonville, FL 32256 / www.cevalogistics.comhttp://www.cevalogistics.com
O: +1<PHONE_NUMBER> / E: robert.liotta<EMAIL_ADDRESS>Making business flow
From: Vincent Royer<EMAIL_ADDRESS>Reply-To: strapdata/elassandra<EMAIL_ADDRESS>Date: Wednesday, May 23, 2018 at 8:03 AM
To: strapdata/elassandra<EMAIL_ADDRESS>Cc: "Liotta, Robert"<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [strapdata/elassandra] Strange problems while inserting via REST (#195)
Hi Bob,
Release <IP_ADDRESS> including the fix is now available for download on github.
Thanks.
Vincent.

Le 22 mai 2018 à 15:04, Vincent Royer<EMAIL_ADDRESS>a écrit :
Hi Bob,
Yes, the build and publication process currently on going to release the next version <IP_ADDRESS> for tomorrow, but right now, you should rebuild from the master branch of https://github.com/strapdata/elassandra5-rc https://github.com/strapdata/elassandra5-rc to include the last fix.
git clone --recurse-submodules https://github.com/strapdata/elassandra5-rc https://github.com/strapdata/elassandra5-rc
cd elassandra5-rc
gradle distribution:tar:assemble -Dbuild.snapshot=false
Then, for a light-weight deployment, you can copy the built file core/build/distributions/elasticsearch-5.5.0.jar to the /lib directory of your running nodes, and restart.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/195#issuecomment-390982159, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmQ9-df7tbDwykvTVr26Zn9SI0nEYks5t1Az3gaJpZM4UHtEw.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/strapdata/elassandra/issues/195#issuecomment-391322004, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQ-uq2BW0PhwoQZdPG4UMHS_ft4Fioduks5t1VAMgaJpZM4UHtEw.
NVOCC Services are provided by CEVA as agents for and on behalf of Pyramid Lines Limited trading as Pyramid Lines.
This e-mail message is intended for the above named recipient(s) only. It may contain confidential information that is privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail by error, please immediately notify the sender by replying to this e-mail and deleting the message including any attachment(s) from your system. Thank you in advance for your cooperation and assistance. Although the company has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.


Multiple windows support

Hi,
Have you considered to add multiple ncurses screen/window/panel support to the lib? Or is there some reason just not doing that? It's great so far, but it would be nice to have also pop-up windows, pop-up-menus and dialogs. Seems that now it's using the root main window (stdscr) for everything.
Maybe some RootWindow class using stdscr when initializing the app, and then maybe some central widget is given to the root which is actually a sub window for stdscr, and that handles widget childs as now. If you want a pop-up, insert a widget to the root or some other high level widget and the pop-up will be on top on everything below the pop-up widget? It might need some major refactoring, though.
-Matti

I've thought about how to do this a few times, so it might happen at some point. It could probably be built without modifying the layout system, just generalizing the current single screen to multiple screens/windows that work the same as the current main window. The newer version of the library no longer relies on ncurses, so that windowing logic would need to be built into TermOx.


Keeping track of the new ordering

Hi, thank you for the example and the package!I
When I have the items reordered, I need to send to the server the new order.
I don't know how to do that.
Is there a way to keep track of the new order (assuming each row also had an id to start), to send the new indexing to the server?
The idea is to get something like this where order represents the new order
{"items"=>{"0"=>{"item_id"=>"114", "order"=>"0"}, "1"=>{"item_id"=>"23", "order"=>"1"}, "2"=>{"item_id"=>"24", "order"=>"2"}, "3"=>{"item_id"=>"22", "order"=>"3"}, "4"=>{"item_id"=>"25", "order"=>"4"}, "5"=>{"item_id"=>"78", "order"=>"5"}}, "action"=>"update_all", "controller"=>"branches"}

Unfortunately it has been a while since I worked in Elm, but below are some tips.
Hope these are helpful!
1. Extend the model/ code to sort a list if records, instead of a list of simple strings

It looks like the data you need per item is a bit more than just a String. So in the example code, you could replace the line 30 with something like , data : List MyItem, and define a type alias with your item, like type alias MyItem = { id : Int, title : String }
then you would need to change your initialList also to hold a list of records instead of a list of strings
change line 38 from List.sort to List.sortBy to tell Elm to sort by the id (probably), or remove the sort altogether
in the itemView function on line 227 you need to modify the code to show the title of the item, because item is now a record, and not a simple string.

2. Send the sorted list (of records) to a server
This would require adding functions for
a) invoke the 'send to server' functions at a logical place in the code
Probably the most logical place is at the DragEnd event, where you add a Cmd when the list is updated. This is in line 113
b) create a message (looks like json-ish structure in your comment)
The source for your message is list of records in model.data. But take care here: you need the updated version of the model, not the original model.data. So probably create a let newModel = ... in  structure.
This list in the (updated) model is already sorted in the new order, and has the right id's, so you could use functions in JSON package of elm to convert your list of records to the desired JSON output.
c) send the message to the server
Several ways to do this. Most basic is an HTTP.send command. You could look this up in the docs, or learn by example (e.g. here)

Thanks you so much for your detailed answer. I really appreciate it!


Added Wait-RSJob

Added Wait-RSJob. This is a slightly modified version of Get-RSJob with
about 10 lines of code change. It should be updated to be dynamic and
call Get-RSJob but it will work in its current state.

This is great! I'm going to go ahead and merge this, but I definitely want to make sure that this outputs the RSJob object like it does with Wait-Job if everything is completed or everything completed before the end of the timeout period.


Show a Chrome notification when a new #Clicky has been received

This is sort of working at the moment, just commented out, but it needs more work to make it stable enough to rely on.

This was added a few versions ago, the option to enable this can be found on the settings page.


Encode numerical constants

Implement an automatic generation of comparing the extracted constants + constants from the planning file. Use similar approach as in this problem file.
Consider:

how to extract numbers from planning file (how are they encoded?)
what predicate to use for the comparison
which types of numbers to parse

extracting the relation for decimal values in the ontology is now solved and the "leq", i.e., lower of equal, relation can be used in the action descriptions to compare two values.
Corresponding commit: 44e8bafeeef18d86d4e851ea841bf1b128005be2.
What is still missing: checking the problem file for existing numerical values and adding comparison operations for them.

Solved with commit 68f3fb5be37fb68d5c3ea69500cbe6670dba5fa2.
Numbers in PDDL problem need to be of type number to be considered for parsing. and the numbers have the following format: <number>_<type>, e.g. 3.15_decimal
So far, the implementation can parse numbers of type decimal. Please open new issue, if support for more types of numbers is desired.

As of commit b1585ac2225432d2e475ec2b55dd6b443c5251ee, the comparison operators for numbers are now lessThan and equalsTo

Hi @tobiaswjohn,
I am not sure if I am doing something wrong, but I cannot replicate this. The lessThan and equalsTo predicates are not being generated.
Check: https://github.com/remaro-network/dlToPlanning/blob/suave/examples/suave/suave_problem_created.pddl

The issue is probably a lack of documentation from my side... Do you run the program with the argument --add-num-comparisons?
Also: You have some objects of type "number" in your problem. You probably want to use "owl-number". I changed this, because I realized that "number" is already defined for different purposes in PDDL (although noone seems to use it).

It worked with the --add-num-comparisons, thanks.
Ok, I will use only owl-number


feat(agent): Add functionality for langchain agent with LlamaToolkit to return sources

Description
I am experimenting with the langchain agent solution provided by llama-index using create_llama_agent and LlamaToolkit. While it provides an easy approach to communicate with my index, the agent only responds back with the string LLM response. The agent should have an optional functionality to return sources as well, similar to load_qa_with_sources_chain from langchain.

Yea this would definitely be great to have. Noting it down!


Support rotation when tracing to new logfile

lager:trace_file/3 can now also handle a new-style configuration proplist
to allow full configuration of a newly created file backend.
If the file backend already exists, however, only the level can be given
(similarly to the old behaviour).
I initially created this commit weeks ago. It would be nice to have persistent tracing into file fully configurable (and I am ready to add this to this branch) but I am not sure how the syntax should look like. (My concern is the handling of Level: should it be part of the backend config or is it a separate mandatory argument of the tracer)

This PR is pretty old so I'm not sure of its status. @Vagabond do you recall anything about this PR?

Haven't heard anything on this for a year. I'm going to close it. Please reopen if needed.


feat: Associate data with run

Overview
Along the protocol run I want to

store files (photos taken from camera)
log additional information about protocol run

I can store this data in files, however I currently see no way to associate files with a particular run.
Implementation details
Possible solutions:

provide name of run as a field in ProtocolContext. This will allow creating a separate folder /data/run_name
or provide a method to store data, like ctx.log(str), that can be later retrieved from http api
other solutions are welcome too

Design
No response
Acceptance criteria
No response

Hey @arogozhnikov! This feature request lines up well with some internal discussions we've been having. There's a lot of potential utility in having a standard API for protocol run "result" data. We'll keep this thread updated with any progress.
In the mean time, ctx.comment(message: str) may be a useful workaround. Any strings you log via this method will be accessible via GET /runs/:run_id/commands


Country

I would like to suggest to add one more public methods for getting country by dialcode:
 class DialCodeComparator : Comparator<Country?> {
        override fun compare(country1: Country?, country2: Country?): Int {
            return country1?.dialCode!!.compareTo(country2?.dialCode!!)
        }
    }

   fun getCountryByDialCode(dialCode: String): Country? {
        Collections.sort(countries, DialCodeComparator())
        val country = Country()
        country.dialCode = dialCode
        val i = Collections.binarySearch(countries, country, DialCodeComparator())
        return if (i < 0) null else countries!![i]
    }

Will integrate this in the next release this weekend 👍🏽


macOS samples?

Is there any desire for contributions of macOS-specific samples, similar to the samples in ios/samples?  So far I have built a macOS project by imitating ios/samples/hello-triangle.

I'm not sure if that's really necessary since everything in filament/samples, such as hellotriangle.cpp and hellopbr.cpp already build & run on macOS.

@prideout I guess that's reasonable.  The iOS samples seemed more inviting to me because they had Xcode projects, which is what I'm used to.  And it wasn't immediately obvious to me whether the general samples would be using OpenGL or Metal.  But I'll take another look at them.

The general samples can use both (some of them have a command line flag to use Metal over OpenGL).

The general samples can use both (some of them have a command line flag to use Metal over OpenGL).

A possible way to make it easier to specify the backend of the general samples would be to modify libs/filamentapp/include/filamentapp/Config.h by inserting
#ifndef FILAMENTAPP_CONFIG_BACKEND
    #define FILAMENTAPP_CONFIG_BACKEND DEFAULT
#endif

and then in the Config structure saying
filament::Engine::Backend backend = filament::Engine::Backend::FILAMENTAPP_CONFIG_BACKEND;

If that sounds useful, I could turn it into a pull request.


1378 old api removal

Pull Request Overview

Removal of the old site settings API
DO NOT MERGE UNTIL FE 1379 is done

@hwindsor https://github.com/WildMeOrg/codex-frontend/pull/454 has been merged.


iOS build fails

Trying to build for iOS with the version of the plugin 1.1.0 fails due to the following error
ExponeaSDK/ExponeaSDK/ExponeaSDK/Classes/InAppMessages/View/InAppMessageWebView.swift:91:24
Swift Compiler Error (Xcode): 'isElementFullscreenEnabled' is only available in iOS 15.4 or newer
if #available(iOS 15.0, *) { <- This is the if statement that causes the issue
    preferences.isElementFullscreenEnabled = false
}

Changing this to 15.4, solves the problem and I was able to build.
On the newest iOS SDK version this problem seems to be solved, so maybe an update to the native SDKs will be sufficient

Hi @pantelistsakoulis-ts, as mentioned https://github.com/exponea/exponea-flutter-sdk/issues/7
We are working on the update, this will be fixed in new Flutter SDK version.
Thank you for your patience


POC: Try adding rexux-observable

I don't know how we'll feasibly solve the multide of potential race conditons and async clean up memory leaks without something like rxjs. So, this is a trial to see the following:

How much does it increase bundle size?
How effective is typechecking?
Does it solve some of the difficult cancelation issues we have?

According to Chrome Dev Tools Network panel, this increases the main bundle by 8kb.

I don't think we'll go this way just yet.


Create New GHE_Perf File

GHE_Perf Run Created this

GHE Performance Test Generated This1534550083071

GHE Performance Test Generated This1534552802906

GHE Performance Test Generated This1534801142095

GHE Performance Test Generated This1536713250489

GHE Performance Test Generated This1541103142880

GHE Performance Test Generated This1541544409770


Added a question for accessibility #172

Description

Contribution towards #172
What does your PR belong to?

[x] Questions / Answers
[ ] Website
[ ] General / Things regarding the repository (like CI Integration)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (non-breaking improvement of a question)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have checked that the changes are working properly
[x] I have checked that there isn't any PR doing the same
[x] I have read the CONTRIBUTING document.

Thanks! @fejes713 😄 I will try to add more questions under the accessibility tag!


Upgrade to Pydantic V2

Upgraded numerous modules comments will be inline to descripe all of the changes and decisions made

@birdperson1970 I've hesitated for some time to close this out since it was such a great effort, but at this point it's become more than clear that we aren't going back to the Python server. I'm going to close the PR, but want to just once again say thank you for the time you spent on improving Continue. Hope all is well!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Room does not get closed

Hi there!
So I'm trying to close a room. I got a participant (client) using the server-sdk-go and another program called closer which tries to close the room.
client
package main

import (
	"fmt"

	"github.com/livekit/protocol/livekit"
	lksdk "github.com/livekit/server-sdk-go"
	"github.com/thanhpk/randstr"
)

func main() {
	host := "ws://localhost:7880"
	apiKey := "devkey"
	apiSecret := "secret"

	roomName := "myroom"
	identity := randstr.Hex(16)

	close := make(chan bool)

	roomCB := &lksdk.RoomCallback{
		ParticipantCallback: lksdk.ParticipantCallback{},
		OnReconnecting: func() {
			fmt.Print("OnReconnecting")
		},
		OnReconnected: func() {
			fmt.Print("OnReconnected")
		},
		OnDisconnected: func() {
			fmt.Print("OnDisconnected")
			close <- true
		},
	}
	room, err := lksdk.ConnectToRoom(host, lksdk.ConnectInfo{
		APIKey:              apiKey,
		APISecret:           apiSecret,
		RoomName:            roomName,
		ParticipantIdentity: identity,
	}, roomCB)
	if err != nil {
		panic(err)
	}

	<-close

	room.Disconnect()
}

closer
package main

import (
	"context"
	"fmt"

	livekit "github.com/livekit/protocol/livekit"
	lksdk "github.com/livekit/server-sdk-go"
)

func main() {
	host := "ws://localhost:7880"
	apiKey := "devkey"
	apiSecret := "secret"

	roomClient := lksdk.NewRoomServiceClient(host, apiKey, apiSecret)

	res_list, _ := roomClient.ListRooms(context.Background(), &livekit.ListRoomsRequest{})

	roomId := res_list.GetRooms()[0].GetSid()

	fmt.Printf("sid: '%s'\n", roomId)

	res_delete, err := roomClient.DeleteRoom(context.Background(), &livekit.DeleteRoomRequest{
		Room: roomId,
	})

	fmt.Printf("res_delete: '%s', error: %v\n", res_delete.String(), err)

	fmt.Printf("done\n")
}

issue
So there is no error, however the room does not get closed either. Simply nothing happens. Btw when I use an invalid roomId I get no error either.
the server logs DEBUG   livekit service/roommanager.go:453      Deleting non-rtc room, loading from roomstore
I expected that the client will get disconnected and that the signal OnDisconnected would get called.
versions

github.com/livekit/server-sdk-go v0.10.4
docker run --rm -it --network host livekit/livekit-server:v1.1.2 --dev

Thanks for your time!

Hey @qwertzui11
were you able to solve the problem?
I'm having a similar issue, when i'm trying to disconnect my local participant, most of the times the OnDisconnected callback is not triggered.


Hi guys, given so many commits,  which one is a release version on master

@kevinchow924 I think this is what you're after?

Thanks you very much.
Saleor is a very good platform.
I am considering to build my own project based on saleor.  Do you have any idea for me ?

@kevinchow924 if you're looking to build a web shop then it is indeed an excellent platform. It got us up and running with shop.enstaved.com very quickly with the flexibility that we needed to customise things as required.
I think this issue can probably be closed now?


can't open or find multiplier but it's listed

$ lsusb
Bus 001 Device 007: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
$ sudo infnoise
Error: Can't open Infinite Noise Multiplier.
$ sudo infnoise -l
ID: 0, Manufacturer: 13-37.org, Description: Infinite Noise TRNG, Serial: 1337-XXX
$ sudo infnoise -s 1337-XXX
Error: Can't find Infinite Noise Multiplier with given serial

XXX replaced because i don't know if it should be secret, --debug doesn't show any other info

never mind, the issue was the daemon was running and keeping the device busy. somehow i thought the tool would connect to that to get randomness, but that's actually in /dev/random now :P


Native SVG documentation

Added documentation on native mobile SVGs.

@Robinfr This doc looks good. The last thing to change is the placement. This doc is a Reference Guide, not a How To.
Please drag and drop the markdown file in to this folder /refguide/native-mobile.
Also please delete the existing link to it in /howto/mobile/native-mobile and add a link to it in /refguide/native-mobile.
After that we are good to go.

Added before/after images and moved it to refguide.

Added before/after images and moved it to refguide.

Did you commit your changes? I don't see the images or a commit.

Maybe.. not? Forgot to push will do it when I get home.

Pushed!


Improve shuffling performance

Avoids multiple createSha256 and Bytes.wrap
Before:
# Run complete.  Total time: 00:01:17

Benchmark                            (indexCount)  Mode  Cnt  Score    Error  Units
ShuffleBenchmark.shuffledIndexBench         16384    ss   15  0.992 ±  0.020   s/op
ShuffleBenchmark.shuffledIndexBench         32768    ss   15  1.958 ±  0.021   s/op
ShuffleBenchmark.shuffledListBench          16384    ss   15  0.008 ±  0.001   s/op
ShuffleBenchmark.shuffledListBench          32768    ss   15  0.014 ±  0.001   s/op

Memory allocations comparison on shuffle benchmark:

related to: #6016
Documentation

[ ] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[ ] I thought about adding a changelog entry, and added one if I deemed necessary.

Worth a changelog entry as well. Otherwise I agree with Paul about extracting a method to do the hash. Looks good otherwise.

ouch, computeProposerIndex doesn't have a unit test

I see I can apply the same pattern to:
getNextSyncCommitteeIndices and isValidMerkleBranch.
And maybe do some cleanup to ssz to use Sha256 class


Update documentation with docker compose example

I'm using docker compose to run the sync, added an example in the docs to provide an example file others can use as a starting point.

I really didn't think about it till you mentioned it.
I'll submit a pull request to add it later.

I'll close this PR and update the documentation referencing the docker-compose as well as another PR for the docker-compose file itself.


Add localization of the UI

Solves #125
This pull request doesn't include the localization of the settings, but allow you to let people having other language than english to actually use the addon.
This sets up the translation of the main UI + enable the translation in french.
With my current code, the minimum requirement for the addon to work is to translate the "channels" and "spec" part ; because the code will crash if it's not present.

Meant to do a review, but then kept finding stuff while re-reading. Some slight optimizations, but biggest win is use the existing global strings for the client.
Actually this looks one is kept up-to date, so https://www.townlong-yak.com/framexml/beta/GlobalStrings.lua vs the tekkub one I linked in comments.

We've taken a different direction on localization.


Fix rope with liger kernels

Port Liger kernel's RoPE implementation to here, and make sure it is the same behavior.

working on this right now


Add rate limiting to workload metadata collector on error.

Context
In MetadataCollectorWorker::run, we currently loop endlessly over calls to MetadataCollector::water, which is meant to continuously recover from errors during the watching of metadata events. This does work for the purpose of logging the error and trying again to watch, but we run into one particularly bad and obvious problem with this pattern: when the Datadog Agent shuts down and we're using the Remote Agent collector, it spams the logs literally as fast as it possibly can.
Workload metadata is ultimately cached, so it generally doesn't benefit us to try and immediately recover: we'd be fine to wait for a second or two before retrying. This would also solve our immediately issue of spamming the logs.

We ended up just going with a fixed 5 second sleep on error for the moment, which we can address in the future if that's somehow too inflexible.


Add support for ExU Resturbed Spawners

In version 1.3.1, I cant seem to connect any connecter to a Resturbed Mob Spawner from Extra Utilities 2.
Is it possible to add support for this block?
As a temporary measure is there a way for a connecter to make a forceable connection?, like connect to a block of Cobble?

What kind of thing would this block need as support? What does it do?

A resturbed Spawner from ExU2 has similar functionalities as a regular Vanilla Spawner, with 2 exceptions.
First: It is redstone controllable, you can decide to make it run continuously, turn on/off when a redstone signal is emitted or spawn once on a redstone pulse.
Secondly: It has 1 inventory slot, which accepts the Exu2 Speed Upgrades, allowing players to increase the spawnrate of the Spawner.
I wanted the Xnet Connecter to be able to connect to the Spawner so it can emit a redstone signal, controlling the spawner.
I currently have a Connecter connected to a line of redstone dust, emitting a signal to the block underneath the Spawner and indirectly controlling the Spawner that way.


Providing the OIF Summit slides on our blog post

We have collected the various talks our community is giving at the OpenInfra Summit 2022 on our blog: https://scs.community/2022/06/02/scs-at-oifsummit2022.
Please upload - if you like - your slides until Monday evening to our website repository and I will link them to the corresponding schedule item in our blog post. This will boost the traffic on our website and hopefully on our social media accounts.
It would be great if you create a huge QR code at the end of your presentation so that visitors can directly receive the shown slides deck. The deep links are already available.
Thank you for contributing to OIF Summit and being part of our joint actions at this exciting event. Looking forward to seeing you next week!
@fkr @berendt @horazont @garloff @matfechner

"oops". :-).
I'll ask Felix if he can provide the slides now at least.

Add our slides as well.


Support Union as a function

Is your feature request related to a problem or challenge?
We have recently issues show that it is time to support Union
#10161 #10139 ScalarValue::iter_to_array
#10180 comparison_coercion
I think the first step is able to create Union in slt file.
Describe the solution you'd like
Follow DuckDB Union or  others well-known system.
https://duckdb.org/docs/sql/data_types/union.html
First step might be able to create table with union type
query error DataFusion error: Error during planning: Inconsistent data type across values list at row 1 column 0\. Was Int64 but found Utf8
create table t1 (u union(num interger, str varchar)) as values
  (1),
  ('two');

Describe alternatives you've considered
No response
Additional context

Built Union on top of Struct
Impl with ScalarUDFImpl

I would like to work on this.

As I mentioned here https://github.com/apache/datafusion/issues/7845#issuecomment-2073675288, the most useful thing for me would be less ugly errors when you do try to compare a union with something else.
Also it would be good to be able to force people to cast unions in my case, so it would be nice if we could switch off comparison_coercion somehow.
@vaibhawvipul if you're working on this, you might be interested in my logic in datafusion-contrib/datafusion-functions-json/src/common_union.rs

My

As I mentioned here #7845 (comment), the most useful thing for me would be less ugly errors when you do try to compare a union with something else.
Also it would be good to be able to force people to cast unions in my case, so it would be nice if we could switch off comparison_coercion somehow.
@vaibhawvipul if you're working on this, you might be interested in my logic in datafusion-contrib/datafusion-functions-json/src/common_union.rs

This was helpful @samuelcolvin. Thank you.
My approach is similar -

adding support for arrow union datatype
need to support cast
will be extending functions to have union functions like union_extract.

take

I opened a PR that adds support for Union datatype on sqlparser which I hope can help here. If so, some review would be very appreciated, since sqlparser-rs dev-bandwith is a bit limited. Thanks 🙏


Adds a check if the phantomJS executable exists at the path.

:+1:

:+1:

👍

👍 's.... 👍 's everywhere.
Looks good to me, thanks for the PR!


Change ioctl test case for ADC to use greater than equal.

Description

Checklist:

[ ] I have tested my changes. No regression in existing tests.
[x ] My code is Linted.

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

@osloapps-max

/bot run checks


GEODE-10237: Remove no-ack from testThinClientTransactionsWithSticky

This removes the no-ack functionality from this test, which fails regularly in the CI.

This is, IMO, too much code to duplicate, and adding the new file rather than editing the existing one really obscures the nature of this change. Please try just editing ThinClientTrasactions.hpp and resubmit.

Good catch Blake! Not sure why I thought I needed to use a new header file. As you point out, just needed to refactor the original header.


Fix invalid links

Fix invalid links
[ ] Configuration Infrastructure
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@sniperking1234: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
b4122aa368580c03148fe19517e0d9889207f54d
link
/test gencheck_istio

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

@sniperking1234: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
b4122aa368580c03148fe19517e0d9889207f54d
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
b4122aa368580c03148fe19517e0d9889207f54d
link
/test integ-ipv6-k8s-tests_istio

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

/retest

@sniperking1234: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
b4122aa368580c03148fe19517e0d9889207f54d
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
b4122aa368580c03148fe19517e0d9889207f54d
link
/test gencheck_istio

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

@sniperking1234: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
d0e77354d4671fb9e6c9f7618cb13f2a8a05f863
link
/test gencheck_istio

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

@sniperking1234: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
d0e77354d4671fb9e6c9f7618cb13f2a8a05f863
link
/test gencheck_istio

unit-tests_istio
d0e77354d4671fb9e6c9f7618cb13f2a8a05f863
link
/test unit-tests_istio

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

@sniperking1234 please run make gen and include any changed files in your PR


Allow Horizontal Pod Autoscaler configurations in Controller Manager

What would you like to be added: Allow configuring Kube Controller Manager, specifically we interested in configuring horizontal-pod-autoscaler-sync-period which in kubernetes defaults to 15s
Why is this needed: Our system relies on horizontal pod autoscaler to scale in/out our servers based on CPU and Memory utilization. Due to different traffic patterns, 15s of sync period turns out to be a bit longer for us. We would like to configure it lower than that. It would be great if this is something which is allowed to configure on EKS

This repository is focused on the EKS-optimized node AMI; please open an issue (or +1 an existing one) on https://github.com/aws/containers-roadmap.
(I'm not able to transfer the issue for you because that repo is in a different GitHub org, sorry)

Hey, I just wanted to add to this feature request, that we also would like to be able to modify  --concurrent-horizontal-pod-autoscaler-syncs parameter, so that HPA can evaluate metrics more frequently (using higher concurrency). We understand starting from EKS 1.30 this value is dynamically increased based on the size of the managed control-plane, but we still think we may need higher concurrency setting. We would suggest you to introduce EKS Parameter Groups (similarly as RDS ones), so that customers can override control-plane configuration based on their needs!


Clicking on lightbulb sometimes adds word to dictionary.

Sometimes when I click on the light bulb icon it will add the word to the dictionary.  This happens because the menu starts to show on the mouse down then if the mouse happens to be over a menu item on mouse up it triggers the selection of that item.  When a misspelled word is toward the bottom of the screen and there is not room for the menu to go down, it will go up from the cursor (I'm on Windows).  The add to dictionary entries are at the bottom of the menu so they appear right under the cursor for (at least some) clicks of the light bulb.  If the menu could always appear slightly away from the cursor this would at least require some movement of the mouse to click on the add to dictionary entry.

Sorry about not answering sooner.
Yes, that can be very annoying. The best thing is to file an issue with VSCode. I do not have control over the light-bulb.

@fryguybob did you manage to open an issue on VS Code?

Hi @Jason3S, the latest VSCode (Version 1.18.0) does not have this problem.  The menu does not open until the mouse up.

Great! Thank you.


Support faker method options

What is the problem this feature would solve?
Currently the mapper in the faker js plugin will append the () to all the values, so that it cannot be customized.
mapper: {
          "status": "faker.random.arrayElement(['working', 'idle'])",
},

This example will eventually resolve to faker.random.arrayElement(['working', 'idle'])() which is wrong.
External documents/projects?
No response
What is the feature you are proposing to solve the problem?
Instead of appending the (), leave the decision to the user/config
What alternatives have you considered?
No response

@antipopp I'm working on a refactor related to the mappers. When this is done, your issue here will be resolved.

Fixed with v2.12.1


Do you support repeatCount & autoReverses in spring animation

Hi,

I am trying to make a cell shake. So I want to move it and reverse that and repeat the process:
cell.layer.springSpeed = 15;
cell.layer.springBounciness = 15;
cell.layer.autoreverses = YES;
cell.layer.repeatCount = 5;
cell.layer.spring.pop_positionY = cell.layer.position.y - 150;

This doesn't seem to work.

I don't think autoreverses and repeatCount properties are directly available on CALayer. You might want to fall back to the standard POP syntax for this edge case.

Ok. Thanks.