Create Xcode project with shared framework schemes for Carthage support

@mw99 Thank you for sharing this great library, much appreciated! ありがとうございます！
I've just added support for installation via Carthage, an alternative to CocoaPods. I think more people will be able to use your library once Carthage support is merged. Basically to support Carthage one just needs a project with shared framework targets, which I added. In case you add more Swift files, you just need to add them to the Xcode project, too, in order to keep support for Carthage. No release steps needed, Carthage automatically uses GitHub tags, so tagging should suffice. If you want a released version supporting Carthage, just tag your master branch with version 3.0.1 after merging this.
Schönen Gruß eines Japan-Interessierten aus Karlsruhe! 🇯🇵 😉

Sorry for the way to late reply. I kinda forgot about this. There is no way to support Carthage without adding a whole Xcode project?
Beste Grüße zurück

That is exactly right. Carthage builds a shared scheme within an Xcode project using the command line tools of Xcode. This requires an Xcode project which also can't be generated as of now with the likes of SwiftPM.

Actually the swift package manager can generate a Xcode project with:
$ swift package generate-xcodeproj

In my opinion Carthage should somehow be able to do this on it's own when it depends on Xcode projects. That way all swift package manager packages would be compatible to Carthage without me doing anything 😄 Maybe I'm not seeing the whole picture here, but wouldn't that the way to go?

Carthage doesn't support such a thing and probably never will (it takes years for them to even answer when it comes to features everybody needs but the maintainers themselves don't, see here for example). It really isn't worth arguing with them or waiting for such a thing.
Also, there are features within Xcode that can't be described within SwiftPM's manifest file, like resource inclusion. Your project doesn't need that, but for this simple reason alone will the Carthage maintainers as I have come to know them never agree to incorporate no-project SwiftPM packages support. I've actually started building a new package manager, that exactly solves these problems of Carthage and will be able to incoporate both Carthage compatible projects as well as SwiftPM compatible projects. But that's "Zukunftsmusik", to put it in a German word. Currently I'm not working on it so it might take until summer until it's ready to use.
So the question here is basically, do you want to support Carthage users or not. Cause if you want, there's currently no other way and although I understand it doesn't feel like a pretty thing to do, I tried to make very clear that the project is only there for Carthage supporting purposes and also put the project into a sub directory so people don't accidentally open it when developing. If you want, you can add a section in the README how contributos can develop in this project, but SwiftPM developers should already know so that shouldn't be a problem.

Oh man I read that thread. Classic github drama. Seeing that does not but a lot of confidence in the future of Carthage. I used Carthage same years ago. I don't remember exactly why, but it felt to rigid and had too much limitations. Configuration options lacking everywhere. So I ditched it.

So the question here is basically, do you want to support Carthage users or not.

That thread and my own Carthage experiences are both rather negative. Besides that, I do want to keep this as simple as possible here. This is a very simple library but for a release I already have to test different versions for:

Swift
SPM
Xcode
Cocoa Pods
And I'm glad I can do this without Xcode project files which have versioning on their own. Also I don't want user to get the impression that Xcode project files are needed. Because they are not. Therefore, sorry, no Carthage support.

If you want, you can add a section in the README how contributos can develop in this project

Will think about that.

I've actually started building a new package manager, that exactly solves these problems of Carthage

Ambitious project. Good luck

Oh, I was not expecting that you actually consider neglecting Carthage support. Just to give you some additional motivation:

You don't need to do anything in the Xcode project. No versioning, nothing. Only if new Swift files were added, you would need to link them in the Xcode project, too. But if you forget it, then only Carthage support would be broken and I would probably just add it via a new PR. So no worries.

To be clear, I don't dislike Carthage and I think Carthage is still the best package manager for many iOS projects. I just don't think you should wait for them to finish any feature you might think they should implement. They won't. But neglecting it entirely (especially given that I did all the hard work) would simply mean that you're not taking the Swift community seriously and might piss off many developers who might otherwise have used this great library.

By not merging this, you're only keeping the repo "as simple as possible" for yourself, but not for the many Carthage users. And as I stated in (1) you don't need to worry about "complexity" for yourself as there's really nothing you need to do to conform to Cartahge, even if you make new releases. It will magically work (that's actually one of the advantages of Carthage compared to CocoaPods).

Regarding the future of Carthage, I don't think it's going to be around once SwiftPM is integrated with Xcode, but that'll take until late 2020, which is still many many months to go where people could use your library.
I hope I could convince you to merge this. You can think of it this way: If you have Carthage support, your library is more likely to gain stars than if it doesn't.

So played a bit with swift package generate-xcodeproj and Carthage and had quite successful results. A generated project basically worked out of the box which surprised me. I just released version 3.3.0 which should have working Carthage support. However only for Swift 5 (needs current Xcode 10.2 beta). I don't plan to back port this, so you may can't use it right away.
Why I'm not merging your pull request and added my own files:
I like the idea of just regenerating. I just run swift package generate-xcodeproj --output CarthageSupport and everything should work again should future versions of Swuft/Xcode break Carthage support. But thanks man.
Drop me a line if you ever come to Tokyo.

Oh, it seems they finally did make some useful progress over there and now support building SwiftPM based projects. Must be a younger addition to Carthage, cause I didn't know about that. Only supporting Swift 5 is fine with me as my intention was future-oriented anyways, shouldn't take long until Swift 5 stable release is fainally here. :)
Thanks for testing this and making it work!
I also just dropped you an email regarding when I'll be in Tokyo.

Oh, I had misunderstood what you the whole time, but I just had a look at the commit and now I understand. 🤣
Of course this works, I thought you were looking for a solution where Carthage would run swift package generate-xcodeproj for you so you don't have to add an Xcode project to the repo. Also I thought Carthage has added that feature in the meantime, but of course they haven't. 😓
You're right that this is a cleaner solution than what I did. I hope it works for all targets (iOS, tvOS, macOS & watchOS) and that it doesn't make any problems when doing an archive and trying to release that. But we'll find out eventually. :)


Option to export VC even if not used in node tree

History of this PR:

In the common usage / historically / simplicity of usage, Vertex Colors are used not only for Vertex Color, but also for transmission of other custom data.
The glTF Specification propose a way to transmit custom attributes, but seem for a number of reasons, this workflow is not commonly used:
Not very well know
Not perfect from Blender side yet (need to use name starting with underscore to avoid exporting internally used custom attributes)
Lack of implementation / easy way to retrieve data for some engine/viewer
This make the end to end workflow of custom attributes not very used (from what I know)

All of these make that VC are commonly used for custom attributes transmission too, even if this goes against the glTF Specification, which says that VC must act as a multiplier of Base Color.

Setting some custom attributes in VC COLOR_0 will generate some valid glTF files, but a fully compliant glTF 2.0 viewer must use these data as a base color multiplier, probably resulting in weird shading.

Even if we truly think we need to put energy setting a global solution around custom attributes (When we say globally, it means from Blender, Unity, Godot, UE, threejs, Babylonjs, etc...), we also know that you have some pipeline and workflow already in production right now, and that the ideal solution will take some time to be implemented in all these softwares.
So here is our proposition:
This PR add a new panel with more options to choose at export:

This PR adds an option to export active VC as COLOR_0, even if not use in node tree as a multiplier of base color.
The generated glTF can look wrong in viewer that are fully compliant with glTF, as the VC will be a multiplier of base color, where it is not in Blender viewport.
The default value is still "MATERIAL", as this is the option fully compliant with glTF Specification

When choosing ACTIVE, a warning will explaining that your workflow can be more robust with another solution:

You can also choose to never export VC:

You can now choose to export additional VC as COLOR_1, COLOR_2, etc...

This also add an option to choose what to do when there is no material. You can now choose to export active VC as COLOR_0, or not export any VC.

Im not a dev but this looks like the optimal solution for everyone. I would say the "export all vertex colors" should include the alpha channel of the VC as well. thank you! Im sure game engines will eventually switch to using custom attributes instead for vertex colors, but who knows how long that will be. (unreal might already but still supports VC)

I did make this suggestion way back when this whole thing started. glad to see someone with more skill and common sense step up.

I think you've covered all the bases and the extra explanation for the feature is important and helpful, thanks!

Which set of options would most closely mirror export_colors from previous versions?
We're having a bug with the Godot engine where Vertex colours weren't being exported when not attached to a material: https://github.com/godotengine/godot/issues/97953
I seem to have fixed it by changing export_vertex_color from MATERIAL to ACTIVE (for Blender 4.2+ obviously), but I'd like some confirmation that this is the right approach.


Consider using spring.application.name

spring.application.name is a property that is very often used to specify the identify of a particular app (service), especially in cloud-native architectures.
Right now we have ApplicationTags with application name and service.
@adriancole mentions that in his original PR. I was tempted to actually implement that logic directly in the auto-configuration of ApplicationTags.
However, I am confused whether we should use application name or service. Looking at the Wavefront dashboard, it seems like the name aggregates an number of "services". From the perspective, I think spring.application.name should be used as the default of wavefront.application.service.

ps there's both application and also service to decide on
Here's some (overwhelming) background to this point https://github.com/spring-cloud/spring-cloud-sleuth/issues/324
It isn't worth waiting for people to ask later in other words, rather choose which of application/service (maybe both) to default.
side note: in hindsight sleuth's property "spring.zipkin.service.name" isn't conventional (as it should be sleuth namespace in hindsight as we don't support custom servers anymore). But anyway, this could be a secondary default so that users running zipkin and migrating to WF, or simply those using WF, but zipkin on laptops etc, can smoothly worth between things.

I've asked for feedback on what those mean and here is a summary of it

Application name=The business application, e.g. "webstore" or "accounting".
Service=Component within that application.

From the perspective, I think wavefront.application.service should use spring.application.name if not set explicitly. I have no opinion on wavefront.application.name.

also don't have an opinion one way or another, both needs to be set to something (that's reasonable from a spring boot perspective)


Can we have a mouseleave similar to hover in the useDrop to customize?

Is your feature request related to a problem? Please describe.
I'm working on a treeMap component which needs to support drag and sort.
I want to draw a dropping line while mouse is over a target.
If mouse is over target top half, the line will be above the target, otherwise, it will below the target.
I'm using hover function from useDrop to detect the position of the mouse, but the problem is that when mouse leaves the target, there is no way I can cleanup the drawn line on the last target.
Currently, I save the lastRef of the target to compare with the currently hovered ref, but the UX is not quite good. I see flickering while drag around
Describe the solution you'd like
I hope there is mouseleave handler that I can customize to cleanup whatever did in the hover.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
None
Additional context
Add any other context or screenshots about the feature request here.
None

You could use the HTML onDragLeave={onDragLeave} on the  OR
create your own hook that would call a callback function when the drag leaves your target.
Something like:
const useLeave = (callback, isOver, canDrop) => {   const [prevIsOver, setPrevIsOver] = useState(isOver);   useEffect(() => {     const isActive = canDrop && isOver;     setPrevIsOver(isOver);     if (prevIsOver && !isActive) {       callback();     }   }, [isOver, canDrop]); };
and in your draggable component, add
useLeave(onDragLeave, isOver, canDrop);


providing an example to create the hbduserstore key

[Enter feedback here]
Hello Team,
we would appreciate if you can put an example command of the hdbuserstore on how to add the key that is scanned by the pre-requisite script as this sometimes could be executed by a non-sap expert users
Thank you

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d5d16f95-6c6c-aad4-7c98-b434327fee2c
Version Independent ID: 2de588d0-81a3-ca99-67ab-267e0cdd42ff
Content: Tutorial - Back up SAP HANA databases in Azure VMs - Azure Backup
Content Source: articles/backup/tutorial-backup-sap-hana-db.md
Service: backup
GitHub Login: @v-amallick
Microsoft Alias: v-amallick

@ibabedal Thank you for your feedback. We will review this request wit the feature owner nd update the doc as appropriate.
@v-amallick FYI

Hi @ibabedal - sorry for the delay in response. You can find the example pre-registration scripe in the table of this section. Request you to please check.
Also, please share your suggestion for us to imporve the article.

Hi @ibabedal - As we did not receive any response, closing this issue - #please-close . Feel free to share your recommendations, we will take it up. Thanks!
We


RFC: Deprecate Cloud Run support

Describe the problem
We have basic Cloud Run support, though it may no longer be required in the near future.
:+1: if you agree with deprecation
:-1: if you wish to see Cloud Run support remain
Please comment if this would be disruptive to your workflow and WHY you use Cloud Run over Functions with this Firebase Adapter

I personally think this would be great going forward.

I personally think this would be great going forward.

You think deprecating Cloud Run or keeping Cloud Run would be great?

I personally think this would be great going forward.

You think deprecating Cloud Run or keeping Cloud Run would be great?

I think deprecating Cloud Run would be a good idea.

I can see how going with "functions" would be much simpler, but I much prefer to use cloud run

@CaptainCodeman I prefer Cloud Run too. I updated the PR with a link, I suggest you take a look.

Sorry, I'm not sure I understand what link you mean and what I am meant to be looking at.
Do you mean the link at the top of this issue? That just links to a list of firebase issues:
https://github.com/firebase/firebase-tools/pulls?q=is%3Apr+sort%3Aupdated-desc+cloud+run+is%3Aclosed

Yes, I meant that link. The existence of issues matching that filter will indicate why this RFC exists.

https://github.com/jthegedus/svelte-adapter-firebase#function-vs-run
The only problem I see its that we would lose the Cold start mitigations, does the "stay tuned" in functions means there will be an equivalent for functions?
My current path its develop locally with functions to use the functions debugger, and when Im ready to deploy I was going to use cloud run to prevent cold start.
There is another way with functions? If so I would be happy to ditch cloud run.

does the "stay tuned" in functions means there will be an equivalent for functions?

As I understand, yes.

Cloud Run has another significant benefit over cloud functions.
The default concurrency is 80 requests per instance and it can be configured as high as 1,000
Cloud functions on the other hand has a limit of ... drum roll ... 1. Yes one concurrent request per instance.
I think if you're doing anything non-trivial there should be benefits to using Cloud Run.

Cloud Functions now has min_instances support.
Official release blog post - https://cloud.google.com/blog/products/serverless/cloud-functions-supports-min-instances
Firebase supports this in https://github.com/firebase/firebase-functions/releases/tag/v3.15.5
You can use it like so:
const myOpts = {
	memory: "1GB",
+	min_instances: 1,
}
exports.myFunc = functions.runWith(myOpts).https.onRequest(async (request, response) => {
	...
});

Also Node.js 16 is available as of https://github.com/firebase/firebase-tools/releases/tag/v9.17.0


Says "PINPUT_RECORD" instead of "INPUT_RECORD"

Says "PINPUT_RECORD" instead of "INPUT_RECORD"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cdf2ea95-c942-16a0-9501-ba56be8c5c44
Version Independent ID: 169d5761-f559-4b3f-ee7a-06befb96e1f2
Content: ReadConsoleInput function - Windows Console
Content Source: docs/readconsoleinput.md
Product: console
GitHub Login: @miniksa
Microsoft Alias: miniksa

Yes. In the Win32 API, all pointer types are prefixed with P. PINPUT_BUFFER is the same as INPUT_BUFFER*.

ohh, okay. Felt a little too obvious to be a mistake


Expression tests and related issues

As promised in #299, I filled in some of the expression tests, raising three kinds of issues:
Test helper

The top-level method actExp(..) is to replace XCTest assertion directly.
It identifies the first text delta and prints expected and actual cleanly for copy/paste.  But it is relatively ungainly and not isolated, and there are likely diffing libraries that would do a better job.  It can merge and work as-is, but I can clean it up per your preferences.  I used it only in the new tests.

Three kinds of test issues

3 tests fail due to JSON encoding differences, presumed due to locale differences

I flagged these as expected fails. In the expected locale, these should be reported as unexpected pass.
I can investigate whether JSONEncoder configuration will avoid locale-dependent behavior.

testAsyncExpression3(): fails when there is no network

It's unclear if we should check and skip, or use a different async call that does not require a network.

The test testIdentifierExprSyntax() now refers to a quoted keyword (`class`).  Let me know if something else was intended.

The variable `class` is rendered as [-n-]{+cl+}a[-me-]{+ss+}.  Is that correct?

Two implementation issues

optional string has quotes around the entire optional: "Optional(\"0\")"
inout variables are rendered constant (unusable) by macro expansion, resulting in compile errors.

Merging
Commits with aspects to investigate are marked DRAFT.  Commits are designed to merge even if the issues above require changes (e.g., tests should continue to pass; the current behavior is accepted for now).  Commits are also separated to isolate the issues above, to allow skipping a particular issue/commit.  The goal was to enable the changes to be merged, with follow-on work scheduled in later tasks.

Sorry, I can't see the logs for the failing Bitrise or Test checks.  I tested on macOS 14 with 5.9.  (It fails as expected on Linux due to missing Foundation API's and objc support.)

Thank you for the PR! I'll check back later.

Sorry, please ignore the first commit to add .project to the .gitignore (cb6d4e...).  (I've added that to my global configuration.)

Please let me know if you'd like me to rebase or merge the branch.

No worries. I just can't take my time.

Thank you very much. It looks good to me. All tests are passing in my local environment, so if there is a problem when I run it on CI, I will fix it on my end.

Thank you for your patience.
I rebased off main, removed the unnecessary commit, and removed the expected failures per request.
fyi, four tests in AssertTests are failing for me:

testMagicLiteralExpression2
testInitializerExpression
testSelectorExpression1
testSelectorExpression2

(XCode 15.0, swift 5.9.0, M1 Studio)
If I discover a solution for inconsistent tests, I'll make a separate PR.
Thanks!


Mutliple Header Rows.

Its not currently possible to put two rows in a
<Thead />

Well I have also a need to put a customized row above the filter header row.
Also they has to have colspan attributes. I will try to customize it the next days. But would be cool, if there is a small tip for this issue :-D


package:ffi 1.2.0 and dart 2.16 both define IntPtr

import 'dart:ffi' show Pointer;
import 'package:ffi/ffi.dart';

import 'file2.dart';

Pointer<IntPtr> intPtrPointerFromPackageFfi = intPtrPointerFromDartFFI;

// file2.dart
import 'dart:ffi';

Pointer<IntPtr> intPtrPointerFromDartFFI = nullptr;

A value of type 'Pointer<IntPtr> (where IntPtr is defined in /Users/dacoharkes/flt/engine/flutter/bin/cache/dart-sdk/lib/ffi/c_type.dart)' can't be assigned to a variable of type 'Pointer<IntPtr> (where IntPtr is defined in /Users/dacoharkes/ffi/lib/src/c_type.dart)'.
Try changing the type of the variable, or casting the right-hand type to 'Pointer<IntPtr> (where IntPtr is defined in /Users/dacoharkes/ffi/lib/src/c_type.dart)'.dart[invalid_assignment](https://dart.dev/diagnostics/invalid_assignment)
[ffi.dart(41, 7): ]()Pointer is defined in /Users/dacoharkes/flt/engine/flutter/bin/cache/dart-sdk/lib/ffi/ffi.dart
[c_type.dart(402, 7): ]()IntPtr is defined in /Users/dacoharkes/flt/engine/flutter/bin/cache/dart-sdk/lib/ffi/c_type.dart
[ffi.dart(41, 7): ]()Pointer is defined in /Users/dacoharkes/flt/engine/flutter/bin/cache/dart-sdk/lib/ffi/ffi.dart
[c_type.dart(421, 7): ]()IntPtr is defined in /Users/dacoharkes/ffi/lib/src/c_type.dart

We didn't notice this on 1.2.0-dev.0.
We could release 1.2.1 which removes IntPtr (or rather re-exports it from dart:ffi), and would be compatible with Dart 2.16.
export 'dart:ffi' show IntPtr;

And sets an upper SDK constraint so that it never uses Dart 2.17.
However, that creates a mess when people want to start using Dart 2.17.
Maybe we should just not release the C types on package:ffi at all, and wait until they come available in Dart 2.17 themselves.

To avoid moving types (and all the issues that come with it), we'll not be releasing 1.2.0-dev.0 as a stable release and remove the C types from there again.
The C types are available on Dart 2.17 dev / main branch and will be available from Dart 2.17 stable.


Adding Symfony4 support

I changed two file for Symfony4 support on #SymfonyConHackday2017

Awesome!

Voting for merge! Thank you!

Friendly ping to @cleentfaar

Is this library still active? Can we merge this PR? Symfony 4 support could be great!

Wohoo!

Merged for what it's worth. Sorry guys obviously this repo is no longer maintained 😢, I will archive it to reflect this.


[FLINK-17076][docs] Revamp Kafka Connector Documentation

What is the purpose of the change
We update the Kafka connector documentation to be universal connector first and remove references to deprecated options and methods. This PR is based on #12253 so I could reference the new WatermarkStrategies. This page now uses a lot of codetabs so that users are only ever reading the docs for a single version so it is probably best to review this by building the docs locally vs using the diff.
cc @aljoscha @alpinegizmo

Thank you for the feedback @alpinegizmo . I will address your comments and merge.


Can't cancel VS Code Server update

Issue Type: Bug

Inside WSL, run code-insiders .
It displays Updating VS Code Server to version 6964233e....
This is taking a while, because I'm using tethering.
Press Ctrl+C while it's downloading.

The percentage moves slightly to the right, but the download is not cancelled.
VS Code version: Code - Insiders 1.35.0-insider (6964233e81c68f5a5f34e7eb1da0836e1d539f14, 2019-05-29T05:18:15.943Z)
OS version: Windows_NT x64 10.0.17763

Note that at the time this happened, ps -ef showed two wget processes running, one of which was owned by PID 1 (i.e. somehow got abandoned). Not sure if this is the cause, a symptom, or an entirely different bug.
It should also be noted that the reason that it was updating in the first place is because I had yesterday's Insiders installed previously.


[Meru AB] Naming suggestions

Description
Fixes https://github.com/dust-tt/dust/issues/3884
Notes

only uses instructions and description for now
Suggestions are computed even for existing assistants
Will appear only if the LLM thinks we are done typing in instructions /descriptions
LLM app to be iterated on

Example given instructions "Act as king of cats."

Risk

Deploy Plan

@philipperolet do check for unicity (not suggest already used handles)?


[Enhancement] Consider changing to Bluebird

Just a thought, but would you consider replacing q with bluebird?  I keep hearing that it has an order of magnitude better performance, though I have no empirical proof of this myself.

At this point, the only change probably worth considering is switching over to using the native Promise type (or a native Promise polyfill). However, my understanding is that the Promise specification doesn't provide support for "progress" events which introduces backwards compatibility problems unless the returned Promise object is monkey-patched to support a progress method or some other more appropriate method (which might be okay).
As for performance, unless you are spawning a lot processes, I don't think the performance of promises is going to matter too much. I think "order of magnitude better performance" is a huge stretch since I doubt we are looking at a 10x difference in performance. If Q was significantly slower in the past, I'm sure  that gap has narrowed.

OK thanks, just thought I'd bring it up.


Missing a defined.setTimeout check.

Missing a defined.setTimeout check at line line #914. This causes an error when running in Rhino/Node.

Updated the cli branch - cd test; node suite.js shows a lot more failures...


Add button for ACPI shutdown

Background
There's three ways to turn off a physical computer:

Login, ask the operating system to shutdown (may require admin permission)
Yank the power cord.
Press a physical button on the computer to indicate you want to shutdown.

Abstract
UTM supports the first two. I hope we can support 3., which is called ACPI shutdown.
Proposal
In the GUI this can be done by changing what happens when you click the shut down button.
Currently it asks if you are sure you want to yank the power cord "CONFIRMATION: this may corrupt the VM and any unsaved changes will be lost. To quit safely, shut down from the guest."
But this could be changed instead to show a dialog box with options:

Soft shutdown (ACPI, requires OS support)
Hard shutdown (immediate stop, may corrupt VM)
Cancel

Note you may also be able to shut down inside the guest operating system.

alternative dialog:
ACPI shutdown
2.

alternative dialog:
How would you like to shutdown the VM?

ACPI shutdown
Hard shutdown
Cancel

(hard shutdown button is red to indicate a slightly dangerous action, both shutdown action would prompt for confirmation and hard shutdown may include info that vm might corrupt, may also apply to restarts if that exists)

It is my opinion that such a feature will lead to "complexity creep". Most (90%) of people won't know what "ACPI shutdown" means or how it's different from other kinds of shutdown. Most people also won't need such an option. Maximum flexibility will come at a cost of a more difficult to understand UX. In most cases, you can trigger an ACPI shutdown directly from the guest.

In order to shutdown from the guest you need to login. And then you need the root password.
It's a lot of steps. So maybe other people also like the ACPI option.

Agree we need a “safe shutdown” button. See https://github.com/utmapp/UTM/issues/3859#issuecomment-1114787051, closes 3859

...Most (90%) of people won't know what "ACPI shutdown" means or how it's different from other kinds of shutdown...

To be honest UTM is already pretty "complex" as such pieces of specialized software are. I tend to believe most users with the need to emulate/virtualize are more tech-savvy to begin with.

Agree we need a “safe shutdown” button. See #3859 (comment), closes 3859

+1

Agree we need a “safe shutdown” button. See #3859 (comment), closes 3859
+1

+1

Just curious:

Will this require spice guest tools or any acpi-compliant os?
When approximately will 4.1 be released with this feature (beta and stable)?

Thanks in advance for adding this feature!

this feature requires ACPI functioning systems because it uses ACPI stuff

The way QEMU implemented it is more generic. Any hw can hook on to that call. In practice I think it’s probably most useful in ACPI systems.

+1

+1

@osy sometimes I find myself clicking the power button accidentally instead of holding it down. I know this is petty and thank you for configuring the ACPI, but do you think it would be possible in settings to add a toggle to "show advanced shutdown options by default"? Many thanks in advance, and I love your software!

I had no idea that holding down the power button showed more options until reading this.
It would be nice if the defaults were the safest for the user:  closing the window could save a snapshot that is restored next time, and hitting the power button would attempt an ACPI shutdown, after some timeout a dialogue could ask if you want to force shutdown.

I didn't either, maybe either what anonymousaga suggests or let people set the default action.

For me setting default close action, as one can with VirtualBox, is the only way to gracefully handle host shutdowns and reboots.
A bare minimum is a pop up on any close request asking what type of shutdown is required, Request Shutdown, Force, or Cancel.

I'd love to have a setting that would either send ACPI shutdown for all running guests on host user log out or shutdown/reboot. The second option could be to save a snapshot. This would block UTM quitting until all guests gracefully exit.

I believe you'll find the newest build does now save state of guest VMs that are capable of being suspended when the host application is requested to quit.

Automatically save state when you close a VM This will only work on VMs that support save states. If your VM does not support it, you will get an error message with an explanation.

https://docs.getutm.app/updates/v4.4/

Great stuff, I'll wait until the GL_ARB_clear_texture bug is resolved before trying this, but it looks good.


Removing last field from options does not reset the lastField property

Removing last field in a record, then reading all records generates an exception
engine.Options.RemoveField("Digitale")
Dim records = engine.ReadFile(fn)

FileHelpers.FileHelpersException: Line: 1 Column: 207. Delimiter ';' not found after field 'CDC'
(the record has less fields, the delimiter is wrong or the next field must be marked as optional).

When removing any field from the Fields array of RecordInfo should reset the lastField property of the last item in the array:
// in Core/RecordInfo.Factory.cs
public void RemoveField(string fieldname)
    {
        var index = GetFieldIndex(fieldname);
        Fields[index] = null;
        Fields = Array.FindAll(Fields, x => x != null);
        Fields[Fields.Length - 1].IsLast = true; // HERE <====
    }

@pradu71 Thanks for the feedback !!
I just reimplementd IsLast IsFirst and change the RemoveField
https://github.com/MarcosMeli/FileHelpers/commit/bc19bb04731ae157d20a22d6fcdeeaa63f9ae2c2
I will try to make a build so you can test it, what .net version are you using ?

.net 4.0

Thanks, I will commit some other changes in some minutes to make tests pass

You can download the build from here:
http://teamcity.codebetter.com/viewLog.html?buildId=198119&buildTypeId=FileHelpersMaster&tab=artifacts
Let me know if it works now

works with this build.

I will release a new version at least as RC via NuGet


[ELE-125] Allowing test configuration on different level

Hi, here is a request to improve running test on a models with varying size. This was originally posted in the support channel on Slack here which is also the reason why the copy-pasted description below looks more like a question than a request.

I have a question regarding test configuration. Its stated here that there are three levels of configuration available for anomaly tests but I miss information about which type of configuration is available and where exactly it should go.
For example; We have a model with a large output and for this we want to configure days_back: 14 rather than the global days_back: 90 which we have defined as default in the dbt_project.yml vars.
I have not been successful in this and would like to get some help. Below is a example .sql to help clarify:
models:
  - name: MODEL_WITH_LARGE_OUTPUT
    description: ~
    config:
      days_back: 14 # <--- This doesn't seem to be picked up by elementary
      meta:
        owner: ~
        days_back: 14 # <--- This doesn't seem to be picked up by elementary
      tags: []
      elementary:
        timestamp_column: ts
        days_back: 14 # <--- This doesn't seem to be picked up by elementary
    tests:
      - elementary.table_anomalies:
          days_back: 14 # <--- The macros doesn't support this argument so this is a no go.
          tags: ["elementary"]

So, how should I go about having model specific configuration that should override the global value?
Thanks in advance!
ELE-125

@oravi Thank you re-opening the ticket again. We want days_back config in each model level as per our requirements. Each model requires different days to configure.

Hi @henriklaurentz ,
I understood that you are willing to contribute this feature, that's awesome!
You are right that we currently do not support configuring this setting in the model or test level. I can outline my recommendation on how to approach it and the relevant areas that need to be changed:

The days_back setting is currently being used in the get_min_bucket_start and get_min_bucket_end macros in get_buckets_configuration.sql.
In order to support passing days_back in the model / test level, it requires a bit of parameter propagating. Here are the places that should be changed:

Define a macro called get_days_back which is similar to the get_timestamp_column macro and how it is used today. It should return either:

days_back if it is passed directly as a parameter (test level)
get it from the elementary config if it is defined (model level)
otherwise, return elementary.get_config_var('days_back')

Call it and get this value in all the anomaly test files, similarly to how get_timestamp_column is called (and also support optionally passing days_back as a parameter to each test):

test_table_anomalies.sql
test_dimension_anomalies.sql
test_column_anomalies.sql
test_all_column_anomalies.sql

Change both the macros get_min_bucket_start and get_min_bucket_end to accept a days_back parameter rather than to read it from a var.
Add and pass a days_back parameter to all the following macros:

complete_buckets_cte (calls get_min_bucket_start)
get_test_min_bucket_start (calls get_min_bucket_start)
table_monitoring_query (calls complete_buckets_cte)
column_monitoring_query (calls complete_buckets_cte)
dimension_monitoring_query (calls complete_buckets_cte)
get_anomaly_scores_query (calls get_min_bucket_end)

I think that should cover it.
We should probably think about a more generic way to pass test configuration at different levels for future parameters.. but as a starting point to enable the requested feature the steps above should work.
Please let me know if it makes sense!
Will also be happy to hop on a call to discuss further if needed.


Linux animated_placeholder_perf failing consistently

Logs:
https://ci.chromium.org/p/flutter/builders/prod/Linux animated_placeholder_perf
Unhandled exception:
Executable Dart file not found: bin/tasks/animated_placeholder_perf.dart
#0      runTask (package:flutter_devicelab/framework/runner.dart:34:5)
#1      _runTasks (file:///opt/s/w/ir/k/recipe_cleanup/tmp11no5H/flutter%20sdk/dev/devicelab/bin/run.dart:115:37)
#2      main (file:///opt/s/w/ir/k/recipe_cleanup/tmp11no5H/flutter%20sdk/dev/devicelab/bin/run.dart:108:11)
#3      _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:281:32)
#4      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)

Seems like the test was deleted but the infra configuration was not. @jonahwilliams @jmagman should we delete the infra config too?

Linux multi_widget_construction_perf__timeline_summary seems that was also removed. Logs:
https://ci.chromium.org/p/flutter/builders/prod/Linux multi_widget_construction_perf__timeline_summary
Unhandled exception:
Executable Dart file not found: bin/tasks/multi_widget_construction_perf__timeline_summary.dart
#0      runTask (package:flutter_devicelab/framework/runner.dart:34:5)
#1      _runTasks (file:///opt/s/w/ir/k/recipe_cleanup/tmprhOGMX/flutter%20sdk/dev/devicelab/bin/run.dart:115:37)
#2      main (file:///opt/s/w/ir/k/recipe_cleanup/tmprhOGMX/flutter%20sdk/dev/devicelab/bin/run.dart:108:11)
#3      _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:281:32)
#4      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)

animated_placeholder_perf was removed in #74062 and multi_widget_construction_perf__timeline_summary was removed in #73986.  The infra config should be removed.


HTML syntax in PHP

Can you please add HTML syntax in PHP file? It would be great.

This does exist. Include a screenshot or code sample if it isn't working.

/duplicate of https://github.com/Microsoft/vscode/issues/670


Point to vale binary outside, but relative to workspace

The binary path doesn't allow paths outside of the workspace. We typically have venv a level up as we use multi folder workspaces. I want to point there for vale, but currently that is blocked.

The bug is caused in this:
https://github.com/ChrisChinchilla/vale-vscode/blob/b1819ae01c1af0feb6ffaf2e309366c7785fef34/src/features/vsUtils.ts#L10-L24
This line:
https://github.com/ChrisChinchilla/vale-vscode/blob/b1819ae01c1af0feb6ffaf2e309366c7785fef34/src/features/vsUtils.ts#L15
should be run on the result of this line:
https://github.com/ChrisChinchilla/vale-vscode/blob/b1819ae01c1af0feb6ffaf2e309366c7785fef34/src/features/vsUtils.ts#L18

Released in v0.19.0


$SHELL handling needs to be more robust

I use very simplistic .ends_with() to detect shells.
This could be considerably improved - breaking up into words and looking for matches.

Resolved by #91


Update contributor and license agreements

cc @tomkralidis
Overview
As part of OSGeo incubation, our Graduation Checklist (https://github.com/ZOO-Project/ZOO-Project/wiki/ProjectGraduationChecklist) requires the project to firm up contribution agreements.
This applies to the ZOO-Project software code files.
This is outlined in https://zoo-project.github.io/docs/contribute/howto.html#licensing.
Template
Hi all, I'd like to contribute <feature X|bugfix Y|docs|code|something else> to ZOO-Project. I confirm that my contributions to ZOO-Project will be compatible with the ZOO-Project license guidelines at the time of contribution.
Committers and contributors can either agree either via the ZOO-Project mailing list, or here in this ticket.
All committers and contributors are listed at https://github.com/ZOO-Project/ZOO-Project/graphs/contributors
Checklist
Committers

[x] @lucadelu (see https://lists.osgeo.org/pipermail/zoo-discuss/2013-July/000972.html)
[x] @kalxas (see https://lists.osgeo.org/pipermail/zoo-discuss/2013-July/000970.html)
[x] @neteler
[x] @rldhont (see https://lists.osgeo.org/pipermail/zoo-discuss/2013-July/000979.html)
[x] @gfenoy
[x] @jmckenna (see https://lists.osgeo.org/pipermail/zoo-discuss/2013-July/000971.html)
[ ] @samsouk
[x] @remicres (see https://lists.osgeo.org/pipermail/zoo-discuss/2017-April/001606.html)
[x] @nbozon
[x] @venka-foss4g
[x] @omshinde
[x] @knutlandmark

Contributors

[x] @dsag (see https://lists.osgeo.org/pipermail/zoo-discuss/2022-November/001799.html)
[x] @marneg (see https://lists.osgeo.org/pipermail/zoo-discuss/2013-July/000991.html)
[ ] @bbrauzzi
[x] @tclarke (see https://lists.osgeo.org/pipermail/zoo-discuss/2022-November/001798.html)
[x] @mmomtchev

Hi all, I'd like to contribute code to ZOO-Project. I confirm that my contributions to ZOO-Project will be compatible with the ZOO-Project license guidelines at the time of contribution.

Hi all, I hereby confirm that my contributions to the ZOO-Project have been and will be compatible with the ZOO-Project license guidelines at the time of contribution.

I hereby confirm that my contributions to the ZOO-Project have been and will be compatible with the ZOO-Project license guidelines at the time of contribution.

Hi all, I'd like to contribute to ZOO-Project. I confirm that my contributions to ZOO-Project will be compatible with the ZOO-Project license guidelines at the time of contribution.

Hi, I also confirm that my contributions to ZOO-Project have been and will be compatible with the ZOO-Project license guidelines at the time of contribution.

Hi all, I'd like to contribute to ZOO-Project. I confirm that my contributions to ZOO-Project will be compatible with the ZOO-Project license guidelines at the time of contribution.

Hi all,
I'd like to contribute to ZOO-Project. I confirm that my contributions to ZOO-Project will be compatible with the ZOO-Project license guidelines at the time of contribution.
Kind regards,
Knut

Hi all, I'd like to contribute code to ZOO-Project. I confirm that my contributions to ZOO-Project will be compatible with the ZOO-Project license guidelines at the time of contribution.

Hi all,
I'd like to contribute to ZOO-Project. I confirm that my contributions to ZOO-Project will be compatible with the ZOO-Project license guidelines at the time of contribution.
Kind regards,
Blasco


String.Contains extension method allowing StringComparison

Follows https://docs.microsoft.com/en-us/dotnet/api/system.string.contains?view=netcore-2.1#System_String_Contains_System_String_System_StringComparison_ but works on netstandard2.0
Regarding String.Replace usage in https://github.com/NuKeeperDotNet/NuKeeper/pull/482/files#diff-8a791fc9d6f84fcd97659a3d22de5bb3 : turns out this was only added when the additional code analyzers were introduced, we don't have a bug/use case so far hitting this (and it's quite unlikely).
This method skips the checks on purpose - they're done in IndexOf anyhow, and this also keeps exceptions consistent with the netcore2.1 version.

Alternative approach to #551


[Q] Did the database change between version 0.9.6 and 1.2.0?

I'm trying to migrate an older database and its tables to a 1.2.0 setup. Reading through the documentation (1.1.10 and back) is taking awhile. So its probably quicker to ask: Is it possible to migrate an older setup's database to the newest version?

Should be possible. Just apply migrations, see https://graphite.readthedocs.io/en/latest/releases/1_1_1.html#upgrading

@deniszh How would that work with a mysql database? Running the migrations with:
PYTHONPATH=/opt/graphite/webapp django-admin.py migrate
--noinput --settings=graphite.settings --fake-initial
Threw an error:
django.db.utils.OperationalError: (1050, "Table 'dashboard_dashboard' already exists")

MySQL should be the same. --fake-initial should fix issue with existing tables, so, not sure why that's happening :(

@deniszh well it hasn't seemed to stop the graphite app from working so I guess I'll see what happens.


ATO-104: Add clean build script

What?
Add scripts to clean - general one and a node_modules specific one
Why?
For clean builds

Probably should add the clean build script as well


Binding problem when attempting to access this

I'm trying to access properties set during the beforeEach() function but I can't access them. Here's a small script for illustration. The first test case doesn't use itParam and works as expected but the second one breaks when using itParam:
// test.js
var assert = require('assert');
var itParam = require('mocha-param');

tests = [{input: 4, expected: -1}];

describe('Array', function() {

  beforeEach(function() {
    this.array = [1, 2, 3];
  })

  describe('#indexOf()', function() {

    it('should return -1 when the value is not present', function() {
      assert.equal(this.array.indexOf(4), -1);  // `this.array` === [1, 2, 3] as expected
    });

    itParam('should return ${value.expected} when the value is ${value.input}', tests, function(test) {
      assert.equal(this.array.indexOf(test.input), test.expected);  // `this.array` is undefined here
    });

  });
});

EDIT:
Here is the output:
./node_modules/mocha/bin/mocha test.js

  Array
    #indexOf()
      ✓ should return -1 when the value is not present
      1) should return -1 when the value is 4

  1 passing (9ms)
  1 failing

  1) Array #indexOf() should return -1 when the value is 4:
     TypeError: Cannot read property 'indexOf' of undefined
    at test.js:21:31
    at Context.<anonymous> (node_modules/mocha-param/lib/index.js:37:20)

You have at least two options here. One is to not use the keyword 'this' to reference the array and to pull the array variable declaration out of the beforeEach scope, for example:
// test.js
var assert = require('assert');
var itParam = require('mocha-param');

tests = [{ input: 4, expected: -1 }];
let array;

describe('Array', function () {

    beforeEach(function () {
        array = [1, 2, 3];
    })

    describe('#indexOf()', function () {

        it('should return -1 when the value is not present', function () {
            assert.equal(array.indexOf(4), -1);  // `this.array` === [1, 2, 3] as expected
        });

        itParam('should return ${value.expected} when the value is ${value.input}', tests, function (test) {
            assert.equal(array.indexOf(test.input), test.expected);  // `this.array` is undefined here
        });

    });
});

The other is to use arrow functions '()=>' instead of  the 'function' keyword as arrow functions have a lexical 'this'. The following will work too:
// test.js
var assert = require('assert');
var itParam = require('mocha-param');

tests = [{ input: 4, expected: -1 }];

describe('Array', () => {

    beforeEach(() => {
        this.array = [1, 2, 3];
    })

    describe('#indexOf()', () => {

        it('should return -1 when the value is not present', () => {
            assert.equal(this.array.indexOf(4), -1);  // `this.array` === [1, 2, 3] as expected
        });

        itParam('should return ${value.expected} when the value is ${value.input}', tests, (test) => {
            assert.equal(this.array.indexOf(test.input), test.expected);  // `this.array` is undefined here
        });

    });
});

I hope this helps.
Mike

Thanks for your response @mikejsdev. I understand the workaround, but it would be nicer if itParam had the same interface and worked similarily as it.
On that note, I noticed that I can't do itParam.only(...), but that might be for a separate issue (we might just need to return the underlying it object).

I'm closing this as it's been open for a while and there is a work around.

The arrow-function workaround didn't work for me, but after a couple of frustrating hours I managed to find the solution (#13)

UP for the PR. As I need to increase the timeout value of the mocha tests. For which I need to use this.timeout(100000)...


Student Yearwise Details Tracker

#python code:
class Student:
    rollnos = []
    names = []

    def __init__(self, no, name):
        self.rollno = no
        self.name = name
        Student.rollnos.append(no)
        Student.names.append(name)

    @classmethod
    def y1details(cls):
        return cls.rollnos, cls.names

    @classmethod
    def y2details(cls):
        return cls.rollnos, cls.names

    @classmethod
    def y3details(cls):
        return cls.rollnos, cls.names

studentcount = int(input("How many students are there: "))
y1info = {'rollnos': [], 'names': []}
y2info = {'rollnos': [], 'names': []}
y3info = {'rollnos': [], 'names': []}
while studentcount != 0:
    year = int(input("\n-Enter a year-: "))
    no = int(input("\nEnter a roll number: "))
    name = input("Enter a name: ")
    if year == 1:
        y1 = Student(no, name)
        y1info['rollnos'].append(no)
        y1info['names'].append(name)
    elif year == 2:
        y2 = Student(no, name)
        y2info['rollnos'].append(no)
        y2info['names'].append(name)
    else:
        y3 = Student(no, name)
        y3info['rollnos'].append(no)
        y3info['names'].append(name)
    studentcount -= 1

x = 'Y'
while x == 'Y' or x == 'y':
    print("\n1. year one, 2. year two, 3. year three\n")
    key = int(input('''which year information
    you like to see?: '''))
    dict = {1: y1info, 2: y2info, 3: y3info}
    print(dict[key])
    print("\nyou want to continue see info?")
    x = input("Yes (Y) / No (N)\n")

Instead of making an issue of this.
Please, make a Pull request for the code to be merged.
Thank you.


Update scalameta, semanticdb-scalac to 4.3.24

Updates

org.scalameta:scalameta
org.scalameta:semanticdb-scalac

from 4.3.22 to 4.3.24.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

labels: library-update, semver-patch

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@800f5be). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #807   +/-   ##
=========================================
  Coverage          ?   82.80%
=========================================
  Files             ?       73
  Lines             ?     5404
  Branches          ?      146
=========================================
  Hits              ?     4475
  Misses            ?      929
  Partials          ?        0

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 800f5be...fdd0b64. Read the comment docs.


docs(readme): update Docker Compose command in installation instructions

Type: docs (documentation update)
Scope: README.md (pertains to the README file)
Message: update Docker Compose command in installation instructions

@artek-koltun should we keep both versions with docker-compose and docker compose in the readme ?

@artek-koltun should we keep both versions with docker-compose and docker compose in the readme ?

We can. Should we add a dedicated script which tries both/checks versions?

see this solution/workaround I used almost everywhere in OPI : https://github.com/opiproject/opi-poc/blob/main/integration/scripts/integration.sh#L14
command -v docker-compose || { shopt -s expand_aliases && alias docker-compose='docker compose'; }


How to get the size of all react-native-fast-image images?

Describe the bug
Does it have a static function?
Maybe user needs to know before clear cache( such as 15MB or 1234KB)
To Reproduce
~~
Expected behavior
~~
Screenshots
~~
Dependency versions

React Native version:0.65.1
React version:
React Native Fast Image version:Lastest

This does not currently exist. IMO not needed since the cache is first in first out, you don't need to manually manage it.
There could possibly be two functions:

getDiskCacheSize
getMemoryCacheSize


Feature/add event source field

Description
Added Source field on  FeatureEvent
Source is set to "PROVIDER_CACHE" for events received through the CollectEvalData endpoint. Otherwise, it is set to "SERVER"
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking changes (change that is not backward-compatible and/or changes current functionality)

Closes issue(s)
Resolve #978
Checklist

[x] I have tested this code
[ ] I have added unit test to cover this code
[x] I have updated the documentation (README.md and /website/docs)
[x] I have followed the contributing guide

hey, @thomaspoignant, please have a look whenever you have some time =)
I failed to see my changes to the docs locally :thinking: , also I'm taking a look at the failed pipeline steps

I haven’t check the PR yet but if you want to have swagger CI to pass you will have to generate the new swagger schema.
To do this please run make swagger and commit the files.

@thomaspoignant good points
I'll make those changes later today. Thanks for reviewing

Thanks for the awesome work on this PR.
I will merge it and it will be available in the next version of GO Feature Flag.

Thanks for the awesome work on this PR. I will merge it and it will be available in the next version of GO Feature Flag.

🎆 thanks for the support
It was nice to learn more about the repo
We use LaunchDarkly at work and, but go-feature-flag would cover all our needs if we were to switch :). I'll let the team know about it and maybe one day we'll migrate if it aligns with the business goals

Oh yes, let me know.
Launchdarkly is way more complete, but sometimes it is too much (and also expensive 😉).
In any case I would be happy to get your feedback about the repo.


Revert gemspec logic to allow install on Ruby 1.9.3

Logic was remove that isolated the net-ssh to 2.9.x for Ruby version 1.9.3
removing this now requires downstream users to explicity install net-ssh 2.9.4

See #505 #510

While I agree with the context of those for projects, however it is pushing the problem downstream rather than addressing directly.  Also if simply doing a gem install for serverspec to do some script testing for you nodes it won't be clear to some end users that you need to pin net-ssh to 2.9.x without digging.


get_all_nodes returning deprecated neonexchange.org URLs

https://api.neoscan.io/api/main_net/v1/get_all_nodes is returning nodes with the URL *.neonexchange.org which no longer have a valid SSL certificate, which causes errors for neon-js users or anyone else using the Neoscan API to select the best node at any given moment.
I believe the neonexchange.org domain is deprecated and those nodes should be changed to point to *.nash.io instead.

As you can see from the following it appears one would need to update the following file to make this change.

Correction, it appears the file https://raw.githubusercontent.com/CityOfZion/neo-mon/master/docs/assets/mainnet.json does not contain the exchange links. The nash servers just need to be added.

Correction, I wasn't synchronized. I'm reviewing to correct the discussion thread now.


Over a minute to create a graph

I've installed the latest version of this gem and run it over an HTML, but using JSON::LD::Reader.new takes over a minute to parse the input. I've set logging to false and skip_registry to true (based on other issues that have been closed here) but they don't make any difference to the time it takes to parse the file. By comparison, scanning the same HTML for Microdata takes a fraction of a second.
Am I missing something obvious?

Can you provide a reference to the file having the issues? I’ve definitely seen html with thousands of JSON-LD script elements take a long time to load.

I'm not sure how your using this, but if you call JSON::LD::Reader.new (or JSON::LD::API.expand) referencing the URL, and if it has the Content-Type: text/html header, the API method will treat it as HTML. When I tried this locally (after a small change to script/parse, it parsed the file in 0.036 seconds, and of course returned no content.
I tried the downloaded file using rdf count kdYEZKJx.html and it does take 0.4 seconds to parse 165 statements of RDFa (with several HTML errors noted). That parses using RDF::RDFa::Reader.new.

Hmm, that's weird. We tried parsing the file here and it took over a minute. We used JSON::LD::Reader.new and added the skip_registry: false option. I'll have to look into this further, it may be a different part of our app that's causing the slow down (we also run the HTML through Nokgiri to find some other things).
From<EMAIL_ADDRESS>Sent: 4 February 2019 23:16
To<EMAIL_ADDRESS>Reply to<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [ruby-rdf/json-ld] Over a minute to create a graph (#46)

On 04 February 2019 at 23:16 Gregg Kellogg<EMAIL_ADDRESS>wrote:
I'm not sure how your using this, but if you call JSON::LD::Reader.new (or JSON::LD::API.expand) referencing the URL, and if it has the Content-Type: text/html header, the API method will treat it as HTML. When I tried this locally (after a small change to script/parse, it parsed the file in 0.036 seconds, and of course returned no content.
I tried the downloaded file using rdf count kdYEZKJx.html and it does take 0.4 seconds to parse 165 statements of RDFa (with several HTML errors noted). That parses using RDF::RDFa::Reader.new.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/ruby-rdf/json-ld/issues/46#issuecomment-460452320

Hmm, that's weird. We tried parsing the file here and it took over a minute. We used JSON::LD::Reader.new and added the skip_registry: false option. I'll have to look into this further.
UPDATE: JSON::LD::Reader.new(html) is still taking an age for me. I've stuck timings through our calls and this appears to be the one line that's killing our performance. As I say, the RDF::Reader.for(:microdata).new(html) runs almost instantly, so I can't understand what's happening here.
EDIT: I'm loading the file using file.open and passing it in as a string.

Right, I've tested a few different things. First, I passed in the HTML as a file, everything went quickly. I then tried passing the HTML in as a StringIO, which started causing JSON::ParserErrors. Finally, I used lib/json/ld/reader.rb:51 exactly to pass into JSON::LD::Reader.new. My tests passed again but were back to being painfully slow.
It seems the second regex on that line is causing some serious slowdown when a string is passed in. When a StringIO is passed in without the regexes then it isn't used and causes a JSON::ParseError, and when a file is loaded in it all runs fine. I'm guessing that the subs are stripping out anything that isn't the LD+JSON lines (it's not the easiest to read), can this be done some other way? The regexes also seem to be catching other CSS and Javascript on the page, causing other JSON::ParserErrors. Would it be more reliable to look for the entire <script type="application/ld+json"> element and strip that down?

There is some inconsistency, probably, when passing text, vs. a file descriptor into JSON::LD::Reader#initialize. There was a fairly minimal (probably too minimal) change to support processing HTML documents. When passing a string, it tries to remove everything before and after JSON content, which is no longer called for in the spec. That could be taking some time, although a profile would be needed. Also, when turning into StringIO, there is no content_type available, so no way to know that it's processing HTML rather than JSON. An option to override content_type would be required here. A recent change to script/parse, used for internal testing, sniffs this based on the .html file extension, and creates an instance method for content_type to return text/html in this case.
The parse error on StringIO comes, as I mentioned because of the presumed content_type of application/ld+json. There would be a similar issue with JSON::LD::Reader.open, unless it's retrieved from HTTP, where content_type is set properly.
Note, though, that you'll probably have more success parsing it as RDFa using RDF::RDFa::Reader.new, as RDFa specifically looks for other content embedded in HTML, including JSON-LD. You'd also get RDFa and Microdata triples in addition to the JSON-LD.
Adding a content_type option to Reader.open and Reader.new is probably a good idea, though, as a way to override what it gets or assumes otherwise. This needs to go in RDF.rb RDF::Reader#initialize, though.

#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;}Ah, I didn't realise I could use RDF::RDFa. My current workaround is to parse the file using Nokgiri and look for script elements with the application/ld+json type. Currently quite fast but if I can search for most schema types in one then I'm just going to do that instead.


Package cleanup

There's a bunch of things here which are a bit messy now so let's clean them up

[x] Remove yarn (we have npm, we don't need it)
[x] Remove husky/lint-staged dev dependencies (we have pipelines for this now)
[x] Move @babel/runtime from dep to dev dep
[x] Properly expose CSS file from package for styles (see #43)

Will try to get these done ASAP so we can move on with addressing the bugs and moving towards having unit tests for all the things

Resolved by #51


How can I force a rerender of the tree?

After the graph is rendered, some changes in the elements don't get the library to rerender it, even when the parent component is rerendered and passed a set of elements with some properties changed.
I have a set of nodes and edges with id's mapping their corresponding id's in the database. The tree gets rendered without problem. After rendered, from a form, I change the target of one of the edges to another node, pass the elements set with the new properties to the component but it still renders the same previous tree. Same happen if I modify styles and then pass the new set to the component.
I've seen in the code that React.memo is extensively used to cache the components, but shouldn't this change in properties force the rerender of the tree?
What property changes in nodes and edges are considered real changes to avoid returning the memoised version of the component?

I've managed to solve it this way, but I think it's quite convoluted:
import React, { useState, useEffect, useRef } from "react";
import ReactFlow, {
  FlowElement as IFlowElement,
  OnLoadFunc as TOnLoadFunc,
  OnLoadParams as TReactFlowInstance,
} from "react-flow-renderer";
import styled from "styled-components";

const WrapperStyled = styled.div`
  width: 100vw;
  height: 80vh;
  overflow: hidden;
`;

interface IProps {
  elements: IFlowElement[];
}
const ReactFlowView: React.FC<IProps> = ({ elements }) => {
  const [receivedElements, setReceivedElements] = useState<
    IFlowElement[] | null
  >(null);
  const instanceRef = useRef<TReactFlowInstance | null>(null);

  const onLoad: TOnLoadFunc = reactFlowInstance => {
    instanceRef.current = reactFlowInstance;
  };

  useEffect(() => {
    setReceivedElements(elements);
  }, [elements, setReceivedElements]);

  useEffect(() => {
    if (instanceRef.current) {
      instanceRef.current.fitView();
    }
  }, [instanceRef, receivedElements]);

  return (
    <WrapperStyled>
      <ReactFlow
        elements={receivedElements ?? []}
        minZoom={0.1}
        defaultZoom={0.5}
        selectNodesOnDrag={false}
        nodesConnectable={false}
        onLoad={onLoad}
      />
    </WrapperStyled>
  );
};

Thanks for the hint. This is a bug. We don't check if the source or target change.

@moklick I get the same issue with Position, I implemented a basic auto-positioning algorithm. But the Canvas will sometimes re-render the elements in the right position, and sometimes not...

The hack I found is to do a clone of my elements before passing them as a prop

Thanks for the library. We are also facing the same issue.

Thanks for the library. We are also facing the same issue.

Look at the snippet ejoysafat posted above. The essential part is this:
const [receivedElements, setReceivedElements] = useState();

  useEffect(() => {
    setReceivedElements(elements);
  }, [elements, setReceivedElements]);

<ReactFlow elements={receivedElements}>

You basically assign your elements to a state and use useEffect to update it.

Hey!
I added an example of how to update node attributes and added a note on the node options site.

The only way to fix this issue I have had is changing the nodes ids each time.


Godot C# Class Inheritance Bug

Godot version:
Godot_v3.2.2-beta2_mono_x11_64
OS/device including version:
OS: 5.6.13-arch1-1
Mono: <IP_ADDRESS>-1
msbuild: 16.5.xamarinxplat.2<IP_ADDRESS>.54-1
Issue description:
If your class has the same name like a Godot node / Godot class, your game probably won't work correctly.
F.e.: public class Spatial : Godot.Spatial
Minimal reproduction project:
https://github.com/JupiterRider/ClassInheritanceBug

That seems obvious no?
Is your IDE not telling you that the name is illegal?

your game probably won't work correctly.

What does this mean? Is there a particular error as a result of this?

Is your IDE not telling you that the name is illegal?

I don't think it would, in C# you're allowed to have classes with the same name if they are in different namespaces.

your game probably won't work correctly.

What does this mean? Is there a particular error as a result of this?

Game starts, but infinite loading screen.

That seems obvious no?
Is your IDE not telling you that the name is illegal?

No. I created that class in Godot, by right clicking the node and adding a script.

The MRP link is broken (the repo must've been removed) and I'm not able to reproduce this issue in v3.5.stable.mono.official [991bb6ac7].
Using the name of a Godot's class as your script class' name is valid in C# as long as they are in different namespaces, although it is discouraged.
I'll close this issue since I can't reproduce it, if anyone is able to reproduce this issue please open a new issue with a minimal reproduction project attached.


Add more details to stored errors

Add more details to errors to comply with error-alert exigences

@claire-lovisa thanks


Jlink software tools: init at V7.92k

Description of changes
SEGGER's J-Links are one of the most widely used debug probes available today for embedded usage.
This PR packages their Software and Documentation pack  which provides a large set of utilities for use with their debug probes.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I am aware that the conditional fetchurl instead of requireFile may be a bit controversial.
I believe that it is a bit more ergonomic for users that are aware of the package's license and
want to automate it's installation.
If deemed unwanted, could I perhaps add the sha256 and url as passthru attributes for the derivation's source attribute? Then users can override the src attribute by explicitly using fetchurl and reusing the passthru attributes.

I missed the PR at https://github.com/NixOS/nixpkgs/pull/255185/commits
I am using the unstable branch and the package was missing, I was not aware it was present in the stable branch. Should I close this?


Upgrade netty version to 4.1.68.Final to avoid cve-2021-37136

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

Waiting for https://github.com/line/armeria/issues/3832

Are they going to release shortly?


pkg/operator: Fix metrics importing tracking

We were overwriting the metrics slice in importResults rather than appending to it, this fixes that. We also sort sooner to ensure the metricBegin/metricsEnd log message fields are accurate.

/retest

/retest

/retest

/retest

/retest

/lgtm


Combinging npo_check and npo_align, Resolving & Tracking missing nodes

This PR contains two thinks, those are:

Combining npo_check and npo_align. These two scripts are sequential, so with the combination the script will be run one time.
Adding new properties completeness and missing-nodes. This properties will be accessible from annotation from mapserver. With these properties, mapviewer can filter for those edge with missing nodes.

Adding new properties completeness and missing-nodes. This properties will be accessible from annotation from mapserver. With these properties, mapviewer can filter for those edge with missing nodes.

How will these new properties be used in mapviewer? Are you working on the changes for mapviewer? Regardless, please raise a ticket here to describe their use. Thanks.

Included with PR #70 so closing.


Cannot input the colon (:) when editing the custom renaming rules

Cannot input the colon (:) when editing the custom renaming rules.
As below:

Hmm...
I disabled colon because windows names cannot contains them, but I that this solution is not correct.

Fixed by 0fe9753eceac56321a49b44c6ec390d30ba0a494


Upgrade support: No upgrade button / Packages tab shows available version but not installed version

Packages tab shows installed version but not installed version for installed packages, it also seems only shows an install button but not an upgrade button for already installed packages

try version 4.0
https://github.com/HandyOrg/HandyWinGet/releases/tag/v4.0.0-beta.1


MakePrintable and coloured blocks (image to text)

I am looking to integrate a bit of code I use in a regular terminal app to output images converted to coloured character blocks. My attempt has gone through ConsoleDriver.MakePrintable, but I am unsure if this is sufficient for display in normal Label views - by simply setting its Text attribute.
My attempt currently just yields a sea of control character output:
NStack.ustring rendering = await RenderImage ("examle.png", 40, 40);
IEnumerable<Rune> runes = rendering.Select (character => ConsoleDriver.MakePrintable (character));
NStack.ustring result = NStack.ustring.Make (runes)!;

m_Label.Text = result;

RenderImage runs https://hpjansson.org/chafa/ and pipes back the output. In a normal terminal app this works wonderfully when just passed to Console.Write, but as described, my attempt above results in control character output like [0m [7m [38; 5; 255m.
Do I need to do some sort of render context escape to properly handle these characters?

What kind of return is chafa producing? is it just characters or is it console control codes for colors etc?
I think you are best creating a new View subclass and adding your logic there.  But without diving into the library you are using its hard to advise.
There is a similar example View in v2 that could be a good place to start to see how a similar problem is tackled natively.


Merge with Dynamic Maximum Concurrency

Copied from https://rx.codeplex.com/workitem/43
Rx defines an overload of the Merge operator with a maxConcurrent parameter that is useful for controlling the level of concurrency through the number of active subscriptions to inner observables; however, the maxConcurrent parameter is static and in some cases it's impossible to write a query that changes the parameter dynamically.  Unsubscribing and re-subscribing to Merge won't work for a hot source due to the fact that Merge uses an internal buffer.  Unsubscribing will lose all of the inner observables that have already been buffered but aren't yet active, and since the source is hot, this causes permanent data loss.
Consider adding a Merge overload such as the one shown in the following discussion:
http://social.msdn.microsoft.com/Forums/en-US/62743ffd-befd-474a-8f0a-19dbaec7a926/design-question-throttling-hits-on-external-systems
It has the following signature:
IObservable<TSource> Merge<TSource>(this IObservable<IObservable<TSource>> source, IObservable<int> maxConcurrent)

What should the operator do when a smaller maxConcurrent value is signalled after a larger one? Stop consuming the excess active ones or let them finish and don't subscribe to new ones until the active source count goes below the current limit?

Here's the comment from the dynamic Merge operator in the linked discussion:
// When the maximum concurrency value is raised, try to dequeue and subscribe to as many
// available observables as needed to fill the new bounds.
//
// When the maximum concurrency value is lowered, do not dispose of any active observables.
//
// Lowering the maximum concurrency value does not imply cancelation; it only implies that
// future inner observables will be deferred until the number of active observables drops
// sufficiently.  The number of active observables may currently be higher than the current
// maximum concurrency value, though prematurely disposing of active observables may result
// in irreversible data loss.

This requires deep changes and possibly done for a lot of merge variants. This is a really old issue, do you still want this or would an implementation with existing building blocks suffice?


[OTHER]Creation of a feedback page

Describe
A clear and concise description of what would you like to add/improve.
A feedback page to know the user experience ant to improve the services, please assign this to me under jwoc 2024
Screenshots
If applicable, add screenshots to help explain your problem

CheckList

[x ] I'm a JWOC'24 Contributor
[ x] I've checked the existing issues, this issue is not a duplicate

@thesri there is already a rate us page present in the website where user can provide the feedback. The screenshot you have added is not uploaded properly. Kindly elaborate more & attach an appropriate screenshot

@thesri there is already a rate us page present in the website where user can provide the feedback. The screenshot you have added is not uploaded properly. Kindly elaborate more & attach an appropriate screenshot

like this, like this is for a travel website i want to make a similar one for this website


Transaction: transaction signature verification method "ValidateTx" performance need to improve

Currently ValidateTx method is almost need 20ms per time.

@rosona We can replace the currently used BouncyCastle implementation with Secp256k1.Net (which is a wrapper for the optimized C implementation). According to the below test stats, the efficiency can be improved by ~20x.
Test stats:
Signing

Repetition
Current(ms)
Secp256k1.Net(ms)

1
14.319
1.361

10
13.979
0.704

100
144.31
6.609

1000
1347.958
67.738

10000
13026.812
642.685

100000
131423.906
6360.004

Verifying

Repetition
Current(ms)
Secp256k1.Net(ms)

1
22.174
0.984

10
31.931
1.169

100
254.593
10.686

1000
2512.999
100.123

10000
25417.837
1086.923

100000
256273.398
10422.293

@gldeng seems like an interesting wrapper, especially that it seems that it has the recover pubkey functionality

Test on latest build, it seems not change too much.

Fix it
For TxMemPool/TxHub.cs VerifySignature method perf:
old
    N           Min           Max        Median           Avg        Stddev
x 33995             9           297            24     33.566201     27.280559

new
    N           Min           Max        Median           Avg        Stddev
x 30460             0            21             0    0.25387393     1.2758351

Close due to fixed.


Import lubridate?

ymd_hms would be a lot simpler than %Y/%m/%d %h:%m:%s in DESCRIPTION files.

...but also less flexible. I just implemented fractional_doy() in 27bc9d1daafc585bef918e1cfd18299ff8525f36 so sticking with base R.


ContentAssistant does work right with real Ibmi-DB2 SQL-Tables (metadatasource=0/1 and naming=system)

System information:

Operating system (distribution) and version === Microsoft Windows 10 Enterprise - Version 10.0.19042 Build 19042
DBeaver version === Version <IP_ADDRESS>104181339 - Released 19 April 2021
Additional extensions === NO, standalone DBeaver instance - Same behaviour in the Eclipse IDE.

Connection specification:

Database name and version ===  Ibmi DB2 V7R4 - Latest TR
Driver name === DB2 iSeries/AS 400 - net.sf.jt400:jt400:RELEASE - Version 10.6
Do you use tunnels or proxies (SSH, SOCKS, etc) === NO

Describe the problem you're observing:

DBeaver is really a very very good tool to work with databases. Many thanks !

I read thru the docs and issues, but did not see what I'm doing wrong.

I would like to actively contribute to find solutions/document/test because we are currently moving to 'real' SQL-Tables instead of PFs and LFs (legacy physical and logical files) and the issues have mostly to do with these new tables.

I can use the Ibmi system I develop on to carry out tests. I cloned the repo to start debugging.

I think all the issues have to do with these driver settings :

naming="system" meaning that the DB-objects are searched in a list of schemas (Libraries) instead of only the one set with SET SCHEMA
metadatasource="0" (Retrieve Object Information) or "1" (SQL stored procedures) or "-1" (??)

Just wanna give an overview of the issues here. I can split them apart later on into separate bugReports for easier handling and supply more details.

Issue 1 : Table properties do not show ANY columns for real SQL-Tables :

Note that an SQL-Script shows the right metadata

Issue 2 : Table properties for legacy PFs do not show column descriptions when metadatasource="1"

Issue 3 : Content assistant in SQL script does only find tables when a schema is set (is against naming=system)

Issue 4 : Content assistant in SQL script does not show columns for real SQL-Tables

does not show for real SQL-Tables

does show right for legacy PFs

Steps to reproduce, if exist:
Include any warning/errors/backtraces from the logs

Sorry for the long responce. I cannot reproduce the issues on DB2 LUW. I will try to find out something.

Sorry for the long responce. I cannot reproduce the issues on DB2 LUW. I will try to find out something.

No problem.
In the meantime, I cloned the repo and could find explanations/fixes for some of the issues.
I would like to open separate issues for better readability and contribute my changes as a starting point for enhancements/discussions.
Is that OK for you ?
Here a summary of my findings :

DB2 is the common name for Ibm DB-products, but they differ significantly. That's the reason why it is difficult to reproduce issues on another platform :

DB2 for i is the product that I use (runs on IbmI, formerly known as AS/400 )
DB2 for Linux/Unix/Windows
DB2 for z/os runs on mainframes

About Issue 1 : Table properties do not show ANY columns for real SQL-Tables :

AS400JDBCDatabaseMetaData driver is very sensitive what regards case
lowercase table names are automatically uppercased if not surrounded by "" thus misleading the driver

About Issue 2 : Table properties for legacy PFs do not show column descriptions when metadatasource="1"

nothing found yet

About Issue 3 : Content assistant in SQL script does only find tables when a schema is set (is against naming=system)

DB2 for I works with a concept of library List that is a list of schemas (instead of just 1 schema)
DBeaver currently does not support that.

About Issue 4 : Content assistant in SQL script does not show columns for real SQL-Tables

same reason as issue 1

Thank you for your investigation. We don't have a fix for it as of now. If you would like to contribute buy doing a pull request we will gladly review it.


Admin should not be default user

Greetings,
I am a security researcher, who is looking for security smells in Puppet scripts. I noticed instances of keeping admin users as default in Puppet classes. I think this is a smell related to security. The smell can violate the ‘principle of least privilege (https://en.wikipedia.org/wiki/Principle_of_least_privilege)’ property, which recommends practitioners to design and implement system in a manner so that by default the least amount of access necessary is provided to any entity.
Would you agree with my finding? Any feedback is appreciated.
Source: https://github.com/CiscoSystems/puppet-openstack/blob/master/manifests/auth_file.pp

Greetings,
I am a security researcher, who is looking for security smells in Puppet scripts. I found instances where the HTTP protocol is used instead of HTTPS (HTTP with TLS). I think this is a smell, and I was wondering why HTTP is used? Is it because of lack of tool support?
I am trying to find out if developers are forced to adopt bad practices due to lack of tool support when it comes to the HTTPS protocol. Maybe it is due to dependency on a resource that uses HTTP?
Any feedback is appreciated.
Source: https://github.com/CiscoSystems/puppet-openstack/blob/master/manifests/controller.pp. (line#107, 216)


[chore]: Adopt vet for Automated OSS Package vetting to Prevent Risky OSS Dependencies

Is your feature request related to a problem? Please describe
Not a problem. Proposing a free and open source tool integration to improve the security of CircuitVerse code base.
Describe the solution you'd like
Team
I am the creator and maintainer of vet, tool to automate vetting of open source dependencies in PR using custom policies (as code). I wanted to check if you are willing to adopt vet to setup a policy driven security guardrail against risky OSS packages being added to CircuitVerse as dependencies.
Example PR vetted by vet:
https://github.com/safedep/vet/pull/239#issuecomment-2331412400
Example policy using which the vetting was done:
https://github.com/safedep/vet/blob/main/.github/vet/policy.yml
If there is interest, I am happy to contribute a PR to integrate vet as a GitHub Action to scan dependency changes during PR in CircuitVerse as per your customised policies.
How does this help?
To reduce the risk of vulnerable or malicious rubygems or npm packages being added to CircuitVerse as dependencies. Also to assist code reviewers to make a faster decision on PRs from the community that add new dependencies.
Describe alternatives you've considered
You can also use GitHub Dependency Review for similar use-cases. But vet is purpose built for developers with high flexibility of risk definition and customization using policy as code.
Additional context
No response
Are you working on this?
Yes

We are open to experiment with this tool, but we will remove this tool if it doesn't provide enough value in our workflow.

Thanks @tachyons I will get a PR raised against this issue to integrate vet as a GitHub Action.

@tachyons @smritigarg I raised a PR to integrate vet with CircuitVerse.
I am happy to volunteer and contribute to CircuitVerse in reviewing PRs with potential security issues identified by vet or any other tool that you may have in CI. I don't want to dump vet on you. If there are failures or other issues related to vet, I can look at it as a CircuitVerse contributor.
I see there are a bunch of older gems with known vulnerabilities. I am happy to contribute updates as well but that will take a while because there may be breaking changes in newer version of the gem which requires some code refactoring.


Cannot build 'base' image, preventing other images from building.

I'm using Docker 20.10.2.  I've tried using Java 8, 11, and 14 all unsuccessfully.  It will build a few images, but then it will get stuck on building base and won't go any further.  It'll just sit there and run forever without actually making any progress.
#15 exporting to image
#15 sha256:e8c613e07b0b7ff33893b694f7759a10d42e180f2b4dc349fb57dc6b71dcab00
#15 exporting layers done
#15 writing image sha256:fefcaafd23eb784049713e005f1eace37d0cfd44f4760ea7437fa0dab91ed225 done
#15 naming to docker.io/local/crayfish:latest done
#15 DONE 0.0s
<=======------> 58% EXECUTING [1m 13s]
> IDLE
> IDLE
> :base:build

This used to work for me as of a few months ago.  I'd like to build and test updating matomo, but am having a heck of a time getting it to build after I bump the version number and the sha for the download.

It wouldn't be able to build crayfish without first building base.  Likely has nothing to do with Java, perhaps buildkit is dying under heavy load (I've noticed that a few times myself) in which cases the process just hangs until it times out.
https://github.com/Islandora-Devops/isle-buildkit/pull/238
Uses a different build system (which can fail in the same way) but subsequent runs generally work.


Make sure we are compatible with webpack2

changes were needed to jsonix so it's now forked and we're using the fork for now until it gets addressed

Coverage remained the same at 75.123% when pulling 405960817f315bae672f2a56e851291bc427f456 on webpack2 into 24c8f0b75f8284173def35b18cf144dc9cb26972 on master.


data-tomark-pass attr only work once. (3MD)

Version

1.2.6
Test Environment

Chorme,Mac OS
Current Behavior

put the code in editor:

123

123

123

123

change mode from markdown to wysiwyg:

then back to markdown mode:

Expected Behavior

data-tomark-pass attribute never be remove.

@LinFeng1997 Sorry for late reply. We tried to maintain html tag that is inserted in markdown. So if the tag maintain while change mode, you don't need to use data-tomark-pass. Also I recommend not to use data-tomark-pass because it is for internal implement.


Create clear-docker-containers.sh

What the program do ?
TL;DR it'll get rid of all Docker containers that didn't self-destroy after run (ps -a)

It grabs the output from docker ps -a and only grabs the ID of the container.
It makes sure the output is a one-liner by using tr
it pipes the output of this to docker rm by using xargs

In what programming language it is written?
Bash

This pull request exeeds the max additions limit. Please fix it and reopen


Real cases using the template

Hi,
Thank you for making this useful template.
I just wonder if we have any real projects in which the template was used.
It would be helpful to see how the template works in concrete examples, what to write in the Makefile, etc.
Thank you!

I came across this project for anyone that this remains of interest to:
https://github.com/cduvallet/microbiomeHD

Closing in favor of having people post these in Show and tell, which we just enabled.


Save Not Working

Error: Service Unavailable
Error: Service Unavailable
    at Request.<anonymous> (https://homebrewery.naturalcrit.com/homebrew/bundle.js:71824:19)
    at Request.Emitter.emit (https://homebrewery.naturalcrit.com/homebrew/bundle.js:1764:20)
    at XMLHttpRequest.xhr.onreadystatechange (https://homebrewery.naturalcrit.com/homebrew/bundle.js:72133:10)
{
  "status": 503,
  "method": "PUT",
  "url": "/api/updateGoogle/mTieLoZq6eUi"
}

Try following the steps in #1580 - this should resolve your issues. If you continue to experience this problem, please re-open this issue.


Tools to validate standards compliance

We need to run tests that ensure the data products meet data and metadata format specifications.
Description
ARPA-E milestone for Nov 2017 is to have tests that data products match published metadata standards
Details

would prevent issues with changing source meta-data

could be used to ensure correct data format from providers

a test for extractors

BETYdb has a solid suite of tests; these may not need to be extended other than capturing errors consistently with other tests

Completion Criteria

[ ] discuss
[ ] break into manageable chunks and create new issues

Examples for external standards compliance

cfchecker --> CF compliance
OGC --> http://www.opengeospatial.org/compliance

Also need to add internal compliance checks
Identify first class data products --> what need to be complied
For example, hyperspectral workflow has three products:

level 1: cubes clipped to plot of reflectance values at full resolution, CF + OGC compliant
level 2: cube clipped to plot of indices and masks at full resolution, CF + OGC compliant
level 3: plot level means of each index inserted into BETYdb

For FLIR, RGB, other images

level 1: geoTIFF clipped to plot, OGC compliant
level 2: plant/soil mask
level 3: traits in BETYdb

need to go through this for ea. data product

next steps:

identify first class data products
for these, compile current metadata outputs from extractors
map to OGC, CF, etc
determine what compliance means