pydk-build-droid failed

cp: '../3dscrabble.app/assets/.' and './assets/.' are the same file
cp: cannot stat '/home/osboxes/Desktop/Code/pydk/wapy-lib/pythons': No such file or directory
 * Removing old builds
pydk-build-droid.sh: line 151: ./gradlew: No such file or directory
pydk-build-droid.sh: line 274: ./gradlew: No such file or directory

Folders were named wrong.


Rename kibana substrings with OpenSearchDashboards in class name, method name and comments

opendistro-for-elasticsearch/security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)
Maintenance

Github Issue # or road-map entry, if available:

Description of changes:
Rename kibana substrings with OpenSearchDashboards  in class name, method name and comments

Why these changes are required?
OpenSearch migration

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)
No changes in behavior

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)
UT

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I found that there are some kibana keywords in loggers, should we rename that in this PR?
e.g. PrivilegesInterceptorImpl.java  line 194, 206

I found that there are some kibana keywords in loggers, should we rename that in this PR?
e.g. PrivilegesInterceptorImpl.java line 194, 206

The plan for these changes will be discussed for indices migration.

@cliu123 Code becomes less readable. For example naming variable that gets "kibana_url" settings as openSearchDashboardsRootUrl makes code less readable.

Changed it back. It'll be renamed in one of the PRs following.


Bug: When switching the layout type in NavigationController to NavBarNone, the settings flyout was not closed

Fixed by d437db8 commit

Fixed by d437db8 commit


[FarmHouseDataModifier] TVs spawned with FarmHouseFurniture are dressers

I need to fix it so that TVs are spawned by creating a new TV object. Should be dynamic, so that it works for all maps and cabins as well as auto-detecting TVs in the FarmHouseFurniture property.

Fixed by 481764b9f31f530fc7e231c01db2c0e9977adcb2.


Change standard function property to External

In build 13.0.22621.0-nl, we need to change the function 'CalcLineTotal' property to External so it can be used in extension.
In page VAT Statement Preview line we have this piece of code:

In our solution we put some logic to OnDrillDown trigger, to migrate this we had to overwrite the variable 'ColumnValue' and calculate it again. To make this possible we should change the function property to external (CalcLineTotal from Report 12 VAT Statement).
Please change the property in the next build so we can use it in extensions.
Thank,
Daniel Balan

Will be done :-) Thanks for reporting!


Firefox 68.4.1esr

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This adds 68.4.1esr on account of this announcement. Also adds the recently-added MOZILLA license family. Hooray!
I guess this should target/become a (new) 68esr branch instead of master? On account of this request, I also volunteered myself as tribute to help maintain: 68 will continue to receive updates until August 2020, and has a lot of value to me for testing purposes.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

target/become a (new) 68esr branch instead of master

Actually, it looks like a few more versions dropped recently: perhaps if this can be merged, and have  new branch cut off master, the newer versions can be PRd on top.

Actually, it looks like a few more versions dropped recently: perhaps if this can be merged, and have new branch cut off master, the newer versions can be PRd on top.

Yes!


Implement built-in function "eq?"

Invocation:
>> (eq? a b)
The "eq?" function's semantics works as follows:

Two numerical values (integers. floats, fractions) are considered equal if they have the same value:
>> (eq? 1 1)
=> #t
>> (eq? 1.0 2.0)
=> #f

Two strings are considered equal if they consists of exactly the same character sequence:
>> (eq? "test" "test")
=> #t
>> (eq? "first" "second")
=> #f

Two lists objects must refer to exactly the same list in order to be considered equal:
>> (define a (cons 1 (cons 2 ()))
>> (define b (cons 1 (cons 2 ()))
>> (eq? a b)
=> #f
>> (eq? a a)
=> #t

Implementation has been finished with commit 70c14b7ba28ff698e6700cacdb2c10173b98cca6


Add support for the Keycloak provider

Upstream Pulumi does support Keycloak, so would there be a chance to get a Kotlin "wrapper" here, too?

That was quick, thank you @jplewa!

@sschuberth Happy to help! It's not released yet, though, I'll ping you when it becomes available in Maven Central :)

@sschuberth Looks like it's been indexed already: https://central.sonatype.com/artifact/org.virtuslab/pulumi-keycloak-kotlin. Let me know if you get a chance to try it out :)

@sschuberth Looks like it's been indexed already: https://central.sonatype.com/artifact/org.virtuslab/pulumi-keycloak-kotlin. Let me know if you get a chance to try it out :)

I will! Tough it could take some time, as we're very new to any IaC solution...


Could not use the Square tool with Wireframe

Of

Fill Areas
￼
No Fill (Wireframe)
￼
Partial Fill
￼
Full Fill

I could not use the Square tool with Wireframe. In fact there is no way to get to the right click menu.
Its shortcut (Q) still worked though.

While in partial or full fill mode, it doesn't matter if you're clicking inside a building or on the building's way. Wireframe mode is a bit different, it's no longer possible to click inside the building - you need to right click, well, on the "wire" (or the building's way in this case). iD will highlight the object in red for you. This is a visual indication that you can use right click now.

@jidanni Yes, see @mmd-osm's answer. Since the fill is hidden in wireframe mode, you have to access the menu by right-clicking on the perimeter or pressing spacebar. A future version of iD will also show the Square tool in the toolbar when a feature is selected so you don't need to right-click.


Are you going to support openai proxy?

Example:
export OPENAI_PROXY="http://<IP_ADDRESS>:7890"

Thank you!
Please refer to https://github.com/OpenBMB/ChatDev/issues/6#issuecomment-1704670499


Error when running Azure DevOps pipeline on Windows Agent

I'm getting a [error]spawn devcontainer ENOENT message whenever I try and run a simple pipeline on an Azure DevOps agent running Windows 10. I've tried running the command the logs indicate it's attempting to run and they work fine. I'm also just running the agent from the command line so it should have the same environment and permissions that I do.
Here's the azure-pipelines.yml definition:
trigger:
- master

pool:
  name: TestPool

steps:

- task: DevcontainersCi@0
  inputs:
    runCmd: dotnet run

The devcontainer.json
{
	"name": "Debian",
	"image": "mcr.microsoft.com/devcontainers/base:bullseye",
	"features": {
		"ghcr.io/devcontainers/features/dotnet:1": {}
	},
	"extensions": [
		"ms-dotnettools.csharp",
		"ms-azure-devops.azure-pipelines"
	]
}

Log output with system diagnostics enabled
2022-12-04T23:43:58.6616649Z ##[debug]Evaluating condition for step: 'DevcontainersCi'
2022-12-04T23:43:58.6618745Z ##[debug]Evaluating: SucceededNode()
2022-12-04T23:43:58.6619095Z ##[debug]Evaluating SucceededNode:
2022-12-04T23:43:58.6619931Z ##[debug]=> True
2022-12-04T23:43:58.6620334Z ##[debug]Result: True
2022-12-04T23:43:58.6620646Z ##[section]Starting: DevcontainersCi
2022-12-04T23:43:58.6744183Z ==============================================================================
2022-12-04T23:43:58.6744423Z Task         : Devcontainers CI Task
2022-12-04T23:43:58.6744624Z Description  : Build and run Dev Containers (https://containers.dev) in Azure DevOps Pipelines
2022-12-04T23:43:58.6745517Z Version      : 0.2.1900000228
2022-12-04T23:43:58.6745658Z Author       : Devcontainers
2022-12-04T23:43:58.6745771Z Help         :
2022-12-04T23:43:58.6745910Z ==============================================================================
2022-12-04T23:43:58.7206053Z ##[debug]Using node path: c:\agent\externals\node10\bin\node.exe
2022-12-04T23:43:58.9589621Z ##[debug]agent.TempDirectory=c:\agent\_work\_temp
2022-12-04T23:43:58.9614794Z ##[debug]loading inputs and endpoints
2022-12-04T23:43:58.9638250Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2022-12-04T23:43:58.9702163Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2022-12-04T23:43:58.9706222Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2022-12-04T23:43:58.9708706Z ##[debug]loading INPUT_BUILDREASONSFORPUSH
2022-12-04T23:43:58.9710972Z ##[debug]loading INPUT_PUSHONFAILEDBUILD
2022-12-04T23:43:58.9713000Z ##[debug]loading INPUT_RUNCMD
2022-12-04T23:43:58.9715062Z ##[debug]loading INPUT_SKIPCONTAINERUSERIDUPDATE
2022-12-04T23:43:58.9719419Z ##[debug]loading SECRET_SYSTEM_ACCESSTOKEN
2022-12-04T23:43:58.9723583Z ##[debug]loaded 8
2022-12-04T23:43:58.9728725Z ##[debug]Agent.ProxyUrl=undefined
2022-12-04T23:43:58.9729676Z ##[debug]Agent.CAInfo=undefined
2022-12-04T23:43:58.9730508Z ##[debug]Agent.ClientCert=undefined
2022-12-04T23:43:58.9731379Z ##[debug]Agent.SkipCertValidation=undefined
2022-12-04T23:43:58.9795443Z ##[debug]Agent.Version=2.213.2
2022-12-04T23:43:58.9796620Z ##[debug]set task variable: hasRunMain=true
2022-12-04T23:43:58.9801811Z ##[debug]Processed: ##vso[task.settaskvariable variable=hasRunMain;issecret=false;]true
2022-12-04T23:43:58.9811938Z ##[debug]which 'docker'
2022-12-04T23:43:58.9870089Z ##[debug]found: 'C:\Program Files\Docker\Docker\resources\bin\docker.exe'
2022-12-04T23:43:58.9871911Z ##[debug]C:\Program Files\Docker\Docker\resources\bin\docker.exe arg: ["buildx","--help"]
2022-12-04T23:43:58.9873100Z ##[debug]C:\Program Files\Docker\Docker\resources\bin\docker.exe arg: ["buildx","--help"]
2022-12-04T23:43:58.9875862Z ##[debug]exec tool: C:\Program Files\Docker\Docker\resources\bin\docker.exe
2022-12-04T23:43:58.9876971Z ##[debug]exec tool: C:\Program Files\Docker\Docker\resources\bin\docker.exe
2022-12-04T23:43:58.9877843Z ##[debug]arguments:
2022-12-04T23:43:58.9878646Z ##[debug]arguments:
2022-12-04T23:43:58.9879395Z ##[debug]   buildx
2022-12-04T23:43:58.9880116Z ##[debug]   buildx
2022-12-04T23:43:58.9880831Z ##[debug]   --help
2022-12-04T23:43:58.9881533Z ##[debug]   --help
2022-12-04T23:43:59.2811989Z ##[debug]Exit code 0 received from tool 'C:\Program Files\Docker\Docker\resources\bin\docker.exe'
2022-12-04T23:43:59.2813957Z ##[debug]Exit code 0 received from tool 'C:\Program Files\Docker\Docker\resources\bin\docker.exe'
2022-12-04T23:43:59.2815641Z ##[debug]STDIO streams have closed for tool 'C:\Program Files\Docker\Docker\resources\bin\docker.exe'
2022-12-04T23:43:59.2817559Z ##[debug]STDIO streams have closed for tool 'C:\Program Files\Docker\Docker\resources\bin\docker.exe'
2022-12-04T23:43:59.2830499Z ##[debug]which 'devcontainer'
2022-12-04T23:43:59.2889774Z ##[debug]found: 'C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd'
2022-12-04T23:43:59.2891006Z ##[debug]C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd arg: ["--help"]
2022-12-04T23:43:59.2891833Z ##[debug]C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd arg: ["--help"]
2022-12-04T23:43:59.2895175Z ##[debug]exec tool: C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd
2022-12-04T23:43:59.2896007Z ##[debug]exec tool: C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd
2022-12-04T23:43:59.2896810Z ##[debug]arguments:
2022-12-04T23:43:59.2897470Z ##[debug]arguments:
2022-12-04T23:43:59.2898123Z ##[debug]   --help
2022-12-04T23:43:59.2898796Z ##[debug]   --help
2022-12-04T23:43:59.5888840Z ##[debug]Exit code 0 received from tool 'C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd'
2022-12-04T23:43:59.5933619Z ##[debug]Exit code 0 received from tool 'C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd'
2022-12-04T23:43:59.5957376Z ##[debug]STDIO streams have closed for tool 'C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd'
2022-12-04T23:43:59.5996612Z ##[debug]STDIO streams have closed for tool 'C:\Users\jesse\AppData\Roaming\npm\devcontainer.cmd'
2022-12-04T23:43:59.6024187Z ##[debug]checkoutPath=undefined
2022-12-04T23:43:59.6049989Z ##[debug]imageName=undefined
2022-12-04T23:43:59.6077870Z ##[debug]imageTag=undefined
2022-12-04T23:43:59.6081478Z ##[debug]platform=undefined
2022-12-04T23:43:59.6095495Z ##[debug]subFolder=undefined
2022-12-04T23:43:59.6100964Z ##[debug]runCmd=dotnet run
2022-12-04T23:43:59.6106129Z ##[debug]env=undefined
2022-12-04T23:43:59.6106758Z ##[debug]cacheFrom=undefined
2022-12-04T23:43:59.6107688Z ##[debug]skipContainerUserIdUpdate=false
2022-12-04T23:43:59.6108585Z !! imageTag specified without specifying imageName - ignoring imageTag
2022-12-04T23:43:59.6108951Z
2022-12-04T23:43:59.6109169Z
2022-12-04T23:43:59.6109360Z
2022-12-04T23:43:59.6109668Z ***
2022-12-04T23:43:59.6110022Z *** Building the dev container
2022-12-04T23:43:59.6110363Z ***
2022-12-04T23:43:59.6110801Z About to run devcontainer build --workspace-folder c:\agent\_work\1\s
2022-12-04T23:43:59.6111618Z ##[debug]task result: Failed
2022-12-04T23:43:59.6139575Z ##[error]spawn devcontainer ENOENT
2022-12-04T23:43:59.6149241Z ##[debug]Processed: ##vso[task.issue type=error;]spawn devcontainer ENOENT
2022-12-04T23:43:59.6158491Z ##[debug]Processed: ##vso[task.complete result=Failed;]spawn devcontainer ENOENT
2022-12-04T23:43:59.6217040Z ##[section]Finishing: DevcontainersCi

At the time I put this issue in, I was helping a client whose IT department's policy only allowed for Windows based machines to be deployed on their network. The testing I did was on a Windows 10 VM in Azure.


web版本编译报错

浏览器：edge最新版
DEPTH : 1
Error: Unsupported operation: Platform._operatingSystem
    at Object.throw_ [as throw] (http://localhost:51836/dart_sdk.js:5069:11)
    at Function._operatingSystem (http://localhost:51836/dart_sdk.js:57603:17)
    at Function.get operatingSystem [as operatingSystem] (http://localhost:51836/dart_sdk.js:57649:27)
    at get _operatingSystem (http://localhost:51836/dart_sdk.js:57562:27)
    at Function.desc.get [as _operatingSystem] (http://localhost:51836/dart_sdk.js:5562:17)
    at get isAndroid (http://localhost:51836/dart_sdk.js:57583:26)
    at Function.desc.get [as isAndroid] (http://localhost:51836/dart_sdk.js:5562:17)
    at initPlatform (http://localhost:51836/packages/pikapika/basic/config/Platform.dart.lib.js:16:23)
    at initPlatform.next (<anonymous>)
    at runBody (http://localhost:51836/dart_sdk.js:40646:34)
    at Object._async [as async] (http://localhost:51836/dart_sdk.js:40677:7)
    at Object.initPlatform (http://localhost:51836/packages/pikapika/basic/config/Platform.dart.lib.js:15:18)
    at InitScreen._InitScreenState.new._init (http://localhost:51836/packages/pikapika/screens/InitScreen.dart.lib.js:330:24)
    at _init.next (<anonymous>)
    at runBody (http://localhost:51836/dart_sdk.js:40646:34)
    at Object._async [as async] (http://localhost:51836/dart_sdk.js:40677:7)
    at InitScreen._InitScreenState.new.[_init] (http://localhost:51836/packages/pikapika/screens/InitScreen.dart.lib.js:329:20)
    at InitScreen._InitScreenState.new.initState (http://localhost:51836/packages/pikapika/screens/InitScreen.dart.lib.js:325:18)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52680:54)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.StatelessElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatelessElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatelessElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatelessElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatelessElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatelessElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52706:13)
    at framework.StatefulElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52699:27)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52706:13)
    at framework.StatefulElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52699:27)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatelessElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatelessElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatelessElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatelessElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatelessElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatelessElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52706:13)
    at framework.StatefulElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52699:27)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at _InheritedNotifierElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at _InheritedNotifierElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at _InheritedNotifierElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at _InheritedNotifierElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at _InheritedNotifierElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at _InheritedNotifierElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52706:13)
    at framework.StatefulElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52699:27)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.InheritedElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.InheritedElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.InheritedElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.InheritedElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.InheritedElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.InheritedElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.InheritedElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.InheritedElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.InheritedElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.InheritedElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.InheritedElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.InheritedElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52706:13)
    at framework.StatefulElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52699:27)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatelessElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatelessElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatelessElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatelessElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatelessElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatelessElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatelessElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatelessElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatelessElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatelessElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatelessElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatelessElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at basic._OffstageElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at basic._OffstageElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at basic._OffstageElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.InheritedElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.InheritedElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.InheritedElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.InheritedElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.InheritedElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.InheritedElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.InheritedElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.InheritedElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.InheritedElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.InheritedElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.InheritedElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.InheritedElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52706:13)
    at framework.StatefulElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52699:27)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52706:13)
    at framework.StatefulElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52699:27)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52706:13)
    at framework.StatefulElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.StatefulElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:52699:27)
    at framework.StatefulElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.SingleChildRenderObjectElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.SingleChildRenderObjectElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.SingleChildRenderObjectElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:33631:29)
    at framework.InheritedElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.InheritedElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.InheritedElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.InheritedElement.new.rebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24218:12)
    at framework.InheritedElement.new.[_firstBuild] (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24988:12)
    at framework.InheritedElement.new.mount (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:24984:26)
    at framework.StatefulElement.new.inflateWidget (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23857:16)
    at framework.StatefulElement.new.updateChild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:23710:25)
    at framework.StatefulElement.new.performRebuild (http://localhost:51836/packages/flutter/src/widgets/widget_inspector.dart.lib.js:25021:31)
    at framework.StatefulElement.new.performRebuild
......

golang并不支持web


chore(ci): bump lotus version in devnet check

Summary of changes

I have recently seen quite a few ci failures in the devnet checks job, this PR tries to upgrade lotus to the latest and see if the issue get mitigated (even not we need the upgrade anyway)
Changes introduced in this pull request:

bump lotus version in devnet check CI job

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Could you please elaborate on the errors that you've encountered?

@LesnyRumcajs a few links below
https://github.com/ChainSafe/forest/actions/runs/7527552013/job/20488198997
https://github.com/ChainSafe/forest/actions/runs/7382999656/job/20083619234

@LesnyRumcajs a few links below
https://github.com/ChainSafe/forest/actions/runs/7527552013/job/20488198997 https://github.com/ChainSafe/forest/actions/runs/7382999656/job/20083619234

Thanks. We are missing logs, I'll add them here https://github.com/ChainSafe/forest/pull/3890


GH-1201: Fix for ChannelAwareBatchMessageListener

Resolves https://github.com/spring-projects/spring-amqp/issues/1201
The previous commit did not work with ChannelAwareBatchMessageListener.
Also add a test to get List<o.s.a.c.Message> in a @RabbitListener (which
exposed this issue).
cherry-pick to 2.2.x

... and cherry-picked to 2.2.x


[WIP] Create organisations index page

New route created pointing to new organisations index page. This page displays stubbed organisations.
https://trello.com/c/F3Hx0P7T/28-create-organisations-index-page

Closing as will be superseded by another PR


Feature request - Set client wifi config without restarting

Hi!
First of, Thank you all for the awesome set of esp related crates :)

I am trying to setup a device for the following scenario.

Device is not configured, start in AP-mode (likely Mixed to allow scanning)
The user connects to the AP using a phone or similar and in a web interface hosted by the device configure what Wifi the device should be connected to (need ability to scan)
The device tries to connect to the selected network (while maintaining connection to the phone through the AP)
If step 3 succeeded, turn of AP. Otherwise maintain connection with phone and allow for another try

First off, is this a scenario that should be supported by esp-idf-svc/embedded-svc?
Looking at the code I have stumbled upon some questions:

Wifi::scan() restarts the wifi? Does it have to do that? or could something like fn scan_with_optional_restart(restart: bool) be exposed?
Wifi::set_configuration(wifi::Configuration::Mixed()) can not start without a client config (can not scan in Ap-mode)
Calling EspWifi::set_configuration(wifi::Configuration::Mixed(Default::default(), ap_config)) fails with ESP-IDF ERROR: ESP_ERR_WIFI_SSID

I tried these changes and they seem to make make it possible to use EspWifi::set_configuration(wifi::Configuration::Mixed(Default::default(), ap_config)) to enter Mixed (and probably Client) without specifying client settings:
    fn set_client_conf(&mut self, conf: &ClientConfiguration) -> Result<(), EspError> {
         info!("Setting STA configuration: {:?}", conf);

-        let mut wifi_config = wifi_config_t {
-            sta: Newtype::<wifi_sta_config_t>::from(conf).0,
+        let mut wifi_config = if conf.ssid.is_empty() {
+            // Empty config
+            unsafe { core::mem::zeroed() }
+        } else {
+            wifi_config_t {
+                sta: Newtype::<wifi_sta_config_t>::from(conf).0,
+            }
         };

         esp!(unsafe { esp_wifi_set_config(wifi_interface_t_WIFI_IF_STA, &mut wifi_config) })?;

-        self.set_client_ip_conf(&conf.ip_conf)?;
+        if !conf.ssid.is_empty() {
+            self.set_client_ip_conf(&conf.ip_conf)?;
+        }

         info!("STA configuration done");

Also, would there be any way to expose some way to change client settings without affecting the Ap connection? Perhaps something like(pseudo code)
pub fn foo(&mut self, conf: &ClientConfiguration) -> Result<(), ErrorNotInMixedOrClientMode | EspError> {
    if not in Mixed or Client mode {
        return Err(ErrorNotInMixedOrClientMode);
    }
    wifi.set_client_conf(conf);
    if conf.ssid.is_empty() {
        status.client_status = Stopped;
    } else {
        status.client_status = Started;
    }
}

Please let me know if you would like me to split this into multiple issues and if you would be interested in a PR

I don't think step 3 is possible. Mixed mode (AP + STA) does require that both AP and STA are running on the same Wifi channel, because the esp32 has a single radio. However, when setting up the AP, you cannot know upfront what Wifi parameters the user would configure for the STA mode, so that you can configure the AP on the same channel.

Oh, that does make sense. Thank you for the clarification :) .
So I would have to do something more like(changed text in bold):

Device is not configured, start in AP-mode (likely Mixed to allow scanning)
The user connects to the AP using a phone or similar and in a web interface hosted by the device configure what Wifi the device should be connected to (need ability to scan)
The device tries to connect to the selected network (by wifi.set_configuration(Mixed(...)), restarting the wifi closing the connection to the browser)
During this time the browser polls the esp for a status of how the connection went(and the phone will most likely reconnect to the ap after restart)
If step 3 succeeded, turn off AP. Otherwise maintain connection with phone and allow for another try

However it would still be possible to perform a scan without restarting the Wifi right? It does at least seem to work in my tests with #76 combined with the above proposed if conf.ssid.is_empty(){ empty config }..
Again, thank you

Should now be fixed.


docker install fails

Successfully built 39e3237514cf
Successfully tagged tutorialcrab_client:latest
docker-compose stop mdb
Stopping tutorialcrab_mdb_1 ... done
docker-compose rm -f mdb
Going to remove tutorialcrab_mdb_1
Removing tutorialcrab_mdb_1 ... done
docker-compose up -d mdb
Creating tutorialcrab_mdb_1 ... done
sleep 10
process_begin: CreateProcess(NULL, sleep 10, ...) failed.
make (e=2): The system cannot find the file specified.
make: *** [reinit_db] Error 2
C:\Dev\bigchaindb\tutorial-crab>docker-compose ps
Name                     Command               State            Ports
tutorialcrab_mdb_1   docker-entrypoint.sh mongo ...   Up      <IP_ADDRESS>:32769->27017/tcp
C:\Dev\bigchaindb\tutorial-crab>

issue with make in windows that does not jump around makefile, need to run commands by hand


Don't see git push terminal quickfix

Testing #167475

Open GH repo in VS Code Insiders
Create new branch off main
Make and commit a change in new branch
I thought I followed the steps shown in docs that'd produce a quick fix, but I'm not seeing one:

I assume I'm missing something obvious, but I can't seem to figure it out from experimentation and reviewing docs.

@bamurtaugh I think you have shell integration disabled as I don't see the circles to the left?

or it failed to activate for some reason - can you hover the tab @bamurtaugh ?

I just took the manual steps to enable shell integration in my PowerShell profile, and when I hover over the terminal tab, I see it says shell integration activated:

I tried the same steps but nothing seems to have changed:

I realize the manual PowerShell configuration (shown below) uses vscode and code - should I update to code-insiders?
if ($env:TERM_PROGRAM -eq "vscode") { . "$(code --locate-shell-integration-path pwsh)" }

I tried changing the latter code to code-insiders but didn't see a difference.

what is your powershell profile @bamurtaugh ?

I have the same issue on Ubuntu 16 with bash:

From running code-insiders $Profile, the C:\Users\brmurtau\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 file opens, and it is empty. I tried adding the manual installation line and reloading, but no change, so I've now removed it again.
I just closed all my terminals and reloaded VS Code one more time, and now when I hover over the Powershell tab, I don't see a mention of shell integration:

I tried pasting in the manual install line, and then I got the following in a terminal, which I think makes sense since I only have Insiders installed:

I updated the install line to mention code-insiders (if ($env:TERM_PROGRAM -eq "vscode") { . "$(code-insiders --locate-shell-integration-path pwsh)" }), closed the terminal, reloaded VS Code, and now I see the integration failed to activate:

here are the profiles I meant above... you should have one called powershell. also, do you have the pwsh extension installed?

The regex should match those 🤔
https://github.com/microsoft/vscode/blob/7b20bd008e5fa5d59d4abd30e9cfef89a301905d/src/vs/workbench/contrib/terminal/browser/terminalQuickFixBuiltinActions.ts#L18-L20
@bamurtaugh If you're in VS Code's screen reader mode, shell integration will not work (it may say it activated which is a bug).

I have the same issue on Ubuntu 16 with bash:

this looks different because shell integration is working for you. thanks for creating that separate issue

@bamurtaugh can you set log level to debug, open dev tools, and screenshot it like this when you run a command such as git sttatus?

I just deleted the line from the PowerShell Profile I was editing, closed the terminal, and reloaded VS Code. I do not have the PowerShell extension installed. I do not have a mention of PowerShell in my settings.json.
I now changed log level to debug from trace. I ran git sttatus and here's the dev tools:

Until shell integration activates, this won't work. What's the warning from powershell in your terminal say? And can you share your settings.json file?

What's the warning from powershell in your terminal say?

When I add if ($env:TERM_PROGRAM -eq "vscode") { . "$(code-insiders --locate-shell-integration-path pwsh)" } to my Profile file? If so, it's:
At C:\Users\brmurtau\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\v
s\workbench\contrib\terminal\browser\media\shellIntegration.ps1:30 char:56
+                 [System.Text.Encoding]::UTF8.GetBytes($match.Value)
+                                                                    ~
Missing closing ')' in expression.
At C:\Users\brmurtau\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\v
At C:\Users\brmurtau\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\v
s\workbench\contrib\terminal\browser\media\shellIntegration.ps1:34 char:3
+     })
+      ~
Unexpected token ')' in expression or statement.
At C:\Users\brmurtau\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\v
s\workbench\contrib\terminal\browser\media\shellIntegration.ps1:35 char:1
+ }
+ ~
Unexpected token '}' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParseException
    + FullyQualifiedErrorId : MissingEndParenthesisInExpression

I'm attaching my settings.json here: settingsNov.txt.

Manual install shouldn't be require so you can remove everything from your profile. I'd recommend doing that then running import-module psreadline

I removed the manual install line and reloaded. Then I ran import-module psreadline in an integrated PowerShell terminal.
I do now see more highlighting in the terminal!

And hovering over the tab says the shell integration is activated.

But I'm not seeing a lightbulb.

ok great progress - now can you set log level to debug, run git sttatus and screenshot the result?

also just fyi from a time saving perspective - no need to reload 😄 just create a new terminal bw changes

you still don't have command decorations, which is surprising given shell integration is activated

@tyriar I don't see indication I'm in screenreader mode (i.e. the status bar UI mentioned here).
When selecting "Use screen reader" in Windows, I don't see any options checked:

However, when I open a new terminal, I do still see the warning:
Warning: PowerShell detected that you might be using a screen reader and has disabled PSReadLine for compatibility purposes. If you want to re-enable it, run 'Import-Module PSReadLine'.
Any advice for how to disable? I see a lot of different info online, so not sure if you have one top of mind.
Subsequent terminals also fail to activate shell integration, even if I run the import-module psreadline:

looks like Set-ItemProperty 'registry::HKEY_CURRENT_USER\Control Panel\Accessibility\Blind Access' On 0

you can also check the value of that via Get-ItemPropertyValue 'registry::HKEY_CURRENT_USER\Control Panel\Accessibility\Blind Access' On

Get-ItemPropertyValue 'registry::HKEY_CURRENT_USER\Control Panel\Accessibility\Blind Access' On outputs 1, so I'll set to 0 and restart in a bit to see if that helps.

If you see this, shell integration and quick fixes will definitely not work:

Warning: PowerShell detected that you might be using a screen reader and has disabled PSReadLine for compatibility purposes. If you want to re-enable it, run 'Import-Module PSReadLine'.

Touching the registry seems risky, I'd search for why pwsh is detecting a screen reader, this will do you good in the long run as PSReadLine makes the PS experience so much better. One possible way to work around this is to run Import-Module PSReadLine inside your profile (run code $Profile). Just running it in the terminal won't get shell integration to work, it needs to be in your profile.

Hmm okay, I'll do some further digging. Adding Import-Module PSReadLine to my Powershell Profile doesn't make a difference (and others online say the same), so I'll need to find the root cause.

Okay I managed to turn off screen reader access - I no longer get the warning when I open an integrated terminal or an external PowerShell terminal.
But shell integration is still failing to activate:

@bamurtaugh what version of powershell are you using? Shell integration is best with pwsh 7.

$PSVersionTable outputs 5.1.25247.1000 for PSVersion. So I just installed PowerShell 7 and created a terminal profile for it in VS Code.
I now got the quick fix! Although as shown in the image, each time I open a new PowerShell 7 terminal instance, the typing is a bit odd and overlaps:

When I ran the command again, the text didn't overlap, but I didn't get a lightbulb:

Not sure if this is expected?
It also took some time to 1) realize I needed PowerShell 7, 2) detect PowerShell 7 in VS Code. Not sure if these items are documented.

It not working here (on Windows) is actually a known issue and there isn't much we can do about it:

See https://github.com/microsoft/vscode/issues/153476

Also the typing overlapping it also a conpty problem that I don't think it on our end.

I tried the git push commands, and there are no warnings either:

I opened a new terminal, and it worked, and I get the telemetry logged correctly.

Let me know if there's anything else I can provide about the topics I mentioned above. Otherwise, I've now gotten this working, it's just not super regular and perhaps there could be greater details in docs (about versions, detecting latest version, etc).

@bamurtaugh looks like the first terminal doesn't have shell integration still, but the new one does. Since it works sometimes I'm guessing it just doesn't work now when the "placeholder decoration" isn't in the expected spot which breaks the command output detection, so a dupe of https://github.com/microsoft/vscode/issues/153476

/duplicate https://github.com/microsoft/vscode/issues/153476


PHPUnit is spelt without  a space :)

Hi @peterchaula
I appreciate it. Im working in a hurry so these things get past


Chef11

Added chef11 support (Will delete nodes / clients) from chef12 & chef11

This was never meant to be pulled into this repo. Please close the PR

Way ahead of you there, but thanks for the heads up! 👍  I wasnt expecting github to default back to the original repo when creating the PR!


Workaround for ansible inventory script group bug

https://github.com/ansible/ansible/issues/13655
... where groups gets added as hosts to the inventory.
That does not happen if group has vars defined, so we
give all groups at least an empty dict of vars.

It's getting closer, much better, thank you @nflx


Partitions can end up out of order

Let's say we have a storage instance with partition size = 2, and we insert rows at timestamp 1 and timestamp 3.
We then have a full partition with minTimestamp=1, maxTimestamp=3. On the next insert, a new partition will be created. When a new partition is created, the first time a row is inserted the minimum timestamp is set (code ref), so let's say we now insert a row at timestamp 2.
We'll now have two partitions with data points out of order. This breaks the query functionality as well.

One possible solution is by setting the min timestamp in the memory partition constructor, and letting the creator enforce the min timestamp to never be less than the max timestamp of the previous partition.
@nakabonne let me know if I'm missing anything with this. Also, do you think this is a real issue and is it worth working on?

@dpgil You're right. This is the issue that I've put off for a while. Basically most data points get timestamped on other programs, where timestamps are not always the same as the process tstorage runs on. Because of that, I presumed we don't determine the min timestamp until the first data point reached.
However, I was totally wrong. We can determine the next min timestamp by just incrementing to the previous max timestamp, a kind of like:
func (s *storage) ensureActiveHead() {
	head := s.partitionList.getHead()
	if head.active() {
		return
	}
	nextMin := head.maxTimestamp + 1

	// All partitions seems to be inactive so add a new partition to the list.
	p := newMemoryPartition(nextMin, s.wal, s.partitionDuration, s.timestampPrecision)


How to accelerate when inferring CAM in parallel

Hello there,
Thanks for your nice work and code sharing.
I currently have a need to perform parallel inference on img tensor with {B, C, H, W} shape.
I am now calculating for each category as well as each image individually, and this method is really slow.
Since I am using the calculation results for design loss, the current speed is not acceptable.
I would like to know if you have any suggested speedup method to inference the cam in parallel.
Looking forward to seeing your reply, thx

Hi @Muyun99, thanks for your interest in our work!
Currently, we do not support batching for this code, but it can be implemented.
To see an example of how batching can be implemented for gradient propagation, please see this issue from our second paper, where I added support of batches to CLIP explainability.
I hope this helps.
Best,
Hila.

Hi @hila-chefer , thank you for your response.
I have a try to shift the solution from the new repo. It`s very easy, thanks for your awesome works.
But I find a problem that the performance of two solutions that generate CAMs(class activation maps) have a difference.
Details
I run the code in VOC2012Aug dataset with vit-base to validate the quality of the CAM.
The solution from Transformer-Explainability will have a mIoU 50.438, and Transformer-MM-Explainability can only reach mIoU 41.562.
Could you explain the difference simply and is there any solution to bridge the performance gap?
Looking forward to seeing your reply, thx

Hi @Muyun99, am I correct in assuming you are estimating semantic segmentation using the explainability maps?
If so- could you please elaborate on how you produce the segmentation from the explainability (how do you binarize the maps)? That could have an impact on how well each method does for semantic segmentation.

Hi @hila-chefer, Yes I want to use this explainability as the groundtruth of semantic segmentation task.
I use this code to evaluate the quality of the CAM, I will inference the map for each class, and use a threshold to convert it to binary map. And suitable thresholds are searched in an interval which is set as [0, 0.6] in this code.
Then I can calculate the mIoU with segmentation groundtruth for quantitative evaluation of the quality of the explainability maps.

I’m not familiar with the code, but we have experimented with both papers and saw that the gap is usually not significant.
With that being said, if you look at the notebooks for ViT with both methods, our gradient based method sometimes outputs smaller relevance values, which possibly requires a different method for proper binarization.
My guess is that this is the source of the gap you see.
On our ICCV paper the Otsu threshold works nicely for DETR, perhaps you could try that?

I’m not familiar with the code, but we have experimented with both papers and saw that the gap is usually not significant.
With that being said, if you look at the notebooks for ViT with both methods, our gradient based method sometimes outputs smaller relevance values, which possibly requires a different method for proper binarization.
My guess is that this is the source of the gap you see.
On our ICCV paper the Otsu threshold works nicely for DETR, perhaps you could try that?

Closing due to inactivity, please re-open if necessary


Update the staging/operator-lifecycle-manager tree

Bump OLM k8s to v0.20.4
Update API to v0.7.1
Preserve existing SA owner refs during installs
Avoid copying CSVs
Workload partition enhancement
Better InstallPlan status handling

/lgtm


Fix 'poetry.utils.env.Env.run(shell=True)' failing when the path to the venv contains a space (resolves #199)

One issue that I discovered while debugging this issue, is that subprocess.Popen(shell=True) decides which shell to use (on Windows) based on the ComSpec environment variable.
Usually, this should point to C:\Windows\System32\system32.exe and that is what my fix assumes.
But if someone has set that to something like C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe, then that person will have some issues since PowerShell wants a . in front of a direct path to an executable for that executable to be executed.
I have chosen not to devise a solution for this issue since I suspect that the number of people that have ComSpec pointed at powershell.exe is minimal at best.

Pull Request Check List

[ ] Added tests for changed code.
[ ] Updated documentation for changed code.

No documentation changes are needed since this is just a bug-fix.
EDIT: Might need to add some documentation to add some documentation for the ComSpec as powershell.exe breaking things issue.

The latest changes escape arguments. I'll add some tests tomorrow or something.

The code currently seems like it's flipping / to \ and sometimes \\.
Is this a real problem (because of escape sequences or something)?
It also fails when escaping python to 'python' on AppVeyor (which I assume is running some form of Linux).
CMD has no such problem and PowerShell doesn't care beyond the quirks I've already mentioned.

git clone https://github.com/sdispater/poetry.git
cd poetry
git checkout 58dbca4
python -m poetry install

Worked fine with ComSpec as cmd.exe, but ComSpec as powershell.exe is still borked.
Why anyone would mess with ComSpec is beyond me, but I tested it just for completeness' sake.


Account for discrete index in robust-fit (optional)

After a discussion with @nucleosynthesis, @ajgilbert, @adewit, and @amarini
This PR adds the possibility of taking into account discrete index during robust-fit via the option "floatDiscreteIndexInRobustFit" set by default to false. If true, CascadeMinimizer::minimize is called instead of ::improve method.

Just to revive this one, thinking about it I can't see a good reason to call CascadeMinimizer::improve instead of minimize here (or at least I can't see a problem just calling minimize and not improve).

@ajgilbert sorry for the slow reply .. as far as I recall, the reason is that ::improve method does not run the iterative minimiser needed if one wants to float the discrete index during robust fit. Therefore, I think the simplest solution should be to call minimise that, on the basis of the presence of the discrete index, runs the short/long set of combinations inside this block:
https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/blob/102x/src/CascadeMinimizer.cc#L423

This should be superseded by #667, and I will close it.


sign function as builInFunction

Sign function as described here (http://en.wikipedia.org/wiki/Sign_function) is easy to implement, but can be a nice-to-have builtinFunction for exp4j.
Great library!

Hey @alexeyegorov ,
Thanks for the input, this might indeed be a useful feature. I will have a look at it, and come back to you.

That'll be great. It is furthermore exciting how easy you've made exp4j to
be extended! :)
I was not actually able to build the project without errors. It does
compile, but while installing it outputs following test errors:

T E S T S
Running net.objecthunter.exp4j.ArrayStackTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.112 sec
Running net.objecthunter.exp4j.ExpressionBuilderTest
Tests run: 201, Failures: 0, Errors: 134, Skipped: 0, Time elapsed: 0.461
sec <<< FAILURE!
Running net.objecthunter.exp4j.ExpressionTest
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec <<<
FAILURE!
Running net.objecthunter.exp4j.ExpressionValidateTest
Tests run: 23, Failures: 0, Errors: 18, Skipped: 0, Time elapsed: 0.003 sec
<<< FAILURE!
Running net.objecthunter.exp4j.FunctionsTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec
Running net.objecthunter.exp4j.PerformanceTest
+------------------------+---------------------------+--------------------------+
| Implementation         | Calculations per Second   | Percentage of Math
|
+------------------------+---------------------------+--------------------------+
| Java Math              |                4195222,50 |
100,00 % |
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.006 sec
<<< FAILURE!
Running net.objecthunter.exp4j.shuntingyard.ShuntingYardTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec
Running net.objecthunter.exp4j.tokenizer.TokenizerTest
Tests run: 22, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 0.013 sec
<<< FAILURE!
Results :
Tests in error:
testExpressionBuilder01(net.objecthunter.exp4j.ExpressionBuilderTest)
testExpressionBuilder02(net.objecthunter.exp4j.ExpressionBuilderTest):
Could not initialize class net.objecthunter.exp4j.function.Functions
testExpressionBuilder03(net.objecthunter.exp4j.ExpressionBuilderTest):
Could not initialize class net.objecthunter.exp4j.function.Functions
...
Not sure what is going wrong.
Cheers,
Alexey
2015-04-22 15:32 GMT+02:00 frank asseg<EMAIL_ADDRESS>
Hey @alexeyegorov https://github.com/alexeyegorov ,
Thanks for the input, this might indeed be a useful feature. I will have a
look at it, and come back to you.
—
Reply to this email directly or view it on GitHub
https://github.com/fasseg/exp4j/pull/38#issuecomment-95178431.

Now tests run through. But I still get some error concerning Javadoc. I'm not that familiar with that stuff and maybe you can help me with this too:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) on project exp4j: MavenReportException: Error while creating archive: Unable to find javadoc command: The environment variable JAVA_HOME is not correctly set. -> [Help 1]

Disabling javadoc generation by adding -Dmaven.javadoc.skip=true should be enough, however, in one of the next steps it will ask you to provide gpg key passphrase, so you should come up with another fancy switch which is -Dgpg.skip=true. Finally your command should look like the following:
 mvn clean install -Dmaven.javadoc.skip=true -Dgpg.skip=true

Thx @sarxos as I'm newbie in the maven world. it would cost me some more hours figuring out.... ;)
From this point it builds successfully. Hope there aren't any other mistakes and sgn function will be in the next update!

@leogtzr you're right! Braces are added!

Will merge this for the next release iteration


feat(Gamut): Added Accordion component

Overview
PR Checklist

~[ ] Related to Abstract designs:~
[x] Related to JIRA ticket: WEB-908
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

Description
A true "Accordion" component is actually difficult because of accessibility: it needs to make its components not narrated or focused when collapsed... which normally means either switching child links to plain text (doable only on a component-by-component basis) or not rendering children at all (hard because it still needs to animate height).
I tried a bunch of pure CSS solutions but couldn’t make anything that looked good and worked well. We’ve been talking about adding animation primitives to Gamut for a while so this seems like a good opportunity to introduce our normal framer-motion library.

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.15-alpha.ef8dc4.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ed9508f70101673b2c411c6--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.15-alpha.7b2c94.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ed957a0127e3b6a169d62da--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.15-alpha.02cf12.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ed96189c8e936eb8e222d47--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.15-alpha.9eda43.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5eda4caaaa7ce080cf44e8f9--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.15-alpha.ec2c04.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5eda4fb879ccc388571b203e--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.15-alpha.90fa74.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ee0093b455d577e06532e2a--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.24-alpha.cb9183.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ee7f2a2e9f333b7e1a4b013--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.24-alpha.66f9da.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5eebd7116c3f1b962687e6b5--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.24-alpha.5ee878.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ef13c0f1480ee019abe6a71--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.24-alpha.0a3d33.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ef13f4b0167f7019d71da7e--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.30-alpha.6efcc3.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@1.7.30-alpha.96e717.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@1.7.30-alpha.d06020.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ef39b9824e3d0ddb8170587--codecademy-styleguide.netlify.appDeploy Logs

Maybe that's related to the tests failing... I shall investigate! 🕵

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.36-alpha.46e7c1.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5f05df40c33520f8351b34e1--codecademy-styleguide.netlify.appDeploy Logs

Looks great, two questions but feel free to dismiss if they are not relevant :D
(Also changelog stuff :P)

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.36-alpha.8af0a6.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5f0633be25fbebb1c7c16445--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.36-alpha.f8e53b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5f0635ebb503ad755a51ef3f--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.37-alpha.675539.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5f063b67062816e14dc0355c--codecademy-styleguide.netlify.appDeploy Logs


xcactivitylog is not a valid xcactivitylog

I've been testing some builds generated with xcodebuild. The command generally looks like:
xcodebuild -workspace Project.xcworkspace -scheme Project  -derivedDataPath 'd_d/Project' clean build -resultBundlePath testResult/Project.test_result

I've noticed that when I try and run xclogparser using the --derived_data argument, I get the following error:

Project/Logs/Build/UUID.xcactivitylog is not a valid xcactivitylog

If I run file on the xcactivitylog, it returns
gzip compressed data, original size modulo 2^32<PHONE_NUMBER> gzip compressed data, reserved method, ASCII, has CRC, encrypted, from FAT filesystem (MS-DOS, OS/2, NT), original size modulo 2^32<PHONE_NUMBER>

I'm not quite too sure where the reserved method, ASCII, has CRC, encrypted, from FAT filesystem (MS-DOS, OS/2, NT) came from. It consistently builds this way.

@BalestraPatrick Cool thanks. I tried using it, though it seems to have some issues with some pods. Ideally I want to have us ditch pods altogether.
Just curious. Do you have internal libs/frameworks which are Carthage packages? And if so, how do you facilitate debugging or modifying it when used with the app? For example we are using private pods (these are locally linked and are committed in our monorepo). Right now the pods project file is included in the workspace. So this means that you essentially have access to all code in the Xcode project.
I'm trying to move us away from that and to prebuilts. However, due to how the app is built, many of those private pods more or less need to app in order to develop for. Do you have a similar circumstance and if so how do you work around this?
I'm working on a proof of concept of using xcodegen to build project files which by default will use prebuilts. But if you need say private pod A or B, it will include those as subprojects. Part of my plan is to move away from pods and to create Xcode projects for everything that can then be added to the app when one needs to debug.

@mobileben That's one way of doing it. We don't really use Carthage or CocoaPods for internal code exactly for that reason.


RDKBDEV-2943 : Adding Necessary Logs In RdkGponManager.

Reason for change:
Adding Necessary Logs In RdkGponManager for improving debuging.
Test Procedure:Sanity Test.
Risks: None.

Internal ticket for tracking https://ccp.sys.comcast.net/browse/RDKCOM-5094


IOS Dropdown

Is there a way to convert the dropdown to use the IOS dropdown menu on mobile?

I don't think so since it's just a div, not a select


how  to add voice msg feature for my andriod app

anyone can pls what is available api for building voice message feature in my app.pls help me

Android Async Http is an HTTP client to make rest API requests.
you should google it.


Web Support?

Can you please add support for this package. I am looking forward to add this to my app. Thanks in advance.

Try,
imagekit_io: ^0.0.1 for web
And let me know if this Package worked or not.
Thank you

Sure.. I just found another package. I will try that. But any idea why you created a separate package??

Because flutter_imagekit is specially build for Android, IOS, Not for Web .
In Other hand Web Required dart.html. other platform Support dart.io.
But imagekit_io Support Both Platform. For More Please check Example how to use new package.
Thank you


Should't the app have notes editor built in?

Ok, I can choose a folder, save there separate notes in .md format, but how do I edit them without additional editor?
The unique idea of adding notes from status bar can't end like this.
Do you plan to make notes editor? A widget?
To read/edit a note now I need to look for a folder, then choose a note by its title (which is date by default), and then open it with chosen editor. That's a lot, while there are apps that have widgets or/and give notes overlook at a glance after one icon click.

Hello. Initially, the app was created solely as an add-on to the already great note-taking app Obsidian, where I was missing just one single feature: the ability to quickly add notes from any screen. Your idea is interesting, and I will think about what functionality for viewing and editing existing notes can be added later, but for now, I can't make any promises.

Well, for people who don't know Obsidian yet: it's probably THE most versatile and feature-rich note-taking application ever written for Android (and desktop as well). Specifically its integrated plugin system is just mighty and let's you basically do anything with notes you can think of. For most people way way too much, a multitude of options make it necessary to really undergo quite a learning curve and maybe even commit to the community support. It's a great app, but too complex for people looking for a quick and easy to use markdown editor.
For those people I can fully recommend the slim and easy markdown app "Markor", available at F-Droid, GitHub and Playstore. This is also the note app I'm trying that notification plugin app with. Besides markdown it's also a fully usable code editor with highlighting capability and opens any text-based file extension. I use it for that kind of stuff which on desktop machines I would use Notepad++ for.


[REQUEST] clip to bounds

is it possible to add a "clip to bound" option?
I've a layout with rounded corner
Than with asyncImage (with the same size of parent) I load an image, but image is bigger and not have corner radius.
thanks

There is Stencil, you could use a RoundedRectangle instruction in a Stencil block to clip your image to this shape.
this is a support question though, if you need more info, use the support channels.


Ingress Objects does not report an IP over kubectl

Somehow, Ingress objects does not have an IP.
I don't know this is intended behavior but in able for me to use the following exposed objects I need their IP the ingress object is exposed at.
enra@sakura:~$ kubectl get ingress
NAME                 HOSTS                      ADDRESS   PORTS     AGE
wanton-ostrich-api   api.local.containerum.io             80        14m
wanton-ostrich-ui    local.containerum.io                 80        14m

inspection-report-20181201_071849.tar.gz

Thanks for the swift response @ktsakalozos, glad to find an actual bug on Microk8s.

For anyone working on a setup behind a corporate firewall and your ingress services do not display an address then it might be also the case that ingress image cannot be pulled.
For example if you run (set correct pod id):
$ microk8s.kubectl describe po/nginx-ingress-microk8s-controller-l7hcp -n ingress
and the result is something like this below
Events:
  Type     Reason   Age                     From              Message
  ----     ------   ----                    ----              -------
  Normal   BackOff  47m (x12863 over 2d1h)  kubelet  Back-off pulling image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller-amd64:0.25.1"
  Warning  Failed   42m (x12885 over 2d1h)  kubelet  Error: ImagePullBackOff
  Normal   Pulling  38m (x4 over 39m)       kubelet  Pulling image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller-amd64:0.25.1"
  Warning  Failed   38m (x4 over 39m)       kubelet  Failed to pull image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller-amd64:0.25.1": rpc error: code = Unknown desc = failed to resolve image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller-amd64:0.25.1": no available registry endpoint: failed to do request: Head https://quay.io/v2/kubernetes-ingress-controller/nginx-ingress-controller-amd64/manifests/0.25.1: x509: certificate signed by unknown authority
  Warning  Failed   38m (x4 over 39m)       kubelet  Error: ErrImagePull
  Normal   BackOff  24m (x63 over 39m)      kubelet  Back-off pulling image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller-amd64:0.25.1"
  Warning  Failed   4m19s (x150 over 39m)   kubelet  Error: ImagePullBackOff


Control opening in odd place when it becomes larger than it's container.

I have a multiselect with a ton of possible options (locations) and it is placed inside a bootstrap panel. I have the panel set to scroll on overflow. If I open the multiselect and select all locations then close it, the control itself is really long; longer than the panel so the scroll bar appears. When I click on the part of the control I can see, the multiselect dialog appears at the bottom of where the list is, ie hundreds of pixels down the screen, before the panel scrolls to see the bottom of the panel. This results in the panel remaining hundreds of pixels down screen completely disconnected from the control which has scrolled into view.
Trying to access the select when only a few things are selected and the control does not overflow results in normal expected behavior.

@valevalorin ,
Width wise, the directive indeed will expand to fill 100% parent element's width. I suggest to put a wrapper element (say a DIV) to wrap the directive. You can then play with the height and width.
If that doesn't work, please replicate this in Plunker or JsFiddler so I can look further.

Is the issue isn't with the width or the height of the element; they can be whatever. The issue is where the multiselect shows up. Here's a fiddle demonstrating the issue: http://jsfiddle.net/valorin/qxwkdmf5/1/
If you click on the directive and hit select all you'll see the dialog move down the page. If you continue selecting and deselecting the directive you'll see the dialog appear and disappear at the bottom of the result pane far away from the directive box.

Ok.. I see what you mean.
This is the reason:

The selection list simply popups at the bottom right after the button (positition:absolute). Now, with all the items selected, the button naturally grows taller. Say 500px tall. When your panel-body is only 300px tall, there will be a 200px height difference. And because of the absolute positioning, it will show up outside of the panel.
Some CSS addition might fix this problem. Would you like to explore this yourself, or you want a direct answer?

I know what it was doing, just not the best way to fix it. I was hoping that might've been a way to specify that the dialog should appear after scroll events or something clean like that. If that isn't the case I'll just CSS. Thanks.

Hi @valevalorin ,
Yeah unfortunately no such way/settings.. it's simply how HTML/CSS works.
Anyway I would use position:relative on the panel-body. It should bring the popup within the panel-body right after the button.


ELF: On reduce, hop to target EventLoop before doing operation

Motivation:
Folds often involves chaining multiple futures together. It's
beneficial if you're already on the target EventLoop as it might
vastly reduce the amount of EventLoop hops.
Modifications:
Execute onto the target EventLoop before doing the folds.
Result:
Fixes #1054

@swift-nio-bot test perf please


docs-bug(COMPONENT): Use of multiple themes: missing styles (Angular 18)

Documentation Feedback
Hi, if I want to set 2 themes as described in the docs, essential styles are missing.
I created my themes with ng generate @angular/material:m3-theme
$ ng version                                                                                130 ↵

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 18.0.1
Node: 22.2.0
Package Manager: npm 10.7.0
OS: darwin arm64

Angular: 18.0.0
... animations, cdk, common, compiler, compiler-cli, core, forms
... localize, material, platform-browser
... platform-browser-dynamic, router, service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1800.1
@angular-devkit/build-angular   18.0.1
@angular-devkit/core            18.0.1
@angular-devkit/schematics      18.0.1
@angular/cli                    18.0.1
@schematics/angular             18.0.1
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.6

dependencies:
{
    "@angular/animations": "^18.0.0",
    "@angular/cdk": "^18.0.0",
    "@angular/common": "^18.0.0",
    "@angular/compiler": "^18.0.0",
    "@angular/core": "^18.0.0",
    "@angular/forms": "^18.0.0",
    "@angular/material": "^18.0.0",
    "@angular/platform-browser": "^18.0.0",
    "@angular/platform-browser-dynamic": "^18.0.0",
    "@angular/router": "^18.0.0",
    "@angular/service-worker": "^18.0.0",
    "jwt-decode": "^4.0.0",
    "rxjs": "~7.8.0",
    "tslib": "^2.6.2",
    "zone.js": "~0.14.3"
  }

in the following examples it is missing but is included in the styles.scss
@use "@angular/material" as mat;
@use "m3-theme";

@include mat.core();

For example:
html {
	@include mat.core-theme(m3-theme.$dark-theme);
	@include mat.button-theme(m3-theme.$dark-theme);

	@media (prefers-color-scheme: light) {
		@include mat.core-color(m3-theme.$light-theme);
		@include mat.button-color(m3-theme.$light-theme);
	}
}

results in:
Note: the input at the top and the icons at the bottom

Note: "Show all properties (57 more)" at the bottom

html {
	@include mat.all-component-themes(m3-theme.$dark-theme);

	@media (prefers-color-scheme: light) {
		@include mat.all-component-colors(m3-theme.$light-theme);
	}
}

results in:
Note: the input at the top and the icons at the bottom

Note: "Show all properties (800 more)" at the bottom

If I use all 3 together, duplicate styles are generated
html {
	@include mat.core-theme(m3-theme.$dark-theme);
	@include mat.button-theme(m3-theme.$dark-theme);
	@include mat.all-component-themes(m3-theme.$dark-theme);

	@media (prefers-color-scheme: light) {
		@include mat.core-color(m3-theme.$light-theme);
		@include mat.button-color(m3-theme.$light-theme);
		@include mat.all-component-colors(m3-theme.$light-theme);
	}
}

Affected documentation page
https://material.angular.io/guide/theming#defining-multiple-themes

Yes, calling both button-theme and all-components-theme mixins will result in duplicate styles. Under the hood, all-component-theme calls all of the other theme mixins.
In our theming guide, we suggest calling the individual component mixins to avoid this extra CSS as you noted.
It seems like in your case you are missing some mixin calls. You will also need to include fab-theme, input-theme, and icon-theme. Let me know if that solves this for you, thanks for using M3!


can't download package vary@dc17535 as the url changed

Issue
Setup:

Deno Version: 1.2.0
v8 Version: 8.5.216
Typescript Version: 3.9.2
Opine HTTP Proxy Version: 2.0.0
Opine Version: 0.20.1

Can't download package vary@dc17535 as the url changed
Details
When I bundle the code,  it shows:
error: Import<EMAIL_ADDRESS>failed: 404 Not Found
Imported from "https://deno.land/x/opine@0.19.1/deps.ts:46"

Ref: https://github.com/asos-craigmorten/opine/issues/48

Heya @youngyou 👋 do you have a minimal reproduceable code snippet I can use to debug? Was sure this should be fixed in #48 🤔

Ah are you using the proxy module? Don’t think I’ve touched that in a while and would certainly explain why your code is still importing 0.19.1 if you are! If so it’s a bug with that and we should get an issue raised there and a fix in ASAP 😄

Hopefully fixed in 2.1.0 - let me know if have further issues.


Inline RPM dependencies in container image build

This PR introduces a radically different - and much more wholistic - approach to producing the apicast container image.
The current build relies on RPM packages that must have been built and pushed in a repository, so they can be pulled and installed into this image. However, this poses several issues with regards to how those RPMs are built, how easy they are to update, etc. etc.
The approach here is not entirely new - it comes from the product build, which has already adopted this multi-stage approach in building RPMs within the container image and then installing them in the final produced image.
It should be noted that - eventually - we could remove the RPM packaging altogether and essentially convert the RPM spec files into Containerfile instructions. This would further simplify the build steps. In this PR, we are only taking one first step towards that.
Some notes:

all dependencies have either been added as git submodules, or vendored into the repo,
all RPM builds now happen in a multi-stage build,
this is just the first version of the Containerfile that I was able to get a passing build on, with podman build -f Containerfile .
there are still several improvements to be implemented in the multi-stage build, to reduce some duplication. The previous build system didn't allow reusing previous build stages in subsequent ones (i.e. it didn't allow FROM rpm-builder AS openresty, etc.), so that still needs some clearing up.
we should probably only keep one of Containerfile and Dockerfile. I just didn't overwrite the Dockerfile in one go to allow for a better chance of review.

Open issue: the jaegertracing-cpp-client RPM is currently commented out. That hadn't previously been ported to its own build stage and I don't know if it's worth doing that now. Luckily, support for opentracing is planned to be dropped in the next 3scale 2.16 release (considering we now have support for opentelemetry), so those lines could probably be removed altogether.
@tkan145 I am creating this as a draft PR, so we can slowly start reviewing it.
(Note: while I was able to build a container image, I haven’t tested it in any way yet. I’d also like your help in figuring out if there is anything important missing in the new Containerfile from the existing Dockerfile ).

Supersedes #1510

@tkan145 ok, this now looks like it has more or less the same failures as master.
Could you please take another look ? (I've basically just created a new branch and created a new PR from that and deleted the old branch)

@gsaslis can you do another rebase? :crossed_fingers:

@tkan145 Looking better!
just busted and prove failing now.

nice! all green! ✅


docs: add tutorial for testing hiera data

Inspired by #601 it would be helpful to have another tile on this page http://rspec-puppet.com/documentation/ for testing modules using hiera data.
I'm using PDK, and sadly quite a lot of material that can be found online is for ancient versions of Puppet and/or hiera, old ways of using rspec in combination with various other gems, and even just lots of copy/paste code, and thus i'm really missing some authoritative pointers as to what and how I ought to test my modules that are getting/looking up data from hiera.
Observation: If I don't specify any hiera_config in the rspec configuration, then the module's "normal" hiera data is the only thing that is used, as defined by my_module/hiera.yaml configuration.
Being new to ruby and rspec, having read the "Why should you test your Puppet modules?
" part of the tutorial, that surprised me.  I was not expecting rspec to use any of my modules hiera data.
I was expecting to have to define my own simplified hiera data inside the my_module/spec/ folder, such that when my modules hiera data changed, my rspec data would stay the same and not be subject to any refactoring changes/erros.
Reading #732 just makes me even more confused as to what the correct way of testing hiera data is.  This PR adds parameters to disable the modules normal hiera data, and any combination in between.
Also notes about how to deal with modules that are using eyaml would be nice.
This subject seems partially discussed in #626.
Anothing that would be nice to have in the README.md#hiera_config, is that it only supports hiera v3 configurations.  The example later on at README.md#hiera-integration, clearly uses v3 syntax, but it doesnt state anything about it, so I thought it was an old exmaple that hadn't been updated.
I wasted a good day of my life trying to figure out why it didn't use my hiera data specified in my my_module/spec/spec_helper_local.rb.  It became clear why, after reading this: HI-598.  Sadly I didn't get any error when running pdk test unit or bundle exec rake spec, but converting my my_module/spec/hiera.yaml from version 5 til version 3 made it work right away.
This also seems to be partially discussed in #551.

Yes please.


Make sure UIAlertViews are always rendered vertically

WoCDisplayMode uses a 'presentationTransform' to rotate the presentation surface for certan apps, but we don't want to use that transform to rotate UIAlertViews (else they render sideways if the app is rotated).  This will be handled automatically when we move UIAlertView over Xaml (as we've already done for UIActionSheet), but for now we need to undo the 'presentationTransform' rotation for UIAlertViews.
Fixes #2611.

:shipit:

:shipit:


Improving batching and thread utilisation at the same time

I've struggled in the past to find a batching solution that is able to:

Be completely flexible (count, byte size, period)
Be consistent across all components
Satisfy at-least-once delivery guarantees in all cases

The batch processor was my first solution and satisfied 2 and 3 (with caveats). Although it offered all the parameters needed to satisfy 1 it would only resolve them during message receipt and isn't capable of flushing a backlog during shutdown. That makes it inappropriate for some common use cases.
The memory buffer was recently added in order to satisfy 1 and 2 entirely, which it does. However, the memory buffer (like any buffer) diminishes delivery guarantees and therefore cannot be considered a general solution. It also prevents users from having batch policies specific to certain inputs.
For the last year or so I've been experimenting with input level parameters for satisfying 2 and 3. The kafka_balanced input, for example, has the parameter max_batch_count. This mechanism has potential since being at the input level it allows us to preserve delivery guarantees without limitations on what kind of batching we implement (1 and 3). However, the challenge would be making this mechanism consistent across all inputs.
I think I have a solution that satisfies all three requirements and also comes with the benefit of improving the user experience of thread utilisation.
Adding Async Methods to Inputs
The first stage of my plan is already in progress. I'm opening up the implementations of all inputs so that they allow asynchronous acknowledgement of messages in transit, with the potential (but not requirement) that subsequent messages can be processed before that ack is made.
This is important as up until now each input makes the assumption that when an acknowledgement is made for a message it applies to all prior messages. This new API will allow Benthos to process messages from a single input in parallel, utilising multiple processing threads and outputs. It also makes it very easy to create a general component that wraps these inputs with a buffer implementation that satisfies our above requirements, the resulting component configs will look something like this:
type: kafka_cg
kafka_cg:
  addresses:
  - localhost:9092
  batching:
    byte_size: 0
    condition:
      type: static
      static: false
    count: 1
    period: ""
  consumer_group: benthos_consumer_group
  topics:
  - benthos_stream

Some inputs fit this new model easier than the previous one. The ones that don't are usually limited as they are ALO but consume a single continuous feed of data that cannot be acked individually (kafka, kinesis). However, there are individual solutions possible for these inputs.
The Headache
The reason why this transition hasn't happened before is because of one single component, the batch processor. The way in which the batch processor operates relies entirely on the feed it receives being one continuous stream of data from a single source. This is why it has always been recommended that the batch processor is placed within the input section of a config.
For some asynchronous inputs it will be important that a batch processor is never present in a pipeline. Therefore, we need to be able to detect when this is the case in order to fallback to old behaviour and warn users.
Plan
My plan is flexible but will work in the following stages:

~Implement async methods for all inputs where applicable. Whist this is happening I'll also be putting work into improving and expanding the integrated test suite. For some inputs the asynchronous version will be a separate component entirely. Note that these methods being implemented does not mean they are being used at this stage.~
~Implement work around for batch processor used with async inputs.~
~Gradually roll out batching fields for all inputs. This is our new standard batching method. The documentation for each component will be updated to state the batch processor is NOT allowed with this input. In reality if the batch processor is used the input will fallback to the old implementation in order to preserve backwards compatibility. If stage 2 was not successful and it isn't possible to reliably detect batch processors at construction time then instead the new async methods will only be used then a user configures batching.~
~Add batching to the broker input in order to support batching for combined async inputs. There will need to be documentation explaining that some inputs potentially will not work with it.~
~Once all inputs support batching fields the documentation for the batch processor will be updated with a deprecation notice. There will also be a warning log when it is used. The batching and pipelines documentation will also be updated/simplified. All tutorials and guides using the batch processor will also be updated.~
Unless a serious flaw has been found with the new batching and input mechanisms the next major release of Benthos (v4) will remove the batch processor entirely and all code related to working around it will be removed.

Stage 1 is currently in progress and almost complete. If anyone has any thoughts please post them here, I'm very interested in feedback at this stage. Also, please let me know if you are testing any of the new components/batching behaviours.

Implementations are done for all inputs now. Any input component that doesn't have a batching field supports the broker batching mechanism. We therefore now have a substantial batching strategy for all inputs and all inputs where asynchronous processing is possible now has it supported by default.

These changes are implemented and scheduled to release in v3.3.0. There's a release candidate out so I'm looking for testers: https://github.com/Jeffail/benthos/releases/tag/v3.3.0-rc1