Add build subcommand and expose configtest.

I can't figure out how to get the new commands to appear in the
'--help' output, but they appear in the 'describe' subcommand output.
I'm not sure if build should actually be restricted to stopped mode.
I'm also not sure if you'll want this one, but I find it useful :)

@bitdancer I need to try that one out for myself :)
Guess yesterday I stumbled over the describe command for the same thing and it actually could be better. Maybe your PR will do what I'd expect the command to do. I'll let you know

@bitdancer

I'm not sure if build should actually be restricted to stopped mode.
I'm usually building while the service is still running. I'd say it is better to not restrict it

Hey @bitdancer, do you want to change the build subcommand to always work? i'd merge it with those changes.

Finally found some time to circle back to this and update the PR.  Sorry it took so long :(

Heyhey @bitdancer, no problem :) Thanks for the changes!


Different Search Result on PowerShells

What can cause this? I search it but I cannot find it.
(Freshly installed OS. Windows OS Build: 17134.345)
Thank you for your responses.
Edit:

This is really weird...

Looks like you have the system version of powershell installed (v5) and powershell core installed as well.

Looks like you have the system version of powershell installed (v5) and powershell core(6.1) installed as well.

I know that I'm having powershell and powershell core (pwsh). What I don't understand is that, why same search function have different outputs?

That was caused by a missing $_.Name call in apps_in_bucket(). PowerShell Core handles the FileInfo-Result from Get-ChildItem differently.

That was caused by a missing $_.Name call in apps_in_bucket(). PowerShell Core handles the FileInfo-Result from Get-ChildItem differently.

Thank you for fix and response.


Cache restore not working - connect ETIMEDOUT <IP_ADDRESS>:9000

Hi,
I am trying to use the cache action with self-hosted runners (in GKE) towards a GHES instance. It seems that saving the cache is just fine, but on restore I receive error connect ETIMEDOUT <IP_ADDRESS>:9000
Environment:
GHES 3.7.4
Self Hosted runner in GKE (base image Ubuntu 22.04 / Runner Agent 2.298.2)
Saving cache:
Post job cleanup.
/usr/bin/tar --posix -cf cache.tgz --exclude cache.tgz -P -C /runner/_work/repo/repo --files-from manifest.txt -z
Cache Size: ~436 MB (456671309 B)
Cache saved successfully
Cache saved with key: Linux-maven-b478786cd53f1de0795ba40ef14f77c81b6ea366bb1970e27f680154fee686c5

Restoring cache:
 ##[debug]Resolved Keys:
##[debug]["Linux-maven-b478786cd53f1de0795ba40ef14f77c81b6ea366bb1970e27f680154fee686c5","Linux-maven-"]
##[debug]Checking zstd --version
##[debug]Unable to locate executable file: zstd. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
##[debug]
##[debug]Resource Url: https://<git-server-url>/_services/artifactcache/aysbnhh9gKLGnX4JIYuIQjZECZmeQnOBpj8GsGJwFdlfESQdA4/_apis/artifactcache/cache?keys=Linux-maven-b478786cd53f1de0795ba40ef14f77c81b6ea366bb1970e27f680154fee686c5%2CLinux-maven-&version=c538a492dc53daaed119aaacbe9be444dd6f0478f3c1e96eef74be5e3b7be6fa
::add-mask::***
##[debug]Cache Result:
##[debug]***"scope":"refs/pull/2/merge","cacheKey":"Linux-maven-b478786cd53f1de0795ba40ef14f77c81b6ea366bb1970e27f680154fee686c5","cacheVersion":"c538a492dc53daaed119aaacbe9be444dd6f0478f3c1e96eef74be5e3b7be6fa","creationTime":"2023-02-08T17:43:30.33Z","archiveLocation":"***"***
##[debug]Archive Path: /runner/_work/_temp/6219a271-8daf-4924-8d78-8d1f70ac401a/cache.tgz
##[debug]Use Azure SDK: true
##[debug]Download concurrency: 8
##[debug]Request timeout (ms): 30000
##[debug]Cache segment download timeout mins env var: undefined
##[debug]Segment download timeout (ms): 3600000
##[debug]downloadCache - Attempt 1 of 2 failed with error: connect ETIMEDOUT <IP_ADDRESS>:9000
##[debug]downloadCache - Attempt 2 of 2 failed with error: connect ETIMEDOUT <IP_ADDRESS>:9000
Warning: Failed to restore: downloadCache failed: connect ETIMEDOUT <IP_ADDRESS>:9000
Cache not found for input keys: Linux-maven-b478786cd53f1de0795ba40ef14f77c81b6ea366bb1970e27f680154fee686c5, Linux-maven-
##[debug]Node Action run completed with exit code 0
##[debug]MSYS='winsymlinks:nativestrict'
##[debug]Save intra-action state CACHE_KEY = Linux-maven-b478786cd53f1de0795ba40ef14f77c81b6ea366bb1970e27f680154fee686c5
##[debug]Finishing: Cache local Maven repository

I cannot figure out what is wrong here.
Thanks

Hi @enricojonas ,
From the debug output

##[debug]Checking zstd --version
##[debug]Unable to locate executable file: zstd. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

I think we have been run into a similar issue in the past and the solution was to simply provide this binary and add it to the PATH on the self-hosted runner.

@hendrik-schaffer thanks for reaching out. I have tried to integrate this and it didn't do any change. It seems to be connected to how our GHES is setup and it's using the storage backend through that address which is not reachable from the runners - so the error message is not very descriptive. I will close this issue here as we this is an infrastructure problem.

@enricojonas I would suggest creating a Support ticket for this since it is related to GHES.

@pdotl yes, that's what we did. Github support helped us to identify the issue.

@pdotl yes, that's what we did. Github support helped us to identify the issue.

What was the issue?

The issue was that we were using MinIO storage - apparently it is not working with this.

The issue was that we were using MinIO storage - apparently it is not working with this.

Thanks for the quick reply! I've been trying to resolve the same problem with GHES but haven't found a solution yet.

Same problem here, did you find any solution. However we are using DELL ISILON S3 compatible storage


Core firebird if db close connect

How to catch an error if the connection is closed?
Error in manual update: connection shutdown
db_soci_error: connection shutdown
terminate called after throwing an instance of 'soci::firebird_soci_error'
what():  connection shutdown
Aborted (core dumped)
Try {
...
}
catch (firebird_soci_error const &e)
{
_CLOGERR(OIMPORT) << "db_soci_error: " << e.what();
}
catch (soci::soci_error const &e)
{
_CLOGERR(OIMPORT) << "soci_error: " << e.what();
}

Catching the exception should definitely work and seemingly does. It's not clear why does your program crash, please try debugging it or, at the very least, reproduce the issue in the SOCI test suite.


Any way to add the username who signed into grafana to send to Matomo?

This way we can track users as well

Yeah, sounds great!


added a detailed read me page

Added a detailed read me page

That looks great. A couple of slight things:

The big W in welcome doesn't render correctly on GitHub so maybe it should just be removed...? There might be another way though.
I'd rename Contributing to Contributors, since Contributing usually refers to how other people can help with the project.
Should it use UK or US spellings? 😅

Thank you for your input, I have fixed everything


Envoy terminates if user follows "Customizing Istio Metrics"

Using 1.6.0-beta.1 the instructions caused me to crash my pods and put them into a CrashLoopBackOff state.
Step 3 says to use a text editor and "locate the envoy.wasm.stats extension configuration."  I found three such examples.  I modified the first one.  After my step 4 changes, it looks like
        name: istio.stats
        typed_config:
          '@type': type.googleapis.com/udpa.type.v1.TypedStruct
          type_url: type.googleapis.com/envoy.extensions.filters.http.wasm.v3.Wasm
          value:
            config:
              configuration: |
                {
                  "debug": "false",
                  "stat_prefix": "istio",
                  "metrics": [
                   {
                     "name": "requests_total",
                     "dimensions": {
                       "destination_port": "destination.port",
                       "request_host": "request.host"
                      }
                    }
                 ]
                }

(This was somewhat tricky because YAML requires extra spacing.  I believe I got it right.)
Step 6 is to apply an annotation "using the following command".  No command is given ... we see text to type into kubectl edit deployment.  I did use a command so that I could produce repeatable output for this Issue:
kubectl patch deployment productpage-v1 --type=json --patch='[{"op": "add", "path": "/spec/template/metadata/annotations", "value": {"sidecar.istio.io/extraStatTags": "destination_port,request_host"}}]'

After that the pods go into CrashLoopBackOff.  kubectl logs shows
2020-05-12T20:32:05.569257Z	critical	envoy main	[external/envoy/source/server/server.cc:97] error initializing configuration 'etc/istio/proxy/envoy-rev0.json': Tag name 'destination_port' specified twice.
Tag name 'destination_port' specified twice.
2020-05-12T20:32:05.573563Z	error	Epoch 0 exited with error: exit status 1
2020-05-12T20:32:05.573608Z	info	No more active epochs, terminating

@gargnupur can you take a look at this?

@esnible : Does this error go away if you don't do step 6 and still see the metrics?

https://preliminary.istio.io/docs/tasks/observability/metrics/customize-metrics/
OK, I deleted and recreated bookinfo but skipped step 6.  Bookinfo works.
I supplied some load and did kubectl exec reviews-v1-5cddfdfd64-f54qf -c istio-proxy -- curl 'localhost:15000/stats/prometheus' | grep request_host.  Also tried grep destination_port.  Neither had data.
There was lots of data if I did grep istio.  Repeated the curl/grep with productpage pod, same results.

@esnible repeating what I added in the chat. please modify all three places in step 3.

OK, made the JSON change to all three places in step three.  I did this using a tricky kubectl patch but I believe I did it correctly.  HOWEVER, THE VALUES SENT TO PROMETHEUS ARE NOT WHAT I EXPECTED.
First, here is my configuration:
kubectl -n istio-system get envoyfilter stats-filter-1.6 -o jsonpath='{.spec.configPatches[0].patch.value.typed_config.value.config.configuration}'
// { "debug": "false", "stat_prefix": "istio", "metrics": [ { "name": "requests_total", "dimensions": { "destination_port": "destination.port", "request_host": "request.host" } } ] }
kubectl -n istio-system get envoyfilter stats-filter-1.6 -o jsonpath='{.spec.configPatches[1].patch.value.typed_config.value.config.configuration}'
// { "debug": "false", "stat_prefix": "istio", "metrics": [ { "name": "requests_total", "dimensions": { "destination_port": "destination.port", "request_host": "request.host" } } ] }
kubectl -n istio-system get envoyfilter stats-filter-1.6 -o jsonpath='{.spec.configPatches[2].patch.value.typed_config.value.config.configuration}'
// { "debug": "false", "stat_prefix": "istio", "disable_host_header_fallback": "true", "metrics": [ { "name": "requests_total", "dimensions": { "destination_port": "destination.port", "request_host": "request.host" } } ] }

Next, here is the output of kubectl exec reviews-v1-5cddfdfd64-f54qf -c istio-proxy -- curl 'localhost:15000/stats/prometheus' | grep request_host:
istio_requests_total{response_code="200",reporter="destination",source_workload="productpage-v1",source_workload_namespace="default",source_principal="spiffe://cluster.local/ns/default/sa/bookinfo-productpage",source_app="productpage",source_version="v1",destination_workload="reviews-v1",destination_workload_namespace="default",destination_principal="spiffe://cluster.local/ns/default/sa/bookinfo-reviews",destination_app="reviews",destination_version="v1",destination_service="reviews.default.svc.cluster.local",destination_service_name="reviews",destination_service_namespace="default",destination_port="x#",request_protocol="http",request_host="reviews:9080",response_flags="-",grpc_response_status="",connection_security_policy="mutual_tls",source_canonical_service="productpage",destination_canonical_service="reviews",source_canonical_revision="v1",destination_canonical_revision="v1"} 12

The problem is the request_host="reviews:9080" (request_host same as destination?) and the destination_port="x#" (I expected 9080, or at least an integer)

what value did you expect for request_host?  that looks reasonable to me, assuming the client used a host header of reviews:9080.
destination_port indeed looks problematic. is it potentially a problematic UTF-8 encoding or something? what does it look like in prom? do all the destination_port values have x# or are they random strings?

destination_port doesn't look right... will try to repro this in istio/proxy..

I was able to replicate this. I've attached my filters and file I used to install (with MeshConfig)
I installed using ./istioctl manifest apply --set profile=default -f extra_stat_tags.yaml
filter-iop.tar.gz

@jacob-delgado : what if you don't set extraStatTags? do you see the crash still?

@gargnupur If I only modify the stats-filter-1.6 the pods continue to stage.

@jacob-delgado : and you see the configured attributes in istio_requests_total in prometheus right?
@mandarjog , @douglas-reid : I don't think we need the extraStatsTags option in documentation? We see the new attributes in prometheus without it and with it, it thinks that definition of the attribute is happening twice and thus crashes.
And I think destination_port is coming up as random in prometheus, because in istio/proxy we see it as "NO_______",

what value did you expect for request_host? that looks reasonable to me, assuming the client used a host header of reviews:9080.

My misunderstanding?  I expected request.host to be the requesting host/workload, not the HOST header on the HTTP request.

what does it look like in prom? do all the destination_port values have x# or are they random strings?

In the Prometheus web UI I see the same destination_port="x#" that I saw with curl.

@kyessenov 's suggestion works(https://github.com/istio/envoy/pull/215).. of changing it to string(int_value)
so, I think we should do following change in the doc:

Remove extraStatTag step for now
and change destination_port to string(destination_port) and add a note that for int values, add a string label above.


Fix .scarymovie command (Halloween)

Relevant Issues
Closes #769
Description
I modified the code to use the proper API endpoint, and changed the HTTP parameters accordingly.
Also, I removed a reference to an environment variable, that was unnecessary. ( That parameter (TMDB_TOKEN) wasn't even present in the list on the Wiki).
I have also added a new filter "include_adult": "false" , to make sure it won't return inappropriate results.
(That was my first ever pull request to an open-source project, I'd like to apologize for the possible mistakes I made, in advance)
Did you:

[x] Join the Python Discord Community?
[x] Read all the comments in this template?
[x] Ensure there is an issue open, or link relevant discord discussions?
[x] Read the contributing guidelines?

@D0rs4n Thank you for the PR!


Write Java Unit Test for: ProjectController Due3/9

This issue was moved to Code4SocialGood/c4sg-services#19


Add root cd command

Navigate to repo root

Probably more complex than it may superficially seem -- as script is executing as child cd'ing parent is... tricky


Rich

https://github.com/richsumn84/mars-exploration-challenge

https://github.com/richsumn84/mars-exploration-challenge/pull/1#


Implement ThreadAccess typestate for Ref

This (should) make it sound to convert Shared references to Variant, which has Send.
This is a draft. There are known issues and some more changes are planned to address them.
Known issues

I find it inconvenient that references can't be used as parameters safely now. I'm thinking about adding a new type for temporary references that tracks typestate (TRef<'a, T, Access>?), so we are able to prevent unique references from being passed into methods.
Would it make sense to allow passing ThreadLocal references into methods? I guess with the thread-safety guideline assumption this is probably sound but I'm not really sure. Need to think about it a bit more.
Dodge the creeps compiles, but the enemies aren't moving. This needs to be fixed.
Currently the bindings won't complain when non-unique Unique references are dropped. I added a runtime check originally, but that caused the compiler to complain about specialized Drops. Not sure if there is a good way to do this currently without ATCs or Drop specialization.
We can't have safe conversions to Ref<T, Unique> because the reference count isn't exposed in the Godot API. Too bad!
The Ref type exposed a nice interface that removed the need for the ugly <T as GodotObject>::PersistentRef qualified type syntax, but inside it's a pile of unspeakable horror due to lack of proper specialization...

Close #447

Also, the thread_access types tend to invade user code a fair amount. Maybe it would make sense to create some type aliased for them, so they would be easier to use (and understand)? e.g.
// Ref already has Access = Shared
pub type UniqueRef<T> = Ref<T, Unique>;
pub type LocalRef<T> = Ref<T, Local>;

Maybe Ptr and Ref should be separated after all? Some copy-pasting will have to happen but maybe it's better than this specialization business.

Updated the code with the TRef. This removed a few non-essential unsafes in the examples, but at the cost of dynamic casts because there isn't an upcast trait yet. This can probably be fixed once we implement an upcast trait in the generator?

Marking as ready for review since I'm liking the current state of this PR.


RFC references should not list "RFC Publisher" as an author organization

Describe the issue
The addition of the following <author> information to RFC references is incorrect:
<author>
<organization>RFC Publisher</organization>
</author>

See, for example, https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml
Please revert.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

@ronaldtse, @strogonoff  Please treat this as urgent.

Sorry I just noticed this. We will find a way to fix the versions using https://github.com/ietf-tools/github-action-build-relaton-yaml-source .
Ping @andrew2net @strogonoff @stefanomunarini

Version pinning solution is ready in https://github.com/ietf-ribose/relaton-data-rfcs, preparing a PR now.

@ronaldtse Correction, this is not applicable to the problem of pinning. Pinning by minor version ensures no change in schema occurs (between patch versions), but it makes no guarantees about unchanging data. With current architecture I don’t see what to do except wait for Andrew to roll back this change. @stefanomunarini any ideas?

This was introduced yesterday: ietf-tools/relaton-data-rfcs@ed4f2a3
I assume that pinning the Relaton gem version in GHAs can avoid issues like this. So, it might be better to prioritize that work too.

@kesara  Sadly, pinning won’t help. Pinning would ensure we don’t inadvertently move from 1.13.x to 1.14.x, but this change—since it’s not a change in the schema, but a change in data—happened between the patch versions of 1.13.x.
To avoid these changes we’d have to not just pin but also have a lockfile to ensure a fully fixed dependency tree of the tools for generating bibdata, with no changes between GHA runs.

IMHO if the gem is going to introduce a new set of data, it should be a minor version update, not a patch.
Pinning to a minor version only going to work if the Relaton gem release strategy is going not going to change any schema & introduce or remove data with patch releases.

To avoid these changes we’d have to not just pin but also have a lockfile to ensure a fully fixed dependency tree of the tools for generating bibdata, with no changes between GHA runs.

You are suggesting that we lock the version to an exact release right?
Isn't this going to add more overhead in maintenance?
But to fix this urgent issue, I'm happy to go ahead with that.

Sorry for getting back late, this issue has been fixed around 10 days ago.

@ronaldtse My spot check shows that it is fixed. Thanks!

Thank you @ajeanmahoney !

It looks like this issue has reappeared.  While trying to publish last week, I noticed that "RFC Publisher" is now listed as an author for RFCs.  For example, see
https://www.rfc-editor.org/v3test/rfc9333.html#section-12.1
https://www.rfc-editor.org/v3test/rfc9333.xml
It seems that the http://bib.ietf.org/ files contain the "RFC Publisher" data.  Examples:
https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml
https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml
https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9020.xml


Load testing

Created a Docker file inside the testing directory that contains binary so that we tm-load-test
run command  tm-load-test -c 1 -T 10 -r 1000 -s 250 \   --broadcast-tx-method async \   --endpoints ws://tm-endpoint1.somewhere.com:26657/websocket,ws://tm-endpoint2.somewhere.com:26657/websocket

Seems like this has been in draft state for quite some time now, so I'll close this for now. Please feel free to reopen if you'd like to update and mark it as ready for review!


Failure to run installation script on MacOS

Component
Foundryup
Have you ensured that all of these are up to date?

[ ] Foundry
[X] Foundryup

What version of Foundry are you on?
NA
What command(s) is the bug in?
foundryup
Operating System
macOS (amd)
Describe the bug
When attempting to install locally on MacOS Monterey, using foundryup (after having run curl -L https://foundry.paradigm.xyz | bash) I get the error:
tar: Error opening archive: Unrecognized archive format

Seperately, I also get a somewhat similar error in a Ubuntu CI environment when running foundryup:
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

Unsure what the cause is, thanks for the help!

Also getting this error on Linux (Ubuntu 20.04 via WSL Win10)

Some artifacts are missing because Windows currently runs out of memory building the release which fails the entire release workflow. I'm investigating

Installing on Manjaro and getting this issue as well.

This should be fixed now. The Windows release has been disabled to allow the other releases to build correctly, and the latest nightly release has builds for both MacOS and Linux.

Awesome, works for me for both MacOS and Ubuntu. Thanks for fixing quickly!


CMake should fail if bad DEFAULT value specified

If a bad DEFAULT value is specified, CMake should fail with a helpful error message.  It should ensure that a valid value is given for the platform being compiled for as well (e.g. it should fail if rapl is specified when running in Windows or on an Apple system).  Currently it just doesn't produce the energymon-default and energymon-default-static targets.  Running make then fails because it can't link against energymon-default:

Scanning dependencies of target energymon
[  3%] Building C object CMakeFiles/energymon.dir/src/app/energymon.c.o
Linking C executable bin/energymon
/usr/bin/ld: cannot find -lenergymon-default
collect2: error: ld returned 1 exit status
CMakeFiles/energymon.dir/build.make:85: recipe for target 'bin/energymon' failed
make[2]: *** [bin/energymon] Error 1
CMakeFiles/Makefile2:60: recipe for target 'CMakeFiles/energymon.dir/all' failed
make[1]: *** [CMakeFiles/energymon.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2

My problem might be related to this issue so I'll post it here. When I ran CMake with the ENERGYMON_BUILD_DEFAULT set to rapl and ENERGYMON_BUILD_LIB set to NONE, the compiled library only compiles the energymon-default. But, this is a problem as for some reason the default energymon-default does not work and always gives 0 on every read. Then, I recompiled energymon with ENERGYMON_BUILD_LIB set to rapl. This time, I modified the line in my program to use energymon_get_rapl instead of energymon_get_default which works perfectly.

Hi @jonathan-alvaro - I'm not able to reproduce your problem.  If I configure cmake with cmake .. -DENERGYMON_BUILD_DEFAULT=rapl -DENERGYMON_BUILD_LIB=NONE it correctly builds the rapl implementation as the energymon-default library and I am able to read, e.g., using the energymon-info utility.
Everything you described sounds like correct behavior except that you were getting 0 values on read.  If you're writing your own code that links against energymon-default, you will have to rebuild it if you're using static libraries (which is CMake's default, as opposed to using shared object libraries).  So if you statically linked against a dummy default implementation previously but didn't recompile, you would continue to get 0 values since it's still using the dummy implementation.  For debug purposes, you can use the energymon.fsource function pointer to get the human-readable description of the library you're linked against and print out the string.

To clarify, the 0 values on read happens only with code that I wrote on my own. The readings from energymon-info works just fine. The weird thing is that the same program that I run worked on another system that runs on ubuntu 18.04. But, when I moved to another system with Ubuntu 14.04, it suddenly gives out 0 reads.

Ubuntu 14.04 is old enough that it may not include (or load) the intel_rapl kernel module by default, which energmyon-rapl requires.  Please verify that 1) the intel_rapl kernel module is loaded (lsmod | grep intel_rapl), and 2) that there are actually files at /sys/class/powercap/ (e.g., ls /sys/class/powercap/intel-rapl\:0/).

I do have the intel_rapl module loaded to the kernel
Yes, there are files within the powercap intel-rapl folders.

Thanks for the update.  That is strange behavior that I cannot explain.  The API design is to return 0 on read error and set errno, so in your code, if you ever a get a 0 return value from fread, you should check if errno is set and respond appropriately (e.g., by logging the error).  (You should also check that finit is returning successfully first.)  Hopefully that will give us some idea of what's going on.  It's still possible that errno won't be set, e.g., if the energy_uj file is actually returning a 0 value.  Since I cannot reproduce this issue, you may just need to run it through gdb (or other debugger) yourself.
If you do see a problem with the library, can I request that you please open a new issue? I'm going to (finally) fix this original issue in CMakeLists.txt.

@jonathan-alvaro I just wanted to follow up to see if you're still having trouble.  You can definitely open a new issue if there is indeed a problem.  Cheers.


Replace unmaintained actions-rs/* actions in CI workflows

Motivation
Basically all of the actions-rs/* actions are unmaintained. See https://github.com/actions-rs/toolchain/issues/216 for more information. Due to their age they generate several warnings in CI runs, for example in https://github.com/recmo/uint/actions/runs/4754627965:

Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions-rs/toolchain@v1, Swatinem/rust-cache@v1, actions-rs/cargo@v1, actions-rs/clippy-check@v1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Solution
To get rid of some of those warnings the occurrences of actions-rs/toolchain are replaced by dtolnay/rust-toolchain, and the occurrences of actions-rs/cargo are replaced by direct invocations of cargo.

Can you update this branch to current main?

Can you update this branch to current main?

@prestwich Done.

Thank you!


Question about Prompt for stable diffusion to obtain Feature maps

Thanks authors for the nice work. I have some questions about obtain feature map from stable diffusion model. According to your code, if I read correctly, you will need a text prompt, e.g., " a photo of cat" to obtain the diffusion feature.
I wonder how authors obtain the text prompts when evaluating on the label progation benchmarks or other benchmarks. Do you need to annonate them in a rough way?

Hi, thanks for your interest in our work!
For DIFT_sd, on homography estimation and label propagation tasks, we use null prompt (empty string). See more implementation details in Appendix A of the paper.

Thanks for the infromation. I will close the issue


Nxppy: Internal Error from BAL Component

Please answer these questions as part of your new issue.
Which version of Python are you using?
Python 2.7.9
Which OS and version are you running?
Raspbian GNU/Linux 8 (jessie)
Is SPI enabled?
Yes
Are you trying to read/write a Mifare Classic card?  (This is currently unsupported)
No
Hello,
I've carefully installed (multiple time) nxppy following the README but for each installation when I call :
nxppy.Mifare()
>>> mifare
nxppy.InitError: Nxppy: Internal Error from BAL Component

and it of course segfault is I call nxppy.select()
I've re-installed the whole thing multiple time and I'm running out of idea. I would gladly get some help on it.

After a day of struggling I solve my own problem, my SPI was simply not properly enabled.
nxppy work perfectly,
Great work.


Make switcher off by default or in life statement

Thank you for your library. I just wanna know how to set the switch to off when the view appears ?
can I write an if statement like :
if name.text == "hello" {
pwSwitch.off
}

Just call setOn(on: Bool, animated :Bool) to set it to On or Off state manually when needed.

I tried PWSwitch.setOn(on: false, animated :true) but when I run the app the switch is in ON state


[FEATURE]: Add an SQLite implementation of the Local Secrets Manager

Contact Details [Optional]
<EMAIL_ADDRESS>Describe the feature you'd like
ZenML currently offers a file-based local secrets manager (found at zenml/src/zenml/secrets_managers/local/local_secrets_manager.py).
It would be good to have an SQLite implementation of the same behaviours, where secrets were stored locally inside a database.
Generally ZenML likes to use SQLModel for its use of SQL databases and the dependency is already available.
Is your feature request related to a problem?
No response
How do you solve your current problem with the current status-quo of ZenML?
The current local secrets manager is implemented as a local file-based store.
Any other comments?
This relates to #ENG-716 (Jira).

As we will deprecate secrets managers in favor of the centralized zenml secrets store, this is outdated. As of 0.34.0, we already support a SQL back-end for the secrets store.


Azure storage: support user delegation SAS

User delegation SAS are the form that SAS take when Azure AD is used. Once #1346 is implemented we can extend the SDK to additionally allow users to generate user delegation SAS.
The implementation should allow callers to configure each of the optional fields in the user delegation SAS, e.g. rscd to set the content-disposition header.
https://learn.microsoft.com/en-us/rest/api/storageservices/create-user-delegation-sas
CC @mario-guerra

Looks good, thank you!


LineChart hide Axis

Hi, I would like to know if it is currently possible to hide the x/y axis of the chart. I am using a timestamp format with milliseconds and this takes up a lot of tile space and cannot seem to find a method to hide it. I know the standard line chart uses the following:
xAxis.setTickLabelsVisible(false);
yAxis.setTickLabelsVisible(false);

Hi there, it would be good if you could provide a bit more information. What chart/skin are you talking about? The best would be to provide a short code snippet that shows the problem so that I can reproduce it on my machine. Thank's, Gerrit

Hi, its the smoothed line chart

In terms of code:
    private ScheduledExecutorService scheduledExecutorService;
    private int timeI = 1;
    XYChart.Series<String,Number> series1= new XYChart.Series<>();

       scheduledExecutorService = Executors.newSingleThreadScheduledExecutor();
        ArrayList<String[]> dataArrayList = new ArrayList<>();
        // put dummy data onto graph per second
        scheduledExecutorService.scheduleAtFixedRate(() -> {

            // get a random integer between 0-10
            Integer random = ThreadLocalRandom.current().nextInt(10);
            // Update the chart
            Platform.runLater(() -> {

                // get current time
                Date now = new Date();
                // put random number with current time
                XYChart.Data datas1 = new XYChart.Data<>(simpleDateFormat.format(now), random);

                String[] dataArray = {(String) datas1.getXValue(), String.valueOf(datas1.getYValue())};
                dataArrayList.add(dataArray);

                series1.getData().add(datas1);
                if (series1.getData().size() > WINDOW_SIZE){
                    series1.getData().remove(0); }
                if (series2.getData().size() > WINDOW_SIZE)
                    series2.getData().remove(0);
            });
        }, 0, 10, TimeUnit.MILLISECONDS);

Ah, ok will take a look at it, thx 👍🏻

I took a look at it and indeed there was no easy way to hide them. So I've added methods to show/hide the ticklabels for x and y. In the latest commit (b3da3e3c36c803fde71459d57ffb4266ee922110) you can either call the setter like
tile.setTickLabelsXVisible(false);

or use it in the TileBuilder as follows:
...
.tickLabelsXVisible(false)

That is much appreciated. Thank you!

Just let me know if you stumble upon other things that are missing...


create a page to create and update a specific voucher for users coming from mobile

th voucher_id is "voucher_mobile"

We dont need a QR code and a link for that special voucher as the users come from the mobile directly

for this voucher the affiliate commission is 0%, affiliate email is<EMAIL_ADDRESS>name is Altme, affiliate blockchain is Tezos, affiliate account is Null
the only fields of the form are : voucher duration, gamer reward
teh voucher_id = voucher_mobile.

the access to this voucher is probably in the first screen with radio button for voucher and membership card "voucher for mobile"

okay


Adding Animations to the home page using framer motion

What feature?
I can add animations to the website using framer motion. Please assign me
Add screenshots
Add screenshots
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Go ahead and add it @rohan9024

Are you working under Gssoc23 @rohan9024

Are you working under Gssoc23 @rohan9024

Yess


Can not enable live chat in course settings

Describe the bug
In the course settings, I can set the tickbox for “enable live chat”, but when I save, it's value actually remains unchanged after a reload.
The describes the error: Uncaught TypeError: admin.LectureList.hasIndividualChatEnabledSettings is not a function
To Reproduce
Steps to reproduce the behavior:

Be an admin
Go to course admin site (with chat disabled in my case, cannot test the other case for obvious reasons)
Click on “Enable Live Chat ” to enable
Click on “Save Settings“
Reload webpage
See that the textbox is unchecked again.
Also note: Chat is not enabled in scheduled stream.

Expected behavior
Chat should be enabled.
Screenshot of relevant console log
This is the error log produced when hitting „Save Settings“:

Desktop:

OS: Windows 10 😞
Browser: Firefox 118.0.1

Oh, this is a duplicate of #1178. Sorry.


Limit type argument inference from binding patterns

Second attempt of #45719 (and #46009)
Fixes #43605
Fixes #45074
Fixes #45663
In the past, when we made inferences to type arguments in return types, we did two things with those inferences: (1) put them in the primary inference context with a low priority, and (2) put them in a secondary inference context that gets used solely for instantiating contextual types of arguments in the same call expression. The consequence of (1) is easily observable when no other inference sources are present to overwrite the low-priority return type inference made from a binding pattern:
declare function f<T>(): T;
const { foo } = f(); // T: { foo: any }

#45719 fixed this by preventing return type inferences from binding patterns altogether, i.e., it stopped both (1) and (2) above. This turned out to be a problem, because (2) produces very desirable behavior with array binding patterns:
declare function f<T>(cb: () => T): T;
const [e1, e2, e3] = f(() => [1, "hi", true]); T: [number, string, boolean]

The binding pattern provides a tuple contextual type for the array literal in the return expression, allowing e1, e2, and e3 to have separate types rather than all having string | number | boolean. To preserve this desirable behavior, I tried #46009 which only prevented inferences from object binding patterns. However, it was later discovered that this still wasn’t a complete fix, because it still allowed:
declare function f<T>(): T;
const [e1, e2, e3] = f(); // T: [any, any, any]

I ended up reverting all these attempts to reevaluate, with the conclusion

While it may be true that object binding patterns never contribute anything useful to type argument inference, it is not true that array binding patterns always contribute usefully to type argument inference. What we really want is for binding patterns to contribute contextual typing information to other inference sources, while never being allowed to stand on their own as inference sources.

So that’s what this PR does. Rather than make any distinctions between object and array binding patterns, I make a distinction between inference passes into separate contexts (1) and (2) above. If a contextual type for the return type came from a binding pattern, we make no inferences into (1), but we always make inferences into (2) so that other arguments can benefit from that contextual type (primarily for the array → tuple case—it does happen in other cases but I haven’t found any that are useful).

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt

@typescript-bot perf test this

@typescript-bot pack this

An example mentioned in the design meeting is broken by this:
declare function id<T>(x: T): T;
const { f = (x: string) => x.length } = id({ f: x => x.charAt });

When getting the type of the function expression inside the call to draw inferences from, we have the contextual type from the binding pattern available, but we don’t use it because we’re skipping context-sensitive functions and return anyFunctionType from checkFunctionExpressionOrObjectLiteralMethod 😕. Any advice there?

Usually that just means we'll pick up the better type in the next inference pass - the SkipContextSensitive pas implies there'll be a context-sensitive second pass that picks up the context-sensitive type.

Doh, of course. That was a red herring. Still debugging.

Ah, I see what the problem is. I mistook how the combineTypeMappers I added in instantiateContextualType would handle the first mapper having no inference candidates—I intended it to delegate to the second, but instead the first mapper produces the constraint/default/unknown and we just go with that. I think adding a cloneInferredPartOfContext would fix this, but I can probably accomplish the same with less object cloning.

Hm, ok. I’m actually still having trouble combining these type mappers in a way that works for every case, and I’m not sure if it’s possible.
The issue is that for instantiating contextual signatures, we actually do use those low-priority return type inferences as well as other inferences made so far. So when I completely separated those inferences, I attempted recombine them from the two contexts, but I don’t think that’s going to work.
An earlier iteration of this PR, rather than removing binding pattern return type inferences from the primary context, flagged them with another priority flag and then avoided returning  those from getInferredType. Maybe I need to go back to something like that 😕

@ahejlsberg do you want to take a look at what I have so far before I go down a rabbit hole trying to solve ☝? Maybe you’ll have an idea for that.

@ahejlsberg the changes we discussed yesterday are up. That approach actually fixed this test case:
declare function id<T>(x: T): T;
const { f = (x: string) => x.length } = id({ f: x => x.charAt });

Seems like the best outcome we could have hoped for!

Is this still waiting on a review or is it ready to merge?

I think @ahejlsberg may have wanted a final look at it.


Fixed incompatibility between Sphinx and docutils on py27

No review needed

Coverage remained the same at 35.309% when pulling 0646ab6fbc992df2383a9a129cefac17328c3b3e on andy/fix-docutils into 9cb627406c38cf32b0a07cea6d50ac6b6a505802 on master.


AD/LDS trigger reports "no matching run profile could be found"

The following error message may appear in the AutoSync logs and the triggered event does not fire
Dropping DeltaImport request from 'AD/LDS change detection (DC=domain,DC=com)' as no matching run profile could be found in the management agent partition DC=domain,DC=com

Instrumented build
autosync.zip

This is caused by a run profile resolution bug where the profile resolution method returns the scheduled import run profile instead of the delta import run profile.

Updated build with a fix for this issue
autosync.zip

Fixed in https://github.com/lithnet/miis-autosync/releases/tag/v1.2.6692


fix: add support for nestjs 9

Updated nest packages to support nestjs version 9.
I published a npm repo that anyone can use until this is merged<EMAIL_ADDRESS>

When will this be getting merged?

@mxarc Please merge the PR! Waiting for this release

@mxarc Could we get this merged please?

can we please merge this?

What is the delay on getting this merged?

merge pls!

Hi @mxarc can we merge this please?

@tay-yijun I ended up creating a new repo for NestJs 9> as this was not being maintained, if it helps, feel free to use it: https://github.com/juicyllama-community/nestjs-redoc


Changed delete span to button, same for reject

Coverage increased (+0.0009%) to 13.733% when pulling 91104299fb7c848dc519dd954c64f230b5bf12fb on b03513-tab-to-delete into d4fe818131f597fcf9a2df12bcb7aa4f777aa2b4 on master.


Re-work Pex documentation.

This change moves Pex off RTD and on to GitHub Pages. Instead of
versioned docs out on RTD, only the latest docs will be available via
https://docs.pex-tool.org and versioned docs will be available via
GitHub Releases (for the PDF) and inside the Pex wheel and Pex PEX
themselves via the new pex3 docs command that serves the appropriate
docs locally, offline, with full functionality.
With this switch, docs are also now built and link-checked in CI. There
should be no more RTD style misconfiguration production outages.

Obviously there is alot going on here in 1 big commit. Not very reviewable!
I'm going to charge forward on green CI and get out a release though to make sure all the bits work / so I can flip some DNS switches, etc. If any of you do end up providing feedback, I'll follow up.
As far as the new doc embedding goes, here is the penalty:
# Before
$ tox -epackage -- --additional-format sdist --additional-format wheel
$ du -sh dist/pex*
3.6M    dist/pex
2.8M    dist/pex-2.1.164-py2.py3-none-any.whl
4.0M    dist/pex-2.1.164.tar.gz

# After
$ tox -epackage -- --additional-format sdist --additional-format wheel --embed-docs
$ du -sh dist/pex*
4.0M    dist/pex
3.3M    dist/pex-2.1.164-py2.py3-none-any.whl
4.0M    dist/pex-2.1.164.tar.gz

So just under 500KB bigger wheel and Pex PEX.

Alright, with that landed on main and my fork rebased I was able to run a test-deploy as described in the CONTRIBUTORS.md edit: https://jsirois.github.io/pex/

The URIs should ~work. Still sorting through a few things on the RTD side for pex.readthedocs.io/ and pex.readthedocs.io/en/latest/ which do re-direct to the new stuff (the old explicit version links still go to RTD).

Ok, the URL redirect stuff is all working now.

Thanks for taking a look Huon. This looks like its all wrapped up now and working smoothly after a bit of fumbling with the RTD redirect rules.

"Cool URIs don't change"/redirects: doing large-scale website switches risks breaking old links, I imagine you may've thought of how to handle this, but I don't see it explicitly discussed?

This made me chuckle. I think you know my hard line policy on never breaking users! So no discussion needed. A discussion would have been needed for the opposite perhaps! The lack of need for notes, etc was doubly so since I did not change any site structure in the PR (there was just a single .rst -> .md for api/vars enabled by / as a test of the MyST integration, but the generated page is still api/vars.html so linking structure is unchanged). The only thing that changed from a content point of view was the new Sphinx theme (fonts / colors / positioning) and a new root URL.

t looks like a fair chunk (174K) of the 500K increase might be the image assets. If one is looking for optimisations, they might be something that could be reduced?
$ wc -c assets/* | sort -n
613 assets/download.svg
884 assets/pdf.svg
946 assets/python.svg
1486 assets/github.svg
2719 assets/pex-full.svg
25312 assets/pex-icon-512x512.png
25424 assets/pex-icon-512.png
34315 assets/pex-full-dark.png
35372 assets/pex-full-light.png
47040 assets/pex.ico
174111 total

This wasn't as big a problem as it looked since only 4 of those files were linked into docs/_static, which is all that is included in the generated docs / PDF. I researched .png support for favicon though and it looks like it was supported by all major modern (last 10 years) browsers both desktop and mobile. So I just killed the .ico file and shared the 512x512 logo .png for the PDF cover page and the favicon. That could be micro-optimized further, but seemed a fine compromise that seems to work well and nets a small 20KB win in binary size for the Pex PEX and the Pex .whl.
Addressed in #2368.


Android: The SDK Build Tools revision (23.0.1) is too low for project ':react-native-social-share'. Minimum required is 25.0.0

I am getting this error because of buildToolsVersion in this line:
https://github.com/doefler/react-native-social-share/blob/master/android/build.gradle#L5
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugApk'.
   > A problem occurred configuring project ':react-native-social-share'.
      > The SDK Build Tools revision (23.0.1) is too low for project ':react-native-social-share'. Minimum required is 25.0.0

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 2.566 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

Versions:
"react": "16.0.0-alpha.6",
"react-native": "0.44.0",
"react-native-social-share": "^1.0.0",

after upgrading buildToolsVersion to:
buildToolsVersion '25.0.0'

The error was fixed.
Should you guys update this in your repo?
This file is in node_modules, and everyone who npm install will get this error.

Hey @fackius
Thank you so much for this.
To be sure do you mean that you want me to change:

apply plugin: 'com.android.library'

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.1"
...

into

apply plugin: 'com.android.library'

android {
    compileSdkVersion 23
    buildToolsVersion "25.0.0"
...

In this file
https://github.com/doefler/react-native-social-share/blob/master/android/build.gradle#L5
And that will fix the problem?
@buskerone @minhtule @Tigrakto @angusmccloud @eggybot have you experienced this error?

@doefler
thanks for the quick response!
yes, you are correct.
I've fixed this error updating that line buildToolsVersion '25.0.0'  in react-native-social-share/android/build.gradle.
This is how my file looks now:
apply plugin: 'com.android.library'

android {
    compileSdkVersion 23
    buildToolsVersion '25.0.0'

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 22
        versionCode 2
        versionName "1.1"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    lintOptions {
      warning 'InvalidPackage'
    }
}

dependencies {
    compile 'com.facebook.react:react-native:+'
}

@fackius You are welcome.
Do you think changing this could cause problems for other people, who uses a different version of the frameworks etc.?

@doefler
I think I couldn't answer that.
I am using react-native-social-share in a new project, with latest version of react/react-native packages, sdk, etc.
So I think sooner or later you'll have to upgrade your settings to keep your library up to date.
If the developers who use this library has problem with latest settings and versions, then they will need to upgrade their projects :)
Hope that answer your question!

@fackius
That makes perfect sense.

@doefler
let me know any update!
I referenced this issue in react-native-vector-icons because I've found the same issue there:
https://github.com/oblador/react-native-vector-icons/issues/484

Hi @doefler
seems that this version issues were caused because something Android Studio did the first time I tried to build Android app.
I re builded the project from scratch in a different branch, without using Android Studio, and the build was successful.
If someone has the same problem, that's answer ^
I think this issue can be closed.
Thanks for your time!
Cheers!

@fackius
Thank you for the update 👍
So I don't change the file and leave things as is, for now?

@fackius btw if you want feel free to connect on Linkedin

In my case, i did not experience any issues with the build tool version yet.
I'll let you guys know if anything happen.

@Tigrakto thanks for trying and getting back to us 👍
Have a nice weekend

Hey guys, I'm facing this error.
* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugApk'.
   > A problem occurred configuring project ':react-native-social-share'.
      > The SDK Build Tools revision (23.0.1) is too low for project ':react-native-social-share'. Minimum required is 25.0.0

React Native: 0.51.0
React Native Social Share: ^1.3.0
Had to update my buildToolsVersion to 25.0.0 and this is the only error I'm getting now.

Hi @Jpadilla1
I am not sure what could be causing this.
Maybe one of the Android experts here can help you out.
CC @facuescobar
P.S.
Try updating React Native Social Share to 1.4.0

No need to change in node-module
Just put these lines into project build.gradle make sure its not app build.gradle
subprojects {
afterEvaluate {project ->
if (project.hasProperty("android")) {
android {
compileSdkVersion 25
buildToolsVersion '25.0.0'
}
}
}
}


Update Jobs

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


bitsearch.to provider

please add this site https://bitsearch.to/

@ibrahim8383 hi. you can try to add it by yourself by following guide here https://github.com/elgatito/script.elementum.burst/blob/master/README.md#adding--editing-providers
and by reading examples here https://github.com/elgatito/script.elementum.burst/blob/master/burst/providers/providers.json
and then you can send a PR via github UI.
this probably would be the fastest way to get it done :-)

@antonsoroko here is the provider i add but i get no links were found from elementum what is wrong?
{
"bitsearch": {
"anime_extra": "",
"anime_keywords": "{title} {episode}",
"anime_query": "EXTRA",
"base_url": "https://bitsearch.to/search?q=QUERY",
"color": "FFF14E13",
"general_extra": "",
"general_keywords": "{title}",
"general_query": "EXTRA",
"language": null,
"login_failed": "",
"login_object": "",
"login_path": null,
"movie_extra": "",
"movie_keywords": "{title} {year}",
"movie_query": "EXTRA",
"name": "bitsearch",
"parser": {
"infohash": "",
"name": "item('a', order=2)",
"peers": "item(tag='td', order=3)",
"row": "find_once(tag='body').find_all('tr')",
"seeds": "item(tag='td', order=2)",
"size": "item(tag='td', order=5)",
"torrent": "item(tag='a', attribute='href', order=2)"
},
"private": false,
"season_extra": "",
"season_extra2": "",
"season_keywords": "{title} Season {season:2}",
"season_keywords2": "{title} Season{season}",
"season_query": "EXTRA",
"separator": "+",
"show_query": "",
"subpage": true,
"tv_extra": "",
"tv_extra2": "",
"tv_keywords": "{title} s{season:2}e{episode:2}",
"tv_keywords2": "",
"tv_keywords3": "",
"tv_keywords_fallback": "",
"tv_keywords_fallback2": ""
}
}

@ibrahim8383

enable debug logging in elementum to see what it sends to burst (how query/URL looks like in the end) - see guide here http://elementum.surge.sh/contribute/log/
also enable debug logging in burst settings to see how burst parses HTML pages based on your parsing rules. see https://github.com/elgatito/script.elementum.burst/blob/e70aa218be55241462e8574c43e0f40740e1f764/resources/language/messages.pot#L163
you need to write correct "parser": { rules to get "row" (each line with torrents), "name", torrent file link and etc. as i can see they do not use tables (tr/td html tags) but uses a lot of div tags, so i guess your code is a copy-paste from other provider. I am not a HTML expert, but i can suggest you to use "dev panel" in browser, then highlight target item and then use "copy"->"copy as selector" to see "path" to item. then convert this path to internal "selection" language. there is not much documentation about this language, i found only https://quasar-burst.readthedocs.io/en/latest/adding_providers.html#parser and comments in code, like https://github.com/elgatito/script.elementum.burst/blob/master/burst/parser/ehp.py#L108
I guess you need to look at different examples (parsing of div based pages), like https://github.com/elgatito/script.elementum.burst/blob/e70aa218be55241462e8574c43e0f40740e1f764/burst/providers/providers.json#L2426-L2432

@ibrahim8383 any success on this??
I also tried for this. But not working..

@ibrahim8383 @naveen1hot
I had to be quite creative with parsing, but I was able to make it work. You can try to make changes locally and test how it works for you (so you can provide some feedback earlier) or wait for new release of burst.

Kudos!!!! Great thanks for your response and help @antonsoroko...

Hello @antonsoroko i am getting the results but failed at resolving links(not playing). sorry to trouble you. just i want to share the status of your commit. thanks..

@naveen1hot strange, it works for me.

I would need a full log file with debug enabled in elementum and kodi from yuo.
See http://elementum.surge.sh/contribute/log/ for a guide.

On a side note, for torrent files bitsearch uses iTorrents.org is a free service for caching torrent files online. and as I can see that sometimes it give us timeout when we try to download torrent file, so you need to try again.
Does this issue happen all the time for you? If only sometimes - this is not a burst issue.

@antonsoroko Itorrents.org is behind Cloudflare defence, so it can work in one case, and not the other.

I just tried to use magnets instead of files, but it does not work for me, never resolve. So I guess we will stick with files and users have click twice if needed.

Thanks @antonsoroko.. seems bitsearch no longer need for now. As we have torrentz..


⚠ Bofrost.at has degraded performance

In 483d467, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 833 ms

Resolved: Bofrost.at performance has improved in 102dab1 after 6 minutes.


The use of the likes of UINT32_MAX requires internal/numbers.h

Merged.
546ca2f4f5f7e26f7352116754e77f63804b78a6 The use of the likes of UINT32_MAX requires internal/numbers.h


Distribute bash completion script

I've combined this into https://github.com/ocaml-dune/binary-distribution/pull/68


[Docs]: Documentation link from PyPi is broken

Page
https://pypi.org/project/interactions.py/
Problem description
The "Documentation" link on PyPi leads to https://naff-docs.readthedocs.io/en/latest/, which itself just has a broken link to a "naff" domain that is parked.
Suggested changes
PyPi should link directly to the current documentation at https://interactions-py.github.io/interactions.py/
Additional context
No response

This will be fixed in the next release. Thank you for reporting this


[OutOfBoundsException]   Could not write to file

i tried you SolderToolbelt, sounds very god and handy, but it throws me an error...

if i create the file before it works:
/home/minecraft/prepare# solder mod pack animania-1.12.2-1.4.3.jar -vvv Archive: animania-1.12.2-1.4.3.zip    deflating: animania-1.12.2-1.4.3.jar
how can i solve this?

Looks like solder-toolbelt can't write to the directory you're in.
What happens if you just try to create a file using something like touch test.zip?

Then everything works...
Btw i startet the command with root


tour: [REPLACE WITH SHORT DESCRIPTION]

Context: https://tour.golang.org/welcome/1
Change the title above to describe your issue and add your feedback here, including code if necessary

bin/
hello                          # command executable
outyet                         # command executable
src/
github.com/golang/example/
.git/                      # Git repository metadata
hello/
hello.go               # command source
outyet/
main.go                # command source
main_test.go           # test source
stringutil/
reverse.go             # package source
reverse_test.go        # test source
golang.org/x/image/
.git/                      # Git repository metadata
bmp/
reader.go              # package source
writer.go              # package source
... (many more repositories and packages omitted)

It's not clear what kind of issue you're reporting. Closing here, since I don't see a tour bug, but feel free to open a new one if you want to report something. Please explain clearly what you're doing, and what the issue is.


FocusNode documentation

FocusNode does not make it clear that you shouldn't just create it in a build method each time.

https://github.com/flutter/flutter/pull/10904


Improves accuracy of vector numerical examples

Vector division
Improves accuracy of vector division approximation example.
The previous implementation was unnecessarily inaccurate:
  Measured max error of 2.465257280 ulp @ (1.2449559e-01, 5.2960633e+36)
        func (0x1.fdef16p-4, 0x1.fdfe0ap+121) = 0x1.fff0f8p-126
    func_ref (0x1.fdef16p-4, 0x1.fdfe0ap+121) = 0x1.fff0fcee3633cp-126
  4'550'824'890 tested in [0 ; inf] x [0x1.000008p-128 ; 0x1p126]
   68.8976110218998059% correctly rounded  (<PHONE_NUMBER>)
   92.7973265084255985% faithfully rounded (+<PHONE_NUMBER>)
    7.2026734915744033% >= 1.0 ulp         (+  327781058)

Which is 21.7 bits of precision rather than the claimed 23.
The new implementation has lower maximum error and higher correctly-
and faithfully-rounded rates:
  Measured max error of 1.493816005 ulp @ (5.0745111e+02, 4.9807361e-01)
        func (0x1.fb737cp+8, 0x1.fe0702p-2) = 0x1.fd69eap+9
    func_ref (0x1.fb737cp+8, 0x1.fe0702p-2) = 0x1.fd69ecfcd5739p+9
  4'550'824'890 tested in [0 ; inf] x [0x1.000008p-128 ; 0x1p126]
   79.6106155822664476% correctly rounded  (<PHONE_NUMBER>)
   99.0013070355691127% faithfully rounded (+  882436413)
    0.9986929644308947% >= 1.0 ulp         (+   45448768)

Which is 22.4 bits of precision.
Max error is greater when the denominator's reciprocal underflows:
previously about 5.26 ulp and now about 4.45 ulp.
The algorithm does not handle infinite or zero denominators (returns
NaN) or subnormal denominators whose reciprocal overflows (returns
±∞).  This commit does not document or change this behavior.

src/vector-examples.adoc (Division approximation example): Use
r + r (1 - y r) formulation for 1/y estimate refinement.

Vector square root
Improves accuracy of vector square root approximation example.
The previous implementation was unnecessarily inaccurate:
  Measured max error of 2.647303869947791 ulp @ 2.0831878e-19
        func (0x1.ebe0fap-63) = 0x1.f5d6b2p-32
    func_ref (0x1.ebe0fap-63) = 0x1.f5d6acb494965p-32
  2'139'095'041 tested in [0 , inf]
   57.2114955877736548% correctly rounded  (<PHONE_NUMBER>)
   88.4557938629712339% faithfully rounded (+  668345235)
   11.5442061370287661% >= 1.0 ulp         (+  246941541)

Which is 21.6 bits of precision rater than the claimed 23.
The new implementation has lower maximum error and higher correctly-
and faithfully-rounded rates:
  Measured max error of 0.800413005053997 ulp @ 3.0387554e-29
        func (0x1.342a9ap-95) = 0x1.8d378p-48
    func_ref (0x1.342a9ap-95) = 0x1.8d378199cfbbcp-48
  2'139'095'041 tested in [0 , inf]
   87.4400844352198163% correctly rounded  (<PHONE_NUMBER>)
<PHONE_NUMBER>000000000% faithfully rounded (+  268668531)

With is 23.3 bits of precision.

src/vector-examples.adoc (Square root approximation example): Use
r - (0.5 r) ((x r) r - 1) formulation for 1/sqrt(x) estimate
refinement.

See what happens when you have someone versed in this field write the code, rather than me? :-)


Seperate tokens for list/edit

The way this module is written I have to create one token that covers list and edit for all zones
go-acme lets me create a list for all zones and an edit just for the zone I'm interested in, this is a somewhat more secure method.

Can you just create a cloudflare.Provider using one key for one zone, and another one for another zone?


New OAS handler fails generating schema w/ TypeError: Cannot read properties of undefined (reading 'getTypeName')

Issue workflow progress

Progress of the issue based on the Contributor Workflow

[x] 1. The issue provides a reproduction available on Github, Stackblitz or CodeSandbox

Make sure to fork this template and run yarn generate in the terminal.
Please make sure Mesh package versions under package.json matches yours.

[ ] 2. A failing test has been provided
[ ] 3. A local solution has been provided
[ ] 4. A pull request is pending review

Describe the bug
When starting 👇 .meshrc, the following error occurs:
...
🐛 🕸  Mesh - Jira Processing /properties/mutationInput/properties/MigrationResource_workflowRuleSearch_post/properties/ruleIds for GraphQL Schema
🐛 🕸  Mesh - Jira Processing /properties/mutationInput/properties/MigrationResource_workflowRuleSearch_post/properties/expand for GraphQL Schema
🐛 🕸  Mesh - Jira Processing /properties/mutationInput/properties/MigrationResource_workflowRuleSearch_post for GraphQL Schema
🐛 🕸  Mesh - Jira Processing /properties/mutationInput for GraphQL Schema
🐛 🕸  Mesh - Jira Processing  for GraphQL Schema
🐛 🕸  Mesh - Jira Attaching execution logic to the schema
💥 🕸  Mesh - Jira Failed to generate the schema TypeError: Cannot read properties of undefined (reading 'getTypeName')
    at addExecutionLogicToComposer (/Users/wwe/x/node_modules/@omnigraph/json-schema/index.js:624:74)
    at getGraphQLSchemaFromDereferencedJSONSchema (/Users/wwe/x/node_modules/@omnigraph/json-schema/index.js:1776:52)
    at async OpenAPIHandler.getMeshSource (/Users/wwe/x/node_modules/@graphql-mesh/new-openapi/index.js:39:24)
    at async /Users/wwe/x/node_modules/@graphql-mesh/runtime/index.js:281:28
💥 🕸  Mesh An error occured while writing the schema file: Error: Schemas couldn't be generated successfully. Check for the logs by running Mesh with DEBUG=1 environmental variable to get more verbose output.
    at Object.getMesh (/Users/wwe/x/node_modules/@graphql-mesh/runtime/index.js:311:15)
💥 🕸  Mesh An error occurred while building the artifacts: Error: Schemas couldn't be generated successfully. Check for the logs by running Mesh with DEBUG=1 environmental variable to get more verbose output.
    at Object.getMesh (/Users/wwe/x/node_modules/@graphql-mesh/runtime/index.js:311:15)
💥 🕸  Mesh - Server Error: Schemas couldn't be generated successfully. Check for the logs by running Mesh with DEBUG=1 environmental variable to get more verbose output.
    at Object.getMesh (/Users/wwe/x/node_modules/@graphql-mesh/runtime/index.js:311:15)
error Command failed with exit code 1.

To Reproduce
Steps to reproduce the behavior:
Use the .meshrc below and run yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>graphql && DEBUG=1 yarn mesh dev.
It seems to be a regression between 0.5.0 and 0.5.1. The command above runs w/<EMAIL_ADDRESS>and fails from v0.5.1 onward.
.meshrc
sources:
  - name: Jira
    handler:
      newOpenapi:
        oasFilePath: https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json

Here's a codesandbox: https://codesandbox.io/s/gql-mesh-issue-4150-qix9q0
Expected behavior
Mesh starts correctly.
Environment:

OS: MacOS 12.4
<EMAIL_ADDRESS><EMAIL_ADDRESS>NodeJS: v16.15.0

Additional context
The offending piece of code is this: const typeTCThunked = types[statusCodeOneOfIndexMap[statusCode] || 0]; (from here)
Before this is called type composers are mapped by response status code. This mapping seems inconsistent.
Example:
types contains two composers, statusCodeOneOfIndexMap three status codes. When trying to get the typeTC in 👆 call, status 403 returns index 2 which is not defined in types.

Covered by https://github.com/Urigo/graphql-mesh/pull/4180
You can test it with canary versions of that PR :)
Thanks for opening the issue

Great, thanks for addressing.
I can confirm it works with the canaries using yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>graphql && DEBUG=1 yarn mesh


Attribute Error Voice API

First time using python and vonage.
I copy pasted the code for making a call from https://github.com/Vonage/vonage-python-sdk#voice-api. But getting the following error.
AttributeError: 'Voice' object has no attribute 'create_all'

Appreciate your contribution!


Provide access to treatEscapes through Prefix

If I understand correctly, currently all compile time string interpolators defined using Contextual do not "treat" escapes. It seems to me like a fairly common use case to want the standard scala string escaping in one's compile time string interpolator.
Perhaps just an additional Boolean parameter to the apply method of the Prefix Object would suffice. Implementation should not be too difficult as the String => String function is exposed here in the std scala library.

I saw this problem, and I think I have a better solution to it... I have a couple more changes to make, but I should be able to release it soon.


(GH-59) Changes for new Debug API

As documented in release notes:
https://code.visualstudio.com/updates/v1_17#_debug-api-updates

Relates to #59


fix(writer): disable ts key in writer

IMPORTANT: Please do not create a PR without creating an issue first!
(Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request).
Summary

Explains the information and/or motivation for making this changes...
Proposed of changes
This PR fixes/implements the following bugs/features:

Bug 1
Bug 2
Feature 1
Feature 2
Breaking changes

How has this been tested?
Proof:

Closing issues
Fixes #
Checklist:

[ ] My code follows the code style of this project.
[ ] My changes successfully ran and pass linters locally (run make lint).
[ ] I have written new tests for my changes.

[ ] My changes successfully ran and pass tests locally.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (c8265b1) 100.00% compared to head (2a7e9da) 100.00%.
Report is 3 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master       #51   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           36        36
=========================================
  Hits            36        36

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


Unable to connect to confluent kafka

I am trying to implement KEDA for Confluent Kafka.  I have tested out different scenarios but the error i get is
2020-10-12T14:39:02.788Z	ERROR	controllers.ScaledObject	Failed to ensure HPA is correctly created for ScaledObject	{"ScaledObject.Namespace": "keda", "ScaledObject.Name": "kafka-scaledobject", "error": "error getting scaler for trigger #0: error creating kafka client: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128
github.com/kedacore/keda/controllers.(*ScaledObjectReconciler).Reconcile
	/workspace/controllers/scaledobject_controller.go:146
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:235
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:209
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:188
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1
	/go/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:155
k8s.io/apimachinery/pkg/util/wait.BackoffUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:156
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:133
k8s.io/apimachinery/pkg/util/wait.Until
	/go/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:90
2020-10-12T14:39:02.796Z	ERROR	controller	Reconciler error	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledObject", "controller": "scaledobject", "name": "kafka-scaledobject", "namespace": "keda", "error": "error getting scaler for trigger #0: error creating kafka client: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:237
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:209
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:188
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1
	/go/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:155
k8s.io/apimachinery/pkg/util/wait.BackoffUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:156
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:133
k8s.io/apimachinery/pkg/util/wait.Until
	/go/pkg/mod/k8s.io/apimachinery@v0.18.8/pkg/util/wait/wait.go:90

I deployed a scaled object as follows.
Scenario 1 without TriggerAuthentication
triggers:
- type: kafka
  metadata:
    bootstrapServers: kafka.svc:9092
    consumerGroup: my-group
    topic: test-topic
    lagThreshold: '5'

Scenario 2 with TriggerAuthentication
triggers:
- type: kafka
  metadata:
    bootstrapServers: kafka.svc:9092
    consumerGroup: my-group
    topic: test-topic
    lagThreshold: '5'
 authenticationRef:
      name: keda-trigger-auth-kafka-credential

apiVersion: v1
kind: Secret
metadata:
  name: keda-kafka-secrets
  namespace: keda
data:
  sasl: "plaintext"
  username: "My confluent kafka API key"
  password: "My confluent kafka API key secret"

apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
  name: keda-trigger-auth-kafka-credential
  namespace: keda
spec:
  secretTargetRef:
  - parameter: sasl
    name: keda-kafka-secrets
    key: sasl
  - parameter: username
    name: keda-kafka-secrets
    key: username
  - parameter: password
    name: keda-kafka-secrets
    key: password

Expected Behavior
After deploying the scaled object, it should get the hpa.
Actual Behavior
ERROR	controllers.ScaledObject	Failed to ensure HPA is correctly created for ScaledObject	{"ScaledObject.Namespace": "keda", "ScaledObject.Name": "kafka-scaledobject", "error": "error getting scaler for trigger #0: error creating kafka client: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"}
Steps to Reproduce the Problem

Helm version is 3.3.x, Installed KEDA from https://github.com/kedacore/keda/releases/tag/v2.0.0-beta
Deployed ScaledObject as mentioned above
Checked the logs of KEDA operator and it errors out as mentioned above in the issue

Specifications

KEDA Version: 2.0.0-beta
Platform & Version: Azure Kubernetes Service
Kubernetes Version: 1.17.9
Scaler(s): Apache Kafka targeting Confluent Kafka

The API version on Scaledobject and TriggerAuthentication is keda.sh/v1alpha1
Scaledobjectsandtriggerauthentications.txt

I'm not a Confluent Kafka expert, does it run inside your cluster or do they manage it? From the looks of it, the address (kafka.svc:9092) points to a local service (which is also the one from our docs), is that correct?

Our confluent Kafka does not run on kubernetes cluster. Confluent Kafka bootstrap servers would look something like this pkc-xxxxx.eastus2.azure.confluent.cloud:9092

@harshik9 okay, so that's the value that should be in bootstrapServers section.

@zroubalik, yes. We tried by using that value in the bootstrapServers. What should be the sasl value when connecting to confluent Kafka.

Same issue here running a Kafka cluster locally, alongside with Keda installed on an on-premise K8s cluster. As a test, I created a Pod and was able to curl Kakfa topics from inside that Pod on my K8s. Apparently, Kafka cluster is reachable from inside my K8s cluster (initially I thought that that was the problem) but it feels like it is Keda that cannot reach Kafka endpoints.
Currently running Kafka without authentication, using Keda v2 and K8s 1.18!

Same issue here running a Kafka cluster locally, alongside with Keda installed on an on-premise K8s cluster. As a test, I created a Pod and was able to curl Kakfa topics from inside that Pod on my K8s. Apparently, Kafka cluster is reachable from inside my K8s cluster (initially I thought that that was the problem) but it feels like it is Keda that cannot reach Kafka endpoints.

The scenario you described here above, is Kafka with or without authentication?

Currently running Kafka without authentication, using Keda v2 and K8s 1.18!

Same issue here running a Kafka cluster locally, alongside with Keda installed on an on-premise K8s cluster. As a test, I created a Pod and was able to curl Kakfa topics from inside that Pod on my K8s. Apparently, Kafka cluster is reachable from inside my K8s cluster (initially I thought that that was the problem) but it feels like it is Keda that cannot reach Kafka endpoints.

The scenario you described here above, is Kafka with or without authentication?

Without authentication.

I was able to connect to confluent kafka with Authentication by going down on the KEDA version to 1.5.  https://keda.sh/docs/1.5/scalers/apache-kafka/
The authmode that I used is sasl_ssl_plain. I deployed all the files from here --> https://github.com/kedacore/keda/releases/tag/v1.5.0 from the deploy folder.

Hm that's strange, unfortunately I am not able to reproduce that. I am using in-cluster Kafka (instaled via Strimzi) and it is working (the same for our e2e tests that are passing).
Is there anything non standard in your Kafka config?

sasl_ssl_plain

@harshik9 for that you used the same configuration of ScaledObject and TriggerAuthentication?

I was able to connect to confluent kafka with Authentication by going down on the KEDA version to 1.5. https://keda.sh/docs/1.5/scalers/apache-kafka/
The authmode that I used is sasl_ssl_plain. I deployed all the files from here --> https://github.com/kedacore/keda/releases/tag/v1.5.0 from the deploy folder.

@harshik9 for that you used the same configuration of ScaledObject and TriggerAuthentication?

@zroubalik Our confluent Kafka is on azure. When we used the KEDA 2.0 BETA version. The Authentication parameters were sasl, Username and password. With sasl= plaintext, we were unable to connect but when I went down on the KEDA version 1.5, I had authentication parameters as authMode, username and password. The authMode that i gave was sasl_ssl_plain and this worked for me. I used the same scaledObject as in here --> https://keda.sh/docs/1.5/scalers/apache-kafka/ . But there was no necessity of providing a ca, cert and key. Username was our azure confluent kafka API key and password was our Confluent kafka API key secret.

I belive the issue was fixed by #1288 please reopen if the problem still persists

We are having the same issue over here. Can someone send some thoughts on how to fix it?
keda logs show the following:
{
   "ScaledObject.Namespace":"channels-integrations",
   "ScaledObject.Name":"ch-int-mercadolivre-orders-inbound-scaledobject",
   "error":"error getting scaler for trigger #0: error creating kafka client: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"
}

And ScaledObject  status show 'Unknown' state.

keda version 2.4
apiVersion: v1
kind: Secret
metadata:
  name: keda-kafka-secrets
  namespace: my-namespace
data:
  sasl: "plaintext as b64"
  username: "username as b64"
  password: "password as b64"
---
apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
  name: keda-trigger-auth-kafka-credential
  namespace: my-namespace
spec:
  secretTargetRef:
  - parameter: sasl
    name: keda-kafka-secrets
    key: sasl
  - parameter: username
    name: keda-kafka-secrets
    key: username
  - parameter: password
    name: keda-kafka-secrets
    key: password
---
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: my-scaled-object-name
  namespace: my-namespace
spec:
  scaleTargetRef:
    name: my-deployment-name
  cooldownPeriod: 30
  minReplicaCount: 0
  maxReplicaCount: 3
  pollingInterval: 10
  triggers:
  - type: kafka
    metadata:
      metricName: my-metric-name
      namespace: my-namespace
      bootstrapServers: our-broker-address.confluent.cloud:9092
      consumerGroup: consumer_group
      topic: my_topic
      lagThreshold: "10"
      offsetResetPolicy: earliest
    authenticationRef:
      name: keda-trigger-auth-kafka-credential

I was also facing the same issue with newer version of KEDA 2.4.
https://github.com/kedacore/keda/discussions/2125

@harshitak27 following approach might help you: https://github.com/kedacore/keda/issues/2101#issuecomment-924909906
Let us know and we can probably document this if it solves your issue.

@zroubalik Thank you for the solution. So here's what I changed in the scaledobject.

I added the parameter "tls" and set the value as "enable". This was not required with the older versions (1.4)
The value for sasl parameter was set as "plaintext"

Except for the above changes and few template changes, rest all remains same.
Also, wanted to know what does "ACTIVE" and "FALLBACK" mean? This shows up once we try to list the Scaledobjects once we deploy them.
Thanks again @zroubalik

Glad to hear that it works for you.
Active shows whether scaling is active - eg. some traffic in the trigger. Wrt Fallback you can read it in the docs: https://keda.sh/docs/2.4/concepts/scaling-deployments/

@harshitak27 Is there something that can be improved in the docs of our scaler / FAQ that could have helped you?
Otherwise I think we can close this issue.

It worked for me for confluent cloud

Just a question: is the broker hostname relative to the namespace the scaled object is in or the KEDA controller?
I'm having to put the full hostname of Kafka.kafkanamespace.svc.cluster.local:9092 to get connectivity despite the scaled object and broker being in the same namespace. I'd have expected Kafka:9092 to have worked like the documentation.

Hm that's strange, unfortunately I am not able to reproduce that. I am using in-cluster Kafka (instaled via Strimzi) and it is working (the same for our e2e tests that are passing).
Is there anything non standard in your Kafka config?

I am having the same issue with my kafka cluster deployed with Strimzi. I am not sure what I am doing wrong. I use the keda version 2.9.1. I want to authenticate using "scram_sha512".
I have the following CRs:
kind: Secret apiVersion: v1 metadata:   name: keda-kafka-secrets   namespace: demo data:   sasl: c2NyYW1fc2hhNTEy   ca: >-     LS0tLS1CR ... QxM2dyQkg=   username: <demo base64> # org.apache.kafka.common.security.scram.ScramLoginModule required username="demo" password="demo;   password: <demo base64> type: Opaque
`apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: kafka-scaledobject
namespace: demo
spec:
advanced:
restoreToOriginalReplicaCount: true
horizontalPodAutoscalerConfig:
behavior:
scaleDown:
stabilizationWindowSeconds: 30
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: consumer-demo
minReplicaCount: 0
maxReplicaCount: 10
pollingInterval: 5
cooldownPeriod:  10
triggers:

type: kafka
metadata:
bootstrapServers: dev-kafka-bootstrap-kafka.apps...com:443
consumerGroup: demo
topic: demo
Optional
lagThreshold: 2
authenticationRef:
name: keda-trigger-auth-kafka-credential`

`apiVersion: keda.k8s.io/v1alpha1
kind: TriggerAuthentication
metadata:
name: keda-trigger-auth-kafka-credential
namespace: demo
spec:
secretTargetRef:

parameter: sasl
name: keda-kafka-secrets
key: sasl
parameter: username
name: keda-kafka-secrets
key: username
parameter: password
name: keda-kafka-secrets
key: password
parameter: ca
name: keda-kafka-secrets
key: ca`

Did you configure something specific for strimzi? or am I missing a parameter for scram_sha512?

What do you see in KEDA operator logs?

I get the following error message: "2023-10-11T13:14:40Z ERROR scalehandler Error getting scalers {"object": {"apiVersion": "keda.sh/v1alpha1", "kind": "ScaledObject", "namespace": "demo", "name": "kafka-scaledobject"}, "error": "error creating kafka client: kafka: client has run out of available brokers to talk to: EOF"}
I currently removed tls for my internal listener, but it doesn't change anything. As soon as I specify scram_sha512 for sasl I get this error message.
When you test with Strimzi, which kafka version did you use? Did you have authentication set? Also did you specify a specific version in the ScaledObject metadata?

Ok I manage to make it work with scram_sha512 and tls. I will post my CRs and I hope it will help some people:
ScaledObject
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: kafka-scaledobject
  namespace: demo
spec:
  advanced:
    horizontalPodAutoscalerConfig:
      behavior:
        scaleDown:
          stabilizationWindowSeconds: 30
    restoreToOriginalReplicaCount: true
  cooldownPeriod: 10
  maxReplicaCount: 10
  minReplicaCount: 1
  pollingInterval: 5
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: consumer-demo
  triggers:
    - authenticationRef:
        kind: TriggerAuthentication
        name: keda-trigger-auth-kafka-credential
      metadata:
        bootstrapServers: 'dev-kafka-bootstrap-kafka.apps.cluster-....com:443'
        consumerGroup: demo
        lagThreshold: '5'
        topic: demo
      type: kafka

TriggerAuthentication
apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
  name: keda-trigger-auth-kafka-credential
  namespace: demo
spec:
  secretTargetRef:
    - key: username
      name: keda-kafka-secrets
      parameter: username
    - key: password
      name: keda-kafka-secrets
      parameter: password
    - key: sasl
      name: keda-kafka-secrets
      parameter: sasl
    - key: tls
      name: keda-kafka-secrets
      parameter: tls
    - key: ca
      name: keda-kafka-secrets
      parameter: ca

Secret
kind: Secret
apiVersion: v1
metadata:
  name: keda-kafka-secrets
  namespace: demo
data:
  ca: >-
    LS0tLS1CRUd ... hZUG9nVXBEeGE5WnhYCktLS0=
  password: T1VMekkd ... 2dyQkg=
  sasl: c2NyYW1fc2hhNTEy
  tls: ZW5hYmxl
  username: aGVsd ... w==
type: Opaque

@edubois10 thanks for sharing. So the problem was in missing tls setting, right?

i am facing the same issue again where in i have confluent kafka on prem with security protocol as sasl_ssl and sasl mechanism is plain therefore using in ssl section of triggerauth yaml as sasl_plaintext and also setting tls to enable but still see the below errors...keda version 2.8 is installed on k8s cluster(v 1.18)....any help would be greatly appreciated.
errors::::::::::
ERROR   Reconciler error        {"controller": "scaledobject", "controllerGroup": "keda.sh", "controllerKind": "ScaledObject", "scaledObject": {"name":"kafka-scaledobject","namespace":"crm-pmo-aswatson-sit"}, "namespace": "crm-pmo-aswatson-sit", "name": "kafka-scaledobject", "reconcileID": "e92dfdeb-a9a9-439d-9ed9-7278a69cb1f3", "error": "error creating kafka client: kafka: client has run out of available brokers to talk to: 2 errors occurred:\n\t* unexpected EOF\n\t* unexpected EOF\n"}
apiVersion: v1
kind: Secret
metadata:
name: kafka-secret
namespace: crm-pmo-aswatson-sit
type: Opaque
data:
sasl: cGxhaW50ZXh0
tls: ZW5hYmxl
saslUsername: cG..O
saslPassword: cG1....Q3JldDU0JA==
kafka-ca-cert.pem: LS0t......S0tCg==
apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
name: kafka-trigger-auth
namespace: crm-pmo-aswatson-sit
spec:
secretTargetRef:
- parameter: saslUsername
name: kafka-secret
key: saslUsername
- parameter: saslPassword
name: kafka-secret
key: saslPassword
- parameter: sasl
name: kafka-secret
key: sasl
- parameter: tls
name: kafka-secret
key: tls
- parameter: caCert
name: kafka-secret
key: kafka-ca-cert.pem
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: kafka-scaledobject
namespace: crm--sit
spec:
scaleTargetRef:
name: consumer-new--keda
kind: Deployment
pollingInterval: 10
minReplicaCount: 1
maxReplicaCount: 10
triggers:
- type: kafka
metadata:
bootstrapServers: uatgit11:9095,uatgi12:9095
topic: public....personalOffer
consumerGroup: pmo....loffer_new
lagThreshold: "3"
authenticationRef:
name: kafka-trigger-auth


[Video Conference] Default mute hotkey conflicts with OneNote

ℹ Computer information

PowerToys version: 0.22.0
PowerToy Utility:
Running PowerToys as Admin: YES
Windows build number: 19041.450

📝 Provide detailed reproduction steps (if any)

Press default mute hotkey (Windows-N)
Both OneNote quick note pop up and mute action occurs.

✔ Expected result
Since they both use the same, this is expected.  Suggestion to change mute key default to not conflict with a widely used product.
What is the expected result of the above steps?
❌ Actual result
Both OneNote quick note pop up and mute action occurs.

@thebitjockey
tracked in https://github.com/microsoft/PowerToys/issues/6246


Decide what to put on slider

[ ] most recent request?
[ ] link to open data explainer
[ ] link to annoucement
[ ] link to oab

@markmacgillivray is the first one possible? or most popular?
@markmacgillivray we can also have the map here yes. That's two!

@markmacgillivray can you clarify what the correct image size or ratio is for this? Is there one, how do you suggest desiging images so that they work at different sizes.

@chealsye this links in with our email discussion.

Notes from chat with @chealsye .

An open access button logo with text under a header saying "Paywalls got you down?"
David Himmelstein slide
slider the announcement. Rocket image, with text overlay with open data button launch.
FOR OAB. Rocket image, text overlay mention open data button launch.
For OAB. Story slider.

Uploaded Himmelstein quote, OAB story slider, and Paywalls got you down?
Sizes 800x500 and 800x400
https://github.com/OAButton/backend/commit/abb94068a16df5f3c9929421f5347ed660045376

Uploaded rocket slides. Orange one for the OAB site, more blue one for ODB. I think this will look best. OAB and ODB are noted in file names. Both 800x500 and 800x400 sizes.
@JosephMcArthur let me know if you want something different, whether totally or just text changes or if you want to add text to indicate someone should click on the image. https://github.com/OAButton/backend/commit/ebfcb0d4a036bf9409962c6de2c7a28efcc83dcb

We've decided, making another issue for putting them up.


AKS add oidc feature swagger to 2022-09-01

ARM API Information (Control Plane)
Port preview feature OIDC to GA api version

For failure in SDK azure-sdk-for-python-track2, caused by issue #1483.

For error DefinitionsPropertiesNamesCamelCase in ~[Staging] Swagger LintDiff , followed Swagger Suppression Process and got following approval.


Line Chart Point Radius cutoff & gradient fill

I am having an issue with my line charts point radius being cutoff at the edge and the fill not encapsulating the entire horizontal space.
See screenshot for reference: http://i.imgur.com/SyARWo0.png

@john-baker which version of Chart.js are you using?

My apologies, I mean to add that information: 1.0.2

Hmm, I know what the issue is but I'm not sure the best way to fix it.
The offending line of code is: https://github.com/nnnick/Chart.js/blob/master/src/Chart.Core.js#L1663
I feel like it would need some user configurable padding added

That does fix the cutoff issue, but does not address the fill color. My deserved effect is to omit the the edge points (first & last).
I have added this functionality for Line charts in my version of the source.
//Now draw the points over the line
//A little inefficient double looping, but better than the line
//lagging behind the point positions
var showFirstPoint = this.options.showFirstPoint;
var showLastPoint = this.options.showLastPoint;

helpers.each(pointsWithValues,function(point, key){
  if ((!showFirstPoint && key == 0) || (!showLastPoint && key == (pointsWithValues.length - 1))){
    //Do not draw point
  }
  else{
    point.draw();
  }
});

I have also added these to the Line chart default options. It's not perfect, but solved my problem.
Thank you :)

Sorry, missed the fill part. It probably draws to the rightmost scale point rather than the edge of the canvas.

Closing as fixed since a solution was found.


Slices of Snippets don't have indentation removed

Description
When creating a snippet with the following contents, the extra indentation of the shown code is removed to make it more readable:
// snippet.hide
import AsyncHTTPClient
import NIOCore
import Foundation

@main
struct Entrypoint {
    static func main() async throws {
        // snippet.show
        myCode()
        // snippet.hide
    }
}

However, doing the same with slices does not seem to have the same effect:
import AsyncHTTPClient
import NIOCore
import Foundation

@main
struct Entrypoint {
    static func main() async throws {
        // snippet.mySlice
        myCode()
        // snippet.end
    }
}

Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
I expect the second code to render as the following in markdown:
myCode()

Actual behavior
Indentation is kept, making code unnecessarily indented.
        myCode()

Steps To Reproduce
No response
Swift-DocC Version Information
No response
Swift Compiler Version Information
No response

i wasn’t able to reproduce this on version 1.3.0 of swift-docc-plugin:

what version are you on?


After upgrading to 3.8.0, useFetch won't make new requests after getting an error

Environment

Operating System: Linux
Node Version:     v18.17.1
Nuxt Version:     3.8.0
CLI Version:      3.9.1
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-fing2w?file=app.vue
Describe the bug
After you make a request without specifying a key, if you get an error as response, it seems useFetch isn't refreshing the automatically generated key so the error gets cached and that request can't be made anymore without refreshing the page.
Additional context
Started happening after upgrading from 3.7.4 to 3.8.0. Downgrading back fixed the issue for me.
Logs
No response

That was fast, thank you so much @danielroe!


Add Tutorial Link for 3D Series

Add an introduction to 3D video series link to the tutorials section

FYI i already linked these (very good) tutorials to the gdx-gltf readme. Since they are kinda specific to gdx-gltf library, i'm not sure it's needed to link them in this repo. I'm not against it, of course :-). It's up to the repo owners i guess.


Add format option to load_in_data_library

Context
See CartoDB/bigmetadata/issues/540. We should add an option to choose the format, which should default to GPKG.
cc @javitonino

Sounds like a plan.We choose the format here, from the [config][https://github.com/CartoDB/cartodb/blob/master/config/app_config.yml.sample#L133), so having an option to override the config could be enough. If this works, maybe we should consider using gpkg for the platform as a whole.
Also, I was going to add that you may want to test fgdb which was recently added to our supported file at the importer. But I don't think we support exporting those yet. I don't know how good our compatibility for fgdb is, but from the rest of formats gpkg is the least lossy of them in most circumstances.

cc @ethervoid @CartoDB/rt-managers RT :pray: ?


Add newline after unit refs in dwarfdump.

Coverage increased (+0.03%) to 86.563% when pulling 3b0ebfed01bd0a3d948c3cd65f726b317bf192a0 on khuey:dwarfdump-newline into<PHONE_NUMBER>9071fea4ef5a4c5576fb42dad7a4e4 on gimli-rs:master.


feat(nix): build and publish fedimint-devtools container

Use nix build -L .#container.fedimint-devtools to build locally.

@elsirion Are you able to create thew new dockerhub repo?

Not that I'm aware of. I do have a docker hub account but it appears to have no rights. It's likely that the fedimint namespace is a normal user account someone created because there were some pricing shenanigans for organizations …

@justinmoon I bet it was you.

We have fedimint/devtools now since fedimint/fedimint-devtools seemed a bit redundant.

We have fedimint/devtools now since fedimint/fedimint-devtools seemed a bit redundant.

So let's rename fedimint/fedimint-devtools to fedimint/devtools in the code here.


Is there any possible way using tensor parallel with ray serve (for multi-replica)?

Any possible work solution or some solution need to be figure out are welcome
I'm willing to contribute, but with only a few experience with using vllm for custom model inference

Yes I believe you can set ray_actor_options in Ray Serve to be {"num_gpus": 2} and setup vLLM with tensor_parallel_size=2.

I've tried, in my ray 2.9.3 and vllm 0.3.0 env, I use tensor_parallel_size=2 and not set num_gpus works with ray serve. Thanks  for you guys help.


incorrect functional induction principle

Prerequisites
Please put an X between the brackets as you perform the following steps:

[X] Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues
[X] Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries.
[X] Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)

Description
On the following example, test.induct is incorrect.
def f (x: Nat): Option Nat :=
  if x > 10 then some 0 else none

def test (x: Nat): Nat :=
  match f x, x with
  | some k, _ => k
  | none, 0 => 0
  | none, n + 1 => test n

#check test.induct

It looks like this:
test.induct (motive : Nat → Prop) (case1 : ∀ (x : Nat), motive x) (case2 : motive 0)
  (case3 : ∀ (n : Nat), motive n → motive n.succ) (x : Nat) : motive x

and case1 is missing an assumption like f x = some k.
Steps to Reproduce
Run lean on the example.
Expected behavior:
Something like this:
test.induct (motive : Nat → Prop) (case1 : ∀ (x k : Nat), f x = some k → motive x) (case2 : motive 0)
  (case3 : ∀ (n : Nat), motive n → motive n.succ) (x : Nat) : motive x

Actual behavior:
Wrong induction principle.
Versions
"4.11.0"
Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

Thanks for the report! I'll investigate. If I'm lucky then https://github.com/leanprover/lean4/pull/4149 might already fix it, we'll see.
I was hoping that two separate match statements might fix this, but it fails even worse:
https://live.lean-lang.org/#codez=CYUwZgBJAUAeBcEByBDALgSkQeQA5oEsB7AO2XQngF4AoCCAyWCAPggEYAGCNACxDIBnIgFsQEbiAA2g8SVIgadCKEhoQgtBDiJUmXRWrL6I9AGNeES4iYQA7gT4RjEAD4RhYiAGsIVNt4u7vIk4v4QpmgWEMwOfC70iW4SfmycCUnJZADUHKk8GlokSpmZAMQWIGa+6poAdAQkwACuZmhAA

I tried nested match statements but that can cause another problem: https://github.com/leanprover/lean4/issues/2962

A quick test confirms my worry that the MVarId.cleanup  step is at fault:
[Meta.FunInd] Goal before cleanup:
case hyp
motive : Nat → Prop
t : Nat
f : Nat.ibelow t
k x✝² : Nat
x✝¹ : _root_.f t = some k
x✝ : Nat.ibelow x✝²
⊢ motive x✝²

[Meta.FunInd] Goal after cleanup (toClear := [f, x✝]) (toPreserve := []):
case hyp
motive : Nat → Prop
x✝ : Nat
⊢ motive x✝

But if I put too much stuff into toPreserve array, then we also get induction principles that are not nice, because they contain completely unused variables, e.g.
info: ackermann.induct (motive : Nat → Nat → Prop) (case1 : Nat → Nat → ∀ (m : Nat), motive 0 m)
  (case2 : Nat → Nat → ∀ (n : Nat), motive n 1 → motive n.succ 0)
  (case3 : Nat → Nat → ∀ (n m : Nat), motive (n + 1) m → motive n (ackermann (n + 1) m) → motive n.succ m.succ) :
  ∀ (a a_1 : Nat), motive a a_1

This may need more careful thought, or a possibly a completely different approach. (Maybe instead of the blunt MVarId.cleanUp, only clean up the context very selectively to not remove useful assumptions.)

Ah, here is a partial work-around for you: If you put h : x in the match you get the assumption at least in two of the three cases:
def f (x: Nat): Option Nat :=
  if x > 10 then some 0 else none

def test (x: Nat): Nat :=
  match f x, h : x with
  | some k, _ => k
  | none, 0 => 0
  | none, n + 1 => test n

/--
info: test.induct (motive : Nat → Prop) (case1 : ∀ (k x : Nat), f x = some k → motive x) (case2 : motive 0)
  (case3 : ∀ (n : Nat), f n.succ = none → motive n → motive n.succ) (x : Nat) : motive x
-/
#guard_msgs in
#check test.induct

But yes, this is not satisfactory.