Common annotations

What this PR does:
Adds  common annotations field to the CRD and propagates these to all resources created by the operator. I'm sure we'll miss some at first since there isn't really a single place where this stuff is handled, but here's a first attempt.
Which issue(s) this PR fixes:
Fixes #1094
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

Closing this as the design has changed.


[Metrics Advisor] Fix datafeed ingestion failing live test

Currently, refreshIngestion tests were failing of reason:
Status code 400, "{"code":"BadRequest","message":"Backfilling data slice before the ingestion start time or the first data slice in database. Backfill Start Time: 2020-01-01 00:00:00.0, First DataSlice in database: 2020-08-30 00:00:00.0"}
Seems the datafeed that we were using in the test had dataStartForm later than the backfill start time provided and so the error . Hence changed the ingestion time to later.

/azp run java - metricsadvisor - tests

/azp run java - metricsadvisor - tests

/azp run java - metricsadvisor - tests


Each time creates new log file in amazon S3

Hi,
I am trying to log the errors in the same file every time, but it creates a new file each time I request.
Please help me to fix this

Hi, this won't be possible, the AmazonS3 sink uses the sink under https://github.com/serilog/serilog-sinks-periodicbatching to provide events in batches and therefore writes one file per batch.
It's not really reasonable to write logs to one file only if you ask me:

Your local file system is getting filled up (Assume a log file with 2 GB over a time) as the sink first writes logs to a local file and then pushes it to S3.

Theoretically you can upload files up to 5TB to S3 (https://aws.amazon.com/de/blogs/aws/amazon-s3-object-size-limit/), but it will take a lot of time to upload and you also might loose data while transfering (Or the upload breaks and you will have to retry it again).
S3 doesn't allow to append to a file directly (Check https://stackoverflow.com/questions/41783903/append-data-to-an-s3-object) --> Every change to your log file would need to either push the local file completely again to overwrite the one in S3, which limits your local file system as already described, or to download the file from S3 locally, append and overwrite the file in S3 again. Both operations are time-consuming and might get expensive (As you pay per up-and download in most cases in S3).

As a workaround for you (Nothing the sink can provide), you can aggregate your files with services like Amazon Elastic Map Reduce (https://aws.amazon.com/emr/) or maybe Amazon AWS Kinesis Firehose (As described in the linked Stackoverflow post as second answer).
I hope, that this helps you, but as described (Mainly of reason 3 as S3 doesn't allow to append to files), there is nothing I can do to change this behaviour right now.


Create Dataloader; Add more datasets

I'd like to generate more interesting training data. One idea I had was generating prime numbers represented in binary. I'm sure there are more interesting ideas.
Ideally the datasets would all use the same abstract class with common methods for generating batches. There would also be a setting in the config.yaml to specify which dataset ought to be used.

I've got a PR for a basic dataloader out now; see #13.
As mentioned in the PR, it is designed for smaller datasets which fit in RAM. In the future we may need to extend it so that it loads minibatches one at a time.
I'll probably make a separate case for that feature, so all that remains for this case is to add a few more example datasets.

Added a few more datasets. They need documentation, but I'll get to that later. I'm going to close this for now.


Loaded code and code displayed are different?

In the Non-determinism example on the website, the backtrack handler code is written like this
let backtrack = handler
  | effect Decide k ->
    (* We use a second handler to handle the continuation. *)
    handle continue k false with
    | effect Fail _ -> continue k true
;;

However, it seems to me, that the paper defines it like follows
let backtrack = handler
  | effect Decide k ->
    (* We use a second handler to handle the continuation. *)
    handle continue k true with
    | effect Fail _ -> continue k false
;;

Notice that the continuations are reversed
When I try loading the code in the REPL, the handler behaves correctly (I believe), even though the code shown above the REPL is wrong.
I am not sure whether this is a misunderstanding on my side or a bug, but I would be appreciative if someone could take a look at it.

On a second look, I didn't notice that backtrack is later overriden in the code...

Hmmm, the second definition was probably unintentional, so I removed it. Thanks!


feat:#509 updated strategy page css and pager

Updated css of the strategy list page
Added pagination component
Implemented pagination functions

All good!

Good job as you have to modify a lot from the old version!
I didn't use strategy/new to create any strategies as it's pretty messy atm. When you test it, did you generate new strategies directly using our backend api?


check file size

In a frozen app, using 'pkg_resources' the file size returned is zero, and with development server the files/images are not shown. With cherrypy wsigserver, throw a exception with ValueError about content-length. With this patch, all is fine.
With this patch, exclusively when content-length is zero, this information isn't passed and firefox and chrome accept the image/scripts/etc and show all.

@untitaker at #870 you says:
"Your usecase makes sense, but you have to keep in mind that a content length of zero is valid as well."
I believe I read any RFC on the content-length zero, but this must be one of those cases where the browser does not follow the specification.

RFC 2616 section 14.13 says:

Any Content-Length greater than or equal to zero is a valid value.

However, RFC 2616 section 4.4 enumerates many cases when a Content-Length header MUST NOT be given. Example:

If a Content-Length header field (section 14.13) is present, its decimal value in OCTETs represents both the entity-length and the transfer-length. The Content-Length header field MUST NOT be sent if these two lengths are different (i.e., if a Transfer-Encoding header field is present). If a message is received with both a Transfer-Encoding header field and a Content-Length header field, the latter MUST be ignored.

and:

Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding. If the message does include a non- identity transfer-coding, the Content-Length MUST be ignored.

We can on and on about this. If this were really to be RFC compliant, greater care should be taken as to when the Content-Length header is sent.
All that being said, I think the worse thing to do is send a Content-Length of 0 when it is, in fact, not 0. Perhaps I’m mis-understanding the cases in which the problem manifests itself.

@TomCorwine thanks for the comment.
And I think that is good to be RFC compliant, but the worse is not having an solution to this problem.
And I agree with you, it´s too bad to send a wrong value.

i wonder if this could be solved differently, i think the setuptools/pkg_ressources file object is wrong in this context (claiming zero size instead of real size)

The zero value is defined at wsgi.py#L551

Ah, this seems reasonable. If it is not filesystem-bound, I believe we can take the performance hit. @RonnyPfannschmidt Do you agree?

The change at resource_stream to resource_string and BytesIO is exactly what happens at pkg_resources. The statement is something like this:
def get_resource_stream(manager, path): return BytesIO(get_resource_string(manager, path)
So what I'm doing is just increasing the len(s), and I think there will be no change in performance.

Okay cool.


new maintainer for shiyan

Apply to be maintainer. Contributions are shown in the link: https://github.com/openkruise/kruise/issues?q=involves%3Ashiyan2016

+1
Yan Shi is a senior member of OpenKruise. She mainly works on typical workloads including CloneSet and Advanced StatefulSet, fixes bugs and optimizes features like pprof, rate limiter, lifecycle hook and defaults injection. She also used to speak at offline meetup and share their experience of application deployment based on OpenKruise in production.
Thanks for all her contribution.

/woof

/cc @Fei-Guo @furykerry

+1
welcome shiyan

+1 welcome


chore: fix build on mac m1

What problem does this PR solve?
Issue Number: ref #6233
Problem Summary:
FAILED: dbms/src/Functions/CMakeFiles/clickhouse_functions.dir/FunctionsRegexp.cpp.o
/Library/Developer/CommandLineTools/usr/bin/c++ -DBOOST_BIND_GLOBAL_PLACEHOLDERS -DBOOST_CONTEXT_EXPORT="" -DBOOST_CONTEXT_NO_LIB -DBOOST_CONTEXT_STATIC_LINK -DBOOST_FIBER_NO_LIB -DBOOST_FIBER_STATIC_LINK -DBOOST_NO_CXX98_FUNCTION_BASE -DBOOST_SYSTEM_NO_DEPRECATED -DCARES_STATICLIB -DFIU_ENABLE -DLZ4_DISABLE_DEPRECATE_WARNINGS=1 -DMULTIPLE_CONTEXT_GTEST -DPOCO_STATIC -DPOCO_UNBUNDLED_ZLIB -DTIFLASH_COMPILER_VPCLMULQDQ_SUPPORT=0 -DTIFLASH_ENABLE_ASIMD_SUPPORT=1 -DTIFLASH_SOURCE_PREFIX=\"/Users/qizhi/p/tiflash\" -I/Users/qizhi/p/tiflash/contrib/libdivide -I/Users/qizhi/p/tiflash/contrib/libmetrohash/src -I/Users/qizhi/p/tiflash/contrib/libfarmhash -I/Users/qizhi/p/tiflash/dbms/src -I/Users/qizhi/p/tiflash/contrib/tiflash-proxy/raftstore-proxy/ffi/src -I/Users/qizhi/p/tiflash/cmake-build-debug/dbms/src -I/Users/qizhi/p/tiflash/contrib/double-conversion -I/Users/qizhi/p/tiflash/contrib/boost -I/Users/qizhi/p/tiflash/contrib/xxHash -I/Users/qizhi/p/tiflash/contrib/libpcg-random/include -I/Users/qizhi/p/tiflash/contrib/libcityhash/include -I/Users/qizhi/p/tiflash/libs/libcommon/include -I/Users/qizhi/p/tiflash/cmake-build-debug/libs/libcommon/include -I/Users/qizhi/p/tiflash/libs/libpocoext/include -I/Users/qizhi/p/tiflash/contrib/poco/Data/include -I/Users/qizhi/p/tiflash/contrib/poco/Foundation/include -I/Users/qizhi/p/tiflash/contrib/zlib-ng -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/zlib-ng -I/Users/qizhi/p/tiflash/contrib/poco/Util/include -I/Users/qizhi/p/tiflash/contrib/poco/XML/include -I/Users/qizhi/p/tiflash/contrib/poco/JSON/include -I/Users/qizhi/p/tiflash/contrib/poco/Net/include -I/Users/qizhi/p/tiflash/contrib/cctz/include -I/Users/qizhi/p/tiflash/contrib/lz4/lib -I/Users/qizhi/p/tiflash/contrib/zstd/lib -I/Users/qizhi/p/tiflash/contrib/client-c/third_party/libfiu/libfiu -I/Users/qizhi/p/tiflash/contrib/prometheus-cpp/core/include -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/prometheus-cpp-cmake/core/include -I/Users/qizhi/p/tiflash/contrib/prometheus-cpp/push/include -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/prometheus-cpp-cmake/push/include -I/Users/qizhi/p/tiflash/contrib/prometheus-cpp/pull/include -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/prometheus-cpp-cmake/pull/include -I/Users/qizhi/p/tiflash/contrib/cpptoml -I/Users/qizhi/p/tiflash/contrib/magic_enum/include -I/Users/qizhi/p/tiflash/contrib/poco/NetSSL_OpenSSL/include -I/Users/qizhi/p/tiflash/contrib/poco/Crypto/include -I/Users/qizhi/p/tiflash/contrib/xxHash/cmake_unofficial/.. -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/kvproto/cpp -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/kvproto/cpp/kvproto -I/Users/qizhi/p/tiflash/contrib/grpc/include -I/Users/qizhi/p/tiflash/contrib/abseil-cpp -I/Users/qizhi/p/tiflash/contrib/client-c/include -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/grpc/third_party/cares/cares -I/Users/qizhi/p/tiflash/contrib/grpc/third_party/cares/cares -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/tipb/cpp -I/Users/qizhi/p/tiflash/cmake-build-debug/dbms/src/Storages/DeltaMerge/File/dtpb -I/Users/qizhi/p/tiflash/contrib/libbtrie/include -I/Users/qizhi/p/tiflash/cmake-build-debug/contrib/libfarmhash -isystem /Users/qizhi/p/tiflash/contrib/fmtlib-cmake/../fmtlib/include -isystem /Users/qizhi/p/tiflash/libs/libsymbolization/include -isystem /Users/qizhi/p/tiflash/contrib/boringssl/include -isystem /Users/qizhi/p/tiflash/contrib/protobuf/src -isystem /Users/qizhi/p/tiflash/contrib/re2 -isystem /Users/qizhi/p/tiflash/cmake-build-debug/contrib/re2-cmake -pipe -march=armv8+crc+simd  -fno-omit-frame-pointer  -Wall -Wno-unused-command-line-argument  -Wnon-virtual-dtor  -Wextra -Werror -g -g3 -ggdb3 -O0 -fverbose-asm -fno-inline  -arch arm64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk -fcolor-diagnostics -fPIC -DDUMMY_BACKTRACE -std=gnu++17 -MD -MT dbms/src/Functions/CMakeFiles/clickhouse_functions.dir/FunctionsRegexp.cpp.o -MF dbms/src/Functions/CMakeFiles/clickhouse_functions.dir/FunctionsRegexp.cpp.o.d -o dbms/src/Functions/CMakeFiles/clickhouse_functions.dir/FunctionsRegexp.cpp.o -c /Users/qizhi/p/tiflash/dbms/src/Functions/FunctionsRegexp.cpp
In file included from /Users/qizhi/p/tiflash/dbms/src/Functions/FunctionsRegexp.cpp:17:
In file included from /Users/qizhi/p/tiflash/dbms/src/Functions/FunctionsRegexp.h:35:
In file included from /Users/qizhi/p/tiflash/dbms/src/Functions/Regexps.h:16:
In file included from /Users/qizhi/p/tiflash/dbms/src/Common/OptimizedRegularExpression.h:145:
/Users/qizhi/p/tiflash/dbms/src/Common/OptimizedRegularExpression.inl.h:620:34: error: reinterpret_cast from 'long' to 'Int64' (aka 'long long') is not allowed
        auto skipped_byte_size = reinterpret_cast<Int64>(matched_str.data() - (subject + prior_offset));
                                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/qizhi/p/tiflash/dbms/src/Common/OptimizedRegularExpression.inl.h:683:16: note: in instantiation of member function 'OptimizedRegularExpressionImpl<false>::replaceAllImpl' requested here
        return replaceAllImpl(subject, subject_size, res_data, res_offset, repl, byte_pos);
               ^
/Users/qizhi/p/tiflash/dbms/src/Common/OptimizedRegularExpression.inl.h:739:5: note: in instantiation of member function 'OptimizedRegularExpressionImpl<false>::replaceImpl' requested here
    replaceImpl(subject, subject_size, res_data, res_offset, repl, byte_pos, occur);

What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

lgtm

/merge

/check-issue-triage-complete

/merge


Error when running CellPose

Hi!
We got this error:
Traceback (most recent call last):
  File "/g/funcgen/galaxy-production/tools/cellpose_segmentation/0.6/cp_segmentation.py", line 94, in <module>
    main(args.inputs, args.img_path, args.img_format, args.output_dir)
  File "/g/funcgen/galaxy-production/tools/cellpose_segmentation/0.6/cp_segmentation.py", line 57, in main
    **options)
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/site-packages/cellpose/models.py", line 282, in eval
    stitch_threshold=stitch_threshold)
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/site-packages/cellpose/models.py", line 542, in eval
    flow = np.array([dx_to_circ(dP[1:,i]) for i in range(dP.shape[1])])
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/site-packages/cellpose/models.py", line 542, in <listcomp>
    flow = np.array([dx_to_circ(dP[1:,i]) for i in range(dP.shape[1])])
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/site-packages/cellpose/models.py", line 64, in dx_to_circ
    flow = (utils.hsv_to_rgb(HSV)*255).astype(np.uint8)
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/site-packages/cellpose/utils.py", line 23, in hsv_to_rgb
    r, g, b = hsv_to_rgb_channels(h, s, v)
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/site-packages/numpy/lib/function_base.py", line 2108, in __call__
    return self._vectorize_call(func=func, args=vargs)
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/site-packages/numpy/lib/function_base.py", line 2186, in _vectorize_call
    ufunc, otypes = self._get_ufunc_and_otypes(func=func, args=args)
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/site-packages/numpy/lib/function_base.py", line 2146, in _get_ufunc_and_otypes
    outputs = func(*inputs)
  File "/g/funcgen/galaxy-production/database/dependencies/_conda/envs/mulled-v1-a3d8e3d2223f740ae00d18494ade7b9bef6e0c49ca4e41a5d033b2a48d633f57/lib/python3.7/colorsys.py", line 146, in hsv_to_rgb
    i = int(h*6.0) # XXX assume int() truncates!
ValueError: cannot convert float NaN to integer

Do you have an idea what the issue may have been?

It looks like the output flows are NaN? Who's cellpose wrapper is this? It's hard for me to tell what's going on without seeing the source code

closing due to inactivity but let us know if you still have issues


[tests-only] code cleanup

delete unused functions
standardise names of interaction functions
clarify what the variables username and password are used for by renaming to adminUsername and adminPassword
change all occurrence of hard-coded admin username to use variable from config file

https://drone.owncloud.com/owncloud/owncloud-sdk/1608/3/11 fails.
It needs some more love.

increasing the log-level seems to make it pass, strange


using make -j for building binaryen is killing my Macbook Air M1 and gitpod

using make -j for building binaryen ( https://github.com/near/near-sdk-js/blob/master/setup.sh#L22 ) is killing my Macbook Air M1 and gitpod.
and binaryen readme does not suggest using -j ( https://github.com/WebAssembly/binaryen#building )

can also confirm that after removing the make -j I'm able to create a JS contract, build and deploy a JS contract VM from my M1 Mac.


VS Code: remove sign-out menu

Context

Sign out immediately instead of showing the quick-pick menu.
Slack discussion

Test plan
Signed-out locally.

Nice, thank you @valerybugakov!
We should remove signout from AuthMenuType too now it's unused, and rename the menu item from Sign Out... (the ... signifies it isn't immediate and has more steps) to Sign Out.

@toolmantim, good points! https://github.com/sourcegraph/cody/pull/1053 fixes them.


/articles mobile: secondary nav text colour + chevron cut off

Site:

Figma:

Reproduced again on aisafety.info at dd1e10e and locally at 8b67900 using chrome and safari on iPhone.
Perhaps this is a webkit mobile browser issue again.

Seems like the style is coming the "user agent stylesheet", so my thinking is that this button just needs a colour class.


I can't update by line item properties

Please list the package(s) involved in the issue, and include the version you are using
checkout-ui-extensions0.26.0,
Describe the bug
I am trying to update the properties of line items using this syntax
let result = await applyCartLinesChange({
type: 'updateCartLine',
id: id,
attributes:  [{
key: '_sale',
value: 'final sale'
}]
})
}
it says success but when i made a purchase this properties doesn't show up in line items

Steps to reproduce the behavior:

Expected behavior

I want when my order get purchased .. i want it to have final sale properties
Screensho

ts

Additional context
I am using shopify script line item to add the final sale tag .. now i want to migrate it to shopify function and it is not working

Hi @ShresthaPrerana. I think I can explain the issue. Keys that start with an underscore, _, are hidden. It's an undocumented feature.


Broken Link

Searched for mint and clicked on "Mint Basic Tokens"

@michaeleberhardt310, sorry about that broken link—I just removed that how-to topic because it was no longer working as documented. I'm not sure how to fix the search to clear it from the results.


Hide the close icon when there is only one trade

Hi,
Attached contained few changes that should address the card here https://trello.com/c/gKGLvNRi/186-remove-the-close-button-if-there-is-only-one-trade-window for your perusal.

Coverage decreased (-0.02%) to 31.375% when pulling ed88774b09040f92ed92bd73d5282b754b822f2c on nuruddeensalihu:nuru/hide_close_btn into e15127850a5172c5f0146f310f3477c50e9fb6d3 on binary-com:master.


which variable represent the http_proxy url?

when use ats to access ,for example:   curl -x xxx.myproxy.com:8080 www.baidu.com
i want print  proxy url:xxx.myproxy.com in access_log.  which variable represent？

@calavera @janfrode @biilmann  help

We don't get the name of the proxy server that is used from curl -x.  We do have the hii, hiih, and php to record the ip and port that the client is connecting to:  https://docs.trafficserver.apache.org/admin-guide/logging/formatting.en.html#network-addresses-ports-and-interfaces

phn is apparently undocumented, but contains the proxy.config.proxy_name in records.config (https://docs.trafficserver.apache.org/admin-guide/files/records.config.en.html#proxy-config-proxy-name)

If this is still an issue please reopen.


style:removes button outline when focused, instead replacing it with a change to the button's secondary color

style:removes button outline when focused, instead replacing it with a change to the button's secondary color
adds comments/documentation to global.css and button.tsx

https://www.a11yproject.com/posts/2013-01-25-never-remove-css-outlines/

This is a really good point
I'll make a new pull request that only removes the outline when it is focused and not tabbed to, using the focus-visible attribute
I made it change colors because I foresaw this problem, but in hindsight, for the visually impaired, this would not be sufficient.


Information line randomly displays and won't disappear

Playing Assassin's Creed III Liberation, 'Holy Shit' profile loaded. The green info display "Configuration loaded. : 4" displays and doesn't disappear unless I open and close the LOLIcon menu.
I know nothing is random, but I haven't figured out what triggers it.
Also, I'd love an option just to turn off the display. Won't solve the underlining issue, but for me would make it moot.

Does it for other games also.


fix: rename X40 classes

Codecov Report
Attention: Patch coverage is 0% with 14 lines in your changes missing coverage. Please review.

Project coverage is 24.30%. Comparing base (2f53134) to head (d69e987).

Files
Patch %
Lines

midealocal/devices/x40/__init__.py
0.00%
7 Missing :warning:

midealocal/devices/x40/message.py
0.00%
7 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #183      +/-   ##
==========================================
- Coverage   24.30%   24.30%   -0.01%
==========================================
  Files          78       78
  Lines        6800     6801       +1
==========================================
  Hits         1653     1653
- Misses       5147     5148       +1

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


[Profilepage] See user information and upload avatar

Add presenter

Optional: Add profile picture upload and display during game.

You can see user information and scores. You cannot upload avatar, but that is a wontfix for now.


LWRP idempotence

I am sad that this cookbook has been skewing my resources-executed numbers but we tend to prefer resources to attribute-loops
I did my best not interfere with mixed use of params and LWRPs (if that's a thing) / be as backwards compatible as possible
Notably, one can paste the first commit's added block (default.rb L38-49) in front of include_recipe 'sysctl::default' as a workaround with the current released version of this cookbook

:+1: Please take a look at this. I too noticed the params are executed every time.

:+1:


Fails to build when used in a esp32 project with feature "std"

Cargo project generated using template from https://github.com/esp-rs/esp-idf-template
Added pn532 = { version = "0.2", features = ["std"] } to dependencies.
Full error log: https://gist.github.com/JohnTheCoolingFan/ca330da3b7e187e28124d98f0573abba

Thanks for the report!
The std feature pulls in the serialport crate, which only compiles for some targets.
Currently that is all that the std feature does, so there is no reason to enable it for the esp32.
I'll try and document this better 😃

Alright, thanks for clarifying

should be documented now


Change interace hash method to #get_hash

per https://github.com/jamesroutley/write-a-hash-table/pull/4 @freefal @jamesroutley

Thanks!

5


Course5 - Kannada JavaScript

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
JavaScript tutorial in Kannada
Why is this valuable (or not)?
it will teach people who speak Kannada how to code in JavaScript and be able to make anything they want
How do we know it's really free?
it is on YouTube for free
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

For youtube, we prefer "playlist" links and the name of the producer/creator. docs/CONTRIBUTING.md#platforms-and-access-notes

For youtube, we prefer "playlist" links and the name of the producer/creator. docs/CONTRIBUTING.md#platforms-and-access-notes

finished

you need to start from a fresh branch for each PR!


Use XDomainRequest instead of ActiveXObject

Since this package makes use of this line - ( xhr.withCredentials = true; ) in the polyfill script on line 19
It would be better to use new XDomainRequest() than new ActiveXObject('Microsoft.XMLHTTP') on line 17
I hope you see reason with me
Thanks

@isocroft XDomainRequest is obsolete and replaced by XMLHttpRequest  in Internet Explorer 10+

If this is a major issue I'm happy to merge in a pull request but I don't see the problem considering IE 8 and 9 are almost a decade old

Alright.... l'll send a PR (sorry, Africa still has XP / Vista hanging around)


Lag while typing k

I have mapped jk to ESC(normal mode) using ZVM_VI_INSERT_ESCAPE_BINDKEY=jk
but when I type 'k' i noticed a lag. can i fix this

can i add both ??

Hi @MohamedIrfanAM ,
Currently, you can do by below code snippet:
# The plugin will auto execute this zvm_after_init function
function zvm_after_init() {
  zvm_bindkey viins  'jk' zvm_exit_insert_mode
  zvm_bindkey viins  'kj' zvm_exit_insert_mode
}

Thanks and regards

Thank you


[PLAT-1085] Make backwards compatible changes using 2to3

Purpose
In order to defray some of the big changes that will arise by switching over to Python3 we've decided to switch backwards compatible changes first so we don't have to go through the process all at once.
Changes

convert map function
convert dicts methods
convert iteritems/itertools methods
convert filter functions
convert reduce function
convert some basestring types to str
convert next function

QA Notes
Not sure how you would test something so big! Passes unittests etc.
Documentation
Not a user facing change.
Side Effects
We might want to break this up into smaller piece if it's a lot to test. The changes are mostly automatic and probably not breaking, but likely some areas aren't touched by unittests
Ticket
https://openscience.atlassian.net/projects/PLAT/issues/PLAT-1085

Aha! It looks like the dict fixer was run twice: first in https://github.com/CenterForOpenScience/osf.io/pull/8726/commits/d2dc159db46e769ecf071db0c8a9cd4991c7b12e then again in https://github.com/CenterForOpenScience/osf.io/pull/8726/commits/da6f0a2b3217f2e1b173fd5dbe49b6b458ef90eb , resulting in the list() wrapping.
@Johnetordoff Can you run all the fixers in one go?

The problem with running them all at once is that I've cherry-picked out some of the breaking conversions, but it shouldn't be hard to do again now that I know what they are.

@Johnetordoff It makes sense that d.keys() -> list(d.keys()). The problem was that this PR was doing d.iterkeys()-> d.keys() -> list(d.keys()), where d.keys() is the desired output. This was happening because 2to3 was run more than once.


ARROW-5501: [R] Reorganize read/write file/stream functions

This patch rationalizes the functions that read/write IPC format data. Summary:

read_<format>() and write_<format>() functions are end-user facing and should follow R idioms: format denotes the file (or connection, or buffer) format being read/written. Readers return an R data.frame (default) or a Table if the argument as_data_frame = FALSE. Writers return the data object, invisibly.
To make these patterns consistent, the functions read_table() and read_record_batch() are deprecated, and their functionality is folded into other functions. As they appeared to have been more developer-oriented functions, it is fair to expect their users (if they exist) to handle slightly less R-friendly interfaces.
Since Arrow IPC has two formats, file (aka Feather) and stream, read/write_ipc_stream() are added as siblings to read/write_feather().
A special write_to_raw() function is added to wrap write_ipc_stream() and return the raw vector containing the buffer that was written. This is to support a use case observed in sparklyr.
Because the intent is ambiguous between IPC stream vs. file format, read/write_arrow() are soft deprecated (documentation advises not to use them, but they do not warn). sparklyr uses write_arrow() and we don't want to raise a deprecation warning until we can switch it to use `write_to_raw() after the 0.17 release.

Thanks for the pedantry, @wesm. I was asking for it :)
In sum, I agree about s/stream/ipc_stream/g, and some of the things you said don't make sense were mainly to keep existing tests passing. I'll look to deprecate the stranger ones. Re read_arrow and write_arrow, the latter is used by sparklyr, so I'd rather deprecate it after 0.17 (and after I submit a PR to sparklyr to stop using it).

I see. Yeah on read_arrow/write_arrow I would say to make them a "soft" deprecation (basically put in the docstring "please don't use this, use this other thing instead") and then hard deprecate (with a warning message or something) in the next release. Agree with not scaring sparklyr users

@wesm I did some further cleanup and, wearing my own pedantic hat, am much more satisfied. PTAL at your convenience; summary updated to reflect the latest. I'll merge now/soon/GitHub willing but I can address any doubts in https://issues.apache.org/jira/browse/ARROW-8300.

Thanks for wrapping this up. On the Feather side

Since Arrow IPC has two formats, file (aka Feather) and stream, read/write_ipc_stream() are added as siblings to read/write_feather().

Let's add read/write_ipc_file also? I'm wary of the "version" option in "write_feather" and the Feather version inference capability in "read_feather". It's potentially confusing and we may choose to add options to write_ipc_file/read_ipc_file that are more developer centric, having to do particular with the IPC format, that are not relevant or appropriate for the Feather APIs.
IMHO it's best for "Feather format" to remain an abstracted higher-level concept with its use of the "IPC file format" as an implementation detail, and segregated from the other things.

Made https://issues.apache.org/jira/browse/ARROW-8324 for that, don't think it's urgent to add


unique filter broken with multi-word parameters?

Hello, I have JSON data that includes multi-word parameters. When I try the unique filter in my ng-repeat I get the error that the second word in the parameter is an unexpected token.
Does the unique filter support multi-word keys/parameters? I've tried wrapping in single quotes, double curly braces to no avail.
(in the following, histConfig.column is a scope variable referring to a multi-word key in importedData)
ng-repeat="row in importedData | uniq:histConfig.column"
error msg:
Error: [$parse:syntax] Syntax Error: Token 'Provider' is an unexpected token at column 11 of the expression [Referring Provider] starting at [Provider].

Copied in the following for a custom filter and it worked fine. Maybe a problem with parsing multiword keys?
return function (arr, field) {
          var o = {}, i, l = arr.length, r = [];
          for(i=0; i<l;i+=1) {
            o[arr[i][field]] = arr[i];
          }
          for(i in o) {
            r.push(o[i]);
          }
          return r;

perfect to me thanks kanethal . I create new filter and use your code. Work fine!


Which characters are not allowed in object/materials/etc names?

So that's is another issue that came up in 3ds Max besides Unicode characters. In 3ds Max, object and material names can contain absolutely any characters - including spaces, commas, slashes, quotes etc. However if an object name includes f.e. spaces, it is no longer selectable by the Nuke Cryptomatte plugin.
The Cryptomatte specification does not say anything about these characters. Should they be replaced by some other valid character, f.e. underscores? Or should the Cryptomatte plugin for Nuke be updated to handle such object names properly? How should quotes be treated (i.e. should they be escaped with a back slash)?
Best regards,
Vlado

Hi Vlado,
I think all characters should be allowed that can be encoded into the json manifest. However you're right that the Nuke implementation does not currently support this.
Right now, if you're using the sidecar_manifests dev branch, here's what's not supported:

Names that start or end with white space
** In the release branches, any white space does not work
Names that start with "<" or end with ">".
Names containing commas (",").

This is a limitation of the plugins that we should look at fixing. There's no fundamental reason why these cases should not be supported. Thanks for the report.

I've made a change that should allow anything you can put into a valid JSON with the exception of strings that both start and end with <>. We'll consider whether this limitation should be an implementation detail of the decoder or something to go into the spec, but for now it's an implementation detail.
The plugin uses YAML internally to encode and decode the matte list. The reason for this is yaml lists look basically like what we've been doing- a comma separated list of strings without quotes becomes a list of strings, but it can also handle all the more difficult cases as well. For example: [hello, <1.3>, "string with spaces, and commas"]. The Nuke plugin removes the "[]" characters in the list shown users. (This is just an implementation detail of the Nuke plugins).


two hands demo

two hands demo

Could you elaborate on what you want to see here?

I want to take the knife out of its sheath, and when it is drawn out, follow the shape of the sheath, and when it is fully drawn out, the knife can be waved freely. When I draw the knife, I should follow a certain path, and only after I pull it out can I wave it by myself. What should I do?


Not working on mobile?

I tested the demo page my mobile phone (Samsung N7100) and the phone mask filter seems like not working?
Anyone have this problem before?

You got any solution for mobile ?


feat(ci): add lint and sca workflows using shared actions

Can I get a review on the shared action integration for Luacheck/ rust-clippy and rust sca using grype ?
How to test and provide feedback?

When the PR is merged, linters (lua / rust) runs on other PR and main branches and create checks and status reports based on changed and dirty files between commits
Semgrep and rust CVE analysis is reported to GitHub code scanning for public repositories.

Shared actions used:

https://github.com/Kong/public-shared-actions/tree/main/code-check-actions/rust-lint
https://github.com/Kong/public-shared-actions/tree/main/code-check-actions/lua-lint
https://github.com/Kong/public-shared-actions/tree/main/security-actions/semgrep
https://github.com/Kong/public-shared-actions/tree/main/security-actions/scan-rust

@saisatishkarra For future reference, could you make sure 3rd party actions like tj-actions/changed-files@v36 are pinned by their hash? It is a security best practice.

Also, the ubuntu-20.04 runner has been removed by GitHub and caused all PR to not able to pass the required check. Could you make sure to use ubuntu-latest for future actions?


Argentina BUR4

The report resolves individual gases only for 2018, for 1990-2018 gas basket time series exist. However BUR3 data was made available in spreadsheet containing all data is available from inventariogei.ambiente.gob.ar. So before reading the data from pdf check if the spreadsheet has been updated (last check: Jan 24, 2022, not updated).
Data is in IPCC 2006 categories with very good sectoral resolution.

read and integrated


How the finetuning output looks like?

Thanks for the great resources.
I tried to finetune with my custom data, and could see the output meesage. After then, when I tried to inference with the model I trained, the output looked totally messed up which is not trained.
my output message for the training is,
{'train_runtime': 5.8012, 'train_samples_per_second': 1.207, 'train_steps_per_second': 1.207, 'train_loss': 2.129377910069057, 'epoch': 1.0}

Is it the correct output that we need to see? I am wondering if it just trains for a single epoch originally.
Thanks,

My mistake to control epochs paramters


docs: update sync service and migrations docs.

See e.g.:
https://deploy-preview-91--electric-sql-website.netlify.app/docs/api/service
https://deploy-preview-91--electric-sql-website.netlify.app/docs/usage/data-modelling/migrations
Note that this is based on the previous deployment concepts PR at https://github.com/electric-sql/electric/pull/794
@magnetised -- afaics, there's nothing in our docs atm about the special prisma username stuff. Except various example connection strings that start with<EMAIL_ADDRESS>We need to either document it and explain why the username is prisma or stop using it in our examples. What is the actual status with this?
@alco -- is the information at https://deploy-preview-91--electric-sql-website.netlify.app/docs/api/service#database-user-permissions correct? I based it on my previous "lower permissions are coming" content. I suspect your more detailed investigations may provide more accurate info? And does it vary by Postgres version? if so, perhaps we can document that here?

@alco let me know if good to go or if you still need to look at the the sync service page. Thanks!

@thruflo still looking at it. I won't hold you back for long, just minor corrections. More significant content updates can be done in as a followup.

@thruflo I'm done with my review. Pushed one new commit to fix a broken link for LOGICAL_PUBLISHER_PORT.

Yup, sorry, have pushed my version (with extra thes).


Update nscplugin, sbt-scala-native, ... to 0.4.7

Updates

org.scala-native:nscplugin
org.scala-native:sbt-scala-native
org.scala-native:scala3lib
org.scala-native:scalalib
org.scala-native:test-interface

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

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-native" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #1095.


Update rss.mdx

There is no information on how to remove trailing slash from rss feed output. Since the rss does not rely on astro.config.mjs trailingSlash option, there is a risk of user sending mixed signals to SE on what url is canonical.

Description (required)

Related issues & labels (optional)

Closes #
Suggested label:

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note
Locale

src/content/docs/en/guides/rss.mdx
Source changed, localizations will be marked as outdated.
en

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


chore(main): release 1.0.8

:robot: I have created a release beep boop
1.0.8 (2023-12-16)
Bug Fixes

edit workflows (58c9362)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/nbtca/blogs/releases/tag/v1.0.8 :sunflower:


Update the manifest of serving to 0.14.0

Fixes #
Proposed Changes

Release Note

@jcrossley3 just added them.

/test pull-knative-serving-operator-upgrade-tests


Update delete_old_notifications task to allow configurable time period with default of 30 days

ref: https://github.com/ohcnetwork/care/pull/1328

[ ] Add settings variable NOTIFICATION_RETENTION_DAYS for delete time period
[ ] Update tests

Hello @sainak ,
I would like to work on this issue!

Hey @arilloid , are you working on this issue ?

Hello @Alokih ,
Yes, I have finished implementing the change, I am trying to test it right now, but have troubles with the dev environment

Okay @arilloid 👍


Add method seriesType

Type of PR: enhancement
PR checklist:

[x] Addresses an existing issue: fixes #670
[x] Includes tests
[x] Documentation update

Overview of change:
Add method seriesType. ex: lineSeries.seriesType(); // 'Line'
Is there anything you'd like reviewers to focus on?

Thanks for you contribution!

Thanks for you contribution!


fast objects

heya, im trying to figure out what param i can tinker with to track fast moving objects. in my case the object is present in 4,5 frames. its being detected by yolo, but tracker wont pick up on it.  i set distance to a higher amount and thinking transience might be it but i dont 100% understand it.

was an error with my detector. all good now!

im still facing some issues with it. im trying to understand inertia but havent found an explanation that i get. i understand inertia has to do with resistance of expected movement, but the way you explain it in your docs with counting down etc just throws me iff. what practical effect does those two params have for my objects?
my scenario is that a bunch of objects gets thrown down a slide at various speeds. the faster ones gets picked up by my detector, but norfair wont put them in matched.

Yeah sure, how it works is quite simple. What we consider to be an object or not depends on how many hits that object gets. We consider a hit to be a match between an object and a detection.
The lifecycle of an object is as follows:

When a detection doesn't get matched to any object, it is transformed into a potential object. It starts with a hit counter of 1, as it has just been created, and has only gotten a single hit.
As the new potential object starts getting new hits, its hit counter starts increasing. When its hit counter goes over hit_inertia_min  + initialization_delay the object is now considered a real object, and is returned to the user for the first time.
After the object is considered real, it will start getting more matches and misses, and its hit counter will go up and down. If it goes below hit_inertia_min the object is considered dead and Norfair deletes it. If it goes above hit_inertia_max its hit counter won't increase anymore, as it could increase infinitely and it would have too much 'inertia" and would then take too long to die after it stops getting matches. So an object's hit counter will always stay between hit_inertia_min and hit_inertia_max as long as the object is alive.

In your case you would need to set initialization_delay and hit_inertia_min to a very low number so you ensure your objects start being considered real as soon as it appears. Be careful, if you set these number too low Norfair wont filter out incorrect detections.
Good luck!

thanks a bunch for explaining that thoroughly, man. appreciate it.

No problem, we should probably be adding this to the documentation now that I think about it 😂. @dekked this could be an easy first PR for someone coming into Norfair.


Don't raise on association not found if any sti class in the hierarch…

PR for myself while not adhering to rails standard

Keep going! I love what you're up to here.


Suggestion: ifon/ifoff methods

I'm building a system that relies heavily on events, and especially emitting events that begin their life as dom events. I don't want every single object i write to bind dom events, because I fear the performance gods. So what I'd like to do is bind events only on the condition that someone up the line has bound an event that requires knowing when a particular dom event has happened. Therefore, I've determined I want something like the following interface:
// should be triggered when the first listener for the 'click' event is added
// (regardless of whether its done through on, onAny, once, or many)
emitter.ifon('click', function() {
   domNode.addEventListener('click', someCallback)
})
// should be triggered when the last listener for the 'click' event is removed
// (regardless of whether this is done through off, offAny, or as a result of 'once' or 'many' calls being fulfilled
emitter.ifoff('click', function(callback) {
   domNode.removeEventListener('click', someCallback)
})

I'm also wondering what your opinion is about the performance related to event emit chains. Without this kind of feature, the system I'm building would essentially attach a listener to every single dom object on the page. I'm assuming that would be no good.

I just realized this could also be used as an alternative to onAny, since you could always use ifon to register new callbacks as needed.

Hmm, my immediate reaction is -1 on this idea because it makes the API surface area larger, it's also a pretty unique use case. If onAny could be used as an alternative to your proposal, are there any new/discrete benefits that this offers?

I actually said ifon could be used as an alternative to onAny - not the other way around. The benefit is that you can know when an event is needed and when its not. onAny doesn't do that for you. If ifon could be called without an event so that its called for any event, then it could be used as an alternative to onAny cause you could do something like:
emitter.ifon(function(event, callback) {
   emitter.on(event, function() {
      // do whatever you'd do in onAny
   })
})

Deleted the comment i just wrote (like 30 minutes ago) cause I realized i'm wrong. ifon can't be used to implement or as an alternative to onAny. I think my brain was trying to tell me that it solves the use case I had for onAny. My use case for using onAny is bubbling events from one emitter through another (so that emitter A emits all the events emitter B emits).
But again, the major things you get with ifon is that you can know when someone is listening for an event or not, and that allows you to not attach lower level event handlers until they're needed - which could potentially be very beneficial for performance.

Have you looked into using the newListener event for this problem?

It might be possible to implement onAny using newListener and removeListener. Problem witih newListener is that its emitted before the listener is actually attached. I was pretty unclear what the sequence of events are in that, so I ended up implementing it another way.

Gonna close this since the discussion seems to have died. Re-open it if you need any more clarification.


Reconstruct original text without extra whitespace tokens after highlighting

Extra whitespace is added to text after tokenization and decoding from highlighting, we can remove the extra whitespace using the original text and update highlighted text characters accordingly

In particular, "COVID - 19", "SARS - CoV - 2", "2019 - nCov" come up repeatedly.


Activity classifier should support test dataset with fewer unique labels than the training set

As described in #964 - the user has introduced larger number of labels in the test set than the number of labels the model have been trained on.
Instead of giving him an explicit error right during the predict() portion of evaluate() - he got a less intuitive error:
ToolkitError: Size of prediction probability vector(3) != number of classes(1)

We should probably detect these cases explicitly, right in the beginning of predict(), and give an informative error.

Actually, it looks like the opposite: the model was trained with three possible labels (hence the model outputting a prediction vector of size 3), but the dataset being evaluated only has 1 class. This should not generate an error at all and should just work.

Ultimately this is due to these Python-based toolkits not inheriting all of the better-tested code paths from the C++ supervised-learning base classes.... It's possible that just printing a better error message is the correct fix in the short term, with the long-term fix to replace all of the Python code and move to C++.

FYI the relevant code is here: https://github.com/apple/turicreate/blob/f51c2e57ec5b31e8fa8a786127e074dd9f2a50a5/src/unity/toolkits/activity_classification/sequence_iterator.cpp#L33

It turns out that this problem is not specific to the activity classifier: it's arguably an API bug in the evaluation toolkit. I filed #1007. For the purposes of the evaluate() method here, we can work around this issue by providing the class index map explicitly, instead of allowing the evaluation toolkit to infer it from the test-set labels.