Remove version: Red.Red.CLI version 09jun23

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

URL: https://static.red-lang.org/dl/auto/win/red-09jun23-01ab176c6.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 886)

/azp run

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

https://github.com/microsoft/winget-pkgs/issues/142854


Export error without Internet access

Hello,
Describe the bug
Export failed with message "Error: Failed to query available provider packages"  when you don't have Internet access.
To Reproduce
Steps to reproduce the behavior:

Export token var and environnment
export DYNATRACE_API_TOKEN=dt0c01.xxxxxxxxxxxxxxxxxx.yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
export DYNATRACE_ENV_URL=https://server/e/env_id

Execute command like below :
./terraform-provider-dynatrace_v1.36.1 -export

See error
...

dynatrace_log_storage
dynatrace_os_services
Writing main.tf
Writing variables.tf
Writing providers.tf
Executing 'terraform init'

Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider
dynatrace-oss/dynatrace: could not connect to registry.terraform.io: Failed
to request discovery document: Get
"https://registry.terraform.io/.well-known/terraform.json": dial tcp: lookup
registry.terraform.io on <IP_ADDRESS>:53: no such host
Desktop (please complete the following information):

OS: RHEL 8
Version v1.36.1

Additional context
Server where provider is execute don't have Internet access due security behaviour.
Best regard

Hello @hvad, with the next release of the Terraform Provider you will be able to specify the flag -skip-terraform-init alongside -export. The execution of terraform init is just meant to be a convenience feature. The generated .tf files will be exactly the same.


fix typo

This repo does not take pull requests.  Please see https://github.com/google/google-api-go-client/blob/master/CONTRIBUTING.md for more information.
Additionally, this project auto-generates code directly from the public JSON API discovery docs, so typos like this need to be fixed in the upstream API, not here.
Closing request.

@gmlewis oops, sorry!

No worries, @shawnps!  Sometimes I wish we could just clean up API typos like this.  Unfortunately, we can't.  😞


Change SetCalledBy from internal to public

Describe the request
Description:
There are fuctions called SetCalledBy in codeunits 80 "Sales-Post" and 90 "Purch.-Post". They serve the same purpose but in "Sales-Post" this function is public and in "Purch.-Post" the same function is internal.
Requested change:
In codeunit  90 "Purch.-Post"
Before change
    internal procedure SetCalledBy(NewCalledBy: Integer)
    begin
        CalledBy := NewCalledBy;
    end;

After cahnge
    procedure SetCalledBy(NewCalledBy: Integer)
    begin
        CalledBy := NewCalledBy;
    end;

Additional context
This function allows to call one posting routine from another and allows subroutine not to throw error in the preview mode. Error will be thrown by the owning posting routine.
We need this change because we have a specific requirement from our customer to post addidtional corrective documents when application of Vendor Ledger Entries occures. Hence we call Purch.-Post from the function subscribed to codeunit 12 "Gen. Jnl.-Post Line". This works perfectly well for Sales Posting where SetCalledBy is public.
Internal work item: AB#539362

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 21453.


fix(goreleaser): clean changelog

Commits bumping version file should not be in changelog

Wow, thanks @vojtechmares !


kube-prometheus alertmanager cluster join failure

What did you do?
Created the Alertmanager CRD as defined in contrib/kube-prometheus/manifests/alertmanager-alertmanager.yaml - altered to set loglevel to debug
What did you expect to see?
Expected 3 alertmanager pods all joined to the same alertmanager cluster
What did you see instead? Under which circumstances?
Sometimes one of the pods does not join the alertmanager cluster, will see 1 in its own partition and 2 that joined the alertmanager cluster, so one instance is failing to join the cluster. I have deleted the CRD and re-created a number of times and can see that all the pods do not join the cluster everytime
I have exposed the alertmanager using a service and node port and can view the status of the alertmanager instances by visiting the /#/status path and can see that 2 instances are peered but one instance does not join and is acting as an independent instance, which means I get multiple notifications and my silences are not shared
Used the following to delete and re-create (After a full kube-prometheus installation)
kubectl delete alertmanagers -n monitoring main

# Wait a minute so the statefulset pod DNS entries are gone

kubectl apply -f alertmanager-alertmanager.yaml

Environment
ubuntu 16.04 on premise cluster

Prometheus Operator version:
Version is from branch release-0.24

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:43:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
kubeadm v1.12.2

Manifests:
This is the CRD manifest, same as in the repo mainfest file with log level set to debug

apiVersion: monitoring.coreos.com/v1
kind: Alertmanager
metadata:
  labels:
    alertmanager: main
  name: main
  namespace: monitoring
spec:
  baseImage: quay.io/prometheus/alertmanager
  logLevel: debug
  nodeSelector:
    beta.kubernetes.io/os: linux
  replicas: 3
  serviceAccountName: alertmanager-main
  version: v0.15.2

Prometheus Operator Logs:
Logs from one of the pods that did not join the alertmanager cluster

kubectl logs -n monitoring alertmanager-main-2 -c alertmanager

level=info ts=2018-11-07T15:30:19.626164445Z caller=main.go:174 msg="Starting Alertmanager" version="(version=0.15.2, branch=HEAD, revision=d19fae3bae451940b8470abb680cfdd59bfa7cfa)"
level=info ts=2018-11-07T15:30:19.626266946Z caller=main.go:175 build_context="(go=go1.10.3, user=root@3101e5b68a55, date=20180814-10:53:39)"
level=debug ts=2018-11-07T15:30:19.651524797Z caller=cluster.go:143 component=cluster msg="resolved peers to following addresses" peers=alertmanager-main-0.alertmanager-operated.monitoring.svc:6783,alertmanager-main-1.alertmanager-operated.monitoring.svc:6783,alertmanager-main-2.alertmanager-operated.monitoring.svc:6783
level=debug ts=2018-11-07T15:30:19.654451038Z caller=delegate.go:209 component=cluster received=NotifyJoin node=01CVQCQDC3AQETN1DEJB0EFZQX addr=<IP_ADDRESS>:6783
level=debug ts=2018-11-07T15:30:19.664648079Z caller=cluster.go:287 component=cluster memberlist="2018/11/07 15:30:19 [WARN] memberlist: Failed to resolve alertmanager-main-0.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-0.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n"
level=debug ts=2018-11-07T15:30:19.672566489Z caller=cluster.go:287 component=cluster memberlist="2018/11/07 15:30:19 [WARN] memberlist: Failed to resolve alertmanager-main-1.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-1.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n"
level=debug ts=2018-11-07T15:30:19.685298266Z caller=cluster.go:287 component=cluster memberlist="2018/11/07 15:30:19 [WARN] memberlist: Failed to resolve alertmanager-main-2.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-2.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n"
level=warn ts=2018-11-07T15:30:19.685351167Z caller=cluster.go:219 component=cluster msg="failed to join cluster" err="3 errors occurred:\n\n* Failed to resolve alertmanager-main-0.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-0.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n* Failed to resolve alertmanager-main-1.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-1.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n* Failed to resolve alertmanager-main-2.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-2.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host"
level=info ts=2018-11-07T15:30:19.685409467Z caller=cluster.go:221 component=cluster msg="will retry joining cluster every 10s"
level=warn ts=2018-11-07T15:30:19.685446068Z caller=main.go:265 msg="unable to join gossip mesh" err="3 errors occurred:\n\n* Failed to resolve alertmanager-main-0.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-0.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n* Failed to resolve alertmanager-main-1.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-1.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n* Failed to resolve alertmanager-main-2.alertmanager-operated.monitoring.svc:6783: lookup alertmanager-main-2.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host"
level=info ts=2018-11-07T15:30:19.685498869Z caller=main.go:322 msg="Loading configuration file" file=/etc/alertmanager/config/alertmanager.yaml
level=info ts=2018-11-07T15:30:19.685500069Z caller=cluster.go:570 component=cluster msg="Waiting for gossip to settle..." interval=2s
level=info ts=2018-11-07T15:30:19.689844329Z caller=main.go:398 msg=Listening address=:9093
level=info ts=2018-11-07T15:30:21.685798444Z caller=cluster.go:595 component=cluster msg="gossip not settled" polls=0 before=0 now=1 elapsed=2.000156573s
level=debug ts=2018-11-07T15:30:23.68605323Z caller=cluster.go:592 component=cluster msg="gossip looks settled" elapsed=4.000427559s
level=debug ts=2018-11-07T15:30:25.686383927Z caller=cluster.go:592 component=cluster msg="gossip looks settled" elapsed=6.000760857s
level=debug ts=2018-11-07T15:30:27.686648033Z caller=cluster.go:592 component=cluster msg="gossip looks settled" elapsed=8.001028863s
level=info ts=2018-11-07T15:30:29.68708214Z caller=cluster.go:587 component=cluster msg="gossip settled; proceeding" elapsed=10.00146267s

I have verified the DNS entries are okay after the pods are up and running by running the following in each pod - all succeeded and returned IPs that match kubectl get pods -n monitoring --selector app=alertmanager -o wide
kubectl exec -ti -n monitoring alertmanager-main-2 -c alertmanager -- nslookup alertmanager-main-2.alertmanager-operated.monitoring.svc

I appreciate this may be an alertmanager issue, but I am using kube-prometheus to install and had not seen this behaviour previously, thought it might be a timing issue and that the alertmanagers would re-try as the log messages indicate after 10 seconds, but one of them goes to gossip settled which seems to stop the retries I'm guessing
Pat

This is likely related to https://github.com/prometheus/alertmanager/pull/1428. Even if DNS entries appear correct at the time when you query them, the alertmanagers likely got outdated IPs returned by the DNS server at startup, and because DNS names are not resolved again by alertmanager (today), you end up with no Alertmanagers finding each other, even over time. To validate this, could you remove your Alertmanager cluster entirely, wait for 5 mintuse (less should be fine as the ttl for DNS entries are rather short in Kubernetes, but just to make sure), and then re-create the cluster. If the Alertmanagers then find each other, then https://github.com/prometheus/alertmanager/pull/1428 should indeed be the solution :slightly_smiling_face: .

Frederic,
Yep verified as you indicated, did this a number of times and comes back with all instances joining the cluster each time
Closing this issue
Thanks


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
docs(package): remove keyword null
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Codecov Report

Merging #651 into master will decrease coverage by 0.55%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #651      +/-   ##
==========================================
- Coverage   93.47%   92.91%   -0.56%
==========================================
  Files           7        7
  Lines        1073     1073
==========================================
- Hits         1003      997       -6
- Misses         70       76       +6

Impacted Files
Coverage Δ

src/service-config.js
92.72% <0%> (-3.64%)
:arrow_down:

src/service.js
90.75% <0%> (-2.11%)
:arrow_down:

src/endpoints-mixin.js
97.97% <0%> (-0.51%)
:arrow_down:

src/service-provider-mixin.js
89.38% <0%> (+3.09%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1dfe69f...1daea2e. Read the comment docs.

Coverage decreased (-0.9%) to 89.74% when pulling 1daea2eb6dd861294919b7295113166550e7f8dd on template-sync-1 into 1dfe69f60ca2113a6dc1acf6f4122e9279ab8541 on master.

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


OpenAI (Independent Publisher) issue

Api Name - shared_openaiip
Bug description - I am using correct API Key and in the prescribed format as "Bearer API_Key". But I am receiving the error Unauthorized with the below log
You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.
Is this a security bug? (Y/N) N
What is the severity of this bug? High

Hi. Can you check to make sure that there is a space between Bearer and your key? And that the are no other characters?

Hi. I am using the below format
"Bearer sk-****************"
But I am still facing issue..  Thanks for checking

Can you generate a new key and try again?

I did that as well, still no luck.. thanks

Could you try in a new Power Automate? And tell us which region you are in?

I tried in South East Asia region and I am still facing same issue. Not sure what to do?

CC: @Amjed-Ayoub @jopanchal

I tried recreating multiple times and the key works fine when used in HTTP action. Can you please help on this?

There is an update in the pipeline that Amjed can check to see if it has been deployed to your region. Can you tell me how many actions for the connector you can see available? The older connector has two, the new one I believe has five.

I can see all 5 engines in my connector as below..

I am seeing this issue too.

I am seeing the same issue.


RuntimeException: No supported encrypter found. The cipher and / or key length are invalid.

Hi,
I get this error when I try to open my BookStack: "RuntimeException: No supported encrypter found. The cipher and / or key length are invalid."
I installed bookstack exactly like this guy on a shared host:
https://github.com/ssddanbrown/BookStack/issues/91
-domain is pointing to /public
-hoster: all-inkl.com
what steps can I do to figure out what the problem is?

sorry it was just in installation misstake it works perfect on shared hosting now. His description of the installation was helpful https://github.com/ssddanbrown/BookStack/issues/91


LlaVa interleave for AutoCompletion

Hi !! We were trying to LORA finetune LLaVa interleave for a autocompletion task on a dataset (DialogCC) that might contain many images (>10) per conversation.

Is it possible to reduce the number of tokens for each image ?

We wanted the truncation side of the tokenizer to be left, will setting it cause any alignment issue with the images ?
For example, say the data is this
"image": ["1.jpg", "2.jpg"],
"conversations": [
    {
        "from": "human",
        "value": "<image> what is difference between the prev image and this <image>"
    },
    ...

and, left truncation makes it
...difference between the prev image and this <image>

then, the <image> will contain 1.jpg or 2.jpg ?

I don’t think there is an easy way to reduce the number of image tokens (say changing configurations), as the model is pretrained with very specific preprocessing that is closely related to how the vision encoder (SigLIP in the case of llava-interleave) is trained. There are many research works though that try to prune vision tokens, which you can look at.
I would imagine there will be misalignment, and this behavior is beyond the control of lmms-finetune (it is defined by the forward pass of llava-interleave implemented by huggingface transformers). Maybe you can try doing a quick test by inferencing with your example with left truncation.

Closing for now. Feel free to reopen if there are more questions.


install_tlc.sh script mutates the state of the test-runner container via apt update

The use of apt update/apt install in the test infrastructure code eliminates the possibility of having a stable (invariant) test runner between test runs.   This code must be rewritten (probably by using a customized docker container to be the test-runner that contains the necessary functionality) ASAP.

@zancas : we need more details on the problem.

I think the gist of this is that the apt-get install/update commands mean that the container running our tests changes each time we build it. This is bad because we'd like to have only the code-under-test and the dependencies it uses changing, leaving all other things stable in that container. We don't want a change to some tertiary package possibly breaking all of our builds. We can create a container that has all the underlying packages installed, then we only do a pip install -e of our code and its dependencies.

Moved from tlc environment


dont create extra threads in server handlers for ruby bidi streams

Changing the server-side handler in ruby benchmarks for bidi calls to not create the extra thread appears to improve qps by around 15 to 20%, at least when comparing benchmarks ran with client and server on the same host.
Thinking that this general approach for the ping pong could be a suggestion for back-and-forth bidi calls, so this also changes the examples and interop tests. Trying to merge this to v1.0.x, mostly because of the change to examples, but I could also move this to master.

latest commit updates the route guide client to try to make a little more clear the independence of requests and responses in the bidi calls


Documentation: Detail the minimum versions for the tooling.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
Is your feature request related to a problem?

The accelerator uses terraform functions that are only available in latter versions, it would be nice to have the minimum version required to run this module.
Also, it should be noted that Windows PowerShell will not work at installing the ALZ PS module.
Describe the solution you'd like

Additional context

Added specific versions.


Add Go's dep tool and upgrade to to 1.9.2

Leave glide in there for the time being until we are happy that we don't
need to use it anymore for anything else.
P.S. looks like my editor auto-fixes Dockerfile formatting errors, hence the extra diff...

The content of the change is fine, but I think your editor is wrong and should feel wrong about the spaces.
Show outdated

@aeijdenberg my bad, fixed.

Would adding an editorconfig help?

Oh I just realised what @aeijdenberg meant it did wrong. I doubt any auto formatting would pick that up in this case without a refactor.

Oh I just realised what @aeijdenberg meant it did wrong. I doubt any auto formatting would pick that up in this case without a refactor.

Yeah I was going to suggest maybe a refactor is in order to just have one cmd per RUN where it makes sense and then the formatting would be a bit more reliable. Happy to do a PR if you like but I didn't want to just change things for the sake of it!

I reckon go for it, but @aeijdenberg is the expert, there might be a reason it's written this way from https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/ so maybe just check there first...

There's actually quite an interesting balance in Dockerfiles between:

Readability
Fast build times, especially when iterating on it.
Number and size of image layers.


Enabling publishing portable apps

Addresses #109

What does the new project.json tool script look like?

Haven't tried it end to end but it should be something along these lines:
  "scripts": {
    "postpublish": "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:publish:FullTargetFramework%"
  }

We would also need to add configuration for this: https://github.com/aspnet/IISIntegration/issues/128. I think it is not for RC2 and it would be optional.

"%publish:publish:" really?
:shipit:

Copied incorrectly. It is just %publish:FullTargetFramework%


Not a single unicode snowman on site or readme

very dissapoint. :snowman:

☃

Fixed
https://github.com/snowman-io/snowman-io#contributing

:confetti_ball: :fireworks: good work here.


Updating Hashdiff Gem

I was tired of seeing rspec error:
The HashDiff constant used by this gem conflicts with another gem of a similar name.  As of version 1.0 the HashDiff constant will be completely removed and replaced by Hashdiff.  For more information see https://github.com/liufengyun/hashdiff/issues/45.

This PR updates the hashdiff library to the 1.x version and changes the reference to the new Hashdiff as opposed to the old HashDiff constant.
Addresses https://github.com/liufengyun/hashdiff/issues/45.

Hi @jonmchan could add your change in history.md (inside a ## Changed section)? after the merge I could generate a new version/tag

@dpzaba what should I make this - 2.2.0.beta4?

@dpzaba what should I make this - 2.2.0.beta4?

Sorry but I think I did not explain properly, I was asking to add the changes in a Changed section that currently does not exist, not to set a version.
To avoid more confusions and to speed up the merge could you just leave the changes to lib/couchrest/model/dirty.rb and couchrest_model.gemspec files?. I will add the change to history.md.
You can use the rest of the changes for a new PR.

@dpzaba ping

@dpzaba ping

it seems I can not merge it, I already ping @samlown

Sorry about that! You should be good to go now @dpzaba! Thanks!

Thanks!


[BUG] Not updating

When updating from v.1.6.0, obsidian reports: "update successful" but the plugin version remains 1.6.0, not 1.6.1.
Versions (please complete the following information):

OS: macOS 11.5.2
Obsidian version: v0.12.12
Plugin version: v1.6.0
Installer version: "5.0 (Macintosh; Intel Mac OS X 11_5_2) AppleWebKit/537.36 (KHTML, like Gecko) obsidian/0.12.12 Chrome/89.0.4389.128 Electron/12.0.14 Safari/537.36"

i forgot to update the manifest file.
I've updated the release files, please check if its fixed now.

Fixed. Thx.


Debugging  engine not selected

Eclipse with JDT starts fine. Highlighting is fine. Run is ok - it is running, but I can't see outputs in a console. However, I can't start debugging: it shows "Debugging engines not installed or not selected." "Debugging engine not selected". How to select debugging engine?

Updates: In running mode the console shows outputs if uses 'println' command. So it is ok.
I have upgraded maven to the latest version and made fresh re-compiling. Still the same error with debugging engine.

Thanks for the feedback.
The Debugger is one of the major features on the roadmap and will be available soon although not in the next few weeks. The current deployment is an alpha release. We're in the process of organising the repository and we will be publishing updates on plans, progress and proposals.
Hope this answers your question, please keep us posted on any issues.

Thank you, understood.
Looking forward for next releases.

Also depends on the Julia debugger getting ready, which is expected in the next julia release.

Next release - you mean 0.4.x or 0.5 ?
Meanwhile I am using current eclipse JDT alpha in editor / console mode and it already has some value to work in that environment.

It will be 0.5. We do expect to have repl integration though, for interactive use.


feat(git): run lint as a pre-commit hook

Since you already have Husky in place why not running lint on commit?
I'd also run tests on push once you have tests.

Thanks @juanjoDiaz !

:tada: This PR is included in version 1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(main): min of list

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


change onClick to onFocus, with a slight delay for safari

Background
I originally wanted to make the amount field select onFocus, as I wanted it to be possible to choose parts of the amount.
It was then pointed out that onFocus does not work for Safari, since the way onMouseUp works there deselects the text again after initially selecting it.
Therefore the choice was made to go with onClick instead, which seemed to work out for everyone involved, and you could still move around using the arrow keys for example if you just wanted to do edits.
Along came https://github.com/spliit-app/spliit/issues/136!
So I decided to look into getting it to work better, and more in line with the original thought.
Solution
After scouring the net I found that there is a rather simple solution for allowing this to work on Safari as well, which is to add a small delay to the selection of the input, since then the mouseup event will have come and gone.
I'm not sure if there are other concerns regarding the solution, but I am open to feedback on it.
Tested on

Safari 16.5.1
Chrome 123.0.6312.86
Mobile Safari iOS 17.4.1

Issues
Closes https://github.com/spliit-app/spliit/issues/136 on merge

Thanks @justcallmelarry!


Incorrect JSON data format passed to prompts.py file

I encountered an issue with the data being passed to the prompts.py script. The expectation was that the data would be in a proper JSON format, but the received data showed formatting errors.
Steps to Reproduce:
1. Creating prompt_generator file:
%%writefile prompt_generator.py

import sys
import json

def generate_prompt(context):
    document = context["vars"]["document"]
    question = context["vars"]["question"]

    return f"""Document.
{document}
Question: {question}
"RELEVANT" or "NOT_RELEVANT":"""

if __name__ == '__main__':
    data = sys.argv[1] if len(sys.argv) > 1 else None
    with open("log_data.txt", "a") as f:
        f.write(f"Log data: {data}\n")
    print(generate_prompt(json.loads(data)))

2. Creating prompfooconfig.yaml file:
%%writefile promptfooconfig.yaml
prompts:
  - 'prompt_generator.py:generate_prompt'
providers:
  - openai:gpt-3.5-turbo
tests:
  - vars:
      question: "question1"
      document: "document1"
    assert:
      - type: equals
        value: 'NOT_RELEVANT'
  - vars:
      question: "question2"
      document: "document2"
    assert:
      - type: equals
        value: 'RELEVANT'

Log data file:
Log data: '{vars:{question:question1,document:document1}}'
Log data: '{vars:{question:question2,document:document2}}'

It should be something like:
{
  "vars": {
    "question": "question1",
    "document": "document1"
  }
}

Hi @maciejbrasewicz,
Interestingly, I'm unable to repro with the example you provided:
$ cat log_data.txt
Log data: {"vars":{"question":"question1","document":"document1"}}
Log data: {"vars":{"question":"question2","document":"document2"}}

Are you able to share more information about your environment? (promptfoo version, python version, OS, ...)

Promptfoo 0.24.1
Python: 3.11.5
Node: v18.18.0
OS: Windows 11

Thanks for the info, I think this is a Windows issue.  Potential fix in #179, though I do not have a Windows machine to confirm.

@maciejbrasewicz I've published a possible fix in version 0.24.2 - please give it a try and let me know if you're still not seeing the right args passed to the script.


Updated weather to get a locationID

Please send your PR's the develop branch.
Don't forget to add the change to changelog.md.

Does the pull request solve a related issue? yes
If so, can you reference the issue? #339
What does the pull request accomplish? (Allows a user to use a locationID to get weather data instead of a city name)
If it includes major visual changes please add screenshots.

Updating the README.md files as appropriate.


feat: IsCoprime.wronskian_eq_zero_iff

Add IsCoprime.wronskian_eq_zero_iff: For two polynomials $a, b \in k[x]$ over a field, $W(a, b) = 0$ if and only if $a' = b' = 0$. This is a part of PR #15706.

There are a couple of unaddressed comments, but otherwise LGTM, thanks!
bors d+

bors r+


BToast default options

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
It would be great to define global default options for the BToast component, to set the pos to top-center for example.
Describe the solution you would like. A clear and concise description of what you want to happen
overrite defaults on plugin installation
Describe alternatives you have considered. A clear and concise description of any alternative solutions or features you've considered
Additional context. Add any other context or screenshots about the feature request here

@VividLemon i can create a pr for that if you want ?

Nothing has defaults, so go ahead and show me your implementation

@tada5hi I need the same, for example, for BModal:
app.use(BootstrapVue3, { BModal: { cancelTitle: 'MyLabel' } })

@tada5hi I need the same, for example, for BModal:
app.use(BootstrapVue3, { BModal: { cancelTitle: 'MyLabel' } })

I will try this weekend or early next week to be able to make a first proposal

@tada5hi Hi! Any news about your proposal?

Moving this to https://github.com/bootstrap-vue-next/bootstrap-vue-next/issues/1607


Multiple Jvmti agents can't interfere with mocking

If a class transformation is requested by any agent, the transformation
starts from the original code. Hence if we previosly added entry hooks
to a class, we now have to add them again. To do that we call into
ClassTransformer#transform every time a class get transformed, not only
when this was triggerd via ClassTransformer#mockClass.
Also added a test that simulates this behavior.
Unfortuantely the test required the slicer lib and jvmti.h again, so I
needed to copy it.

I haven't tried this or thought about it in detail, but is there any way we can either point the test code at the same external folder as the other code, or have a gradle task to copy it over to the second location before starting a build?
I don't love needing two copies of the same library pasted in, especially since then it'd need to be updated in two places. Another (even better) option might be to repackage this lib in a separate github repo, the way Jake did for dx: https://github.com/JakeWharton/dalvik-dx  Not sure if we can easily do that for a native library though.
If none of those options work, I'm fine with this, but just curious what else you've tried.

I could reuse the /external dir of dexmaker-mockito-inline. Changes updated.


fix: show the top of page after navigation

Closes #348
📑 Description
Scroll to the <main> element (that is the direct parent element of the page content slot) after navigation.
✅ Checks

[x] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] I have checked the page with https://validator.unl.edu/
[x] All the tests have passed
[x] My pull request is based on the latest commit (not the npm version).

Thank you for your PR.


[libmicrohttpd] update and various fixes

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Changes are in the individual commits for clarity.
They can be squashed into single commit

It is strange that the whole repo is licensed under MIT/Expat license, while any contribution requires acceptance of separate license.
Ok, my contribution isn't that large so I @microsoft-github-policy-service agree
However, according to the repo license, any person have rights to use it, while according to Contribution License Agreement only Microsoft and persons who receive the code from Microsoft (directly or indirectly) have rights to use it.
Isn't it a legal issue?
How can I check that code, which I receive from 3rd party, is coming from Microsoft?
Doesn't these two licenses conflict with each other?

@Karlson2k please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

It is strange that the whole repo is licensed under MIT/Expat license, while any contribution requires acceptance of separate license.
Ok, my contribution isn't that large so I @microsoft-github-policy-service agree
However, according to the repo license, any person have rights to use it, while according to Contribution License Agreement only Microsoft and persons who receive the code from Microsoft (directly or indirectly) have rights to use it.
Isn't it a legal issue?
How can I check that code, which I receive from 3rd party, is coming from Microsoft?
Doesn't these two licenses conflict with each other?

@Karlson2k please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

It is strange that the whole repo is licensed under MIT/Expat license, while any contribution requires acceptance of separate license.
Ok, my contribution isn't that large so I @microsoft-github-policy-service agree
However, according to the repo license, any person have rights to use it, while according to Contribution License Agreement only Microsoft and persons who receive the code from Microsoft (directly or indirectly) have rights to use it.
Isn't it a legal issue?
How can I check that code, which I receive from 3rd party, is coming from Microsoft?
Doesn't these two licenses conflict with each other?

@Karlson2k please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

It is strange that the whole repo is licensed under MIT/Expat license, while any contribution requires acceptance of separate license.
Ok, my contribution isn't that large so I
@microsoft-github-policy-service agree
However, according to the repo license, any person have rights to use it, while according to Contribution License Agreement only Microsoft and persons who receive the code from Microsoft (directly or indirectly) have rights to use it.
Isn't it a legal issue?
How can I check that code, which I receive from 3rd party, is coming from Microsoft?
Doesn't these two licenses conflict with each other?

@Cheney-W Do you want to squash all commits?
Otherwise I don't see how I can remove the port-version.
Even with squashed commits it needs at least "port-version": 2, correct?

Please remove "port-version": 1, from vcpkg.json because you have updated the "version": from 0.9.75 to 0.9.77.

If the port files are changed but the "version" is still 0.9.75, then the value of "port-version" should add 1. Obviously, you are not in this situation now.

@Cheney-W Seems that you are looking at overrall changes by this PR.
Please check individual commits.
This PR has 10 commits with changes of vcpkg.json. Each commit is atomic, resulting vcpkg.json is fully functional after each commit.

Let me know if you need to squash all of them into single commit.
We single commit port-version must be removed.

This PR has 10 commits with changes of vcpkg.json. Each commit is atomic, resulting vcpkg.json is fully functional after each commit.

The PR will be squased when merged.

@dg0yt OK, clear. I'll update it.

The PR has been updated.


Generate videos as zipped artifacts

Another attempt at generating videos on a schedule. Maybe these could be generated as artifacts with a nice expiration date!

These should have very short expiration dates, and ideally only a single version per playlist, if even that


Patch 1

I appreciate your collaboration, but I do not think that using a shellscript to make adjustments is a good option, and soon after the implementation of the graphical interface that would be left unused, that is why I created the options to pass the parameters directly to the main.py, but there are other changes to make, you can start by updating README.md, explaining how to adjust the brightness options, whenever you want to commit, do not use Portuguese, so that the project maintains consistency in a single language so you can attract as many contributors as possible, not only from Brazil (more languages can be added when a graphical interface is created), thanks

I appreciate your collaboration, but I do not think that using a shellscript to make adjustments is a good option, and soon after the implementation of the graphical interface that would be left unused, that is why I created the options to pass the parameters directly to the main.py, but there are other changes to make, you can start by updating README.md, explaining how to adjust the brightness options, whenever you want to commit, do not use Portuguese, so that the project maintains consistency in a single language so you can attract as many contributors as possible, not only from Brazil (more languages can be added when a graphical interface is created), thanks

OK. I'll help as best I can. About the English language, the Avell are not very well known by these consumers. However I will contribute using English as far as I can. Thanks for listening.

it is true that avell is not very well known outside of brazil, however this rgb keyboard comes from a company called tong fang, which distributes the same type of keyboard to companies that make customized notebooks around the world, so this algorithm will not only serve in the future for notebooks avell

as you do not hear any more activities I will close this PR, any doubt look for me that I will open again


[Feature request] 16:9 image size, the 1:1 now is too narrow, the text part is too wide.

Thanks for your great idea!
16:9 image size, the 1:1 now is too narrow, the text part is too wide. Reduce the width of the text and increase the width of the image.

Thanks for your support. Unfortunately, I'm not good at CSS, and the original style references other websites. I use this plugin mainly to extract text information from URLs. After all, you can not search the text on images in Obsidian.
And considering the varying size of the image, the feature might have to provide different styles for different images, or auto switch between styles based on the image size. As I said, I'm not good at CSS, so I honestly don't know how to implement such a feature.
If you like to modify the width of the image, you can fork this repo and create a revised version. This plugin is relatively stable for now, so a fork is recommended.

That's Great! The CSS snippet may be useful for others. Thank you for sharing!


API Error while register

Right now register is broken because of this. The error is most likely from the hash_data function:
https://github.com/belgio99/smartfactory/blob/eac70e3054822b6cb065a155826213e9ff71f22a/api/src/app.py#L49-L54
Traceback
ERROR:root:Exception: can only concatenate tuple (not "str") to tuple
INFO:     <IP_ADDRESS>:44178 - "POST /smartfactory/register HTTP/1.1" 500 Internal Server Error

Just to not forget, while the register now work, we get the hashed username instead of the username given!
We might simply be able to use  the name set in user settings, and perhaps we should, but  the odd thing is that the role is hashed too...


T02.01 - Move app schema deletion after deleting textview.

When you delete the app namespace schema reference ("app:xmlns") before deleting the text view, android studio will tell you that your xml document is invalid because the "app" is still referenced by the text view.
This PR will reorder the TODO to delete the text view first and then delete the schema reference.

On the other hand, students should get familiar with common IDE's errors and warning.

I think if the purpose of deleting the namespace first is to introduce with xml validation error to the student, then that would make sense. I still would warn the student that deleting the namespace will make the IDE display squiggly error lines in the xml.

Coding design decision that will not be done.. Closing the PR.


add command line prompts to stage scripts

might be simplest to add command line prompt to all steps in stage scripts and ask user it this is appropriate

tutorial for bash command line prompts here
https://www.linkedin.com/pulse/part-4-input-output-bash-scripts-your-devops-guide/

Done!

closed issue

Done.


Library is overriding the stdlib module.

I am getting below warning and my program does not run.
"c:\Machine Learning Project\pyenv\Lib\datetime.py" is overriding the stdlib module "datetime"
The warning is being shown for many libraries and my program does not run.
How do I fix this issue.

@mohsinzz, my first thought is this sounds like a duplicate of #3751 where Pylance is not automatically excluding your virtual environment directory and you need to manually exclude it with:
  "python.analysis.exclude": ["pyenv"],

If that doesn't work, please provide more detail on your project directory and virtual environment directory structure.

Datetime is a module, so you need to change your file name.


Bug: [Audit_RV] Two known vulnerabilities detected

2 vulnerabilities and 1 deprecated crate are detected while performing dependency linting.
The vulnerabilities will lead to memory leakage and segfault, considered to be sever ones.
Strongly recommend to upgrade to patched versions.

warehouse repo has the same vulnerabilities.

However, these vulnerabilities seem belong to substrate. Need to report to Substate if the latest Substate release has the same problem.
Description
{
    "database": {
        "advisory-count": 421,
        "last-commit": "2718c2db84a5d7607aa510fe33565e00c7959859",
        "last-updated": "2022-07-05T12:48:56Z"
    },
    "lockfile": {
        "dependency-count": 919
    },
    "settings": {
        "target_arch": null,
        "target_os": null,
        "severity": null,
        "ignore": [],
        "informational_warnings": [
            "unmaintained"
        ]
    },
    "vulnerabilities": {
        "found": true,
        "count": 2,
        "list": [
            {
                "advisory": {
                    "id": "RUSTSEC-2021-0130",
                    "package": "lru",
                    "title": "Use after free in lru crate",
                    "description": "Lru crate has use after free vulnerability.\n\nLru crate has two functions for getting an iterator. Both iterators give\nreferences to key and value. Calling specific functions, like pop(), will remove\nand free the value, and but it's still possible to access the reference of value\nwhich is already dropped causing use after free.",
                    "date": "2021-12-21",
                    "aliases": [],
                    "related": [],
                    "collection": "crates",
                    "categories": [
                        "memory-corruption"
                    ],
                    "keywords": [
                        "use-after-free"
                    ],
                    "cvss": null,
                    "informational": null,
                    "references": [],
                    "source": null,
                    "url": "https://github.com/jeromefroe/lru-rs/issues/120",
                    "withdrawn": null
                },
                "versions": {
                    "patched": [
                        ">=0.7.1"
                    ],
                    "unaffected": []
                },
                "affected": {
                    "arch": [],
                    "os": [],
                    "functions": {
                        "lru::LruCache::iter": [
                            "<0.7.1"
                        ],
                        "lru::LruCache::iter_mut": [
                            "<0.7.1"
                        ]
                    }
                },
                "package": {
                    "name": "lru",
                    "version": "0.6.6",
                    "source": "registry+https://github.com/rust-lang/crates.io-index",
                    "checksum": "7ea2d928b485416e8908cff2d97d621db22b27f7b3b6729e438bcf42c671ba91",
                    "dependencies": [
                        {
                            "name": "hashbrown",
                            "version": "0.11.2",
                            "source": "registry+https://github.com/rust-lang/crates.io-index"
                        }
                    ],
                    "replace": null
                }
            },
            {
                "advisory": {
                    "id": "RUSTSEC-2020-0071",
                    "package": "time",
                    "title": "Potential segfault in the time crate",
                    "description": "### Impact\n\nUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.\n\nThe affected functions from time 0.2.7 through 0.2.22 are:\n\n- `time::UtcOffset::local_offset_at`\n- `time::UtcOffset::try_local_offset_at`\n- `time::UtcOffset::current_local_offset`\n- `time::UtcOffset::try_current_local_offset`\n- `time::OffsetDateTime::now_local`\n- `time::OffsetDateTime::try_now_local`\n\nThe affected functions in time 0.1 (all versions) are:\n\n- `at`\n- `at_utc`\n- `now`\n\nNon-Unix targets (including Windows and wasm) are unaffected.\n\n### Patches\n\nPending a proper fix, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods.\n\nUsers and library authors with time in their dependency tree should perform `cargo update`, which will pull in the updated, unaffected code.\n\nUsers of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.\n\n### Workarounds\n\nNo workarounds are known.\n\n### References\n\ntime-rs/time#293",
                    "date": "2020-11-18",
                    "aliases": [
                        "CVE-2020-26235"
                    ],
                    "related": [],
                    "collection": "crates",
                    "categories": [
                        "code-execution",
                        "memory-corruption"
                    ],
                    "keywords": [
                        "segfault"
                    ],
                    "cvss": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                    "informational": null,
                    "references": [],
                    "source": null,
                    "url": "https://github.com/time-rs/time/issues/293",
                    "withdrawn": null
                },
                "versions": {
                    "patched": [
                        ">=0.2.23"
                    ],
                    "unaffected": [
                        "=0.2.0",
                        "=0.2.1",
                        "=0.2.2",
                        "=0.2.3",
                        "=0.2.4",
                        "=0.2.5",
                        "=0.2.6"
                    ]
                },
                "affected": {
                    "arch": [],
                    "os": [
                        "linux",
                        "redox",
                        "solaris",
                        "android",
                        "ios",
                        "macos",
                        "netbsd",
                        "openbsd",
                        "freebsd"
                    ],
                    "functions": {
                        "time::OffsetDateTime::now_local": [
                            "<0.2.23"
                        ],
                        "time::OffsetDateTime::try_now_local": [
                            "<0.2.23"
                        ],
                        "time::UtcOffset::current_local_offset": [
                            "<0.2.23"
                        ],
                        "time::UtcOffset::local_offset_at": [
                            "<0.2.23"
                        ],
                        "time::UtcOffset::try_current_local_offset": [
                            "<0.2.23"
                        ],
                        "time::UtcOffset::try_local_offset_at": [
                            "<0.2.23"
                        ],
                        "time::at": [
                            "^0.1"
                        ],
                        "time::at_utc": [
                            "^0.1"
                        ],
                        "time::now": [
                            "^0.1"
                        ]
                    }
                },
                "package": {
                    "name": "time",
                    "version": "0.1.44",
                    "source": "registry+https://github.com/rust-lang/crates.io-index",
                    "checksum": "6db9e6914ab8b1ae1c260a4ae7a49b6c5611b40328a735b21862567685e73255",
                    "dependencies": [
                        {
                            "name": "libc",
                            "version": "0.2.120",
                            "source": "registry+https://github.com/rust-lang/crates.io-index"
                        },
                        {
                            "name": "wasi",
                            "version": "0.10.0+wasi-snapshot-preview1",
                            "source": "registry+https://github.com/rust-lang/crates.io-index"
                        },
                        {
                            "name": "winapi",
                            "version": "0.3.9",
                            "source": "registry+https://github.com/rust-lang/crates.io-index"
                        }
                    ],
                    "replace": null
                }
            }
        ]
    },
    "warnings": {
        "unmaintained": [
            {
                "kind": "unmaintained",
                "package": {
                    "name": "net2",
                    "version": "0.2.37",
                    "source": "registry+https://github.com/rust-lang/crates.io-index",
                    "checksum": "391630d12b68002ae1e25e8f974306474966550ad82dac6886fb8910c19568ae",
                    "dependencies": [
                        {
                            "name": "cfg-if",
                            "version": "0.1.10",
                            "source": "registry+https://github.com/rust-lang/crates.io-index"
                        },
                        {
                            "name": "libc",
                            "version": "0.2.120",
                            "source": "registry+https://github.com/rust-lang/crates.io-index"
                        },
                        {
                            "name": "winapi",
                            "version": "0.3.9",
                            "source": "registry+https://github.com/rust-lang/crates.io-index"
                        }
                    ],
                    "replace": null
                },
                "advisory": {
                    "id": "RUSTSEC-2020-0016",
                    "package": "net2",
                    "title": "`net2` crate has been deprecated; use `socket2` instead",
                    "description": "The [`net2`](https://crates.io/crates/net2) crate has been deprecated\nand users are encouraged to considered [`socket2`](https://crates.io/crates/socket2) instead.",
                    "date": "2020-05-01",
                    "aliases": [],
                    "related": [],
                    "collection": "crates",
                    "categories": [],
                    "keywords": [],
                    "cvss": null,
                    "informational": "unmaintained",
                    "references": [],
                    "source": null,
                    "url": "https://github.com/deprecrated/net2-rs/commit/3350e3819adf151709047e93f25583a5df681091",
                    "withdrawn": null
                },
                "versions": {
                    "patched": [],
                    "unaffected": []
                }
            }
        ]
    }
}

Possible Fix
upgrade the dependent package to patched versions.
Steps to Reproduce

Install cargo-audit subcommand.
Navigate to root folder (same directory with cargo.toml)
Run cargo audit.

Context
Adversary databased used: RustSEC.

LRU issue has been resolved in substrate 28.
the second - time - is still present.

no longer an issue.


made the answers interactive

We need a variable that counts the number of correct answers

let correctAnswersCount = 0;
let wrongAnswersCount = 0;
they don't change, because they outside of the scope.  we need to store only correct results in variable and use it.

2) also this code snippet adds ul element 4 times to the DOM: answersListElement.appendChild(answerElement);


[Draft] TransactionStream support

Yes I agree, the mutex is a workaround so it can fit with the existing code. Managing events from two streams the "right" way would require a bit of a rethink, but for now the performance should still be close to optimal (with a big enough upload pool)


[sx] Add ginput

This PR adds sx.ginput that uses a PlotWidget to get a set of points given by the user.
The function plugs an object on a PlotWidget to handle the interaction and use its status bar to provide indication to the user.
It operates by default the most recent visible plot created with either sx.plot or sx.inshow.
It blocks until one of the following occurs: the user select all the required points, the PlotWidget gets hidden or a timeout is triggered.
It returns a list of (x,y) coordinates of all the points.
Points can be undo with either Delete, backspace or Ctrl-Z.
Points can only be set while in zoom mode.
I didn't succeeded so far in writing an interactive test for it...
Closes  #1614

It would be convenient to give back a list of objects with compatibility with matplotlib.
If those objects are accessed as a list they get the same information as being just (x, y) but leaving the door open to provide more information (xPixel, yPixel, data, ...)

I can provide objects that subclass tuple and give more information through additional getters

Also need to fix support of draggable markers: selected points data does not get updated...

It now returns a list of result objects that inherits from 2-tuple but provide additional information about the top-most item in the plot at that position through additional methods: getItem, getData, getIndices
I fixed consistency of returned positions by removing the fact that markers are draggable.
If draggable markers are needed, it can be done, but it is simpler this way and the user can always undo the last point.
I added how-to use examples in ginput docstring.

Great.
I was expecting that when calling ginput, the widget to which ginput refers should be shown on top:
w.show() w.raise_()


Missing for stable release

[ ] Documentation

Anything else ?

From Slack about Buzz and React:

@nyholm: I know Im conservative to tag 1.0, and I also know that there are plenty of major version numbers after 1.0. But what is our general rule? I feel that Buzz is too immature. React is mature but it has only 500 downloads and unstable dependencies.

Guzzle5 on the other hand has been used quite a lot and no PR has been merged the last couple of months. Thats when I think we should tag 1.0. Any thoughts on this topic? (edited)

@dbu: in my opinion, we should tag 1.0 when we either are confident or when nothing much happened for a month and the library looks ok

eternal beta is also not great - people will still start to rely on it and doing a BC break from some beta to the actual 1.0 will be more trouble than just bumping to 2.0

unstable dependencies is not great however. is there any chance they become stable?

@nyholm: Not in the case of react as far as I know

Lets tag 1.0 for Buzz at the end of August.

As for React I’ll leave that up to someone else. It has been no/few changes there but I do not know if that is because none uses it or because it is perfect.

For the cackephp-adapter I think we should wait 3-6 months before a stable release. Just to see how people are using it and if they are happy with it.

Given how rare this is used, we can probably close this for now and keep using 0.x majors.


Rebrand main version to Welkin

⚠ IMPORTANT ⚠: This is a public repository. Make sure to not disclose:

[x] personal data beyond what is necessary for interacting with this Pull Request;
[x] business confidential information, such as customer names.

Quality gates:

[x] I'm aware of the Contributor Guide and did my best to follow the guidelines.
[x] I'm aware of the Glossary and did my best to use those terms.

Hi folks,
This PR rebrands the main version of the public docs to Welkin. I also took this opportunity to upgrade mike and other dependencies.
This is a very special PR, for a few reasons:

It was already reviewed in a staging environment by a large number of stakeholders.
It changes 232 files.
The gh-pages branch was changed out-of-process, to facilitate migration.

Therefore, until this PR is merged:

GitHub Actions is disabled, to avoid weird behavior with gh-pages. I will test if actions works correctly after the PR is merged.
CODEOWNERS is disabled, to avoid spamming everyone.

The PR is quite large and has been broadly reviewed. Please only "sample" a few changes to make sure something stupid didn't squeeze in, but otherwise, I believe we can fix these after-the-fact.

Nice catch @linus-astrom . Thanks and fixed!


Create a exception to thow when Options not exists

When the user try to get a option that not exist, cxxopt library
throw a std::domain_error, that make a segfaults. See #185.
On this PR I create a new Exception class from OptionParseException
that is throw when this situation occur. This avoid the SegFaults
error.

This change is

I don't think it's a ParseException, so it probably shouldn't derive from that. I would like to know why it ends up segfaulting. Presumably if the std::domain_error is caught then it won't segfault.
I think this one makes sense to be a std::domain_error, in the same way that you'll get a dynamic cast exception if you cast a value that exists to the wrong type. I don't think that this error is using cxxopts incorrectly in the same way that all the other exceptions indicate parse errors, at that point you're just using a value stored in a container incorrectly.

Closing because this is currently the correct behaviour.


hardware_info: different fields between native_python and raspberry

The fields from hardware_info are different between the implementations:
https://github.com/fusion44/blitz_api/tree/main/app/repositories/hardware_impl
e.g. native_python has disk_io stuff which would be cool

I agree. On RaspiBlitz we only fetch the available hardware values that are available through Redis instead of fetching them with Python for performance reasons. @rootzoll what do you think? Should I fetch them via python or do we add more fields via the native RaspiBlitz script?

what do you think? Should I fetch them via python or do we add more fields via the native RaspiBlitz script?

If its not a bit performance think and its just system info data you can also use the python native way.


Migrate to Polymer 1.0

Some features used by Polymer 0.5 may be deprecated and we should migrate to ensure compatibility with newer browser versions.
Example: https://github.com/uProxy/uproxy/issues/1899

Just noticed the following message in the js console (while working on uproxy-website) which also uses Polymer 0.5:
'Object.observe' is deprecated and will be removed in M50, around April 2016. See https://www.chromestatus.com/features/6147094632988672 for more details. [polymer.js:4193]

Lo and behold, it's April 2016! Should this be prioritized?

@jpevarnek, how far are we from the migration? It would be great to enumerate what is left, and maybe spread the load. We could even organize a "Fix-it" day or two with the team to get it done?
Mobile is having issues with performance and memory consumption, and Polymer 1.0 can save it. According to the Polymer 1.0 documentation, we get:

Dramatically faster startup time and runtime performance than 0.5, even in Chrome where web components are natively supported.
Significantly smaller payload than 0.5.

Also, as someone getting started with Polymer, it's being a huge pain, since the documentation for 0.5 is gone. And learning something that is already deprecated is not very motivating :-/
Please let me know if I can help!

Right now the big thing to do is to eliminate data-binding issues.  That's
being tracked in #2556.  If you want to work on any of those it would be
wonderful!
I've been prioritizing Android lately in line with what we talked about,
but looking forward to moving back to taking care of those once Android
becomes a bit more stable.
On Wed, Aug 17, 2016 at 1:04 PM Vinicius Fortuna<EMAIL_ADDRESS>wrote:

@jpevarnek https://github.com/jpevarnek, how far are we from the
migration? It would be great to enumerate what is left, and maybe spread
the load. We could even organize a "Fix-it" day or two with the team to get
it done?
Mobile is having issues with performance and memory consumption, and
Polymer 1.0 can save it. According to the Polymer 1.0 documentation
https://www.polymer-project.org/1.0/docs/about_10#highlights, we get:
Dramatically faster startup time and runtime performance than 0.5, even in
Chrome where web components are natively supported.
Significantly smaller payload than 0.5.
Also, as someone getting started with Polymer, it's being a huge pain,
since the documentation for 0.5 is gone. And learning something that is
already deprecated is not very motivating :-/
Please let me know if I can help!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/uProxy/uproxy/issues/1900#issuecomment-240478196, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA3G7mEB1s1r6L9SmUheVqmNIxXL-_f_ks5qgz8egaJpZM4F-oUB
.

since the documentation for 0.5 is gone

http://polymer-project.org/0.5/ (but yeah hopefully we won't need that for much longer!)

I believe it may be possible to have Polymer 1.0 and 0.5 co-exist. I was able to get that to partially work.
What I did was to replace all mentions of Polymer with Polymer05 in the old library and our code. I was then able to have both Polymer 1.0 and 0.5 components co-exist in a simple page.
It broke down when I had 1.0 and 0.5 components that depended on the same component. That's because the components are registered globally with the same tag name. If we replace the tag names as well (e.g. 'paper-button' -> 'paper05-button'), then it may work. I didn't get to try that and I'm not sure what else may break.
It may be worth looking more into this. By allowing the different libraries to co-exist, we can:

Stop adding 0.5 code that will need to be replaced
Incrementally replace existing code, which is much more feasible than doing it all at once.

OMG they just released 1.7.0 and they're already talking about the breaking changes for the upcoming 2.0 release

It's not that bad. I talked to the Polymer team while I was in San Francisco. They are well aware of the issues on the migration to 1.0, and thought careful about the migration to 2.0.
For instance, you will be able to make an incremental transition to 2.0. They also introduced this "hybrid mode" where you can have your 1.0 elements be forward-compatible.
For more info on the migration to 2.0, see https://www.polymer-project.org/1.0/blog/2016-09-09-polymer-2.0.
With Polymer 2.0 almost out of the door, we should consider migrating to 2.0 directly, rather than to 1.0.


Create bot boilerplate

This contains logging and extensions. Logs will be written to zz.log.

better than what I had since it's my first time using disnake


👥 EntraID integrations with AWS Identity Center tracking issue (see comments)

User Story
As the AP team I want to know where we are at with AWS Identity Center
Value / Purpose
🗣 Keep team updated on external dependancies
Useful Contacts
Julia and Rich
Proposal
keep this issue in block until done
Definition of Done

[ ] App Registrations have been created by TechServices
[ ] Work completed on AWS Identity Centre

From the 13/05/24 John N
"The two EntraID App Registrations have been scoped that will need to be completed for the SCIM functionality and the AWS Identity Centre connection. Yesterday they started looking at the Entra Security Groups self-service side of the demand. It is the piece that we need to spend some time focussing on getting right for us and you so that it will be secure and easy for you moving forward until we look at the next demand for options on automation."

Meeting scheduled to for today 15/05 09:30 with John N

Original demand submitted on April 30th.
Approved on May 13th
Contacted by TS requesting additional information on May 21st
Returned questionnaire on May 22nd.
Expecting a meeting either 23rd-24th May or First week of June

Solution Surgery attended
Next step to continue implementation and I will start an ADR

Related issue

ADR-010 created here

Successfully tested app registrations on Friday with Julia and Dave for auth0

Ongoing

IDAM Submissions for Application Registrations approved and received
Integration testing with Identity Center completed
Planned Next Steps
App registration added to Auth0 configuration
Current GitHub Team group to accounts to be transformed into EntraID groups
Testing with users


Update zio, zio-test, zio-test-sbt to 2.0.12

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

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

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

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

Superseded by #235.


How not to show the zero values after scanning?

Hi Jeremy.
First of all I would like to know if there is a post scan call that when showing the data in the report, the records that are zeroed, do not appear, as the file is too big for viewing.
This call can be during execution or after execution?
Second, is it possible to sort these records by severity?
Att,
Bertino

By zeroed - you mean have no identified vulnerabilities?

No, on the contrary, many files are registered that have the counter reset, and the file html are large with more than 50mb.

What counter are we talking about?
Dealing with large scans - we do have a planned feature to only report vulnerable dependencies which will reduce the size some. You can also use one of the other report formats instead of HTML.  Alternatively, is there a way to break the scan up into small pieces?

Jeremy
I tried to send an attachment as a sample but unfortunately it exceeds the
capacity
Att,
Bertino
Em qua., 2 de dez. de 2020 às 10:12, Jeremy Long<EMAIL_ADDRESS>escreveu:

What counter are we talking about?
Dealing with large scans - we do have a planned feature to only report
vulnerable dependencies which will reduce the size some. You can also use
one of the other report formats instead of HTML. Alternatively, is there a
way to break the scan up into small pieces?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/2986#issuecomment-737221630,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE6INEKRQ3F3GNGDUKY6HIDSSY4LNANCNFSM4UH6RYMA
.

circling back to this issue....  What type of project is this? I'm betting it is node.js and you have the RetireJS analyzer enabled. For node.js projects I would highly recommend disabling the RetireJS analyzer and the nodeJS Analyzer (at least in ODC 6.0.x and earlier). The RetireJS Analyzer is looking for client side JS and scans every JS file and creates an entry in the report for every single one...  The node JS analyzer is currently just producing tons of false positives.

circling back to this issue....  What type of project is this? I'm betting it is node.js and you have the RetireJS analyzer enabled. For node.js projects I would highly recommend disabling the RetireJS analyzer and the nodeJS Analyzer (at least in ODC 6.0.x and earlier). The RetireJS Analyzer is looking for client side JS and scans every JS file and creates an entry in the report for every single one...  The node JS analyzer is currently just producing tons of false positives.


No --safe option

There is no --safe option documented here

It works for me, documentation should probably be updated though. PR welcome.

Sorry for the delay,
I created a PR with the update


Default items minted on drop page

https://kodadot.xyz/ahp/gallery/108-85
https://kodadot.xyz/ahp/gallery/108-66
https://kodadot.xyz/ahp/gallery/108-88
https://kodadot.xyz/ahp/gallery/108-57
https://kodadot.xyz/ahp/gallery/108-24
https://kodadot.xyz/ahp/gallery/108-6
it looks like we still have this issue
minting default img of the collection

Do you know if #9575 will fix that?
close if duplicate

the issue is that metadata were never updated by the bot :)
My best bet is that UI dont respect the fact that API needs to be called after user minted it


Bad state: No element

I've been using it for a long time, but now it's not working and i got this message
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Bad state: No element
E/flutter (14161): #0      List.first (dart:core-patch/growable_array.dart:343:5)
E/flutter (14161): #1      Geocoder2.getDataFromCoordinates (package:geocoder2/src/geocoder2.dart:25:44)
E/flutter (14161):
E/flutter (14161): #2      MyApp.printdata (package:untitled/main.dart:12:20)
E/flutter (14161):

I have the same problem. I had it working on Flutter Web, but it does not function with the Android restricted key


Organize Get Started pages in docs

Get Started

with Go
with contributing to Juno
with contributing to Juno docs

Done


Slightly incorrect stack trace in release (with debug info) mode

Here is the sample code that reproduces the issue:
#define BACKWARD_HAS_DW 1
//... includes above
#define BACKWARD_HAS_DW 1
using namespace backward;

void print(ResolvedTrace& trace)
{
    for (auto& loc : trace.inliners)
        std::cout
            << " " << loc.filename
            << " " << loc.function
            << ": "
            << loc.line
            << std::endl;
}

void Backtrace()
{
    StackTrace st;
    st.load_here(32);

    TraceResolver tr;
    tr.load_stacktrace(st);

    for (size_t i = 0; i < st.size(); ++i)
    {
        ResolvedTrace trace = tr.resolve(st[i]);

        print(trace);

        std::cout
            << " " << trace.object_filename
            << " " << trace.object_function
            << " [" << trace.addr << "]: "
            << trace.source.line
            << std::endl;
    }
}

namespace ns
{
    template <typename T, typename U>
    inline void foo(T t, U u)
    {
        Backtrace();
    }
}

template <typename T>
struct Klass
{
    T t;

    inline void bar()
    {
        ns::foo(t, true);
        auto x = 0;
    }
};

inline void c()
{
    Klass<int> k;
    k.bar();
}

void b()
{
    c();
}

void a()
{
    b();
}

int main(int argc, char* argv[])
{
    a();
}

The stack trace it produces (removed not interesting info) is:
sample Backtrace() [0x559733a2e67a]: 41
sample/src/test.cpp foo<int, bool>: 77
sample/src/test.cpp bar: 85
sample/src/test.cpp c: 90
sample/src/test.cpp b: 95
sample/src/test.cpp a: 100
sample main [0x559733a2e258]: 66
line 41 is inside Backtrace - ok
line 77 is inside bar() - reported foo<int, bool>
line 85 is inside c() - reported bar()
line 90 is inside b() - reported c()
etc ...
It looks like it is shifted (inlined  functions).
Works perfectly in debug. Not sure if interpret it correctely though.

are you using unwind for walking the stack?
what platform, os, compiler are you using
On Wed, Nov 28, 2018, 12:23 Alexandre Anoutchine<EMAIL_ADDRESS>wrote:

Here is the sample code that reproduces the issue:
#define BACKWARD_HAS_DW 1
//... includes above
#define BACKWARD_HAS_DW 1using namespace backward;
void print(ResolvedTrace& trace)
{
for (auto& loc : trace.inliners)
std::cout
<< " " << loc.filename
<< " " << loc.function
<< ": "
<< loc.line
<< std::endl;
}
void Backtrace()
{
StackTrace st;
st.load_here(32);
TraceResolver tr;
tr.load_stacktrace(st);

for (size_t i = 0; i < st.size(); ++i)
{
    ResolvedTrace trace = tr.resolve(st[i]);

    print(trace);

    std::cout
        << " " << trace.object_filename
        << " " << trace.object_function
        << " [" << trace.addr << "]: "
        << trace.source.line
        << std::endl;
}

}
namespace ns
{
template <typename T, typename U>
inline void foo(T t, U u)
{
Backtrace();
}
}
template struct Klass
{
T t;
inline void bar()
{
    ns::foo(t, true);
    auto x = 0;
}

};
inline void c()
{
Klass k;
k.bar();
}
void b()
{
c();
}
void a()
{
b();
}
int main(int argc, char* argv[])
{
a();
}
[image: screenshot]
https://user-images.githubusercontent.com/417876/49179983-d4a1aa80-f353-11e8-822d-9a054d4549d0.png
The stack trace it produces (removed not interesting info) is:
sample Backtrace() [0x559733a2e67a]: 41
sample/src/test.cpp foo<int, bool>: 77
sample/src/test.cpp bar: 85
sample/src/test.cpp c: 90
sample/src/test.cpp b: 95
sample/src/test.cpp a: 100
sample main [0x559733a2e258]: 66
line 41 is inside Backtrace - ok
line 77 is inside bar() - reported foo<int, bool>
line 85 is inside c() - reported bar()
line 90 is inside b() - reported c()
etc ...
It looks like it is shifted (inlined functions).
Works perfectly in debug. Not sure if interpret it correctely though.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bombela/backward-cpp/issues/130, or mute the thread
https://github.com/notifications/unsubscribe-auth/AANMjNT2pdV0UMx970u5_z3wyXEOTUOKks5uzvDcgaJpZM4Y4X3m
.

Yes, unwind (dw, elf)
Ubuntu 18.04.1 x86_64
gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0

It seems that for inlined functions the line number doesn't correspond to the function name.
struct inliners_search_cb {
...
 case DW_TAG_inlined_subroutine:
	ResolvedTrace::SourceLoc sloc;
	Dwarf_Attribute attr_mem;

	if ((name = dwarf_diename(die))) {
		sloc.function = name;
	}
	if ((name = die_call_file(die))) {
		sloc.filename = name;
	}

	Dwarf_Word line = 0, col = 0;
	dwarf_formudata(dwarf_attr(die, DW_AT_call_line, &attr_mem), &line);

So the function name it reports doesn't correspond to the line number. It is like it is shifted for the function names but the line numbers are correct. Any idea what might be wrong ?
By the way, is it possible to have demangled names for the inline functions ?

As far as I can tell the code relies on the information from the die. Could it be in your case the https://github.com/bombela/backward-cpp/blob/master/backward.hpp#L2759 branch is taken and behaves wrong?
Dwarf function names are not mangled. Only object information (used as fallback) are mangled though, and we demangle them as best as we can.


Choose which GPU to use

How can I choose which GPU to use with Keras and the Tensorflow backend? I have an AWS gx.8xlarge with 4 GPUs, I'd like to run totally seperate experiments on each, does anyone know if this possible?

you can use tensorflow tf.device just like you would in regular tensorflow code. Please see this for an example http://blog.keras.io/keras-as-a-simplified-interface-to-tensorflow-tutorial.html

@tetmin
Use environment variable CUDA_VISIBLE_DEVICES
http://www.acceleware.com/blog/cudavisibledevices-masking-gpus

@tetmin Another possibility is to run your experiments in separate docker containers and pass one GPU per container with the --device flag. See this.

@linxihui, @denlecoeuche good ideas guys, i'm actually using a docker container already so that seems like a good way to do it. I tried using tf.device as suggested but that doesn't seem to work, the network ended up using multiple GPUs in a strange way.

At the beggining of the script set the following enviroment variables.
import os
os.environ["CUDA_DEVICE_ORDER"] = "PCI_BUS_ID"
os.environ["CUDA_VISIBLE_DEVICES"] = "1"  # use id from $ nvidia-smi

Worked for me to choose the 2nd GPU in the cluster i'm using.


Decorators as an alternative to mixins

It'd be good to give an option to not use mixins. Just giving my idea to start the discussion.
import {Navigation, State, TransitionHook} form 'react-router/high-order-components';

@TransitionHook()
@Navigation()
@State()
class Foo {
  // propTypes can be used to name the props
  // otherwise they default to routerTransitions, routerNavigation, routerState
  static propTypes = {
    transitions: TransitionHook.propType,
    nav: Navigation.propType,
    contrivedExample: State.propType
  };

  constructor(){
    // the implementation doesn't matter and TransitionHook's component
    // can define its own componentDidMount,
    // and clean up in its componentWillUnmount (if needed)
    this.props.transitions.register({
      routerWillLeave: this.routerWillLeave.bind(this);
    });
  }

  render(){
    const {nav, contrivedExample} = this.props;
    return (
      <div>
        <button onClick={() => nav.goBack()}>Back</button>
        <button className={contrivedExample.isActive('/home') && 'active'}>Home</button>
      </div>
    );
  }

  routerWillLeave(nextState, router){
    // ...
  }
}

And an example implementation:
// dummy propType
State.propType = () => {};

function State(opts, C){
  // trick to allow any of State()(C), State(opts)(C), State(opts, C)
  if (!opts && !C) {
    return State.bind(null, {});
  }

  // pull our prop name out of propTypes
  const {propName = "routerState", restPropTypes} = extractPropType(State.propType, C.propTypes);

  return class StateComponent {
    static propTypes = restPropTypes;

     /* context stuff */

    render(){
        const props = Object.assign({}, this.props, {
          [propName]: {isActive: this.context.router.isActive}
        });
        return <C {...props} />;
    }
  }
}

function extractPropType(value, propTypes){
  const propNames = Object.keys(propTypes);
  const propName = propNames.find((key) => propTypes[key] === value);
  const restPropTypes = blacklist(propTypes, propName);
  return {propName, restPropTypes};
}

@brigand Thank you for staring the discussion here. I haven't personally started using decorators in my code yet, but I'd like to get some in for the 1.0.0 release if they aren't too much work. I think @gaearon should be able to chime in here and comment on your ideas.

There's already some discussion here https://github.com/rackt/react-router/issues/1173

Ah missed that. Thanks.

Thanks @taurose, I had forgotten about that.
@brigand Let's close this and follow up there?

To clarify, decorators are just sugar for function calls. Using decorators to perform mixins is different from high order components (e.g. high order functions don't modify the definition of the function they're passed and then return that function). This is about an alternative to the mixins, not a different way to apply them.
I think it's two separate requests.


Cloud computing update

Describe your changes
Removed proprietary products and added something about public and private cloud as discussed during the maintainer meeting.
Related issue number or link (ex: resolves #issue-number)
Checklist before opening this PR (put x in the checkboxes)

[ x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[ x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

Hmm...I thought that was the conclusion of our last meeting. Instead of adding a VPC term, we reference VPC and public cloud in this entry. I was just implementing our decision. Should we skip it here AND not have a VPC term?
Meeting note: New term suggestion Public Cloud issues/1737 (related with ongoing effort for VPC) → Agreed not to include, and mentioning it in cloud computing term.

Hi @CathPag :)
I thought the conclusion of our last meeting is.. Instead of adding Public cloud as a new term, just adding short description about Public cloud and Private cloud in the existing Cloud computing term so that the VPC term (ongoing work) can reference public cloud from Cloud computing.
I guess we didn't make another decision for the VPC term itself.


New package: Nakala v0.9.2

Registering package: Nakala
Repository: https://github.com/sardinecan/Nakala.jl
Created by: @sardinecan
Version: v0.9.2
Commit: c8007e19648b335c0685a26094cba171ac18fc77
Reviewed by: @sardinecan
Reference: https://github.com/sardinecan/Nakala.jl/issues/9#issuecomment-2358833754
Description: A Julia Package to work with Nakala's API

[noblock] Thank you for submitting your package! Just as a comment: I don't think we have a particular policy about natural languages in the General registry. In principle, I might actually advocate for General having an English-only requirement (and we should have other official registries for other languages). I say this as a non-native speaker (albeit US resident), just based on English being the lingua franca for technology. I don't know… Maybe having things in English is less of an important factor these days, where AI-supported translation is widely available.
On that note. I was having some trouble with having your documentation translated to English by my browser's (Safari's) translate button. I suspect that might be because some of your headings are in English. It might be helpful to make sure that your pages are consistently written in one language, whether it's French or English, and maybe test how it comes out in browser translation.
It would also be helpful to expand your README a little. You could potentially use that as an opportunity to give a summary of your package in English, with a brief usage example, to give a starting point to a wider audience. I generally also recommend putting an explicit link to the full documentation in the README: the link in the About section on Github isn't always as easy to find, and isn't there for people who clone the package and only have the README to look at.

[noblock] Thank @goerz you for your comment and encouragement. I started writing the documentation in English, but for now, Nakala is a service that is only available to engineers and researchers in the humanities and social sciences (HSS) field in France. So I thought it was more appropriate to write it in French. That said, as you suggested, I have added an English presentation to the README file.
Unfortunately, the French to English translation is quite poor (I tried with Firefox), not to say disastrous... However, regarding the titles, there's not much I can do, as they correspond to the endpoints of the Nakala API, and for the sake of clarity, I kept the same names for the package modules. Nevertheless, I will look into providing a complete english translation of the documentation.


thiscall_t is broken.

Using thiscall_t results in code that will not compile.
The definition produced by the function_signature template is:
(__thiscall)()
Which is not legal, even when only used as
(__thiscall*)()

Triaged, this is an issue only with MSVC.
Clang and GCC continue to compile without issue.

This appears resolved as of at least Visual Studio 17.8.3

Temporary fix in-place with https://github.com/SubstituteR/MoarPtr/commit/9d82a52ef84550d8066f24fb8d71933e0e7f6abb


Pending at Acceptor

I found some time today to revisit https://github.com/seanmonstar/warp/pull/431 and finally think I understood the issue.
SSCCE:
use futures::ready;
use hyper::{
    server::{
        accept::Accept,
        conn::{AddrIncoming, AddrStream},
    },
    service::{make_service_fn, service_fn},
    Body, Response, Server,
};
use std::{
    io::Error,
    net::SocketAddr,
    pin::Pin,
    str::FromStr,
    task::{Context, Poll},
};

#[tokio::main]
async fn main() {
    let incoming = Acceptor::new(
        AddrIncoming::bind(&SocketAddr::from_str("<IP_ADDRESS>:8000").unwrap()).unwrap(),
    );

    let make_svc = make_service_fn(|_| async {
        Ok::<_, Error>(service_fn(|_| async {
            Ok::<_, Error>(Response::new(Body::from("Hello World")))
        }))
    });

    Server::builder(incoming).serve(make_svc).await.unwrap();
}

struct Acceptor {
    incoming: AddrIncoming,
    pended: bool,
}

impl Acceptor {
    fn new(incoming: AddrIncoming) -> Self {
        Self {
            incoming,
            pended: false,
        }
    }
}

impl Accept for Acceptor {
    type Conn = AddrStream;
    type Error = Error;

    fn poll_accept(
        self: Pin<&mut Self>,
        cx: &mut Context<'_>,
    ) -> Poll<Option<Result<Self::Conn, Self::Error>>> {
        let pin = self.get_mut();
        if pin.pended {
            println!("already pended!");
            match ready!(Pin::new(&mut pin.incoming).poll_accept(cx)) {
                Some(Ok(sock)) => Poll::Ready(Some(Ok(sock))),
                Some(Err(e)) => Poll::Ready(Some(Err(e))),
                None => Poll::Ready(None),
            }
        } else {
            println!("pended once!");
            pin.pended = true;
            Poll::Pending
        }
    }
}

So as far as I understood, returning Poll::Pending from Accept::poll_accept isn't handled or I'm not handling it properly.

The acceptor is responsible for arranging for its task to be woken (via Context::waker) at the appropriate time.

Alright, so if I understand correctly, the issue I was having in https://github.com/seanmonstar/warp/pull/431 was because poll_peek doesn't arrange the task to be awoken?

The issue in your example above is that the else branch does not arrange the task to be awoken.

Thank you so much.
To explain the context I was referring to:
fn poll_accept(
        self: Pin<&mut Self>,
        cx: &mut Context<'_>,
    ) -> Poll<Option<Result<Self::Conn, Self::Error>>> {
        let pin = self.get_mut();
        match ready!(Pin::new(&mut pin.incoming).poll_accept(cx)) {
            Some(Ok(mut sock)) => {
                let mut byte = [0];
                // `poll_peek` doesn't arrange the task to be awoken again
                // therefore on `Poll::Pending` this will never awaken again
                ready!(sock.poll_peek(cx, &mut byte))?;
                Poll::Ready(Some(Ok(sock)))
            }
            Some(Err(e)) => Poll::Ready(Some(Err(e))),
            None => Poll::Ready(None),
        }
    }

So basically my question is how do I arrange the task to be awoken properly when trying to use poll_peek. I was looking through the code and found this: https://docs.rs/tokio/0.2.20/src/tokio/net/tcp/stream.rs.html#270-289.
Which tells me that poll_peek should work appropriately.
So unless I did something else wrong up there, there is some bug in tokio/mio that prevents this example from working?
I will close this because it seems there is no issue with hyper and this has become a "help me" thread instead.

If the socket does not immediately have a byte available to peek, that code throws it away and tries to accept a new connection.

Thanks.
I think I finally narrowed it down.
In https://github.com/seanmonstar/warp/pull/431 I fixed the problem of not throwing away the socket and trying to accept a new connection, but the problem was when the client would come back with a HTTPS connection I already gave away the socket to handle the upgrade.
So I guess this PR is gonna have to involve some more work.
Thank you so much again.


Sign and verify offchain message packets.

Messages between two dst node (offchain communication) are currently sent and received as plain text json.
In order to to ensure the authenticity and integrity of the messages, a signature needs to be generated before sending it and should also be verified upon reception.This mechanism needs to be implemented in the read and write functions in channel module.
Additional information :

Onchain keys can be used for signing as they will available and accessible by dst software.
Functions for signing and verifying that are defined in the identity module can be reused.
See creation and verification of states for an example of how to use these functions.

Issue closed, as it relates to the older implementation which is now archived on legacy/master


Feature - admin-theme - rtl and ltr - Calendar control in publish later part doesnt show selected year and month correctly

This issue appears on workflow edit page in admin-theme in publish later part.
Can't see the selected month and year.

Fixed


GEODE-3129 - Added error messages to protobuf protocol

added a new ErrorResponse type to ClientProtocol
removed success field from several RegionAPI response objects and refactored operation handlers to instead return ErrorResponses
made all op handlers take ClientProtocol.Requests and return ClientProtocol.Responses instead of operation specific types
moved the protobuf specific response building code from operation handlers to ProtobufResponseUtilities
moved the request building functions from MessageUtil (under Test) to ProtobufRequestUtilities
moved all utility classes to ...protocol.protobuf.utilities and added javadoc comments throughout
changed GetRegions to GetRegionNames, returns strings instead of Regions
replaced logging through the cache's LogWriter with log4j logging
updated all imports to be in the correct order for the new geode style guide
Signed-off-by: Brian Rowe<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

This was opened for about 90 minutes before it was merged into develop. Was there a review done by a committer on this code?

Yes, there was a PR related to this, but it was deleted and then this one created. In addition, there is/was a review in apache reviewboard since Jul,3

Thanks! It was not clear from the history of the pull request.
--Mark