fix: update placeholder regex to match multiple occurences in same st…

Description
Update placeholder regex to support multiple occurences in the same string
Fixes: #144
Checklist
Please make sure that your PR fulfills the following requirements:

[x] Reviewed the guidelines for contributing to this repository
[x] The commit message follows the Conventional Commits Guidelines.
[x] Tests for the changes have been updated
[ ] Docs have been added / updated

Type of Change

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

Other information

I will look if I can write a test tonight ! :)

@llavaud Thanks for the PR! Hopefully updating the existing tests/adding new ones isn't too hard, e.g, fixing this one:
=== RUN   TestMain/will_replace_templates_from_local_vault
2021-06-14T13:18:55.967Z [DEBUG] core0.identity: creating a new entity: alias="id:"3e0f62a7-2706-0976-f0e3-04318cfba481" canonical_id:"4f8b83fb-012c-6fac-c37e-0edff5c7ec9d" mount_type:"approle" mount_accessor:"auth_approle_2ac48815" mount_path:"auth/approle/" metadata:{key:"role_name" value:"role1"} name:"1e260ae6-c205-80ee-ad95-4452cd4f627c" creation_time:{seconds:1623676735 nanos:967905631} last_update_time:{seconds:1623676735 nanos:967905631} namespace_id:"root""
Error: Replace: could not replace all placeholders in Template:
replaceString: missing Vault value for placeholder path:secret/testing#secret-var-value in string SECRET_VAR: <path:secret/testing#secret-var-value>

you plan to release a 1.1.1 quickly ?

@llavaud yes, i will try to get 1.1.1 released today


webpack.optimize.ModuleConcatenationPlugin is not a constructor

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
On my local machine I noticed no issues with the webpack upgrade, but travis fails each time since upgrade.
Travis cannot complete npm run test command, throws the following error

21 06 2017 20:16:31.514:ERROR [config]: Invalid config file!
TypeError: webpack.optimize.ModuleConcatenationPlugin is not a constructor
at Object. (/home/travis/build/.../webpack.prod.config.babel.js:91:3)
at Module._compile (module.js:569:30)
at loader (/home/travis/build/.../node_modules/babel-register/lib/node.js:144:5)

If the current behavior is a bug, please provide the steps to reproduce.
Updated to Webpack 3 and add the following snippet to webpack config
  // Webpack 3 Scope Hoisting
  new webpack.optimize.ModuleConcatenationPlugin(),

What is the expected behavior?
Travis not to fail
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
node: 8.1.2
npm: 5.0.3
webpack: 3.0.0

Please submit support requests and questions to StackOverflow using the tag [webpack]. StackOverflow is better suited for this kind of support. The issue tracker is for bug reports and feature discussions. See also our CONTRIBUTING guidelines.

have same problem,
<EMAIL_ADDRESS>TypeError: webpack.optimize.ModuleConcatenationPlugin is not a constructor

For posterity... I had a similar issue, and it was just a matter of having not imported the right stuff. Try something like this in your webpack js file:
var ModuleConcatenationPlugin = require("webpack").optimize.ModuleConcatenationPlugin;
...
plugins: [
  new ModuleConcatenationPlugin()
]


[firebase_mesaging] Correct place for FCM initialisation

My app has next routing:
return MaterialApp(
      debugShowCheckedModeBanner: false,
      title: 'App',
      theme: ThemeUtil.instance.appTheme,
      routes: {
        Routes.onboarding: (_) => OnboardingPage(),
        Routes.login: (_) => LoginPage(),
        Routes.signUp: (_) => SignUpPage(),
        Routes.homePage: (_) => HomePage(),
        Routes.inbox: (_) => ConvoListPage(),
      },
      initialRoute: (isOnboarding) ? Routes.onboarding : Routes.homePage,
    );

HomePage has 5 tabs (pages) and this is a main apps part. Pushes should redirect user to inbox.
The question is where should be configured FCM?
When it is initiated in Home page it catch push and redirect user to Inbox, but when user should be returned to one of tabs of Home page, it is initiated again and makes a loop (user went to Home and onResume / onLaunch redirects to Inbox again and again).
I can't initiate FCM on higher level because in the routing isn't available there.

Actually, you can initiate FCM on same level as you are initiating Material app.
All you need to do is to add navigatorKey: navigatorKey parameter to MaterialApp.
Here is example of declaration:
static final GlobalKey<NavigatorState> navigatorKey = GlobalKey();
Then once you get push notification just refer to navigatorKey and push Route something like this:
navigatorKey.currentState.pushNamed


[html5] Android stock browser: Float32Array is not defined

Tested on Samsung Galaxy Y
typed arrays is only supported on Android 4 and above
http://caniuse.com/#feat=typedarrays
Threre is a polyfill that works
http://inexorabletash.github.io/polyfill/typedarray.js
and about the polyfill:
http://stackoverflow.com/questions/11278619/looking-for-javascript-typed-arrays-emulation-library/11278663#11278663
It's hard to debug on the android stock browser, I found a app that helped. It's a webview with a javascript console:
https://play.google.com/store/apps/details?id=com.starbug1.android.htmldomviewer

I was thinking if we could have the polyfill in the lib folder (in the output), and load the file only on androids with lower versions. The problem is to detect the android version. The number is in the user agent string, but each agent string is different from the others.
This is a problem now but it will go away someday. Maybe lime could have a option to build with the polyfill, for the people that need support to android 2.3.

Okay, revisiting this again, I think that we should not include a polyfill for this in Lime right now:
http://caniuse.com/#feat=typedarrays
If we could reliably include the polyfill only when required, then I'd be open to it, but I'm concerned about the difficulty of testing this. I'd be open to a pull request, but for now, I think that perhaps not including it is reasonable by default, however, it could definitely be included per project, like this:

Download typedarray.js into your project
Add  to your project XML

This would add 38KB to your project, and should ensure that this is available once you run your project


error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details. Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081 :ReactNative:Unexpected empty result of running 'npx.cmd --quiet --no-install react-native config' command from 'null' directory. :ReactNative:Running 'npx.cmd --quiet --no-install react-native config' command from 'null' directory failed.

FAILURE: Build failed with an exception.

Where:
Script<EMAIL_ADDRESS>line: 170

What went wrong:
A problem occurred evaluating script.

Command config unrecognized.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 3s
error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
:ReactNative:Unexpected empty result of running 'npx.cmd --quiet --no-install react-native config' command from 'null' directory.
:ReactNative:Running 'npx.cmd --quiet --no-install react-native config' command from 'null' directory failed.
FAILURE: Build failed with an exception.

Where:
Script<EMAIL_ADDRESS>line: 170

What went wrong:
A problem occurred evaluating script.

Command config unrecognized.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 3s
at checkExecSyncError (child_process.js:621:11)
at execFileSync (child_process.js:639:15)
at runOnAllDevices (C:\react\zinia\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:94:39)
at buildAndRun (C:\react\zinia\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\index.js:158:41)
at C:\react\zinia\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\index.js:125:12
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Command.handleAction (C:\react\zinia\node_modules\react-native\node_modules\@react-native-community\cli\build\index.js:164:9)

React Native version:

Steps To Reproduce

System:
OS: Windows 10 10.0.18362
CPU: (4) x64 Intel(R) Core(TM) i7-4610M CPU @ 3.00GHz
Memory: 1.48 GB / 7.91 GB
Binaries:
Node: 12.13.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.19.1 - C:\Users\Dell\AppData\Roaming\npm\yarn.CMD
npm: 6.13.2 - C:\Users\Dell\AppData\Roaming\npm\npm.CMD
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-191.8<IP_ADDRESS>00203
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
please help :(

Hello siddiqaQ , what you do to solve this problem?!

@rickhanlonii what was the reason for closing this? Please help us with any info that could allow us to trace the cause of this issue.

I faced the same problem.
npx --quiet react-native config or npx.cmd --quiet react-native config
That command, if you execute in the root directory of your project, will produce JSON output (if everything is configured correctly).
The problem is, I did not locate my react native project in the root folder of the git repository. After then, I created another git repo and set the root folder of the repo to be the root folder of the react native project, and everything is ok then.

I had this same problem. In my case I was using an old version of npm (3.10.3) and all I did was upgrade to 6.12.1. It worked for me.

Thanks everyone for the help!
I closed this issue because it didn’t fit the template or include a meaningful description.
The comment must have got lost in the process sorry about that.

I am also facing the same problem . Is there any work around?

On my side issue 838 allowed me to solve the issue. I uninstalled and reinstalled globally:
npm uninstall -g react-native react-native-cli
npm install -g react-native react-native-cli
react-native start --reset-cache
Then cleaned the project and built again.
Don't be too harsh if it doesn't work for you ;) Also, I am not 100% it helps in this case, but the interesting read that led me to the solution was issue #804, because at core it seems to be related to the build script not calling npx from the root React Native directory.

If anyone is still seeing this issue, please submit a new issue that conforms to the bug template and we'll take a look.

I am also facing same issue...
:ReactNative:Unexpected empty result of running 'npx.cmd --quiet --no-install react-native config' command from 'null' directory.
:ReactNative:Running 'npx.cmd --quiet --no-install react-native config' command from 'null' directory failed.

ERROR: Command config unrecognized. Make sure that you have run npm install and that you are inside a react-native project.

@rickhanlonii I've created #27707 using a template. Let me know if you nee more information.

error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
Unable to install C:\Users\Athira\Desktop\ReactProjects\demo2\android\app\build\outputs\apk\debug\app-debug.apk
com.android.ddmlib.InstallException: Unknown failure: Error: failed to write; Failed to allocate 23022086 because only 0 allocatable
at com.android.ddmlib.Device.installRemotePackage(Device.java:1063)
at com.android.ddmlib.Device.installPackage(Device.java:903)
at com.android.ddmlib.Device.installPackage(Device.java:881)
at com.android.ddmlib.Device.installPackage(Device.java:870)
at com.android.builder.testing.ConnectedDevice.installPackage(ConnectedDevice.java:126)
at com.android.build.gradle.internal.tasks.InstallVariantTask.install(InstallVariantTask.java:179)
at com.android.build.gradle.internal.tasks.InstallVariantTask.install(InstallVariantTask.java:110)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:103)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:48)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:41)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:28)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:702)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:669)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$5.run(ExecuteActionsTaskExecuter.java:401)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:394)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:92)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:390)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:373)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$200(ExecuteActionsTaskExecuter.java:79)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:210)
at org.gradle.internal.execution.steps.ExecuteStep.lambda$execute$1(ExecuteStep.java:33)
at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:33)
at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:26)
at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:58)
at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:35)
at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:48)
at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:33)
at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:39)
at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:73)
at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:54)
at org.gradle.internal.execution.steps.CatchExceptionStep.execute(CatchExceptionStep.java:35)
at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:51)
at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:45)
at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:31)
at org.gradle.internal.execution.steps.CacheStep.executeWithoutCache(CacheStep.java:201)
at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:70)
at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:45)
at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:49)
at org.gradle.internal.execution.steps.StoreSnapshotsStep.execute(StoreSnapshotsStep.java:43)
at org.gradle.internal.execution.steps.StoreSnapshotsStep.execute(StoreSnapshotsStep.java:32)
at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:38)
at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:24)
at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:96)
at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:89)
at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:54)
at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:38)
at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:77)
at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:37)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:36)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:26)
at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:90)
at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:48)
at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:33)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:117)
at org.gradle.api.internal.tasks.execution.ResolveBeforeExecutionStateTaskExecuter.execute(ResolveBeforeExecutionStateTaskExecuter.java:75)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:62)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:108)
at org.gradle.api.internal.tasks.execution.ResolveBeforeExecutionOutputsTaskExecuter.execute(ResolveBeforeExecutionOutputsTaskExecuter.java:67)
at org.gradle.api.internal.tasks.execution.ResolveAfterPreviousExecutionStateTaskExecuter.execute(ResolveAfterPreviousExecutionStateTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:94)
at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:95)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:73)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:49)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:416)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:406)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:102)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:49)
at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:43)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:355)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:343)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:336)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:322)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker$1.execute(DefaultPlanExecutor.java:134)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker$1.execute(DefaultPlanExecutor.java:129)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:202)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:193)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:129)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:installDebug'.

com.android.builder.testing.api.DeviceException: com.android.ddmlib.InstallException: Unknown failure: Error: failed to write; Failed to allocate 23022086 because only 0 allocatable

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 17s
at checkExecSyncError (child_process.js:611:11)
at execFileSync (child_process.js:629:15)

I had a similar problem, and it appeared when I used the Android emulator, but everything worked fine when I debugged with a mobile phone.

same problem here

same problem here

please check your devices connected Or USB debugging on ( causes of a lot of time )

I checked bro I even listed the device using adb devices comand

Facing the same problem 😞

Same

same

This appears to have been a bug in the react-native cli which has been fixed in the latest version, see: https://github.com/react-native-community/cli/issues/804

the same bug I am also facing

the same bug .. I ever have seen

same

I'm facing the same bug too after moving to react native 0.62

As mentioned in https://github.com/facebook/react-native/issues/27707, this issue was in the react-native cli and should be fixed.
If you're still seeing this, please comment or open a new issue in the CLI.
Going to lock this so that the +1 comments don't burry this message.


[cPP Comment 24] FCS_DTLSC_EXT.2; A.7.1.1

Location: FCS_DTLSC_EXT.2; A.7.1.1
Comment 24: Elements 2 and 3 of this SFR apply regardless of whether mutual authentication is supported
Suggested Change: Add these elements to FCS_DTLSC_EXT.1 and omit them from FCS_DTLSC_EXT.2

I tend to agree with the proposed change, but we'd need to do a consistency check.
My guess (inferred from App Notes) as to why Elements 2 and 3 are in DTLSC_EXT.2 because DTLSC_EXT.1.1 was initially thought to be primarily for syslog (e.g., one way sending logs protected to a syslog server). NDcPPv2.2e App Note 63 says, "FCS_DTLSC_EXT.1 should only be used if the TOE transmits application-layer data to an external entity using a trusted channel provided by DTLS without receiving application data that needs to be protected." I believe there are other similar statements in 2.2e.
This always seemed like an odd restriction and NDcPPv3.0 no longer has a corresponding App Note, so I think the Elements should be moved.


Resize Image: Extension from contentType

Extension name: Resize-Images
This feature request is for extension: storage-resize-images
What feature would you like to see?
Currently, the file extension is being read from the original file name. If no file extension is provided, the type should be read from the image contentType to generate the new image.
Appending the extension to the resulting resized images should be conditional based on if the original name included the extension.
It is possible that this feature will solve issue 20. I experienced the same issue when I first uploaded files w/o extensions.
How would you use it?
Store images keyed off of a field in a db w/o having the manage the image file type.

XFN Team: This could either be implemented, or leave as-is with improved documentation explaining images to be resized must include an extension (e.g. `.png) in the filename.

Hey @GeeDollaHolla v0.1.3 should already fix the issue of reading the contentType from the original image (https://github.com/firebase/extensions/issues/20). We will work on fixing issue #20 which is a slightly different issue.Thanks for reporting!


Make angular injectable

This simply pulls the existing package into an injectable service.  The user would use like any other Angular service, calling the generate() method to create a unique id.  Also, organized the files into src and dist folders.  Hopefully presenting this as a service makes it easier to consume in existing Angular 2 projects.  see readme.md for usage.  Thanks.

@wulfsolter Is there any issues with this PR?
Was wondering why it's not merged yet?

Is there any improvements in performance in this approach? Curious to know?

No, I don't believe there is any performance benefit.  The main benefit, from my perspective, is the added ability to include the library in your project using the "angular way" (i.e. as an injected dependency).  Based on a few issues that I came across, people were confused about how to consume the library.  Ex. Issue 2 and Issue 6
I made sure to retain the option to import it into a typescript project (not necessarily angular) in the same way as before.
@msaiyaff


 You can also read Vitalik Buterin article on the question.
Some major technical improvement are needed before going to the moon !
To finish, the way you ask for things to get done won't help (the opposite could occur). All devs are volunteer, please be respectful, Do Only Good Every Day :)

We could achieve all of the above by changing the Dogecoin color to a nice shade of red. Red is the fastest color.

Red's an interesting idea :)

Interesting idea, issue #2024 seems to solve it.


Basic support for Events

The goal is to implement the most common events for a video player to improve its interactivity and facilitate integration with applications. The implemented events should adhere to industry standards and cover the most frequent use cases. With this we will be able to interact with the player, and even build plugins based on the events the Player triggers :D
moqplayer.addEventListener('play', () => {
    console.log('Video started playing');
});

We can use HTMLMediaElement Events documentation as a reference: https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement#events
Basic Playback Events:

waiting: Fired when playback has stopped because of a temporary lack of data.
loadeddata: Fired when the first frame of the media has finished loading.
play: Triggered when the video starts playing.
pause: Triggered when the video playback is paused.
ended: Triggered when the video reaches the end.
(nonstandard) adaptation:  Triggered when the player changes the rendered video or audio track. (see ShakaPlayer -> AdapationEvent  )
(nonstandard) catalogupdated: Triggered when the catalog is updated. (see ShakaPlayer -> ManifestUpdatedEvent)

User Interaction Events:

volumechange: Triggered when the user adjusts the volume.
fullscreenchange: Triggered when the user enters or exits fullscreen mode.

Player State Events:

loadedmetadata: Triggered when the video metadata (duration, dimensions, etc.) has been loaded.
timeupdate: Triggered periodically as the video plays, providing the current playback time.
error: Triggered when an error occurs during video playback.

Zafer: Suscribedone, subscribestared can also be imploemeted

pr here on @JoaquinBCh repo awaiting the merge of this pr


Wrong positioning due to long text wrapping

Hi,
First, great library, thanks for this!
I'm encountering a positioning bug with a textarea, probably due to some wrapping of long text (in my case, links).
Here is when it works:

And when it fails (AFTER the link pushed to a new line):

Any idea how to solve this?
PS: viewport is very wide, I just cropped the interesting part only, so it's not a repositioning of some sort.
Thanks!

@romaincointepas  please use Caret.js#master to check if it solve your problem. Then i will release a new hotfix version.

@ichord Tried using master of Caret.js, doesn't seem to fix the problem :/
You can reproduce (before your fix, production caret.js) here: http://www.twitshot.com/?text=Dribbble - Hixle Dashboard by Balraj Chana&url=https%3A%2F%2Fdribbble.com%2Fshots%2F1890201-Hixle-Dashboard (try typing @... right after the link).
BTW, I'm using Google Chrome 40, stable channel on OS X Yosemite.

I'm using the same browser( Chrome 40) and OS, It's how i saw by simulating your text.
There just one line text.

Let me have try on that link later, I can't access it now. (I'm in china, and the VPN is not working on my 3G router)

BTW. You can play around on http://ichord.github.com/Caret.js , I have updated it for that fix.
Basically, this is the problem of Caret.js; if Caret.js work fine, then At.js would be fine too.

I can't reproduce on At.js or Caret.js example pages. Waiting for your feedback when you can access twitshot.com (I've tried playing around css properties, like box-sizing, nothing).
Ah, other people can also reproduce (I wanted to make sure it wasn't just on my machine).

...... You might not be using the right Caret.js file, I download the whole page and just replace the min file and it work fine.

Please make sure you are using the newest one, which must have this codes https://github.com/ichord/Caret.js/commit/e575bdc16e3f253776198b369cbec419c478c55b
If the problem still exist (it can't be....), and you can't reproduce it on any demo page, please provide me a available demo.

@ichord My bad, it works (don't know what I did wrong the first time I tested).
Thank you for being this quick and sharp on fixing this!


Backdrop image issue in Tracks activity

    private void loadImage() {
        DbSingleton dbSingleton = DbSingleton.getInstance();
        Track current = dbSingleton.getTrackbyName(track);

        if (current.getImage().length() != 0) {
            Picasso.with(getApplicationContext()).load(current.getImage()).into(backdrop1);

        }
    }

According to Mario, we don't want to have any image inside tracksActivity backdrop.

Thanks, will remove it and send PR.

@the-dagger Also there is a FAB icon for sharing. I think we should also share that.

Yeah, moving that to toolbar was a good idea.
I had a look at that :)

Attached is the new look.


change while to if

I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License.
This while should never loop

@charlesgriffiths
Thank you for your contribution.
-Neil


npm login (after sending credentials)

Hi guys,
Can you take a look at the cmd console on a azure website running default version of node.js >=0.12.0.
I'm taking advantage of the new private npm service offered by npmjs.org. Using the latest npm-cli supporting login, I login using my credentials. Upon submitting the command, the console waits. Upon reloading the page, access to private npms works (because the login is successful). I'm sure it's a trivial fix on your side, just receive acknowledgement from the npm login command.
Thanks

I'm not quite following. Is this something you're doing in a git custom deployment script? Can give give more complete/precise steps to describe exactly what you are doing?

Sure, I'd be happy to show you. It's actually quite simple to reproduce.
Create a new Azure Web app. Within the site's configure settings, add within the application settings WEBSITE_NODE_DEFAULT_VERSION: 0.12.3
Restart the website and within your browser go to the Kudo manager debug console for your new site: https://.scm.azurewebsites.net/DebugConsole
Once you are here - within the command console type npm -v and verify npm is  version 2 or later. If so, type npm login
You will need to register for an account on npmjs.org to complete the following step. Upon entering your credentials, console remains idle. Test the same command on your local machine and cross-check the behavior. It will be obvious then.

Oh I see, you're doing this interactively in Kudu console. The problem is that Kudu console simulates a console, but is not a true console like you'd get with ssh. It works well for commands that do simple stdin/stdout, but for commands that deal with input in fancier way, it doesn't always work.
If there is any way you can pass the params directly on the npm command line, or maybe set environment variables for them before running the command, that might provide a workaround.

Yeah it's a very minor issue and only wanted to surface it.

Found a simple way of solving this. Just include a .npmrc within the project root directory. Details on storing credentials within this file or obtaining this file from your local system can be found here.


Automatically generate the digest of the base debian image

Added a program to fetch the latest debian image from GCR and parse the output to get the digest of the image.

PTAL


Common: publish Docker images for scala-stream-collector, beam-enrich and stream-enrich to Docker Hub

@jbeemster can you add the env vars to publish to Docker Hub, similarly to what have been done for Snowplow Micro here please?

Closing in favor of https://github.com/snowplow/snowplow/issues/4237


fix: Update Bitbucket SSH host key

https://bitbucket.org/blog/ssh-host-key-changes

related;
Had an issue where cloning resulted in:
level=fatal msg="artifact bitbucket-repository failed to load: failed to clone \"git@bitbucket.org:X/X.git\": ssh: handshake failed: knownhosts: key mismatch"

This started to occur after bitbucket added their keys as of 15th of May (blogpost). This would not happen if go-git was upgraded to >=5.5.0, as it includes a fix described here (https://github.com/go-git/go-git/issues/411)
I'm not sure why the go-git module is forked in argo-workflow (https://github.com/argoproj/argo-workflows/blob/c1c3a5a1fe47508da7bc2942dbee4763dccadcd6/go.mod#L260), but argo-cd uses the upstream version of go-git (https://github.com/argoproj/argo-cd/pull/11893). They have had similar problems (https://github.com/argoproj/argo-cd/issues/7723)

Thank you. For anyone else having the issue, the workaround is to mount the updated host keys in /etc/ssh/


Why not like Pyscript ?

hear the news from pyscript.net
We thinks the code need simple like <phpscript> </phpscript>

You can use <script type = "text/php">


LightningModule: predict_step has different signature than other steps

Outline & Motivation
In the documentation, (train|validation|test|predict)_step all accept the same arguments. However, they have very different function signatures. This makes it confusing to subclass as I need to be careful about using different type signatures for each step. Some consistency would be nice.
Pitch
All steps should be consistent. Either:
def *_step(self, *args: Any, **kwargs: Any) -> Optional[STEP_OUTPUT]:

or:
def *_step(self, batch: Any, batch_idx: int, dataloader_idx: int = 0) -> Any:

Personally I prefer the latter, as it makes it more clear what arguments will be passed and what types they can be.
Additional context
No response
cc @justusschock @awaelchli @carmocca @borda

Good catch. Yes, the predict_step signature needs an update.
However, to be technically correct, it has to be *args, **kwargs because it supports the def predict_step(dataloader_iter) flavor.


fix line endings in DorkBuild

The line-endings for the DorkBuild scripts were being set to CRLF on the CI when producing the DorkBuild package, which caused issues when using DorkBuild on non-Windows. This should ensure that the next DorkBuild build has the right line endings. It's a safe change because we use it on all of our other repos (and .sh should always use \n anyway)
/cc @victorhurdugaci

Apparently this is fixed in release.


fix: let keyboard control debug panel tabs

Description
The Pivot inside the DebugPanel was trying to make its internal Label text clickable instead of relying on its own built-in handling, which is properly a11yfied.
Task Item
fixes #6462
Screenshots

Coverage decreased (-0.01%) to 52.066% when pulling cbc11eb1ca50624db7e2262528212266230077d0 on beyackle/focusWebchatInspector into 1b44b1631f4aebdb2eff865ceec732e7551134e0 on main.


i3 module - Workspace names

Icons are shown correctly depending on workspace,
but the workspace %name% is not displaying.
tried to change workspace name to "terminal" instead of "1",
the size of the bar changed but the text still does not appear.
[module/i3]
type = internal/i3
format = <label-state> <label-mode>
pin-workspaces = true

ws-icon-0 = 1;
ws-icon-1 = 2;
ws-icon-2 = 3;
ws-icon-3 = 4;
ws-icon-4 = 5;
ws-icon-default = 

label-dimmed-underline = ${root.background}

label-focused = %icon%  %name%
label-focused-foreground = #f3f3f3
label-focused-background = #3f3f3f
;label-focused-underline = #${colors.accent}
label-focused-underline = #9f78e1
label-focused-font = 4
label-focused-padding = 4

label-unfocused = %icon%  %name%
label-unfocused-underline = #555555
label-unfocused-font = 4
label-unfocused-padding = 4

label-urgent = %icon%  %name%
label-urgent-foreground = #000000
label-urgent-background = #bd2c40
label-urgent-underline = #9b0a20
label-urgent-font = 4
label-urgent-padding = 4

label-visible = %icon%  %name%
label-visible-foreground = #55ffffff
label-visible-font = 4
label-visible-padding = 4

i3 - config
# Define names for default workspaces for which we configure key bindings later on.
# We use variables to avoid repeating the names in multiple places.
set $ws1 "1"
set $ws2 "2"
set $ws3 "3"
set $ws4 "4"
set $ws5 "5"
set $ws6 "6"
set $ws7 "7"
set $ws8 "8"
set $ws9 "9"
set $ws10 "10"

How are you renaming the workspaces? Works for me when doing it via i3-msg "rename workspace 1 to terminal".
Does i3bar show the new workspace name?

I was renaming them on i3 config & polybar config,
also i'm not using i3bar, i'm using a script to launch 2 bars a polybar-top & polybar-bottom
I've just switched to i3bar and
i3-msg "rename workspace 1 to terminal"
seems to work there, the name shows up..
But on my polybar-bottom text still not showing up,
the size changes, it looks like its there but it isn't,
also changed the background color thinking the font
might be the same colour but itś not :D

Does the issue persist even after you restart the bar?
Please run polybar with -l info and post the output here after you renamed the workspace and it didn't show up in polybar.
Can you also post a before and after picture so that I can see what is happening on your system, as I am unable to reproduce this.

Thanks for the fast reply, the problem seems to persist after restarting the bar..
Polybar bottom -l infoOutput
* Loaded /home/zemike/.config/polybar/config
* Loaded monitor eDP-1 (1366x768+0+0)
warn: The config parameter `bar/bottom.border-top` is deprecated, use `bar/bottom.border-top-size` instead.
* Bar geometry: 1366x30+0+738
error: Disabling module "bspwm" (reason: Could not find socket: /tmp/bspwm_0_0-socket)
* Starting application
* Starting module/i3
* Entering event loop (thread-id=1)
* Eventqueue worker (thread-id=3)
* Configured DPI = 96x96
* Loaded font "NotoSans-Regular:size=8" (name=Noto Sans, offset=0, file=/usr/share/fonts/noto/NotoSans-Regular.ttf)
* Loaded font "MaterialIcons:size=10" (name=Material Icons, offset=2, file=/usr/share/fonts/TTF/MaterialIcons-Regular.ttf)
* Loaded font "Termsynu:size=8" (name=Noto Sans, offset=0, file=/usr/share/fonts/noto/NotoSans-Regular.ttf)
* Loaded font "WunconSiji:pixelsize=10" (name=Wuncon Siji, offset=1, file=/usr/share/fonts/misc/siji.pcf)
* Loaded font "FontAwesome:size=10" (name=FontAwesome, offset=0, file=/usr/share/fonts/OTF/FontAwesome.otf)
* Loaded font "NotoSans Mono:size=8" (name=Noto Sans Mono, offset=0, file=/usr/share/fonts/noto/NotoSansMono-Regular.ttf)
* Bar window: 0x1000001
error: Failed to restack bar window
* Disabling tray manager (reason: missing `tray-position`)
* module/i3: Rebuilding cache
* Redrawing bar window
* module/i3: Rebuilding cache
* Redrawing bar window
* module/i3: Rebuilding cache
* Redrawing bar window
* module/i3: Sending workspace focus command to ipc handler
* module/i3: Rebuilding cache
* Redrawing bar window

Before i3-msg "rename workspace 1 to terminal"

After i3-msg "rename workspace 1 to terminal"

Also  tried to rename it to a larger name

Ah I see. Can you post your entire polybar config, I think the problem might not be in the i3 module itself but maybe you have a font issue or something to do with the colors.
What distro are you running?

I'm running Arch with i3 wm..
Polybar Config
;=====================================================
;
;   To learn more about how to configure Polybar
;   go to https://github.com/jaagr/polybar
;
;   The README contains alot of information
;
;=====================================================

[colors]
accent = #fba922

[bar/top]
enable-ipc = true
monitor = eDP-1
width = 100%
height = 27

;background = #222
;background = #1f1f1f
background = #cc000000
foreground = #eee

;border-bottom-color = #333
border-bottom = 1
border-bottom-color = #cc000000

overline-size = 10
overline-color = ${self.background}
underline-size = 10
underline-color = ${self.background}

padding-left = 0
padding-right = 0
module-margin-left = 3
module-margin-right = 3

font-0 = NotoSans-Regular:size=8;0
font-1 = MaterialIcons:size=10;2
font-2 = Termsynu:size=8;0
font-3 = WunconSiji:pixelsize=10;1
font-4 = FontAwesome:size=10;0
font-5 = NotoSans Mono:size=8;0

modules-left = powermenu mpd
modules-center = xwindow
modules-right = volume wireless-network wired-network battery clock

wm-restack = bspwm

tray-position = right

[bar/bottom]
monitor = eDP-1
bottom = true
width = 100%
height = 27

;background = #1c1c1
;background = #000f0f0fc
;default (background = #000f0f0f)
background = #cc000000
foreground = #eefafafa

overline-size = 3
overline-color = ${colors.accent}
underline-size = 3
underline-color = ${colors.accent}

;border-color = #ff0000
border-top = 3
;border-top-color = #3d3d3d
border-top-color = #cc000000
;border-bottom = 0
;border-bottom-color = #333333

spacing = 3
;padding-right = 4
padding-left = 0
padding-right = 0
module-margin-left = 0
module-margin-right = 6

font-0 = NotoSans-Regular:size=8;0
font-1 = MaterialIcons:size=10;2
font-2 = Termsynu:size=8;0
font-3 = WunconSiji:pixelsize=10;1
font-4 = FontAwesome:size=10;0
font-5 = NotoSans Mono:size=8;0

modules-left = bspwm i3
;modules-center =
;modules-right = memory
;modules-right = memory

wm-restack = bspwm

[bar/external]
enable-ipc = true
monitor = HDMI-1
bottom = true
;dock = true
width = ${bar/bottom.width}
height = ${bar/bottom.height}

background = ${bar/bottom.background}
foreground = ${bar/bottom.foreground}

underline-size = ${bar/bottom.underline-size}
underline-color = ${bar/bottom.underline-color}
overline-size = ${bar/bottom.overline-size}
overline-color = ${bar/bottom.overline-color}

border-bottom.= ${bar/bottom.border-bottom}
border-bottom.color = ${bar/bottom.border-bottom-color}

spacing = ${bar/bottom.spacing}
padding-left = ${bar/bottom.padding-left}
padding-right = ${bar/bottom.padding-right}
module-margin-left = 0
module-margin-right = ${bar/bottom.module-margin-right}

font-0 = ${bar/bottom.font-0}
font-1 = ${bar/bottom.font-1}
font-2 = ${bar/bottom.font-2}
font-3 = ${bar/bottom.font-3}
font-4 = ${bar/bottom.font-4}
font-5 = ${bar/bottom.font-5}

modules-left = bspwm i3
modules-center = xwindow
modules-right = fs-root clock

wm-restack = ${bar/bottom.wm-restack}

[module/fs-root]
type = internal/fs
mount-0 = /
label-mounted = %{F#e60053}%percentage_used%%%{F-} used of %mountpoint%

[module/xbacklight]
type = internal/xbacklight
output = eDP-1
format = <ramp> <bar>

ramp-0 = 
ramp-0-foreground = #666
ramp-1 = 
ramp-1-foreground = #999
ramp-2 = 
ramp-2-foreground = #fff

bar-width = 12
bar-indicator = |
bar-indicator-font = 6
bar-indicator-foreground = #bbffffff
bar-fill = ─
bar-fill-font = 6
bar-fill-foreground = #9f78e1
bar-empty = ─
bar-empty-font = 6
bar-empty-foreground = #44

[module/backlight]
type = internal/backlight
card = intel_backlight
format = <ramp> <label>
ramp-0 = 
ramp-1 = 
ramp-2 = 
ramp-foreground = #666
interactive = true

[module/i3]
type = internal/i3
format = <label-state> <label-mode>
pin-workspaces = true

ws-icon-0 = 1;
ws-icon-1 = 2;
ws-icon-2 = 3;
ws-icon-3 = 4;
ws-icon-4 = 5;
ws-icon-default = 

label-dimmed-underline = ${root.background}

label-focused = %icon%  %name%
label-focused-foreground = #f3f3f3
label-focused-background = #3f3f3f
;label-focused-underline = #${colors.accent}
label-focused-underline = #9f78e1
label-focused-font = 4
label-focused-padding = 4

label-unfocused = %icon%  %name%
label-unfocused-underline = #555555
label-unfocused-font = 4
label-unfocused-padding = 4

label-urgent = %icon%  %name%
label-urgent-foreground = #000000
label-urgent-background = #bd2c40
label-urgent-underline = #9b0a20
label-urgent-font = 4
label-urgent-padding = 4

label-visible = %icon%  %name%
label-visible-foreground = #55ffffff
label-visible-font = 4
label-visible-padding = 4

[module/bspwm]
type = internal/bspwm
format = <label-state> <label-mode>

ws-icon-0 = 1;
ws-icon-1 = 2;
ws-icon-2 = 3;
ws-icon-3 = 4;
ws-icon-4 = 5;
ws-icon-default = 

label-dimmed-underline = ${root.background}

label-focused = %icon%  %name%
label-focused-foreground = #f3f3f3
label-focused-background = #3f3f3f
;label-focused-underline = ${colors.accent}
label-focused-underline = #9f78e1
label-focused-font = 4
label-focused-padding = 4

label-occupied = %icon%  %name%
label-occupied-underline = #555555
label-occupied-font = 4
label-occupied-padding = 4

label-urgent = %icon%  %name%
label-urgent-foreground = #000000
label-urgent-background = #bd2c40
label-urgent-underline = #9b0a20
label-urgent-font = 4
label-urgent-padding = 4

label-empty = %icon%  %name%
label-empty-foreground = #55ffffff
label-empty-font = 4
label-empty-padding = 4

[module/memory]
type = internal/memory
interval = 0.2
format = <label> <bar-used>

label = RAM
label-font = 3
label-foreground = #99

bar-used-width = 30
bar-used-gradient = true
bar-used-foreground-0 = #449f3d
bar-used-foreground-1 = #2f8419
bar-used-foreground-2 = #f5a70a
bar-used-foreground-3 = #ed5456
bar-used-indicator = █
bar-used-indicator-font = 5
bar-used-indicator-foreground = #fff
bar-used-fill = █
bar-used-fill-font = 5
bar-used-empty = █
bar-used-empty-font = 5
bar-used-empty-foreground = #44

[module/wireless-network]
type = internal/network
interface = wlp1s0
interval = 2.0
ping-interval = 10

format-connected = <ramp-signal> <label-connected>
label-connected = %essid%
label-disconnected =    not connected
label-disconnected-foreground = #66

ramp-signal-0 = 
ramp-signal-1 = 
ramp-signal-2 = 
ramp-signal-3 = 
ramp-signal-4 = 

animation-packetloss-0 = 
animation-packetloss-0-foreground = #ffa64c
animation-packetloss-1 = 
animation-packetloss-1-foreground = ${bar/top.foreground}
animation-packetloss-framerate = 500

[module/wired-network]
type = internal/network
interface = net0
interval = 2.0

label-connected =   %local_ip%
label-disconnected = Ethernet disconnected
label-disconnected-foreground = #66

[module/mpd]
type = internal/mpd
format-online = <bar-progress>  <icon-prev> <icon-stop> <toggle> <icon-next>  <label-song>
format-online-overline = ${root.background}
format-online-underline = ${root.background}
format-offline = <label-offline>
label-offline = mpd is off

icon-play = 
icon-pause = 
icon-stop = 
icon-prev = 
icon-next = 
icon-random = 
icon-repeat = 

toggle-on-foreground =
toggle-off-foreground = #55

bar-progress-width = 45
bar-progress-format = %{+o +u}%fill%%{-o -u}%indicator%%{+o +u}%empty%%{-u -o}
; bar-progress-indicator = |
bar-progress-indicator = █
bar-progress-indicator-foreground = #ff
bar-progress-indicator-font = 3
; bar-progress-fill = ─
bar-progress-fill = █
bar-progress-fill-foreground = #bb
bar-progress-fill-font = 3
; bar-progress-empty = ─
bar-progress-empty = ▒
bar-progress-empty-font = 3
bar-progress-empty-foreground = #44

[module/clock]
type = internal/date
interval = 5
format-padding = 5
;format-background = #000
format-background = #cc000000
format-foreground = #fff
date = %%{F#bb}%Y-%m-%d%%{F-}  %%{F#ee}%H:%M%%{F-}

[module/volume]
type = internal/volume
speaker-mixer = Speaker
headphone-mixer = Headphone
headphone-id = 9

format-volume = <ramp-volume> <label-volume>

label-volume = volume %percentage%%
label-volume-foreground = #ff

format-muted-prefix = " "
format-muted-foreground = #66
label-muted = sound muted
label-muted-foreground = #99ffffff

ramp-volume-0 = 
ramp-volume-1 = 
ramp-volume-2 = 
ramp-volume-3 = 
ramp-volume-foreground = #9f78e1

ramp-headphones-0 = 
ramp-headphones-1 = 
ramp-headphones-foreground = #9f78e1

[module/battery]
type = internal/battery
full-at = 98
format-charging = %{T3}Battery <label-charging> %{T-}
format-discharging = %{T3}Battery <label-discharging> %{T-}
;format-full = %{T3}Battery <label-full>
label-charging-font = 3
label-discharging-font = 3
label-full =
;label-full-font = 3

[module/xwindow]
type = internal/xwindow
label-maxlen = 75
label-foreground = #bbb

[module/powermenu]
type = custom/menu

format-padding = 3
format-background = #000
format-foreground = #fff

label-open = 
label-close = i
label-separator = " - "

;menu-0-0 = Terminate WM
;menu-0-0-foreground = ${colors.accent}
;menu-0-0-exec = bspc quit -1
;menu-0-1 = Reboot
;menu-0-1-foreground = ${colors.accent}
;menu-0-1-exec = menu-open-1
;menu-0-2 = Power off
;menu-0-2-foreground = ${colors.accent}
;menu-0-2-exec = menu-open-2

;menu-1-0 = Cancel
;menu-1-0-foreground = ${colors.accent}
;menu-1-0-exec = menu-open-0
;menu-1-1 = Reboot
;menu-1-1-foreground = ${colors.accent}
;menu-1-1-exec = sudo reboot

;menu-2-0 = Power off
;menu-2-0-foreground = ${colors.accent}
;menu-2-0-exec = sudo poweroff
;menu-2-1 = Cancel
;menu-2-1-foreground = ${colors.accent}
;menu-2-1-exec = menu-open-0

menu-0-0 = reboot
menu-0-0-exec = menu-open-1
menu-0-1 = power off
menu-0-1-exec = menu-open-2

menu-1-0 = cancel
menu-1-0-exec = menu-open-0
menu-1-1 = reboot
menu-1-1-exec = sudo reboot

menu-2-0 = power off
menu-2-0-exec = sudo poweroff
menu-2-1 = cancel
menu-2-1-exec = menu-open-0

; vim:ft=dosini

The problems are these lines:
label-focused-font = 4
...
label-unfocused-font = 4
...
label-urgent-font = 4
...
label-visible-font = 4

Those point to font-3 which is siji and siji doesn't have any character or number glyphs. And the way the prefered font works in polybar, is that during rendering the prefered font gets swapped with the first font in the list and since siji doesn't have those glyphs the next font is used, which is MaterialIcons, and for some reason it overrides the glyphs for the numbers and small letters with empty glyphs and so they aren't rendered, if you actually changed the workspace name to something with an upper-case letter, you would only see the upper case letters.
There are a few things you can do, either wrap the icons in the %{T4}...%{T-} tag, so that only the icon is rendered using that font, rearrange the fonts so that MaterialIcons can't override lower-case letters and numbers.


Weird disparity values being published in stereo_node

Hello,
I am trying to retrieve a disparity image from the stereo_node publisher with mode != depth, and the values observed, be it from a subscriber to .../stereo/disparity or with a rostopic echo .../stereo/disparity, seem off:
most are 0 with some integer values scattered everywhere. I checked that the disparity image obtained directly from the device with a getFrame call does not produce these values but "proper values" ranging between 1 and 255.
Also, I noticed with rostopic echo that the delta_d attribute of the published DisparityImage is 0.0, whereas the source code for the DisparityConverter seems to produce values that are either 1 or 1/32.
Could these two observations be related ?
Thanks in advance

Sorry for the issue. We are looking into it.

Hi, can you try to turn subpixel off? As for the delta error, it was a cast bug, it will be merge into main soon, if you need it fixed now you can try this branch for the depthai-ros repo: https://github.com/luxonis/depthai-ros/tree/daxoft/fix_disparity

@psFournier  Can you check this viewer to verify ? the image looks good to me,
 rosrun image_view disparity_view image:=/stereo_publisher/stereo/disparity

Same me I think, but I didn't make test. Just black disparity with
normalised ticked or not. ROS2 warp branch
On Thu, 14 Apr 2022, 18:06 Sachin Guruswamy, @.***>
wrote:

Sorry for the issue. We are looking into it.
—
Reply to this email directly, view it on GitHub
https://github.com/luxonis/depthai-ros-examples/issues/36#issuecomment-1099417795,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AITQOVGKIZYR5O2PRHOAR7DVFBGB3ANCNFSM5TKL6JMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Error when install Pace.javascript package from nuget

Hi, guys
I have ASP.NET MVC project with target framework 4.6.1 in Visual Studio 2015 Comunity Edition
I'm trying to install Pace.javascript package from nuget by command
Install-Package Pace.javascript
The installation failed with error:

Install-Package : Could not install package 'Pace.javascript 1.0.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.6.1', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
At line:1 char:1

Install-Package Pace.javascript

  + CategoryInfo          : NotSpecified: (:) [Install-Package], Exception
  + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand

Could you please help to fix the issue?
Thank you in advacne

Yes. I'm facing the same. Below is the error I got.
Could not install package 'Pace.javascript 1.0.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Please do needful.
Thank you in advance.


added logger msgs in ROS2 Jazzy

No need. Just being ported over from ROS1. I removed everyone but forgot to finalize the merge.


Show .NET Core version

Please show what version you are running on, down to the revision level. This can help with bug repros and the like. (And maybe one day you will haev a selection)

but of course you can write some C# code that will run dotnet --version for you :) I suspect this explicit feature is a ways off, but that's a nice shortcut.


About Dynerf dataset

Hello, you tested multiple data sets in the paper, but I didn’t find the relevant processing code of dynerf in the project. Will they be added in the future?

Not an author but here's what worked for me to preprocess. To train just do -s (dynerf path)
`import os
import cv2
data_path = "data/dynerf/sear_steak/"
Create a VideoCapture object and read from input file
cams = []
for i in range(21):
name = data_path + "cam" + str(i).zfill(2)
cam = cv2.VideoCapture(name + ".mp4")
try:
    os.mkdir(name)
    outpath = os.path.join(name, "images/")
    os.mkdir(outpath)
except:
    continue

if (cam.isOpened()== False):
    print("Error opening video stream or file")

# Read until video is completed
j = 0
while True:
    ret, frame = cam.read()

    if ret == True:
        frame = cv2.resize(frame, (1352, 1014), interpolation=cv2.INTER_AREA)
        cv2.imwrite(outpath + "/" + str(j).zfill(4) + ".png", frame)
        j += 1
    else:
        break

print(f"Done with {name}")

`

Not an author but here's what worked for me to preprocess. To train just do -s (dynerf path)
import os
import cv2

data_path = "data/dynerf/sear_steak/"

# Create a VideoCapture object and read from input file
cams = []

for i in range(21):
    name = data_path + "cam" + str(i).zfill(2)
    cam = cv2.VideoCapture(name + ".mp4")

    try:
        os.mkdir(name)
        outpath = os.path.join(name, "images/")
        os.mkdir(outpath)
    except:
        continue

    if (cam.isOpened()== False):
        print("Error opening video stream or file")

    # Read until video is completed
    j = 0
    while True:
        ret, frame = cam.read()

        if ret == True:
            frame = cv2.resize(frame, (1352, 1014), interpolation=cv2.INTER_AREA)
            cv2.imwrite(outpath + "/" + str(j).zfill(4) + ".png", frame)
            j += 1
        else:
            break

    print(f"Done with {name}")

Thank you very much for your reply, I will try it ！

Hi, We have already supported DyNeRF.
However, I emphasized monocular in the title, because the majority of multi-view datasets are essentially sparse. Around 20 viewpoints are sparse for 3D-GS, and that's why Lego's convergence in the D-NeRF dataset is the worst. Therefore, I believe that using GS-based methods for multi-view has no advantages compared to IBR-based methods like ENeRF, im4d, and 4k4d. Of course, an extreme point cloud initialization in 4d-gaussian-splatting can help alleviate this issue.
From my perspective, I would recommend this method more for monocular datasets.

I tested multi-view and monocular data at the same time, and the results were very different. The monocular data had very good performance, while the multi-view data (dynerf-cook_spinach) had poor results and no clear images were generated. The initialization point cloud I used here is Obtained from the first frame of colmap.
I can understand that multi-view data cannot reach the quality of monocular, but why is the quality so poor that it is completely impossible to see the content clearly?

I believe there are two reasons.

The number of viewpoints. Cook-Spanish has only about 20 training viewpoints, while D-NeRF and other real-world monocular datasets have rich training viewpoints. This affects the geometric convergence of GS, leading to depth estimation errors and resulting in poor rendering results.
The coverage range of viewpoints. A noteworthy detail is that the official dataset for 3D-GS is also 360 viewpoints. D-NeRF is 360, Nerf-DS is 90-180, and the coverage range of viewpoints also affects the convergence of depth. In situations where training cannot ensure accurate depth, satisfactory results can only be obtained through better initialization, but this is too tricky.

Another observed phenomena in the experiments is that if 3D-GS can converge, the deformable-GS will converge as well. You can pay attention to the next version of the paper; I have already submitted the updated version to arXiv.

Thanks Reply.
Looking forward to your new paper.

I believe there are two reasons.

The number of viewpoints. Cook-Spanish has only about 20 training viewpoints, while D-NeRF and other real-world monocular datasets have rich training viewpoints. This affects the geometric convergence of GS, leading to depth estimation errors and resulting in poor rendering results.
The coverage range of viewpoints. A noteworthy detail is that the official dataset for 3D-GS is also 360 viewpoints. D-NeRF is 360, Nerf-DS is 90-180, and the coverage range of viewpoints also affects the convergence of depth. In situations where training cannot ensure accurate depth, satisfactory results can only be obtained through better initialization, but this is too tricky.

Another observed phenomenon in the experiments is that if 3D-GS can converge, the deformable-GS will converge as well. You can pay attention to the next version of the paper; I have already submitted the updated version to arXiv.
My experiment results on the DyNeRF dataset (300 frames) are shown as follows:
Test PSNR	Best iteration
sear-steak	33.239/36.7357	20k
coffee-martini	27.072/34.1954	10k
flame-steak	33.169/32.8128	33k
cut-beef	32.803/34.8096	20k
cook-spanish	32.803/34.3375	28k
flame-salmon	26.938/28.75(oom)	6k
Sparse viewpoints can result in overfitting on the training set.

A preview version if you don't mind.

I believe there are two reasons.

The number of viewpoints. Cook-Spanish has only about 20 training viewpoints, while D-NeRF and other real-world monocular datasets have rich training viewpoints. This affects the geometric convergence of GS, leading to depth estimation errors and resulting in poor rendering results.
The coverage range of viewpoints. A noteworthy detail is that the official dataset for 3D-GS is also 360 viewpoints. D-NeRF is 360, Nerf-DS is 90-180, and the coverage range of viewpoints also affects the convergence of depth. In situations where training cannot ensure accurate depth, satisfactory results can only be obtained through better initialization, but this is too tricky.

Another observed phenomenon in the experiments is that if 3D-GS can converge, the deformable-GS will converge as well. You can pay attention to the next version of the paper; I have already submitted the updated version to arXiv.
My experiment results on the DyNeRF dataset (300 frames) are shown as follows:
Test PSNR	Best iteration
sear-steak	33.239/36.7357	20k
coffee-martini	27.072/34.1954	10k
flame-steak	33.169/32.8128	33k
cut-beef	32.803/34.8096	20k
cook-spanish	32.803/34.3375	28k
flame-salmon	26.938/28.75(oom)	6k
Sparse viewpoints can result in overfitting on the training set.

Are there any special parameters when you train cook-spanish?
I extracted 300 frames from each video for training. The camera parameters used the official npy file, points3D.ply generated by colmap.
The psnr I trained is not as high as what you tested.

Of course, reducing the number of frames can increase PSNR. However, I believe the inherent reason why GS-based methods struggle with multi-view datasets is that 3D-GS relies more on rich viewpoints compared to Nerf (a common issue in point-based rendering), rather than on point cloud initialization or frame length (indeed, it's challenging to achieve long-capture based on the deformation field).
If someone can address the ability of 3D-GS to model sparse scenes effectively, I believe our method can model multi-view scenes without relying on tricks.


Update UiaOperationAbstraction.h

This PR add the Try/Catch helpers in UiaOperationAbstraction wrappers. It also add a helper for GetCurrentFailureCode.

Can we change the title of this PR to be more descriptive?

/azp run

@zhayuli do you have any more feedback before we merge this in?

@zhayuli do you have any more feedback before we merge this in?

LGTM.

@mavangur permission to merge?

Sure Ben. Please go ahead. Thank you. :)

@zhayuli Thanks Zhaoyu :)


Allow gh-pages to be previewed locally

Everyone should be able to see their changes to this branch without having to push to GitHub.  This oughtta do it per these instructions.
Try it out:

Pull down this branch,
Make sure you're running ruby >= 2.0.0
Run bundle install
Run bundle exec jekyll serve
Profit?

Awesome thanks @iamEAP! LGTM.


Toolkit crashes after launch

I am using the binary available at http://www.healthintersections.com.au/FhirServer/ release v0.0.46 2018-09-27.
It tells me to install the base package via package manager, but immediately after closing this message window the program exits with the following error:

Same for R4

is this OSX or windows?

Same issue on Windows 10, both R4 and R3 crash out.

Fixed with v0.0.48


Add test for bridge flags for enabling and disabling flooding on ports.

Tests that flooding behaves as intended when both enabled and disabled, for both unicast and multicast.
Minor correction of a comment.

No particular reason for the IPv4 multicast. I needed a multicast address and I made one :). Now I've switched to your suggestion. Also split up the correction into another commit.


Add Endpoint for Leverage Ratio

Which endpoint you are willing to add?
Endpoint to calculate Leverage ratio
Reference formula for the calculation.
There are two forumulas to calculate leverage ratio

and

Name of the endpoint you want to suggest.
/leverage_ratio_income : to calculate using first formula
/leverage_ratio_equity: to calucalate using second

Looks god, go ahead and make a PR.


Added data package search functionlity for publisher - refs #211, #198

@Fak3 will you get a chance to review this in the next 24h? If not I'll have a go.

I can review this saturday evening

Looks good now. Merging.


Fixing PHP-ML link

Hey @ziadoz
just fixing a link here...
Cheers!

@spekulatius Thanks!

No worries @ziadoz  :+1:

Btw @ziadoz, let me know if you need help maintaining the repo - happy to help out :+1:


Reordered Trainer doc page for intuitive browsing.

What does this PR do?
Reordered sections in Trainer doc page for intuitive browsing (mostly alphabetical).

limit_train_batches section was far down the page, away from train_test_batches and train_val_batches.
log_every_n_steps was between sections starting with r- and s-

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
It's my first pull request into a public repo! Although it's just docs I hope to contribute more into the future :)

I have checked that no section was not lost :]

I have checked that no section was not lost :]


Accept str and torch.device in device handling; add unittests

Eventually we should add a few more unit-tests for the device handling and update the type annotations so that both strs and torch devices are allowed. I will take care of this later.
Originally posted by @constantinpape in https://github.com/computational-cell-analytics/micro-sam/pull/245#pullrequestreview-1696685811

This has been implemented in #251 and #280.


onChange event

fire another event, when resize coords completed?
Anyway to do it?

Not currently, but would be easy to add.
On Tuesday, 9 August 2016, kobiak<EMAIL_ADDRESS>wrote:

fire another event, when resize coords completed?
Anyway to do it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/davidjbradshaw/image-map-resizer/issues/42, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAkHEpWFkw6lVQ68J6g4EpX7Ch4kWQHYks5qd_TrgaJpZM4JfryM
.

--
Sent from my iPhone.

it will be nice to have this added :)


Wikiprojects parser sanity tests

Add tests for methods used by WikiProjects parser
Add testfiles/ with sample wikitext containing WikiProjects for comparison in tests
Modify parser from iterative to recursive
Minor improvements to regexes

Generally, I'm concerned that the WikiProjectsParser constructs a session in it's init and that the host/URL for the WikiProject page is hard coded in that method.  It doesn't seem like the class is performing a very useful function here.  It would be better to have a pattern like:
def extract_directory(session, directory_page="Wikipedia:WikiProject..."):
    ...

def parse_section(section_text):
    ...

def parse_section_intro(intro_text):
    ...

def parse_wikiproject_table(table_text):
    ...

session = mwapi.Session(...)

print(extract_directory(session))

Then you'd write tests for parse_section() but not extract_directory which would only be responsible for making calls to the api iteratively.
In the end, this works.  I'd like to, at minimum, get it pep8 compliant before we merge.  We can worry about a restructuring later.

This looks good!  I ran flake8 and it found a few more pep8 glitches, report is attached.
pep8.txt

Thanks Adam! for your suggestions regarding flake8.


manager manifest in OCP flotta operator release v.0.0.1 points to the wrong image

The image value in release 0.0.1 of the flotta operator for OCP points to the wrong image value:
image: controller:latest
The correct value should be:
image: quay.io/project-flotta/flotta-operator as it is shown in the K8s manifest.

Flotta operator v0.1.0 was released last week and should be considered the first supported release.
The prior draft release was removed.


💡 [Caching] - Enable Use of Cookie

We are currently using local storage...... so want to migrate to cookies. Main Aim is to increase speed.

Hi @anmode, I would like to work on this issue under Gssoc'23. Please assign it to me.

that's cool!

Are you sure? you can do this? this is hard one and also level 3

Yes, I previously worked with cookies. I think I can do that.

@archiejain28 ?

Hi @anmode,
Sorry for the delay. I am available now.
I can connect once you are free to understand the requirements better.

@archiejain28 update us please?

Hi @Abhinavcode13 , I already discussed the updates with Anmol.
@anmode Opened the PR, please review.


Update UI screenshot

For #73.

Codecov Report

Merging #74 (e31b2a5) into master (70644bb) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #74   +/-   ##
=========================================
  Coverage     66.70%   66.70%
  Complexity      538      538
=========================================
  Files            95       95
  Lines          1817     1817
  Branches        211      211
=========================================
  Hits           1212     1212
  Misses          535      535
  Partials         70       70

Continue to review full report at Codecov.

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


Deeplink Integration

Summary

The mobile app did could not be launched from an external application.
Changelog

[General] [Add] - Add deeplinking support for iOS and Android
[General] [Add] - Added deeplink support for executing a custom search query for the maps tab
[General] [Add] - Transition to map tab if a certain class of deeplink queries is executed (deeplinking.searchmap)
[General] [Add] - Listener if a deeplink has been received
Test Plan

Tested on iOS and Android by creating dummy web page that linked to "campusmobile://deeplinking.searchmap?query=covid". Clicking on this link caused the UC San Diego mobile app to open to the maps tab where the query had already been searched for. This query can be changed to include any search query. Note: Only when clicking on the deeplink from an in-app Safari ViewController (iOS only), the expected behavior happens underneath the VC. When the user closes the in-app safari view, they will be at the maps tab as expected.

I tested using the apk download for android. For iOS, the build was unavailable on TestFlight, so I pulled a PR branch that Charles created that had experimental merged with it: https://github.com/c3bryant/campus-mobile/pull/new/pr-1192-testing
Dummy webpage for deeplinking (links to covid test, parking, Geisel): https://mobile.ucsd.edu/replatform/v1/qa/webview/mihir-test/dummy_deeplink.html
Notes on Android and iOS:
Deep linking/maps search only occurs when user has app open to the home tab.

If user is on the maps, notification, or profile tab of app, clicking on the dummy webpage link does not perform search on query, but rather the app just stays in the same state as before the link was clicked.

ex) if user has 'covid test kits' searched up on maps tab, if they click the link to direct to 'parking' on dummy webpage, then the user gets taken to the app, however it remains in the previous state of the 'covid test kits' search (no new search performed).
ex) if user has the notifications tab open, and clicks link to direct to 'parking' on webpage, then user is brought back to the notifications page and no search occurs.

If the app is completely closed, clicking on the link causes app to open and stay on home tab without any searches.

Notes only on iOS:

Logout using profile tab causes this error and webview doesn't show up on app:

A non-null String must be provided to a Text widget.
'package:flutter/src/widgets/text.dart':
Failed assertion: line 370 pos 10: 'data != null'
The relevant error-causing widget was:
WebViewContainer file:///Users/sonikaram/development/campus-mobile/lib/ui/home/home.dart:154:13

I tested using the apk download for android. For iOS, the build was unavailable on TestFlight, so I pulled a PR branch that Charles created that had experimental merged with it: https://github.com/c3bryant/campus-mobile/pull/new/pr-1192-testing
Dummy webpage for deeplinking (links to covid test, parking, Geisel): https://mobile.ucsd.edu/replatform/v1/qa/webview/mihir-test/dummy_deeplink.html
Notes on Android and iOS:
Deep linking/maps search only occurs when user has app open to the home tab.

If user is on the maps, notification, or profile tab of app, clicking on the dummy webpage link does not perform search on query, but rather the app just stays in the same state as before the link was clicked.

ex) if user has 'covid test kits' searched up on maps tab, if they click the link to direct to 'parking' on dummy webpage, then the user gets taken to the app, however it remains in the previous state of the 'covid test kits' search (no new search performed).
ex) if user has the notifications tab open, and clicks link to direct to 'parking' on webpage, then user is brought back to the notifications page and no search occurs.

If the app is completely closed, clicking on the link causes app to open and stay on home tab without any searches.

Notes only on iOS:

Logout using profile tab causes this error and webview doesn't show up on app:

A non-null String must be provided to a Text widget.
'package:flutter/src/widgets/text.dart':
Failed assertion: line 370 pos 10: 'data != null'
The relevant error-causing widget was:
WebViewContainer file:///Users/sonikaram/development/campus-mobile/lib/ui/home/home.dart:154:13

The app should now receive deeplinks from all views in the app (home, maps, notifications, and profile). I tested this extensively in a iOS simulator and on-device for Android (Samsung Galaxy S6).
As far as the iOS-specific profile logout issue, I was not able to reproduce this in a simulator or on-device.
The changes to the PR should be ready for further testing.


The memory of Primary process keep increasing

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[ ] 3.1
[ ] 3.2
[x] 3.3
[ ] self-compiled devel branch

Mode:

[x] Cluster
[x] Single-Server

Storage-Engine:

[ ] mmfiles
[x] rocksdb

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[ ] Linux

[ ] Debian .deb
[ ] Ubuntu .deb
[ ] SUSE   .rpm
[ ] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[ ] docker - official docker library
[x] other: CentOS7

[ ] Windows, version:
[ ] MacOS, version:

I want to control the total memory the ADB uses, so I set below parameters:
--cache.size<PHONE_NUMBER> \
--rocksdb.block-cache-size<PHONE_NUMBER> \
--javascript.v8-max-heap 1024

If I run ADB in single-server mode, it works. The single process uses about only 3G memory. But if I run ADB in cluster mode, the setting seems useless. The primary db process uses 7G memory（90% of my total memory) and keep increasing.
How I can control the total memory in cluster mode?

I try to insert 5000000 documents, and then recurrently insert the same 5000000 documents, the memory keeps increasing too.

As discussed in https://github.com/arangodb/arangodb/issues/11577 exposing more options of rocksdb to the commandline seems to ease the memory situation.
Namely:

--rocksdb.cache-index-and-filter-blocks-with-high-priority
--rocksdb.pin-l0-filter-and-index-blocks-in-cache
--rocksdb.pin-top-level-index-and-filter

These have been added to the now released ArangoDB 3.7 - hence closing this.


Delete operators/appsody-operator

Signed-off-by: Leo Christy Jesuraj<EMAIL_ADDRESS>Appsody Operator is no longer supported and should be removed.
Appsody sunset: https://appsody.dev/blogs/DevelopmentEnded
Proof of ownership:

I am a primary contributor to this operator and I am also listed as a maintainer in the latest ClusterServiceVersions: https://github.com/k8s-operatorhub/community-operators/blob/f8bbaabc02ebffb5b09e40e2d3a9306fca3a1f87/operators/appsody-operator/0.6.0/manifests/appsody-operator.v0.6.0.clusterserviceversion.yaml#L317-L318

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

/merge possible


updated webpack to latest version

some configuration changed in latest beta-version:
** loaders are now rules
** eslint is now in LoaderOptionsPlugin

Coverage increased (+8.2%) to 23.182% when pulling 6284deed9f91c234447cea46550f2e1f82a7a126 on webpack-eslint into e1299357c127e82f1eb6cbef818f52da617b8569 on master.


Can't extract assets from Lose the Heat 2

Doubt I'm going to hear anything since this project appears to be abandoned but here goes. When I go to decompile Lose the Heat 2 with D12, I'm first greeted with a script error and no other information. I clicked yes. Then the file prompt appeared twice. Then when I went to extract the assets, it complained that the Physics Xtra was missing, and the program quit without any warning or error message.

Managed to get it to output a log. It keeps generating an illegal CSV file which crashes Shockwave. Even if I only extract sounds (which is what I'm looking to extract)
The error is Failed to open file. Reason: Bad file name, Path: -2147483645Casts.csv

Not abandoned, I just haven't had time to work on it! Please attach a zip file containing all of the files you were trying to extract from, and I'll take a look at some point in the future

About the script error and file prompt appearing twice, I noticed that bug recently too. It only occurs on my laptop, not my desktop that I normally use for development. I still need to investigate that too.

Not abandoned, I just haven't had time to work on it! Please attach a zip file containing all of the files you were trying to extract from, and I'll take a look at some point in the future

lose_the_heat_2.zip
Here are the files. I fetched them from Flashpoint, a preservation project. I'm also on Windows 11, so I may need to use Windows XP in a VM for proper compatibility if that's the case. And when the program quits, no files are even dumped. I just get a log which is often blank. Even if I tell it to only extract audio. Decompiling it back to a DIR using ProjectorRays results in the same outcome; Shockwave complains about a missing Xtra followed by crash to desktop. I'm glad this is still being worked on. Shockwave is about as rippable as Lego Island's SI files.

@n0samu , small update. I was able to extract the assets to the game just fine under a Windows XP VM. The cast ripper did not complain about missing Xtras or generate an illegal CSV file. I suspect Windows 11 may have broke the utility.

Okay I'll look into it asap. I hope it is not a Windows 11 issue because I don't have that to test. Though I may update to it soon.

Okay I'll look into it asap. I hope it is not a Windows 11 issue because I don't have that to test. Though I may update to it soon.

I actually thank you for making this utility standalone. It's much easier to use, even if the rips are incomplete (right now) and is a bit buggy and I'm forced to use Windows XP.