text:
Failed to download Bazel This could be a target path issue.

When I try to just open and sync your example project, I have error
I have Mac Os High Sierra and installed Bazel
Caused by: java.lang.RuntimeException: Failed to download Bazel to /Users/olegBorisenkov/.bazel-leaf/bazel-leaf-master/bazel! This could be a target path issue.
	at com.spotify.gradle.bazel.tasks.DownloadBazelTask.download(DownloadBazelTask.java:119)
	at com.spotify.gradle.bazel.BazelLeafPlugin.checkIsBazelBinaryValid(BazelLeafPlugin.java:234)
	at com.spotify.gradle.bazel.BazelLeafPlugin.apply(BazelLeafPlugin.java:98)
	at com.spotify.gradle.bazel.BazelLeafPlugin.apply(BazelLeafPlugin.java:50)

Caused by: java.net.ConnectException: Operation timed out (Connection timed out)

in local.properties:
bazel.bin.path=/path/to/bin/bazel
Replace /path/to/bin/bazel with the path to your installed bazel bin.

I add bazel.bin.path and got new error

Got process exit code 1 when running bazel BazelExec: [/Users/olegBorisenkov/.bazel/bin/bazel, build, --curses=no, --color=no, --experimental_ui=no, --progress_in_terminal_title=no, --symlink_prefix=/Users/olegBorisenkov/Desktop/bazel-leaf-master/build/bazel-build/, //andlib:aarbin, --output_groups=noop, --aspects, build/bazel_aspects/__andlib/get_rule_kind.bzl%print_aspect]

org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':andlib'.
	at org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:109)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.onAfterEvaluateFailure(LifecycleProjectEvaluator.java:105)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.notifyAfterEvaluate(LifecycleProjectEvaluator.java:87)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:72)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.access$100(LifecycleProjectEvaluator.java:37)
	at org.gradle.configuration.project.LifecycleProjectEvaluator$ConfigureProject.run(LifecycleProjectEvaluator.java:125)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:317)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:309)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:185)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:97)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:52)
	at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:677)
	at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:138)
	at org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:35)
	at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:62)
	at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:41)
	at org.gradle.initialization.DefaultGradleLauncher$ConfigureBuild.run(DefaultGradleLauncher.java:262)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:317)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:309)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:185)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:97)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
	at org.gradle.initialization.DefaultGradleLauncher.configureBuild(DefaultGradleLauncher.java:175)
	at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:132)
	at org.gradle.initialization.DefaultGradleLauncher.getConfiguredBuild(DefaultGradleLauncher.java:110)
	at org.gradle.internal.invocation.GradleBuildController$2.call(GradleBuildController.java:86)
	at org.gradle.internal.invocation.GradleBuildController$2.call(GradleBuildController.java:83)
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:152)
	at org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks(StopShieldingWorkerLeaseService.java:38)
	at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:96)
	at org.gradle.internal.invocation.GradleBuildController.configure(GradleBuildController.java:83)
	at org.gradle.tooling.internal.provider.runner.ClientProvidedBuildActionRunner.run(ClientProvidedBuildActionRunner.java:70)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.run(RunAsBuildOperationBuildActionRunner.java:47)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:317)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:309)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:185)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:97)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:43)
	at org.gradle.tooling.internal.provider.SubscribableBuildActionRunner.run(SubscribableBuildActionRunner.java:51)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:50)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:46)
	at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:65)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:46)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:32)
	at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:39)
	at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:25)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:80)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:53)
	at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:62)
	at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:34)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25)
	at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43)
	at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:59)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:31)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:59)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:44)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:46)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:30)
	at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)
	at org.gradle.util.Swapper.swap(Swapper.java:38)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:62)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:82)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
	at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: java.io.IOException: Got process exit code 1 when running bazel BazelExec: [/Users/olegBorisenkov/.bazel/bin/bazel, build, --curses=no, --color=no, --experimental_ui=no, --progress_in_terminal_title=no, --symlink_prefix=/Users/olegBorisenkov/Desktop/bazel-leaf-master/build/bazel-build/, //andlib:aarbin, --output_groups=noop, --aspects, build/bazel_aspects/__andlib/get_rule_kind.bzl%print_aspect]
	at com.spotify.gradle.bazel.AspectRunner.getAspectResult(AspectRunner.java:57)
	at com.spotify.gradle.bazel.BazelLeafPlugin.configurePlugin(BazelLeafPlugin.java:123)
	at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:91)
	at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:80)
	at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:42)
	at org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:230)
	at org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:149)
	at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:58)
	at org.gradle.internal.event.BroadcastDispatch$CompositeDispatch.dispatch(BroadcastDispatch.java:324)
	at org.gradle.internal.event.BroadcastDispatch$CompositeDispatch.dispatch(BroadcastDispatch.java:234)
	at org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:140)
	at org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37)
	at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy32.afterEvaluate(Unknown Source)
	at org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:83)
	at org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:80)
	at org.gradle.api.internal.project.DefaultProject.stepEvaluationListener(DefaultProject.java:1393)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.notifyAfterEvaluate(LifecycleProjectEvaluator.java:80)
	... 92 more
Caused by: java.io.IOException: Got process exit code 1 when running bazel BazelExec: [/Users/olegBorisenkov/.bazel/bin/bazel, build, --curses=no, --color=no, --experimental_ui=no, --progress_in_terminal_title=no, --symlink_prefix=/Users/olegBorisenkov/Desktop/bazel-leaf-master/build/bazel-build/, //andlib:aarbin, --output_groups=noop, --aspects, build/bazel_aspects/__andlib/get_rule_kind.bzl%print_aspect]
	at com.spotify.gradle.bazel.utils.BazelExecHelper$BazelExec.start(BazelExecHelper.java:55)
	at com.spotify.gradle.bazel.AspectRunner.getAspectResult(AspectRunner.java:55)
	... 109 more

authors: Kadanza menny

repo: menny/bazel-leaf


text:
Update x64dbg

Since 2022-10-10 the minidump command was added so you can remove that plugin as well.

Thanks! Will do it.

source: gharchive/issue

authors: merces mrexodia

repo: mentebinaria/retoolkit

license_type: permissive

license_source: github-api


text:
Added Japanese translation

Hello!

Thanks. This looks good. To be able to put this on Google Play and F-Droid as Japanese, it's best to have the following two strings translated for the listing too. Could you comment with a translation of these?

Short description: "A 2D space shooter game."
Long description:Space pirates are disrupting your work. They're stealing your company's cargo. You must destroy their stations that they use for their theft, but that won't happen without a fight.

Thugaim is a 2D space shooter and is free and open source software.

Hi! Braden
Short description:
"2D スペースシューティングゲーム。"
Long description:
宇宙海賊があなたの仕事を妨害しています。 やつらは会社の貨物を盗んでいます。 やつらが盗むために使っているステーションを破壊するため、戦わなけなければなりません。
Thugaim は 2D スペースシューティングゲームで、フリーでオープンソースのソフトウェアです。

Thanks. I will include this in the next release.

source: gharchive/pull-request

license: mit

license_source: bigquery


text:
fix 'Could not start Idris process' on windows

I tried to fix the bug of this plugin on windows.
This error is mentioned here: #33 .
This is because in windows, spawn is written differently, but this library unifies the writing in different environments.
Or you can also use the parameter shell:
spawn(xxx, { shell: true })

Another problem is that fsPath from workspaceFolders should be used, which will use platform-specific separators, while path use linux-style separators.
My modified code works fine on my windows.
I'm using idris1, I haven't tested the situation with idris2, but it looks like it has nothing to do with the version of idris, just a compatibility issue with different platforms.

Thanks for the PR :+1:. I'll look at it as soon as I can. It looks good, I just want to try running it locally.

Sorry about the wait. I don't use Windows much, so it took me a bit to get it set up. I was able to reproduce it, which is a good start.
I didn't need cross-spawn or add shell: true to get it to run, just the change to fsPath was enough. Can you confirm whether that is enough on your system?

my environment:

windows 10 21H1
node v16.13.1

my config:

I confirm that idris has added environment variables and can be used in cmd:

I tried to modify only fsPath, got the error: Could not start Idris process with: idris.
Here's a debug of what went wrong:

stack:
"Error: spawn idris ENOENT\n\tat Process.onexit (node:internal/child_process:283:19)\n\tat onErrorNT (node:internal/child_process:478:16)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:83:21)"

And when I add shell: true, the plugin works fine:

license: MIT


text:
Comparison tool

New cli tool "compare" (odxtools - Issue 35)
Can be used to compare databases (pdx-files) and/or ecu variants with each other.
Compares all diagnostic services as well as its parameters of the specified databases /variants with each other and displays the changes.
Katja Köhler <katja.koehler@mercedes-benz.com>, on behalf of MBition GmbH.
Provider Information

Where did the file examples/somersault_01.01.02.pdx come from?

nice, thanks all!

authors: andlaus kakoeh kayoub5

repo: mercedes-benz/odxtools


text:
Update IntelliJ Plugin and Repository

Wanted

plugin should be compatible with newest version of IDE
plugin must be importable (current way with https://plugins.jetbrains.com/plugins/alpha/list does not work anymore)

Solution
Make plugin compatible with IDE
Update custom repository (see: https://plugins.jetbrains.com/docs/intellij/custom-plugin-repository.html)
Update User guide (https://www.jetbrains.com/help/idea/managing-plugins.html#repos)

A custom plugin repository is only necessary when we do not use the official JetBrains marketplace, but we want to use it.
That the aplpha list channel is no longer available is a problem and must be solved.

I will close this issue - the upload of V0.4.0 has been done.

authors: de-jcup lorriborri

repo: mercedes-benz/sechub-plugin-intellij


text:
HG_Init_opt() doesn't return NULL even if HG_Core_init_opt() fails

Hi,
while testing Mercury in our development cluster we found a minor bug where if an invalid na_info_string is propagated from HG_Init() to HG_Init_opt(), it can happen that HG_Init() returns a valid hg_class_t * which has not been properly initialized.
In the following snippet, if HG_Core_init_opt() fails, the error is reported but hg_class is not reset to NULL. This causes our server to continue running until it tries to call HG_Addr_self() which produces a fatal error because hg_class->hg_class.core_class is actually NULL.
hg_class_t *
HG_Init_opt(const char *na_info_string, hg_bool_t na_listen,
    const struct hg_init_info *hg_init_info)
{
    struct hg_private_class *hg_class = NULL;

    hg_class = malloc(sizeof(struct hg_private_class));
    if (!hg_class) {
        HG_LOG_ERROR("Could not allocate HG class");
        goto done;
    }
    memset(hg_class, 0, sizeof(struct hg_private_class));
    hg_thread_spin_init(&hg_class->register_lock);

    hg_class->hg_class.core_class = HG_Core_init_opt(na_info_string, na_listen,
        hg_init_info);
    if (!hg_class->hg_class.core_class) {
        HG_LOG_ERROR("Could not create HG core class");
        goto done;
    }

    /* Set more data callback */
    HG_Core_set_more_data_callback(hg_class->hg_class.core_class,
        hg_more_data_cb, hg_more_data_free_cb);

done:
    return (hg_class_t *) hg_class;
}

Unless I am missing some special semantics from Mercury, the fix should be pretty simple:
hg_class_t *
HG_Init_opt(const char *na_info_string, hg_bool_t na_listen,
    const struct hg_init_info *hg_init_info)
{
    struct hg_private_class *hg_class = NULL;

    hg_class = malloc(sizeof(struct hg_private_class));
    if (!hg_class) {
        HG_LOG_ERROR("Could not allocate HG class");
        goto done;
    }
    memset(hg_class, 0, sizeof(struct hg_private_class));
    hg_thread_spin_init(&hg_class->register_lock);

    hg_class->hg_class.core_class = HG_Core_init_opt(na_info_string, na_listen,
        hg_init_info);
    if (!hg_class->hg_class.core_class) {
        HG_LOG_ERROR("Could not create HG core class");
        free(hg_class);
        hg_class = NULL;
        goto done;
    }

    /* Set more data callback */
    HG_Core_set_more_data_callback(hg_class->hg_class.core_class,
        hg_more_data_cb, hg_more_data_free_cb);

done:
    return (hg_class_t *) hg_class;
}

Should I submit a PR?

@alberto-miranda no that's not necessary to submit a PR, I'll push a fix for it. Thanks for pointing that out!

authors: alberto-miranda soumagne

repo: mercury-hpc/mercury


text:
[Feat][ts] api to start source task

Why
Plugins (as well as lake framework) should not care about when to trigger the plugin jobs. We will provide task trigger api and left users deciding when to trigger jobs.
How
Post request example(but not confirmed now):
POST  /sources/${source id}/task
{
    sourceId: 'uuid', // source id is returned by source api
    options: {
        projects: ['ProjectName'],
        boards: ['Scrum Board Id']
    } // options will be passed to plugin's execute method
}
response:
{ task: 'task id' }

@jaxzhou  I assume you are working on this. Please assign it to someone else if I am wrong. Assigning you for now.

Questions:

Why would we ever need to start a task? Why not just add it to the queue and then process the tasks as soon as we can?

Can you explain this API a little more? Maybe we no longer need this ticket?

After #242 merged, we can create plugin configuration via source api. The next step of rest api module is to add task trigger api.
what to do

[ ] update sourceTask model to fit current requirement
[ ] add CRUD api for source task, the create api is with high priority, others not.
[ ] add some unit test
[ ] add some e2e test

we should save a source task record to db and then add a queue task by producer service.

@hezyin would like us to change the name 'source' to 'plugin'

authors: jaxzhou joncodo narrowizard

repo: merico-dev/lake


text:
[Jira]Customization of the range of data to collect

Description
For some jira users from ee, they have many many data in their jira instance. It costs too much time and resources to collect all the data from their jira instance.
We hope to control the data scope by some filters when collecting:

update_time: collecting data updated after update_time.
project: collecting data belongs to some projects
board: collecting data related to some boards.

support update_time for iter2, project would be delay and further discuss.

authors: klesh narrowizard


text:
Demo site implementation

Description
Create a series of demo sites, our marketing team (@MaximDub @nitinvasanth ) can share them with our target users to help them experience Dev Lake. It'll be a huge boost for us to get more users.
Describe the solution you'd like

create a series of sites in the URL like:

demo.devlake.io (homepage)
github.devlake.io
gitlabci.devlake.io

The homepage shows the overall metrics. The rest sites show the metrics from a single data source.
Demo sites will use the data from our own Github project.
Demo sites should have a basic auth system.

Reliance
It's partly blocked by #556
Additional context
Add any other context or screenshots about the feature request here.

Will do it for later. We can use Tin for now.


text:
Generic functions to print tables and lists

Description of change

Fixes https://github.com/meroxa/mdpx/issues/575
Type of change

[x]  New feature
[ ]  Bug fix
[ ]  Refactor
[ ]  Documentation

How was this tested?

[x]  Unit Tests
[ ]  Tested in staging
[ ]  Tested in minikube

Demo

before
after

Additional references

Documentation updated

I pushed everything up to github that I had worked on

repo: meroxa/cli


text:
Liquid Physics

In the game's current version, all liquid blocks (water and lava) are completely static and do not flow.
We want to change this so that water and lava blocks:

Spread horizontally and downwards, infinitely

Create stone blocks when they come into contact with each other

[Optional] Spread horizontally to a maximum of three block distance, and downwards infinitely

Potential Implementation Methods:

Introduce integer "spread" to liquid blocks. While spread is bigger than zero, change neighboring air blocks into liquid blocks. No idea on how to implement the "water + lava = stone" reaction with this method.

Change all possible blocks that could neighbor a liquid block so that when they are destroyed, they replace themselves with the same type of liquid block they are next to, or with a stone block if they are next to both water and lava blocks. No idea on how to implement maximum spread distance with this method.

Issuelar en az 700 character ile anlatilmali. Tekrar duzenleyiniz

Pardon, karakter sayisini yanlis saymisim. Icerik olarak uygundur.

-Sıvı bloklar oyuncu tarafından kaldırılabilir hale getirildi
-Oyuncunun başlangıç envanterine sıvı ve lav blok kondu

authors: cagdasgerede sozcan

repo: mertserezli/Terasology


text:
Support for ASCII emojies

The default emojione supports for ASCII emojies like :) :( etc.
Can the emojionearea provide the same support?

Currently no. But you can replace ':)' with emojione after editing.
How do you think it supposed to be?
User enter ':)', and it replace with smiles?
I don't like it, so don't wanna do this.
If you want, you can add this feature,
contributions are welcome.

I tried replacing that with emojione! But I am facing the issue of caret moving to the starting position of the field. It was hard!!
If you can give me a hint on mapping ASCII smiles to the shortcodes, I am ready for providing contribution! 😀😀
Sent from my iPhone

On 03-Oct-2016, at 6:23 AM, Andrey Izman notifications@github.com wrote:
Currently no. But you can replace ':)' with emojione after editing.
How do you think it supposed to be?
User enter ':)', and it replace with smiles?
I don't like it, so don't wanna do this.
If you want, you can add this feature,
contributions are welcome.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Today, many people write short texts in the form of ":)" or ":-)". It is both a quick response and expresses itself beautifully. Whether you want it or not, all major sites are doing autocompletions like this. Example: Whataspp and Facebook. Because people are accustomed to these sites, they are very common in this text when they leave the text ": D" in our texts. EmojiOne is a great script but the shortcuts are very useless. Metode: To open the panel when we press the key: Completion may be more convenient by adding an automatic smile when we add a D-shaped expression. Think about it for the next version.
(Translated by Google Translate)

It is a open source repo, feel free to make this feature :smile:

To be clear I don't like such features, and i will not do this

authors: mervick sibidharan viperaykiri

repo: mervick/emojionearea


text:
[chore] Update APIs

Notes for Reviewers
This PR

Updates connections API endpoints of Meshery server
Updates Remote Provider endpoints

This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit c9f2b7a0f1efef37421bbf17fa4e53a70e7d9cfb at: https://6487188ffdb3c62dc82e277b--meshery-docs-preview.netlify.app

repo: meshery/meshery


text:
Fixing typo in readme

should read external_data_centers, not data_center_url

LGTM!

@eastlondoner Thanks for the PR!

authors: eastlondoner mohitsoni

repo: mesosphere/dcos-cassandra-service


text:
Add ContainerInfo for TaskSpecification

The existing DefaultTaskSpecification does not provide appropriate entry points for running containers as tasks. This PR proposes an updated TaskSpecification interface.
cc @gabrielhartmann

Can one of the admins verify this patch?

I would request somebody to point me to the final TaskInfo construction so that the getContainer interface method can be utilized to add ContainerInfo to the protobuf.

@activatedgeek:  Thanks for the PR.  Looks reasonable to me.  Could you add a few unit tests validating that this generates expected protobufs.  In particular I'm interested in validating that getExistingOfferRequirement works as expected after launching with a ContainerInfo.  Should be fine, but would be nice to validate with a test or two.

What happens when ContainerInfo and CommandInfo are set simultaneously ?

Also, @activatedgeek and @mohitsoni.  I this situation we'd probably want to make CommandInfo optional.  I think with entry points all combinations are possible, and I don't see how we could validate TaskSpecifications actually.  Maybe trust the developer?  A revolutionary thought.

@mohitsoni, From what I remember after seeing mesos.proto, I think ContainerInfo uses CommandInfo if it is available for the [command] part in docker run [options] image [command]). Please correct me if I am wrong.
@gabrielhartmann I did think about making both the ContainerInfo and CommandInfo optional which in fact does keep us in line with the protobuf definition anyways (where both are optional and "trust the developer" kind of thing). I believe it should be done and an exception can be thrown in case both are empty(). What do you think?

@activatedgeek:  I think we're getting somewhere.  I was trying to think what validation we could perform.  Both empty throwing the exception you specify sounds good to me.  Can't validate the developer hasn't done something incorrect if both are specified.
Making the change discussed above and writing some unit tests should be sufficient to get this across the line.
/cc @mohitsoni

@gabrielhartmann I rebased from master and updated my code. Requesting for review.

To ensure that the developer doesn't end up missing both CommandInfo and ContainerInfo, only appropriate constructors have been provided. More precisely, constructor arguments of CommandInfo and ContainerInfo are not optional in the DefaultTaskSpecification.

The static DefaultTaskSpecification.create method throws appropriate exceptions and uses appropriate constructors based on which of the two protobufs are available.

Updated tests for CustomTaskSet (covering all possible constructors)

@mesosphere-ci: retest this please

@activatedgeek:  Looks good.  A couple comments.  Also, this needs OfferRequirement tests.  I'd like to see something that rejects creation of an OfferRequirement if input is bad, and validates expected content in expected cases.

@activatedgeek:  mostly copy/paste from Slack:
The test is fine but more is needed.  It looks like all the tests in DefaultOfferRequirementProviderTest are focused around testing already launched Tasks.  Ignoring that oddness, it would be nice to have a couple tests that use the getNewOfferRequirement method of the DefaultOfferRequirementProvider with the new kinds of TaskSpecification you’ve enabled.
And then check that the OfferRequirement has been constructed as expected.  One with just a ContainerInfo, one with just a CommandInfo, one with both, and one with neither should be sufficient.  Then there should be a couple tests that test the getExistingOfferRequirement method to make sure one can recover from crash and detect changes to the TaskSpec.
e.g. One might start with a valid TaskSpecification, and then change it so that it's no invalid.  That should cause a failure in generating an an OfferRequirement.

@gabrielhartmann Right, that falls in line. Thanks!

@mesosphere-ci: retest this please

authors: activatedgeek gabrielhartmann mesosphere-ci mohitsoni

repo: mesosphere/dcos-commons


text:
fix: update for upcoming linter bump

The new linter does not like the word "node" as used. Fixing that and updating the GPU supported platforms in the repo docs.

Let's solve this another way. Preferably through a file described here
https://github.com/textlint/textlint-filter-rule-allowlist

@faiq updated.

authors: faiq tillt

repo: mesosphere/konvoy-image-builder


text:
extends #1028 - Add a test that checks, that no health checks will be st...

...arted for staging tasks

Merge only after #1028 has been merged.

Thanks!

Build failure:
[info] HealthCheckActorTest:
[INFO] [01/16/2015 16:04:50.946] [pool-1-thread-1-ScalaTest-running-HealthCheckActorTest] [akka://system/user/$$A] Starting health check actor for app [test] and healthCheck [HealthCheck(Some(/),HTTP,0,None,15 seconds,10 seconds,20 seconds,3)]
[info] - should not dispatch health checks for staging tasks *** FAILED ***
[info]   true was not false (HealthCheckActorTest.scala:45)

Will rebase this one on top of my patch. Otherwise, the test will fail obviously.

Yep, this is the regression I'm testing ;-)

Rebase with https://github.com/mesosphere/marathon/pull/1028

Great, thanks.

Tiny nit regarding a lost comment, feel free to :ship: it once that's fixed.

authors: ConnorDoyle drexin sttts

repo: mesosphere/marathon


text:
Delete report

Delete report has been worked on
Kindly find attached the link to the loom video
https://www.loom.com/share/91817528ddff4830bd4c09ef493d89cf?sid=dab7b190-0b24-4948-986e-e88cdcf53221

There are conflicts. Resolve these conflicts

Conflicts have been resolved

Conflicts still exists. Pull current changes into your branch

conflicts have been resolved

authors: VidaOwusu alexboateng

repo: mestafrica/mobile-wallet-fraud-database


text:
Improve storage config of server

We need to ensure that the server has sufficient space for the data it will be downloading to do the plotting, and ensure that storage is part of the EC2 instance rather than the docker container.

Based on Alex's comment and the fact that we're loading the data through goofys streaming, this issue is no longer relevant so I am closing the issue.


text:
error: no match for ‘operator--’ during make

I am getting following error while make at 84%
[  0%] Built target meta-util
[  2%] Built target liblinear
[  3%] Built target meta-eval
[  5%] Built target libsvm
[  7%] Built target meta-kernel
[  8%] Built target ExternalICU
[  8%] Built target meta-stats
[  9%] Built target meta-parser-trees
[ 12%] Built target meta-loss
[ 13%] Built target graph-test
[ 15%] Built target ceeaus
[ 17%] Built target housing
[ 19%] Built target breast-cancer
[ 21%] Built target cranfield
[ 23%] Built target meta-io
[ 24%] Built target meta-utf
[ 25%] Built target meta-parser-io
[ 27%] Built target meta-tree-visitors
[ 28%] Built target meta-to-glove
[ 29%] Built target meta-learn
[ 29%] Built target glove
[ 30%] Built target meta-succinct
[ 31%] Built target wiki-page-rank
[ 32%] Built target compressor-test
[ 34%] Built target utf8-test
[ 35%] Built target meta-tokenizers
[ 38%] Built target meta-corpus
[ 40%] Built target meta-sequence
[ 41%] Built target meta-regression
[ 42%] Built target mph-vocab
[ 46%] Built target meta-filters
[ 48%] Built target meta-parser-featurizers
[ 48%] Built target corpus-gen
[ 48%] Built target meta-greedy-tagger
[ 51%] Built target meta-parser
[ 52%] Built target meta-crf
[ 53%] Built target meta-hmm
[ 55%] Built target meta-analyzers
[ 55%] Built target parser-test
[ 56%] Built target parser-train
[ 58%] Built target crf-train
[ 58%] Built target read-trees
[ 58%] Built target hmm-train
[ 58%] Built target pos-tag
[ 59%] Built target tokenize-test
[ 61%] Built target meta-index
[ 62%] Built target meta-embeddings
[ 62%] Built target meta-parser-analyzers
[ 63%] Built target meta-sequence-analyzers
[ 63%] Built target embedding-vocab
[ 65%] Built target meta-language-model
[ 67%] Built target pos-tokenizer
[ 67%] Built target sr-parse
[ 67%] Built target profile
[ 69%] Built target meta-topics
[ 69%] Built target top-k
[ 69%] Built target meta-embeddings-analyzers
[ 70%] Built target lda-topics
[ 71%] Built target embedding-cooccur
[ 74%] Built target meta-ranker
[ 76%] Built target meta-features
[ 76%] Built target interactive-embeddings
[ 76%] Built target search-vocab
[ 77%] Built target print-vocab
[ 78%] Built target forward-to-libsvm
[ 79%] Building CXX object src/index/tools/CMakeFiles/interactive-search.dir/interactive_search.cpp.o
[ 80%] Built target index
[ 80%] Building CXX object src/index/tools/CMakeFiles/search.dir/search.cpp.o
[ 80%] Built target diff-test
[ 81%] Built target sentence-likelihood
[ 82%] Built target query-lm
[ 82%] Built target build-mph-lm
[ 82%] Built target meta-lm-analyzers
[ 82%] Building CXX object src/topics/tools/CMakeFiles/lda.dir/lda.cpp.o
[ 82%] Built target regression
[ 83%] Building CXX object src/topics/tools/CMakeFiles/topic-corpus.dir/topic_corpus.cpp.o
[ 83%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/binary_classifier_factory.cpp.o
[ 84%] Building CXX object src/features/tools/CMakeFiles/feature-summary.dir/feature_summary.cpp.o
In file included from /usr/include/c++/8.2.1/bits/stl_algobase.h:66,
                 from /usr/include/c++/8.2.1/algorithm:61,
                 from /home/harsh/Documents/meta/deps/cpptoml/include/cpptoml.h:10,
                 from /home/harsh/Documents/meta/src/features/tools/feature_summary.cpp:10:
/usr/include/c++/8.2.1/bits/stl_iterator_base_funcs.h: In instantiation of ‘constexpr void std::__advance(_RandomAccessIterator&, _Distance, std::random_access_iterator_tag) [with _RandomAccessIterator = meta::learn::dataset_view::iterator; _Distance = long int]’:
/usr/include/c++/8.2.1/bits/stl_iterator_base_funcs.h:206:21:   required from ‘void std::advance(_InputIterator&, _Distance) [with _InputIterator = meta::learn::dataset_view::iterator; _Distance = long int]’
/home/harsh/Documents/meta/include/meta/parallel/parallel_for.h:49:21:   required from ‘std::vector<std::future<typename std::result_of<Function(Iterator, Iterator)>::type> > meta::parallel::for_each_block(Iterator, Iterator, meta::parallel::thread_pool&, Function&&) [with Iterator = meta::learn::dataset_view::iterator; Function = meta::parallel::reduction(Iterator, Iterator, meta::parallel::thread_pool&, LocalStorage&&, MappingFunction&&, ReductionFunction&&) [with Iterator = meta::learn::dataset_view::iterator; LocalStorage = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda()>&; MappingFunction = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda(meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&, const instance_type&)>&; ReductionFunction = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda(meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&, const meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&)>&; typename std::result_of<LocalStorage()>::type = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts]::<lambda(meta::learn::dataset_view::iterator, meta::learn::dataset_view::iterator)>; typename std::result_of<Function(Iterator, Iterator)>::type = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts]’
/home/harsh/Documents/meta/include/meta/parallel/algorithm.h:60:25:   required from ‘typename std::result_of<LocalStorage()>::type meta::parallel::reduction(Iterator, Iterator, meta::parallel::thread_pool&, LocalStorage&&, MappingFunction&&, ReductionFunction&&) [with Iterator = meta::learn::dataset_view::iterator; LocalStorage = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda()>&; MappingFunction = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda(meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&, const instance_type&)>&; ReductionFunction = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda(meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&, const meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&)>&; typename std::result_of<LocalStorage()>::type = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts]’
/home/harsh/Documents/meta/include/meta/parallel/algorithm.h:84:21:   required from ‘typename std::result_of<LocalStorage()>::type meta::parallel::reduction(Iterator, Iterator, LocalStorage&&, MappingFunction&&, ReductionFunction&&) [with Iterator = meta::learn::dataset_view::iterator; LocalStorage = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda()>; MappingFunction = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda(meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&, const instance_type&)>; ReductionFunction = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::<lambda(meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&, const meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts&)>; typename std::result_of<LocalStorage()>::type = meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]::prob_counts]’
/home/harsh/Documents/meta/include/meta/features/feature_selector.h:253:42:   required from ‘void meta::features::feature_selector::calc_probs(const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]’
/home/harsh/Documents/meta/include/meta/features/feature_selector.h:207:9:   required from ‘void meta::features::feature_selector::init(const LabeledDatasetContainer&, uint64_t) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view; uint64_t = long unsigned int]’
/home/harsh/Documents/meta/include/meta/features/selector_factory.h:112:5:   required from ‘std::unique_ptr<meta::features::feature_selector> meta::features::make_selector(const cpptoml::table&, const LabeledDatasetContainer&) [with LabeledDatasetContainer = meta::classify::multiclass_dataset_view]’
/home/harsh/Documents/meta/src/features/tools/feature_summary.cpp:51:61:   required from here
/usr/include/c++/8.2.1/bits/stl_iterator_base_funcs.h:183:2: error: no match for ‘operator--’ (operand type is ‘meta::learn::dataset_view::iterator’)
  --__i;
  ^~~~~
[ 84%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/binary_classifier.cpp.o
make[2]: *** [src/features/tools/CMakeFiles/feature-summary.dir/build.make:63: src/features/tools/CMakeFiles/feature-summary.dir/feature_summary.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1421: src/features/tools/CMakeFiles/feature-summary.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 85%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/classifier.cpp.o
[ 85%] Linking CXX executable ../../../topic-corpus
[ 85%] Built target topic-corpus
[ 85%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/dual_perceptron.cpp.o
[ 86%] Linking CXX executable ../../../search
[ 86%] Linking CXX executable ../../../interactive-search
[ 86%] Linking CXX executable ../../../lda
[ 86%] Built target search
[ 86%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/knn.cpp.o
[ 86%] Built target lda
[ 86%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/nearest_centroid.cpp.o
[ 87%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/logistic_regression.cpp.o
[ 87%] Built target interactive-search
[ 87%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/naive_bayes.cpp.o
[ 87%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/one_vs_all.cpp.o
[ 88%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/one_vs_one.cpp.o
[ 88%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/sgd.cpp.o
[ 88%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/svm_wrapper.cpp.o
[ 88%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier/winnow.cpp.o
[ 89%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/classifier_factory.cpp.o
[ 89%] Building CXX object src/classify/CMakeFiles/meta-classify.dir/confusion_matrix.cpp.o
[ 89%] Linking CXX static library ../../lib/libmeta-classify.a
[ 89%] Built target meta-classify
make: *** [Makefile:130: all] Error 2

I undertand it's because of c++ 8.2.1 stl library but I don't know how to fix this error.
I am running Manjaro Linux with g++ version 8.2.1
Please do let me know if I should provide any more details.

I used a different version of g++ and it builds without any issue. I think the issue is specifically with g++-8 version.

I have exactly the same with g++9

It work only with g++7.
Not work on g++ 8 or 9

authors: hkundnani sebglon

repo: meta-toolkit/meta


text:
Allow line-corpus format corpora to be segmented

For example, our yelp dataset has two segments: score (which is everything) and sentiment (which is just the extreme reviews). These subsets can be independently indexed if using file_corpus, but not when using line_corpus.
Not sure if this is worth it or not, but it could potentially be useful for the same reasons it was useful for file_corpus.

I don't feel strongly about this anymore---I think it's fine to just create another corpus with just the documents you want if you want to do this.


text:
mirrord copy pod

Following Discord discussion:
https://discord.com/channels/933706914808889356/1111113277053870161/1111263282054045697
User wants to:

Get an existing pod environment variable
Have networking exposed both incoming and outgoing of the cluster
But they don't want to steal an existing pod traffic

I thought a more generic use case would be something like mirrord exec --replica -t pod/pod
which instead of running targetless, it will create a replica of an existing pod.
Things to consider:

Should we run the original app or just our agent with the replica? (then pause / steal?)
?

Another usecase - CronJob.

Short update - we're prioritizing this as part of mirrord for Teams.
https://github.com/metalbear-co/operator/issues/321

This was implemented as part of mirrord for Teams.

repo: metalbear-co/mirrord


text:
dapr sidecar isn't accessible

When running curl in a mirrord exec ran as the main app, it cannot access the gRPC port (50001) or the health check (3500).
When using ephemeral agent, the health check works but still can't access the gRPC port.
https://discord.com/channels/933706914808889356/1261388094746267811
mirrord config
{
  "internal_proxy": {"log_level": "mirrord=trace", "log_destination": "/tmp/mirrord.log"},
  "target": {
    "path": "deployment/publisher/container/test",
    "namespace": "default"
  },
  "agent": {
    "namespace": "default",
    "log_level": "mirrord=trace",
    "ephemeral": false
  },
  "feature": {
    "network": {
      "incoming": { "mode": "steal", "ignore_localhost": false },
      "outgoing": { "tcp": true, "udp": true, "ignore_localhost": false }
    },
    "fs": "read"
  }
}

app
apiVersion: apps/v1
kind: Deployment
metadata:
  name: publisher
  labels:
    app: test
spec:
  replicas: 1
  selector:
    matchLabels:
      app: test
  template:
    metadata:
      labels:
        app: test
      annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "publisher"
        dapr.io/enable-api-logging: "true"
    spec:
      containers:
      - name: test
        image: debian:bookworm
        command:
          - "tail"
          - "-f"
          - "/dev/null"

helm:
repositories:
  - name: dapr
    url: https://dapr.github.io/helm-charts/

releases:
  - name: dapr
    namespace: dapr-system
    chart: dapr/dapr
    values:
      - global:
          mtls:
            enabled: false

mirrord command
mirrord exec -f .mirrord/mirrord.json /bin/bash

When running tcpdump -nvvei lo using kubectl debug on the pod, we can see that traffic to 3500 is seen (and works) but traffic to 50001 is just ignored.


text:
Validate 2024 PDF layout using production standard

We need to validate our implementation of the 2024 layout against a production standard:

https://github.com/metanorma/mn-samples-iso-private/blob/main/reference-docs/19152-1_2024.pdf

This is a private copy.

Our implementation of the 2024 layout looks differently:

page margins

rendered PDF

production standard

header font-size

rendered PDF (0.5pt smaller font)

production standard

copyright font-size

rendered PDF

production standard

main text font-size

rendered PDF

production standard

last page footer

rendered PDF

production standard

Our PDF layout was updated in https://github.com/metanorma/metanorma-iso/issues/1079 based on the provided PDF example 2024-iso-new-pdf-layout.pdf "Sample of layout for an International Standard (cover page, back page and internal centered layout)".
@ronaldtse to further actions I have to know exactly - what is the correct PDF - in this issue or in https://github.com/metanorma/metanorma-iso/issues/1079?
Note: the PDF from the initial posts opens in the Chrome browser only. Adobe Acrobat opens it and closes immediately, also Foxit Reader and PDF-XChange Viewer. So I have to repair it somehow.

Adobe Acrobat opens it and closes immediately

I'm seeing the same issue too. I can open it in macOS Preview however.
It is very likely that their "design spec" and implemented production PDF are slightly different.

To check the whole document I'll encode it in adoc.

one numbered Note

rendered PDF:

production PDF:

The rendered PDF is correct. From https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor340:

24.3 Numbering and subdivision
Within a given clause or subclause, notes shall be numbered sequentially. The numbering restarts at each new subdivision. A single note in a subdivision shall not be numbered.

ordered list numbering - alphabetic vs. arabic:

rendered PDF:

production PDF:

From https://www.metanorma.org/author/topics/blocks/lists/#general-2:

different font size of Note:

rendered PDF (a bit smaller):

production PDF:

wrong baseline when list text contains superscripted text

rendered PDF:

there isn't footnotes separator (51mm horizontal line) in the rendered PDF

indents between footnotes:

rendered PDF:

production PDF:

There is the identical entry in the Normative references and Bibliography:

therefore different identifiers should be used in the adoc:
[bibliography]
== Normative references

* [[[ISO19103,ISO 19103]]], _Geographic information -- Conceptual schema language_
...

[bibliography]
== Bibliography

* [[[ISO19103bib,ISO 19103]]], _Geographic information -- Conceptual schema language_
,..

[ ] Source color link:

rendered PDF:

production PDF:

[ ] Example (numbered vs. unnumbered) alignment:

rendered PDF:

production PDF:

[ ] dash after modified:

rendered PDF en dash (U+2013):

production PDF em dash (U+2014):

Presentation XML contains en dash:
</xref>, modified
 – Note 1 to entry removed.]</termsource>

[ ] different vertical indents between the definition list items, need increase a bit

[ ] text with indent

rendered PDF:

production PDF:

Note: I don't know how to achieve it.

[ ] space before table name

rendered PDF:

production PDF:

[ ] table footer top border

[ ] space between footnotes

rendered PDF

production PDF

[ ] space after table

rendered PDF:

production PDF:

[ ] reference from Annex A sub-clause to another sub-clause

rendered PDF:

production PDF:

[ ] reference from Annex A sub-clause to main section sub-clause

rendered PDF

production PDF

[ ] table cell borders

rendered PDF:

production PDF:

@Intelligent2013 can you help file issues for @opoudjis for those he needs to fix? Thanks.

[ ] smallcap font-size

rendered PDF

production PDF

[ ] references to the Bibliography items

rendered PDF:

production PDF

[ ] comma between bibliography references

rendered PDF:

production PDF:

Adoc markup:
<<ref10>>,<<ref15>>

[ ] text with indent

rendered PDF:

production PDF:

This issue can be solved via css: [css text-indent:7mm]#*1) CoreClassConformant*#.
Rendered PDF:

[ ] reference to the standard

rendered PDF

production PDF

ISO XSLT updated for PDF layout 2024.
Only one issue remains: https://github.com/metanorma/metanorma-iso/issues/1141
On hold.

Done.

repo: metanorma/metanorma-iso


text:
metanorma/metanorma-docker#119 replace references to *.scss with *.css

metanorma/metanorma-docker#119

Metanorma PR checklist

NO Breaking changes (list related PRs)
NO Documentation update required (create task for this)
NO External dependency introduced (documentation update need)
NO Gem with native library introduced

@CAMOBAP There are two issues to resolve:

Can people use SASS or only CSS?
Add instructions on how to build your own Docker container with a custom flavor.

Can people use SASS or only CSS?

As far as I understand it depends:

for packed-mn-based solutions it's impossible. for Docker and Ruby it's possible if sassc installed

@ronaldtse @strogonoff @opoudjis  Could you please suggest a good page to add this information?

Add instructions on how to build your own Docker container with a custom flavor.

@ronaldtse  Any suggestion which Dockerfile should be used as base?

Yes, only docker based solutions can use SASS. We need to make that clear. I think we need a guide for a flavor builder. We don't have a good guide right now.
Probably metanorma/metanorma?

The reason I didn't merge this a while ago is that we need better quality docs for Metanorma adoption. Will create a new ticket for that.

authors: CAMOBAP ronaldtse


text:
Dev

webbrowser authentication is removed and replaced with a backend refresh-token-loop
Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

azure funnction from bimsync manager is incorporated into the app instead of running a refresh token function within the app

repo: metarom/bimsync-retriever


text:
numbering of dataset name

Is your feature request related to a problem? Please describe.
If dataset names are duplicates, separate them by numbers.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered

I want to identify datasets by name
Additional context

duplicated issue

repo: metatron-app/metatron-discovery


text:
F#2243 show null as missing

Description
Null values will be treated as missing on the Histogram bar.
Related Issue : https://github.com/metatron-app/metatron-discovery/issues/2243
How Has This Been Tested?
Run locally.
Need additional checks?
Yes. Let's use one of testbeds.
Types of changes

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

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.

Additional context:
For string type, I'd like to keep showing (null) for null values. (One of the famous data preparation tools works the same way).
(null) might be removed for non-string types, later. (It makes the page messy!)
But now, all null values are shown as (null).

run build
deploy to 1


text:
No link from forgot password to login

Why is there no link from the "forgot password" page to the login page? It can happen that the user suddenly remembers his/her password and will log in instead of reset their password.
Isn't it bad UI to deadlock the user.

I have been looking for an option to add a back to login link from the forgot password page! How can I do this. I was going to edit the template but I can' t even find the forgot password template.
Please update so we can show back to login from the forgot password page!

The choice was to prevent having too much stuff at the same time within the form...
It seemd more logical to go back ti sign-up and then, possibly back again to sign-in.
Feel free to modify this line by overriding the template helper like this:
AccountsTemplates.atFormHelpers['showSignInLink'] = function(next_state){
  if (AccountsTemplates.options.hideSignInLink)
    return false;
  var state = next_state || this.state || AccountsTemplates.getState();
  if (AccountsTemplates.options.forbidClientAccountCreation && state === "forgotPwd")
    return true;
  return (state === "forgotPwd") || (state === "signUp");
}

this should get easier and much more straightforward in v2.0 though...

authors: 57even sferoze splendido

repo: meteor-useraccounts/core


text:
Calculate SVP table on-demand

The SVP table in improver/psychrometric_calculations/svp_table.py is a large table stored as a constant inside python code and has accompanying tests to verify that the table matches calculated values.
This PR removes the constant table and adds a function which calculates the table when needed, using the existing SaturatedVapourPressureTable code. The calculated table is cached so that any subsequent access to the table is fast. The first-time calculation of the table takes about 10-50ms, which should be relatively minor in the context of a larger scale plugin or CLI operation.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

See the complete overview on Codacy

I've added another commit to loosen the acceptance test relative tolerances so that the current KGO files can be kept as-is.
Thanks @neilCrosswaite for checking the acceptance tests after I'd previously only run the unit tests and thought that it was all ok to go.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

See the complete overview on Codacy

authors: benfitzpatrick tjtg

repo: metoppv/improver