consider having timeouts in test binaries be recoverable/handled

The way timeouts are thrown cause the binary to exit immediately
https://github.com/golang/go/blob/4d608eb224fe1ba8e8532fcc44f91702a5b17f9f/src/testing/testing.go#L1740-L1744
This circumvents T.Cleanup and any cleanup logic that might have been in TestMain. In order to guarantee setup/teardown occurs it has to be done outside the go test process. Thus either a testing script or the use of go test -exec xprog
The challenge with these workarounds is you lose the simplicity of invoking go test.
Thus my ask is

when a timeout occurs run T.Cleanup functions
considering surfacing the timeout as a panic but allow the ability to handle that panic

My second point could be accomplished by having the panic be surfaced by M.Run() and could be handled in the following way
func TestMain(m *testing.M) {
   os.Exit(run(m))
}

func run(m *testing.M) (exitCode int) {
  setup()
  defer cleanup()
  exitCode = m.Run()
}

Note that the t.Deadline method was introduced specifically so that tests could arrange their own, earlier, timeouts.

Yeah - I'm aware of the deadline per test.
My main concern is the setup and teardown that's called out in the TestMain docs

It is sometimes necessary for a test program to do extra setup or teardown before or after testing.


Fix regex to exclude Wikipedia links to image file pages

The regex to exclude the Wikipedia links does not always work as if you visit a page in a different language, i.e. Danish, the link will look differently:
https://da.m.wikipedia.org/wiki/Fil:Danmark-locator.png
This will break the images when using the --inline cli option as it will instead try to base64 encode contents of https://da.m.wikipedia.org/wiki/Fil:Danmark-locator.png, which is an HTML page.
I propose that we change the regex as shown in the commit to take into account different languages.

That's a good idea! I wonder if we should extend the regex to something like /wikipedia\.org\/wiki\/[a-z]+:/i to make sure we're not too general with the exclusion rule?

Agreed, shall I change it in the commit?

That would be great, if you don't mind!

Fixed, please review.


feat: remove gaxios dependency

Removes dependency on gaxios by refactoring File.isPublic.
This

Allows the library to capitalize on the existing retry logic in nodejs-common
Removes a dependency
Makes the isPublic function consistent with most other functions in the library

This isn't really going to do much for you. gaxios is a required dependency of google-auth-library, and removing it here doesn't actually remove it from the transitive dependency graph. We want to move away from the request style libraries, not closer towards them.

Good to know! We'd like to move over the isPublic function to common anyway to be consistent with the rest of the library and also to leverage the retry functionality we recently implemented in common.


Automator: update ztunnel@master in istio/istio@master

Generated by Automator - 2024-08-07T15:23:01+00:00

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
true
/test integ-basic-arm64

unit-tests-arm64_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
true
/test unit-tests-arm64

integ-ambient_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
true
/test integ-ambient

integ-cni_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
true
/test integ-cni

integ-ds_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
true
/test integ-ds

integ-distroless_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
true
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test lint

integ-ipv6_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test lint

integ-ipv6_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test integ-ipv6

integ-security-istiodremote_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test lint

integ-ipv6_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test integ-ipv6

integ-security-istiodremote_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test integ-security-istiodremote

integ-telemetry_istio
e71838794a5838f96bcb36802832daa81e3feaa6
link
unknown
/test integ-telemetry

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


Error: Can't resolve 'crypto'

When trying to include this project into an Angular project, it fails with:
 Error: Can't resolve 'crypto' in '..\node_modules\kdbxweb\dist'
Is there any chance this could be made webpack compatible?

Hi! It's compatible with WebPack, however you need to tune your config. Probably you need to exclude crypto, something like this:
node: {
    crypto: false
}


Disable enter keypress in names form

A side effect of having individual 'remove' buttons is, on enter keypress in any of the text inputs, this submit action is actioned, removing the active name.
In order to stop this behaviour, we are going to disable form submits on enter keypress, only on text inputs, and only for the names form, not other forms.

@zheileman @BNewing May I suggest a better solution? Add a default submit input(that does the same as your primary action) to the beginning of the form. Set that input to display: none.

@solidgoldpig I see what you mean, problem is, there is no clear expectation of what we should do here. In other forms, enter key will submit the form, and if there are no validation errors, it means it will "advance" to the next step.
But in the names steps, it is a bit more complicated, as if we just say "let's advance" that means a user filling a first/last name, and hitting enter in the last name, will advance the form to the next step, which might not be ideal as they might want to add more children, or more people in general.
If instead of advance we say, ok, "let's just add this name and reload the page" then we are back to the original "bug report" (When entering your child's names, if you hit return in the "Childs Name" box, it doesn't Continue - it adds another child)


Fix bug with highlight

Summary of changes
Now all the items within All Attribution list at the Attribution view are highlighted on hover and highlighted when selected. The same holds for attributions and signals lists at the Audit view.
Context and reason for change
A bug with items highlight.

Please, squash and fix commit message before merging


Support python 3.13

Hey,
Would be very happy if you could support python 3.13 and create a new release and wheels compiled for python 3.12.
Thank you very much!

Hey @alisaifee, can you take a look?
Really looking forward to upgrading to python3.13 :)

Apologies for the delay in getting to this. I've added it to CI but unfortunately there's a few other unrelated issues in the build process that need to be ironed out before I can make a release.

Compiled wheels are available as of daad833a650126e92a166b3ffd07341f903c14e5. This is only in https://test.pypi.org/project/coredis/ at the moment but I'll make a release over the weekend.

Thanks @alisaifee :)
Could you cut a new release so those wheels will be available?
Thank you!

Apologies for the delay - the 4.18.0 release is now available with the compiled wheels.


intellij idea community edition does not work

Hi, Does this plugin support intellij idea community version？

I couldn't get it to work either, I got this error from IDE :
java.lang.AbstractMethodError: Receiver class co.huggingface.llmintellij.LlmLsCompletionProvider does not define or inherit an implementation of the resolved method 'abstract boolean isEnabled(com.intellij.openapi.editor.event.DocumentEvent)' of interface com.intellij.codeInsight.inline.completion.InlineCompletionProvider.
My token works, I managed to run this :
import requests

API_URL = "https://api-inference.huggingface.co/models/bigcode/starcoder"
headers = {"Authorization": "Bearer hf_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}

def query(payload):
    response = requests.post(API_URL, headers=headers, json=payload)
    return response.json()

output = query({
    "inputs": "for my_list in ",
})

I couldn't get it to work either, I got this error from IDE :
java.lang.AbstractMethodError: Receiver class co.huggingface.llmintellij.LlmLsCompletionProvider does not define or inherit an implementation of the resolved method 'abstract boolean isEnabled(com.intellij.openapi.editor.event.DocumentEvent)' of interface com.intellij.codeInsight.inline.completion.InlineCompletionProvider.
My token works, I managed to run this :
import requests

API_URL = "https://api-inference.huggingface.co/models/bigcode/starcoder"
headers = {"Authorization": "Bearer hf_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}

def query(payload):
    response = requests.post(API_URL, headers=headers, json=payload)
    return response.json()

output = query({
    "inputs": "for my_list in ",
})

I work with PyCharm CE 2023.2. Here are LLM plugin settings :

same issue...

This plugin depends on Intellij's LSP API which is not available to free/community edition IDEs.
[shameless-plug]
LSP4IJ is a free and open source LSP client implementation for all JetBrains IDEs. Given llm-intellij is fairly small, I think it might be possible to easily migrate it to use LSP4IJ instead. Just saying ;-)
Disclaimer: I'm one of LSP4IJ's maintainers
[/shameless-plug]


deps: Upgrade Flutter to 3.27.0-1.0.pre.25

And update Flutter's supporting libraries to match.

Thanks! Looks good; merging.


Out-of-vocabulary keywords

What is the URL of the doc?
https://picovoice.ai/docs/quick-start/porcupine-react/#custom-keywords
What's the nature of the issue? (e.g. steps do not work, typos/grammar/spelling, etc., out of date)
1 : Nothing about what to do if the words are not recognized by the console
2 : How to make your own wake word after giving it a mp3 file , basically for example we want to set a password word as a wake word for gate opening and we cannot do that because of that issue and no information about how to achieve it

If the wake word you have in mind is not available in the Console vocabulary, there is unfortunately nothing you can do about it. If you believe it's a valid word and should be included in our dictionary, please let us know.

yes htere are wakewords missing please tellme how can i provide the m to you

Reopen this issue please we need to add the missing words

i mean we need to send the words to you so you can add them tell me here how to send them to you

You can list your words here as a comment. We will wait to commit to adding them, to be precise. If it makes sense, we will add them at some point. If you are an existing enterprise customer and need help, please reach out to your account manager directly.

oh thank yo uso much yo uare a live saver sending you on next message

For now critical is only one wake word  in  Russian vocabulary we need the name Anny , we got the working on English that is Hello Anny , now we need the same for the Russian vocabulary but on there greeting that is Privet Anny so in Russian it is written like this " Привет Энни" . There are lots of names that are not recognized too but for us the critical one is that one for now LOL fans will appreciate too. We are not Enterprise but we are planning to become one  and we depend on you now So please help us with this matter

https://translate.google.am/?hl=hy&sl=ru&tl=en&text=Привет Энни&op=translate here are text and  sound samples from google translate for the first wake word we need

i added the images to teh future too so i wait for your answer guys in two sides here and in future

besides of ANny our planned next hero  is Darius so we will need him too but for now we need Annie here is the missing darius  prooves from the console


window.fetch throws FormatException when passed URL

Hi,
I have a PDF file that I need to download, and it requires an authentication token passed to the header. I've read about the Fetch API https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch and is trying to use it in flutter.
The signature of fetch function in html_dart2js.dart is Future fetch(/*RequestInfo*/ input, [Map? init]) so I tried to use it like so
import 'dart:html' as html;
...
ElevatedButton(
            child: Text('fetch'),
            onPressed: () async {
              final r = await html.window.fetch({'<link to pdf file>')});
              final url = html.Url.createObjectUrl(await r.blob());
              final anchor = html.AnchorElement(href: url);
              anchor.download = 'test.pdf';
              anchor.click();
            },
          ),

I no longer get a type exception, but this always throws a FormatException whenever I pass in a url here is an output for trying to fetch a random image
ERROR - 2022-11-10 12:28:57.382828
GET /%7Bhttps://fileinfo.com/img/ss/xl/jpg_44.png%7D
Error thrown by handler.
FormatException: Scheme not starting with alphabetic character (at character 1)
%7Bhttps://fileinfo.com/img/ss/xl/jpg_44.png%7D

I guess there is an issue with url encoding. Or is my usage wrong?
Thanks

It does look like the url string is malformed - it starts with /%7B.
Note, Dart just forwards to the underlying browser API:
https://developer.mozilla.org/en-US/docs/Web/API/fetch
The first argument is passed unmodified to the JS code.  It should just be a string - that's not clear in your example.  The error is coming from JS.

And {'<link to pdf file>')} is a Set<String>.

Thank you so much I got it to work passing data like so

final r = await html.window.fetch(
                                                  pdfUrl,
                                                      {
                                                        'headers': {
                                                          'accessToken': accessToken
                                                        }
                                                      });

Thanks for the update.  I'll repurpose this bug as a req to improve documentation.


Update babeltrace to 1.5.11-1

This is my first PR in this project, please help me check my work.
Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

babeltrace was behind, at 1.5.7. I brought it back up to upstream stable at 1.5.11.
Change Log

Packages affected: babeltrace, ceph
No longer needs a patch to its source

Does this affect the toolchain?

NO
Associated issues

N/A
Links to CVEs
N/A
Test Methodology

Local build

Buddy-Build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=679456&view=results

@mfrw Can you please retrigger the signature check Action?


What about the same for reactnative ?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27055428-what-about-the-same-for-reactnative?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github).

I don't understand your question.


Replace IRC with Discord in CONTRIBUTING file

I'd prefer to mention both; there are people who don't have Discord nor want to get it, and for those I think it's nice to mention the existence of the channel as well.
(but maybe s/FreeNode/Freenode)? :))

Oh, and can we finally ditch that mailing list? Is anyone even using/reading it?

Looks like this was addressed in #3159


Migrate docker image repository to k8ssandra docker org

As a companion to #95 we also want to consolidate the docker images generated for the management-api under the k8ssandra docker org.
Also included in this work should be a refactoring of the way the repositories are structured so that all management-api images are consolidated under a single repository with relevant tags applied denoting the various version options available.
We also should generate new naming conventions that avoid the Apache Cassandra trademarks.
This would consolidate all of the following repositories:
https://hub.docker.com/r/datastax/cassandra-mgmtapi-4_0_0
https://hub.docker.com/r/datastax/cassandra-mgmtapi-3_11_10
https://hub.docker.com/r/datastax/cassandra-mgmtapi-3_11_9
https://hub.docker.com/r/datastax/cassandra-mgmtapi-3_11_8
https://hub.docker.com/r/datastax/cassandra-mgmtapi-3_11_7
Note that we do not intend to move the DSE related management-api repository if possible:
https://hub.docker.com/r/datastax/dse-mgmtapi-6_8

As far as the tags go, are you wanting something like:

cassandra-mgmtapi:4.0.0
cassandra-mgmtapi:3.11.10
cassandra-mgmtapi:3.11.9
etc...

Or something like:

cassandra-mgmtapi:4.0.0-v0.1.23
cassandra-mgmtapi:3.11.10-v0.1.23
cassandra-mgmtapi:3.11.9-v0.1.23
etc...

I'm not a fan of the second version, but if they all end up in the same Docker repo, they need to be distinguished by Cassandra version and Management API version, so we may not have much of a choice.

A suggestion was brought up to create a tagging scheme such that a Cassandra-only tag would be equivalent to a latest tag. So something like:
cassandra-mgmtapi:3.11.10
would be the same as the latest
cassandra-mgmtapi:3.11.10-X.Y.Z
Also, the naming of the repo should probably be cass-mgmtapi as opposed to cassandra-mgmtapi

@bradfordcp @jdonenine @JeremiahDJordan Any comments on the tagging strategy, or the image rename on this?

what about k8ssandra/management-api::3.11.10-vX.Y.Z ?  But really I think any of those is fine.

A suggestion was brought up to create a tagging scheme such that a Cassandra-only tag would be equivalent to a latest tag. So something like:
cassandra-mgmtapi:3.11.10
would be the same as the latest
cassandra-mgmtapi:3.11.10-vX.Y.Z

I'm cool with what's suggested here.


JuliaRegistrator trigger issue

@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/87434
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" e37aacf3615f9fe70b01adb68d20386cd3448d5e
git push origin v0.2.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/87644
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 40fc19ab98ed1b9725e71d9bca00a79483513051
git push origin v0.3.0

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request created: JuliaRegistries/General/87645
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.1.0 -m "<description of version>" 40fc19ab98ed1b9725e71d9bca00a79483513051
git push origin DomainColoringToy-v0.1.0

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request updated: JuliaRegistries/General/87645
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.1.0 -m "<description of version>" d94f3d00de872353926359f1beaae5d0c650fff8
git push origin DomainColoringToy-v0.1.0

Registration pull request created: JuliaRegistries/General/89260
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.0 -m "<description of version>" 5e50d68c45591cc7c4df3f1a3accbb605f13721b
git push origin v0.4.0

Registration pull request created: JuliaRegistries/General/89261
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.2.0 -m "<description of version>" 5e50d68c45591cc7c4df3f1a3accbb605f13721b
git push origin DomainColoringToy-v0.2.0

Registration pull request created: JuliaRegistries/General/89267
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.1 -m "<description of version>" fdef3014a4c7d1375012e377e8db2e1a10652827
git push origin v0.4.1

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/89611
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.5.0 -m "<description of version>" 7cac420f6e4e26034dbed83d161177a9423fc8e1
git push origin v0.5.0

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request created: JuliaRegistries/General/89612
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.3.0 -m "<description of version>" 7cac420f6e4e26034dbed83d161177a9423fc8e1
git push origin DomainColoringToy-v0.3.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/89639
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.5.1 -m "<description of version>" 4cef8cebd22629a8f6894b6291945571e17d08da
git push origin v0.5.1

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request created: JuliaRegistries/General/89640
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.3.1 -m "<description of version>" 4cef8cebd22629a8f6894b6291945571e17d08da
git push origin DomainColoringToy-v0.3.1

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/89705
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.6.0 -m "<description of version>" 2cde596a844d678d451cb7ddfbbe9d2c6d65a2aa
git push origin v0.6.0

@JuliaRegistrator register subdir=DomainColoringToy

Error while trying to register: "Tag with name DomainColoringToy-v0.4.0 already exists and points to a different commit"

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request created: JuliaRegistries/General/89708
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.4.0 -m "<description of version>" 2cde596a844d678d451cb7ddfbbe9d2c6d65a2aa
git push origin DomainColoringToy-v0.4.0

Registration pull request updated: JuliaRegistries/General/89708
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.4.0 -m "<description of version>" 2cde596a844d678d451cb7ddfbbe9d2c6d65a2aa
git push origin DomainColoringToy-v0.4.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/89936
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.6.1 -m "<description of version>" 3a16241006632d12479394dc0204bd4ad054df6f
git push origin v0.6.1

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/90927
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.7.0 -m "<description of version>" b7e0d62ab839112a1ef84ecba82ab666527eb34f
git push origin v0.7.0

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request created: JuliaRegistries/General/90931
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.5.0 -m "<description of version>" b7e0d62ab839112a1ef84ecba82ab666527eb34f
git push origin DomainColoringToy-v0.5.0

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request updated: JuliaRegistries/General/90931
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.5.0 -m "<description of version>" b7e0d62ab839112a1ef84ecba82ab666527eb34f
git push origin DomainColoringToy-v0.5.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/91052
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.8.0 -m "<description of version>" 05d3fd81f0e944da2936c6f4350b2d174afd299a
git push origin v0.8.0

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request created: JuliaRegistries/General/91053
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v0.6.0 -m "<description of version>" 05d3fd81f0e944da2936c6f4350b2d174afd299a
git push origin DomainColoringToy-v0.6.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/91769
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 4fa82892db317d0deb8f5394736ad1c1844a4cd2
git push origin v1.0.0

@JuliaRegistrator register subdir=DomainColoringToy

Registration pull request created: JuliaRegistries/General/91771
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v1.0.0 -m "<description of version>" 4fa82892db317d0deb8f5394736ad1c1844a4cd2
git push origin DomainColoringToy-v1.0.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/93579
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.1 -m "<description of version>" 3977232ca16e6704e873e42b84a19975b2f165f6
git push origin v1.0.1

Registration pull request created: JuliaRegistries/General/93580
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a DomainColoringToy-v1.0.1 -m "<description of version>" 3977232ca16e6704e873e42b84a19975b2f165f6
git push origin DomainColoringToy-v1.0.1


Improve parsing of xmp records

Better handling of lists/sequences -- append into attribute arrays
instead of allowing each value to overwrite the previous one.

Better inference of unknown attributes that look like int, float, or
rational, rather than cramming into strings.

Fixed what I now think were bugs in handling rational values.

Fixes #2874

Fixes #2874


Patch project page and dependencies

Codecov Report

Merging #332 (967a0cc) into main (63cdadf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #332   +/-   ##
=======================================
  Coverage   49.26%   49.26%
=======================================
  Files          40       40
  Lines        4098     4098
=======================================
  Hits         2019     2019
  Misses       2079     2079

Impacted Files
Coverage Δ

dribdat/public/api.py
28.35% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Emacs 29.1 support

Current master fails to bootstrap using emacs 29.0.90 with the following error:
Debugger entered--Lisp error: (void-variable native-comp-deferred-compilation-deny-list)
  straight--build-native-compile((:type git :host github :repo "radian-software/straight.el" :files ("straight*.el") :branch "master" :package "straight" :local-repo "straight.el"))
  straight--build-package((:type git :host github :repo "radian-software/straight.el" :files ("straight*.el") :branch "master" :package "straight" :local-repo "straight.el") nil)
  #f(compiled-function () #<bytecode 0x7cf19944a8f5436>)()
  straight--transaction-exec(use-package-\"c809124e9c5270ea1c72e2c3507331d1\"-nil-nil :now #f(compiled-function () #<bytecode 0x7cf19944a8f5436>))
  straight-use-package((straight :type git :host github :repo "radian-software/straight.el" :files ("straight*.el") :branch "master"))
  eval-buffer(#<buffer  *load*-100331> nil "/home/user/.emacs.d/straight/repos/straight.el/boo..." nil t)  ; Reading at buffer position 5397
  load-with-code-conversion("/home/user/.emacs.d/straight/repos/straight.el/boo..." "/home/user/.emacs.d/straight/repos/straight.el/boo..." nil t)
  load("/home/user/.emacs.d/straight/repos/straight.el/boo..." nil nomessage)
  (let ((bootstrap-file (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory)) (bootstrap-version 5)) (if (file-exists-p bootstrap-file) nil (save-current-buffer (set-buffer (url-retrieve-synchronously "https://raw.githubusercontent.com/raxod502/straigh..." #'silent #'inhibit-cookies)) (goto-char (point-max)) (eval-print-last-sexp))) (load bootstrap-file nil 'nomessage))
  eval-buffer(#<buffer  *load*> nil "/home/user/.emacs" nil t)  ; Reading at buffer position 825
  load-with-code-conversion("/home/user/.emacs" "/home/user/.emacs" t t)
  load("~/.emacs" noerror nomessage)
  startup--load-user-init-file(#f(compiled-function () #<bytecode -0xd489cb3187ae488>) #f(compiled-function () #<bytecode -0x1f3c61addc0b39f5>) t)
  command-line()
  normal-top-level()

The variable  native-comp-deferred-compilation-deny-list seems to have changed to  native-comp-jit-compilation-deny-list.
One can go around this error by setting the old variable before loading straight:
(setq native-comp-deferred-compilation-deny-list nil)

Duplicate of https://github.com/radian-software/straight.el/issues/1059
Please search past issues prior to creating a new one.


What is the difference between your work and the U^2 net?

U^2 Net: https://github.com/xuebinqin/U-2-Net

网络模块不同，应用不同，具体细节可参考我们的论文。
renxwang @.***> 于2023年2月17日周五 13:07写道：

U^2 Net: https://github.com/xuebinqin/U-2-Net
—
Reply to this email directly, view it on GitHub
https://github.com/danfenghong/IEEE_TIP_UIU-Net/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFL2GZT7NGICOIY7SGRNSA3WX4BQVANCNFSM6AAAAAAU676V6Y
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

谢谢回复，我看了你们的论文，

There are several modules in your model folder, but they are not added at all in uiunet.py. The code of uiunet is exactly the same as u2net.

Can u illustrate the difference please  ??


Github capitalization

In the list of icons, the github tag is listed 'Github,' which returns an error. It's actually 'GitHub' in the package.

cheers, fixed in master!


Pluggable credentials decryption for VCAP_SERVICES data on CF

To enhance security we are modifying all our service brokers to encrypt key pieces of data in the credentials map return as part of VCAP_SERVICES.
I started looking at how I could have a pluggable interface in CloudFoundryServiceInfoCreator that by default would not decrypt credentials, but could be replaced by one that decrypts based on our strategy.
Based on my initial analysis, as all ServiceInfoCreators are not created as part of the Spring lifecycle, but instead are through Java's ServiceLoader, there is no easy injection point that doesnt involve changes in several places that at this stage I'm not keen to embark on.
Is this something we forsee implementing or do you have pointers on best I could proceed to provide a PR?

@johnmcteague This question is pretty old, my apologies for letting it slip through the cracks. The use of ServiceLoader would make it difficult to design a pluggable mechanism for decoding credentials from VCAP_SERVICES. There is a possibility that we could move to a Spring bean loading mechanism in a future release, but nothing like that is planned at this time. The only option I see right now is to replace the default CloudFoundryServiceInfoCreator implementations for the services you care about with custom implementations.
Have you come up with a solution since creating this issue?

We have simply created a custom set of ServiceInfoCreators that replace all the standard ServiceInfoCreators (MySql etc) where we have amended the service to use encrypted passwords. The complication we still have which we work around in a less-than-ideal scenario, is when we use these off-platform where our decryption service is not available. A pluggable scheme would have allowed us to switch out the decryption scheme, for now we use a bunch of if/else's to try and detect when we are running in CF.

Thanks for the information @johnmcteague. I'll add that as another big advantage to moving to a Spring loading mechanism in the core of Connectors.

Experimental implementation implemented in https://github.com/spring-cloud/spring-cloud-connectors/commit/0cb7c25754b31cfade104ded9c2ef00f74162eca


[WASM-Mixer] Provide a way to terminate the job

On the dApp, we need to terminate the jobs for a long-running task generate_zk_proof
This should kill the worker reject the promise for the action/actions

Closed in #70


Initialization Problem

Hi~ Can I initialize the network with pre-trained weights rather than random numbers?

See model.get_weights and model.set_weights methods.

If you are looking for a pre-trained image labelling model, you coud use: https://gist.github.com/baraldilorenzo/07d7802847aaad0a35d3


Address warnings

This PR addresses some (IMHO justified) IntelliJ IDEA warnings. Feel free to throw away specific commits if you don't the like the corresponding changes.
Side question: Is there a reason why you use CRLF instead of LF in Response and RequestParser?

I didn't like the appearance of the raw requests with \r but without \n. The asymmetry bothered me. But looking again, I think the absence of noisy double quotes outweighs that slightly.
CRLF is used throughout the HTTP/1.1 spec (RFC 2616), so it feels like a standard, familiar shorthand.

CRLF is used throughout the HTTP/1.1 spec (RFC 2616)

Oh, OK. Didn't know that. 👍


[Enhance] add floating preview window feature support to vim

Problems summary
Are you consider adding floating preview window feature support to vim to show snippet and hook information, just like coc.nvim?
Or create a new plugin to implement this feature both work on nvim and vim ? I noticed that both ddc.vim and coc.nvim are plugins based on ts scripts. Does this make it possible to increase floating windows feature for vim ?

https://github.com/matsui54/ddc-nvim-lsp-doc
The plugins exists for nvim-lsp floating preview information.
I don't add the feature in ddc.vim.  Because it should be implemented in other plugin.
I don't interest the feature.  So I don't create new plugin...


fix: reverse reference address not working anymore

The api/v1/address/reverse of the reference address is not working in some cases since commit 1c339f6ba63b16b47fcd11ecd372c317c7be034a (use of gps coordinates) whatever the address is used.
To test: on production site, either use the reference button on the map, or go to account settings, set a new address in reference address, save (it seems to work), then refresh the page.
"Couldn't find location."
400 Bad Request

Should be fixed. Give it a try and call again if I ever forgot something.

I also fixed the location filter from /items as I saw it was broken. When we were selecting "Don't use geolocation" and typing an address, it didn't do anything. The functions that were previously in frontend/src/views/TheItemsView.vue were left there and not moved to frontend/src/components/ItemsFilters.vue so the filter couldn't call the API to retrieve the correct address etc.
Added minor update there too where you now can select a distance range when using this "Don't use geolocation" option (wasn't the case before, I don't know why?) + made the address field disabled when using geolocation or ref location (as you shouldn't be able to update those to be consistent in user experience).
I'll add a new issue tho, because a great way to make it possible would be to change the "philosophy" of that location filter. It would look like that: only 2 buttons (geolocation and ref location) in click mode instead of selection mode, 1 label "Address:" instead of "Or enter an address:" and the address field always never disabled. That way, the address filled by the buttons could be edited without being misinterpreted.
Lot of explanations but as I can't knock on your door anymore I give all the details in my comments ;)


npx command doesn't work

The npx command doesn't work

@quentinmarchand1 Hey and welcome
Could you share OS and Node.js version? Appreciate if you also try with the latest version of Practice (released today)

Sorry for the late reply, the problem was my node version


fix(Lezer grammar): Highlight CompareOp

This PR changes the tests to use CallExpression because we don't want expressions at the root. The grammar still allows it tho, but we should fix that.
Changing the tests resulted in that the operator tests breaking which led me to change expresssion inside the CallExpression token to test which made the test pass, and which also made the comparison operators properly highlight in CodeMirror when used in the context of a call expression.
This PR also adds a test for two subsequent comments which is something that produced a weird tree before we got rid of the Statement and PipelineStatement tokens.

I'll merge because I trust your direction @vanillajonathan
But more broadly — I would caution against moving away from tests which can test small individual examples, such as expressions, since it means that even small tests need lots of context, and the output of something very small is quite large ("Query(Pipeline(CallExpression(Identifier,ArgList(BinaryExpression(Integer,ArithOp,Float)))))")
If you prefer to have tests which test a full query, an alternative to many small tests is a small number of larger tests, which each test as much as possible ("Write tests, not too many, mostly integration"). For example, a few big queries that have lots of examples in them. In that approach, when we make a change to our code, we can add a expression to a large test. That's often less maintenance when the code we're testing doesn't have as many layers that we want to individually verify.

I like the small tests, they're a great way to progressively hack at the Lezer grammar until it falls into places, and they're good for catching regressions.
I intend to keep the small tests, but here they got a bit bigger because I wanted to the Lezer grammar (which is context sensitive) to reflect real PRQL.
Big tests have previously not been feasible because the grammar wasn't yet mature and exhaustive enough. It's getting there though.
Soon a larger test will be added but small tests are good for pinpointing regressions which can be tricky to pinpoint in a larger tests.

Great, thanks @vanillajonathan


how to conenct uibuttons in the xib file to the tableviews

I have UIButton in my xib that when i go to connect as IBAction I can only doit in the UITableViewCell class and not the corresponding UITableView Class, I have registered it in the view and gave it the correct identifier, let me know if anyone else is having this issue. Same problem with the demos as well.

http://stackoverflow.com/questions/31775670/cannot-connect-ibaction-to-table-view-from-xib/31775848#31775848


admin.site.site_header not being honored in django 1.7

Hi when using django 1.7 and the new admin.site.site_header option import-export reverts to the default site_header value of Django Site Admin instead of the customized variable.

PR welcome :)


UKWN instead of token name

After contract deployment minted tokens displayed in tonkeeper as "Unknown Token" with "UKWN" symbol, interestingly that on tonscan it clearly can read metadata and if we go to jetton contract itself - name, symbol, description and even image are displayed correctly, however if we go to wallets that hold minted tokens they are also displayed as "Unknown Token". Anyone knows what could be the problem?

Tonkeeper has own whitelist for all jettons. You need to pass their procedure to solve this issue.

I'm not sure if that's tonkeeper issue, because on tonscan it displayed correctly if we go to the contract itself: https://testnet.tonscan.org/jetton/EQC1FKZNzLVVmVN-_nmxEjk0T06XcpLHXMfBEvHYChEHKMTn, but if we go to holders and then to jettons it's displayed as "unknown" https://testnet.tonscan.org/address/0QDAAON_lNBFKexjgdFnYgiAkX1MRKLS5CJV8dw_bxFVhBmM#tokens, I tried to mint tokens via tonraffles and they meta displayed correctly even though they also labeled as "unverified".

100% related to tonkeeper, you can search the same issue here @ton_dev chat

Thanks, I'll look into it.


remove nni devnet chainid 103

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

Hi, i understand this is manually reviewed. We removing our old address
Old > BcRr96qhSoaKFjGJDKtSWmHDvTrv7ziuq29dRjtUmHuk
New > buMnhMd5xSyXBssTQo15jouu8VhuEZJCfbtBUZgRcuW
Hope i'm taking the right steps in doing so. Thank you team

All is amended. Thank you team


British Summer Time and current rate

Describe the bug
I'm not sure if this is a bug with this module or something within home assistant more generally.  Since the clocks changed this weekend, the current rate seems to be an hour out from what the rate should be for a given point in the day.
To Reproduce
Steps to reproduce the behavior:

Set the timezone to London
Check the sensor.octopus_agile_current_rate sensor
Look up the rate for the current time in octopusagile.rates
The current rate will be for the previous hour

Expected behavior
Expectation is that the rate for a given time will match that timecode in the octopusagile.rates attributes.
Desktop (please complete the following information):

OS: Universal
Browser Chrome

Mine seem ok.
Is the time on your server set correctly?
Does the server have it's GMT time correct? and timezone and DST settings correct?

Sorry, just looked again and realised the times in octopusagile.rates are UTC encoded rather than local time.  Using the rates card it looks correct and the current rate matches the octopus website.


Why users make donations with the wrong profile?

We constantly have users making a donation with their personal  profile instead of their organizational one. I think part of the reason is that when you click on a tier to donate you land with an anchor direcly in the payment method section of the order:

The anchor should be at the top of the page instead so the first think you see is the personal details

@znarf This is happening again, at least in events.
Click on Become a Sponsor here https://opencollective.com/sustainoss/events/sustainuk-2018-442ev
The anchor is at the bottom of the page instead of the 'contribute as'

re-opening issue

@piamancini ok, let me know if there is any other cases to cover.


Allow use to get wireguard config for their network in 3bot deployer

Allow use to get wireguard config for their network in 3bot deployer

Commit_ID a1b57396c977ac25d566d340405a9f9a177ddeb8, Branch development


Feature Request: find all Storyboard UI elements for which an AccessibilityID has not been set

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the [Contribution Guidelines]
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I would love to have a feature in Fastlane which parses the Storyboards for a project and produces a report of which UI elements do not have AccessibilityID set .. this would make it easier to send to the Testing Engineer, who can easily see what elements are not yet named (and which are therefore not accessible to a UITest) ...

Interesting idea. Do you have an idea which tool to place this in? Where does it belong to best?

I feel that this might be more on the side of a Build Phase script through a library that checks the storyboards of a project and generate warnings than on the fastlane suite.

Don't you think a "good code" or "accesibility check" would be a good addition to fastlane? I do, I just can't think of a good place to put it right now.

Wouldn't it be a sub-function of snapshot?  Seems to me that automatic screenshot generation, as well as automated reporting of Accessibility, are kind of along similar lines?  I haven't grok'ed the fastlane snapshot code well enough yet, but I would imagine it'd be aligned with the existing automated screenshot methods currently used?  i.e. parsing Storyboards.

Snapshot runs tests and takes screenshots - pretty different task I think.

Fair enough.  I guess I'll have to spend a few days getting up to speed with the fastlane code base to come up with a recommendation on where to put such a feature .. I guess I could be referred to as an "Accessibility Lint" style function ..

Any chance I could get a statement from you guys on if you think this feature will end up on the workbench in the near future?  If its not something of interest, I'll probably try to hack something together myself else wise, but if you think it is worth it - but don't have the time - then I might invest into grok'ing the code in fast lane well enough to send a PR ..

Maybe as a fastlane plugin? That would totally make sense.
That way the actual logic could be implemented and tested without any commitment needed from the core contributors, and if it turns out to be super popular and used very often it can maybe still be integrated to the core action further down the line.
You can read more about creating a plugin here: https://docs.fastlane.tools/plugins/create-plugin/


{RDBMS} Remove cluster information from config file

Description
Removal of information from public repo. Used for testing purposes, moving forward will be injecting into JSON file.
Testing Guide
Manually

RDBMS

@calvinhzy  @evelyn-ys  Please have this be included for current milestone, safer practice to remove info


Issue duplicate functions in javascript also naming convention are not right

Issue duplicate functions in javascript also naming convention are not right
also objects in javascript page are not available

Thanks


some inputs have lost their styles

Overview
The profile search input, along with some of the inputs on node integrations seem to have lost there styles.
Screenshots
Current

Expected

this is also on the node integrations create screens:

I'll pick this up since I just did all the chef-input stuff.  Should be a quick fix

@chef/ui-team  - Sourcing opinions here...
What's going on is that our inputs are now using the #chefInput directive for styling purposes.  with our current setup, this requires chef-form-field to wrap the input.  We are seeing inconsistency because this works if chef-form-field is simply present on the page somewhere.
My thought is that we have 2 solid options.

require that every input is wrapped in chef-form-field.
move .chef-input class styling into global scope.

My opinion is that .chef-input class should be moved into the global scope, as we want these all to have a consistent styling unless specifically overwritten in their local CSS.  Anyone have strong opinions?

Let's try your opinion and see how it goes. We don't want to bloat global scope but this might be a good instance to insert some global styling. Ping me when the branch is up so I can give it a look.


consolidated .json files into one and updated the imports and references to it.

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #38200

I forked the correct repository this time.
consolidated .json files into one at utils/words.json on fix/update-congratulatory-quotes branch.
and also updated the files that referenced the original separate .json files to reference the new consolidated .json file.
Let me know if it is ok?

Hi,
Can you confirm this was done locally and you have tested everything works?
Also we would need you to go through the contributing documentation throughly. We recommend you to send pull-requests from a non-default branch (which would be master). This is to avoid soiling your copy fork for review changes that we may request.
Please reach out to contributors chat room if you need help thru this.

@raisedadead yes I forked it and then worked on it locally created a new branch made the changes needed and merged it back into the master of my fork, pushed it to the fork and then made the pull request.
No I have not tested it because I didn't know how to go about that, I will ask in the contributors chat room as you suggest.

I didn't know how to go about that, ...

I believe we have documented everything in our guidelines for contributing. I recommend you give it a through read.

@raisedadead thanks I will take another look I must have missed that.

Please re-open a fresh request when ready


chore(master): release 1.1.4

:robot: I have created a release beep boop
1.1.4 (2023-08-11)
Miscellaneous

deps: update dependency wayofdev/cs-fixer-config to v1.2.41 (78026b5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-webhook-client/releases/tag/v1.1.4 :sunflower:


TypeError: Cannot read property 'type' of undefined

Getting an TypeError when try to annotate using spread operator for Objects,
e.g.
   const obj = { test: 1, test2: 2 };      const copyObj = { ...obj };

Should work now. Released in version 1.12.0.


This is the How to Run for quick reference

I can ldd & stat the library as I built it from source... the thing is I built it with old gcc (4.4.7) /libc... not sure to what degree it could affect the run.. I'm using absolute path.. the problem is not with the library but rather with unknown symbol referenced by library

Hey @nevgeniev, I don't think you can compile libagent with gcc's younger than 4.5. I personally used 4.6+ for the development.

this is true unless you define 'nullptr'... once you do you can compile in with gcc older than 4.6

@nevgeniev, I believe it's more complicated than just nullptr. Since you're using gcc-4.4 which doesn't have standard c++ atomic's library cstdatomic will be used instead.
#if __GNUC__ == 4 && __GNUC_MINOR__ < 6 && !defined(__APPLE__) && !defined(__FreeBSD__) && !defined(__clang__)
#	include <cstdatomic>
#else
#	include <atomic>
#endif

Unfortunately it doesn't work well with std::atomic<X> where X is not primitive type, even a pointer to it. Code within concurrent_map.h unfortunately contains:
std::atomic<Job*> job;
std::atomic<HashTable*> current;

That's why runtime linker is complaining about undefined symbols. It's easy to find them all BTW:
?> ~/w/honest-profiler on master ? nm build/liblagent.so | grep memory_order | grep -e '\bU\b'                    19:20:04
                 U _ZNVSt6atomicIPN3map3JobEE5storeES2_St12memory_order
                 U _ZNVSt6atomicIPN3map9HashTableEE5storeES2_St12memory_order

The only simple solution that can fix this issue is to replace this two variables' type to std::atomic_address (std::atomic<void*>) which is defined in cstdatomic - cstdatomic and cast it to appropriate type like Job* when needed.
I can try to implement this, but know how long will it take.

Given the fixing PR has been merged I'm closing. Please re-open if the problem persists.


Does not work with leddartech evaluation kit

Is it not supposed to work with leddartech eval kit?

@pbaj yea for CAN connections it should, at least it did for the 10 or so eval kits i tried. what issues are u running into?
i used PCAN USB to connect to my laptop (ubuntu 14.04 and 16.04) over USB. i was not able to get PCAN-USB Pro FD to work, see http://www.peak-system.com/forum/viewtopic.php?f=179&t=2367.
if u are using CAN make sure terminal resistor DIP switch (8 iirc, see data sheet) is on. setup the network interface to it:
$ sudo ip link set can0 up type can bitrate 1000000
$ sudo ip link set up can0

and start streaming:
$ cansend can0 740#0300000000000000

here 0x740 is the default CAN rx id. i use the leddar windows cfg tool to check things are set correctly (tx/rx ids, bitrate, etc).
if all this works then this ros driver should as well (just make sure you pass the right params when you launch it).

How do you manage to connect the CAN to the VU8? I dont see any connection on the VU8


Remove support for @checked once code has been migrated to use covariant

Once major code bases (e.g. Flutter) have migrated to covariant from @checked, we should deprecate and then remove support for @checked.
cc @sethladd

Flutter has migrated via flutter/flutter#8300

I think this can now be done at any point that is convenient.

dart2js doesn't seem to support covariant yet

@zoechi can you elaborate?  It was marked as implemented here: https://github.com/dart-lang/sdk/issues/28165 , so if there's something missing we should follow up on it.  Note though that dart2js just implements the Dart 1.0 semantics, which is just to ignore it (since Dart 1.0 functions are covariant already).


Implement contact method

implement https://core.telegram.org/bots/api#sendcontact
to allow:
Telegraph::contact($phoneNumber, $firstName, $lastName, $vcard)

Hi, @fabio-ivona , I would like to work on this issue

Hi @tombenevides feel free to do it 😉

Now we also need a method.

@tombenevides any update? otherwise we can work this one


Add support for OpenID-Connect

Include RPM mod_auth_openidc for OpenID-Connect support.

@simaishi Please review and merge if appropriate.
Thank you! JoeV


Data Metric Graphs

Currently the daily metrics of tokens is shown as simple numbers to the admin. It would be nice to have visualizations of these metrics using d3 or any other library.

Where are the metrics located in the project? I could do some D3

Hey @AmGarera ,
The metrics are stored in a postgres table 'metrics'. You can see the schema definition in /db/schema.
The metrics are generated using a basic regex search on papertrail logs and is shown to the admin in the metrics view (/views/analytics.erb)


Kubemark Initial Run

Make Kubemark initially run with ignite-etcd:

Create a Docker image
Update Kubernetes and Kubemark scripts and configs
Make it run and collect initial results
This does not include fixing performance issues that may be found

There's a good overview of kubemark at https://stupefied-goodall-e282f7.netlify.app/contributors/devel/kubemark-guide/
We use GCE to run kubemark performance tests, so this would need a GCE account. There is a way to run it locally as well, but I have not tried it.
Please see the document https://github.com/sonyafenge/arktos-tool/blob/master/perftools/Howtorunperf-tests.md . Please look through the steps to see how it relates to the above overview document.
When bringing up the cluster, the kube-up script sets up the master VM and runs a configure script that starts etcd and runs etcd in a pod (etcd.manifest tells kubelet where to get the container image for etcd and how to start it). And I don't know if etcd-events.manifest is applicable to ignite. Is it?
Please review:
gci/configure-helper-common.sh:function prepare-etcd-manifest {

The key thing to do here is to replace etcd with ignite in a way not very different from what we did with local-up-cluster, but it may be a bit more work. Overall though, I think it would be sufficient to replace this function with something like prepare-ignite-manifest, but I may be missing something.
From the above how-to-run-perf doc (which is specific to our project), I would change the env variables in step 1 as illustrated below (you can choose your own zones, prefixes, net-names):
export MASTER_ROOT_DISK_SIZE=100GB MASTER_DISK_SIZE=120GB KUBE_GCE_ZONE=us-west2-b MASTER_SIZE=n1-highmem-32 NODE_SIZE=n1-highmem-8 NUM_NODES=2 NODE_DISK_SIZE=200GB KUBE_GCE_NETWORK=kubemark-500 GOPATH=$HOME/go KUBE_GCE_ENABLE_IP_ALIASES=true KUBE_GCE_PRIVATE_CLUSTER=true CREATE_CUSTOM_NETWORK=true KUBE_GCE_INSTANCE_PREFIX=kubemark-500 KUBEMARK_NUM_NODES=100

For starters, just to try things out, an admin cluster with 2 VM nodes (NUM_NODES=2) and 100 virtual nodes is sufficient. You can skip step 2 in above document.
The k8s perf tests come from repo https://github.com/kubernetes/perf-tests
In my experience, it is best to setup the k8s repo and perf-tests repo under standard go paths for it to work without extra efforts. i.e.
~/go/src/k8s.io/kubernetes/
~/go/src/k8s.io/perf-tests/

We usually run the load and density perf tests (they can be run separately). To run the perf-tests:
cd perf-tests/clusterloader2/
nohup ./run-e2e.sh --nodes=$KUBEMARK_NUM_NODES --provider=kubemark --kubeconfig=$HOME/go/src/k8s.io/kubernetes/test/kubemark/resources/kubeconfig.kubemark --report-dir=$HOME/logs/perf-test/ --testconfig=testing/load/config.yaml --testconfig=testing/density/config.yaml


Black

Applicable Issues

Based-on: #183
Description of the Change

Run black with -l 100 instead.
Alternate Designs

None
Benefits

Clearer code and it fits better with other ETOS components that run with -l 100.
Possible Drawbacks

None
Sign-off

Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
Signed-off-by: Tobias Persson<EMAIL_ADDRESS>

No changes since @fredjn approved.


WIP: Update Lyo Sandbox for the paper & June demo

Closes #95

This change is

Andrii,
I wanted to tryout the robot twin fix. Make gives the following error.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] sandbox-parent ..................................... SUCCESS [  0.085 s]
[INFO] Sandbox PPDL Domain ................................ SUCCESS [  1.406 s]
[INFO] webapp-whc ......................................... FAILURE [01:12 min]
[INFO] webapp-twin ........................................ SKIPPED
[INFO] webapp-twin-shelf .................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:13 min
[INFO] Finished at: 2018-04-13T11:05:58+05:30
[INFO] Final Memory: 26M/566M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project webapp-whc: Could not resolve dependencies for project se.ericsson.cf.scott.sandbox:webapp-whc:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.eclipse.lyo.trs:trs-consumer:jar:2.4.0-SNAPSHOT, org.eclipse.lyo.trs:trs-server:jar:2.4.0-SNAPSHOT: Could not find artifact org.eclipse.lyo.trs:trs-consumer:jar:2.4.0-SNAPSHOT in lyo-snapshots (https://repo.eclipse.org/content/repositories/lyo-snapshots/) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :webapp-whc
Makefile:2: recipe for target 'up' failed
make: *** [up] Error 1

Ah yes, you are correct, these two need to be installed manually as I have not yet contributed changes to the original libraries.
–Andrew.
(sent from my phone)

On 13 Apr 2018, at 07:46, swarupmohalik<EMAIL_ADDRESS>wrote:
Andrii,
I wanted to tryout the robot twin fix. Make gives the following error.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] sandbox-parent ..................................... SUCCESS [ 0.085 s]
[INFO] Sandbox PPDL Domain ................................ SUCCESS [ 1.406 s]
[INFO] webapp-whc ......................................... FAILURE [01:12 min]
[INFO] webapp-twin ........................................ SKIPPED
[INFO] webapp-twin-shelf .................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:13 min
[INFO] Finished at: 2018-04-13T11:05:58+05:30
[INFO] Final Memory: 26M/566M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project webapp-whc: Could not resolve dependencies for project se.ericsson.cf.scott.sandbox:webapp-whc:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.eclipse.lyo.trs:trs-consumer:jar:2.4.0-SNAPSHOT, org.eclipse.lyo.trs:trs-server:jar:2.4.0-SNAPSHOT: Could not find artifact org.eclipse.lyo.trs:trs-consumer:jar:2.4.0-SNAPSHOT in lyo-snapshots (https://repo.eclipse.org/content/repositories/lyo-snapshots/) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :webapp-whc
Makefile:2: recipe for target 'up' failed
make: *** [up] Error 1
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

@swarupmohalik you (and @rssouza) will need to do extra steps:

Clone https://github.com/eclipse/lyo-trs-server/tree/mqtt ('mqtt' branch)
install it by running mvn clean install in the root folder.
Clone https://github.com/eclipse/lyo-trs-client/tree/mqtt ('mqtt' branch)
install it by running mvn clean install in the root folder.

Then the twin fix should work.

We finally got the connection from the twin to ROS master working:

And the build succeeds on Ricardo's machine.

Close in favour of #99 w/o merging


wps: added ComplexDataInput class

Hi *,
i've added in wps the ComplexDataInput class. It can be used to add a complex input parameter (either an url reference or direct content). Before this there were only classes for special complex data input (FeatureCollection, ...).
Travis tests were all passing :)
Further changes:

fix: unicode input is now possible for literal input data
doctests for wps with ComplexDataInput: wps_request_7, ...
doc: added note about testing and available anconda packages for owslib
updated wps example wps-birdhouse.py
moved the IWebProcessingService interface to interfaces.

Cheers,
Carsten

@cehbrecht thanks for the contribution.  At first glance it appears that Travis-ci tests fail for anything Python 3 (single failure at https://travis-ci.org/geopython/OWSLib/jobs/77119673#L1389).

sorry ... i've overseen that failure. I've fixed now the wps 52n test. Seems to be successful :)
Some owslib tests are "online" tests and they fail if a service is not available or too slow ...

Thanks @cehbrecht!


Programming exercise: Enable viewing template and solution repositories

Adds functionality to view the solution and template repositories while assessing a programming submission. To avoid confusion, the app does not let the user add/edit feedback while viewing a non-student repository.
Demo:
https://github.com/ls1intum/Themis/assets/22798314/7989d381-d865-4b41-a5c3-d6305459ba55

Thanks for the review! This Artemis PR (https://github.com/ls1intum/Artemis/pull/6810) will fix the issue.

The issue is now fixed 🙂


WIP: rewrite GitHub Actions runner Dockerfile

Signed-off-by: Adrian Cole<EMAIL_ADDRESS>

I need to find a way to get msitools on centos, and it isn't available there, and neither are all the deps needed to build it (not even rocky has all of them, notably libgcab1-devel).
However, msitools is available on fedora. Monday, I'll try running fedora msitools binaries on centos to see if they are compatible enough. If that doesn't work I might consider dropping code signing from the centos builder.
https://pkgs.org/search/?q=msitools

it isn't likely go 1.18 will be out before February based on release cadence, but I'll do this anyway as otherwise I'll forget all the context. https://golang.org/doc/devel/release


"FIERBINȚI-TÂRG" is listed in the drop-down menu

Description:
When user writes "FIERBINȚI-TÂRG" the location appears in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "FIERBINȚI-TÂRG"

Expected results
The location appears in the drop-down menu as "Oras FIERBINȚI-TÂRG, IALOMIȚA "

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write again in the search bar "FIERBINȚI-TÂRG"

Expected results
The location appears in the drop-down menu as "Oras FIERBINȚI-TÂRG, IALOMIȚA, (FIERBINȚI-TÂRG) "


it will block http request ?

I want  create a tools to request server by  conversation with the user via a console.
but found request is canot be send until  the loop completed.
code like this
server
//main.js

var http = require("http");
var i=0;
http.createServer(function(request, response) {
    console.log('request received' + i );
    response.writeHead(200, {"Content-Type": "text/html;charset=utf-8"});
	response.write(i.toString());
        response.end();
	i++;
}).listen(9990);
console.log('server started');

client
// readline.js
// npm install readline-sync
// npm install request

var readline = require("readline-sync");
var request = require("request");

for (var i = 0; i < 10; i++) {

    var ans = readline.question("do requ ?");

    if (ans == "y") {
       console.log("begin to request");

        request("http://localhost:9990", function (err, resp, body) {

            console.log("get ->" + body);

        });
    }
}

exe processing:
left is server , right is client
The first four cycles , the server output nothing.

untill  ten times ,  server output  all things.

i have two question

why not send request one by one ?
how should to modified to  send  request after press y and enter ?

thanks very much

Hi linecheng, thank you for your post.
The matter is very simple. This is correct JavaScript behavior.
First, you must understand about JavaScript working.
JavaScript basically works in single thread. The event loop does not run unless you release the thread.
For example:
setTimeout(function() {
  console.log('3 seconds?');
}, 3000);

var startTime = Date.now();
while (true) {
  if (Date.now() - startTime > 10000) {
    console.log('10 seconds');
    break;
  }
}

The code above and your code don't work by the same cause.
The callback you gave to request is executed at next event loop, but you don't release the thread until a request is called 10 times. The thread is released after that is called 10 times, and then, the callbacks are executed, and requests are finished.
Same result comes even if readlineSync is not used because this is JavaScript behavior.
//var ans = readline.question("do requ ?");
var ans = 'y';

If you want to send a request per the user response, release the thread per calling the request.
For example:
var readlineSync = require('readline-sync'),
  request = require('request'),
  count = 0;

function doRequest() {
  if (!readlineSync.keyInYN('Do request?')) { return; }
  console.log('begin to request');
  request('http://localhost:9990', function (err, resp, body) {
    console.log('get ->' + body);
    if (++count < 10) { doRequest(); }
  });
}

doRequest();

anseki,
Thank you so much for your apply.
I have understond  JavaScript basically works in single thread.

Hi linecheng.
Did you post a comment? And did you close and reopen this again?
There is no reply... and I have no idea.
If you reopened this because you still have question, tell me it.
If this issue was solved, close it please. :smiley:

anseki ,
Thanks for your apply so much .
sorry point the wrong button accidentally ....
I have understond  JavaScript basically works in single thread  ,  realized it was JavaScript behavior.
I can understand the callback will be called  after the thread is released .
but how about the request ?
even  sending request  will wait for  the released thread  ?
I have test with another code in chrome ,  the results seems like some differents between that code .
//reference jquery in current page

for(var i=0;i<10;i++){
    console.log(i);
    $.get("http://localhost:9990",{},function(data){

       console.log(i+"--> get " + data);

    });
}

when one loop executed,  the server got one request , and gaven response. after 10 times , the thread is  released , the 10 callbacks are executed .
According up  , I should get one request  on server   in one loop .
but that code   for (var i = 0; i < 10; i++) {   request (........)  }   , No sending one request  in one loop.This is where I'm confused .
I don't know if I  express it clearly , thank you for your apply again .

That is very simple too.
Remember, JavaScript can not send the HTTP request oneself.
So, how did you send the HTTP request? Yes, you used the libraries.
That is, which library you used?
You used request module, and jQuery. Of course, the library decide when it send the request.

request module sends the request when an event is fired. That is, in event loop that started after the thread was released from your code.
jQuery sends the request immediately when ajax is called. That is, in your code of a loop. (the method sends the request, and it returns thread to your code.)

These are the behavior of libraries. Not JavaScript. (Many modules of Node that include request module are event-driven, because Node is event-driven. It's basic and big and important feature of Node.)
Try these 2 code:
function like_request(cb) {
  setTimeout(function() {
    cb('DONE: like_request');
  }, 10);
}

for (var i = 0; i < 10; i++) {
  console.log(i);
  like_request(function(data){
    console.log(i + ' --> get ' + data);
  });
}

function like_jQuery(cb) {
  // setTimeout(function() {
    cb('DONE: like_jQuery');
  // }, 10);
}

for (var i = 0; i < 10; i++) {
  console.log(i);
  like_jQuery(function(data){
    console.log(i + ' --> get ' + data);
  });
}

See 2 results, and difference of 2 codes.
BTW,
You can see the order of those steps easily by the Developer Tools of Chrome or others.
Press [F12] key to open the Developer Tools. And open "Sources" tab.
And then, you can make the code run step by step, by [F10], [F11] key, etc.. You get a time when the request is sent.

anseki,
Thank you for your patience.
I understand  they are different between the two libraries now .
request module sends the request when an event is fired,   but the jQuery sends the request immediately.
I will learn more basic things of Node .
You have solved my confusing , thank you so much ,  I will close this  issue .
Thank you .  : )

I recommend you reading the official document always. There are many many unofficial documents, samples, etc. in the internet, but a official document will most help us.
For example, a document about your first question is here.
(explanation about the behavior of request module, information about the time when your callback is called, etc.)
The official document will let us avoid the problems, or it will let us solve the problems.
Enjoy coding! :smile:

Ok, Thank you so much !
Yes, Enjoy coding! :smile:


Make parameters named instead of positional

context.s.file_uploadProgressSnackBarContent(1, file.name, 0) is not descriptive, but this is:
context.s.file_uploadProgressSnackBarContent(
  fileName: file.name,
  totalNumberOfFiles: 1,
  currentIndex: 0,
)

That's why I argue for making parameters named and @required instead of positional by default.

I don't understand - where is your example coming from?


Guides – Visualizing big datasets: aggregations and clustering

Proposed structure

Global aggregation
Viewport Aggregation
Resolution
Clustering

Add a note regarding to resolution as a way to improve rendering when a lot of points overlap

New guide has been merged to master 🚀

VAMOS! 💪


OAuth2: add Yandex provider (#8335)

Fix #8335

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1812f7b). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #10564   +/-   ##
=========================================
  Coverage          ?   43.72%
=========================================
  Files             ?      585
  Lines             ?    82008
  Branches          ?        0
=========================================
  Hits              ?    35854
  Misses            ?    41715
  Partials          ?     4439

Impacted Files
Coverage Δ

modules/git/command.go
86.95% <ø> (ø)

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 1812f7b...c47a831. Read the comment docs.

Looks like some stuff keeps failing. Is it something I should address?

Seems when I resolved conflicts I didn't do it in a way that was go fmt capable, could you run make fmt?

Looks good now


feat(website): support hmr and react refresh

Because I initially chose the SSR example from the loadable-component repository when setting up the website, it has never supported HMR. Instead, it has been downgraded to use the livereload package. Now I finally have time to add these functionalities to it!

support hmr
support react refresh
support nodejs server hot swap

The only downside is that, in reality, an ideal SSR architecture only requires two webpack configuration files. However, in this case, I have three because the example from @loadable-component runs webpack on the server-side JSX files to generate chunks and stat JSON files. This seems unnecessary since the client-side has already gone through the process. Simply copying the client-side files would suffice. So, in essence, the ideal SSR architecture consists of one webpack configuration file for compiling the client-side and another webpack configuration file for compiling the server-side Express renderToString server, as we need to hot reload the server-side code.
For example, in this case https://github.com/tomtom94/react-easy-ssr/blob/master/src/server/index.tsx, it does not use webpack to run JSX on the server-side. Instead, it directly uses the entry point generated from the client-side stat JSON file. Maybe I will consider migrating again when I have time.

Great practice!

Great practice!


First cut of Route53

Note: I don't expect this to get merged since it's so raw, but I'm just curious if I'm on basically the right track here. I'm new to Elixir, and I'm mostly just cargo-culting the SQS and S3 implementations.
I got the Route 53 integration test to pass, meaning that it's hitting the AWS API with all the correct params.
If you want to run the test yourself, it's actually pretty easy. You can just set up a hosted zone in Route 53, even one you don't own. Just add Route 53 to your AWS account and add "example.org" as a hosted zone.
So, anyways, let me know if I'm stumbling in roughly the right direction.

Hey there!
I realize it's been an eon since this was created. I'm just letting you know that we have dramatically simplified the structure of ExAws as we go into 1.0. We would be happy to look at a contribution for Route53 again, but I'm gonna close this for now as most of what is here is related to boilerplate only necessary pre 1.0.
Thanks!

Ben

Thanks for the heads up. Good luck!
On Fri, Jul 22, 2016 at 3:47 PM, Ben Wilson<EMAIL_ADDRESS>wrote:

Closed #108 https://github.com/CargoSense/ex_aws/pull/108.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CargoSense/ex_aws/pull/108#event-732192641, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAsydX-bxDIWi11ZKCuTz3_68JrpmVVks5qYR5XgaJpZM4HP1-a
.


Testing and validation

Project requirements

[ ] Use validations for models.
[ ] Write unit tests for models.

For the User model:
Name must not be blank.
PostsCounter must be an integer greater than or equal to zero.
For the Post model:

Title must not be blank.
Title must not exceed 250 characters.
CommentsCounter must be an integer greater than or equal to zero.
LikesCounter must be an integer greater than or equal to zero.

Added unit specs for all of My models' methods and validations.

User model:
Post model:

These are all my testing file i did and are passing all


Move OBSEA to IFCA-LCG2

Summary
Updating VO SLA OLA to move OBSEA from CESGA-CLOUD to IFCA-LCG2

Related issue :

FYI @aidaph


py_aff3ct on Windows?

Hey I was wondering if there was a guide or handbook on how to install and use py_aff3ct on Windows? Thanks

Update
I was able to successfully compile a .pyd file in build/lib/py_aff3ct*.pyd on MinGW but importing the bfer_rsc.py gives me the following error:
Traceback (most recent call last):
  File "py_aff3ct\examples\full_python\bfer_rsc.py", line 5, in <module>
    import py_aff3ct
ModuleNotFoundError: No module named 'py_aff3ct'

For aff3ct, I used a pre-built version from here() since I don't plan on changing the source code and used the doxygen documentation and corresponding XMLs from the Linux build.
Is there something that I'm doing wrong?


FlexCNN returns all zero result

Hi,
I was trying to compile the FlexCNN HLS source to an Alevo FPGA board using Vitis. I was able to get the bitstream, but when running the bitstream on HW, I found that the total execution time was too short (0.21ms), and the accelerator designs returns all zero result after the kernel is finished.
I did not change anything in the kernel code. I only changed the buffer allocation flags used in the host program a bit to bind the buffers with HBMs instead DDRs, otherwise the XRT would complain [XRT Error]: bad alloc:
  cl_mem_ext_ptr_t GlobMem_BUF_in2_Ext;
  GlobMem_BUF_in2_Ext.param = 0;
  GlobMem_BUF_in2_Ext.flags = 0 | XCL_MEM_TOPOLOGY; // XCL_MEM_DDR_BANK1;
  GlobMem_BUF_in2_Ext.obj = bias_hw.data();

All the 4 input buffers are bound to the same HBM bank, but I do not think this will affect the functionality correctness.
Do you have any suggestions on the debugging?

Hi,
From the runtime, the kernel is not doing any computation at all. Have you modified the makefile? The current version binds the interfaces to DRAM banks, you should replace those with something like this: https://github.com/Xilinx/Vitis_Accel_Examples/blob/master/host/hbm_simple/krnl_vadd.ini

Thanks @atefehsz!
I was using the HLS source files under the SDx_project folder. I used the example Makefile from the Vitis_Accel_Example repo. Actually I tried to bind the arguments with both storage media (i.e. DDR and HBM), but neither of those worked.
I ran into two different issues: the bitstream hangs forever after the kernel is launched. And if I kill the process and re-run it, I got the all-zero results and the kernel does not do any computation.The HW/SW emulation will cause SegFault. So I am not fully sure what is the root cause...

Could you insert print statements in the SW emulation mode to see where the SegFault happens? You can also make sure if you are reading the data that it is supposed to read.

Fixed it. The segfault is casued by a typo of the index.
I am able to launch the kernel the SW emulation now. It prints "Passed0" and hangs forever.

I guess it is normal for the SW to be super slow. It takes around 30-40s for each layer to be processed. I can try the HW emulation and see what will happen.

I assume your problem is solved and close this issue. If you still have a problem, open a new one.

Hi, Dear @Hecmay,
I also try to compile it on the Alevo FPGA board using Vitis 2020.2. But I'm stacked by the bitstream generation under the System directory. I just push the full information to issue #18.
Do you have some suggestions for that? Looking forward to your reply :-)

Hi, Dear @Hecmay,
I also try to compile it on the Alevo FPGA board using Vitis 2020.2. But I'm stacked by the bitstream generation under the System directory. I just push the full information to issue #18.
Do you have some suggestions for that? Looking forward to your reply :-)


Updated example.md, fixed typo

The previous version was unable to bold the second-level title

Could you sign your commits @HsimWong ? more info here: https://github.com/src-d/gitbase/pull/945/checks?check_run_id=185225905 thanks!


chore: update composer.json to make package compatible with symfony 6

just a minimal update to make it work with symfony/finder 6

Thanks @diego-ninja for releasing a replacement :+1: We really need it last 3 months.
https://github.com/diego-ninja/Preloader/releases/tag/v3.0.0

The PR drops support for PHP 7.4 and breaks backward-compatibility. I know PHP 7.4 is almost end of life, but there are still lots of PHP projects staying with PHP 7.
It would be nice to two PRs instead. One to add support for new versions of package symfony/finder (and PHP 8), and another one to drop support for PHP  7, use new features in PHP 8, plus other nice tweaks.