[tool_crash] ProcessException: Failed to find "C:\Users\user\AndroidStudioProjects\heatlh\android\gradlew.bat" in the search path. Command: C:\Users\user\AndroidStudioProjects\heatlh\android\gradlew.bat, OS error code: 0

Command
flutter --no-color build apk

Steps to Reproduce

...
...
...

Logs
ProcessException: Failed to find "C:\Users\user\AndroidStudioProjects\heatlh\android\gradlew.bat" in the search path. Command: C:\Users\user\AndroidStudioProjects\heatlh\android\gradlew.bat, OS error code: 0
#0      LocalProcessManager.start (package:process/src/interface/local_process_manager.dart:56:7)
#1      ErrorHandlingProcessManager.start.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:691:24)
#2      _run (package:flutter_tools/src/base/error_handling_io.dart:567:20)
#3      ErrorHandlingProcessManager.start (package:flutter_tools/src/base/error_handling_io.dart:690:12)
#4      _DefaultProcessUtils.start (package:flutter_tools/src/base/process.dart:425:28)
#5      _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart:444:35)
#6      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:374:38)
#7      AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:179:11)
#8      BuildApkCommand.runCommand (package:flutter_tools/src/commands/build_apk.dart:108:26)
<asynchronous suspension>
#9      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1140:27)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#11     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:288:9)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:236:5)
<asynchronous suspension>
#15     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)

[✓] Flutter (Channel stable, 2.8.1, on Microsoft Windows [Version 10.0.19042.1466], locale en-US)
    • Flutter version 2.8.1 at C:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (7 weeks ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[!] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at C:\Users\user\AppData\Local\Android\sdk
    • Platform android-31, build-tools 32.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.63.2)
    • VS Code at C:\Users\user\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.34.0

[✓] Connected device (3 available)
    • V2030 (mobile) • f5ec5c2e • android-arm64  • Android 11 (API 30)
    • Chrome (web)   • chrome   • web-javascript • Google Chrome 97.0.4692.99
    • Edge (web)     • edge     • web-javascript • Microsoft Edge 97.0.1072.76

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 77d935af4db863f6abd0b9c31c7e6df2a13de57b
Plugins
fluttertoast-8.0.8

Hi @Muhwildanferdiansyah, Thanks for filing the issue. The error seems to suggest that the gradlew.batfile is missing from the project could you please check at this location C:\Users\user\AndroidStudioProjects\heatlh\android\gradlew.bat and confirm if the file is present?


CORE-19168, CORE-19176: show intermediate hashes in merkle tree and proof representations

Extend the text representation of Merkle trees to include intermediate hashes. This makes the way the trees work more transparent in the unit tests.
SInce the intermediate hashes are private this involves moving the tree rendering code to be available from a toString() method. I also extended the tree rendering code to allow labels on all nodes as well as just leaves, and I took the time to document the rendering routine better.
Use ints rather than longs for the trivial hashes so that the test cases look nicer. The way the trivial hashes are done the least significant bits are the distinctive ones so we can't just truncate in renders.
Rendering a Merkle proof requires using the root calculation algorithm with additional bookkeeping, so we add a callback to that code.

Thanks @vlajos and @kyriathar - I have  addressed @kyriathar's typo comment and the rename, in an upcoming change


Cross-package inlining

Currently, only emacs/rt package functions can be inlined into user packages.
Implementation has ad hoc nature.
To generalize inlining, particular strategy must be selected.
Some of them are listed below.

Always invoke AST parsing and conversions (for imports).
(+) Convenient for the user.
(+-) Can be sped up by alternative translation routine that searches for inlineable functions specifically.
(-) Slower compilation speed.
(-) No way to specify functions as "want it to be inlined" (useful for runtime). Inliner does not posses enough information to make correct decision in some cases.

Expect optional special file inline.go inside emacs/* packages.
All functions defined at that file treated as candidates for inlining.
(+) Significantly reduces amount of files that should be visited.
(+) Provides explicit control over inlining.
(-) Enforces code separation even if it is logically bound to other file.

Good global cross-package inlining requires big amounts of code to be translated.
Example:
packages A, B, C
A imports B
B imports C

package A
import "B"
func F() int { return B.F() }

package B
import "C"
func F() int { return C.F() }

package C
func F() int { return f() }
func f() int { return 1 }

To inline return 1 into A.F we need to parse all code shown above.
Optimizations must be applied to each of those packages.
Soon I will push first attempt to implement this.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v3.16 to before v4.19.198",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=058504edd02667eef8fac9be27ab3ea74332e9b4",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6de9f0bf7cacc772a618699f9ed5c9f6fca58a1d"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "058504edd02667eef8fac9be27ab3ea74332e9b4",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "6de9f0bf7cacc772a618699f9ed5c9f6fca58a1d",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "seq_file: disallow extremely large seq buffer allocations\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.19.198 by commit 6de9f0bf7cacc772a618699f9ed5c9f6fca58a1d, it was introduced in version v3.16 by commit 058504edd02667eef8fac9be27ab3ea74332e9b4. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001378


Added auto-reload of device plugins when configmap is changed.

Fixes issue #49
Important Notes

This removes environment variables from the bridge plugin all together.
Must have service account for namespace or be deployed in the kube-system namespace.
Adds in k8s.io/client-go as a dependency. (if you guys know a better way without adding in the dependency please let me know as I suck with golang still)

Hello contributor, thanks for submitting a PR for this project!
I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.
In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

Type ci test please on this PR to trigger automated tests for it.
Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically.
If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

Yeah I'm pretty bad with dependency management in Go. Let me know what I need to do to fix the 6,000 file diff lol.
Actual changed files:
modified:   Gopkg.toml
modified:   cmd/network/bridge/bridge.go
modified:   pkg/network/bridge/lister.go

@phoracek Changes made. Thanks for the suggestion!


Clarify documentation of providerConfig.type

I also updated the v2alpha ticket to reflect changes someone suggested by commenting in the documentation.


Add methods to unbind for single page JS apps.

If this still an issue, I'd be happy to review a pull request that namespaces the jQuery.on calls!


Make JsonResource Macroable

Hello,
I'm suggesting that Illuminate\Http\Resources\Json\JsonResource class should be Macroable.
The use case that i'm facing that led me propose this feature is that some data in many resources need to be adjusted in similar way so instead of creating another base JsonResource class the Macroable trait would make it much easier.
For example i've price property in few resources which i want to format all prices + adding the currency code beside the formatted price.

You could also (for now) put the methods in a trait, then apply the trait to the models and call $this->resource->[METHOD_NAME]();

Sounds like an odd use case to use macros for. Sounds like you're better off making your own price formatting helper class or simply a global function. Macros are more for extending the functionality of the thing you use.
Worse case you should probably just make a trait and add it to the resources where you need it (or the model like @CrixuAMG mentioned) rather than adding a macro.

Heya, thanks for submitting this. This seems like a feature request or an improvement. It's best to post these at the laravel/ideas repository to get support for your idea. After that you may send a PR to the framework. Please only use this issue tracker to report bugs and issues with the framework.


Port basic clock plugin functionality from gazebo-yarp-plugins

Clock plugin docs is https://github.com/robotology/gazebo-yarp-plugins/blob/master/plugins/clock/include/gazebo/Clock.hh#L35 .
The clock functionality are two:

It publishes the simulation time on a Yarp port /clock

It opens a Yarp RPC Port (/clock/rpc) to allows control of the simulation time.

This issue focus on the first functionality, i.e. publication of simulation time on yarp port /clock.

Useful resource: https://github.com/robotology/gz-sim-yarp-plugins/issues/4 .

I'm gathering documentation related to this feature to understand how to perform the porting:

Gazebo sim Classes:

Clock
WallClock
NetworkClock

Gazebo physics documentation
Old Issue from @diegoferigo, potentially useful: https://github.com/gazebosim/gz-sim/issues/51

I've seen that the clock plugin makes use of the thrift definition for the Clock service: https://github.com/robotology/gazebo-yarp-plugins/blob/cb3521f7543a5a07e2a65a82dedd2eb2ec2cea12/thrift/clock/clock_rpc.thrift
This file gets compiled and produces a ClockServer class, that in turn is inherited by ClockServerImpl class. This class is used as a data member of class GazeboYarpClock that implements the gazebo::SystemPlugin base class.
I have to understand how this logic maps to the new Gazebo sim paradigm and whether it is needed to use the thrift definitions for the clock service.

CC @traversaro

I have to understand how this logic maps to the new Gazebo sim paradigm and whether it is needed to use the thrift definitions for the clock service.

If you want to implement the /clock/rpc part of the plugin, yes. However, as a first iteration you can also just concentrate on publishing the /clock port.

I leave here some refs to useful classes and tutorials for controlling the simulation that @diegoferigo showed me:

WorldControl class
SimulationRunner class
Reset simulation tutorial

I think this will be useful in future to control the clock rpc part.

@traversaro, up to now the clock plugin sends on the /clock port the current simulation time at each simulation step, do you think it's useful to add a check to avoid writing a message if the current timestamp is the same of the previous sent?
This could be useful to avoid sending thousands of messages of the same timestamp when gazebo server is launched or when in general the simulation is paused, but maybe there are cases that I don't have in mind for which it is better to always send the timestamp.

@traversaro, up to now the clock plugin sends on the /clock port the current simulation time at each simulation step, do you think it's useful to add a check to avoid writing a message if the current timestamp is the same of the previous sent?

Yes, I think it make sense.


"Boncești" is listed in the drop-down menu

Description:
"Boncești" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Boncești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Boncești, Alba (Câmpeni)".


fix(api): removed lazy load option from mod and moved it to mod_curpu…

…s_association model

using lazy="joined" to always load the related table into an object using a join
modified reference_crud.py to reflect changes in the models

Pizza mezzaluna, no mezzo giorno.


e2e infrastructure needs for CloudEvent sink for Azure Event Grid

With regards to the e2e infrastructure for CloudEvent sink for Azure Event Grid, what we will need to add is:

An Azure Event Grid Topic to which we will push events
An Azure Service Bus Namespace + Topic that is used to subscribe to events, from the above Azure Event Grid Topic.

Relates to https://github.com/kedacore/keda/issues/3587

done!

https://github.com/kedacore/testing-infrastructure/actions/runs/8412383836/job/23033171611


document COPY TO query parameter

ack

ack

This PR can be closed, since PR #3022 supersedes it.


Apache 2.4

This compiles and seems to pass its tests. There are still several non-fatal compile-time warnings.

Hi Peter,
Thanks for your patches, incorporated into the 2.3.99b1 beta.
Cheers,
Gavin

I don't understand how this patch would not break other code chunks with
#ifndef APACHE22
...
#else
clearly the build will be broken with only -DAPACHE24
Debian patch uses proper, universal call to identify which Apache version is used:
+#if AP_MODULE_MAGIC_AT_LEAST(20111130,0)

There were 3 sets of patches out there - Peter's, Ivo's/debian's, and Dietmar's. The 2.4 changes are are a blend of all 3, and do use AP_MODULE_MAGIC_AT_LEAST (check the code).
Cheers,
Gavin

ah, I see now. good!


Automatic building from modules

The modules! macro could be replaced with an attribute.
Also attributes can be moved into attributes.
it could look something like this:
#[derive(Component)]
#[shaku(#
  interface = DateLogger),
  module = "MyModule"
]
struct DateLoggerImpl {
    #[shaku(inject)]
    logger: Arc<dyn Logger>,
    #[shaku(default = (module = "MyModule", value = "Jan 26"))
    today: String,
    #[shaku(default = (value = "Jan 26"))
    year: usize,
}

The second default would apply to all modules listed above.
The fully build module can be generated as a Lazy in the main.rs file.
This would basically remove the need to declare anything in the main function.
How do I find this idea?

I'm not sure the example makes sense. A module brings together many components and providers, it doesn't have injected fields of it's own.
I'm not looking to drastically change the API right now.

Sounds fair


sftp access with password to containers

It would be nice to be able to create accounts that can access a path of the container filesystem through sftp with password authentication. These users should not have access to a shell just to sftp-server. The use case is a replacement for ftp which some customers are still in love to.

Users wanting 90's approach will be able to buy a dedicated ip address (i am currently defining the api for managing them) and directly map it to the container. This will solve basically any non-expected use case

Mmm there's a good chunk of people still in the 90s tech wise, you recently added an ftp client so you should be aware of that ;) Whatever you'll end up with is fine for me. Thanks!


release 0.10.25 to fix bug and support queryset_class

Hey bro, release please. The document had been updated, but the version is old.

Done


add .vscode/settings.json in the .gitignore?

Hey, each time I pull the repository, I have a chante in the .vscode/settings.json (see snapshot):

I suspect that it is in my vscode settings. Shouldn't we add this file in the .gitignore? Or the .vscode/ folder?

For dev purposes, people preferred to keep the settings file in the repo. This allowed for specific settings to debug in vscode to be preshared.

If you would add the already commited file to the .gitignore, it won't igonore it. You would need to remove it from you local index:  git update-index --assume-unchanged <file> (https://stackoverflow.com/a/28497505)


Does not work on ionic

ERROR Error: Uncaught (in promise): TypeError: Object(...) is not a function
Ionic:

   ionic (Ionic CLI)  : 4.12.0 (/Users/victor/.nvm/versions/node/v10.15.3/lib/node_modules/ionic)
   Ionic Framework    : ionic-angular 3.9.2
   @ionic/app-scripts : 3.2.0

Cordova:

   cordova (Cordova CLI) : 8.1.2<EMAIL_ADDRESS>   Cordova Platforms     : android 8.0.0, ios 5.0.1
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, (and 12 other plugins)

System:

   Android SDK Tools : 26.1.1 (/Users/victor/Library/Android/sdk)
   ios-deploy        : 1.9.4
   ios-sim           : 8.0.1
   NodeJS            : v10.15.3 (/Users/victor/.nvm/versions/node/v10.15.3/bin/node)
   npm               : 6.9.0
   OS                : macOS Mojave
   Xcode             : Xcode 10.2.1 Build version 10E1001
```

@prescindivel I believe this is a duplicate of https://github.com/shipshapecode/angular-shepherd/issues/10
I think the issue there was we have compiled and released the latest version with Angular 8, which has made it incompatible with previous versions. Can you confirm your Angular version?

@rwwagner90 That's why, my angular version is 5+.


Migrate Prow jobs to Github Actions

Description
As Prow will be discontinued in 2024, we have to move the Prow jobs used for the Application Connector Manager to an alternative CI/CD system. In our case Github Actions is the preferred choice.
Overview of all existing Prow-jobs is listed here: https://github.com/search?q=repo%3Akyma-project%2Ftest-infra+framefrog&type=code&p=1
See also https://github.com/kyma-project/application-connector-manager/blob/main/docs/contributor/04-10-ci-cd.md
AC:

[ ] Identify which of the jobs listed in the URL above are required during the Application Connector Manager development-lifecycle and relevant in the longterm (have to be migrated)
[ ] All Application Connector Manager related Prow jobs are migrated to Github Actions

Reasons
Migrate CI/CD jobs from Prow to Github Actions as Prow will be discontinued in 2024.
Attachments

Relations
Relates to #104

There is a chance that this issue will make #104  obsolete!


add conditional to rpm spec to test for arch, fixes 13616

Summary of testing can be viewed at the gist
https://gist.github.com/polygotdev/8610fff8d0c0419c0b22215850517433#file-readme-md
Additional changes should be considered in the future for the glibc dependency but for now this is a minimal change.

Hi @polygotdev, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks for this @polygotdev! It should be available in the Insiders build tomorrow and I've added verification needed to the issue #13616 so it gets tested before the released :fireworks:


🐛 uplift all vulnerable dependencies

Uplift x/net and micklei/go-restful to latest non-vulnerable versions.

/test-ubuntu-integration-release-1-2

/retest

/test-ubuntu-integration-release-1-2

/test-ubuntu-integration-release-1-2


Hybrid rendering: Cannot destructure property 'firstRequest' of 'state.value' as it is undefined

Reproduction: https://stackblitz.com/edit/github-fi3r47-xug7re
The reproduction project is SSR but one of the routes is set with { ssr: false }.
This error occurs when I navigate to this route via address bar.
Step:

Open the repro link
Append /bug in webcontainer address bar after the dev server started
You will see 500 Cannot destructure property 'firstRequest' of 'state.value' as it is undefined.

@kingyue737 I can protect the code against the error, I have no idea what's happening since we can't register anything, check vuetify-client-hints.client.ts

@kingyue737 I guess I've found the way to hack it via Nitro plugin detecting non SSR page request and sending server-timing http headers to the client, rn the new /no-ssr  page in the playground works on page refresh, I need to expose the configuration to the Nitro Plugin and finish some logic in the client to restore the theme

@kingyue737 added nitro plugin and updated SSR client hints logic to restore theme-color, working fine.
If you want to test it, you can fork this repo and checkout the PR branch, instructions in the PR to run the playground.

@kingyue737 should be fixed in v0.9.1, the fix didn't require a nitro plugin, the data can be configured in the client plugin


Experiment with Mongo Docker Testing

Could we possibly do this together?
Would love to get more in-depth with Docker.

Running mongo test image in pipeline.


Update plugin-zohosprints.yml

Permission file

Description

Submitter checklist for changing permissions

Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[x] Add link to resolved HOSTING issue in description above

For a new permissions file only

[ ] Make sure the file is created in permissions/ directory
[ ] artifactId (pom.xml) is used for name (permissions YAML file).
[ ] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[ ] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[x] All newly added users have logged in to Artifactory at least once

Maintainer checklist (not for requesters!)

[x] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[x] Check that the $pluginId Developers team has Admin permissions while granting the access.
[x] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
There are IRC Bot commands for it

I am on-holding this request as the plugin appears to have security issues.

@daniel-beck  Mentioned changes are done. updated to repo

The issue I was concerned about has been addressed.

@slide  All my changes are done. Can you please check this request.


feat: support for lambda authorizer

Description of changes:
This PR adds support for a new authorization type supported by AppSync : AWS_LAMBDA.
Customers will be able to use an AWS Lambda function to determine whether to authorize a request based on a custom authorization token.
Similarly to OIDC, customers will be able to provide their own token to Amplify by providing an auth factory, an instance of a type conforming to APIAuthProviderFactory, and by overriding the functionAuthProvider() method to return an AmplifyFunctionAuthProvider as follow:
class MyFunctionAuthProvider: AmplifyFunctionAuthProvider {
  func getLatestAuthToken() -> Result<AuthToken, Error> {...}
}

class MyAPIAuthProviderFactory: APIAuthProviderFactory {
  open func functionAuthProvider() -> AmplifyFunctionAuthProvider? {
        return MyFunctionAuthProvider()
  }
}

let apiPlugin = AWSAPIPlugin(apiAuthProviderFactory: MyAPIAuthProviderFactory())
try Amplify.add(plugin: apiPlugin)

Support for Lambda in DataStore (multi-auth included) is achieved with new AuthRuleStrategy and AuthRuleProvider values custom and function.
We've decided to use custom as rule strategy for different reasons:

future implementations of additional auth modes as flexible as a Lambda function (i.e. http)
using a Lambda to decide whether a request is authenticated or not provides a high (if not the highest) degree of flexibility

Check points:

[ ] Added new tests to cover change, if needed
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1334 (d96a815) into main (027140b) will increase coverage by 1.67%.
The diff coverage is 72.70%.

@@            Coverage Diff             @@
##             main    #1334      +/-   ##
==========================================
+ Coverage   58.85%   60.53%   +1.67%
==========================================
  Files         651      633      -18
  Lines       19156    18940     -216
==========================================
+ Hits        11275    11466     +191
+ Misses       7881     7474     -407

Flag
Coverage Δ

API_plugin_unit_test
65.32% <73.65%> (+9.95%)
:arrow_up:

AWSPluginsCore
75.92% <74.68%> (-0.46%)
:arrow_down:

Amplify
48.56% <62.12%> (+0.49%)
:arrow_up:

Analytics_plugin_unit_test
?

Auth_plugin_unit_test
82.31% <100.00%> (+0.02%)
:arrow_up:

DataStore_plugin_unit_test
74.42% <73.90%> (+0.77%)
:arrow_up:

Predictions_plugin_unit_test
30.42% <ø> (-3.10%)
:arrow_down:

Storage_plugin_unit_test
57.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

Amplify/Amplify.swift
86.95% <ø> (ø)

...lify/Categories/API/APICategoryConfiguration.swift
100.00% <ø> (ø)

Amplify/Categories/API/APICategoryPlugin.swift
0.00% <ø> (ø)

...ries/API/AuthProvider/APIAuthProviderFactory.swift
0.00% <0.00%> (ø)

...plifyAPICategory+AuthProviderFactoryBehavior.swift
0.00% <ø> (ø)

...r/AmplifyAPICategory+GraphQLBehavior+Combine.swift
0.00% <ø> (ø)

...vior/AmplifyAPICategory+ReachabilityBehavior.swift
0.00% <ø> (ø)

Amplify/Categories/API/Error/APIError.swift
63.33% <ø> (+5.00%)
:arrow_up:

...tegories/API/Reachability/ReachabilityUpdate.swift
0.00% <ø> (ø)

.../Categories/API/Request/GraphQLOperationType.swift
0.00% <ø> (ø)

... and 230 more

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 318fcfd...d96a815. Read the comment docs.

Comments inline, plus:

Add integ tests

Added API integration tests


Remove ads from the tweets object

Figure out a way to remove any ads that may have snuck into the json archive

Should probably implement this in the scraper too, but that thing needs a full rewrite at this point


Creating a scene for blinds, both positions are not saved

Did you read the instructions?

[X] I have read the README, including the advanced debugging section.

The problem
Creating a new scene for blinds, I was able to set the position and the rotation of the blinds.
This is not working anymore.
After applying values for position and rotation and hitting "save", the values are reset.
What version of this integration (ha-tahoma) has the issue?
2.8.2
What version of Home Assistant Core has the issue?
core-2021.10.4
Which gateway / hub do you use?
 I am not using this myself, thus I would need to have a look, however I wonder why this isn't working. It doesn't seem like an issue on the integration side.
@vlebourl, @tetienne what do you think?

@iMicknl - first of all, thanks for you replying so quick!
No, I am afraid, the only covers are Tahoma ones.

@sebnaf When you set the position of your blind creating the scene do they move?
Here an example of YAML to set the position.
- id: '1634214050767'
  name: Foo
  entities:
    cover.volet_du_bureau_4:
      current_position: 39

Yes, they move to the requested position.

@sebnaf have you tried saving the scene? I have the same front-end bug as you, however it still works.
When I change the cover position in the scene, my cover will move directly, but the slider will revert to original position. Now I press save. When I have my cover in another position and I activate the scene, it works.


raft: Forward-port improvements to campaign on restart

This brings the code on master in sync with the 1.12 changes in #1588. The code on master does not have the same problem (since a newer etcd/raft library lets it skip the problematic check), but the version being adopted by 1.12 should be a bit more robust.
This is a separate PR against master instead of cherry-picking from master to bump_v1.12.2 because the code has diverged and needs to be a bit different on master anyway (different etcd/raft version).
cc @LK4D4 @mrjana

Current coverage is 54.09% (diff: 100%)

Merging #1589 into master will increase coverage by 0.02%

@@             master      #1589   diff @@
==========================================
  Files            84         84
  Lines         13847      13849     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           7487       7491     +4
+ Misses         5356       5355     -1
+ Partials       1004       1003     -1

Powered by Codecov. Last update 8f8099a...d0844fa

Passes Docker integration tests (except the ones that are normally flaky for me)

@aaronlehmann I don't quite understand. Does this code needed at all in master?

I think it's more correct than the code that's on master right now. It may call Campaign too early, and the new version of etcd/raft automatically ignores that call. So we may have 5 second startup delays in rare cases. This PR should theoretically prevent that.

LGTM


implement Clone on Database

In order to use fdb in a State in Axium, we need Database struct implement Clone.
It should be possible because the inner (fdb_sys::FDBDatabase) is just a type to struct FDB_database which implement themself Clone.
Open to make a PR, but I got an error with build.rs files:
error[E0282]: type annotations needed
  --> foundationdb-sys/build.rs:56:9
   |
56 |     let api_version;
   |         ^^^^^^^^^^^

Hello :wave:
For this kind of usage, I believe you shouldn't clone the whole state of the database but rather use a shared pointer using Arc<>. Additionally, for your api_version error, that might be because you didn't specify a feature version of your FoundationDB client target (see foundationdb-sys/build.rs#13). You can use embedded-fdb-include` to use the version installed on your system.

Thank you @alexandrebrg ,
Yes, using an Arc solves the problem, but since Database corresponds to a binding on the native client anyway, I don't think implementing Clone would make much difference.
Thanks for the tip on api_version, I found the solution after posting my question, so a little README update would be good.


Load MathJax only if not present yet.

We added a simple if statement to check whether mathjax is already loaded:
if (typeof MathJax == 'undefined') {
    ...
}

On our platform, mathjax may already be loaded, so this modification prevents
redundant resource loading.

Did you check that MathJax really working?
Because you skip loading of configuration script mathjax_config.js.

If I just simply load MathJax.js without mathjax_config.js, it will not always work.
Difference you could see here:
http://web-docs.gsi.de/~linev/js/dev/index.htm?nobrowser&file=../files/latex.root&item=ex3;1&mathjax=1
and
http://web-docs.gsi.de/~linev/js/dev/index_mathjax.htm?nobrowser&file=../files/latex.root&item=ex3;1&mathjax=1

We are loading the mathjax_config.js file within our mathjax setup via require.js.


Published storybook includes internal shared mdx files

🧹 Tech Debt
Our storybook docs are accidentally pulling in all mdx files as stories, even if they are not meant to be stories. For example:

The files to pull in are specified here:
https://github.com/ni/nimble/blob/fde3626559e2469f8540c45d9ff774838b49bb75/packages/nimble-components/.storybook/main.js#L4-L9
We should update our file names and the wildcards in .storybook/main.js to only pull in the actual stories we want as part of our storybook page. As a note, we cannot do this by renaming the public ones to be *.stories.mdx because this causes problems in storybook because .stories.mdx files are treated in a special way by storybook (see https://github.com/storybookjs/storybook/issues/20496).
For more information/background on this issue see https://github.com/ni/nimble/pull/1411#discussion_r1283509701

It looks like this was resolved by #1490 & #1495, so I'm going to close the issue.
@jattasNI, feel free to re-open this if you are aware of more work that should still be done as part of this issue.


[Bug] pdf2parquet  must calculate hash and size on the file

Search before asking

[X] I searched the issues and found no similar issues.

Component
Tools/ingest2parquet
What happened + What you expected to happen
I had duplicate documents (see attached).
I was expecting the exact same duplicate files to have same size and hash.
But seems like the hash is being calculated on 'contents' which is actual content + meta data (like file name)
I think the hash and size should be calculated on the actual file/document not on meta data.

Expected Behaviour

hash should be identical to identical files
size should be physical file size in bytes
to avoid confusion, these columns can be renamed (or new columns can be created) with names like  file_hash  and file_size

Reproduction script
earth.pdf
Create a copy of the above file
execute the pdf2parquet section here : https://github.com/sujee/data-prep-kit-examples/blob/main/dpk-intro/dpk_intro_1_python.ipynb
Anything else
No response
OS
Ubuntu
Python
3.11.x
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

At the moment the hash column contains the hash of the actual contents column. This is the JSON representation of the output, which has the property file-info.filename, so different filenames will have different content.
Internally, the JSON has a property description.document-hash which is the actual hash of the binary input file.
It could indeed make sense to expose that one as well. Where? Should it be the document_id? Another field? Happy for an open discussion here.

I do see document_hash in the contents.
I would like to see this propagated up as a top-level column in parquet.  Along with actual file size.

@dolfim-ibm with the new Docling integration, will this be addressed as well?

Reading again above, there were some open questions about which field to expose and with which names. The fact of exposing both is for sure a good idea, since they serve different purposes.

Should be fixed in https://github.com/IBM/data-prep-kit/pull/756.

@sujee Can you test and see if this can be closed?

pdf2pg now bloked by #767


Credential Request Entropy

Looking for some clarification around entropy. It's listed as Optional() in the types.py Class yet if I omit it and pass a prover_did instead, I get an error message app.libs.anoncreds.error.AnoncredsError: entropy is required.
Should this be marked as required in the python class?

Furthermore, setting both entropy and prover_did yields app.libs.anoncreds.error.AnoncredsError: Prover did and entropy must not both be supplied.
So to use the prover_did, I need to provide the prover_did as entropy and set prover_did to None, rendering the prover_did attribute useless.

prover_did is used only when you are handling objects with 'legacy' identifiers, meaning by that those coming from Indy (e.g. DIDs that are 21-22 base58 characters long, or schemas/credDefIds matching the pattern from legacy Indy objects). In such case, you must only provide it (leaving entropy undefined).
On the other hand, when you are using fully qualified DIDs (or any other kind of identifiers that is not legacy), you must provide entropy and leave prover_did.
So the question here is... what kind of identifiers are you using for your issuer, schema, cred def, etc?

Thanks for the clarification. In my scenario I'm using a did:web identifier ie: did:web:domain:alice, therefore I should be using the entropy attribute. My issue is about the prover_did attribute from the CredentialRequest.create() function which I suspect is not useable with the current code implementation. entropy should be marked as required and ideally prover_did removed from said function.

Thanks for the clarification @TimoGlastra , I will close the issue


TypeScript migration and experiment with Oclif for CLI management

TODO

[x] Use TypeScript compiler (#1018)
[x] Move source code to TypeScript (#1020)

Closed with #1018 and #1020.


The links in the menu titles on the left seem to be clickable off they should not be.

The links in the menu titles on the left seem to be clickable off they should not be.

CSS pointer-event on label needs to be set to none

Fixed with commit eb144a1. Pull develop branch to test it. Closing, reopen if necessary.


Accept pragmas within declare expressions

(_declare_item): accept pragmas
Assert pragmas (and other "executable" pragmas) are specifically allowed in declare expressions, thanks to a recent AI22-0045. They are accepted by the latest GNAT compilers.
Regenerate grammar using tree-sitter-linux-x64-0.20.7; add test.

Thanks for the patch, all good and merged !


kubeconfig-default-ttl-minutes setting should be made to accept only integer values

Setup
Rancher version: 2.6-head 78017e6
Browser type & version: Chrome
Describe the bug
Currently we can set the value for kubeconfig-default-ttl-minutes setting in the UI to any non-integer values. By accidentally setting the value to a non-integer value, when we try to download the kubeconfig button, the file will not be downloaded and fails with an error
To Reproduce

On rancher v2.6-head, navigate to global settings >> Settings >> set kubeconfig-token-ttl-minutes to 2/
Navigate to local explorer, click on download kubeconfig button

Result
Download fails with the error
message: "failed to get default token TTL: failed to parse setting 'kubeconfig-default-ttl-minutes': error parsing token ttl: time: unknown unit \";m\" in duration \"2;m\""
Expected Result
UI not allowing to save non integer values.
Related: https://github.com/rancher/dashboard/issues/6120

Verified on v2.6-head 6629e3e
Input takes only integer values.


Wrong BOLT11 prefix in regtest

Issue: https://github.com/lightningnetwork/lnd/issues/882
Blocked by: https://github.com/Roasbeef/btcd/pull/19
In this pull request was only added tests to check correctness of prefix in encoded invoice

[ ] Update Gopkg.toml after merging btcd change

BTW, I am seeing this when running LND with bitcoind as my backend, so I don't think that it would be correct to assume that fixing btcd will correct this.

@litch it will, lnd has dependency from forked btcd because use some libraries from it, one of them is chain configuration

Ah, ok.  I stand corrected.  Thank you.
I was having some other issues in general with LND and regtest (not simnet) invoice payments.  Hopefully that can get sorted.

Thanks @vapopov, the test cases you've added LGTM. Should be able to get this in after your PR to btcd is merged 🙌


Support JSDoc's @example

I would like to see doc.deno.land supporting @example tag – https://jsdoc.app/tags-example.html.
Example of using such tag:

https://github.com/Im-Beast/deno_tui/blob/7ab514cb31abb9ac96f509fde2942a0851b161bb/src/event_emitter.ts#L43

It looks like vscode handles these on hover text. We should as well. Going to need support in deno_doc first.


Cloud debugger does not seem to work with the jetty9 compat image

I check the internal docker image we have, and Cloud debugger is working there.
But not from what we have in github.
The script diff I see is only this:
Test if the argument is executable and if then run it directly
if type "$1" &>/dev/null; then
exec "$@"
fi
in the jetty_run.sh script
Not sure what else is different..

Those extra lines are to conform to the docker policy of supporting 'docker run image bash' or similar.  If they are a problem for the debugger, then just remove them as they are not that important.

I tried briefly, and the container did not start (no response)
Did not have time to debug
On Sep 26, 2015 12:41 AM, "Greg Wilkins"<EMAIL_ADDRESS>wrote:

Those extra lines are to conform to the docker policy of supporting
'docker run image bash' or similar. If they are a problem for the debugger,
then just remove them as they are not that important.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/issues/96#issuecomment-143369364
.

I'll be available this evening to help debug if need be.

1 issue at least is that wget is not in the base image. I'll add it to the base jdk image.

via ssh to the image,
Info: Limiting Java heap size to: 2569M
/var/lib/jetty/jetty_run.sh: line 30: wget: command not found
/var/lib/jetty/jetty_run.sh: line 36: wget: command not found
Downloading Cloud Debugger agent from https://storage.googleapis.com/vm-config.openblend-demo.appspot.com/
/var/lib/jetty/jetty_run.sh: line 41: wget: command not found
tar (child): cdbg_java_agent.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
/var/lib/jetty/jetty_run.sh: line 45: cdbg/format-env-appengine-vm.sh: No such file or directory
2015-09-25 17:06:31.606:INFO::main: Logging initialized @235ms
2015-09-25 17:06:32.239:INFO:oejs.Server:main: jetty-9.3.2.v20150730
2015-09-25 17:06:32.287:INFO:oejs.AbstractNCSARequestLog:main: Opened /var/log/app_engine/request.2015_09_25.log
2015-09-25 17:06:32.532:INFO:oejs.ServerConnector:main: Started ServerConnector@310ba866{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:8080}
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.eclipse.jetty.util.TypeUtil.construct(TypeUtil.java:564)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:347)
at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:259)
at com.google.apphosting.vmruntime.jetty9.VmRuntimeWebAppDeployer.doStart(VmRuntimeWebAppDeployer.java:72)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:405)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:372)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1510)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1435)
Caused by: java.lang.NoClassDefFoundError: org/apache/http/conn/ClientConnectionManager
at com.google.apphosting.vmruntime.jetty9.VmRuntimeWebAppContext.(VmRuntimeWebAppContext.java:206)
... 18 more
Caused by: java.lang.ClassNotFoundException: org.apache.http.conn.ClientConnectionManager
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 19 more

Ah -  wget was removed when we started assembling the maven depenencies with maven rather than with wget.  I didn't notice that it was needed by the run script.
I've not seen this put back, so I'll make a PR shortly.

OK, so next step is how we set the Cloud Debugger for 'custom' runtimes, Since the Java8 work is pending, the 3 images produced here are seen as custom runtime in the backend deploy process, and it does not handle the Cloud debugger out of the box. Here is what the debugger lead says:
Here is how it works on MVM today:

During the deployment AppEngine (I think it's done in admin console) checks runtime ID. If it starts with "java", it copies cdbg_java_agent.tar.gz from Cloud Debugger GCS to application GCS.
We then sets gae_debugger_filename metadata to the URL of the debugger .tar.gz file in application GCS.
jetty_run.sh picks it up, downloads and enables the debugger.
The purpose of this elaborate mechanism is to ensure that:
All instances use the same version of the debugger.
Every time you redeploy, you get an up to date version of the debugger.
In the Java8 image:
It is a custom runtime, so gae_debugger_filename metadata property is empty.
The jetty_run.sh script should not even try to download the debugger package, but it does for some reason (did you set CDBG_AGENT_URL environment variable?). It downloads some file from https://storage.googleapis.com/vm-config.openblend-demo.appspot.com/, but it's not .tar.gz., so it wouldn't work.

As a workaround if you set CDGB_AGENT_URL environment variable to https://storage.googleapis.com/cloud-debugger/appengine-java/current/cdbg_java_agent.tar.gz, everything should just work.
We need to fix it properly though. We can either extends the current mechanism to support custom runtimes, or we can just relax our two requirements for Cloud Debugger that is mentioned above and include cdbg_java_agent.tar.gz in Dockerfile.

Currently jetty_run.sh determines the value of CDGB_AGENT_URL with:
  CDBG_REF_URL="http://metadata/computeMetadata/v1/instance/attributes/gae_debugger_filename"
  if [[ -z "${CDBG_AGENT_URL}" ]]; then
    CDBG_AGENT_URL="https://storage.googleapis.com/vm-config.$(echo ${GAE_LONG_APP_ID} | sed -e 's/^\(.*\)\:\(.*\)$/\2.\1.a/g').appspot.com/"
    CDBG_AGENT_URL+="$( wget -q -O - "$@" --no-cookies --header "${METADATA_HEADER}" "${CDBG_REF_URL}" )"
  fi

If I understand the MVM advice you've reported, we can replace this code with simply setting the variable:
CDGB_AGENT_URL=https://storage.googleapis.com/cloud-debugger/appengine-java/current/cdbg_java_agent.tar.gz

The current script then downloads the agent with:
  echo "Downloading Cloud Debugger agent from ${CDBG_AGENT_URL}"
  AUTH_HEADER="Authorization: Bearer ${OAUTH_TOKEN}"
  wget -O cdbg_java_agent.tar.gz -nv --no-cookies -t 3 --header "${AUTH_HEADER}" "${CDBG_AGENT_URL}"

The MVM advice is that we don't download the agent at all?  But I can't see how that can work with just setting CDBG_AGENT_URL?   Perhaps the advice about that variable is just a work around until another mechanism automatically adds the agent files.
The proposed agent URL appears to be a public URL, so I don't believe that OAUTH is now needed and we could just do the wget.
The script then expands the tgz and determines the command line arguments with:
  # Extract the agent and format the command line arguments.
  mkdir -p cdbg ; tar xzf cdbg_java_agent.tar.gz -C cdbg
  DBG_AGENT="$( cdbg/format-env-appengine-vm.sh )"

This appears that it will still work with the agent that is downloadable from the proposed location.
So I'll prepare a PR that adheres to what I think the advice is... but I'm not yet sure I know how to test this.

I've created PR #105 that I believe follows the advice regarding the agent download.
I'm not yet familiar with how I can test the cloud debugger, but running manually within a boot2docker instance I can see the agent downloaded, installed and run. It produces output like:
root@2072edc34a88:/var/lib/jetty# java -agentpath:/var/lib/jetty/cdbg/cdbg_java_agent.so=--log_dir=/var/log/app_engine,--logtostderr=true,--cdbg_agentdir=/var/lib/jetty/cdbg,--cdbg_extra_class_path=/var/lib/jetty/webapps/root/WEB-INF/classes:/var/lib/jetty/webapps/root/WEB-INF/lib -jar /usr/local/jetty/start.jar
I0927 23:05:08.424062    54 jvmti_globals.cc:300] Build time: Jul 16 2015 09:26:30
I0927 23:05:08.424195    54 jvmti_agent.cc:113] Java debuglet initialization started
I0927 23:05:08.424242    54 jvmti_agent.cc:154] Java debuglet initialization completed
I0927 23:05:08.492349    54 jvmti_agent.cc:163] Java VM started
I0927 23:05:08.497036    54 jvmti_agent.cc:173] JvmtiAgent::JvmtiOnVMInit initialization time: 4707 microseconds
I0927 23:05:08.497097    63 jvmti_agent_thread.cc:72] Agent thread started: CloudDebugger_main_worker_thread
I0927 23:05:08.499094    63 jvm_internals.cc:37] Loading class loader from /var/lib/jetty/cdbg/cdbg_java_agent_internals_loader.class
I0927 23:05:08.500098    63 jvm_internals.cc:335] Loading internals from /var/lib/jetty/cdbg/cdbg_java_agent_internals.jar
I0927 23:05:08.556953    63 jni_logger.cc:15] Initializing ClassPathLookup, default classpath: true, extra classpath: [/var/lib/jetty/webapps/root/WEB-INF/classes, /var/lib/jetty/webapps/root/WEB-INF/lib], config: /var/lib/jetty/cdbg/cdbg_config.xml
I0927 23:05:08.676368    63 jni_logger.cc:15] Total size of indexed resources database: 1026 bytes
I0927 23:05:08.680930    63 jvm_internals.cc:109] ClassPathLookup constructor time: 137863 microseconds
2015-09-27 23:05:08.957:INFO::main: Logging initialized @534ms


Refocus the :focused element after the layout rendering

Fix for problem described here #4097 : Focused element loses focus when MaterialLayout is upgraded

LGTM.
Waiting for ACK from @sgomes or @surma for a sanity check before merge.

LGTM :) Thanks @rundef!


analytics-node does not close HTTPS connection on closeAndFlush

closeAndFlush() does not close the HTTPS connection to the Segment API:
Leaked resources 0:
[WTF Node?] open handles:
- File descriptors: (note: stdio always exists)
  - fd 2 (tty) (stdio)
  - fd 1 (tty) (stdio)
  - fd 0 (tty)
- Sockets:
  - XX.XX.XX.XX:61342 -> <IP_ADDRESS>:443

@nferch I tested this -- the HTTP connection closes, but it might take an extra tick if you're dumping wtf-node right after.
await analytics.closeAndFlush()
setImmediate(() => wtf.dump())

// [WTF Node?] open handles:
- File descriptors: (note: stdio always exists)
  - fd 2 (tty) (stdio)
  - fd 1 (tty) (stdio)


Tidier column names and types

Convert column names to lower_snake_case to avoid users having to employ backticks. Eventually the EBD will be released with a header using the same column name format. Only way I was able to figure out how to do this was via  dplyr::select(ds, dplyr::all_of(col_names)), but very open to a simpler way if there is one.
Set column types based on name rather than position. Only those columns that aren't character are specified, everything else defaults to character. This has three benefits:

The EBD has been know to change without warning, e.g. dropping or adding columns or changing order, so hopefully this protects us against that.
Many of the EBD columns are not required or redundant, and users may want to remove columns prior to importing to parquet to reduce file size.
This will allow us to now import either the EBD of Sampling Event Data using the same code since the SED has a subset of the EBD columns.

Very nice.  Yup, totally with you on snake_case. I was hesitant to change from the default heading but happy to do so with your endorsement!  Also agree on the explicit column names, thanks for adding that.

Oh minor thing @mstrimas , can you update the unit test to use the new snake_case column name?  See checks above.  (yeah so far the unit testing is pretty minimal!)

Oops, forgot about those unit tests, should be fixed now!

Nice, thanks!
I'm fine with having the patch for #3 in here.   (As long as the PR is small enough to enable easy review I never mind addressing multiple issues in a single PR.  I think that kind of modularity is more important only on bigger / widely used projects)


Question about redux and angular2

Hi,
I'm not submitting a bug report, I'm just looking for some explanations, and want to be sure I understand correctly the way angular 2 and redux work together.
When the reducer returns the new state, this is a completly new object. So, in my angular components, every @select() is "triggered" right ?
In my case, I have a pretty complex state looking more or less like this :
{
    dasboard: {
        users: {
             123456AB: {...},
             123456AC: {...},
             123456AD: {...},
        },
        vectors: {
             123456AE: {...},
             123456AF: {...},
        },
        ...
    }
}

In one component, i have
@select(['dashboard', 'users']) users$: Observable<any>;
...

ngOnInit() {
    this.subUsers = this.users$.subscribe((users) => {
         // blablabla
    })
}

and in another one i have
@select(['dashboard', 'vectors']) vectors$: Observable<any>;
...
ngOnInit() {
    this.subVectors = this.vectors$.subscribe((vectors) => {
         // blablabla
    })
}

And in my templates I have something like

{{ user.name }}

(keys is a pipe I created so I could loop over an object)
Suppose I update dashboard.vectors.123456AE. My reducer returns a new state, because at the begin I copy the state this way : let copyState = JSON.parse(JSON.stringify(state)) in order to work on a new object.
All my components are rendered again, even the one linked only to the users part, and even if the users properties did not change. Is it right, or am I doing something wrong ? I'm not sure about the perf, because my whole application is refreshed even when it should not be.
Thanks a lot !

Hi @gnujeremie
I'm not sure why all components get re-rendered. My guess is: the check works "per store object". In this case "dashboard" (it is dashboard, not dasboard, right?). Normally you don't group data in the store by view (or anything else) but make the kind of data you're dealing with the root properties. Like this:
{
  users: {
    list: [ { /* Normally arrays are better because they have an order you can rely on. */ } ],
    loading: false // normally I use a flag here to indicate whether the list is loading. This way it's very easy to implement loading indicators.
  },
  vectors: { /* ... */ }
}

But I can tell you that JSON.parse(JSON.stringify(state)) is slow. A better approach could be this:
const newState = Object.assign({}, oldState, {changedProperty: changedValue});

Alternatively you can use a library that makes working with objects and arrays easier without modifying them - example: Ramda (But it's not yet nice to use with ES6 import). Or you can use libraries like Immutable.js.

Thanks for you answer. I was planning to change my store so I would have something like your advice
{
    users: {...},
    vectors: {...}
}

Thanks again :)

Just a comment: do you remember to unsubscribe in the ngOnDestroy methods?

Another comment - if you're using | async, you don't need to also subscribe in ngOnInit: async will manage the subscription for you.
As for refresh - @select (and the non-decoration version, ngRedux.select) both use the distinctUntilChange operator under the hood to cut down on updates when that selector's input data hasn't changed.  So the users stuff should not be firing if only the vectors stuff changed, and vice versa.  It's possible that your JSON serialize/deserialize approach is doing something odd; I second @alinnert 's comment about Object.assign or Ramda instead (Ramda is a great lib).
However if you want to dig into it a little more, @select also allows you to specify a custom comparator that it will determine if the selector's data really changed:
function usersComparator(old, new) {
  // Custom comparator logic: stick a debugger in here to see what's going on?
  return old === new; // This is what the default check does.
}

@select([ 'dashboard', 'users' ], usersComparator);

Finally, depending on what your keys pipe does, you may be running into ngFor oddness that happens when it's given a new array instance each time it loops.  Can you post the code for 'keys'?

@spock123 yes, i unsubscribe in ngOnDestroy :)
@SethDavenport thanks for your explanations. I know @select does the unsubscribe, however I do need to subscribe in my component, for other operations on the data from the state.
I'll dig into Ramda, and for know I started using several reducers (one for users, one for vectors) and it seems to fix most of my problems.
Thanks to all of you for your help and explanations !


Rename check-your-answers.html to check-answers.html

Fixes #804.
This PR changes the file title of our check-your-answers.html template to check-answers.html. This is to mirror the name of the pattern in the Design System.

Closing this as it dupes #1088.


NASNet Large achieves low accuracy on ImageNet subset

(As the issue is related to making predictions on a subset of ImageNet pictures I can not include a code that does not require external data download)
I make class predictions on the following dataset, which is a dog only subset of ImageNet images:
https://www.kaggle.com/c/dog-breed-identification/data
Image preprocessing

Image size: 331*331 pixels
Image preprocessing: preprocess_input() from keras.applications.inception_v3
Data augmentation: No

Models

I tested the below listed Keras models with “include top” option, and ImageNet weights, no modification whatsoever
I use predict_generator() to make the predictions

Top 1 accuracy results

NASNetLarge: !!!51.21%!!!
InceptionResNetV2: 92.61%
Xception: 92.31%

Environment:

Ububtu 17
Keras 2.1.4
Cuda V8.0.61
CuDNN 7.0.5
Tensorflow 1.4.0rc0
NVIDIA Quadro P5000

@andraskuti can you try out the version in keras-contrib? It was implemented independently which could help figure out the problem https://github.com/keras-team/keras-contrib/blob/master/keras_contrib/applications/nasnet.py

Sure. I got very similar results.
Top1 accuracy on the given task for NASNetLarge (keras-contrib version) is 50.61%
(using the same setup as described above)

This is surprising. I know this is starting to sound repetitive, bit can you try to make predictions using the Tensorflow NASNet large model directly using the slim implement?
If that can score close to the inception models, and the Keras models can't, it may point to some preprocessing bug, or perhaps even some bug in how the weights are loaded.
When I was loading the weights, I was careful to check the shape, and number of weights that I loaded. All weights extracted as numpy arrays we're loaded successfully into their Keras equivalent layers. I also made sure to use the correct batch norm hyperparameters for the different models. Theoretically, there should be no major difference to the Keras version and the Tensorflow slim version

I did try nasnet on a completely different task and get surprisingly poor results, but that could have been due to one of many factors, so I didn't suspect a problem like you describe here. If this is an actual conversion bug I'm curious what the root cause might be.

We have another report of problems with the weights transferred for NASNet:
https://github.com/keras-team/keras/issues/9674

There are several independent reports of problems with the NASNet weights, see https://github.com/keras-team/keras/issues/9586

Yes I get that this is an issue. Presently, I am occupied with my final semester so I won't have time to dedicate to this.
If anyone wants to take a look at how to fix this, please go to : https://github.com/titu1994/Keras-NASNet/tree/master/weight_translation
Create two folders, checkpoint and weights. Place the checkpoint you want to translate into it's folder and run extract_weights.py. Then, simply run the NASNet.py code after modifications to get the model you want and save the weights.
Then you can cut paste these weights and load them into the normal model at the root and see if the predictions are correct or not.

Also, there are other independent implementations of NASNet in Keras and PyTorch. Are they using these wonky weights as well ? If not, perhaps we could try using those weights and try some tests to see if model training or ImageNet evaluation is still an issue

Hi all! I fixed it for NASNet-Mobile.
@titu1994, please check https://github.com/titu1994/Keras-NASNet/pull/12
I think, the same would work for NASNet-Large. (hope, I will fix it later)
Without the fix, weights were assigned incorrectly by type.
For example, weights from conv0_bn/moving_mean were assigned to conv0_weights or
weights from conv0_bn/beta were assigned to conv0_bn/moving_mean, etc.
Hope, it would help!

@veronikayurchuk Thank you for this fix ! I am astonished that I thought for a second glob.glob() provides a sorted list of files.
However, I tested out your weights from your repository on the evaluation script on the cheetah and elephant images. Your weights are providing exceedingly low scores for the cheetah, and the elephant (at 38% and 72% respectively).
I used your updated scripts for weight loading and created the weights for NASNet mobile again, and tried prediction on the above images and here are the new results :
Loaded NASNet Mobile
1/1 [==============================] - 4s 4s/step
Predicted: [[('n02130308', 'cheetah', 0.9362247), ('n02128385', 'leopard', 0.002087888), ('n02128925', 'jaguar', 0.0011769015), ('n07802026', 'hay', 0.00055119535), ('n02127052', 'lynx', 0.00042987464)]]

Loaded NASNet Mobile
1/1 [==============================] - 4s 4s/step
Predicted: [[('n02504458', 'African_elephant', 0.78309786), ('n01871265', 'tusker', 0.124640346), ('n02504013', 'Indian_elephant', 0.016551586), ('n02391049', 'zebra', 0.0006357454), ('n01768244', 'trilobite', 0.0005858325)]]

After recreating the weights with your fix locally, the cheetah recognition skyrockets to 93%, whereas elephant increases to 78% as well.
 I don't believe there should be such a drastic difference, especially since I basically ported the weights using your corrected code.
Also, can I inquire as to the OS, TF and Keras versions you use locally?

What's more surprising however, is that NASNet large tends to perform worse on the same images as compared to the Mobile versions, indicating this fix may not entirely solve this problem.
Most probably, there is some weights which are being skipped, or some other problem with how the weights are loaded into their respective layers. @veronikayurchuk I've pushed a few patches to my repo, could you refer to them and see if you can try to find a fix for NASNet Large?
Loaded NASNet Large
1/1 [==============================] - 5s 5s/step
Predicted: [[('n02130308', 'cheetah', 0.869967), ('n02128925', 'jaguar', 0.016802093), ('n02128385', 'leopard', 0.012212922), ('n02129165', 'lion', 0.0035213656), ('n02128757', 'snow_leopard', 0.003336287)]]

Loaded NASNet Large
1/1 [==============================] - 7s 7s/step
Predicted: [[('n02504458', 'African_elephant', 0.52621555), ('n01871265', 'tusker', 0.33077866), ('n02504013', 'Indian_elephant', 0.02492782), ('n02093647', 'Bedlington_terrier', 0.00040763052), ('n01704323', 'triceratops', 0.00040301887)]]

Hi, @titu1994 !
It sounds very weird, as I used my weights and the result are pretty high, but differs from yours.
Cheetah prediction is
1/1 [==============================] - 3s 3s/step Predicted: [[('n02130308', 'cheetah', 0.93829703), ('n02128385', 'leopard', 0.0031160081), ('n02128925', 'jaguar', 0.0016547953), ('n02128757', 'snow_leopard', 0.00067107304), ('n02127052', 'lynx', 0.0005479519)]]
Elephant prediction is
1/1 [==============================] - 3s 3s/step Predicted: [[('n02504458', 'African_elephant', 0.73011684), ('n01871265', 'tusker', 0.17269203), ('n02504013', 'Indian_elephant', 0.017120298), ('n02391049', 'zebra', 0.0007252202), ('n01768244', 'trilobite', 0.0006577261)]]
I am using python3 and Ubuntu 16, keras - '2.1.5', tensorflow -  '1.4.0'.
Can you, please, tell us what is you Keras, TF, OS version?
:)

Windows 10, CUDA 9, Keras 2.1.5, Tensorflow 1.6

Are these scores for NASNet Mobile or NASNet Large? Cause your scores for cheetah match the ones from my mobile model. My scores for the elephant are slightly higher.

yes, exactly!
It is for NASNet Mobile.
But, it sounds weird to me, that the score for elephant differs for 5,3%

Hmm, are you using from weight_translation.weight_load_mobile import * and not from weight_translation.weight_load_large import * by accident ?
In hindsight, using two files with the same methods was a bad design choice

@titu1994 have these changes been brought into keras-contrib?

Not yet I'm afraid. Seems the predictions do not line up with what Tensorflow slim version gets.
I think porting the weights from the tf-hub model / setting it as the baseline and tuning the model weights might be a way forward.
Recent discussion on the MobileNetV2 merge in Keras master can possibly point a proper way to transfer weights to models without the manual error prome method.
If someone can try that, I would be grateful.

@ahundt I've been playing around with TF-Hub to see what exactly is the issue here, so that I can fix NASNet.
Here are the script that i'm using to compare the two (based on the MobileNetV2 discussion a day or two ago) :
import numpy as np
import tensorflow as tf

import tensorflow_hub as hub

from keras.preprocessing import image
from keras.applications.imagenet_utils import decode_predictions

from nasnet import NASNetLarge, NASNetMobile, preprocess_input

size = 331

img_path = 'images/elephant.jpg'
img = image.load_img(img_path, target_size=(size, size))
x = image.img_to_array(img)
x = np.expand_dims(x, axis=0)

y = np.copy(x)
x /= 255.0

inputs = tf.placeholder(tf.float32, [None, size, size, 3])
model = hub.Module("https://tfhub.dev/google/imagenet/nasnet_large/classification/1")
features = model(inputs, signature="image_classification", as_dict=True)
probs = tf.nn.softmax(features['default'])

with tf.variable_scope('keras'):
    model2 = NASNetLarge(weights=None)
    model2.load_weights('weights/NASNet-large.h5')

with tf.Session() as sess:
    sess.run(tf.global_variables_initializer())
    preds = sess.run(probs, {inputs: x})

y = preprocess_input(y)
preds2 = model2.predict(y)

print('Hub Predicted:', decode_predictions(preds[:, 1:]))
print('Model Predicted:', decode_predictions(preds2))

Heres the scores for the cheetah and elephant in my repo :
Cheetah
Hub Predicted: [[('n02130308', 'cheetah', 0.914707), ('n02128925', 'jaguar', 0.0027237295), ('n02128385', 'leopard', 0.0025306053), ('n02423022', 'gazelle', 0.0006407299), ('n01582220', 'magpie', 0.0005725752)]]
Model Predicted: [[('n02130308', 'cheetah', 0.89602923), ('n02128925', 'jaguar', 0.011666419), ('n02128385', 'leopard', 0.00976224), ('n02129165', 'lion', 0.0029320156), ('n02128757', 'snow_leopard', 0.0021664116)]]

Elephant
Hub Predicted: [[('n02504458', 'African_elephant', 0.5226582), ('n01871265', 'tusker', 0.30211642), ('n02504013', 'Indian_elephant', 0.05298932), ('n02408429', 'water_buffalo', 0.0003982857), ('n02391049', 'zebra', 0.00037648008)]]
Model Predicted: [[('n02504458', 'African_elephant', 0.5382313), ('n01871265', 'tusker', 0.31587833), ('n02504013', 'Indian_elephant', 0.026553808), ('n02093647', 'Bedlington_terrier', 0.00042403332), ('n02397096', 'warthog', 0.00039423758)]]

I'm going to try to port the weights using the technique suggested in that thread, and see if these results are the same are not. For now, the weights are very slightly different for sure.

Hmm, that's unfortunate. I'd say the lack of human usability is one of the biggest problems with these NN designed NNs! If only there were a human_usability loss function. 👍

The error has been fixed in #10209.


tarball source url gives error 500

Cant install atom-ternjs because https://www.atom.io/api/packages/atom-ternjs/versions/0.18.3/tarball gives error 500

looks like a general issue on this server

This seems to be an issue with atom itself. Have you tried finding a solution on there forums or on GitHub?


mariadb/SQL error on startup

Hi, I'm getting the following log when trying to start the server (using any release later than 2.3.1)
2022-05-05T15:54:21.050711045+02:00 [INFO ] potentially running migration '20201103-rename_language_mappings_table'
2022-05-05T15:54:21.052938583+02:00 [INFO ] potentially running migration '20201106-migration_cascade_constraints'
2022-05-05T15:54:21.056297881+02:00 [INFO ] no need to migrate '20201106-migration_cascade_constraints'
2022-05-05T15:54:21.056338695+02:00 [INFO ] potentially running migration '20210202-fix_cascade_for_alias_user_constraint'
2022-05-05T15:54:21.059205149+02:00 [INFO ] no need to migrate '20210202-fix_cascade_for_alias_user_constraint'
2022-05-05T15:54:21.05924913+02:00 [INFO ] potentially running migration '20220403-drop_user_project_idx'
2022-05-05T15:54:21.062063084+02:00 [INFO ] no need to migrate '20220403-drop_user_project_idx'
2022-05-05T15:54:21.077097674+02:00 [ERROR] Error 1069: Too many keys specified; max 64 keys allowed
panic: Error 1069: Too many keys specified; max 64 keys allowed

with the following stack backtrace
goroutine 1 [running]:
github.com/emvi/logbuch.(*StandardFormatter).Pnc(0x40000a0000?, {0x4000126640?, 0x4000126640?}, {0x0?, 0x0?, 0x0?})
	/home/joerg/go/pkg/mod/github.com/emvi/logbuch@v1.2.0/standard_formatter.go:57 +0x44
github.com/emvi/logbuch.(*Logger).Fatal(0x40000a0000, {0x4000126640, 0x38}, {0x0, 0x0, 0x0})
	/home/joerg/go/pkg/mod/github.com/emvi/logbuch@v1.2.0/logger.go:132 +0x78
github.com/emvi/logbuch.Fatal(...)
	/home/joerg/go/pkg/mod/github.com/emvi/logbuch@v1.2.0/funcs.go:55
github.com/muety/wakapi/migrations.RunSchemaMigrations(0x0?, 0x0?)
	/home/joerg/prod/wakapi/migrations/migrations.go:39 +0x84
github.com/muety/wakapi/migrations.Run(0x40000eaea0?, 0x2?)
	/home/joerg/prod/wakapi/migrations/migrations.go:33 +0x34
main.main()
	/home/joerg/prod/wakapi/main.go:142 +0x59c

Seems like this is again mariadb related.
System information

Wakapi version: 2.3.4
Operating system: Debian aarch64 (latest stable)
Database:  mariadb 10.5.15

Hi, I've been using 2.3.4 since it released and didn't have any problems up until I restarted the server yesterday. MariaDB didn't update either so I'm not sure what could have caused it.
I ran the following bash command
for i in aliases diagnostics heartbeats key_string_values language_mappings project_labels summaries summary_items users; do echo "use wakapi; show create table $i" | sudo mariadb > $i.txt; done

and uploaded the outputs here, I hope the formatting isn't too bad :D. I suppose something has gone wrong with the users table.

Thanks for your support with this! Might be a bug with GORM's MySQL driver. I opened https://github.com/go-gorm/mysql/issues/74 in the upstream repo. In the meanwhile, the only workaround I can think of is manually dropping the duplicate keys:
alter table users drop index api_key_2;

Did some more digging. See https://github.com/go-gorm/gorm/issues/5324. A quick workaround would be to add default:NULL to the gorm field tag here.

@muety could this be released in a patch release? I am also running into this issue as well. Thanks for all your work!

Sorry, release is out now!


Wind-Generator added

Title and Issue number

I have added the wind generator.
Close #3528

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

@MohitGupta121 ,@TusharKesarwani Can it be merged now?


How is this used?

I can't get this to work
var BM25 = require("okapibm25").BM25;
var documents = [
    "place",
    "documents",
    "here",
    "Each test document will be searched with the keywords specified below.",
];
var query = ["keywords", "of", "your", "query."];
// A numerical scoring will be returned.
var result = BM25(documents, query, { k1: 1.3, b: 0.9 });
console.log(result);

====
var result = BM25(documents, query, { k1: 1.3, b: 0.9 });
             ^

TypeError: BM25 is not a function

Hey @atorsvn. Thanks for contacting me. As this is a Typescript library, you cannot use okapibm25 out-of-the-box.
You need to do one of the following:
1) Typescript Approach

Install Typescript via npm install --save-dev typescript
Create a typescript file

// index.ts
import BM25 from "okapibm25";
const documents = [
  "place",
  "documents",
  "here",
  "Each test document will be searched with the keywords specified below.",
];
const query = ["keywords", "of", "your", "query."];
// A numerical scoring will be returned.
const result = BM25(documents, query, { k1: 1.3, b: 0.9 });
console.log(result);

Next, compile and run:
npx ts-node index.ts
You should get the following output:
[ 0, 0, 0, 0.5760464234664954 ]

2) Node.js experimental module support

Ensure you have an up-to-date Node.js version.
Create a .mjs file:

// index.mjs
import BM25 from "okapibm25";

const documents = [
  "place",
  "documents",
  "here",
  "Each test document will be searched with the keywords specified below.",
];
const query = ["keywords", "of", "your", "query."];
// A numerical scoring will be returned.
const result = BM25(documents, query, { k1: 1.3, b: 0.9 });
console.log(result);

Run the module using this node --experimental-modules index.mjs
Other options
3) Use esm
4) Use babel
I'm not very well-versed on these options, but see the following issue for examples.

Of course, you could always just download the compiled javascript from this repository and use it locally.

Please forgive m y ignorance, I'm fairly new to much of this. Which files
specifically are the compiled JS?
On Tue, Aug 24, 2021 at 1:56 PM FurkanToprak @.***>
wrote:

Of course, you could always just download the compiled javascript from
this repository and use it locally.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FurkanToprak/OkapiBM25/issues/5#issuecomment-904854814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASSLWKPPYETKKI2AFOZRUSDT6PMNHANCNFSM5CXGGZJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

I'm trying to use this in a discord bot for GPT contextual calibration as to grab relevant data to be used as a context suggestion in a prompt. I've done it with the python rank_bm25 and this looks similar.  If I can get it down to a simple javascript function call that would be fabulous.

Hey @atorsvn it sounds like you have a large-ish project on your hands.
My preference: Typescript + npm
So that your project is as simple as possible, I recommend you follow the steps for Typescript and use npm to initialize a project and install the package. It might look a little daunting at first, but it's very similar to python and pip.  This will also allow you to use many libraries.
Your preference: Regarding compiled JS
The compiled JS doesn't exist anymore (sorry, I forgot about this). Instead, if you want to use the existing code, the easiest thing for you to do would probably be to copy BM25.ts, rename it to BM25.js, and remove all of the Typescript annotations (all of the parameter types and return types).
If you don't want to manually convert the typescript, you can compile the ts to js file using tsc. Learn more here
Again, this is not my preferred approach and I recommend you overcome the learning curve and follow the first step. I'm happy to keep providing support, but this really comes down to personal preference.

Thanks for the tip!
On Tue, Aug 24, 2021 at 2:37 PM FurkanToprak @.***>
wrote:

Hey @atorsvn https://github.com/atorsvn it sounds like you have a
large-ish project on your hands.
My preference: Typescript + npm
So that your project is as simple as possible, I recommend you follow the
steps for Typescript and use npm to initialize a project and install the
package. It might look a little daunting at first, but it's very similar to
python and pip. This will also allow you to use many libraries.
Your preference: Regarding compiled JS
The compiled JS doesn't exist anymore (sorry, I forgot about this).
Instead, if you want to use the existing code, the easiest thing for you to
do would probably be to copy BM25.ts, rename it to BM25.js, and remove
all of the Typescript annotations (all of the parameter types and return
types).
If you don't want to manually convert the typescript, you can compile the
ts to js file using tsc. Learn more here
https://www.typescriptlang.org/docs/handbook/compiler-options.html
Again, this is not my preferred approach and I recommend you overcome the
learning curve and follow the first step. I'm happy to keep providing
support, but this really comes down to personal preference.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FurkanToprak/OkapiBM25/issues/5#issuecomment-904880960,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASSLWKLLK7A6YZH3NL52KILT6PRE7ANCNFSM5CXGGZJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Project isn't actually very big btw. Just a hobby and so far this is the
only thing that works to keep GPT from becoming divergent.
On Tue, Aug 24, 2021 at 2:48 PM עינ הרע @.***>
wrote:

Thanks for the tip!
On Tue, Aug 24, 2021 at 2:37 PM FurkanToprak @.***>
wrote:

Hey @atorsvn https://github.com/atorsvn it sounds like you have a
large-ish project on your hands.
My preference: Typescript + npm
So that your project is as simple as possible, I recommend you follow the
steps for Typescript and use npm to initialize a project and install the
package. It might look a little daunting at first, but it's very similar to
python and pip. This will also allow you to use many libraries.
Your preference: Regarding compiled JS
The compiled JS doesn't exist anymore (sorry, I forgot about this).
Instead, if you want to use the existing code, the easiest thing for you to
do would probably be to copy BM25.ts, rename it to BM25.js, and remove
all of the Typescript annotations (all of the parameter types and return
types).
If you don't want to manually convert the typescript, you can compile the
ts to js file using tsc. Learn more here
https://www.typescriptlang.org/docs/handbook/compiler-options.html
Again, this is not my preferred approach and I recommend you overcome the
learning curve and follow the first step. I'm happy to keep providing
support, but this really comes down to personal preference.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FurkanToprak/OkapiBM25/issues/5#issuecomment-904880960,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASSLWKLLK7A6YZH3NL52KILT6PRE7ANCNFSM5CXGGZJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Good luck!

var BM25 = require("okapibm25").default; // This has to be .default
var documents = [
"place",
"documents",
"here",
"Each test document will be searched with the keywords specified below."
,
];
var query = ["keywords", "of", "your", "query."];
// A numerical scoring will be returned.
var result = BM25(documents, query, { k1: 1.3, b: 0.9 });
console.log(result);
On Tue, Aug 24, 2021 at 3:52 PM FurkanToprak @.***>
wrote:

Closed #5 https://github.com/FurkanToprak/OkapiBM25/issues/5.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FurkanToprak/OkapiBM25/issues/5#event-5202709591, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASSLWKIS45C6QP45FSHJOH3T6PZ7TANCNFSM5CXGGZJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


Add (competitive) season

Adds season to competitiveStats (with typing int|null) to provide information of which season the stats are from.

Personally I'd like to instead move this under competitiveStats instead (as competitiveStats.season) since it basically describes that part of the response.
But this would mean that instead of a reusable StatsCollection struct I would need to split that into a CompetitiveStatsCollection and QuickPlayStatsCollection and I wasn't sure if that would be acceptable.

Looks good! Thanks :)


fund-contract script returns non-zero exit code under truffle exec even when it succeeds

When running ./scripts/fund-contract.js using truffle exec, the transaction is returned to the callback function where an error is supposed to be returned. This means that the script is reporting an error even under successful execution, example:
/chainlink # truffle exec scripts/fund-contract.js --network cldev
Using network 'cldev'.

Funding contract: 0xa8B323695d987DdE23F63e6B4500FBc84Cd3cd4e
0x3d210eb43710fe4d777a08d871bde9f7bf63b95014c346275a1d203693f2afd9
Truffle v5.2.3 (core: 5.2.3)
Node v10.24.0
/chainlink # echo $?
1

Line 20 here: https://github.com/smartcontractkit/box/blob/master/scripts/fund-contract.js#L20 uses the callback function to return a transaction ID, although according to https://www.trufflesuite.com/docs/truffle/getting-started/writing-external-scripts this should be used for error reporting

Hmmm. Sounds like you're suggesting an if statement in there instead of just reporting the transaction receipt?

Going to close for now


algorithm.eval() vs. algorithm.model.eval()

Hi,
Really nice job with this repo! I had a small comment on the use of algorithm.eval() vs. algorithm.model.eval() in the wilds/examples/train.py file that might be useful to others.
I wasn't able to find this in the code, but how does algorithm.eval() differ from algorithm.model.eval()?
I ask because algorithm.model.eval() preserves the grad_fn attribute on the model output, while algorithm.eval() does not.  This was unexpected behavior since pytorch's .eval() function doesn't do this. This is important for my use case, since I'm trying to evaluate the gradients when the model is in eval mode. If this does not break behavior elsewhere, I'd suggest switching to algorithm.model.eval().
Happy to explain more if this was confusing!

Thank you Divya!
The relevant code is here, and another relevant thing to note is that nn.Module.eval() is equivalent to nn.Module.train(False) as described here. Sorry this is confusing and inconsistent with the expected behavior in torch. We'll look into updating this in our future release! For now, I think you should be able to work around it by setting the grad_enabled flag manually or removing the relevant line in code.

That makes sense! Yeah, simple to workaround, thanks for the quick response 🎉


No such file 'ph:// ......'

For my part, I solved my problem. This was that the uri was not valid when converting images to base64. I solved it as follows:
let imagePATH = null;
if(Platform.OS === 'ios'){
let regex = /://(.{36})//i;
let result = uriPhoto.match(regex);
let photoPATH = assets-library://asset/asset.JPG?id=${result[1]}&ext=JPG;
  const dest = `${RNFS.TemporaryDirectoryPath}${Math.random().toString(36).substring(7)}.jpg`;

  imagePATH = await RNFS.copyAssetsFileIOS(photoPATH, dest, 500, 500, 1.0, 1.0, 'contain');
}
else if(Platform.OS === 'android'){
  imagePATH = photo;
}

const photoBase64 = await RNFS.readFile(imagePATH, 'base64');

if (Platform.OS === 'ios') {
let arr = fileUri.split('/')
const dirs = RNFetchBlob.fs.dirs
filePath = ${dirs.DocumentDir}/${arr[arr.length - 1]}
} else {
filePath = audioDataUri
}


👷  (gh-actions) attempt to cache playwright installs [b]

~7m (12.x) => ~13m (13.x) => turned off => ~5m => ~3m => 1m35s

Going to turn back on :100:
Nice, last one was ~50s of course I am sure upstash will now complain we are using the thing you pay for 😑

This pull request has been deployed to Vercel.

Latest commit:
f0958dd

✅ Preview:
https://jeromefitzgerald-ng9nsobrr-jerome5.vercel.app

🔍 Inspect:
https://vercel.com/jerome/jeromefitzgerald/B37kDmWVsJ8FR51dXMWDKEzDxSYv

View Workflow Logs


The documentation online page of incflo was missing

The site https://amrex-codes.github.io/incflo/docs_html/ is not working properly.

Could you please fix it? Compiling on my local host is sometimes not convenient.

Thanks for reporting the issue. It should be fixed now.

Note that the new URL is https://amrex-fluids.github.io/incflo/docs_html/.

Thanks. Now it works.


add binaries download for windows 10/11

add binaries download for windows 10/11

They're available under releases
vegeta_12.11.1_windows_amd64.zip


Saving multiple raw text files vs. saving one raw text database for all files scanned

A choice has to be made between saving multiple raw text files to search from vs. making one text file.
It should make no difference, as each page from each pdf file is saved as a jsonl entry.
Eg:
{"filename": "./path/to/file.pdf", "pageNum": 1, "text": ["text chunk 1\n", "text chunk 2"... }

currently implementing search to use filename from the loaded json to get filenames, so later either method will be fine

Now, the program uses an individual jsonl file for each pdf.
later, this can be changed to a single jsonl.
later, a hash can be added to ensure if it's the same file or not.
eg:
{'filename' :
    {'filehash': AB923SNJ,
     'pgs':{ 0 : ["text chunk 1\n", "text chunk 2"... ],
             1 : ["text chunk 1\n", "text chunk 2"... ] ... } } }

this also means cleanup routines will need to be added to remove files that are no longer around.

Now the program only uses one file named files/jarPhysDB.jsonl, as specified above.
Resolved


chore(loader-list): added angular2-template-loader

Not sure if this order is generated before or after.

LGTM. Feel free to merge.


Complete Edition & Core Edition

X-Friese
I wonder if the source is Complete Edition & Core Edition ?
if it's Core Edition ? how to get Complete Edition source?

This  is a combined source code. A compiler flag makes it complete or core.

No longer relevant since we now only have FlyWithLua NG.


[Device Specific] “Please buy and sell responsibly”  walkthrough screen’s description overlaps on Carousel from CELO walkthrough screens.

Frequency: 100%
Repro on build version: Play Store build V1.12.2
Does not repro version App store build V1.12.2
Repro on devices:  LG K7i(6.0)
Does not repro devices Samsung Galaxy S4(4.4.2), HTC Desire 526G+ (4.4.2) , samsung galaxy S4(5.0.1), Samsung Galaxy A5(7.0), Samsung Galaxy M31 (10.0),  iPhone XR (14.4.1), iPhone 6+ (12)
Tested Account:<PHONE_NUMBER> / Backup Key
Repro Steps:

Launch the application and login with a test account.
Tap on the Hamburger menu.
Now tap on the CELO option.
Now users should be able to see walkthrough screens.
Now start swiping on the LHS side until the “Please buy and sell responsibly” walkthrough screen display.
Observed that,

Current Behavior:  Description of walkthrough screen overlaps on Carousel.
Expected Behavior:  Description should not overlap on Carousel.
Impact: Bad user experience.
Attachment: CouroselOverplapsOn4thWalkthrough.mp4

https://valora.testquality.com requirement R72.

Hi @MuckT We have verified this issue on Latest Android internal build V1.17.0 & Test flight build V1.17.0 and updated the status in test quality tool.
Test quality tool link:

Android:
- https://valora.testquality.com/project/12128/plan/21240/run/149557/result/2450228

iOS:
- https://valora.testquality.com/project/12128/plan/21240/run/149557/result/2450219

Verified On Devices: iPhone SE (14.2), Samsung Galaxy S4 (4.4.2),


Change deprecated logseq.App.showMsg

logseq.App.showMsg is deprecated in the logseq API, so I've changed the use of logseq.App.showMsg to logseq.UI.showMsg.

@haydenull I forked the repository to remove the Commit & Push from being an error message, but I've found that you fixed that three days ago! Thank you!
While I had the fork open, I went ahead and updated the showMsg calls.
Your plugin has been really helpful, and I'm really happy with it now that I no longer get error for no changes 😄


[SPARK-36401][PYTHON] Implement Series.cov

What changes were proposed in this pull request?

Implement Series.cov
Why are the changes needed?

That is supported in pandas. We should support that as well.
Does this PR introduce any user-facing change?

Yes. Series.cov can be used.
>>> from pyspark.pandas.config import set_option, reset_option
>>> set_option("compute.ops_on_diff_frames", True)
>>> s1 = ps.Series([0.90010907, 0.13484424, 0.62036035])
>>> s2 = ps.Series([0.12528585, 0.26962463, 0.51111198])
>>> s1.cov(s2)
-0.016857626527158744
>>> reset_option("compute.ops_on_diff_frames")

How was this patch tested?

Unit tests

Can one of the admins verify this patch?

cc @xinrong-databricks @itholic FYI

Thanks @itholic , I resolved your reviews except one. Could you please review it again?

Would you add entry in python/docs/source/reference/pyspark.pandas/series.rst?

Could you please re-review, is it ready to merge ?  @srowen @itholic @xinrong-databricks

ok to test

Test build #142929 has started for PR 33752 at commit e0a8fe6.

Test build #142929 has finished for PR 33752 at commit e0a8fe6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142929/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47431/

Test build #142946 has started for PR 33752 at commit 74f354a.

Test build #142946 has finished for PR 33752 at commit 74f354a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142946/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47447/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47447/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47447/

Thanks! merging to master.


dist/index.js has not been built since fix

Can you please build and push?

Done! Sorry for the delay!


A parameter cannot be found that matches parameter name: OsVhdUri

Hi, i am having trouble on the Managed Image Generation job.
The machine builds successfully but it looks like the OsVhdUri is not being outputted so the variable isn't being passed into the create-managedimage.ps1 script.
I am building this with an Azure Hosted VM and trying to build 2022-Datacenter.
Error in question is:
D:\a\1\a\VMSSFiles\Scripts\Setup\create-managedimage.ps1 : A parameter cannot be found that matches parameter name
'OsVhdUri'.
At D:\a\_temp\fe1cd036-928c-4234dc-86e7-33dsrf344a3dc1.ps1:4 char:426
+ ... 5c28 ` -Location UKSOUTH ` -ImageType windows2022 ` -OsVhdUri  ` -OsT ...
+                                                         ~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [create-managedimage.ps1], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : NamedParameterNotFound,create-managedimage.ps1

Any assistance on this would be super.  I have tried to debug this for a good couple of days now but ran out of ideas.  Thanks
Oh, also, i don't know if it's worth mentioning but i am not importing the runner-images.  I am using Azures image.  Could this be the problem?  This is my packer build file.
{
    "builders": [{
      "type": "azure-arm",

      "client_id": "[client_id]",
      "client_secret": "[client_secret]",
      "tenant_id": "[tenant]",
      "subscription_id": "[sub]",

      "managed_image_resource_group_name": "rg-packer-test",
      "managed_image_name": "myPackerImage",

      "os_type": "Windows",
      "image_publisher": "MicrosoftWindowsServer",
      "image_offer": "WindowsServer",
      "image_sku": "2022-Datacenter",

      "communicator": "winrm",
      "winrm_use_ssl": true,
      "winrm_insecure": true,
      "winrm_timeout": "10m",
      "winrm_username": "packer",

      "azure_tags": {
          "dept": "Cloud",
          "task": "Image deployment"
      },

      "build_resource_group_name": "rg-packerbuild-test",
      "vm_size": "Standard_D2_v2"
    }],
    "provisioners": [
        {
        "type": "powershell",
        "scripts": [
            "{{ template_dir }}/scripts/installers/Install-AzureCli.ps1"
        ]
    },
      {
      "type": "powershell",
      "inline": [
        "& $env:SystemRoot\\System32\\Sysprep\\Sysprep.exe /oobe /generalize /quiet /quit",
        "while($true) { $imageState = Get-ItemProperty HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Setup\\State | Select ImageState; if($imageState.ImageState -ne 'IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE') { Write-Output $imageState.ImageState; Start-Sleep -s 10  } else { break } }"
      ]
    }
  ]
  }

You aren't using my setup and it doesn't work? That looks to be the problem, I'm afraid. I have created 3 new VM's today, the current version of my repo works...
Some things to look at:

From the looks of your packer file, you are directly creating a Managed Image. You do not need the create-managedimage.ps1.
You also can't use it, because it expects the .vhd uri as an input and you don't get that because you have a managed image already
The output of the OsDiskUri value is done in PowerShell, by reading the output of the packer command: https://github.com/YannickRe/azuredevops-buildagents/blob/b940b59ed2533d61c8453a4ad0952608aeefc209/scripts/build-image.ps1#L63
Again, since you do not have a VHD, most likely the packer command isn't outputting this value

That's all I can help with when you aren't using the runner-images repository, as this whole setup is based on that.


[music] Add a queue

Add a song queue. Requested songs get put at the end of the queue and are played automatically. Commands for skipping current song, shuffle, clearing the queue etc.

Simple Queue implemented with 2c86ceb. Still need to add commands for handling the queue (e.g. skip, list queue, remove song etc.)


feat(@tinacms/field): Adds new CheckboxGroup Field

Adds support for component: checkbox-group to Tina Forms.
CheckboxGroupField is an array of options that allow for multiple values (as opposed to Select or RadioGroup which only allows for a single value from options).
On submission, CheckboxGroupField submits as an array of each checked option.

Closes #1866

We're ignoring danger fails on anything related to add-pnp-2 for right now, so going to disregard the errors here.