Nuxt Starter Project no longer works when SSR is false on 3.4.0

Environment

Operating System: Darwin
Node Version:     v16.18.1
Nuxt Version:     3.4.0
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      ssr
Runtime Modules:  -
Build Modules:    -

Reproduction
I created a new Nuxt application using npx nuxi init project-ssr-false
Then ran npm install
The only change I made was in nuxt.config.ts:
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
    ssr: false
})

Then npm run dev
Here is a repo with the configuration specified above that reproduces the issue: https://github.com/justinwride/project-ssr-false
Describe the bug
The bug is a blank white page when I expected to see my Nuxt application.
After navigating to http://localhost:3000 I get the following console errors:

Additional context
This error does not happen on version 3.3.3. It is a new error with version 3.4.0.
The line that appears to be failing is this:
const nuxt = createNuxtApp({ vueApp });

Which is failing because of this line:
const runtimeConfig = process.server ? options.ssrContext.runtimeConfig : reactive(nuxtApp.payload.config);

It appears that nuxtApp.payload.config is undefined
Logs
entry.js:39 value cannot be made reactive: undefined
createReactiveObject @ vue.js?v=2e04f03c:1090
reactive @ vue.js?v=2e04f03c:1076
createNuxtApp @ nuxt.js?v=33afac7b:97
initApp @ entry.js:39
(anonymous) @ entry.js:57
Show 3 more frames
entry.js:58 Error while mounting app: TypeError: Cannot create proxy with a non-object as target or handler
    at createNuxtApp (nuxt.js?v=33afac7b:98:1)
    at initApp (entry.js:39:18)
    at entry.js:57:3
(anonymous) @ entry.js:58
Promise.catch (async)
(anonymous) @ entry.js:57

Huge apologies for this. It's already resolved in the edge channel via https://github.com/nuxt/nuxt/pull/20216, and I'll be releasing a patch shortly.


Integrating With Git Repo

Integrating With Git Repository e.g Bitbucket or GitHub ...
Maybe this feature looks like in Visual Studio...
This feature can upload project into Git Repo directly via Bracket Editor ...
Look like Visual Studio, the project working in Editor can upload directly The project Issue, Update New code and etc into Visual Studio Online ...
Just it! I'm Sorry for my bad English :)  #Suggestion

Brackets-Git. 'Nuff said. :)

Brackets Git Extension from the extension registry :100:


Initialization error Adapty.setFallbackPaywalls

Flutter 3.3.8
Adapty package: https://pub.dev/packages/adapty_flutter
Problem initializing Adapty.setFallbackPaywalls
the custom_payload line has an error
Default from adapty Json:
E/Adapty_v1.11.0(22951): Couldn't set fallback paywalls. com.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Unterminated object at line 26 column 13 path $.data[0].attributes.custom_payload
The line that indicates the error:
"custom_payload": "{"abTestData":{"resale_2ytz6bu":false}}"
Manually removed \
Couldn't set fallback paywalls. com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 25 column 28 path $.data[0].attributes.custom_payload
The line that indicates the error:
"custom_payload": {"abTestData":{"resale_2ytz6bu":false}}
Put on custom_payload null
Everything is ok if:
"custom_payload": null

@samatzhusup could you please send the fallback paywalls to our support so that we debug your case?

Some characters are treated as escape characters and omitted, so when creating a String variable for the file contents, please use so called raw strings:
String fallbackPaywalls = r'xxxxx'
where "xxxxx" is copied from the file as is


Get status of PRVs with EPANET-Matlab toolkit

Hello all,
When I use d.getLinkStatus for status of PRVs, I get 0 (closed) or 1 (open) for PRVs while in EPANET software we can get three status for PRVs after hydraulic solving. These status are Open (means Inactive or fully open), Active and Closed.
How I distinguish the status of Open with Active in PRVs with EPANET-Matlab toolkit?
Thank you all,
Alireza

Thanks @alireza2032 for posting this. The STATUS reported by the function is basically OPEN or CLOSED. There are more STATES for links and nodes. Form the code:
typedef enum {
  XHEAD,        /*   pump cannot deliver head (closed) */
  TEMPCLOSED,   /*   temporarily closed                */
  CLOSED,       /*   closed                            */
  OPEN,         /*   open                              */
  ACTIVE,       /*   valve active (partially open)     */
  XFLOW,        /*   pump exceeds maximum flow         */
  XFCV,         /*   FCV cannot supply flow            */
  XPRESSURE,    /*   valve cannot supply pressure      */
  FILLING,      /*   tank filling                      */
  EMPTYING
} StatType;     /*   tank emptying                     */

So we can add an EN_STATE option to ENgetlinkvalue and ENgetnodevalue and return the exact state. This was also suggested to me by Fernando Martínez.
Thoughts anyone?

Thanks a lot Dear eladsal,
I consider your guide.

Committed 99e7151. It turned out that a special check for pumps was needed.
Please test!

@eladsal , I have tested this now and it's ok! Also the status in the binary file it's the same with state (without events). fyi

Thanks @Mariosmsk ,
Is it possible to set the initial status of PRVs with EMT in states Open, Close and None (means active)?

You can use the function d.setLinkInitialStatus(LinkIndex, status)  where status is Initial link status (0 = closed, 1 = open)

Dear @Mariosmsk ,
Thanks, but, 1=fully open and I want to define the initial link status on None (=active or partially open). Is it possible?

Dear @Mariosmsk ,
Thanks, but, 1=fully open and I want to define the initial link status for PRV valve on None (=active or partially open). Is it possible?

Hi @eladsal ,
Sorry for bringing up an old closed issue, but I was wondering if there was any reason why we never got EN_STATE in v2.2 on EPANET, did this commit just miss getting merged in or was there further reasons for it not being included?
cc @neslerel

@lbutler after some investigation, I believe that this enum got refactored as EN_PUMP_STATE - even though you can use it to get non-pump information. It takes some serious browsing of the git-blame, but it does look like Elad's contribution was modified a few times by Lew and that's where it ended up. We should probably have a documentation issue to track that weirdness.
Thanks for bringing this up!

Thanks @samhatchett for tracking what happened, I gave it a try and it worked perfectly.
It would be good if there was an enum for the rest of the states and potentially a more descriptive method name, but we can discuss that in a new issue.


Is it possible to disable swipe right, in order to DON'T open the sidebar menu?

My application needs to open the sidebar right in a few pages, but in other pages it shouldn't open.
For example, if i'm using google maps and i swipe right, i don't need the sidebar menu to open because i'm just scrolling.
How can i prevent the sidebarmenu from opening?

My case is close to this: I would like to disable the swipe right in certain case only, I'm using an outside plugin for Carousels, and when we slide right, the sidebar opens. I don't want it.

Hi, answering myself: there's swipe demo that does exactly what I want.
It's here: http://mobileangularui.com/demo/#/swipe
Just need to use the directives ui-swipe-left ui-swipe-right to the element that we want to swipe by itself without dragging the menu with it. Those directives accepts functions too.
;)

That just solved it, it was exacly what i was looking for!
thanks ErickXavier :)

I have the same problem, and i know this solution but is not workingfor me.
Like in demo i have an index page, and then add content in view otherwhise in  tag
here's some code.
In the controller of the content section i write:
"content": {
						templateUrl: 'views/page1.html',
						controller: function($scope) {
							$scope.$watch('ready', function() {
								$('.app').addClass('transparent');
								$('body').addClass('transparent');
								$scope.swiped = function(direction) {
									alert('Swiped ' + direction);
								};
								engine.camera.initialize();
							});
							$scope.on("$destroy", function(){
								alert("destroy");
								$('.app').removeClass('transparent');
								$('body').removeClass('transparent');
							})

						}
					}

and then in page1.htlm:

that's a div with position absolute tha cover all the screen.
How can i do

i've got to say, i'm not a pro in this affair, i'm gonna tell how i solved it.
but what i did was: in the div i didn't want to open the menu, i used ui-swipe-right=''
here is the demo html page:
view-source:http://mobileangularui.com/demo/swipe.html
click ctrl+u to see the source
instead of a div absolute position, try this:

tell me if it worked :p

i've just tried this solutoin and dosn't worked....this is very strange behavior


Error: (SystemJS) ctorParameters.map is not a function 	TypeError: ctorParameters.map is not a function

Trying to use the ng2-completer but getting error
Error: (SystemJS) ctorParameters.map is not a function
TypeError: ctorParameters.map is not a function
my

package.json has  "ng2-completer": "^1.5.0"
systemjs.config map has 'ng2-completer': 'npm:ng2-completer/ng2-completer.umd.js'
App.module has

1. `import { Ng2CompleterModule } from "ng2-completer" and import { FormsModule } from '@angular/forms';`
2. `@NgModule imports has Ng2CompleterModule and FormsModule`

what i am doing wrong?

hard to say, need some more info like you system.js config

Hello - I am getting the same error - Upgraded Angular from 2.0.0 to 2.1.0

can you try 'ng2-completer':             'npm:ng2-completer'
See the demo plunk for a reference

Now I get
zone.js:232 Error: SyntaxError: Unexpected token <
at eval ()
Evaluating http://localhost:2592/node_modules/ng2-completer.js
Error loading http://localhost:2592/app/boot.js

did you try with Angular 2.1.0?

Yes - and I get the error - (SystemJS) ctorParameters.map is not a function TypeError: ctorParameters.map is not a function

According to this  it's an issue with Angular compiler-cli >= 2.3.0.
looks like the minimal supported version should be 2.3.0.
Maybe you can import from ng2-completer/src and not from ng2-completer.


coroutines broken when using g++ (due to built in defines?)

I have a project configured with cmake that makes use of C++20's coroutines. (I use cmake's generated compile_commands.json to help clangd).
When working on the project under macOS clangd worked very well and I could use anything relating to coroutines fine.
However, working on it under Linux is giving me quite a lot of trouble.
A small reproduction case is included at the end.
I think I have traced it back to the builtin defines being "wrong".
It seems that even with compile_commands.json, clangd uses its internal defines instead of the ones given my g++.
For example, when parsing a file with clangd, __clang__ is defined.
Is this currently the intended behaviour? I saw #533 and was not sure where this exactly applies. I would expect compile_commands.json to "just work", i.e. use everything from the compiler specified there.
Interestingly enough, I also tried compiling clangd from git main and then the repro case below works. However, it still does not work well for my project, since I am using boost.asio there. The following snippet fails there, since __clang__ is defined, but the header <experimental/coroutine> is not found.
// Support the co_await keyword on compilers known to allow it.
#if !defined(ASIO_HAS_CO_AWAIT)
# if !defined(ASIO_DISABLE_CO_AWAIT)
#  if defined(ASIO_MSVC)
#   if (_MSC_VER >= 1928) && (_MSVC_LANG >= 201705) && !defined(__clang__)
#    define ASIO_HAS_CO_AWAIT 1
#   elif (_MSC_FULL_VER >= 190023506)
#    if defined(_RESUMABLE_FUNCTIONS_SUPPORTED)
#     define ASIO_HAS_CO_AWAIT 1
#    endif // defined(_RESUMABLE_FUNCTIONS_SUPPORTED)
#   endif // (_MSC_FULL_VER >= 190023506)
#  elif defined(__clang__)
#   if (__cplusplus >= 201703) && (__cpp_coroutines >= 201703)
#    if __has_include(<experimental/coroutine>)
#     define ASIO_HAS_CO_AWAIT 1
#    endif // __has_include(<experimental/coroutine>)
#   endif // (__cplusplus >= 201703) && (__cpp_coroutines >= 201703)
#  elif defined(__GNUC__)
#   if (__cplusplus >= 201709) && (__cpp_impl_coroutine >= 201902)
#    if __has_include(<coroutine>)
#     define ASIO_HAS_CO_AWAIT 1
#    endif // __has_include(<coroutine>)
#   endif // (__cplusplus >= 201709) && (__cpp_impl_coroutine >= 201902)
#  endif // defined(__GNUC__)
# endif // !defined(ASIO_DISABLE_CO_AWAIT)
#endif // !defined(ASIO_HAS_CO_AWAIT)

Logs
clangd.log
System information
Output of clangd --version:
clangd version 13.0.0
Features: linux
Platform: x86_64-pc-linux-gnu

Editor/LSP plugin: clangd for vscode
Operating system:
Linux 5.15.13 (arch)
Small repro case:
CMakeLists.txt:
cmake_minimum_required(VERSION 3.14)

# set the project name
project(clangd_gcc_coro)

set(CMAKE_CXX_STANDARD 20)
set(CMAKE_CXX_STANDARD_REQUIRED True)
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fcoroutines")
set(CMAKE_EXPORT_COMPILE_COMMANDS ON)

# add the executable
add_executable(clangd_gcc_coro main.cpp)

main.cpp:
/* taken from here: https://www.scs.stanford.edu/~dm/blog/c++-coroutines.html */
#include <concepts>
#include <coroutine>
#include <exception>
#include <iostream>

struct ReturnObject {
  struct promise_type {
    ReturnObject get_return_object() { return {}; }
    std::suspend_never initial_suspend() { return {}; }
    std::suspend_never final_suspend() noexcept { return {}; }
    void unhandled_exception() {}
  };
};

struct Awaiter {
  std::coroutine_handle<> *hp_;
  constexpr bool await_ready() const noexcept { return false; }
  void await_suspend(std::coroutine_handle<> h) { *hp_ = h; }
  constexpr void await_resume() const noexcept {}
};

ReturnObject
counter(std::coroutine_handle<> *continuation_out)
{
  Awaiter a{continuation_out};
  for (unsigned i = 0;; ++i) {
    co_await a;
    std::cout << "counter: " << i << std::endl;
  }
}

int
main()
{
  std::coroutine_handle<> h;
  counter(&h);
  for (int i = 0; i < 3; ++i) {
    std::cout << "In main1 function\n";
    h();
  }
  h.destroy();
  return 0;
}

compiles fine here:
➜  clangd_gcc_coro uname -a
Linux archer 5.15.13-arch1-1 #1 SMP PREEMPT Wed, 05 Jan 2022 16:20:59 +0000 x86_64 GNU/Linux
➜  clangd_gcc_coro g++ --version
g++ (GCC) 11.1.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

➜  clangd_gcc_coro cmake --build . && ./clangd_gcc_coro
Consolidate compiler generated dependencies of target clangd_gcc_coro
[ 50%] Building CXX object CMakeFiles/clangd_gcc_coro.dir/main.cpp.o
[100%] Linking CXX executable clangd_gcc_coro
[100%] Built target clangd_gcc_coro
In main1 function
counter: 0
In main1 function
counter: 1
In main1 function
counter: 2

Your original minimal example fails with clangd 13 because coroutines are off by default and clang doesn't support GCC's -fcoroutines flag. Clang's flag is -fcoroutines-ts. I'm not sure why, clang usually tries to be flag-compatible with gcc, but maybe they're not quite equivalent - maybe worth filing a bug against clang asking for an alias. In any case, it works at head because -std=gnu++20 enables coroutines in clang 14.
Regarding boost and compiler detection:
The short version is that clangd is clang-like rather than gcc-like or msvc-like, and is treated/detected as such. It defines __clang__, and only defines gcc/msvc compatibility macros to the extent that clang itself does.
Setting argv0 to gcc/g++/cl.exe is something like "parse flags more like X compiler would, and activate quirks for X compiler" (like -fms-extensions, note that most gcc extensions clang supports are on by default anyway). It doesn't pretend to be that compiler in a deep way. Similarly --query-driver is about extracting implicit -I and -target implied by the argv0, but doesn't extract built-in macros precisely because that would imply some deep emulation.
If the code can't be parsed by clang, then clangd is going to fail to parse it too. So I'm not sure it makes sense to support evading checks - what do we do when we pretend to be GCC, don't use GCC's parser, and users complain their project doesn't work?
The issue here is that the code is explicitly detecting clang and saying it should use a different header, rather than just detecting __has_include(<coroutine>). I don't know why it's doing that. It could be e.g. because clang has insufficient coroutine support (so evading the check won't help).  In any case, we don't really support second-guessing that, for better or worse user code can detect the parser being used and do arbitrary things.

Thanks a lot for the quick response!

Your original minimal example fails with clangd 13 because coroutines are off by default and clang doesn't support GCC's -fcoroutines flag. Clang's flag is -fcoroutines-ts. I'm not sure why, clang usually tries to be flag-compatible with gcc, but maybe they're not quite equivalent - maybe worth filing a bug against clang asking for an alias. In any case, it works at head because -std=gnu++20 enables coroutines in clang 14.

Hmm I will have to double check my actual project, but I don't remember having to set that flag there and it worked fine on macOS. Wondering why that could be the case.

The short version is that clangd is clang-like rather than gcc-like or msvc-like, and is treated/detected as such. It defines clang, and only defines gcc/msvc compatibility macros to the extent that clang itself does.

That's good to know and makes a lot of sense. I guess my initial assumption was that it's compiling fine with gcc and clang normally, so why is it failing with clangd.

Setting argv0 to gcc/g++/cl.exe is something like "parse flags more like X compiler would, and activate quirks for X compiler" (like -fms-extensions, note that most gcc extensions clang supports are on by default anyway). It doesn't pretend to be that compiler in a deep way. Similarly --query-driver is about extracting implicit -I and -target implied by the argv0, but doesn't extract built-in macros precisely because that would imply some deep emulation.

If the code can't be parsed by clang, then clangd is going to fail to parse it too. So I'm not sure it makes sense to support evading checks - what do we do when we pretend to be GCC, don't use GCC's parser, and users complain their project doesn't work?

Yeah that also makes a lot of sense. I guess the issue really lies in the boost code explicitly detecting clang, while we are actually using gcc's libstc++. For now I (mostly) solved the issue by also installing clang and configuring with clang just for clangd. (Not fully solved, but I think the remaining issue is entirely with the library).
Maybe it could be worth mentioning this somewhere in the documentation? (Especially since the actually errors I encountered were quite confusing. The library just turned off coroutine support so clangd was just complaining about missing types.) Maybe something along the lines of: For more complex projects it can make sense to have a separate configure target using clang instead of gcc, so clangd can more accurately parse your code.

The issue here is that the code is explicitly detecting clang and saying it should use a different header, rather than just detecting __has_include(). I don't know why it's doing that. It could be e.g. because clang has insufficient coroutine support (so evading the check won't help). In any case, we don't really support second-guessing that, for better or worse user code can detect the parser being used and do arbitrary things.

Would you say that this is an issue anyways that should be raised with the library? I am not well versed enough in this kind of feature detection to know how one best does this.

Maybe it could be worth mentioning this somewhere in the documentation?

Agree. I'm not sure we can do much about the errors being far away from the problem though - this comes out of the fact that we treat the PP directives are an opaque program that we run, and if they choose not to emit warnings there'll be no warnings. I'm not sure we have great alternatives to this behavior.

Would you say that this is an issue anyways that should be raised with the library?

Yes - I don't know what the fix is because I don't know the motivation for the detection. But it's really on the library to keep this detection as up-to-date as possible.
But in general when the library chooses to do this there isn't that much we can do - the preprocessor metaprogram is fairly opaque, trying to interpret the code in some other way than running it will misinterpret a lot of real code.


[stable/mongodb-replicaset] Add nodeSelector

Add nodeSelector

/ok-to-test

/retest

/retest

CI just times out. Chart installs and tests run successfully on my GKE cluster.

/lgtm


cocco

Dos!x!s!?s?zz
Alalalalslsslslz
z
askslzlz
ZZs

@Showzinha Please describe your issue so I can help you.


quay.io/ceph/ceph:v17.2.2 causes segfault of Ceph Mgr

Describe the bug
The ceph/ceph:v17 container-image (v17.2.2) does not have a fully working Ceph Mgr.
See rook/rook#10627 for more details.

@nixpanic considering the PR is merged, shall we close this issue?

@nixpanic considering the PR is merged, shall we close this issue?

No, we need to track the bug in Ceph(-containers) and use :v17 once it it fixed.

this was fixed with #3275


Unable to update (Create/Edit) MP info for Configurations (2)

Issue: When a user wishes to create/edit a Configuration, the system throws a validation error on the screen and prevents the record from being created
Steps to Reproduce:
Login to ECMPS
On the Select Configurations screen, open and checkout a Configuration under a Facility
Select any one option from the Sections dropdown, click Create and enter information as needed. Click Create
System throws an error (sample below)
image.png
Bug valid for the following sections:
Qualifications - Fail (Creates, but when user clicks on View/Edit the UI crashes)
*Qual Percent - Unable to test due to Qualifications bug
*Qual LEE - Unable to test due to Qualifications bug
*Qual LME - Unable to test due to Qualifications bug
System Component - Fail. UI shows the API Error
Fuel Flow - Fail (Does create, but UI shows error "undefined Internal server error". Edit is fine)
Unit Information - Fail (Section does not load and UI no longer works.
*Unit Fuels, Unit Controls, Unit Capacity - Unable to test due to loading bug)

Original Ticket:
Unable to update (Create/Edit) MP info for Configurations#3410


Default security headers not sent with request.

So the default security headers are not sent with requests, and it doesn't look like there is anyway in the plugin to configure them currently.
https://docs.spring.io/spring-security/site/docs/current/reference/html/headers.html
Just doing some quick looking, it looks like this may have been added in Spring Security 3.2

Hi @virtualdogbert !  Thank-you for the bug report.
Do you recall which version of grails and spring-security-core you were using when you discovered this?

Just did a quick look up, and I think, at the time I think we were at Grails  3.0.9 and spring-security-core 3.0.0, we've since upgrade to 3.2.4 and 3.1.1.

Can you confirm that, since the upgrade, the default security headers are being sent with requests?
spring-security-core version 3.1.x utilizes spring-security version 4.x which should provide the desired functionality.
Thank-you for taking the time to investigate and respond. It's much appreciated :)

Just got back from vacation. I'll see if I can test it this week. I know as a work around we're using an interceptor to add the headers, so I'll have to refamiliarize my self with where that code is and disable it.

Just did a quick check and it looks like it's working.

Thank-you @virtualdogbert 🏅


Clean up CI

We have done quite a lot to clean up the CI. What are some meaningful changes that are left? I think we need:
### Tasks
- [x] [ ] Linting workflow (remove PR comments)
- [x] [ ] Type-check workflow (remove PR comments)

Feel free to agree, disagree, and add to this.

@MartinBernstorff anything else we are missing?
@sarakolding are there any of the workflows we have now that are unclear / need more documentation?

Linting is the same is pre-commit?
What does the test_post_coverage_comment do?

Pre-commit is actions run before committing (this could include testing, linting, static type checking etc.) in our case it is mostly linting though.
so the pre-commit ci == linting in our case, but it might be more clear what it does it we call it linting (and then in the script call pre-commit). @MartinBernstorff and I discussed that we could potentially go away from pre-commit (but it makes linting quite easy as it bundles a lot of workflows in one).

What does the test_post_coverage_comment do?

I believe it created a message with coverage (@MartinBernstorff). Might be worth renaming it so create_coverage_comment, the fact that it is run after the test is then just specified in the file.

so the pre-commit ci == linting in our case, but it might be more clear what it does it we call it linting (and then in thee script call pre-commit).

I think calling it linting would make more sense - that also seems to be the way we do it with other tasks (i.e. naming according to task, not specific package).

@MartinBernstorff and I discussed that we could potentially go away from pre-commit (but it makes linting quite easy as it bundles a lot of workflows in one).

As far as I can tell, the pre-commit workflow includes ruff, black and check-yaml?

Yep also removed that from the swift template.


Using interpretML in a python script

Hi!
I was wondering if it's possible to use the library in a python script. I've tried to do that for shap plots expecting for interpretML to produce a link to a dashboard:
shap = ShapKernel(predict_fn=bbc.predict, data=background_val, feature_names=feature_names) shap_local = shap.explain_local(most_probable.drop(['prediction','probabiltiy','target'],axis=1),                                 most_probable.target, name='SHAP') show([shap_local])
The last line produces:
{'text/html': '\n<a href="http://<IP_ADDRESS>:7974/140466213906184/" target="_new">Open in new window<iframe src="http://<IP_ADDRESS>:7974/140466213906184/" width=100% height=800 frameBorder="0">'} as in jupyter notebook.
However, when I open the link it says this site can't be reached.
Is there a way to call dashboards from the console or the library is to be used exclusively in jupyter?
Thanks!

Find a work around in the issue #16. Closing.


Bullish vs Bearish indicators not checking Open vs Close

For instance, bearishspinningtop returns true for the following data
low: [205],
high: [207.95],
open: [206.16],
close: [207.9],
volume: [5231.61]

I noticed a couple things in the following code:

let bodyLength           = Math.abs(daysClose-daysOpen); // this is good
let upperShadowLength    = Math.abs(daysHigh-daysOpen); // this should be daysHigh - Math.max(daysOpen, daysClose)
let lowerShadowLength    = Math.abs(daysHigh-daysLow); // this should be Math.min(daysOpen,days.close) - daysLow
let isBearishSpinningTop = bodyLength < upperShadowLength &&
  bodyLength < lowerShadowLength; // this should include check for daysClose < daysOpen

it wasn't explicitly checking if open < close (definition of bearish in this case)
the shadow calculations were off (comments in code above)

Would you like me to start a PR to go through and fix these?  I'm very interested in getting all these working for my project and would prefer to contribute to your lib rather than fork to correct.

@kwhitley Sure provide a pull request. Make sure you update the test. Let me know if you face any issue setting up the workflow.

Will do @anandanand84
As to the work environment, I needed to run the following (OSX) before npm install would complete successfully:
brew install cairo
xcode-select --install

...and to fully install (to run npm test)
npm install --save-dev draw-candlestick@^1

These will be included in the README update with the PR if you don't mind!

Also, should I be working on the .ts files in /src or the .js files in /lib?  I don't see a script in the package.json to transpile TypeScript into the lib folder (where the tests are being run from), and am generally unfamiliar with TypeScript dev/build processes.

Nevermind, read some TS docs and will add that step to the README as well:
# install typescript
npm install -g typescript

# run typescript within project to build from ./src to ./lib for testing
tsc

@kwhitley sorry for the late reply. glad you figured that out. I would recommend vscode https://code.visualstudio.com  vscode come with typescript support so you dont have to run the tsc command every time and I missed the draw-candlestick and cairo installation part which are necessary for developement that gives you the image of the test data so it is easy to develop new patterns. It would be helpfull if you add it to the readme along with pr. Thanks


[FEATURE] Add LAMB optimizer

Description
The LAMB optimizer:
It has been proposed in Reducing BERT Pre-Training Time from 3 Days to 76 Minutes.
A simple neural network has been used for verification, and the results show that the model can converge normally with large batchsize. Need to be verified further on the BERT.
@eric-haibin-lin  Verification may require your help because of some computing resource limitations.
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[x] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Job PR-733/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-733/1/index.html

Job PR-733/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-733/2/index.html

Job PR-733/3 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-733/3/index.html

Job PR-733/4 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-733/4/index.html

Job PR-733/5 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-733/5/index.html

Job PR-733/6 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-733/6/index.html

Job PR-733/10 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-733/10/index.html

Job PR-733/11 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-733/11/index.html


add toba-kosen

I can prove my domain.
Our college is also called Toba Kosen.This collage is affiliated with the National Institude of Technology.
So, Whois Infomation is the same of Toba Collage.
Here is our collage's official web site.
http://www.toba-cmt.ac.jp/
And I’m sorry, I can’t show you any reference page saying we use the domain. There’s no page about that anywhere.
In addition, I show you WHOIS information about toba.kosen-ac.jp.(from http://whois.jp/)

Domain Information: [ドメイン情報]
[Domain Name]                   KOSEN-AC.JP
[登録者名]                      独立行政法人　国立高等専門学校機構
[Registrant]                    National Institute of Technology, Japan
[Name Server]                   ns1.dns.ne.jp
[Name Server]                   ns2.dns.ne.jp
[Signing Key]
[登録年月日]                    2015/02/23
[有効期限]                      2018/02/28
[状態]                          Active
[最終更新]                      2017/06/02 15:19:54 (JST)
Contact Information: [公開連絡窓口]
[名前]                          独立行政法人　国立高等専門学校機構
[Name]                          National Institute of Technology, Japan
[Email]<EMAIL_ADDRESS>[Web Page]
[郵便番号]                      193-0834
[住所]                          東京都八王子市
東浅川町701-2
[Postal Address]                Tokyo
Hachioji-shi
701-2 Higashiasakawa-machi
[電話番号]<PHONE_NUMBER>
[FAX番号]

The attached picture was distributed to students.This is explaining how to use mail address of toba.kosen-ac.jp in office365.

@JUNNETWORKS Thank you for the clarification! The attached picture, which was distributed to students, is fine. Pull request merged. Thanks a lot!


Support for declaring items types in empty array

I dont seem to be able to figure out how properly declare that items within an array have a type unless my array object in values.yaml has an array with those objects declared.  But I want the default to be [].
For example:
domains: []
# - domain.com
# - domain.co

results in domain: { type: array }
I want to be able to make this become domain: { type: array, items: { type: string }}

@ryan-dyer-sp I've added support to set Items type from comment. you can use it like this:
imagePullSecrets: [] # @schema item: object

which will generate json schema:
"imagePullSecrets": {
    "items": {
        "type": "object"
    },
    "type": "array"
},

You need to update plugin version to 1.2.2


Supporting deployment and managing of cloud-functions

Cloud functions are used in different Mausbrand projects to provide dedicated, secure functionality for specific things.
A nice enhancement for viur-cli would be to manage these cloud functions as well.

Is handled with #98


Push route without context?

I am wanting to push a route without context (vrouter.to("PATHHERE")). Is this possible?

Is this what you are looking for?

Thank you!


Adjust width of report table

Commited:
https://github.com/chaineco/blockcare/commit/94c1b11016336c9198874cbb08890295733d1ccd


💡 [REQUEST] - Seperate Quasar Plugin Configuration

Describe the feature

Make quasar vue plugin configurable via separate file (Use app.config.ts maybe?). This should make it possible to configure plugin without restarting the nuxt server. @nuxtjs/i18n achieves this via importing the configuration file from a dynamically generated file created at startup. But will probably simpler to use app.config.ts.
Should support nuxt layers.
Plugin configuration include lang, iconSet and following properties.
Deprecate nuxt.config.ts equivalents, prioritize the properties present in config file. (app.cfg > layers > nuxt.cfg)

// app.config.ts
export default defineAppConfig({
  quasar: {
    brand: {
      // ...
    }
  }
})

Additional information

[ ] Would you be willing to help implement this feature?
[ ] Does this feature have a potential to break existing features?

Happy new year!!! 🔥🎉
I'm curious, why no quasar.config.ts? app.config.ts would imply it is a nuxt or app configuration...
I'm preparing a feature request for nuxt, in which we add an array of configuration files (matching the modules configKey, and nuxt will pick up the corresponding module.config.ts file.
Like:
nuxt.config.ts
export default defineNuxtConfig({
  modules: ["nuxt-quasar-ui"],
  configFiles: ['quasar'],
})

Then each nuxt module can provide a defineXConfig composable:
quasar.config.ts
export default defineQuasarConfig({
   plugins: [
      'Notify', 'Dark', 'Dialog'
    ],
    extras: {
      font: 'roboto-font',
      fontIcons: ['fontawesome-v6', 'material-icons']
    },
    iconSet: 'material-icons',
})

That way nuxt.config.ts doesn't become a monolithic monster. 👀
Otherwise each module author will use different approaches, some would use a module.config.ts file, others will use the  module options in nuxt options, and this will result in lack of consistence
and in a mental overhead thinking "will this module check for a module.config.ts file, or will I need to add the configuration in nuxt.config.ts? 🤔😵💫" every time we install a module.
For now, each module in my opinion should check if there's a module.config.[ts,js,mjs,json] file first, then check if there's a module options in nuxt options. Nuxt authored modules configuration should follow the same approach other technologies follow for their configuration, like .npmrc, .eslintrc, .prettierrc, nest-cli.json, i18n.config.ts, etc.
Is there a config file? Use that. Isn't there a config file? Check in nuxt.config.ts for a module option.
This way, people who prefer a monolithic approach, and people who prefer a modular approach, will all be happy.
Not always we can have everyone happy, but I think this time we can haha. 😅
Final Words
nuxt-quasar-ui keeps getting better! Great job being done 🔥🤝💚💙

Happy New Year!

I'm curious, why no quasar.config.ts? app.config.ts would imply it is a Nuxt or app configuration...

As context regarding my opening of this issue, I was dissatisfied with how configurations unrelated to the Nuxt build phase were bootstrapped in nuxt.config.ts. Even basic things like changing the default color of the LoadingBar required a full server restart.
So, the first thing I thought of was allowing users to define these configurations via a separate file (namely quasar.config.ts). However, I didn't initially know how to achieve this, so I put it on hold due to a tight schedule. After quite a while, I discovered that @nuxtjs/i18n did something similar via i18n.config.ts, giving me an example to work with.
As I started working on it, I quickly realized that I had to handle all the stuff related to managing that new configuration file. For example, tracking the existence of configuration files between layers, merging said configurations, implementing composables to define, use, and update configurations at runtime. Of course, these are not very demanding tasks, but while thinking about this, I also had a slight concern about whether this new configuration file would create confusion with the actual quasar.config. Moreover, it's another configuration file that might lead to bloat.
Then I looked at app.config.ts since it handled all of these things out of the box. However, I wasn't sure if other modules leveraged app.config.ts to handle runtime configurations and if it would be acceptable for this module to do so, since my initial perception was that app config was meant for application developers to configure their, well... app.
After looking around at other modules, I found out that nuxt-icon was using app.config.ts to handle <Icon> component's runtime behavior. The initial issue which proposed the idea of app.config.ts also suggests that it could be used by module authors to integrate their modules and handle all its hot-reloaded configuration needs. With these in mind, I felt like using app config would be the best and most practical choice.
Regarding your feature proposal, I do not think it is necessary. You can simply separate module configurations yourself and import them from nuxt.config.ts. Plus, there is also the distinction between build and runtime configurations. For example, @nuxtjs/i18n handles build configurations in nuxt.config.ts via the i18n config key, while runtime configurations (mostly vue-i18n plugin configurations) are handled in i18n.config.ts.
Thank you for your feedback, and let me know your final thoughts on this topic.

Happy New Year!

I'm curious, why no quasar.config.ts? app.config.ts would imply it is a Nuxt or app configuration...

As context regarding my opening of this issue, I was dissatisfied with how configurations unrelated to the Nuxt build phase were bootstrapped in nuxt.config.ts. Even basic things like changing the default color of the LoadingBar required a full server restart.
So, the first thing I thought of was allowing users to define these configurations via a separate file (namely quasar.config.ts). However, I didn't initially know how to achieve this, so I put it on hold due to a tight schedule. After quite a while, I discovered that @nuxtjs/i18n did something similar via i18n.config.ts, giving me an example to work with.
As I started working on it, I quickly realized that I had to handle all the stuff related to managing that new configuration file. For example, tracking the existence of configuration files between layers, merging said configurations, implementing composables to define, use, and update configurations at runtime. Of course, these are not very demanding tasks, but while thinking about this, I also had a slight concern about whether this new configuration file would create confusion with the actual quasar.config. Moreover, it's another configuration file that might lead to bloat.
Then I looked at app.config.ts since it handled all of these things out of the box. However, I wasn't sure if other modules leveraged app.config.ts to handle runtime configurations and if it would be acceptable for this module to do so, since my initial perception was that app config was meant for application developers to configure their, well... app.
After looking around at other modules, I found out that nuxt-icon was using app.config.ts to handle <Icon> component's runtime behavior. The initial issue which proposed the idea of app.config.ts also suggests that it could be used by module authors to integrate their modules and handle all its hot-reloaded configuration needs. With these in mind, I felt like using app config would be the best and most practical choice.
Regarding your feature proposal, I do not think it is necessary. You can simply separate module configurations yourself and import them from nuxt.config.ts. Plus, there is also the distinction between build and runtime configurations. For example, @nuxtjs/i18n handles build configurations in nuxt.config.ts via the i18n config key, while runtime configurations (mostly vue-i18n plugin configurations) are handled in i18n.config.ts.
Thank you for your feedback, and let me know your final thoughts on this topic.

Yes you're right! 🤯


[EventHubs] Fix broken tests

Open this PR to fix the broken tests in eventhubs as it turns out the sanitizer that we use in eventhubs' test will accidently applies to the tag operation's test recording and make the assertion fail.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

Can you update here as well? The test is ignored, no re-recording needed. But when it's added back, it will have the same issue.
https://github.com/Azure/azure-sdk-for-net/blob/100aedb7e84c9ffb1aaeb3770ad9e57c0d45daca/sdk/eventhub/Azure.ResourceManager.EventHubs/tests/Tests/EventHubClusterTests.cs#L68-L70

API change check
API changes are not detected in this pull request.


Add yaml imports

imports:
  - path: ../other-project/gmakec.yaml
    # filter by target, omit for full import
    targets:
      - target1
      - targrt2

Maybe we need (sub)project dependencies instead...

Each gmakec.yaml file needs to be configured & built before the actual one is even parsed.

Maybe something like a configure/build context for each yaml can solve the problem.

Fixed in https://github.com/thetredev/gmakec/commit/1a295bd66de8f113b525bde6cf36fdbc05c3061a


64x64 p3 ghosting/double ing

Hi,
I am trying to use 64x64 p3 panel.
One piece, single panel.
It's connector starts with R1 pin.
I connected all pins according your explanation(thank to your very detailed connection example)
The problem is panel has ghosting or double ing issue. I don't know how to say in one word but let me explain the issue:
Is I use first 16 line(16x64) everything is ok on this are but next 16 line(16-32x64) is getting same thing i draw/write on first part.
Also it's same for second half of panel too...
It's like I have 4  16x64 panel and first two showing same thing and second two is showing same thing.
If I write "2dom" in first 16x64 I will have:
1* 16x64= -----2dom-----
2* 16x64= -----2dom-----
3* 16x64= -------------------
4* 16x64= -------------------
Did I over-explain? :)

Also I can't draw/write on second and last part of panel.
They are only copying things from first and third part.

Just saw this issue on GitHub...did you solver your problem? How?

i figured out new function of your library!
if someone need copy first row to second and third row to fourt they just can use my trick...
#define P_E 2
#define P_OE 0
:D


[SPARK-19799] Support WITH clause (CTE) in subqueries

Because of SPARK-17590 support of WITH clause (CTE) in subqueries requires only grammar support.
Test for augmented syntax is provided.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Test build #98453 has started for PR 22936 at commit 66cd537.

Test build #98453 has finished for PR 22936 at commit 66cd537.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98453/
Test FAILed.

Test build #98568 has started for PR 22936 at commit 5377087.

Test build #98568 has finished for PR 22936 at commit 5377087.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98568/
Test FAILed.

Test build #98569 has started for PR 22936 at commit 3080ed4.

Test build #98569 has finished for PR 22936 at commit 3080ed4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98569/
Test PASSed.

@gbloisi Any update?

@chrysanxia Could you take over this?

@gatorsmile @gbloisi @chrysanxia may I take over this?
I played a bit with recursion support recently:
https://github.com/apache/spark/pull/23531# and during porting https://github.com/postgres/postgres/blob/master/src/test/regress/sql/with.sql I also found that WITH is not supported in subqueries https://github.com/apache/spark/pull/23531#discussion_r249968739 (point 6).

@gatorsmile here is my PR: https://github.com/apache/spark/pull/24831


ImageViewer does not seem to use images cached to disk, causing a slow loading

Hi @ascoders ,
I used your ImageViewer component in other apps and everything works fine, but in the last app I'm developing I'm using Firebase Storage to allow users to upload photos.
ImageViewer does not seem to use images cached to disk if I use a Firebase Storage URL. This causes a slow loading and black screen long duration when the modal is open.
So, is there a way to avoid this slowdown on the component side?
If you want, I can send you a test URL by e-mail.

See #26 or #3

@ascoders thank you for the answer.
Can I alternatively use react-native-cached-image?
If I use cachable-image, how to it implement using ImageViewer component? I'm confused.
Finally, why do not you use FastImage in react-native-image-zoom?

Here is how I use FastImage for image caching
renderImage={(props) => (
    <View style={{width: '100%', height: '100%', marginTop: moderateScale(-100)}}>
        <FastImage
            style={{width: '100%', height: '100%'}}
            source={{
                uri: props.source.uri,
                priority: FastImage.priority.normal,
            }}
            resizeMode={FastImage.resizeMode.contain}
        />
    </View>
)}

Here is how I use FastImage for image caching
renderImage={(props) => (
    <FastImage
        {...props}
        style={{width: '100%', height: '100%}}
        source={{
            uri: props.source.uri,
            priority: FastImage.priority.normal,
        }}
        resizeMode={FastImage.resizeMode.contain}
    />
)}

This reduced the performance of my app. Things got working Ok after I uninstalled it. Please what could have caused it?

althought using FastImage, this library still takes time to calculate some layout before render. i saw it  in code.

set width & height to imageUrls itemes
imageUrls={[
  {
     url: media.url,
     width: Utils.dimentions.width,
     height: Utils.dimentions.height,
   },
]}

then use FastImage component:
<FastImage
        {...props}
        style={{width: '100%', height: '100%}}
        source={{
            uri: props.source.uri,
            priority: FastImage.priority.normal,
        }}
        resizeMode={FastImage.resizeMode.contain}
    />
)}

althought using FastImage, this library still takes time to calculate some layout before render. i saw it in code.

https://github.com/ascoders/react-native-image-viewer/issues/293#issuecomment-869171408


Anima patch support

Support for showing an infobox for the anima patch.
Let me know if you want me to take a different approach to isolating the patch.
The plugin is coupled pretty tightly to Time Tracking's tabs, so spoofing a tab seemed the path of least resistance.
Resolves #42

LGTM, could you resolve the conflicts with master?
Also if you feel like maintaining this for a longer period of time, please let me know and I can give you contributor permissions.

LGTM, could you resolve the conflicts with master?
Also if you feel like maintaining this for a longer period of time, please let me know and I can give you contributor permissions.

Yea sure, I'd be happy to help maintain this.


Add support for SapMachine bulids

Make build process accept SapMachine variant to build from github.com/SAP/sapmachine
I am assuming the default branch of sapmachineis the correct one to use.
I've also got a fix for the fact that a git error is currently thrown when the option not to do a shallow clone is specified, as (at present) that option is required to get around another issue in the SAP build (it tries to do a git log HEAD^ which doesn't work on a shallow clone
Note to reviewers: I've made the variant option SapMachine - with hindsight perhaps it's better to leave it all lower case as sapmachine instead
Note 2 to reviewers: The two if statements for the variants could be replaced with a case ...
Note 3: This has been tested through the following job: https://ci.adoptopenjdk.net/view/work in progress/job/SAPmachine10_build_x86-64_linux/ which I can move into the main build tab once this is accepted and the job is modified not to pull from my fork of this repository :-)

Just a side comment, I think trying to invoke --jtreg via the build script might not be a good think going forwards, we should make that an independent process.
In a way its making the build script brittle and we have to maintain this link each time we make changes of this nature.
jtreg.sh maintained on its own is more beneficial than via a call from within the build script which we may have intended in the past but never ever have used it in this effect.
What does everyone think about this, in favour of testing and maintaining both build and test scripts.

We are running the openjdk regression tests (https://ci.adoptopenjdk.net/view/OpenJDK tests/) as a separate test build where we call jtreg directly per test group jdk_io, jdk_lang, jdk_beans, etc, so its already independent in that respect.
The one downside is that we do not have test machines for all platforms, once this is addressed, you may wish to not run the --jtreg option as part of the build as we duplicate testing, and increase build time.  I have created this test build https://ci.adoptopenjdk.net/view/work in progress/job/openjdk10_sap_openjdktest_x86-64_linux/ which will be triggered by the SAPmachine build that @sxa555 just added.  It will run all of the openjdk regression tests (minus the ones we have excluded due to known issues).

Would also prefer the build job name follow the same naming convention as other builds (as there seems to be one), so expected it to be named openjdk10_sap_build_x86-64_linux

@smlambert Thanks for sharing this with us, and yes let's do as you suggest
@sxa555 is it possible to apply the goodness of your work to other build types, platforms and OSes?

@neomatrix369 The changes were pretty straightforward and will work for any platform we choose to build on. The only issue (which may be a non-issue anyway!) is that the applyingJCovSettingsToMakefileForTests() function in jtreg.sh doesn't work as they don't have a jdk/test directory in their v10 source (ours does). So I'm going to leave that "broken" for now as it's not a prereq to getting a build out.
FYI Have created https://github.com/AdoptOpenJDK/openjdk-build/issues/218 for any further discussions since that's a better place for it than a PR for tracking purposes. I'll make my job available in the main build tab on jenkins as openjdk10_sap_build_x86-64_linux as @smlambert suggests for now and anyone can object in that issue if they so desire :-)


Support carriage return "\r" in blocks language

Resolves #1090

What about \r\n? This should be considered as one Enter only.

A possible way to handle that, which is not so beautiful, would be calling String.replace(target, replacement); method.


Support mjs by default

Is your feature request related to a problem? Please describe.
import * as utils from 'utils-ts'
console.log(utils)

it will throw an error:
Error: ENOENT: no such file or directory, stat '/Users/foobar/my-react-project/node_modules/utils-ts/dist/utils-ts.js'

The package.json of utils-ts is:
{
  "name": "utils-ts",
  "version": "0.1.0-alpha.3",
  "types": "./dist/utils-ts.d.ts",
  "main": "./dist/utils-ts.cjs",
  "module": "./dist/utils-ts.mjs",
  "exports": {
    ".": {
      "import": "./dist/utils-ts.mjs",
      "require": "./dist/utils-ts.cjs",
      "default": "./dist/utils-ts.cjs"
    }
  }
}

Describe the solution you'd like
Support .mjs by default.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

In react app, we use src as root.
https://github.com/vitejs/vite/blob/91f829dc1bfb5c1ed8411751b31f17c2322ed0a7/src/node/resolver.ts#L180-L183
So we can't resolveNodeModuleEntry from src/package.json


v15 installation issues

Hello
i installed on Ubuntu 22.04 it did not give me any error during installation, at the end it gave me success message but, it did not work, simply didnt work.
currentsite.txt is not created and i restarted bench with bench restart command here is what i get
frappe-bench-workers:frappe-bench-frappe-schedule: stopped
frappe-bench-workers:frappe-bench-frappe-short-worker-0: stopped
frappe-bench-workers:frappe-bench-frappe-long-worker-0: stopped
frappe-bench-web:frappe-bench-frappe-web: stopped
frappe-bench-workers:frappe-bench-frappe-schedule: started
frappe-bench-workers:frappe-bench-frappe-short-worker-0: started
frappe-bench-workers:frappe-bench-frappe-long-worker-0: started
frappe-bench-web:frappe-bench-node-socketio: ERROR (spawn error)
frappe-bench-web:frappe-bench-frappe-web: started
ERROR: supervisorctl restart frappe-bench-workers: frappe-bench-web:
subprocess.CalledProcessError: Command 'supervisorctl restart frappe-bench-workers: frappe-bench-web:' returned non-zero exit status 7.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/bin/bench", line 8, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.10/dist-packages/bench/cli.py", line 132, in cli
    bench_command()
  File "/usr/local/lib/python3.10/dist-packages/bench/commands/utils.py", line 41, in restart
    Bench(".").reload(web, supervisor, systemd)
  File "/usr/local/lib/python3.10/dist-packages/bench/utils/render.py", line 126, in wrapper_fn
    return fn(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/bench/bench.py", line 152, in reload
    restart_supervisor_processes(bench_path=self.name, web_workers=web, _raise=_raise)
  File "/usr/local/lib/python3.10/dist-packages/bench/utils/bench.py", line 321, in restart_supervisor_processes
    failure = bench.run(f"{sudo}supervisorctl restart {group}", _raise=_raise)
  File "/usr/local/lib/python3.10/dist-packages/bench/bench.py", line 48, in run
    return exec_cmd(cmd, cwd=cwd or self.cwd, _raise=_raise)
  File "/usr/local/lib/python3.10/dist-packages/bench/utils/__init__.py", line 158, in exec_cmd
    raise CommandFailedError(cmd) from subprocess.CalledProcessError(return_code, cmd)
bench.exceptions.CommandFailedError: supervisorctl restart frappe-bench-workers: frappe-bench-web:

Ok, seems like i won't get ant respond, but i will note my proceedings.
i think this script doesn't work right on newly fresh installed systems, too many things to install, update and upgrade that can not be configured all at the same time even you run update and upgrade command before you start running the script.
so i deleted frappe_bench folder and re-run the script, i will see what is next, and i will keep informing you.

@washaqq Your first attempt most likely resulted in an error somewhere during the process, which went unnoticed. The  What I recommend when this happens is exactly what you have already done, so watch out for the process and see if any error is displayed during the installation process.
The script doesn't currently handle errors when they occur during installation so your first attempt could have resulted in an error which you may not have noticed. A newer version of the script is currently in the works with significant error handling capabilities. The new version will be deployed as soon as all stability tests are completed.

@washaqq your last attempt failed because of the changes in this file /etc/supervisor/supervisord.conf which suggests that the installation was successful. please run bench doctor in your frappe-bench directory and let me know if bench is running.

@washaqq your last attempt failed because of the changes in this file /etc/supervisor/supervisord.conf which suggests that the installation was successful. please run bench doctor in your frappe-bench directory and let me know if bench is running.

@flexcomng
here is the result;
-----Checking scheduler status-----
Workers online: 2
-----None Jobs-----

Can you try to access your site?

Can you try to access your site?

i access the site after i saw the message, it seems working now, so what is the problem that it did not work on first and second try?

I'm happy your installation is now working. As I said earlier, because the script currently does not log errors, it is difficult to say what exactly could have happened without actually monitoring the installation process. My best guess at this point is package installation failure which prevented the site from installing successfully the first time. The new version of the script, when released, will solve this loophole.

thank you for this great script, even i have problems, it took less than the other manuel installation. Can't wait the new release.


Possible to migrate from binary to source?

I'm am currently running gogs from binary, is it possible to upgrade it using sources?
Currently I tried to restore a backup made by the binary version of gogs, but it fails like in https://github.com/gogits/gogs/issues/4797

Had to compile gogs with tags (sqlite) https://gogs.io/docs/installation/install_from_source#build-with-tags and then restore went fine.


Prepare for Bond 11.0 release

Resolves https://github.com/microsoft/bond/issues/1131

Please do not merge yet. Some other changes will be needed before this release is ready.

This work will need to be restarted at a later date.

Resolves https://github.com/microsoft/bond/issues/1131

https://github.com/microsoft/bond/commit/29c47af2bd98ac794ea441ab23098b203c4f3a15


razorpay recurring payments

recurring payment options not available. Is any future plan to support recurring payment in this repo?

Support for subscriptions has been added.


Update junit

Had to rename assertThrows in our custom Asserts class because the
Assert base class (inherited from in ESTestCase / LuceneTestCase)
added a new assertThrows method that broke the method resolution.
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Looks good, could be maybe also something like assertThrowsSqlError and we could include isSqlError directly.

Good idea. Something to follow up on? Would even trim it down to just assertSqlError.

Looks good, could be maybe also something like assertThrowsSqlError and we could include isSqlError directly.

Good idea. Something to follow up on? Would even trim it down to just assertSqlError.

Yes sure. I can do this as a follow-up.


Mac OS 9 - No Image, Even Address Bar

Been trying to figure this out for a while now. I'm running Mac OS 9.2.2 on my iBook G3, trying to get Browservice (running on Windows) to work. However, when I connect to the server through a browser, it connects, but displays nothing, not even the address bar. It does this with Classilla 9.3.3, Internet Explorer 4.5 (I've also tried 5.0 and 5.5, but those have that issue of looping between pages), Netscape 6.2.1, Netscape 7.0.2, and Opera 6.03. I've tried these arguments:
--chromium-args=use-gl=disabled
--chromium-args=use-gl=egl
--chromium-args=use-gl=angle
--chromium-args=use-gl=swiftshader

As well as some others. I've also tried it on my PowerMac G4, which gives the same issues I've tried running the 32-bit version, which didn't help. I've also tried using directories, connecting to something like:
http://xxx.xxx.xxx.xxx:8080/goto/google.com

Doing this, it still does not display anything. I've also tried doing it on the host (connecting to the server from my Windows computer), which does work. Hell I've even tried connecting them with a different ethernet cable. So based on all of this information:

It's not the browser, as I've tried it with many different browsers
It's not the computer, as I've tried it with different computers
It's not the operating system, based on other posts I've found where people had no issue getting an image running different browsers in Mac OS 9.2.2 and Mac OS 9.2.1
It's not the server, since if it was, it wouldn't work connecting from the host

So, why does it not work then? What am I missing? I don't think it's the connection between the machines, as every web browser says it connects, and I've replaced the cable, but still it seems to me like the most likely option.

It seems we are together (#55) in this. Just to rule out any possible connection issues, have you tried running the server with --vice-opt-http-listen-addr=<IP_ADDRESS>:8080?

I just tried using a listening address of <IP_ADDRESS>:8080, and it gave a "connection was refused" error

classilla has noscript, did you try enabling scripts globally? that's what fixed this for me

however, even then, there are some remaining issues. see #32 and #33

yep, i found it strange as well. no problem. now that it seems to work for you, are you getting an issue with resizing?

There is indeed this strange issue where the Classilla window can't decide whether or not to include scroll bars, and keeps switching back and forth between both states unpredictably.

ok same here, i'm going to try to test this commit today which apparently should fix the issue, cc @ttalvitie

Tried enabling scripts globally in Classilla, and it does work, but yea, has the resizing issue.

is anyone able to build browservice with the code change i highlighted above and test that it works? i still can't get it working

@luquillito In this case, you only need to rebuild retrojsvice.so/retrojsvice.dll (replacing the library in the binary release package), as it is the only part that the change affects. This should be a bit easier than rebuilding the complete Browservice package as it does not require CEF.
However, for this change, a binary patch may be the easiest solution: just replace
var bodyOverflowHiddenNotSupported = false;
by
var bodyOverflowHiddenNotSupported = true ;
(It is important to keep the length same to avoid breaking the binary; that's why we add an extra space after true.)
Instructions on how to patch:

Download the Browservice v<IP_ADDRESS> release package
If on Windows:

Extract the release package.
Open Git Bash/Cygwin in the extracted directory.
Run the following commands:mv retrojsvice.dll retrojsvice_orig.dll
sed -b 's/var bodyOverflowHiddenNotSupported = false;/var bodyOverflowHiddenNotSupported = true ;/g' retrojsvice_orig.dll > retrojsvice.dll

Start browservice.exe in the extracted directory normally.

If on Linux:

Move the release package to an empty directory.
Open terminal in the directory containing the release package.
Run the following commands (replacing x86_64 with the correct architecture, if necessary):./browservice-v<IP_ADDRESS>-x86_64.AppImage --appimage-extract
mv squashfs-root/opt/browservice/retrojsvice.so squashfs-root/opt/browservice/retrojsvice_orig.so
sed -b 's/var bodyOverflowHiddenNotSupported = false;/var bodyOverflowHiddenNotSupported = true ;/g' squashfs-root/opt/browservice/retrojsvice_orig.so > squashfs-root/opt/browservice/retrojsvice.so

Run Browservice using squashfs-root/AppRun instead of the AppImage:squashfs-root/AppRun OPTIONS...

Let me know whether this fixes things; if it does, then we could add the fix to the next mainline release.
(And it seems I should really try to improve the instructions and tools for building Browservice so that we wouldn't have to resort to binary patches 😅)

@ttalvitie i can confirm this fixed the issue for me

The resize issue should be fixed in v<IP_ADDRESS>.


Will ASP.NET Core still support DisplayMode?

DisplayMode in ASP.NET MVC 5 is very useful feature. But we couldn't found it in ASP.NET Core.
Have any plan to support DisplayMode in ASP.NET Core?

Found similar question in https://github.com/aspnet/Razor/issues/751

There aren't any plans to bring back Display Modes. I just commented on https://github.com/aspnet/Razor/issues/751 so we can keep the discussion going on there. Thanks!


Generalize Error Handling

Description
This adds a more generalized error handling by placing the former handle(error: Error function in a Struct, and intializes an example on the RegisterViewModel. This intitialzation method allows for us not to have to call the struct up the chain to the parents and an instance is intalizied when the ViewModel is called.
This also adds a more generalized Enum and adds a custom case to allow users to create general, customized error messages that can be thrown via the toast.
Testing Steps

Locate the SuccessMockRegisterService struct located in RegisterNetworking on line 49 and add the following before the return on line 56.
throw BaseError.custom(reason: "Your error message here")
Launch application, attempt to register a user.
View error thrown as a toast message.
Remove added throw.
Attempt to register again, ensuring that you get a success.

Areas of Code Impacted
Error handling.
Other Notes/Considerations
N/A

We have updated to having a few protocols to help handle errors or logging. There are ErrorHandling and ScribeLogging for error handling and logging. Both ErrorHandler and Scribe allows for plugins to be added.


Map ASCII codes to font?

Hey there. I've been attempting to use graphical tiles in my tcod-rs based game. I found this wiki article outlining how this can be done with the Python version of tcod but I've gotten stuck replicating these instructions with these Rust bindings.
I'm loading the custom font with the following form of the Root's builder:
let mut root = Root::initializer()
    .font("TiledFont.png", FontLayout::Tcod)
    .font_type(FontType::Greyscale)
    .font_dimensions(32, 10)
    .size(SCREEN_WIDTH, SCREEN_HEIGHT)
    .title("Roguelike")
    .init();

But when it comes to the wiki's next step of using map_ascii_codes_to_font, I get stuck. I searched the repository but it seems like the only reference to this method is in the tcod-sys crate which does not seem to be publicly exposed. Additionally, the method doesn't seem to be called by any publicly available functions.
Am I missing something or is there no way to accomplish this at this moment? If it's currently missing, do you have any thoughts on how this can/should be implemented? Perhaps keeping it within the Root's builder pattern as with custom fonts? I'm happy to help out with a PR!

I looked into the map_*_to_font functions and it seems like they should be called after the Root console has been initialized. This would mean that they need to be added as methods taking &mut self to Root here.
Unfortunately I don't have the time to implement them right now but you can look at the existing functions at the linked location if you'd like to send a PR.

Yep. And to hopefully clarify your confusion: tcod_sys contains the direct unsafe bindings to libtcod. They were generated automatically and should have all the libtcod functions with identical names.
The tcod crate uses these to provide higher-level bindings that are hopefully safer and look more like Rust and less like C. These are not complete yet and some things such as the map_ascii_codes_to_font function are not there yet.
If you add "tcod-sys" in your dependencies and use extern crate tcod_sys, you should be able to call the raw functions within an unsafe block.
So the line in the tutorial would look something like this:
unsafe {
    tcod_sys::TCOD_console_map_ascii_codes_to_font(a, 32, 0, y);
}

You can use that for now, but I would happily merge a pull request that adds these to tcod proper.
You can check this function out as a reference for what it would look like:
https://github.com/tomassedovic/tcod-rs/blob/master/src/console.rs#L239
And the corresponding tcod_sys function:
http://tomassedovic.github.io/tcod-rs/tcod_sys/fn.TCOD_console_set_keyboard_repeat.html

When using this above, everything works just fine until I attempt to actually display a tile to the screen, at which point I get a segmentation fault. Here is the info:
Process:               skyspace [12013]
Path:                  /Users/USER/*/skyspace
Identifier:            skyspace
Version:               0
Code Type:             X86-64 (Native)
Parent Process:        ??? [12012]
Responsible:           skyspace [12013]
User ID:               501

Date/Time:             2017-07-10 15:15:31.525 -0700
OS Version:            Mac OS X 10.12.5 (16F2073)
Report Version:        12
Anonymous UUID:        80AAD2AE-F073-4C6B-6A45-3585EEB0F319

Sleep/Wake UUID:       1D92D166-404F-4273-ADF0-1BFEB3BBB2FA

Time Awake Since Boot: 42000 seconds
Time Since Wake:       9800 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x00000001021f6e00
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Bus error: 10
Termination Reason:    Namespace SIGNAL, Code 0xa
Terminating Process:   exc handler [0]

VM Regions Near 0x1021f6e00:
    VM_ALLOCATE<PHONE_NUMBER>1f5000-00000001021f6000 [    4K] rw-/rwx SM=PRV
--> VM_ALLOCATE<PHONE_NUMBER>1f6000-00000001021f7000 [    4K] r--/r-- SM=PRV
    MALLOC metadata<PHONE_NUMBER>1f7000-00000001021f8000 [    4K] r--/rwx SM=ZER

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libtcod.dylib                 	0x0000000101f59c84 TCOD_sys_console_to_bitmap + 2196 (sys_sdl_c.c:737)
1   libtcod.dylib                 	0x0000000101f5baa4 TCOD_sys_render + 1348 (sys_sdl_c.c:607)
2   libtcod.dylib                 	0x0000000101f5b454 TCOD_sys_flush + 84 (sys_sdl_c.c:1312)
3   libtcod.dylib                 	0x0000000101f2c022 TCOD_console_flush + 98 (console_c.c:240)
4   skyspace                      	0x0000000101e36569 tcod::console::Root::flush::h251df1bfc759ef50 + 25 (console.rs:327)
5   skyspace                      	0x0000000101e11f62 skyspace::draw::draw_map + 4242 (mod.rs:109)
6   skyspace                      	0x0000000101e1bb5e skyspace::main + 1134 (main.rs:146)
7   skyspace                      	0x0000000101e433fd __rust_maybe_catch_panic + 29 (lib.rs:106)
8   skyspace                      	0x0000000101e428a5 std::rt::lang_start::hbfec38d925b4a67f + 485 (rt.rs:59)
9   skyspace                      	0x0000000101e1db3a main + 42
10  libdyld.dylib                 	0x00007fff91cab235 start + 1

@christopherdumas  libtcod with the SDL backend on OSX hasn't been the most reliable thing historically. Could you try running it with the OpenGL backend just to see if it's an error in libtcod or the Rust library?
Also could you share a minimal repro to see if we/I can reproduce it?

My actual project is here. In assets, the master16x16_ro.png has the tileset/font, and my tile loading logic is in src/main.rs at the top of the file. I tried using OpenGL, GLSL, and SDL, and all three crash on my attempt to use the tiles that I mapped. You can see my mapping code in worldgen/terrain.rs near the top of the file (after the imports). I also have another problem, which is that when I turn off tiles, it doesn't crash, but all text is shifted down roughly two and a third lines.

As you can see in that image, not only are characters wrong, but they are taking small clips of others below them.  For your convenience, here is my tileset:

The tileset on roguecentral is missing so my organization of the tileset is complete conjecture. I would appreciate any kind of help I can get!

@christopherdumas sorry for not replying for so long.
Just to clarify, is this still a problem even with the "safe" bindings from #245? (these just got merged so it may be easier to verify).
If so, could you please try to the angband16x16.bmp tileset that got merged now as well? If that crashes as well, the issue is likely somewhere in tcod-rs or libtcod. If it works fine, then it's likely in your tileset. Either way, it'll help us narrow it down.
I will try to look at your project at some point, but it'll probably be some time before I can.

Thank you for getting back to me, I've fixed the problem. I had to specify the size of the font. Also, good to know that the safe bindings finally got merged, I haven't updated tcod-rs in awhile. Also, how are the libtcod 1.6 bindings coming?

Glad to hear that! I'll close this issue.
Re: libtcod 1.6, I don't have the time to work on this crate much these days and there wasn't a ton of interest for it.
There are ancient bindings is the libtcod-1.6.0 branch you can take a look at:
https://github.com/tomassedovic/tcod-rs/tree/libtcod-1.6.0
It's just one commit, so it shouldn't be too hard to rebase it. On the other hand, the building process for libtcod1.6 is changed I believe, so it will probably require updates to build.rs as well.


Update Makefile

Codecov Report
All modified lines are covered by tests :white_check_mark:
:loudspeaker: Thoughts on this report? Let us know!.


on "application error", return success=false, but should not destroy the container

Environment details:

local deployment

Steps to reproduce the issue:

create an action that returns as:

return {error: "this was a failure..."}

invoke the action repeatedly
Note that each invocation returns an "initTime", indicating no container reuse, and also in invoker logs, container is destroyed, despite a 200 response:

[2018-07-30T17:39:14.145Z] [INFO] [#tid_Ebq8zgXiJVIQJyJJVxk57kOu6jal0BUB] [ContainerProxy]  [marker:invoker_collectLogs_start:547]
[2018-07-30T17:39:14.156Z] [INFO] [#tid_Ebq8zgXiJVIQJyJJVxk57kOu6jal0BUB] [InvokerReactive] posted completion of activation 89e79852c3fd4768a79852c3fd47688d
[2018-07-30T17:39:14.175Z] [INFO] [#tid_Ebq8zgXiJVIQJyJJVxk57kOu6jal0BUB] [ContainerProxy]  [marker:invoker_collectLogs_finish:578:31]
[2018-07-30T17:39:14.178Z] [INFO] [#tid_Ebq8zgXiJVIQJyJJVxk57kOu6jal0BUB] [CouchDbRestStore] [PUT] 'whisk_local_activations' saving document: 'id: guest/89e79852c3fd4768a79852c3fd47688d, rev: null' [marker:database_saveDocument_start:581]
[2018-07-30T17:39:14.180Z] [INFO] [#tid_sid_dbBatcher] [CouchDbRestStore] 'whisk_local_activations' saving 1 documents [marker:database_saveDocumentBulk_start:38009]
[2018-07-30T17:39:14.192Z] [INFO] [#tid_sid_invokerNanny] [DockerClientWithFileAccess] running /usr/bin/docker rm -f 4090ec441622f9eedd13c3b244b1f1fa5f3d9d7a74e3d92dad087665a7ff8e79 (timeout: 1 minute) [marker:invoker_docker.rm_start:38018]

Provide the expected results and outputs:
Container reuse should be possible on an error that was gracefully handled by the action.
Provide the actual results and outputs:
Container is not reused.
Additional information you deem important:
Is there a reason for this? I couldn't find good docs on the handling of "application error" state, where container operates properly but returns an error. A typical use case is "parameter validation" - there is no reason the container cannot be reused if it simply rejects the activation based on invalid input, as opposed to bubbling up an exception or some non-200 response.
This can be handled in ContainerProxy by updating:
case Right(act) if !act.response.isSuccess

to
case Right(act) if !act.response.isSuccess && !act.response.isApplicationError

This is by design - all errors are treated equally and destroy the container. You make a fair point which has been previously considered: if the error is handled inside the function, reusing the container may still be wholly valid.

I think, on a broader perspective, this might also be related to our general behavior on errors. I think we return 200 for a success and 502 for an error on a blocking invocation.
There was a lengthy discussion once whether that should be the case, and whether we should rather see our containers as upstream applications, that, if they returned an error themselves, should be considered successful in the sense that: they didn't crash.
We could change that behavior to only return a 502 on a system error (when the platform is at fault) or action-developer error (uncaught/unhandled exceptions), and return a 200 on anything else. Since we have web-actions, you can choose to return fine-grained results anyway if you need them, I don't think we had them back in the day. In the same sense, we would leave containers running that don't cause a system-error or an application-developer error.

See #645 for the "old" discussion on this.


fix(queue): do nothing when queue is empty (#1679)

Doing something like this would temporary fix #1679, until the inner issue https://github.com/doublesymmetry/KotlinAudio/pull/41 gets fixed.

@hvihvi thanks for providing the PR's to fix this!
I'm actually hopeful we can get your Kotlin reviewed and merged pretty quickly. If that's the case I think that's the right move. If we don't get that merged in the next day or so I'll push forward with merging this.
Does that work for you?

@hvihvi thanks for providing the PR's to fix this!
I'm actually hopeful we can get your Kotlin reviewed and merged pretty quickly. If that's the case I think that's the right move. If we don't get that merged in the next day or so I'll push forward with merging this.
Does that work for you?

Yeah I also believe fixing this issue on the KotlinAudio side would be best if possible. 😅
As a temporary fix, library clients can check that the queue is empty before calling TrackPlayer.removeUpcomingTracks() to work around this issue.

The KotlinAudio MR was just merged. All we need now is to wait for a release and then bump the version we're using in the gradle file.


re.facerec_from_webcam_multiprocessing

face_recognition version:1.2.1
Python version: 3.8
Operating System: windows 10

Description
i was trying this facerec_from_webcam_multiprocessing
I changed only the the statement
video_capture = cv2.VideoCapture(0)
to
video_capture = cv2.VideoCapture("./face_recognition/examples/short_hamilton_clip.mp4")
The problem faced is in capture function it always goes into sleep except after 1st frame
Pls suggest

please check the path how you gave- i think ./path wont work, it is ../path. since it is just trying to fetch the video.
what are you getting in the first frame. if it is blank screen then its a path issue only i think.
i don't have opencv now to check.
please update once you get solution
helpful to others!! :)

Hi Thanks yes... load_image_file was failing ... works now


bugdom: 1.3.2 -> 1.3.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/jorio/bugdom/releases.
meta.description for bugdom is: A port of Bugdom, a 1999 Macintosh game by Pangea Software, for modern operating systems
meta.homepage for bugdom is: https://github.com/jorio/Bugdom
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.3 with grep in /nix/store/4y1fsyvyr3flx1q367z6sydbwvrzzadf-bugdom-1.3.3
found 1.3.3 in filename of file in /nix/store/4y1fsyvyr3flx1q367z6sydbwvrzzadf-bugdom-1.3.3

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
bugdom

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4y1fsyvyr3flx1q367z6sydbwvrzzadf-bugdom-1.3.3
ls -la /nix/store/4y1fsyvyr3flx1q367z6sydbwvrzzadf-bugdom-1.3.3/bin

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

1 package built:

bugdom

Maintainer pings
cc @luxferresum for testing.

Superseded by #213314.


New Release 2023.07.11

Status
READY
Description
Docs update

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 96.355%

Totals

Change from base Build<PHONE_NUMBER>:
0.7%

Covered Lines:
1877

Relevant Lines:
1948

💛  - Coveralls


Update documentation

Adding a comment about kube config paths.

If anybody wants to change the path to kubeconfig, it's doable via standard env variable:
$ KUBECONFIG=/dev/null helm dashboard


Adding to Troubleshooting section

Issues I have been encountering off late - adding to Troubleshooting section

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

This change is

@ellis-bigelow get this in 0.2.1 tag. Represents some common issues which happen

/assign @ellis-bigelow

closing and doing a clean one


Container and images are unnecessarily large

The Dockerfile leaves around the installer TGZ internally which is unnecessary.
Once installed by default the management server is turned on which is a significant overhead for a container.
Try to use Alpine instead of an entire CentOS installation

One approach you could poke around at is using multistage builds so the installer isn't included in the final image layers.
Ex:
`FROM centos:7 as vector-builder
RUN yum install -y libaio sudo
Pull in Vector saveset
This Dockerfile will work with any community linux version that follows this naming convention
ENV VECTOR_ARCHIVE actian-vector--community-linux-x86_64
ENV II_SYSTEM /VectorVW
ADD ${VECTOR_ARCHIVE}.tgz .
Install Vector
RUN cd $VECTOR_ARCHIVE && ./install.sh -express $II_SYSTEM VW -noad && hostname > /tmp/hostname.build
FROM centos:7
Docker file for Actian Vector Community Edition
LABEL com.actian.vendor="Actian Corporation"
description="Actian Vector Community Edition"
<EMAIL_ADDRESS>#TAG actian vector community
Pull dependencies
RUN yum install -y libaio util-linux-ng sudo
ENV II_SYSTEM /VectorVW
Copy Vector installation from builder stage
COPY --from=vector-builder $II_SYSTEM $II_SYSTEM
COPY --from=vector-builder /tmp/hostname.build /tmp/
set environment globally
RUN cp $II_SYSTEM/ingres/.ingVWsh /etc/profile.d/vectorVW.sh
fix hostname as localhost
RUN source /etc/profile.d/vectorVW.sh && sed -i -e "s,cat /tmp/hostname.build,localhost," $II_SYSTEM/ingres/files/config.dat && ingsetenv II_HOSTNAME localhost
Install Vector control script
RUN ln -s $II_SYSTEM/ingres/utility/dockerctl /usr/local/bin/dockerctl
Allow external connections
NOTE: these are instance ID dependent (II_INSTALLATION)
EXPOSE 27832 27839 44223 16902
Give the actian user a database password to allow for access from outside the container
Only uncomment this line if you want to allow this
An alternative, and more secure technique is to do this after the image is created and commit the resulting container.
That way, the real password isn't embedded in a Dockerfile
docker exec -u actian -it vector bash -i -c 'echo "alter user actian with password =actian;commit;\p\g"|sql iidbdb'
docker commit vector actian/vector:community
RUN sudo su - actian -c 'ingstart >/tmp/ingstart.out;echo "alter user actian with password =actian;commit;\p\g" | sql iidbdb>/tmp/pw.out;ingstop -force >/tmp/ingstop.out||true'
Allow external locations - uncomment to make these available for use
Data
VOLUME /VectorVW/ingres/data
Backup
VOLUME /VectorVW/ingres/ckp
Journals
VOLUME /VectorVW/ingres/jnl
TxLog
VOLUME /VectorVW/ingres/log
Configuration
VOLUME /VectorVW/ingres/files
ENTRYPOINT ["dockerctl"]`
This approach drops the size from 1.93GB to 1.59GB. It still needs some work since the actian/demo users don't exist in the final image when it runs. There may also be some additional files that need to be copied over from the builder as well that I'm not aware of.
Just thought I'd share since I've been using the same multistage pattern for another project I'm working on.


feat: move observability api from management to default

What this PR changes/adds
Remove observability controller from management api and put on the default context as it was before the api context refactoring
Why it does that
Untangling dependencies between an hi-level api as observability and the management api
Further notes

Linked Issue(s)
Closes #3165
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Patch coverage has no change and project coverage change: -55.64 :warning:

Comparison is base (00c5d53) 65.29% compared to head (7e3023c) 9.66%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #3166       +/-   ##
==========================================
- Coverage   65.29%   9.66%   -55.64%
==========================================
  Files         834     834
  Lines       16763   16752       -11
  Branches      924     924
==========================================
- Hits        10946    1619     -9327
- Misses       5444   15088     +9644
+ Partials      373      45      -328

Impacted Files
Coverage Δ

.../api/observability/ObservabilityApiController.java
0.00% <0.00%> (-64.00%)
:arrow_down:

...c/api/observability/ObservabilityApiExtension.java
0.00% <0.00%> (-85.72%)
:arrow_down:

... and 562 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Spurious logs about non-systemd OS

in csi-cephfsplugin log, every mount tries to detect systemd.
I0808 15:05:19.650648       1 mount_linux.go:198] Cannot run systemd-run, assuming non-systemd OS
I0808 15:05:19.650672       1 mount_linux.go:199] systemd-run failed with: exit status 1
I0808 15:05:19.650688       1 mount_linux.go:200] systemd-run output: Failed to create bus connection: No such file or directory

This seems to be caused by isMountPoint check that calls mount.New("").IsLikelyNotMountPoint(p)

Can we somehow make it do the detection just once by caching mount.New("") ?


Update readme.md for options

This is good to mention in general (if you disagree, reject the PR)

nah you're good


lnproxy payments

So far this just adds lnproxy to local dev for beginning to test/play around with it.
I've made a few modifications to lnproxy (just configuration/ops stuff) in this fork: https://github.com/huumn/lnproxy-relay

Since we're no longer using lnproxy (see #1178), can this PR be closed?


Bump rb-sys

Hopefully that should fix the cross-gem action that's been failing. I manually triggered the build gem workflow, we'll see.

Superseded by #85


is it possible find external walls?

Hi, guys your app is awesome but i have a pb, i need to find which walls is external, and which is not. I need it for drawing internal in one color and external for other. Is is possible find?

Did you manage to solve this?

Hi @fix2015 and @mafrost,
This is an old problem for us, at the moment we have a few ideas to solve it but they would require a lot of time for implementation... However I reopen this issue and we will try to solve it as soon as possible

hi, thx


feat(tree): Added most frequent subtree sum.

Coverage remained the same at 100.0% when pulling 9572bb802f5d95aee54a79f43e257e88b9578919 on most-frequent-subtree-sum into e03bb757629f96994db9349123b2879f3b5f50dc on master.


Treat life loss as termination in training mode

Another PR following #32.
This PR make the treatment of live count different in test mode and train mode by introducing mode attribute and life_lost flag in environment.
On breakout, this change yields faster learning and better result. (I will keep updating the data).

https://gist.github.com/mthrok/93bcaf2ef996de6ad156ee3b994d5dd4

Looks good, thanks for nice clean code. How far we are from replicating the exact results from Nature paper?

@tambetm Thanks for merging.
The evaluation methods they used in Nature paper are different between Extended Data Table 2 and 3, and as simple_dqn's method is more similar to that of Table 3, I only have direct comparison on Breakout and Space Invaders. I think both are pretty much similar.
Result on Space Invaders with this commit


Cannot get data in real time with Update Subscription

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.17.3
Amplify CLI Version
7.6.26
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
auth, api
Amplify Commands
codegen
Describe the bug
Cannot get when Update Subscription is set in the sign-in state (Cognito UserPool).
User belongs to one or more groups.
It worked fine with IAM guest login.
It is possible that the code here is incorrect, but I would be happy to have you guys confirm this.
Expected behavior
Cannot get when Update Subscription is set in the sign-in state (Cognito UserPool).
I did not catch the error.
Reproduction steps

User belongs to one or more groups.
cognito login
use amplify-js (ionic)

this.apiService.OnUpdateRoomsListener(id).subscribe(
 (data) => {
console.log('get Data');
},

update Rooms

GraphQL schema(s)

# Put schemas below this line
type Rooms @model
@auth(rules: [
  { allow: owner, ownerField: "id", operations: [create, update, read] }
  { allow: groups, groups: ["employee"] }
  { allow: public, provider: iam, operations: [create, update, read] }
]) {
  id: ID!
  data1: string
  data2: string
  data3: string
}

Log output

# Put your logs below this line

Additional information
No response

thank you.
I re-created the account and it now works fine.
However, it was a little strange since it seemed to work before.
If you have no idea what is going on on your end, you can close it.
Sorry I could not reproduce it.

Hello @shichi18, Thank you for reaching out. Looking at the schema and on replicating in my Amplify application. I can see the ownerField: "id" which will cause record creation errors. As the ID field is unique, AppSync will fill in the id as owner but will cause a creation error on the next record with the same id. could you please remove the ownerField and deploy the API.

@ykethan
ID field was unique.
Guest login (random string) and user login (UserPool ID) used different IDs.
Get was working, so I felt that IDs were not a problem.
After updating data, I was able to get the updated information with GetRoom.
OnUpdateRoomListener could not get the data in real time (this is the topic of this issue).
Nothing was returned.
When I switched the login to another account or guest, it worked, so it is possible that something is wrong with the DB.
However, the ID did match the account.
Creating and recreating the account solved the problem and I am able to use it again, but I will also try it the way you have taught me.
Thank you!

Hey @shichi18, I replicated the onUpdateRooms in my local application utilizing the following code.
const subs = API.graphql({
      query: subscriptions.onUpdateRooms,
      variables: { id: "<id of owner>" },
    }).subscribe({
      next: ({ provider, value }) => console.log({ provider, value }),
      error: (error) => console.warn(error),
    });

on running a npm start I was able to see the room update actions in my browser console on each update room query. I was unable to see an error when creating a subscription. But I experienced an DynamoDB:ConditionalCheckFailedException error when creating a new room as the owner field is unique.
I understand the issue had been resolved after recreating the account, please do reach out if you are experiencing any issues.

closing the issue. Please do reach out to us again.


keyd and russian layout

Hello, I use dvp and russian layout.
keyd didn't work with setxkbmap -option ctrl:nocaps -option grp:win_space_toggle us,ru -variant dvp,typewriter
I disable dvp and create dvp in default.cfg:
layout(dvorak)

[mylayer]
; = $
a = 0
s = 1
d = 2
f = 3
q = $
z = grave
w = 7
e = 8
r = 9
x = 4
c = 5
v = 6

[dvorak]
meta = meta
space = space
rightalt = layer(mylayer)
leftalt = leftcontrol
compose = compose
esc = esc
capslock = leftalt
leftcontrol = leftalt
rightcontrol = rightcontrol
leftshift = leftshift
rightshift = rightshift
enter = enter
tab = tab
backspace = backspace
up = up
down = down
left = left
right = right
mode = mode
q = semicolon
w = comma
e = dot
r = p
t = y
y = f
u = g
i = c
#....etc

after I chose Russian setxkbmap -option grp:win_space_toggle us,ru -variant ,typewriterwith , keymap use old (US). How implement Russian in cfg and change layout without setxkbmap?  Only keyd?

i just hacking  holy XKB and add layout to RALT in /usr/share/xkb/symbols/en,ru and change LALT LCTRL in /usr/share/xkb/keycodes/evdev

thanks

See also #33

There is now first class support for this, so you can do o = ö directly in the config file (provided the xkb option compose:menu is set. See the man page for details.

Thanks for answer, but I create my layout for XKB (X/Wayland), Windows.
So, I didn't use any programs today.

@rvaiya
so we'll be able to map language layout in keyd itself?
[russian:layout]
q=й
w=ц
e=у
...
?

@fedoranvar Indeed. It uses X macros, so I'm not sure how well it would work for a full layout but it seems to work reasonably well for the odd international character. I would appreciate it if you could give it a try and let me know how it goes.

P.S
:layout is no longer valid syntax. You may want to reread the man page.

there is no way for wayland yet?

It should work on both, though you may need to explicitly enable XIM if you
use gnome. If you encounter any issues, feel free to open a dedicated issue.
On Tue, Apr 5, 2022 at 5:29 AM Anvar Kildebekov @.***>
wrote:

there is no way for wayland yet?
—
Reply to this email directly, view it on GitHub
https://github.com/rvaiya/keyd/issues/26#issuecomment-1088478473, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOP7GJLANRAP6PMJHK4NRLVDQBYJANCNFSM5DSIBR2A
.
You are receiving this because you were mentioned.Message ID:
@.***>

tested full language remapping - it works on wayland

Cool...

@rvaiya there is some constaint.
If i remap all characters + digits and modifiers, it throws something liike:
you've exceeded max count of macros > 60

you've exceeded max count of macros > 60

This should be fixed in the latest commit.

when i'm trying to type uppercase letter it prints this....

The reason this happens is because keyd doesn't know how to produce uppercase letters on its own. It just produces the unicode character you mapped to the key. So when you do shift+<key> it will do <shift>+<xcompose macro> which will result in the garbled output you are seeing. To solve this problem you need to manually override the shifted keys like so:
[russian]
q = д
[shift+russian]
q = Д
# etc..