US868108: Update Copyright statements to 2024

Ticket: https://internal.almoctane.com/ui/entity-navigation?p=131002/6001&entityType=work_item&id=868108

A developer build has not yet been created for this branch. Click here to go ahead and create the build...


specify alt attribute of avatar image through User component

Feature request 🚀

User component uses Avatar component so I want to pass alt like prop.

Examples:
This is just my idea... I couldn't find better prop name than altText.
<User src="/assets/avatar.png" name={author} altText="author">
    {summary}
</User>

Great, looks good for me.


[CHALLENGE SUBMISSION] - day 23

Please provide the following information for your submission:
What is your name? (First, Last)
Barbara Forbes
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/Ba4bes/25daysofserverless/tree/master/Daya23ChasseGalerie
What Challenge is this for? (Challenge number between 1 and 25)
23
(Optional) Anything else we should know? e.g., language used, location, blog post?
PowerShell Function app, Log Analytics and Azure Alerts

The unthinkable has happened: after weeks of community members all over the globe chipping in to help solve people's problems with serverless technology, the evil grinch's heart is starting to soften! He's still not quite ready to give up his server-stealing plot, but our whole Azure Cloud Advocacy team is flying up to the grinch's lair to help convince him to change his ways.
As such, the team behind 25 Days of Serverless is OOF (Out Of Facility/Office) between Dec 24, 2019 and January 1, 2020. We'll not review Issues in this period of time, but encourage you to catch up on any challenges you haven't had the time to work on yet. 😄 Our Discord Server is a perfect place to reach out to for community support during this time. After our return, we'll add contributors who submitted a working solution as an Issue to CONTRIBUTORS.md file until January 15, 2020.


storage account v1

closes #118
this is the first version of a storage account meant to:

accept arbitrary data being posted
make it available via queries

this account will be used for #117  , so changes within this scope are to be expected.
opening this now to avoid a massive pr later down the line.

Now that I think about it, probably worth updating the docs Account section as well including this new functionality

Now that I think about it, probably worth updating the docs Account section as well including this new functionality

fair, I adjusted the existing accounts section to refer to base account instead of just an account.
added a section for the storage account, but left it with todo for now as this version of the account is just for testing / poc.


Suggestions and a Bug Report for AutoTools Mod

Hello! First, thank you for developing the AutoTools mod for Minecraft Java! It’s a very helpful addition to the game, and I appreciate the work you’ve put into it.
I have a couple of suggestions that could make it even better. First, it would be great if tools or weapons with low durability didn’t automatically move from the inventory to the hotbar. Additionally, a notification about low durability would be helpful to remind players to repair or replace items before they break. It would be awesome if players could choose the percentage at which the system notifies them about critical item durability, or also set a specific numerical value (up to 10 or so) at which a tool can no longer be used. I found similar features in the mods Durability Guard and Low Durability Switcher, and you might want to check those out for inspiration.
I also encountered a bug: when I try to break an ender chest with a pickaxe enchanted with Silk Touch, the mod always automatically switches to a different pickaxe without Silk Touch from my inventory. Could you please look into fixing this issue?
Thank you again for your work, and I’m excited to see how AutoTools will improve in future updates!

these are some pretty great suggestions! i hope he looks into these at some point.


Part 1.

Strings (String construction mode)
logic operations
apply immediately
apply later

[ ] Strings (String construction mode)
[ ] logic operations
[ ] apply immediately
[ ] apply later

this is done


chore: remove formal verification chapter

This change is

I would remove this as non of these are usable in production

remove the references or the whole chapter?
could be nice to leave the chapter with the short explanation? dont know actually

I don't see the point of talking about formal verification if it's not something you can leverage for your contracts security. If there's any tool easily usable, why not, but I don't think it's the case today

@enitrat  ready to merge


soundd: scale volume with ambient noise instead of speed

Where is the code location of the volume scaling functionality?

Oh I see, it´s in sound.cc file line 49.

Is the calculation of the ambient noise already implemented or not? If not, where in code can I get signal values from the microphone?

Nope. I'd start here to get audio input: https://doc.qt.io/qt-5/qtmultimedia-multimedia-audioinput-example.html.

This may no longer be necessary with the new sounds I just merged in. Even at 100% volume with no ambient noise, they're quite pleasant.

They are so jingly.


fastmerge, prfixmaster: Add issue number to commit message header

Emulate GitHub's behavior when squash-merging a PR.

This change is

Oooh, great! I read the title of the issue this morning on my phone, so I didn’t even noticed who submitted it (no user images on notifications on mobile). I though “sounds reasonable, will implement this afternoon”. Now I came to see it and noticed it was actually a pull request. Thumbs up to that! Thank you.

Is message a OS X utility I don't have, or just a syntax error?
message "Amending commit message with issue number (#${issue_number})"
When I try using after update:
 [.../homebrew-cask/Casks] > prfixmaster -c
/usr/local/bin/prfixmaster: line 118: message: command not found
[master ea70191] Added Synergy (1.7.6) (#22644)
[snip]

Ah, whoops, looks like that function is defined in fastmerge but not prfixmaster. Seems to be just a shim for echo, though.

Yep, that’s correct. At one point I decided to use message in some of the noisiest scripts (the ones that output more messages not specifically set by me) just in case I ever decided to change the styling of the output messages. fastmerge was made after prfixmaster, if I recall correctly.


Integer#divmod sig more accurate

This improves the signature of Integer#divmod to make it more accurate.

Integer#div with an Integer argument always returns an Integer
Integer#mod with an Integer argument always returns an Integer
Hence Integer#divmod with an Integer argument should always return [Integer, Integer]

Motivation
In the project I'm working at we use Integer#divmod in a few places.
Test plan
I can add some tests if someone shows me:

in which file they should be located;
which other tests I can use as an example.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_I3edyF9OBCEHS4

Tests on the Stripe codebase went OK w/o any issues...
I'll let @jez speak of any testing recommendations for this one, though.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_IDpazRTX2E250x


Roll back codecov CI task to v3

As per #12303

CI on my fork failed with a random error at Github's end before the codecov step, the PR run attempted a tokenless upload, hit the rate limit and aborted without an error, and the run against the Wagtail branch used the token and actually succeeded. Given that the last one is the only one that's supposed to have a chance of reliably working, I guess that counts as a success...? :-)


Allow tests to run and pass in Devcontainers.

Fixes: #154
The tests in test_webhooks assume that Redis is not setup.  In order to
replicate this in a Devcontainer were Redis is running, we point the tests
to a different DB.  Changes were made in the env file to match the settings
in nautobot_config.

One Black failure in CI:
nautobot/core/tests/nautobot_config.py:48:1: E305 expected 2 blank lines after class or function definition, found 1

🚢 🇮🇹


🐛 Bug Report: @techdocs/cli version 1.8.12 fails to publish

📜 Description
When we do techdocs-cli publish with the latest version of @techdocs/cli (1.8.12) we get this error in our Azure DevOps pipeline:

Cannot find module 'morgan'
Require stack:

/opt/hostedtoolcache/node/18.20.3/x64/lib/node_modules/<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/opt/hostedtoolcache/node/18.20.3/x64/lib/node_modules/@techdocs/cli/bin/techdocs-cli

##[error]Bash exited with code '1'.

This started happening after version 1.8.12 was released. If we install the previous version with this command npm install -g<EMAIL_ADDRESS>it works like a charm to publish.
👍 Expected behavior
I think version 1.8.12 of @techdocs/cli should work like before. I can't see any changes in functionality in the changelog.
👎 Actual Behavior with Screenshots
The publish command failed with this error:

Cannot find module 'morgan'
Require stack:

/opt/hostedtoolcache/node/18.20.3/x64/lib/node_modules/<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/opt/hostedtoolcache/node/18.20.3/x64/lib/node_modules/@techdocs/cli/bin/techdocs-cli

##[error]Bash exited with code '1'.

👟 Reproduction steps
Try running this command with version 1.8.12 of @techdocs/cli (account information hidden):

techdocs-cli publish  --entity $(entity)
--publisher-type azureBlobStorage
--azureAccountName $(AZURE_ACCOUNT_NAME)
--azureAccountKey $(AZURE_BLOB_STORAGEKEY)
--storage-name $(AZURE_BLOB_STORAGENAME)

If it fails, try running it again using version 1.8.11 and see if that works. If it does, this should mean a bug in 1.8.12?
📃 Provide the context for the Bug.
We build and publish docs in our Azure DevOps pipelines. This stopped working yesterday (18th of June 2024) after version 1.8.12 was released which we automatically started using since we install @techdocs/cli with this command, giving us the latest version: npm install -g @techdocs/cli
🖥 Your Environment
Running in Azure DevOps pipeline using vmImage: 'ubuntu-latest'.
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, I don't have time to work on this right now

Closing as duplicate of https://github.com/backstage/backstage/issues/2530, patch should be out later today

I guess you linked the wrong issue. @freben


[SPARK-26429][SS]add jdbc sink for Structured Streaming.

What changes were proposed in this pull request?
Add jdbc sink for Structured Streaming based on
How was this patch tested?
unit tests

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #100384 has finished for PR 23369 at commit 3f776f5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100384/
Test PASSed.

@dongjoon-hyun , code style issues fixed done. Please help to review again. Thanks.

Test build #100428 has started for PR 23369 at commit 107a1e1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6392/
Test PASSed.

Test build #100428 has finished for PR 23369 at commit 107a1e1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100428/
Test PASSed.

Test build #100434 has started for PR 23369 at commit aa67565.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6395/
Test PASSed.

Test build #100434 has finished for PR 23369 at commit aa67565.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100434/
Test FAILed.

Retest this please.

Test build #100444 has started for PR 23369 at commit aa67565.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6403/
Test PASSed.

Test build #100444 has finished for PR 23369 at commit aa67565.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100444/
Test PASSed.

Please follow the recent discussion of data source API V2. In the current stage, you can use foreachBatch(), which was explained in the doc: https://docs.databricks.com/spark/latest/structured-streaming/foreach.html

OK, I will follow the doc. Thanks.

Hi @yanlin-Lynn is there a plan to support JDBC as a source type for the Structured Streaming API?

Hi @yanlin-Lynn is there a plan to support JDBC as a source type for the Structured Streaming API?

No. I have added it in bahir project.


Add a response header 'X-Sequins-Proxied-To'

What does this PR do?
Exposes which server handled the request to the client, though a response header X-Sequins-Proxied-To
Why?
To increase visibility on how many requests are proxied though sequins.  With this data we can chart if requests become slow though proxying or not.
r @colinmarc

Can you squash into one commit? Otherwise, LGTM.

Can do!


Recently updated api request error

Recently updated api request error，I have been using the previous api for over 2 years！

/sp/targets/bid/recommendations：
this endpoint request error 500，and cannot be improved。
/sp/campaigns/budget/usage：
this endpoint request error 401，But it has actually been authenticated, and calling other apis is normal

Is there a problem with the api？

Hi @niceman121 I don't see any changes to the documentation for either of the above endpoints. If you think there is a bug with the API, please open a JIRA ticket to get assistance from our support team.


⚠ Bofrost.de has degraded performance

In 783892e, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2759 ms

Resolved: Bofrost.de performance has improved in 9793796.


color syntax inside of strings when viewing .bash, .sh, .fish, etc. files

This would be an amazing feature.

I think this would be a good idea, too. But you should address this request to the language-shellscript package.
My grammar only scopes pure AWK scripts. If I extend it to several kinds of shell syntax I'll get in conflict with Atoms default grammar for shell script.
Basically Atom supports including grammars from within another one and when I started this language package I did some testing on how to use it for highlighting "nested" awk in shell scripts. Finally I dropped it because I wasn't able to completely understand their string matching and I don't want to mess up their syntax highlighting with my untested code. :wink:
Maybe some of the contributors to the shell script grammar can do this.

:+1:


isDeepEqual takes functions as arguments, returning a partially applied function

Codecov Report

Merging #202 (731a212) into master (4948216) will decrease coverage by 0.08%.
The diff coverage is 90.32%.

@@            Coverage Diff             @@
##           master     #202      +/-   ##
==========================================
- Coverage   98.73%   98.65%   -0.09%
==========================================
  Files         229      229
  Lines        3241     3271      +30
==========================================
+ Hits         3200     3227      +27
- Misses         41       44       +3

Impacted Files
Coverage Δ

x/isDeepEqual.js
96.42% <90.32%> (-3.58%)
: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 4948216...731a212. Read the comment docs.


Backport ES changes

Summary of the changes / Why this improves CrateDB
See commits for details
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Our crate Version differs quite a bit from es Version, maybe it is worth including VersionsTests as well ?

Our Version differs quite a bit from es Version, maybe it is worth including VersionsTests as well ?

I can follow up on looking into Version. It's bound to be different because we've our CrateDB/ES version distinction but they added some logic to reduce the amount of boilerplate required for the version tracking. Maybe we could port something there.


Add Druid Tab

Add the new druid tab into spark web ui. and add the common runtime properties from druid into recourse folder of test.

thanks @ZimingWang this is merged, commit is 14d6f30e2f19a6ce31f78b0a9b7fade10b2a4923


Fix-reference-box

removed image link, but not image.

@sidwray - fixing images. i don't have permission to edit directly in gh-pages. i need an approver.


Azure Service Bus Component - Add "decode base64 message" option to input bindings

Describe the proposal
When connecting an Azure service bus queue or Azure storage queue (maybe also event hub) to a storage account to receive e.g. the blob created events, all queue messages/events are base64 encoded. This will cause an error in the application in case the POST route handler applies an automated JSON parsing of the body (because the headers have the content-type application/json) so a special middleware has to be added to decode the message before it gets parsed.
Instead, it'd be great if there is an option like "decode base64 message" so that the application doesn't need to implement the decoding logic.
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: <name>
spec:
  type: bindings.azure.servicebusqueues
  metadata:
  - name: connectionString
    value: https://***
  - name: queueName
    value: queue1
  - name: decodeMessage
    value: true

@youngbupark @yaron2 We can start by implementing this in the specific component mentioned here. If this proves to be a common need for other components, then it might be worth to bake it into the runtime.

I agree.

Hello @subesokun!
As I work quite a lot with Azure storage and Service bus I wanted to recreate your environment to contribute with a PR and add the decodeMessage feature.
Could you add some information about the steps you are following? I created and Azure event grid subscription from Azure storage with blob events redirected to Azure service bus queues and it is not base64 encoded.
Are you using az functions?

I have this change working in a local branch, however there is something I would like to ask. The dapr api method onOutputBindingMessage, is marshalling the data request payload to []uint8 and it is including the string quotes in the target data message:
https://github.com/dapr/dapr/blob/master/pkg/http/api.go#L254
When you try to decode the base64 it is invalid so you need to trim the string payload:
if a.metadata.DecodeBase64 == "true" {
			if decoded, err := decodeBase64Data(msg.Data); err == nil {
				msg.Data = decoded

func decodeBase64Data(data []byte) ([]byte, error) {
	data = bytes.Trim(data, "\"") //Need to trim the byte array
	decoded := make([]byte, base64.StdEncoding.DecodedLen(len(data)))
	_, err := base64.StdEncoding.Decode(decoded, data)

	if err != nil {
		return nil, err
	}

	return decoded, nil
}

If you do not try to decode the message the target application is receiving the message with quotes but we need to do this trimming to decode the base64 as far as I know. (More a C# guy :P)
Is this something we want to do?

@CarlosLanderas Just let me double-checked that I'm not mixing up things here. I thought that I've also observed this behavior with the Service Bus and not only with the Storage Queue. But I'll try to reproduce it with the Service Bus.
My last setup looked like the following:
Azure Blob Storage -> Event -> Storage Queue -> Local running Dapr app (Node.JS based). For the HTTP server, I was using Fastify instead of Express. And I was using the Azure Portal for uploading the blob file.

Hello @subesokun, thanks for your answer :)
I am using the events section in storage account. If I create an event grid subscriptions from Blob Storage to Azure Service Bus and a input binding I obtain the following payload in a golang dapr app:
{
   "topic":"/subscriptions/2a9be777-4217-4473-87cc-f539de44d0f3/resourceGroups/lande-we/providers/Microsoft.Storage/storageAccounts/teststorage123lande",
   "subject":"/blobServices/default/containers/container1/blobs/AD",
   "eventType":"Microsoft.Storage.BlobCreated",
   "eventTime":"2020-03-05T09:00:37.1101536Z",
   "id":"f1830947-c01e-00ce-47cc-f29df506f80f",
   "data":{
      "api":"PutBlockList",
      "clientRequestId":"d7286a2b-1b8c-417c-9228-740d6bdf302c",
      "requestId":"f1830947-c01e-00ce-47cc-f29df5000000",
      "eTag":"0x8D7C0E3ABF21047",
      "contentType":"application/octet-stream",
      "contentLength":518,
      "blobType":"BlockBlob",
      "url":"https://teststorage123lande.blob.core.windows.net/container1/AD",
      "sequencer":"000000000000000000000000000026FD0000000001603668",
      "storageDiagnostics":{
         "batchId":"60f44233-0006-0035-00cc-f2206f000000"
      }
   },
   "dataVersion":"",
   "metadataVersion":"1"
}

Ok, I think the problem is with Azure Storage Queues:
Binding input:
eyJ0b3BpYyI6Ii9zdWJzY3JpcHRpb25zLzJhOWJlNzc3LTQyMTctNDQ3My04N2NjLWY1MzlkZTQ0ZDBmMy9yZXNvdXJjZUdyb3Vwcy9sYW5kZS13ZS9wcm92aWRlcnMvTWljcm9zb2Z0LlN0b3JhZ2Uvc3RvcmFnZUFjY291bnRzL3Rlc3RzdG9yYWdlMTIzbGFuZGUiLCJzdWJqZWN0IjoiL2Jsb2JTZXJ2aWNlcy9kZWZhdWx0L2NvbnRhaW5lcnMvY29udGFpbmVyMS9ibG9icy9BRCIsImV2ZW50VHlwZSI6Ik1pY3Jvc29mdC5TdG9yYWdlLkJsb2JEZWxldGVkIiwiZXZlbnRUaW1lIjoiMjAyMC0wMy0wNVQxMzo1NDoyMC4wODg4ODQ4WiIsImlkIjoiOWEzZTY3NWUtNzAxZS0wMTIwLTQyZjUtZjJjOWQxMDYyYWQ3IiwiZGF0YSI6eyJhcGkiOiJEZWxldGVCbG9iIiwicmVxdWVzdElkIjoiOWEzZTY3NWUtNzAxZS0wMTIwLTQyZjUtZjJjOWQxMDAwMDAwIiwiZVRhZyI6IjB4OEQ3QzEwQ0I0MEY1RTEwIiwiY29udGVudFR5cGUiOiJhcHBsaWNhdGlvbi9vY3RldC1zdHJlYW0iLCJjb250ZW50TGVuZ3RoIjo1MTgsImJsb2JUeXBlIjoiQmxvY2tCbG9iIiwidXJsIjoiaHR0cHM6Ly90ZXN0c3RvcmFnZTEyM2xhbmRlLmJsb2IuY29yZS53aW5kb3dzLm5ldC9jb250YWluZXIxL0FEIiwic2VxdWVuY2VyIjoiMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDI2RkQwMDAwMDAwMDAxYTg0NmMwIiwic3RvcmFnZURpYWdub3N0aWNzIjp7ImJhdGNoSWQiOiI2MTgzMGNjMC0wMDA2LTAwMzUtMDBmNS1mMjIwNmYwMDAwMDAifX0sImRhdGFWZXJzaW9uIjoiIiwibWV0YWRhdGFWZXJzaW9uIjoiMSJ9
Decoded:
{"topic":"/subscriptions/2a9be777-4217-4473-87cc-f539de44d0f3/resourceGroups/lande-we/providers/Microsoft.Storage/storageAccounts/teststorage123lande","subject":"/blobServices/default/containers/container1/blobs/AD","eventType":"Microsoft.Storage.BlobDeleted","eventTime":"2020-03-05T13:54:20.0888848Z","id":"9a3e675e-701e-0120-42f5-f2c9d1062ad7","data":{"api":"DeleteBlob","requestId":"9a3e675e-701e-0120-42f5-f2c9d1000000","eTag":"0x8D7C10CB40F5E10","contentType":"application/octet-stream","contentLength":518,"blobType":"BlockBlob","url":"https://teststorage123lande.blob.core.windows.net/container1/AD","sequencer":"000000000000000000000000000026FD0000000001a846c0","storageDiagnostics":{"batchId":"61830cc0-0006-0035-00f5-f2206f000000"}},"dataVersion":"","metadataVersion":"1"}

Can we close this issue?

Yes sorry! It's merged. Closing

Sorry for the late feedback and thank you for the fix :) !


SDL2/SDL_GetWindowWMInfo() always returns 0

SDL2syswm_c.txt
compiling above example on AmigaOS4 I always get 0, under macOS returns 1.
Is such funcion implemented? IIRC in SDL1 there is SDL_GetWMInfo() and works fine.

https://wiki.libsdl.org/SDL2/SDL_GetWindowWMInfo
It seems that version information was not set correctly.
SDL_GetError() usually gives some extra information and there is also a serial debug version of the library.

adding SDL_VERSION(&wmInfo.version) make code working. THXaLOT


test: Make "Checks that monitor aggregation restricts notifications" reliable

The test is validating whether the ICMP packets used to check
connectivity between nodes can be found in the monitor output. The test
suffered from two issues which made it unreliable:

By using WithTimeout(), the impression is created that the search
operation is repeated until the timeout is hit. This has not been
accurate as the body() is using Expect() which will fail immediately
if the expected condition is not met. Fix this by making the body
return an error instead so the monitor output is checked repeatedly
until the timeout occurs.

The test expected a single ICMP notification in each direction.
However, the connectivity check will invoke PingCount ICMP requests.
PingCount defaults to 5. Change the test to require at least one
observed ICMP request. It is possible to require the exact PingCount
but then the monitor test has to be extended to make sure that the
monitor is in fact listening before the first ICMP request is being
sent. This commit chooses the simpler form by validating that the
notification pipeline works, the latter could be achieved by using
Hubble. This commit does not use Hubble to make it possible to
backport this commit if required.

test-me-please

Coverage increased (+0.004%) to 44.772% when pulling b4f503afc31bd7946b6a61b309098a031a48316c on pr/tgraf/ci-check-monitor into 86045f79ad6c3aeb104a0092d48c3691130b1699 on master.


<EMAIL_ADDRESS>hash check failed

Updating 'regscanner' (2.45 -> 2.46)
Downloading new version
regscanner-x64.zip (93.0 KB) [=========================================================================================================] 100%
Checking hash of regscanner-x64.zip ... ERROR Hash check failed!
App:         scoop-nirsoft/regscanner
URL:         https://www.nirsoft.net/utils/regscanner-x64.zip
First bytes: 50 4B 03 04 14 00 02 00
Expected:    6ad09ab86b3b674f16585081eec01f97b15609fddaf7be8acb76fe15caa07de2
Actual:      f5a5b276a55b837ff16bdc918734b9358fcd54073b6428ba786471ef39860101

Sorry i didn't notice this earlier.
For some reason, my server fails to update the bucket for the last couple weeks. I suspect it has been IP-banned from nirsoft.net. I'll contact them.

Apparently nirsoft's firewall blocks when there are too many TCP connections open. IDK how the updater reached that threshold, but he kindly unblocked me. Things are back to normal.


Image width and height are not equal

It seems that the code can't calculate the metric on the images with unequal width and height, can it be expanded to calculate images of various sizes?

I think it should work out of the box
model = models.PerceptualLoss(model='net-lin', net='vgg', use_gpu=False, spatial=False)

H,W = 179, 32
dummy = torch.zeros(1,3,H,W)
print(model(dummy, dummy).item())

Thanks for your answer, it does work in the example you provided. After my testing as the test_network.py script settings, I found that this problem is mainly caused by the setting of {net/spatial} parameter.
model = models.PerceptualLoss(model='net-lin', net='alex', use_gpu=False, spatial=True)
H,W = 160, 64
dummy = torch.zeros(1,3,H,W)

the error information as follow:
RuntimeError: The size of tensor a (61) must match the size of tensor b (58) at non-singleton dimension 3

Got it. I pushed a change to do resizing in both dimensions. Let me know if it works. Keep in mind the features in each layer will not necessarily be well-aligned in these cases

The issue still persists for me. I was trying compute_dists_pair.py and got the same error when the image height and width were different but it all worked fine when I resize them to have same height and weight.
The error looks like this:
RuntimeError: The size of tensor a (13) must match the size of tensor b (15) at non-singleton dimension 3

The two images must be in the same size


how to use PhotoView in ImageSwitcher?

thank you very much.

You probably just want to perform an alpha fade from one image to another and not use the actual ImageSwitcher widget


⚠ ClamAV has degraded performance

In d7af1bd, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 441 ms

Resolved: ClamAV performance has improved in 5f5681d.


[Constraint Solver] Try defaultable bindings even if other bindings exist

What's in this pull request?
This pull request ensures that the constraint solver tries defaultable bindings even when other bindings exist, because those bindings might not actually work out anyway.
Resolved bug number: (rdar://problem/17444930)
The resolved radar had all of its tests already reflected in our testsuite.

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci please smoke test and merge

Not sure what happened. Any idea, @shahmishal ?

/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/swift/utils/build-script--preset=buildbot_linux_1404 install_destdir=/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/swift-nightly-install installable_package=/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/PR-TEST-ubuntu14.04.tar.gz
/tmp/hudson4183501763193310298.sh: line 32: /home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/swift/utils/build-script--preset=buildbot_linux_1404: No such file or directory
Build step 'Execute shell' marked build as failure


Update room info

closes #363

Haha, it looks so good on the design but it's so bad in reality:

Brilliant... :)

@tbergq Could you please improve this elements align?

Should be dooable

@mrtnzlml Alignment improved


Datagrid background

I set the backgroundcolor white for the datagrid. This works well for rows with content, but if i have space with no content the color is shown gray? In the xamarin version this space was white too. Is it a bug in the maui version?

which platform are you facing with the problem?

Multiple bugs exist in the current stable version of MAUI
https://github.com/dotnet/maui/issues/9135
https://github.com/dotnet/maui/issues/14966
https://github.com/dotnet/maui/issues/15553
https://github.com/dotnet/maui/issues/15592

The sensible-layout PR may have fixed this. https://github.com/akgulebubekir/Maui.DataGrid/pull/121


New update

i want in new update prefix & slash commands

NanoSpacePlus only use Slash Commands. Its clearly said in About & README section.
If u wanna a prefix one there is NanoSpace.
And if u wanna NanoSpacePlus support prefix then make ur own. Coz Adivise would not doing it.

Hope u'll understand. Thank You


bars off the chart

Expected Behaviour
Actual Behaviour
Steps to Reproduce:

NOTE: Add a GIF/Screenshot if required.
Frappé Charts version:
const { Chart } = require("frappe-charts/dist/frappe-charts.min.cjs.js");

const data = {
  labels: ["18:00", "19:00", "20:00", "21:00"],
  datasets: [
    {
      chartType: "bar",
      name: "prod",
      values: [40, 50, 30, 60]
    },
    {
      chartType: "bar",
      name: "err",
      values: [10, 10, 10, 0]
    },
    {
      chartType: "bar",
      name: "stop",
      values: [10, 0, 20, 0]
    }
  ]
}

const el = document.querySelector("body > div");

new Chart(el, {  // or a DOM element,
  title: "status preview",
  data,
  type: "axis-mixed",
  colors: ["green", "red", "yellow"],
  barOptions: {
    stacked: true
  }
  // axisOptions: {
  //   xAxisMode: "tick",
  //   yAxisMode: "tick"
  // }
})

just by refactoring the datasets:
  datasets: [
    {
      chartType: "bar",
      name: "Marcha",
      values: [40, 50, 70, 60]
    },
    {
      chartType: "bar",
      name: "Error",
      values: [50, 10, 10, 20]
    },
    {
      chartType: "bar",
      name: "Parada",
      values: [10, 40, 20, 20]
    }
  ]

So, adding
  yRegions: [{ label: "Minutes", start: 0, end: 60 }]

it kinda fixes...

This is the final result
const { Chart } = require("frappe-charts/dist/frappe-charts.min.cjs.js");

const data = {
  labels: ["18:00", "19:00", "20:00", "21:00"],
  datasets: [
    {
      chartType: "bar",
      name: "Production",
      values: [40, 50, 30, 60]
    },
    {
      chartType: "bar",
      name: "Error",
      values: [10, 10, 10, 0]
    },
    {
      chartType: "bar",
      name: "Stopped",
      values: [10, 0, 20, 0]
    }
  ],
  yRegions: [{ label: "Minutes", start: 0, end: 60 }]
}

const el = document.querySelector("body > div");

new Chart(el, {  // or a DOM element,
  title: "Status report",
  data,
  type: "axis-mixed",
  colors: ["green", "red", "yellow"],
  barOptions: {
    stacked: true
  }
})

is this a bug? asking a OP to close if needed

Hmm, I'm seeing something a bit similar on a mixed-axis graph.

Can you share a codepen or codesandbox?

Same here:

{
    "title":"Test",
    "data":{
        "labels":["2021-01","2021-02","2021-03","2021-04","2021-05","2021-06","2021-07","2021-08"],
        "datasets":[
            {"name":"Test","chartType":"bar","values":[206,281,217,207,210,198,257,200]}
        ]
    }
}

For me looks like adding (global) "type": "bar" fixes the issue, but I must say that it worked without it for a while (with other datasets).


Splitted react-jsx into react and jsx-to-markup

This is a complete rewrite of the react-jsx transformer.
There is no API break and the change offers to create
common.js modules from patterns without rendering
static markup.

Don't merge until tested with current projects.

The compile queue doesn't use browserify/babelify yet so Stage-0-Features don't work.
An attempt to chain the jsx content through browserify before taking it to react react-to-markup didn't work out either.

@Dangoo what do you mean by 'don't use browserify/babelify'? The new react transformer just create a valid react component from a pattern.
The react-to-markup transform uses babel-core to transpile your code. Maybe there is some config for the transformer missing so stage-0 could be enabled. But it shouldn't be enabled by default.

In the current implementation stage 2 is the default for babel and could be easily overwritten by adding a transforms.js in the mypatternate/configuration/patternplate-server folder and configure the transformer options by using the same tree structure as in the patternplate-server. This doesn't work anymore with the new jsx-transformer.

@Dangoo The latest commit should fix the missing configuration and enable stage-0 on request.

@Dangoo, @levito, @opatut, @marionebl Please check this server pull against your projects so this does not break anything.
@Dangoo: You should be able to use any import/require from node_modules in your jsx pattern now.

Enable stage 0 is required but does not work since whitelisting blocks stage0 feature enabling.

@Dangoo: Please recheck. You have to set the stage-0 opts for the react transformer as well as for the react-to-markup transformer.

@KnisterPeter: I get the following error in patterns which depend on other patterns:
error: [patternplate-server] Error in "atoms/avatar" during transform "react" of "/Users/.../index.jsx": unknown: Unexpected token (16:0)
debug: [patternplate-server] SyntaxError: unknown: Unexpected token (16:0)
  14 | </div>
  15 |
> 16 | );
     | ^
  17 |
  18 | 	}
  19 | }

@levito: Should be fixed. Please retest

@KnisterPeter the above error is fixed, but a previous feature is missing. Originally, I could set the context option in an @environments pattern:
    "react-jsx": {
      "opts": {
        "context": {
          "foo": "bar"
        }
      }
    }

Now this.context.foo is undefined.
I also tried setting it for "react", this doesn't work either.

@levito I've added a config like this to simulate this hack. But there is a breaking change required on the configuration.
Please update your config to match this structure:
"react-jsx": {
  "opts": {
    "globals": {
      "context": {
        "foo": "bar"
      }
    }
  }
}

@levito, @Dangoo, @opatut To test this pull requests you could also do 'npm install patternplate-server@beta' (or even 'npm install patternplate@beta')


Tests/LibWasm: Mark two static functions "static inline"

-Wmissing-declarations would complain about these.

Static is enough, no need for inline. This ain't C.

(...static would be enough in C too, but just inline is often spelled static inline in headers that are shared between c and c++)

😭 no bully Cbrain


Update azure-operator-service-manager-overview.md

@lnyswonger - you should submit author changes via the private repo. Thanks

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.
We'll close this PR. Thank you.


Added Lielow

Added Lielow by Michael Amundsen and Alek Erickson.

Thanks! I will take a look when I can.


Implement Audience, Commands now use the custom User object

User now implements ForwardingAudience.Single (to represent a single Audience) & Identified (which could be useful idk)

Channel now implements ForwardingAudience

commands now use the custom User object as the command sender (User == CommandSender, ChatUser == Player, ConsoleUser == ConsoleCommandSender).

With the addition of the ConsoleUser, I've had to move around some of the User stuff to make it work correctly.

ChatUser has been moved to the API module as an interface, and we now have ChatUserImpl as our backing implementation
player() and lastMessagedUser() methods from User have been moved to the ChatUser interface

Other changes:

relocated dependencies
handled offline players more gracefully, as before calling user.lastMessagedUser().player(), could possibly cause an NPE. So now we remove the lastMessagedUser when they leave the server. if this is to ever throw, something has gone horribly wrong.

We should probably change the events to use ChatUser instead of Player.


bug: Error creating subscription with existing management group

Community Note

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

Versions

Please paste the output of terraform version command from within the initialized directory:
terraform v1.5.1

Please enter the module version that you are using:
v3.2.0

Description
I'm trying to use the module to only create subscriptions. I have an existing management group. The SPN I'm using has owner permissions to the management group id. Here is my code:
module "lzvending" {
  source = "/path/to/code/github/terraform-azurerm-lz-vending"

  location = "uswest2"

  subscription_alias_enabled                        = true
  subscription_alias_name                           = test
  subscription_billing_scope                        = "/providers/Microsoft.Billing/billingAccounts/xxxx/enrollmentAccounts/yyyyy"
  subscription_display_name                         = test
  subscription_management_group_association_enabled = true
  subscription_management_group_id                  = production
  subscription_workload                             = "Production"
}

Output of terraform apply
module.lzvending.module.subscription[0].azurerm_subscription.this[0]: Creating...
╷
│ Error: creating new Subscription (Alias "test"): subscriptions.SubscriptionsClient#AliasCreate: Failure sending request: StatusCode=0 -- Original Error: Code="BadRequest" Message="Specified method is not supported."
│
│   with module.lzvending.module.subscription[0].azurerm_subscription.this[0],
│   on /path/to/code/github/terraform-azurerm-lz-vending/modules/subscription/main.tf line 2, in resource "azurerm_subscription" "this":
│    2: resource "azurerm_subscription" "this" {
│
╵

Steps to Reproduce

clone this repo
authenticate as the spn that has owner permissions
terraform init, plan, and apply

Screenshots

Additional context

Hi, we test this scenario here:
https://github.com/Azure/terraform-azurerm-lz-vending/blob/main/modules/subscription/testdata/TestDeploySubscriptionAliasManagementGroupValid/main.tf
It works in the test framework so we will need to understand what's different.
In your example, you seem to have string values presented without the double quotes. Is this how you've done it in the real code?

I think I've spotted the problem.
The management group id is the last segment of the resource id, not the whole thing.
If you are using the AzureRM data source then select the .name property instead of .id.

As we tried to explain here but clearly didn't do a good enough job 😄
https://github.com/Azure/terraform-azurerm-lz-vending#input_subscription_management_group_id

I think I've spotted the problem.
The management group id is the last segment of the resource id, not the whole thing.
If you are using the AzureRM data source then select the .name property instead of .id.

data "azurerm_management_group" "this" {
  display_name = "production"
}

module "lzvending" {
  source = "/path/to/code/github/terraform-azurerm-lz-vending/modules/subscription"

  subscription_alias_enabled                        = true
  subscription_alias_name                           = "test"
  subscription_billing_scope                        = "/providers/Microsoft.Billing/billingAccounts/xxxx/enrollmentAccounts/yyyyy"
  subscription_display_name                         = "test"
  subscription_management_group_association_enabled = true
  subscription_management_group_id                  = data.azurerm_management_group.this.name
  subscription_workload                             = "Production"
}

Unfortunately, it doesn't seem to make a difference. I also added quotes around the strings with no change in behavior.

Can I clarify, are you specifying the correct billing scope?
I presume you are replacing the xxxxxx and yyyyyy with the actual values from your Enterprise Agreement?

Also I noticed that you are not calling the submodule directly, was this intentional?
Normally we recommend calling the parent module.

I think I found the issue! (or at least now I'm able to create the subscriptions). I had to setup a data source for the MCA scope. Once I did this, it ended up working. I also specified the parent module (which required a subscription). Code here:
data "azurerm_billing_mca_account_scope" "this" {
  billing_account_name = "xxx"
  billing_profile_name = "yyy"
  invoice_section_name = "zzz"
}

data "azurerm_management_group" "this" {
  display_name = "production"
}

module "lzvending" {
  source = "/path/to/code/github/terraform-azurerm-lz-vending"

  location = "westus2"

  subscription_alias_enabled                        = true
  subscription_alias_name                           = "test"
  subscription_billing_scope                        = data.azurerm_billing_mca_account_scope.this.id
  subscription_display_name                         = "test"
  subscription_management_group_association_enabled = true
  subscription_management_group_id                  = data.azurerm_management_group.this.name
  subscription_workload                             = "Production"
}

Thank you for your help @matt-FFFFFF

Glad you sorted it!


hangs browser (chrome) on higher resolution video

web browser (google chrome Version 54.0.2840.50 beta-m) frequently stops responding when streaming video of higher resolution (640x480+). video plays fine at 320x240. CPU is about 0.3%. Guessing it's a buffer issue - can't debug it as browser is hung.

I managed to fix it by adding
if (n > ZIG_ZAG.length)
break;
into the decodeBlock while(true) loop. I mean fix it as in it doesn't crash the browser but sometimes the feed gets corrupted.

Thank you for this issue!
I often encounter this kind of situation too.

Does this issue still persist in the current version?


Emulate Delays in Sensor Readings

Purpose

Adding artificial delays adds to sensor realism in the simulation.
Description

The sensor classes should be updated to support artificial delays. In particular, we should be able to observe the following:
Suppose we have a publish period of 0.5 seconds, and a delay period of 0.8 seconds. On the first publish, 0.5 seconds have passed, but the sensor reading should not be updated because of "delays". On the second publish, 1.0 seconds have passed, and you should now update the sensor reading since we have exceeded the delay period. The delay period should be updated according to some policy (i.e. fixed, random, etc.)

When testing, do not measure real time. Rather look to go polling cycle by polling cycle.


Too slow and cant change ip

Hi it seems to be too slow in changing ip and trying passwords and way to speed  up?
It tries to change ip thousand times and and tries again and again on 1 single password.
Help plz
Gonna try A 10000 password list
App wat active for more than 2 days just tried 1200 password

this project look like outdated so it could be fixed and never work again


[Question] Why doesn't work disable cascade with CascadeAction.NONE?

Hi,
I have 3 entities in my project and they looks like with this:
@Table( name = "Task" )
@Entity( name = "TaskEntity" )
public interface ITaskEntity extends Persistable {
    @Key @Generated
    int getId();

    String getTitle();

    @ForeignKey
    @OneToOne
    ICycleEntity getCycle();
}

@Table( name = "Cycle" )
@Entity( name = "CycleEntity" )
public interface ICycleEntity extends Persistable {
    @Key @Generated
    int getId();

    String getName();

    @Convert( ListOfLongConverter.class )
    List<Long> getIncrements();

    @ForeignKey
    @OneToOne
    IAlarmEntity getAlarm();

    @OneToOne( mappedBy = "cycle" )
    ITaskEntity getTask();
}

@Table( name = "Alarm" )
@Entity( name = "AlarmEntity" )
public interface IAlarmEntity extends Persistable {
    @Key @Generated
    int getId();

    @Convert( CalendarConverter.class )
    Calendar getCalendar();

    @OneToOne( mappedBy = "alarm" )
    ICycleEntity getCycle();
}

In my code, to create a Task with dataStore.insert( task ), first I create a Cycle with dataStore.insert( cycle ) and an Alarm, with the method insert() too. But, when I checked the log what I saw it was:
I/requery: beforeExecuteUpdate sql: create table Alarm (id integer primary key autoincrement not null, calendar varchar(255))
I/requery: afterExecuteUpdate 0
I/requery: beforeExecuteUpdate sql: create table Cycle (id integer primary key autoincrement not null, alarm integer, increments varchar(255), name varchar(255), foreign key (alarm) references Alarm (id) on delete cascade)
I/requery: afterExecuteUpdate 0
I/requery: beforeExecuteUpdate sql: create table Task (id integer primary key autoincrement not null, cycle integer, title varchar(255), foreign key (cycle) references Cycle (id) on delete cascade)
I/requery: afterExecuteUpdate 0
I/ALERT: On Insert Alarm
I/requery: beforeExecuteUpdate sql: insert into Alarm (calendar) values (?)
I/requery: afterExecuteUpdate 1
I/ALERT: On Insert Cycle
I/requery: beforeExecuteUpdate sql: insert into Alarm (calendar) values (?)
I/requery: afterExecuteUpdate 1
I/requery: beforeExecuteUpdate sql: insert into Cycle (alarm, increments, name) values (?, ?, ?)
I/requery: afterExecuteUpdate 1
I/ALERT: On Insert Task
I/requery: beforeExecuteUpdate sql: insert into Alarm (calendar) values (?)
I/requery: afterExecuteUpdate 1
I/requery: beforeExecuteUpdate sql: insert into Cycle (alarm, increments, name) values (?, ?, ?)
I/requery: afterExecuteUpdate 1
I/requery: beforeExecuteUpdate sql: insert into Task (cycle, title) values (?, ?)
I/requery: afterExecuteUpdate 1

So, I researched and I found that we can use the annotation option @OneToOne( cascade = CascadeAction.NONE ), because I thought that it was the problem. The code changed like this:
// In Task class
   [...]
    @ForeignKey
    @OneToOne( cascade = CascadeAction.NONE )
    ICycleEntity getCycle();
   [...]

// In Cycle class
   [...]
    @ForeignKey
    @OneToOne( cascade = CascadeAction.NONE )
    IAlarmEntity getAlarm();

    @OneToOne( mappedBy = "cycle" )
    ITaskEntity getTask();
   [...]

// In Alarm class
   [...]
    @OneToOne( mappedBy = "alarm" )
    ICycleEntity getCycle();
   [...]

But, after run, the result was the same.
What did I do wrong? I forgot something?
Best regards

What's your expected outcome for this change? If it's about the order of insertion, that order has to be maintained because of the foreign key relation ships between your entities.

I expected that, in the end of the operation, had only one entity of each type. But, the log shown that there are 3 Alarms, 2 Cycles and 1 Task.
For default, Requery use CascadeAction.SAVE. What I understood is that when I insert an entity with another entity associated, the Requery will persist the two entities, in CascadeAction.SAVE. With the CascadeAction.NONE I expected that only the entity I insert would be persisted.
When I insert a Task the effect is a insertion of the 2 others types, but I want insert only a Task.
The same to the Cycle. When I insert a Cycle I want persist only the Cycle, but an Alarm is persisted too.
I expected that the log would show me something like that:
I/requery: beforeExecuteUpdate sql: create table Alarm (id integer primary key autoincrement not null, calendar varchar(255))
I/requery: afterExecuteUpdate 0
I/requery: beforeExecuteUpdate sql: create table Cycle (id integer primary key autoincrement not null, alarm integer, increments varchar(255), name varchar(255), foreign key (alarm) references Alarm (id) on delete cascade)
I/requery: afterExecuteUpdate 0
I/requery: beforeExecuteUpdate sql: create table Task (id integer primary key autoincrement not null, cycle integer, title varchar(255), foreign key (cycle) references Cycle (id) on delete cascade)
I/requery: afterExecuteUpdate 0
I/ALERT: On Insert Alarm
I/requery: beforeExecuteUpdate sql: insert into Alarm (calendar) values (?)
I/requery: afterExecuteUpdate 1
I/ALERT: On Insert Cycle
I/requery: beforeExecuteUpdate sql: insert into Cycle (alarm, increments, name) values (?, ?, ?)
I/requery: afterExecuteUpdate 1
I/ALERT: On Insert Task
I/requery: beforeExecuteUpdate sql: insert into Task (cycle, title) values (?, ?)
I/requery: afterExecuteUpdate 1

I understood the effects of Cascade wrong? If yes, what I must do to have the results that I expect?
Thanks for the fast reply!

Have you associated these objects to each other? sounds like they were not. If the objects are associated you only need to insert the main entity once (with the default cascade mode)

The problem is exactly  this. I want create a Task. This object is associated with a Cycle which, in turn, is associated with an Alarm. I need configure it before to associated it this with the Cycle. The same thing to the Cycle and Task.
The process is:
(1)create Alarm -> (2)configure Alarm -> (3)insert Alarm ->
(4)create Cycle -> (5)configure Cycle -> (6)associate Cycle with Alarm -> (7)insert Cycle ->
(8)create Task -> (9)configure Task -> (10)associate Task with Cycle -> (11)insert Task.
The problem:
In step (7) a Cycle and another Alarm were persisted, not only the Cycle. In step (11) a Task was insert, but another Cycle and Alarm too. In the end of the process I have: 1 Task, 2 Cycles and 3 Alarms, because cascade effect. But I want only one of the entities. In step (7) and (11), because of cascade, I end up persisting a Alarm and a Cycle again.
I thought that I can insert a Task and, with default cascade mode, a Cycle and Alarm are persisted too, like you said. And, after that, I would update this entities with the configurations, but, if I did this I must change the code.
So, I saw that Requery has how to disable the cascade mode, and it would enable me to insert and associate the entities manualy, that would cost me less work.
The change what I did in code was what I said: I added the option cascade = CascadeAction.NONE in annotation @OneToOne. But it didn't work. I did something wrong or I forgot something?

@npurushe, it will be great! Thank you for the attention.

1.3.2 has this change thanks

Wow!
Very fast! Thank you for the support!


Use GraphQL to determine if a user is new.

For some reason the /repos/ORG/REPO/commits?author=AUTHOR endpoint hasn't been working to see if a user has posted any commits (I don't know why). This switches it to use GraphQL which seems to be more reliable in my testing. AFAICT, the query costs 1 point, so it shouldn't be too expensive.
I could instead revert 077cdf8b11e0aa10d2cdfad655f14bbb0a4532b9 and use the /search endpoint instead. However, that endpoint has some issues, such as not working on forks (mainly a problem for testing), and tight rate limits (30/minute, which is very unlikely to be hit, but I think is very small and could compete with other triagebot handlers).
I decided to not use cynic for this and instead just issue JSON to the endpoint directly. I can build the cynic types, but I'm finding using cynic to be awkward. For one-off queries like this, it generates a dozen types, and it is also a pain to iterate and change the query. If you want to make any changes, you have to find the original query, find and set up the cynic generator, and regenerate the types, and then copy all that stuff back in and adjust all the code using it. Cynic is better if you are actually using the returned values, but in this case there is just one value that is needed in one place.
I'm fine with doing either alternative (use /search or use cynic), just let me know. I just find this approach a little more reliable and easier to write and iterate on.
Fixes #1689

@Mark-Simulacrum Just checking if you had any questions on this?

My previous approval is still good here - do we still have the merge limitations, or can you go ahead and merge?

Hm, I'm not entirely sure why I can't merge. It says I am not authorized. I know that GitHub does not allow an author to approve their own PR, but I've had situations on other repos where after someone else approves it, the author is allowed to merge it. But maybe the branch protection rule in this repo is slightly different. Unfortunately GitHub doesn't provide any information to help debug an authorization problem, and I don't have permissions to inspect the permissions in this repo.

Yeah, I remembered since then - we unblocked merges for a bit by manually adding the triagebot team to branch protections, but that broke sync-team since it doesn't know what that entry means. https://github.com/rust-lang/team/blob/master/repos/rust-lang/triagebot.toml could have branch protections dropped potentially...


Could partial_ratio support Levenshtein.normalized_similarity?

rapidfuzz  3.9.6 and python 3.10.
I have carefully read the rapidfuzz docs and made tests. I find: partial_ratio use Indel.normalized_similarity.
Could partial_ratio also support Levenshtein.normalized_similarity? Maybe default to use Indel.normalized_similarity, but we can choose to use Levenshtein.normalized_similarity.
In my use case, I indeed need partial_ratio to use Levenshtein.normalized_similarity.
thanks!!
from icecream import ic
from rapidfuzz import fuzz
from rapidfuzz.distance import Levenshtein, Indel

a = '34cdef16z'
c = '09cdef78'
ic(fuzz.partial_ratio(a, c))
ic(fuzz.partial_ratio_alignment(a, c))
ic(fuzz.ratio(a[0:6], c))
ic(Indel.normalized_similarity(a[0:6], c) * 100)
ic(Levenshtein.normalized_similarity(a[0:6], c) * 100)

ic| test.py:25 in <module>- fuzz.partial_ratio(a, c): 57.14285714285714
ic| test.py:26 in <module>- fuzz.partial_ratio_alignment(a, c): ScoreAlignment(score=57.14285714285714, src_start=0, src_end=6, dest_start=0, dest_end=8)
ic| test.py:27 in <module>- fuzz.ratio(a[0:6], c): 57.14285714285714
ic| test.py:28 in <module>- Indel.normalized_similarity(a[0:6], c) * 100: 57.14285714285714
ic| test.py:29 in <module>- Levenshtein.normalized_similarity(a[0:6], c) * 100: 50.0

In theory we could support this, but this comes with a couple of issues:

partial_ratio is used in a lot of the "combined" algorithms like WRatio. So it's not completely clear what to do about them
would this only allow Indel and Levenshtein which seems a bit arbitrary or more metrics? For more metrics it gets a lot more complex to handle things like the different kinds of normalizations
This has a couple of optimizations to keep the sliding window algorithm remotely fast by skipping some unneeded calculations. This doesn't work for the generic case though. Probably this could have a generic fallback, but it would likely need optimized versions for algorithms where this is possible.

One more possible setting could be whether the sliding window allows for shorter substrings at the start / end of the longer string.
Not completely sure whether this should be added under a different name either.
I assume a generic implementation shouldn't be too much work and optimized versions could be added over time. Still not sure when I will get around to it though.

thanks a lot for maxbachmann.
You have a global view on this issue!
As Indel and Levenshtein are very similar, I think it would be easier only support Indel and Levenshtein in partial_ratio, to save your time. For me, I hope to only use Levenshtein in most NLP process.


Out of Memory

I have encountered an issue downloading PDFs and running out of memory.  The stack trace is below.
The api is called with:
envelopesApi::getDocument(<accountId>, <envelopeId>, 'combined', null, <callback>)

The memory issue occurs when the ApiClient attempts to deserialize the PDF which has a returnType of Object. Therefore, a potential fix for this issue would be to check if the return type is not Object because the error occurs when the if statement attempts to do Object.keys(data) which is the response.body of the PDF.
    if (returnType !== Object && (data == null || !Object.keys(data).length)) {
      // SuperAgent does not always produce a body; use the unparsed response as a fallback
      data = response.text;
    }

STACK TRACE
--- Last few GCs --->
[emulators] >
[emulators] >  [36403:0x102654000]    10254 ms: Mark-sweep 106.4 (133.6) -> 101.9 (119.1) MB, 10.6 / 0.0 ms  (+ 31.7 ms in 37 steps since start of marking, biggest step 2.5 ms, walltime since start of marking 49 ms) (average mu = 0.993, current mu = 0.995) finalize incr[36403:0x102654000]    11878 ms: Mark-sweep 265.0 (278.6) -> 262.3 (304.1) MB, 16.5 / 0.0 ms  (+ 5.4 ms in 2 steps since start of marking, biggest step 4.1 ms, walltime since start of marking 1162 ms) (average mu = 0.991, current mu = 0.986) allocation fa
[emulators] >
[emulators] >  <--- JS stacktrace --->
[emulators] >
[emulators] >  ==== JS stack trace =========================================
[emulators] >
[emulators] >      0: ExitFrame [pc: 0x13f23e5dbe3d]
[emulators] >  Security context: 0x14b7e619e6e9
[emulators] >      1: keys [0x14b7e61851a1](this=0x14b7e6184639 <JSFunction Object (sfi = 0x14b7ef78e301)>,0x14b74ad07191 <Very long string[22711550]>)
[emulators] >      2: deserialize [0x14b717ffaef1] [/Users//v//packages//functions/node_modules/docusign-esign/src/ApiClient.js:343] [bytecode=0x14b7a371e8c9 offset=66](this=0x14b7a705a381 <exports map = ...
[emulators] >
[emulators] >  FATAL ERROR: invalid table size Allocation failed - JavaScript heap out of memory
[emulators] >   1: 0x10003c597 node::Abort() [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >   2: 0x10003c7a1 node::OnFatalError(char const*, char const*) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >   3: 0x1001ad575 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >   4: 0x100579242 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >   5: 0x1006e4e81 v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Rehash(v8::internal::Handlev8::internal::OrderedHashSet, int) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >   6: 0x1006e4175 v8::internal::OrderedHashSet::Add(v8::internal::Handlev8::internal::OrderedHashSet, v8::internal::Handlev8::internal::Object) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >   7: 0x10065a31d v8::internal::KeyAccumulator::AddKey(v8::internal::Handlev8::internal::Object, v8::internal::AddKeyConversion) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >   8: 0x10050e709 v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastStringWrapperElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)9> >::CollectElementIndices(v8::internal::Handlev8::internal::JSObject, v8::internal::Handlev8::internal::FixedArrayBase, v8::internal::KeyAccumulator*) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >   9: 0x10065c2b7 v8::internal::KeyAccumulator::CollectOwnElementIndices(v8::internal::Handlev8::internal::JSReceiver, v8::internal::Handlev8::internal::JSObject) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >  10: 0x10065b5ae v8::internal::KeyAccumulator::CollectOwnKeys(v8::internal::Handlev8::internal::JSReceiver, v8::internal::Handlev8::internal::JSObject) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >  11: 0x10065aa4b v8::internal::KeyAccumulator::CollectKeys(v8::internal::Handlev8::internal::JSReceiver, v8::internal::Handlev8::internal::JSReceiver) [/Users//.nvm/versions/node/v10.15.3/bin/node]
[emulators] >  12: 0x10065a103 v8::internal::KeyAccumulator::GetKeys(v8::internal::Handlev8::internal::JSReceiver, v8::internal::KeyCollectionMode, v8::internal::PropertyFilter, v8::internal::GetKeysConversion, bool, bool) [/Users//.nvm/versions/node/v10.15.3/bin/node]

Hi @mrudling DocuSign has a size limit for documents, what is the size of your PDF? https://developers.docusign.com/esign-rest-api/guides/resource-limits

Hi,
It is 22mb.  It was created and sent to docusign using this library, then failed on fetching it.

Hi,
I have exactly the same problem, so I would extremely vote to merge given fix to master and release new version as soon as possible.
Thanks

I've duplicated the problem internally and have filed internal bug report DCM-4415

@mrudling this issue has been resolved in versions v5.8.1 and v4.10.1


Persist tags on ensureResourceGroup

Which issue this PR addresses:
Fixes this
What this PR does / why we need it:
Currently, if we PUCM a cluster with tags set on the cluster resource group, it will remove them.  We do allow tagging of the clsuter resource group, so we shouldn't be removing these.
Test plan for issue:
Unit tests & tested locally.
Is there any documentation that needs to be updated for this PR?
no,

:1st_place_medal:


Update parameters.json to v8.1.0

We are using as a list of legal keys.

I'm not sure how can we have parameters.json as a dependency. We could consider adding https://github.com/imgix/imgix-url-params as a git submodule here, but we still would need to keep it up to date while publishing to rubygems.org.


Error on parsing regExp as String

If you try to parse a regExp within a string it returns a error.
for example:
{"regExp":"\d+"}

Pretty sure \d is not a valid escape sequence; see https://jsonlint.com/. You need \\d for a literal backslash.


core/monit: allow theme override for monit widget

closes opnsense/plugins#937

@fichtner thanks for finding it, I've fixed it.

merged manually with minor consistency changes, thanks <3


fix: createUser, createGroup and addUserToGroup do not support Busybox

Issue #, if available:
Description of changes:
Why is this change necessary:
How was this change tested:

[ ] Updated or added new unit tests.
[ ] Updated or added new integration tests.
[ ] Updated or added new end-to-end tests.
[ ] If my code makes a remote network call, it was tested with a proxy.

Any additional information or context required to review the change:
Documentation Checklist:

[ ] Updated the README if applicable.

Compatibility Checklist:

[ ] I confirm that the change is backwards compatible.
[ ] Any modification or deletion of public interfaces does not impact other plugin components.
[ ] For external library version updates, I have reviewed its change logs and Nucleus does not consume
any deprecated method or type.

Refer to Compatibility Guidelines for more information.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Mirrorxxi
Please rebase your change, then we should be able to merge this.
@shaguptashaikh please review.

Can you provide some details here about what manual testing you performed?

Hi @shaguptashaikh, here are some records for manual test.

ggc_user and ggc_group can be created & ggc_user can be added to ggc_group in Alpine os by nucleus now:
https://user-images.githubusercontent.com/111258711/196684073-8f91b3ba-d811-4500-b499-0e2a85596562.mp4

ggc_user and ggc_group can be created & ggc_user can be added to ggc_group in Ubuntu os by nucleus now:
https://user-images.githubusercontent.com/111258711/196684124-83194337-c54e-491e-99f5-2f7fd5491786.mp4

Below is record to show above commands are not supported in Alpine in the past:
https://user-images.githubusercontent.com/111258711/196684188-c637763b-e770-485a-b58d-768092e20d1a.mp4
Use below command to start Alpine os and then install nucleus:
docker pull alpine
docker images
docker run -dit  -v /gginstall:/gginstall  --name alpine-test alpine
docker exec -it alpine-test /bin/sh


Smart battery data not logged

When looking at the battery data of different logs I realized that the smart battery specific data is not logged correctly.
Different entries ('capacity', 'cycle_count', 'serial_number', 'average_time_to_empty', 'run_time_to_empty') in 'battery_status' store an array of zeros.
The following log shows this behavior for example:
https://logs.px4.io/plot_app?log=d9bf3e69-ecc5-478c-8713-23581efa84ad

You need to set BAT_SOURCE to 1

Also, make sure you are starting the smart battery driver in your startup script.
e.g batt_smbus -X start
This will start the driver on PX4_I2C_BUS_EXPANSION.

Currently it supports starting on PX4_I2C_BUS_EXPANSION and PX4_I2C_BUS_ONBOARD.
@dagar do I need to add options for other i2c buses depending on the hardware?

For now I think we'll need to copy what other i2c drivers do (try all the buses). See the differential pressure sensors as an example.
As long as the driver can probe and fail gracefully (quickly) you can have it try to start everywhere by default. See rc.sensors for similar examples.


Recommendations for multi-node training of a 7B model with RL

If I want to run multi-node 7BRL training experiments, what is the recommended configuration? Should actor_num_gpus_per_node be set to multiple 7s?
Is it also necessary to launch in the same way as the 70B model, using the following command:
source configs/beaker_configs/ray_node_setup.sh && python open_instruct/ppo_vllm_thread_ray_gtrl.py?

Hi @zhudefa, 7 is fine for a single node setting: we use 7 gpus for training and 1 gpu for inference. Its usage is like this:
--actor_num_gpus_per_node 7 8 8 8 meaning using 7 gpus in the first node to do training and 8 gpus in the next 3 nodes to do training.

Is it also necessary to launch in the same way as the 70B model, using the following command:
source configs/beaker_configs/ray_node_setup.sh && python open_instruct/ppo_vllm_thread_ray_gtrl.py?

yes. the ray_node_setup.sh  setups the multi node ray stuff to connect to the main ray head node.


no more popup warnings :(

I use to get this nice popup warnings when I would try to save a file with critical errors. I upgrade prettier-vscode and I did change a few settings (I'm not sure what, but I no longer get the nice popup warnings.  When there's error the file would save but prettier will not reformat the code.  Pretter only reformats the code when there are areas.  Although this too is a nice feature, I miss the popups directing me to the error.  How can I get the popup warning back?

The popups were annoying for many users. There is a new output channel where the errors are posted. There is also a statusbar item which indicates if there are errors or not.
Output channel:

Statusbar item:

lol Understood.  I'll miss them.

@RobinMalfait Would it be reasonable to add an option to disable the Output from prettier? It seems jarring to have eslint problems reported subtly with squiggly lines in the editor but have prettier use Output.

I shipped a PR to disable the output


ISPN-15067 All RESP handlers should use ASCII string whenever possible

https://issues.redhat.com/browse/ISPN-15067
Also made some changes to prevent String concatenation for integer using more efficient write

Updated

Thanks, @wburns!


ADD Dockerfile command does not unpack tarballs

Describe the bug
ADD tarball.tar.gz / is supposed to unpack the said tarball into the root. Instead, it just copies it into it.
To Reproduce
The specific Dockerfile I ran into this at:
FROM scratch

ENV LANG=C.UTF-8
ENV LC_ALL=C.UTF-8

ARG DEBIAN_FRONTEND=noninteractive

ARG OSPACK=debian.tar.gz
ADD ${OSPACK} /

RUN apt-get update

Here, debian.tar.gz is a minimal Debian rootfs tarball.
Expected behavior
The tarball is unpacked, so that I can run commands using its contents.
Instead, I’m getting:
info	* Step 6/7 (modifyfs) : ADD debian.tar.gz /  (465a0d0c)
info	* Execute ADD debian.tar.gz /  (465a0d0c) took 91.261753ms
info	* Not committing step ADD debian.tar.gz /  (465a0d0c)
info	* Step 6/7 (modifyfs) : RUN apt-get update  (d6692f4c)
error	failed to execute build plan: execute stage: build stage 0: build node: do execute: execute step: cmd start: exec: "sh": executable file not found in $PATH

Thanks, but it seems that PR only adds support for tar.gz but not plain tar
archives or tar.bz2/tar.xz or tars compressed with other compressors.
--
Cheers,
Andrej
On Wed, 11 Mar 2020, 22:01 Yiran Wang<EMAIL_ADDRESS>wrote:

Closed #298 https://github.com/uber/makisu/issues/298 via #309
https://github.com/uber/makisu/pull/309.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/uber/makisu/issues/298#event-3120508317, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACLQBM64OMTN3BKP6LNHSDRG73Z3ANCNFSM4KGQU4AQ
.

Let me keep the issue open until they are all supported


refactor(RingTheory/Ideal/Pointwise): Generalize to semirings

This PR generalizes much of RingTheory/Ideal/Pointwise to semirings. I also moved a couple lemmas from the Group section to the Monoid section, and added a lemma to RingTheory/Ideal/Over.

bors merge
Thanks!


tidying up the prefab docs

There were the following issues with your Pull Request

Commit: 05988291e1f58e8b197c17a73d5b036ef76f3b65
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

There were the following issues with your Pull Request

Commit: efa594d22ca8eeadc5c9fe278746b743c0ffac57
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

There were the following issues with your Pull Request

Commit: 03d9bd2f147669562468a0c0fcb484a4ecdba954
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com


Add target coverage-map

Add target to get line coverage for test files.

Coverage decreased (-0.06%) to 83.435% when pulling 7eabe6319e20d381a94f2d5621f3c57f4c179d94 on coverage-map into 59340fbcf501e8982705f34f1eed0c50fb98e51e on master.

Small change to makefile, n o tests added, passes travis-ci. Okay?


fixed absolute and msdn links

Fixes #756
/cc @BillWagner @cartermp
Removed en-us and version from msdn links so that localized versions in the future will take the user to the language stored in their browser cache. Removing the version to always go to the tip.
Made other small fixes on the affected topics.
I haven't changed the API links that will be handled separately and are tracked by this issue: #787

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

Docset 1: core-docs

Looks great. I noticed two small typos, and had a couple questions.
Once you fix the typos, :shipit:

LGTM!

@BillWagner I saw the comment about the missing space. Was there another typo (you mention two in your comment)? The change to MSDN links was on purpose.

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

Docset 1: core-docs

@mairaw It was just the one.  Off-by-one error on my part.

No problem @BillWagner. Just wanted to make sure I didn't miss anything. I'll fix the conflicts and merge this. Thanks!

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

Docset 1: core-docs

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

Docset 1: core-docs


requirements.txt should specify latest version of spacy

Currently broca installs spacy==0.84. But when you run python -m spacy.en.download, it throws a weird error: preshed.counter.PreshCounter has the wrong size, try recompiling
Bumping to spacy==0.88 seems to fix this problem.

closed in 0d75eb9bf4a25d06e471bda1b48c0b4b0ac20ca8, thanks!


Docker-less builds

(See #1.)

I would recommend making sure that you still can do docker based builds. That way, running on windows still would work.

The idea is to run the whole recipe build in docker or podman or what have you, not just the _build stage.


Textarea overwrite input field in wizard

Select one ...  (check one with "x")
[X ] bug
[ ] feature request
[ ] enhancement

Expected behavior
I have a wizard with several leading input fields of type text, then a textarea, 'Description',  (rows = 5), followed again by several input fields of type text. I expect the subsequent input fields to appear below the text area.
Actual behavior
The text area extends down over the subsequent input fields. The subsequent fields are visible through the textarea though, just not below it.
Sorry, don't know how to create a plunker link but I've included screenshots of the issue and sample code from my app (using your wizard with form validation code as a starting point).

wizard.component.txt
Reproduction of behavior

Include a link to the reproduction scenario you created by forking one of the Clarity Plunker Templates:

Environment details

Angular version: 4.0.X

Clarity version:
.9.13

OS and version:
macOS 10.12.6

Browser: [all | Chrome 60  | Safari 10.12 |

@beaker1977
What's causing this is the label that is being wrapped around the textarea to force a validation tooltip on the textarea.
This appears to be a duplicate of #45 which we have not implemented yet.
As for plunkr, it's fairly easy to copy-paste the code you sent into the sample app in plunkr.
The problem for us is that we get so many requests that we can't possibly do the plunkr for everyone who might have an issue.


Update http4s-blaze-server, http4s-circe, ... to 0.23.8

Updates

org.http4s:http4s-blaze-server
org.http4s:http4s-circe
org.http4s:http4s-dsl
org.http4s:http4s-server

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

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

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

Superseded by #72.


Consolidate Extension Methods

This PR address #61.

[x] Related GitHub issue(s) linked in PR description
[x] Destination branch merged, built and tested with your changes
[x] Code formatted and follows best practices and patterns
[x] Code builds cleanly (no additional warnings or errors)
[x] Manually tested
[x] Automated tests are passing
[x] No decreases in automated test coverage
[x] Documentation updated (readme, docs, comments, etc.)
[x] Localization: No hard-coded error messages in code files (minimally in string constants)

Since moving some of the IEnumerableExtensions.cs methods to EnumerableExtensions.cs is a breaking change, is there a reason to not move everything and delete it?

The reason these particular extensions were an issue is because the same name was used and it was just a pass-through to the core extensions anyway.  With that in mind, I think it's probably ok to leave the remaining EnumerableExtensions in the Extensions project.  Or were you asking something different?


[scripts] Variables not properly set in prepare and cleanup scripts

Motivation
The script prepare_helm_release.sh was creating a asymmetric key unless I pass --symmetric as last parameter of the command line.
It turns out that the variable is set to false in every step of the parameter parsing loop.
Modifications
Moved variable assignment outside of the loop.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
But is verifiable through the output of the script execution. Passing the parameter --symmetric in any order, the output should be:
The jwt token secret keys are generated under:
    - '${release}-token-symmetric-key'

Instead of:
The jwt token secret keys are generated under:
    - '${release}-token-asymmetric-key'

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API: no
The schema: no
The default values of configurations: no
The wire protocol: no
The rest endpoints: no
The admin cli options: no
Anything that affects deployment: yes

Documentation

Does this pull request introduce a new feature? no

@zymap Would you also please help review this？


Just noticed something in the galactic crate config

I loaded in the default config that you provided and got this in console on the default crazy key award.
Caused by: org.yaml.snakeyaml.scanner.ScannerException: while scanning an anchor
in 'string', line 125, column 21:
DisplayName: '&b&lCrazy Crate &6&lKey &7(x2)'
^
expected alphabetic or numeric character, but found &(38)
in 'string', line 125, column 23:
DisplayName: '&b&lCrazy Crate &6&lKey &7(x2)'
^
It seems to not like the '&' symbol. I'm not sure but thought you'd like to know.

The '^' symbols in config pointed to the '&' symbol that chat just reformatted it.

Strange. Delete your Galactic Config again. Because I just tested this and it works fine for me.

Ok no big deal just wanted to make sure it wasn't an issue I just removed
the color coding from that spot. :)
On Thursday, June 2, 2016, BadBones69<EMAIL_ADDRESS>wrote:

Strange. Delete your Galactic Config again. Because I just tested this and
it works fine for me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kicjow/Crazy-Crates/issues/6#issuecomment-223480664,
or mute the thread
https://github.com/notifications/unsubscribe/ASxTqhklfwLr63tIVWtOjNbKiPGO5jM-ks5qH5t4gaJpZM4ItJw8
.

Strange tho. Well hf.


something_markdown works some_thing_else_markdown does not work.

look at what_todo_on_reexamination_markdown for example.

We also need to have a shorter markdown initiate support. For instance.
something_something_MKDN or something like. All upper case only matching should make it unusual that Mark down will not be supported...


Wrangler.toml not appearing on wrangler generate

When I run wrangler generate the folder it creates does not contain a wrangler.toml file anywhere. I don't know if this is a bug or the file was deprecated and the docs were not updated. Either way I'd be happy to help with this issue.
This is on a Mac running 10.14.2, in case that's relevant

this is currently on master- simply not deployed. can you try running cargo install --git https://github.com/cloudflare/wrangler and trying again?


DB2 to MySQL database migration: Syntex error

Detail:
Error starting data transfer
Can't create target table:
SQL Error [1064] [42000]: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(1048576),
            is_internal VARCHAR(1),
            created_on BIGINT NOT NULL,
            created_by INT' at line 5
SQL Error [1064] [42000]: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(1048576),
            is_internal VARCHAR(1),
            created_on BIGINT NOT NULL,
            created_by INT' at line 5
  You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(1048576),
            is_internal VARCHAR(1),
            created_on BIGINT NOT NULL,
            created_by INT' at line 5
  You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(1048576),
            is_internal VARCHAR(1),
            created_on BIGINT NOT NULL,
            created_by INT' at line 5

System information:

Operating system (distribution) and version: Windows 10
DBeaver version: 6.3.4 Community version
Additional extensions: None

Connection specification:

Database name and version: DB2(Dash DB)  and MySQL 8.0.19 community server
Driver name: Db2cc.jar, MySQL JDBC Driver(MySQL Connector JAVA 8.0.19.jar)
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing: Please refer
Steps to reproduce, if exist: Create table in db2 with data type description LONGTEXT(1048576), and migrate it in MYSQL.
Include any warning/errors/backtraces from the logs: Please refer as given above.

thanks for the bug report

This is no exactly a bug.
DBeaver failed to determine correct target data type for MySQL column, But you can set target data type in columns mapping dialog/tree.
Current type detector will be improved in #7745 but it won't be started till 7.0 release.

@subesingh1981 Hello
Can you check, please, new DBeaver version. Is problem still actual?
If so, what DDL did the exported table have?
Thanks for advance!

There was no response for a long time, so the ticket is closed.
You can reopen the ticket if the problem occurs again.

There was no response for a long time, so the ticket is closed.
You can reopen the ticket if the problem occurs again.


[CELEBORN-1727] Correct the calculation of worker diskInfo actualUsableSpace

What changes were proposed in this pull request?
Correct the calculation of worker diskInfo actualUsableSpace.
Make the expression of the function to get the reserve size clearer. (getMinimumUsableSize -> getActualReserveSize).
Let deviceMonitor startCheck after the first storageManager.updateDiskInfos() to avoid disks from being misidentified as HIGH_DISK_USAGE.
Fix PushDataHandler#checkDiskFull judge.
Why are the changes needed?
Make sure worker disk reserve work correctly.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Cluster test and UT.

Seems need to fix many UT failures. @onebox-li
- celeborn spark integration test - hash-checkDiskFull *** FAILED ***
  235 was not less than or equal to 0 (CelebornHashCheckDiskSuite.scala:83)


dynatrace_aws_credentials resource bug

Describe the bug
We have had issues with running a terraform apply for the dynatrace_aws_credentials resource since version 1.36.0. It looks like that release contained a bug fix (Added validation to verify external ID is populated in dynatrace_aws_credentials resource) that may be the culprit?
To Reproduce
You can create a new dynatrace_aws_credentials resource with the config below (it has to have the supporting_services_to_monitor
param) but when you run a second deploy/apply it will fail.
CONFIG:
resource "dynatrace_aws_credentials" "account_name" {
  label          = "account_name"
  partition_type = "AWS_CN"
  tagged_only    = false
  authentication_data {
    account_id = "account_name"
    iam_role   = "role_name"
  }
  supporting_services_to_monitor {
    name = "route53"
  }
  supporting_services_to_monitor {
    name = "route53resolver"
  }
  supporting_services_to_monitor {
    name = "ssm-runcommand"
  }
}

ERROR:
╷
│ Error: must be null
│
│   with module_path.dynatrace_aws_credentials.resource_name,
│   on module_path/resource_name.tf line 1, in resource "dynatrace_aws_credentials" "resource_name":
│    1: resource "dynatrace_aws_credentials" "resource_name" {
│
╵
Error: Terraform exited with code 1.
Error: Process completed with exit code 1.

Expected behavior
Continue to deploy/apply after resource has already been added
Additional context
I'm not 100% sure if the data_source for aws_creds is nested or used by the actual resource, but I'm wondering if this bug was somehow introduced here > https://github.com/dynatrace-oss/terraform-provider-dynatrace/commit/539e513bebe973b34d79922645ad560408c8496f#diff-fd38a6b9f303511c298863a145fdc8a443e1e6c27743a5ffb5d2b7aa2a927a9fR60
based on the behavior it would seem that it does a query of the creds before running so there's no issues if new but if NOT new it breaks.
it's also worth mentioning that this problem only exists for dynatrace_aws_credential resources that have the optional supporting_services_to_monitor param. However, we were using this config as it's listed above without issues prior to v1.36.0 where we just list the service name but not the monitored_metrics and let it add the default options.

Hello @ekleiner14, we're planning for a release tomorrow. The bug you've identified will be fixed with that release.
Apologies for the inconvenience.

No problem @Dynatrace-Reinhard-Pilz - thanks for your help!


MapFuncCore's Range Operation is Ill-Defined

Range is defined to return multiple rows per invocation.  For example:
Range(0, 3)

id
value

0
0

1
1

2
2

This is sort of bonkers, since it allows completely non-sensical things such as joining where the key contains a Range (which is an operation that has no sane definition).
The correct definition of Range would be to return an array in a single row, which the user can subsequently flatten:
Range(0, 3)

id
value

0
[0, 1, 2]

This would be implementable by all connectors, and has a sane interpretation in all cases of MapFunc.
As a general rule, MapFuncs should never operate on anything more than a single row.  A single row may be eliminated (by going to Undefined), or it may be transformed in a perhaps-structural fashion, but you cannot return multiple rows, and you cannot operate on more than one row at a time.  Any functions which violate this invariant should not be included in MapFunc, since their inclusion prevents sane interpretation of joins, sorts, and other row-level operations.
If we cannot redefine Range in the fashion I describe (for example, if this operation is part of ANSII SQL and constrained to behave in a multi-row fashion), then we need to remove it from MapFunc.

💯 The current definition is broken and doesn't mean anything sensible.


Fixes #104: correctly parse id repr for Rust 1.78+

It would be super nice if somebody using Windows / MacOS could confirm this works with Rust nightly on their machine :pray:

Since this is probably breaking the CI for everyone who has stable testing, may I suggest merging this soon?

Thanks, I'd really like a test by someone on windows though, since paths may be different there (notably slash vs backslash).

You shouldn't need any platform-specific testing done.  If the output of the old (opaque) id worked for you then extracting it should work here as well because they are both URLs and are platform-independent and you already had to be handling any platform-specific logic for the old id format.

@epage Ah thanks for the information, I hadn't realized this was platform-independent.


Allows more customization

Customizable features

Background image

Custom image

Visualizer

Custom length

Visualizer position

Custom horizontal and vertical position based on screen width, height

Hi,
I know that I told you to send a pr but on giving it some thought this project is a sample/template for audio visualizer api so its  been decided to keep it simple and focused on the api.
So I am closing this.

I'll add yours to the gallery once its open :D

Alright sure, thanks.
On Fri, 2 Dec 2022, 16:15 Dani John, @.***> wrote:

I'll add yours to the gallery once its open :D
—
Reply to this email directly, view it on GitHub
https://github.com/rocksdanister/audio-visualizer-wallpaper/pull/3#issuecomment-1334891785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF6W3JWK7BKYHUWEP6TXOJDWLGVZ5ANCNFSM6AAAAAASPSAFGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


400 BadRequest: x-no-cors-reason

Issue Summary
I have a Firebase cloud function called needCode that sends an email using sendgrid. However, I always get a Bad Request.
Steps to Reproduce

Invoke needCode cloud function
Check needCode error log in Firebase console

Code Snippet
import * as sgMail from '@sendgrid/mail'
sgMail.setApiKey(SENDGRID_API_KEY);
export const needCode = functions.https.onCall((data, context) => {
    const { email, name, message } = data
    return new Promise(function (resolve, reject) {
        const msg = {
            to<EMAIL_ADDRESS>            from: email,
            templateId: 'd-ac6fdd2f3ee746fc94d211ad947a8d0e',
            dynamic_template_data: {
                name: name,
                message: message
            }
        }
        return sgMail.send(msg)
            .then(() => {
                resolve(
                    { message: "Email sent" }
                );
            }).catch(error => {
                console.log(error)
                reject(
                    new HttpsError('unknown', 'Error sending email')
                );
            });
    });
})

Exception/Log
{ Error: Bad Request
    at Request.http [as _callback] (node_modules/@sendgrid/client/src/classes/client.js:124:25)
    at Request.self.callback (node_modules/request/request.js:185:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)
    at Request.<anonymous> (node_modules/request/request.js:1161:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at IncomingMessage.<anonymous> (node_modules/request/request.js:1083:12)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:111:20)
  code: 400,
  message: 'Bad Request',
  response:
   { headers:
      { server: 'nginx',
        date: 'Sat, 14 Mar 2020 04:09:13 GMT',
        'content-type': 'application/json',
        'content-length': '402',
        connection: 'close',
        'access-control-allow-origin': 'https://sendgrid.api-docs.io',
        'access-control-allow-methods': 'POST',
        'access-control-allow-headers': 'Authorization, Content-Type, On-behalf-of, x-sg-elas-acl',
        'access-control-max-age': '600',
        'x-no-cors-reason': 'https://sendgrid.com/docs/Classroom/Basics/API/cors.html' },
     body: { errors: [Array] } } }

Technical details:

sendgrid-nodejs version: 6.5.1
node version: v12.4.0

Probably need a paid firebase account to allow external network calls. Recommend checking the error details:
console.log(error.response.body)

I have the exact same issue and error, same setup. Has anyone got a solution?
I have some other projects using the exact same setup and they don't seem to have an issue.

@teanz Have you tried my comment above?

Since the others haven't responded, I'll chime in that I found my way here with the same error and what childish-sambino suggested worked perfectly.  The error messages in the HTTP response are actually really good.  In my case I had a trailing space on my template ID.  Just to be thorough, here is the full code snippet that solved this problem for me:
sgMail.send(msg).catch(err => {
            console.log(err);
            console.log(err.response.body)
          });;

I've updated the docs in a few places to better indicate how to handle/log error responses: https://github.com/sendgrid/sendgrid-nodejs/commit/0e8c2761fb8d0beeac8107d0d963bb6ab80b0a6d

Thanks, logging the error out further gave me the real cause... not having my sender identity setup -_- Appreciate the help.


elul, glaucidium

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[e,g]

/trunk merge


Add chiro, trickle, lust, cargo, tick

Nice, thanks for the great libraries! :smiley:

Are trickle and lust specific to LÖVE, or at least have some connection?
:+1: on the other three

trickle and lust aren't specific to LÖVE, though trickle's main use case is for online games.


Time Zone update not working

Hi,
I with this image time zone update not working with EV or host folder mapping. Could you please check.

What's your docker compose look like?

Fixed by mapping host time zone file.

I will do the test.

Time Zone working with this build.

Updated in https://github.com/modem7/DHCP-Relay/commit/18982ddbba2881e95c7daa3d6a33558d8e8cbf5b


Make introspection update interval configurable in RouDi

Brief feature description
At the moment Roudi runs introspections every second. To make it more flexible (e.g. for quicker integration tests) it makes sense to have inrospection update interval configurable.
Detailed information

Tests that use introspection info can benefit, because they don't need to wait for 1 sec each.
Regular users can also benefit from it, so CLI option may also be added.

@r7vme shall I assign you for this issue?

@elBoberido Yes, please

Closing as won't do see details here