Loading arbitrary text into modules

Vaguely related to #581.
The WebAssembly ports can be run in environments where the filesystem is read-only or doesn't exist at all. To give users the ability to add code, I hacked in a $load_chars system predicate that sometimes relied on the looser module behavior.
// trealla-js api
pl.consultText("foo(bar).", "mymodule")

Runs a query like this:
mymodule:'$load_chars'("foo(bar).").

There's a quick fix:
module(mymodule), mymodule:'$load_chars'("foo(bar).").

But I was wondering if having a non-hacky way to load arbitrary text into a (potentially new) module might be useful? Even as an internal system predicate. Perhaps it could take the module as an argument instead of relying on the old implicit behavior.
There are a couple other places where I use this:

To let people write predicates in Javascript/Go, it loads a shim into user which looks kind of like: user:'$load_text'("my_cool_predicate(A) :- '$host_call'(my_cool_predicate(A)).") ← this could just be an assertz instead, but it would be nice to keep it non-dynamic.
I have a predicate http_consult(Module:URL) which loads code from a URL into the given (new) module, this is the main thing that broke from the module changes. To be honest, the usefulness of this one is questionable, I mostly just put it in for fun.

As for prior art, SWI's load_files/2 can take module(Name) as one of the options, but I'm not sure if you can give it strings of code to load. Pengines lets you load code as a query parameter, so it probably exists somewhere.
Here's the code I have for my internal predicate, it's pretty simple. I'm happy to just tack on a module name and create it here, but if we had a better way to do this it would be one step closer to move away from needing a wasm fork.
static bool fn_sys_load_chars_1(query *q)
{
	GET_FIRST_ARG(p1,any);
	size_t len;
	module *m = NULL;

	if (is_cstring(p1)) {
		const char *src = C_STR(q, p1);
		m = load_text(q->st.m, src, q->st.m->filename);
	} else if (scan_is_chars_list(q, p1, p1_ctx, true) > 0) {
		char *src = chars_list_to_string(q, p1, p1_ctx);
		m = load_text(q->st.m, src, q->st.m->filename);
		free(src);
	} else if (is_nil(p1)) {
		return false;
	} else
		return throw_error(q, p1, p1_ctx, "type_error", "chars");

	check_heap_error(m);
	return true;
}

I think module/1 should not create a module, rather just be a test for
existence.
On Fri, 30 Aug 2024, 21:40 guregu, @.***> wrote:

Vaguely related to #581
https://github.com/trealla-prolog/trealla/issues/581.
The WebAssembly ports can be run in environments where the filesystem is
read-only or doesn't exist at all. To give users the ability to add code, I
hacked in a $load_chars system predicate that sometimes relied on the
looser module behavior.
// trealla-js apipl.consultText("foo(bar).", "mymodule")
Runs a query like this:
mymodule:'$load_chars'("foo(bar).").
There's a quick fix:
module(mymodule), mymodule:'$load_chars'("foo(bar).").
But I was wondering if having a non-hacky way to load arbitrary text into
a (potentially new) module might be useful? Even as an internal system
predicate. Perhaps it could take the module as an argument instead of
relying on the old implicit behavior.
There are a couple other places where I use this:

To let people write predicates in Javascript/Go, it loads a shim
into user which looks kind of like: user:'$load_text'("my_cool_predicate(A)
:- '$host_call'(my_cool_predicate(A)).") ← this could just be an
assertz instead, but it would be nice to keep it non-dynamic.
I have a predicate http_consult(Module:URL) which loads code from a
URL into the given (new) module, this is the main thing that broke from the
module changes. To be honest, the usefulness of this one is questionable, I
mostly just put it in for fun.

As for prior art, SWI's load_files/2 can take module(Name) as one of the
options, but I'm not sure if you can give it strings of code to load.
Pengines lets you load code as a query parameter, so it probably exists
somewhere.
Here's the code I have for my internal predicate, it's pretty simple. I'm
happy to just tack on a module name and create it here, but if we had a
better way to do this it would be one step closer to move away from needing
a wasm fork.
static bool fn_sys_load_chars_1(query *q)
{
GET_FIRST_ARG(p1,any);
size_t len;
module *m = NULL;
if (is_cstring(p1)) {
const char *src = C_STR(q, p1);
m = load_text(q->st.m, src, q->st.m->filename);
} else if (scan_is_chars_list(q, p1, p1_ctx, true) > 0) {
char *src = chars_list_to_string(q, p1, p1_ctx);
m = load_text(q->st.m, src, q->st.m->filename);
free(src);
} else if (is_nil(p1)) {
return false;
} else
return throw_error(q, p1, p1_ctx, "type_error", "chars");
check_heap_error(m);
return true;
}
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/582, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSERD5WTP6AHFARFUP7LZUBK3JAVCNFSM6AAAAABNMJ5YROVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4TMOJZHA2DIMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I think module/1 should not create a module, rather just be a test for
existence.

I agree that way makes more sense, the current behavior creates a module though. A different blessed way to create a module would solve my problem.

At least the module part that is. The text loading part is the other bit. One alternative would be a C API for it, working kind of like how consult(user) does. Having a predicate is nice though.

I think module/1 should not create a module, rather just be a test for existence.

The standard predicate to test module existence, or enumerate existing modules by backtracking, is current_module/1. No reason to deviate from that. The module/1 predicate is used by some systems to set the "type-in" module, usually at the top-level.

Do you think module/1 should create modules then?
On Sat, 31 Aug 2024, 17:55 Paulo Moura, @.***> wrote:

I think module/1 should not create a module, rather just be a test for
existence.
The standard predicate to test module existence, or enumerate existing
modules by backtracking, is current_module/1. No reason to deviate from
that. The module/1 predicate is used by some systems to set the "type-in"
module, usually at the top-level.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/582#issuecomment-2322819830,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEUZV5HZHNGR654C5QTZUFZHPAVCNFSM6AAAAABNMJ5YROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRSHAYTSOBTGA
.
You are receiving this because you commented.Message ID:
@.***>

Do you think module/1 should create modules then?

The module/1 predicate do create modules (when the argument is not an already existing module) as a side-effect when changing the default top-level module in SWI-Prolog and YAP. See e.g. https://www.swi-prolog.org/pldoc/doc_for?object=module/1

Everything looks good to me, thanks!


Aead

Codecov Report
Attention: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 69.64%. Comparing base (531d72f) to head (61c2c81).
Report is 8 commits behind head on main.

Files
Patch %
Lines

cry/enc.go
83.33%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #475      +/-   ##
==========================================
+ Coverage   69.39%   69.64%   +0.25%
==========================================
  Files          55       55
  Lines        6423     6407      -16
==========================================
+ Hits         4457     4462       +5
+ Misses       1642     1626      -16
+ Partials      324      319       -5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


go-to-def doesn't jump to template template parameter decl.

Given the following dependent code:
template<template<typename> typename X, typename Y>
void k() {
  X a;  // issue: go-to-def on X does nothing
  Y b; // good: go-to-def on Y jumps to the template parameter Y
}

We probably miss something when handling the DeducedTemplateSpecializationType in FindTarget.cpp

My first thought was that X a; is not a valid usage of a template-name X.
But since C++17, it is (the template arguments could be deduced using CTAD).


chore: fix paramspace test case

Description

QC

[x] The PR contains a test case for the changes or the changes are already covered by an existing test case.
[x] The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

@SichongP I have created a PR from your repo containing the fix.


Problem Initializing vertex array

I declare
Vertex_Array                 : GL.Objects.Vertex_Arrays.Vertex_Array_Object;
then either
GL.Objects.Vertex_Arrays.Initialize_Id(Vertex_Array);
or
Vertex_Array.Initialize_Id;
Project builds OK but running produces
constraint error: raised CONSTRAINT_ERROR : erroneous memory access
I have no problems with GL.Objects.Buffers.Buffer variables which initialize_id, bind and run without error.
Context is:
type tWindow is new Glfw.Windows.Window with null record;
Main_Window                : aliased tWindow;
Main_Window_Access  : access tWindow := Main_Window'Access;
Main_Window.Init(Window_Width, Window_Height, "HelloTriangle");
glfw.Windows.Context.Make_Current(Main_Window_Access);
What am I doing wrong?
Regards,
Roger

Does GL_Test.OpenGL3 (from the tests dir) work for you? Do you call Glfw.Init? I do not see any obvious error in the code lines you pasted. You may want to produce a minimal verifyable example.

I built gl_test-opengl3 but it failed with:
/Ada_Source/OpenGLAda-master/tests/gl_test-opengl3
Initialized GLFW window
raised CONSTRAINT_ERROR : erroneous memory access
[2016-11-21 11:30:56] process exited with status 1, elapsed time: 02.94s
I'll prepare a minimal verifyable example.
Thanks,
Roger

Minimal verifyable example:
vertex_array_test.adb.txt

Some warnings that occurred:
glfw-api.ads:327:39: warning: "Set_Window_User_Pointer.Pointer" involves a tagged type which does not correspond to any C type
glfw-api.ads:331:13: warning: return type of "Get_Window_User_Pointer" does not correspond to C type

Debugger produced:
Program received signal SIGSEGV, Segmentation fault.
0x0000000100023786 in gl.api.gen_vertex_arrays (param1=1, value=0) at /Ada_Source/OpenGLAda-master/src/gl/implementation/gl-runtime_loading.adb:429
Call stack:
gl.api.gen_vertex_arrays
gl.objects.vertex_arrays.initialize_id
vertex_array_test

Well, if the OpenGL 3 test fails, that indicates either a problem with your environment or an incompatibility of OpenGLAda with your environment. Can you give details about your OS, compiler, and OpenGL implementation?

I dug up this article: link
It seems like the implementation of glXGetProcAddress violates the spec because it may return a non-null pointer even if a function is not available. If that is the case, OpenGLAda will assume that the function exists and call it, which leads to the error you get.
So your problem is that your OpenGL implementation does not provide vertex arrays. And OpenGLAda does not recognize this because of a non-conforming glXGetProcAddress implementation (if it did, it would simply raise a Feature_Not_Supported_Exception). There's no workaround other than updating your OpenGL implementation if possible, or not using this feature.

My system is:
OSX 10.11.6
XCode 8.0
GNAT GPL 2016 (20160515-49)
Copyright (C) 1996-2016, Free Software Foundation, Inc.
glfw3-3.2.1
Using GL.Context:
OpenGL version supported:  3. 3
Renderer: Intel HD Graphics 3000 OpenGL Engine
Primary_Shading_Language_Version: 3.30
I understand that my "OpenGL implementation" is an Apple implementation.
I'll look into Apple's OpenGL documentation and also the link that you provided to try and figure out if there's a way around the problem.
Thanks for your explanation which clearly explains the problem.
Roger

The OpenGL 3 test should definitely work on OSX, I developed it there. Important for OSX is to explicitly specify the desired OpenGL version of your context before initializing the window:
Glfw.Windows.Hints.Set_Minimum_OpenGL_Version (Major => 3, Minor => 2);
Glfw.Windows.Hints.Set_Forward_Compat (True);
Glfw.Windows.Hints.Set_Profile (Glfw.Windows.Context.Core_Profile);

The test does that. I will check later on my Mac whether the OpenGL 3 test is broken for OSX.

I tried including
Glfw.Windows.Hints.Set_Minimum_OpenGL_Version (Major => 3, Minor => 2);
Glfw.Windows.Hints.Set_Forward_Compat (True);
Glfw.Windows.Hints.Set_Profile (Glfw.Windows.Context.Core_Profile);

in my minimal example but it still
raised CONSTRAINT_ERROR : erroneous memory access
I'm wondering if my OpenGL environment is somehow messed up?

You can try querying the actual context version with GL.Context.Major_Version and GL.Context.Minor_Version (they will fail if you did not get a context >= 3.x) after initializing the window. For me, it looks like OSX does deliver an old OpenGL 2 context to you (in which case GL.Context.Version_String should work).
Not that the article I linked does not apply to OSX since that does not use glXGetProcAddress – it uses CFBundleGetFunctionPointerForName instead and so it seems strange that you get that error. Did you correctly set -XWindowing_System=quartz when building?

GL.Context.Major_Version produces 3
GL.Context.Minor_Version produces 3
GL_Version                   : String := GL.Context.Version_String;
produces: raised CONSTRAINT_ERROR : erroneous memory access
presumably because my OpenGL is not version 2?
I am using GPS which produces the command line:
gprbuild -d -eL -P/OpenGL_Projects/GLFW Tutorial/Vertex_Array_Minimal/vertex_array_minimal.gpr -XLIBRARY_TYPE=static -XAuto_Exceptions=enabled -XMode=debug -s
Adding  -XWindowing_System=quartz doesn't seem to make any difference.

Is this relevant?
http://stackoverflow.com/questions/19825582/modern-opengl-with-glfw3-on-mac-osx-10-8-4-missing-glgenvertexarrays-and-glb

I built a C++ version using CodeBlocks.
This returned the compilation error; use of undeclared identifier 'glGenVertexArrays'.
However, it suggested 'glGenVertexArraysAPPLE' which I used.
The program then worked without complaint!

glGenVertexArrays should be available on OSX with #include <OpenGL/gl3.h> (but not with #include <OpenGL/gl.h>).
But the actual problem is that a C++ version that binds directly to the function is not comparable to the Ada version. OpenGLAda uses runtime loading for all OpenGL features beyond 1.1, so a function pointer for glGenVertexArrays is queried from the OS when first calling it. To be comparable, the C++ version would need to do the same stuff OpenGLAda does in GL_Subprogram_Reference.

The SO questions you linked concern headers. This is not relevant for OpenGLAda, because it does not require any C headers. But it is for recreating the issue with C++, as explained above.

I tested it on my Mac and get the same error. So it seems like OpenGLAda currently does not work on OSX. I currently have no idea what the actual issue is, but it obviously has to do with runtime loading of function pointers.
But one thing I noticed is that ld complains that the OpenGLAda files have been built for OSX 10.12, which indicates that AdaCore's GNAT GPL may be the culprit. So I tried using this distribution which claims to be for OSX 10.11. Curiously, compiling with this GNAT version yields the same ld warnings, but the OpenGL 3 test works with it. Please check if it works for you.

All my vertex array OpenGL programs, including OpenGL 3,  now work using
gcc-6.1.0-x86_64-apple-darwin15-2016-bin.tar.bz2
However, I don't get the ld complaint that you mention.
Regards,
Roger

Okay, then that is unrelated.
This would be nice to be reported to AdaCore, but I don't think bug reports on the GPL version have a high priority there. So best thing to do is to

[ ] document that OpenGLAda does not work with current GNAT GPL.

I agree, so we can close this issue now?

I will close it when the documentation updated happened.

README warns now about the problem.

Thanks for your help.
Regards,
Roger

On 24 Nov 2016, at 3:16 AM, flyx<EMAIL_ADDRESS>wrote:
Closed #15.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Re-architect to process per function

Upon deployment, a new sub-process should be created for the function, emulating the production service more closely. This enables emulation of "warm functions". Sub-processes should be shut down after a configurable period of inactivity. This change will eliminate the isolation configuration setting and simplify debugging.

Will solve #35


Support for user defined additional filters

Describe the feature
This enhancement will allow user to add any additional filters in app-config other than these current default filters [openFilter, incomingFilter, assigneeToMeFilter].
for example
defaultFilters:
- name: 'Open Bugs'
shortName: 'Bugs'
query: 'type = bug AND resolution = Unresolved ORDER BY updated DESC, priority DESC'
- name: 'Epics'
shortName: 'Epics'
query: 'type = epic AND resolution = Unresolved ORDER BY updated DESC, priority DESC'
Added value
This provides flexibility for users to tailor their dashboard views without modifying the core codebase.
Additional context

Hi, this sounds like a very useful feature! A PR would be much appreciated.


Add version number in dev env

Thanks for the PR, but it's not a bug it was intentional: by leaving out the version number for development builds, it makes it obvious to not use it for deployment (it saved some release already 😉 ).

We need to make the tester know the internal version No. And add the '(dev)' postfix makes it obvious.

I agree that this is a valid use case then, but to make it work you have to run the env script as part of the start script. Can you update your PR to fix this issue?
I also made a comment, while still at it let's make the version semver compatible if someone needs to manipulate it for some reason 😉

Hmmm seems that the test and test:ci scripts also needs to run the env script before, that's why the CI is broken I think


migrate remaining builds to android studio

Though the library has migrated long ago, the demo and messenger apps remain to be migrated. It would also be useful to migrate the presentation level test suites, and the crypto test suites.
https://developer.android.com/sdk/installing/migrate.html

Completed.


How would I add analytics?

How could I add google analytics to my site?

Follow Google's basic instructions. For step 3 ("…add the tag right after the opening <head> tag on each page"), you'll want to add the code to the base layout file, which gets used for all site pages:
/_includes/layouts/base.njk

Let me know if any issues!

If using Netlify for hosting then you can use their analytics add-on. It isn't free ($9/mo) but it's a good option, particularly since there's no code needed to set it up.

If using Netlify for hosting then you can use their analytics add-on. It isn't free ($9/mo) but it's a good option, particularly since there's no code needed to set it up.

another (free) option if using Netlify is to take advantage of their snippet injection. in fact, the documentation mentions analytics as a use case

Most analytics providers, retargeting services, and A/B testing services will give you an HTML snippet and ask you to add it to every page on your site. Netlify lets you do this without having to pollute the source code for the site with production specific analytics snippets.

Very useful to know, thanks @zackseuberling!


Auto-detect whether using AWS iGenome and run appropriate STAR version

Closes #808
Fixed locally https://github.com/nf-core/tools/issues/1530

K. Let me know if you have any more comments @mahesh-panchal or feel free to merge.


Missing template causes panic in Mixer

When I failed to register a custom template in mixer/template/BUILD, Mixer crashed with the following error. Hopefully, this could be handled in a more graceful manner.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x2051e73]

goroutine 1 [running]:
istio.io/mixer/pkg/runtime.(*handlerFactory).Build(0xc4202315c0, 0xc42037b230, 0xc4200a0a28, 0x1, 0x1, 0x2dc18e0, 0xc4203ce6c0, 0x100b4a0, 0xffffffffffffffff, 0x0, ...)
	pkg/runtime/handler.go:116 +0x273
istio.io/mixer/pkg/runtime.(*Controller).publishSnapShot.func1(0xc42037b230, 0xc4200a0a28, 0x1, 0x1, 0xc42039e8a8, 0x1, 0xc42039e978, 0x2258700)
	pkg/runtime/controller.go:136 +0x145
istio.io/mixer/pkg/runtime.(*handlerTable).initHandler(0xc4201cd458, 0xc4203a8d20)
	pkg/runtime/handlerTable.go:147 +0x267
istio.io/mixer/pkg/runtime.(*handlerTable).Initialize(0xc4201cd458, 0xc42037b110)
	pkg/runtime/handlerTable.go:135 +0x381
istio.io/mixer/pkg/runtime.(*Controller).publishSnapShot(0xc4201b3c20)
	pkg/runtime/controller.go:146 +0x2b3
istio.io/mixer/pkg/runtime.startController(0x2dc2b60, 0xc42025b680, 0xc42025b140, 0xc4203bae40, 0x2dc4160, 0xc42025acf0, 0x2da6660, 0xc4201ec100, 0x2469b71, 0x13, ...)
	pkg/runtime/init.go:112 +0x23c
istio.io/mixer/pkg/runtime.New(0x2dc4160, 0xc42025acf0, 0xc4202fae60, 0xc4202fae80, 0x2469b71, 0x13, 0x24618c1, 0xc, 0x2dc2b60, 0xc42025b680, ...)
	pkg/runtime/init.go:43 +0x11a
istio.io/mixer/cmd/server/cmd.setupServer(0xc4202bc000, 0xc4203bae40, 0xc420010500, 0xa, 0xa, 0xc4204023d0, 0x2, 0x2, 0x24e7740, 0x24e7738, ...)
	cmd/server/cmd/server.go:286 +0x5ba
istio.io/mixer/cmd/server/cmd.runServer(0xc4202bc000, 0xc4203bae40, 0xc420010500, 0xa, 0xa, 0xc4204023d0, 0x2, 0x2, 0x24e7740, 0x24e7738)
	cmd/server/cmd/server.go:439 +0x12c
istio.io/mixer/cmd/server/cmd.serverCmd.func2(0xc4204e5200, 0xc4203bb1a0, 0x0, 0x3)
	cmd/server/cmd/server.go:143 +0x7b
github.com/spf13/cobra.(*Command).execute(0xc4204e5200, 0xc4203bb0b0, 0x3, 0x3, 0xc4204e5200, 0xc4203bb0b0)
	external/com_github_spf13_cobra/command.go:647 +0x234
github.com/spf13/cobra.(*Command).ExecuteC(0xc4204e4000, 0xc4204e5440, 0xc4204e5200, 0xc4204e4240)
	external/com_github_spf13_cobra/command.go:734 +0x2fe
github.com/spf13/cobra.(*Command).Execute(0xc4204e4000, 0x4, 0x4)
	external/com_github_spf13_cobra/command.go:692 +0x2b
main.main()
	cmd/server/main.go:43 +0x248

Did this fail on startup? Or failed at a later time?
I agree It should not sigsegv .
I think it is better to fail hard on internal inconsistencies. An explicit panic is better with a clear error message that states missing template info.
/cc @guptasu
‘’’
// ti should be there for a valid configuration.
ti, _ := h.tmplRepo.GetTemplateInfo(tmplName)
‘’’
Code already states that it expects valid configuration.

This is broken since we are not yet validating the config during config
ingestion. There is  inot much we can do during runtime.
Will take a look to handle this better.
On Nov 11, 2017 5:22 PM, "mandarjog"<EMAIL_ADDRESS>wrote:

Assigned #1678 https://github.com/istio/istio/issues/1678 to @guptasu
https://github.com/guptasu.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/1678#event-1337426411, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK6xEwK0C3hr5jFzSwKxTXz-xwm99dyJks5s1kg_gaJpZM4QaqRP
.

I don’t think this is strictly related to config Validation. An adapter that is a part of the Mixer build is using an unknown template. This should fail build validation and must fail a unit test.

@mandarjog is this still a problem in mixer or has validation logic been added??

@jmuk I know you had a PR that was validating config during ingestion if the template referenced by instance config is valid or not ? This problem will go away if we reject the config during ingestion time.
Looking at the code, we are still doing the same thing and expect the config to be valid before.
@GregHanson is this blocking your development ? We are working on a new runtime2 design, and we can address this issue there as a temporary thing, but I think in the long term, we should reject configs that have broken references.

@jmuk friendly ping


feature: update user on login

To simplify user-management this pull request implements a feature, which updates the user's display name and email on log-ins using SAML2.
It is enabled using a new config-parameter: SAML2_UPDATE_USER_ON_LOGIN.

This is related to #3771. Ideally we'd align functionality across these methods, but SAML2 can be a starting point.

Since there's been recent follow up or activity I'll close this off.
Feel free to still comment or update though if there is progress and this can be re-opened if needed.


oui.mk: allow applications to omit htdoc folder

This is useful for "root" applications which provide top-level menu entries and/or RPC files without defining any views.

Merged. Thanks.


FalkorDB

To your knowledge engine part, I would add FalkorDB - a ultra-performant graph database for GraphRAG from the creators of Redis Graph

done in #48


Cannot install from palette

Hi,
I have tried to install from the palette, but there is a error which appears to be related to the canvas dependencies. I have read the other issues which may be related.

Node Red 1.0.6
I have tried to install canvas as root user as indicated this was possibly a permissions problem, but canvas won't even install on its own
There is a similar issue with node-red-contrib-face-recognition node which also won't install

Appreciate any advice
Error message
pi@CameraPi:~/.node-red $ npm install node-red-contrib-teachable-machine
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142

><EMAIL_ADDRESS>install /home/pi/.node-red/node_modules/canvas
> node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://github.com/node-gfx/node-canvas-prebuilt/releases/download/v2.6.1/canvas-v2.6.1-node-v64-linux-glibc-arm.tar.gz
node-pre-gyp WARN Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v64 ABI, glibc) (falling back to source compile with node-gyp)
Package pixman-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `pixman-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'pixman-1' found
gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. 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 (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.19.97+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/home/pi/.node-red/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/home/pi/.node-red/node_modules/canvas/build/Release" "--napi_version=6" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"
gyp ERR! cwd /home/pi/.node-red/node_modules/canvas
gyp ERR! node -v v10.20.1
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/home/pi/.node-red/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/home/pi/.node-red/node_modules/canvas/build/Release --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/pi/.node-red/node_modules/canvas/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
node-pre-gyp ERR! System Linux 4.19.97+
node-pre-gyp ERR! command "/usr/bin/node" "/home/pi/.node-red/node_modules/canvas/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/pi/.node-red/node_modules/canvas
node-pre-gyp ERR! node -v v10.20.1
node-pre-gyp ERR! node-pre-gyp -v v0.11.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/home/pi/.node-red/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/home/pi/.node-red/node_modules/canvas/build/Release --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1

I’m getting the same issue. Running on pi 4.
Any ideas for getting it to run?

I have not been able to get it to run on a Pi, but did get it to run on a Linux PC, possibly Pi related

For now it is not working due to the canvas npm module. It does not exist a pre-built package and it has problems when trying to compile it for the Raspberry Pi...
node-pre-gyp WARN Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
I have not yet investigated how to make it work on a Raspberry Pi (with the compilation of the canvas). What I tried to git rid of the canvas npm package... but could not find the solution. I only use canvas to handle the image though... The problem here is that teachable machine original npm package is designed to work within a webpage not in a server making use of all global objects such as document or canvas, and with this node I can emulate that so that it behaves as webpage (making use of JDOM library)... I also wanted to get rid of that... but with no success.
Let me know if you find any solution! Thanks!

Hi
Just tried to install from Node-red Manage Pallete on both Pi and Windows but just get this error
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/node-contrib-teachable-machine - Not found

On Raspberry Pi it is not supported yet. Windows is supported.
GET error seems like a npm bad connection http response, not a problem of the node itself. Can you try to install it again @Viggen-l ?

Yes know it's working on windows.
What's missing to run this on a Pi, the project i'am looking on are probably going to run on a Pi.

I think the issue on the Pi comes down to fsevents - linus is not supported OS (Darwin is).
If this dependency can be removed, then I think the Pi will work. I can get all other packages to install.

https://github.com/paulmillr/chokidar maybe this can be used instead of fsevents?

Thanks for working on this!  I am having the same issue, neither the npm install nor install through the palette works, both generate the same error message for me.
Is it possible to develop a specific version of the node for use on the Raspberry Pi?  Teachable Machine is a great starting idea, but currently seems rather limited to "look, my browser can tell if there's a cat in the image or not!"  But I want to actually be able to DO something with that information.  Being able to run those models on a Pi with Node Red making it easy to program the doing part (turn on GPIO pins, send text messages, etc.) would turn this from something kinda interesting to something actually super-useful.

Teachablemachine are easy but usefull, trying it out on a production line (node-red on windows) together with Siemens PLC and it's working well so far. But yes it would be nice to be able to run it on a Pi as or maybe Siemens IoT20** hardware.

New release v1.2.0 - compatible with Raspberry Pi and official dockerized Node-RED


Help with --help option for react_on_rails

See below for an example of what rails generate model --help does. Missing for react_on_rails:

[ ] Defaults for options (default is for the flag to be off, so default of -b means that skip-bootstrap is off. Default for -R is that redux is off.
[x] Detailed description. At least specify the URL of more docs.

Usage:
  rails generate react_on_rails:install [options]

Options:
  -R, [--redux], [--no-redux]                          # Install Redux gems and Redux version of Hello World Example
  -S, [--server-rendering], [--no-server-rendering]    # Add necessary files and configurations for server-side rendering
  -j, [--skip-js-linters], [--no-skip-js-linters]      # Skip installing JavaScript linting files
  -L, [--ruby-linters], [--no-ruby-linters]            # Install ruby linting files, tasks, and configs
  -H, [--heroku-deployment], [--no-heroku-deployment]  # Install files necessary for deploying to Heroku
  -b, [--skip-bootstrap], [--no-skip-bootstrap]        # Skip integrating Bootstrap and don't initialize files and regarding configs

Runtime options:
  -f, [--force]                    # Overwrite files that already exist
  -p, [--pretend], [--no-pretend]  # Run but do not make any changes
  -q, [--quiet], [--no-quiet]      # Suppress status output
  -s, [--skip], [--no-skip]        # Skip files that already exist

This is an example of what we should strive for:
rails generate model --help                                                                                ✭ [12:26:22]
Usage:
  rails generate model NAME [field[:type][:index] field[:type][:index]] [options]

Options:
      [--skip-namespace], [--no-skip-namespace]  # Skip namespace (affects only isolated applications)
      [--force-plural], [--no-force-plural]      # Forces the use of the given model name
  -o, --orm=NAME                                 # Orm to be invoked
                                                 # Default: active_record

ActiveRecord options:
      [--migration], [--no-migration]    # Indicates when to generate migration
                                         # Default: true
      [--timestamps], [--no-timestamps]  # Indicates when to generate timestamps
                                         # Default: true
      [--parent=PARENT]                  # The parent class for the generated model
      [--indexes], [--no-indexes]        # Add indexes for references and belongs_to columns
                                         # Default: true
  -t, [--test-framework=NAME]            # Test framework to be invoked
                                         # Default: test_unit

TestUnit options:
      [--fixture], [--no-fixture]   # Indicates when to generate fixture
                                    # Default: true
  -r, [--fixture-replacement=NAME]  # Fixture replacement to be invoked

Runtime options:
  -f, [--force]                    # Overwrite files that already exist
  -p, [--pretend], [--no-pretend]  # Run but do not make any changes
  -q, [--quiet], [--no-quiet]      # Suppress status output
  -s, [--skip], [--no-skip]        # Skip files that already exist

Description:
    Stubs out a new model. Pass the model name, either CamelCased or
    under_scored, and an optional list of attribute pairs as arguments.

    Attribute pairs are field:type arguments specifying the
    model's attributes. Timestamps are added by default, so you don't have to
    specify them by hand as 'created_at:datetime updated_at:datetime'.

    As a special case, specifying 'password:digest' will generate a
    password_digest field of string type, and configure your generated model and
    tests for use with ActiveModel has_secure_password (assuming the default ORM
    and test framework are being used).

    You don't have to think up every attribute up front, but it helps to
    sketch out a few so you can start working with the model immediately.

    This generator invokes your configured ORM and test framework, which
    defaults to ActiveRecord and TestUnit.

    Finally, if --parent option is given, it's used as superclass of the
    created model. This allows you create Single Table Inheritance models.

    If you pass a namespaced model name (e.g. admin/account or Admin::Account)
    then the generator will create a module with a table_name_prefix method
    to prefix the model's table name with the module name (e.g. admin_accounts)

Available field types:

    Just after the field name you can specify a type like text or boolean.
    It will generate the column with the associated SQL type. For instance:

        `rails generate model post title:string body:text`

    will generate a title column with a varchar type and a body column with a text
    type. If no type is specified the string type will be used by default.
    You can use the following types:

        integer
        primary_key
        decimal
        float
        boolean
        binary
        string
        text
        date
        time
        datetime

    You can also consider `references` as a kind of type. For instance, if you run:

        `rails generate model photo title:string album:references`

    It will generate an `album_id` column. You should generate these kinds of fields when
    you will use a `belongs_to` association, for instance. `references` also supports
    polymorphism, you can enable polymorphism like this:

        `rails generate model product supplier:references{polymorphic}`

    For integer, string, text and binary fields, an integer in curly braces will
    be set as the limit:

        `rails generate model user pseudo:string{30}`

    For decimal, two integers separated by a comma in curly braces will be used
    for precision and scale:

        `rails generate model product 'price:decimal{10,2}'`

    You can add a `:uniq` or `:index` suffix for unique or standard indexes
    respectively:

        `rails generate model user pseudo:string:uniq`
        `rails generate model user pseudo:string:index`

    You can combine any single curly brace option with the index options:

        `rails generate model user username:string{30}:uniq`
        `rails generate model product supplier:references{polymorphic}:index`

    If you require a `password_digest` string column for use with
    has_secure_password, you should specify `password:digest`:

        `rails generate model user password:digest`

Examples:
    `rails generate model account`

        For ActiveRecord and TestUnit it creates:

            Model:      app/models/account.rb
            Test:       test/models/account_test.rb
            Fixtures:   test/fixtures/accounts.yml
            Migration:  db/migrate/XXX_create_accounts.rb

    `rails generate model post title:string body:text published:boolean`

        Creates a Post model with a string title, text body, and published flag.

    `rails generate model admin/account`

        For ActiveRecord and TestUnit it creates:

            Module:     app/models/admin.rb
            Model:      app/models/admin/account.rb
            Test:       test/models/admin/account_test.rb
            Fixtures:   test/fixtures/admin/accounts.yml
            Migration:  db/migrate/XXX_create_admin_accounts.rb

@justin808 below description is a bit confusing:

Defaults for options (default is for the flag to be off, so default of -b means that skip-bootstrap is off. Default for -R is that redux is off.

should it be ?:

Defaults for options (default is for the flag to be off, so default of -b means that skip-bootstrap is off. Default for -R is that redux is on.


[portaudio] Expose CMake targets, not just headers/libraries?

Is your feature request related to a problem? Please describe.
http://www.portaudio.com/docs/v19-doxydocs/compile_cmake.html#cmake_building upstream exposes targets accessible via find_package(portaudio).
However, when I run vcpkg install portaudio, I do not get a message saying CMake targets were added. (vcpkg install sqlite3 has a message.) Subsequently, if I try running find_package(portaudio REQUIRED) in another project using CMake vcpkg, it does not find it.
Similar to https://github.com/microsoft/vcpkg/issues/7632
Proposed solution
According to upstream docs, portaudio's CMakeLists.txt is designed to allow find_package() to work. vcpkg should expose these targets to projects using vcpkg.
Describe alternatives you've considered
vcpkg already exposes the headers and dynamic/static .lib, but this requires more complexity to use in another CMake project than find_package.
(I don't know how find_package works.)
Additional context
Windows 10 x64 1903, en-US, CMake (not msbuild).

Hi @jimbo1qaz
I took a look at our portaudio port and it seems to be outdated, which explains the lack of CMake targets. Would you be able to create a PR to update it to a more recent version?

portaudio is an old and very slow-moving library... According to http://www.portaudio.com/download.html, pa_stable_v190600_20161030 is the most recent release. portaudio v19 was released back in 2007, and has the API not had breaking changes since then?

@NancyLi1013
They have a Git repo, which means that we can use vcpkg_from_git() to fetch a stable commit or tag.
https://app.assembla.com/spaces/portaudio/git/source
git clone  https://git.assembla.com/portaudio.git

Hi @jimbo1qaz thanks for posting this issue. This port has been updated. This issue should be fixed now. Please try to update vcpkg and use it.
@vicroms thanks for the info you provided above.


connect with ogario and quantity of minions

1)how to connect with ogario?
2)with this code if (this.config.serverMinions > 0 && ws.remoteAddress == "insert your ip here") {
How do I
Specify the number of minions with that code?

these questions..

Can you provide the link to the script?
You can already connect with that code, just insert it into the place where I told you.
What do you mean by "fix"

How do I
Specify the number of minions with that code?

use the serverMinions config

@Megabyte918 I cant do /login ADMIN Is there anyway to do /login samby??

@NameYT https://github.com/Megabyte918/MultiOgar-Edited/blob/master/src/enum/userRoles.json#L4


Attach to process quick pick (base code + POSIX support)

For #8701
This PR adds the base code to make the quick pick work + the code to make it work on linux+macOS (by calling the ps command)
Other PRs:

windows support
functional tests
picker content sorting

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[x] Has a news entry file (remember to thank yourself!)
[ ] Appropriate comments and documentation strings in the code
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[x] Unit tests & system/integration tests are added/updated
[ ] Test plan is updated as appropriate
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #9097 into master will decrease coverage by 0.45%.
The diff coverage is 34.45%.

@@            Coverage Diff             @@
##           master    #9097      +/-   ##
==========================================
- Coverage   57.13%   56.68%   -0.46%
==========================================
  Files         551      558       +7
  Lines       29108    29255     +147
  Branches     4397     4404       +7
==========================================
- Hits        16631    16582      -49
- Misses      11570    11765     +195
- Partials      907      908       +1

Impacted Files
Coverage Δ

src/client/common/constants.ts
100% <100%> (ø)
:arrow_up:

src/client/common/utils/localize.ts
94.73% <100%> (+0.08%)
:arrow_up:

src/client/debugger/extension/serviceRegistry.ts
100% <100%> (ø)
:arrow_up:

src/client/debugger/extension/adapter/activator.ts
100% <100%> (ø)
:arrow_up:

...client/debugger/extension/attachQuickPick/types.ts
100% <100%> (ø)

...lient/debugger/extension/attachQuickPick/picker.ts
16.21% <16.21%> (ø)

...ient/debugger/extension/attachQuickPick/process.ts
25% <25%> (ø)

...ugger/extension/attachQuickPick/psProcessParser.ts
28.57% <28.57%> (ø)

...t/debugger/extension/attachQuickPick/psProvider.ts
35.48% <35.48%> (ø)

...ient/debugger/extension/attachQuickPick/factory.ts
46.66% <46.66%> (ø)

... and 32 more

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 2536a97...900054d. Read the comment docs.

Discussed offline with @kimadeline on how this code can be simplified. But we will do it when we get to the windows bits. This way we can be sure that the simplification makes sense and works for the various platforms.


Add local setup instructions for README

What is this PR doing?
Adding local setup instructions to readme for running the app locally.
How should this be manually tested?
Formatted readme can be viewed on the branch: https://github.com/maikthomas/opentok-meet/tree/readme-local-setup
You could follow the steps I added to the readme and try to run to the app.
What are the relevant tickets?
There is no ticket for this.

I think that's backwards, build should be the build process, if we want to
build on postinstall then the postinstall script should call the build
script, not the other way around
On Wed, 13 Jan 2021, 20:11 Kongpheng Nanthavongsa<EMAIL_ADDRESS>wrote:

@v-kpheng commented on this pull request.
In package.json
https://github.com/opentok/opentok-meet/pull/92#discussion_r556765391:

@@ -42,6 +42,7 @@
},
"scripts": {
"postinstall": "webpack",

"build": "webpack",

How do you feel about making build an alias of postinstall? This way, the
intention is more clear?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opentok/opentok-meet/pull/92#pullrequestreview-567537637,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2V4ZPA5NWN6C3F2S7U4E3SZXV5FANCNFSM4WA72HYQ
.

I think that's backwards, build should be the build process, if we want to
build on postinstall then the postinstall script should call the build
script, not the other way around
On Wed, 13 Jan 2021, 20:11 Kongpheng Nanthavongsa<EMAIL_ADDRESS>wrote:

@v-kpheng commented on this pull request.
In package.json
https://github.com/opentok/opentok-meet/pull/92#discussion_r556765391:

@@ -42,6 +42,7 @@
},
"scripts": {
"postinstall": "webpack",

"build": "webpack",

How do you feel about making build an alias of postinstall? This way, the
intention is more clear?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opentok/opentok-meet/pull/92#pullrequestreview-567537637,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2V4ZPA5NWN6C3F2S7U4E3SZXV5FANCNFSM4WA72HYQ
.

I think that's backwards, build should be the build process, if we want to build on postinstall then the postinstall script should call the build script, not the other way around

So you're a no-go for something like this?
"postinstall": "webpack",
"build": "npm run postinstall",

Or,
"postinstall": "webpack",
"build": "npm run install && npm run postinstall",

I think that's backwards, build should be the build process, if we want to build on postinstall then the postinstall script should call the build script, not the other way around

So you're a no-go for something like this?
"postinstall": "webpack",
"build": "npm run postinstall",

Or,
"postinstall": "webpack",
"build": "npm run install && npm run postinstall",

Yes I think that's the wrong way around.
The build script should define how to build the app.
If we want to build the app after installing, then we can reference build
from the postinstall.
If we want to do some other stuff later in postinstall we can add that to
the postinstall script, and this shouldn't affect the build process.
If it was the other way around then changing what we want to do after
installing would affect what the build script does.
On Wed, 13 Jan 2021, 20:29 Kongpheng Nanthavongsa<EMAIL_ADDRESS>wrote:

I think that's backwards, build should be the build process, if we want to
build on postinstall then the postinstall script should call the build
script, not the other way around
So you're a no-go for something like this?
"postinstall": "webpack",
"build": "npm run postinstall",
Or,
"postinstall": "webpack",
"build": "npm run install && npm run postinstall",
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opentok/opentok-meet/pull/92#issuecomment-759672534,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2V4ZPRZPCXWBEWNM6FC5DSZXYDJANCNFSM4WA72HYQ
.

Yes I think that's the wrong way around.
The build script should define how to build the app.
If we want to build the app after installing, then we can reference build
from the postinstall.
If we want to do some other stuff later in postinstall we can add that to
the postinstall script, and this shouldn't affect the build process.
If it was the other way around then changing what we want to do after
installing would affect what the build script does.
On Wed, 13 Jan 2021, 20:29 Kongpheng Nanthavongsa<EMAIL_ADDRESS>wrote:

I think that's backwards, build should be the build process, if we want to
build on postinstall then the postinstall script should call the build
script, not the other way around
So you're a no-go for something like this?
"postinstall": "webpack",
"build": "npm run postinstall",
Or,
"postinstall": "webpack",
"build": "npm run install && npm run postinstall",
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opentok/opentok-meet/pull/92#issuecomment-759672534,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2V4ZPRZPCXWBEWNM6FC5DSZXYDJANCNFSM4WA72HYQ
.

postinstall is a script that npm runs after it installs packages, we can't
rename it, it's is a npm hook of sorts.
On Wed, 13 Jan 2021, 21:36 Kongpheng Nanthavongsa<EMAIL_ADDRESS>wrote:

@v-kpheng commented on this pull request.
In README.md
https://github.com/opentok/opentok-meet/pull/92#discussion_r556812610:

+- redis (Recommended to install via homebrew on mac: see instructions)

+## Running meet locally
+
+- Copy the contents of config.json.sample into config.json and add your credentials.
+
+- Ensure redis is running (e.g. redis-server on mac)
+
+- Install npm dependencies
+
+ +npm i +
+
+- Run the server:
+
IOW, is there anything from preventing us from doing what we need to do in
order to make things better?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opentok/opentok-meet/pull/92#discussion_r556812610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2V4ZIV3QY5HC2L2HQFFOTSZX76DANCNFSM4WA72HYQ
.

postinstall is a script that npm runs after it installs packages, we can't
rename it, it's is a npm hook of sorts.
On Wed, 13 Jan 2021, 21:36 Kongpheng Nanthavongsa<EMAIL_ADDRESS>wrote:

@v-kpheng commented on this pull request.
In README.md
https://github.com/opentok/opentok-meet/pull/92#discussion_r556812610:

+- redis (Recommended to install via homebrew on mac: see instructions)

+## Running meet locally
+
+- Copy the contents of config.json.sample into config.json and add your credentials.
+
+- Ensure redis is running (e.g. redis-server on mac)
+
+- Install npm dependencies
+
+ +npm i +
+
+- Run the server:
+
IOW, is there anything from preventing us from doing what we need to do in
order to make things better?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opentok/opentok-meet/pull/92#discussion_r556812610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2V4ZIV3QY5HC2L2HQFFOTSZX76DANCNFSM4WA72HYQ
.

@albertoacn there's a line in the readme that says:
If you wish to fork this project, please fork the parent project.
Referring to the aullman repo.
It appears that this is no longer correct advice, the projects appear to have diverged and we are no longer keeping this up to date with aullman/opentok-meet.
If that's true then we should definitely remove this midleading info, wdyt?

@albertoacn there's a line in the readme that says:
If you wish to fork this project, please fork the parent project.
Referring to the aullman repo.
It appears that this is no longer correct advice, the projects appear to have diverged and we are no longer keeping this up to date with aullman/opentok-meet.
If that's true then we should definitely remove this midleading info, wdyt?

@maikthomas @v-kpheng
IMHO I am more of a fan of:
scripts: {
"build": "webpack",
"postinstall": "npm run build",
...
}

I just find it more intuitive, i.e. as a post install action we build the app. Building the app here means webpack. So every action does what is expected.
I found
"postinstall": "webpack",
"build": "npm run postinstall",

misleading since it feels we should run a post-install when building the app.

@maikthomas @v-kpheng
IMHO I am more of a fan of:
scripts: {
"build": "webpack",
"postinstall": "npm run build",
...
}

I just find it more intuitive, i.e. as a post install action we build the app. Building the app here means webpack. So every action does what is expected.
I found
"postinstall": "webpack",
"build": "npm run postinstall",

misleading since it feels we should run a post-install when building the app.

@albertoacn there's a line in the readme that says:
If you wish to fork this project, please fork the parent project.
Referring to the aullman repo.
It appears that this is no longer correct advice, the projects appear to have diverged and we are no longer keeping this up to date with aullman/opentok-meet.
If that's true then we should definitely remove this midleading info, wdyt?

yep, that's correct, this is the one ahead from a couple of years now. I would remove the fork parent repo line. People should just fork this repo (fork).

@albertoacn there's a line in the readme that says:
If you wish to fork this project, please fork the parent project.
Referring to the aullman repo.
It appears that this is no longer correct advice, the projects appear to have diverged and we are no longer keeping this up to date with aullman/opentok-meet.
If that's true then we should definitely remove this midleading info, wdyt?

yep, that's correct, this is the one ahead from a couple of years now. I would remove the fork parent repo line. People should just fork this repo (fork).

@albertoacn I have updated the npm scripts to what we agreed.
I have also updated the disclaimer info, and I added extra info about the config to avoid the problem we saw about having mismatch between dev and prod config.
Please re-review when you can

@albertoacn I have updated the npm scripts to what we agreed.
I have also updated the disclaimer info, and I added extra info about the config to avoid the problem we saw about having mismatch between dev and prod config.
Please re-review when you can


Fix linter errors

We need to fix relevant issues and disable irrelevant checks.

The last commit needs to be reverted.


fix: delete rebase from mike

This can be the fix for:
error: failed to push some refs to 'https://github.com/splunk/splunk-connect-for-snmp'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details."

according to https://github.com/jimporter/mike/issues/60

:tada: This PR is included in version 0.11.0-beta.14 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support more weekday formatting tokens

The following symbols from TR35 are not properly supported and need to be:

"EEE"
Other lengths of "E"?
various lengths of "e"?
"ccc"
"cccc"

This applies to both code generation in elm-cldr-generator and symbol expansion.

Fixed in 2.0.0 by doing our own formatting.


Custom index name doesn't work with nested field

The configuration file for fluentd is as below,
    <source>
      @type tail
      path /var/lib/docker/containers/*/*.log
      tag fluentd
      <parse>
        @type json
        time_key time
        keep_time_key true
      </parse>
      refresh_interval 5
    </source>
    <filter **>
        @type parser
        format json
        key_name log
        reserve_data true
        hash_value_field log
    </filter>
    <match fluentd>
      @type elasticsearch
      host elasticsearch
      port 9200
      flush_interval 10s
      index_name test-${log.tenantid}-%Y%m%d
      <buffer tag, log.tenantid, time>
         @type memory
         timekey 3600
      </buffer>
    </match>

I generated the following examle log entry,
{"level":"info", "tenantid":"tenant1", "msg":"hello"}
And docker converted the above log entry into:
{"log": "{\"level\":\"info\", \"tenantid\":\"tenant1\", \"msg":\"hello\"}", "stream":"stderr", "time":"2018-01-27T02:38:16.382229755Z"
Fluentd sent the log to elasticsearch successfully, and I could see the log on Kibana as well. But the issue was that the index name was "test--20180127", which wasn't what I expected. I was expecting to see the index name "test-tenant1-20180127".
Using Fluentd and ES plugin versions
OS version: Oracle Linux 7.3
Fluentd image was built with the following Dockerfile:
FROM fluent/fluentd:v0.12.33-debian
......
gem install fluent-plugin-elasticsearch
......

Thanks for the info.

could you show you new configuration for custom index name ? thanks

I wonder whether adoping buffer will cause fluentd to lose log entries when elasticsearch crashes or restarts?

For preventing to lose log, you can use @type file in buffer configuration:
<buffer tag, $.log.tenantid, time>
  @type file
  timekey 3600
</buffer>

If you don't use $.log.tenantid in buffer directive argument, emitting chunk order will be changed.
But it does not cause to lose log in case of using file type buffer.

hey ,i try to use ${$.log.tenantid} ,but it does not work , this is my configuration
<source>
  @type forward
  port 24224
  bind <IP_ADDRESS>
  <parse>
    @type json
    time_key time
    keep_time_key true
  </parse>
</source>

<filter *>
  @type record_transformer
  <record>
    yay test
  </record>
</filter>

<match *>
  @type elasticsearch
  host xx
  port 9200
  flush_interval 10s
  logstash_format true
  logstash_prefix ${$.yay}
  user xx
  password xx
</match>

Here's an example solution using target_index_key and the record_modifier plugin:
https://gist.github.com/dobesv/ffb27537fcc2df74ce8049fcfb937c4d


New version to Hackage for GHC 8.8 and beyond

Hi,
Sorry to bother, but is there any plans on releasing a new version to Hackage as the current highest version <IP_ADDRESS> doesn't work on ghc 8.8?

there is a candidate release here: https://hackage.haskell.org/package/haxl-<IP_ADDRESS>/candidate
can you try that out?

Hi, thanks! I did give it a quick spin and didn't find any problems 👍

Now published: https://hackage.haskell.org/package/haxl-<IP_ADDRESS>


Highlight Specific lines in Code

Hi
I am thinking about moving a WordPress blog to grav.
However, I unable to find a plugin to highlights the specific lines in my code snippet.

Prism supports highlighting specific lines of code if you add those plugins.
https://prismjs.com/
You could just add the relevant JS/CSS to your theme, then use standard <pre><code> HTML blocks and it should just-work.
The problem with using Markdown code-blocks is there's no standard way to get line numbers rendered appropriately for the JS you decide to use.


Use the 3.5.0-alpha ZooKeeper client

Fixes #359.
Normally I'd be wary of using a version marked "3.5.0-alpha". But given the pace of ZooKeeper releases and also judging from messages from the maintainers on the mailing list, I believe:

This version should be stable, especially the client bits.
It could literally be months/years until we see the next official "stable" release.

Given that we've already been bitten by #359 in production at Spotify, I'd rather just go ahead with this. Especially since all the tests pass and we're not upgrading any ZooKeeper servers, just the client.

Wow good find. I took a look at the at your fix and it seems sensible. I didn't look at zookeeper mailing lists and change log though. I'll defer to you on that. It is a bit scary it's an alpha though...

Just to summarize our in-person discussion for the record: yeah, it's "alpha", but all known issues are pretty well-documented in the ZooKeeper JIRA — and it will probably be several releases before we get through alpha, beta, RC, etc. Here's the proposed schedule:
http://markmail.org/message/ymxliy2rrwjc2pmo
None of the 3.5.0 issues affect our usage of it as a client library.

In that case :+1


New package: tacitdynamics.foldersync-desktop-production version 1.1.0

Pull request has been created with komac v2.2.0 :rocket:

Resolve #147613

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\FolderSync Desktop.exe returned exit code: -1073741515

(Automated response - build 876.)

[Policy] Zip Binary

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

@Exorcism0666 - Support for zipped binaries has now been added and is available in the pipelines. This will require you to update your submission to ManifestVersion: 1.9.0 and set ArchiveBinariesDependOnPath: true in the installer node. To keep things clean, this PR is being closed. Please submit a new PR for the latest version of this package. Thank you for your contributions!


BaseButton.pressed is both a signal and property

Godot version
4.0.dev (a5b2988)
System information
Windows 10
Issue description
You can't bind to BaseButton.pressed, becasue it is both a signal and a property.
Steps to reproduce
func _ready():
	var btn = Button.new()
	add_child(btn)
	btn.pressed.connect(self.on_button_pressed) # Cannot find property "connect" on base "bool".

func _on_btn_pressed():
	pass

I think that has already been reported in the tracker issue and there is a PR but no consensus on the new names.
https://github.com/godotengine/godot/pull/48193

Duplicate of #38937


Client crash

A lot of people, master client has crashed

It is needed to check id of game object in the message handling in the manager
Currently for some reason crash in Ghost
Maybe connected?

The bug with Ghost is reproduced in 0.2.0 -> the reason of the bug is here

"It is needed to check id of game object in the message handling in the manager" -> wrong
The bug was about MoveEffect

Still not fixed -> MoveEffect bug appeared after 0.2.0 release.

C:\Users\Kremius\Documents\Qt\KVEngineQt\knv-server-go>knv-server-go.exe -db-roo t=db-local 2016/02/28 02:52:14 client: registering client 2016/02/28 02:52:14 registry: registered new id 1 for player 'Admin' 2016/02/28 02:52:14 registry: creating new unit for client 1, login 'Admin' 2016/02/28 02:52:14 client[1]: registered, is it master? true 2016/02/28 02:52:14 client[1]: starting main loop 2016/02/28 02:52:38 client: registering client 2016/02/28 02:52:38 registry: reusing existing id 1 for player 'Admin' 2016/02/28 02:52:38 registry: no players left, cleaning up 2016/02/28 02:52:38 registry: registered new id 1 for player 'Admin' 2016/02/28 02:52:38 registry: creating new unit for client 1, login 'Admin' 2016/02/28 02:52:38 client[1]: inbox closed, closing connection 2016/02/28 02:52:38 client[1]: registered, is it master? true 2016/02/28 02:52:38 client[1]: starting main loop 2016/02/28 02:52:57 client: registering client 2016/02/28 02:52:57 registry: registered new id 2 for player 'Guest2673' 2016/02/28 02:52:57 registry: creating new unit for client 2, login 'Guest2673' 2016/02/28 02:52:57 client[2]: registered, is it master? false 2016/02/28 02:52:57 client[2]: starting main loop 2016/02/28 02:52:57 registry: requesting master 1 to send map 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:58 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:52:59 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:00 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:01 hash-check: master 1 did not sent his hash 2016/02/28 02:53:02 hash-check: master 1 did not sent his hash 2016/02/28 02:53:02 hash-check: master 1 did not sent his hash 2016/02/28 02:53:02 hash-check: master 1 did not sent his hash 2016/02/28 02:53:02 client[1]: reciever failed to read message: WSARecv tcp 127. 0.0.1:1111: An existing connection was forcibly closed by the remote host. 2016/02/28 02:53:02 hash-check: master 2 did not sent his hash 2016/02/28 02:53:02 hash-check: master 2 did not sent his hash 2016/02/28 02:53:02 hash-check: master 2 did not sent his hash 2016/02/28 02:53:02 hash-check: master 2 did not sent his hash 2016/02/28 02:53:02 hash-check: master 2 did not sent his hash 2016/02/28 02:53:04 client[2]: reciever failed to read message: WSARecv tcp 127. 0.0.1:1111: An existing connection was forcibly closed by the remote host. 2016/02/28 02:53:04 registry: no players left, cleaning up

Launch client with login == 'Admin', launch second client with login == 'Admin' (the first admin client will be disconnected). Then launch next client with login == 'Guest' -> tick_mismatch will popup in the client.
New client  10304
Map upload to  "http://localhost:8011/?id=4574640382776250421" , tick  427
Current game tick:  191
It took  0 ms to send the map
Map has been sended to  "http://localhost:8011/?id=4574640382776250421" , length:  4
Tick mismatch!  428   192
The server does not reset tick counts when admin relogin occurs. Probably it should be forbidden to relogin (the server should send something like 'ALREADY_CONNECTED' back on relogin request from the client).

Fixed reset on new game, please check it out.

Seems like fixed


Priority decreasing per transaction

Feature Request
Feature Request
As it is the coin of people, priorities should be done counting transactions of a wallet per day. if it is the first transaction (such send or much receive) of a wallet its prio 1, second is prio 2 etc. like a normal consumer has like 30 Transactions per day . So we could reset the priorisation iterator with the rise of the moon (nightfall). or maybe you can set it to whatever (24+) time you want... to seperate your transactions "in the middle".

Describe Preferred Solution

Implement a priority iterator
Implement priority mining
Miners must mine priority transactions. Maybe a stack system is required
Describe Alternatives

Related Code
Sadly im not deep enough in the DOGE programming. I can try to write some pseudocode:
Priority iterator:
For transactionPerWallet:
if time > timer + 24:00
priority=0
priority=+1
If priority = 1
set timer(hh:mm)
Mining Stack:
p1=getSenderWalletPriority
p2=getReceivingWalletPriority
transactionPriority= LowerPrio(p1,p2)
Insert e at end of transactions to do with the same priority
Miners can mine lower priority through an iterator too after mining some higher priorities. reset to 1 in 10 minutes or something?

Additional Context
It could prevent some issues of attacks (fan-in/fan-out).
Consumer will have fast mined transactions.
Please be gentle with me, I'm relatively new to coding ;)

Besides that you should never reuse an address, so there's no way to tell this without de-anonymizing, assume we would magically do this (won't) and let's do a thought experiment: what if I'm an employer and I am paying out salaries in DOGE? Would you be okay waiting 5 weeks for your money just because you're at the bottom of my list?

ok, isnt it possible to implement the counter directly into the wallet? It was in the back of my head, that the anonymity would suffer because of an additional counter token per transaction. Or are the wallets easy moddable?
the the transaction priority will always be the lower one. so if an employee made like 30 transactions on a day before payment, the transaction is prio 31. if he made no transaction on payment day, the transaction is prio 1.

ok, isnt it possible to implement the counter directly into the wallet?

Sure! But then you're de-anonymizing yourself. And how do miners know you're not lying?
I'm closing this here because this idea will not make it into Dogecoin Core.
By all means though, please continue exploring your idea and talk to people about it on reddit though! https://www.reddit.com/r/dogecoindev/

Thanks for the information.
I see, i have a lot to learn.


Add SAS token function for the service bus/event hub resource

Developers wishing to send messages to the service bus using the SAS token need to create the token themselves, as described here:
https://docs.microsoft.com/en-us/rest/api/eventhub/generate-sas-token
This is error prone and also convoluted to do in bicep because of the hashing step.
Ideally this should be available as a native property on the service bus resource. In the meantime, we should also be able to add support in bicep to have a list*() function that is able to create the SAS token for the service bus resource:
value: serviceBus.generateSAStoken()

This is error prone and also convoluted to do in bicep because of the hashing step.
Out of interest, do you have an example to share of how you currently do this in Bicep or ARM Templates?

This is error prone and also convoluted to do in bicep because of the hashing step.

Out of interest, do you have an example to share of how you currently do this in Bicep or ARM Templates?

I am currently doing this in an Ev2 shell extension bash script. Check out -
https://docs.microsoft.com/en-us/rest/api/eventhub/generate-sas-token#bash
I explored doing this in bicep inside an ARM 'Microsoft.Resources/deploymentScripts' resource but hit a snag at the openssl sha256 hashing step because I didn't find appropriate inbuilt functions for doing it inside the resource.

I explored doing this in bicep inside an ARM 'Microsoft.Resources/deploymentScripts' resource but hit a snag at the openssl sha256 hashing step because I didn't find appropriate inbuilt functions for doing it inside the resource.

Thanks for the context! I think the biggest challenge here is probably going to be idempotency - the same call to listXYZ() at a different time will result in a different SAS key (different start + end time), but this is something we'll certainly discuss.
Just to probe a little further - do you know what was missing with the deploymentScripts implementation? Was it the openssl binary that was missing?

Microsoft.Storage RP provides the listAccountSas function that hides the cryptographic logic (and idempotency?) and I'd envision this issue is about having a similar solution for ServiceBus (and optionally Event Hub).

I explored doing this in bicep inside an ARM 'Microsoft.Resources/deploymentScripts' resource but hit a snag at the openssl sha256 hashing step because I didn't find appropriate inbuilt functions for doing it inside the resource.

Thanks for the context! I think the biggest challenge here is probably going to be idempotency - the same call to listXYZ() at a different time will result in a different SAS key (different start + end time), but this is something we'll certainly discuss.
Just to probe a little further - do you know what was missing with the deploymentScripts implementation? Was it the openssl binary that was missing?

Yes.

Just to probe a little further - do you know what was missing with the deploymentScripts implementation? Was it the openssl binary that was missing?

Yes.

@jorgecotillo/@alex-frankel - is openssl something we've considered adding to the base deploymentScripts image (or had other asks for)? Feels like it would be pretty useful generally.

Right now it's a large work item to add customizations to the base image(s) that we are using. We have it on our backlog to make this easier, as we have had asks for a variety of binaries to be added to the images we use.
cc @marcre

Can this be fixed by engaging the RP for ServiceBus and EventHub?


Waiting, endpoint for service is not ready yet...

When running
gofabric8 deploy --package=system -n fabric8

I get the following output:
[..]
Processing resource kind: Deployment in namespace fabric8 name wit-db
Failed to create Deployment: deployments.extensions "wit-db" already exists
system........................................................................✘ Failed to create Deployment: deployments.extensions "wit-db" already exists
If this your first deployment then it may take a while to download the docker images, please be patient.
To track progress run the following command in a new terminal session:
watch kubectl get pods -n fabric8

Please make sure your github OAuth Application Client ID: *** points to the
Authorization callback URL: http://keycloak.fabric<IP_ADDRESS>.100.nip.io/auth/realms/fabric8/broker/github/endpoint

Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...

which keeps then reporting this line forever.
Versions
macOS Sierra

$ gofabric8 version
gofabric8, version 0.4.167 (branch: 'master', revision: 'd966ec40c')
  build date:       '20171013-16:27:35'
  go version:       '1.8.1'

$ minikube version
minikube version: v0.22.3

$ kubectl version
kubectl Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.0", GitCommit:"6e937839ac04a38cac63e6a7a306c5d035fe7b0a", GitTreeState:"clean", BuildDate:"2017-09-28T22:57:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}

$ docker --version
Docker version 17.09.0-ce, build afdb6d4

$ xhyve -version
1f1dbe

For some reason after many retries it worked.


change to using sac-home source for latest sac2c

oops, minor hotfix needed to get actions working again!

obvious change!


feat: support lora revisions and qkv_proj weights

This PR resolves two issues with lora. This PR adds support for @revisions on lora adapters. This will fetch or use lora adapters with a specific revision/branch/commit. Additionally this PR adds lora support for qkv_proj weights, which are used in the phi3 model. Lastly this PR has some other small refactors and improved error messages for lora

merging as these changes hotfix and issue with loading loras on phi3


DSA 2.2.7 Searching & Sorting Algorithms : Insertion Sort - Documentation #3293

Description 📜
Added explanation and implementation of insertion sort algorithm
Fixes #3293

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] DSA

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

/assign

@lvi131  Looks good to me.
Congrats on getting your PR merged !!

Thank You!


这个微信的协议也是WEB版的吗

Description
First of all, thanks for your attention to open an issue for this project.
Please notice that if you are requesting a feature, then you should give a brief description of your request.
If you are reporting a bug, please follow the template below.
A bug report without detailed information required will have a very low priority and even be ignored (closed directly)!
Specifications

Version of Electron (run $ electron --version): v0.0.0
OS: <OS>
Stack trace from the error message (if any)

<Stack trace here>

是
On Sun, Sep 17, 2017, 21:38 caiyusheng<EMAIL_ADDRESS>wrote:

Description
First of all, thanks for your attention to open an issue for this project.
Please notice that if you are requesting a feature, then you should
give a brief description of your request.
If you are reporting a bug, please follow the template below.
A bug report without detailed information required will have a very
low priority and even be ignored (closed directly)!
Specifications

Version of Electron (run $ electron --version): v0.0.0
OS:
Stack trace from the error message (if any)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/geeeeeeeeek/electronic-wechat/issues/561, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG7R--OMchuX6g5gyqXWY8JCTVKD1JN8ks5sjcl8gaJpZM4PaWzJ
.

现在WEB版的，封的好厉害，有啥招呢

怎么调用的 wechat api 接口没看懂


Fix NativeMemory static constructor crash

A fix to e61fbb05aaa36706f959f3984c3d63fdb5fa8746 , it somehow causes the static constructor to throw a NullReferenceException due to _strBufferForStringToCoTaskMemUTF8 field has not been initialized yet. Sorry for the inconvenience.

Accidentally closed


Fixes Pester Tests for SqlWatch

Type of Change

[X] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[X] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[X] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
It was rightly pointed out by @niphlod in #4407 that all Pester tests should clean up after themselves. Previously, the Pester tests for Install-DbaSqlWatch and Uninstall-DbaSqlWatch used the master database.
Approach
This PR modifies the Pester tests for these two functions to first create their own database, run the tests, and then remove the database when the tests are complete.

fab, thank you @koglerk !


Where is 4.0.0-beta.1?

I’m trying to install AlamofireImage swift3 branch via CocoaPods. It depends on Alamofire 4.0.0-beta.1, but I can’t find 4.0.0-beta.1 anywhere. Did you remove the tag?
My Podfile:
target ‘MyProject’ do
  use_frameworks!
  pod 'AlamofireImage', :git => 'https://github.com/Alamofire/AlamofireImage.git', :branch => 'swift3'
end

Error message from CocoaPods:
[!] Unable to satisfy the following requirements:

- `Alamofire (= 4.0.0-beta.1)` required by `AlamofireImage (3.0.0-beta.1)`

None of your spec sources contain a spec satisfying the dependency: `Alamofire (= 4.0.0-beta.1)`.

I have the same issue... Should we solve it by specifying the swift3 branch, instead of a tag?

Not really.
Use that:
target 'Bangumi M' do
    pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire.git', :branch => 'swift3'
    pod 'AlamofireImage', :git => 'https://github.com/Alamofire/AlamofireImage.git', :branch => 'swift3'
end

Then pod update or pod update Alamofire. It's works well.
Learn more. #153

Thanks @MainasuK. 🍻
We'll be cutting the beta.1 releases shortly once we get the AFError PR through. Until then, you can use @MainasuK's solution. You could also point to a specific commit hash on the swift3 branch rather than the swift3 branch itself in the Podfile to save yourself from a future breaking update.
Cheers. 🍻

After I updated 4.0.0-beta.1, Xcode 8 beta 6 output many build errors. Only me?

@MainasuK hehe yeah exactly what I wrote... specifying branch, not "~> 4.X.Y..."

It happened to me too - locally i was able to get it to build by removing the Manager.swift file.   Looking at previous commits it looks like this got added accidentally

On Aug 29, 2016, at 12:16 AM, Kazuaki Hara<EMAIL_ADDRESS>wrote:
After I updated 4.0.0-beta.1, Xcode 8 beta 6 output many build errors. Only me?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/Alamofire/Alamofire/issues/1434#issuecomment-243049538, or mute the thread https://github.com/notifications/unsubscribe-auth/ABf5_gbEEaRbLKzcgeCinCE7FHKKQSLLks5qkodcgaJpZM4Jup5a.

The Alamofire.Manager class has been renamed SessionManager @edwardvalentini

exactly.  so why was it added back into the repo in this commit e1cc66446c635cb593eaf4f7635d64242cf5a9e9 ?

@edwardvalentini good question! As @cnoon proposed, maybe we should specify a commit rather than branch. Try 3cc5b4e, it worked for me

Pointing Alamofire and AlamofireImage both to the swift3 won't work at the moment because AlamofireImage's podspec file requires Alamofire (= 4.0.0-beta.1). Are there plans to push one of these betas to Cocoapods trunk soon, or is there any other workaround? :)

@JaviSoto AFI hasn't been fully updated for 4.0.0-beta.2, so you'll need to lock your Podfile to the last compatible commit.

I couldn't find any commit that both:

Compiles under Swift 2
Targets a correct version of Alamofire to satisfy the Cocoapods dependency resolver.

:(

Anyone found any way to resolve or workaround this yet? Following errors received when targeting Alamofire and AlamofireImage swift3 branches.
[!] Unable to satisfy the following requirements:

Alamofire (from https://github.com/Alamofire/Alamofire.git`, branch swift3)required byPodfile`
Alamofire (= 4.0.0-beta.1) required by AlamofireImage (3.0.0-beta.1)

I moved over to Carthage as a work-around for the time being:
github "Alamofire/Alamofire" "swift3"
github "Alamofire/AlamofireImage" "swift3"

+1
I have the same issue here and I'm so lazy to move all my project to Carthage 😅 It would be great resolve that dependency. Thanks!

Anyone found a non carthage workaround? GM dropped today so if ever there is a time?...

@danielgalasko this works for me:
pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire.git', :commit => '3cc5b4e'

but hmm was a couple of days ago since I ran pod install

Perfect, that got it. Thanks @Sajjon
pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire', :commit => '3cc5b4e'
pod 'AlamofireImage', :git => 'https://github.com/Alamofire/AlamofireImage', :branch => 'swift3'

@danielgalasko I can't get Alamofire to compile using this commit...

@danielgalasko  commit 418b0fc is ok for me.

@bizhara For me, the issue is that I'm also using AlamofireImage at branch swift3 which requires 4.0.0-beta.1 Alamofire. And that will conflict with 418b0fc.

@KelvinJin How were you able to reference the pull request in your Podfile?
I've tried referencing the latest commit SHA:
platform :ios, '9.0'
use_frameworks!

target 'Nooklyn' do
    pod 'Alamofire',
        git: 'https://github.com/Alamofire/Alamofire.git'

    pod 'AlamofireImage',
        git: 'https://github.com/Alamofire/AlamofireImage.git',
        commit: '0469d9ebab544478ba6644a9881aba3833ce1a'

    pod 'Crashlytics'
    pod 'Fabric'
    pod 'FBSDKCoreKit'
    pod 'FBSDKLoginKit'
    pod 'Google/Analytics', '~> 1.0.0'
    pod 'MBProgressHUD', '~> 0.9.1'
end

but this is the error I get:
Analyzing dependencies
Pre-downloading: `Alamofire` from `https://github.com/Alamofire/Alamofire.git`
Pre-downloading: `AlamofireImage` from `https://github.com/Alamofire/AlamofireImage.git`, commit `0469d9ebab544478ba6644a9881aba3833ce1a`

[!] Error installing AlamofireImage
[!] /usr/local/bin/git checkout --quiet 0469d9ebab544478ba6644a9881aba3833ce1a

error: pathspec '0469d9ebab544478ba6644a9881aba3833ce1a' did not match any file(s) known to git.

@adimitri not sure you can use that syntax (maybe I am wrong...), but I use this syntax:
pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire', :commit => '3cc5b4e'

Until the cocoapods spec gets updated, I've managed to get pod install to work with:
pod 'Alamofire',
  :git => 'https://github.com/Alamofire/Alamofire',
  :commit => '76558cf44275cc6a6b9ebee9e3ac53b281d504b2'
pod 'AlamofireImage', :git => 'https://github.com/Alamofire/AlamofireImage.git'

I guess all is in flux these days with developers catching up with Swift 3 and the new Xcode release, so this will probably be outdated pretty quickly.

pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire', :commit => '4.0.0'
pod 'AlamofireImage', :git => 'https://github.com/Alamofire/AlamofireImage'
This worked for me.

This was likely just a vestige of issues of getting ready to launch the new versions.
This works:
pod 'Alamofire', '~> 4.0.0'
pod 'AlamofireImage', '~> 3.0.0'

Oh, i couldn't get that to work for me just now, but I will try it again.

I get this error when doing it that way
- `Alamofire (~> 4.0.0)` required by `Podfile`
None of your spec sources contain a spec satisfying the dependency: `Alamofire (~> 4.0.0)`.

You might need to run the following command in your terminal first:
$ pod repo update


Store summary cr objects

PR Type:
Refactoring

PR Description:
This PR focuses on refactoring the summary object labels to lowercase. This includes the workload name, kind, and container name. The changes are reflected in both the main code and the corresponding tests.

PR Main Files Walkthrough:
repositories/apiserver.go: The changes in this file involve converting the workload kind, name, and container name to lowercase using the strings.ToLower() function. This is done in the functions enrichSummaryManifestObjectLabels() and GetCVESummaryK8sResourceName().
repositories/apiserver_test.go: The changes in this file are related to the tests for the functions that were modified in the apiserver.go file. The expected results and input data for the tests have been updated to reflect the change to lowercase.

User Description:
move summary object name and kind label to lower case

should you rebase this PR? it looks like it contains 13 commits for just a few changes, which is weird...


Logo request

To claim a logo, please fill the template below. If you have a feature request or bug report, open a blank issue.

Eligibility check
For open source projects

[ x ] There are regular commits to my project
[ x ] My project has more than one contributor
[ ]  My project has over 100 GitHub stars
[ x ]  The git history of my project spans over 1 year

For NGOs

[ ] My organization is registered in at least one country
[ x ] My organization has been existing for over one year

Name of your project/organisation:
Web Essentials / Kalify Inc
Link to git repository and/or website:
https://webessentials.com.br/
https://github.com/Yagasaki7K/website-essentials
Brief description of your project:
Many people after formatting the computer forget about which software they have installed, which is the best browser to use, which text editor to encode that program or even which version of the operating system they find to install on another computer. Instead of jumping from site to site in search of this information, I developed essentials, a web tool that shows through list; Softwares that are useful for your computer and that no longer need to stay in your head, so you can worry about other things.
What logo do you want? Provide a link to it:
https://www.librelogos.org/logo/28

It's yours. Thanks!

@Yagasaki7K Here's the SVG: https://github.com/enjeck/libre-logos/blob/main/src/images/logos/svg/28-unicorn-in-circle.svg

Thank you!


Using custom SentryExceptionsFilter is missing features of BaseExceptionFilter

Picking up from our discussion from https://github.com/ericjeker/nestjs-sentry-example/issues/1#issuecomment-1737453215 I've now tried the new Setup with. Thanks for your work!
While I first thought it's great to switch to an ExceptionFilter, I didn't know only one single ExceptionFilter will always be called, I thought one could pass on to the next ExceptionFilter. So with the current implementation, the features of the default BaseExceptionFilter will be lost.
I've also read, an ExceptionFilter should not throw an error. It actually makes sense to me, while it's not explicitly stated in the docs, the example also does not throw as well as the BaseExceptionsFilter.

This could be a solution, which im happy to contribute, if #8 is resolved.
import { ArgumentsHost, Catch } from '@nestjs/common';
import { BaseExceptionFilter } from '@nestjs/core';
import * as Sentry from '@sentry/node';

/**
 * Catch all exceptions and forward to Sentry, this might not be what you want to do
 * as it's going to catch everything, including 404s, but it's a good starting point.
 *
 * You can further refine or filter out exceptions that you don't want to send to Sentry.
 */
@Catch()
export class SentryExceptionsFilter extends BaseExceptionFilter {
  catch(exception: unknown, host: ArgumentsHost): void {
    // capture the error, you can filter out some errors here
    // const httpStatus = exception instanceof HttpException ? exception.getStatus() : HttpStatus.INTERNAL_SERVER_ERROR;
    Sentry.captureException(exception);

    return super.catch(exception, host);
  }
}

Hi @KiwiKilian , I hope this is not too late. I answered in the other issue you opened. I'll check on that ExceptionFilter thing.
Just so that you know, I had a discussion with the Sentry Javascript team a while back and they told me they will change a lot in v8, which was released 3d ago. So this whole repository will probably change accordingly, at least in it's v3.
That's also one of the reason I didn't update it much since then.

No worries! Awesome to hear things might be getting easier with v8. Happy to give feedback on any new changes but I guess my concerns about the usage of ExceptionFilter still apply. Currently we use the solution commented above.

Hi @KiwiKilian,
I created a release/v2.0 branch that will hold the previous version of this example, and also fixed the license problem by adding a MIT-0 license. If you want to contribute you can do a PR on that branch with your proposal.
I reviewed the BaseExceptionFilter and it makes sense to do that change. I actually didn't know about it, I was following the catch all from their documentation.
When using the BaseExceptionFilter I guess it's a matter of ordering the global filters so that more specific filters are declared first as discussed in this answer you mentioned. Currently the filter is declared using APP_FILTER in SentryModule but we can certainly move it to the main.ts file so the declaration order is more explicit.
For example: app.useGlobalFilters(new SentryExceptionFilter(), new NotfoundFilter());
Let me know what you think and I'd be happy to check your PR. And I'll start working on the v3.0 using the new version of Sentry Javascript.

Thanks once again for your work @ericjeker!
Did you see there is now official docs on NestJS with Sentry? https://docs.sentry.io/platforms/javascript/guides/nestjs/
Did you already do a comparison, does it behave mostly the same as your setup?

Hi @KiwiKilian,
Yes, my v3 is based on that doc. I mention it in the README.
But basically this repository is not so useful anymore. I might add more complexities to the setup if necessary.
What do you think would be interesting to show here? Did you migrate to the SDK v8 already?

Ah sorry, didn't see you already did update to v8 using their docs...

But basically this repository is not so useful anymore.

It was great to have your setup, while there was no official approach. Now I would also say the repo is obsolete. Thanks again!


Fix the release download URL.

Never mind, RELEASE_TAG needs to be the full tag since we also release nightly builds.


Support UI count for link references?

Markdown-oxide can show counts for tag references, reference counts for [[ links would be very nice too, and be a good IDE equivalent of Obsidian's Strange New Worlds plugin.

Hey thanks for the suggestion!
I think this would be cool! I'd be happy to take PRs for this and suggest to implement it using inlay hints.

I'll leave this open for a couple weeks to see if anyone bites, but after that I'll need to close it to keep the repo focused on priorities.

So I guess you're not gonna implement it.


elContainer.style.flex - direction = 'column';

Description
using Brackets with the beautifier plugin wanted to set in Javascript the container display to flex with direction column.
elContainer.style.flex-direction = 'column';

transforms to:
elContainer.style.flex - direction = 'column';

Input
The code looked like this before beautification:
elContainer.style.flex-direction = 'column';

Expected Output
The code should have looked like this after beautification:
elContainer.style.flex-direction = 'column';

Actual Output
The  code actually looked like this after beautification:
elContainer.style.flex - direction = 'column';

Steps to Reproduce
beautify Javascript file
Environment
OS: Brackets 1.12 with Linux Mint 18.3

I think this is accurate for javascript.  Dashes are not allowed as part of identifier names.

@TudorHulban
Your code snippet is not a valid JavaScript syntax. You probably want to use
elContainer.style.flexDirection = 'column';

thank you!