pivot table just have rows, totals show me 0.00

This pivot table just has rows, no cols, i want to totals it but error. It shows me 0.00, why? How to sovled it?

I found i didn't append values to vals[], i solved it. But now i want to know how to format totals value? I found code source just keep two fixed. How to format it by myself?

I found i didn't append values to vals[], i solved it. But now i want to know how to format totals value? I found code source just keep two fixed. How to format it by myself?


Is it possible to make ngDroplet to upload only one image

I want to use ngDroplet in an application when you only need to upload one image, and not many. But I could not find an option to emulate this behavior. I would like to see that when I reupload an image, the old one is replaced.
Is it possible to accomplish this behavior? If not, which changes should we perform on the code?

It's entirely up to your backend to overwrite the previously uploaded file for any given user.
However, for uploading only a single image, I suppose we need to implement maximumValidFiles as in the Ember equivalent — EmberDroplet.
Let me take a look.

Thanks! I have tested the maximum and it works. But if you drop a second image does not replace the previous. I guess I should handle that from my backend.

It would also be nice if we could provide a strategy to ngDroplet to tell it what it should do in such circumstances. By default it could simply set the additional files as INVALID, or it could start invalidating files added earlier to make room for new files.
Thoughts?

Yes You can upload one image and 10 at the same time via ngDroplet.
Since I'm using Node and Express and multer for file handling, all I had to do is to define the requestURL in ngDroplet Controller:
$scope.interface.setRequestUrl('http://localhost:3000/api/upload');
and the request will be sent to Node API, just define multer on top of your API.
router.use(multer({ dest: __dirname + '/public/uploads' }));
router.post('/upload', function(req, res)
{        res.json({"filename": req.files.file});
});

and thats it file upload.... also you can fetch the filenames from response if you want to insert it into DB.


Switch from k8s.gcr.io to registry.k8s.io

Context
Google is asking to switch the registry source from k8s.gcr.io to registry.k8s.io wherever possible.
Reference:

https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/3000-artifact-distribution
kubernetes/kubernetes#109938

Alternatives
none

Closed via #40


Rename ftp host

What? and Why?

Rename FTP_HOST to FTP_PATH

Checklist

[x] CHANGELOG.md updated? (if required)

Codecov Report

Merging #125 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #125   +/-   ##
=======================================
  Coverage   88.56%   88.56%
=======================================
  Files          24       24
  Lines        1827     1827
=======================================
  Hits         1618     1618
  Misses        209      209

Impacted Files
Coverage Δ

transform/transformers/ImageTransformer.py
65.15% <100%> (ø)
:arrow_up:

transform/settings.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


data tiling path crashes in mobile_ssd models on cascadelake target

To repro:
Download and import the model: https://storage.googleapis.com/iree-model-artifacts/mobile_ssd_v2_float_coco.tflite
Compile the model: iree-compile --output-format=vm-bytecode --iree-hal-target-backends=llvm-cpu ~/mobile_ssd_v2_float_coco.mlir -o /tmp/a.vmfb --iree-input-type=tosa --iree-flow-enable-data-tiling --iree-llvm-target-cpu=cascadelake --iree-llvm-target-triple=x86_64-unknown-linux-gnu
Run the model: iree-benchmark-module --module_file=/tmp/a.vmfb --device=local-task --entry_function=main --function_input=1x320x320x3xf32

I can not narrow the input down.... It won't crash if I add --iree-flow-trace-dispatch-tensors flag.
Also, it can only be reproduced with having --iree-llvm-target-cpu=cascadelake --iree-llvm-target-triple=x86_64-unknown-linux-gnu compilation flags.

Probably need to dust off the asan support for generated code... (And would be good to document)

Probably need to dust off the asan support for generated code... (And would be good to document)

Yes! I just finished the ASAN build (and can document how I do it somewhere).

I can compile simple input (like matmul) with ASAN, but not the mobile ssd model. I'm using the system linker; I get many  relocation R_X86_64_PC32 cannot be used against symbol '__asan_option_detect_stack_use_after_return'; recompile with -fPIC errors.

can't reproduce the issue on ToT, closing the issue


GROOVY-9637: Improve the performance of GString

Co-authored-by: Daniel Sun<EMAIL_ADDRESS>

@blackdrag this is the other alternative I alluded to in earlier comments. No change to GString, GStringImpl enhanced slightly with a flag that enables defensive copy in/out for the string and value arrays. We create GStrings in @CompileStatic code with that flag set. Caching is only enabled when that flag is set and values are simple immutables. This piggy-backs on the idea that @CS turns off "dynamic behaviors" even though mutating those arrays is a bit of a stretch of what constitutes dynamic behavior.

Daniel's simple benchmark:
long b = System.currentTimeMillis()
def gstr = makeGString()
for (int i = 0; i < 10000000; i++) {
	gstr.toString()
}
long e = System.currentTimeMillis()
println "${e - b}ms"

<EMAIL_ADDRESS>def makeGString() {
    def now = java.time.LocalDateTime.now()
    "integer: ${1}, double: ${1.2d}, string: ${'x'}, class: ${Map.class}, boolean: ${true}, now: ${now}"
}

My feeling is that stretch is a bit too far.

Closing this one but see:
https://github.com/apache/groovy/pull/1329


[Map] Use custom Ground marker for point features

User-defined fill color required building the bitmap in memory out of constituent vector parts, since it's not possible to edit a single vector path in Android without extra libraries or workarounds.
Fixes #117, fixes #171. #364, #373 still pending.

@hintzemichael w00t! 🎉

It doesn't right to have 3 separate xmls for a single icon. Is it possible to have a single xml and dynamically update color using a custom attr

It doesn't right to have 3 separate xmls for a single icon. Is it possible to have a single xml and dynamically update color using a custom attr
Update:
I tried to look for a solution which would selectively allow us to color only a single path.

custom attribute can be used but that can't be updated on runtime. So, all color must be defined as separate themes (not much usable for us then)

Let's keep it as it for now and look for a possible solution in the future!

Exactly, that's how I landed on this solution - it seemed the least bad option. Thanks for looking into it too!

By the way, the three-part vector will also be useful when introduce icon overlays (e.g., preloaded or user-specified symbols that can be overlaid inside the map marker).

app:srcCompat

Thanks, this appeared after merging with your recent PR. Should be fixed now.


Accessing a Vector Element

With the recent switch to use the normal std::vec::Vec the way to access elements in the vector has changed.
In particular, vec.index(i) is replaced with vec[i]
There could be an issue with reasoning about the returned value. In the NR proofs, we access the operations vector:
<EMAIL_ADDRESS>== operations[i as int]

This unfortunately results in exceeding the rlimit. Adding the & makes the proof go through:
<EMAIL_ADDRESS>== &operations[i as int]

@achreto I haven't been to able to reproduce. What version of verus are you using, and what exact command are you running?
Even though I couldn't reproduce the specific error, the AIR code does change between files. Specifically, all the VIR identifiers change; that could easily cause "flakiness". I also think it would be a good idea to fix, even if I haven't confirmed it's the issue here.
(The reason the VIR identifiers change is that they depend on HIR node IDs, and the addition of a single & node bumps all the IDs by 1.)

[ ] Normalize variable names in rust->VIR conversion rather than keeping the HIR node IDs. (We still need to use them to disambiguate, but we can replace them with smaller ints: e.g., change x~42 and x~99 to x~1 and x~2)

Sorry for the delay in responding. The command is the following
../verus/source/tools/rust-verify.sh --release nr/src/main.rs --arch-word-bits 64

Output (re-run today):
note: while loop has been running for 2 seconds
   --> nr/src/exec/log.rs:868:13
    |
868 | /             while idx < nops
869 | |                 invariant
870 | |                     self.wf(),
871 | |                     0 <= idx <= nops,
...   |
943 | |                 idx = idx + 1;
944 | |             }
    | |_____________^

error: while loop: Resource limit (rlimit) exceeded; consider rerunning with --profile for more details
   --> nr/src/exec/log.rs:868:13
    |
868 | /             while idx < nops
869 | |                 invariant
870 | |                     self.wf(),
871 | |                     0 <= idx <= nops,
...   |
943 | |                 idx = idx + 1;
944 | |             }
    | |_____________^

Version:
Verus
  Platform: linux_x86_64
  Version: 0.2<IP_ADDRESS>e3d21d
  Profile: release

Z3 version is 4.12.2. (assuming it always takes the one obtained through the script)

fixed in https://github.com/verus-lang/verus/pull/1003


[composer-json-factory] How to auto-wire into service

I'm trying to inject ComposerJsonFactory into a service from my Symfony maker (to make the skeleton of a bundle, in fact), and it's not behaving as expected.  Likely I'm not autowiring it correctly, or need an alias, or something like that.
class MyBundle extends AbstractBundle
{
    public function loadExtension(array $config, ContainerConfigurator $container, ContainerBuilder $builder): void
   {
        $builder->autowire(MakeBundle::class)
            ->addTag(MakeCommandRegistrationPass::MAKER_TAG) // 'maker.command'
            ->addArgument($config['template_path'])
            ->addArgument($config['relative_bundle_path']) // /packages
            ->addArgument($config['bundle_name'])
            ->setArgument('$jsonFileManager', new Reference(JsonFileManager::class))
            ->setArgument('$composerJsonFactory', new Reference(ComposerJsonFactory::class))
        ;

My MakeBundle class, that can make files from a command by implementing Symfony's MakerInterface
// MakeBundle.php
class MakeBundle extends AbstractMaker implements MakerInterface
{
    public function __construct(
        private string              $templatePath,
        private string              $bundlePath,
        private string              $bundleName,
        private JsonFileManager     $jsonFileManager,
        private ComposerJsonFactory $composerJsonFactory
    )
    {
    }
}

The error:
The service "Survos\Bundle\MakerBundle\Maker\MakeBundle" has a dependency on a non-existent service "Symplify\ComposerJsonManipulator\ComposerJsonFactory".

Any suggestions?

Possibly related: is this really a bundle?
{
    "name": "symplify/composer-json-manipulator",
    "description": "Package to load, merge and save composer.json file(s)",
    "license": "MIT",
    "type": "symfony-bundle",

Usually bundles extend Bundle or AbstractBundle, but I'm not seeing a class that does that, and the services are all private.
In the end, I got it to work by making the necessary classes public:
        $builder->register(ParameterProvider::class)
            ->setArgument('$container', new Reference('service_container'))
            ->setPublic(true)
            ->setAutowired(true)
            ->setAutoconfigured(true);

        foreach ([SmartFileSystem::class, JsonCleaner::class, JsonInliner::class, JsonFileManager::class, ComposerJsonFactory::class] as $symplifyClass) {
            $builder->register($symplifyClass)
                ->setPublic(true)
                ->setAutowired(true)
                ->setAutoconfigured(true);
        }

It doesn't feel right, though.

Hi, this is not a bundle. Yet you can include the service config and use services with ease :)
https://github.com/symplify/composer-json-manipulator/blob/main/config/config.php


merge json-comm.h with orka-debug.h

VASSERT_S is only defined in orka-debug.h, but  ASSERT_S is defined in both json-common.h and orka-debug.h
Should we merge them and only keep one?

I have to include "orka-debug.h" to json_scanf.c for creating better diagnostic messages. This causes redefine MACRO warnings as "json-common.h" is also included.  But removing "json-common.h" causes some compilation errors.

Ok, I will do the merge!

Done


feat: driver for wa-sqlite

Implements a driver for wa-sqlite and the necessary unit tests.
It provides a start method that creates the DB, the electric namespace, and starts satellite but it does not provide an electrify call (on purpose) as that will no longer be needed when integrating the DAL.

LGTM.

@kevin-dp wa-sqlite should be a peer or a dev dependency, not a dependency.

Yup


feat: Press Escape key to cancel select

Issue: https://github.com/cpeditor/cpeditor/issues/786

Seems like the problem is with CI.


support for custom indexes

It would be nice to be able to specify custom indexes. so for example index: "customIndex"  the string customIndex would get passed along to the adapter.
If the index was a bool then the current behavior would hold.

5 years, wow

It's 7 years. This would still be a good feature to add.

Just short of 11! 🤡


Small animation glitch when resizing the browser window

I'm submitting a ...
[ x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

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

What is the current behavior?
when I scale down my browser window to the point where the menu on the left side gets hidden completely an animation starts. When this happens, the hide buttons (small triangles) from the larger version of the menu pops up and the menu is moving to the left.

What is the expected behavior?
The menu should just move to the left without changing its shape.

What is the motivation / use case for changing the behavior?
Right now it looks like an animation glitch.

Please tell us about your environment:

Angular version: 2.0.0-rc.4
Browser: [all]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

HI @fgather, thanks for submitting the issue, though I'm not sure I can reproduce it. Would you be able to provide some kind of a video?


No such file or directory error invoking angular build

I have a project with an Angular module that is failing to build with Gradle 7.5.1 but works with Gradle 7.5.
UPDATE: I'm now also getting the same error with Gradle 7.4.2, where it was previously working. So it seems to be a non-repeatable error.
This is how I'm invoking the Angular build:
tasks.register<Exec>("buildAngular") {
  group = BasePlugin.BUILD_GROUP
  commandLine("ng", "build")
}

And this is the output from the failure:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':projects:la-ui:buildAngular'.
> A problem occurred starting process 'command 'ng''

* Try:
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':projects:la-ui:buildAngular'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:142)
        at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:140)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:128)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
        at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
        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:77)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
        at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:69)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:327)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:314)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:307)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:293)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:420)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:342)
        at org.gradle.execution.plan.DefaultPlanExecutor.process(DefaultPlanExecutor.java:96)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph.executeWithServices(DefaultTaskExecutionGraph.java:140)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph.execute(DefaultTaskExecutionGraph.java:125)
        at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:39)
        at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:51)
        at org.gradle.execution.BuildOperationFiringBuildWorkerExecutor$ExecuteTasks.call(BuildOperationFiringBuildWorkerExecutor.java:54)
        at org.gradle.execution.BuildOperationFiringBuildWorkerExecutor$ExecuteTasks.call(BuildOperationFiringBuildWorkerExecutor.java:43)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
        at org.gradle.execution.BuildOperationFiringBuildWorkerExecutor.execute(BuildOperationFiringBuildWorkerExecutor.java:40)
        at org.gradle.internal.build.DefaultBuildLifecycleController.lambda$executeTasks$7(DefaultBuildLifecycleController.java:161)
        at org.gradle.internal.model.StateTransitionController.doTransition(StateTransitionController.java:247)
        at org.gradle.internal.model.StateTransitionController.lambda$tryTransition$7(StateTransitionController.java:174)
        at org.gradle.internal.work.DefaultSynchronizer.withLock(DefaultSynchronizer.java:44)
        at org.gradle.internal.model.StateTransitionController.tryTransition(StateTransitionController.java:174)
        at org.gradle.internal.build.DefaultBuildLifecycleController.executeTasks(DefaultBuildLifecycleController.java:161)
        at org.gradle.internal.build.DefaultBuildWorkGraphController$DefaultBuildWorkGraph.runWork(DefaultBuildWorkGraphController.java:156)
        at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:249)
        at org.gradle.internal.work.DefaultWorkerLeaseService.runAsWorkerThread(DefaultWorkerLeaseService.java:109)
        at org.gradle.composite.internal.DefaultBuildController.doRun(DefaultBuildController.java:164)
        at org.gradle.composite.internal.DefaultBuildController.access$000(DefaultBuildController.java:45)
        at org.gradle.composite.internal.DefaultBuildController$BuildOpRunnable.run(DefaultBuildController.java:183)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
Caused by: org.gradle.process.internal.ExecException: A problem occurred starting process 'command 'ng''
        at org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241)
        at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218)
        at org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:370)
        at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87)
        at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
Caused by: net.rubygrapefruit.platform.NativeException: Could not start 'ng'
        at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start(DefaultProcessLauncher.java:27)
        at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start(WrapperProcessLauncher.java:36)
        at org.gradle.process.internal.ExecHandleRunner.startProcess(ExecHandleRunner.java:98)
        at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:71)
        ... 3 more
Caused by: java.io.IOException: Cannot run program "ng" (in directory "/some/directory/that/does/exist"): error=2, No such file or directory
        at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start(DefaultProcessLauncher.java:25)
        ... 6 more
Caused by: java.io.IOException: error=2, No such file or directory
        ... 7 more

Thank you for your interest in Gradle!
Your issue appears to be a question about how to use Gradle. Your question might be better answered on our forums or StackOverflow. We have several resources on help.gradle.org that you should check out first.
If you think you have come across a Gradle bug, please file a new issue describing the problem and how to reproduce it.
If you think Gradle is missing a feature, please file a new issue describing your use case for the feature.

Looks like ng is not on your PATH.

Thanks for looking at this ticket but I think you've been a bit hasty in closing it.
To clarify, this build has been working for a couple of years with earlier versions of Gradle.
ng is on the PATH. But I agree that it seems as though it's not when Gradle runs.
Running ng from the command line in that directory always works.
It only fails when run from Gradle, but not every time.

Sorry that you're having trouble with Gradle!
Your issue lacks information about how to reproduce the problem you're having. A reproducer project can really help us track down and fix your problem quicker.  We may also be able to suggest workarounds or ways to avoid the problem if we can reproduce it.
You can use the following as a base for your reproducer: https://github.com/gradle/gradle-issue-reproducer
This issue will be closed after 7 days, unless you can provide more information.

Ok, this might be a genuine problem then, but pls. provide us with a reproducer to simplify our investigation.

Hi @kevinstembridge . Do you think you'll be able to provide some kind of reproducer?


Functions to store and retrieve marker data

Added two functions to the DataStore() class. One makes all the markers created by the user into a list so they can be retrieved and the second function stores the properties of each marker.

Please perform:
git reset --soft 7707cd18ffb1a06c3218aa71810979179fed690f
git rebase develop


Empty incoming changes not recognised

Thanks for the bug report, I'll look into this 👍

I also had this issue on vscode: Version 1.8.1 Commit ee428b0eead68bf0fb99ab5fdc4439be227b6281 Date 2016-12-19T14:41:20.664Z Shell 1.4.6 Renderer 53.0.2785.143 Node 6.5.0

Greate extension!
Empty current not handled too.

When do you have plans to fix this issue??? it would really helpful!!

I also just observed this problem.
Otherwise, excellent tool.

I don't know this environment well enough to do a fix, test, and pull request, but it looks like the problem is in Line 19 of mergeConflictParser.ts:
const conflictMatcher = /(<<<<<<< (.+)\r?\n)^((.\s)+?)(^=======\r?\n)^((.\s)+?)(^>>>>>>> (.+)$)/mg;
The regular expression looks for a line of text between each of the markers. In the case of insertions or deletions, there isn't such a line for one of the change lines.


MIssing GET /vectors/list endpoint

Are you planning/already working on a missing list endpoint? https://docs.pinecone.io/guides/data/list-record-ids
Or do you need a hand with this?
Monkey patch example for reference:
# /config/initializers/pinecone.rb

#
# Monkey patch to add not implemented #list method to vectors (Pinecone::Vector)
# https://docs.pinecone.io/reference/api/data-plane/list
#
module Pinecone
  module ListEndpoint
    def list(prefix: '', limit: nil, pagination_token: nil, namespace: '')
      query_string = URI.encode_www_form({ prefix:, limit:, paginationToken: pagination_token, namespace: } )
      self.class.get("#{@base_uri}/vectors/list?#{query_string}", options)
    end
  end
end

Pinecone::Vector.prepend Pinecone::ListEndpoint

@xzdshr Thanks for the heads up. For a long while this endpoint wasn't available so it escaped my notice. It looks like it only works for serverless indexes.
Would you like to take a crack at the PR?

#36


fix operation accessibility

Ideally, we should have a test case for typespec input of mgmt. So that, we should have seen this in the first place.


Support custom user defined ID patterns (on model and global basis)

Problem
I prefer to scope my ids with initials of the models. This helps developers and customer support reduce any confusion by knowing exactly what model an ID corresponds to.  Stripe uses this heavily.
Eg:
usr_<id>
post_<id>
price_<id>

Suggested solution
It would be nice to allow developers to override the default ID generator (as an advanced feature).
This may be coupled with the idea to allow the user to define the ID generation. For example, using nanoid or shortid  as the id generator.
import { nanoid } from 'nanoid';
prisma.generateId = () => nanoid();
prisma.user.generateId = () => `u_${nanoid()}`;

Alternatives
My preference though would be to do this as close to the schema definition as possible. So another preferable option could be to allow support for other id generators + prefixes in the schema definition.
eg:
model User {
    id  @id(type: "nanoid", prefix: "u_")
}

Additional context
Example of stripe id prefixes:
https://gist.github.com/fnky/76f533366f75cf75802c8052b577e2a5

What's the progress on this?

Bumping this up

Lil' bump ! We would use this heavily in our apps too

Yes, I would love to have support for that as well. Stripe saved me a ton of time thanks to those prefixes.

Up, we need this

There is a matter of prefixing things using middleware. If a bigger configuration is out of the question (like setting prefix on schema level), how about adding nanoid support at least?

I saw there is a similar issue present here: https://github.com/prisma/prisma/issues/12125
After tweeting this: https://twitter.com/jacek_smolak/status/1544805438344122371 I was asked to write about my use-case, so here it is.
The problem
When I saw what the possible options for generating IDs (as a string) with Prisma are, I noticed there are cuid() and uuid(). After reading about both and discovering nanoid and learning it is better (I suggest Googling it, and of course this is not 100% true [it being better] for everyone), I wasted to make it possible to be used for Prisma's schema.
The (mid) solution
I discovered that I could mutate the data for certain actions before it hits the DB. And in order to do that, one can use middleware. tl;dr - for create action you take the payload and overwrite the id property with whatever you want. Here's what I did (not exact code, but you will get the idea):
export const generateModelId: Prisma.Middleware = async (params: Prisma.MiddlewareParams, next) => {
  if (params.action === "create") {
    switch (params.model) {
      case "User":
        params.args.data.id = generateUserId();
        break;

      // ...
    }
  }

  return await next(params);
};

And registering it:
prisma.$use(generateModelId);

I went this way to have separate ID generators for separate models so that I could go with prefixes. Why? I can't tell you how great they are if all you see is some IDs here and there in logs or in payloads etc. and not knowing exactly where they originate from. See my previous comment.
So, the generateUserId() (and any other) has this implementation:
import { generateId } from "./generateId";

export const USER_ID_PREFIX = "usr_";

export const generateUserId = () => generateId(USER_ID_PREFIX);

And the underlying generateId function is this:
import { customAlphabet } from "nanoid";

// I went with custom alphabet to limit mistakes with I and l and alike (not all but some)
const ALPHABET = "abcdefghijkmnopqrstuvwxyzABCDEFGHJKLMNPQRSTUVWXYZ1234567890_";

export const generateId = (prefix = "") => `${prefix}${customAlphabet(ALPHABET)()}`;

Problems with that solutions
Going with middleware I saw that:

Since schema.prisma has no @default(...) value set on @id type of column, I had to provide a default value in all of the code where given model was present. So e.g. if I have a User model and it looks like this:

User {
  id String @id
 ...
}

Then if I want to e.g. create a user in some parts of the code, I need to pass id with a value in any form, e.g.:
prisma.user.create({
  data: {
    id: 'I can put whatever here, or leave it as an empty string, as the middleware will overwrite it but I NEED to',
    email<EMAIL_ADDRESS>    name: 'John'
  },
});

That sux.

Upserting data. If you want to do that, then the usage looks like this:

prisma.user.upsert({
  where: {},
  update: {},
  create: {
    id: 'same situation as before',
    email<EMAIL_ADDRESS>    name: 'John'
  },
});

And then the payload in the middleware changes, and so I need to create separate switch / case model handling. That sux again.
A better solution
Minimal one
The minimal one would be to have a ID generator registered / added, something like:
interface CustomIdGenerator {
  name: string;
  generateId: () => string; // or a Promise<string> as some generators out there are async
}

// Strict naming convention so that it can be used in schema
const name = 'customGenerator';
const generateId = () => { ... }

prisma.addIdGenerator({ name, generateId });

Usage in prisma.schema:
User {
  id String @id @default(customGenerator())
 ...
}

Perhaps also adding a setIdGenerator to Prisma's interface - for overwriting a custom existing one, if need be. Just thinking out loud.
That would be the simplest version.
A slightly better one
This time model would be passed to the generator, so that if I wanted to have different prefixes set up for different models, I could do so.
interface CustomIdGenerator {
  name: string;
  generateId: ({ model }) => string; // or a Promise<string> as some generators out there are async
}

const name = 'customGenerator';
const generateId = ({ model }) => {
  switch(model) {
    case 'User':
      return 'usr_123';
      break;
  }
}

prisma.addIdGenerator({ name, generateId });

Usage in prisma.schema:
User {
  id String @id @default(customGenerator())
  ...
}

In both cases there's no detecting what method is using it, as the generator would just be used as any other built in.
Hope this was clear :v:

Yes, but I don't know if you can do it for all of the DBs supported by Prisma.

Hi @Zn4rK  Please tell me prisma.addIdGenerator({ name, generateId });
where does the addIdGenerator method get it? I use nestjs x prisma x postgresql.
Thanks you

Bump it. we need this instead of terrible long id which is not useful in small project.

Not really related to the feature request but : https://github.com/Vivalldi, any reason to thumbs down every bump on this particular issue ?

We are showing support of this support why thumb me down?

In my experience, the best practice is to react with 👍🏻 on the feature request rather than just "bumping" this in a new comment every time. All a bump comment does is notify every person watching a request. It's exhausting to watchers (and to maintainers who watch every issue). The less "bump" noise a maintainer has, the more likely they are to pay attention to an issue when the relevant discussion comes up (see Zn4rK's response for example). Nothing against individuals, just trying to keep the bumps to a minimum. I'll happily stop doing so as it seems you all are in favor of these bumps.

👍 then :)

@Zn4rK Thanks for post the nanoid function. I ran into a problem with default values and I realized that is due to the ending line of the function -- it should be VOLATILE not STABLE as we do not return the same results given the same arguments for all rows in a statement. With STABLE, when I added the new shortId column to a table of existing data, I ended up with the same identical value in the shortId column (or a migration failure if I applied @unique -- I'm not using @id as I already have an existing id column).
So the function should be:
CREATE EXTENSION IF NOT EXISTS pgcrypto;

CREATE OR REPLACE FUNCTION nanoid(
    prefix text DEFAULT null,
    size int DEFAULT 21
)
RETURNS text AS $$
DECLARE
id text := '';
  i int := 0;
  urlAlphabet char(64) := 'ModuleSymbhasOwnPr-0123456789ABCDEFGHNRVfgctiUvz_KqYTJkLxpZXIjQW';
  bytes bytea := gen_random_bytes(size);
  byte int;
  pos int;
BEGIN
  WHILE i < size LOOP
    byte := get_byte(bytes, i);
    pos := (byte & 63) + 1; -- + 1 because substr starts at 1 for some reason
    id := id || substr(urlAlphabet, pos, 1);
    i = i + 1;
END LOOP;
IF prefix IS NULL THEN
    RETURN id;
ELSE
    RETURN CONCAT(LOWER(prefix), '_', id);
END IF;
END
$$ LANGUAGE PLPGSQL VOLATILE;

More on this in the PostgreSQL docs: https://www.postgresql.org/docs/current/xfunc-volatility.html

@Zn4rK I realized that line is from the repo you referenced -- I'll go make an issue/PR over there.

Any plan to provide this feature in near future?
Currently I am using cuid everywhere in my code for custom Ids, but now have to move to new project, so curious to know if it will be planned in near future or not.

If you're using Postgres and just want a prefix on UUIDs you can do this:

Setup a model with a @default that uses dbgenerated()
model User {
  id    String    @id @default(dbgenerated("prefix_uuid('user_'::text)"))
  ...
}

Run npx prisma migrate dev --create-only (just following the instructions here)

Paste this SQL at the top of the generated migration
CREATE EXTENSION IF NOT EXISTS pgcrypto;

CREATE OR REPLACE FUNCTION prefix_uuid(prefix text) RETURNS text AS $$
BEGIN
    RETURN concat(prefix, gen_random_uuid());
END;
$$ LANGUAGE PLPGSQL VOLATILE;

Run npx prisma migrate dev

Thanks @Zn4rK and @cymen for your comments, partially based this on them 🙂

This would be great, another use case for this would be to generate ids with a custom prefix and sequences.
<prefix>_<id>
transaction_000000001
transaction_000000002
transaction_000000003
transaction_000000004
...
transaction_000099823

In ~4 months this issue/feature request is going to be 2 years old ;) Any chances of picking it up?

In ~4 months this issue/feature request is going to be 2 years old ;) Any chances of picking it up?
And it will be 10 years old if none of us will implement it 😉 2 years is enough to come to a conclusion that Prisma company does probably not see too much value in this or has other priorities. But the code is open source, so you can just grab the issue and implement it. Comments like yours and many others like bump, I need this won't help making this happen 😉

In ~4 months this issue/feature request is going to be 2 years old ;) Any chances of picking it up?

And it will be 10 years old if none of us will implement it 😉 2 years is enough to come to a conclusion that Prisma company does probably not see too much value in this or has other priorities. But the code is open source, so you can just grab the issue and implement it. Comments like yours and many others like bump, I need this won't help making this happen 😉

I will agree and disagree.
First - you're right. We should take matters into our own hands, as it is an Open Source project.
But also - if your users need it, and keep asking for it, what do you think should happen? ;)

But also - if your users need it, and keep asking for it, what do you think should happen? ;)
If you're not paying for their product then you're not a user they will care about 😅 Also, I assume all enterprises that cooperate with Prisma have other channels for support and feature requests than GitHub Issues.

If somebody needs nanoid, I just merged this: https://github.com/prisma/prisma-engines/pull/3556

If you're using Postgres and just want a prefix on UUIDs you can do this:

Setup a model with a @default that uses dbgenerated()model User {
  id    String    @id @default(dbgenerated("prefix_uuid('user_'::text)"))
  // ...
}

Run npx prisma migrate dev --create-only (just following the instructions here)
Paste this SQL at the top of the generated migrationCREATE EXTENSION IF NOT EXISTS pgcrypto;

CREATE OR REPLACE FUNCTION prefix_uuid(prefix text) RETURNS text AS $$
BEGIN
    RETURN concat(prefix, gen_random_uuid());
END;
$$ LANGUAGE PLPGSQL VOLATILE;

Run npx prisma migrate dev

Thanks @Zn4rK and @cymen for your comments, partially based this on them 🙂

FWIW I've been prefixing my PG db is'd using MD5 random ('transaction-'::text || md5((random())::text)) as column default.  Spits out a nice manageable id like transaction-3wcvvxnfd7m3ljo9i7y13m.

If you're using Postgres and just want a prefix on UUIDs you can do this:

Setup a model with a @default that uses dbgenerated()model User {
  id    String    @id @default(dbgenerated("prefix_uuid('user_'::text)"))
  // ...
}

Run npx prisma migrate dev --create-only (just following the instructions here)
Paste this SQL at the top of the generated migrationCREATE EXTENSION IF NOT EXISTS pgcrypto;

CREATE OR REPLACE FUNCTION prefix_uuid(prefix text) RETURNS text AS $$
BEGIN
    RETURN concat(prefix, gen_random_uuid());
END;
$$ LANGUAGE PLPGSQL VOLATILE;

Run npx prisma migrate dev

Thanks @Zn4rK and @cymen for your comments, partially based this on them 🙂

"If you're using" is not an answer. Any solution here should be DB-agnostic and provided by Prisma'a API.

"If you're using" is not an answer. Any solution here should be DB-agnostic and provided by Prisma's API.

Ok then I suppose I should just tell the boss my delivery for a prefixed id in PG will be delayed until Prisma gets around to providing a versioned release supporting the requirement.
Get outta here....and a big thank you to all the other comments here that provide hacks and workarounds to help me out.

"If you're using" is not an answer. Any solution here should be DB-agnostic and provided by Prisma's API.

Ok then I suppose I should just tell the boss my delivery for a prefixed id in PG will be delayed until Prisma gets around to providing a versioned DB-agnostic release supporting the requirement.
Get outta here....and a big thank you to all the other comments here that provide hacks and workarounds to help me out.

Or you can go with a middleware solution for now. Have a look at my comment, where I've presented it. I am using it in my project, and when Prisma will support it at some point in time, I will remove it.

@smolak btw, you could keep the default value on the model to avoid issue #1 in solution: setting id in the create/update payload to a random value
id           String    @id @default(cuid())

middleware will provide an actual value, so default is not used

@AndreyMarchuk - that is a good idea. But it has some downsides too, and a couple of them:

ID generation will be doubled (a tiny efficiency impact)
if you forget to set an ID in the middleware, you will have an inconsistency on those models (cuid vs the one you want)

The way that I have it set up now is that I need to provide an ID on the model, and I am setting the same enum value everywhere so that if I do forget to set an ID on the model through the middleware, I will get an exception from the DB that ID is not unique.

If you're using Postgres and just want a prefix on UUIDs you can do this:

Setup a model with a @default that uses dbgenerated()model User {
  id    String    @id @default(dbgenerated("prefix_uuid('user_'::text)"))
  // ...
}

Run npx prisma migrate dev --create-only (just following the instructions here)
Paste this SQL at the top of the generated migrationCREATE EXTENSION IF NOT EXISTS pgcrypto;

CREATE OR REPLACE FUNCTION prefix_uuid(prefix text) RETURNS text AS $$
BEGIN
    RETURN concat(prefix, gen_random_uuid());
END;
$$ LANGUAGE PLPGSQL VOLATILE;

Run npx prisma migrate dev

Thanks @Zn4rK and @cymen for your comments, partially based this on them 🙂

FWIW I've been prefixing my PG db is'd using MD5 random ('transaction-'::text || md5((random())::text)) as column default. Spits out a nice manageable id like transaction-3wcvvxnfd7m3ljo9i7y13m.
EDIT: Just ran a migration in turborepo using the following custom id field:
id String @id @default(dbgenerated("concat('prefix_', md5(random()::text))"))
will generate an id something like prefix_x3u6ewghvjc7wazgazimk
you can also trim the generated id to say prefix + 10 random() chars using something like this:
 id String @id @default(dbgenerated("concat('prefix_', substring(md5(random()::text), 0, 10))"))
will generate a shoter id something like prefix_x3u6ewghvjc

The trouble with this is that with each migration, Prisma wants to add this default value. Prisma seems to not detect that the change has already been made in the database.

any progress for this?

Any updates? Surprised a prefix solution hasn't been implemented yet.


Withdrawal function(V3) not implemented

In the API reference, the POST /withdrawals is defined, but it is not implemented on V3

Hey @hdnauth,
Unfortunately, currently I don't have time to add these to the api (maybe in a month or 2), but PRs are always welcome.


unable to run node-speaker in Electron (on windows)

Electron version: v0.36.9
Operating system: Windows 10 Pro x64

I cloned Node-Speaker, ran npm install in it's folder.
(Output:)
$ npm install

><EMAIL_ADDRESS>install ..\node-speaker
> node-gyp rebuild

..\node-speaker>if not defined npm_config_node_gyp (node "C:\Users\[User]\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "" rebuild )

Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  win32.c
  win_delay_load_hook.c
  output.vcxproj -> ..\node-speaker\build\Release\\liboutput.lib
  binding.cc
  win_delay_load_hook.c
     Creating library ..\node-speaker\build\Release\binding.lib and object ..\node-speaker\build\Release\binding.exp
  Generating code
  Finished generating code
  binding.vcxproj -> ..\node-speaker\build\Release\\binding.node
npm WARN<EMAIL_ADDRESS>No license field.

When I test it running $ node examples/sine.js, it works fine.
When I test it running $ electron examples/sine.js, I get this error:
Error
 A dynamic link library (DLL) initialization routine failed.
\\?\..\node-speaker\build\Release\binding.node
    at Error (native)
    at process.module.(anonymous function) [as dlopen] (ATOM_SHELL_ASAR.js:159:20)
    at Object.Module._extensions..node (module.js:450:18)
    at Object.module.(anonymous function) [as .node] (ATOM_SHELL_ASAR.js:159:20)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at bindings (..\node-speaker\node_modules\bindings\bindings.js:76:44)
    at Object.<anonymous> (..\node-speaker\index.js:9:38)

:sob:
Am I doing something wrong?
I also tested it on Mac and Linux and it works fine there
So can you help me with this bug?
Thanks...

node-speaker relies on a native Node module, you need to rebuild native module to target Electron, as explained in the docs.

unfortunately that does not help.
It is also an other error then what you get when you are running the wrong build...
more ideas maybe?

What doesn't help? What did you try? What errors did you get?

rebuilding with 'electron-rebuild' doesn't help
I tried it on the 'node-speaker' module it self and on a project with the 'node-speaker' dependency
and I got the same errors

This looks similar to https://github.com/atom/node-spellchecker/issues/18 which seemed to be resolved via targeting a specific visual studio version.
Perhaps you want to try what this comment mentions https://github.com/atom/node-spellchecker/issues/18#issuecomment-128350864

:cry: It didn't work for me...
this is what I did
notes :

I installed NodeJs @ c:\nodejs.
I updated npm globally to the most recent version with npm install npm -g
I have Visual Studio Community 2015 version 14.0.24720.00 Update 1 installed.
I use the latest python 2.7.10 version.
I ran npm install -g node-gyp --msvs_version=2015
and ran npm uninstall speaker; npm install speaker
finally I ran node-gyp rebuild --target=0.30.2 --arch=x64 --dist-url=https://atom.io/download/atom-shell

But then I got a new error:
C:\>node-gyp rebuild --target=0.30.2 --arch=x64 --dist-url=https://atom.io/download/atom-shell
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp info spawn C:\Python27\python.EXE
gyp info spawn args [ 'C:\\Users\\LeMe\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-G',
gyp info spawn args   'msvs_version=auto',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\LeMe\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\LeMe\\.node-gyp\\0.30.2\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\\Users\\LeMe\\.node-gyp\\0.30.2',
gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\LeMe\\AppData\\Roaming\\npm\\node_modules\\node-gyp',
gyp info spawn args   '-Dnode_lib_file=node.lib',
gyp info spawn args   '-Dmodule_root_dir=C:\\',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'C:\\build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp: binding.gyp not found (cwd: C:\) while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (C:\Users\LeMe\AppData\Roaming\npm\node_modules\node-gyp\lib\configure.js:305:16)
gyp ERR! stack     at emitTwo (events.js:100:13)
gyp ERR! stack     at ChildProcess.emit (events.js:185:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Windows_NT 10.0.10586
gyp ERR! command "C:\\nodejs\\node.exe" "C:\\Users\\LeMe\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--target=0.30.2" "--arch=x64" "--dist-url=https://atom.io/download/atom-shell"
gyp ERR! cwd C:\
gyp ERR! node -v v5.7.1
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok

Probably due to the "Atom Shell" no longer exist and that we now use "Electron"...
So can you help me fix this or can you provide me with a alternative "step 7"?

Okay, I was in the wrong folder... Oops!
But it still didn't work.
I even tried these for step 7:

node-gyp rebuild --target=5.7.1 --arch=x64 --dist-url=https://atom.io/download/atom-shell
node-gyp rebuild
npm rebuild
npm rebuild --msvs_version=2015

But still the same error...:sob:

You need VS2013 to compile against Electron

same results...
:cry:
I got the old error again:
Error
 A dynamic link library (DLL) initialization routine failed.
\\?\..\node-speaker\build\Release\binding.node
    at Error (native)
    at process.module.(anonymous function) [as dlopen] (ATOM_SHELL_ASAR.js:159:20)
    at Object.Module._extensions..node (module.js:450:18)
    at Object.module.(anonymous function) [as .node] (ATOM_SHELL_ASAR.js:159:20)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at bindings (..\node-speaker\node_modules\bindings\bindings.js:76:44)
    at Object.<anonymous> (..\node-speaker\index.js:9:38)

BTW
https://atom.io/download/atom-shell is outdated

After many tries, I got a new error: :angry:
After executing the following commands:
$ cd C:\Users\IEUser\Documents\melome_player\app\node_modules\speaker
$ HOME=~/.electron-gyp node-gyp rebuild --target=0.37.5 --msvs_version=2013 --arch=ia32 --dist-url=https://atom.io/download/atom-shell

$ electron examples\sine.js
- or -
$ cd C:\Users\IEUser\Documents\melome_player\app
$ electron .

I got this error:
Error: %1 is not a valid Win32 application.

\\?\C:\Users\IEUser\Documents\melome_player\app\node_modules\speaker\build\Release\binding.node
    at Error (native)
    at process.module.(anonymous function) [as dlopen] (ATOM_SHELL_ASAR.js:158:20)
    at Object.Module._extensions..node (module.js:440:18)
    at Object.module.(anonymous function) [as .node] (ATOM_SHELL_ASAR.js:158:20)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at bindings (C:\Users\IEUser\Documents\melome_player\app\node_modules\bindings\bindings.js:76:44)
    at Object.<anonymous> (C:\Users\IEUser\Documents\melome_player\app\node_modules\speaker\index.js:8:34)

When I execute:
$ cd C:\Users\IEUser\Documents\melome_player\app\node_modules\speaker
$ HOME=~/.electron-gyp node-gyp rebuild --target=0.37.5 --msvs_version=2013 --arch=x64 --dist-url=https://atom.io/download/atom-shell

I get the old error...
Can someone try this for me on their win10 (x64) system?
I don't know what I am doing wrong.... :sob:
just install 'electron-prebuilt' global npm install -g electron-prebuilt
install 'node-speaker' somewhere npm install speaker or git-clone it Git:node-speaker
rebuild away!
and then run $ electron examples\sine.js.
It should generating a 440.0 hz sine wave for 2 seconds
and then please tell me how you did it, in the smallest detail if you can
Thanks!!!


wrong factorio version on stable

this link is giving 1.1.103 on stable for factorio instead of 1.1.101 current version of factorio https://hub.docker.com/r/factoriotools/factorio

Looks like the updater got stuck, but its at least back with 1.1.104 now

So this issue may not be resolved it was stuck on the experimental but both the experimental and normal factorio are the same right now

Based on https://factorio.com/api/latest-releases and https://github.com/factoriotools/factorio-docker/blob/master/buildinfo.json#L54-L55 this is correct


feat: display currency in tx history

adds display currency in tx history

This PR still requires two things:

Fee to returned from the api in a display amount
Regenerate the storybook mock data with the new tx fields

I also updated the background colors to match other branding in the app, although I am now realizing it may not be enough contrast with the white text.


markdown editor added

Pull Request Template
Markdown Editor -
The Markdown editor helps user to create, open, write, view and save markdown file.
Issue no.- #908
Self Check(Tick After Making pull Request)

[x] This issue was assigned to me.
[x] One Change in one Pull Request
[x] My file is in proper folder (Name of folder should be in lowercase with no space in between) (E.g. meet_schedular)
[x] I am following clean code and Documentation and my code is well linted with flake8.
[x] I have added README.md and requirements.txt (Include version numbers too e.g. pandas==0.0.1) with my script
[x] I have used REPO README TEAMPLATE (Necessary)
[x] Just including required dependencies in requirements.txt (Don't include Python version too)

If issue was not assigned to you Please don't make a PR. It will marked as invalid.

Great work @kaliappan01


Apple Silicon compatibility

Quick question: what is required to get this example to work on Apple Silicon?
building for macOS-x86_64 but attempting to link with file built for macOS-arm64

It should just work for the code in this repository (I'm on an M1 myself).
For everything else you should describe in more detail what you're doing.

Apologies. I can leave this issue here despite my own embarrassment, if other people run into the same.
Had at some point configured terminal to run under Rosetta 2 and evidently failed to switch it back.
uname -m must return arm64 on Apple Silicon otherwise swift compiler will compile for the wrong architecture and won't link to the rust dylib.

Don't worry. I've run into that several times now (in both directions). Glad you were able to figure it out.


create_map<Unaligned>

Is it possible to do this DatabaseOptions::create_map::<Unaligned<f64>>()?
I get an error:
error[E0277]: the trait bound `f64: lmdb::traits::LmdbRaw` is not satisfied
  --> src/index.rs:49:52
   |
49 |             (IndexKind::Unique, KeyType::Float) => DatabaseOptions::create_map::<Unaligned<f64>>(),
   |                                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `lmdb::traits::LmdbRaw` is not implemented for `f64`
   |
   = note: required because of the requirements on the impl of `lmdb::traits::LmdbOrdKeyIfUnaligned` for `f64`
   = note: required because of the requirements on the impl of `lmdb::traits::LmdbOrdKey` for `lmdb::Unaligned<f64>`
   = note: required by `lmdb::DatabaseOptions::create_map`

The compiler's error message here is unfortunate. The actual problem is that f64 is not LmdbOrdKeyIfUnaligned because f64 is not Ord.
You have a couple options here.
The u64 representation of f64 sorts real numbers and infinities the same way and gives NaNs a consistent (but not useful) total ordering with the rest of the values, so you could use create_map::<Unaligned<u64>>() and use from_bits and to_bits to go between u64 and f64 in your code.
The other option is to define your own newtype around f64 and then add the needed impls to make it work here:
#[derive(Clone, Copy, Debug)]
struct YourWrapper(f64);
impl PartialEq for YourWrapper { ... }
impl Eq for YourWrapper { }
impl PartialOrd for YourWrapper { ... }
impl Ord for YourWrapper { ... }
unsafe impl LmdbRawIfUnaligned for YourWrapper {
  fn reported_type() -> String { "YourWrapper".to_owned() }
}
unsafe impl LmdbOrdKeyIfUnaligned for YourWrapper { }

There are some suggestions for dealing with NaNs in this SO question. Since your Ord impl will be called from C code, if you plan to use the option that delegates to a derived PartialCmp, you'll need to use something like .unwrap_or_else(::std::process::abort) instead of plain .unwrap() since panicking across C stack frames is undefined behaviour.

Thanks for explanation. I understand that floating point types have only partial eq/ord implementations but compiler really confused me by this message.


Not able to use toggleSeries with next js application

I want to toggleSeries data of a chart in my next js application. I am trying to use that method in 2 different ways, but none of them is working. I will show you the error I am getting with both these methods differently. Please help me with a solution.
Method 1:
import ApexCharts from 'apexcharts';

toggleSeries = (seriesName) => {
  ApexCharts.exec('myChartId', 'toggleSeries', 'seriesName');
}

In method 1 there are 2 problems
Most of the time I get window is not defined for ApexCharts
Second, sometimes I get: apexcharts__WEBPACK_IMPORTED_MODULE_9___default.a.exec is not a function
In order to resolve error: window is not defined I use dynamic import as I use dynamic import for react-apexcharts see below, even checking from typeof window !== undefined is not working here
Method 2:
const ApexCharts = dynamic(() => import('apexcharts'), { ssr: false });

toggleSeries = (seriesName) => {
  ApexCharts.exec('myChartId', 'toggleSeries', 'seriesName');
}

In method 2 it says ApexCharts.exec is not a function.
Please help me with the solution for this

Basically exec function is coming undefined
Can anybody help ??


create-setters: handle multiple lines and substrings

This pr adds the following changes

Doesn't add the comments to the scalar values with multiple lines
Matches the longest substring setter value to set the comment
Updates the docs accordingly

Please rebase to pick up CI fix in #373

All *.md files requires @droot's approval to ensure consistency across kpt.

@droot Lets merge this Pr. I can have a follow up PR with suggested changes.

@droot Lets merge this Pr. I can have a follow up PR with suggested changes.

Ack.


[Proposal] Add clamp(to:) to the stdlib

This proposal is an attempt to add clamp(to:) to the Swift standard library.
The idea has been discussed (with some great feedback) on the following Swift Evolution mail threads:
Draft Proposal Thread
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170313/thread.html#33831
Idea Pitch Thread
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170306/thread.html#33674
Thanks!

@DougGregor Thank you for assigning @dabrahams and @airspeedswift !
Is there something I could do to help move this along or is this proposal not a priority at this time?

Hi @Nirma,
I feel strongly that an empty range should not be treated specially here.  Clamping to an empty range should yield the value of the range's lowerBound / upperBound.

@dabrahams Thanks so much for the feedback!
Yeah I was a little unsure about how to treat empty ranges, but it makes sense to me to just clamp
on their lowerBound / upperBound for consistency.

@dabrahams I updated the proposed implementation like so:

extension Strideable where Stride: Integer {
    func clamped(to range: Range<Self>) -> Self {
        let clampRange: ClosedRange<Self>

        if range.lowerBound == range.upperBound {
            clampRange = range.lowerBound...range.upperBound
        } else {
            clampRange = range.lowerBound...(range.upperBound - 1)
        }

        return clamped(to: clampRange)
    }
}

How does it look now?

@JustinJiaDev Thanks for pointing that out! Fixed it!

@dabrahams @airspeedswift Thanks again for looking at this, is there anything I can do to possibly move this along?
Thanks!

Hello.
Can someone explain me why 42..<42 is valid range?

@bernikowich-cedoni There's more to an empty range than the values it encloses.  Think of what happens when you replace an empty range in a collection, for example.  In fact, insert(contentsOf:) is implemented in terms of replaceSubrange.  In general, discontinuities where valid code becomes invalid (e.g. "replacing is fine until the range is empty") is bad for usability, and should only be undertaken where there is a substantial efficiency cost to providing continuously valid behavior, or there is a very high chance of catching bugs by trapping.  HTH

@dabrahams so this code returns not empty range from empty range?
    let clampRange: ClosedRange<Self>

        if range.lowerBound == range.upperBound {
            clampRange = range.lowerBound...range.upperBound
        }

@bernikowich-cedoni if you're asking whether clampRange is empty, the answer is no.  There's no such thing as an empty ClosedRange.

@Nirma  Thanks for your contribution!. The next time you propose new APIs for the standard library, it would be a good idea to include the attendant documentation comments.


[Hub Generated] Review request for Microsoft.AlertsManagement to add version preview/2023-07-12-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I have reviewed the general guidance on the spec PR review process: https://aka.ms/specprreview.
[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data-plane related specifications.
[x] I commit to follow the Breaking Change Policy.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can request review from an ARM API Review board.

ARM API changes review

If you want for the ARM team to review this PR, you must add the ARMReview label.
The automation may automatically add the ARMReview label, if appropriate.
If this happens, proceed according to guidance given in GitHub comments also added by the automation.

Breaking change review
If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.
Getting help

For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For additional help, see https://aka.ms/azsdk/support/spectools.

@rkmanda Can You please review this PR?

The breaking change is because I switched from #/parameters/api-version to common-types/resource-management/v2/types.json#/parameters/ApiVersionParameter
The Swagger LintDiff contains issues for a lot of existing APIs that I don't want to fix in this PR.
thank you!

@rkmanda Can You please review this PR?

The breaking change is because I switched from #/parameters/api-version to common-types/resource-management/v2/types.json#/parameters/ApiVersionParameter
The Swagger LintDiff contains issues for a lot of existing APIs that I don't want to fix in this PR.
thank you!

For the breaking changes you need to follow the process described here: https://github.com/Azure/azure-rest-api-specs/pull/24854#issuecomment-1643462719

or lintDiff error, they are listed if they are introduced in current version, are all of these from previous version? If so, what will be the plan to fix these? Going forward you should have a work item to track these fixes. For the ones that you'll be able to fix, you should try to fix th

@zizw123 They are related to existing APIs not to the new private preview I've added.
I will add a WI to fix the existing API.

/azp run

/azp run

@ms-zhenhua I've added suppression in the readme file in order to pass the lint validations that were not caused by this new api version.

The folder structure doesn't look like its supposed to.
You should be including swaggers for ALL supported apis that are in the new api-version. Not just the new ones...
Or switch to using serviceGroup folder structure.
https://github.com/Azure/azure-rest-api-specs#folder-structure-for-service-group

The folder structure doesn't look like its supposed to. You should be including swaggers for ALL supported apis that are in the new api-version. Not just the new ones...
Or switch to using serviceGroup folder structure. https://github.com/Azure/azure-rest-api-specs#folder-structure-for-service-group

This is how it used to be done prior to this PR.
I've created a new work item to fix current exisitng issues Product Backlog Item 24832853: Fix existing swagger Lint errors
Can I work on this fix as part of the new WI?


Refactor Cache interfaces

I think we can simplify dskit in the following ways:

Add a Delete method to Cache - If an LRU doesn't have a delete method it can be a no-op. If people feel strongly about not adding a Delete method that doesn't work, we can split the interface into Cache and DeletableCache.
Remove cache.RemoteCacheClient - it's an abstraction that's only used in a handful of places.
Remove cache.MemcachedCache - it's a wrapper around remoteCache which doesn't do much.
Remove cache.RedisCache - it's a wrapper around remoteCache which doesn't do much.
Rename and refactor methods in cache.memcachedClient to implement cache.Cache.
Rename and refactor methods in cache.redisClient to implement cache.Cache.

@56quarters You were also mentioning about removing cache.RemoteCacheClient in another PR comment. You may want to share your thoughts here.


Nice wallet specially for XRP and XLM.

0x1Fa4397d73b1C17C88FBb978b36ad50Bf4d12E61

Please leave your address in https://github.com/ultiledger/utoken/issues/21
Don't open new thread.


Move drawing code to drawing

move bloq counts drawing functionality to drawing package
show_xxx jupyter helper functions for all the different things
organize qualtran.drawing submodules: split classical sim drawer and bloq counts graph into their own modules

@tanujkhattar anything else?


Template preview modal - Double scroll

We should not have double scroll on this info modal
As a (type of user)
I want (goal)
so that (reason/ why/ value)
Acceptance Criteria
Scenario 1:
GIVEN ... (you or your condition)
WHEN ... (what you do)
THEN ... (what you see)
Scenario 2:
xxxxxx
Validation Rules?
(If yes, list here)
Screenshot
(Link above will always be the most up-to-date version.)

@TomChapmanGov


Type alias

@rezonant
This is a big update, it would be nice to merge and publish this with a beta/alpha tag (next) just to not cause any problem downstream.
Compiler Feature:

serialize -> serializeExpression support more inputs and there's no need to wrap everything in literalNode
also the function checks if the return type is an actual expression

Serialize string template to aid in the creation of new nodes, i find the following slightly more readable.

            Serialize`(t => __RΦ.t["${customId}"] =
            {TΦ: "${T_ALIAS}",
            name: "${emitName}",
            a: t,
            t: () => ${forwardedType},
            p: ${decl.typeParameters ? decl.typeParameters.map(p => p.name.text) : []}
            })(${identifierName});`, -> this will create all the nodes with ts.Factory

Feature:

Type alias rt information

type A = number;
reflect<A>().isAliased() === true
reflect<A>().kind === "class" // aliases are transparent to the end user if they don't care
reflect<A>().as('alias').name == "A"
reflect<A>().as('alias').kind == "alias"

Type TypeParameter rt information

type A<T> = number;
reflect<A>().as("alias").hasArguments() === true
reflect<A>().as("alias").arguments() === ["T"]

type B<T> = {a:T -> 'encoded as kind variable'}
reflect<B>().as("alias").hasArguments() === true
reflect<B>().as("alias").arguments() === ["T"]
const obj = reflect<B>().as("alias").reflectedType.as("object")
obj.members[0].type.kind === 'variable'
obj.members[0].type.as("variable").name === 'T'

Rt type builders

const builderA = new InterfaceTypeBuilder();
builderA.name = "A";
builderA.addProperty("a", Number);
builderA.addProperty("b", String, F_OPTIONAL);
const t:ReflectedTypeRef = builderA.getType();
t.matchesValue({a:1}) === true

Generic support

type A<T> = T;
let t = reflect<A<Array<number>>>();
t.kind === "generic";
const result = t.resolveType();
t.kind === 'array'

/*matchesValue for generics */
export interface I<T> {
                    a: T,
                    b: T,
                    c: T,
};
export const t = reflect<I<number>>();
t.matchesValue({a:1,b:1,c:1}) === true

/* build generic types */
t = reflect<A>().createType(Number);
t.matchesValue(1) === true
t = reflect<A>().createType(String);
t.matchesValue("hello") === true

resolveType() ReflectedTypeRef
Return the computed type following the chain of aliases, generics, mapped ect.

export type C<T> = T;
export type B<T> = C<T>;
export type A<T> = B<T>;
export const a = reflect<A<1>>().resolveType();
a.as('literal').value === 1;

Tests:

added test case for pretty much everything

What is missing:

Generics for interface/class/methods/functions

I have enabled CI builds for PRs and pulled in this branch to get it started. Future commits should run the CI now.
Hoping to look at this much closer soon, but in the mean time there are some failed tests, see https://app.circleci.com/pipelines/github/typescript-rtti/typescript-rtti/349/workflows/b9e938cf-adfb-4852-b52c-4ac90722ab4a

The CI will also run the "corpus" test suite. This test suite will compile and test a number of open source projects using the RTTI transformer, expecting them all to work as expected.

Thank you!
I usually run the test locally too.
I will add the missing features in the near future (failed tests)
On Sun, Jul 24, 2022, 6:48 PM William Lahti @.***>
wrote:

The CI will also run the "corpus" test suite. This test suite will compile
and test a number of open source projects using the RTTI transformer,
expecting them all to work as expected.
—
Reply to this email directly, view it on GitHub
https://github.com/typescript-rtti/typescript-rtti/pull/85#issuecomment-1193420457,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANLTRZ5M73FHEGNV23UAWV3VVXI35ANCNFSM54JIFYYA
.
You are receiving this because you authored the thread.Message ID:
@.***>

On the topic of TypeBuilder, I don't get the sense that this was required to complete the type-alias work, I'd prefer if we move that into a separate PR to discuss the use cases and merits.

In the future do be careful to keep features separate when drafting PRs, as reviewing something of this size is extremely difficult.

On the topic of TypeBuilder, I don't get the sense that this was required to complete the type-alias work, I'd prefer if we move that into a separate PR to discuss the use cases and merits.

It's used to build generic types at runtime, in general to make the test inside src/lib/value-matches-generics.test.ts to works properly.
like:

                import { reflect } from 'typescript-rtti';
                export type B<T> = {
                    a: T,
                }
                export type A<T,K> = {
                    a: T,
                    b: K,
                    c: [T,K],
                    d: B<T>,
                };
                export const t1 = reflect<A<number,string>>();
                // t1 === t2 they are the same type
                export const t2 = reflect<A>().createType(Number,String);

@rezonant
I fixed the recursive tests.
On the generic side classes and interface are incomplete as i saw that interfaces/classes that extends generics does not work.
This will be the work for a future pull.

forgot about the FLAGS for aliases :´)
fixed

Any news on this PR? The description sounds really promising, and I would love to be able to use reflection on generic type aliases!

After taking another look at this today, I'm going to close this PR. This is not due to quality of the work. I think there are issues with the core approach, the overall size is risky and there's a lot of unrelated changes, and it's not clear what goals emitting type alias information would accomplish.
Downsides of the concept of reflecting on type aliases:

It is impossible to encode alias references in inferred scenarios. For instance:type A = number;
function g(): A { return 123; }
function f() { return g(); } // <-- TS itself sees f() return value as number, not A

It's not clear how to expose the fact that an alias was used in a declaration within reflect()'s API without requiring that the alias be dealt with, which creates a lot of boilerplate and footgun corner cases

Downsides of this PR's implementation of type aliases:

Extending interface tokens / type reification in order to support aliases at the declaration site is heavy, (implementation complexity, compilation performance, file size) and should only be done if we really want the capability. Emitting aliases in the call-site (type ref) alone would be better, but then we lose the ability to uniquely identify them as we do with all other types (which have stable TS-compiler-given numeric IDs). Aliases do not actually exist as discrete Types within the TS compiler, so we would have to synthesize a way to identify them.

On the general front:

This is a massive PR which has a lot of formatting changes, refactorings, and even retools the entire emit path (builders). I don't entirely agree with all of the internal refactorings included, or at least I'd like to discuss them individually without the shadow of a larger feature set.
There are also some regressions regarding inference that I noticed while doing local testing. I think these cases are not well covered by the (existing) tests at the moment. I'm more than a little worried about this as given the extent of the changes being proposed, it's quite possible other untested pathways could be affected.

More than any other reason, I am struggling to understand why exposing type aliases would be useful over other RTTI reflection capabilities we already have. I would love to see use cases, but let's discuss them on issue #74. It does seem likely that users will reach for reflecting on aliases over reflect<MyAlias>.matchesValue() which already works today for validation/conditional scenarios and has none of the downsides/footguns.

Thanks for your clear explanation Cristian. We're still in the middle of some experiments with reflecting types, and I'm still new to typescript-rtti. We'll report in #74 with a clear use case if needed.


Cross compilers (rebased)

Taking over the PR: https://github.com/lf-edge/eve/pull/2978
Changes in this PR:

Rebase to master branch

LGTM. I don't know if we need to update EVE to use lf-edge/eden#840 to make the volume test pass.

I think so, it makes sense, let's merge that one first.

Seems like the timeouts are caused by the eden run ending up building all of EVE from source.
I think it makes sense to  merge this PR since the built artifact works, and then check that we can actually run eden for other PRs once this is in. If it causes future eden runs to time out then we'll have to back it out.


Added public compressedSize & uncompressedSize to Entry.

Hello,
I added two public variables in order to get the compressed and uncompressed size of an Entry.
Best
Marco

Hi Marco,
Sorry for the late reply.
Entry only offers a bare minimum of metadata by design. By adding more public properties to the class we'd probably end up duplicating the whole state of the CentralDirectoryStructure and the LocalFileHeader in Entry. We could expose uncompressedSize via the Entry.attributes dictionary. This already contains the permissions and the modification time stamp.
Foundation/FileManager has no notion for compression so it sadly doesn't offer a FileAttributeKey that we could use for compressedSize.


non-sense segment is been generated

When doing schema change, error occurs when flushing segment.

Segment which size reaches OLAP_MAX_COLUMN_SEGMENT_FILE_SIZE will be flushed into disk. If the previous segment reach the threshold just right, and been flushed into disk. The following finalize() when closing ColumnDataWriter will generate a non-sense segment. In this scenario, undefined behavior will happens.


wget.exe has stopped working error MSB1009: Project file does not exist.

I get this windows error if i choose not to update to latest source on git,  it says "CMake configuration failed" and ends there.

Then when i choose to use the latest from git it shows lots of not found messages and ends with
MSBUILD : error MSB1009: Project file does not exist.
Switch: build\pvpgn.sln
[ R E L E A S E ]___
SOMETHING GONE WRONG :-(
Press any key to continue . . .

There was a problem with download source which I just fixed.
But it looks like your error is the same as here https://github.com/pvpgn/pvpgn-magic-builder/issues/31
Contact with me on<EMAIL_ADDRESS>if you can provide Teamviewer access.


lynis: 3.0.1 -> 3.0.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/lynis/versions.
meta.description for lynis is: "Security auditing tool for Linux, macOS, and UNIX-based systems"
meta.homepage for lynis is: "https://cisofy.com/lynis/"
meta.changelog for lynis is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.0.3 with grep in /nix/store/5l10lzq7isawrlffkvxn5cd39ybb83iy-lynis-3.0.3

directory tree listing: https://gist.github.com/abae2f3a13e3dab10984b6ab1dc017a3

du listing: https://gist.github.com/07aa919e0e047baf5deed6f55f16bbe2

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
lynis

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5l10lzq7isawrlffkvxn5cd39ybb83iy-lynis-3.0.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A lynis https://github.com/r-ryantm/nixpkgs/archive/1d6ebd3f203ce870143b4bad80aea5a76400b53a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5l10lzq7isawrlffkvxn5cd39ybb83iy-lynis-3.0.3
ls -la /nix/store/5l10lzq7isawrlffkvxn5cd39ybb83iy-lynis-3.0.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

lynis

Maintainer pings
cc @ryneeverett for testing.

Built and ran an audit.
I noticed that all of r-ryantm's bumps for a few hours yesterday added the "sha256-" prefix to the hash. I'm assuming that's ok.

Yes, that's okay since the min version of nix in nixpkgs supports that format.

Built and ran an audit.
I noticed that all of r-ryantm's bumps for a few hours yesterday added the "sha256-" prefix to the hash. I'm assuming that's ok.

Yes, that's okay since the min version of nix in nixpkgs supports that format.


updated strfmt to v0.20.2 (bsonobjectid validation)

Signed-off-by: Nick Dimov<EMAIL_ADDRESS>

This shouldn't be required afaik. if you update your strfmt locally you should be good. This repo only contains the code necessary to build the CLI

This shouldn't be required afaik. if you update your strfmt locally you should be good. This repo only contains the code necessary to build the CLI

You are right. I am closing this PR.


10 extract api methods

Ref #10
I have created the following API methods:
javacore_analyzer.process_javacores_and_generate_report_data
javacore_analyzer.generate_javecore_set_data
javacore_set.JavacoreSet.generate_report_files
javacore_set.JavacoreSet.get_javacore_set_in_xml

Also javacore_set.JavacoreSet is public API class.
I expected the change to be smaller but it is at it is.
All tests are passing
Please check if API methods have correct name and correct documentation.
Some of the methods/variables do not have public documentation as mainly used method will be javacore_analyzer.process_javacores_and_generate_report_data. I do not want to spend too much time on something I do not think will be frequently used in near future. The gap can be filled once there is a business need for this.
Also there is a missing update in README.md how to run API. I will add it once this is reviewed.

 As I agreed with Piotr, the fix looks good for him so we can merge it.


Fix ime popup coordinates and artifacts

Describe your PR, what does it fix/add?
Fixes #5255
Fixes #5256
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Is it ready for merging, or does it need work?
Ready

**
__**


Ability to set priority classes for the postgres pods

Since Kubernetes 1.8. we can speed-up the scheduling of database pods by pre-empting some stateless pods that are already running using the priorityClassName pod attribute:
https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
Add an ability to configure it for both individual postgres clusters and globally via the operator configuration.

The pre-requisite to that is updating the client-go library (https://github.com/zalando-incubator/postgres-operator/issues/307).

Implemented in
https://github.com/zalando-incubator/postgres-operator/commit/59f0c5551ecf858c320504d524fcdf92aea87295


nerdctl can not create volume successfully

I want to use -v command to create a volume and mount into container path:
docker run -d --name registry-https --restart always -p 443:443 -v /opt/tke-installer/registry:/var/lib/registry -v registry-certs:/certs -e REGISTRY_HTTP_ADDR=<IP_ADDRESS>:443 -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/server.crt -e REGISTRY_HTTP_TLS_KEY=/certs/server.key registry.tke.com/library/registry-amd64:2.7.1

For docker runcommand it can create the registry-certsand I can check certs  from /varlib/docker/volume/registry-certs/_data
# ls /var/lib/docker/volumes/registry-certs/_data/
server.crt  server.key

But for nerdctl it can not create the registry-certs volume:
# nerdctl run -d --name registry-https-test --restart always -p 443:443 -v /opt/tke-installer/registry:/var/lib/registry -v registry-certs:/certs -e REGISTRY_HTTP_ADDR=<IP_ADDRESS>:443 -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/server.crt -e REGISTRY_HTTP_TLS_KEY=/certs/server.key registry.tke.com/library/registry-amd64:2.7.1
FATA[0000] volume "registry-certs" not found: not found

Does nerdctlcan not support create volume when nerdctl run -v?
How to use nerdctl -vcommand to create volume like docker?
Thanks a lot.

Hi @Huimintai ,
the volume should start with / (e.g registry-certs) otherwise it will treat it like a nerdctl volume

Hi @Huimintai ,
the volume should start with / (e.g /registry-certs) otherwise it will treat it like a nerdctl volume
sthg like this :
# nerdctl run -d --name registry-https-test --restart always -p 443:443 -v /opt/tke-installer/registry:/var/lib/registry -v /registry-certs:/certs -e REGISTRY_HTTP_ADDR=<IP_ADDRESS>:443 -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/server.crt -e REGISTRY_HTTP_TLS_KEY=/certs/server.key registry.tke.com/library/registry-amd64:2.7.1

The registry-certs is a nerdctl volume.I want to nerdctl can create the volume for me.It is not a path.
The docker command can create the registry-certsfor me although I didn't create the volume before run the docker run -v registry-certs:/certs .
# docker volume ls
DRIVER              VOLUME NAME
local               registry-certs

ls /var/lib/docker/volumes/registry-certs/_data/
server.crt  server.key

Currently it has to be created with nerdctl volume create <NAME>

Yes,I can create the volume manully then I mount the volume into docker container.But I can not find the data from the volume:
# nerdctl volume create registry-certs
registry-certs

# nerdctl run -d --name registry-https-test --restart always -p 443:443 -v /opt/tke-installer/registry:/var/lib/registry -v registry-certs:/certs -e REGISTRY_HTTP_ADDR=<IP_ADDRESS>:443 -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/server.crt -e REGISTRY_HTTP_TLS_KEY=/certs/server.key registry.tke.com/library/registry-amd64:2.7.1
7fdc4dc42221ea59373bf5a98cbff261f5d6d6e76933497c85f88cc90289c00d

# nerdctl volume ls
VOLUME NAME       DIRECTORY
registry-certs    /var/lib/nerdctl/1935db59/volumes/default/registry-certs/_data
root@VM-0-28-ubuntu:~# ls  /var/lib/nerdctl/1935db59/volumes/default/registry-certs/_data
root@VM-0-28-ubuntu:~#

You can see it is empty without my data.But for docker container I can see the data :
# ls /var/lib/docker/volumes/registry-certs/_data/
server.crt  server.key

What's your nerdctl version? Could you try the latest version (v0.9.0)?

My nerdctl version:
# nerdctl version
Client:
 Version:	v0.8.3
 Git commit:	487f94aa7a8cfa833a1e96600d11b0c2bdc931f3

Server:
 containerd:
  Version:	v1.5.2
  Revision:	36cc874494a56a253cd181a1a685b44b58a2e34a

I try to use 0.9.0 to test.It can also can not find the certs in volume.
# nerdctl version
Client:
 Version:	v0.9.0
 Git commit:	39a46444754c581e020fffa63261f2a859c16bac

Server:
 containerd:
  Version:	v1.5.2
  Revision:	36cc874494a56a253cd181a1a685b44b58a2e34a

# docker run -it --rm --entrypoint=sh tkestack/tke-installer-amd64:2107f202f84d0f520983ab741501770a7e1c08d5
/app # ls
assets                certs                 data                  images.tar.gz         provider
bin                   conf                  hooks                 manifests             public.charts.tar.gz
/app # ls bin/
kubectl        tke-installer
/app # ls certs/
server.crt  server.key
/app #

# nerdctl run --name tke-installer -d --privileged --net=host --restart=always -v /etc/hosts:/app/hosts -v /opt/tke-installer/data:/app/data -v /opt/tke-installer/conf:/app/conf -v registry-certs:/app/certs tkestack/tke-installer-amd64:2107f202f84d0f520983ab741501770a7e1c08d5
24f166302ffd313d412c94b85fd40f7434a7f7bd52b18a7edb2019261cdc04fe
root@VM-0-28-ubuntu:~#
root@VM-0-28-ubuntu:~# nerdctl volume ls
VOLUME NAME                                                         DIRECTORY
4cb05dd0fbe7cdf6909f183066aa0da60dcf3900d8d4c680a499eb2dc62ec36d    /var/lib/nerdctl/1935db59/volumes/default/4cb05dd0fbe7cdf6909f183066aa0da60dcf3900d8d4c680a499eb2dc62ec36d/_data
registry-certs                                                      /var/lib/nerdctl/1935db59/volumes/default/registry-certs/_data
test                                                                /var/lib/nerdctl/1935db59/volumes/default/test/_data
tke-installer-bin                                                   /var/lib/nerdctl/1935db59/volumes/default/tke-installer-bin/_data
root@VM-0-28-ubuntu:~# ls /var/lib/nerdctl/1935db59/volumes/default/registry-certs/_data
root@VM-0-28-ubuntu:~#

@AkihiroSuda  https://github.com/containerd/nerdctl/blob/39a46444754c581e020fffa63261f2a859c16bac/run_mount.go#L110 here imageVolumes  seems to be empty. it detect only imageVolumes that are defined in Dockerfile "VOLUME" instruction. I takz care about the fix

thanks!

@AkihiroSuda @fahedouch Thanks for all your quick response and fix:>>

Yes, it should be fixed in #263.
Will be included in v0.10.0.

Thanks for your hardworks.Nerdctl can run successfully:>
# nerdctl run  -d --privileged --net=host --restart=always -v /etc/hosts:/app/hosts -v /run/containerd/containerd.sock:/run/containerd/containerd.sock -v /opt/tke-installer/data:/app/data -v /opt/tke-installer/conf:/app/conf -v registry-certs:/app/certs -v tke-installer-bin:/app/bin docker.io/tkestack/tke-installer-amd64:2107f202f84d0f520983ab741501770a7e1c08d5 tke-installer
1ebeaf9c038ae07ea762b6717848236136f719a7b83242f4577995503bc2ba6f
root@VM-8-15-ubuntu:~#
root@VM-8-15-ubuntu:~#
root@VM-8-15-ubuntu:~# nerdctl ps
CONTAINER ID    IMAGE                                                                              COMMAND                   CREATED          STATUS    PORTS    NAMES
bc7399322ae1    docker.io/tkestack/tke-installer-amd64:2107f202f84d0f520983ab741501770a7e1c08d5    "/app/bin/tke-instal…"    5 minutes ago    Up

# nerdctl volume ls
VOLUME NAME          DIRECTORY
registry-certs       /var/lib/nerdctl/1935db59/volumes/default/registry-certs/_data
tke-installer-bin    /var/lib/nerdctl/1935db59/volumes/default/tke-installer-bin/_data


No such module ‚TensorFlow‘

With Xode 10 (Beta 3) and toolchains
swift-tensorflow-DEVELOPMENT-2018-06-29-a-osx.pkg and
swift-tensorflow-DEVELOPMENT-2018-07-12-a-osx.pkg
I get an error when trying to import TensorFlow into a Command Line project:
No such module ‚TensorFlow‘

In playground and Swift REPL everything is working fine:
Welcome to Swift version 4.2-dev (LLVM eb00ef6046, Clang d9545f2833, Swift 3d37ae7c06). Type :help for assistance.
  1> import TensorFlow
  2>

When using Xode 9.4.1 and toolchain swift-tensorflow-DEVELOPMENT-2018-06-25-a-osx.pkg an import of TensorFlow into a Command Line project is possible.
Environment:
macOS 10.13.6

Xcode 10 beta doesn't work very well with third-party toolchains. A workaround is the following:

Go to "File" - "Project Settings"
Set "Build System" to "Legacy Build System"
Click "Done".

Great, that works. Thanks!


Please add Mekif Alef

Mekif Alef, Beer Sheva, Israel.
thank you!

@shanag1801 Could you please explain what sisma.org.il is? It looks like a broad platform where a lot of students can get a free email address. Too broad platforms not linked to a specific school can be a source of free license misuse, thus we have to understand better who is eligible to get an inbox there.
The website sisma.org.il says it provides service to 1,000,000 people, which is about 10% of the total Israeli population. Thus, it does not appear to qualify for inclusion in this repository.

@shanag1801 You might miss my previous comment. Please react.

Hi, thank you for reaching out to me. The Sisma website is a platform high
schools in Israel use to provide email addresses for their students. Most
schools in Israel don’t have their own website or personal domain and
instead most schools use Sisma.
I’d be more than happy if you could add it to your list.
Thanks a bunch 🙏🏻
On Thursday, May 2, 2024, Philip Torchinsky @.***>
wrote:

@shanag1801 https://github.com/shanag1801 You might miss my previous
comment. Please react.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/20675#issuecomment-2091423606,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWNXW2EBU45SI6TUG3NK3XLZAKJVBAVCNFSM6AAAAABGLRVCXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRGQZDGNRQGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you so much 😊
On Monday, May 6, 2024, Philip Torchinsky @.***> wrote:

@shanag1801 https://github.com/shanag1801 Thank you for your patience
while waiting for a review and processing your request. Pull request merged.
Please notice that adding umbrella domains like this is not in our general
policy. So, the domain is conditionally added to the trusted list for an
experiment, with close monitoring of its use. Shall we detect any
fraudulent activities, we'll have to remove this domain from the trusted
list immediately.
I appreciate your understanding.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/20675#issuecomment-2095315073,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWNXW2HVCGW7DMJBQBZXJB3ZA4TBLAVCNFSM6AAAAABGLRVCXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVGMYTKMBXGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


socket can't bind to <IP_ADDRESS>

socket can't bind to "<IP_ADDRESS>"

Hi @scriptkitz - thanks for posting. Can you please provide some more context? Also, when filing issues please try to follow our contribution instructions.

Python 2.7.12 (default, Dec  4 2017, 14:50:18)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import socket
s=socket.socket(socket.AF_INET,socket.SOCK_STREAM)
s.bind(("<IP_ADDRESS>",0))
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/socket.py", line 228, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 99] Cannot assign requested address

In real linux,  work fine!

@benhillis

For the sake of getting this closed, by-design.
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
bind(3, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = -1 EADDRNOTAVAIL (Cannot assign requested address)

Rehash of this. I should have spoke up last year.

The OP ask takes on WSL2.


Passing Additional Data to prepareParams

We have a very similar set up to @ianstormtaylor's question in https://github.com/relay-tools/react-router-relay/issues/58. How would you suggest we get the cookie information (or any other non-url related data) into the prepareParams method? As of right now, the second argument (not sure what to call it) in prepareParams seems to only return the following properties:
{
routes,
params,
location,
components,
router,
matchContext
},

Placing the data we need within one of the properties above works, but we feel this may not be the best way to approach this. To begin with, none of those properties seem to have any reference to any data that is not extracted from the url/route. Is there something we're missing?

I think you can possibly just pass it by passing down to route components as props
Here I define the data I want to pass inside the component

And here I pass it to component

And the rendered component will contain the data from route props