default response for custom adapter

I am building a chatbot and I have created a few custom adapters. my custom adapters inherit from logic adapter class. I am not able to set a default response in case my adapter can't process a statement and in that case, it returns the query itself as a response.
Please help me how can I set a default response for my custom adapters, if it can't process the response.

could you provide your chatbot config?

Here is my chatbot config file -
from chatterbot import ChatBot
import conversation_adapters
import pdb
chatbot = ChatBot(
    "Terminal bot",
    logic_adapters=[{
            "import_path" : "my_custom_adapter.MyCustomAdater1"
        },
        {
            "import_path" : "my_custom_adapter.MyCustomAdater2"
        },
        {
            "import_path" : "my_custom_adapter.MyCustomAdater3"
        }
    ],
    input_adapter="chatterbot.input.TerminalAdapter",
    output_adapter="chatterbot.output.TerminalAdapter"
)

print("Hello I am Terminal bot")

while True:
    try:
        bot_input = chatbot.get_response(None)

    except (KeyboardInterrupt, EOFError, SystemExit):
        break

Here is a sample of my one of custom adapter
from chatterbot.logic import LogicAdapter
from chatterbot.conversation import Statement
import location_details
import random
import pdb

class MyCustomAdapter1(LogicAdapter):

	def __init__(self, **kwargs):
		super().__init__(**kwargs)

	def can_process(self, statement):

		words = ["Hello", "Hi", "Hey" ]
		if any(word in statement.text.lower().split() for word in words):
			return True
		else:
			return False

	def process(self, statement):
		responses = ["Hello", "Hi there!", "How are you"]
		confidence = 1
		response_statement = (Statement(random.choice(responses)))
		return confidence, response_statement

I didn't find any issue with your logic, may you could try with enabling logging to see how chatterbot is selecting logic functions
https://github.com/gunthercox/ChatterBot/blob/dc1af906d1e34884deddd4857cc7947fa5257697/examples/terminal_example.py#L7

I tried that. NoConfidenceAdapter selects the response. This is what i got in verbose logs
skldjflksd
INFO:chatterbot.adapters:Received input statement: skldjflksd
INFO:chatterbot.adapters:"skldjflksd" is not a known statement
INFO:chatterbot.adapters:Not processing the statement using CustomAdapter1
INFO:chatterbot.adapters:Not processing the statement using CustomAdapter2
INFO:chatterbot.adapters:Not processing the statement using CustomAdapter3
INFO:chatterbot.adapters:NoKnowledgeAdapter selected "skldjflksd" as a response with a confidence of 0
skldjflksd

Instead of it I want to get a default response "I am sorry but I did not understand that."
Is there a way I can handle this. I tried with lowconfidence adapter, but in that case, it always returns "I am sorry but I did not understand that." as a response even though my custom adapters are able to process the statement.
This is the verbose logs when I use lowconfidence adapter
INFO:chatterbot.adapters:Received input statement: Hello
INFO:chatterbot.adapters:"Hello" is a known statement
INFO:chatterbot.adapters:Not processing the statement using CustomAdapter1
INFO:chatterbot.adapters:CustomAdapter2 selected "Hello" as a response with a confidence of 0
INFO:chatterbot.adapters:Not processing the statement using CustomAdapter3
INFO:chatterbot.adapters:LowConfidenceAdapter selected "I am sorry, but I do not understand." as a response with a confidence of 0
INFO:chatterbot.adapters:NoKnowledgeAdapter selected "Hello" as a response with a confidence of 0
INFO:chatterbot.chatterbot:Adding "Hello" as a response to "I am sorry, but I do not understand."

I am not getting how can I handle this.

You could write like this
from chatterbot import ChatBot
import my_custom_adapter
import pdb
chatbot = ChatBot(
    "Terminal bot",
    logic_adapters=[{
            "import_path" : "my_custom_adapter.MyCustomAdater1"
        },
        {
            "import_path" : "my_custom_adapter.MyCustomAdater2"
        },
        {
            "import_path" : "my_custom_adapter.MyCustomAdater3"
        }
    ]
)

print("Hello I am Terminal bot")

while True:
    try:
        input_text = input("Enter your name: ")   # Python 3 builtlin function read input from standard input stream
        response = chatbot.get_response(input_text)
        if response.confidence == 0:
            print("I am sorry, but I do not understand.")

    except (KeyboardInterrupt, EOFError, SystemExit):
        break

No that didn't seem to work. Even my adapter is returning confidence as 1. when I do response.confidence it's always 0.

I didn't understand your statements

when I do response.confidence it's always 0.

What i understood above statements response.confidences is always "0" then your problem solved right?

What I meant was, if my adapter able to process the statement, it should return confidence as 1. But I am getting it 0. I have checked in logs, it says
CustomAdapter2 selected "Hello" as a response with a confidence of 1
But I am getting 0 when I do response.confidence for a valid statement. I don't understand where I am going wrong.

Thanks, @vkosuri for the help.

@vkosuri I have one more doubt. Say two of my adapters are able to process the statement and they both return the response with confidence 1. In such case, chatterbot picks up a random response and returns it. What I want is return all the responses in such case. I looked at custom output adapter documentation but it's not clear. Can you tell me if that's possible with the chatterbot. If yes how can I do that?

@sinscary I am not sure, may be you could overwrite your selected logic adapter process method.
For example if you are using best match adapter, https://github.com/gunthercox/ChatterBot/blob/c777b98d51d413c8fa662cdee90476ffdcb2cd5e/chatterbot/adapters/logic/base_match.py#L5
over ride process methods what origianl method going to return https://github.com/gunthercox/ChatterBot/blob/c777b98d51d413c8fa662cdee90476ffdcb2cd5e/chatterbot/adapters/logic/base_match.py#L71


Token tweaks

Description:

Return 401 when camera/media player not found and no auth provided
Use more secure random number for camera and media player album art access tokens
Re-generate access token for camera's every 5 minutes
For camera's, current and previous auth token are valid.

🐬


RuntimeError: The second supplied array does not contain any binary object.

Traceback (most recent call last):
File "evaluate_patients.py", line 400, in
metrics_acdc.main(path_gt, path_pred, path_eval)
File "/home/sivajyothi/acdc_segmenter/metrics_acdc.py", line 312, in main
df = compute_metrics_on_directories_raw(path_gt, path_pred)
File "/home/sivajyothi/acdc_segmenter/metrics_acdc.py", line 109, in compute_metrics_on_directories_raw
hausdorff_list.append(hd(gt_binary, pred_binary, voxelspacing=zooms, connectivity=1))
File "/home/sivajyothi/acdc_segmenter/src/medpy/medpy/metric/binary.py", line 348, in hd
hd1 = __surface_distances(result, reference, voxelspacing, connectivity).max()
File "/home/sivajyothi/acdc_segmenter/src/medpy/medpy/metric/binary.py", line 1166, in __surface_distances
raise RuntimeError('The second supplied array does not contain any binary object.')
RuntimeError: The second supplied array does not contain any binary object.
I'm getting this error while evaluating the model.
As mentioned in the previous issue i reinstalled matplotlib, but i'm getting this error. Can you please help me to resolve this issue???

This probably does not have to do with the model, since it seems your problem comes from the fact that it asks you for binary data and you may be giving it, multi-class data maybe?

It is because the hausdorff metric. One of the mask your model predict is maybe all zero.


Problem using the new reference CHM13

I'm trying to use the reference chm13 to visualize the short arm of chromosome 14, but it gives me this error:
Error in `genome<-`(`*tmp*`, value = "hs1") :
  Failed to set session genome to 'hs1'

This is my code:
library(Gviz)
ideoTrack <- IdeogramTrack(genome = "hs1", chromosome = "chr14")
plotTracks(ideoTrack, from = 1, to = 11400261)

Could you please help me?

HI @sara77777777,
It is related to rtracklayer bug: https://github.com/lawremi/rtracklayer/issues/84 It needs to be fixed there.


UX for API rate limit exceeded

Bug report
Describe the bug
I busted through Github's API rate limits while testing the organizations' star history feature, will be good to show a toast for such an error and the corresponding UI state across the pages.
Resolving https://github.com/supabase/repository.surf/issues/33 should mitigate the issue of busting rate limits too

Sounds good.
Also, ideally, I think we should have a queue of GitHub API requests to make.
So hypothetically, if we want to show the total star chart for Google (~1.3 million total stars), the data will be ready in a few hours. Once it's cached in SB, refreshing it is going to be much cheaper.

Sounds good.
Also, ideally, I think we should have a queue of GitHub API requests to make.
So hypothetically, if we want to show the total star chart for Google (~1.3 million total stars), the data will be ready in a few hours. Once it's cached in SB, refreshing it is going to be much cheaper.

Related issue: #71

Related issue: #71

Related: https://github.com/supabase/repository.surf/issues/90

Related: https://github.com/supabase/repository.surf/issues/90


Update harness-git-ops-agent-with-self-signed-certificates.md to add steps for mounting certs with Helm

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66aa7b713c8aca06200c53b7--harness-developer.netlify.app


Vulnerability roundup 111: qemu-6.1.0: 1 advisory [6.5]

search, files

[ ] CVE-2021-4145 CVSSv3=6.5 (nixos-21.11, nixos-unstable)

CVE details
CVE-2021-4145
A NULL pointer dereference issue was found in the block mirror layer of QEMU in versions prior to 6.2.0. The self pointer is dereferenced in mirror_wait_on_conflicts() without ensuring that it's not NULL. A malicious unprivileged user within the guest could use this flaw to crash the QEMU process on the host when writing data reaches the threshold of mirroring node.

Scanned versions: nixos-21.11: 2128d0aa28e; nixos-unstable: 5aaed40d22f.
Cc @alyssais
Cc @edolstra

This is fixed on master since we have QEMU 6.2.0.  It's not included in 6.1.1 though, so needs to be fixed on stable. Probably after we have 6.1.1 since it'd be a merge conflict.


pulseview,pavucontrol-qt: use qt5.mkDerivation

Motivation for this change
I've noticed both of these apps don't start anymore due to missing Qt plugin path.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

(@ttuegel)

@ttuegel Would it be possible to open a tracking issue so people to explain to people how then can easily migrate to the qt wrappers?
The influx of PRs like this is going to be large, so it would be easy to track if each one opened would reference that single issue also.

Addressed both comments.

I'm now a bit confused whether expressions should use the qt5 package set directly or not, see https://github.com/NixOS/nixpkgs/issues/65399#issuecomment-515379765.
But anyway, please split the commit in two, one for each package you're updating.

No more confusion, this is how to do it: https://github.com/NixOS/nixpkgs/issues/65399#issuecomment-515464616.

We should never use qt* directly.

@bjornfor said 3 weeks ago:
But anyway, please split the commit in two, one for each package you're updating.

In the meantime I merged https://github.com/NixOS/nixpkgs/pull/66869, since it had pulseview/single package as a separate commit. Please rebase.


Support for Windowing

As a developer I'd like to have an event time based windowing functionality. See here for details on what Beam currently supports.

Please note that for now this only applies to the only non-streaming step we currently have: Merge Join.
Because of this, I suggest to define the windowing function on the Beam Job Config level:
One of:

Fixed-time window
Sliding time window
Session window
Single global window

see; https://beam.apache.org/documentation/programming-guide/#setting-your-pcollections-windowing-function

I was more thinking about having a dedicated step for this.
If I had to define it on the job level, at which stage would that windowing function be applied? As the last step before writing out the data?

I guess indeed a step is even easier.


Functionality of add a guest page

Pull the information from the form and send it to the server via ajax POST request. Create server route to insert into the database. Add functionality to cancel button by adding a link to the guest details page.

Pull request #45  partially resolved this. It pulled most of the information from the form, but the checkbox needs to be modified. It an AJAX request to post a new guest. Server route is incomplete. Cancel button incomplete.

Created new issue for checkbox issue. Issue #46.

Add functionality to cancel button on add a guest form to lead back to the details page has it's own issue. Issue #47


Collector: revisit Deployment and Distribution pages

PR #1332 introduced a Deployment page, which doesn't really talk about deployment (i.e., "how to deploy") but rather possible runtime configurations. Consider renaming the page and/or consolidating it with ** Distributions**. Maybe the latter can be folded into the Collector landing page.
Thoughts @svrnm @cartermp @austinlparker?

I think it is fine to keep it as-is for now. These are about deployment models/strategies. I think we can extend the page over time to have specific guides, but for now it is helpful to describe the concepts.

+1 for "keeping it as-is for now"
+1 for extending. I thought about this a little bit: this could be an incredible helpful page with a deep dive on this topic. Many people do not see all the potential you have with the collector and  I also have people internally asking question about the collector, how to deploy it beyond the basics, etc.
A potential structure:

Calling out once again the flexibility of the collector and linking back to some basic pages (collector concepts, OTLP, ...).
Maybe some "basics"/"theory" on deployment (collectors can be chained, there can be LBs and other things between you and the collector, using operators etc for rolling them out)
"0-collector" deployment, go a little bit more into details when you can use no collector, what advantages you have with that model and when you should consider having a collector. It would be the advanced version of what we have discussed a while back on "why otel collector" with @cartermp.
agent mode collector
gateway collector
...

For the "..." I was thinking about the work @jpkrohling was doing with his talk on deployment models (This is my go to material when people ask me):

https://www.youtube.com/watch?v=WhRrwSHDBFs
https://github.com/jpkrohling/opentelemetry-collector-deployment-patterns/)
(Of course only if @jpkrohling is OK with that, we also can link there from the docs)

Sorry for the silence on this and other related PRs/issues, I've been AFK for a couple of months and have just returned. I'll review what we currently have and provide my feedback here later this week. If I don't, feel free to ping me directly.

If desired, we can create issues for the individual points.

👍 -- we should do that, maybe group them by page.

[ ]  The Deployment modes page needs some rewording: we don't use the term "Gateway" anywhere else and I think it causes more confusion than clarification.
[ ]   There's no different binary nor difference in the configuration between the modes, so it may confuse users. We should either clarify that or remove the notion of "deployment modes" altogether. Perhaps the earlier suggestion on expanding the page to have "patterns" instead would be a good replacement.

I forked the Deployment page out because of the confusion it creates and it also significantly downplays the things you can do with the collector (by chaining them, etc.), so I am all in for redoing it towards a "patterns" page.

[ ]  The "Getting Started" starts by requiring people to read two other pages. One of them refers them back to the Getting Started page. I would prefer to have the getting started as the first thing users might read, making a brief explanation on what the collector is and how it fits the big picture.
[ ]  In the Getting Started, we should guide users in configuring and running the collector, instead of telling them to just run a docker compose and referring them to the repository. We might still use docker compose to start other things, like Prometheus, Jaeger, and the load generator.
[ ]  Everything else on the Getting Started page could go to other sub pages. For instance, running the collector on Kubernetes does not belong to the Getting Started.

That's a good point! If we compare the Getting Started page of the collector with the individual languages, it's a very different experience, it's just about different ways of installing it vs "here's a 30 minutes tutorial on how to get things up and running". @cartermp and I just touched upon that topic with PHP that most of the language guides have or should have a quick "here's how you setup a collector", e.g. python has it: https://opentelemetry.io/docs/instrumentation/python/getting-started/#configure-and-run-a-local-collector
So yes, moving everything out into a "Installation"(?) page and reducing the Getting Started to such a tutorial would be great.

[ ]  Perhaps the Distributions page should be joined with the "Build a custom collector". It should also say a few words about vendor-specific distributions.

We have a "Distributions" page in concepts & for the collector, not sure if/how they can be merged or connected.

[ ]  The "building a custom collector" page needs some love. The main use case isn't to allow people to run a code within their favorite Go IDE, although that's a good side effect. Also, chmod 777 is never a solution. This page also states a specific version as the latest, which is of course outdated by now.

cc: @rquedas

[ ]  Building a Custom Authenticator refers to client authenticator interfaces that have been removed and replaced with https://pkg.go.dev/go.opentelemetry.io/collector/config/configauth#ClientAuthenticator .

cc: @pavankrish123

[ ]  Building a Trace Receiver should probably be renamed to "Building a component". I would assume that a "trace receiver" is just an example of the component to be built. Readers can then expand from the example to build other components, like extensions or exporters.
[ ]  The config seems to use Jaeger gRPC port, but the Docker command doesn't export this port. It does export the HTTP one though.
[ ]  The guide seems to be using the first person, which doesn't seem consistent with the other pages

cc: @rquedas

@jpkrohling I think all those todos are great, I bubbled them up to be their own issues so we can close this one and have them visibile.


METROL-213: Enable monitored plugins when built from external repositories

Previously the monitored plugins were enabled autmatically when the
plugin was enabled. However due to split of plugins betweeen
ThunderNanoServices and RDKServices, some of the plugins resides in
different repository, thus cannot be autmatically enabled.
This commit introduces the possibility to automatically monitor
plugins that are built within this repository and manually enable
plugins that are outside of this repository.

Added a Jira ticket
Rebased against sprint/2101

Please review

Added a Jira ticket
Rebased against sprint/2101

Please review

Configuration has been added to the Buildroot buildsystem.
https://github.com/WebPlatformForEmbedded/buildroot/pull/285

Configuration has been added to the Buildroot buildsystem.
https://github.com/WebPlatformForEmbedded/buildroot/pull/285


MPIJobs and Istio

I tried to run some MPIJobs with Istio enabled in the user namespaces but have bumped into a couple of issues. I'll use this issue to expose the bugs that occurred as well as proposed solutions. Although we might need to break this into smaller issues.
I used the tensorflow-benchmarks example, so this will be my point of reference.
The problems we've observed are the following:

The main container will need to wait for the sidecar to start

We can use Istio's proxy.istio.io/config: '{"holdApplicationUntilProxyStarts": true}' annotation on the pods

Workers communicate with the Launcher Pod via Pod IPs, which goes through Istio's PassthroughCluster. This could be a problem in more security strict environments where mTLS mode is STRICT (pod-to-pod is not mTLS so requests will be blocked)

https://istio.io/latest/docs/ops/configuration/traffic-management/traffic-routing/#headless-services
https://istio.io/latest/docs/ops/configuration/traffic-management/traffic-routing/#unmatched-traffic

The Launcher will use kubectl exec which can use the sidecar

We could extend the controller to set the kubectl.kubernetes.io/default-container annotation in the worker pods

Apologies if there were duplicate issues for Istio and MPIJob. Are there any plans for mitigating some of these issues and ensuring MPIJob can work with Istio?
Also if I need to open this issue in kubeflow/training-operator please tell me and I'll open a new one.

cc @terrytangyuan @johnugeorge @alculquicondor @gaocegege

/cc @zw0610

/lifecycle frozen


Improve error/warning messages for SusieFineMapper

Background
Currently finemapping of a loci can fail for a variety of reasons, but the current implementation will often only raise an error when it reaches, and fails, the stage of extracting the numpy array from the block matrix. This means it isn't immediately clear whether the cause of the issue is the sumstats or the LD index.
Tasks

[ ] add error/warning messages for common issues

https://github.com/opentargets/gentropy/pull/764


Bug upload is not working

Steps:

git clone ... && node server
open localhost:8000 in a browser
write upload
select a file
get an error in the server console
empty file at the application/resources folder

Server console:
8:53  W2   log     <IP_ADDRESS>        files/upload
13:58:53  W2   error   <IP_ADDRESS>        GET     /api    400     400     Error: Stream -2097281614 is not initialized
  WsChannel.binary (/node_modules/metacom/lib/channel.js:159:23)
  WebSocket.<anonymous> (/node_modules/metacom/lib/ws.js:10:26)
  WebSocket.emit (node:events:390:28)
  Receiver.receiverOnMessage (/node_modules/ws/lib/websocket.js:1180:20)
  Receiver.emit (node:events:390:28)
  Receiver.dataMessage (/node_modules/ws/lib/receiver.js:526:14)
  Receiver.getData (/node_modules/ws/lib/receiver.js:459:17)
  Receiver.startLoop (/node_modules/ws/lib/receiver.js:158:22)
  Receiver._write (/node_modules/ws/lib/receiver.js:84:10)
  writeOrBuffer (node:internal/streams/writable:389:12)
13:58:54  W1   debug   Reload: /resources/icon.svg
13:58:57  W2   debug   Heap: 11 Mb of 12 Mb, ext: 2 Mb
13:58:57  W3   debug   Heap: 10 Mb of 12 Mb, ext: 2 Mb
13:58:57  W2   debug   Contexts: 5, detached: 0
13:58:57  W3   debug   Contexts: 5, detached: 0
13:58:57  W5   debug   Heap: 10 Mb of 12 Mb, ext: 2 Mb
13:58:57  W5   debug   Contexts: 5, detached: 0
13:58:57  W1   debug   Heap: 10 Mb of 12 Mb, ext: 2 Mb
13:58:57  W1   debug   Contexts: 5, detached: 0
13:58:57  W4   debug   Heap: 10 Mb of 12 Mb, ext: 2 Mb
13:58:57  W4   debug   Contexts: 5, detached: 0

Env:
(base) ➜ Example git:(master) ✗ node -v
npmv16.13.0
(base) ➜ Example git:(master) ✗ npm -v
8.1.0

ws client:
{"stream":1,"name":"icon.svg","size":1454}
{"call":5,"files/upload":{"streamId":1,"name":"icon.svg"}}
Binary Message
{"stream":1,"status":"end"}
{"callback":-2097281614,"error":{"message":"Stream -2097281614 is not initialized","code":400}}

Workaround:
/node_modules/metacom/lib/server.js
45: this.ws.on('connection', (connection, req) => {
46:      connection.binaryType = 'arraybuffer';

/node_modules/metacom/lib/client.js
 22+: this.socket.binaryType = 'arraybuffer';

/node_modules/metacom/lib/streams.js
29:  static decode(arrayBuffer) {
30:    const chunkView = new Uint8Array(arrayBuffer);

As of today the issue is still exists but not on a server side. Workaround from above is outdated due to massive changes in metacom. Currently the issue in client side code at this repository:
https://github.com/metarhia/Example/blob/2435b8e643af3fc4a62fea1f3f20bdedc1e1d9c1/application/static/console.js#L187-L193
streamId isn't exists in return contract of application.metacom.createBlobUploader from
https://github.com/metarhia/Example/blob/2435b8e643af3fc4a62fea1f3f20bdedc1e1d9c1/application/static/metacom.js#L74-L75
Current state at the metacom repository is the same https://github.com/metarhia/metacom/blob/acb90a6d8cb358fe1db9e28cec8f9b4a8107cffc/dist/metacom.js#L76-L77


I'm glad my hard work didn't go unnoticed, hah, thanks.
I think bug is happen in dcb2243 commit, because excalidraw images IS "app://...", but not "app://local..."

I also fixed another bug in there #41 . It's such a simple solution, but it's not easy.....


Revert "Migrate core devicelab framework to null safety."

Reverts flutter/flutter#85993
There were a bunch of benchmark failures with this, so I need to sort that out before we can land this.

Left comment with fix on the original commit, #85993


Build scala separately on Travis.

Travis CI often kills the build during the querydsl-scala tests
because it's out of memory (error code 137).

Looks good

It looks good to merge, waiting for last input of my question.
It's not necessary, but just asking.


Update django slugify url

Incorrect url noted in https://github.com/django-extensions/django-extensions/issues/1099#issuecomment-867069345=

It's not the incorrect URL. One of them is the function and the other one is the template tag. The doc refers to the function.


Performance: avoid loading expensive modules until needed

We were loading adal and requests without actually needing any functionality from them in some scenarios.
This PR refactors the Profile class to delay load those particular modules.
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[N/A] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[N/A] Each command and parameter has a meaningful description.
[N/A] Each new command has a test.

(see Authoring Command Modules)

Codecov Report

Merging #2871 into master will decrease coverage by <.01%.
The diff coverage is 75.86%.

@@            Coverage Diff             @@
##           master    #2871      +/-   ##
==========================================
- Coverage   63.17%   63.17%   -0.01%
==========================================
  Files         466      466
  Lines       26139    26149      +10
  Branches     3997     3998       +1
==========================================
+ Hits        16514    16520       +6
- Misses       8544     8547       +3
- Partials     1081     1082       +1

Impacted Files
Coverage Δ

src/azure-cli-core/azure/cli/core/telemetry.py
54.1% <0%> (ø)
:arrow_up:

src/azure-cli-core/azure/cli/core/_profile.py
84.47% <78.57%> (-0.67%)
:arrow_down:

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 3f4409b...dce8f81. Read the comment docs.


indent option on breakable

This commit adds the ability to toggle whether or not a Breakable will
indent when it is printed. In order to achieve this, we delay pushing
anything into the output buffer until flush is called. When it is
called, we iterate through the doc nodes and check at each step if they
fit into the current line (as we did before). Now, however, when a
Breakable is printed, it checks if it should indent itself or not.
These changes open the door for many more changes that can be
accomplished now that printing is delayed until flush is called. Because
of the delay:

nodes in the doc tree can now change their representation depending on
whether or not the current group is broken
we can force all parent groups to break up the tree, instead of just
the current group. This will allow all of the nodes up the tree to
break and change their representation as well
by passing the indent level through the tree as its being printed
instead of keeping a single variable around, we can more tightly
control indentation level as the tree is printed.

Thanks @tenderlove I've updated from your feedback.


Failure to read config file from .github/workflows/

Environment details

OS: Same as specified in https://github.com/google-github-actions/release-please-action/releases/tag/v3.7.11
Node.js version: Same as specified in https://github.com/google-github-actions/release-please-action/releases/tag/v3.7.11
npm version: Same as specified in https://github.com/google-github-actions/release-please-action/releases/tag/v3.7.11
release-please version: Same as specified in https://github.com/google-github-actions/release-please-action/releases/tag/v3.7.11

Steps to reproduce

Create a workflow file which uses the release-please action

on:
    push:
        branches:
            - main
    workflow_dispatch:

permissions:
    contents: write
    pull-requests: write

name: release-please

jobs:
    release-please:
        runs-on: ubuntu-latest
        steps:
            - uses: google-github-actions/release-please-action@v3
              with:
                  command: manifest
                  config-file: .github/workflows/config/release-please-config.json
                  manifest-file: .github/workflows/config/.release-please-manifest.json

Set the config-file and manifest-file to locations inside of the .github/workflows directory
Trigger the action
Observe the action logs:

Run google-github-actions/release-please-action@v3
  with:
    command: manifest
    config-file: .github/workflows/config/release-please-config.json
    manifest-file: .github/workflows/config/.release-please-manifest.json
    token: ***
    fork: false
    clean: true
    bump-minor-pre-major: false
    bump-patch-for-minor-pre-major: false
    changelog-host: https://github.com/
    github-api-url: https://api.github.com/
    github-graphql-url: https://api.github.com/graphql
    monorepo-tags: false
❯ Fetching .github/workflows/config/release-please-config.json from branch main
❯ Fetching .github/workflows/config/.release-please-manifest.json from branch main
✔ Building releases
...
✔ updating from 0.1.1 to 0.1.1
⚠ file changelog.json did not exist
❯ Fetching changelog.json from branch main
❯ Fetching .github/workflows/config/.release-please-manifest.json from branch main
✔ Starting GitHub PR workflow...
✔ Successfully found branch HEAD sha "cd7f677660dbeeef4e44311bb16bf820477cdcc1".
✔ Successfully created branch at https://api.github.com/repos/elijaholmos/ci-cd-playground/git/refs/heads/release-please--branches--main--components--test
✔ Got the latest commit tree
Error: release-please failed: Error adding to tree: cd7f677660dbeeef4e44311bb16bf820477cdcc1

This error goes away if I relocate the config files to any directory outside of the .github/workflows directory.
For more information, view this repo.

This is likely because the .github/workflows directory has additional required permissions in order to make changes to the files. We don't recommend putting the manifest file there.

I got a similar error. I wanted to version my github reusable workflows separately. Is it possible to do so?
    ".github/workflows": {
      "release-type": "simple",
      "package-name": "workflows"
    },


Nim support

Check for existing issues

[X] Completed

Language
Nim
Tree Sitter parser link
No response
Language server link
https://github.com/PMunch/nimlsp
Misc notes
No response

What needs to be done to get this over the line and  how can I help?


BIGTOP-1983. Move BigPetStore data generator to bigtop-data-generators

BIGTOP-1983. Move BigPetStore data generator to bigtop-data-generators

+1 .. i think this is just a pure mv operation.

Don't have GitHub permissions, so I merged manually.


touch no-file/ fails with a sub optimal error

$ touch no-file/
touch: cannot touch 'no-file/': Other

GNU:
$ touch no-file/
touch: setting times of 'no-file/': No such file or directory

We should probably mix the two and have
touch: cannot touch 'no-file/': No such file or directory

The code is in:
https://github.com/uutils/coreutils/blob/1bb23cdf73f22a10d534293cb36d8960930fbac3/src/uu/touch/src/touch.rs#L88
@miDeb Any idea how to implement that? thanks :)

The current uutils behaviour is:
touch: cannot touch 'no-file/': Is a directory

not great either :)

May I give this a shot?

Yeah, go ahead!

I checked out main and ran cargo run touch no-file/ and got
touch: cannot touch 'no-file/': No such file or directory

It seems this issue has been already addressed in https://github.com/uutils/coreutils/pull/2408. The code that handled this was later removed in https://github.com/uutils/coreutils/commit/0cfaaeceda67947f98c938b69c6c7d2f2064cc83#diff-9565d8fad7b29837b3b468a61a809dc187fb351a72421ffe4b7c4879a8445b27R85 but the test from the PR is still in place and is passing.
@tertsdiepraam

The current uutils behaviour is: touch: cannot touch 'no-file/': Is a directory

How (platform, version of uutils) are you getting this behaviour? I couldn't reproduce it (macos, built from main).

Maybe it depends on whether or not no-file/ exists as a directory? I.e. before and after mkdir no-file

@tertsdiepraam I did try these scenarios and they all seem to behave as expected:
$ touch non-existent
# no output, creates a file named "non-existent"

$ touch non-existent/
touch: cannot touch 'non-existent/': No such file or directory

$ touch existing-dir
# no output, touches the dir

$ touch existing-dir/
# no output, touches the dir

these behaviors are consistent across my default touch implementation (BSD), GNU's and uutils'. Except the slight wording differences: BSD's  leaves out the cannot touch part and GNU's replaces it with setting times of as described in the issue description.

Maybe it depends on whether or not no-file/ exists as a directory? I.e. before and after mkdir no-file

The case when no-file actually exists as directory doesn't and AFAIK shouldn't produce any error at all.
Anyway, the uutils' implementation seems to behave just this issue proposes. Am I missing something?

Very curious, I'm still getting the same result, but maybe it's me who's missing something :) I'm on Linux and on the main branch.
❯ cargo run -- no-file/
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running `/home/terts/Programming/coreutils/target/debug/touch no-file/`
/home/terts/Programming/coreutils/target/debug/touch: cannot touch 'no-file/': Is a directory

Very curious, I'm still getting the same result, but maybe it's me who's missing something :) I'm on Linux and on the main branch.

Curious indeed! Seems like maybe the platform is the culprit here. Gimme some more time to try on linux as well. And also to find out where exactly these messages originate.

The issue appears to originate in this block. The Error returned by File::create is OS-dependent, and so is the message.
On Linux, printing the error gives Os { code: 21, kind: IsADirectory, message: "Is a directory" }
On MacOS, it gives Os { code: 2, kind: NotFound, message: "No such file or directory" }
on Windows, it gives Os { code: 123, kind: InvalidFilename, message: "The filename, directory name, or volume label syntax is incorrect." }
The last part of the error message on each platform appears to be just the message field of the Error (I'm guessing generated by map_err_context, but I'm not 100% sure).

Thanks for investigating this!

(I'm guessing generated by map_err_context, but I'm not 100% sure).

Yes that is correct

It seems to me that there might need to be some custom error message rules around this, since modifying the implementation of map_err_context feel like too broad of a change for this.
I'm thinking something like take the error from line 119 and then write a function that interprets it based on the OS and outputs the appropriate error message. Would that be an acceptable solution?
(Also, I'm not tied to writing this---if @goodhoko still wants to work on this, I would be happy to let them).

I checked GNU to see what they do and where the discrepancy comes from. They do the following:

Open (or create) the file (fd_reopen) and store the error into open_errno
Set the time (fdutimensat) and store the error into utime_errno
If utime_errno != 0 show the error
Else if open_errno != 0 show the error

Hence, if a non-existent directory is given, the creation fails (with Is a directory on Linux) and then the setting of the time fails (with No such file or directory). That last error is then shown and the second ignored. I think this is quite strange behaviour and I might actually prefer Is a directory, though neither option is great. I like Is a directory because it gives the reason why touch hello succeeds, but touch hello/ fails if both don't exist. So maybe we should just leave it like it is?
I agree that we shouldn't change map_err_context for this change and only write a small workaround if we still want this. Modifying the error messages seems finicky, but might be a good option.
@sylvestre, what is your opinion here?

Two quick things to note:

On Windows, the error message is going to be something like touch: cannot touch 'no-such-file/': The filename, directory name, or volume label syntax is incorrect., which seems pretty confusing.
On MacOS, the error is touch: cannot touch 'no-such-file/': No such file or directory, both if you try to touch a non-existent directory and if you try to touch a file in a non-existent directory (e.g. touch no-such-dir/ and touch no-such-dir/no-such-file). On Linux/Windows, the error message is different in these two cases.

I don't know to what extend cross-platform consistency in error messaging is a goal here, but to get MacOS to behave like the other two platforms would require an additional check upon first getting this error.

(Also, I'm not tied to writing this---if @goodhoko still wants to work on this, I would be happy to let them).

Sorry for ghosting this. 🙈  Life dragged me somewhere else. Feel free to take over this.

Hello, I would like to work on this.
@chipbuster Could you tell me what error message has to be shown for an OS? I was thinking of no such file or directory for Mac, Linux & BSD targets.
I'm not sure for Windows as their default error message is confusing.

@chipbuster Could you tell me what error message has to be shown for an OS? I was thinking of no such file or directory for Mac, Linux & BSD targets.

Unfortunately, you're asking the wrong person. My only contribution to this project has been identifying the source of the error strings--my opinion on what the right message should be matters less than yours, if you end up implementing this, and much less than anyone with some actual involvement with this project

Shouldn't this issue be closed due to this PR?

It is still there (linux, debian):
$ coreutils touch no-file/
touch: cannot touch 'no-file/': Is a directory
$ coreutils --help | grep multi
coreutils 0.0.25 (multi-call binary)


[vcpkg bootstrap] build failure

Operating system
Windows 11 Home Single Language
Compiler
Microsoft Visual Studio Community 2022
Steps to reproduce the behavior
1. I clone the git repo from Powershell: `git clone https://github.com/Microsoft/vcpkg.git`
2. I type .\vcpkg\bootstrap-vcpkg.bat and ENTER
3. It show failure log.

Failure logs
Program 'bootstrap-vcpkg.bat' failed to run: Access is deniedAt line:1 char:1
+ .\vcpkg\bootstrap-vcpkg.bat
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ .\vcpkg\bootstrap-vcpkg.bat
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

Additional context
My PS version:
Name                           Value
----                           -----
PSVersion                      5.1.22621.2506
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.2506
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

When I navigate to the folder and run it directly, it shows message box:

Windows cannot access the specified device, path, or file" error when you try to install, update or start a program or file

I have fully adminitrastor permission (since its my personal computer tho)
My only AntiVirus is Window Defender (Win Security) and it totally turn off real time protection, firewall,... i mean i never let it active.
My windows version:

Edition:	Windows 11 Home Single Language
Version:	23H2

I actually do researched many hours for this issue and not found a solution. Any help is approriated, thanks!

Might be because you are using powershell 5. You need powershell 7 for vcpkg bootstrap install.

Might be because you are using powershell 5. You need powershell 7 for vcpkg bootstrap install.

I tried ps7 just now. It stay same.

UPDATE: I reset my computer (removing everything, re log in with my current account - no sync) and it worked. But this just cost too much to reinstall other. So I wonder if any explain to this questions still.

Use cmd instead of PowerShell


SW-17653 | $sArticle.image.description not filled properly on article detail page

Description
Please describe your pull request:

Why is it necessary?
There are two issues (known bugs).
What does it improve?
It makes sure all provided image descriptions are available on the article detail page, even if the article has configurator options
Does it have side effects?
No.

Questions
Answers

BC breaks?
yes

Tests pass?
yes

Related tickets?
Issue 1 Issue 2

How to test?
2 Articles: one with variants and image description, one without variants and image description. Both descriptions must appear.

Hi @danielwolf1, thanks for your help and making Shopware better! Your fix will be included in the next release!


Google Play Store needed?

I tried installing the CWA on my Android smartphone. It did not work properly - it was claiming that I would need to update Play Store services. For sure, I had disabled this service because I have never used Play Store and also don't intend to do so.
For testing purposes (in order to narrow down the issue) I had enabled Play Store services today. The first thing that I was requested to is to log in with my Google account - that I don't have.
Do I really need a Google account, and what good is it?
This raises a serious concern. CWA was developed to keep data protection policies. On the other hand, am I requested to open a Google account and provide my private personal data there?! This would lead any data protection compliance ad absurdum.
Or, did I miss anything?

Hello @okievv,
thanks for reaching out and asking that question. To implement the Exposure Notification API, Google is using the Google Play Services application. Therefore you have to have the Google Play Services in place to be able to use the API in combination with the Corona-Warn app. We do have a FAQ article which summarizes this: https://www.coronawarn.app/de/faq/#googleplay
https://www.coronawarn.app/en/faq/#googleplay
Regarding your question, if you need to have a Google account to use the Google Play Services. This really is a question for Google. You will find a quick description about the Google Play Services in the PlayStore, you can access via your desktop computer: https://play.google.com/store/apps/details?id=com.google.android.gms&hl=de
You can reach out to Google using the speech bubble in the top right corner of the link I shared with you.
Thank you,
LMM
Corona-Warn-App Open Source Team

Hi okievv,
do you still have the problem? Did you read my comment under above link from daimpi?

let me try, I was hiking in the mountains today to escape the weather conditions...

Hi @stevie21 ,
as a desperate action, I had re-enabled to Play Store services on my mobile. First smoke tests did not show any change.
In the meantime, after a couple of days, I have tried to re-install CWA. There was an Android update in the meantime, too, but I don't have any clue whether this was supporting my issue.
When I just tried - I could successfully install CWA without the app complaining about missing Playstore access, and now it seems up and running to me.
Thank you, and all other ones who cared about this.

Hi @okievv,
this sounds good. When i read your first entry, then i can say to you, that we are on a simliar wave.
I also do not want to have a google account, so that my handy is probably a open book for google.
My handy is my private, and should not be open for google or whatsapp etc.
But this must everybody decide for himself. I hope that your CWA will run well now.
kind regards:
stevie21

Hi @okievv,
now i have got the following link from vaubaehn,
[https://www.apkmirror.com/apk/robert-koch-institut/]
who is somehow the supervisor of error:
"Fehler bei Kommunikation mit Google API (39508) #774"
I am involved in this error #774.
This seems to me that we can download next version 1.2.0 cwa apk from there on a supported way of Robert Koch Institut.

Thanks all for your proposals. As mentioned in the FAQ, there is currently no APK delivery planned and you can track wishlist item https://github.com/corona-warn-app/cwa-wishlist/issues/57 for any updates on the subject. To keep the website repo manageable, we'll close the issue accordingly.


feat: added usages link for variables

Current dependencies on/for this PR:

main

PR #129   👈

This comment was auto-generated by Graphite.


Aurora upgrade can not be triggered

Description
I want to upgrade Aurora PostgraSQL version from 12.9 to 14.6.
I updated the terraform script and apply the change, but the terraform hang in "still modifying" status for more than one hour. Check the Aurora status from AWS console and found that the Aurora upgrade doesn't no start at all.

[x] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Module version [Required]: 7.71

Terraform version:  1.4.6

Provider version(s):  provider registry.terraform.io/hashicorp/aws v5.55.0

Reproduction Code [Required]
module "aurora_event_db" {
source = "terraform-aws-modules/rds-aurora/aws"
#create_random_password and allowed_security_groups is not supported in latest version of Terraform module
version = "7.7.1"
name                        = "${var.projectname}-${var.environment}-${var.region}-event-db"
engine                      = "aurora-postgresql"
engine_version              = "14.6"
allow_major_version_upgrade = true
auto_minor_version_upgrade  = false
preferred_maintenance_window = "mon:04:00-mon:05:00"
preferred_backup_window      = "00:00-01:00"
backup_retention_period      = 30
kms_key_id                   = aws_kms_external_key.event_db_key.arn
deletion_protection = true
instance_class = var.environment == "prod" ? "db.t3.large" : "db.t3.medium"
instances = {
event_1 = {
identifier        = "${var.projectname}-${var.environment}-${var.region}-event-db-1"
availability_zone = data.aws_subnet.az1.availability_zone
}
event_2 = {
identifier        = "${var.projectname}-${var.environment}-${var.region}-event-db-2"
availability_zone = data.aws_subnet.az2.availability_zone
}
event_3 = {
identifier        = "${var.projectname}-${var.environment}-${var.region}-event-db-3"
availability_zone = data.aws_subnet.az3.availability_zone
}
}
vpc_id                 = data.aws_vpc.default.id
db_subnet_group_name   = "${var.projectname}-${var.environment}-${var.region}-event-db"
create_db_subnet_group = true
subnets = [
data.aws_subnet.az1.id,
data.aws_subnet.az2.id,
data.aws_subnet.az3.id
]
create_security_group               = true
allowed_security_groups             = [data.aws_security_group.compute.id]
iam_database_authentication_enabled = true
master_username                     = local.credentials.role_name
master_password                     = local.credentials.password
create_random_password              = false
apply_immediately = true
create_db_cluster_parameter_group = true
db_cluster_parameter_group_name   = "${var.projectname}-${var.environment}-${var.region}-event-db-14"
db_cluster_parameter_group_family = "aurora-postgresql14"
db_cluster_parameter_group_parameters = [
{
name         = "log_min_duration_statement"
value        = 4000
apply_method = "immediate"
}, {
name         = "rds.force_ssl"
value        = 1
apply_method = "immediate"
}
]
create_db_parameter_group                  = true
db_parameter_group_name                    = "${var.projectname}-${var.environment}-${var.region}-event-db-14"
db_parameter_group_family                  = "aurora-postgresql14"
db_cluster_parameter_group_use_name_prefix = false
db_parameter_group_parameters = [
{
name         = "log_min_duration_statement"
value        = 4000
apply_method = "immediate"
}
]
db_cluster_db_instance_parameter_group_name = "${var.projectname}-${var.environment}-${var.region}-event-db-14"
create_monitoring_role          = true
iam_role_name                   = "${var.projectname}-${var.environment}-${var.region}-event-db-monitoring"
iam_role_force_detach_policies  = true
enabled_cloudwatch_logs_exports = ["postgresql"]
}
Steps to reproduce the behavior:

Expected behavior
The Aurora upgrade could be trigged normally.

Actual behavior
The upgrade didn't start at all and the terraform will fail after around 1 hour as below prompt:
module.aurora_event_db.aws_rds_cluster.this[0]: Still modifying... [id=meid-dev-eu-central-1-event-db, 1h3m31s elapsed]
module.aurora_event_db.aws_rds_cluster.this[0]: Still modifying... [id=meid-dev-eu-central-1-event-db, 1h3m41s elapsed]
module.aurora_event_db.aws_rds_cluster.this[0]: Still modifying... [id=meid-dev-eu-central-1-event-db, 1h3m51s elapsed]
╷
│ Error: updating RDS Cluster (meid-dev-eu-central-1-event-db): InternalFailure:
│       status code: 500, request id: 653b0c3e-4446-4f3f-ab93-6c274d2abbd7
│
│   with module.aurora_event_db.aws_rds_cluster.this[0],
│   on .terraform/modules/aurora_event_db/main.tf line 61, in resource "aws_rds_cluster" "this":
│   61: resource "aws_rds_cluster" "this" {
│
╵
Releasing state lock. This may take a few moments...
Terminal Output Screenshot(s)

Additional context

BTW, I also tested with version 9.3.1, the upgrade sill can't be trigged.


Reduce vertex size

Vertices are 56 bytes in size, which leads to bandwidth becoming the bottleneck in high-throughput renders. Vertices should be optimized and compressed to be 32 bytes in size. Look into: computing tangent/bitangent on the GPU from UVs, octahedron normal encoding.

Vertex data is now acquired dynamically through channels on the GPU, so this is closed by 5c4dd6a. It may still be valuable to compute the tangent/bitangent if the streams aren't available. Normal encoding is also a possibility.


codeql: 2.7.3 -> 2.7.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/github/codeql-cli-binaries/releases.
meta.description for codeql is: "Semantic code analysis engine"
meta.homepage for codeql is: "https://codeql.github.com"
meta.changelog for codeql is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/kyipkjbaxikhqvp0caxqs76vhk73daf5-codeql-2.7.5/bin/codeql had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.7.5 with grep in /nix/store/kyipkjbaxikhqvp0caxqs76vhk73daf5-codeql-2.7.5
found 2.7.5 in filename of file in /nix/store/kyipkjbaxikhqvp0caxqs76vhk73daf5-codeql-2.7.5

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

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
codeql

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

codeql

Maintainer pings
cc @jollheef for testing.

@ofborg eval


API Changes for Open Match 0.6.0

As we plan the road map to Open Match 1.0, we are revisiting the Data Model and the API surface exposed by Open Match and are proposing modifications to these to facilitate future feature work to achieve scale and production readiness.
The goal of this proposal is to solidify the concepts understood by Open Match, clearly identify and define the APIs exposed (and thereby identify the concepts / features that are beyond the scope of Open Match). The proposal also states some design principles and refactors the existing API to achieve those.
The proposal focuses on the API modifications while providing some details on the features these changes will achieve. Separate proposals / issues will be created for other significant related features.
Please go over the proposal and add your comments:
Open Match API Change Proposal

https://github.com/GoogleCloudPlatform/open-match/pull/322 added the new API.


Fix for strange symbols in repository id in cache url

What strange symbols are you seeing? It would be useful to understand their nature, and add specs if they are legitimate.

@BanzaiMan
Repository id can be a number or (new feature) a string like {123-456}
The test is added.


Amazon Bedrock agent example

Change Description
An example code to invoke Amazon Bedrock agent
Issue reference
N/A
Checklist

[x] I have reviewed the contribution guidelines
[ NA] My code includes unit tests
[x] All unit tests and lint checks pass locally
[NA] My PR contains documentation updates / additions if required

Hey @begimher , thanks for the contribution. I noticed there is a duplicated code in the file, is this expected?

Thank you @CandiedCode @asofter !

@begimher thank you for the contribution


JBPM-5300 - Enable custom assignments for service tasks only when cus…

…tomeditors property is not empty (if it exists)
This PR is cherry-pick of #403. QE team would like to include this change also into 6.5.x branch because our effort is to minimize work with updating of internal tests.

+1


Dynamic graph display

Hi, I am using your library and use addEntry function to add data on the graph. The adding rate is about 80Hz, so 125 points per second. I set 400 points display on the window and remove entry outside window.
During the test on iPad mini, the whole app will be slower and slower after about 3 minutes. Maybe the library efficiency could be improved.

With your numbers, it means 22,500 data entries after 3 minutes. That will definitely draw slower.
Drawing the viewport as the end portion of the data, means the chart is looping over the data until reaching the data that is in the viewport. As it has no way to know which xIndex is inside the viewport without calculating it first.
We do have performance improvements planned, but it's not magic and sometimes we have to make compromises. In the meantime you can maybe remove some data that you are not using.

Hi @danielgindi, thanks for this. I've already tried the approach you have mentioned, and as expected, there was a significant improvement in the performance. I was wondering maybe it would be of value to include this as a note in the docs regarding dynamic drawing?

I've got the exactly same function, update LineChartView about 100 times/second. But my problems is the graph seems not to update apparently, Could you point me out what's wrong with this? what is my mistake?
-> these lines of code will be call 100 times/sec
let chartDataSet = self.lineChartView.data?dataSets[0]
var index = chartDataSet?.valueCount
if index > MAX_XVALS {
chartDataSet.removeFirst()
index--
}
let entryData = ChartDataEntry(value: arc4random_uniform(1000) + 1, xIndex: index!)
chartDataSet.addEntry(entry)
self.lineChartView.notifyDataSetChanged()

@tulm00073 would you just check if the drawRect is called and the data you are sure it's updated.
Calling notifyDataSetChanged eventually will invoke setNeedsDisplay, so there should be a redraw of your line chart. You can debug from there.


StickyListHeaders and SwipeActionAdapter

I use the StickyListheaders (https://github.com/emilsjolander/StickyListHeaders) and wants to add the SwipeActionAdapter.
Does anyone have done this?
The problem is that the "StickyList" needs an "StickyListHeadersAdapter".
My CusrsorAdapter implements the "StickyListHeadersAdapter" and I set it to the "StickyListHeadersListView" without "SwipeActionAdapter".
Now I set the CursorAdapter to the "SwipeActionAdapter" and want to set the "SwipeActionAdapter" to the "StickyListHeadersListView", but this does not work because "SwipeActionAdapter" does not implement "StickyListHeadersAdapter"!
How can I solve this? Or does it not work to use this both?

You should then wrap the SwipeActionAdapter with an adapter that implements StickyListHeadersAdapter.
To do this you can write a custom adapter which extends from DecoratorAdapter (a utility class in this library that just passes all calls to the adapter it wraps) and implements StickyListHeadersAdapter.
I hope this puts you on the right track.


Getting started with generics

Introduces the basics of generics in Go. With generics, you can declare and use functions or types that are written to work with any of a set of types provided by calling code.

Done it


Model for testing materials in Godot

Zip with DAE and .blend:
GodotBall.zip

That looks really cool!

It has a godot Logo on it !!!
why is the logo a different material. does it has two material channels? (are multiple material channels even supported?)
Why is it an issue? Are you planning to implement this as a default material testing object?

@toger5
Yes, multiple materials are supported. If you have single mesh you have to assign to different parts different tmp materials. Then when you export to dae and import to Godot multiple slots for materials will be available in inspector for that mesh resource.
I made issue so it wont get lost and anybody can download. There was idea on IRC to have one of those. Although I don't know for what purpose exactly. xD

Oh I had idea to animate one of the parts. Will update DAE soon to support this xD

looks nice, except for the stand it's too long and thin.

@tGuMedia
I wanted a cone in there ;) No one includes Cones in material previews! No one! We need them : [

That visible UV seam kind of bothers me, but I guess its useful for it helps notice any normal map issues.

UV is tiled I just didn't used tiled texture.

Now that's more like it, now can we have that replace the broken test-cube? 😄

What if the test cube is replaced by a "test mesh instance" with a primitive as resource ? In the same way as the collision shape gives a choice between several shapes. Is this a good idea ?

@DriNeo Welcome to the party, #8661 is just doing that. 😃

this was used already and works great, thanks!
closing


Lokalise: Translations update

This pull request was initiated by Lokalise (user Peter Murray) at 2020-12-30 03:13:00

yarn run v1.22.4
$ eslint .
/home/jenkins/workspace/folio-org_ui-remote-storage_PR-9/project/src/index.js
1:1  error  The directory 'src' must be named 'RemoteStorageSettings', after the exported value of its index file  filenames/match-exported
✖ 1 problem (1 error, 0 warnings)
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.


NPM start failed when upgraded to 1.0.0-beta.21

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Windows 10 64 bit
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

$ ng --version
angular-cli: 1.0.0-beta.21
node: 7.1.0
os: win32 x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

npm install -g angular-cli@latest
ng new ng2-hello
cd ng2-hello
npm start <---this step failed.

The log given by the failure.

Normally this include a stack trace and some more information.

hantsy@HANTSY-T540P E:\temp\ng2-hello
$ npm start

><EMAIL_ADDRESS>start E:\temp\ng2-hello
> ng serve                                                        40927ms building modules                               15ms ad05551ms 564ms asset 95% emitting[default] Checking started in a separate process...               153ms emittingevents.js:160
      throw er; // Unhandled 'error' event
      ^

Error: This socket is closed
    at WriteStream.Socket._writeGeneric (net.js:683:19)
    at WriteStream.Socket._write (net.js:734:8)
    at doWrite (_stream_writable.js:334:12)
    at writeOrBuffer (_stream_writable.js:320:5)
    at WriteStream.Writable.write (_stream_writable.js:247:11)
    at WriteStream.Socket.write (net.js:661:40)
    at WriteStream.process.stderr.write (E:\temp\ng2-hello\node_modules\angular-cli\lib\cli\index.js:40:27)
    at Console.warn (console.js:51:16)
    at printErrorAndExit (E:\temp\ng2-hello\node_modules\awesome-typescript-loader\node_modules\source-map-support\source-map-support.js:406:11)
    at process.emit (E:\temp\ng2-hello\node_modules\awesome-typescript-loader\node_modules\source-map-support\source-map-support.js:419:16)
    at process._fatalException (bootstrap_node.js:292:26)

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v7.1.0
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `ng serve`
npm ERR! Exit status 7
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'ng serve'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ng2-hello package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ng serve
npm ERR! You can get information on how to open an issue for this project with: npm ERR!     npm bugs ng2-hello
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ng2-hello
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     E:\temp\ng2-hello\npm-debug.log

Regression in Nodejs, update to 7.2.0 This is not cli related

Ok, just updated to NodeJS 7.2, it is disappeared.
Thanks, @Nikki1993


Issue #84

Added onclick in about section
📋 Description
Adding About Us
🔨 Changes Made

I have added clickon in about us section in dashboard.html file

📸 Screenshots

Thank you for contributing to Research Nexus! We look forward to reviewing your PR and getting it merged!

Open a new pull request with new branch  will check it out


Content Observer cause furnace stopped blasting

Describe the Bug
The furnace stop blasting when I put Content Observer at side of the furnace.
Smoker and Blast Furnace stop blasting , but it still using fuel.
Reproduction Steps
1.Put a furnace(Blast Furnace or Somker).
2.Put Content Observer neared furnace.
3.Furnace stop blasting.
...
Expected Result
Furnace can blasting.
Screenshots and Videos
https://user-images.githubusercontent.com/40121560/149175312-51d91c26-e35c-4593-ba05-06bca98aee6e.mp4
Crash Report or Log
No response
Operating System
Windows 7
Mod Version
0.4.0b
Minecraft Version
1.18.1
Other Mods
No response
Additional Context
No response

FAPI issue


Command Line Poll Creation

It would be beneficial if a new poll could be created using the same method as in V1, by creating a single text line with all of the appropriate flags.  This would be useful for creating relatively complex polls that re-occur.
My example is in support of Clash of Clans, after CWL, I ask my clan to vote on who should get bonus loot.  The only change in the poll each season is the number of recipients and the list of names.  all other flags stay the same, so I would be copying and pasting the majority of the <pm!new> message if I could do it in a single line instead of the wizard.

Feature is implemented, but requires testing before going live.
You can help testing on the support discord (Pollmaster HQ)


Make images and slides for notebook 06

Done, see the slides here - https://github.com/mrdbourke/pytorch-deep-learning/blob/main/slides/06_pytorch_transfer_learning.pdf


Revert back to using javax.validation as jakarta.validation is not supported by micronaut

Note: Use jakarta.validation-api version 2.0.2 instead of version 3.0.0 to be able to use javax.validation instead of jakarta.validation.

Tomas has approved this based on this slack discussion:
[Tomas Langer][2:03 AM](https://proddev-paas-fmw.slack.com/archives/D02H83WT8LW/p1657184618305489)
That change is OK. As I have seen you are changing some versions of dependencies, so I have added Joe + added the label
[Tomas Langer][8:51 AM](https://proddev-paas-fmw.slack.com/archives/D02H83WT8LW/p1657209114331679)
go ahead and merge

... so I will merge once the pipeline completes successfully.


remaining newscale issues

I'm not planning on fixing these issues since we are going to get new lickspout stages soonish, but I'm documenting them in case they become issues in the short term, and they might help when updating the code to the new stages

The python-newscale repository throws "unprintable" errors, which means if you try to print the error, it throws another error
The python-newscale repository prints error messages in addition to raising them, which is visually annoying
Its unclear why we are getting errors from python-newscale to begin with
Once we lose the connection to the stage, I can't seem to reconnect. I dont understand what the issue is
The way we wait for feedback from the IOWorker thread is by sleeping the main thread repeatedly, then checking to see if the result is done. This is bad, we should use slots/signals to get feedback asynchronously and trigger a function.
I'm not familiar with the approach of sending commands to a queue in the IOWorker object, but it seems like there should be a more robust solution.

@alexpiet I'm going to close this issue since we will soon move away from the newscale system entirely


samples: migrate code from googleapis/java-dialogflow

Migrating samples from googleapis/java-dialogflow into java-docs-samples/dialogflow

samples: scaffold pom.xml files (#112)
chore(deps): update dependency com.google.cloud:libraries-bom to v4.3.0 (#121)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.13 (#126)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.14 (#131)
chore(deps): update dependency com.google.cloud:libraries-bom to v4.4.0 (#133)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.15 (#136)
chore(deps): update dependency com.google.cloud:libraries-bom to v4.4.1 (#137)
chore(deps): update dependency com.google.cloud:libraries-bom to v5 (#147)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.16 (#153)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.17 (#159)
chore(deps): update dependency com.google.cloud:libraries-bom to v5.2.0 (#163)
chore(deps): update dependency com.google.cloud:libraries-bom to v5.3.0 (#174)
chore(deps): update dependency com.google.cloud:libraries-bom to v5.4.0 (#186)
chore(deps): update dependency com.google.cloud:libraries-bom to v5.5.0 (#197)
chore(deps): update dependency com.google.cloud:libraries-bom to v5.6.0 (#209)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.18 (#210)
chore(deps): update dependency com.google.cloud:libraries-bom to v5.7.0 (#212)
chore(deps): update dependency com.google.cloud:libraries-bom to v6 (#219)
chore(deps): update dependency com.google.cloud:libraries-bom to v7 (#222)
chore(deps): update dependency com.google.cloud:libraries-bom to v7.0.1 (#227)
chore(deps): update dependency com.google.cloud:libraries-bom to v8 (#233)
chore(deps): update dependency com.google.cloud:libraries-bom to v8.1.0 (#246)
samples: Dialogflow to gcp (#1181)
samples: Fix DialogFlow tests and update to canonical sample format. (#1210)
samples: Update KnowledgeBaseManagement Tests to address inconsistent results.  (#1233)
samples: Make the test less flaky (#1245)
samples: Update streaming sample to use non-deprecated method (#1413)
samples: TTS / Sentiment GA (#1421)
samples: Rework the tests to remove flakiness (hopefully) (#1488)
samples: Recreate Test Knowledge Base after it was deleted and update other tests to use UUIDs (#1535)
samples: Update KnowledgeBaseId and update rouge SA roles (#1553)
samples: Force delete to wait for call to finish to fix tests (#1830)
samples: dialogflow: add and increase timeout to document creation for tests (#1996)
samples: dialogflow: increase timeout for test (#2136)
samples: update shared config (#2443)
samples: dialogflow: delete samples that are not in docs (#2602)
samples: samples: refactor dialogflow for 2.1.0 (#3283)
chore(deps): update dependency com.google.cloud:libraries-bom to v9
chore(deps): update dependency com.google.cloud:libraries-bom to v9.1.0
chore(deps): update dependency com.google.cloud:libraries-bom to v10 (#270)
chore(deps): update dependency com.google.cloud:libraries-bom to v11
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.21 (#303)
chore(deps): update dependency com.google.cloud:libraries-bom to v11.1.0 (#307)
samples: add sample code to query regional Dialogflow agent (#310)
chore(deps): update dependency com.google.cloud:libraries-bom to v12 (#311)
test(deps): update dependency junit:junit to v4.13.1
chore(deps): update dependency com.google.cloud:libraries-bom to v12.1.0 (#321)
chore(deps): update dependency com.google.cloud:libraries-bom to v13 (#327)
chore(deps): update dependency com.google.cloud:libraries-bom to v13.1.0 (#331)
test(deps): update dependency com.google.truth:truth to v1.1 (#328)
chore(deps): update dependency com.google.cloud:libraries-bom to v13.2.0 (#335)
chore(deps): update dependency com.google.cloud:libraries-bom to v13.3.0 (#337)
chore(deps): update dependency com.google.cloud:libraries-bom to v13.4.0 (#344)
chore(deps): update dependency com.google.cloud:libraries-bom to v14 (#354)
chore(deps): update dependency com.google.cloud:libraries-bom to v15 (#356)
chore(deps): update dependency com.google.cloud:libraries-bom to v16 (#375)
chore: added retry for flaky test (#391)
chore(deps): update dependency com.google.cloud:libraries-bom to v16.2.0 (#402)
chore(deps): update dependency com.google.cloud:libraries-bom to v16.4.0 (#409)
test(deps): update dependency junit:junit to v4.13.2 (#432)
test(deps): update dependency com.google.truth:truth to v1.1.2 (#414)
samples(deps): update dependency com.google.cloud:google-cloud-core to v1.94.1 (#429)
chore(deps): update dependency com.google.cloud:libraries-bom to v17 (#446)
chore(deps): update dependency com.google.cloud:libraries-bom to v18 (#449)
chore(deps): update dependency com.google.cloud:libraries-bom to v18.1.0 (#460)
chore(deps): update dependency com.google.cloud:libraries-bom to v19 (#464)
samples(deps): update dependency com.google.cloud:google-cloud-core to v1.94.3 (#458)
deps: update dependency com.google.cloud:google-cloud-core to v1.94.4 (#477)
chore(deps): update dependency com.google.cloud:libraries-bom to v19.1.0 (#484)
chore(deps): update dependency com.google.cloud:libraries-bom to v19.2.1 (#486)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.22 (#498)
deps: update dependency com.google.cloud:google-cloud-core to v1.94.6 (#501)
chore(deps): update dependency com.google.cloud:libraries-bom to v20 (#510)
deps: update dependency com.google.cloud:google-cloud-core to v1.94.7 (#508)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.1.0 (#519)
deps: update dependency com.google.cloud:google-cloud-core to v1.94.8 (#528)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.2.0 (#535)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.3.0 (#547)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.4.0 (#556)
samples: updated legacy field (#493)
samples: updated legacy field in detectintentknoledge (#569)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.5.0 (#567)
samples: updated legacy field in detectintentaudio (#571)
samples: updated legacy field in detectintenttexts (#572)
samples: updated legacy field in detect intent samples (#575)
test(deps): update dependency com.google.truth:truth to v1.1.3 (#573)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.6.0 (#584)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.0.23 (#583)
deps: update dependency com.google.cloud:google-cloud-core to v1.95.1 (#580)
deps: update dependency com.google.cloud:google-cloud-core to v1.95.2 (#590)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.7.0 (#604)
deps: update dependency com.google.cloud:google-cloud-core to v1.95.3 (#603)
deps: update dependency com.google.cloud:google-cloud-core to v1.95.4 (#607)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.8.0 (#615)
chore(deps): update dependency com.google.cloud:libraries-bom to v20.9.0 (#624)
deps: update dependency com.google.cloud:google-cloud-core to v2 (#634)
deps: update dependency com.google.cloud:google-cloud-core to v2.0.3 (#647)
deps: update dependency com.google.cloud:google-cloud-core to v2.0.5 (#649)
chore(deps): update dependency com.google.cloud:libraries-bom to v21 (#655)
deps: update dependency com.google.cloud:google-cloud-core to v2.1.0 (#661)
deps: update dependency com.google.cloud:google-cloud-core to v2.1.1 (#664)
chore(deps): update dependency com.google.cloud:libraries-bom to v22 (#673)
deps: update dependency com.google.cloud:google-cloud-core to v2.1.2 (#680)
samples: add update intent code sample  (#639)
chore(java): install maven 3.8.1 at runtime (#1202) (#689)
samples: set agent code sample (#660)
chore(deps): update dependency com.google.cloud:libraries-bom to v23 (#694)
deps: update dependency com.google.cloud:google-cloud-core to v2.1.3 (#702)
deps: update dependency com.google.cloud:google-cloud-core to v2.1.4 (#711)
chore: remove dependency dashboard labels (#715)
deps: update dependency com.google.cloud:google-cloud-core to v2.1.6 (#718)
samples: add webhook sample (#730)
chore(deps): update dependency com.google.cloud:libraries-bom to v23.1.0 (#737)
samples: added region tags (#738)
deps: update dependency com.google.cloud:google-cloud-core to v2.1.7 (#728)
docs(sample): adds new list training phrases sample (#742)
samples: Added comments (#748)
deps: update dependency com.google.cloud:google-cloud-core to v2.1.8 (#749)
deps: update dependency com.google.cloud:google-cloud-core to v2.2.0 (#751)
chore(deps): update dependency com.google.cloud:libraries-bom to v24 (#760)
deps: update dependency com.google.cloud:google-cloud-core to v2.3.0 (#770)
deps: update dependency com.google.cloud:google-cloud-core to v2.3.1 (#772)
deps: update dependency com.google.cloud:google-cloud-core to v2.3.2 (#780)
deps: update dependency com.google.cloud:google-cloud-core to v2.3.3 (#784)
chore(deps): update dependency com.google.cloud.samples:shared-configuration to v1.2.0 (#779)
chore(deps): update dependency com.google.cloud:libraries-bom to v24.1.0 (#796)
chore(deps): update dependency com.google.cloud:libraries-bom to v24.1.1 (#801)
chore(deps): update dependency com.google.cloud:libraries-bom to v24.1.2 (#807)
deps: update dependency com.google.cloud:google-cloud-core to v2.3.4 (#809)
deps: update dependency com.google.cloud:google-cloud-core to v2.3.5 (#811)
chore(deps): update dependency com.google.cloud:libraries-bom to v24.2.0 (#819)
deps: update dependency com.google.cloud:google-cloud-core to v2.4.0 (#833)
chore(deps): update dependency com.google.cloud:libraries-bom to v24.3.0 (#843)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.0 (#838)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.1 (#845)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.3 (#847)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.4 (#854)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.5 (#867)
chore(deps): update dependency com.google.cloud:libraries-bom to v24.4.0 (#874)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.6 (#872)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.8 (#883)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.9 (#886)
chore(deps): update dependency com.google.cloud:libraries-bom to v25 (#892)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.10 (#891)
samples: add sample code for ConversationProfile, Conversation and Participant (#832)
samples: update sample code for knowledge base (#898)
deps: update dependency com.google.cloud:google-cloud-core to v2.5.11 (#902)
chore(deps): update dependency com.google.cloud:libraries-bom to v25.1.0 (#907)
deps: update dependency com.google.cloud:google-cloud-core to v2.6.1 (#909)
chore(deps): update dependency com.google.cloud:libraries-bom to v25.2.0 (#920)
chore(deps): update dependency com.google.cloud:libraries-bom to v25.3.0 (#926)
deps: update dependency com.google.cloud:google-cloud-core to v2.7.1 (#927)
chore(deps): update dependency com.google.cloud:libraries-bom to v25.4.0 (#934)
samples: update sample code for document (#938)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.0 (#939)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.1 (#945)
chore(deps): update dependency com.google.cloud:libraries-bom to v26 (#956)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.3 (#963)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.4 (#966)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.5 (#972)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.7 (#975)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.8 (#979)
chore(deps): update dependency com.google.cloud:libraries-bom to v26.1.0 (#983)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.9 (#987)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.10 (#988)
chore(deps): update dependency com.google.cloud:libraries-bom to v26.1.1 (#990)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.12 (#995)
chore(deps): update dependency com.google.cloud:libraries-bom to v26.1.2 (#1002)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.13 (#1006)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.14 (#1010)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.15 (#1014)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.16 (#1021)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.18 (#1027)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.19 (#1029)
deps: update dependency com.google.cloud:google-cloud-core to v2.8.20 (#1030)
chore(deps): update dependency com.google.cloud:libraries-bom to v26.1.3 (#1037)

Fixes #issue

It's a good idea to open an issue first for discussion.

[ ] I have followed Sample Format Guide
[ ] pom.xml parent set to latest shared-configuration
[ ] Appropriate changes to README are included in PR
[ ] API's need to be enabled to test (tell us)
[ ] Environment Variables need to be set (ask us to set them)
[ ] Tests pass:   mvn clean verify required
[ ] Lint  passes: mvn -P lint checkstyle:check required
[ ] Static Analysis:  mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
[ ] Please merge this PR for me once it is approved.

I'm not sure the test actually ran:
#
# dialogflow/snippets
#

 Testing completed.

#
# Summary
#

SUCCESS: 1, FAILURE: 0, SKIPPED: 0, ERROR: 0,
dialogflow/snippets...................................................[ SUCCESS]

@averikitsch - a bunch of tests were not migrated since the samples those tests were testing were not used anywhere and based on the assessment I left them to be deleted without migration:
https://github.com/googleapis/java-dialogflow/tree/fixit/sample-migration/samples/snippets/src/test


Update v_generate_user_grant_revoke_ddl.sql

Added sequence number to order DDLs by hierarchy. Added schema admin to DDL statement.

Updated multitablerestore utility with cosmetic changes, improved error handling and PEP8 compliance.
Added sequence to v_generate_user_grant_revoke_ddl view for hierarchy and also added schema name admin.

deleted v_find_dropuser_privs.sql to replace with v_generate_user_grant_revoke_ddl. created v_vacuum_summary to flatten stl_vacuum data.


framework: sets one minute timeout for process

so as to catch unhandled exception if stdout/stderr has not an ascii character

Replaced by https://github.com/OISF/suricata-verify/pull/936


.local TLD pass as public domains

Run validate.url('http://base-test-site.local', public=True)
it returns true but should be false

This can be fixed by updating the regex -
I have a local branch but I do not have permission to push.


package.json on hover does not show latest version

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.70.2
OS Version: macOS 12.5.1

Steps to Reproduce:

package.json with typescript
hover over typescript

Actual:

Expected: Latest version: 4.8.2
Code pointer: https://github.com/Microsoft/vscode/blob/9a03a86c0a54a24c355bd950ddad91a0e74de6dd/extensions/npm/src/features/packageJSONContribution.ts#L303

1.71 is likely to ship later today. When it does, please re-test and close this if fixed.

I verified it's fixed in the insiders build, closing by that!


Auri is insanely overpowered right off the bat.

What happened?
As the title exclaims. I picked up Auri at roughly level 5 and literally at my first combat encounter I see Auri dealing 400 damage to some giant spriggan creature. Alternatively, she would do ~200 damage to humanoid/armoured targets.
Modlist version
<IP_ADDRESS>

should be more balanced now, removed all her starting perks


More support for codecs

Get ZStd tested as codec In GitHub Actions.
Use versioned zstd for dynamic loading as the base zstd installation(yum install zstd for instance) only installs versioned shared libraries. yum install libzstd-devel on the other hand installs libzstd.so too, but I think we should generally use versioned libraries to be sure that we get a tested/compatible zstd package.
No need to find_package() for dynamically loaded packages. This PR supersedes #104, so closing that PR for now.

Codecov Report

Merging #105 (ff11096) into develop (6ea23d9) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #105      +/-   ##
===========================================
+ Coverage    62.57%   62.61%   +0.03%
===========================================
  Files           57       59       +2
  Lines        17651    17696      +45
===========================================
+ Hits         11045    11080      +35
- Misses        6606     6616      +10

Impacted Files
Coverage Δ

core/include/codec/codec_zstd.h
75.00% <100.00%> (ø)

core/src/array/array.cc
54.75% <0.00%> (-0.38%)
:arrow_down:

core/src/codec/codec_zstd.cc
90.90% <0.00%> (ø)

core/src/codec/codec.cc
75.15% <0.00%> (+0.47%)
: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 6ea23d9...ff11096. Read the comment docs.


Add poetry lockfiles

closes https://github.com/open-austin/Odyssey-Court-Records-to-JSON/issues/11


Error on npm run develop

Hello!
I cloned the repo for my new gatsby project and I got an error on npm run develop
npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR!  npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/gatsby npm ERR<EMAIL_ADDRESS>from the root project npm ERR!  npm ERR! Could not resolve dependency: npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/gatsby-plugin-offline npm ERR<EMAIL_ADDRESS>from the root project
Is there a workaround get the development running?
Thanks

Hi @MateThemes
Thanks a lot for reporting this issue ! I will look into this asap !

This should be solved on version 2.0.2


Add copy subcommand & fix clippy warnings

This PR mainly add the copy subcommand in the src/tool/core/copy.rs file. Other files also had to be modified.
The subcommand automatically copies the leetcode-relevant code, so it can be pasted directly into leetcode

Thanks, that's a good idea. I'll take a look when I get a chance.

Can I request to split the PR into two. One for clippy lints and a separate one for the copy feature (which I think is a great idea btw)? If it's not easy for you I can also do it.

In hindsight I should also mention that if you are interested (and you aren't already part of our discord you are welcome to join us on discord if you want to compare your solutions with others and that kind of thing. There is also a topic there where we do work on this project. You're more than welcome to join us there as well.

The only clippy specific change was in src/leetcode_env/tree.rs. The others were required to make the copying work. I can revert that file later today

Ok if it's just one then leave it. It's fine no worries.

Will you merge?

Yes I will, just haven't had a chance to review it yet.

Thank you very much for the PR. Really good job following the structure of the code. Looks good overall just have a few questions.
The main one is I haven't seen how the command identifies which file it should copy the text from. It looks like it just uses the first file found that is not lib.rs. It is quite possible the user has many solutions in the folder and it might copy the wrong one. Please let me know if I missed it. I'm thinking we could either ask for the filename which the shell may be able to auto complete or we could try to use the same format as what we do for generate. Let me know what you think. Alternatively we could use the most recently modified file to make it easier but I'm seeing that might end up being annoying in some cases if another file gets edited for whatever reason.
I made a few other suggestion / added questions attached to specific lines in the code. Let me know if you have trouble finding them.

It looks like it just uses the first file found that is not lib.rs.

Yes, that's exactly how I implemented it. I couldn't find it stored anywhere, and this seemed like a good solution.

It is quite possible the user has many solutions in the folder and it might copy the wrong one

Looks like I had a different view of the project. I thought each solution required its own project, which makes more sense to me in Leetcode's case. Having multiple solutions in the same project would be very practical for the user either, since cargo test, for example, would test all the solutions at once.

It looks like it just uses the first file found that is not lib.rs.

Yes, that's exactly how I implemented it. I couldn't find it stored anywhere, and this seemed like a good solution.

Yes you are correct it isn't stored anywhere because the application doesn't maintain any state between runs so we'd need the user to supply that information when they run it.

It is quite possible the user has many solutions in the folder and it might copy the wrong one

Looks like I had a different view of the project. I thought each solution required its own project, which makes more sense to me in Leetcode's case. Having multiple solutions in the same project wouldn't be very practical for the user either, since cargo test, for example, would test all the solutions at once.

I understand your point of view however it is setup right now to expect each problem to be a module. This allows for sharing of common resources between problems, like dependencies and specification of rust version. I will make a note to add the assumed project structure to the reademe.  If we add support for multiple then I think it will cause each feature we add to require much more effort to work with all structures. We already have two types of file names with and without the problem number.
Some users specify which test they want to run when they call cargo test but I actually only keep the modules in lib.rs that I am currently working on so only those get run / compiled.

Updating with my current thoughts after the discussion in Issue https://github.com/rust-practice/cargo-leet/issues/86
I think the fundamental problem is that we have a different perspective on keeping already submitted solutions. At first I was comparing the two options in the context of keeping solutions. But given that you do not intend to do that, yours is just a subset of mine. It's the case of a new setup with the first solution being done. So anything that works for my setup should also work for yours. I've given the cache setup more thought. It only causes problems if it's global. Local variables to the rescue. I thought about how it's done in the mainmatter workshop runner and they use a database in the same folder to store state but I'm not familiar with using Sqlite yet. If I thought it would be a better solution I'd invest the time now but I think just a state struct that we persist to disk in ron or json format would also work and we just add it to the .gitignore so it doesn't get committed. The struct could look like the following:
pub struct AppState {
    pub last_problem_slug: Option<String>,
    pub should_use_problem_number_in_name: bool,
}

Don't stress about the implementation complexity. I don't mind implementing it if desired. I'm thinking that we can load the state on app startup and persist it to disk on successful exit. Does this approach solve the problem in a way that works for you?

@Antosser how do you feel about this approach?

Sorry for the late response! I appreciate your thoughts and suggestions in #86.
I still have some thoughts about the design choice of having multiple solutions in a single crate. For me, it's similar to why I prefer keeping my other projects in separate crates. This structure allows me to avoid specifying the exact project to build, making things simpler when I have that project in my working directory.
This approach means I can just run cargo test instead of something like cargo test -p container-with-most-water -- container_with_most_water::tests (unless there's a shorter way I’m missing?).
I see the value in your suggestion of using a cache to track the current solution, but it feels a bit like reimplementing what working directories (cd) already achieve. I understand that some prefer having all their solutions in one directory, but I still find the fundamental design decision a bit challenging.
Thanks again for your insights and willingness to implement the solution. Does this perspective make sense from your end?

Sorry for the late response! I appreciate your thoughts and suggestions in #86.

No worries let not your heart be troubled.

I still have some thoughts about the design choice of having multiple solutions in a single crate. For me, it's similar to why I prefer keeping my other projects in separate crates. This structure allows me to avoid specifying the exact project to build, making things simpler when I have that project in my working directory.

Technically we could achieve that using workspaces to be able to just cd into the directory and have only one project there but I think that swings too far the other way in terms of number of files stored. Furthermore I don't plan to change the structure I'm currently using so separate crates isn't a solution that works for me.
Right now I don't have to specify which one to run. I just use cargo test I only keep the one I'm working on in lib.rs as a module. I just keep the others there so I can search over them and refer to them as desired.

This approach means I can just run cargo test instead of something like cargo test -p container-with-most-water -- container_with_most_water::tests (unless there's a shorter way I’m missing?).

There is and isn't. If you look at mine you can see that lib.rs is basically empty so yes when I'm using it I use it just like you in terms of doing cargo test.

I see the value in your suggestion of using a cache to track the current solution, but it feels a bit like reimplementing what working directories (cd) already achieve. I understand that some prefer having all their solutions in one directory, but I still find the fundamental design decision a bit challenging.

Since it's not a new project it would mean changing an old decision and changing it means that it no longer works the way I use it....

Thanks again for your insights and willingness to implement the solution. Does this perspective make sense from your end?

Yes I follow your perspective but unfortunately I think changing the overall design to only support one file is a non-starter. We'd need to come up with a solution that works for both because I do keep my old files and don't want to suddenly not be able to use it anymore.

Looks like a support legacy code at all vs. technically more correct, and I don't think I can expect that core design principle to change any time soon

I disagree that your approach is better. Just because you choose not to keep your completed exercises does not make your approach better. It is not legacy code... It's the code in use and is working as designed. You are correct in your assessment of changes to core principles. They will not be changed without sufficient reason. The reason provided thus far does not warrant breaking backward compatibility.

There doesn't seem to be interest in moving this forward at this time. May revisit in the future.

After thinking about it some more, I do see both the ups and downs, and at least for this repo, which already has active users, my approach doesn't make sense. I strove for absolute correctness in the way you choose your current problem you're working on, and I don't think that's possible with any approach. In any way, I still really like the project and look forward to contributing keeping that in mind!

Thanks, looking forward to working with you. If you want to revisit this let me know and I'll try to do any parts that are giving you issues.


updateconfigs

change v = 3 to v = 1, to improve system performance

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.