Agree on shell code styling

I've been building a loose “style guide” for BlueSkyConnect shell scripts. I've been documenting it in a .editorconfig and you can see the changes in the main branch of my fork.
Some additional changes I want to make right away:

consistent variable name casing ($camelCase vs $SNAKE_CASE)
replacing the SolarWinds reverse DNS with something like net.blueskytools.connect
consistent formatting on the inline MySQL

There should be no functional changes, just formatting, documentation, bug fixes, small optimizations, and very minor restructuring — but with 1200 lines and counting changed, it will definitely require testing.
If these kind of linting changes are of interest and people agree with my style choices, I can submit a PR, but I also know reviewing big PRs is a time suck, so it might be easier to start like a 2.4alpha branch or something. Whatever the community is interested in.

If you create the dev branch I’ll submit a PR against it when I have this at a good point. Maybe dev-2.x? To leave room for a future dev-3.x.

Also definitely want @AllPurposeBen’s input on the styling choices.

I'm good with whatever standardization as long as it's documented for ref and/or editor config'd.
Definitely a testing branch. I'd love to be able to unitary test via docker so if we can document how a dockerfile for getting from a branch to a working testing env, that would help with consistency, for me at least.
I've got stock testing VMs back to 10.11 for client testing, wasn't planning on going older than that. I'd even feel ok bumping the "we tested this X far back, YMMV" floor up to like 10.14.

I think I have my shellFormatting branch at a good point to consider merging into the dev-2.x branch. I didn't change the reverse DNS since that could be a breaking change.
Since there are no functional differences I don't think it's worth a release, but I think it is a better point to move forward with actual modifications.
I still need to test it to make sure I didn't bork anything obvious and then I'll submit a PR.

I have the first few rounds of code cleanup ready, but I think it'd be easier to wait until existing PRs are committed so we don't have merge conflicts.


Change to RootSolvers tolerance

This is an alternative to #140.
Pros: the interface is likely more stable (assuming we'll continue with RootSolvers), since this gives us a lot of flexibility in specifying the tolerance.
Cons: users must depend on RootSolvers if they want to use custom tolerances
Similar to #140, in this PR we don't directly have the temperature_tol, and need some estimate for handling how we break out into freezing edge cases:
freezing_temperature_tol(tol::RS.ResidualTolerance, ::Type{FT}) where {FT} =
    tol.tol
freezing_temperature_tol(tol::RS.AbstractTolerance, ::Type{FT}) where {FT} =
    FT(0.1)

# then, when we need temperature_tol:
temperature_tol = freezing_temperature_tol(tol, FT)

Superseded by #140


Elements with duplicate masks

Bug Description
In stories like https://wp.stories.google/stories/10-web-stories-and-whats-great-about-them-storytime/ there are multiple elements or element masks with the same ID attribute.
Expected Behaviour
That shouldn't happen. IDs should be unique.
Steps to Reproduce
?
Screenshots

Additional Context

Plugin Version: 1.1.0
Operating System: macOS
Browser: Chrome 86

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

I haven't been able to reproduce this so far, tried the cases where this could logically happen:

Using the same text sets multiple times
Using the same page templates multiple times
Duplicating elements
Duplicating pages
Copying and pasting elements

I think I remember one case where the ID was used from the pages templates directly but that got fixed when implementing Custom Page Templates.
I'll try to testing this some more.

Still haven't been able to reproduce this. Took a closer look at the story in the description to see if using similar shapes would somehow be helpful to reproduce this (e.g. background video), however, no luck so far.
Also checked some already existing stories in local / QA (some of them including 37 pages of various media / shapes, etc.) and all seems correct.
@swissspidy Do you know of a more recent occasion of this bug?
Otherwise, I'd recommend moving it to the backlog since perhaps it has been fixed since it was last reported around 6 months ago.

I don't have a recent example, no. Sounds like we can close this for now and re-open if it appears again.


increase InstanceReadyCheckTimeout for OpenStack from 10 seconds to 10 minutes

Signed-off-by: Hubert Ströbitzer<EMAIL_ADDRESS>What this PR does / why we need it:
Customers have the issue that the provided default (10 seconds) is to small for OpenStack to get a VM up and running. They can for sure override this value but having good defaults is a better approach IMO.
Which issue(s) this PR fixes (optional, in fixes #<issue number> format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Optional Release Note:
Increasing the default value for OpenStack instances to get ready from 10 seconds to 10 minutes.

/retest

Is this happening due to some test? If so, can we override the instanceReadyCheckTimeout for this test?

We learned that most of the customers have issues with the timeout of 10 seconds. What are other options @kron4eg ?

@shaase-ctrl other option is to build "retry after" logic, to let events flow without being blocked.

FYI I am on vacations the next two weeks, so I can not take care of this customer request. Please take care of it.

I'll try to do something else here.

@kron4eg  customer asked about status for this fix, could you provide me a followup issue/PR and a timeline for it?

This requires quite a refactoring, so there is no timelines.

WIP PR https://github.com/kubermatic/machine-controller/pull/1019


Typo in definition of cco:has_process_part

The definition of cco:has_process_part is:

For processes P1 and P2, P1 has process part P2 if and only if P2 occurs on a temporal interval that is during the temporal interval of P1 and P2 either provides an input to P1, recieves an output of p1 or both.

The last "p1" should be "P1".

Will fix

Typo fixed.


Empty annotation support

Does mmdetection support empty annotation in coco dataset? The meaning of empty annotation is that the image is just a background and doesn't contain the object. The image is noted in the images portion , but has no data about that image in the annotations portion. For example:
 "images": [
        {
            "id": 0,
            "file_name": "0.png",
            "height": 416,
            "width": 416,
        },
]

Yes, it does.
You may check this https://github.com/open-mmlab/mmdetection/blob/3e2693151add9b5d6db99b944da020cba837266b/mmdet/datasets/coco.py#L121.


TypeError: 'type' object is not subscriptable

TypeError: 'type' object is not subscriptable

Does https://github.com/jackssrt/robloxnotif/commit/fb8c9ab8b4f538ca8ca48e944939727469464cde fix this issue?


Add required fields for 3DSecure

purchaseRequest attribute in the formData is missing for 3DSecure

To be done

[ ] Add tests cases
[ ] Update the documentation
[ ] Add a new function to handle purchases on Sisp class
[ ] Deprecate the old function to handle purchases


Upgrade AutoTensorCore as to a TIR Pass

AutoTensorCore is a pattern detection util that detects the matrix multiplication pattern, and rewrites the compute to make use of the tensorcore intrinsics. https://github.com/apache/incubator-tvm/pull/4234
However, because part of the pattern analysis depends on the tensor expression information and couples with the analysis, it does not qualify as a pass.
Under the unified IR, a transformation pass should to take in information from a PrimFunc in the IRModule, and output another information as a PrimFunc.  A pass should not take additional information from the high level DSL stages. This being said, we could apply transformations in the high level to add decorations(e.g. pragma) to a loop to achieve the same goal.
Due to the current restriction, the AutoTensorCore rewrite has been temporarily moved as a special post processor in
https://github.com/apache/incubator-tvm/blob/master/src/te/schedule/schedule_postproc_rewrite_for_tensor_core.cc
However, this rewriting  should really qualifies as a pass.  As a part of unified IR effort, we want to reduce "non-pass"  transformations to a minimum set(only lowering from te to TIR).
This is an issue to track the issue and discuss potential solutions. There are two potential ways to migrate the pass.

E0: Directly migrate the matmul pattern detector to search over the loop nest, instead of the te stage.
E1: If analysis on the te stage is necessary, run a light weight transformation on te to tag the tensor core related information.

Ideally E0 is preferred. Notably, @Hzfengsy is also working on related changes to TIR to make direct pattern detection in the TIR easier.

cc @minminsun @Hzfengsy @merrymercy @jcf94, @yangjunpro

#5498 Kind of related to this one.
The current TensorCore code generation is tricky --- since we have no fundamental wrap reduction support in TVM, generating TensorCore code inevitably messes up the thread bind. No threadIdxwas bound to a reduce axis before, but we inevitably need a threadIdx for that reduce axis.
Is it possible to somehow represent the warp wise reduce in the schedule, and then the TIR analyzer and rewriter can detect this opportunity of matching TensorCore.

cc @minminsun @Hzfengsy @merrymercy @jcf94, @yangjunpro

Thanks! We've also noticed the problem that current implementation of AutoTensorCore is not pretty enough.
We're working on enabling TVM to auto generate schedule in the project Ansor with @merrymercy now, and we also had some discussions with @Hzfengsy during the development.
Auto TensorCore codegen support is an important feature for us, we'll continue to work on it and try to figure out a better way.

Thanks @jcf94 . I agree that making a better approach for tensorization is important and we should continue to push that direction.
My specific issue is about what to do with the pass as in its current state now. Specifically, there are a few options:

A0: Temporarily remove AutoTensorCore, assuming it has limited usecase and most of the current TensorCore goes through the tensorcore intrinsics, add a better solution back later.
A1: Migrate the AutoTensorCore to TIR by pattern matching the loop nest(instead of the compute expression), so that it can becomes part of the TIR pass, replace the pass later once we have a better solution.
A2: Keep AutoTensorCore in its current location, which introduce a friction pt to the overall design itself, maintaining it as we refactor the code base while tolerating the design friction, remove it once we have a better solution.

We can find that in all of these cases, the AutoTensorCore pass as it is will get removed eventually once we find a better solution. They have different pros and cons, for example, A2 brings a design friction pt to the overall architecture, and could cause problem if we want to release before we find a better solution. A0 is  the easiest for the developers, but also means the feature will be un-available until we find a better solution.  A1 maintains the codebase itself, while continues to migrating it to a better state that fits into the current design, of course it puts more demands on the developers themselves.
This is an interesting case, the code itself becomes a technical debt that we need to pay as maintainers.  It is fun to develop new features. In the meanwhile, maintaining existing code, revisit the design and keep keep migrating them to a better infrastructure is equally important, if not more important for a healthy project. As all new features eventually become technical debts when other new features are added on top. It is important for us to keep infrastructure innovation and  refactoring to reduce the amount of key concepts back to minimum. So that we can more effectively evolve to deliver great new features.
Would love to see thoughts wrt to the three options.

Thanks @tqchen.

It is fun to develop new features. In the meanwhile, maintaining existing code, revisit the design and keep keep migrating them to a better infrastructure is equally important

Can't agree more!
Just as @jcf94 said this pass is required for Ansor to generate code for TensorCore, so we prefer not to remove it for now. We will try to figure out the possiblilty of matmul pattern matching of on TIR instead of TE.

close for now due to inactive status


authentication doc

doc to close https://github.com/djc/couchdb-python/issues/263

Thanks! Sorry for the slow response, but I've now merged your change (and subsequently updated the getting started document a little bit).


Fixed typographical error, changed accross to across in README.

@MicrosoftEdge, I've corrected a typographical error in the documentation of the Demos project. You should be able to merge this pull request automatically. However, if this was intentional or if you enjoy living in linguistic squalor, please let me know and create an issue on my home repository.

Thanks @orthographic-pedant !
That was probably because English is not my first language so thank you for correcting it.
Also, TIL what a squalor is. I think I'm going to use that word a lot :)


Problems with Demo running

❓ Questions and Help
Environment:
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
cuda 9.0
After the installation followed by  the INSTALL.md, when running 'Inference in a few lines' step, I encounter the errors as following . Hoping get the instruction for solving it .
Traceback (most recent call last):
File "../maskrnn/maskrcnn-benchmark-master/MyDemo/Inference.py", line 18, in
predictions = coco_demo.run_on_opencv_image(image)
File "../maskrnn/maskrcnn-benchmark-master/demo/predictor.py", line 169, in run_on_opencv_image
predictions = self.compute_prediction(image)
File "../maskrnn/maskrcnn-benchmark-master/demo/predictor.py", line 193, in compute_prediction
image = self.transforms(original_image)
File "../python3.6/site-packages/torchvision-0.2.1-py3.6.egg/torchvision/transforms/transforms.py", line 58, in call
File "../python3.6/site-packages/torchvision-0.2.1-py3.6.egg/torchvision/transforms/transforms.py", line 119, in call
File "../python3.6/site-packages/torchvision-0.2.1-py3.6.egg/torchvision/transforms/functional.py", line 109, in to_pil_image
TypeError: pic should be Tensor or ndarray. Got <class 'ellipsis'>.

question Questions and Help
Environment: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609 cuda 9.0
After the installation followed by the INSTALL.md, when running 'Inference in a few lines' step, I encounter the errors as following . Hoping get the instruction for solving it .
Traceback (most recent call last):
File "../maskrnn/maskrcnn-benchmark-master/MyDemo/Inference.py", line 18, in
predictions = coco_demo.run_on_opencv_image(image)
File "../maskrnn/maskrcnn-benchmark-master/demo/predictor.py", line 169, in run_on_opencv_image
predictions = self.compute_prediction(image)
File "../maskrnn/maskrcnn-benchmark-master/demo/predictor.py", line 193, in compute_prediction
image = self.transforms(original_image)
File "../python3.6/site-packages/torchvision-0.2.1-py3.6.egg/torchvision/transforms/transforms.py", line 58, in call
File "../python3.6/site-packages/torchvision-0.2.1-py3.6.egg/torchvision/transforms/transforms.py", line 119, in call
File "../python3.6/site-packages/torchvision-0.2.1-py3.6.egg/torchvision/transforms/functional.py", line 109, in to_pil_image
TypeError: pic should be Tensor or ndarray. Got <class 'ellipsis'>.

Hi!  I have the same problem. Can you tell me how you solved this problem. Thank you in advance!

opencv is returning an ellipsis instead of a np.array.
Check that you can read from your webcam, this should help you identify the issue

Traceback (most recent call last):
File "picture.py", line 18, in
predictions = coco_demo.run_on_opencv_image(image)
File "/home/opex/maskrcnn-benchmark/demo/predictor.py", line 172, in run_on_opencv_image
predictions = self.compute_prediction(image)
File "/home/opex/maskrcnn-benchmark/demo/predictor.py", line 198, in compute_prediction
image = self.transforms(original_image)
File "/home/opex/anaconda3/envs/maskrcnn/lib/python3.7/site-packages/torchvision-0.2.1-py3.7.egg/torchvision/transforms/transforms.py", line 60, in call
File "/home/opex/anaconda3/envs/maskrcnn/lib/python3.7/site-packages/torchvision-0.2.1-py3.7.egg/torchvision/transforms/transforms.py", line 126, in call
File "/home/opex/anaconda3/envs/maskrcnn/lib/python3.7/site-packages/torchvision-0.2.1-py3.7.egg/torchvision/transforms/functional.py", line 112, in to_pil_image
TypeError: pic should be Tensor or ndarray. Got <class 'str'>.
I would like to run  'inference in a few lines' on my own picture. I just changed image = ("30.jpg"). Then I got this error. I can run webcam exactly. Could you help me, I am a new of this. Thank you very much!

You should pass a numpy array, not a string. Check https://github.com/facebookresearch/maskrcnn-benchmark/blob/master/demo/Mask_R-CNN_demo.ipynb for more details


Register proxy broker URLs to point to SM instead of Proxy

Register proxy broker URLs to point to SM instead of Proxy
Motivation
The Service Broker Proxy component will no longer act as a proxy component for the respective platforms. It will still be responsible for reconciling and updating the state of the platforms, but OSB calls will now be directly go through the Service Manager.
Approach
The Service Broker Proxy will register brokers in the platforms and will set as URL the SM URL instead of its own URL. Also the broker should be registered with the platform credentials retrieved when registering the respective platform. This is because now the platforms will directly call SM OSB APIs which are protected with basic authentication (platform credentials).
Note
This change should take into account previously registered brokers with the proxy URL and update them accordingly.

Coverage remained the same at 90.102% when pulling 53deeb7c4318a2849dfff52eae72c3f8bc64a088 on migrate-url into 6c4c24e19c9c3feefd2a4f82a3ee73a4017d3030 on master.


Added an ifdef for USE_POWER_PINS around the power pins of the SRAM in RTL verilog

Added an ifdef for USE_POWER_PINS around the power pins of the SRAM module in the RTL verilog file mgmt_core.v to match the verilog of the SRAM module itself.  As far as I am aware, the VexRISC core does not need the same treatment because the VexRISC core does not define power supply pins at all. Note that this is a change to an automatically-generated file, and the change needs to be made elsewhere in the LiteX code to become permanent.

This PR should have been marked with the branch caravel_stanford as target.  It has already been merged into that branch, so this pull request can be closed (the permanent fix is in the LiteX code, not a quick fix to the RTL verilog, so this will not be merged into branch main).


Update Saxon-HE to 10.3

Updates net.sf.saxon:Saxon-HE from 9.9.1-8 to 10.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "net.sf.saxon", artifactId = "Saxon-HE" } ]

labels: library-update

+1
The schematron stuff hasn't been in an official release yet, so I doubt many people are using it/relying on performance. I'd prefer to have the latest and greatest, and if people start using it and do run into performance issues we can figure out the best way to address it.


Gradient doesn't cover whole text

The entire heading is not covered by the linear gradient (bg image) in some resolutions.

Fixed in #15


SecurityException: Unable to retrieve security descriptor for this frame.

Getting this  below error in my ASP.Net Core 1.1 app/IIS 8.
Tried to impersonate @ middleware level but ran into various issues, so trying to impersonate as a actual windows user instead of IIS app pool user @ the controller level.
Have this below code in my controller
 public class SearchController : Controller
    {
.......
            var winIdent = HttpContext.User.Identity as WindowsIdentity;
            if (winIdent != null)
            {
                 WindowsIdentity.RunImpersonated(winIdent.AccessToken, () =>
                {
                    numMatches = shim.GetNumMatches(scm);
                });
            }
.................
}

Error:
SecurityException: Unable to retrieve security descriptor for this frame.
Any help will be appreciated.;

This issue was moved to dotnet/cli#7502


Upgrade Next to 14.0.4, update Mina package configuration & proper dynamic-rendering

This PR should fix the errors regarding the dynamic-rendering, as well as our mina package not properly building.
Build on Vercel is now completing

force merging


feat: AU-1949: E2E, Implemented hidden field validation

AU-1949
What was done
This pull request implements the possibility to test for hidden fields. These tests are useful in the scenario where the value of field X alters the visibility of field Y.
What has been implemented

Implemented the new property itemsToBeHidden. This property accepts an array of items that are expected to be hidden on a given page. The property works similarly to itemsToRemove, as it also removes the items from the test itself (so no need to enter both itemsToRemove AND itemsToBeHidden if you want to test for hidden fields).

Implemented validateHiddenFields(). This function is called when filling in a form page if said page has defined anything the the itemsToBeHidden array. The function makes sure that the items in the array are indeed hidden and not visible.

Modified createFormData() so that items in itemsToBeHidden are also removed from the test.

How to install
Make sure your instance is up and running on correct branch.

git checkout feature/AU-1949-missing-field-tests
make fresh
make drush-cr

How to test

Add this to the .test_env file:

DISABLED_FORM_VARIANTS="success"

Run make test-pw-p PROJECT=forms-48. Make sure that all the tests pass, and that the output for the under5000 test is similar to this:

Add the field edit-toiminta-yhteistyokumppanit to the itemsToBeHidden array in the under5000 test.
Run make test-pw-p PROJECT=forms-48 again and see that the test fails, since the field isn't hidden.

Mä testaan tän ku saadaan toi Paavon pullari mergettyä ku siinä niitä ympäristöasioita. joo joo, ei pitäs fiksailla lennosta toisiin pullareihin. mut niin tein.


[BUG]:

What is the bug related to?
Registry CLI
What went wrong?
When I ran 'registry help', I get the following error:
/home/shuller/.nvm/versions/node/v6.17.1/lib/node_modules/registry-cli/out/src/cli.js:14
async function run(argv) {
^^^^^^^^
SyntaxError: Unexpected token function
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:549:28)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
at Module.require (module.js:504:17)
at require (internal/module.js:20:19)
at Object. (/home/shuller/.nvm/versions/node/v6.17.1/lib/node_modules/registry-cli/bin/registry:13:2)
What did you expect to see?
I should have seen commands to use with the registry
Additional Context
No response
Relevant logs/output
No response

Hi @spiliti,
It looks like you are using Node v6.17.1. The Registry CLI needs a minimum of Node 8 because it uses async-await. However, using the latest version of Node (v16.13.0) is recommended.
From the logs, I understand you are using NVM to manage NodeJS versions. Here is the command you can run to switch to the latest version:
nvm use lts

Let me know if you need any help.

Registry Setup
Thanks. Now when I try to initialize a registry (/example$ registry init) I get the following feedback:
✔ All necessary tools installed!
✔ Enter the name of the registry · Example
✔ Enter the name of the Keycloak realm to create · sunbird-rc
✔ Enter the ID to assign to the admin client in Keycloak · admin-api
✔ Enter the ID to assign to the frontend client in Keycloak · registry-frontend
✔ Enter a username for the admin account in Keycloak · admin
✔ Enter a password for the admin account in Keycloak · admin
✔ Enter the path to a directory containing entity schemas · use-example-config
✔ Enter the path to a file containing consent configuration · use-example-config
✔ Successfully copied over necessary files
✖ An unexpected error occurred while starting the registry: Command failed with exit code 125: docker compose up -d

Below is my docker-compose.yaml. I quess I have to upgrade docker-compose .
version: '2.4'
services:
es:
image: docker.elastic.co/elasticsearch/elasticsearch:7.10.1
environment:
- discovery.type=single-node
- 'ES_JAVA_OPTS=-Xms512m -Xmx512m'
healthcheck:
test: ['CMD', 'curl', '-f', 'localhost:9200/_cluster/health']
interval: 30s
timeout: 10s
retries: 4
ports:
- '9200:9200'
- '9300:9300'
db:
image: postgres
ports:
- '5432:5432'
environment:
- POSTGRES_DB=registry
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=postgres
rg:
image: dockerhub/sunbird-rc-core
volumes:
- ./config/schemas:/home/opensaber/config/public/_schemas
environment:
- connectionInfo_uri=jdbc:postgresql://db:5432/registry
- connectionInfo_username=postgres
- connectionInfo_password=postgres
- elastic_search_connection_url=es:9200
- search_provider=io.opensaber.registry.service.ElasticSearchService
- sunbird_sso_realm=sunbird-rc
- sunbird_sso_url=http://kc:8080/auth
- sunbird_sso_admin_client_id=admin-api
- sunbird_sso_client_id=registry-frontend
- sunbird_sso_admin_client_secret=INSERT_SECRET_HERE
- claims_url=http://cs:8082
ports:
- '8081:8081'
depends_on:
es:
condition: service_healthy
db:
condition: service_started
kc:
condition: service_healthy
kc:
image: dockerhub/ndear-keycloak
volumes:
- ./config/keycloak:/opt/jboss/keycloak/imports
environment:
- DB_VENDOR=postgres
- DB_ADDR=db
- DB_PORT=5432
- DB_DATABASE=registry
- DB_USER=postgres
- DB_PASSWORD=postgres
- KEYCLOAK_USER=admin
- KEYCLOAK_PASSWORD=admin
- KEYCLOAK_IMPORT=/opt/jboss/keycloak/imports/realm-export.json
- KEYCLOAK_FRONTEND_URL=http://localhost:8080/auth
healthcheck:
test: ['CMD-SHELL', 'curl -f http://localhost:9990/ || exit 1']
interval: 30s
timeout: 10s
retries: 5
ports:
- '8080:8080'
- '9990:9990'
depends_on:
db:
condition: service_started
cs:
image: dockerhub/open-saber-claim-ms
environment:
- connectionInfo_uri=jdbc:postgresql://db:5432/registry
- connectionInfo_username=postgres
- connectionInfo_password=postgres
- opensaber_url=http://rg:8081
ports:
- '8082:8082'
depends_on:
db:
condition: service_started
rg:
condition: service_started

// Answering in #164


Moving move files to naming and naming_base

Relies on #5024

@msimberg this is good to go, I think. Please review.


Spacebar triggering sweetalert submit (latest CDN build)

When I press the spacebar on an input field in the sweetalert modal, the form seems to submit. You can see a barebones demo here. This makes typing strings with spaces impossible.
(Updated title because a bug on my end led me down the wrong train of thought for a possible cause).

Any updates for this issue, seems critical

Good news everyone!
Swal2 now supports input and select types, you example: https://jsfiddle.net/47L0mf97/2/
Input example: http://limonte.github.io/sweetalert2/#input-field
Select box example: http://limonte.github.io/sweetalert2/#select-box

unfortunately if you use custom html there's no way to disable afaik to disable the spacebar triggering

@rubencodes I just opened #178 to address this behavior as a configurable option

@esetnik this issue is related to the modal with input (JS prompt() alternative). You are trying to disable submitting of JS alert() alternative which is different from native alert() behaviour.


Add support for azurerm_sql_database

Terraform resource: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/sql_database
Terraform says azurerm_sql_database is deprecated and azurerm_mssql_database should be used instead. We can add support for azurerm_sql_database by re-factoring/using the same logic as a few users have requested this.
We can also add azurerm_sql_active_directory_administrator as a free resource.
We should check if azurerm_mssql_server is free too.

@alikhajeh1 as part of this I'm going to migrate mssql_database to the new resource structure.

@dsfrederic just FYI that this'll get released in v0.9.16 next week.

@dsfrederic this is live in v0.9.16.


remove validate_json_schema

Way too soon, this hasn't even been deprecated yet. The deprecation is starting in 0.17.0 (see: #5262)

Way too soon, this hasn't even been deprecated yet. The deprecation is starting in 0.17.0 (see: #5262)

Indeed. The 2020 date  in blame  played me.


non default db connection bug patch

Released in 3.12.2 🎉

Your welcome :+1:
thank you for fast response.


CI needs to support Python 3.6

The standard Python on RHEL8 remains at version 3.6, so really this needs to be supported in CI!

I don't believe we can do this - the python3-pip-skeleton uses pyproject.toml for configuration, the current standard for recent versions of Python, and the support for that only arrives in setuptools versions from ~61. Unfortunately those versions of setuptools do not support Python 3.6 at all.
While it doesn't really help us, Python 3.6 is two years past EOL, and so I don't see much gain in trying to retrofit the builds to work with Python 3.6.

Well, at least we do have (slight half baked) support for newer versions of Python on RHEL8.


Fix wrong error var being printed

Thanks for reporting! Will be reviewed shortly.

Looks good, thanks.


Feature Request Website: Hover on Tag-Component

Is your feature request related to a problem? Please describe.
In Kabenas, weeks ago we hab a Tag-component of Bootstrap in use, which had a hover effect. Since we replaced the component with the Tag-Component of SBB's public design system, we don't have the hover anymore. The hover was similar or the same as the pills of the SBB Intranet.
Describe the solution you'd like
A hover on Tag-Component, comparing to the pills of the SBB Intranet.
Describe alternatives you've considered
We can keep it like this or we can try to make the change just for Kabenas.
Additional context

Thank's for your feature request.
We'll check that and keep you informed about the next steps.


Use system theme

next-theme 's useTheme hook returns both theme and resolveTheme Docs.
theme, by default returns 'system', but we need to use either "light" or "dark".
resolveTheme does just that.
Reproduction steps
Previously, when opening Drift in an incognito window (no theme setup, so it defaults to "system"), the first click on the header theme will do nothing (it will set theme to something other than "system").
The background is white, and the icon is a 🌞

Works great, thanks!


Rename noosphere crate to noosphere-core

The name of the noosphere crate is a bit misleading: it sounds like it is the entrypoint for someone who is interested in the collective body of code, but in fact it is just the kernel of our code base (mostly just the raw IPLD type definitions as associated implementation). We should rename the crate to noosphere-core to more appropriately reflect its purpose.

This issue is done, right? https://crates.io/crates/noosphere-core

This issue is done, right? https://crates.io/crates/noosphere-core

yes! thanks for catching this, fixed via #112


JsonSchema.Net v2.0.0

Depends on #201
Resolves #197

Test failures are in JSON Logic.  I'll address that separately.


Spike: Investigate WalletConnect

Background:
WalletConnect is a popular multi-chain wallet aggregator, including wallet connect alongside other stellar wallets increases the user base.
Acceptance criteria:
Review https://docs.walletconnect.com/2.0/json-rpc/stellar and provide a PoC implementation.

After reviewing WalletConnect and it's adoption in the Stellar ecosystem we decided that it's not the right moment to include it, due to low adoption (only LOBSTER supports WalletConnect at the time) and the fact that it's still in beta with an incomplete documentation.
We should review it again in 3-6 months.


3 implement rl approach

Investigate memory explosion:
Try tf.stop_gradients() on live generated training data (train_deepq.py, line 53)


settings: Don't try to disable flake8, document relevant limitation

flake8 plugin is disabled by default. If it's been enabled in the pylsp configuration then it's not possible for another plugin to disable it.
The other four plugins (pycodestyle, pyflakes, mccabe, pyls_isort) are all enabled by default so the ruff plugin can disable them, provided they're not explicitly enabled in the configuration.
Closes #46
Thanks for maintaining python-lsp-ruff, it's a very handy plugin! :grin:

i am a little confused the title, i remember this 'ruff' plugin was (aim to) going to be the only linter for pylsp,
but now kept the flake8 default be enabled there? if yes, was there some additional configure to disable it?
or some con/pro if leave the 'enable' there? and this seems a bit un-imcompatible (and break game?) if yes.

@Shane-XB-Qian Linting with flake8 is disabled by default. The idea behind removing it from the list of disabled plugins was that it would otherwise awake the idea of it always being disabled, regardless of the user configuration.
Effectively this changes nothing since flake8 is disabled by default unless explicitly enabled by the user.
See #46 for more details

I've edited the description of the PR, as it was a bit terse. Hope that's clearer, @Shane-XB-Qian.

ok, just wish keep this/its 'aim', make the result be stable and simple/clear.

only left things (to be refined) of pylsp as i knew maybe were: hover-doc and auto-import, and seems they are doing the refine now.
// but just the latter one was on 'rope' still, wish someday 'ruff' can offer that....... :smile:


Idea to get Optional values (Level 1)

Summary
Since .get() and its associated .orElse()... are out of bounds for us for this lab, how are we meant to implement the succ() method?
Description:
I've heard a common method is to use .map(), but what exactly can I map, without specifying .get() inside the map method?
Code Snippets
Here's an idea that would break the getter requirement:
return Num.<Integer>of(AbstractNum.s.apply(this.opt.get()));

.map() should be used to expose the variable in Optional().
this.opt.map(x -> AbstractNum.s.apply(x))

You have access to the AbstractNum(Optional<T> opt) constructor. Also note that Num, like Optional<Integer> is a high level wrapper around Integer, so it would simplify a lot of code you have to write later down the line by defining custom map, filter, flatMap etc for Num

To add on, the idea is to change the value within the optional since you would have already made a constructor to handle an optional input. So you shouldn't really be trying to "get" the integer value out but rather just make the changes necessary within the optional.

you could also try flatMap with appropriate constructors

As everyone above has mentioned, you require a constructor that can take in an Optional<Integer>.
Referring to JDK17: https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/Optional.html
map(Function<? super T,? extends U> mapper) here transforms an Optional<T> into an Optional<R> using the Function mapper, which allows you to change the contents of the Optional without extracting the value. Hence, there is no need to extract the value out of the Optional with get() and orElse().
Hence, succ() can be implemented with the Optional::map method using the Function s given in the base code for AbstractNum which in inherited to its subclass due to the protected property.

just like the above comments, you don't need to get value. you can just ask optional to change it for you

As mentioned above, there is no need to explicitly retrieve the value from optional, which I heard is also banned in codecrunch. Rather, let the optional do your work for you by changing/mapping the values.

The posts above have summarize my thoughts exactly on this matter.
Probably to complete @Ryan-loves-movies's post, after you finally manage to get the Num's Optional (not get the Num's Optional's value), you map it to it's succ by applying s;
then you would need to pass that succ-ed Optional to create a new Num. How would you do that?
My way is to create a Num constructor that call super to ... [fill in the blanks here]

You can use map or flatMap and let them use a function to modify the value for you


🐛 Bug Report — Difference deploy behavior from wrangler CLI and Cloudflare website.

When I deploy a project across git CLI and already connect Cloudflare Works, and it builds successfully, you can view it at https://be758b82.balanced-chef.pages.dev/, it can open, but the /blog/* page doesn't work, I check everything is OK.
After, I tried to deploy the project through npx wrangler pages deploy dist, and it worked well on every page, you can see it at https://fe5e61f6.balanced-chef.pages.dev/
What's wrong?
I'm not sure is suitable to report this issue here.

I removed this issue to Cloudflare Community, so I'll close this issue.


Setting the cookie domain and path

I'm using the example code to create the remember me cookie in my login route (/public/account/login):
// If the user wants to be remembered, create Rememberme cookie
if(!empty($data['rememberme'])) {
    $app->remember_me->createCookie($user->id);
} else {
    $app->remember_me->clearCookie();
}

However, the cookie is now limited in visibility to requests to /public/account/login.  How can I set the cookie path here via your API?

Just put the following line before your code (or on the line after creating the RememberMe object):
$app->remember_me->getCookie()->setPath("/");

Thanks for the question, I'll make it easier to set your own Cookie instance in version 2.

Yup, that's what I ended up doing.  It would also be good if we could set the cookie name and other parameters in the createCookie method as well.

Also if you change the path and get "saved" by the cookie it will discard previously defined paths. Or as far as I can understand.
What I've done is prior to checking the cookie with (in this example)
$app->remember_me->login()
I do this to ensure that the path is still '/' after cookie is renewed.
$cookie = $app->remember_me->getCookie(); $cookie->setPath('/'); $app->remember_me->login()

In Version 2.0 the default path for the cookie is now '/'


iOS 8 compatibility

It seems that the lib is using CASpringAnimation which is only available on iOS9+. But the readme says it is iOS8 compatible.

You're correct. I've removed statement of support for iOS8 from the readme 69b65edc0648265f909c26b37f90b22f0aa96065


How many dataloaders do we need ?

Hey, do you create 1 loader for each type of entity and that's enough? no need for separate loaders for subqueries? So if you query
{Article (where: {id: 1})
    {
        Comments  { id }
    }
}

, if you have a CommentLoader that will load as only 2 SQL calls?
Or do we need a CommentByArticleLoader to only be used with this query?

You'll sometimes need to create separate loaders for subqueries
in this case I would do CommentByArticleLoader


chore: update expo config and android cli package

#156

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.36%. Comparing base (4a1a4f7) to head (d155e00).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #157   +/-   ##
========================================
  Coverage    91.36%   91.36%
========================================
  Files           11       11
  Lines          417      417
  Branches        79       79
========================================
  Hits           381      381
  Misses          31       31
  Partials         5        5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


CBAPI-2079: Remove All Flake8 Errors in Source

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Tests have been added that prove the fix is effective or that the feature works.
[x] New and existing tests pass locally with the changes.
[x] Code follows the style guidelines of this project (PEP8, clean code, linter).
[x] A self-review of the code has been done.

What is the ticket or issue number?

https://jira.carbonblack.local/browse/CBAPI-2171 (https://jira.carbonblack.local/browse/CBAPI-2079)
Pull Request Description

Ensure that the code has all errors removed and Flake8 outputs no errors.
Does this introduce a breaking change?

[ ] Yes
[x] No

How Has This Been Tested?

All existing unit tests run on the de-flake8'd code.

The TBD comments need completed

If it says "TBD" that means I couldn't figure it out and I need help. Luke actually has helped figure out a couple of them, and that will be reflected when I check in this next batch of changes.

The TBD comments need completed

If it says "TBD" that means I couldn't figure it out and I need help. Luke actually has helped figure out a couple of them, and that will be reflected when I check in this next batch of changes.

Ok. Give a link to any that remain after that and I'll take a look

Ok. Give a link to any that remain after that and I'll take a look

./src/cbc_sdk/base.py:132:            instance_type: TBD
./src/cbc_sdk/base.py:168:            instance_type: TBD
./src/cbc_sdk/base.py:186:            instance_type: TBD
./src/cbc_sdk/base.py:212:            instance_type: TBD
./src/cbc_sdk/base.py:251:            instance_type: TBD
./src/cbc_sdk/base.py:302:            instance_type: TBD
./src/cbc_sdk/base.py:332:            instance_type: TBD
./src/cbc_sdk/connection.py:134:            object: TBD
./src/cbc_sdk/connection.py:359:            *args: TBD
./src/cbc_sdk/connection.py:611:        api: TBD
./src/cbc_sdk/connection.py:612:        cls: TBD
./src/cbc_sdk/connection.py:613:        unique_id: TBD
./src/cbc_sdk/connection.py:618:        TBD
./src/cbc_sdk/live_response_api.py:159:            delay (float): TBD
./src/cbc_sdk/live_response_api.py:185:            delay (float): TBD
./src/cbc_sdk/live_response_api.py:1265:            TBD


Not work of "source.fixAll.eslint": "explicit"  on v3.0.10

.vscode/settings.json
"editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit"
},

vscode version 1.84.0

@seepine I tried to reproduce this but it works for me. See screen cast. Could you share a GitHub repository I can clone with a minimal setup that reproduces what you are seeing.
https://github.com/user-attachments/assets/5d0874ed-e2e1-4f09-aed8-344691bbdc36

If you use prettier and yarn pnp you might be affected by: https://github.com/yarnpkg/berry/issues/6335


Add --no-version-check flag

Currently whenever a local tool version doesn't match the version in a baseline file the developers are forced to update it even when there are no secrets change. Together with an updated timestamp this creates a constant merge conflict problems when multiple developers are working in parallel.
This change adds a new flag --no-version-check that allows to skip the version update in the baseline file when there are no other changes.
The new flag is false by default, allowing to keep back compatibility with the previous behaviour.
An additional small update in util_test.py addresses the fact that packaging dropped support for LegacyVersion in version 0.22, so test_version_compare tests are now failing on the old version parameter with an invalid format exception.

Hi @eiri, I apologize for the delay in my review, I was on break until recently.
Regarding your PR, the skip version check feature works counter to Detect Secrets' design. When Detect Secrets is run and its version is not up-to-date, it will output a message letting the user know that the version is outdated and will provide a link which includes instructions on how to update Detect Secrets (upgrade guide). The latest version of Detect Secrets should always be used because it could contain enhancements to secret detection and bug fixes.
If everyone is on same (latest) version of Detect Secrets, this should fix the merge conflict issues. I would recommend using the pre-commit hook for your team's repositories if it's not already being used. Before a commit is made, the pre-commit hook will check that the detect secrets version specified in .pre-commit-config.yaml  is being used to prevent mismatched Detect Secrets versions. If the version does not match, it will block the commit from being made until this is corrected. Note that running pre-commit autoupdate updates the pre-commit hook to use the latest version of detect secrets (it will update the Detect Secrets version in .pre-commit-config.yaml).
Here is a guide on how to set up the pre-commit hook.
I'd recommend adding this to your project READMEs to ensure that developers set up Detect Secrets correctly locally:
## Detect Secrets

This project uses the [Detect Secrets CLI tool](link to w3 Detect Secrets home page) to scan for potential leaked secrets at commit time. In order for this to function as intended, each developer must initialize the pre-commit tool as a one-time step after cloning the repo. Requires Python 3 and pip.

Steps can be found [here](https://github.com/IBM/detect-secrets/blob/master/docs/developer-tool-faq.md#how-do-i-set-up-the-pre-commit-hook).

I do appreciate you having submitted a PR, but I would recommend this workflow in the future for bringing up issues:

Submit an issue describing your feature request
Wait for a maintainer to respond
If the enhancement is accepted in the issue and solutioned out w/ a contributor, then proceed to work on and submit a PR

Another thing, the pre-commit hook should be set up for each repo.
Your version: 0.13.1+ibm.55.dss
Latest version: 0.13.1+ibm.56.dss
See upgrade guide at https://ibm.biz/detect-secrets-how-to-upgrade
Your baseline file (.secrets.baseline) is unstaged.
git add .secrets.baseline to fix this.
You can run “pre-commit autoupdate” to update the DS version used in your pre-commit config file, or point to master (?)


chore: syncing optimizations

Refactored pbft syncing. Pbft syncing had these problems:

Restartsyncing pbft was triggered on too many places (a lot of which are redundant and not needed) and often with the force flag which could cause recursive sending of too many pbft sync requests leading to errors
Restartsyncing method was not protected so it was possible for two threads to restart syncing at the same time

RestartSycning method is now renamed in startSyncing since it does not have a force flag and only starts syncing if syncing is not already running.
Pbft syncing in now only triggered:

In status packet handler if other nodes are ahead
If node we are currently syncing to has disconnected
If pbft syncing to a node has finished to verify that there is no other node ahead
In dag syncing if requested dag syncing period shows other node is ahead
In pbft manager if 2t+1 voted block is missing the proposed block

There is no longer force flag in restartSyncing to avoid use cases where it was possible to send multiple sync requests at the same time.
startsyncing is now protected with a mutex to avoid multiple threads executing at the same time.
If syncing state is already true, invoking it will not make any effect.
Syncing state will be set to false only in these cases:

Syncing to a node is successfully completed
Response to sync request times out
Sending sync request failed
Node we are syncing to got disconnected
Sync packet we received is below our pbft block chain height which means we are already synced
Error state where PBFT blocks get stuck in queue and are not being processed for a long time

prnet cleaned-up successfully


"The operation timed out" Issue

I'm brand new to programming, and just came across a problem in which NadekoBot.exe had stopped working. The issue, from the log, had told me that the "operation timed out".
Here is the credentials.json file, (where I put "MY-___-HERE" is where I already put my actual info):
{
"ClientId": MY-CLIENT-ID-HERE,
"Token": "MY-TOKEN-HERE",
"OwnerIds": [
MY-OWNER-ID-HERE
],
"LoLApiKey": "",
"GoogleApiKey": "",
"MashapeKey": "",
"OsuApiKey": "",
"SoundCloudClientId": "",
"CleverbotApiKey": "",
"CarbonKey": "",
"Db": {
"Type": "sqlite",
"ConnectionString": "Data Source=data/NadekoBot.db"
},
"TotalShards": 1,
"PatreonAccessToken": "",
"PatreonCampaignId": "334038",
"RestartCommand": null,
"ShardRunCommand": "",
"ShardRunArguments": "",
"ShardRunPort": null,
"MiningProxyUrl": null,
"MiningProxyCreds": null,
"BotListToken": null,
"TwitchClientId": null,
"VotesToken": null,
"VotesUrl": null
}
And here is the log:
-1 03:34:42 ShardsCoordinator | Starting NadekoBot v2.17.4
-1 03:35:03 ShardsCoordinator | System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.Http.WinHttpException: The operation timed out
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Threading.Tasks.RendezvousAwaitable1.GetResult()    at System.Net.Http.WinHttpHandler.<StartRequest>d__105.MoveNext()    --- End of inner exception stack trace ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()
at System.Net.Http.HttpClient.d__59.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at System.Net.Http.HttpClient.d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NadekoBot.Core.Services.Impl.RedisImagesCache.<>c__DisplayClass50_0.<b__6>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NadekoBot.Core.Services.Impl.RedisImagesCache.d__50.MoveNext()
Unhandled Exception: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.Http.WinHttpException: The operation timed out
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Threading.Tasks.RendezvousAwaitable1.GetResult()    at System.Net.Http.WinHttpHandler.<StartRequest>d__105.MoveNext()    --- End of inner exception stack trace ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()
at System.Net.Http.HttpClient.d__59.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at System.Net.Http.HttpClient.d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NadekoBot.Core.Services.Impl.RedisImagesCache.<>c__DisplayClass50_0.<b__6>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NadekoBot.Core.Services.Impl.RedisImagesCache.d__50.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NadekoBot.Core.Services.ShardsCoordinator..ctor()
at NadekoBot.Program.Main(String[] args)
at NadekoBot.Program.(String[] args)
I would like assistance on fixing this problem, thanks!

Your DNS is screwed. Try restarting your Internet. If that doesn't work, just wait.

Your DNS is screwed. Try restarting your Internet. If that doesn't work, just wait.

I did that and it worked. Thanks for your quick reply!


Switch to new rocksdb with some hacks to resolve linking errors

Rocksdb and wasmtime-environ both link zstd. In the final link step,
this leads to linking errors because of duplicate symbols. The linked
Rocksdb fixes this by using zstd-sys as well. However, this currently
also requires modifications in zstd-sys. Someone will need to come up
with a better implementation.

@bkchr a few failing tests here it seems...


model error

I am suddenly getting this error:

and since I tried relading it:

Any idea what could cause this?  It worked fine until about 1-2 days ago.  I noticed the error but ignored it because I was busy, now I see reloading doesn't fix it, the URL is correct.  So.... what upset him suddenly?  :(

That is really weird, never happened to me before.

If you reboot node-red it still happens?
If you recreate the node it still happens?
If you use a new trained model it still happens?

The part from model is not ready, is expected if the model is not loaded and you are already sending an image.
What is you image sending rate? I recommend putting a delay node in front of the teachable machine node to limit the speed of images that will be really processed, if you are sending them really fast, you could end up with queued images to be processed and there is no limit, so you could theoretically filling your entire RAM.
I'll need more information regarding this problem to be able to reproduce it and fix it in case it is really a bug from the node. Thanks!

❌ rebooting Node-RED
❌ recreating the node
❌ using a new trained model
Actually I am quite happy that it still doesn't work with a different project, because I did work on the first one and I wouldn't have wanted it to be "too big" or something.
Do you know of any way in which we could debug what is happening?
I can also say, I did not install anything new in Node-RED, only changes to node arrangements.
Maybe a... system update, broke something?  Is that possible?  I mean a simple sudo apt upgrade.

I tried uninstalling and reinstalling node-red-contrib-teachable-machine, still the same error.  Hmm....

Did you try in a Docker? I have no problems with a clean installation.
It feels like some dependency from Node-RED has totally broken.

I just run it installed through npm, I actually don't know what docker is, didn't have to know yet.
I tried it in a Virtual Machine with a fresh install and it's working perfectly so yes...

some dependency from Node-RED has totally broken.

Now, how do I find out how to fix this because I am quite afraid of problems when porting everything I've done to a fresh install.
Maybe I should backup everything and do a npm audit fix --force. This will take a day or two to recover from, let's see.  Without --force, doesn't solve it.
EDIT:  Actually... this might give a hint:
node-fetch  <2.6.1
The `size` option isn't honored after following a redirect in node-fetch - https://github.com/advisories/GHSA-w7rc-rwvf-8q5r
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change

I got an idea to travel here, and found this:

Then I went to ~/node-red/node_modules/node-red-contrib-teachable-machine/ and fixed everything in there, everything is fixed, then I completely sudo uninstalled node-red-contrib-teachable-machine, deleted the folder, reinstalled through Node-RED Palettes, uninstalled through there, reinstalled through there, npm audit shows zero vulnerabilities.
Still, same error.
I'll keep trying a bit more, to maybe help future users.

I recommend to reinstall Node-RED or use a Docker with Node-RED.
I'll close this issue since tested using a clean install there are no errors. Thanks for the information it might help future newcomers.

I found the problem and solved it!
npm-audit fix --force, reinstalling Node-RED fresh or anything like that has nothing to do with it, I just broke everything with those type of things, and had to revert to a backup.
The problem was:  node-red-contrib-tesseract.  That's all, removed that from Palettes and the model loads without problem.

Problem node:


[keychain] New port

Describe the pull request
This pr adds the keychain library portfile.

What does your PR fix? Fixes #
/

Which triplets are supported/not supported?
/

Have you updated the CI baseline?
No

Does your PR follow the maintainer guide?
Yes

@robertobernabe ,Sorry to reply you so late.
Can you please resolve the conflicts against master?

@JonLiu1993 So i've tried my very best to resolve all the issues in the portfile. Please have a look! I only struggling with the linux installation. It works if you install libsecret-1-dev via apt. But how is the best way to deal with that in vcpkg world right now?
For now i just throw an error if libsecret isn`t on the system.

I can't see CI test log at present, I have rerun the CI test, after CI test I will check the log

Hi there - no problem. Better late than never :) I've resolved the merge conflict and the tests should now run.

Hi there - no problem. Better late than never :) I've resolved the merge conflict and the tests should now run.

Great, let's wait for the CI test result

Hi there - no problem. Better late than never :) I've resolved the merge conflict and the tests should now run.

Great, let's wait for the CI test result
CI Tests run trough 👌🏻

@robertobernabe, could you address the review suggestions? Thanks!

@robertobernabe ,Are you still working on this pr?

Closing this PR since it seems that no progress is being made. Please reopen if work is still being done.


Question: adding a new application to an existing system

Is it possible with this library to add a new application to an existing system and have it process existing domain events of its upstream applications?

yes you can pull_and_process(leader_name=UpstreamApplication.__name__, start=1) to process events from the start.

Alternatively @d-m, you can add a new application to a system definition and restart your system runner. Which does what @peterDijk said.


Use "order by id" to create a time window, and query by id returns wrong results.

I created a materialized view and created an index ad_id. There are about 2.5 million records in the materialized view. When I execute select * from ad_ctr_5min where ad_id=9; or any existing ad_id, I cannot find any matching records. When When I query select * from ad_ctr_5min where ad_id=0, all the records are queried, I think this is a very strange thing, do you have a similar experience? The following is my code to create the materialized view and related query statements:
1.
CREATE MATERIALIZED VIEW ad_ctr_5min AS
SELECT
ac.ad_id AS ad_id,
ac.clicks_count :: NUMERIC / ai.impressions_count AS ctr,
ai.window_end AS window_end
FROM
(
SELECT
ad_id,
COUNT() AS impressions_count,
window_end
FROM
TUMBLE(
ad_impression,
impression_timestamp,
INTERVAL '1' MINUTE
)
GROUP BY
ad_id,
window_end
) AS ai
JOIN (
SELECT
ai.ad_id,
COUNT() AS clicks_count,
ai.window_end AS window_end
FROM
TUMBLE(ad_click, click_timestamp, INTERVAL '1' MINUTE) AS ac
INNER JOIN TUMBLE(
ad_impression,
impression_timestamp,
INTERVAL '1' MINUTE
) AS ai ON ai.bid_id = ac.bid_id
AND ai.window_end = ac.window_end
GROUP BY
ai.ad_id,
ai.window_end
) AS ac ON ai.ad_id = ac.ad_id
AND ai.window_end = ac.window_end order by ad_id;
2.
dev=> select * from ad_ctr_5min where ad_id=9;
ad_id | ctr | window_end
-------+-----+------------
(0 rows)
3.
dev=> select * from ad_ctr_5min where ad_id=0;
ad_id  |              ctr               |     window_end
--------+--------------------------------+---------------------
1 |                           0.50 | 2022-06-22 12:58:00
1 |                          0.375 | 2022-06-22 14:02:00
1 |                           0.40 | 2022-06-22 17:51:00
1 | 0.5384615384615384615384615385 | 2022-06-22 18:08:00
1 |                           0.50 | 2022-06-22 18:11:00
1 |                           0.80 | 2022-06-22 19:57:00
1 |                          0.375 | 2022-06-22 20:13:00
2 |                         0.4375 | 2022-06-22 14:44:00
2 |                           0.50 | 2022-06-22 18:29:00
2 |                           0.40 | 2022-06-22 20:25:00

I guess there is something wrong with encoding. I'll take a look at this.

I just encountered a similar problem. Maybe related #3452

Can't reproduce, feel free to open it again if it still happens.


Option to add redirects to --save-old-urls

Summary
Right now the modules enables to keep old url rewrites. For url consistency it would be helpful to have the ability to redirect old urls to the newly generated 'consistent' urls.
It would be nice if copied incorrect urls would still redirect to the correct url. So copied links on external websites, emails, etc would still work.
Basic example
An added option to --save-old-urls that would add a redirect from the old urls to the new urls.

Hey @koentjeh, this kind of looks like the same issue i had before, maby this also helps in your situation. Please check out this thread where i explain my solution :)
https://github.com/olegkoval/magento2-regenerate_url_rewrites/issues/53
Please try in a test-environment first!


feat: new calendar components

Thanks to Eduard Predescu for his ongoing work on RadixVue Calendar ❤

I'll try to update docs and add more examples for Calendar or other components and also remove "New" labels from old components in docs.ts (sidenav)

Waiting for new calendar fixes to be released after that we can merge this ✨

@sadeghbarati We can merge this! Also, let's remove those "new" tag for other components 😁


[iOS] make WXPerformBlockSyncOnBridgeThread public

CheckList:
if isBugFix :

[x] Make sure that you add at least one unit test for the bug which you had fixed.

elif isNewFeature :

[ ] Update API docs for the component.
[ ] Update/Add demo to demonstrate new feature.
[ ] Update test scripts for the feature.
[ ] Add unit tests for the feature.

We already public this method in master. This pr will be closed.
Thanks.


Add automated release process and fix tslint errors

Hey @RobinBuschmann, hopefully everything is fine for you! :heart:
Just wanted to know, what is the current state for adding colaborators to the project and how is going with the automated release process via GitHub as discussed in #856.
If you need some help to maintain sequelize-typescript, I would be happy to do so. 😃
What changes this PR introduce ?

Update dependencies to the latest version so it fixes vulnerabilities
Delete the package-lock.json file since packages on npm doesn't have lockfiles (I added a rule for that in .npmrc).
Add .github/dependabot.yml
Fix ts-lint errors since the current build on master is failing
Delete .travis.yml file and instead use GitHub Actions as it is better integrated with GitHub and they change their pricing model, see: blog post
Create a GitHub Action to automatically release the package on npm when someone create a new release on GitHub (see .github/workflows/npm-publish.yml)
You will need to set a new secret NPM_TOKEN on the repo so it could works as it is explained there.

I totally forgot to answer your questions.

Just wanted to know, what is the current state for adding colaborators to the project and how is going with the automated release process via GitHub as discussed in #856.

I did not add anyone as collaborator yet and I also didn't make any efforts to implement an automated release process. Are you interested in being added as a collaborator for this project?

I totally forgot to answer your questions.

Just wanted to know, what is the current state for adding colaborators to the project and how is going with the automated release process via GitHub as discussed in #856.

I did not add anyone as collaborator yet and I also didn't make any efforts to implement an automated release process. Are you interested in being added as a collaborator for this project?

@RobinBuschmann Right, I bring back the package-lock.json file.
I would be interested to maintain sequelize-typescript not as a real core contributor but to approve PRs, answer issues, yes with pleasure!

@RobinBuschmann Right, I bring back the package-lock.json file.
I would be interested to maintain sequelize-typescript not as a real core contributor but to approve PRs, answer issues, yes with pleasure!

@Divlo Thanks for fixing ;) The builds are failing due to /home/runner/work/_temp/d5780aa8-b8a0-4c2d-b34d-68a6ae9131f8.sh: line 1: nyc: command not found. Any ideas why it can't find nyc?

@Divlo Thanks for fixing ;) The builds are failing due to /home/runner/work/_temp/d5780aa8-b8a0-4c2d-b34d-68a6ae9131f8.sh: line 1: nyc: command not found. Any ideas why it can't find nyc?

@RobinBuschmann Good, I answer and closed incorrect issues. If I accidentally closed a real issue, please reopen it.
I also approve PR that need to be merged, I'll try to continue this work and answer issues in the future. :smile:
Note: dependabot doesn't need to run (branch protection rules), since it will never run, because it runs once a day to update dependencies. I don't know why but the dependencies badges on the README is broken.

@RobinBuschmann Good, I answer and closed incorrect issues. If I accidentally closed a real issue, please reopen it.
I also approve PR that need to be merged, I'll try to continue this work and answer issues in the future. :smile:
Note: dependabot doesn't need to run (branch protection rules), since it will never run, because it runs once a day to update dependencies. I don't know why but the dependencies badges on the README is broken.

@Divlo

Note: dependabot doesn't need to run (branch protection rules), since it will never run, because it runs once a day to update dependencies.
Ha, yes, makes totally sense :D Thanks!

Good, I answer and closed incorrect issues. If I accidentally closed a real issue, please reopen it.
I also approve PR that need to be merged, I'll try to continue this work and answer issues in the future. 😄

Great! Unfortunately I don't have time to check all issues you've commented. So I trust you to be conscientious :)

@Divlo

Note: dependabot doesn't need to run (branch protection rules), since it will never run, because it runs once a day to update dependencies.
Ha, yes, makes totally sense :D Thanks!

Good, I answer and closed incorrect issues. If I accidentally closed a real issue, please reopen it.
I also approve PR that need to be merged, I'll try to continue this work and answer issues in the future. 😄

Great! Unfortunately I don't have time to check all issues you've commented. So I trust you to be conscientious :)


mark_as_consumed! is not stubbed, causing Karafka::Errors::MissingClientError

Affects 1.3, 1.4 and 2.0.
Won't be fixed in 1.3 as it is no longer supported.

new karafka-testing has been released. it fixes this problem.

ah reopening as need to add it to 2.0 as well


Support MSVC 32-bit "C decorated name" style symbol mangle (stdcall, fastcall, cdecl)

Is your feature request related to a problem? Please describe.
The MSVC compiler will mangle C symbols, with a different style being used per calling convention. According to the documentation, this is only applicable to 32-bit code.
Ghidra does not currently handle demangling of these symbols. I do have a workaround in a script here, but it should be fixed properly, likely in MDmang.
The mangle/decoration style is documented here, and I'll reproduce it here:

Calling convention
Decoration

__cdecl
Leading underscore (_)

__stdcall
Leading underscore (_) and a trailing at sign (@) followed by the number of bytes in the parameter list in decimal

__fastcall
Leading and trailing at signs (@) followed by a decimal number representing the number of bytes in the parameter list

__vectorcall
Two trailing at signs (@@) followed by a decimal number of bytes in the parameter list

Here is a minimal example for testing, compiled with MSVC compiler (32bit 13.00.9466). When loading into Ghidra, the symbols will be recovered but will not be demangled properly.
int __stdcall func_stdcall(int x) {
	return x+1;
}

int __fastcall func_fastcall(int x) {
	return x+1;
}

int __cdecl func_cdecl(int x) {
	return x+1;
}

Compile with: cl.exe /c example.c
Symbol table:
$ strings example.obj | grep func
_func_stdcall@4
@func_fastcall@4
_func_cdecl

Download source and compiled object file here: example.zip
If you link to create a full .exe with the /map flag to generate a mapfile, the map file will also list symbols in this way:
 0001:00000000       _func_stdcall@4            00401000 f   example.obj
 0001:0000000d       @func_fastcall@4           0040100d f   example.obj
 0001:0000001e       _func_cdecl                0040101e f   example.obj

Describe the solution you'd like
Ideally Ghidra should support demangling these symbol names with the MicrosoftDemangler.
Describe alternatives you've considered
I've created a script to demangle these names, but I consider the script approach to be a second-class solution.
Additional context
Ghidra recovers the symbol names from the object file symbol table, but does not demangle them as expected:

I extended your example with
int __stdcall func_stdcall_1(int x, char c) {
	return x+1+(int)c;
}

int __fastcall func_fastcall_1(int x, char c) {
	return x+1+(int)c;
}

int __cdecl func_cdecl_1(int x, char c) {
	return x+1+(int)c;
}

int __stdcall func_stdcall_2(int x, char c, float f) {
	return x+1+(int)c+((f > 0)? 1: 0);
}

int __fastcall func_fastcall_2(int x, char c, float f) {
	return x+1+(int)c+((f > 0)? 1: 0);
}

int __cdecl func_cdecl_2(int x, char c, float f) {
	return x+1+(int)c+((f > 0)? 1: 0);
}

Output is was as I thought it might be (representing 4 bytes of storage for char):
 0001:00000000       _func_stdcall@4            00401000 f   test.obj
 0001:00000010       @func_fastcall@4           00401010 f   test.obj
 0001:00000030       _func_cdecl                00401030 f   test.obj
 0001:00000040       _func_stdcall_1@8          00401040 f   test.obj
 0001:00000060       @func_fastcall_1@8         00401060 f   test.obj
 0001:00000080       _func_cdecl_1              00401080 f   test.obj
 0001:00000090       _func_stdcall_2@12         00401090 f   test.obj
 0001:000000d0       @func_fastcall_2@12        004010d0 f   test.obj
 0001:00000110       _func_cdecl_2              00401110 f   test.obj

I don't think there is anything we can do with the parameter storage anyway.
Regarding cdecl mangling, I don't see any way to distinguish the mangled symbol from any other non-mangled symbol.  It could easily be a global integer variable.

I don't think there is anything we can do with the parameter storage anyway.

I'm not sure exactly, but I'm pretty sure the prototype could be checked/updated to make sure the correct number of paramaters are present. The char param in your example will be implicitly sign extended to an integer, so in your example above I do expect it to take 4 bytes as you've shown.

Regarding cdecl mangling, I don't see any way to distinguish the mangled symbol from any other non-mangled symbol. It could easily be a global integer variable.

According to the documentation I linked previously, I think all C symbols compiled with MSVC should be decorated/mangled in this case (32b executable), unless some symbol is intentionally added that violates this convention.
As for globals, I actually wasn't sure what the compiler would do; so I've tested it and confirmed that global integer values are also decorated like cdecl, with a prefixed underscore. Compiled the same way as before:
int my_global;
int _my_global2;

$ strings example.obj | grep my_global
__my_global2
_my_global

I think this name demangling policy would be generally safe to add (that is, not demangling clean names), under the condition that the target executable being analyzed is 32bit.

@mborgerson @GXTX
There has been no progress on this other than more thoughts triggered by your query.
Issue in the past was with a collision in the mangled name space.  Example is if we find a symbol _name at an address, if it is of an integer type, we don't want to create a function with cdecl convention; but if there is or should be a function, we might want to create a function with its signature.  There could also be a collision between the mangled name in the older scheme and a non-mangled name in the newer scheme where both are functions, but have different calling conventions.  The current demangler processing model does not use knowledge about the target architectures or whether there is or will be a function at the address; this is likely part of the change that would be needed to make this work.
Assuming we change the processing model to pass in information to break the processing conflict, we then need to confirm that we can lock in the signature in an appropriate way that does not lock it so tightly that the Decompiler cannot hone the result.  I believe that we have the new ability to set some parts of the signature (maybe the CC) without locking all... need to wait for @ghidra1 to consult.  I also think we would be limited to setting arguments to undefined4 type, which would hopefully let them be reassigned by the Decompiler.  What the triage of 4 years ago did was confirm that char, int, and float all used 4 bytes; so it would be an assumption that we would take the total size of parameters and divide by 4 to get the number of parameters.  If this assumption is wrong, it could make things worse.
Do you have thoughts on this?


can't use azure-sdk-for python in china

hi team
we can't use azure-sdk-for python in china. after I replaced from windows.net to chinacloudapi.cn still can't use it.

I've listed the various base URLs to use here:
https://github.com/Azure/azure-sdk-for-python/issues/284

Will close this.  If you still have trouble, please reopen and include the relevant code snippets.  Thanks.


Feature: keep node on even versions

Closes #6274
This PR ignores a number of off versions of nodejs image and reverts the current image back to the latest v22 image.
There seems to be no way to know if a version of node is LTS so we will end up going to a even version before it's really a LTS version.
see also https://github.com/dependabot/dependabot-core/issues/2247 for a description of the problem.

Thanks but I don’t have any reason to limit it to only LTS


Add ReduxPersist to an existing boilerplate project

Hi. Great project! It enabled me to start creating an app without knowing much about mobile development. My inexperience has betrayed me though. I'd never use ReduxPersist and I thought I wouldn't be needing it when generating my project. I regret that decision now and I would want to add it. If some one could spare some of their time, I could use some help setting it up on an existing project.
Thanks in advance 🙂

This generator uses ignite-redux-persist to set that up, so you may be able to simply run ignite add<EMAIL_ADDRESS>

Thanks for the kind words, @jrodriguesimg! Also, thanks for helping out, @ruddell !


Clarify that on-the-wire communication with Simplenote is encrypted (#207)

Hi troy,
Could you close this and make the pull request to the 2.2.5 branch?


import dependency tree

I wonder if it's easy to get a tree representation of all the modules that import other modules so we can see when a certain module is changed, which other modules have to recompile.
In our project, we have over 300 files and recompiles are costly bottlenecks of the workflow.
Love your work btw!

Good point! I've been making some structural changes for #102 which already collects all the data for this. In #101 I removed the directed layout while it was mainly missing this information and not properly performing.
I'm thinking about using http://www.graphviz.org/ but I am not sure yet.

Looks like a nice tool to get some dependency trees going. The current implementation (elm-visualization) has some artefacts where the centre node would jump around.
I didn't realise you started with a directed graph. That information would be awesome to have! I'd happily take on extra CPU cost to see it!

I've released a digraph representation that can be viewed using graphviz in the 0.12.0 release. Have you checked it out?


Admin-Lte anda Laravel entristece-gui views problem

Hi.
There are some incoatibility with user packed var when view is maked. The user VAR is uded by entrust-gui too. To solve this without overwrite controllers i change the name of the user packed VAR before sending it yo View.

???

Hi. Apologies, it was the fault of the corrector in Spanish.
This is the problem. I have entrust-gui installed to handle permissions and roles.
When I try to use the views along with the admin-lte layout there is a conflict because the user variable passed to the view has the same name in the two packages.
Is there any way to publish the Controllers to be able to change the variable without touching the package? Otherwise maybe for some update a custom variable name could be used so that there is no conflict with a very common variable name like "Users"

@pbaldovi AdminLTE is only a UI/UX and can used in any Framework, ask the Laravel Community for this problem.


Full width not working

Hi, I'm trying to set the the width property to 100% and it doesn't work.
Only with CSS it also doesn't work pretty good, there is a offset of about 20 pixels to the right which doesn't get drawed.

What should I do? Could you add full width support to it?

You can handle dynamic width and height for canvas by provide parent width and height to canvas.
this should give you the idea
Notice the image that you draw is in pixels, that means if you have a canvas with 100px wide and you draw along its width, then you change it to 200px, the lines you drew earlier will still be 100px

P.S. don't forget to handle on window resize


[SYSTEMML-632] Handle source statements in imported scripts

This patch expands parser wrapper import statement processing to handle cases where an imported script1 also imports and calls functions in another script2.  Previously, the custom function calls in script1 to script2 would fail due to namespace undefined in main script.  Test cases were added for both dml and pydml where an imported script sources additional script(s) that also source scripts.

All tests passed in OnDemand build 143.
As an additional manual test outside the unit tests, reused the deep learning scripts from SYSTEMML-618 and moved the workaround source statements to files that directly use the imported functions.  For example, modified tests.dml imported grad_check.dml and test.dml only.  Similarly, grad_check.dml and test.dml imported the files each one directly used.
Verified the revised tests.dml ran successfully.
Note SYSTEMML-631 opened to address handling of potential namespace conflicts.

thanks @gweidner - I would recommend to also add some tests with functions that are not inlined in order to test the runtime part as well. Right now we inline any "single-statement-block functions" (recursively).  So for example a function with control flow like loops or non-folded branches would do the trick.

@gweidner This is awesome!  I ran some tests locally, and the intended use case of executing source statements in a sourced module so that those required modules don't have to be sourced at the top-level script works great.  Thanks!

Also, I found another specific case that we'll want to test for as part of the follow-up SYSTEMML-631: modules that (inadvertently) source themselves, or more generally, circular references.  Otherwise we will end up in an infinite loop.  In general though, if we fix the handling of namespace conflicts and duplicates, this will be fixed anyway.

Thank you both for the review, comments and feedback.  I've push commits to address the following:

Added tests with non-inlined functions at the inner-most imported script.  The corresponding test scripts were adapted from functions.misc.FunctionInliningTest except functions foo1 and foo2 were refactored into separate script files.  Manually checked under Eclipse debugger that StatementBlock.rIsInlineableFunction returned false (at reject control flow blocks).

Added verification of no parser error output to console (similar to what was done in functions.misc.SetWorkingDirTest of SYSTEMML-611.  This ensures test fails when parse issues displayed to console.

Also investigated circular references between separate scripts and reproduced stack overflow issue SYSTEMML-625.  Based on stack trace, it hangs in ParseTreeWalker loop before ParserWrapper.createDMLProgram modified in this PR.  I can next look into both issues [SYSTEMML-631], [SYSTEMML-625] as part of separate PR(s).

LGTM - thanks @gweidner
With regard to circular references, I would recommend to use a similar approach as IPA and the parfor optimizer, i.e., a simple function/namespace stack that is carried along while parsing.

Merged.  Thanks, @gweidner!


New issue Between Aurora And Corsair MM800

So, after the update of Aurora to 0.5.1b it still reports Corsair as uninitialized. I have done a clean install of aurora when updating it and I did the same to CUE 2 v2.4.66, as before CUE2 reports it being controlled by third party software but Aurora dont initalize it. my previus issue is: #154 Is there any additional information I can provide to help fixing this?
Edit, Including the logfile:
http://puu.sh/rmAOA/b59bed543e.txt
Looking at the logfile Aurora seems unable to even Identify the MM800

Oh... your issue was due to the mouse mat not being supported. My apologies, I thought it was related to the fact that other users had issues with CUE 2.
Umm.. well, unfortunately, full MM support won't come until next big version. If I need to release a 0.5.1c, then I will include a solid color based on the single peripheral light.

How far off are we-isch to the next big update? currently the only features I was planning on using was slow breathing from bright to dark red and the Interactive flow effect, I can patiently wait and use CUE2 for the breathing effect in the meantime so you do not need to rush in a hotfix if you don't want to.

I cannot tell you an exact date, we still have to convert all game profiles to the new layers system, finish up different keyboard/mouse virtual configurations, and resolve issues with foreign keyboard layouts. So.. It's a bit of work. Plus we have some people contributing to this project, so it would be nice to sync up completion dates.

I hear it WILL be WORTH the wait :)

I added support for it in the 0.5.1c version as well as the dev branch.


ITP for debian

I intend to package and maintain pick for Debian.
All files are licensed with the MIT license?

@eavgerinos That's great, thank you!
There is some BSD licensed code in https://github.com/thoughtbot/pick/tree/master/src/compat.

Nice :) I'll close this issue when the ftp-masters approve the package.

Awesome! Thanks so much!

UPDATE: Progress can be tracked here

Submitted the package to Debian.
Now we are waiting the Debian ftp-masters to review it (it may take a while considering they are busy with the jessie stable release)

That's awesome! Thanks for helping out, @eavgerinos!

Accepted to Debian unstable (at last) :)

Great! Thanks a lot @eavgerinos! Would you like to add installation instructions to the README?

Will do later today :) (or worst case withing this week)

No hurry! Thanks.

Hey @eavgerinos! I just released pick 1.2.0. Would you like to update the Debian package and also add installation instructions to the README?


Cloud Native Checklist - typo

In contents (and heading)
Modeled -> Modelled
Modeled -> Modelled

Fixed in #28


update template engine code sample

renderSync has been renamed to renderComponent in Lume.Engine
see also lumeland/lume@fc8b331

Good catch. Thanks!


downgrade to protobuf 3 to satisfy temporary workaround

What was changed
This PR essentially reverts the protobuf 4 upgrade changes that were merged into main as part of https://github.com/temporalio/sdk-python/pull/136. The intent of this PR is to create a workaround for projects that incur unresolvable package dependency issues caused by the upgrade and is NOT meant to be merged into main.
Relevant Slack thread in Temporal Slack community: https://temporalio.slack.com/archives/CTT84RS0P/p1667336466199119
Why?
temporalio==0.1b2 introduced some nice changes like the testing module but also upgrades the protobuf dependency to protobuf < 4.22, >= 4.21 which can cause issues in existing projects that utilize packages that don't support protobuf 4. As a workaround, this PR downgrades the protobuf package and attempts to create a wheel that includes the 0.1b2 changes excluding the protobuf upgrade.
Checklist

This PR doesn't close any issues but the relevant issue to track this is https://github.com/temporalio/sdk-python/issues/181

How was this tested:
As long as CI passes I think we're good?

Any docs updates needed?
None needed I believe

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

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

Approving to run. This made more changes than just the proto downgrade.

Yep, thanks for pointing that out @cretz I'm still in the process of grooming the changes will poke you when I feel like it's ready

Okay I think it's in a state now where at least the files touched are the same as the update PR. Lines changed still look a little different but :man_shrugging:

See https://github.com/temporalio/sdk-python/pull/215 where I have added proto 3 support back into the library

@jeremy-cho-skydio - with proto 3 and proto 4 now both supported in the latest release, can we close this?

Closing PR. Can reopen if needed.


Fix typo on Chinese documents

As title.

Codecov Report

Merging #12982 into master will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #12982   +/-   ##
=======================================
  Coverage   42.60%   42.60%
=======================================
  Files         671      671
  Lines       73625    73625
=======================================
+ Hits        31366    31369    +3
+ Misses      37179    37174    -5
- Partials     5080     5082    +2

Impacted Files
Coverage Δ

modules/indexer/stats/db.go
60.86% <0.00%> (-8.70%)
:arrow_down:

modules/git/repo.go
46.70% <0.00%> (-1.02%)
:arrow_down:

services/pull/pull.go
40.78% <0.00%> (-0.50%)
:arrow_down:

modules/queue/workerpool.go
60.00% <0.00%> (+1.22%)
:arrow_up:

modules/queue/unique_queue_disk_channel.go
55.38% <0.00%> (+1.53%)
:arrow_up:

modules/log/event.go
59.43% <0.00%> (+1.88%)
:arrow_up:

Continue to review full report at Codecov.

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


fix(12): use proper bracketing, don't use numeral

Use zero instead of 0 to explicitly avoid notation here.

merged by 0acbf4e


Inline text highlighting

Problem
Outlook partners are asking for a way to highlight a portion of a TextBlock. There is currently no way to do so.
Proposed solution
Markdown officially allows html tags. We should allow the use of the standard  tag in TextBlock. For instance:
{
    "type": "TextBlock",
    "text": "This is <mark>highlighted</mark>"
}

would result in the word "highlighted" being, well, highlighted.
The highlight color would have to be configurable in HostConfig as part of container styles. The associated font color for highlighted text would also have to be configurable (given that the highlight essentially changes the text's background color.) It would look like this:
{
        ...
        containerStyles: {
            default: {
                backgroundColor: "#FFFFFF",
                foregroundColors: {
                        ...
                },
                highlightBackgroundColor: "#0000FF",
                highlightForegroundColor: "#FFFFFF"
            },
            ...
        }
}

Open questions

How easy is it to programmatically construct markdown? There doesn't seem to be any libraries for it. Maybe we should use an array of runs instead?

Alt solution
[Andrew Leader] Mimick what XAML does with RichTextBlock...
{
  "type": "RichTextBlock",
  "wrap": 2,
  "paragraphs": [
    {
      "inlines": [
        {
          "type": "TextRun",
          "text": "This is "
        },
        {
          "type": "TextRun",
          "text": "highlighted",
          "highlight": true
        }
      ]
    }
  ]
}

This could also be our solution for inline colors, #1079, and inline advanced emojis #1645, and inline actions #865

Closing in favor of the consolidated inline text runs issue: #1933


Create ability/filter to view adopted drains on map all at once

This could be in the admin area or on the main page.

this can be done by exporting adopted drains to excel and then creating a map, so i'm a gonna close it.


device register action failing on OSX

when running the command resin device register on OSX I see the following:
ಠ_ಠ (04:52 pm) ~/ resin device register 17202
Registering to Virtuality: 8105ef2de26a7a62efec35fbd3db74cf510d0b7ebb5069a881e0fd2895374a
ResinRequestError: Request error: If the id property is set it must be non-null

If you need help, don't hesitate in contacting us at:

  GitHub: https://github.com/resin-io/resin-cli/issues/new
  Forums: https://forums.resin.io

ಠ_ಠ (04:52 pm) ~/ resin device register Virtuality
Registering to Virtuality: cbfac3e490bcad6a766434d423b5a41d8dc335f4380e8f15022ac7c1c54f68
ResinRequestError: Request error: If the id property is set it must be non-null

If you need help, don't hesitate in contacting us at:

  GitHub: https://github.com/resin-io/resin-cli/issues/new
  Forums: https://forums.resin.io

No idea why this never got looked into at the time, sorry. I'm assuming @LucianBuzzo you have no idea what was causing this, and no way to reproduce it now?
I can't see any reports of this in our sentry logs (which cover the last 90 days), and we haven't changed the core logic of this code in the CLI for quite a while now, so I suspect this was an api bug. Lots of the logic around provisioning was changing around that kind of time. I'm going to close this for now, but feel free to reopen if you can still reproduce this.


python, ruby: Remove collapsed files after reading

Description
We do not delete the output files of py-spy and rbspy. This PR fixes that.
The issue was introduced in 1efe4a7f87d322beaa1708cb56a5913c18e316e9 (version 1.0.0) - we ceased from deleting the core temporary folder each iteration, instead it survives for the lifetime of the GProfiler object.
It was worsened by 0ab54a089f9c31d267b29e4a1b33060c68ff7e58 which added random a prefix in each output file - so now files of the same target PID don't override each other; so storage keeps on growing!
Motivation and Context
Bugfix.
How Has This Been Tested?

Verified manually that files are now gone.
Added logic to the tests to ensure it from now on.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have updated the relevant documentation.
[x] I have added tests for new logic.

Tests fail because the intermediate storage dir (e.g: tmpygfl6_1a) also exists.
Also, I realized that the test isn't good: after going down, it makes sense if gProfiler removes its files. What's interesting to check if before going down & after a bunch of iterations. Will add that test instead.

Code is good.
Test doesn't work because we have another temp dir.

We will add these tests later, first I want to solve this issue


Uncaught Exception: listen EADDRINUSE <IP_ADDRESS>:5672

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.2.4
Time: Sat Jun 11 2016 22:50:12 GMT-0400 (Eastern Daylight Time)
Error:
listen EADDRINUSE <IP_ADDRESS>:5672
Error: listen EADDRINUSE <IP_ADDRESS>:5672
    at Object.exports._errnoException (util.js:890:11)
    at exports._exceptionWithHostPort (util.js:913:20)
    at Server._listen2 (net.js:1234:14)
    at listen (net.js:1270:10)
    at net.js:1379:9
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #325


Add Styling to the Contact icons

I think these icons would be more appealing if they change background color on hover.
So , may I make this small change ?

Sure @VanshSh


Add Runescape

Thank you for the contribution! Case insensitive is the worst. 😠

Yeah, the security posture at Jagex is very bad with all the hacks and leaks in the past years. They seem to be stuck in the '90s!


[FR] Parametric Net Survival

- [ ] Like a cox model but with an offset for the population part
- [ ] Possibility for mixed effects ? Longitudinal ?

Wait for SurvivalModels.jl to catch up, will be easier.


InsertAsync is not async

In the GenericSqlStatements class there is an InsertAsync method.
Why does this method use the connection.Execute and not the connection.ExecuteAsync ?
    public async Task InsertAsync(IDbConnection connection, TEntity entity, AggregatedSqlStatementOptions<TEntity> statementOptions)
    {
        if (_sqlBuilder.RefreshOnInsertProperties.Length > 0)
        {
            var insertedEntity =
                (await
                 connection.QueryAsync<TEntity>(
                     _sqlBuilder.ConstructFullInsertStatement(),
                     entity,
                     transaction: statementOptions.Transaction,
                     commandTimeout: (int?)statementOptions.CommandTimeout?.TotalSeconds)).FirstOrDefault();
            // copy all the database generated props back onto our entity
            this.CopyEntity(insertedEntity, entity, _sqlBuilder.RefreshOnInsertProperties);
        }
        else
        {
            connection.Execute(
                _sqlBuilder.ConstructFullInsertStatement(),
                entity,
                transaction: statementOptions.Transaction,
                commandTimeout: (int?)statementOptions.CommandTimeout?.TotalSeconds);
        }
    }

Yeah that looks like a bug to me.

I've created the following PR to address this issue:
https://github.com/MoonStorm/Dapper.FastCRUD/pull/153

fixed