duplicate content of api-overview in reference and concepts sections

This is a...

[x] Feature Request
[ ] Bug Report

Problem:
If possible, re-use the content of concepts/overview/kubernetes-api.md
in reference/using-api/api-overview.md or vice-versa.
The pages are very similar.
Proposed Solution:
Re-use content or link to one of the pages. The reference version has some formatting issues (can be easily fixed).
Page to Update:
concepts/overview/kubernetes-api.md,
reference/using-api/api-overview.md

/close


Investigate Secondary Binding For xla::cond.

Hi all
This is a personal reminder to investigate looking into to binding the xla::cond primitive to dLux::cond. This would be the exact same as jax::cond but it would not compile the branch functions. I just want to do this so the jax.profiler can be used more effectively.
Regards
Jordan.

Can just use if statements. I just need to be careful with compiling.


Allow admins to access targets. Provide more details to admins.


Make prepare silent

Issue Type

Feature request

Molecule and Ansible details
ansible 2.8.5
  config file = None
  configured module search path = ['/home/robertdb/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 3.7.5 (default, Oct 17 2019, 12:16:48) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]
molecule, version 2.22

Molecule installation method (one of):

pip

Ansible installation method (one of):

pip

Desired Behavior
When CI fails (in my case, quite often ;-) ) I need to scroll down and find the error in a long list of output.
I'd like molecule to be more silent and only show the converge output. I'm less interested in the prepare output. (Maybe if prepare failed, show the output, otherwise be (more) silent.
Other molecule users may be interested in the prepare output, so I guess a parameter needs to be introduced to change the behavior of Molecule. A suggestion:
provisioner:
  name: ansible
  options:
    prepare_output: none|all|on_failure

We've definitely had an issue with verbosity being either too little or too much. This could be a good way to start to reduce the noise.
I am worried that it is too many fiddling in the configuration. For each sequence step, we'll have a output none/all/on_failure? We should also provide these on the CLI too which also feels like overkill.
Glad you raised this ticket but I'm not satisfied on how to proceed.
Looking forward to hear more thoughts.

I would be happy of prepare showed output only on failure by default. So maybe register the output and show when prepare is failed.
I could even go as far as to say that I don't need output if any step (even converge) has no errors, but I guess that's a little extreme.

I am closing this because is unlikely any core would implement it but others are welcomed to raise PR that implements this feature.


Stop Button Inactive After Running Scripts

The "Stop" button within the application's interface becomes unresponsive or inactive after initiating script execution. Users are unable to halt the execution of ongoing scripts, leading to potential inconvenience and an inability to control the application's behavior effectively. This issue undermines the intended functionality of the "Stop" button, impeding users from interrupting or terminating script execution as needed.

The issue where the "Stop" button became inactive after running scripts has been addressed and fixed in Version 5.0.


Flake in guarddog_impl_test

Triggered in https://github.com/lyft/envoy/pull/1134, see https://travis-ci.org/lyft/envoy/jobs/244689841:
[----------] 2 tests from GuardDogMissTest
[ RUN      ] GuardDogMissTest.MissTest
external/envoy/test/server/guarddog_impl_test.cc:164: Failure
Expected: 1UL
Which is: 1
To be equal to: stats_store_.counter("server.watchdog_miss").value()
Which is: 2
[  FAILED  ] GuardDogMissTest.MissTest (647 ms)

@dnoe What do you reckon?

I took a look at the code to refresh my memory.  The test uses a mock timer and over-rides the condition_variable.wait_for() timeout by early triggering the condition variable after advancing the mock timer.  But the condition variable timeout IS still active, and it's 500ms per the test.  So I suspect the scenario is that under heavy load the wait_for timeout is expiring and then the loop runs again due to the force check and it will count a miss in both circumstances because the mock time is sufficiently advanced to count a miss.  This would result in the watchdog_miss timeout incrementing twice instead of just once which is what you see in the actual vs. expected results.
This could be "fixed" by making the test allow one-or-greater (not crazy about this solution).  Or the implementation could be changed to only count one miss per forward increment of the last watchdog timestamp.   There could be over counting of misses in a real scenario (if the watched thread has not responded for many 500ms intervals, it will count each as a miss - plus there could be spurious wakeups on shorter intervals).  The fix would be to keep a local copy of watched_dogs_ vector that stores the time the watched thread last responded when counting a miss. The miss counter would only be incremented if the delta is greater than the threshold AND the time is greater than the last time we incremented the counter (ie, the watched thread responded at least one in the meantime).  I don't think the implementation is too difficult, I'll work up a PR unless you think it would be better to go for the simple "fix" to the test.

(I decided against "fixing" the test.  I have a test case for this scenario and 90% of the implementing done, expect a PR shortly)

Most of these sound reasonable. In an ideal world, our CVs would be mockable and we could introduce a mock time source for those as well, but that's probably outside the scope of this work.


If the Content-Type header is not null, the Accept header is not checked for api version

In MediaTypeApiVersionReader.Read, Content-Type is checked for version first -- if it's not null. The problem is that I want to provide the api version in the Accept header, which does not work if there is any content in the Content-Type header. The suggested behaviour is to call ReadAcceptHeader if ReadContentTypeHeader returns null.

There are a couple of edge cases with versioning by media type. I think you've just hit one of them. The rules are basic and meant to be straight forward.

Content-Type - the v={version} parameter indicates the API version when sending content to the server with methods such as POST, PUT, PATCH and so on.
Accept - the v={version} parameter indicate the API version when no content is provided such as GET

While it's more that reasonable to send both Content-Type and Accept in a request that sends content to the server and gets a response, it's arguably not that common. Similarly, while the input API version and output API version can technically be different, it's not a particular common scenario and it can't be intrinsically rationalized on the server side (at least in the ASP.NET stack). The initial action mapping handles the incoming content. If you wanted to handle response content in an API version different from the request API version, you'd have to handle the Accept header yourself. This can be achieved using a custom MediaTypeFormatter in Web API or a custom IOutputFormatter in ASP.NET Core.
If the client is not sending any content, then it should not contain the Content-Type header. When the client does send content, Content-Type always takes precedence over Accept because only the incoming request can be bound to an action. Alternate output in this scenario is something you'd have to customize, if you need it.
The other edge case is the DELETE method. This method is typically not expected to have Accept, Content-Type, or any other suitable header for that matter. This is currently a known limitation and the recommendation is to send Accept even though there will be no content. This is the most compelling scenario to have version-neutral actions, which is not currently supported. This is something I certainly want to enable in the future.
I hope that helps clear things up.

Did this clear things up for you or are you still facing an issue?

At least to me, using Content-Type to specify the API version when Accept exists is not what I would expect.
Content-Type is the media type of the request, and Accept is the acceptable media types of the response.
If using MediaTypeApiVersionReader, you're explicitly versioning the media type, not the "API version".
If my API needs to support versions of requests AND versions of responses, MediaTypeApiVersionReader currently doesn't allow for that. :(

Yes - that's true. This is because there is no way to rationalize that in the platform. This is a more of a limitation of how HTTP is mapped to ASP.NET Core. If Content-Type and Accept don't match, there's no action that can really be taken. A single action is mapped to request (e.g. input and output).
You could potential/partial solve this issue with custom media type formatters, but then versioning would be of media type formatters rather than controllers and actions. That would be fine if the controller and action logic is the same and only the payload is different.
From a REST perspective, I full agree that the input and output media types, even with versions, do not have to match. I'm not sure how this could be implemented on the ASP.NET stack (any flavor). You can do this today purely with media types (say JSON in and XML out), but not with versioning, which also controls what implementation is executed.
If you have ideas or suggestions about how seperate input and output execution logic could be handled, I'd listen to it.


Griefing with Cursed Earth from extra utilities 2 mod

My versions are

Griefprevention -1.12.2-<IP_ADDRESS>1.
Forge-1.12.2-<IP_ADDRESS>15
SpongeForge 1.12.2-2768-7.1.6-RC3616

My issue is when you obtain drop of evil from Extra utilities 2 (Information about the item is below) and get near a claim area that you do not have permission to just get near outside the claim. Right click the drop of evil it will spread out into the claim and grass block will turn into cursed earth.
https://ftb.gamepedia.com/Drop_of_Evil

Also can confirm this is actively being exploited.


Documentation on e2e authentication is incompatible with linked article on refreshing access tokens

The tutorial on this page Tutorial: Authenticate and authorize users end-to-end in Azure App Service instructs the user to add the following "loginParameters" configuration in Azure Resource Explorer:
"loginParameters": ["response_type=code id_token","scope=openid api://<back-end-client-id>/user_impersonation"],

Further down in the article, a link is provide to this section of another tutorial that provides information on how to configure Easy Auth to allow the tokens in the token store to be refreshed. That article tells the user to add the following "loginParameters" configuration , also in Azure Resource Explorer:
"identityProviders": {
  "azureActiveDirectory": {
    "login": {
      "loginParameters": ["scope=openid offline_access"]
    }
  }
}

Individually, these instructions work, but they are not compatible with each other. I've attempted to add both sets of configuration, resulting in this:
  "loginParameters": [
    "reponse_type=code id_token",
    "scope=openid api://<back-end-client-id>/user_impersonation",
    "scope=openid offline_access"
  ],

But this results in a failure to authenticate. If I use the the loginParameters from the first tutorial, I get valid access tokens, but the call to refresh fails with a 401. If I use the loginParameters configuration from the second tutorial, the call to refresh the tokens succeeds, but I receive access tokens with invalid audience parameters.
Is there a way to both receive valid access tokens, as in the first tutorial, and also be able to refresh the tokens as in the second tutorial. Or is there some other way to do this?
Thank you.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 28fe407c-980d-6dfc-305c-63202534bf48
Version Independent ID: 09bed06c-ca37-a511-b4a4-0028e76f8919
Content: Tutorial: Authenticate users E2E - Azure App Service
Content Source: articles/app-service/tutorial-auth-aad.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Additional info:
In Easy Auth V1, the following loginParameters configuration could be used to both retrieve valid access tokens and allow the token refresh procedure to work. If I attempt to use this configuration in Easy Auth V2, I get an error saying the "resource" parameter is not valid:
          "loginParameters": [
            "reponse_type=code id_token",
            "resource=<back-end-client-id>"
          ],

@michaeldaw Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@michaeldaw you just need to merge the two "scope" lines into one with "scope=openid offline_access api://<back-end-client-id>/user_impersonation". I've added some clarification that will be published today.

Hi @cephalin. Thank you very much for responding.
I've done as you indicated. The "loginParameters" now looks like this:
"loginParameters": [
"reponse_type=code id_token",
"scope=openid offline_access api:///user_impersonation"
],
However, I still receive a status code 403 when calling the .auth/refresh endpoint.
The call to .auth/me to get the access token is working correctly.


Add sentences that describe data

Try to create sentences that describe data (datasets, organs, samples, groups), for example
There are 220 datasets

where the number 220 is obtained on the fly from the dataframe.
For example, the number of datasets is the number of rows in the dataframe
number_of_datasets = len(df)
answer = f'The number of datasets is {number_of_datasets}'
st.write(answer)

To compute unique values of a column do
answer = df['names'].unique()
len(answer)

Add these statements at the top of At a Glance


I use 2018.3 but I don't seem to support text with shiny

Am I using in incorrectly?

Hi @HHHHHHHHHHHHHHHHHHHHHCS
Thank you for reporing!

Shader "UI-Effect-Shiny" seems to be broken.
Are there errors in the shaders?

Sorry, I've cloned the latest version. It seems that there's no problem! This is my mistake! Thank you for taking the time to check it out.


chore: drop Macross.Json.Extensions from dependencies

Would you accept a PR which removes this and adds a custom enumconverter like I did here https://github.com/campersau/playwright-dotnet/commit/4d9c4109b9e7b401f7921196d32b2bcb1ecd83e1 ?


Run against existing S3 images.

I guess it would be useful for a lot of people if you could also run this function against pre-existing files on S3. Is there a way to do so? I've seen some people use S3 list for such kind of things. Is this possible using Claudia.js?

You would need to install Claudia globally and then you can use test-lambda command with --event flag. The problem is that you should create separate event file for each already existing image you would like to process. You can use the event_source.json from fixtures as example and update file path, bucket ARN and name and I guess that would be it. Let me know if this works for you.

You can copy S3 objects from existing bucket to a bucket configured to trigger a LAmbda function. Every copied file will trigger a Lambda function. To copy files use 'aws s3 cp'

Thanks, that worked for me. However I still think it is nice to do it without moving all files back and forth. Guess that just isn't supported by the way AWS implemented Lambda events?

@Joostvanderlaan which method worked for you? The one from @sheh1000 ?

Got it working. Lambda function wasn't triggering because of bucket policies.


Steam won't install - cannot download libvulkan1.deb from any mirror

Issue description
I'm trying to install steam on my fresh NixOS installation. I get the error :
curl: (22) The requested URL returned error: 404 Not Found
error: cannot download libvulkan1.deb from any mirror
builder for '/nix/store/ia8g6grzgmajmi0jrlz3b7b4n097klvx-libvulkan1.deb.drv' failed with exit code 1
building '/nix/store/k13k56wnzm6s698n5fsb6x3v3rv0q3kg-libx11-6.deb.drv'...
building '/nix/store/n14ic4g08snkjygxp6zkhmcadp4wcchn-libx11-data.deb.drv'...
building '/nix/store/2msn0xc9dmg2fvihz6ri6dq8sg6wnjxx-libx11-xcb1.deb.drv'...
building '/nix/store/hbhfj73imjv54h3lkx1003qlrprnvl91-libxau6.deb.drv'...
cannot build derivation '/nix/store/ix2kwzv85q503ncbav999r9gy123bryy-steam-runtime.json.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/r15kqc4sn25wq67d9mv8s6lxqwnn237h-steam-runtime-2016-08-13.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/bq005jgyqz74mi9gzgwd4jfv2f5jcpp4-steam-runtime-wrapped.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/npnfqdg5ansavc40rlrnkml5ln0px5jf-steam-usr-multi.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/5jgnnd0cas6kbjdvhxl7paxd6gfj42sc-steam-fhs.drv': 1 dependencies couldn't be built
building '/nix/store/j25lqaishvz7a1rp3dkhj7v4hjm37rb8-steam-original-<IP_ADDRESS>.drv'...
building '/nix/store/lpyrhsaiiqmn73wq8kgifjzjq382nsmv-steam-wrapper.sh.drv'...
cannot build derivation '/nix/store/pr74gm36jv4c65p0sshga8sr86impiqr-steam-init.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/aikkixznbqscqx1qjqvwqggms8y60dpi-steam.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/5k90n0w9ri1n3ca4gpr1fsa6z8mh0k7k-system-path.drv': 1 dependencies couldn't be built

Steps to reproduce

Add steam to your packages in configuration.nix
nixos-rebuild switch

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.76, NixOS, 18.09.932.09195057114 (Jellyfish)`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.1.1`
 - channels(root): `"nixos-18.09.932.09195057114, nixos1803-18.09.932.09195057114, unstable-19.03pre155751.45a419ab5a2"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I can confirm this happens on unstable.

@abbradar looks like this is fetching from your domain, would you mind taking a look?

Looks like the steam runtime deb packages have changed. I think @abbradar is just running a mirror of the packages.
I've just checked out release-18.09, ran update-runtime.py, and installed. I can log into steam and stream content from another computer.

Fixed in https://github.com/NixOS/nixpkgs/pull/49363

I still have the same problem. Do I have to do something special, more than "nixos-rebuild switch --upgrade" et reboot, that I tried without success ?

@seb62 It will take some time for the channel to update, see http://howoldis.herokuapp.com/ or https://channels.nix.gsc.io/nixos-18.09/

Thanks for your replies.
@jethrokuan : as you joigned this issue to the non upgraded unstable channel problem, does it mean that the problem won't be solved in the 18.09 channel ?

I can confirm it works : after cherry-picking the PR in my git repo, I can install Steam.
Thanks for the quick reaction !

@seb62: ah yeah if you're on nixos-18.09 then you shouldn't have to wait too long, since the PR has been backported to nixos-18.09. nixos-unstable channel users will have to wait till that is resolved.


Front - Admin - Send notification

Prerequisites
Description
When the admin create a new newsletter, a notification will be sent to all users of the application.
UX / UI
To design
Technical
Analyse
Proposals :

Use Firebase Functions to trigger the new entry in the collection "newsletters"
If the user authorize the notifications, we save the token of the device in the collection "devices"
The collection "devices" will be secured as follows : allow write if the user is connected and allow read if the uid is the uid of the Firebase service ONLY
Remove the obsolete token
If the user click on the notification, we redirected to the XpeApp application in the newsletter detail page?

Questions :

Use Firebase Functions need to use Blaze package (pay as you go). Allowed ?
Save the token in Firebase is sufficiently secure ?
How to determine that a token is obsolete?
How do I set the redirect path in the notification?

@PiotrFLEURY Can you see the proposals and check with me to answer all the problems ?

Firebase Messaging is decommissioned in 2024
Need to search another solution


Handle REST client exception for unsupported URL

Handles org.springframework.web.client.HttpClientErrorException: 404 when fedora metadata for filename contain special characters.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

coverage: 82.192% (-0.5%) from 82.644% when pulling 26b46caaf28d08a35b8dccce9998298da99af42a on 500-on-metadata-not-found into 73cf3fa50ffded237ada96ff6fe06bb7dcceba0a on main.

@jcreel seeking approval for release candidate deployment to debug production 500 Internal Server Error a bit further.


Bad precision. Choosing of index parameters

Hello!
I run script to evaluate precision of indexed float arrays.
import nmslib
import numpy

number = 100000

data = numpy.random.randn(number, 100).astype(numpy.float32)

index = nmslib.init(method='hnsw', space='l2')
index.addDataPointBatch(data)
index.createIndex(index_params={'post': 2}, print_progress=True)

neighbours = index.knnQueryBatch(data, k=1, num_threads=4)
idxs, _ = zip(*neighbours)
idxs = numpy.vstack(idxs).ravel()
precision = sum(idxs==range(number))*100/number
print("Precision: {}%".format(precision))

The problem is, that I get only 57% of precision. Are there any recommendations to choose index/search parameters to increase precision with minimal time spend on query?

Hi @Aljaksandr
it's hard to tell without the data. What is the dimensionality? Also, is there a chance that you have a lot of ties. So, some things to try:

Increase ef (query time parameter) and/or M (index-time parameter)
Try say k = 10

This low precision is especially surprising given that you search for already indexed data. In this case, the precision would be higher than for searching previously unseen data points.

Hi, @searchivarius
Data are generated according numpy.random.randn() function. 100000 features x 100 floats each.
Increasing efConstruction from default 200 to 400 and M from default 16 to 32 allows reach 91.5% accuracy. But indexing takes much more time. Changing k from 1 to 10 doesn't affect.
Is it correct behavior?

@Aljaksandr methods of k-NN search don't work well for randomly generated high-dimensional data. In fact, in this case, k-NN search stops being a meaningful operation. The only useful operation for such data is a near-duplicate detection, which is usually solved using hashing approaches. For near-duplicate detection a query should be really close to the data your search .


Filtering root level field with JsonPath Expression

Partial matching of request using jsonPath match is not working when I am trying to match the root element.
For example:
"body":{
"jsonMatch":"{\t"itemId": \”<VALUE_A>",\t"stockNumber": "AA323IK",\t"count": "324"}"
}
As per TommySitu
Tommy Situ @tommysitu Jun 22 10:26
@subham1112, the standard JSONPath expression to achieve what you need is<EMAIL_ADDRESS>== 123456)]”
Unfortunatly the JSONPath go library we are using doesn’t work properly if the JSON node in the query is a root attibute.
Please help.

Firstly, we don't support JSONPathMatch if the JSON node in the query is a root attribute. This is a known issue.
Another thing is that your example is using jsonMatch, which should work.

Do we have any plan to fix this known issue?

Any news on this ?

Quickly looking at this, this looks like a duplicate issue of #636.

I don't think the Go JsonPath library that hoverfly uses (https://github.com/NodePrime/jsonpath)  supports root level filtering, for example: https://stackoverflow.com/questions/25031187/jsonpath-selecting-root-level-field-if-satisfies-a-condition
It could be a problem for some users, and I will also raise this issue with that project.

Thanks for the quick reply.
The https://github.com/NodePrime/jsonpath project looks abandoned to me, so I don't think that raising an issue with that project will help.

Have you got any better suggestions @maxtepkeev ?

At least 2 come to mind:

Try to find another active project that implements jsonpath or if there's none
Make a fork of the NodePrime/jsonpath, fix the bug there, make PR which will hopefully be merged someday. Until it's not merged vendor this fork.

We have tried several jsonpath libraries for Golang and none of them does all the jsonpath magics. Also NodePrime/jsonpath is deprecated, hoverfly is now using this jsonpath package: https://github.com/kubernetes/client-go/blob/master/util/jsonpath
There will be a workaround once the matcher chaining feature is implemeted: https://github.com/SpectoLabs/hoverfly/issues/761


Hello everyone, beginner here! util.prompt_for_user_token

Is there a way I can get the redirected link automatically? Also, how can I get the user id when running? Sorry if this is a repost. Thanks for any replies.

There isn't any way to get the redirect link automatically, as the user has to authorize the app's scopes. Although through using flask, I've managed to automate this slightly by using flask's request object to get the current URL and then using the oauth2 object from spotipy to recreate the other steps in util.prompt_for_user_token()
 code = sp_oauth.parse_response_code(request.url)
 token_info = sp_oauth.get_access_token(code)
 token = token_info['access_token']

Hope this helps.

I'm going to try this, thanks!

Is there a way I can get the redirected link automatically?

@JeanPaiva42's answer seems right!

Also, how can I get the user id when running?

From the official app, go to your profile and do "Copy profile link". Your user ID is part of the link.
Hope this helps. Closing for now but feel free to reopen if needed.


postcss-plugin keyword

Please check PostCSS Plugin Guidelines: https://github.com/postcss/postcss/blob/master/docs/guidelines/plugin.md
At least, you forget to add postcss-plugin keyword to package.json.

done


Personalization

Adds personalization to Milo.
More info coming here soon...
Resolves: MWPW-124495
Test URLs:

Before: https://main--milo--adobecom.hlx.page/?martech=off
After: https://cpeyer-manifest--milo-target--adobecom.hlx.page/?martech=off

Closing as the forked branch has been moved to milo and a new PR has been raised.  All PR feedback has been incorporated into the new PR #874


Add IP memory safety proofs

Add CBMC memory safety proof for SendEventToIPTask originally written by Adrian Palacios and now rebased against the current master branch.
I have verified that the proofs work against the current master.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

An earlier version https://github.com/aws/amazon-freertos/pull/623 of this pull request was approved and ready for merge.

The proofs in this pull request are works in progress.
We are committing them now because they are correct and have value, and because we want them to keep current with code changes.
But they make assumptions, and in the next pass we will do a better job of extracting the assumptions, stating the assumptions, and making the assumptions as weak as possible (to make the proofs as strong as possible).


Add regression tests for sandbox pods when no CNI plugins are initialized

What is the problem which i am trying to solve?
As mentioned in PR #10744, when no CNI plugins are initialized, the pod network teardown within sandbox_run.go gets deferred and fails, causing NetNS removal to get blocked. This results in a failed pod creation that cannot be cleaned up.
Describing the solution
To address issue #10768, I've added a regression test to sandbox_run_rollback_test.go to ensure that the sandbox creation fails with the expected error message when no CNI plugins are initialized, as identified in PR #10744. @sameersaeed @mikebrow

please also note that PR #10770 has been opened to resolve the issue of pod network teardown failures blocking cleanup

i think that error can be fixed by
t.Log("Inject CNI plugin initialization failpoint")
conf := &failpointConf{
Add: "1*error(no CNI plugins initialized)",
}
injectCNIFailpoint(t, sbConfig, conf)
adding these 'failpointconf' struct to this. since passing a map[string]string to the injectCNIFailpoint function, but it's expecting a pointer to a failpointConf struct

Please rebase now that https://github.com/containerd/containerd/pull/10839 has been merged.

@nabeelmohamed can you rebase your test and make it work correctly with the update?

Hi @nabeelmohamed, I left some suggestions on your most recent commit - please review and let me know if you have any questions!

Hi @sameersaeed
I’ve made the changes as per your suggestions. Specifically, I’ve:
Removed the detailed PodSandbox state checks.
Updated the test to assert that zero pods are up when the 'no CNI plugins initialized' error is thrown.
Added cleanup logic to remove the pod used for this check.
Included assertions to ensure no pods are up before and after the containerd restart.
Thanks for your guidance. Please let me know if there are any further adjustments needed.

Hi @nabeelmohamed, thanks for making the requested changes. There are still some minor nitpicks I have with the current code based on my previous suggestions.
I've made some additional changes on my own branch. Could you please merge these changes onto your branch?
Please also make sure to rebase and run gofmt if needed, so that the tests pass. Thank you!

Thank you @nabeelmohamed! Just seems like the gofmt you ran in commit 0cbcd3a modified some unexpected files. We would only need to run it on the file we are changing for this test, sandbox_run_rollback_test.go
To fix this, could you please first revert to commit 7526ea1, (i.e. git reset --hard 7526ea1), and then squash the extra 2 commits that you have on this branch (i.e. git reset --soft HEAD~2)?
After doing the above, you can check if you need to run gofmt on sandbox_run_rollback_test.go by running gofmt -l integration from within your containerd directory. If no output is returned, it should be fine to push without any further changes. Otherwise, if you see the test file being outputted, you can run gofmt -s -w ./integration/sandbox_run_rollback_test.go to format the file.

@nabeelmohamed - It seems like the tests are failing due to the current commit message not including a sign-off
Could you please run git commit -s --amend and change the commit message to the following, as mentioned in my previous comment?
Add regression tests for sandbox pods when no CNI plugins are initialized
Co-authored-by: Mohamed Nabeel<EMAIL_ADDRESS>Signed-off-by: Sameer<EMAIL_ADDRESS>
Feel free to reach out to me on the Kubernetes / CNCF Slack if you have any questions on this!

/retest

/ok-to-test

Hi @nabeelmohamed, thanks for making the requested changes - seems like all the tests are passing as expected now.
Could you please rebase once again? Please also make sure to set the commit message using git -s --amend once again, as was mentioned in my previous post

hey @sameersaeed ,i dont know why all of a sudden there is 5 failing test which is not in the previos check. all i done is rebase with upstream and force pushed with commit amend message.can you guide me....

Hi @nabeelmohamed, it seems that there were failures in the latest CI run that are not related to the changes from this PR's test code. You can rerun the tests with the /retest command if needed.
Before you do so, could you please use git commit -s --amend to set modify the commit message to the following?
Add regression tests for sandbox pods when no CNI plugins are initialized
Co-authored-by: Sameer<EMAIL_ADDRESS>Signed-off-by: Mohamed Nabeel<EMAIL_ADDRESS>

Hi @nabeelmohamed, from checking your most recent commit (5ac091f), it seems that the commit message is still set as the following:
Add regression tests for sandbox pods when no CNI plugins are initialized
Co-authored-by: Mohamed Nabeel<EMAIL_ADDRESS>
Signed-off-by: nabeelmohamed<EMAIL_ADDRESS>
As mentioned, could you please change it to the following by using git commit -s --amend and editing the commit message?
Add regression tests for sandbox pods when no CNI plugins are initialized

Co-authored-by: Sameer<EMAIL_ADDRESS>Signed-off-by: nabeelmohamed<EMAIL_ADDRESS>

Hi @nabeelmohamed - sorry for the delay, I didn't receive a notification on your most recent rebase
Could you please rebase once again and tag me or @mikebrow after doing so? Thank you

Hi @nabeelmohamed - sorry for the delay, I didn't receive a notification on your most recent rebase
Could you please rebase once again and tag me or @mikebrow after doing so? Thank you

hey @sameersaeed just rebased and force pushed. also I didn't forget to use git commit --amend command . could you please review this


Out of date wiki link?

The Binaries page of your wiki lists a link to see what pre-built binaries are available, but it lists no binaries since sqlite version 2.2.4. Is this correct, and binaries are not available for v3.0.*, or is that link just out of date?

Thanks for flagging. Yes the link is out of date. The new link however does not have an html page yet, so I need to generate it.

Closing this as this task is a part of / tracked by: #268


refactor: use fully formed URLs

Use fully-formed URLs to be consumed by the UI.
closes #173

I am changing these parts of code to use K8s. I suggest that we don't merge this PR to avoid conflicts. We can keep it open and I will include the concerned parts in my PR and then close it.

Makes sense, thanks!


feat(setup.py): add nltk to install_requires

Description

The nltk library has been added to the list of required dependencies in setup.py.

Fixes #7605
Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

(FYI, I appreciate the candor associated with option 3.)
Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Thanks, this likely should have be done sooner!
Regarding the comment on the linked issue btw, it was a nested import since previously it was an optional dependency (If the import isn't at the top, it's likely an optional dependency)


Use fakeroot and faketime when creating BTRFS filesystems

Description of changes
Without this, a NixOS image created as a normal user will be broken. This matches the behavior in the make-ext4-fs.nix.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Oh, good catch, thank you! And welcome :-)
Just to confirm, the faketime addition is unrelated to the original issue you wanted to fix, yes? You just added faketime in order to copy what make-ext4-fs.nix had been doing, namely to improve reproducibility.
Could you perhaps include, here in the comments, a short paste of the error you encountered before you fixed the issue, for future reference?
If you have the time and energy to go the extra mile and a test (innixos/tests) to ensure we will not regress on this issue, that would be extra awesome. But from my point of view (not being experienced in these parts of nixpkgs myself), this pull request is already fine to be merged as it is.

Thank you @iblech for the review!

Just to confirm, the faketime addition is unrelated to the original issue you wanted to fix, yes?

Correct, I just copied what the ext4 code was doing. The issue encountered was that after booting, nix-build --expr '{}' would fail with a permission error on /nix/var/nix/temproots (specifically, this is the first check home-manager runs before activation and that was the primary thing failing) and there were errors in the log related to / and /nix being owned by a different user (non-root).

If you have the time and energy to go the extra mile and a test (innixos/tests) to ensure we will not regress on this issue, that would be extra awesome.

I would be happy to but I'm not quite sure how one would go about writing a test for this. I don't see any tests even for the make-ext4-fs.nix module to base this off of.


Upgrading to dataTables.Net 1.12.1 causes resize cursor to not show

I upgraded to dataTables.net version 1.11.5 to 1.12.1 and the resize cursor will not longer show.  I can resize the columns, but is is difficult to see where to drag from without the cursor.  I changed the library reference back and forth in my code and it seems the upgraded is definitely the problem.

.......dt-colresizable-hover {
cursor: col-resize !important;
background-color: #eaeaea;
border-left: 1px solid #bfbfbf;
}......


at least one new complete module design in jacdac-ddk

[ ] add entries to device catalog (special category for "reference design")
[ ] photos of prototypes (CAD to start)
[ ] links to hardware design and firmware

I added eagle design

still waiting on altium...


cut location floating number with 6 decimals

-36.84929156444202,174.76839760477938
That's too accurate, we should cut them on pokemon

Leaving as addition

Are there any advantage in cutting it at all? Since it is a float64 in the proto, I think that we should keep raw data as is and not touch it.
(By the way, capture probabilities are float32 in proto.)

@Mygod storage & lack of need for precission above 6 digits

Floats are either 32 or 64 bit - no of decimal points makes no difference to storage size

Yes, but we use 64-bit floats which are meaningless, nope? 32 should be good enough for most needs.

Well you are only saving 8 bytes per row but losing scanned information (server gives you float64). I don't think it's worth this tiny optimization.

The main "problem" I saw was at the front side. When data was sent to users (maps/notifications). But that's application role to round values and not a scanner.

Yeah I am fine to keep it like that. If it's really only 8 bytes per row to save, that would be 4 MB for 500k Pokemon processing per hour. and as Golbat supports now pokemon processing in memory only as well I am fine with keeping the high precision right now :)
If any other thoughts - Feel free to reopen or create a new issue :)


Example doesnt work - Class extends value undefined is not a constructor or null

I cant get tsParticles to work on any environment, I was building a project just using vite and typescript when I started getting this same error " Class extends value undefined is not a constructor or null", after hours of debugging with the bundler I decided to switch to Astro for an easier implementation but I get the same output. Im not running any extra code, I create a new astro project and copy paste the example. It doesnt work with neither Bun or Node

Can you share more details about installed packages?

  "scripts": {
    "dev": "astro dev",
    "start": "astro dev",
    "build": "astro build",
    "preview": "astro preview",
    "astro": "astro",
  },
  "dependencies": {
    "astro": "^4.7.1",
    "astro-font": "^0.0.71",
    "astro-icon": "^1.1.0",
    "astro-particles": "^2.10.0",
    "tsparticles": "^3.3.0",
    "tsparticles-engine": "^2.12.0"
  },
  "devDependencies": {
    "typescript": "^5.4.5"
  },
}

Property 'particlesInit' does not exist on type 'Window & typeof globalThis'.ts(2339)
Type 'Engine' is missing the following properties from type 'Engine': effectDrawers, interactors, movers, pathGenerators, and 19 more.ts(2345)
Property 'particlesLoaded' does not exist on type 'Window & typeof globalThis'.ts(2339)

https://github.com/tsparticles/astro/issues/22#issuecomment-2002506209 Same problem as here


404 when Unit Testing Dingo API Routes

I've seen issue #571, #540 and a few others, but I have no clue as to how they correlate to my problem because I'm not protecting my routes with any Middlewares nor I'm using WithoutMiddleware trait.
I have a working endpoint routed like this:
$api = app('Dingo\Api\Routing\Router');

$api->version('v2', function ($api) {

    $api->get('/', function(){
        return 'hi';
    });

    $api->get('stores', 'App\Http\Controllers\v2\StoresController@index');
    $api->get('stores/{slug}', 'App\Http\Controllers\v2\StoresController@show');
});

with these Environment Variables
API_STANDARDS_TREE=x
API_SUBTYPE=prime
API_DOMAIN=api.local.puphpet
API_VERSION=v2
API_NAME="App Name"
API_STRICT=false
API_DEBUG=true
API_DEFAULT_FORMAT=json

And I can easily make a call for it using Postman, AngularJS or even a wget will work when running wget http://api.local.puphpet/prime-laravel/public/stores
But with my Unit Test, I only get 404.
<php>
        <env name="APP_ENV" value="testing"/>
        <env name="DB_CONNECTION" value="sqlite_testing"/>
        <env name="API_STANDARDS_TREE" value="x"/>
        <env name="API_SUBTYPE" value="prime"/>
        <env name="API_DOMAIN" value="api.local.puphpet"/>
        <env name="API_VERSION" value="v2"/>
        <env name="API_DEFAULT_FORMAT" value="json"/>
        <env name="API_STRICT" value="false"/>
        <env name="CACHE_DRIVER" value="array"/>
        <env name="SESSION_DRIVER" value="array"/>
        <env name="QUEUE_DRIVER" value="sync"/>
    </php>

The function looks like this
    /**
     * @tests
     */
    public function it_should_get_all_stores() {
        $collection = factory(Store::class)->times(3)->make();

//        $result = $this->call('GET', 'http://api.local.puphpet/prime-laravel/public/stores', [], [], [], ['Accept' => 'application/x.prime.v2+json']);
//        dd($result);    // Message 404 Not Found

//        $result = $this->get('http://api.local.puphpet/prime-laravel/public/stores');
//        dd($result);    // Message 404 Not Found

        // $this->get('/', ['Accept' => 'application/x.prime.v2+json'])->dump();    // Gives 404
    }

None of these options works.
This is my TestCase
class TestCase extends Illuminate\Foundation\Testing\TestCase {
    /**
     * The base URL to use while testing the application.
     *
     * @var string
     */
    protected $baseUrl = 'http://api.local.puphpet/prime-laravel/public';

    /**
     * Creates the application.
     *
     * @return \Illuminate\Foundation\Application
     */
    public function createApplication() {
        putenv('DB_CONNECTION=sqlite_testing');

        $app = require __DIR__ . '/../bootstrap/app.php';

        $app->make(Illuminate\Contracts\Console\Kernel::class)->bootstrap();

        return $app;
    }

    public function setUp() {
        parent::setUp();
        Artisan::call('migrate');
    }

    public function tearDown() {
        Artisan::call('migrate:reset');
        parent::tearDown();
    }

}

After much digging into the vendor classes and a lot of die and dump, I realized that the HostValidator was rejecting the calls, so here are my findings:
I run this on a Puphpet / Vagrant / Virtual Box setup with a Linux (CentOS) environment. My host machine is Windows. When I was making calls to the API, I was using Windows, so my hosts file would redirect to the Puphpet machine and it would get routed just fine. When trying to do it using Unit Test, I didn't realize that I had to use <IP_ADDRESS> to make it work.
I changed my phpunit.xml to
       <env name="API_STANDARDS_TREE" value="x"/>
        <env name="API_SUBTYPE" value="prime"/>
        <env name="API_DOMAIN" value="<IP_ADDRESS>"/>
        <env name="API_VERSION" value="v2"/>
        <env name="API_DEFAULT_FORMAT" value="json"/>

and in my TestCase I changed the BaseURL like
protected $baseUrl = 'http://<IP_ADDRESS>';

and my call works like this
$this->get('/stores', ['Accept' => 'application/x.prime.v2+json'])->dump();

I ran across the same problem and I had used a virtual host for the app, changing ;API_DOMAIN' solved it for me too, thank you for this :)


Changed config parser priority.

Config priority:
command line > --config method.py > default from parser.py
First parser run to get the parameters to load f{args.method}.py
If we provided a --config file, loads it. Else, tries to find one for the method.
Push the default values for this method to the parser Second parser run to get the final parameters.
I also changed back the default values to parser.py as there was no longer a need for the dict to stay in a separate file.

Hi, @mauriciodev,
We'd like to express our appreciation for your valuable contributions to OpenSTL. Your efforts will significantly enhance the project's quality. However, we have already tackled the conflict of adjusting some important training hyperparameters (e.g., the learning rate) by the config and the arg parser. Therefore, we may not accept your pull request. Thanks again for your efforts!

Hi, @Lupin1998 . Thank you very much for putting your attention to this subject. I will try to explain exactly what I was trying to fix with that pull request.
Since the previous change, the example notebook stopped working, because we no longer have a default value for the learning rate scheduler. This was easily fixed by adding the "onecycle" parameter to the config. But that got me into looking at the changes made and I understand that now we have a dict of default values hardcoded in tools/train.py. That's actually a problem, because the colab do not use tools/train.py, and default values were already defined in parser.py.
Then I tried to test the EarlyStopping procedure. I added "early_stop_epoch = 10" to the config file (configs/mmnist/simvp/SimVP_gSTA.py):
tools/train.py -d mmnist -c configs/mmnist/simvp/SimVP_gSTA.py --ex_name mmnist_simvp_gsta
This doesn't work as expected, because "-c" is applied after parsing the command line argument. The config is updated with what was set in the config file. So the default "-1" was already in place and could not be overwritten by the value provided in SimVP_gSTA.py.
Currently, the parameters in the command line, SimVP_gSTA and in train.py have different priorities. "epoch" has a different priority than "early_stop_epoch", for example. I tried to make them have a single sequence:
command line > --config SimVP_gSTA.py > default from parser.py
To do that I realized that the command line must be last parameter to update the config. But since it has it's default parameters, we should provide the SimVP_gSTA.py modifications as default values to the parser. Thus we first get the config file from the command line, read it's default values and after that we parse the command line again using those default values.

Hello, @mauriciodev. The problem you mentioned is quite important, and we try to solve it in the latest commit. We create default_parser() to provide the default values and update the config after filling values in the given config file. Once again, we express our great gratitude for your contributions to OpenSTL, and it would be appreciated if you could run the latest version to check whether this issue is really solved.


In "Draw" mode with Apple Pencil, allow panning with finger

Pan with single finger
Zoom with 2 fingers

https://user-images.githubusercontent.com/52999758/219848545-196db3e2-fdcb-45d7-95ba-361435db0e34.MP4

The one finger here on mine doesn't do anything, it should drag the screen just like in miro.app or freeform

This is a very important ux feature

Would also like to comment that this is the main feature of other drawing apps (e.g. OneNote) that is superior to Excalidraw

after using other apps I saw that this could be very problematic because palmreject despite being good is not 100%, this feature can lead to undue drags

after using other apps I saw that this could be very problematic because palmreject despite being good is not 100%, this feature can lead to undue drags

I can envisage this being an issue but at least in my experience of OneNote this has never been a problem for me (in fact I actually cannot pan at all if I try to with my palm) so it seems there "should" be some way of making this near 100% reliable

@tim-forrer are you talking about OneNote desktop app or the web app?
@zsviczian I believe you've enabled panning/zooming in pen mode for Obsidian, or am I mistaken? If true, how did you get around the potential UX issues?

@dwelle

are you talking about OneNote desktop app or the web app?
The app for ipad.

I just tried it on both the web app and the desktop app (by mirroring to ipad) and neither worked so it seems to only be a thing on the iPad app (maybe mobile too but I don't own an iphone)

The plugin on Obsidian iPad version has quite nice experience, if possible, can we just merge the features provided by this plugin and have a iPad mode on the web page?
BTW, I still hope that we can have an excalidraw iOS app to be released soon...


make custom plugin

make plugin payment (webmoney) for posting paid ads. write the cost and deadlines.
details when ordering. payment for work is guaranteed

Please don't post job ads here, this is for issues regarding Grav.  Feel free to ask in our Discord chat though. https://chat.getgrav.org/

ok


Error 500

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows, Mac]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

hey @jkboscolo, thanks for reporting this, but could you please fill out the template to give us a bit more information on how you ran into this error?


Typescript error when using variant on Text

Describe the bug
I want to use variants on Text, but it's throwing an error
To Reproduce
Define Text variant in extendTheme. Use that variant in Text component.
Also some elements, including Text are warning that all(a lot) props are required after upgrading to 3.2.1
Everything works as expected when running on device, just the error appears. I can't use typecheck pre-commit hook :(
Expected behaviour
No errors
Screenshots

Platform

NativeBase version [3.2.1]
Device: [iPhone Xr]
OS: [iOS14.7.1]
React Native version [0.66.0]
node [v12.14.1]
npm [6.13.4]

This is happening, because in default theme Text has no variants, and so variant prop in not defined. I'm not sure if that's intentional.
As a workaround you can extend the ITextProps interface manually:
const theme = extendTheme();
type CustomThemeType = typeof theme;

declare module 'native-base' {
  type ICustomTheme = CustomThemeType;

  interface ITextProps {
    variant?: keyof CustomThemeType['components']['Text']['variants'];
  }
}

This helped me a lot, but I had to move the declaration outside the extendTheme since It was throwing a typescript error on ['variants'].
This is my solution, hope it helps.
import {extendTheme, ITheme} from 'native-base';
declare type IExtendThemeParam = ITheme | Record<string, any>;

const customTheme: IExtendThemeParam = {
  components: {
    Text: {
      variants: {
        caption: {
          color: '#ccc',
        },
      },
    },
  },
};

const theme = extendTheme(customTheme);
type CustomThemeType = typeof customTheme;

declare module 'native-base' {
  interface ITextProps {
    variant?: keyof CustomThemeType['components']['Text']['variants'];
  }
}

This has been resolved in NativeBase 3.2.2 . Please let us know if you face any issue.

@makkarMeenu variants are not working for Text component in NativeBase 3.2.2. When I use any of my variants it will be completely ignored

@makkarMeenu variants are not working for Text component in NativeBase 3.2.2. When I use any of my variants it will be completely ignored

We cannot reproduce it, you can share a link of the snack if you face the same issue, we will re-open this issue.

@makkarMeenu variants are not working for Text component in NativeBase 3.2.2. When I use any of my variants it will be completely ignored

We are unable to reproduce this. You can share your issue with repo link, so that we can help you regarding this.

Thank you. Sure, I will prepare codesandbox today


SES v2 send_email

Amazon announced a new version of the SES API earlier this week.
I would like to use the new send_email call with moto.
In boto3 this appears as boto3.client('sesv2').send_email(), compared to the old boto3.client('ses').send_email() and .send_raw_email().
I haven't yet looked into the details of the differences. The arguments have changed, and there's a few new ones.
In general, what does it take to add a new service to moto when it's an upgrade of an existing service? I expect that it should be relatively easy to just add a function that wraps around the old version in moto (or the other way around), compared to the complexity of implementing v2 from scratch separately to the existing v1. (In fact, the APIs should refer to the same underlying resources.)
Related to #5075

Hi @mdavis-xyz! As Moto intercepts the underlying HTTP request that boto3 sends to AWS, implementing any service consists of two things:

Discover and decode the format of the HTTP request/response.
Implement the actual mock-behaviour

The first part will always need to happen, for any service. Once that's done, the actual mock-behaviour can probably just call the SES backend instead, and reuse that logic,  yes.
If you want to have a go at implementing this, the Contributing-section of our documentation might be useful. I haven't looked into the details of this particular service yet, so I can't be much more specific. Let me know if you get stuck though, happy to help out.

I can take a look at this. Should I go ahead?

Sounds good to me @denny-sam - I'm not aware of anyone else working on this. Happy to help out if you run into any issues!

@denny-sam did you make a start on this?
In particular I don't understand how to write a new service such that it shares resources with an existing service.
e.g. Users should be able to create an SES domain identity with the v1 API, then send emails with that identity using the v2 api.

@mdavis-xyz  Within a particular service, you can directly access the backend of other services. See this example, where ELB needs to access EC2 resources:
https://github.com/getmoto/moto/blob/5d2f2bca8c3b3922127594835fad0c39345d6616/moto/elb/models.py#L282

@denny-sam Any chance this will be implemented? :)

Hey @denny-sam, I can take a look if you haven’t made much progress yet


[BACKPORT v1.4] core/plugins: fix install includes

Backport of #1982

Nevermind that doesn't work.


Adjusting hive

Closes https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/2275
Verified that, installing with /allusers switch, the hive in registry is HKCU

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@kaarins PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@gacarini , I just merged this, but can you please confirm that this change is correct? If it isn't, I will revert. Thanks!


240 dd pfx regr

What
Fixed regression where _design/ had to be specified for DesignDocumentManager even though it was documented as being optional.
How

Added missing doc on DesignDocumentManager.remove(String, String)
The optional _design prefix functionality was regressed, ensured that _design/ is added to design document IDs when using the DesignDocumentManager class.
Since the URI path builder already un-escapes the first “/“ in _design or _local document IDs there is no need to build the path elements separately so removed that added complexity from DatabaseURIHelper.
Updated CHANGES.md.

Testing
Added new tests to DesignDocumentsTest for optional prefix cases:

designDocGetNoPrefix()
designDocGetNoPrefixWithRevision()
designDocRemoveNoPrefix()
designDocRemoveNoPrefixWithRevision()
designDocRemoveNoPrefixWithObject()
designDocPutNoPrefix()

Added new test to DesignDocumentsTest to validate deleting a document with an index:

deleteDesignDocWithIndex()

Reviewers
reviewer @mikerhodes
Issues
Fixes #240

+1

LGTM +1


Extension crashes and hit 100% CPU usage

Hey there,
I found a bug with the latest version of vscode-eslint extension that I want to report. This bug basically crashes the extension, and because of that, it leaves a process with 100% CPU usage that runs forever, also, if you try to restart the ESLint server and again face this issue, you'll end up with multiple processes that consume the CPU and eventually drain your battery very fast.
Problem
In the latest version 2.4.0 and the 2.2.6 version, there is a bug that if you throw an error in the middle of the code (that causes the rest of the code to become useless) and you try to reformat the code after it, the vscode-eslint extension will crash and the process will hit 100% CPU usage and remains forever:
throw new Error('something')
// some code
...

Here is the .eslintrc for reproducing the error:
{
  "parser": "@typescript-eslint/parser",
  "extends": [
    "plugin:@shopify/esnext",
    "plugin:@shopify/typescript",
    "plugin:@shopify/prettier",
    "prettier",
    "plugin:prettier/recommended"
  ],
  "parserOptions": {
    "ecmaVersion": 2018,
    "sourceType": "module"
  },
  "rules": {
    "@typescript-eslint/no-unused-vars": [
      "error",
      {
        "argsIgnorePattern": "^_"
      }
    ],
    "valid-jsdoc": ["warn", { "requireReturnType": false, "requireParamType": false }],
    "@typescript-eslint/explicit-member-accessibility": 0,
    "@typescript-eslint/explicit-function-return-type": 0,
    "@typescript-eslint/no-parameter-properties": 0,
    "@typescript-eslint/interface-name-prefix": 0,
    "@typescript-eslint/explicit-module-boundary-types": 0,
    "@typescript-eslint/no-explicit-any": "off",
    "@typescript-eslint/ban-types": "off",
    "@typescript-eslint/no-var-requires": "off"
  }
}

Solution
I managed to solve the problem by downgrading the vscode-eslint to 2.2.2.

Since something like this is very version and source code dependent can you please provide me with a Github repository I can clone that demos this.

And what happens when you validate the file in the terminal using the eslint CLI after the server hangs / crashed?

I did a quick test locally with one of my setups and it doesn't happen for me.

Just want to share that I also had this issue and had to downgrade to 2.2.2. I just killed the process so I'm sorry don't include any reproduction steps.

I had the same issue, but haven't been able to reproduce this myself, sorry!

Could you enable tracing using
	"eslint.trace.server": "messages",
	"eslint.debug": true,

and provide me with the content of the ESLint output channel when this happens.

I can reproduce this issue, I use neovim's built-in LSP to request LSLint for formatting my code asynchronously:
client.server_capabilities.documentFormattingProvider = true
client.request("textDocument/formatting", {}, nil, bufnr)

and the CUP of the node process reaches 100% when I exit neovim immediately after the request was sent:
https://user-images.githubusercontent.com/17523360/235344572-b4ed42f4-19f6-4adb-90ee-b28bc2f4e098.mp4
When I comment on the code above it goes working. So I guess ESLint might be in a dead loop due to the LSP client of neovim closing.
I'm sorry that not sure how to debug it, since it needs to be triggered after neovim exits :(

I would like to mention that I faced the same problem and had to switch back to version 2.2.2. I terminated the process, so I regret to inform you that I cannot provide any steps to replicate the issue.

As said before this can depend on many factors and without a repository I can clone and some steps it is very hard to tell what is happening.
Regarding neovim: the server has some support to exit itself when the hosting process dies. It might be that neovim is not setting this up correctly. The server has a command line argument --clientProcessId which it will use to monitor the client process.

This issue has been closed because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

@dbaeumer , Just beginning to investigate this, but I had been experiencing very high CPU usage (and fan going crazy) on a brand new Dell XPS 15". I tried turning off every extension in VSCode except ESLint, and the fan has been very quiet ever since. I know this is not enough information for you to repro, but just wanted to corroborate what others are seeing. I'll report back if and when I learn more.


GH-35027: [Go]: Use base64.StdEncoding in FixedSizeBinaryBuilder Unmarshal

This changes FixedSizeBinaryBuilder's Unmarshal to use base64.StdEncoding instead of base64.RawStdEncoding. The previous implementation caused an error when unmarshaling from JSON previously produced by a FixedSizeBinary array instance.
I also added a test for Marshal/Unmarshal to set the expectation that these operations should mirror one another.

Closes: #35027

I'm not sure why some tests are failing for certain architectures and not others. Any help/advice here would be appreciated 🙇

@hermanschaaf It looks like the common thread is an issue with Go 1.18 (as opposed to Go 1.17 which is succeeding)

I'm not sure why some tests are failing for certain architectures and not others. Any help/advice here would be appreciated 🙇

Looks like the go 1.18 tests are more comperehensive, should work now.


rlp: new package

Now that I have shored up encode/decode, I will add error conditions. I suspect most of the error checking will have to do with the stated size of data vs. the actual size of data being parsed.

OK. Going to add some tests for the decoding error conditions and then I think we'll be ready for final review and merge.


Add Chaos Frontend Toolkit to the list of tools

This PR adds Chaos Frontend Toolkit to the list of tools.
Chaos Frontend Toolkit is a browser extension (Chrome, FF, Edge) that applies Chaos Engineering experiments to web apps.
The experiments cover network, timers, history, accessibility, localization, inputs, ...
(Re-opened from #114 after a failed rebase)

Thanks @Errorname


Heatmap   SetTicks

I am using the Heatmap to display spectral data.  I have  used TickGenerator and RenderManager to successfully make a Y-axis.  I am struggling with the time-based X-axis.  I found this example for a regular chart using SetTicks but that does not seem to be available for a Heatmap chart?    Is there an example of how to convert the heatmap index-based X-axis to show a time-based axis?
ScottPlot.Plot myPlot = new();
// use manually defined ticks
double[] tickPositions = { 10, 25, 40 };      // I assume that these would be the heatmap array index values?
string[] tickLabels = { "Alpha", "Beta", "Gamma" };
myPlot.Axes.Bottom.SetTicks(tickPositions, tickLabels);

I think I found a solution just using ScottPlot.TickGenerators.NumericAutomatic and Plot.Axes.Bottom.TickGenerator and then just make the function return the associated time as needed.

Hi @woodynwc, thanks for your original question, and it seems like you resolved this issue! If you have further questions let me know and we can open this back up.
Tangentially related, see https://github.com/swharden/Spectrogram


IllegalStateException: This is not a JSON Array.

15:28	Plugin Error: Android Localizationer threw an uncaught IllegalStateException. Disable Plugin
15:28	IllegalStateException: This is not a JSON Array.

同问

我也是报	IllegalStateException: This is not a JSON Array，怎么解决？

下午 2:43	IllegalStateException: This is not a JSON Array.


Provide Ubuntu package meta data files

In the XCM repository, include meta data files necessary for building an Ubuntu .deb package.

Such files do not belong in the upstream source repo.


Bump version of Hadoop dependencies to 3.3.6

Description
Upgrade the version of Hadoop dependencies from 3.3.4 to 3.3.5
Changed:
in file plugins/repository-hdfs/build.gradle:
upgrade org.apache.hadoop:hadoop-client-api, org.apache.hadoop:hadoop-client-runtime, org.apache.hadoop:hadoop-hdfs to 3.3.5
in file test/fixtures/hdfs-fixture/build.gradle:
upgrade org.apache.hadoop:hadoop-minicluster to 3.3.5
Issues Resolved
Hadoop library introduces many transitive dependencies to OpenSearch, and using outdated dependencies is a red flag for some security scanners.
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

test failure occurs in the tests:
    org.opensearch.repositories.hdfs.HdfsBlobStoreContainerTests.testReadOnly
    org.opensearch.repositories.hdfs.HdfsBlobStoreRepositoryTests.testDeleteBlobs
    org.opensearch.repositories.hdfs.HdfsBlobStoreRepositoryTests.testContainerCreationAndDeletion
    org.opensearch.repositories.hdfs.HdfsBlobStoreRepositoryTests.testMultipleSnapshotAndRollback
    org.opensearch.repositories.hdfs.HdfsBlobStoreRepositoryTests.testList
    org.opensearch.repositories.hdfs.HdfsBlobStoreRepositoryTests.testSnapshotAndRestore
    org.opensearch.repositories.hdfs.HdfsRepositoryTests.testCreateSnapshot
    org.opensearch.repositories.hdfs.HdfsRepositoryTests.testCleanup
    org.opensearch.repositories.hdfs.HdfsRepositoryTests.testListChildren
    org.opensearch.repositories.hdfs.HdfsTests.testSimpleWorkflow

As a part of https://issues.apache.org/jira/browse/HADOOP-11867, it looks like there were new additions to the low level class RawLocalFileSystem which takes care of file system operations within the Hadoop library.
The data stream operations has a new IOStatisticsAggregator operation which, I presume, takes care of the statistics aggregation when the stream is closed .
This class internally uses parallelStream utilizing the underlying implementation of Java ConcurrentHashMap, which has it's parallelStream based of ForkJoinPool

These bulk operations accept a parallelismThreshold argument. Methods proceed sequentially if the current map size is estimated to be less than the given threshold. Using a value of Long.MAX_VALUE suppresses all parallelism. Using a value of 1 results in maximal parallelism by partitioning into enough subtasks to fully utilize the ForkJoinPool.commonPool() that is used for all parallel computations. Normally, you would initially choose one of these extreme values, and then measure performance of using in-between values that trade off overhead versus throughput.

We did have a similar problem earlier (Ref: #6538) with ForkJoinPool creation because SecureSM within OpenSearch blocks the modifyArbitraryThreadGroup permission within the codebase.

Hi @reta! Do you have idea about the above failure while upgrading the hadoop version to 3.3.5 or 3.3.6?

Hi @reta! Do you have idea about the above failure while upgrading the hadoop version to 3.3.5 or 3.3.6?

Hm ... I think I know why, some time ago we've run into an issue that Hadoop was using ForkJoin pull for some operations, as @kotwanikunal mentioned, let me take over this pull request,  @tlfeng no objections?

let me take over this pull request, @tlfeng no objections?
@reta No problem, please feel free to close this pull request.

@owaiskazi19 @tlfeng so it is really tricky, it is feasible in general (to supply own ForkJoinPoolFactory) but the problem is that it is one per whole application (the plugins could not change it). I will look into other ways, may be we could submit the change to Hadoop for that.

@owaiskazi19 @tlfeng so it is really tricky, it is feasible in general (to supply own ForkJoinPoolFactory) but the problem is that it is one per whole application (the plugins could not change it). I will look into other ways, may be we could submit the change to Hadoop for that.

I see. What do you think of adding the permission in the policy file? I know this is not the right solution to go around this problem?
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "modifyThreadGroup";

Also SOLR has done similar to pass own ForkJoinPoolFactory here.

@owaiskazi19 @tlfeng so it is really tricky, it is feasible in general (to supply own ForkJoinPoolFactory) but the problem is that it is one per whole application (the plugins could not change it). I will look into other ways, may be we could submit the change to Hadoop for that.

I see. What do you think of adding the permission in the policy file? I know this is not the right solution to go around this problem?
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "modifyThreadGroup";

I see. What do you think of adding the permission in the policy file? I know this is not the right solution to go around this problem?

That won't help because the default ForkJoinPoolFactory overrides the context

Also SOLR has done similar to pass own ForkJoinPoolFactory here.

Haha, I ended up very close  :D but the issue is - it has to go to OpenSearch core, when plugin is initialized  - the common pool is (very very very likely) already created.

@reta looks like your were able to upgrade hadoop to 3.3.6?

@reta looks like your were able to upgrade hadoop to 3.3.6? Will this change affect the downstream plugins?

@owaiskazi19 Correct but there is a catch - we need to use custom ForkJoinPoolFactory, we probably need to think if that opens up any undesired flaws.


Splitting window building-process in multiple builder functions does not show all windows but only the last one beeing called

Is there an existing issue for this?

[x] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
I have multiple windows that i need to build and in order to keep the main function neat and clean i wanted to split the build process of these windows into their own files/build functions.
// main.rs

let app = app::App::default().with_scheme(app::Scheme::Gleam);

// ...

// build new entry window
new_entry_window::build_ui();

// build loading window
loading_window::build_ui();

// build info window
info_window::build_ui();

// build main window
main_window::build_ui();

app.run().unwrap();

// loading_window.rs
// example builder of one of the windows

pub fn build_ui() {
    // app state
    let state = app::GlobalState::<AppState>::get();
    let cfg = state.with(|s| s.cfg.clone());

    // screen working area
    let (x, y, w, h) = app::screen_work_area(cfg.screen_num);

    // loading window
    let mut loading_window = window::Window::default().with_size(400, 90).center_screen();

    loading_window.set_label("Lade PDF...");
    loading_window.make_modal(true);
    loading_window.set_pos(x + (w / 2 - 400 / 2), y + (h / 2 - 90 / 2));
    loading_window.set_cursor(enums::Cursor::Wait);

    let mut loading =
        image::PngImage::load(std::path::Path::new("assets/hourglass1.png")).unwrap();

    loading.scale(60, 60, true, true);

    let mut loading_frame = frame::Frame::default().center_of_parent();

    loading_frame.set_image(Some(loading));

    loading_window.end();

    // add window to app state
    state.with(move |s| s.wnd_load = loading_window.clone());
}

I am using the global state to be able to get a referance to one of the windows. When i .show() on any window, it only shows the last one. In this case the main window and not my "info" window which should open ontop of the main window. The main window gets displayed tho. Both have the .show() method beeing called on them.
I have also tried to use the global state in the main rust file to show both windows but it has exactly the same result.
I also noticed that the window i want to show too is flickering at startup so it gets created but closes immediatly and only the last one beeing called is visable.
My guess is it has something to do with scoping of the build functions. In that case, what is the best way to split out the build process of larger projects without that happening?
What is the expected behavior?
The main window and the info window should both be visible at the same time.
Version
master
Operative System
Windows
Do you have any log output?
No response

The code seems unrelated to iced. iced exposes no way to build a window.

I'm so sorry i had the wrong repository selected!! It's a fltk-rs related problem.
Sorry for the inconvinience :(


WordPress Extra File Types: Request for adding .docx extension

Hi David,
Sorry for bothering you in Github. I found you are the author of https://www.airaghi.net/blog/2015/01/02/wordpress-extra-file-types/?hilite='WP'%2C'Extra'%2C'File'%2C'Types'
The Wordpress plugin has many file types built-in, but not docx - MS Word main stream file. I am wondering if possible for you to add that.
Name: MS Word
extension: docx
MIME: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Refer to:

https://stackoverflow.com/questions/4212861/what-is-a-correct-mime-type-for-docx-pptx-etc
https://wordpress.org/plugins/wp-extra-file-types/

Thanks very much.
Paul

you can configure new file types by yourself using plugin's settings page.
have you already tried to do that ? is so, how have you configured it ? (a screenshot to see could be very useful to help you)


Override styles.

Is it possible? if it is, could you point me to an example?
Thank you for this library

Hi @zomars, you can use customRender prop to override styles

This will let me override each individual item but not the whole list or container isn't it?

right, you can style the input and each list items but not the list. I have to think about this. Do you have any ideas ?

Maybe pass a customListRender or customContainerRender with a the results as an array prop?

Good idea. I will do as soon as I can but if you want to make a PR to make it fast, you are welcome :)

@zomars Just release v3.4.0 with customContainerRender prop


[XLA PjRT] Ongoing progress and future plan of PjRT distributed runtime

Hi TF developers,
This issue intends to get more knowledge about the ongoing and future plan of XLA PjRT, especially on the distributed runtime of GPU.
Although there are some related commits (e.g., 44e771aa50ad8be454b7f4469ad04a815d03cca1 and 8a72c4466a0f44de9bd1cfbf47a701727731036c), existing PjRT code seems quite preliminary in supporting distributed training on multiple hosts -- As far as I could see, it now only provides basic control operations such as setting up the connections and sharing GPU topology, and it is not trivial to run a real distributed demo with communication.  Another issue https://github.com/google/jax/issues/2731 seems also aligns with this point.
So I would like to confirm if TF team is also working on this and may probably release some new features soon. For now, our   interest is on using PjRT to run HLO with collective or P2P communication, possibly including all-reduce, all-gather, reduce-scatter, send/recv, etc.
Any response will be appreciated. Thanks.

/cc @mhmoodlan

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Bump to v0.2.3

Added API to reset peripherals
Improved API of timer.
Separation of TIM reg and TIM pin interface

bors r+


:bug: fix issue #544

only add activeMath attribute for the url config in navbar

activeMatch is already supported.


typo in Debian dependency command

Correcting libuwind8 to libunwind8

@dzsquared : Thanks for your contribution! The author, @stevestein, has been notified to review your proposed change.

Thank you @dzsquared  #sign-off

@craigg-msft: I'm sorry - only the author of this article, @stevestein, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Implements customized kout/kneighbor, multi-node-shortest-path, jaccard-similar and template-paths

already implemented in #1157


fix: handle short cache for console correctly

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


[PROCS-4328] Add ECS EC2 e2e test for process checks in the core agent.

What does this PR do?
Adds an e2e test for running the process checks in the core agent in ECS EC2. The tests are marked as flakes because that issue has yet to be resolved. ECS Fargate will come at later time and in a different suite. The existing suite name was updated to reflect this so that it is better differentiated.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Running the tests locally (without the flake marker) works.
❯ new-e2e-tests.run --targets=./tests/process --run=TestECSEC2TestSuite
...
=== RUN   TestECSEC2TestSuite/TestECSEC2ProcessCheck
    suite.go:251: No change in provisioners, skipping environment update
=== RUN   TestECSEC2TestSuite/TestECSEC2ProcessCheckInCoreAgent
    suite.go:251: No change in provisioners, skipping environment update
    print.go:225: Stack up took 2m4.7042065s
...
--- PASS: TestECSEC2TestSuite (269.10s)
    --- PASS: TestECSEC2TestSuite/TestECSEC2ProcessCheck (40.03s)
    --- PASS: TestECSEC2TestSuite/TestECSEC2ProcessCheckInCoreAgent (145.85s)
PASS
ok  	github.com/DataDog/datadog-agent/test/new-e2e/tests/process	272.150s

DONE 3 tests in 291.910s
All tests passed

/merge


Associated Edge Data

I'm looking at graph for backing a RVSDG implementation which is centered around edge "kinds" that hold various data, ex a value edge or a control flow edge. The ability to store data within edges and to query against it effectively (sometimes you just want to see state nodes from a given source to destination) is essential for that, so that'd be a really great addition.
This also requires the ability to have multiple (possibly identical) edges going between nodes and the multiplicity of the edges being retained, if that's a concern.
Thanks!

@Kixiron feel free to reopen if you don't think that the current state of the crate is sufficient for your use case.


Add a new Sierra reader that picks up deleted records

For https://github.com/wellcomecollection/catalogue-pipeline/issues/2325
The problem
Our queries for Sierra are only picking up modified records, not deleted records. I don't know if this was always broken or has broken since we originally wrote it; either way our existing queries aren't sufficient.
This is causing problems for Collections Information's workflows, and is obviously the wrong behaviour for the pipeline.
Idea #1: modify the Scala apps
I had a brief look at modifying the existing Sierra reader code, but it's somewhat gnarly and I think it would need significant changes to support this new type of query.
In particular, it writes records in bulk an S3 bucket, which then get "demultiplexed" by a Lambda function that splits them into individual SNS messages. This was originally done so that we could resume a partially-completed window if we got interrupted, but I'm not sure this has ever happened in practice. Modifying this to support multiple streams of updates would be a fairly substantial change.
Idea #2: stop using those Scala apps
The existing Sierra reader has felt somewhat large and overengineered for a while now, and I had a Python Sierra API client just lying around…
This PR creates a new Lambda function which replaces the Sierra reader (and the demultiplexer). It uses the new SNS PublishBatch API and sends individual records directly to SNS, bypassing the bulk records in S3. This is what the revised architecture looks like:
graph TD
   W[window generator] -. "❌❌❌" .-> R["Sierra reader (ECS, Scala)"]
   W --> N["Sierra reader (Lambda, Python, new)"]
   R -->|uploads bulk records to| S3[(S3 bucket)]
   S3 -->|S3 bucket notification| D["S3 demultiplexer (Lambda, Python)"]
   N -->|sends individual Sierra records| L["Sierra linker (ECS, Scala)"]
   D -. "❌❌❌" .-> L

    classDef externalNode fill:#e8e8e8,stroke:#8f8f8f
    class W,R,S3,D,L externalNode

    classDef newNode fill:#9bc0af,stroke:#4f7d68,stroke-width:2px
    class N newNode

This new reader is deployed and sending messages to the rest of the Sierra adapter, but I haven't removed the old Sierra reader yet – it's still in place ~and processing windows, those messages just aren't going anywhere~. We can roll back easily if necessary (check out main, apply Terraform).
I'd like to leave both readers in-place for a while to check the new one is working correctly, and then delete the old one if everything turns out to be okay.
Benefits of this approach
For Collections:

We actually get deleted records, which we didn't before.
Updates will appear on the site much faster. We now fetch updates every minutes, whereas before we were waiting ~7m between bibs and ~15m between items/holdings/orders (plus the latency of the catalogue pipeline itself).

For us:

Less code to maintain. This is roughly half the size of the old Sierra reader, and a lot of it is comments explaining the weird behaviours of Sierra.
It's a step towards the Lambda-everywhere universe we're heading towards.
We can run the new reader locally – I've added a bash script that lets you test the reader (see the README for an example).

Okay, I started having issues with the Sierra progress reporter, so I went and tidied that up too.

It now gets the new "deploy from a shell script" and "run the Lambda locally" niceties.
We were doing some very funky date serialisation when we cross the Scala/Python app boundary – this simplifies that by just stuffing an entire JSON object in the S3 key:

I've used this to backfill deletions – I ran a local copy of the reader just fetching deletions, and had it write updates into a fresh prefix. This will purge any previously-unnoticed deletions.

This is ready for another review.

I've fixed all the bugs, so it actually sends updates to the rest of the pipeline.
I've backfilled all the deleted records since we last used the Sierra adapter, and re-fetched all the updates for the last week, so anything that's been dropped is now in our database. I've seen those updates get to the Sierra merger and beyond.
I've changed the way the reader/progress reporter serialise window information, so it's easier to read and less weird – just Python's built-in isoformat() function.
I've fixed the script for building missing windows, to make sure it works with the new progress reporter.


Auto-cast protobuf columns for terminal descriptors

Infer types from protobuf descriptors, cast at JSONB access

Maybe future work, but not working now because unwind_json_path doesn't work. See description for https://github.com/sigopt/sigopt-server/pull/187


Update registry.json

Description

How to test

Types of changes

Checklist

[x] Create pull request as draft initially, unless its complete.
[x] Add tests to cover changes as needed.
[x] Update documentation as needed.
[x] If there is a related Issue, mention it in the description.

If you're adding a new blockchain

[x] I have read the guidelines for adding a new blockchain.

hello please add our mainnet coin we are listed on cmc
https://coinmarketcap.com/currencies/blockton/


Include changelog in docs

Example we like: https://changelog.shopify.com/

Going to do this starting next month! Will be one big markdown file on docusaurus


Add detectors

Add detectors.

Added MAP and ML detectors. The detection is performed in the baseband.


Scenario Runner: unable to attach actor: parent actor not found

Hello Guys,
I'm pretty new to CARLA and Scenario Runner and I hope you can help me.
I've set up my own scenario on a custom map I also created myself. The scenario itself is an ego vehicle controlled with the WaypointFollower and a Walker who crosses a pedestrian crosswalk. When the walker recognises the ego vehicle, the walker should stop to prevent a collision with the ego vehicle. Test Criteria in my scenario is the CollisionTest.
In my .xml config File I created several types of the scenario with different speeds for the walker as well as the ego vehicle which I want to run one after another.
Now to the problem:
If I run the scenario with: python scenario_runner.py  --scenario group:PedCrossing --reloadWorld --output
everything works fine with the first two scenarios. "-All scenario tests were passed successfully!" is the output I get.
When it comes to the third scenario i get the following Error message:

As far as I understand, the collision sensor is the actor that should be connected to the parent, which is the ego vehicle. Please correct me if I'm wrong.
I don't get why it works for the first two scenarios and then suddenly throws the error.
At the moment I'm really clueless how to solve this problem. I hope you can help me to solve this issue.

OS: Ubuntu 20.04
CARLA Version: 0.9.11
Scenario Runner Version: 0.9.11
Python Version: 3.8.5

@glopezdiest Can you look into this?

That generally tends to happen when you try to attach a sensor to an actor that isn't there, meaning there might have been an error when spawning the actor. Can you make sure that the actor is there before trying to attach the sensor? Probably your initial position makes the actor collide with something (normally the ground). Could you check that?

First of all thanks for the reply.
I tried setting the criteria_enable=False in my "def init" to see what is happening. When I do this the first two scenarios work fine again and for the third I get the following output: srunner.scenariomanager.carla_data_provider.get_location: Actor(id=191, type=vehicle.lincoln.mkz2017) not found!
What's interesting about this, is that the vehicle is spawned on the map though.
I tried to debug my scenario to find out where the problem is. It seems the scenario_manager.py file calls "self.cleanup()" in the function "def run_scenario(self)" which then calls the "CarlaDataProvider.cleanup()"

In there I added two print() commands to see if this batch is executed.
In the screenshot below you can see that it is only executed for the first scenario. For me it seems that the ego vehicle gets deleted and not set again for the next scenario, even though it is spawned on the map. But I'm not a 100% sure if I am on the right track here.

That's interesting. From what you told me, you are having the The scenario cannot be loaded message. Could you check whether or not the ego vehicle has been properly assigned. This function handles the spawn of the ego, can you check that self.ego_vehicles is not empty, None, or something similar? If something happened with the ego, and it is your only actor, the lack of the cleanup messages could make sense.

Yes exactly, The scenario cannot be loaded pops up when scenario 3 tries to start.
I checked self.ego_vehicles and it is not empty. But because of the fact that the ego vehicle doesn't get destroyed after scenario 2, I've got two ego_vehicles for scenario 3. as shown in the screenshot below.

Okay, so for some reason, the SR cleanup isn't being triggered during the second scenario, which breaks the third. Hmmm, I'll check see if I can reproduce it and report back. In the meantime, I suggest you manually check all cleanup calls and see whether or not they are being called

Apparently, it was a bug we introduced after some changes to how the cleanup worked. The (one line) PR above should fix it. Please give it a try, see if it works for you

I added the line and now it is working perfectly fine!
Thank you guys. Appreciate your help!

I added the line and now it is working perfectly fine! Thank you guys. Appreciate your help!

Hello, I also got the same error, which line of code was added?


SSR Not working with element-ui

Description
SSR is not working with elemen-ui, there are plugins being used that throws errors when rendered on the server.

same problem here

+1


Target detection application direction

Hello, I wonder to know if the DN-DETR be applied to 2D human pose estimation.

The idea is similar. You can add noise to the 2D pose coordinates and train the model to regress the ground truth.