Compilation errors when execute 'yo meanjs'

OS X Yosemite
node v4.1.2
npm  v2.14.4
When attempting to install meanjs with the yo generator the following errors were encountered:

node-pre-gyp install --fallback-to-build

CXX(target) Release/obj.target/debug/src/debug.o
In file included from ../src/debug.cc:2:
../node_modules/nan/nan.h:261:25: error: redefinition of '_NanEnsureLocal'
NAN_INLINE v8::Local _NanEnsureLocal(v8::Local val) {
^
../node_modules/nan/nan.h:256:25: note: previous definition is here
NAN_INLINE v8::Local _NanEnsureLocal(v8::Handle val) {
^
../node_modules/nan/nan.h:661:13: error: no member named 'smalloc' in namespace 'node'
, node::smalloc::FreeCallback callback
^
../node_modules/nan/nan.h:672:12: error: no matching function for call to 'New'
return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
^~~~~~~~~~~
/Users/jaford/.node-gyp/4.1.2/include/node/node_buffer.h:31:40: note: candidate function not viable: no known conversion from 'uint32_t' (aka 'unsigned int') to 'enum encoding' for 3rd argument
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate* isolate,
^
/Users/jaford/.node-gyp/4.1.2/include/node/node_buffer.h:43:40: note: candidate function not viable: 2nd argument ('const char ') would lose const qualifier
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate isolate,
^
/Users/jaford/.node-gyp/4.1.2/include/node/node_buffer.h:28:40: note: candidate function not viable: requires 2 arguments, but 3 were provided
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate* isolate, size_t length);
^
/Users/jaford/.node-gyp/4.1.2/include/node/node_buffer.h:36:40: note: candidate function not viable: requires 5 arguments, but 3 were provided
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate* isolate,
^
In file included from ../src/debug.cc:2:
../node_modules/nan/nan.h:676:12: error: no viable conversion from 'v8::MaybeLocalv8::Object' to 'v8::Localv8::Object'
return node::Buffer::New(v8::Isolate::GetCurrent(), size);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:210:7: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'v8::MaybeLocalv8::Object' to
'const v8::Localv8::Object &' for 1st argument
class Local {
^
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:210:7: note: candidate constructor (the implicit move constructor) not viable: no known conversion from 'v8::MaybeLocalv8::Object' to
'v8::Localv8::Object &&' for 1st argument
class Local {
^
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:214:13: note: candidate template ignored: could not match 'Local' against 'MaybeLocal'
V8_INLINE Local(Local that)
^
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:326:13: note: candidate template ignored: could not match 'S ' against 'v8::MaybeLocalv8::Object'
V8_INLINE Local(S that)
^
In file included from ../src/debug.cc:2:
../node_modules/nan/nan.h:683:26: error: no member named 'Use' in namespace 'node::Buffer'
return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
^
../src/debug.cc:194:25: warning: ISO C++11 does not allow conversion from string literal to 'char *' [-Wwritable-strings]
result_type = "";
^
In file included from ../src/debug.cc:2:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/jaford/.node-gyp/4.1.2/include/node/node.h:42:
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:221:5: error: assigning to 'v8::Primitive *volatile' from incompatible type 'v8::Value *'
TYPE_CHECK(T, S);
^~
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
(static_cast<T volatile*>(0)) = static_cast<S*>(0);
^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:414:12: note: in instantiation of function template specialization 'v8::Localv8::Primitive::Localv8::Value' requested here
return NanEscapeScope(NanNew(v8::Undefined(v8::Isolate::GetCurrent())));
^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                         ^

In file included from ../src/debug.cc:2:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/jaford/.node-gyp/4.1.2/include/node/node.h:42:
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:221:5: error: assigning to 'v8::Boolean volatile' from incompatible type 'v8::Value '
TYPE_CHECK(T, S);
^~~~~~~~~~~~~~~~
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
(static_cast<T volatile>(0)) = static_cast<S>(0);
^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:424:12: note: in instantiation of function template specialization 'v8::Localv8::Boolean::Localv8::Value' requested here
return NanEscapeScope(NanNew(v8::True(v8::Isolate::GetCurrent())));
^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                         ^

In file included from ../src/debug.cc:2:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/jaford/.node-gyp/4.1.2/include/node/node.h:42:
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:221:5: error: assigning to 'v8::Function volatile' from incompatible type 'v8::Value '
TYPE_CHECK(T, S);
^~~~~~~~~~~~~~~~
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
(static_cast<T volatile>(0)) = static_cast<S>(0);
^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:1514:12: note: in instantiation of function template specialization 'v8::Localv8::Function::Localv8::Value' requested here
return NanEscapeScope(NanNew(handle)->Get(kCallbackIndex)
^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                         ^

In file included from ../src/debug.cc:2:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/jaford/.node-gyp/4.1.2/include/node/node.h:42:
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:221:5: error: assigning to 'v8::Object volatile' from incompatible type 'v8::Value '
TYPE_CHECK(T, S);
^~~~~~~~~~~~~~~~
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
(static_cast<T volatile>(0)) = static_cast<S>(0);
^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:1632:12: note: in instantiation of function template specialization 'v8::Localv8::Object::Localv8::Value' requested here
return NanEscapeScope(handle->Get(NanNew(key)).Asv8::Object());
^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                         ^

In file included from ../src/debug.cc:2:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/jaford/.node-gyp/4.1.2/include/node/node.h:42:
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:221:5: error: assigning to 'v8::String volatile' from incompatible type 'v8::Value '
TYPE_CHECK(T, S);
^~~~~~~~~~~~~~~~
/Users/jaford/.node-gyp/4.1.2/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
(static_cast<T volatile>(0)) = static_cast<S>(0);
^ ~~~~~~~~~~~~~~~~~~
../src/debug.cc:168:18: note: in instantiation of function template specialization 'v8::Localv8::String::Localv8::Value' requested here
return NanEscapeScope(value->ToString());
^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                         ^

1 warning and 10 errors generated.
make: *** [Release/obj.target/debug/src/debug.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 14.4.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64/debug.node" "--module_name=debug" "--module_path=/Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64"
gyp ERR! cwd /Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug
gyp ERR! node -v v4.1.2
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64/debug.node --module_name=debug --module_path=/Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:818:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Darwin 14.4.0
node-pre-gyp ERR! command "/usr/local/bin/node" "/Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug
node-pre-gyp ERR! node -v v4.1.2
node-pre-gyp ERR! node-pre-gyp -v v0.6.12
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64/debug.node --module_name=debug --module_path=/Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64' (1)

<EMAIL_ADDRESS>install /Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler
node-pre-gyp install --fallback-to-build

CXX(target) Release/obj.target/profiler/src/profiler.o
CXX(target) Release/obj.target/profiler/src/cpu_profiler.o
CXX(target) Release/obj.target/profiler/src/cpu_profile.o
CXX(target) Release/obj.target/profiler/src/cpu_profile_node.o
CXX(target) Release/obj.target/profiler/src/heap_profiler.o
CXX(target) Release/obj.target/profiler/src/heap_snapshot.o
CXX(target) Release/obj.target/profiler/src/heap_output_stream.o
CXX(target) Release/obj.target/profiler/src/heap_graph_node.o
CXX(target) Release/obj.target/profiler/src/heap_graph_edge.o
SOLINK_MODULE(target) Release/profiler.node
COPY /Users/jaford/NorthwindNode/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/build/profiler/v5.2.12/node-v46-darwin-x64/profiler.node
TOUCH Release/obj.target/action_after_build.stamp
npm ERR! Darwin 14.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.1.2
npm ERR! npm  v2.14.4
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the v8-debug package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR!     npm owner ls v8-debug
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/jaford/NorthwindNode/npm-debug.log

Post this on the generator repo.

I too got the same error while doing with yeoman generator .....
it seems something like https://github.com/strongloop/strong-pm/issues/278#issuecomment-141845213 .
.....
time being workaround :
I then cloned the meanjs repo master branch and the same errors occured but was able to bypass the errors and the build successfully completed ....

@ilanbiala ,
Just my opinion : I cloned the https://github.com/meanjs/mean repo and checked out tag 0.4.1 and did npm install and the same error occurred .... so even without the generator that error occurred ... so it seems like it has nothing to do with the generator ...
Sorry, if it is wrong .... trying out meanjs only today ..

@ilanbiala @HarishAtGitHub Almost same error stack for me while trying to install the 0.4.1, 0.4.0 and 0.3.3 (stable) version of MEAN.js. As Harish said, it has nothing to do with the yo generator.  Linux 3.19.0-25-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR! Linux 3.19.0-25-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.   System Linux 3.19.0-25-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v14-linux-x64/debug.node" "--module_name=debug" "--module_path=/home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v14-linux-x64"
gyp ERR! cwd /home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v14-linux-x64/debug.node --module_name=debug --module_path=/home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v14-linux-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
node-pre-gyp ERR! stack     at maybeClose (child_process.js:1015:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
node-pre-gyp ERR! System Linux 3.19.0-25-generic
node-pre-gyp ERR! command "node" "/home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug
node-pre-gyp ERR! node -v v0.12.7
node-pre-gyp ERR! node-pre-gyp -v v0.6.12
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v14-linux-x64/debug.node --module_name=debug --module_path=/home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v14-linux-x64' (1)

<EMAIL_ADDRESS>install /home/rahil/jsr/mean-master/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler
node-pre-gyp install --fallback-to-build

I am using Ubuntu 14.04 and had installed all the dependencies required to MEAN.js

Are you behind a proxy at a company? Read the whole stack trace.

@ilanbiala yes I had read the stack trace and I  on my personal computer with windows environment. I normally install npm packages without any errors and have also tried different npm registries for example the Chinese one, but this proxy issue only occurred while installing any build of Mean.js

Sorry Ubuntu environment


Update Guacamole VMs to recent OS, add Win11

Resolves #3153
What is being addressed
The VM images used with Guacamole aren't very recent.
How is this addressed

Add Windows 11 as an option when creating a Guacamole user resource
Update some of the other Windows version options

/test-extended

/test-extended

/test-extended

/test-extended


⚠ Bofrost.at has degraded performance

In 8dfe04e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1405 ms

Resolved: Bofrost.at performance has improved in 6a953de.


Fix add wishart wishartfast prod

Looks like you beat me to it. Will this not break if Wishart or InverseWishart is on the right side instead of left? And can you add tests for InverseWishart too?

Ah hoped that you already have tests, yeah I will do.

Will this not break if Wishart or InverseWishart is on the right side instead of left?

not it does not I have test for this. In bayes base we check if there is a rule if we will swap the arguments.

Perfect. Poke me if you're done, I will review and merge.


Revert "Making Application Gateway rule priority a required field"

Reverts Azure/azure-rest-api-specs#19007
'Priority' field cannot be made required since Application Gateway V1 SKU and V2 SKU have the same api spec but V1 sku does not support this field and would break the V1 gateways. Only V2 sku needs to have the 'Priority' field as mandatory and there is no way to conditionally make the field optional/required based on the SKU. Hence reverting this change.

/azp run


ways to fix windsock iterative compile times

It currently takes 3 minutes to do an iterative build of our windsock benchmarks.
Needless to say this is really bad so I'm looking for ways to improve this.
Ideas:

Remove shotover dependency from benches, will have to duplicate the transform Configs into windsock but should be a significant win.

https://github.com/shotover/shotover-proxy/pull/1437 demonstrates that this will be a big win

Split setup and bencher logic into 2 seperate binaries. The setup can then be compiled in debug mode which should be a win. We can also avoid recompiling one binary if only the other has changed

The first point was mostly addressed by https://github.com/shotover/shotover-proxy/pull/1441
The second point relies on various unimplemented features in cargo.
So lets abandon this idea unless we find the need to further optimize windsock compile times in the future.


minDate : 30 days ago?

Hi,
I am trying to make a range from 30 days ago to today.
     flatpickr(".flatpickr", {
          minDate: (new Date()).setDate() - 30,
          maxDate: new Date(),
          enableTime: true,

          // create an extra input solely for display purposes
          altInput: true,
          altFormat: "F j, Y h:i K"
    });

but I didn't get the range as I expected, the 30 days ago range doesn't work.

Try new Date().fp_incr(-30)

Thanks. It works.

@chmln , I have an addition question, how can I make it (set view) show on the current day when user clicked onto the calendar. It is currently showing at the minDate.

onReady: function(dates, datestr, fp) {
    fp.jumpToDate(Date.now());
}

I am not sure if i have the right syntax, but it doesnt seem work
   input#start.flatpickr(type='text', name='sDate', placeholder='Start Date/ Time..')

    document.getElementById("start").flatpickr({
        onReady: function (dates, datestr, fp) {
            fp.jumpToDate(Date.now());
        }
    });

Here is the error:
   TypeError: Cannot read property 'removeChild' of null(…) "TypeError: Cannot read property 'removeChild' of null


'source_view_paths' vs 'view_paths'

The documentation says to use this in the sculpin_kernel.yml to change view directories.
sculpin_twig:
   view_paths: ['_views', '_layouts', ...]

But as far as I can tell this doesn't actually change any of the template directories. It was only after I dug through the configuration file for the twig extension that I found another node for source_view_paths. Using this in the config changes the template directories the way the documentation describes.
Am I missing something about view_paths or is the documentation wrong? I can't seem to find any place where view_paths is even passed on to the twig file loader the way source_view_paths is.

+1 Would be great to be able adjust view_paths.


Cannot run PROC IMPORT on remote Unix machine

Describe the bug
Running VS Code on a Mac, connecting to SAS via SSH on a remote Unix machine, I can get some code to run (so the connection works), but I get an error message if I try to run "PROC IMPORT":
NOTE: Writing HTML5 Body file: sashtml.htm
NOTE: This SAS session is using a registry in WORK.  All changes will be lost
at the end of this session.
ERROR: The connection to the X display server could not be made. Verify that
the X display name is correct, and that you have access authorization.
See the online Help for more information about connecting to an X
display server.
ERROR: Device does not support full-screen.
Steps to reproduce
Run the line
proc import datafile=x out=_csv dbms=csv replace; run;
Environment (please complete the following information):
Client OS: MacOS 12.7.2
Extension version: 1.5.0
SAS version: 9.4

It looks like the remote SAS session is trying to open an X window on the remote machine.  Did you include the -noterminal option on the command you used to launch SAS?


Replicating Grave's Generative Wikipedia Model

I'm attempting to replicate the results in Generating Sequences With Recurrent Neural Networks, by Alex Graves for a generative model on Wikipedia. The generative example here  is built by eating a sequence of n characters and then attempting to predict the n+1th character.
However, the paper by Graves (as I understand, place correct me if wrong) eats characters (with a zero vector as the first input) and outputs the same characters being eaten. ie: "*Hello World" would be the input characters and "Hello World" would be the outputs, where "*" would indicate the zero vector. Another note in the paper is that, to learn the long term structure, they eat 10k characters (100 byte sequences with internal state only reset every 100 sequences, and sequences are kept in order)  but only push the gradient back to 100  steps.
So I started to set up a similar model as
model = Sequential()
model.add(LSTM(2048, return_sequences=True, input_shape=(max_len, tokens), truncate_gradient=100))
model.add(Dropout(0.5))
model.add(LSTM(2048, return_sequences=True, truncate_gradient=100))
model.add(Dropout(0.5))
model.add(LSTM(2048, return_sequences=False, truncate_gradient=100))
model.add(Dropout(0.5))
model.add(Dense(tokens))
model.add(Activation('softmax'))

model.compile(loss='categorical_crossentropy', optimizer=Adam(clipnorm=1))

However I'm not sure this is correct, and I'm not sure what shape the target variable y should be. I think the training matrix would be shaped as X = np.zeros((train_sequences, max_len+1, tokens), dtype=np.bool), where the +1 would be for the zero vector start.
I have all characters read into a string and my initialization looks like
row= 0
for i in range(0, len(train_bytes), max_len):
    for t, byte in enumerate(train_bytes[i:i+max_len]):
        X[row, t+1, ord(byte)] = 1
    row += 1

Can anyone help me finish this / set me in the right direction? I'm not seeing how to indicate to keras that if I made y 3 dimensional how the targets line up with the inputs. ie: the fist "l" should be predicted after receiving "*He" and the gradient pushed back from there, and then the second "l" after "*Hel", and so on.
I saw issue #395 , but it is set up somewhat different - and the issue quite cluttered at this point.

However I'm not sure this is correct,

As a model that maps a sequence of n characters to the (n+1)th character, it looks correct. However! Do not specify input_shape=(max_len, tokens) in the second layer. Only do that in the first layer.

I'm not sure what shape the target variable y should be.

It should be the (n+1)th character, encoded as a binary vector of k dimensions (k = size of your vocabulary). Take a look at the LSTM text generation example we have.

Do not specify input_shape=(max_len, tokens) in the second layer. Only do that in the first layer.

Oops! Copy-pasta error.

As a model that maps a sequence of n characters to the (n+1)th character, it looks correct.

Right, I understand that - but I want the training procedure to train on every character, since my sequence is now 100k long. As I understand the Graves paper, if I wanted to train on say "Hello World!" and only do BPTT for 2 steps, I want to train on the sequences:

Input "*" and output "H"
Input "*H" and output "e"
Input "*He" and output "l"
Input "*Hel" and output "l"
Input "*Hell" and output "o"
Input "*Hello" and output " "
...
Input "*Hello Worl" and output "d"
Input "*Hello World" and output "!"

I could produce several input output pairs this way, and use the same style code in the LSTM example already in Keras, but this would blow up the number of training points. This is because its learning a sequence mapped to a single output. What I want to replicate in the paper, as I understand it, is to train a sequence mapped to the same sequence (but lagging a character behind). The discussion in #395 is similar, but it appears they are trying to map a sequence to a dense representation, and then decode the dense representation back to a new sequence.
Am I making sense?

Ok, I've been playing around and I think I've got a toy example of what I want working.
txt = "Hello World!"

model = Sequential()
model.add(LSTM(64, return_sequences=True, input_shape=(len(txt)+1, tokens), truncate_gradient=-1))
model.add(TimeDistributedDense(tokens))
model.add(Activation('softmax'))

model.compile(loss='categorical_crossentropy', optimizer=Adam(clipnorm=1))

X = np.zeros((1, len(txt)+1, tokens), dtype=np.bool)
y = np.zeros((1, len(txt), tokens), dtype=np.bool)

for t, byte in enumerate(txt):
    X[0, t+1, ord(byte)] = 1
    y[0, t, ord(byte)] = 1

model.fit(X, y, batch_size=1, nb_epoch=3000)

Am i correct that, in this code, if I set truncate_gradient=2, that the gradient will be truncated with respect to its occurrence in the sequence?
Ie: the "o" character will be truncated to the two "l"s, the " " would be truncated to "lo".
If I sample from this
for i in range(len(txt)):
    print(model.predict(X[:, 0:i+1, :], verbose=0).shape)
    print(chr(sample(model.predict(X[:, 0:i+1, :], verbose=0)[0][i], 0.7)))

I get the expect output, and predict returns a prediction for all the previous steps as well. Is there a way to predict on the next unseen token once I've trained a model?

I found it a lot better (and faster) to let the last layer return_sequences = True and set the input sequence as data[:,:-1,:] and the output data as data[:,1:,:] and not truncate the gradient at all.

@lemuriandezapada could you provide a code example? I'm not sure I understand where data is coming from. Are you saying you do the 100 sequences with 100 characters each, instead of doing a 10k sequence with truncation?
Also, do you mean faster in computation or convergence (or both)? Thanks for helping!

My code is ugly as fuck, and cleaning it to post it would take too long :))
What I do is I chop the one hot sequences in say 100 characters each randomly from the text corpus.
data will be of size (train_sequences, seq_len, vocab_size) and you do 1hot encoding on the vocab size. So you can just set return_sequences=True in your model, and then call model.fit(data[:,:-1,:],data[:,1:,:])
Basically setting as input all the first n-1 [0:n-1] chars and target output the last n-1[1:last] chars. Instead of the usual way of using [0:n-1] input and [n] output.
It's faster on convergence (you start seeing results after fewer iterations), because it propagates back errors from more than 1 char. The other way still computes the reservoirs at every step and propagates the error through it from the last step but ignores all the other potential chars. Computing time per iteration itself is pretty much the same.

@lemuriandezapada sorry for the late reply and thank you for contributing, but I'm not sure I understand. If you’re training on only 100 character sequences, and your not somehow copying hidden state to the next "sequence", how would the model get a chance to learn dependencies that are longer (1000 time-steps back or more).

Basically setting as input all the first n-1 [0:n-1] chars and target output the last n-1[1:last] chars. Instead of the usual way of using [0:n-1] input and [n] output.

This is part of what was specified in the graves paper that I was trying to replicate, as the keras example only does from one output. I think I have that part working now (as in my toy example above)

It wouldn't. :)
For 1000+ timesteps you'd chop them up in 1000+ character sequences.
Keras's lack of RTRL-like implementation makes having to chop your sequences in any way mandatory and there's no workaround that I can think of. You'd need to try to propagate your errors all the way far into the past somehow.
Or you can try implementing something fancy like this:
http://arxiv.org/pdf/1402.3511v1.pdf
Though I've no idea how to do those timestep skips in keras/theano.

@lemuriandezapada Ah, the main goal here is to replicate Grave's results with learning dependencies over very long ranges. From what I can find, his approach of doing sequential batches and copying hidden state from one to the next is the standard approach, and should be much better from a performance / GPU memory use perspective. I don't think the CW-RNN would help me train on longer sequences since the GPU memory is my bottle neck here.
Thank you for your help though!


Update for tiled v0.1.0a79

All the failures are transient failures with the odd-ball legacy backends.
FAILED databroker/assets/tests/test_asset.py::test_single_datum_register[column_hdf5-dict] - TimeoutError: cursor call timed out
FAILED databroker/assets/tests/test_write.py::test_file_exist_fail[sqlite] - TimeoutError: cursor call timed out
FAILED databroker/assets/tests/test_write.py::test_file_exist_fail[column_hdf5] - TimeoutError: cursor call timed out


BUG: Overwriting binding of key tab

Hi,
I'm using version beta.4 with react version 17.0.2.
I'm trying to override the tab function as shown in the Quill docs, and as mentioned in lots of threads:
keyboard: {        bindings: {        // This will overwrite the default binding also named 'tab'            tab: {                key: 9,                handler: function() {                     // Handle tab                }            },       }    }
What happens is that if I press anything other than the key tab, the editor will break and disappear.
And then if I go around my app, it gives me this error:
TypeError: Cannot read properties of undefined (reading 'delta')
ReactQuill.componentDidUpdate
src/src/index.tsx:277
274 | // The component has been regenerated, so it must be re-instantiated, and
275 | // its content must be restored to the previous values from the snapshot.
276 | if (this.state.generation !== prevState.generation) {

277 |   const {delta, selection} = this.regenerationSnapshot!;
| ^  278 |   delete this.regenerationSnapshot;
279 |   this.instantiateEditor();
280 |   const editor = this.editor!;

I've tried to debug, but couldn't find any answer as to why it happens.
Thanks

It seems the problem comes from the setState() inside the onChange function of ReactQuill component
If I comment the setState, the editor works without any errors

I've got the exact same error (TypeError: Cannot read properties of undefined (reading 'delta')), but not because of the same reason - I'm using the quill-mention plugin and when I change it's config value (from the modules prop), I get that error

Update:
Before I said that the editor without the setState worked seamlessly, but that's not true. It still is disappearing if I try to overwrite the "tab" function.

Any help here? I'm having the same issue and I don't know how to solve it :/

Same error here, anyone able to solve it?

I was making the mistake to define the binding like:
  tab: {
    key: 9,
    handler: function () {
      return true;
    },
  },
};```

Inside the react-component but if you declare it outside as a static const, it is going ok!


rocAL - Tensor metanodes + readers + iterator changes

Changed bboxes to absolute format and float dtype
Changed all meta nodes to use absolute bboxes - added meta_node_resize back
Added update_meta_data API back to rescale bboxes after decoding
Added python unit test changes for testing unit test output with readers
Added C++ unittests for testing augmentation and reader outputs with golden outputs
Tested and benchmarked tensor classification training with this branch - classification trainings can be run once this PR is merged
Note: The previous PRs (https://github.com/LakshmiKumar23/MIVisionX/pull/33 , https://github.com/LakshmiKumar23/MIVisionX/pull/34 ) has to be merged before this PR for building this PR and checking the C++ and python unit tests in this PR. The number of file changes will be reduced to 45 once the two PRs are merged

@fiona-gladwin can you resolve merge conflicts?

@LakshmiKumar23 The merge conflicts are resolved. Until the python PR (#34) is merged, file changes from that PR will be shown in this PR as well

@LakshmiKumar23 The golden outputs for the tensor branch is different from ToT so please use this branch for testing python unit tests. I have modified the python unit tests to be similar to the C++ unit tests so -b gpu is not needed for testing augmentation outputs in GPU backend. By default, the python unit tests runs for both backends and both color formats.

@SundarRajan28 can you fix merge conflicts?

@SundarRajan28: Can you please fix those merge conflics in this pr

@LakshmiKumar23 @rrawther I have fixed the merge conflicts with this PR

@rrawther @LakshmiKumar23 I have resolved the review comments for this PR. Please check.


Google Analytics added

Reference Issues/PRs

Google Analytics added

What does this implement/fix? Explain your changes.
Any other comments?

According to messed up happened because of different accounts, conflicts, and mistakenly combination of google tag manager and google analytics tags, this PR is closed and another one is created.


add: velodrome, aerodrome contracts

Adding Velodrome and Aerodrome contracts
any_evm was used for contracts deployed to BOB chain. Please lmk if I should remove those contracts

Thanks Zoomer! Looks good -- will try to merge with the next batch later tonight. Will let you know if there are any issues.

/validate 9bc9ba017f2784249a9d0f6ef7dfa3fc5e1fdb5c

/validate 40b0439d11f3cc73a62267d03731b5d486e157f5

Fixed some improper formatting, CI should pass now

Thank you! I ran the CI late last night. Let me check the validations now.
Note: we already have a bunch of Velo & Aero contracts attributed via your deployers. So enumerating each contract isn't strictly necessary unless the same deployer may have been used by more than one project.

@ethzoomer alright, validations look good for the most part. There's a bug that causes any PR before a certain point to grab 5 addresses that are not associated with your project and reject them. We can ignore those.
Here are the ones I found for you...
Couldn't locate a contract on Base or OP:

0x8d9c67488c154286b9d4ccac6c4cbf30589107a7
0x3a63171dd9bebf4d07bc782fecc7eb0b890c2a45
0x31832f2a97fd20664d76cc421207669b55ce4bc0
0x0f3887909c548c41eb8a6667a4b23fc6683ef8ba

Contract is on OP, but missed by validator:

0x8eb6838b4e998da08aab851f3d42076f21530389
0xc3f14f34ea43943e6fd677a2bdcea65882e67783
0x593d092bb28ccefe33bfdd3d9457e77bd3084271

Will merge for now. At some point we might do a refactor so that any contract on any chain linked to one of the deployers is present, but for now it's fine to include these for comprehensiveness.


SequenceInstructionTable and SequenceExecutionConfig

Part of the decode circuit:

https://www.notion.so/scrollzkp/DecoderConfig-address-table-6fc3fa61f51541acb3cc661fdc038bdc?pvs=4
The "output region" part (sequence instruction exectuions)

It also make use of AddressTableRow struct and add SequenceExec struct in witgen.

Unit test passed. Ready to be merged


Cherry-pick #5584 into release-1.10 [DO NOT SQUASH]

#5584 was included in a hotfix for 1.9 but we never cherry-picked into master so it didn't make its way into 1.10. Hopefully it can be included in the next hotfix for 1.10
Please do not squash this commit

We don't have a hotfix planned for 1.10

We don't have a hotfix planned for 1.10

I am aware. But it will happen sooner or later :) Since this commit was in a hotfix for 1.9, it should at least be included in the next hotfix for 1.10 IMHO


chore(main): release 0.35.2

:robot: I have created a release beep boop
0.35.2 (2024-07-24)
Bug Fixes

align helm chart service (#619) (259e207), closes #618
extra file (#623) (a8dedd0)
force version update on helm release (#622) (9bf36d8)
make service names consistent (#626) (7a50bea)
move rendered file (#624) (b1bc1a2)
show diff when template diverges (#621) (65637fc)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

0.35.2
:sunflower:


Fix arrayFill function

There is currently a method called arrayFill that lives in /lib/arrayFill.js.
It is incomplete and needs to be fixed!
Acceptance Criteria:

Running yarn test arrayFill results in tests passing.
You have written a skeleton method for someone else to work on.
You have written tests surrounding your skeleton method.
Running yarn lint does not print any errors to the console!
Optional: write one or two more tests surrounding the method you are solving to account for potential edge cases.

Please include the skeleton of a new method + an accompanying test for someone else to work on at the time of creating a pull request! A pull request will most likely be denied if it does not contain a skeleton method for someone else to work on! For more information, please read the Contributing Guide.
Thank you so much for your contribution!

I'll do this issue :)

Awesome @Galleria ! It is yours. I will apply the 'in progress' label to it- that buys you 24 hours! If you feel like you need more time, feel free to reach out and I will happily oblige. Please make sure to include a "Skeleton Method" when you make a pull request to resolve this issue. Thanks and good luck!!

Thanks!


v1.5.4 Dex Server Pod has no liveness or readiness checks

Describe the bug
i ran into this bug
https://github.com/argoproj/argo-cd/issues/9091
after hibernating a cluster and turning it back on.
time="2022-07-22T09:08:02Z" level=info msg="config refresh tokens rotation enabled: true"
failed to initialize server: server: Failed to open connector openshift: failed to open connector: failed to create connector openshift: failed to query OpenShift endpoint Get "https://kubernetes.default.svc/.well-known/oauth-authorization-server": dial tcp: i/o timeout

Restarting the dex pod works ok - but it should have a liveness/readiness check on the Deployment (it does not).
kind: Deployment
apiVersion: apps/v1
metadata:
  annotations:
    deployment.kubernetes.io/revision: '2'
  resourceVersion: '418643'
  name: argocd-dex-server
  uid: 18354e9c-c864-460d-b8cb-59fb2a3f0cbc
  creationTimestamp: '2022-07-22T08:28:56Z'
  generation: 2
  namespace: ateam-ci-cd
  ownerReferences:
    - apiVersion: argoproj.io/v1alpha1
      kind: ArgoCD
      name: argocd
      uid: b8fd55d8-de1f-4395-8cf3-ff59b208c381
      controller: true
      blockOwnerDeletion: true
  labels:
    app.kubernetes.io/component: dex-server
    app.kubernetes.io/managed-by: argocd
    app.kubernetes.io/name: argocd-dex-server
    app.kubernetes.io/part-of: argocd
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: argocd-dex-server
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/name: argocd-dex-server
        dex.config.changed: 07222022-082822-UTC
    spec:
      restartPolicy: Always
      initContainers:
        - name: copyutil
          image: 'quay.io/argoproj/argocd:v2.3.6'
          command:
            - cp
            - '-n'
            - /usr/local/bin/argocd
            - /shared/argocd-dex
          resources: {}
          volumeMounts:
            - name: static-files
              mountPath: /shared
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: Always
      serviceAccountName: argocd-argocd-dex-server
      schedulerName: default-scheduler
      terminationGracePeriodSeconds: 30
      securityContext: {}
      containers:
        - resources: {}
          terminationMessagePath: /dev/termination-log
          name: dex
          command:
            - /shared/argocd-dex
            - rundex
          ports:
            - name: http
              containerPort: 5556
              protocol: TCP
            - name: grpc
              containerPort: 5557
              protocol: TCP
          imagePullPolicy: Always
          volumeMounts:
            - name: static-files
              mountPath: /shared
          terminationMessagePolicy: File
          image: >-
            registry.redhat.io/openshift-gitops-1/dex-rhel8@sha256:20cb34d1ba5b7cfb868546e55844cddcca19c7756426529d9102d7852f8d127b
      serviceAccount: argocd-argocd-dex-server
      volumes:
        - name: static-files
          emptyDir: {}
      dnsPolicy: ClusterFirst
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 25%
      maxSurge: 25%
  revisionHistoryLimit: 10
  progressDeadlineSeconds: 600

To Reproduce
Steps to reproduce the behavior:
Stop OpenShift Cluster. Leave it down. Restart it.
Cannot login to ArgoCD using dex.
Expected behavior
Can login to argocd.

This has already been fixed with https://github.com/argoproj-labs/argocd-operator/pull/615 and is pending release w/ GitOps Operator v1.6.0

closing as dupe - looks very similar to this: https://github.com/redhat-developer/gitops-operator/issues/263

thanks @jannfis  !!


Document hb-subset

https://github.com/harfbuzz/harfbuzz/blob/main/docs/repacker.md is lovely, write up how the rest of subsetting works with code refs

serializer design: https://goo.gl/bHvnTn
subsetter design: https://goo.gl/Qy3Eqc

Do you need/want to add anything to that or can I close this?

I tend to think it still makes sense to describe how it works akin to how repacker.md does?

I feel like that can be a task for Garret now.

🚌=>@garretrieger

I just added a short writeup of how the serializer works in hb here: https://github.com/harfbuzz/harfbuzz/blob/main/docs/serializer.md

I think we can call this complete, thank you. I'll add links to the root readme.


Fix typo in code, create

TextSizes does not exist. TextSize is right.

@dem108,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/create/libraries/NET.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thanks!

@dem108,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/create/libraries/NET.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


How to embed dataset's field in Body?

Hi,
Could someone please give an example for how to embed dataset's field in Body of this Web activity?
Cheers.

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

ID: 34b3d465-6a2b-88ad-6e80-4fb784cd489e
Version Independent ID: 51b70888-d089-7352-4abd-7d587726700a
Content: Web Activity in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/control-flow-web-activity.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

@thucnguyen77 Thank you for reaching out. At this time we are reviewing the ask and will provide an update as appropriate.

@thucnguyen77 Thank you for reaching out here. At this time your query seems to be a product question and not directly related to this document content. These kind of queries are best suited for community forums. We request you to please post your question on "MSDN - Azure Data Factory" and other forums (Stackoverflow - Azure Data Factory). We have our engineers and others who are monitoring them and will be happy to assist.
If you have a document which you are following and if you think it needs an update, please let us know about that here.
Thank you.

Please do share the forum link here once query is posted.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.
Thank you.


[Chore] Add translation in the farmer dashboard

Farmer Languages
We support three kind of language in the farmer dashboard.

Tagalog
English
Cebuano

However, the language preference is still not persistent. The preference vanish on refresh or logout

Error: Process completed with exit code 1 in line 46 can be fixed by running this on the command prompt:
npm install --legacy-peer-deps --save @ngx-translate/core npm install --legacy-peer-deps --save @ngx-translate/http-loader
This is an angular translation support that we have utilized to develop language preference.

In this commit, this issue has been fixed by downgrading the versions of @ngx-translate/core and @ngx-translate/http-loader to versions that are compatible with our current Angular version (12.x).


Apollo Kotlin users: we want to interview you!

Description
Hi all 👋🏻  Jeff Auriemma here, I'm the Engineering Manager serving the client library maintainers here at @apollographql.  If you use Apollo Kotlin, I want to talk to you 👀  We want to build the absolute best open-source GraphQL client SDK possible, and no one knows what you need better than, well, you!  If you can spare 45-60 minutes to help make our open-source software better, we'd be so grateful.  Feel free to email me at jeff.auriemma [at] apollographql [dot] com or find me on Discord @jeff.auriemma and we'll figure out a date and time.  Thanks so much for supporting our open-source software!

Thanks so much everyone! To those of you who reached out, we appreciate having had the opportunity to speak with you. Your feedback has been truly helpful and will make a difference. We'll also be trying to get more feedback in the future through other means like surveys as well 🙏🏻


Add constructor to VaultTemplate that takes a VaultEndpoint, a ClientAuthentication and RestTemplate

This refers to #572. This is far from being finished (testing, documentation etc), also I'm not sure if it is a good idea at all to add this constructor. I thought it would be helpful to have some code to talk about

@L7R7 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@L7R7 Thank you for signing the Contributor License Agreement!


Improve the developer experience

Closes #255

More robust way of defining the initial dependencies which will setup the package environment. (plain inv <cmd> working in all the packages)
Improved Invoke commands according to Notion.
Fixes the meta package way of importing and using devutils.

Hey @OvidiuCode, not sure if you missed the:

Note: auto-generated by _gen_workflows.py

or not (hopefully you didn't have to manually update all the test workflows)
If you did use it, the _gen_workflows.py is not committed... otherwise, please do the changes you need on _gen_workflows.py and then make sure you run it to update things in the test workflow files.

Thanks @fabioz. I missed that, that is why some were failing.

I was just seeing the action_server/docs/api and I was thinking that for the action server the API isn't really helpful (as it's not a library and it's not meant to be interacted through its API, unlike the other projects in this repo).
I think we should just remove those api docs instead of updating them in this PR...
What do you think @cmin764?

Yes, no need to generate and store API docs for the Action Server (as it's not a library on its own), and we can skip it from docs generation during the docs command if we detect that there's no docs/api folder present already, this way fixing the check-all command which will also run the docs in CI to ensure that there's nothing newly generated.


Update to support Revio

update pbmm2
update regex movie names

@juniper-lake Does this look reasonable?
@amwenger Am I missing anything?


Use node LTS and Update nextjs

What changed? Why?
Notes to reviewers
How has it been tested?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Extensibility

Wow this parser looks fantastic. I'm super excited to see that its being tested against test262 unlike many of the other options.
I'm working on a js engine written in js (https://github.com/devsnek/engine262) and currently using acorn. I'd love to switch to cherow but I'm concerned about being able to extend the parser. This is very important to me because the engine is used to prototype and test new features for js. In acorn you can just subclass and override, but it looks like everything here is direct calls to other functions.
Are there any plans to allow extending and modifying the parser?

@devsnek @aladdin-add @fkleuver
I think we come to a conclusion that Cherow will never be so extandable as you hoped for, but take a look at the Buntis TS parser I'm working on.
This will accept both JS and TS, and also support plug-ins in the same way as Acorn.


doc/statuscodes.md: Remove HTTP status codes

The HTTP status codes are more for REST; they don't work with gRPC. We
shouldn't be encouraging them and they are confusing when you compare
them to doc/http-grpc-status-mapping.md .

As brought to my attention by grpc/grpc-java#5916 (which was re-filed as #19094). This partially reverts #18003, but I don't think it impacts the original goal of that PR.
CC @jadekler, @sheenaqotj

CC @legendtang


JS: Use direct function invocation when possible for calls with 4 or 5 args

Ultimate Problem
A library I'm working with (react-dart) involves frequent calls to Dart functions from JS code via allowInteropCaptureThis, and many of them take 4 arguments (for a total arity of 5 when you count the JS this).
Since these calls take too many arguments, they fall back to the generic function calling, which makes use of the JS Function.prototype.apply, which isn't as fast.
Changes

Directly invoke functions, when possible, for arities up to 5, as opposed to up to 3.

I think this threshold is more reasonable, but please say otherwise if it's not.

Add test for Function.apply called with 0-5 arguments.

Is signed it! (My company, Workiva, signed it!)

LGTM


Splash position fix

Describe your PR, what does it fix/add?
This fixes the offcenter splash rendering
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Fixes https://github.com/hyprwm/Hyprland/issues/679
On screens with a higher than texture ratio, the splash will be offscreen (below),
this is not introduced by this pr.
The splash has to be moved by the same amount as the origin.y value
in createBGTextureForMonitor in those cases.
Is it ready for merging, or does it need work?
I think yes, it doesn't fix the problem totally, but it makes things better.

I'll wait for when you fix that other issue. Let's just make one PR to end those alignment issues once and for all

@vaxerski  this is done!
I tested it like crazy with different monitor settings.
I eat my shoe if this is not working!

thanks as usual


[WIP] Update buttons locked and with spinner class

Added button locks and spinner class for the update view.

Will continue on this later. Needs some UI adjustments

Updating DXCCs works:

But updating distances results in nothing being shown to the user here. Window / content stays as it is (buttons were pressed):

https://github.com/user-attachments/assets/6a2894f9-3d00-4153-b18c-664b6f66373e


Usage with Next.js gives failed to load resource

Bug Description
Trying to implement @livechat/widget-react with Next.js but it gives https://cdn.livechatinc.com/tracking.js net::ERR_BLOCKED_BY_CLIENT and is not working
To Reproduce
Implementing the code for Livechat as follows:
<LiveChatWidget
license="MY_LICENSE_KEY"
group="0"
visibility={'maximized'}
/>
Expected behaviour
The Livechat widget should be shown on the page maximized
Screenshots

Desktop (please complete the following information):

OS: MacOS Catalina v10.15.7
Browser: Chrome Version 101.0.4951.64 (Official Build) (x86_64)

Additional context
"react": "^17.0.2"
"next": "12.0.1"
"@livechat/widget-react": "^1.1.0"

Hello @convert-zia 👋
Thanks for the report. Sad to hear you have encountered an issue with the library.
The error you have encountered while trying to load our https://cdn.livechatinc.com/tracking.js is most probably related to the AdBlock-like browser extension. Error message directly points to the reason for request failure: the client (your web browser) has blocked an outgoing request to load our code from the CDN.
Please try again without any of such extensions enabled and let us know if the error is still present.


Add additional fields to logger that will be present on all new entries

We have a bunch of things we want to go into every log line: App name, region app is running in, server name, etc. The existing solution is to Create an Entry and distribute that throughout your code in place of a logger. Howere, that requires all methods than previously took a Logger to take an Entry, which is non-intuitive (at least to me)

👍  I've nosing around a bit to see if something like this already existed. Thanks for submitting it!

Those failing checks don't appear to be related to my change, some problem with the airbrake dependency maybe?


Node-pressure Eviction

According to the documents :

The kubelet uses the following parameters to determine the pod eviction order:

Whether the pod's resource usage exceeds requests
Pod Priority
The pod's resource usage relative to requests

I was wondering will pods like kube-apiserver and kube-controller-manager (Burstable qos but system-node-critical priority which has the highest priority) still respect rules above ?  If so,  does it means kube-apiserver will be evicted instead of another pod has 0 priority but qos is Guaranteed?

related page: https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#pod-selection-for-kubelet-eviction

/language en

related page: https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#pod-selection-for-kubelet-eviction

@tamilselvan1102  This is where my confusion comes from.
When kubelet decides to evict pods, according to this document, kube-apiserver are more likely to be evicted than a random pod(let say it's a pod runs unimportant programs) has a Guaranteed qos. I think it's counterintuitive.
So the answer is "yes" ?

I think Control-Plane components are treated with some special way than user created pods

The problem I'm facing is that I'm using operators to deploy some important components like calico(cni), but those calico pods has BestEffort qos and system-cluster-critical priority.
So according to the rules mentioned in document, those cni pods will be evicted first which may cause serious problems.
apiVersion: v1
kind: Pod
metadata:
  ...
  name: calico-kube-controllers-74d8fb767-69bq7
  namespace: calico-system
spec:
  containers:
    image: calico/kube-controllers:v3.26.3
    imagePullPolicy: IfNotPresent
    resources: {}
  preemptionPolicy: PreemptLowerPriority
  priority:<PHONE_NUMBER>
  priorityClassName: system-cluster-critical
  ...
status:
  ...
  qosClass: BestEffort

I was wondering if the kubernetes shipped priority class doesn't follow the eviction rules, I woundn't worry about this problem.

May be this blog helps your need

guaranteed-scheduling

@tamilselvan1102 thx, it helps.

if you got a solution, please close the issue.


Quartz / cRonstrue mismatch

I use cRonstrue to display a readable translation of a Quartz expression.
The cron expression '0 0 6 * * *' is translated by cRonstrue as 'At 06:00 AM'.
Yet this expression is not supported by Quartz: it's not possible to specify both a day-of-month and a day-of-week (see the first note of https://www.quartz-scheduler.org/api/2.3.0/org/quartz/CronExpression.html).
So, as cRonstrue is supposed to support Quartz expressions, I wonder if it is possible to raise an issue in this case (maybe using a specific 'quartzCompliant' config option).

cRonstrue is not meant to validate cron expressions.  I would recommend validating a cron before passing it into cRonstrue and or Quartz.


Update init.lua

NOTE
Please verify that the base repository above has the intended destination!
Github by default opens Pull Requests against the parent of a forked repository.
If this is your personal fork and you didn't intend to open a PR for contribution
to the original project then adjust the base repository accordingly.

I was jusy forking the repo for my own customisations but mistakenly opened a pr so sorry for that


Add comment documenting the lack of compatiblity of the STACK flag on non-unix platforms.

The STACK flag is only compatible with unix compatible platforms, but was not documented. This PR adds documentation so it is immediately clear to the user that this can only be used on UNIX platforms.
Open questions:

[ ] Should we panic or error when the flag is attempted to be used on windows?
[ ] Should the STACK flag not be compiled in when target_family is not "unix"?

Thanks for clarifying the documentation for MmapFlags::STACK.
Note that this flag is also a no-op on Linux, so in that sense having it be a no-op on Microsoft Windows also makes sense. Maybe it makes sense to clarify this in the documentation too, since this also applies to flags such as MmapFlags::NO_CORE_DUMP and MmapFlags::TRANSPARENT_HUGE_PAGES.
Hiding those flags on specific platforms would make the API a bit more tedious to use imo. For certain flags, it may make sense for MmapOptions::map() and friends to return an error, though (e.g. MmapFlags::HUGE_PAGES), since that is what happens on platforms where the request cannot be honored anyway.  However, these functions generally shouldn't panic, since in this case the user should be able to fallback to requesting a memory mapping without the offending flags, rather than have their code fail at run-time on a specific platform.


unable to run kubitect apply --config ./kubitect.yaml --action upgrade

i exported the config for the existing cluster, then tried running kubitect apply --config ./kubitect.yaml --action upgrade - which resulted in an error. i noticed that the git diff added some strange lines so removed them and tried again and still got an error.
the keys that kubitect are complaining about don't exist in the cluster config:
│   cluster.nodes.loadBalancer.instances.1.priority
│   kubernetes.manager

here's my kubitect.yaml file:
jchen@MacBook-Air-4(main|…1)> cat kubitect.yaml                                                                                ~/workspace/homelab/kubitect
hosts:
    - name: catnet21390176
      default: true
      connection:
        user: root
        ip: <IP_ADDRESS>
        type: remote
        ssh:
            keyfile: ~/.ssh/id_ed25519
            port: 22
      mainResourcePoolPath: /var/lib/libvirt/images/
      dataResourcePools:
        - name: rook-pool
          path: /var/lib/libvirt/images/
    - name: catnet21390118
      default: false
      connection:
        user: root
        ip: <IP_ADDRESS>
        type: remote
        ssh:
            keyfile: ~/.ssh/id_ed25519
            port: 22
      mainResourcePoolPath: /var/lib/libvirt/images/
      dataResourcePools:
        - name: rook-pool
          path: /var/lib/libvirt/images/
cluster:
    name: pounce
    network:
        cidr: <IP_ADDRESS>/16
        mode: bridge
        bridge: br0
    nodeTemplate:
        user: jchen
        os:
            distro: ubuntu22
            networkInterface: ens3
            source: https://cloud-images.ubuntu.com/releases/jammy/release-20230606/ubuntu-22.04-server-cloudimg-amd64.img
        ssh:
            addToKnownHosts: false
        cpuMode: custom
        dns:
            - <IP_ADDRESS>
        updateOnBoot: true
    nodes:
        master:
            default:
                cpu: 2
                ram: 4
                mainDiskSize: 32
            instances:
                - id: "1"
                  host: catnet21390176
                  cpu: 4
                  ram: 8
                  mainDiskSize: 32
        worker:
            default:
                cpu: 2
                ram: 4
                mainDiskSize: 32
            instances:
                - id: "1"
                  host: catnet21390176
                  cpu: 8
                  ram: 48
                  mainDiskSize: 512
                  dataDisks:
                    - name: rook
                      pool: rook-pool
                      size: 256
                - id: "2"
                  host: catnet21390118
                  cpu: 8
                  ram: 56
                  mainDiskSize: 768
                  dataDisks:
                    - name: rook
                      pool: rook-pool
                      size: 256
        loadBalancer:
            vip: <IP_ADDRESS>
            default:
                cpu: 2
                ram: 4
                mainDiskSize: 32
            instances:
                - id: "1"
                  host: catnet21390118
                  cpu: 4
                  ram: 4
                  mainDiskSize: 16
            forwardPorts:
                - name: http
                  port: 80
                  targetPort: 80
                  target: workers
                - name: https
                  port: 443
                  targetPort: 443
                  target: workers
kubernetes:
    version: v1.26.5
    dnsMode: coredns
    networkPlugin: cilium

kubitect version v3.4.0
any ideas?

Thanks for reporting this issue, will look into this and report back. It seems that allowed events for a specific actions need to be tweaked a bit.

The kubernetes.manager field should be automatically detected. Can you try adding the following into your configuration?
kubernetes:
  manager: kubespray

Regarding the LB priority, can you share the LB configuration from ~/.kubitect/clusters/pounce/config/kubitect--applied.yaml? Thanks

lb section from applied.yaml
        loadBalancer:
            vip: <IP_ADDRESS>
            default:
                cpu: 2
                ram: 4
                mainDiskSize: 32
            instances:
                - id: "1"
                  host: catnet21390118
                  cpu: 4
                  ram: 4
                  mainDiskSize: 16
            forwardPorts:
                - name: http
                  port: 80
                  targetPort: 80
                  target: workers
                - name: https
                  port: 443
                  targetPort: 443
                  target: workers

jchen@MacBook-Air-4(main|✚1…1)> kubitect apply --config ./kubitect.yaml --action upgrade
┌
│ Error type: Invalid Configuration Change
│ Config path:
│   cluster.nodes.loadBalancer.instances.1.priority
│   kubernetes.manager
│ Error:
│   Change is not allowed. Upgrade action allows changing only 'kubernetes.version'.
└
┌
│ Error: Configuration file contains errors.
└
[1] jchen@MacBook-Air-4(main|✚1…1)> git diff
diff --git a/kubitect/kubitect.yaml b/kubitect/kubitect.yaml
index eb3170b..5627edc 100644
--- a/kubitect/kubitect.yaml
+++ b/kubitect/kubitect.yaml
@@ -104,4 +104,5 @@ kubernetes:
     version: v1.26.5
     dnsMode: coredns
     networkPlugin: cilium
+    manager: kubespray


django.core.exceptions.ImproperlyConfigured: Requested settings, but settings are not configured.

Hi,
running "python3 setup.py test" fails, with the error message: django.core.exceptions.ImproperlyConfigured: Requested settings, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.

@SnarkBoojum request that you try following this: https://django-rest-framework-simplejwt.readthedocs.io/en/latest/development_and_contributing.html thanks!

Oh, support for tests from setup.py is already dropped... ok, I can live with that.
Thanks!


Change SDK separate handling for v11/v12+ GTM objects

Currently, if users have v11 and v12 devices they need to manage, they need to write separate functions as we don't provide a single method to handle both cases. This is broken.
Reference

the whole interface was setup this way, the way our classes work is that they are chained to roughly reflect the REST URI, since v11 and v12 interfaces changed drastically this is reflected in the modules. I would suggest doing something that is not going to change the current class structures for those endpoints

Thanks for this; we have a clearer understanding of what to expect using the SDK, now.


implement simple mapper node

In the experimental github repo, I made a simple mapper node for the crazyflie as an replacement of the slam toolbox, https://github.com/knmcguire/crazyflie_ros2_experimental. That worked actually much better for the multiranger.
Eventhough we have a slamtoolbox tutorial, maybe we can consider adding the simple mapper to this repo anyway?
Some improvements need to be added to it though:

Make sure that it is able to handle the same inputs as the slam toolbox (as it didn't before), so it is easy to switch
Perhaps look at this work how to make the map even better. This blogpost of 2 years ago made some improvements to the original point cloud code Marcus made so perhaps we can use that as well (with proper citing ofcourse)

I will start with tutorials and simulation first (I only have one crazyflie and don't want to charge all the time) so I can align the same input parameters for both packages. For myself, it will be a little discovery task first to get hands on it.


build_linux/Makefile-sdktool, Makefile-tcsconsole: Add -Werror now.

The -Werror option can now be added for sdktool and tcsconsole directories.

Very nice!


Xcode 10 issue

In your sample app itself when you run sample application  in Xcode 10.0 It displays the error:
Could not cast value of type 'Swift.Optional' (0x1101a4458) to 'DipSampleApp.PersonProviderAPI' (0x1101a4580).

Should be fixed with https://github.com/AliSoftware/Dip/issues/193


Question about max_pending_requests and max_connections in circuit breaker

From https://github.com/envoyproxy/envoy/blob/6aee60364ef1bb539e19abc68d1e6cbe93c41512/source/common/http/conn_pool_base.cc#L114_L138, when there ready_clients_ is empty, the following happens:

a check against max_pending_requests when there ready_clients_ is empty
the pending requests counter is incremented while a new connection is being created

Envoy does not seem to pre-intialized ready_clients_. Does this mean if max_pending_requests is smaller than max_connections, requests could be rejected due to the number of pending requests hitting the max_pending_requests limit,  even if the number of connections to upstream is less than max_connections?

Does this mean if max_pending_requests is smaller than max_connections, requests could be rejected due to the number of pending requests hitting the max_pending_requests limit, even if the number of connections to upstream is less than max_connections?

Yes, I think that's correct, and is something that could happen after a cold start. I wouldn't expect it to happen once a steady-state has been reached.

Yes, that's correct with the current impl.

Thanks for the clarification. Regarding:

I wouldn't expect it to happen once a steady-state has been reached.

Will the created ActiveClient instances always be around and moved back to ready_clients_ after being used? Or could they be also closed (for example, in https://github.com/envoyproxy/envoy/blob/6aee60364ef1bb539e19abc68d1e6cbe93c41512/source/common/http/conn_pool_base.cc#L99-L103 perhaps?)
If the ActiveClient being created could be closed after steady-state, could that lead to a similar type of problem like the cold start scenario (requests being rejected due to max_pending_requests being hit before the max_connections limit is hit)?

Yes it's possible you could get back into that situation due to idle timeouts or something else.

Thanks, this clears things up.


Remove redundant call to checkNodeDeferred

Fixes #22491
If I have this right, we will always do one more check after all SkipContextSensitive checks.
Before this PR, the assertion (also added in this PR) would have failed for most arrow functions in call expressions.
For posterity, a simple test case that failed was:
// @noUnusedLocals: true
// @noUnusedParameters: true
declare function f<T>(a: (s: string) => T): void;
f(s => s);

(we have lots of test cases like this already, so didn't see a need to add a new one.)

It means we recheck the grammar during every every inference pass, which seems wasteful.

I wonder if it wouldn't impact performance to just move all the grammar checking out to its own tree walk -- would certainly make the code easier to read.

@andy-ms We effectively already do js-only grammar checks in a separate tree walk in program, so it can't be that bad.


Add setting to exclude symlinks from search paths

VSCode Version: Code 1.17.1 (1e9d36539b0ae51ac09b9d4673ebea4e447e5353, 2017-10-10T14:21:18.489Z)
OS Version: Linux x64 4.13.5-200.fc26.x86_64
Extensions: Extensions are disabled

Steps to Reproduce:

Open a project with this structure:
./src/one_file.js
./srclink -> symlink to ./src

Do a fuzzy search of "onefile".

2 results will appear, one under each folder.

Before, the workaround explained at https://github.com/Microsoft/vscode/issues/36549 could be used, but since its regression, you only can choose among having several or none results, not just one.
The feature proposal here is to add a setting that allows you to exclude symlinked files from searches automatically.

Reproduces without extensions: Yes

Thanks! ❤

Verified on macOS.


Weird AnnotationAssertion in owlaxioms: section of OBO file

AnnotationAssertion(<http://www.geneontology.org/formats/oboInOwl#created_by> <http://purl.obolibrary.org/obo/MONDO_0300000> \"\")

Is the presence of this assertion necessary or should it be removed?

there is this extra annotation, is that what you mean? I can fix this

Thanks Nicole! I have already fixed it in the pull request here: https://github.com/monarch-initiative/mondo/pull/903

cool, thanks @matentzn!

Fixed by https://github.com/monarch-initiative/mondo/pull/903


Application form

@PatilHarshh

Please check this i added application form that take user's basic information like name, email, phone
in secord part it take resume of particular user
and after that it will take user exprience
also added validations

screen-shorts

and when user submit their application they got success messgae:

@PatilHarshh Please check it and merge it

resolve conflicts

@PatilHarshh  Conflicts Resolved

@PatilHarshh can you please provide me ss of deploy error..

resolve conflicts

client/package-lock.json
client/package.json
Remove this files!! No need of this !! Did you use any new react package ?

@PatilHarshh
All conflicts resolved

Conflicts !!

@PatilHarshh
now evevrything working properly
i designed application form with all validation
it first take basic information from user like name, email, phone etc...
in second step it take resume of user
and in third step it take experience if they have
kindly check it and merge it
please add level 3 label

@PatilHarshh
kindly please check this and merge it

And My Huge Request to Update your local repo ! There is massive changes happening in Main Repo . Due to not Proper updation You are pushing Old Code Which is already changed !! Which is affecting Our Repo.

@PatilHarshh
can you please add level 3
i designed application form with all validation
designed same as linked in apply form
it first take basic information from user like name, email, phone etc...
in second step it take resume of user
and in third step it take experience if they have
i store all user's information in state and print it in console
kindly check it and merge it


Presence of no necessary output in Free Data Sample Study on Antares Desktop

Description
In the 000Free Data Sample on Antares Desktop, we have some results witch are not necessary and not usable (any economy folder is present).
The best way is to put this study example without output.
Screenshot

Additional informations
Antares Desktop 2.14.4 (github action artefact)
This issue is not urgent.

Do we want to put no output or a realisitic one with the folder economy ?

No output it the best way.


Calling .nack() disables exponential backoff and creates log jams

Environment details

OS: Debian
Node.js version: 16.13.1
npm version:
@google-cloud/pubsub version: 2.18.1

Steps to reproduce

Create a subscription with an exponential backoff (i.e., using retryPolicy.minimumBackoff and retryPolicy.maximumBackoff)
Receive a message
Call .nack()
See that the message is delivered again nearly immediately
Call .nack() again
See that the message is delivered again nearly immediately
Call .nack() again
See that the message is delivered again nearly immediately
Call .nack() again
See that the message is always delivered again nearly immediately and never respects the minimumBackoff or exponential backoff

Other notes
The immediate problem this creates is that if the subscription's maxMessages is set to 1, other messages get log-jammed behind the one that's being .nack()'d.
This can be partially alleviated by using the optional delay with .nack() like .nack(60), but this still wouldn't honor exponential backoffs unless the engineer built their own exponential backoff mechanism to pass .nack()` an ever-increasing value each time. But it'd be a bit disappointing to have to do that when that's a feature already baked into Google Cloud Pub/Sub. EDIT: This feature has been removed, leaving no way to work around this.
Not calling .nack() creates its own problems, especially in light of the client's automatic extension of ack deadlines. See: https://stackoverflow.com/a/59128326.
A similar issue can be found here, but it's slightly different: https://github.com/googleapis/nodejs-pubsub/issues/119.

Thinking about this more, simply increasing the maxMessages wouldn't scale well, since let's say you increased it to 5, and there were 5 messages currently being .nack()'d as soon as they were received, you'd still create a log jam.

Just stumbled across documentation that discusses using .nack() with exponential backoff:

If messages are in a batch, Pub/Sub starts the exponential backoff when one of the following occurs:

The subscriber sends a negative acknowledgement for every message in the batch.

The only solution to this that I've found, and it's not ideal, is to:

Ensure the retryPolicy.minimumBackoff is a few seconds greater than the ackDeadline
Set the flowControl.maxExtensionMinutes to 0
Never .nack() a message

There are several downsides to this approach, though:

Since the minimumBackoff has a maximum value of 600 seconds, this solution won't work if the ackDeadline is larger than that
You can't have a minimumBackoff less than ackDeadline, even if that's desired
If you want to use ack deadline extensions, you can't, since you have to disable that feature
Since you can't call .nack() anymore, subscribers that can't process a message get knocked out-of-commission while they wait for the ackDeadline to expire, even when they know they're ready to move on to other messages

I think we had a discussion about this before and that had a "works as expected" sort of result, but I'll try to get some attention on this again. @kamalaboulhosn ?

If the exponential backoff settings are not being respected, then a support case should be entered so that more investigation can be done on the server side.

@kamalaboulhosn was a support case entered? I do have this issue. I want to nack a message so it gets retried later, but i also want it to respect the exponential backoff.
Right now it will just instantly retry it, which is not the desired behaviour.

@vmorgado if you are having this issue, you should enter your own support case.

Follow-up on this issue should be via a support case.

@kamalaboulhosn Can you clarify why a bug with this @google-cloud/pubsub package needs to be resolved by Google Cloud Platform's support? I wasn't aware they had the ability to fix bugs in this package. I will note that there are plenty of other open bug issues for bugs with this package.

@WesCossick Adherence to the retry settings is a server-side behavior, not a client-side behavior, which is why this needs to be investigated via a support case.

@kamalaboulhosn I'd be a little surprised if this was a problem with the server side of Google Pub/Sub, since it's clearly documented how nack and exponential backoff should work together, and the Node.js client is the only client I could find that has a report of the nack and exponential backoff not working in accordance with Google's own documentation. If it was a problem on Google's server end, I would suspect other client libraries would have received similar reports.
In any case, submitting a technical support request on our end requires paying Google a fee, and paying Google to help Google debug its own software isn't something we would pay for. If you're confident it's not a client issue, then I believe the correct move would be to open an issue with the Google Pub/Sub issue tracker.

@WesCossick I can assure you that the behavior of backing off is a behavior in the server, not the client. If the nack is sent by the client, the act of the backoff occurring before the next delivery happens on the server, not the client. I can't say with 100% certainty that the issue is in the server, but in order to debug further, we need to ask user-specific information and look up information on the backend and doing that requires a support case. It might be the combination of properties on the subscription, it may have to do with the delivery details of throughput or how messages are generally being processed by the user code, or it could be several other things. But in order to say for certain in any way, more information that cannot be requested without a support case is needed. Creating an issue in the public issue tracker will not be sufficient as we need to ask for non-public information.

@kamalaboulhosn Purely backing off is a service-side responsibility, true. But this client has a number of nuances and complexities to how it operates, and there's no issue with how exponential backoff works as long as you don't call .nack() in this client. So that leads me to suspect it's a client issue. Here are a few nuances that might impact how nack + exponential backoff are working together:

This client doesn't actually send a "nack" request; instead, it sets the ack deadline to 0 and then removes the message from its own inventory.
This client quietly performs automatic message extensions by default.
This client used to support a "delayed" nack, and had been built around that concept.
This client manages batching for you and has a concept of leasing messages.

Seeing as you work for Google, if you're able to open a technical support request on our behalf, I'd be happy to provide more information, including non-public information. But our company isn't willing to pay Google to help Google debug its own services. We operate at a large enough scale that working around this bug isn't particularly problematic for our company. But it could be a significant performance bottleneck for other companies, so I would expect Google would be interested in resolving the problem.

This client doesn't actually send a "nack" request; instead, it sets the ack deadline to 0 and then removes the message from its own inventory.

Maybe because there is no "nack" API? I think "nack" just means to zero ack deadline.

@WesCossick Looking at the pubsub API, they don't have any special "nack" other than meaning to zero ack deadline. So, the issue might be truly on server side.

@pksunkara Personally, I would conclude the opposite. Seeing as the server-side doesn't actually offer NACK, therefore calling .nack() is purely a client-side thing, if calling .nack() causes problems, I would conclude that the source of those problems therefore lies with the client.

Serverside does offer nack by saying it's modAck(0).


Insight fixes

Current coverage is 100.00%

Merging #9 into master will not affect coverage as of e26233d

@@            master      #9   diff @@
======================================
  Files            2       2
  Stmts          100     100
  Branches         0       0
  Methods         20      20
======================================
  Hit            100     100
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of e26233d

Powered by Codecov. Updated on successful CI builds.


Avoid string allocations in Cfg

Code gen time continues to be painful for me. I've been meaning to remove the allocation of strings inside Cfg as that's a really hot bit of code so here goes.
Unfortunately, the vast majority of time running code gen is actually spent on rustfmt and not code gen itself. For example, the main code generator - tool_windows - takes about 10 seconds (under 3 seconds in release) to run without rustfmt and over 150 seconds with rustfmt.

the main code generator - tool_windows - takes about 10 seconds (under 3 seconds in release) to run without rustfmt and over 150 seconds with rustfmt.

That's interesting: for me on Linux (with some tweaks to disable #[link(name = "windows")] in -sys and simplifying it in the core windows crate - issue coming up) it runs much, much faster than that:
cargo r --release -p tool_windows  213.75s user 24.07s system 2154% cpu 11.041 total

Have you optimized this in the past 12 days? Even on a 32C/64T system I didn't expect to be ±13.6 times faster :)

Did some experimentation with prettyplease. Interestingly, since the rustfmt binary is already compiled in release mode, the use of prettyplease only improves things in release mode.
When running tool_windows in release mode on my Windows machine, I get the following results:

rustfmt: ~41s
prettyplease: ~16s
no formatting: ~3s

When running in debug:

rustfmt: ~58s
prettyplease: ~92s
no formatting: ~19s

It's also important to note the two added dependencies (prettyplease and syn) do increase the release build times:

without: 13s
with: 25s

This means that for release builds from scratch:

rustfmt: ~54s
prettyplease: ~41s

Some additional tradeoffs:

using prettyplease means that we don't rely on the user having rustfmt installed. Albeit rustfmt is pretty essential so the likelihood of this is pretty small.
prettyplease's formatting is a bit worse, but from a spot check it doesn't look too bad. The biggest issue is that it uses a lot more lines (presumably since it doesn't respect the rustfmt config where we allow for wider lines). We could use prettyplease in development and rustfmt for the final change.

This does sound promising enough to warrant thinking about. @kennykerr thoughts?


Do tokenizers have to be slow?

Currently tokenizers are forcibly loaded as slow, but it's not always possible: for instance tokenizers saved from RobertaTokenizerFast don't provide a slow version (since that would require to generate a sentencepiece model from the tokenizers one, something that's currently not supported). As a result, trying to use one of the models (e.g. lgrobol/xlm-r+CreoleEval_all currently fails.
As a temporary fix I have tried to remove use_fast=False from the dataset collection code ans everything seems to work fine. Am I missing something? Is there still a reason for forcing the use of a slow tokenizer or can this be removed?

Hmm, I'd rather have a check in place and use the slow one when it is available. I tried to tokenize the whole UD with mBERT fast and slow a couple years back, and the fast one led to many more character differences. One of the strangest example being:

from transformers import AutoTokenizer
tokenizer = AutoTokenizer.from_pretrained('bert-base-multilingual-cased')
tokenizer.decode(tokenizer.encode("do not"))
"[CLS] don't [SEP]"

Ok, I surrounded it in a try-except block for now, seems like a robust solution

Wow, this is so bizarre, I had no idea. Anyway, thank you for the quick fix!


Clarify that the vararg aligned register pair rule may leave a7 unused

I think it's worth being explicit here, even though doing anything else would be impossible (as va_list couldn't work).

agreed


Added signed version

This addresses #1
Would you care to review and publish it?
I did some minor changes to the tests too.
One tests (MdFilesTest) fails (on the unaltered codetoo), but I haven't found out why. This may be some encoding thing.

I changed to key file path to be relative


Add property effects public getter

Hi. I am using Polymer 3.0.
So what do I want in Polymer Elements public API:
The method that returns specific effects of the given property, with the signature like this:
getPropertyEffects(string prop, PROPERTY_EFFECT_TYPES effectType);
Now I  have to access, for example, __computeEffects directly to retrieve effect.
Use case:
Consider;
get properties() {
    return {
          condition: Number,
          items: Array
    }
}

first() { return [1, 2, 3]; }
second() { return [4, 5, 6]; }
...

I want to change computation function of items depending on condition dynamically using createComputedProperty but it doesn't remove old compute effect. So getPropertyEffects method will help to retrieve old one and remove it using public method removePropertyEffect.
Thanks in advance

Or createMethodEffect will return created effect. This way Element will incapsulate other effects.

@TimvdLippe Yeah, I think so. How is it going?

Haven't had the time to continue :(
On Mon, Oct 8, 2018 at 6:45 PM Makhambet<EMAIL_ADDRESS>wrote:

@TimvdLippe https://github.com/TimvdLippe Yeah, I think so. How is it
going?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/polymer/issues/5369#issuecomment-427921298,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrDbwgk79LJbMUxZHv00lqQT3R78Ewwks5ui48qgaJpZM4XLX5t
.


⚠ Cioos National CKAN has degraded performance

In e237456, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 5700 ms

Resolved: Cioos National CKAN performance has improved in 882c74c after 5 minutes.


Integrate with new CAC API for side panel

KMission provided me a new API that allows control of the side panel - integrate with it.

there two methods in API
CustAmmoCategories.CombatHUDInfoSidePanelHelper.SetSelfInfo(AbstractActor actor, Text text)
CustAmmoCategories.CombatHUDInfoSidePanelHelper.SetTargetInfo(AbstractActor actor,ICombatant target, Text text)

Done in 8.0.0, but updates only on a refresh of the targeting HUD. Per KMission 'it would be nice' if the update reflected the current preview move state, if possible.
no i mean in battle :slight_smile:
eg . it is good idea to update it on MoveStatusPreview.Prefix taking Vector3 worldPos as base point instead of unit.CurrentPosition
i think

Fixed in 1.0.0


Implement support for more sophisticated function signatures.

Currently, we only support "raw" JSON-in/JSON-out, which in Golang terms translates to a rather non-pretty map[string]interface{} on both ends. It works, but UX wise leaves a lot to desire. Namely:

We don't support Golang-style error handling. Users would have to handle all errors inside their code and transform them into appropriate JSON maps.
We don't support arbitrary types (that are JSON marshalable). Users have to deal with transforming the map[string]interface{} into their own types to make something useful of it.
We don't support taking a context object. Another Golang standard, especially for anything that does networking.

So this implements all that.

We now support returning errors from a function. The error is assumed to be an application error and is thus transformed into a "proper" OpenWhisk compatible JSON with the 'error' key.
We now support arbitrary types as input and output as long as they are marshalable from and to JSON. We handle that for the user.
We now support passing a Context object to a function. It doesn't do anything useful yet, but can be augmented with the function's deadline and context in a following step.

For posterity, this allows functions like
package main

import (
	"fmt"
)

type MyInputTypeIsSoCool struct {
	Name  string `json:"name,omitempty"`
	IsBad bool   `json:"isbad"`
}

type Output struct {
	Greeting string `json:"greeting,omitempty"`
}

func Main(in MyInputTypeIsSoCool) (*Output, error) {
	if in.IsBad {
		return nil, fmt.Errorf("%s is a baaaaaaaad guy.... duh!", in.Name)
	}
	return &Output{
		Greeting: fmt.Sprintf("Hey %s", in.Name),
	}, nil
}

package main

func Main(r Request) (*Response, error) {
	return &Response{
		Body: r,
	}, nil
}

type Request struct {
	Method  string            `json:"__ow_method,omitempty"`
	Headers map[string]string `json:"__ow_headers,omitempty"`
	Path    string            `json:"__ow_path,omitempty"`
	User    string            `json:"__ow_user,omitempty"`
	Body    string            `json:"__ow_body,omitempty"`
	Query   string            `json:"__ow_query,omitempty"`
}

type Response struct {
	Headers    map[string]string `json:"headers,omitempty"`
	StatusCode int               `json:"statusCode,omitempty"`
	Body       interface{}       `json:"body,omitempty"`
}

Not yet, there wasn't even a task to do this in the first place. More of a morning-experiment gone good for now 😂

If this merges, I'd propose to rewrite the sample golang function as
package main

func Main(in Input) Response {
	name := "stranger"
	if in.Name != "" {
		name = in.Name
	}

	return Response{
		Body: "Hello " + name + "!",
	}
}

type Input struct {
	Name string `json:"name"`
}

type Response struct {
	Body string `json:"body"`
}

Ran the scala tests locally and it looks all good.


✨ [Feature request]: Automatic tweet about newly created play

Is your feature request related to a problem? Please describe.
The idea is to submit an automatic tweet as soon as a new play gets merged to main. It will remove, all manual intervention and will reduce human error.
Describe the solution you'd like

Gather the creator's tweeter handle (optional) during play creation
Create a standard template for new play tweet
Create a git hook (nhost) to submit a tweet once it gets merged,

Describe alternatives you've considered
NA
Additional context
Review the template before proceeding

Hi @koustov, I would like to contribute to this issue if it is up for grabs so that you could assign it to me.


[NTR/gene] MTOR

Preferred gene-related syndrome label
MTOR-related Overgrowth spectrum
Synonyms
MONDO:0100283
Parent term (use OLS, or your favorite ontology browser)
MONDO:0019716
Definition
Please write the definition in the format: Any [parent class] in which the cause of the disease is a mutation in the [gene name] gene.
Any malformations/disorders resulting from pathogenic gain-of-function variants in the MTOR gene. The variants can be germline or somatic
**Definition source (Please give PubMed ID, if applicable, in format PMID:#######)
PMID: 27860216; 33833411; 35163267
Children terms (if applicable) Should any existing terms be re-classified as children underneath this new proposed term?
MONDO:0011818
MONDO:0014716
Your nano-attribution (ORCID) or URL for a working group
If you don't have an ORCID, you can sign up for one here
https://clinicalgenome.org/affiliation/50020/

Dear @abbe-Lai,
Thank you for reaching out to the Mondo Disease Ontology, part of the Monarch Initiative!
We have received your ticket and will review it as soon as possible.
If you have any additional information or updates relevant to your inquiry, please add them in a comment on this ticket. Your input is valuable in helping us understand and resolve the issue effectively.
Thank you for your patience and for your contributions to Mondo!
Sincerely,
The Mondo Team

Hi @abbe-Lai I see you requested MONDO:0100283 as a synonym, but this is an existing class, so it does not make sense, ontologically, to add this as an exact synonym. We could add it as a related synonym? Does that work?

MONDO:0011818 'isolated focal cortical dysplasia type II' has mutations in 3 possible genes (according to OMIM), so in this case as well, it doesn't make sense ontologically to add this as a child of MTOR-related overgrowth spectrum because that would mean every case of 'isolated focal cortical dysplasia type II' would have a mutation in MTOR, but according to OMIM, there may be variations in any of these three genes but not every case has an MTOR variation.
Also, I don't think it makes sense to classify MONDO:0014716 'macrocephaly-intellectual disability-neurodevelopmental disorder-small thorax syndrome' as a child of overgrowth syndrome, as overgrowth is just a feature of this disease.
Let me know if you have further questions about these, thanks!


sshd.config stage: support PermitRootLogin option

Add support for PermitRootLogin option in the
org.osbuild.sshd.config stage.
I kept the "yes" and "no" values for consistency with other stage
options. While it will make the implementation in osbuild-composer
harder, it won't be impossible as we already have a precedence for doing
it this way (e.g. in the org.osbuild.pam.limits.conf).
Modify the stage unit tests to check the new option.
Remove the empty org.osbuild.sshd.config stage from a.mpp.json
since it does not add any value and it actually made the tree-diff
tool provide a weird tree diff results.
Fix #910
Signed-off-by: Tomas Hozza<EMAIL_ADDRESS>

@gicmo CI tests passed (and finally also the qemu assembler test) and hopefully no bot will force push until merged... 😆
❤ in advance for a review....

@gicmo could I please get another try? thanks