improvement let the storage_page_cache_shard_size conf be rounded up to a power of two

Proposed changes
Issue Number: close #xxx
Problem summary
When I set the storage_page_cache_shard_size parameter to something other than a power of two, the be would crash and fail to start
0515 14:26:21.037065 3604161 daemon.cpp:214] OS physical memory 62.06 GB. Process memory usage 435.77 MB, limit 55.85 GB, soft limit 50.27 GB. Sys available memory 55.94 GB, low water mark 1.60 GB, warning water mark 3.20 GB. Refresh interval memory growth 0 B
I0515 14:26:21.060109 3604119 load_path_mgr.cpp:71] Load path configured to [/mnt/disk1/data/doris/doris-master/storage/mini_download]
I0515 14:26:21.060180 3604488 result_buffer_mgr.cpp:147] result buffer manager cancel thread begin.
F0515 14:26:21.066411 3604119 lru_cache.cpp:528] Check failed: (num_shards & (num_shards - 1)) == 0 (14 vs. 0) num_shards should be power of two, but got 15
*** Check failure stack trace: ***
    @     0x55b7a6295e1d  google::LogMessage::Fail()
    @     0x55b7a6298359  google::LogMessage::SendToLog()
    @     0x55b7a6295986  google::LogMessage::Flush()
    @     0x55b7a62989c9  google::LogMessageFatal::~LogMessageFatal()
    @     0x55b79f27d74d  doris::ShardedLRUCache::ShardedLRUCache()
    @     0x55b79f27e53e  doris::new_lru_cache()
    @     0x55b79f356f06  doris::StoragePageCache::StoragePageCache()
    @     0x55b79f356d5a  doris::StoragePageCache::create_global_cache()
    @     0x55b79f4357e4  doris::ExecEnv::_init_mem_env()
    @     0x55b79f434b01  doris::ExecEnv::_init()
    @     0x55b79f433c5e  doris::ExecEnv::init()
    @     0x55b79eb731ba  main
    @     0x7efe5e669083  __libc_start_main
    @     0x55b79eb7202a  _start
    @              (nil)  (unknown)
*** Query id: 0-0 ***
*** Aborted at<PHONE_NUMBER> (unix time) try "date -d @1684131981" if you are using GNU date ***
*** Current BE git commitID: 92bf485abd ***
*** SIGABRT unknown detail explain (@0x36fe97) received by PID 3604119 (TID 3604119 OR 0x7efe5e4c8d00) from PID 3604119; stack trace: ***
I0515 14:26:21.438664 3604161 daemon.cpp:214] OS physical memory 62.06 GB. Process memory usage 672.64 MB, limit 55.85 GB, soft limit 50.27 GB. Sys available memory 55.87 GB, low water mark 1.60 GB, warning water mark 3.20 GB. Refresh interval memory growth 0 B
 0# doris::signal::(anonymous namespace)::FailureSignalHandler(int, siginfo_t*, void*) at /mnt/disk1/compile/doris-master/be/src/common/signal_handler.h:413
 1# 0x00007EFE5E688090 in /lib/x86_64-linux-gnu/libc.so.6
 2# raise at ../sysdeps/unix/sysv/linux/raise.c:51
 3# abort at /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:81
 4# 0x000055B7A62A0809 in /mnt/disk1/software/doris-master/be/lib/doris_be
 5# 0x000055B7A6295E1D in /mnt/disk1/software/doris-master/be/lib/doris_be
 6# google::LogMessage::SendToLog() in /mnt/disk1/software/doris-master/be/lib/doris_be
 7# google::LogMessage::Flush() in /mnt/disk1/software/doris-master/be/lib/doris_be
 8# google::LogMessageFatal::~LogMessageFatal() in /mnt/disk1/software/doris-master/be/lib/doris_be
 9# doris::ShardedLRUCache::ShardedLRUCache(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long, doris::LRUCacheType, unsigned int, unsigned int) at /mnt/disk1/compile/doris-master/be/src/olap/lru_cache.cpp:528
10# doris::new_lru_cache(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long, doris::LRUCacheType, unsigned int) at /mnt/disk1/compile/doris-master/be/src/olap/lru_cache.cpp:663
11# doris::StoragePageCache::StoragePageCache(unsigned long, int, unsigned int) at /mnt/disk1/compile/doris-master/be/src/olap/page_cache.cpp:45
12# doris::StoragePageCache::create_global_cache(unsigned long, int, unsigned int) at /mnt/disk1/compile/doris-master/be/src/olap/page_cache.cpp:31
13# doris::ExecEnv::_init_mem_env() at /mnt/disk1/compile/doris-master/be/src/runtime/exec_env_init.cpp:234
14# doris::ExecEnv::_init(std::vector<doris::StorePath, std::allocator<doris::StorePath> > const&) at /mnt/disk1/compile/doris-master/be/src/runtime/exec_env_init.cpp:178
15# doris::ExecEnv::init(doris::ExecEnv*, std::vector<doris::StorePath, std::allocator<doris::StorePath> > const&) at /mnt/disk1/compile/doris-master/be/src/runtime/exec_env_init.cpp:97
16# main at /mnt/disk1/compile/doris-master/be/src/service/doris_main.cpp:432
17# __libc_start_main at ../csu/libc-start.c:342
18# _start in /mnt/disk1/software/doris-master/be/lib/doris_be

So in this PR, even if the user sets the wrong configuration, the be will still start normally, but it will prompt an alarm message in the log
W0515 14:37:40.072067<PHONE_NUMBER> exec_env_init.cpp:239] num_shards should be power of two, but got 104. Rounded up to 128. Please modify the 'storage_page_cache_shard_size' parameter in your conf file to be a power of two for better performance.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.62 seconds
stream load tsv:          424 seconds loaded<PHONE_NUMBER>9 Bytes, about 168 MB/s
stream load json:         24 seconds loaded<PHONE_NUMBER> Bytes, about 93 MB/s
stream load orc:          59 seconds loaded<PHONE_NUMBER> Bytes, about 17 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230515110617_clickbench_pr_143836.html

run buildall

run buildall

run buildall

run buildall


Test Digits on the new Android Emulator

In the sign up flow it asks you to Enter your phone number

Can you complete this flow using the Android Emulator? If so, what number do you have to enter here?

You can enter your own mobile number. There is no requirement you receive an SMS on the device you are registering.


[RFC] Camera zoom WIP

It would be useful to have a feature where the camera can zoom in. Say there's a conversation going, the camera could be set to zoom in on the characters on :talk.
Another use case is that the character walks somewhere and the camera pushes in on a close-up, and when the character walks back out, the camera pulls out.
I think there could technically be other cameras, but with only one visible at any time and limited support in ESC scripts, surely it'd be more pain to deal with. And those cameras need to zoom as well.
After some struggling, I sort of got zooming to work, but didn't realize in advance that scaling the viewport causes the action menu (and all that, tooltips etc) to get zoomed as well! There must be a better way!
Is there a way to filter out the HUD and dialog stuff and scale them down when scaling the viewport up? Does that question make sense? It should be easier than tagging all the TextureRects and sub-scene nodes with affected_by_zoom or whatever.
I've been asking around on IRC and searching online for a while, but no evident answer has popped up.
For some reason camera.zoom = ... has had no impact, does this work for anyone?
This branch is off my devel branch, which has apparently deviated a lot from master. Sorry. It is not meant to be merged, but to be discussed, though I did hope the commit history would be cleaner. Pay no attention to the commits older than 2018-03-02 ;) (I may sort my devel branch later and force-push it)
You can check out the gh-mjtorn-devel-zoom branch and update the submodule, I set it up so it points to a corresponding branch in my prototype submodule. It includes buttons for changing the zoom level to play around with. Unfortunately the TextureRects I used are white, as the background, so they are a bit awkward to find, but looking at them changes the zoom. That means the camera zoom functionality is properly exported in the ESC scripts, so that's at least something.
The relevant HEAD in my prototype submodule is 7e27cdafe176e6405780680c4bda3832b9e952f3 (branch room.002.zoom.

As discussed on IRC, I don't think this can be achieved* without also scaling the hud, including inventory and verb/action menu, as long as it's all part of the same viewport. I think the only good solution for this is to have the game scene be a part of a second viewport, but that would require a major rewrite, so it would be helpful if @punto- and @StraToN would comment before we start work on that.
This rewrite would give a scene tree looking something like this:
game
├── hud
│   ├── verb_menu
│   ├── inventory
│   └── action_menu
└── viewport
    └── scene
        ├── background
        ├── terrain
        ├── player
        ├── item1
        └── item2

Which would mean that we can't load a room directly, but instead instanciate it into the game scene.

That is achieved without hacky workarounds like scaling the hud elements the other way to counteract the effect.

AFAIU this means the camera is moved out of game so that it can use viewport, right?
The problem may be that the children of hud are still scaled up, and would require that hacky workaround. I conducted a little experiment with it and couldn't get them scaled back.
Would this have performance problems, with checking if things have been scaled?
I also posted a question on the Q&A, and we can wait a while to see if anyone replies, but judging by the (in)activity in some of the questions, we shouldn't hold our breaths.

I meant that the game and hud would use the default viewport and camera to not be affected by scaling, since we'd only scale the second viewport. And, yeah, that second viewport will also need a camera. I don't think the second viewport node will need to worry about whether or not it's scaled at all, but I will make a proof-of-concept as soon as possible to check that this doesn't cause problems with input events being offset from where they should occur.

I dropped some links on IRC for discussion,
http://docs.godotengine.org/en/3.0/tutorials/2d/canvas_layers.html
http://docs.godotengine.org/en/3.0/tutorials/2d/2d_transforms.html
A friend of mine, who admittedly doesn't know Godot but also hasn't been broken by this, suggested that maybe viewports aren't the way to go but some kind of canvas layering.
Thoughts?

After making a simple demo project to test this, I agree that canvas layering is definitely the way to go:
https://github.com/fleskesvor/canvas-test
The project zooms in/out on mouse click, and as you can see, the scene node and its children are scaled together, while the sprite in the separate canvas layer remains unchanged.
This is very similar to how Escoria is structured today, so there likely shouldn't be too many changes needed to get this to work. The action menu must be placed within the canvas layer of the hud though, and there are probably some other issues as well. This means that your friend is right though, as I'm now also convinced this is the way to go.

Fixed by #80.


dockerfileNative should not require GraalVM SDK

Duplicates #49?

Not exactly. #49 is about dockerBuildNative task, this one is about dockerfileNative.
Just simply generating a Dockerfile shouldn't require GraalVM locally


chore(asf): Update GitHub repo metadata

Platforms affected
Github
Motivation and Context

Update tags and only enable squash merge button like we do on other repos.
Checklist

[ ] I've run the tests to see all new and existing tests pass
[ ] I added automated test coverage as appropriate for this change
[x] Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
[ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
[ ] I've updated the documentation if necessary

@NiklasMerz are you able to merge this?

Sure. Thanks for the reviews.


As a user, I would like to be able to visualize the scope of today’s deforestation because it will help me to understand its threat to my future

Hey team! Please add your planning poker estimate with ZenHub @ChristopherSterza @Donovanphenry @gdochoa @sedwardsmarsh


[otbn] Finish off DV plan

There are a few TODO comments left. Get everything done except for functional coverage.

estimate 4

This will be done once #5703 and #5704 are merged.


Add support for comments

I haven't seen it in the wild, but VDF apparently allows for C-style inline comments so add support for this. The question for implementation should be whether comments should be exposed through the parser or ignored. It would be good to see how other data formats that support comments handle this.

Added in 6fc56a024db14c0083d60cbd48e45ad14f74d5ef


Gh 228

Verification

run make local-setup OCM_SINGLE=true MGC_WORKLOAD_CLUSTERS_COUNT=1
ensure a secret called mgc-aws-credentials in the namespace  multi-cluster-gateways is created with the creds from aws-credentials.env
ensure the managed zone cr created contains a reference in the spec to the name and namespace and type of the dnsprovider credentials from above

spec:
   provider:
    name: mgc-aws-credentials
    namespace: multi-cluster-gateways
    type: AWS

run through the walkthrough https://github.com/Kuadrant/multicluster-gateway-controller/blob/main/docs/how-to/ocm-control-plane-walkthrough.md everything should work as expected
Status in the managedzone should be updated

@R-Lawton when this merges everyone local setup is going to fail. So might be worth announcing in the slack channel that they need to setup these new env files

/hold
There shouldn't be any reason to break local-setup

/retest

/retest

/hold cancel
This looks good, tried it locally and things work as expected, few small comments.
Not sure about the e2e test, but when that passes i think we should be good to merge.
Secret is created as expected:
kubectl get secret -n multi-cluster-gateways
NAME                   TYPE                DATA   AGE
mgc-aws-credentials    kuadrant.io/aws     3      28m
myapp.mn.hcpapps.net   kubernetes.io/tls   3      3m54s

Would be nice if some details of the provider type could be surfaced when listing zones(kubectl get managedzones -n multi-cluster-gateways), but not something we need to do now.

/lgtm
/approve


added coverage compare function - [closed]

In GitLab by @guyingyan on Feb 2, 2018, 08:03
Merges dev-jenkins -> dev

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  10.5%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  10.5%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  10.5% check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  10.5%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  25%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  25%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  25%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  25%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  25%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  13.2%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the coverage is  13.2%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI coverage is check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI coverage is30% check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI coverage is30% check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI coverage is 30% check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI Coverage is 38.11% check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI Coverage is 38.11% check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.2%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.3%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.3%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the service coverage is  13.3%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  13.3%   UI Coverage is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.6%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.6%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.4%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  23.0%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  NaN%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  92.3%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  NaN%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  NaN%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  NaN%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  NaN%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  %   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.20%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.20%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.40%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.40%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.70%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
the API Server Coverage is  17.70%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  54.35%   and for frontend is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  55.65%   and for frontend is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
The test coverage for backend is  %   and for frontend is %   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:30
closed


Caching

Hey! Llama.cpp has a built-in state save/load mechanism which allows for fast startup on contexts that have been processed before. Is this possible to do with ctransformers somehow?

Hi, currently it doesn't have them but I can look into adding them.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 09:18:29 on 2023.08.12
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 1, errors out: 0
Original problem ID: 35302
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=35302

Problem has been resolved in 3m 0s at 09:21:29 on 2023.08.12
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 35302


west: runners: jlink: JLink.exe name collision

Describe the bug
The jlink binary runner uses the location of JLink.exe or JLinkExe to determine the location of the JLink libraries,
https://github.com/zephyrproject-rtos/zephyr/blob/117039ca2b7202fb08ea7cc4bcc35ca5a015241c/scripts/west_commands/runners/jlink.py#L26
https://github.com/zephyrproject-rtos/zephyr/blob/117039ca2b7202fb08ea7cc4bcc35ca5a015241c/scripts/west_commands/runners/jlink.py#L38
https://github.com/zephyrproject-rtos/zephyr/blob/117039ca2b7202fb08ea7cc4bcc35ca5a015241c/scripts/west_commands/runners/jlink.py#L177-L178
Unfortunately the OpenJDK runtime also distributes an executable called jlink.exe : https://strontic.github.io/xcyclopedia/library/jlink.exe-15C86A7D8376EC476DD2AE27EAEE31D1.html
Trying to run west flash with the runtime on the path results in errors like:
packages\pylink\library.py", line 286, in __init__
    self.load(dllpath)
  File "C:\Python310\lib\site-packages\pylink\library.py", line 392, in load
    with open(self._path, 'rb') as inputfile:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Program Files\\Eclipse Adoptium\\jdk-<IP_ADDRESS>-hotspot\\bin\\JLink_x64.dll'

Expected behavior
The jlink plugin should ideally be more resilient to finding a SEGGER executable, not any old executable called jlink.exe.
Impact
Annoyance, the correct path can be selected with west flash --commander /path/to/JLink.exe
Environment (please complete the following information):

OS: Windows

@JordanYates FYI. Thanks for this. I ran into this as well.

@JordanYates Also thanks. Same issue here.

We need a different assignee. Does someone on this ticket want to take this on?

I have also encountered this problem, and a temporary solution is:
Add the required Jlink.exe path to the first line of the environment variable PATH.


Frontend - UI Changes for Landing, Auth Pages 🛠

Change 1

Take a look at the width of the input boxes on the right, i want the same width for the input box, headings on the left for User Register Page
Change 2

For all the Login/Logout pages i want the placeholder to be visible only for mobiles
I want the button, forgot password etc left aligned for the DESKTOP

Change 3

I want the first box to go up by some pixels with increased font size
I want the second box  (buttons) to go up by some pixels too, no changes in font

@IAmTamal Can you please assign this issue to me?

@IAmTamal Can you please assign this issue to me?

Sure, make sure you do all the 3 changes as i have said above.
Make sure it is done withing 3 days !

@IAmTamal  please assign to me if still not resolved.

@IAmTamal @HKAgrwl It's almost done I'm about to make a PR.

cool

@IAmTamal I have implemented the suggested changes. Please review the screenshots and let me know about further improvement or making PR.
Change 1

Change 2

Change 3

Hey, I can help you out with this issue. if not done assign it to me.


Jenkins(Deploy game-of-life on tomcat)

Sir,we can use scp jenkins:gameoflife-web/target/gameoflife.war jenkins:/var/lib/tomcat8/webapps/.
Can i have the output log of your tomcat build.

scp syntax: scp <source_path> user@<ip_of_tomcatserver>:<destination_path>
my config: scp $ArtifactLocation jenkins@$tomcat_server:/var/lib/tomcat8/webapps/'
where $ArtifactLocation= /var/lib/jenkins/workspace/gameoflife\ project/gameoflife-
web/target/gameoflife.war
$tomcat_server=<IP_ADDRESS>
make sure you pass these parameters from the upstream project

check your syntax scp
like @sanjaysureshmv  as said.

thanks guys worked
i refer not giving names in jenkins items(New item) with spaces(i.e game of life),suggested game-of-life


After recent update getting error on DraggableScrollableSheet

I hadn't updated flutter for about 4-6 months I think. A few days ago I updated to the latest version and something that was working in my app began to fail. after checking my commit history for anything that might have caused it I believe it's due to the update.
The error:
Exception has occurred.
_AssertionError ('package:flutter/src/widgets/draggable_scrollable_sheet.dart':
Failed assertion: line 170 pos 7:
'isAttached':
DraggableScrollableController is not attached to a sheet.
A DraggableScrollableController must be used in a DraggableScrollableSheet before any of its methods are called.)

The affected code:
    ...
            DraggableScrollableSheet(
              initialChildSize: minHeight,
              minChildSize: minHeight,
              maxChildSize: min(1.0, max(minHeight, getMaxExtent(context))),
              controller: dController,
              builder: (context, scrollController) {
                bloc.scrollObserver.add(dController.size);
                return CoinDetailsGlidingSheet(
                  bloc.nullCacheView ? null : MetadataView(),
                  dController,
                  scrollController,
                );
              }),

It maybe that I was using DraggableScrollableSheet and its DraggableScrollableController in a dangerous configuration from the start and a recent update of flutter fixed a vulnerability related to those widgets?
Anyway, You can see what I'm trying to do here, observe the DraggableScrollableController.size value. Is there a more correct way to do it?

not the best way to have side effects in the build method. There might be 2 options: add check dController.isAttached before size property is used
or subscribe to dController since it's Listenable somewhere in initState or something like that, in order to track size changes
https://api.flutter.dev/flutter/widgets/DraggableScrollableController-class.html
A [DraggableScrollableController](https://api.flutter.dev/flutter/widgets/DraggableScrollableController-class.html) is a [Listenable](https://api.flutter.dev/flutter/foundation/Listenable-class.html). It notifies its listeners whenever an attached sheet changes sizes. It does not notify its listeners when a sheet is first attached or when an attached sheet's parameters change without affecting the sheet's current size. It does not fire when [pixels](https://api.flutter.dev/flutter/widgets/DraggableScrollableController/pixels.html) changes without [size](https://api.flutter.dev/flutter/widgets/DraggableScrollableController/size.html) changing. For example, if the constraints provided to an attached sheet change.


Multiple Form Builders

Hi,
In my use case, I need to create several fb-builder's which are arranged in tabs like this http://cl.ly/Xm3j so that an admin user can build the form and get it rendered with "Prev Section" and "Next Section" functionality.
This is the change that I made to allow

 so that I can use ng-repeat to dynamically create the fb-builder's :
scope: {
    fbBuilder: '@'
}

This results in $builder.forms variable to be in this structure:
{ default: [], form1: [formObject1, formObject2], form2: [formObject3], and so on }

When I move certain formObject around in one of the form (e.g. form1) the $builder.updateFormObjectIndex(scope.formName, oldIndex, newIndex) is executed (line 259) and then execute the reindexFormObject (line 1205) method too.
However, the issue that I encounter here is that the reindexFormObject method also update and affect form2 (e.g. if I move a formObject from index 2 to index 3 in form1, the form object at index 3 in form2 is deleted), which should not be the case. Because I only want to update form1.
Any idea on this matter? Does anyone encounter this issue also when trying to implement multiple form builder?
Appreciate any help here.
thanks.

I solved this.
As stated you should first change
scope: {
    fbBuilder: '@'
}

Afterwards take the following lines of code
and remove them. That should enable you to have multiple forms each with their own data.
You can see my forked implementation of this together with the directive:

The implementation of this directive can be found here and the way I implemented this in the view can be found here
One more thing I'm trying to implement is skip logic such that people may build surveys and have parts of them skipped depending on some user answers. Any hints for this? Interested?

I found a better way so not to simply remove that $builder.removeFormObject line.
I can determine if the code being executed is for the form on which you performed your drag by putting a condition around the removeFormObject, like this:
                          if (formObject.editable) {
                              if (scope.formObjects.indexOf(draggable.object.formObject) > -1)  // MAC-MOD
                                   $builder.removeFormObject(attrs.fbBuilder, formObject.index);
                            }

Also, there seemed to be an issue on the calculation of NewIndex a little below that. It seems that the $(element) being accessed to obtain newIndex was accounting for all contained form objects for any forms defined previous to the current form. This cause the drag-and-move UP to be ignored because the drop index was way beyond the total objects of that form. The move DOWN worked sometimes. I recalculated newIndex to account for all earlier objects so if you defined four forms and are performing a move in the third, I account for the first and second now as well. So far so good.
I replaced this code:
                              if (oldIndex < newIndex) {
                                  newIndex--;
                              }

with this:
                              var formNames = Object.keys($builder.forms);
                              var totalObjects = 0;
                              for (var i = 0; i < formNames.length; i++) {
                                  if (formNames[i] != scope.formName) {
                                      totalObjects += $builder.forms[formNames[i]].length;
                                  }
                                  else
                                      break;
                              }
                              newIndex -= totalObjects;

And the following one is left alone. It should look like this:
                              $builder.updateFormObjectIndex(scope.formName, oldIndex, newIndex);

Now if I could just figure out a way move objects between forms. Anybody got an idea there?


Update tagline in our OpenGraph image

Description

Updates our OpenGraph image with the "DevOps for Node-RED" tagline.

Related Issue(s)
Closes #456
Checklist

[x] I have read the contribution guidelines
[x] I have considered the performance impact of these changes
[-] Suitable unit/system level tests have been added and they pass
[-] Documentation has been updated

I am curious why you went with a different format to the one I submitted in https://github.com/flowforge/website/issues/456

because thy use different fonts across each of the images, neither of the fonts are the one within our Branding Guidelines,  the text is not properly spaced & aligned, and for the second image the cloud b/g image is overlayed on top of the text

In find in your version there is too much focus on 'DevOps for Node-RED'.

Very fair, will reduce the font size

will reduce the font size

done

I am curious why you went with a different format to the one I submitted in #456

because thy use different fonts across each of the images, neither of the fonts are the one within our Branding Guidelines, the text is not properly spaced & aligned, and for the second image the cloud b/g image is overlayed on top of the text

OK, I guess it would have been nice if you had pointed this out in the issue that I submitted.
FWIW, I would like to be the person updating the social media accounts. I am spending a fair bit of time there so it is important we don't overlap on the changes.

OK, I guess it would have been nice if you had pointed this out in the issue that I submitted.

You'd mentioned they were mock ups - so I took them as such, not as the images you'd like to feature on our socials directly.

FWIW, I would like to be the person updating the social media accounts. I am spending a fair bit of time there so it is important we don't overlap on the changes.

Was an easy thing for me to do, and the existing images were not up to a standard that I would want us publishing from a design perspective. I take your point though, and will leave that with you in the future.

@iskerrett are you okay with this now that i've reduced the font size for "DevOps for Node-RED"? If so, can you review/approve please?

I think I am missing something since I don't see any difference between the two images?  Can you post the new one directly into the comments.

If you go to the "Files Changed" tab in this window, you'll see them side by side:

That version looks like the one I didn't like with the larger font. It also looks different from the version you posted on our twitter profile so I am a bit confused on what I am approving.

reduce the font-size and the gap slightly too - think it looks much better now, and is consistent with the others. Thought I had already reduces this font size when asking for the re-review, so apologies.


Deprecated import broken in 0.0.46

This deprecated import is now broken after the move of the silero classes: https://github.com/pipecat-ai/pipecat/blob/main/src/pipecat/vad/silero.py#L11 (the updated import works, but rather than giving a warning this just breaks builds)

Indeed. We just patched this: https://github.com/pipecat-ai/pipecat/pull/638. Thanks for reporting.

We'll cut a new pipecat release too. Apologies for this.


Add version command to get current version of binary

This should come first: https://github.com/strangelove-ventures/noble-cctp-relayer/issues/31

https://github.com/strangelove-ventures/noble-cctp-relayer/pull/49


Upgrade cordova-android from 5.2.2 to 7.1.0

This fixes a build incompatibility with recent versions of
the Android SDK.  It also enables some new features of
cordova-android, like Java 8 support.

Actually, the yarn build command fails with this error:
/Users/alalama/Desktop/firehook/outline-client/gulpfile.js:155
    throw new Error(`Failed to set up environment, no such path: ${config.targetDir}`);
    ^

Error: Failed to set up environment, no such path: platforms/android/app/src/main/assets/www
    at writeEnvJson (/Users/alalama/Desktop/firehook/outline-client/gulpfile.js:155:11)
    at /Users/alalama/Desktop/firehook/outline-client/gulpfile.js:225:9
    at /Users/alalama/Desktop/firehook/outline-client/gulpfile.js:134:17
    at ChildProcess.exithandler (child_process.js:263:7)
    at emitTwo (events.js:125:13)
    at ChildProcess.emit (events.js:213:7)
    at maybeClose (internal/child_process.js:927:16)
    at Socket.stream.socket.on (internal/child_process.js:348:11)
    at emitOne (events.js:115:13)
    at Socket.emit (events.js:210:7)

I think updating the targetDir for Android to the new directory structure should fix it.

Done.


Added Follow/Unfollow feature Backend Closes #12

I have made changes in user and alumni models and writeen routes for follow and unfollow feature. API have been mentioned in comments in code for better readibility

I m merging it.
But I might ping you again


refactor(falco): Falco chart v2

What type of PR is this?
/kind cleanup
/kind design
/kind documentation
/kind feature
/kind chart-release
Any specific area of the project related to this PR?
/area falco-chart
What this PR does / why we need it:
This PR is a complete renovation of the Falco Helm chart. The introduction of the plugin system, which changed the deployment paradigm, indirectly forced us to rethink how this chart should work. Nevertheless, I also tried to modernize the implementation and clean up the code from legacy stuff (which is not used anymore, I guess). Moreover, the new way of configuring the chart is inspired by some discussions I had with folks from the community and by #339 :heart:
Which issue(s) this PR fixes:
Fixes #339
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

falco/OWNERS [Issif,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


requestSubscription

Hi there, Im getting issue on try requestSubscription,request completes successfully but it works like product purchase in sandbox testing it show only five minutes then expired, user have to subscribe his subscription from google play store ,

it was working before
Version of react-native-iap : 6.0.3
Version of react-native :0.59.9
Platforms you faced the error Android
Expected behavior :Need to show sub price/time or auto subscribe from playstore
Actual behavior, have to subscribe forcefully from play store
Tested environment Real Device

getting same issue

Looks like you are registered as a test user in playstore. Please check that.

@hyochan What is the meaning of test user in Playstore? I have added my account in the internal testing in Play store, so that I am able to get build for testing. Earlier, it was working fine for this user and showing Subscribe button instead of 1-tap buy. If we remove user from their, we won't be able to get the build.
Can you please explain it? Seems very strange issue. We need to go live and stuck because of this.

@aadityapaliwal94 hello sir have you found any solution regarding this, me also stuck at here,
as you have said it was working fine, and it should be,
***Please let me know if you found any explanation,
**purchaseUpdateListener is running 4 time do you also facing this issue,
thanks


Syncplay disconnects when streaming from a URL

https://pastebin.com/7a9J3hMs
On MacOS, currently troubleshooting for a friend.
I made them output this error by running Syncplay through terminal. The error is caused after I let them stream from a link. It works fine if they play it directly through mpv, but if the mpv was running under Syncplay it would cause weird issues by either:

Disconnecting by Timed Out when playing through playlists or double-clicking a link
Opening the video on a separate mpv process when dragging the link to mpv itself, causing Syncplay to hang until force-closed.

Thank you~

Hi, thanks for reporting this.
From the paste, it looks like the problem might be in the URL itself. Could you report here the URL you were using or, at least, any special characters that it included?

Hi, thanks for reporting this.
From the paste, it looks like the problem might be in the URL itself. Could you report here the URL you were using or, at least, any special characters that it included?

Fictionalized%20BBC%20Special%20Report%20of%20NATO-Russia%20conflict-VWqWAi_H_9o.mkv
Hosted on an HTTP server, this is the only part of the URL that has special characters on it.

Hi @kathelynn, are you still experiencing this?

I just tested with mpv 0.34.0 on Windows 10 and it seems to work fine with both the encoded and decoded versions of the URLs.


Split tests to add common code to api repo

The code written for library tests which generates random devfile content can also be applied to the api repo, and largely replace the current tests.
First step is to port what tests currently run and set up the framework for sharing code. Once this is in place the tests can be extended over time to cover the full schema. The split will be as follows
api repo:
tests/v200/apiTest/api-test.go - the go test
tests/v200/utils/api/test-utils.go - test utilities specif for api tests, for example reading and compiling the schema file.
test/v200/utils/common/test-utills.go, command-test-utils.go etc. - test utilites to generate valid devfiles . Shared by both sets of tests
as a group this is sufficient to run the tests in the api repo and not include any references to, or code required, by library tests.
library repo:
tests/v2/libraryTest/api-test.go - the go test
test/v2/utils/library/test-utils.go,  command-test-utils.go - tests utilites specific to the library, for example test which update the devfile and verify the content is as expected.
these test require use of test/v200/utils/common/ from the api repo.

Issue is stale, closing for now.


Change box colors to UB-ERI colors (CSS)

UB-ERI colors may be found on the website https://www.uberibz.org/
purple, blue, orange, and green
Change the CSS box style to match these, and adjust text color as needed so text is legible
box styles in custom_style.css are in section /* Custom styles for boxes */

Ill work on this one.

Should I replace the existing section-box and their alternate or create new ones with the UB-ERI color set ?

Good question. You can replace the box styling. We can always access the old ones by 'checking out' a previous state of the repository if needed. Code is never lost in git, which is really nice. This way we can keep the code short(ish) without truly losing anything.


Mention that PRs from forked repos do not work yet

See https://github.com/andrewmcodes/rubocop-linter-action/issues/68#issuecomment-568892868

@eregon does this not address this issue? If not, could you make a PR to the docs instead? https://rubocop-linter-action.readthedocs.io/en/latest/faq/

No, it's too far and too hidden.
If other people, like me, try to use this action with PRs (in general, not just from the same repo) they will be very disappointed and only find this information after spending way too much time trying to set up things and figure out what goes wrong.
This limitation is very clearly the most important limitation of this action.
I think the way to go here is to contact GitHub and ask their plan to address that or if there is any workaround.
But until it works, I believe this warrants a very visible disclaimer in the README, because it just doesn't work for most use cases.

@eregon It is worth mentioning the limitation seems to be with the Checks API not with actions. If it is with actions, it isn't a problem with this action it's an issue with the checkout action. I actually saw a workaround the other day that may be worth trying.

Feel free to improve the message in the README, I don't know the exact cause either.
But please merge this PR, right now I'm not aware of any simple way to make this action work with PRs from a forked repository, and I believe this should be disclaimed in the README.

Will open another PR with the wording from the GitHub docs. FWIW, we could update the action to just output the results in the cli if it's a forked request.
Thank you for bringing this up!

https://github.com/andrewmcodes/rubocop-linter-action/pull/100 looks good, thank you for adding that.


New package: SimSpread v1.0.2

Registering package: SimSpread
Repository: https://github.com/cvigilv/SimSpread.jl
Created by: @cvigilv
Version: v1.0.2
Commit: 91a57876f13f72058224a37442358ab271e4c06c
Reviewed by: @cvigilv
Reference: https://github.com/cvigilv/SimSpread.jl/commit/91a57876f13f72058224a37442358ab271e4c06c#commitcomment-131164272
Description: SimSpread is a novel approach for predicting interactions between two distinct set of nodes, query and target nodes, using a similarity measure vector between query nodes as a meta-description in combination with the network-based inference for link prediction.

close PR


Glossary and Information Sources

Project Tracking: #12
Define any special terminology in the application domain (i.e., not programming terms). Provide a list of useful informational references or links to related or competitive products. Enter this information in your team wiki. Please clearly state the open source license for your project.

@bojotamara is this task completed, or do we still need a list of references?

@WJXHenry It's completed, I'll move it to done


python312Packages.email-validator: 2.1.2 -> 2.2.0

Description of changes
Changelog: https://github.com/JoshData/python-email-validator/releases/tag/v2.2.0

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build python3Packages.email-validator python311Packages.email-validator

please check why the nix manual is failing. I have the feeling that it's the same error I had in https://github.com/NixOS/nixpkgs/pull/329464

It fails because of pydantic test failures
=================================== FAILURES ===================================
_ test_address_invalid[foobar-The email address is not valid. It must have exactly one @-sign.] _

value = 'foobar'

    def validate_email(value: str) -> tuple[str, str]:
        """Email address validation using [email-validator](https://pypi.org/project/email-validator/).

        Note:
            Note that:

            * Raw IP address (literal) domain parts are not allowed.
            * `"John Doe<EMAIL_ADDRESS>style "pretty" email addresses are processed.

        Note:
            Note that:

            * Raw IP address (literal) domain parts are not allowed.
            * `"John Doe<EMAIL_ADDRESS>style "pretty" email addresses are processed.
            * Spaces are striped from the beginning and end of addresses, but no error is raised.
        """
        if email_validator is None:
            import_email_validator()

        if len(value) > MAX_EMAIL_LENGTH:
            raise PydanticCustomError(
                'value_error',
                'value is not a valid email address: {reason}',
                {'reason': f'Length must not exceed {MAX_EMAIL_LENGTH} characters'},
            )

        m = pretty_email_regex.fullmatch(value)
        name: str | None = None
        if m:
            unquoted_name, quoted_name, value = m.groups()
            name = unquoted_name or quoted_name

        email = value.strip()

        try:
            parts = email_validator.validate_email(email, check_deliverability=False)
        except email_validator.EmailNotValidError as e:
>           raise PydanticCustomError(
                'value_error', 'value is not a valid email address: {reason}', {'reason': str(e.args[0])}
            ) from e
E           pydantic_core._pydantic_core.PydanticCustomError: value is not a valid email address: An email address must have an @-sign.

pydantic/networks.py:744: PydanticCustomError

During handling of the above exception, another exception occurred:

value = 'foobar'
reason = 'The email address is not valid. It must have exactly one @-sign.'

    @pytest.mark.skipif(not email_validator, reason='email_validator not installed')
    @pytest.mark.parametrize(
        'value,reason',
        [
<EMAIL_ADDRESS>'There must be something before the @-sign.'),
            ('f<EMAIL_ADDRESS>'The email address contains invalid characters before the @-sign'),
            ('foobar', 'The email address is not valid. It must have exactly one @-sign.'),
            ('foobar@localhost', 'The part after the @-sign is not valid. It should have a period.'),
<EMAIL_ADDRESS>'The part after the @-sign is not valid. It is not within a valid top-level domain.'),
<EMAIL_ADDRESS>', None),
            ('foobar<EMAIL_ADDRESS>None),
<EMAIL_ADDRESS>None),
<EMAIL_ADDRESS>None),
            ('foo<EMAIL_ADDRESS>None),
            ('foo<EMAIL_ADDRESS>None),
<EMAIL_ADDRESS>None),
<EMAIL_ADDRESS>None),
<EMAIL_ADDRESS>None),
            (' @example.com', None),
<EMAIL_ADDRESS>None),
<EMAIL_ADDRESS>None),
<EMAIL_ADDRESS>None),
<EMAIL_ADDRESS>None),
            ('foobar<EMAIL_ADDRESS>None),
            ('foobar<EMAIL_ADDRESS>None),
            ('foobar<EMAIL_ADDRESS>None),
            ('foobar <>', None),
            ('first.last<EMAIL_ADDRESS>None),
            pytest.param('foobar <' + 'a' * 4096 +<EMAIL_ADDRESS>'Length must not exceed 2048 characters', id='long'),
        ],
    )
    def test_address_invalid(value: str, reason: Union[str, None]):
>       with pytest.raises(PydanticCustomError, match=f'value is not a valid email address: {reason or ""}'):
E       AssertionError: Regex pattern did not match.
E        Regex: 'value is not a valid email address: The email address is not valid. It must have exactly one @-sign.'
E        Input: 'value is not a valid email address: An email address must have an @-sign.'

tests/test_networks.py:952: AssertionError
______________________________ test_string_fails _______________________________

    @pytest.mark.skipif(not email_validator, reason='email_validator not installed')
    def test_string_fails():
        class MoreStringsModel(BaseModel):
            str_regex: constr(pattern=r'^xxx\d{3}$') = ...
            str_min_length: constr(min_length=5) = ...
            str_email: EmailStr = ...
            name_email: NameEmail = ...

        with pytest.raises(ValidationError) as exc_info:
            MoreStringsModel(
                str_regex='xxx123xxx',
                str_min_length='1234',
<EMAIL_ADDRESS>                name_email='foobar @example.com',
            )
        # insert_assert(exc_info.value.errors(include_url=False))
>       assert exc_info.value.errors(include_url=False) == [
            {
                'type': 'string_pattern_mismatch',
                'loc': ('str_regex',),
                'msg': "String should match pattern '^xxx\\d{3}$'",
                'input': 'xxx123xxx',
                'ctx': {'pattern': '^xxx\\d{3}$'},
            },
            {
                'type': 'string_too_short',
                'loc': ('str_min_length',),
                'msg': 'String should have at least 5 characters',
                'input': '1234',
                'ctx': {'min_length': 5},
            },
            {
                'type': 'value_error',
                'loc': ('str_email',),
                'msg': (
                    'value is not a valid email address: The email address contains invalid '
                    "characters before the @-sign: '<'."
                ),
                'input'<EMAIL_ADDRESS>                'ctx': {'reason': "The email address contains invalid characters before the @-sign: '<'."},
            },
            {
                'type': 'value_error',
                'loc': ('name_email',),
                'msg': (
                    'value is not a valid email address: The email address contains invalid characters '
                    'before the @-sign: SPACE.'
                ),
                'input': 'foobar @example.com',
                'ctx': {'reason': 'The email address contains invalid characters before the @-sign: SPACE.'},
            },
        ]
E       assert [{'ctx': {'pa...SPACE.', ...}] == [{'ctx': {'pa...SPACE.', ...}]
E
E         At index 2 diff: {'type': 'value_error', 'loc': ('str_email',), 'msg': 'value is not a valid email address: An open angle bracket at the start of the email address has to be followed by a close angle bracket at the end.', 'input'<EMAIL_ADDRESS>'ctx': {'reason': 'An open angle bracket at the start of the email address has to be followed by a close angle bracket at the end.'}} != {'type': 'value_error', 'loc': ('str_email',), 'msg': "value is not a valid email address: The email address contains invalid characters before the @-sign: '<'.", 'input'<EMAIL_ADDRESS>E
E         ...Full output truncated (2 lines hidden), use '-vv' to show

tests/test_types.py:1862: AssertionError
=========================== short test summary info ============================
FAILED tests/test_networks.py::test_address_invalid[foobar-The email address is not valid. It must have exactly one @-sign.] - AssertionError: Regex pattern did not match.
FAILED tests/test_types.py::test_string_fails - assert [{'ctx': {'pa...SPACE.', ...}] == [{'ctx': {'pa...SPACE.', ...}]
==== 2 failed, 4485 passed, 98 skipped, 2 deselected, 12 xfailed in 18.39s =====
/nix/store/jmbs9r5wjaak8qrdf444qpr9v1npyg61-stdenv-linux/setup: line 1655: pop_var_context: head of shell_variables not a function context
error: builder for '/nix/store/ijyxhfkmilwqqd4rdr9yjqnq8jz9sjzd-python3.12-pydantic-2.7.4.drv' failed with exit code 1;

Closing in favor of #329464


send data from android app to hololens

Hi,
I am trying to connect android (As server) to hololens. i tried tcp connection but uwp does not supported.
What connection can i make between the devices?
If i want to use the SharingStage.cs -"Allows you to communicate between a Windows and non-Windows device"   how can i connect android device?
Thanks,
Chen

This question seems to belong in the MixedRealityToolkit-Unity repo. To answer the question, SharingStage.cs relies on a connection to SharingServer.exe. Any device should be able to connect to that IP.


Add a function for reconnect in TcpSocket

Add a function for reconnect in TcpSocket, used by server high performance socket programming
Recommit the code with d code style and unittest.

For me, createSocket is confusing. Socket seems to be std.socket.Socket, not socket_t.
Why don't use 'reconnect'?

It not connect some address, just create a new socket handle.

It not connect some address

Oops, You are right.
Hmm... createNew(Socket)Handle?
std.socket.Socket has handle property.
I can't think of other better names...

Ok, I think use createSocketHandle better.

Thanks!
I noticed that your comment for this method is not documentation comment.
Please add documentation comment for showing up on the API page.
@klickverbot : What do you think about this pull request? I found you at old pull request.

I'm first time to use github  and don't know how to update my old pull request just now.

@klickverbot: works for you?

^_^ Thanks,  can merge my pull request now?

@raojm : Do you have a benchmark?
You wrote "used by server high performance socket programming" in this description.

Yes, it used in my server,  reuse the socket object.

@raojm : Great!
If you have time, please paste a performance result or attach a graph.
@klickverbot : Thought?
If you ok, I merge this pull request.
Currently, you are a heavy user of std.socket.

The simplest change is make function "void setSock(socket_t handle)" public, can somebody change it, and I close my pull request. ^_^

Sorry, make function "void setSock(sockett handle)" protected.

@klickverbot:

feel free to merge whatever you see fit.

Don't worry. I don't merge if someone has a couple of unresolved questions.

Meaningful benchmarks for object creation/GC pressure would probably be hard to come up with since its impact depends very much on the environment.

Yes, but the more comparing elements is better than nothing.
@raojm:
OK. Please close this pull request and re-submit new pull request or issue.

@klickverbot: Thanks for your suggestions.  At the beginning, I just want change the function (void setSock(socket_t handle)) protected, but worry about affect std.socket design.
Ok, I close this pull request and re-submit new pull request to make (void setSock(socket_t handle)) protected.


Implementation Problems with Custom Events in Google Tag Manager

I implemented the tiktok Pixel in GTM and tried to create custom events such as Lead & Booking Lead. The event fires and is getting recognized by tiktok but i can not select these events for optimization purposes in my campaign setup.

Hi, I am sorry for the problems you run into, but we are only the code maintainer of Google Tag Manager template itself.
To get better support from our dedicated support team, please submit a ticket here


Add definition onto DefinitelyTyped

Add definition onto Definitely Typed
https://github.com/DefinitelyTyped/DefinitelyTyped

PRs are welcome :)

Is this really required? VSCode has automatic type adquisition, not sure about other IDEs


Fix LCSC numbers appearing on silkscreen

Fixes #546
The Python scripting API is a bit awkward.  It would be nice if pcbnew.FOOTPRINT.SetField returned the resulting field so we could call SetVisible(False) on it.
I looked for ways to bypass the call to GetFieldByName().  The source code for SetField has some ideas.  But it wasn't working quite right and I would have to modify the function signature to take pcbnew as an argument for use in standalone mode.  I think we would also have to modify our standalone impl to add a couple of extra stub methods.
Thanks @Carbon225 for the example code showing the problem and a prototype solution.

The original push would unconditionally set the LCSC field to be hidden, but I realized that was a bit unclean.  What if a user had manually set the field to be visible?  We wouldn't want the plugin to make it hidden in that case.  So I force-pushed a new implementation which only sets the field to visible if it did not already exist.


Timed out when fetching nodes

I tried searching for my issue already, but couldn't find anyone having the same problem as I am currently.
I don't have this happening all the time, but every so often the plugin will fail to fetch anything from the REST API. The error returned is this (removed all sensitive information and replaced with REDACTED:
ERROR #11321  PLUGIN

"gatsby-source-prismic" threw an error while running the sourceNodes lifecycle:

request to https://REDACTED.cdn.prismic.io/api/v2/documents/search?page=1&pageSize=100&access_token=REDACTED&fetchLinks=&lang=*&ref=YJuQzxEAACAAO38D&q=%5B%5D failed, reason: connect ETIMEDOUT
<IP_ADDRESS>:443

  FetchError: request to https://REDACTED.cdn.prismic.io/api/v2/documents/search?page=1&pageSize=100&access_token=REDACTED&fetchLinks=&lang=*&ref=YJuQzxEAACAAO38D&q=%5B%5D failed, reason: connect ETIME
  DOUT <IP_ADDRESS>:443

  - index.js:1393 ClientRequest.<anonymous>
    [node-fetch-npm-2.1.2-696de0a8dd-9f9fcdc37d.zip]/[node-fetch]/lib/index.js:1393:11

  - node:events:365 ClientRequest.emit
    node:events:365:28

  - node:_http_client:447 TLSSocket.socketErrorListener
    node:_http_client:447:9

  - node:events:365 TLSSocket.emit
    node:events:365:28

  - destroy:193 emitErrorNT
    node:internal/streams/destroy:193:8

  - destroy:158 emitErrorCloseNT
    node:internal/streams/destroy:158:3

  - task_queues:83 processTicksAndRejections
    node:internal/process/task_queues:83:21

This occurs when running gatsby develop (haven't tried running a production build yet, but I assume the same thing would occur there). If I copy the URL that it's trying to fetch from and paste it into a browser, I'm able to get the requested data from the API, so not sure why it's timing out in Gatsby.
It seems that if I do some sort of update on the backend (e.g. add an access token, update access token, etc.) then the problem goes away for a while. I'm not 100% certain that that is what's fixing it, but it's something that I've done and I noticed that the fetch request would succeed after doing those actions.
Any ideas what this could be?
EDIT: Forgot to add which version of the plugin I'm using, which is 3.3.6
EDIT2: Doesn't appear that what I was doing in the Prismic backend is having any effect on this. Since I was updating the backend as I mentioned and it would still break. The only thing that seems to work is retrying the gatsby develop command. I should also mention that I'm using Gatsby v3 and Yarn v2, not sure if that has any effect on this.

Hi @jacknbeans, sorry you didn't get a reply about this sooner. It's difficult to tell exactly what was causing that problem since the network request simply failed.
You could try configuring the plugin to fetch your repository content in smaller batches. By default, the plugin will fetch content 100 documents at a time. This may result in a long API response delay. You can configure this number using the pageSize option (see the API reference here).
// gatsby-config.js
{
  resolve: "gatsby-source-prismic",
  options: {
    repositoryName: "your-repo-name",
    pageSize: 50
  }
}

I'm going to close this issue since it is quite old, but please feel free to reply back here if this is still an issue and I will reopen it.


hi

Describe your bug here.
i set all the weeks on locked but when i played it it kicked me out
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

...Because they're all locked???


Table property filter

What problem does this PR solve?
Use table property filter to speed up cdc sorter, so that CPU usage and latency can be reduced.
Issue Number: close #xxx
Check List
Tests

Unit test

Benchmarks
vanilla v.s. patched, with the default configurations:

vanilla v.s. patched, with modified configurations:

tikv.min-ts-interval = 100ms
cdc.owner-flush-interval = 50ms
cdc.processor-flush-interval = 50ms

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

Codecov Report

Merging #5440 (7600a01) into master (687e248) will decrease coverage by 0.3286%.
The diff coverage is 51.8954%.

Flag
Coverage Δ

cdc
60.6863% <51.8954%> (+0.0877%)
:arrow_up:

dm
51.9869% <ø> (-0.4827%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #5440        +/-   ##
================================================
- Coverage   56.1240%   55.7953%   -0.3287%
================================================
  Files           522        528         +6
  Lines         65325      69556      +4231
================================================
+ Hits          36663      38809      +2146
- Misses        25094      27033      +1939
- Partials       3568       3714       +146

/merge

/merge

/merge

/run-all-tests

/cherry-pick release-6.1


Write a blog article about the kong-authz middleware

See similar ones (OPA and ACL) at: https://docs.konghq.com/hub/

https://docs.konghq.com/hub/kong-inc/opa/
https://docs.konghq.com/hub/kong-inc/acl/

We may name it "casbin".

@rushitote

I will start work on this after APISIX's plugin.

@rushitote hi, has this been done?

Sorry, have not done it yet. I have few other things going on and can't promise any date for this. 🙁


Allow per-publish commit messages when publishing to GitHub

Right now, the only way to set the commit message when publishing to GitHub is in Settings -> Advanced, but this is prohibitively onerous if you want meaningful commit messages.

The "GitHub commit message" field in Settings -> Advanced should be removed.
In Publish on... -> GitHub, a "Commit Message" field should be added with two inputs:
A checkbox, which is checked by default, with the label, "Ask me to provide a commit message every time I click the 'Update publishing' button."
A text input field, which is disabled by default, and becomes enabled when the checkbox is unchecked.

If the box is checked, then every time the user clicks the "Update publishing" button, a modal dialogue appears before the commit occurs, containing a single text input with the label "Commit message:", and two buttons, "Cancel" and "Commit".
If the box is unchecked, then the current behavior is performed, but with the commit message coming from the per-publish dialogue as opposed to from the global settings menu.

What's the status of this issue? The proposed functionality here and in #416 looks like a real enhancement.


Revert "Reland "Android Q transition by default (#82670)""

Reverts flutter/flutter#88409
Caused a performance regression, see #88480.
Unfortunately #88409 also caused some unexpected golden image failures on internal tests, i.e. not just failures that were obviously due to the route change animation (see internal Google issue b/197155815)
Fixes #88480

What we would want here is a transition that used raster operations to both zoom and fade the widget. Unfortunately our zoom and our fade widgets operate independently so they would fight over who was creating the raster copy.
Eventually I could see this working via the following technique - an Opacity widget wrapping a raster scale widget with the scale widget caching the transitioning child and the opacity widget simply overriding the opacity of the scale widget's rendering.
We already have raster caching on the scale transition widgets, enabled by the filterQuality parameter on the transition widget.
Unfortunately the Opacity implementation will either cache its child (resulting in double caching in this case), or use a saveLayer (essentially the same thing, but using temporary memory rather than memory that carries forward between frames). There is already an issue (https://github.com/flutter/flutter/issues/75697) that has been requesting that the opacity layers forward their opacity values to the children for implementation, but we don't have a solution for that yet. When we do, though, the technique I outline here would work much better than what can be accomplished now.

@flar Do you think we can reland this again? I saw the default enabled DisplayList has landed.


Tutorial for Prerequisites

FEATURE REQUEST
What happened:
What you expected to happen:
Create tutorial for Prerequisites before going through the OpenEBS
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

OpenEBS installation/setup tutorials for the following categories are available here: https://docs.openebs.io/docs/ - these contain the pre-requisites for the setup along with the actual procedures/steps.

Developer solutions (Minikube)
On-premise solutions (Vagrant-based, ansible-based for baremetal)
Different-platforms (OpenShift)
Cloud (AWS, GKE, IBM private cloud)

@nsathyaseelan , can you be specific about what pre-requisites are missing/needed in these docs ? Thanks !!

Prerequisites are documented now. Closing.


added circular easing

This PR would belong better on the actuate repo :)
(It won't be merged in here as actuate is on the way out of the core code)


Segmentation fault when enabling Protocol h2

After upgrading to Apache to 2.4.27 (Amazon) Apache threads are terminating intermittently with signal 11, Segmentation fault after a few hundred thousand requests, but only when "Protocol h2" is enabled.
Let me know if additional information is needed. Here is what we're running:
Server Version: Apache/2.4.27 (Amazon) OpenSSL/1.0.2k-fips PHP/5.6.32 mod_fastcgi/2.4.6 mod_qos/11.45
Server MPM: worker
llibcrypto.so.1.0.2k
libnghttp2.so.14.15.2
libz.so.1.2.8
I've taken a number of core dumps and they vary, but the commonality are the call to h2_* and ap_ functions.
Core 1
Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by /usr/sbin/httpd'.
Program terminated with signal 11, Segmentation fault.
#0  qos_get_clientIP (r=r@entry=0x7fc7ac1ade60, sconf=sconf@entry=0x55cdcc2b0c30, cconf=0x0, caller=caller@entry=0x7fc82cf2b1fa "hp",
ip6=ip6@entry=0x7fc80bb0ba00) at mod_qos.c:1963
1963      forwardedForLogIP = QS_CONN_REMOTEIP(cconf->c);
(gdb) where
#0  qos_get_clientIP (r=r@entry=0x7fc7ac1ade60, sconf=sconf@entry=0x55cdcc2b0c30, cconf=0x0, caller=caller@entry=0x7fc82cf2b1fa "hp",
ip6=ip6@entry=0x7fc80bb0ba00) at mod_qos.c:1963
#1  0x00007fc82cf1e0e7 in qos_hp_cc (r=r@entry=0x7fc7ac1ade60, sconf=sconf@entry=0x55cdcc2b0c30, msg=msg@entry=0x7fc80bb0bb58,
uid=uid@entry=0x7fc80bb0bb60) at mod_qos.c:5852
#2  0x00007fc82cf23ca1 in qos_header_parser (r=) at mod_qos.c:8887
#3  0x000055cdcbe81ff0 in ap_run_header_parser (r=r@entry=0x7fc7ac1ade60) at config.c:86
#4  0x000055cdcbe7b681 in ap_process_request_internal (r=r@entry=0x7fc7ac1ade60) at request.c:246
#5  0x000055cdcbe98978 in ap_process_async_request (r=r@entry=0x7fc7ac1ade60) at http_request.c:434
#6  0x000055cdcbe98c64 in ap_process_request (r=r@entry=0x7fc7ac1ade60) at http_request.c:471
#7  0x00007fc836d2ea6b in h2_task_process_request (c=0x7fc7ac1a5fb0, task=0x7fc7ac002970) at h2_task.c:677
#8  h2_task_process_conn (c=0x7fc7ac1a5fb0) at h2_task.c:724
#9  0x000055cdcbe8c780 in ap_run_process_connection (c=c@entry=0x7fc7ac1a5fb0) at connection.c:42
#10 0x00007fc836d2ff1c in h2_task_do (task=0x7fc7ac002970, thread=thread@entry=0x55cdcc268960, worker_id=) at h2_task.c:634
#11 0x00007fc836d33a94 in slot_run (thread=0x55cdcc268960, wctx=0x55cdcc76bea8) at h2_workers.c:230
#12 0x00007fc83bfe0de5 in start_thread (arg=0x7fc80bb0c700) at pthread_create.c:308
#13 0x00007fc83bb0930d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113`
Core #2
#0  0x00007f09cd79e006 in __strcmp_sse42 () from /lib64/libc.so.6 #1  0x00007f09bf3aa3d4 in fcgi_util_check_access (tp=tp@entry=0x7f08d41acf08, path=path@entry=0x7f08d41b0460 "/home/web/path_to_fcgiscript", statBuf=statBuf@entry=0x7f08d41b2878, mode=mode@entry=1,     uid=<optimized out>, gid=<optimized out>) at fcgi_util.c:277 #2  0x00007f09bf3aa7e0 in fcgi_util_fs_is_path_ok (p=0x7f08d41acf08, fs_path=0x7f08d41b0460 "/home/web/path_to_fcgiscript", finfo=0x7f08d41b2878) at fcgi_util.c:387 #3  0x00007f09bf3a4841 in create_fcgi_request (r=r@entry=0x7f08d41acf80, path=path@entry=0x0, frP=frP@entry=0x7f0993951c18) at mod_fastcgi.c:2482 #4  0x00007f09bf3a74f4 in content_handler (r=0x7f08d41acf80) at mod_fastcgi.c:2628 #5  0x0000555889914900 in ap_run_handler (r=r@entry=0x7f08d41acf80) at config.c:170 #6  0x0000555889914e49 in ap_invoke_handler (r=r@entry=0x7f08d41acf80) at config.c:434 #7  0x000055588992a98a in ap_process_async_request (r=0x7f08d41acf80) at http_request.c:436 #8  0x000055588992ac64 in ap_process_request (r=r@entry=0x7f08d41acf80) at http_request.c:471 #9  0x00007f09c8b899fb in h2_task_process_request (c=0x7f08d41a6f50, task=0x7f08d41aaf70) at h2_task.c:666 #10 h2_task_process_conn (c=0x7f08d41a6f50) at h2_task.c:713 #11 0x000055588991e780 in ap_run_process_connection (c=c@entry=0x7f08d41a6f50) at connection.c:42 #12 0x00007f09c8b8aedc in h2_task_do (task=0x7f08d41aaf70, thread=thread@entry=0x55588a45cb78, worker_id=<optimized out>) at h2_task.c:623 #13 0x00007f09c8b8eb44 in slot_run (thread=0x55588a45cb78, wctx=0x555889e98698) at h2_workers.c:228 #14 0x00007f09cdc38de5 in start_thread () from /lib64/libpthread.so.0 #15 0x00007f09cd76130d in clone () from /lib64/libc.so.6

The crash is happening in mod_qos. Maybe you should contact the author of that module, if he/she can identify the cause of this?

I am in touch with the author of mod_qos and he is working on a work around. He wrote and said “the h2 module stumbles over his own mistake: an invalid connection structure used for the internal dummy HTTP/1 requests”. That comment is over my head. I have also seen crash dumps after enabling h2 that cause other mods (mod_logio, mod_fastcgi) to generate a segmentation fault, and the common denominator is enabling h2. I wish I could provide more information. I will provide any additional information if I get it.
Program terminated with signal 11, Segmentation fault. #0  ap_logio_add_bytes_out (c=0x7f1bb4000a30, bytes=15549) at mod_logio.c:70 70          cf->bytes_out += bytes; (gdb) where #0  ap_logio_add_bytes_out (c=0x7f1bb4000a30, bytes=15549) at mod_logio.c:70 #1  0x00007f1c087c525b in send_out (task=task@entry=0x7f1bb4004a50, bb=0x7f1bb419b820, block=block@entry=0) at h2_task.c:111 #2  0x00007f1c087c544d in slave_out (task=task@entry=0x7f1bb4004a50, f=f@entry=0x7f1bb40011f8, bb=bb@entry=0x7f1bb419b820) at h2_task.c:176 #3  0x00007f1c087c598d in h2_filter_slave_output (filter=0x7f1bb40011f8, brigade=0x7f1bb419b820) at h2_task.c:385 #4  0x00007f1c087ae4e9 in h2_filter_headers_out (f=<optimized out>, bb=0x7f1bb419b820) at h2_from_h1.c:607 #5  0x000055978d447bec in ap_content_length_filter (f=0x7f1bb40084f0, b=0x7f1bb419b820) at protocol.c:1758 #6  0x000055978d47a27f in ap_byterange_filter (f=0x7f1bb40084c8, bb=0x7f1bb419b820) at byterange_filter.c:494 #7  0x00007f1c08be3479 in filter_harness (f=0x7f1bb4199570, bb=0x7f1bb419b820) at mod_filter.c:314 #8  0x00007f1bfe9be961 in qos_out_filter (f=0x7f1bb419b5e8, bb=0x7f1bb419b820) at mod_qos.c:9860 #9  0x000055978d44dd2f in default_handler (r=0x7f1bb400b368) at core.c:4756 #10 0x000055978d45f900 in ap_run_handler (r=r@entry=0x7f1bb400b368) at config.c:170 #11 0x000055978d45fe49 in ap_invoke_handler (r=r@entry=0x7f1bb400b368) at config.c:434 #12 0x000055978d474cec in ap_internal_redirect (new_uri=<optimized out>, r=<optimized out>) at http_request.c:765 #13 0x00007f1bfe9a595d in qos_error_response (r=r@entry=0x7f1bb4006a60, error_page=error_page@entry=0x55978e520918 "/feedback.html") at mod_qos.c:3340 #14 0x00007f1bfe9ba772 in qos_header_parser (r=<optimized out>) at mod_qos.c:9053 #15 0x000055978d45eff0 in ap_run_header_parser (r=r@entry=0x7f1bb4006a60) at config.c:86 #16 0x000055978d458681 in ap_process_request_internal (r=r@entry=0x7f1bb4006a60) at request.c:246 #17 0x000055978d475978 in ap_process_async_request (r=r@entry=0x7f1bb4006a60) at http_request.c:434 #18 0x000055978d475c64 in ap_process_request (r=r@entry=0x7f1bb4006a60) at http_request.c:471 #19 0x00007f1c087c4a6b in h2_task_process_request (c=0x7f1bb4000a30, task=0x7f1bb4004a50) at h2_task.c:677 #20 h2_task_process_conn (c=0x7f1bb4000a30) at h2_task.c:724 #21 0x000055978d469780 in ap_run_process_connection (c=c@entry=0x7f1bb4000a30) at connection.c:42 #22 0x00007f1c087c5f1c in h2_task_do (task=0x7f1bb4004a50, thread=thread@entry=0x55978e4a0550, worker_id=<optimized out>) at h2_task.c:634 #23 0x00007f1c087c9a94 in slot_run (thread=0x55978e4a0550, wctx=0x55978e90c728) at h2_workers.c:230 #24 0x00007f1c0da76de5 in start_thread (arg=0x7f1be05a8700) at pthread_create.c:308 #25 0x00007f1c0d59f30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

If the author could explain to me what expectations mod_h2 needs to accommodate, I am sure that can be arranged. Just saying that there is an error does not help any of us. Hopefully he can contact me here or on the Apache httpd dev mailing list. Or he opens a specific bug on bugzilla. That would also be fine. Thanks!

Here's the latest stack trace and notice it does not reference mod_qos. It's been decades since I've written or debugged any C, but the one thing that appears consistent in every stack trace is there eventually is a reference to the c->conn_config and some member of that structure is referenced but it is NULL.
Let me know how I can help.
mod_logio.c:70
logio_config_t *cf = ap_get_module_config(c->conn_config, &logio_module);
cf->bytes_out += bytes; // fails here, cf is NULL
here is the value of the parameters in the last function call:
(gdb) p *c $1 = {pool = 0x7f1bb40009b8, base_server = 0x55978e4eeee8, vhost_lookup_data = 0x0, local_addr = 0x7f1bcc027b10, client_addr = 0x7f1bcc027bd0, client_ip = 0x7f1bcc028258 "<IP_ADDRESS>", remote_host = 0x0,   remote_logname = 0x0, local_ip = 0x7f1bcc028228 "<IP_ADDRESS>", local_host = 0x0, id =<PHONE_NUMBER>33, conn_config = 0x7f1bb4000af8, notes = 0x7f1bb4000de0, input_filters = 0x7f1bb4001308, output_filters = 0x7f1bb40011d0,   sbh = 0x7f1bcc027cd0, bucket_alloc = 0x7f1bb40029c8, cs = 0x0, data_in_input_filters = 0, data_in_output_filters = 0, clogging_input_filters = 1, double_reverse = 0, aborted = 0, keepalive = AP_CONN_CLOSE,   keepalives = 1, log = 0x0, log_id = 0x7f1bb4000fa0 "67-1", current_thread = 0x55978e4a0550, master = 0x7f1bcc027cd8} (gdb) p *c->pool $2 = {parent = 0x7f1bb81bb078, child = 0x7f1bb40069e8, sibling = 0x0, ref = 0x7f1bb81bb080, cleanups = 0x7f1bb4001138, free_cleanups = 0x0, allocator = 0x7f1bb40008c0, subprocesses = 0x0,   abort_fn = 0x55978d43af40 <abort_on_oom>, user_data = 0x0, tag = 0x7f1c087cb25e "h2_slave_conn", active = 0x7f1bb4000990, self = 0x7f1bb4000990, self_first_avail = 0x7f1bb4000a30 "\270\t", pre_cleanups = 0x7f1bb40012e8} (gdb) p *c->conn_config $3 = <incomplete type>
The full trace:
#0  ap_logio_add_bytes_out (c=0x7f13f01a8f60, bytes=223) at mod_logio.c:70
#1  0x00007f147946925b in send_out (task=task@entry=0x7f13f01acf80, bb=0x7f13f01b3d78, block=block@entry=0) at h2_task.c:111
#2  0x00007f147946944d in slave_out (task=task@entry=0x7f13f01acf80, f=f@entry=0x7f13f01a9728, bb=bb@entry=0x7f13f01b3d78) at h2_task.c:176
#3  0x00007f147946998d in h2_filter_slave_output (filter=0x7f13f01a9728, brigade=0x7f13f01b3d78) at h2_task.c:385
#4  0x00007f14794524e9 in h2_filter_headers_out (f=, bb=0x7f13f01b3d78) at h2_from_h1.c:607
#5  0x000055f39b9c7bec in ap_content_length_filter (f=0x7f13f01b09c0, b=0x7f13f01b3d78) at protocol.c:1758
#6  0x000055f39b9fa27f in ap_byterange_filter (f=0x7f13f01b0998, bb=0x7f13f01b3d78) at byterange_filter.c:494
#7  0x000055f39b9f396e in ap_send_error_response (r=0x7f13f01aef90, recursive_error=0) at http_protocol.c:1554
#8  0x000055f39b9f58e9 in ap_process_async_request (r=r@entry=0x7f13f01aef90) at http_request.c:459
#9  0x000055f39b9f5c64 in ap_process_request (r=r@entry=0x7f13f01aef90) at http_request.c:471
#10 0x00007f1479468a6b in h2_task_process_request (c=0x7f13f01a8f60, task=0x7f13f01acf80) at h2_task.c:677
#11 h2_task_process_conn (c=0x7f13f01a8f60) at h2_task.c:724
#12 0x000055f39b9e9780 in ap_run_process_connection (c=c@entry=0x7f13f01a8f60) at connection.c:42
#13 0x00007f1479469f1c in h2_task_do (task=0x7f13f01acf80, thread=thread@entry=0x55f39cbe7a60, worker_id=) at h2_task.c:634
#14 0x00007f147946da94 in slot_run (thread=0x55f39cbe7a60, wctx=0x55f39d0535a8) at h2_workers.c:230
#15 0x00007f147e71ade5 in start_thread (arg=0x7f144e246700) at pthread_create.c:308
#16 0x00007f147e24330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
`

Thanks for the detailed trace. This NULL crash means, that mod_logio had no chance to run its pre_connection hook on the h2 slave connection. This happens, if another module with pre_connection callback runs before and returns something else than OK or DECLINE.
So, it looks to me as if you had a module loaded that messes up connection initialization for h2 sub-connections. Can you disable non-standard modules for testing if the "cures" the mod_logio problem? Thanks!

What is meant by “non-standard modules”? Anything not prepackaged with apache?
Here are what I believe to be “non-standard” modules in use:

mod_qos – disabling this exposes significant security threats
mod_fastcgi – disabling this will slow the server down so much it may reach capacity
mod_php – disabling this will break WordPress
mod_geoip – disabling this will prevent geo targeting ads
mod_unique_id – used by mod_qos
mod_forensic- can be disabled with minimal impact

It is not feasible to disable these modules in our production environment.  The segmentation faults occur 1 or 2 times per hour or about once every 100,000 requests, so reproducing this in a development environment with little or no traffic is going to be very difficult. Any ideas?
# all the proxy modules: (those in use in bold)
LoadModule proxy_module modules/mod_proxy.so
LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_express_module modules/mod_proxy_express.so
LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_hcheck_module modules/mod_proxy_hcheck.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so

Here is the list of mods in use that call  pre_connection() directly:

mod_ssl
mod_reqtimeout
mod_proxy
mod_logio
mod_info
mod_http2

Loaded but not used:

mod_dumpio
mod_proxy_ftp

mod_info would show the hook order for pre_connection.

I went in the direction of disabling mods to see if I could get the problem to go away. Sure enough, after disabling the firewall (mod_qos) there were no segmentation faults for 12 hours. After re-enabling mod_qos a segmentation occurred within 15 minutes.
The core dump matches the one referenced earlier in this thread that fails at mod_logio.c:70.
I will send this information to the author of mod_qos, it would be great if you worked together on this.

Thanks for pursuing this. I sure would like this to be resolved. If there is anything, I can do to help, let me know. If mod_http2 can make anything easier here for module authors, I am all for it.

Am 11.02.2018 um 06:40 schrieb richard-cdp<EMAIL_ADDRESS>I went in the direction of disabling mods to see if I could get the problem to go away. Sure enough, after disabling the firewall (mod_qos) there were no segmentation faults for 12 hours. After re-enabling mod_qos a segmentation occurred within 15 minutes.
The core dump matches the one referenced earlier in this thread that fails at mod_logio.c:70.
I will send this information to the author of mod_qos, it would be great if you worked together on this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

The author of mod_qos responded by updating mod_qos to address this issue. Version 11.49 of mod_qos has been running successfully with mod_http2 for the last 10 hours and during peak traffic. Thanks for your attention to this!

Glad to help. Good to hear that it seems resolved.

Am 11.02.2018 um 18:18 schrieb richard-cdp<EMAIL_ADDRESS>The author of mod_qos responded by updating mod_qos to address this issue. Version 11.49 of mod_qos has been running successfully with mod_http2 for the last 10 hours and during peak traffic. Thanks for your attention to this!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Gather statistics about render times

The project about SQL API limits (CartoDB/cartodb-management#4976) wants to set limits according to the real use of the API. New limits must be based on real use, to gain reliability and user experience at the same time.
Since SQL API calls mean render actions too, we need to measure those render actions as well. So we need to gather statistics with these key points:

For the last 40 days
For every type of account
Organized by percentiles and its time in milliseconds.

The goal is to understand easily how many users are on the percentile x for n milliseconds. With that kind of information, we can take better decisions choosing the new limits.

This is one issue with statistics information from @msaenzde11: https://github.com/CartoDB/cartodb-platform/issues/3266

We got some statistics from the issue mentioned above, @msaenzde11. It's one elaborated by you. Did you remember if those statistics were useful? If at the end of the project were taken as valid and thus used?

@inigomedina @oleurud These statistics were extracted for a 1 week period due to the amount of logs that we constantly generate for the goal of recognizing the amount of users (at each segment) that would be affected after some limits applied to their accounts. I was asuming they had been useful, but don't believe they were applied... It'd be better @rochoa to know it!

Thanks, @msaenzde11. Do we have any kind of dashboard for that? Is there maybe on Kibana a kind of search with filters to gather now these data? Or it was just a script launched at that time?
And, do we have aggregated data? On the issue mentioned above, I see the results for a month period of time, divided into different rows with the numbers for each type of account. But not as an aggregated information.

Hey @inigomedina, it's true, at the end I managed to extract data for one month (I didn't remember, as we talked a lot to do it for a week). Unfortunately it was a script launched at that time.
Regarding aggregated data, which kind of results would you like? Do you mean total percentiles (not caring about account_types), don't you? If this is the case, I believe I still have the raw data, so I can try to provide you with this nrs :)

Well, I think data are distributed daily. They are too distributed in percentiles with ranges that don´t allow to understand types of groups.
To me, it would be much easier to create groups of response times. So you can say: "25% of all of the response times are under 5 seconds", "20% of all of the response times are above 5 seconds and under 10 seconds", etc.

Logs
We will need to read the Postgres logs for the stats gathering. Currently, the Postgres logs are saving the queries with a time duration of more than 2 seconds. If we can to suppose that the limits will be upper than 2 seconds, we can work without changing the database logs. If we can not suppose it, we need to change the database logs from some days and wait some time until the logs have data. Also, this second way increases the time needed for the stats gathering (there will be more stats for processing).
Another important thing, the logs do not save info about the account type.
Source of data
We have 2 options to extract the data:

From Kibana (it reads the Postgres logs)
Straight from Postgres logs

We have code for both cases (a good starting point).
So, as we only need the execution time and who do the request, for me, it is easier to use Kibana.
For last 40 days
It is too much stats. I don't know the log size by day (it depends on the query duration limit), but I expect several gigabytes. Can we use a small dataset? We can show it on the fly.

The first Kibana Dashboards for slow queries and queries times execution made by @oleurud.
http://kibana.cartodb.net/#/dashboard/elasticsearch/Slow queries
http://kibana.cartodb.net/#/dashboard/elasticsearch/Queries duration

The "slow queries" is not made by me ;)

Based on 4 millions of slow queries (queries with a duration of more than 2 seconds) from october 2nd to november 1st, we have the results:

Account
p99
p95
p75
p50

Enterprise
57.584
18.432
6.047
2.762

Free
127.016
24.659
5.386
2.746

Personal
100.126
26.003
8.652
4.385

Great @oleurud. That information is on the ranges we thought. With that numbers, we can start thinking about first date to apply them.


Transaction data missing

My transactions tab in the Bulwark wallet is not listing all my transactions.
The sum total of the CSV export, from the transactions tab, is 428.121418 less than "Total" in the overview tab. Meaning I have more coins than the transactions tab accounts for.
I specifically remember receiving my first ever master node reward on 5/27. All transactions between 5/23, "payment to yourself", to 6/20 also "payment to yourself" are missing.
Recover Transactions 1 has been completed - no results
Rebuild Index has been completed - no results
Rescan blockchain files has been completed - no results
Deleting my wallet, downloading a new wallet and pasting in masternode.conf and wallet.dat has been done - no results
Can you help?

The reason for my persistence on this issue is I'd like to load all my transactions into a tracking software.

Where are we on this?

We actually need some more information on this before we can address the issue;
How did you calculate the expected total?
Did you have All selected in your transactions tab from the dropdown menu of filters?
The CSV export exports your transactions tab exactly as it shows in your wallet, filters and all.
We can't find any errors in the code that would account for such an issue, and are having trouble replicating it, any more information you can provide us would be extremely helpful.

Did my email attachments make it through to you?

Yes, they made it. Can you confirm that you exported the data while you had All selected as your filter?

The screen shot shows all and I haven’t changed it. I will play with that
filter tomorrow but doubt that’s it. I’ve rebuilt the wallet 4 times.
On Wed, Sep 5, 2018 at 5:05 PM Michael Terrance<EMAIL_ADDRESS>wrote:

Yes, they made it. Can you confirm that you exported the data while you
had All selected as your filter?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bulwark-crypto/Bulwark/issues/109#issuecomment-418896930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlqX2X7VE6HxRKKjmrdPUlqgho6gVUw1ks5uYEq1gaJpZM4V0qJH
.

--
Ken Bangs
<EMAIL_ADDRESS>|<PHONE_NUMBER> mb

I double checked and can confirm that both filters are set to all. I even
change the date filter to custom and the 5/27 to 6/20 aren't pulling up.
On Wed, Sep 5, 2018 at 5:12 PM, KW Bangs<EMAIL_ADDRESS>wrote:

The screen shot shows all and I haven’t changed it. I will play with that
filter tomorrow but doubt that’s it. I’ve rebuilt the wallet 4 times.
On Wed, Sep 5, 2018 at 5:05 PM Michael Terrance<EMAIL_ADDRESS>wrote:

Yes, they made it. Can you confirm that you exported the data while you
had All selected as your filter?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bulwark-crypto/Bulwark/issues/109#issuecomment-418896930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlqX2X7VE6HxRKKjmrdPUlqgho6gVUw1ks5uYEq1gaJpZM4V0qJH
.

--
Ken Bangs
<EMAIL_ADDRESS>|<PHONE_NUMBER> mb

--
Ken Bangs
<EMAIL_ADDRESS>|<PHONE_NUMBER> mb

Interesting. I'll report back when I have more news or recommendations for you.

This relates to #81 and is currently being investigated.  For the time being you can pull all the transactions from the block explorer: https://explorer.bulwarkcrypto.com/api/address/{wallet_address} by replacing {wallet_address} if that helps.


[🐞] In server$(function(){ ~ }) "this" is undefined

Which component is affected?
Qwik Runtime
Describe the bug
When I'm using routeAction$ to handle form submit and once I use more than 1 server$ to complete action it breaks because I'm using server$ to access cookies or env variables, also when in server$ I use more than 1 other server$ functions it breaks, but works fine with one.
Am I doing something wrong?

Reproduction
https://stackblitz.com/edit/qwik-starter-ugmdvt?file=src%2Froutes%2Findex.tsx
Steps to reproduce
No response
System Info
  System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (8) x64 Intel(R) Xeon(R) CPU           W3550  @ 3.07GHz
    Memory: 17.80 GB / 27.39 GB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 20.5.1 - ~/.nvm/versions/node/v20.5.1/bin/node
    npm: 9.8.0 - ~/.nvm/versions/node/v20.5.1/bin/npm
    bun: 1.0.11 - ~/.bun/bin/bun
  Browsers:
    Chrome: 120.0.6099.109
    Chromium: 120.0.6099.109
  npmPackages:
    @builder.io/qwik: ^1.3.1 => 1.3.1
    @builder.io/qwik-city: ^1.3.1 => 1.3.1
    undici: ^5.26.0 => 5.28.2
    vite: ^5.0.6 => 5.0.10

Additional Information
4:27:12 PM [vite] Internal server error: Cannot read properties of undefined (reading 'cookie')
  File: /var/www/node/project_6/src/routes/index.tsx:8:1
  6  |  });
  7  |  export const getCookie2 = server$(function () {
  8  |      return this.cookie.get("cookie2")?.value;
     |   ^
  9  |  });
  10 |
      at /var/www/node/project_6/src/routes/index.tsx:8:17
      at invoke (/var/www/node/project_6/dist-dev/tsc-out/packages/qwik/src/core/util/implicit_dollar.js:1099:22)
      at /var/www/node/project_6/dist-dev/tsc-out/packages/qwik/src/core/util/implicit_dollar.js:6917:25
      at then (/var/www/node/project_6/dist-dev/tsc-out/packages/qwik/src/core/util/implicit_dollar.js:337:54)
      at /var/www/node/project_6/dist-dev/tsc-out/packages/qwik/src/core/util/implicit_dollar.js:6903:14
      at invokeQRL (/var/www/node/project_6/dist-dev/tsc-out/packages/qwik/src/core/util/implicit_dollar.js:6934:26)
      at serverQrl_stuff_wOIPfiQ04l4 (/var/www/node/project_6/node_modules/@builder.io/qwik-city/index.qwik.mjs:1101:21)
      at invoke (/var/www/node/project_6/dist-dev/tsc-out/packages/qwik/src/core/util/implicit_dollar.js:1099:22)
      at /var/www/node/project_6/dist-dev/tsc-out/packages/qwik/src/core/util/implicit_dollar.js:6917:25
      at then (/var/www/node/project_6/dist-dev/tsc-out/packages/qwik/src/core/util/implicit_dollar.js:337:54)

Thanks @notcod I close this one b/c it's a duplicate of this one https://github.com/BuilderIO/qwik/issues/4417


APIM-6981: fix long words break

Issue
https://gravitee.atlassian.net/browse/APIM-6981
Description
Breaking long words in document. Used overflow-wrap for modern browsers and word-wrap for older browsers compatibility.
Additional context

4.1.x is no longer suported. Can you target 4.2.x branch for your PR?
Could you also provide some before/after screenshots? When fixes are about CSS stuffs, it's easier to validate with a screenshot ;)
thank you