[Feature] implement tzip26, proof of event

to adapt tzip26

type of proposal_id is change to bytes
Resolve_proposal is renamed to Proof_of_event_challenge
emit event proof_of_event when resolve a proposal

other

fix test cases for upgrading the version of ligo compiler

version

promote version to 0.3 as the changes was incompatible to 0.1

@JulesGuesnon

I was wondering about the doc, as we mentioned that the challenge_id should be a concatenation of something dapp id + proposal number should we mention it in the documentation as a way to retrieve some dapp specific transactions ?

in this version, the challenge_id is equal to proposal_id. no much different from previous version.
The idea you are talking is about verify.  so far, the whole idea isn't clear. I'd go back this topic after letting tzsafe-ui support this version.
@tj825 when you are available, please help review the contract. I'll merge it first.


FlexCPU visualizer

Here's a thought. I'd like to see a visualization of this CPU. See the instructions in each of the queues and all of the instructions in the instruction window. I think this would be helpful in debugging.
This might be a good place to start with understanding the FlexCPU. It will also help debug the problems with it. I can draw what I'm thinking on the board next week.

[x] Add method to print inflight inst (with color for state?)
[x] Add method to thread to print all inflight insts in order
[x] Come up with cool visualization
[x] Add information about dependencies (maybe just a list)

This takes inspiration from the O3PipeView.
If you're really ambitious there's also this GUI for it that would be cool to replicate.

Done?

there's a minor bug; I'm fixing it

Done.

Mark this closed when you merge the PR #156 into flexcpu (#29)

Done!


pythonPackages.py3status: 3.0 -> 3.5

I also added some patches to fix binary paths.
pkgs.file is needed to detect file encoding.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Just to ping the maintainer: @garbas

ping

Sorry for not getting back to you, exams and stuff...
I actually disabled tests to make this work on Python 3, but I think I'll need to work on this again to also call the python3 version in all-packages.nix.
Then, I'll also try to run the tests in python3 (I think they are simply not run when using version 2), but because of all the modules used by some component of py3status, I don't think I will have much luck. NixOS and dynamic loading of dependencies just don't go together.

Actually, I think I'll open a new pull request when I have the time.


Missing Grids

There is an issue where the last grid it left off as in the image below. Its a server issue, not a client one.

Fixed in dev branch will be merged into release soon


added some images

👷 Deploy Preview for gladia processing.

Name
Link

🔨 Latest commit
5ae2412cdbd61d51d16dddd79a1071d34c142048

🔍 Latest deploy log
https://app.netlify.com/sites/gladia/deploys/668a80da602ebb0008bb22f3


Unable to set db_subnet_group_name for a replica.

Unable to set db_subnet_group_name for a replica (MySQL)
It's keep getting set same value as source database.
Looks like it's by design?

Looks like it's by AWS design, has nothing to do with TF...


Implement Irmin.compare_and_set

This is actually currently only implemented for the RW backend as it is the basis to ensure that Irmin.update is consistent. Could be useful to implement it in the high-level API though (instead of throwing a "TODO") though.

S.with_tree, S.set, S.set_treeandS.removenow have an optional argument?strategy` which can either be:

Set: "last writer wins" which was the only option in pre-1.0.
Test_and_set: atomic update of the subtree, checking if the previous subtree has changed and retrying the transaction if that's the case.


[Event Request] table 5407 "Prod. Order Component": CreateDim

Object: table 5407 "Prod. Order Component"
Function: CreateDim
Integration Event:
OnBeforeCreateDim(Rec, IsHandled);
local procedure OnBeforeCreateDim(var  ProdOrderComponent: Record "Prod. Order Component"; var IsHandled: Boolean)

There is already an OnAfterCreateDim(Rec, DefaultDimSource); at the end that has been implemented for another request, I assume that it will work in your case too, since you can replace all the dimension fields with whatever you want in that event?


Font sizes of the Jot briefs should have the same size but should have weight 700

Unread messages have timestamp with larger font than other messages. Size should stay same
but the font weight should be "bold"/700 for unread (both username and text).

https://github.com/unaio/jot-client-una/commit/91dd089297fbe717d9f45c7e8201954eb9b1ea14


Use of const in strict mode causing failures installing Node 0.12

NPM version: 2.11.3
Node version: 0.12.7
Node Process: { http_parser: '2.3',
node: '0.12.7',
v8: '<IP_ADDRESS>',
uv: '1.6.1',
zlib: '1.2.8',
modules: '14',
openssl: '1.0.1p' }
Node Platform: linux
Node architecture: x64
./ui/node_modules/gulp-sass/node_modules/node-sass/node_modules/request/node_modules/hawk/node_modules/boom/lib/index.js:5
const Hoek = require('hoek');
^^^^^
SyntaxError: Use of const in strict mode.
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/home/tbugge/mocat/ui/node_modules/gulp-sass/node_modules/node-sass/node_modules/request/node_modules/hawk/lib/index.js:5:33)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)

Looks like a dependency changed.  I took a quick look at the releases on hawk and boom and didn't see anything recent.  This stopped building with this error in the last hour or so.

We just hit this too. It looks like it was caused by this update to request:
https://github.com/request/request/commit/479143d546d6dff378da0e5fac5801dd3bf01f15

Indeed that was it.  In our package.json file we just added a hard set of request to version 2.81.0 which is before they set hawk to 6.x and that fixed the build.  So long as all your tests pass that is a work around.

This error message started to appear recently. Is there anything you guys suggest may be ?
/node_modules/grunt-sass/node_modules/node-sass/node_modules/request/node_modules/hawk/node_modules/boom/lib/index.js:5
11:16:32 const Hoek = require('hoek');
11:16:32 ^^^^^
11:16:32 SyntaxError: Use of const in strict mode.
11:16:32 at exports.runInThisContext (vm.js:73:16)
11:16:32 at Module._compile (module.js:443:25)
11:16:32 at Object.Module._extensions..js (module.js:478:10)
11:16:32 at Module.load (module.js:355:32)
11:16:32 at Function.Module._load (module.js:310:12)
11:16:32 at Module.require (module.js:365:17)
11:16:32 at require (module.js:384:17)
11:16:32 at Object. (/var/jenkins/workspace/artbees-portal/pr/253/node_modules/grunt-sass/node_modules/node-sass/node_modules/request/node_modules/hawk/lib/index.js:5:33)
11:16:32 at Module._compile (module.js:460:26)
11:16:32 at Object.Module._extensions..js (module.js:478:10)

got bitten by this too. had to lock request to 2.81.0

Looks like the way to prevent this is possible.
If you have a working version prior to update go to that installation and use:
npm shrinkwrap
or
npm shrinkwrap --dev

then a new file will be created

npm-shrinkwrap.json

Check that file and make sure dependencies are created. Normally this file has all the existing dependencies. Put that file in the folder which you run npm install inside. NPM will use the old versions and should work.
As an alternative you can remove all unrelated dependencies and keep only node-sass with request dependency.
          "node-sass": {
            "version": "2.1.1",
            "from"<EMAIL_ADDRESS><3.0.0",
            "resolved": "https://registry.npmjs.org/node-sass/-/node-sass-2.1.1.tgz",
            "dependencies": {
              "request": {
                "version": "2.79.0",
                "from"<EMAIL_ADDRESS><3.0.0",
                "resolved": "https://registry.npmjs.org/request/-/request-2.79.0.tgz",
              },
            }
          },

Hi @Bugget  - We are facing same issues and we are using node:0.12.7 version of image. Please can you help what changes are required to resolve this issue.

quick fix: npm install node-sass<EMAIL_ADDRESS>

Thanks for update. I am already having "npm install" used. Should I remove
this line and use one suggested by you.
I tried using npm install
npm install node-sass<EMAIL_ADDRESS>but still giving error.
On 21-Sep-2017 12:52 am, "Karsten"<EMAIL_ADDRESS>wrote:
quick fix: npm install node-sass<EMAIL_ADDRESS>—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2100#issuecomment-330954381, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aephblcclmp1fpSohNktz5zGsGDGy5s6ks5skWXdgaJpZM4PdDZz
.

I'm going to leave this unlocked, and not speaking for any of the other maintainers, but 0.12 has been EOL since January 1st. I don't know how much effort will be put into fixing this, but I do appreciate the folks suggesting the workaround by pinning the request dependency.

@majidpal to fix versions you'll need prune, shrinkwrap and a correct package.json. In a fresh repo that would look like:
npm install node-sass<EMAIL_ADDRESS>shrinkwrap
npm init # make sure <=2.81.0
npm prune
npm shrinkwrap

Thanks you for response. We are planning to move away with this version but
the for temprary need to fix so that work can continue. I am using below in
my jobs -
./docker run --rm -t
-v "/data/jenkins/home/jobs/test/workspace/:/src/"
node:0.12.7 bash -c "git config --global url."https://".insteadOf git://;

cd /src;
npm install;
npm install -g bower;
bower install --allow-root --config.interactive=false ;
npm run build
npm run cache-buster
npm run www-build-index"
in my package.json we have  gulp-sass": "^2.1.1"
Please let me know what to change. Appreciate help.
On Thu, Sep 21, 2017 at 9:49 AM, Karsten<EMAIL_ADDRESS>wrote:

@majidpal https://github.com/majidpal to fix versions you'll need
prune, shrinkwrap and a correct package.json. In a fresh repo that would
look like:
npm install node-sass<EMAIL_ADDRESS>shrinkwrap
npm init # make sure <=2.81.0
npm prune
npm shrinkwrap
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2100#issuecomment-331046889,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aephbuj6n9vpD2-VUPtx1yOxytzDs4nGks5skeO8gaJpZM4PdDZz
.

We were able to resolve issue by adding bolded line. This needs to comer before npm install  -
./docker run --rm -t
-v "/data/jenkins/home/jobs/test/workspace/:/src/"
node:0.12.7 bash -c "git config --global url."https://".insteadOf git://;
cd /src;
npm install gulp-sass<EMAIL_ADDRESS>
npm install;
npm install -g bower;
bower install --allow-root --config.interactive=false ;
npm run build
npm run cache-buster
npm run www-build-index"
Still have an open question - We had tried using latest version of image node:6.3.5 but still it was failing. I hope latest node image should have point to current version of gulp-sass.
Can you please let me know which latest stable version we should use so that explicit download of gulp-sass is not required?

Looks like this is all caused by https://github.com/hueniverse/hawk/issues/153 from 2 years ago...

@nschonni @xzyfer what about making a snapshot release locked to<EMAIL_ADDRESS>and being the last one to support 0.10, 0.12 (and provide binaries for them)?

We're experiencing this issue with our Travis CI job for the Select2 repo: https://travis-ci.org/select2/select2/jobs/279037851.  How does npm install node-sass<EMAIL_ADDRESS>translate into a change in our package.json?

package.json generated from my previous comment:
{
<SNIP>
  "dependencies": {
    "node-sass": "^4.5.3",
    "request": "<=2.81.0",
    "shrinkwrap": "^0.4.0"
  },
<SNIP>
}

Switch to using package.json and npm-shrinkwrap.json to manage transitive dependencies deterministically.
https://github.com/uber/npm-shrinkwrap
https://docs.npmjs.com/files/package.json

Thanks!  I'm pretty green with respect to npm and Node in general (I'm primarily a PHP developer), but I'll bring this up with the project creators!

Updating nom and nodejs worked for me:
sudo apt-get install -y nodejs
npm install -g npm@latest```

We've run into this as well across a few of our environments. Success locally with the temporary fix provided by @kmcminn and are trying to update our deployment scripts now accordingly.

Below error/issue resolved with this solution:
Solution:
sed -i '27 a "request":"2.81.0",' /opt/apache-ambari-2.2.2-src/ambari-web/package.json
I just added specified "request" version(older version "2.81.0")  in "package.json" file below problem resolved.
Here is my error:
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
[DEBUG] Configuring mojo org.codehaus.mojo:exec-maven-plugin:1.2.1:exec from plugin realm ClassRealm[plugin>org.codehaus.mojo:exec-maven-plugin:1.2.1, parent: sun.misc.Launcher$AppClassLoader@5c647e05]
[DEBUG] Configuring mojo 'org.codehaus.mojo:exec-maven-plugin:1.2.1:exec' with basic configurator -->
[DEBUG]   (f) basedir = /opt/apache-ambari-2.2.2-src/ambari-web
[DEBUG]   (f) classpathScope = runtime
[DEBUG]   (f) commandlineArgs =  build
[DEBUG]   (f) executable = brunch
[DEBUG]   (f) longClasspath = false
[DEBUG]   (f) project = MavenProject: org.apache.ambari:ambari-web:<IP_ADDRESS>.0 @ /opt/apache-ambari-2.2.2-src/ambari-web/pom.xml
[DEBUG]   (f) session = org.apache.maven.execution.MavenSession@5ce4369b
[DEBUG]   (f) skip = false
[DEBUG]   (f) workingDirectory = /opt/apache-ambari-2.2.2-src/ambari-web
[DEBUG] -- end configuration --
[DEBUG] Executing command line: brunch build
/opt/apache-ambari-2.2.2-src/ambari-web/node_modules/ember-precompiler-brunch/node_modules/jsdom/node_modules/request/node_modules/hawk/node_modules/boom/lib/index.js:5
const Hoek = require('hoek');
^^^^^
Error: You probably need to execute npm install to install brunch plugins. SyntaxError: Use of const in strict mode.
at /opt/node-v0.10.44-linux-x64/lib/node_modules/brunch/lib/watch.js:433:19
at Array.map (native)
at loadDeps (/opt/node-v0.10.44-linux-x64/lib/node_modules/brunch/lib/watch.js:418:10)
at loadPackages (/opt/node-v0.10.44-linux-x64/lib/node_modules/brunch/lib/watch.js:438:15)
at /opt/node-v0.10.44-linux-x64/lib/node_modules/brunch/lib/watch.js:458:19
at /opt/node-v0.10.44-linux-x64/lib/node_modules/brunch/lib/helpers.js:529:16
at /opt/node-v0.10.44-linux-x64/lib/node_modules/brunch/lib/helpers.js:485:14
at /opt/node-v0.10.44-linux-x64/lib/node_modules/brunch/node_modules/read-components/index.js:263:16
at /opt/node-v0.10.44-linux-x64/lib/node_modules/brunch/node_modules/read-components/index.js:72:14
at Object.cb [as oncomplete] (fs.js:169:19)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main ........................................ SUCCESS [  3.970 s]
[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.591 s]
[INFO] Ambari Web ......................................... FAILURE [01:08 min]

update to ^2.8 solved for me

Looks like request switched to hawk 3.1.3 in https://github.com/request/request/pull/2789

We're already locked to a handful of outdate packages that have dropped Node 0.10 support. I'm not sure how long we can continue to do this dance though when any transitive dependency can hurt us like this.
We'll be officially dropping support for Node < 6 in node-sass@v5 later this year. In the mean time I suggest we

continue to support old Node versions in the form of supplying prebuilt binaries
create a locked issue documenting how to install a working version of request for Node < 4

Thoughts @saper @nschonni ?

@xzyfer I think adding it to the TROUBLESHOOTING or README might be helpful. When we break in 5, we can make an explicit message too

Node Sass 4.x continues to support Node < 4.
However due to some of our dependencies dropping support older Node versions npm install will fail an error like
SyntaxError: Use of const in strict mode.

This is out of our control. We recommend updating Node to an active LTS or current version 6, 7, or 8 if possible. If you must support Node < 4 you can explicitly install an older version of request for node-sass to use by running the following
npm install --save<EMAIL_ADDRESS>

@Michael - I wanted to move to latest node and i did trued node 6.X version
but it was still failing with same error "SyntaxError: Use of const in
strict mode."
Please let me konw which is the stable latest version available and steps
for them , so that I can put this up to development team and migrate to
that.
Thanks for support.
On Fri, Oct 6, 2017 at 9:21 AM, Michael Mifsud<EMAIL_ADDRESS>wrote:

Closed #2100 https://github.com/sass/node-sass/issues/2100.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2100#event-1281100966, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AephbjUJpkvcxuxf1YjJfWstJTZRrHNkks5spaPTgaJpZM4PdDZz
.

@xzyfer, thanks for the solution! Curious how this works as it goes against my understanding of how NPM v2 structures its dependencies (which would be the version tied to > node 4)
https://docs.npmjs.com/how-npm-works/npm2
Since node-sass specifies it's version of request my understanding was that it would use this version in it's dependency tree, and ignore the version specified by the user's dependencies?

I had this happen using manifoldJS for packaging an edge extension.
to fix it I had to update
C:\Users\eyal\AppData\Roaming\npm\node_modules\manifoldjs\node_modules\manifoldjs-lib\package.json
changing the request dependency to
"request": "<=2.81.0",

This is resolved in the latest node-sass. Run npm update node-sass
On 5 Feb. 2018 3:19 am, "Eyal Lewinsohn"<EMAIL_ADDRESS>wrote:

I had this happen using manifoldJS for packaging an edge extension.
to fix it I had to update
C:\Users\eyal\AppData\Roaming\npm\node_modules\manifoldjs
node_modules\manifoldjs-lib\package.json
changing the request dependency to
"request": "<=2.81.0",
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2100#issuecomment-362919095,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWO5wIC_G7ODntoVLRCMtzdr-0Dntks5tRdiUgaJpZM4PdDZz
.


Treeshaking: Named export of objects includes whole file into the bundle instead of only used exports. (with sideEffects: false in package.json)

Bug report

What is the current behavior?
Creating a bunch of objects in a single file while directly exporting them from there with named exports will cause the whole file to be included in the bundle instead of treeshaking the unused exports.
Using a barreling approach where every object gets created and exported from its own file will treeshake correctly.
If the current behavior is a bug, please provide the steps to reproduce.
This repo let's you reproduce this behavior.
https://github.com/Huuums/repro-webpack-treeshaking-object-issue

What is the expected behavior?
Only include used exports into the bundle when defining multiple exports in a single file.

Other relevant information:
webpack version: 4.41.5
Node.js version: 13.6
Operating System: Mac OS (Catalina) and Windows behaved the same.
Additional tools: Create React App
mode: 'production' is set (Create react apps build script).

JSX is considered as side-effecty code, so you need to put it into a function to allow it to be removed.

https://github.com/babel/babel/pull/11126

babel fix was merged


Return value of Each()

The Each function returns the original list to the caller, which is not very functional because the caller passed it in.
A much more useful return value would be the values returned by the lambda functions. It is telling that all of the each test cases declare a variable which will be used to accumulate the lambda values.

Actually, in its current version, which is not yet released though, it is actually returning the value of the each lambda, allowing for transformations and such of lists.
Sorry for not having made a release of this yet though. I'll spend some time this weekend, and get a new release out the door ...


How to implement it at the same time autoplay and seamless slide screen?

Your component library is great！
but How to implement it at the same time autoplay and seamless slide screen?
I'm a novice，
Hope to get a reply！

We have a demo showing how to use the autoplay in the documentation.


BorderRadius doesn't affect media

Hey,
I'm trying to add border radius to the media but it doesn't work:
media: AdMediaView(
        decoration: AdDecoration(
          borderRadius: AdBorderRadius.all(10),
        ),
      ),

Also tried wrapping the NativeAd in ClipRRect, it also didn't work.
Please advise,
Thanks.

You can't apply a border radius to asset views, such as AdMediaView or AdIconView

Understandable, Thanks 👍


Fix fs info reporting negative available size

Description
Today, the fs info may report a negative available size, which happens when the following conditions are met:

A node has both data and search roles.
Some space is reserved for file cache.
The file cache space is being used by other files, primarily local indices files.

Related exception:
java.lang.IllegalArgumentException: Values less than -1 bytes are not supported: -1781760b
	at org.opensearch.core.common.unit.ByteSizeValue.<init>(ByteSizeValue.java:78) ~[classes/:?]
	at org.opensearch.core.common.unit.ByteSizeValue.<init>(ByteSizeValue.java:73) ~[classes/:?]
	at org.opensearch.monitor.fs.FsInfo$Path.getAvailable(FsInfo.java:141) ~[classes/:?]
	at org.opensearch.cluster.InternalClusterInfoService.fillDiskUsagePerNode(InternalClusterInfoService.java:452) ~[classes/:?]
	at org.opensearch.cluster.InternalClusterInfoService$1.onResponse(InternalClusterInfoService.java:265) ~[classes/:?]
	at org.opensearch.cluster.InternalClusterInfoService$1.onResponse(InternalClusterInfoService.java:260) [classes/:?]
	at org.opensearch.action.LatchedActionListener.onResponse(LatchedActionListener.java:58) [classes/:?]
	at org.opensearch.action.support.TransportAction$1.onResponse(TransportAction.java:113) ~[classes/:?]
	at org.opensearch.action.support.TransportAction$1.onResponse(TransportAction.java:107) [classes/:?]
	at org.opensearch.action.ActionRunnable.lambda$supply$0(ActionRunnable.java:74) [classes/:?]
	at org.opensearch.action.ActionRunnable$2.doRun(ActionRunnable.java:89) ~[classes/:?]
	at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [classes/:?]
	at org.opensearch.common.util.concurrent.OpenSearchExecutors$DirectExecutorService.execute(OpenSearchExecutors.java:341) [classes/:?]
	at org.opensearch.action.support.nodes.TransportNodesAction$AsyncAction.finishHim(TransportNodesAction.java:315) [classes/:?]

Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

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

Thanks for the changes @bugmakerrrrrr. Can you please add in a changelog entry in the 2.x section?

Update: Path.free includes both bytes that are available for allocation and bytes that are reserved for privileged processes, so we cannot make a direct comparison between the free, available, and fileCacheReserved values.

@bugmakerrrrrr Looks like the test is still failing: https://build.ci.opensearch.org/job/gradle-check/31254/testReport/org.opensearch.monitor.fs/FsProbeTests/testFsInfoWhenFileCacheOccupied/

@kotwanikunal Fixed. 1. We cannot rely on the available value because the available space will change as the test progresses. 2. free space includes both bytes that are available for allocation and bytes that are reserved for privileged processes, so we cannot make a direct comparison between the free, available, and fileCacheReserved values.

@kotwanikunal hi, can we merge this pr?

@kotwanikunal hi, can we merge this pr?

Sure. Let me try to get it to green. Current failures seem to be unrelated.

Take 2: looks like the failure is related
* What went wrong:
Execution failed for task ':server:spotlessJavaCheck'.
> The following files had format violations:
      src/test/java/org/opensearch/monitor/fs/FsProbeTests.java
          @@ -45,12 +45,9 @@
           import·org.opensearch.index.store.remote.filecache.FileCacheFactory;
           import·org.opensearch.test.OpenSearchTestCase;

          -import·java.io.BufferedWriter;
           import·java.io.IOException;
           import·java.nio.file.FileStore;
          -import·java.nio.file.Files;
           import·java.nio.file.Path;
          -import·java.nio.file.StandardOpenOption;
           import·java.nio.file.attribute.FileAttributeView;
           import·java.nio.file.attribute.FileStoreAttributeView;
           import·java.util.Arrays;
  Run './gradlew :server:spotlessApply' to fix these violations.

@bugmakerrrrrr can you please run ./gradlew spotlessApply? And while you are at it, do you mind rebasing as well?
Thanks :)

Take 2: looks like the failure is related
* What went wrong:
Execution failed for task ':server:spotlessJavaCheck'.
> The following files had format violations:
      src/test/java/org/opensearch/monitor/fs/FsProbeTests.java
          @@ -45,12 +45,9 @@
           import·org.opensearch.index.store.remote.filecache.FileCacheFactory;
           import·org.opensearch.test.OpenSearchTestCase;

          -import·java.io.BufferedWriter;
           import·java.io.IOException;
           import·java.nio.file.FileStore;
          -import·java.nio.file.Files;
           import·java.nio.file.Path;
          -import·java.nio.file.StandardOpenOption;
           import·java.nio.file.attribute.FileAttributeView;
           import·java.nio.file.attribute.FileStoreAttributeView;
           import·java.util.Arrays;
  Run './gradlew :server:spotlessApply' to fix these violations.

@bugmakerrrrrr can you please run ./gradlew spotlessApply? And while you are at it, do you mind rebasing as well? Thanks :)

@kotwanikunal done.

@bugmakerrrrrr Are you planning to continue on this PR and targeting any upcoming release?
This has been stalled now, and if this is not planned to be continued, lets close this.

@kotwanikunal Is there anything else I can do for this PR? or should I close this?

@bugmakerrrrrr We need to get the Gradle Check step to pass in order to merge PRs. Sometimes the Gradle Check will fail due to flaky tests, you can refer to: https://github.com/opensearch-project/OpenSearch/blob/main/DEVELOPER_GUIDE.md#flaky-tests
Specifically here it looks like you need to rebase your branch and fix the merge conflicts and then see if there are any more test failures. Thank you!

@bugmakerrrrrr Sorry for the delay here. I've pushed a rebase and fixed up the changelog conflicts.

hi @andrross, can we merge this


HP G3 Tegra K1 Hardware Acceleration or improvements.

Good day fellow Gitters.
I've been using Crouton on my Chromebooks for a very long time, since the very first revision was made. Everything had always worked great, until I broke things.. Anyways, I just bought a new addition to the family, the HP G3 Tegra K1 powered Chromebook. I chose this over the Intel variants for more native ARC support for android applications. Which works great.
Then comes crouton; not very good. It's not crouton itself obviously, it's the lack of hardware acceleration from the GPU. I'm aware it's all down to the drivers, but has their been any improvements or even alternatives if native support is not possible. I mean, maybe some kind of faster alternative to iwix... I've tried all the major DE's, my hopes lie dying that XFCE or LXDE would have some kind of speed boost without direct acceleration. But, sheesh, moving windows around reminds me of running windows 98 on a 25Mhz 80486. It's just aweful. I thought that maybe I set something wrong, so I tried all the major desktops in both Xephyr and iwix. Latter is quicker, but very buggy when switching windows. Xephyr is too slow.
Does anyone have any hacks or improvements on getting atleast some basic acceptable speed out of this? CPU hangs around ~20% and the 4GB of RAM is more than plenty.
I tried Chrubuntu, but all of the setup scripts i've ran across are broken on the HP G3 (No Wifi driver, and they cannot detect the display so I get stuck with a TTy window.)
Any help is greatly appreciated in getting either Crouton working quicker, or pointing me in the direction of a Chrubuntu script that is not garbage.
Thank you for taking the time to at least make it this far.
-Sam

See https://github.com/dnschneid/crouton/issues/1089
It has been noticed for a while and tried to solve.

@tonyxue
"The armxorg stuff will be merged alongside the x11_freon branch (#1415), but that only provides access the the T1's framebuffer device, not real acceleration."
Hmm, I've not tried fbdev.. Is that supported out of the box by a install flag? Or in a config?

https://github.com/dnschneid/crouton/commit/0fafa652779f96aff7ce432643b02b0b4898054f
It helps you take care of it already. Is this something you are looking for?
If you are on the latest Crouton, that's the best solution so far.

Ahh, yes I see. I just re-installed Crouton this morning, So I'd assume I was using the latest as it was retrieved from GitHub.. I'm installing via the x11_Freon, as we speak. I'll keep this updated until I find the best available solution.


fft

What type of PR is this?

[ ] Add a new dev container collection
[ ] Update to an existing dev container collection
[ ] Documentation/spec update
[ ] Other containers.dev site update (UX, layout, etc)

Related Issues

Related Issue #
Closes #

Description
Please replace this line with a description of your PR.
Collection checklist
If your PR contributes a new collection, please utilize this checklist:

[ ] Collection name
[ ] Maintainer name
[ ] Maintainer contact link (i.e. link to a GitHub repo, email)
[ ] Repository URL
[ ] OCI Reference
[ ] I acknowledge that this collection provides new functionality, distinct from the existing collections part of this index.

Looks like this was created by accident, closing. If needed, feel free to reopen with more details, thank you!


Missing Data in Graphs on Comparison Charts

Something is not updated in the comparisons from our latest API endpoint updates.  Look at this:

Fixed in this commit.


Support ts 5.5 tsconfig.json with ${configDir}

Hello! Recently, ts 5.5 was announced in beta with new feature https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-beta/#the-configdir-template-variable-for-configuration-files
This lets us share tsconfig across packages, and I wanted to use it for my monorepo, but ctix cannot find the files properly, my guess is that it's still using an older version of typescript, I'm not sure if it's this package? or from the ts-morph package where it wraps the ts compiler API, I can think of perhaps 2 ways to solve it here:
Have a "next" branch that ups the deps to the beta version as well and simply just publish it as an alpha/beta
Have the typescript dep as a peerDep? and have userland install the required version? I'm not sure if that actually works, just a thought
For reference I used with typescript ver: "5.5.0-dev.20240518",
and shared configuration package I'm trying to create: https://github.com/Esposter/Esposter/tree/shared-configuration/packages/configuration
usage: https://github.com/Esposter/Esposter/blob/shared-configuration/packages/shared/package.json

@imjuni Yep! It serves as a good workaround for now, for others who also want to use this feature, here's my PR which hopefully provides a good enough example of how to use it https://github.com/Esposter/Esposter/pull/249/files
using pnpm workspaces and pnpm overrides. I think we can leave this open until ts 5.5 is released and we should be able to remove the overrides workaround after

@Q16solver Hello, thank you for your patience
ctix now supports TypeScript 5.5. I also tested the peerDependencies you suggested and it works fine, so I moved TypeScript to peerDependencies.

Seems to work now, thanks!

@Q16solver Can you please provide a reproducible repo, or tell me what I need to do in the repo mentioned in the first issue. Thank you.

@imjuni If you fork my repo:

change to shared-configuration branch
Pnpm i
Cd packages/shared for example
Run build

You should encounter the issue that dist files are empty. If you then change the tsconfig to be the non config dir one (you can reference main branch), then ctix generates fine

@Q16solver Hello,
Due to my recent personal circumstances, it is difficult for me to analyse the problem at this code level. I looked at the repo you uploaded and saw that the include' and exclude' options are missing from the .ctirc' file. Could you please add the includeandexcludeoptions to your.ctircfile and try again? Theincludeandexcludeoptions work the same as in thetsconfig.json` file.
I think the problem is that the tsconfig.json file in the shared project doesn't have the include and exclude options, so it can't find the project files to add to the index.ts file.

@imjuni oh you're right! seems like doing **/*.ts in include option fixes this. Maybe there's some issue now with ctix trying to use $configDir in tsconfig and would only work with normal paths. But either way, this is a good enough workaround, I'm happy for us to close this now, thanks so much C:

@Q16solver
ctix looks for the target file in the include option; if there is no include option, it uses the TypeScript Compiler API to read the tsconfig.json file and use the SourceFiles list included in the Config object instead of ctix's include option.
However, if neither the ctix include option nor the include option in the tsconfig.json file is present, it creates an empty index.ts file.
I'll add a feature to tell about this in the next version to make it more obvious, thanks.

Yeah, though it seems like if the include in tsconfig has $configDir, it doesn't read it properly, might be some weird incompatibilities with how I've specified it with $configDir/src/**/*.ts


[18.09] python.pkgs.pygraphviz: add graphviz path

Motivation for this change
Backport of #51501, since it fixes a bug.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build python2.pkgs.pygraphviz python3.pkgs.pygraphviz

Sorry for all the requested review, selected the wrong base and githubs code owner system went wild.


Lesson 8 ViT Patch Embeddings

I've read the paper several times and I think the patch embeddings are created by:

creating patches from raw image (224*224*3 [H,W,C] -> 196*14*14*3 [n,h,w,c])
flattening patches (196*16*16*3 [n,h,w,c] -> 196*768 [n,h*w*c])
transforming patches by a trainable linear projection E (196*768 [n,h*w*c] -> 196*D [n, latent_dim])
adding [class] embedding (196*D [n, latent_dim] -> 197*D [n+1, latent_dim])

Rather than using Conv2D with out_channel = 768?
Any answer is appreciated.

Never mind me.


Infinite loop when expanding indexes

I think the problem seen on https://github.com/UUDigitalHumanitieslab/mwe-query/blob/bug/expand-cycle/tests/test_expand.py is the results of two index nodes being expanded together.
Here's what the tree from that example looks like before expansion:

And this is after expansion (which is ended prematurely), with the cycle highlighted in red:

(The original sentence is: "Ik ben blij met de taakverdeling die u voor ogen staat waarbij beslissingen over voeding de bevoegheid van de Europese instellingen onder meer die van de Commissie en het Parlement")

This was fixed a while ago


Investigate adding semantic actions

Currently a tree is automatically created to support the packrat operation as well as transform. However, for full flexibility it should also be possible for the user to define his/her own output. To do this requires two things:

The ability to add an action to a rule
A method in the code to not automatically generate a tree

One option to do this might be to define a default rule, which automatically creates the AST, which can then be overridden with a user-defined function.

Added first attempt for semantic actions. An example of a semantic action being attached to a rule:
number = (-space + r"[1-9][0-9]*") { parseint(_1.value) }

Quick notes:

Curly braces are now used
Either expressions or functions are allowed
For now _i is an alias for children[i]. Not entire sure the underscore is the best symbol, but something is required that isn't likely to cause a name conflict.

The examples calc1.jl, calc2.jl, and calc3.jl are updated to reflect this.  The other examples need to be updated.

Semantic appear to be working properly.


Upgrade github action

Signed-off-by: Mike Ng<EMAIL_ADDRESS>Need to upgrade GitHub action. See https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ for more details.

/lgtm


Add Styling concept md

closes #63
Changes
Add a new markdown file that describes the styling concept of our website.
describe problem here
So far styling was inconsistent and not modular.
Checklist before merge
Developer's responsibilities

[ ] Assign one or two developers
[ ] Change code if reviewer(s) has/have requested it
[ ] Pull request build has passed
[ ] tested locally (in at least chrome & firefox if frontend)
[ ] updated the documentation
[ ] added tests where necessary

I miss the formatting (syntax highlighting) of the code blocks in the corresponding programming language.

true I have overwritten the changes accidentally. Now it should work again


Customize 0140T with new Navi App

Hi,
I habe a patched 0140T installed, but the navigation is quite buggy. Is it possible to either leave the 0140T train (I heared it‘s not), or can I manually copy the navigation app from a newer firmware?

Update to 254


qa for param

Testing pr 562

uhh

/assign

umm

Try again maybe but slower? QA uses GitHub actions runtime which is significantly slower to cold start.
Like 13 seconds vs 500ms difference.

but this difference is like 11 hours vs 500 ms

/assign

yep its working now

/unassign

/start

/start

/start

/wallet 0xa611a37657A76583305F557D63B94834a35C7bF4


Unable to connect to Ollie after using sphero.js

I am on a Macbook Pro.
Used $ node ./node_modules/noble/examples/advertisement-discovery.js to find Ollie's UUID and then ran ran the below code with my UUID.
var sphero = require("sphero"),
   bb8 = sphero("F3:F2:6D:55:71:09"); // change BLE address accordingly

bb8.connect(function() {
  // roll BB-8 in a random direction, changing direction every second
  setInterval(function() {
    var direction = Math.floor(Math.random() * 360);
    bb8.roll(150, direction);
  }, 1000);
});

Ollie connected quickly and started rolling around. Then I killed the script that I was running from the command line using CTRL + C.
After this I have not been able to connect to Ollie again, even the app has stopped working with it.
I have tried charging Ollie to full, waking up Ollie by inserting and removing the USB cable..
Any ideas?
Disclaimer: I have no idea what caused this and it may in fact not be related to the sphero.js project at all. I have also opened a support ticket with Sphero.

Here is a log from what a connection attempt looks like now...
https://gist.github.com/foopod/d022a75f3fc325614a79932aa53edce7

Took it apart and the phone could connect if held super close to the antenna, it was a little bent, so I straightened it up(shhhh.. don't tell sphero) and now it seems to work fine.


Suggestion: Check case of configuration filenames to avoid cross-platform incompatibilities

Following discussion on Reddit, I think it might be a good idea if dep checked the case of the names of its configuration files such as Gopkg.toml, at least on Mac.
This would prevent the problem of Mac users checking in a project with gopkg.toml in lower case, which works on the Mac (because it's case-insensitive) but fails on Linux.

@sdboyer Can I work on this? If yes, can you point me in the right direction wrt where I would have to make the changes?

@sudo-suhas yes, absolutely! 🎉 🎉
the key place to look will be in Ctx.LoadProject(). that's where the check will need to happen.
as for doing the check itself, you'll probably want to take inspiration from fs.isCaseSensitiveFilesystem(), though i'd prefer we do a bit of copying rather than exporting it directly, at least for now.
that should be enough to get you started - please let me know what other pointers would be helpful!

@sdboyer I took a look at the functions you pointed to. However, I think the problem here is slightly different. What I need to do is check if the Gopkg.toml exists with an incorrect case. Which can mean any of gopkg.toml, gopkg.TOML, GoPkg.toml etc. The simple way would be, ask for os.stat(ManifestName) and cross check the contents of stat.Name(). However, this simply returns the name we supplied for getting stats and not the actual file name:
package main

import (
	"fmt"
	"os"
)

func main() {
	fileStat, err := os.Stat("./test.txt")
	if err != nil {
		panic(err)
	}
	fmt.Println(fileStat.Name())
}

$ ls
main.go  Test.txt

$ go run main.go
test.txt

The only way to print the exact case of the file that I have been able to figure out is to use File#Readdir:
package main

import (
	"fmt"
	"os"
	"path/filepath"
)

func main() {
	dirname := "." + string(filepath.Separator)

	d, err := os.Open(dirname)
	if err != nil {
		fmt.Println(err)
		os.Exit(1)
	}
	defer d.Close()

	files, err := d.Readdir(-1)
	if err != nil {
		fmt.Println(err)
		os.Exit(1)
	}

	fmt.Println("Reading " + dirname)

	for _, file := range files {
		if file.Mode().IsRegular() {
			if filepath.Ext(file.Name()) == ".txt" {
				fmt.Println(file.Name())
			}
		}
	}
}

$ go run main.go
Reading .\
Test.txt

However this is quite wasteful. Is there any better way to do this?

However this is quite wasteful. Is there any better way to do this?

there is not, AFAIK. that's why i was loathe to recommend it, and just suggested the crappier approach of trying the one case variation. you're right, of course, that we have to try all the combinations if we actually want to truly enforce this as a rule.
the best i can offer is that you can at least avoid having to os.Stat() everything by doing case-insensitive comparison of each of the files in the list using strings.FoldEqual()


React example

@victory-sokolov @robbernan  I am struggling to use the library with React. Could you please add a sample code snippet?

Hey @robbernan ,
Any news on a React sample?

any updates on React usage examples?

I would love to integrate nordigen bank ui with my angular app...

@adroneleh could you share an open repository with an example?


Invalid record spread syntax

{...foo};

This is invalid syntax. [...bar] works and prints as plain bar; for consistency, {...foo} should print as foo.

one question: Is it confusing that {...foo} would become foo? I believe the ES6 spread is supposed to make a new allocation when using {...} (which matters when there are mutable fields etc).

 Dunno but it shouldn't throw a syntax error I think.

As discussed in #704, the diff works on syntax level, but fails at invariants in the compilation. Reopening the issue and will continue discussion in the diff.

Close please


Assist Microphone Addon: microphone detected but does not pickup any audio

Hi, for the last couple of days I was playing with Assist Microphone Add-on for HA. Unfortunately I cannot get it working. I can see the microphone is detected but nothing happens. I know that the open_wakeword addon works fine as I can test it via assist in the web browser (over https connection). I am using a generic mic/speaker set (like this one: https://www.aliexpress.com/item/1005005929228163.html). I tested it on my standalone debian pc and that worked without any drivers (plug and play).
My system
Proxmox VM with HA OS (pass through USB hub and generic mic/speaker)
Home Assistant 2023.10.5
Supervisor 2023.10.1
Operating System 11.1
Frontend 20231005.0
Connected Speakers/Mics/Sound Cards - speaker/mic connected to a pass through hub that I know it is working as I have my zwave stick connected to it and HA is correctly detecting that speaker/mic device:
ha audio info
audio:
  application:
  - addon: 47701997_assist_microphone
    index: 2
    mute: false
    name: ALSA plug-in [aplay]
    stream_index: 1
    stream_type: input
    volume: 1
  card:
  - driver: module-alsa-card.c
    index: 0
    name: alsa_card.usb-BY_BY_Y02_20180508-00
    profiles:
    - active: false
      description: Analog Stereo Input
      name: input:analog-stereo
    - active: false
      description: Digital Stereo (IEC958) Input
      name: input:iec958-stereo
    - active: false
      description: Analog Stereo Output
      name: output:analog-stereo
    - active: true
      description: Analog Stereo Duplex
      name: output:analog-stereo+input:analog-stereo
    - active: false
      description: Analog Stereo Output + Digital Stereo (IEC958) Input
      name: output:analog-stereo+input:iec958-stereo
    - active: false
      description: Digital Stereo (IEC958) Output
      name: output:iec958-stereo
    - active: false
      description: Digital Stereo (IEC958) Output + Analog Stereo Input
      name: output:iec958-stereo+input:analog-stereo
    - active: false
      description: Digital Stereo Duplex (IEC958)
      name: output:iec958-stereo+input:iec958-stereo
    - active: false
      description: "Off"
      name: "off"
  input:
  - applications:
    - addon: 47701997_assist_microphone
      index: 2
      mute: false
      name: ALSA plug-in [aplay]
      stream_index: 1
      stream_type: input
      volume: 1
    card: 0
    default: true
    description: BY Y02 Analog Stereo
    index: 1
    mute: false
    name: alsa_input.usb-BY_BY_Y02_20180508-00.analog-stereo
    volume: 0.5495452880859375
  output:
  - applications: []
    card: 0
    default: true
    description: BY Y02 Analog Stereo
    index: 2
    mute: false
    name: alsa_output.usb-BY_BY_Y02_20180508-00.analog-stereo
    volume: 0.860992431640625
host: <IP_ADDRESS>
update_available: false
version: 2023.06.0
version_latest: 2023.06.0

Assist Microphone Logs
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service assist_microphone: starting
s6-rc: info: service assist_microphone successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
DEBUG:__main__:Namespace(host='homeassistant', token='REMOVED', port=8123, api_path='/api', pipeline='', protocol='http', mic_device=None, snd_device=None, mic_command=None, snd_command=None, snd_command_sample_rate=22050, awake_sound='/usr/src/sounds/awake.wav', done_sound='/usr/src/sounds/done.wav', volume=1.0, vad='silero', vad_model=PosixPath('/usr/local/lib/python3.11/dist-packages/homeassistant_satellite/models/silero_vad.onnx'), vad_threshold=0.5, vad_trigger_level=3, vad_buffer_chunks=40, wake_buffer_seconds=0.0, noise_suppression=2, auto_gain=15, volume_multiplier=1.0, udp_mic=None, udp_snd=None, udp_snd_sample_rate=22050, debug_recording_dir='', debug=True)
DEBUG:__main__:Waiting for speech
DEBUG:__main__:Using webrtc audio processing
2023-10-29 12:20:41.278480944 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '131'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278540429 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '136'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278552608 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '139'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278561751 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '140'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278570442 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '134'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278638153 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '628'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278650253 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '623'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278659081 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '629'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278667310 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '620'. It is not used by any node and should be removed from the model.
2023-10-29 12:20:41.278688366 [W:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing initializer '625'. It is not used by any node and should be removed from the model.
DEBUG:__main__:Using silero VAD
DEBUG:root:Microphone command: ['arecord', '-r', '16000', '-c', '1', '-f', 'S16_LE', '-t', 'raw']
Recording raw data 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono

Where am I going wrong?
Thanks

Hello, same situation for me.
Everything seems ok but the wake work is never detected.
I've tried the same pipeline with my phone and assist and it works, I've done an esp32+mic (with wakeword enable) and it works but nothing with the embedded Assist Microphone USB. The microphone is detected, seems to work but not...
I've already used this mic with Rhasspy and it's working like a charm.
Configuration :

Home Assistant in VM with microphone USB passthrough on server 1.
Dockered pipeline (Piper, OpenWakeword and Whisper) in LXC on server 2 (i've tested the Pipeline integrated in the Home Assistant VM but CPU was nearly at 100% and needed 5-10 seconds for STT, now i'm at 1 second for STT).

The only thing i see in the logs is "mic_device=None, snd_device=None, mic_command=None, snd_command=None" even if the mic is detected. Is it normal to have mic_device to None ?
If I remove the mic I've this kind of logs :
`ALSA lib pcm_pulse.c:758:(pulse_prepare) PulseAudio: Unable to create stream: No such entity
arecord: set_params:1416: Unable to install hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 16
CHANNELS: 1
RATE: 16000
PERIOD_TIME: 125000
PERIOD_SIZE: 2000
PERIOD_BYTES: 4000
PERIODS: 4
BUFFER_TIME: 500000
BUFFER_SIZE: 8000
BUFFER_BYTES: 16000
TICK_TIME: [0 0]`
that make me thinking that when plugged the mic is well detected.
Here is a typical log block :
DEBUG:__main__:Speech detected DEBUG:homeassistant_satellite.remote:{'type': 'auth_required', 'ha_version': '2023.10.5'} DEBUG:homeassistant_satellite.remote:{'type': 'auth_ok', 'ha_version': '2023.10.5'} DEBUG:homeassistant_satellite.remote:{'id': 1, 'type': 'result', 'success': True, 'result': None} DEBUG:homeassistant_satellite.remote:{'id': 1, 'type': 'event', 'event': {'type': 'run-start', 'data': {'pipeline': '01hdbn06ae95fpv1nwabgedd0e', 'language': 'fr', 'runner_data': {'stt_binary_handler_id': 1, 'timeout': 300}}, 'timestamp': '2023-11-01T17:55:08.411465+00:00'}} DEBUG:homeassistant_satellite.remote:{'id': 1, 'type': 'event', 'event': {'type': 'wake_word-start', 'data': {'entity_id': 'wake_word.openwakeword', 'metadata': {'format': 'wav', 'codec': 'pcm', 'bit_rate': 16, 'sample_rate': 16000, 'channel': 1}, 'timeout': 3}, 'timestamp': '2023-11-01T17:55:08.411584+00:00'}} DEBUG:__main__:wake_word-start {'entity_id': 'wake_word.openwakeword', 'metadata': {'format': 'wav', 'codec': 'pcm', 'bit_rate': 16, 'sample_rate': 16000, 'channel': 1}, 'timeout': 3} DEBUG:homeassistant_satellite.remote:{'id': 1, 'type': 'event', 'event': {'type': 'error', 'data': {'code': 'wake-word-timeout', 'message': 'Wake word was not detected'}, 'timestamp': '2023-11-01T17:55:10.193578+00:00'}} DEBUG:__main__:error {'code': 'wake-word-timeout', 'message': 'Wake word was not detected'} DEBUG:homeassistant_satellite.remote:{'id': 1, 'type': 'event', 'event': {'type': 'run-end', 'data': None, 'timestamp': '2023-11-01T17:55:10.193647+00:00'}} DEBUG:__main__:run-end None DEBUG:homeassistant_satellite.remote:Pipeline finished DEBUG:__main__:Waiting for speech
This kind of message is even showed without speech / noise..
I've tried differents VAD settings without success.
If I look at OpenWakeword logs I only have :
2023-11-01T20:45:19.513748000Z DEBUG:wyoming_openwakeword.handler:Client connected:<PHONE_NUMBER>1372 2023-11-01T20:45:19.514012000Z DEBUG:wyoming_openwakeword.handler:Receiving audio from client:<PHONE_NUMBER>1372 2023-11-01T20:45:21.708255000Z DEBUG:wyoming_openwakeword.handler:Client disconnected:<PHONE_NUMBER>1372
But the wake word is never triggered.
Here is an example  with my esp32 sat :
2023-11-01T20:39:30.472160000Z DEBUG:wyoming_openwakeword.handler:Client connected:<PHONE_NUMBER>1432 2023-11-01T20:39:30.472436000Z DEBUG:wyoming_openwakeword.handler:Receiving audio from client:<PHONE_NUMBER>1432 2023-11-01T20:39:33.325156000Z DEBUG:root:Triggered alexa_v0.1 (client=18462392791432) 2023-11-01T20:39:33.331786000Z DEBUG:wyoming_openwakeword.handler:Client disconnected:<PHONE_NUMBER>1432
It makes me thinking that it could be mic settings.
Any idea or advice ?
Thanks!

Hello,
I'm beginning to have result.
My USB Mic was at 100% volume in HA. I think it was saturated voice. I've put it down to 50 % (ha audio volume input --index 0 --volume 50). I've disable noise reduction.
It's still not very accurate but it begin to works. I'm trying to finetune it.
If someone has advice to help to be more accurate...
Regards

whisper base model is not sufficient for me to recognize wake word (alexa) I needed to switch to small-int8 to make it works (with 7 seconds of delay on a dedicated lxc for pipeline...)

I am having the same issue, my log also gets stuck at
Recording raw data 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono
I think it is a missing configuration from home assistant and the raspberry pi, where the pi doesn't select correctly the audio hardware. I have bring this up multiple times but developers just ignore it.

I am also in the same situation, stuck at
Recording raw data 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono

Please try the official Assist Microphone add-on: https://github.com/home-assistant/addons/tree/master/assist_microphone


RA/UM - review queries to add HRID

Comment from Joanne about circ queries: “For queries where there are record IDs in the results, it would be helpful to show the HRID versions, rather than the Folio system ID versions, because to look things up in the various Apps, you must use the HRIDs. In most cases, it doesn’t even give you the option of searching by the Folio system IDs.”

derived tables:

items_holdings_instances: has item hrid, but should change label to clarify it's item_hrid; also add holdings hrid and instance hrid
loans_items: has item hrid, but should change label to clarify it's item_hrid; also has holdings id, should we also add holdings hrid?
loans_renewal_count: add item hrid
loans_renewal_dates: add item hrid
requests_items: has item hrid, but should change label to clarify it's item_hrid; also has holdings id, should we also add holdings hrid?

report queries:

claimed_returned: add item hrid
item_related_exceptions: add item hrid
items_lost_in_transit: add item hrid
missing_items: add item hrid
overdue_items: doesn't have item id, should we add item hrid anyway?
requests: doesn't have item id, should we add item hrid anyway?

not going to make it for Lotus. also note that some of these have already been ported to Metadb, so any future edits to these tables should happen for both LDP and Metadb versions.


[HOLD for payment 2023-12-26] [$500] Dev: Web - Console error in modal route navigation

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

Version Number: Dev 1.4.0
Reproducible in staging?: n
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @allroundexperts
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1700217148936209
Action Performed:

Go to NewDot
Log in with any account
Navigate to any modal route

Expected Result:
No console error in modal route navigation
Actual Result:
Console error in modal route navigation
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01cb7a8b97975fcd6d
Upwork Job ID:<PHONE_NUMBER>376543744
Last Price Increase: 2023-11-24
Automatic offers:

ntdiary | Reviewer | 27849866
dukenv0307 | Contributor | 27849868

Proposal
Please re-state the problem that we are trying to solve in this issue.

We are getting console error for BackHandler on web.

What is the root cause of that problem?

We are getting console error due to use of useNavigation hook as it uses useBackButton hook internally.
And useBackButton hook uses BackHandler which is not available in web.
So we need to disable useBackButton hook on web.

What changes do you think we should make in order to solve the problem?

We can add below code at eod in our @react-navigation+native+6.1.6.patch file to disable useBackButton hook on web.

diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index e016a69a1..1903b148a 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -1,6 +1,7 @@
 import * as React from 'react';
-import { BackHandler } from 'react-native';
+import { BackHandler, Platform } from 'react-native';
 export default function useBackButton(ref) {
+  if(Platform.OS === 'web') return;
   React.useEffect(() => {
     const subscription = BackHandler.addEventListener('hardwareBackPress', () => {
       const navigation = ref.current;
\ No newline at end of file

One enchancement we can do is update my patch to use code from react-native-modal+13.0.1.patch which adds a escape key handler for web.
https://github.com/Expensify/App/blob/91ef64083723d1ef98351f6f0e6eafeea6950117/patches/react-native-modal%2B13.0.1.patch#L35-L38

What alternative solutions did you explore? (Optional)

We can upgrade our package to latest 6.x version. But it will probably require changes in our patches and codebase.

Adding engineering just to confirm this is reproducible since it's a dev error.

@bfitzexpensify I reproduced 👍

Great. @ntdiary, looks like we've got a few proposals ready for review.

Proposal
from: @abdullahbinahmed
Please re-state the problem that we are trying to solve in this issue.
Backhandler is not supported for the web and is being called by React Modal so we are getting the error on the Web in console.
What is the root cause of that problem?
BackHandler is imported in web code but is not part of the react-native-web API (0.19) anymore.
What changes do you think we should make in order to solve the problem?
Backhandler is not present for web code as mentioned above so if the website is being accessed by the user from the web interface, we should detect it and not call backhandler for it.
This issue has been raised in react-navigation repo here
So my solution is the solution that have been tested and merged in the main branch by the developer of react-navigation.
import type {
  NavigationContainerRef,
  ParamListBase,
} from '@react-navigation/core';
import * as React from 'react';
import { BackHandler, Platform } from 'react-native';

export default function useBackButton(
  ref: React.RefObject<NavigationContainerRef<ParamListBase>>
) {
  const handleEscape = (event) => {
    if (event.key === 'Escape') {
      const navigation = ref.current;
      if (navigation && navigation.canGoBack()) {
        navigation.goBack();
      }
    }
  };
  if (Platform.OS === 'web') {
    document?.body?.addEventListener?.('keyup', handleEscape);
    return () => {
      document?.body?.removeEventListener?.('keyup', handleEscape);
    };
  }
  React.useEffect(() => {
    const subscription = BackHandler.addEventListener(
      'hardwareBackPress',
      () => {
        const navigation = ref.current;

        if (navigation == null) {
          return false;
        }

        if (navigation.canGoBack()) {
          navigation.goBack();

          return true;
        }

        return false;
      }
    );

    return () => subscription?.remove?.();
  }, [ref]);
}

The patch would be created as a solution as follows:
---<EMAIL_ADDRESS>2023-11-22 10:59:35.340000000 +0500
+++ test.js	2023-11-22 11:17:35.370000000 +0500
@@ -3,11 +3,25 @@
   ParamListBase,
 } from '@react-navigation/core';
 import * as React from 'react';
-import { BackHandler } from 'react-native';
+import { BackHandler, Platform } from 'react-native';

 export default function useBackButton(
   ref: React.RefObject<NavigationContainerRef<ParamListBase>>
 ) {
+  const handleEscape = (event) => {
+    if (event.key === 'Escape') {
+      const navigation = ref.current;
+      if (navigation && navigation.canGoBack()) {
+        navigation.goBack();
+      }
+    }
+  };
+  if (Platform.OS === 'web') {
+    document?.body?.addEventListener?.('keyup', handleEscape);
+    return () => {
+      document?.body?.removeEventListener?.('keyup', handleEscape);
+    };
+  }
   React.useEffect(() => {
     const subscription = BackHandler.addEventListener(
       'hardwareBackPress',
@@ -28,6 +42,6 @@
       }
     );

-    return () => subscription.remove();
+    return () => subscription?.remove?.();
   }, [ref]);
 }

The idea behind the solution is we only add the listeners when users tries to go back. This way we can make sure that the listener is added as late as possible. This will make sure that our handler will run first when back button is pressed.
What alternative solutions did you explore? (Optional)
We cannot update the version of the package as this fix is not included in a version release yet so we have to create a patch file for this issue.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/smabdullahahmed

Hi, @arosiclair, is this the error you see when opening the app or refreshing the app?

Yes that error shows immediately after opening the app.

we had a similar issue https://github.com/Expensify/App/issues/31120 before, and the final decision was to close that issue and wait for the upgrade.

Okay it sounds like we should upgrade. The version linked in that issue was an alpha release. Has that been put in any stable release?

Okay looks like that is @dukenv0307's original proposal. Let's go ahead and upgrade that package.

Payments finalised, @ntdiary please complete the BZ checklist when you get a moment - thanks!

Thanks @ntdiary, agreed - let's close this out


Add ability to verify 2020 proofs using 2018 keys.

Addresses issue #11

Codecov Report

Merging #12 (b55745a) into main (59d741e) will increase coverage by 3.70%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   79.62%   83.33%   +3.70%
==========================================
  Files           2        2
  Lines          54       60       +6
==========================================
+ Hits           43       50       +7
+ Misses         11       10       -1

Impacted Files
Coverage Δ

lib/Ed25519Signature2020.js
82.75% <90.00%> (+3.91%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 59d741e...b55745a. Read the comment docs.


Network Discovery not working on iOS?

I'm not sure if anyone else is seeing this problem, but for me, on iOS, when I start a network discovery, I never get a callback.
It's working on macOS and Android.
I can set the IP address manually and connect.
Its only network discovery. Is anyone else seeing this?

Hihi
theres a few reasons why it may not work out of the box on iOS
https://github.com/MirrorNetworking/Mirror/pull/3255
Broadcast address might need to be different.
You may also need Certain entitlements for LAN broadcasting (yes iOS can be a pain)

Closing this as not a bug (fixable by setting the Broadcast address or by external config outside of Mirror's control.
For additional support, please join our Discord.

@antiero  Try <IP_ADDRESS>
and <IP_ADDRESS>
I cant remember to be honest, but something does work.

Thanks, tried both of those but Discovery not working sadly from the iOS side. If I start the server on iOS, the Mac app can connect but not the other way around 🤷🏼♂😕


[GLUTEN-1910][CH] Fix fallback when executing window function: lead, lag and so on

What changes were proposed in this pull request?
Fix fallback when executing window function: lead, lag, stddev and so on:
Currently, when executing window functions: lead, lag, it will fallback to vanilla spark, but these functions are supported.
Close #1910.
(Fixes: #1910)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@lgbo-ustc please help to review, thanks.

Run Gluten Clickhouse CI

LGTM


AHU definition != Air_Handler_Unit definition

Hey Gabe - congrats on the 1.1.0 release!  Looking forward to going through it!
I think this is a mistake?  The definition looks like it should be for a differential pressure sensor or something...
https://github.com/BrickSchema/Brick/blob/54847b9419836fa29c21f8d7815b24f632b7ec9b/Brick.ttl#L9282-L9286

Oh, good catch! I'll push a fix soon

@corymosiman12 we'll be updating the website soon with the updated classes and definitions: small technical bug holding up that update for now. This repo will be up to date though


native: fix ref navigation

I should have used navigation.navigate, not navigation.push. Fixed here.
fixes LAND-1845
Makes it so that we don't transition to a new screen when pressing a ref.

Maybe we need a pop and then a push if it's a different channel? Unsure what the idiomatic way to navigate to the same screen with different props is

Maybe we need a pop and then a push if it's a different channel? Unsure what the idiomatic way to navigate to the same screen with different props is

This is what I ended up doing, seems to do what we want.

I think this might be the use case that replace is for.

🫡 replaced with replace


Please clarify pattern syntax for ignore

I thought files-to-prompt used globbing patterns to ignore files, and thus expected the following to work but it doesn't:
files-to-prompt --ignore "*.{jpg,svg,pdf}" myproject/docs/

I can't tell if this is a bug or not, so the actual request her is to clarify that expression language is in use.

From looking at the code, it uses fnmatch on the basename (last part) of the path.
fnmatch supports these operators:


Adds "What's new: OpenSearch Reporting CLI" blog

Description
Creates a blog post announcement for the Reporting CLI release.
Issues Resolved
Blog 1334
Check List

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

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

hi @rupal and @joshuali925 , i'm not sure why but GitHub isn't letting me see your review comments. unless i made exact same change with a commit?

hi @Rupal and @joshuali925 , i'm not sure why but GitHub isn't letting me see your review comments. unless i made exact same change with a commit?

I think there were no comments. Josh and I approved it but new commits dismissed review.

Update: received approval to send to editorial review via Slack from @brijos.

Hi @natebower , please verify that your suggested changes are now committed. Thanks

Note: The recent new commits are only part of a DCO sign off rebase task. When I committed suggestions, GitHub didn't add my DCO to them, so they didn't pass the DCO check.
Good news is that the instructions to fix it worked beautifully.

@krisfreedain - The blog includes meta and has gone through editorial, and is now ready to publish.


Fix double cast to string use scientific notation in Fe

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #3692
Problem Summary(Required) ：

mysql> explain SELECT * FROM t0 WHERE CAST(CAST(CASE WHEN TRUE THEN -1229625855 WHEN false THEN 1 ELSE 2 / 3 END AS STRING ) AS BOOLEAN );
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Explain String                                                                                |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0                                                                                |
|  OUTPUT EXPRS:1: c_0_0 | 2: c_0_1 | 3: c_0_2 | 4: c_0_3 | 5: c_0_4 | 6: c_0_5 | 7: c_0_6 | 8: c_0_7 | 9: c_0_8 | 10: c_0_9 | 11: c_0_10 | 12: c_0_11 | 13: c_0_12 | 14: c_0_13 | 15: c_0_14 | 16: c_0_15 |
|   PARTITION: UNPARTITIONED                                                                                |
|                                                                                |
|   RESULT SINK                                                                                |
|                                                                                |
|   1:EXCHANGE                                                                                |
|                                                                                |
| PLAN FRAGMENT 1                                                                                |
|  OUTPUT EXPRS:                                                                                |
|   PARTITION: RANDOM                                                                                |
|                                                                                |
|   STREAM DATA SINK                                                                                |
|     EXCHANGE ID: 01                                                                                |
|     UNPARTITIONED                                                                                |
|                                                                                |
|   0:OlapScanNode                                                                                |
|      TABLE: t0                                                                                |
|      PREAGGREGATION: ON                                                                                |
|      PREDICATES: CAST('-1.229625855E9' AS BOOLEAN)                                                                                |
|      partitions=1/1                                                                                |
|      rollup: t0                                                                                |
|      tabletRatio=10/10                                                                                |
|      tabletList=3180400,3180402,3180404,3180406,3180408,3180410,3180412,3180414,3180416,3180418                                                                                |
|      cardinality=3                                                                                |
|      avgRowSize=16.0                                                                                |
|      numNodes=0                                                                                |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

-1229625855 cast to double first and cast to string use scientific notation.
mysql> select  CAST('-1.229625855E9' AS BOOLEAN);
+-----------------------------------+
| CAST('-1.229625855E9' AS BOOLEAN) |
+-----------------------------------+
|                              NULL |
+-----------------------------------+
1 row in set (0.00 sec)

mysql> select  CAST('-1229625855' AS BOOLEAN);
+--------------------------------+
| CAST('-1229625855' AS BOOLEAN) |
+--------------------------------+
|                              1 |
+--------------------------------+

but string with scientific notation will result in NULL

[FE PR Coverage check]
:heart_eyes: pass : 4 / 4 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/operator/scalar/ConstantOperator.java
4
4
100.00%

@Mergifyio backport branch-2.2


Don't auto-install hooks when using the npm package

:zap: Summary

Don't auto install hooks when using the npm package
Value
I was surprised when the npm auto-installed the lefthook hooks -> I work in a large monorepo, and I can't assert that all users will want or need the hooks. It's not very clearly documented in lefthook that the npm package does this auto-install behaviour.
I have a CI system for validating work, but would still like to version lefthook in my repo -> I'd love a way to opt-out (or opt-in) to the auto install behaviour.
One reason for using the npm package as opposed to say, homebrew, would be to manage new features in lefthook - how do I know my users are using the correct version of lefthook with the lefthook config file I've comitted?
Prior art: husky has an init script that will set up a prepare script: https://typicode.github.io/husky/get-started.html. It does not auto install by default: https://typicode.github.io/husky/#articles
Behavior and configuration changes
Breaking change - don't auto install the hooks, following the same philosophy as husky

Hey @anthonyhayesres! Thank you for creating this feature request. This question about auto-install of lefthook is debatable. I agree that auto-installing something from an npm package can be surprising. The intent was to force using git hooks in a project that has explicit dependency specified.
If you want to have optional hooks but want to make sure the user will have appropriate version of lefthook, then you can use min_version setting. I hope that it solves your problem.
I respect the philosophy of husky, but husky is a tool that is distributed only via npm package, while lefthook can be installed with many different ways. That's why the approach was different from the very beginning. If you specify lefthook as a dependency, you'll probably want to force git hooks usage, and it can be convenient in case you don't want to worry about making sure all developers properly installed lefthook. But if you want to keep lefthook optional you can only have lefthook.yml in the repository and let the enthusiasts use it or not.
In CI lefthook skips auto install if the CI variable is set. So, using with CI shouldn't be a problem.
But if you have some problems, please describe them. I don't deny the possibility of a bug here 🤔

Hey thanks for the quick response! Thanks for highlighting the min_version setting - I think the combination of that with installing lefthook manually will work for my use case. 🎉


AZ CLI: Update iisnode.yml to target 10.14.1instead of 8.9.4.

Tool
Name: az bot
Describe the solution you'd like
Update the iisnode.yml to point to Node.js version 10.14.1 , which is now supported on Azure Webapps and Function apps, and that we're now targeting ^10 in the botbuilder-js SDK (Microsoft/botbuilder-js#709) in the 4.3 release going forward.
[enhancement]

We need to also update the ARM templates to configure WEBSITE_NODE_DEFAULT_VERSION to v10.14.1

Closing via Azure/Azure-cli#8445


[Testerina] Derive test suite from syntax tree and semantic model

Description:
Look into an approach to derive test suite from syntax tree and semantic model
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Create a mapping with semantic model and syntax tree for each module. We need to make the test related information available in syntax tree.

[ ] store semantic model and syntax tree for tests

[ ] Insert test related data to syntax tree

Come up with a way to map the info from semantic model and syntax tree to the test suite

ATM, the test sources in a module are not supported by the semantic API, it's being fixed by https://github.com/ballerina-platform/ballerina-lang/pull/27277

We have kept the old implementation for mock annotation handling until compiler plugin extensions are supported using new APIs.

We have kept the old implementation for mock annotation handling until compiler plugin extensions are supported using new APIs.


Relay support

We should be able to parse some information from Relay definitions.

It would be great! 👍


Segmentation fault when model save

Laravel Version: 5.8
PHP Version: 7.1 and 7.2
Database Driver & Version: MYSQL
10.0.38-MariaDB-0+deb8u1 - (Debian)

Description:
I have this issue when running laravel queue:work on console.
In my code this error appears when one model is saved
I tested with laravel 5.6,5.7 ,5.8 and PHP 7.1,7.2 ,7.3
The segmentation fault call in php_iconv_string()
I am very lost with this error, the same code has worked correctly executing it without the worker
Regards
`
Reading symbols from /opt/plesk/php/7.1/bin/php...(no debugging symbols found)...done.
(gdb) run -d memory_limit=1G artisan queue:work --queue=apc --memory=50
Starting program: /opt/plesk/php/7.1/bin/php -d memory_limit=1G artisan queue:work --queue=apc --memory=50
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[2019-07-25 06:53:04][562] Processing: iPortPilot\Jobs\ProcesarAPC
[New Thread 0x7fffeedff700 (LWP 32360)]
[Thread 0x7fffeedff700 (LWP 32360) exited]
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff49865de in __gconv_open (toset=toset@entry=0x7fffff7ff0a0 "UCS-4LE//", fromset=fromset@entry=0x7fffff7ff080 "UTF-8//",
handle=handle@entry=0x7fffff7ff0c8, flags=flags@entry=0) at gconv_open.c:33
33      gconv_open.c: No such file or directory.
(gdb) bt 0
(More stack frames follow...)
(gdb) frame 0
#0  0x00007ffff49865de in __gconv_open (toset=toset@entry=0x7fffff7ff0a0 "UCS-4LE//", fromset=fromset@entry=0x7fffff7ff080 "UTF-8//",
handle=handle@entry=0x7fffff7ff0c8, flags=flags@entry=0) at gconv_open.c:33
33      in gconv_open.c
(gdb) bt
#0  0x00007ffff49865de in __gconv_open (toset=toset@entry=0x7fffff7ff0a0 "UCS-4LE//", fromset=fromset@entry=0x7fffff7ff080 "UTF-8//",
handle=handle@entry=0x7fffff7ff0c8, flags=flags@entry=0) at gconv_open.c:33
#1  0x00007ffff49862bb in iconv_open (tocode=0x7fffff7ff0a0 "UCS-4LE//", fromcode=0x7fffff7ff080 "UTF-8//") at iconv_open.c:71
#2  0x00000000004f8237 in php_iconv_string ()
#3  0x00000000004f877b in ?? ()
#4  0x00000000004f8c60 in ?? ()
#5  0x00000000006d9b62 in ?? ()
#6  0x000000000068049b in execute_ex ()
#7  0x000000000062633d in zend_call_function ()
#8  0x0000000000565575 in ?? ()
#9  0x00000000006d9b62 in ?? ()
#10 0x000000000068049b in execute_ex ()
#11 0x000000000062633d in zend_call_function ()
#12 0x0000000000565575 in ?? ()
#13 0x00000000006d9b62 in ?? ()
#14 0x000000000068049b in execute_ex ()
#15 0x000000000062633d in zend_call_function ()
#16 0x0000000000655530 in zend_call_method ()
#17 0x000000000067083a in ?? ()
#18 0x000000000067264c in ?? ()
#19 0x00000000006b281c in ?? ()
#20 0x000000000068049b in execute_ex ()
#21 0x000000000062633d in zend_call_function ()
`
Steps To Reproduce:

I don't see a Laravel related problem here. Laravel does not use php_iconv_string so it must be a problem on your system.


Cross compilation to arm-linux-androideabi is broken

The CI setup in Tokio has broken due to libc not providing an accept4 function on that platform. See e.g. this run
error[E0425]: cannot find function `accept4` in crate `libc`
Error:    --> /cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.7.9/src/sys/unix/tcp.rs:446:18
    |
446 |           syscall!(accept4(
    |                    ^^^^^^^ help: a function with a similar name exists: `accept`
    |
   ::: /cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.87/src/unix/mod.rs:686:5
    |
686 | /     pub fn accept(
687 | |         socket: ::c_int,
688 | |         address: *mut sockaddr,
689 | |         address_len: *mut socklen_t,
690 | |     ) -> ::c_int;
    | |_________________- similarly named function `accept` defined here

error[E0425]: cannot find function `accept4` in crate `libc`
Error:    --> /cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.7.9/src/sys/unix/uds/listener.rs:55:18
    |
55  |           syscall!(accept4(
    |                    ^^^^^^^ help: a function with a similar name exists: `accept`
    |
   ::: /cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.87/src/unix/mod.rs:686:5
    |
686 | /     pub fn accept(
687 | |         socket: ::c_int,
688 | |         address: *mut sockaddr,
689 | |         address_len: *mut socklen_t,
690 | |     ) -> ::c_int;
    | |_________________- similarly named function `accept` defined here

Refs: #1465

Can confirm same for me on libc 0.2.87

Likewise for armv7-linux-androideabi using libc 0.2.87.

This seems like a regression in libc..? The CI for #1468 now also fails on Android arm, which passed before.

Confirmed that this is a regression between libc 0.2.86 and 0.2.87.

I created https://github.com/rust-lang/libc/issues/2101.

Re-posting from #1469.
For a quick fix add the following to your Cargo.toml:
[dependencies]
libc = "=0.2.86" # Note the `=` here.

In our cross-compilation heavy project we were more specific:

Libc v0.2.88 is out, so after a cargo update this should all work again.


feat: add compatibility for CustomBush Mod

Added compatibility for CustomBush Mod
Please test thoroughly, I have been struggling for a long time to reach these results.
NB: Translations are not added, I am not confident about translating myself and didn't want to use Machine translations.

Thank you for the second contribution, I'm currently not active in SDV modding after I finished my playthrough :(
I'll test this in a few days but so far it looks good.
I've assigned the 50% DP on nexusmods to you(it was 100% to slothsoft before).


Not able to connect to container through WAN

I have installed this great overthought service but I don't seem to be able to connect to my container.
The rule is added automaticly on container create (port 9999 mapped):
<IP_ADDRESS> 80/tcp ALLOW FWD Anywhere # whoami:3f4ca202aaffe2ec4e8c151a4085346a9515e4f808921141f53de17e00d0136a
The rule seems to be fine, is this a ufw-docker issue or something else ?
Refering to: https://github.com/chaifeng/ufw-docker/issues/50

Hi @Yamakasi what's your full docker run command or docker-compose file?

@shinebayar-g  Here you go:
docker run -d -p 9999:80 -l UFW_MANAGED=TRUE --name whoami -t jwilder/whoami

If the image you're running is jwilder/whoami I believe it runs on port 8000, not 80.
docker run -d -p 9999:8000 -l UFW_MANAGED=TRUE --name whoami -t jwilder/whoami

This command works. After this I was able to hit the container.
❯ curl <IP_ADDRESS>:9999
I'm 7f5b5fa3ef36

vagrant@ubuntu18-docker:~$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
22                         ALLOW       Anywhere
22 (v6)                    ALLOW       Anywhere (v6)

<IP_ADDRESS> 8000/tcp        ALLOW FWD   Anywhere                   # whoami:7f5b5fa3ef363a8dbf7447a089a3eeabd277ace66bf47867843a5cd3d7527326

@shinebayar-g  You are completely right, sorry my mistake and it works well!
I actually ran into this test because I was adding manually rules before for existing containers like SMTP which had the same issue. IP's are OK, so I was like "no clue".
Any advise there ?
Thanks for the great module!

@shinebayar-g  You are completely right, sorry my mistake and it works well!
I actually ran into this test because I was adding manually rules before for existing containers like SMTP which had the same issue but that seems to be resolved as well.
Thanks for the great module!

Glad it worked.

Glad it worked.


renderText improvements

As discussed in #29, this PR:

uses positive angles to rotate the rendered text clockwise
changes the order of the bounding points returned by the method

Both changes aim to make the API more familiar to Apple platform developers

Perfect – thank you!


cache.put receiving request and not the static files

I'm not totally sure about this, just came here from your post. Verify it's correct, but I think cache.put should receive the request and not the html files

Thanks for this @EloyID!
My service working was throwing an error because of the same line, causing quite a few oddities. I changed:
Line 88: caches.open(version).then(cache => cache.put(event.request.url, clonedResponse));
Line 99: caches.open(version).then(cache => cache.put(event.request.url, clonedResponse));
Now it is working very well for my app!

Hey,
Thank you very much for your interest.
Actually the reason I put cache.put(HTMLToCache, clonedResponse) was because Meteor projects are SPA (single web page application) so every single page has the same HTML. It means that it was a waste a space to cache each page differently. Instead if HTML is request I always cache under the same request url ('/') and I serve it if HTML is required.


Causes niggervirus

When I use this garrys mod executor it gives me niggervirus. Please help...

no

yes


Add [2D-Incucyte assay, a 2D-cell titer glo assay, a 3D microtissue assay, in vivo PDX assay] to [assay]

List the new value
Value: 2D-Incucyte assay, a 2D-cell titer glo assay, a 3D microtissue assay, in vivo PDX assay
Using OLS or a similar resource, please find a standard term that fits your needs. OLS-listed NCIT and OBI dictionaries are preferred sources. Non-OLS sources of ground truth for specific items such as ONCOTREE for cancer types, or GEO for platform definitions are also appropriate.
Provide definition and source for the new value
Definition:
Source url:
Are there similar but not-quite-right values?
Please list if applicable.
Additional comments

Resolved by #83


[Bug]: Dropdown doesn't keep order of data from query

Describe the bug
According to the documentation, by default the dropdown values would appear in the same order as in the query producing them, but it appears to put them in ascending order instead.
Steps to Reproduce
Create SQL query named 'bug':
  SELECT unnest([3,2,1]) AS value

Create component using the query results:
<Dropdown data={bug} name=bug value=value/>
Logs
No response
System Info
System:
    OS: macOS 13.6.4
    CPU: (4) x64 Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz
    Memory: 146.37 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.16.0 - /usr/local/bin/node
    npm: 10.8.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 127.0.6533.120
    Safari: 17.3
  npmPackages:
    @evidence-dev/bigquery: ^2.0.7 => 2.0.7
    @evidence-dev/core-components: ^4.7.2 => 4.7.2
    @evidence-dev/csv: ^1.0.12 => 1.0.12
    @evidence-dev/databricks: ^1.0.7 => 1.0.7
    @evidence-dev/duckdb: ^1.0.11 => 1.0.11
    @evidence-dev/evidence: ^39.1.1 => 39.1.1
    @evidence-dev/motherduck: ^1.0.2 => 1.0.2
    @evidence-dev/mssql: ^1.0.9 => 1.0.9
    @evidence-dev/mysql: ^1.1.3 => 1.1.3
    @evidence-dev/postgres: ^1.0.6 => 1.0.6
    @evidence-dev/snowflake: ^1.1.0 => 1.1.0
    @evidence-dev/sqlite: ^2.0.6 => 2.0.6
    @evidence-dev/trino: ^1.0.7 => 1.0.7

Severity
annoyance
Additional Information, or Workarounds
Workaround: create a new column that represents the required order then use that for the order parameter of the component.

I had some suspicion that we broke something when we rewrote the Dropdown component, but I created a project with an older version and it still sorts in ascending order.
@mcrascal @hughess Thoughts on if/how we should be sorting dropdown options by label/value? Maybe the behavior could be hinged on a prop?

I have fixed the docs to reflect the actual behaviour. Will go out with next release.


Add Robot#eavesdrop

Lots of new tests and refactoring to eventually add Robot#eavesdrop and fix #866.
Each commit should be able to stand alone (all tests passing), refactor commits don't touch code and tests at the same time, and new tests were added first to cover all areas being modified.
TextListener was removed in favor of a common pattern of putting all matcher logic in Robot instead of some in Robot and some in a subclass of Listener.
This also introduces Robot#listen as a new public method.

I'll gut and rewrite this when #986 merges

I'll gut and rewrite this when #986 merges

@michaelansel still planning on doing this?

And a bit of copy-paste later, we are all back up to date!
Apparently we lost our CI, but tests are passing on my laptop.


THY-adjust-about-grid

I did not like how squished the grid was on the about page. Adjusting it from 8 to 12 widens it slightly on mobile devices.

This also adds consistency between the leaderboard and about grids as the leaderboard was already a 12.


UiSettings class support

UISetting is settings for the user interface of a GoogleMap.
Contains any gesture enabled and control visible.
Map.HasZoomEnabled, HasScrollEnabled are use for simple or keep compatibility.
UISetting is full spec for map controls.

Android - UiSettings  |  Google APIs for Android  |  Google Developers
iOS - GMSUISettings Class Reference  |  Google Maps SDK for iOS  |  Google Developers

Changes made in #110, but it needs a little bit more testing

In comparison with UiSetting class and Map class properties.

UiSettings class[NEW!]
Map class
Synchronize

CompassEnabled
N/A
N/A

RotateGesturesEnabled
HasRotationEnabled
Yes

MyLocationButtonEnabled
IsShowingUser
No

N/A
MyLocationEnabled[NEW!]
N/A

IndoorLevelPickerEnabled
N/A
N/A

ScrollGesturesEnabled
HasScrollEnabled
Yes

TiltGesturesEnabled
N/A
N/A

ZoomControlsEnabled
HasZoomEnabled
No

ZoomGesturesEnabled
HasZoomEnabled
No

Synchronize - "Yes" means synchronize property value UiSettings and Map class.
map.UiSettings.RotateGesturesEnabled = true;
Debug.WriteLine(map.HasRotationEnabled); // true

map.HasRotationEnabled = false;
Debug.WriteLine(map.UiSettings.RotateGesturesEnabled); // false

Released in https://github.com/amay077/Xamarin.Forms.GoogleMaps/releases/tag/v2.1.0-beta2

Hi @amay077  im not able to show the Zoom Controls on both iOS and Android even after  map.UiSettings.ZoomControlsEnabled = true;


Fix error in benchmarking dynamic link

https://github.com/line/cosmwasm/actions/runs/4563043875/jobs/8051225273

duplicate of #291


Adds support for layer style SBOM

Adds name field to the dependency
Dotnet -> .NET
Updates packit to latest version for Syft - .Net compatibility

Resolves #317
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@ForestEckhardt I just tried using this buildpack + the rest of the language family + this steeltoe sample app and it's not showing any SBOM file coming from this buildpack. Can you reproduce this? I'm pretty sure that app should have dependencies that show up in the SBOM.


Use UTF-8 when extracting build cache artifacts

Fixes #9877
We have been using UTF-8 as the encoding when creating TAR files to store cached output. However, we haven't been using the same encoding when unpacking. Instead, we were using the system default (which is UTF-8 in most cases, but not always). This causes no issues as long as the file names stored in the TAR file are ASCII-only. And the TAR implementation in commons-compress that we use does some tricks to support non-ASCII characters even when a non-UTF-8 character set is chosen for unpacking. However, in some cases there is a failure due to this confusion of encodings.

I haven't been able to reproduce the problem reported by @andrey-fomin even with the provided reproducer (see attachment), as it did not manage to decompress:
$ unzip test.zip
Archive:  test.zip
  inflating: test/build.gradle.kts
   creating: test/gradle/
   creating: test/gradle/wrapper/
  inflating: test/gradle/wrapper/gradle-wrapper.jar
  inflating: test/gradle/wrapper/gradle-wrapper.properties
  inflating: test/gradlew
  inflating: test/gradlew.bat
  inflating: test/out.log
   creating: test/src/
   creating: test/src/main/
   creating: test/src/main/java/
error:  cannot create test/src/main/java/������.java
        Illegal byte sequence

It seems that the TAR implementation we are using from commons-compress already corrects for a non-UTF-8 default charset (see source code). This explains why nobody has reported problems with unpacking non-UTF-8 file names when loading from cache. What it doesn't is how @andrey-fomin could have encountered the exception in the first place.
Nevertheless, I added some more thorough integration tests around packaging, and set the encoding for the unpacking to UTF-8 as it should have been all along.

@lptr I manged to reproduce the error on my machine. The changes were to use an output directory with the file with the bad name in it and the windows-1250 charset. See my last two commits here: https://github.com/gradle/gradle/compare/wolfs/build-cache/issue-9877
Let's see if the test also breaks on CI: https://builds.gradle.org/viewLog.html?buildId=24765494&buildTypeId=Gradle_Check_Quick_1_buildCachePackaging&tab=buildResultsDiv&branch_Gradle_Check_Quick_1=wolfs%2Fbuild-cache%2Fissue-9877

Retriggered the build caused, failed with stderr: fatal: Could not write new index file.


Unable to install on MacOS

Homebrew recipe doesn't work on MacOS.

This is because the homebrew recipe only installs the linux-musl target: https://github.com/michidk/homebrew-tools/blob/main/Formula/vscli.rb#L5
If anyone want's to tackle this, feel free to open a PR over here: https://github.com/michidk/vscli

Can i ask (nicely) that this issue be re-opened for others (like me) that expected the Homebrew recipe would install on macOS ?

I added the aarch64-apple-darwin target to the CI, so we now also have ARM images for M1+ macs to https://github.com/michidk/vscli/releases/tag/v0.2.2.

@michidk thanks I will give it a try.

I added macos support to the homebrew file: https://github.com/michidk/homebrew-tools/commit/d85f54d227bc50327c166b5a3d7e05993965909b
Also made it so that vscli CI automatically updates it: https://github.com/michidk/vscli/commit/4bc37a185cf0ef6f776497d6954c5c793b912690


Fix(Listing): Administration Tab: Bookmark icon no change unless page refresh #596

#596
@clarkjefcoat
@wski
@akonsowski
@mannyrivera2010

dependent: https://github.com/ozone-development/ozp-backend/pull/166

@rkenyon1969 im unsure what these changes are doing the changes to backend prevent the icon from being changed by throwing a 404 error. I think there should be a warning that pops up stating the application is disabled and cant be changed.

:-1:  was not working when i tested it bookmarked an app disabled the app refreshed the page bookmark the app was still not bookmarked

:+1:

@clarkjefcoat
@wski
@akonsowski
@mannyrivera2010

:+1:

:-1:
bookmark an app then disable it
refresh the page
enable and uncheck the bookmark gives an error
BookmarkButton.jsx:43 Uncaught TypeError: Cannot read property 'id' of undefined

@akonsowski  - please test again

:-1: the button now appears to let you bookmark when the application is disabled. if you disable the listing bookmark and reenable it will still show as bookmarked however when you check in hud the bookmark is not there. go back to center and the listing is not bookmarked

:+1: i would suggest squishing some of those branches though

This has been rebased. Please review again to make sure nothing changed because of rebasing. - thank you,
@clarkjefcoat
@wski
@akonsowski
@mannyrivera2010

:-1: the rebase looks off. it should not have all the commits still it should only have the ones that you made not the ones others made as well.

@akonsowski - please review again