ASTC encoding

This PR adds ASTC encoding support via -t astc4x4 etc. There's also #ifdef'd support for ASTC decoding in image.cpp, which, going by the in-file style of the existing decoders, is not really appropriate to be in the core lib, as it requires a significant amount of code from 3rdparty/astc. You might want to just exclude it, I was using it for testing, as there wasn't a clean way to inject it as part of image_decode (say).
The ASTC codec is originally from https://github.com/ARM-software/astc-encoder, I've modified it so it can be used in library form.

There is some issue with VS build:
referenced in function "class vtype4 __cdecl eigenvector(struct mat4,float)" (?eigenvector@@YA?AV?$vtype4@M@@Umat4@@M@

Yup, I forgot to re-apply the usual Windows compile fixes when updating to the latest astc-encoder that's now on github. 85e79c2 fixed some of it, 3bcf40f should be the final, famous last words.

I disabled it for now until I have time to figure out decoding and 3rdparty dependencies.

Thanks. I was wondering about a decoder function hook that defaulted to the checkerboard, but could be overridden by texturec.
I'll try to remember tabs v spaces next time :)

I'll try to remember tabs v spaces next time :)

Just install EditorConfig https://editorconfig.org/ for your favourite editor and you don't have to worry about it.


Client Definations - Switch from copy to template

Initial shot at resolving https://github.com/sensu/sensu-ansible/issues/211 by switching this to template. Opening the PR to see if the integration tests pass.
Signed-off-by: Jared Ledvina<EMAIL_ADDRESS>

Nope won't work, see https://github.com/sensu/sensu-ansible/issues/211#issuecomment-466716560


Added autofill functionality for all sheets in the study doc

Summary Change Description
Added autofill functionality for all sheets in the study doc
Also fixed issues encountered in manual testing.
Details:

added: Each column in each sheet in the study doc that references columns in other sheets were used to feed the autofill dict.
fixed: Added population of the LC Protocols sheet with all data from the database (when a study doc was provided - previously it was only happening with the first load of a peak annotations file without an accompanying study doc).
changed: Improved next row index and next row group number determination using the max() builtin instead of assuming that the length was the next number.
changed: Previously, the row group number in the infusates and tracers sheet was only calculated and tracked in individual methods.  When I added functionality to other methods to be able to add rows to those sheets, the row group numbers were getting re-used inappropriately, so I made instance attributes for keeping track of the next infusate and tracer row group numbers.
changed: Changed the autofill-only mode determination to be based on the population of any column NOT involved in autofill (whether it's a column that feeds the autofill dict or consumes it.
fixed: Tweaked the _read_from_excel method to ignore dtype if the sheet isn't present in the dtype dict.
changed: Added type hints to all models that have a custom objects instance (so that their methods get highlighted and get contextual menus when right-clicked in VS Code).
changed: Wrapped the call in Tracer to Compound.compound_matching_name_or_synonym in a try/catch.
added: Added a method to MSRunSequence: parse_sequence_name, along with a class attribute for the sequence name delimiter.
added: Added a method to LCMethod: parse_lc_protocol_name.
changed: Changed the order of the StudyTableLoader.DataUniqueColumnConstraints so that the NAME would be first.
changed: Changed the TracersLoader.DataUniqueColumnConstraints to have only 1 group (instead of 2) so that both NAME and ID would be in the same unique constraint, in order to correctly calculate a unique key to look up rows that need an ID to distinguish them.
changed: Removed DAYS_INFUSED_KEY from DataRequiredValues in the SamplesLoader, because the database field is optional.
added: Added an optional class attribute to TableLoader: FieldToDataValueConverter, which is used in get_dataframe_template to populate the column in the correct units, when the default representation of what's in the database is not the same as what we accept as input.  This was used for Animal.age, Sample.collection_time, and LCMethod.run_length.

Affected Issues/Pull Requests

Partially addresses #829
Merges into PR #1029
Next PR: #1035

Review Notes
This PR turned out to be bigger than I'd initially expected, but I think I should be able to comment the changes to make review relatively easy, compared to its size.
Checklist

This pull request will be merged once the following requirements are met.  The
author and/or reviewers should uncheck any unmet requirements:

Review requirements

Minimum approvals: 1
No changes requested
All blocking issues resolved by reviewers
Specific reviewers: @add_username_here

Review period: 2 days

Associated issue/pull request requirements:

[x] All requirements in affected issues marked "resolved" are satisfied
[x] All required pull requests are merged (or none)

Basic requirements

[x] All linters pass
[x] All tests pass
[x] All conflicts resolved

Overhead requirements

[x] New/changed method tests implemented/updated (or no change)
[ ] Updated Unreleased section of changelog.md (or no change)
[x] Migrations created & committed (or no change)

Merged via #1076


JWT support

We need a JWT support to manage tokens in headers for mantain user sessions
[ ] bug report => search github for a similar issue or PR before submitting
[X] feature request

It's done


[BUG]: dfencoder import missing from prod DFP example

Version
23.11
Which installation method(s) does this occur on?
Docker, Conda, Source
Describe the bug.
Last step of production DFP example fails with 'dfencoder' import missing.
Minimum reproducible example
python dfp_azure_pipeline.py --train_users none  --start_time "2022-08-30" --input_file="../../../data/dfp/azure-inference-data/*.json"

Relevant log output
Click here to see error details
[Downloading artifacts: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 6/6 [00:00<00:00, 20.53it/s]
2023/12/05 18:28:35 WARNING mlflow.pytorch: Stored model version '1.13.1+cu116' does not match installed PyTorch version '2.0.1'
Error trying to get model
Traceback (most recent call last):
File "/workspace/examples/digital_fingerprinting/production/morpheus/dfp/stages/dfp_inference_stage.py", line 101, in on_data
loaded_model = model_cache.load_model(self._client)
File "/workspace/examples/digital_fingerprinting/production/morpheus/dfp/utils/model_cache.py", line 109, in load_model
self._model = mlflow.pytorch.load_model(model_uri=self._model_uri)
File "/opt/conda/envs/morpheus/lib/python3.10/site-packages/mlflow/pytorch/init.py", line 713, in load_model
return _load_model(path=torch_model_artifacts_path, **kwargs)
File "/opt/conda/envs/morpheus/lib/python3.10/site-packages/mlflow/pytorch/init.py", line 628, in _load_model
return torch.load(model_path, **kwargs)
File "/opt/conda/envs/morpheus/lib/python3.10/site-packages/torch/serialization.py", line 809, in load
return _load(opened_zipfile, map_location, pickle_module, **pickle_load_args)
File "/opt/conda/envs/morpheus/lib/python3.10/site-packages/torch/serialization.py", line 1172, in _load
result = unpickler.load()
File "/opt/conda/envs/morpheus/lib/python3.10/site-packages/torch/serialization.py", line 1165, in find_class
return super().find_class(mod_name, name)
ModuleNotFoundError: No module named 'dfencoder'

Full env printout
Click here to see environment details
[Paste the results of print_env.sh here, it will be hidden by default]

Other/Misc.
No response
Code of Conduct

[X] I agree to follow Morpheus' Code of Conduct
[X] I have searched the open bugs and have found no duplicates for this bug report

closing, was due to old mlflow docker volumes from previous test runs


[Feature Request]Use default windows 11 context menu's More Options to open nileshell instead of open nileshell directly when the -treat parameter is not added

Use default windows 11 context menu's More Options to open nileshell instead of open nileshell directly when the -treat parameter is not added

I would like that, the only thing I don't like about nileshell and I like in the Windows context menu is having the icons for copy, cut, paste, rename and delete all together at the top or at the bottom.

I would like that, the only thing I don't like about nileshell and I do like about the Windows context menu is having the icons for copy, cut, paste, rename and delete all together at the top. In fact my favorite context menu is the Files one, which also adds the properties icon to the top bar and to show more options you don't have to click, just hover over it. The bad thing about Files is that it is a bit slow when showing me the context menu.

NS used to work this way. After a certain Windows update the legacy context menu could not be edited with NS when opened with "more option". The workaround was to stop the modern context menu (temporarily), but no solution has been found so far

copy, cut, paste, rename and delete all together at the top
https://github.com/moudey/Shell/issues/425#issuecomment-1959842606


Toast "email: required input is missing" is raised when hit Cancel (X) on the password reset form

Describe the bug
Toast "email: required input is missing" is raised when hit Cancel (X) on the password reset form
To Reproduce
Steps to reproduce the behavior:

Go to http://localhost:3000/password-reset
Click on 'X' to cancel
There's a toast popup message

Expected behavior
No toast

This also happens on the contact form.

Also in Register Form when you click 'save' with empty values.

Cannot reproduce anymore.


DBSCAN is commonly used. Hope to add it ~

Thanks for your idea. We could create a project in mljs organization with our setup to implement the algorithm. Once published we can add it in this project.
@DoubleCorner Would you like to implement this algorithm and the corresponding test cases ?

yes，it is my honor.

https://github.com/uhho/density-clustering/blob/master/lib/DBSCAN.js。 Many people in github have implemented DBSCAN. May be it is useful.

We just setup the project and if you are interested you may create a PR on https://github.com/mljs/dbscan.
If there are some reference implementation in R or Mathlab it is always interesting to check that the results are the same.

I have implement dbscan ~

logarithmic regression is not Found. it has been implemented ?


Add npm start command for server & front-end

Could use concurrently

See https://github.com/rijkvanzanten/obachine/pull/64


Test coverage for creating and viewing addons

During the revamp, test coverage for addons was forgone in order to ship faster. We need to revisit and fill out test coverage.
Test Cases

[ ] When wallet is not connected, should not be able to edit addons
[ ] When wallet is connected, should be able to add addon to list
[ ] When wallet is connected, should be able to reorder addons in list
[ ] When wallet is connected, should be able to delete an addon from list
[ ] When wallet is connected, should be able to toggle enable for addon in list

The multiselect presents some difficulties, see this for advice on how to implement

This is related to #709 so will make sure my PR includes the necessary test cases


Favorite comics sorting

Add the possibility to manually sort comic tiles in the favorites page
That sorting should maybe be reflected in the slideshow view as well

This is probably over-engineering


High score new config

#1257
Added new config value in config spec, and referenced that new value within high score. All tests run through unittest locally passed. No new unit test was added, though. Is that sufficient for testing these changes, or should I build my own local machine for a full test?

Hi @jabdoa2 , I have resubmitted with changes. Could you please review?

reverse_sort is now a category
config in both new machine and previous have been updated to account for category
new machine files are still required for test because of new test data breaking old tests


move wiki docs to sphinx

made a subdirectory for i24-ssx docs
copied everything from the wiki to the docs

the huge i24 ssx document should still be split up and recategorised


refactor(tests): replace K8sExecInPod with AssertCommand for consistency in test assertions

Purpose of PR?:
Fixes #1643
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::

Verified that the K8sExecInPod calls were successfully replaced with AssertCommand without impacting test results.
Confirmed that permissions and expected outputs are consistent with the new implementation.
Ensured that refactored code retains functionality across all test cases.

Additional information for reviewer? : This PR is part of the refactoring effort to standardize test execution methods. It follows up on a previous PR where initial AssertCommand replacements were introduced.
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[x] Bug fix. Fixes #1643
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Commit has unit tests
[x] Commit has integration tests

hey @daemon1024 @rootxrishabh please review this.

hey @rootxrishabh last time the checks failed because of some typo, i have fixed it and pushed the changes, please approve the workflows and let me know if you find anything else that needs to be fixed.

hey @daemon1024 @rootxrishabh if anyone of you can approve the workflow and review this, so that i get to know if everything is working fine with the changes.

Can we debug the tests and make them passing?

hey @daemon1024 i have fixed the errors occured in the tests, now they should succeed as expected. please approve the workflows. thanks.

@abhashsolanki18 there are some other issues as well that we're facing in CI, we're working on it, once it's fixed i will revert back here.

@abhashsolanki18 can you please rebase to main?

@abhashsolanki18 can you please rebase to main?

hey @rksharma95 i have rebased to main, thanks.

@abhashsolanki18 can you please rebase to main?

@rksharma95 Done.

@abhashsolanki18 can you squash the commits as well?

@rksharma95 Done.

hey @rksharma95  is this PR getting merged or are there any issue with the fix? thanks.

@abhashsolanki18 can you please handle the ci failure? We could merge after all tests are passing.

@rksharma95 please approve the tests, thanks.


Update Readme for beginners

Instructions on installing yarn and differences between yarn and using npm
setting up the environment
How to fork the repo and make a pull request, contribute
links to bootstrap 5 and react bootstrap, react router
Brief description of the folder structure each page has their own folder in components
setting up prettier in vscode and auto format on save

Hey, @redxzeta I am good at documentation can I too contribute for this issue. I am  Sophomore looking for Open Source Work.

Started but not finished.
On Wed, 13 Oct 2021, 20:07 Nathan, @.***> wrote:

@iamhardikat11 https://github.com/iamhardikat11 did you want to work on
this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/redxzeta/Awesome-Adoption/issues/125#issuecomment-942372985,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS27VSQXFAUAUUMZMNBHLILUGWKTZANCNFSM5F2ZEFYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@iamhardikat11 take your time


Collect a reason in a confirm dialog

Dear @volkanceylan,
I was wondering if there is a simple way to collect a reason (string) in a confirm dialog or something like that...
I have not seen any example to adapt...
Thanks for you support
Best Regards

You need to write one deriving from PropertyDialog. You can take NoteDialog as a sample.

Copy that!
Thank you very much


Testcafe does not respect base tag

What is your Test Scenario?
My application at some point injects <base> tag into website and after that creates a new <script> tag with relative src. Testcafe does not respect the value of base tag when injecting the <script> tag
What is the Current behavior?
For example sets <base href="http://localhost:8080/chapters/de/auth/"> and injects <script src="build.js" type="text/javascript" /> resulting into browser downloading script from http://localhost:8080/chapters/de/auth/build.js.
When running the same application in testcafe, the result is slightly different. Inserted base is  <base href-hammerhead-stored-value="http://localhost:8080/chapters/de/auth/" href="http://localhost:1337/Lj6CFUfNF/http://localhost:8080/chapters/de/auth/"> and script is <script src-hammerhead-stored-value="build.js" src="http://localhost:1337/Lj6CFUfNF!s!utf-8/http://localhost:8080/account/build.js" type="text/javascript" />
Suddenly the previously relative url build.js turned into http://localhost:8080/account/build.js which is inconsistent with what is set in
What is the Expected behavior?
I would expect the injected script tag to be <script src-hammerhead-stored-value="build.js" src="http://localhost:1337/Lj6CFUfNF!s!utf-8/http://localhost:8080/chapters/de/auth/build.js" type="text/javascript" />
What is your web application and your TestCafe test code?
I am sorry, there is no sample url available at the moment
Your Environment details:

testcafe version: 1.1.0
node.js version: 8.10.0
command-line arguments:  running from node:

createTestCafe('localhost', 1337, 1338)
    .then(testcafe => testcafe.createRunner()
        .src('e2e/**/*.test.js')
        .browsers(browsers)
        .startApp('yarn start')
        .run({
            selectorTimeout: 30000,
            assertionTimeout: 30000,
            skipJsErrors: true,
        })
    )
    .then(failedCount => {
        if (failedCount) {
            process.exit(1);
        }
        process.exit(0);
    });

browser name and version: Chrome
platform and version: macOs

I was not able to reproduce the issue. I prepared a sample project. Please check the attached file.
project.zip

I would appreciate it if you modify my example to reproduce the issue.

Hey @AlexKamaev
thank you very much for your reply. The project you sent works as expected and it took me some time to understand how is my use case different from yours. In the end, it seems, that it depends on where I am inejcting base tag into document. If that happens after the script is created (not injected) the testcafe seems to get confused. I have slightly updated your code to reflect that. In short term, I think I can update the base url before creating script tags in my case, it just seems that in this edge case testcafe / hammerhead is missbehaving slightly, so would still consider it being a bug
project.zip

Thank you @mbazalik
Now I can reproduce the issue. I think since there is a difference between Chrome and TestCafe we can consider this as a bug.


Support access-control-access-point-device device type

Is your feature request related to a problem? Please describe.
My residential apartment complex has implemented an alarm.com based gate access control system. Right now this requires use of a local dealer's alarm.com backed app to 'buzz' myself or a guest through the apartment complex gates and various other doors. Realise this is likely an implementation of a business grade alarm system but it would appear several residential apartment complexes in my area have employed the local Alarm.com dealer to do similar installations.
homebridge-node-alarm-dot-com is able to log in to the account I have been allocated but does not generate a HB accessory for any of the available devices.
[28/07/2024, 12:02:26] [Apartment Complex Gates] Initializing Alarmdotcom platform... [28/07/2024, 12:02:26] Loading 13 accessories.
Describe the solution you'd like
It would be great if this alarm.com accessory type was supported as Lock accessory (or perhaps a momentary switch would be better)
Additional context
This is how the devices appear in the https://www.alarm.com/web/api/devices/accessControlAccessPointDevices route:
    {       "id": "NNNNNNNNN-NNNN",       "type": "devices/access-control-access-point-device",       "attributes": {         "managedDeviceType": 1,         "state": 2,         "desiredState": 2,         "canBuzz": true,         "canLockUnlock": false,         "readerAntiPassbackEnabled": false,         "apbDelay": 0,         "twoPersonAccessEnabled": false,         "hasMiwaLock": false,         "twoPersonAccessSupported": false,         "hasState": true,         "canBeRenamed": true,         "canBeDeleted": false,         "canAccessWebSettings": true,         "canAccessAppSettings": false,         "webSettings": 505,         "canAccessTroubleshootingWizard": false,         "troubleshootingWizard": null,         "addDeviceResource": 0,         "canBeAssociatedToVideoDevice": true,         "associatedCameraDeviceIds": {},         "macAddress": "",         "manufacturer": "",         "isAssignedToCareReceiver": false,         "isOAuth": false,         "isZWave": false,         "supportsCommandClassBasic": false,         "isMalfunctioning": false,         "isZWaveWakeupNode": false,         "unitSupportsRemovingWakeupNode": false,         "primaryAssociatedDeviceIds": null,         "canBeSaved": false,         "canChangeDescription": false,         "description": "Front Gate",         "deviceModelId": 3315,         "canConfirmStateChange": true,         "canReceiveCommands": true,         "remoteCommandsEnabled": true,         "hasPermissionToChangeState": true,         "deviceIcon": {           "icon": 408         },         "batteryLevelNull": null,         "batteryLevelClassification": null       },       "relationships": {         "system": {           "data": {             "id": "NNNNNNNNN",             "type": "systems/system"           }         },         "stateInfo": {           "data": {             "id": "NNNNNNNNN-NNNN-N",             "type": "devices/state-info"           }         }       }     }
A 'buzz' event generates a call to the following route:
https://www.alarm.com/web/api/devices/accessControlAccessPointDevices/NNNNNNNNN-NNNN/buzz
with the following content
{"statePollOnly":false}
Very grateful for any consideration of this feature request!

Very interesting. Thank you for providing such an in-depth issue! Am I assuming correctly that state represents if the door is unlocked? Would it be reasonable for this to be represented as a lock in HK where the unlock motion sends a buzz and makes the lock appear as unlocked for x seconds?

Thanks for the response!
It would appear that 2 is the 'temporary unlock/buzz' state. It would appear there is also a lock/unlock method that would hold the door in state but "canLockUnlock": false does not expose this route to me.
I think your reasoning that this should be a HK lock representation is sound (I have hacked together a POC in Python and homebridge-script2 with hardcoded credentials and routes that presents this as a switch, but this probably isn't ideal).
Note, the way the system is configured in my apartment complex means that the 'default' system is empty (no idea why) so I have to send a POST to web/api/systems/availableSystemItems/{systemId}/selectSystemOrGroup before sending the /buzz request. I realise this puts us into Issue #20 territory which I note is a closed issue. This is a fairly newly configured system so perhaps the configuration will get cleaned up to a single system (since the second system is redundant at present).


Pipeline Triggers Documentation Implies Incorrect Behaviour

Hi,
On the Pipeline Triggers documentation , in the section defining CI behaviour based on branches, there is the statement:

If you don't specify any triggers, the default is as if you wrote:
trigger:
  branches:
    include:
    - '*'  # must quote since "*" is a YAML reserved character; we want a string

In the Q&A section at the bottom, there is then the statement:

The YAML file in my branch is different than the YAML file in my master branch, which one is used?
When you have configured a CI trigger or a PR trigger, the YAML file that is in the branch being pushed is used.

For CI triggers, the YAML file that is in the branch you are pushing is evaluated to see if a CI build should be run.
For PR triggers, the YAML file that is in the source branch of the PR is evaluated to see if a PR build should be run.

This suggests that the only thing that will cause the yml file in the push branch to be used is if a CI or PR trigger is defined. Because of the earlier statement that one is defined by default, the suggestion to me was that only if the CI or PR trigger was customised to be different from master would the local branch be used.
However, testing this behaviour shows that a change to a section other than the trigger, has the local change incorporated in the build. My testing example was to change the Agent Pool for the build job, leaving the default trigger in place in both master and my branch.
Rather than behaving as I would expect based on the above wording (I have not specified a trigger, so I would expect the master yml to be used), I instead see the non-trigger change (changing the Agent Pool) incorporated in my new build.
I would suggest that the behaviour of VSTS is correct, as I would always expect the 'local' pipeline yml to be used (unless advised otherwise as in this case!).
I think that the documentation should be updated to reword the Q&A section to state that the 'local' version of the pipelines yml will always be used (unless there are any use cases where it wouldn't be triggered from the branched version - I just haven't found one yet).
Let me know if more information is required.
Ben

@BenResTech I'll make an update to the documentation to make it clearer that it is the YAML file in the branch being pushed that is used, even if you don't have a CI or PR trigger explictly defined in the YAML file. I can see how the "When you have configured a trigger" portion is ambiguous. I'll get that fixes, thank you for pointing that out.


StaticTextBlock

Hi
1- how i can set the value in StaticTextBlock from the current row
2- i want to set the one parameter in request with fixed value from Dialog.ts and it's not in the form
example
this.form.xyz=123
i want or replace it to
this.request.xyz=123
so in my Repository i can make some conditions

Add a new field with the [NotMapped] property in the row:
        [DisplayName("xyz"), NotMapped]
        public String xyz
        {
            get { return Fields.xyz[this]; }
            set { Fields.xyz[this] = value; }
        }

Then on dialog, you can assign a value to it
protected getSaveEntity () {
           let entity = super.getSaveEntity ();
           entity.xyz = '123';
           return entity;
       }

Next in Repository:
 private class MySaveHandler : SaveRequestHandler<MyRow>
        {
            protected override void BeforeSave()
            {
                base.BeforeSave();
                if (Row.xzy == '123')
                {
                        //todo
                }
                else
                {
                    //todo else
                }
            }
        }

hope help you

Closed due inactivity
Also check the issue guidelines.
If you still need help, you can ask this on stackoverflow with our new tag.
https://stackoverflow.com/tags/serenity-platform


v0.17.0's dependency upon timers conflicts with celluloid v<IP_ADDRESS>'s dependency on it.

celluloid-io v0.17.0 has a "~> 4.0.0" requirement on timers which conflicts with celluloid v<IP_ADDRESS>'s ">= 4.1.1" requirement on timers.

I will recut Celluloid::IO -- which I believe is the only one I haven't recut with the new dependencies.

Resolved


Apply solution upgrade sometimes hangs

Hi Wael,
Tried setting to Async & increasing timeout
Thanks, Jeremy

@JezNorton do you see the same behaviour from the UI?
How long does it hang for and does it fail eventually?

@WaelHamze I've been cancelling the releases, I haven't let it fail yet, but it has gone on for hours. Upgrade works OK in CRM, but the release is broken.

@JezNorton if you set the system.debug = true in the release, where does the upgrade solution get to in the logs and what is the state of the environment/solutions after hours?

@WaelHamze will try system.debug = true for the next release. The upgrade solution completes in CRM, but doesn't feedback to DevOps

@JezNorton: I have experienced similar issues, although using our own tooling and not this. - However, do you have a big solution? Have you checked for how long a standard solution import (with publish) takes either in UI or by API directly (via XrmToolbox plugin for example)?
If your solution is too big, the proxy might time out. - it is actually not thaaat uncommon to see projects with solutions taking a loooong time (1hr+) to import.
Also, if you are using this via Azure Pipelines, please check the timeout limit on your agent. - Build pipelines have default 60 minutes timeout, while I cannot remember Release pipelines timeout if any.

@bo-stig-christensen: thanks for this, I'm helping this client with CRM DevOps, first thing was to trim down the solution , it now takes around 20 minutes to import and doesn't timeout when run manually


Dependencies - Not get the video jars

Hi all,
Using the instagram4j has grown my project times 5 in size. There are a ton of platform dependent jars that seem to be related to video. Anyone have a solution for excluding those from your local repository?
Thanks, Kosta

Maybe you could exclude dependencies when importing instagram4j. I don't have plans to cleanup it in the short term :(

Addressed in rewrite or no longer relevant.


non funziona un cazzo

Please briefly describe your problem and what output you expect. If you have a question, please don't use this form. Instead, ask on https://stackoverflow.com/ or https://community.rstudio.com/.
Please include a minimal reproducible example (AKA a reprex). If you've never heard of a reprex before, start by reading https://www.tidyverse.org/help/#reprex.
Brief description of the problem
# insert reprex here

non è vero che non funziona un cazzo

hai ragione!


Add $baddog assetlist.json

Adding baddog asset information. wasn't automatically pulled from cosmos registry.

Oops, had to revert @SmolFatality . Many details are incorrect--the base denom and the ibc data are not right.

Okay I will try to get it fixed correctly before I try to pr again. Sorry.


Permission per job

Pls add that you can define permissions per job, e.g. miner.job is needed to change the job to miner.

the next version will check if the player has a permission, that can be set in the config for a job, if he wants to join a job

Thx mate!


SceneSeg fails on machines that do not support CUDA (CPU-only)

Steps to reproduce
Run image_visualization.py or video_visualization.py pipelins on a machine that does not support CUDA.
Example:
On Macbook Pro M1 machine with 8 cores:
run python image_visualization.py --model_checkpoint_path <some path>/iter_140215_epoch_4_step_15999.pth --input_image_filepath <some path>/sample.jpg
Actual Result
I get the following error:

Attempting to deserialize object on a CUDA device but torch.cuda.is_available() is False. If you are running on a CPU-only machine, please use torch.load with map_location=torch.device('cpu') to map your storages to the CPU.

Stacktrace
Using cpu for inference
Traceback (most recent call last):
File "/autoware.privately-owned-vehicles/Models/visualizations/image_visualization.py", line 67, in
main()
File "/autoware.privately-owned-vehicles/Models/visualizations/image_visualization.py", line 44, in main
model = SceneSegNetworkInfer(checkpoint_path=model_checkpoint_path)
File "/autoware.privately-owned-vehicles/Models/visualizations/../inference/scene_seg_infer.py", line 30, in init
self.model.load_state_dict(torch.load
File "/env/lib/python3.9/site-packages/torch/serialization.py", line 1351, in load
return _load(
File "/env/lib/python3.9/site-packages/torch/serialization.py", line 1848, in _load
result = unpickler.load()
File "/env/lib/python3.9/site-packages/torch/_weights_only_unpickler.py", line 385, in load
self.append(self.persistent_load(pid))
File "/env/lib/python3.9/site-packages/torch/serialization.py", line 1812, in persistent_load
typed_storage = load_tensor(
File "/env/lib/python3.9/site-packages/torch/serialization.py", line 1784, in load_tensor
wrap_storage=restore_location(storage, location),
File "/env/lib/python3.9/site-packages/torch/serialization.py", line 601, in default_restore_location
result = fn(storage, location)
File "/env/lib/python3.9/site-packages/torch/serialization.py", line 539, in _deserialize
device = _validate_device(location, backend_name)
File "/env/lib/python3.9/site-packages/torch/serialization.py", line 508, in _validate_device
raise RuntimeError(
RuntimeError: Attempting to deserialize object on a CUDA device but torch.cuda.is_available() is False. If you are running on a CPU-only machine, please use torch.load with map_location=torch.device('cpu') to map your storages to the CPU.

Expected results
Image with semantic segmentation is generated

Thanks for picking this @Nagi70 - I have created a branch for this issue called 'sceneseg-cuda-cpu-only', could you please submit a pull request with a fix for this.


Migrate calls to public contract attributes to new vyper format

Issue
Previously to get a public contract attribute, attribute, from a vyper contract you had to prepend get_ to form get_attribute(). In the current version of Vyper, this is no longer the case. get_ is no longer supported and attributes are called with attribute().
Proposed implementation

Update vyper version in requirements.txt and Dockerfile
Update calls to public contract attributes in pytest suite
Update calls to public contract attributes in validator_service.py
Remove get_ previously named public methods to conform to new style. (example: get_deposit_size --> deposit_size
migrate imports from viper to vyper

For example:
index = casper.get_nextValidatorIndex()

will be converted to
index = casper.nextValidatorIndex()

Important note
This will have to be coupled with a corresponding PR to https://github.com/karlfloersch/pyethapp/blob/dev_env/pyethapp/validator_service.py and related code/tests

Closing in favor of #63


Add ability to see/edit which template I used in environments page

Rancher Version: master 11/01
** Comments: **  I should be able to see which template I used when I created an environment.  I should also be able to change the templates.

See yes, edit not supported.  The template is only used once on creation of the environment.

Version - master 11/06
Verified fixed


network, setup: tiny cleanup

What this PR does / why we need it:
Some tiny cleanup:

Drop the redundant interface count check
Use LookupInterfaceByNetwork at podnic
Drop redundant variable

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/sig network
/retest

change: Dedicate a commit to adjust the tests to conform to the 1:1 network/interface rule. Per the review feedback.

/retest

change: Rebase


Doorbell Dummy Switch

It it possible to add a doorbell dummy switch to the camera?
It would be wonderful to expose a doorbell button so we can hook a dummy doorbell url for automatic notifications :) in HomeKit.

I am currently using the homebridge-camera-ffmpeg project to get it working. When someone opens the garden entrance, it triggers a dummy doorbell switch, and I receive a notification with a screen capture from the camera. However, this solution does not provide all the features of the Tapo camera that are available in your project.
It would be great if this functionality could be implemented in your project

I also used the camera-ffmpeg plugin to trigger the camer with rtsp. But, the ffmpeg plugin is very slow to show the live feed comparing to the Tapo plugin. This is why adding a dummy switch would be wonderful if possible 🤗 plus the benefits you mentioned.

Hey folks, I'm not sure I understand. I can definitely add a dummy switch, but can you describe me in more detail your use case?


Cannot init frame, error on viewDocument

canViewDocument returns true for my file, but on opening I get an error.
The message states "cannot init frame", but the error description object within states:
"Object doesn't support property or method 'replace'"
Not sure what to do about this.
OS: Windows 10
Cordova ver: 5.4.1

may be the url you pass in is not a valid string?


Date Time Chooser Widget does not seem to work

I have tried on Windows and Linux to get the DateChooser widget to work.
I can get the dialog box as shown below:

But when I choose a date, nothing gets populated in the field or passed through to the argument.
I don't see any error messages or anything else to indicate things aren't working.
I tried this with my own apps as well as the example.py script.
I am using the Anaconda python distro with Python 2.7.8 and wxPython 3.0
Let me know if there's anything else I can do to help out.

Fixed!
I misunderstood how wxDialogs return their value. Turns out the wx.id_ok had to be on the button itself, rather than returned in the event handler.
You can pull down the fix from the repo or upgrade via pip.
Thanks for the report!

Thanks for the quick response. It is working better but it seems like the value that is being returned is only the day - "Tue" for example.
Shouldn't it be a full timestamp of some sort:

We'll that's peculiar.. Do you see this on Windows and Linux?

Linux at the moment.

Ok. Looks better on Windows - I get a string like "09/05/15"
Same program on Ubuntu returns the day as a string.

Grr. Alright.. I'm spinning up a linux box now. I'll get to the bottom of it. WxPython's shoddy cross platform behavior strikes again!
Thanks for checking for me.

Fixed (on both Windows and Linux this time)!
 On Windows, Dialog.Close returns the ID of the event source, on Linux... it does not. Oy..

Confirming that it works. Thanks for the quick fix!


Make pmd's cache work with build cache

In #2223 , PMD plugin introduced analysis cache, which may cause issue when working with build cache. We need to provide some integration tests in the following scenario:

run the task with some inputs that generates an analysis file
make some changes to the inputs
run the task again, this time get a cache hit and load from cache – this will leave the analysis file in place, even though it’s not relevant for the inputs anymore
make some changes again
run the task again: this time you might have problems because of the irrelevant analysis file

However, for the moment, it seems like the checksum for the cache is based on the hash of just the order and absolute file paths for the PMD classpath so changes to the contents of jars would be ignored: https://github.com/pmd/pmd/blob/master/pmd-core/src/main/java/net/sourceforge/pmd/cache/AbstractAnalysisCache.java#L90, and the maintainer of pmd promised this would be fixed in later release. If not, we'll consider disable the incremental analysis in build cache.

However, for the moment, it seems like the checksum for the cache is based on the hash of just the order and absolute file paths for the PMD classpath so changes to the contents of jars would be ignored: https://github.com/pmd/pmd/blob/master/pmd-core/src/main/java/net/sourceforge/pmd/cache/AbstractAnalysisCache.java#L90, and the maintainer of pmd promised this would be fixed in later release. If not, we'll consider disable the incremental analysis in build cache.

PR submitted for PMD 6.0.0 - https://github.com/pmd/pmd/pull/615 👍

@jsotuyod Could you somehow extend Pmd's API so you could actually use the data from Gradle which files changed since the last execution? Using IncrementalTaskInputs would probably help a lot, maybe even making the use of the Pmd analysis cache superfluous when using Gradle. WDYT?

@wolfs doing so would be too Gradle-specific. We built the feature to support all platforms making use of PMD and intend to support it and extend it as necessary for everyone. PRs are welcomed, but we have no concrete plans on building this ourselves in the short term.
Non the less, as far as I can tell, the current implementation should have no issue with the gradle-build cache, and shall there be any, they would probably still affect other platforms, making them top priority for us.

@jsotuyod What I was referring to was that it could be possible to provide a list of changes to the PMD API (which is currently the Ant task from the Gradle viewpoint), instead of PMD trying to guess the changes. This way the Gradle plugin wouldn't need to use the analysis cache but could rely on the already calculated information for incremental builds instead.

@wolfs I know. But again, doing so would mean moving change detection to the tools, which none other than Gradle do (specially not changes to pmd version, auxclasspath, etc.), hence the gradle-specific part.
Moreover, even if they did, different tools would use different implementations, which would lead to different behaviors. We'd rather provide a single tested implementation where, using PMD-specific knowledge of what is or is not relevant, we can provide the best experience.
For instance, adding a new dependency to my project would produce a change to my auxclasspath. Under Gradle, that means all files are considered out of date. However, that may not be actually true. If no configured rule makes use of DFA / type resolution, changes to the auxclasspath are simply irrelevant.
Also of note, under your suggested implementation, the cache would still be needed, we would simply rely on inputs for invalidation / cache hits; but analysis results would still need to be serialized to the cache. Otherwise we would not be able to generate full-reports, but only report on the changed files (leaving out all non-changed files with violations), which is not the intention of the feature. The report should be exactly the same with incremental analysis, just way faster to compute.

Closed by #3125 . We're reverting pmd's new feature in 4.3RC1 since it seems not mature enough.

Any progress @blindpirate  / @oehme ?

I am trying to configure pmd 6.1.0 with gradle 4.6, and It seems like the ability to set the incremental build cache has been reverted. Is there any way to pass in the -cached argument to the pmd plugin manually to remove the warning as a part of our build?  I saw that there is an internal PmdInvoker.antPmdArgs at https://github.com/gradle/gradle/blob/release/subprojects/code-quality/src/main/groovy/org/gradle/api/plugins/quality/internal/PmdInvoker.groovy#L44
Is there any way to set that manually, until the proper plugin solution gets merged?

In the absence of support for the build cache, PMD 6.2 added a "-no-cache" option that disables this warning (https://github.com/pmd/pmd/pull/954).

In our project we get a few hundreds lines per module with such warning and logs become unreadable. Is there any chances to get this fixed?

Still an issue, not impressed with you guys, sending a --no-cache is a 5-Minute-Fix, seriously... I'll fix it for you guys, if you cannot handle a single argument to fix this issue... sad puppy eyes

what about this?
https://docs.gradle.org/5.6-rc-1/release-notes.html#support-for-pmd-incremental-analysis

So it looks like pmd's cache now works with the build cache. Closing.


Cyrillic symbols support

Hey, I want to add cyrillic symbols support, but I have some questions.

Is it needed?
How should I implement it?

Now I use custom formatCharacters for that and I have two variants.

'Я' - cyrillic and latin symbols,
'Ё' - only cyrillic symbols.

I think it would be nice to add cyrillic symbols to a and A patterns. Thats very easy.
For example, I use this pattern /[А-Яа-яЁёA-Za-z]/. Guys from another cultures can add some additional symbols in it.

hello @cy6eria
you use pattern={/[А-Яа-яЁёA-Za-z]/} ?
(if react)

@yuritoledo hello. Yes, /[А-Яа-яЁёA-Za-z]/ for cyrillic and latin. /[А-Яа-яЁё]/ only for cyrillic.

@cy6eria thank you :)

Greetings.
Could you please advise how to enable Cyrillic in the InputMask component, if the mask attribute accepts the string.
<InputMask
       id="decimalNumber"
       v-model="decimal"
       mask="ЯЯЯЯ.99999-99"
       placeholder="ПППП.ХХХХХ-ХХ"
/>

I need the pattern to be `[A-Ya]{4}.99999-99''.
Stack: Vue 3, PrimeVue.


some logos are too small on Showcase page

Actual Behaviour
https://apisix.apache.org/showcase/

Might want to use the same css as that on the logos on the home page here.  Though some are just too small in size, so might pixelate.

cc @bzp2010 to have a look, thanks

Might want to use the same css as that on the logos on the home page here. Though some are just too small in size, so might pixelate.

But scaling down those small  logos with css makes them blurry? Is there anyway to do this @1502shivam-singh

But upscaling those small logos with css makes them blurry? Is there anyway to do this @1502shivam-singh

AI upscaling maybe, though a drag and might not result in required result. Best we get new logo pngs from the web for respective companies, of appropriate size.

But upscaling those small logos with css makes them blurry? Is there anyway to do this @1502shivam-singh

AI upscaling maybe, though a drag and might not result in required result. Best we get new logo pngs from the web for respective companies, of appropriate size.

Yes


ADD installPlan approval method to opcap

Included InstallPlanApprove method
added call on main operator install function
cleaned up a few duplicate pieces of code by adding variable operatorGroup
cleaned up some comments that are not used anymore

Signed-off-by: acmenezes<EMAIL_ADDRESS>

closes #28

/lgtm


pqiv: use ffmpeg4

Motivation for this change
See migrate away from ffmpeg_3 #120705.
Things done

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

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

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

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pqiv

Result of nixpkgs-review pr 121480 at 52752135 run on x86_64-linux 1

1 package built successfully:

pqiv

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/applications/graphics/pqiv/default.nix:25:5:
   |
25 |     maintainers = [];
   |     ^


Assessment Gateway: Input PY Award consumed and Create related application reassessment on a reassessment

Input PY total of all required awards to Camunda
For all the awards which requires the PY maximum consideration during assessment, we need to send the total award value consumed by the student for that PY to assessment gateway.
Chronology:  Ordering by assessment calculation date (assessment_date) of original assessment.
Logic: Get the sum of assessed value for a given award from all the applications, whose original assessment calculation date is after processing application's original assessment calculation date.
Example:
Assume we are considering CSLP for this example.
Application 1:  Original Assessment Calculation Date: Jan 01
CSLP Awarded/Assessed : 300
Input to Assessment Gateway: variable `PYCLSPConsumed = 0`

Application 2:  Original Assessment Calculation Date: Jan 02
CSLP Awarded/Assessed : 200
Input to Assessment Gateway: variable `PYCLSPConsumed = 300`

Application 3:  Original Assessment Calculation Date: Jan 03
CSLP Awarded/Assessed : 100
Input to Assessment Gateway: variable `PYCLSPConsumed = (300 + 200) = 500`

Identify Impacted applications and create reassessment:
As per #2665, Use the centralized logic during re-assessment to identify all the impacted applications due to this change and create re-assessments.
Additional Context
PT Awards affected:

CSPT
CSGD
CSGP (Across FT/PT)
SBSD (Across FT/PT)
BCAG

Note: While calculating the PY award consumed, awards from declined COE must not be included.
Acceptance Criteria

[ ] Input PY total consumed for all required awards to assessment-gateway
[ ] Call the centralized logic(to be built in  #2665) to create impacted applications from assessment-gateway
[ ] Have basic E2E. Nice to have

@CarlyCotton to put the award types and their source spreadsheet into this ticket and then move to grooming

@Joshua-Lakusta @CarlyCotton while doing the SUM for awards between full-time/part-time CSGD and BCAG will be calculated together?
In the below list (from the ticket description) where it reads (Across FT/PT) would it be applied to CSGD and BCAG also, right?
PT Awards affected:

CSPT
CSGD
CSGP (Across FT/PT)
SBSD (Across FT/PT)
BCAG


Improve documentation for Host Interface returned strings

What
Give more context and better examples of identifier and displayName.

Some notes added in https://github.com/OpenAssetIO/OpenAssetIO/pull/839, but may need more in the interface class docstrings.


WIP: provide a /wopi/iop/open endpoint

To match https://github.com/cs3org/cs3apis/pull/75, I propose to have a new /wopi/iop/open endpoint with the following arguments:
Headers:

Authorization: Bearer and the shared Reva/WOPI secret
TokenHeader: an x-access-token to serve as user identity towards Reva

Query parameters:

enum (int) viewmode: how the user should access the file
string username (optional): user's full display name, typically shown by the Office app
string filename OR fileid: the full path of the filename to be opened, or its fileid
string folderurl: the URL to come back to the containing folder for this file, typically shown by the Office app
string endpoint (optional): the storage endpoint to be used to look up the file or the storage id, in case of multi-instance underlying storage; defaults to 'default'

To be decided: given the foreseen deployment, we may want to drop the whitelist of allowed clients for this call, and just keep the shared secret.

A general comment: most of the code did not really change and was only moved around. Apart addressing the remarks, we need to discuss if we want to drop the allowedclients logic as with Reva the authentication relies on both a shared secret and the TokenHeader, both non-guessable.


🚀 - Resizing the code image

Which @codeimage/* package(s) are relevant/releated to the feature request?
No response
Description
Add a width and height to change the width and height of the final result

Hi @saiidhanna21, what's the use case of this request? Changing the width and the height of the final result may generate inconsistencies between the exported image and the visible canvas

@riccardoperra, there's lot of dead space between the code and the code canvas that can be reduced for better visibility


Validate Database - GeoMaterialDict does Not Meet Standard

While working to convert a database to GeMS, Tracey Felger and I were getting a validation error when using Validate Database on the GeoMaterialsDict. See below:

The GeMS database we used was generated with the Create New Database script, so I would expect the GeoMaterialsDict to be correct.
To troubleshoot the problem, I:

Pulled the latest version of the toolbox
Ran Create New Database
Validated the brand new empty GeMS database

I ended up receiving the same error about definitions missing for the three GeoMaterialDict items. I took a look at the GeMS_lib.gdb, where the table is copied from in the Create New Database script, and noticed that the GeoMaterialDict table is missing those three definitions:

Should the GeMS_lib.gdb/GeoMaterialsDict table have defintions for Other materials, Water or ice, and Unmapped area so that we can prevent this validation error?

Ok, hang on. I need to change the Create Database tool. That tool does make the table from GeMS_lib.gdb, but the Validate Database uses GeoMaterialDict.csv in the Scripts folder. I like saving the table in the more open format so I will work toward removing GeMS_lib.gdb.

Updated in v2.12.4


Add a Gitter chat badge to README.md

saucisson/lua-layeredata now has a Chat Room on Gitter
@saucisson has just created a chat room. You can visit it here: https://gitter.im/saucisson/lua-layeredata.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Done in d5f86cd97ac0089abbbb29591b523d6df82ce876.


Refactor plural endpoints

Our entities can have many children. For example, a collection has a set of entries, and each entry has users, versions, etc. We should not be returning the full child objects, but rather a summary of them (maybe id and name for example). Returning the full objects can get very large very fast, and can cause memory issues on the site, and slowdowns for users.
Take the collection example, if we grab a collection, we shouldn't grab all of the entries. Instead, we should grab an array of entry ids (and maybe something like entry path). We definitely should not be grabbing entry versions or anything like that. If we need those, we would specifically call the endpoint to grab an entry with its versions.
This will require some investigation into how we use our current endpoints in the UI, how we can change them to be more performant (less information returned), and whether we need any new endpoints.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Sprint: Backlog
┆Issue Number: DOCK-1344

Particularly need to avoid this pattern
        Hibernate.initialize(x.getEntries());
        Hibernate.initialize(x.getAliases());

which occurs a few time. Use JPQL to grab just the content that is needed

I bet the one that's chewing up the most memory is source files. Moving those to a new endpoint would probably have the most dramatic impact. But it would also require the most code changes, especially on the UI.

It's also version descriptions


Add course selection dialog to course project action

Description of the PR
This adds a course selection dialog when the user selects "Turn Project Into A+ Course Project". The dialog is only shown if the project isn't already a course project. If the project is a course project already, then the same course will be used again without showing the selection, since it would be undesirable to turn the same project into a course project of a different course.
Testing

unit
integration
manual

- [x] new unit tests created
- [x] all unit tests pass

- [ ] new integration tests created
- [x] all integration tests pass

- [x] manual testing went well

Have you updated the TESTING.md or other relevant documentation?

[ ] Yes
[ ] Not yet. I will do it next.
[x] Not relevant

should the course selection be based on branch multicourse-support-base, where we could first aggregate all the changes and then merge to test? @nikke234

should the course selection be based on branch multicourse-support-base, where we could first aggregate all the changes and then merge to test? @nikke234

should the course selection be based on branch multicourse-support-base, where we could first aggregate all the changes and then merge to test? @nikke234

Ah, I forgot about that one and merged language selection already to test. However, there isn't an automatic release from test anymore so it shouldn't cause issues

should the course selection be based on branch multicourse-support-base, where we could first aggregate all the changes and then merge to test? @nikke234

Ah, I forgot about that one and merged language selection already to test. However, there isn't an automatic release from test anymore so it shouldn't cause issues

please update TESTING.md

please update TESTING.md


Feature/space savings2

Shrink Static RAM from 19k to 12k
Shrink Flash from 360k to 120k

Basic idea is to remove all std::strings and iostream garbage from the codebase and replace it with utensor::string and c style string processing. utensor::string maintains a stable hash of const char* using the java string hash.

bump @Knight-X

@Knight-X @neil-tan Should i update this PR?

We can always maintain it during the debug profile and remove strings on release. Or only use c strings

@neil-tan  What is expected time of this release version ? Do we have enough time to do interface refactor and binary tensor ?

Since we will have to update many operators at the same time, aiming for the release after CNN is more realistic.
However, one nice thing about releasing it with CNN is that, we can get rid of the SD card and don’t have to update the readme twice.

@neil-tan @Knight-X I rebased this PR onto the latest develop and ran CI. The savings numbers are probably out of date. Can one of you guys get the new number for me?

Before string replace:

After

Note the bulk of the size is attributed to deep mlp constants now being in ROM.
The key size difference is lib stdc++ dropping from 172027 Bytes to 6662 Bytes.

this is awesome

That is great.
However, @neil-tan mentioned that we can just use Macro to replace the string, and it probably saves more space than using char.
ex.
#define TENSOR_1 1
#define TENSOR_2 2
How do you think about the strategy?

Macro strings will save a lot of space by removing the c strings all together, but this is know different than just maintaining a single int in the utensor::string. The other downside is we can no longer support sd tensors or really any tensors on the file system as these require string lookups

@neil-tan @Knight-X ?

@mbartling  good work


Proposal: inactivity_ms does not perform as expected/documented, let's fix that.

According to the documentation, when providing a value for inactivity_ms, "If no changes happen by the timeout, Follow will signal an error." But it actually calls on_inactivity, which restarts the feed (see https://github.com/iriscouch/follow/blob/master/lib/feed.js#L624-L637).
In some cases it is not desirable to automatically retry the feed. In my case, for example, I have a large number of databases which I want to stop following once they have been inactive for a while.
Furthemore, the documented behaviour (emiting an error) seems somewhat confusing: the fact that there haven't been changes on a database should not be an error.
Instead, I would propose the following:

Emit a 'timeout' signal when the timeout expires.
Add a setting retry_after_timeout (default true), which determines whether the feed should be retried after a timeout.

This would allow users to indicate what they want Follow to do when there is a timeout, without breaking backwards compatibility.
If you are okay with this proposal, I'll implement it and send a PR.

@grimborg thanks for bringing this up. I made this change a while ago when I felt the erroring could be a bit too aggressive since its not a fatal case. The changes you suggested seem reasonable, I would just make it an inactive event rather than a timeout event. There is already a timeout event that has different semantics currently.

Thanks for the feedback! I'll emit an inactive event as you propose.


Set up secrets management

SOPS-based secret management set up, secrets now live in /infrastructure/secrets


Transparency principle x 2 ?

Is it normal that the Transparency principle appears twice ?
See:
https://github.com/healthonnet/HON-Health-Trust-Indicator/blob/9ce39df0c437f8731d07fc8eef3ef5d27558e192/app/scripts/popup.js#L5-L7
From https://github.com/healthonnet/Kconnect-search/pull/135

Wow how didn't we see it ?!
Thank you !


The Plugin does not show the correct content for text and html format attachments.

Hi Team,
The Plugin does not show the correct content for text and html format attachments in AfterHooks section.
The attachments are added using below code.
HTML Attachment:-
	StringBuilder stringBuilder = new StringBuilder("

Field Name	Field Value

Field Name One	Field Value One

Field Name Two	Field Value Two
");
	stringBuilder.append("

");
	scenario.embed(stringBuilder.toString().getBytes(),"text/html");

Text Attachment:-
	scenario.embed(FileUtils.readFileToByteArray(new File("target/Log/Scenario_Execution_"+scenario.getId()+".log")), "text/plain");

To Reproduce
Steps to reproduce the behavior:

Try to generate the report for attached "cucumber.json" file.
Check Scenario Details in generated reports (see attachments section)

Expected behavior
Actual content of the attachments should be displayed as per given formats.
Actual behavior

Embedding content is displayed as it is.
screenshots are displayed properly.

Attachments
PFA Sample json and Reports
JSON and Reports.zip
Additional context
Add any other context about the problem here.

Hi Benjamin,
First of all, Thanks for such a great reporting plugin for cucumber reporting. I have recently started using this. I really appreciate the work done.
I would also like to contribute for improving the same. This will be my first contribution to open source community.
I have already started working on this issue.
I will be creating pull request for the same once I finish the fix.
Kindly help me with the guidelines and practices on Github if anything goes wrong from my side.
Thanks,
Rameshwar Shiral

Greetings, Jenkins HTML report is not displaying the charts and animations from Jenkins. However, opening the same HTML file locally works perfectly. I have seen some old posts but if anyone can direct me to the solution would be great. thank you.

Hi! I'm looking forward to your pull request.

Hello,
Please open a separate issue as your comment was unrelated to the thread.
Thanks!
From: tobiswajitdas<EMAIL_ADDRESS>Reply-To: trivago/cluecumber-report-plugin<EMAIL_ADDRESS>Date: Monday, 22. October 2018 at 06:09
To: trivago/cluecumber-report-plugin<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [trivago/cluecumber-report-plugin] The Plugin does not show the correct content for text and html format attachments. (#97)
Greetings, Jenkins HTML report is not displaying the charts and animations from Jenkins. However, opening the same HTML file locally works perfectly. I have seen some old posts but if anyone can direct me to the solution would be great. thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Benjamin,
The bug is fixed with Pull request https://github.com/trivago/cluecumber-report-plugin/pull/99.
Please review the same.

Hi,
I am working on it. will commit required changes today.
Thanks,
Rameshwar


[Website Main page]  Suggestions with MP 5.0 Release and Onwards

@TetianaFTV & @rstjames,
Brainstorming via this ticket and including you two as the ones to update the website on anything Releases.

Issues

The card lost the mention and link to the past release. Can we bring it back ?

Suggested Additions:

Thanks to @emecas, the MP 5.0 Spanish presentation is almost ready for import to the website. We ought to add it here.  once is ready. StandBy. Emerson, please pull via the other ticket the action. :)
The blog (english and Spanish) could be added here too. Double the sharing seems smart and allows for lazy browsing where the card provides everything on MP 5.0. What do you think Ryan and Tetiana? Spanish version will be published as soon as the presentation is completed and will be pushed via media, the same amounts as the english versions up until end of Feb 2022 when next release is planned.

Thanks for brainstorming with me on this. 👍

The card lost the mention and link to the past release. Can we bring it back ?

added

Thanks to @emecas, the MP 5.0 Spanish presentation is almost ready for import to the website. We ought to add it here. once is ready. StandBy. Emerson, please pull via the other ticket the action. :)

the link to folder with both English and Spanish version of presentation and blog article is already placed at the website here https://microprofile.io/resources/#presentation
at home page (same as previous time) we have a direct link to English presentation only,
so basically we don't need to make any changes at the site when Spanish content is ready, just spread it via social media

Tetiana,
Thank you for promptly adding 4.1 :)
The remainder of the Resources tab under presentation was needed. thank you, completely forgot that we have chosen to spread the releases across the website.
I think with the new Implementation page that deals directly with compatibility this will be fixed. :)
What about the announcement blog under the card on main pain?  Valuable?

What about the announcement blog under the card on main pain? Valuable?

not sure I understand what you mean by this

@TetianaFTV,
please disregard. Via this  https://github.com/eclipse/microprofile/issues/239#issuecomment-993944867
we have updated:

landing MP. 5 description to include the announcement blog link.
release guidelines steps wiki
release gudiliens git issue check list.

I think it is enough :)
Thank you for the follow up. I will close ticket.


"Automation science alt 1" not found at startup, Clown's Science and Angel's Refining need to be disabled

Thanks for the report, i am surprised it took someone that long to find it, i was missing a sanity check wrapper around that new function... ill get that fixed in a few mins, just checking the other issues first.


visualize qemu vm statistics in real-time

Description
We (w/@dentrax) thought it'd be good to create a sub-command like stats which would display the VM statistics in real-time as the docker's stats command.
# can take a VM name as an argument or will list all the VM stats if no VM name is given
$ limactl stats <VM>
NAME     CPUS    MEMORY    DISK
vbox     %13     %27       %31

Similar to:

#835


Explain how to tell dockershim apart from cri-dockerd

This is a Feature Request

What would you like to be added
Update https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use/ to explain how to tell apart two cases that involve Docker Engine as a container runtime

Docker Engine + dockershim + kubelet
Docker Engine + cri-dockerd + kubelet

The second case, using 2 third-party components, is not affected by the dockership deprecation. As a project we are not telling cri-dockerd users to migrate away.
Why is this needed
If someone is using cri-dockerd with Docker Engine, they don't need to take action relating to the deprecation of dockershim. That person might visit https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use/  and then be confused about whether they still need to take action.
Comments
/sig node
/priority important-soon
/language en
/kind feature
Part of https://github.com/kubernetes/kubernetes/issues/104878

Very relevant to #30972

It really should say # For docker, rather than # For dockershim
It doesn't say "for cri-containerd" or "for containerd with cri plugin", either.

Neither kubectl nor crictl seem to have a way to tell the CRI in use ?
They only describe the container runtime, and in some cases the API version...

Looks like crictl is only documented under "debugging", even if now required ?
https://kubernetes.io/docs/tasks/debug-application-cluster/crictl/

/triage accepted

If someone is using cri-dockerd with Docker Engine, they don't need to take action relating to the deprecation of dockershim.

I think it would be more interesting to look at users using the "docker" container runtime, to see if they have changed CRI.
They would need to change their CRI, from dockershim.sock to cri-dockerd.sock. Including kubelet and crictl configuration ?
But they don't need to relearn everything or transfer images, etc.

https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use/
This should say "docker" (which the command does), and not # For dockershim (not really relevant)

it should be divided into two:

how to change dockershim to cri-dockerd
how to change docker to containerd

That seems fair enough. We can also add instructions for switching your node from Docker Engine to something else, if we want.

where feasible we prefer to link to external docs that are specific to external tools, rather than document them ourselves.
This case seems like a reasonable case for doing the documenting ourselves.

Unfortunately it also assumes that there are any good external docs, which doesn't seem to be the case for either CRI.

Visual summary:

The top diagram would be when running Kubernetes 1.23, and the bottom diagram would be when running Kubernetes 1.24
The docker installation (docker.service) stays the same, the only introduction is the new cri-dockerd (cri-docker.service)

@afbjorklund @sftim
From what I understand, Find out what container runtime is used on a node needs to add info about how cri-dockerd users aren't affected, and how to check the CRI socket to tell if you do use cri-dockerd. (how? if crictl is not installed, is there another way?)
Also, https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/ needs more guidance for migrating from dockershim to cri-dockerd (in addition to migrating from Docker Engine to containerd). Is this out of scope for this issue?
/assign

more guidance for migrating from dockershim to cri-dockerd … is this out of scope for this issue?

I'd say yes: it is out of scope for this issue. It's fine to track a separate issue to add docs for that.

if crictl is not installed, is there another way?

I believe that crictl is mandatory, without dockershim

There is a Version request. If you talk CRI to some unidentified CRI socket and the thing at the other end identifies itself as Docker Engine, odds on you're talking to cri-dockerd or dockershim.
You can narrow it down by running lsof /path/to/unknown/socket. That's likely to give you either the PID and name of the daemon involved, or possibly point to a socket-activation tool such as systemd. If it is systemd owning the socket, you'd grep through systemd config to find what's configured to listen on that socket.

@sftim Is this essentially an umbrella issue for #32131 and #31132 now?

It's all done!


Public contrast_limits_range setter, and climSlider popup on right click

Description
Small PR here to make it easier for people to change the range of the contrast limits slider by setting layer.contrast_limits_range.  This came up one at image.sc.  I am also preparing a PR for complex images, and there it becomes important to be able to reset the range as the data range can change dramatically...
This also includes a helper function (utils.validators.validate_N_seq) that could be used anywhere we need to make sure that incoming data is a sequence with a certain length and (optionally) datatype.
Will add tests if the general idea is ok with everyone.  This will need to merge before the complex images PR (#838).
Type of change

[x] New-Feature (non-breaking change which adds functionality)

How has this been tested?

[x] added tests for some qt_image_base_layer behavior
[x] all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

This looks great @tlambert03 - I am in favor, and I think with tests it will then be good to go
I'm also linking #624 and #570 here too - they are more about editing the contrast limits, but maybe now we can add two QLineEdits that can be used to set the contrast limits (and if values are outside the current range then the range will expand too). All this can wait for other PRs, but I just want us to be tracking it too.

maybe we could add that right-click context menu to let users manually edit it?  (like the play button menu)

context-menu could work though discoverability might be hard if there wasn't a dedicated icon for it. I do like the way the numbers are shown on the right of the dims sliders right now, with the slice being editable. There was also maybe the request that right clicking causes the slider to expand and we could then add editable numbers to be only in the expanded slider.

I'm into the right-click idea — the real estate up there is precious!
Anyway, I'm 👍 on this change!

it would be pretty straightforward to add a right-click to bring up an expanded range slider (for more real-estate) along with LineEdits for changing the limits... so I'll work on adding that here.  I was also playing around with QTapAndHoldGesture, that accomplishes the long-press behavior that @jni, once mentioned.  I think it feels a bit out-of-place in a mouse-based environment though (touchpad maybe, touchscreen definitely)... but I do think we should remember the gestures framework for things like sidecar!

the right-click to expand the clim slider is working now.  Here's a gif... stylistic or other suggestions welcome:

Love this @tlambert03 - I like the color of the expanded slider more than the color of the slider in the docked control panel - we might want to change those colors over to be the same, but that is a dedicated styling PR.
I've noticed slightly strange things happen if I type in a clim_range upper value that is smaller than the clim lower value, it doesn't clamp properly until after you make one adjustment of the slider - i.e. say I have [0, 20, 40, 100] reading left to right. If I type in 10 for the 100, then I get [0, 20, 10, 10] which is obviously strange. Then if I adjust the slider it clamps everything to [0, 20, 20, 20]. I'd probably say that when finishing typing it should clamp to [0, 10, 10, 10]
Once this is in, I think it makes an interesting idea for #675 and the histogram widget - should that appear above the elongated slider? Or is that really its own thing in a dock window? Will that supersede this / be combined with it? Having a right-click on the clim slider be the way to access the histogram makes sense to me too. Curious what your thoughts are on this.

Thanks for catching that @sofroniewn.  Fixed the clamping behavior, added some tests, and hopefully wired up all the necessary connections correctly.  I also added a couple "reset" and "full range" buttons, along with some helper functions on the image layer to introspect data.  If you have another chance to bang on it a little bit, that'd be great.  Looks like I have some tests related to the surface layer that I need to fix in the meantime but will ping again when ready for review.

Once this is in, I think it makes an interesting idea for #675 and the histogram widget - should that appear above the elongated slider? Or is that really its own thing in a dock window? Will that supersede this / be combined with it? Having a right-click on the clim slider be the way to access the histogram makes sense to me too. Curious what your thoughts are on this.

yeah, I'm not sure.  There's obviously some similar functionality, but don't see them as totally overlapping.  I see this as a way to refine the behavior of an otherwise cramped slider, and expose the ability to change the range of the slider easily.  The histogram is a full-blown data evaluation tool and I sort of see it as its own dock widget (I think it takes up too much real estate for a popup)...  though perhaps a small button in the popup (or next to the clim slider) could show the histogram widget.

This is ready for review, but has expanded a fair amount in scope.  I don't think that anything here should be difficult to merge with other open PRs, (but sorry if so).  Here is the updated list of what is happening in this PR:

Surface/Image.contrast_limits_range is now a public method, setting the range on the model will update all view sliders accordingly.

I extracted duplicated code between the Surface and Image layers into layers.mixins.ImageSurfaceMixin that controls gamma, clims, and colormap logic.

Added a validator for "sequences of length n" that might be handy elsewhere in napari.utils.validators

Created a new modal window (_qt.qt_range_slider_popup) that has a range slider and linked   LineEdits for range min/max and current min/max.

Made a QRangeSliderPopup appear when right clicking contrastLimitsSlider.  It additionally includes a "reset" button (returns it to the calc_data_range choices) and "full range" button (only appears on np.unsignedinteger types and will show full bit range).

a couple more tweaks to QRangeSliders carried over from #842

added docs and tests that should nearly completely cover all new features as well as some existing features like QtBaseImageControls

@tlambert03 I'm having some problems typing negative numbers and decimals into the clim range text edits, both if the actual image data is int or float. In general I think we should be a flexible as possible there.
The clamping is now working great, thanks. I will continue to review

Thanks for catching that @sofroniewn.  I made all these changes, fixed the validator, and added a little smart width adjustment so labels don't get hidden on (slightly) bigger numbers.
Stylistic question:  it occured to me that the meaning of the LineEdits might be hard to glean without labels, but I don't really want to add a lot of words like "range min", "current value", etc...
I could add those labels if you think... or i could do something like this mockup, where the current value is always above the handle (at the expense of a little vertical room):

thoughts?  @jni?

The hover is nice, curious what others think. We should have tool tips too - they might be enough. Not sure if we have them right now

Looking at it one more time I think labels on top is nice and clear, my vote is to go for that, with tool tips too
What does @kevinyamauchi think?

Also would be nice to add similar pop up / edit labels / range control for our single sliders too - in which case having one number above the slider is the natural generalization
This would be particularly useful for things like the point size slider where the upper end of the slider range was picked pretty arbitrarily
For things like opacity it’s still nice to expand so you can type in a direct value, but there maybe we shouldn’t allow the range ends to be editable as 0, 1 is the natural choice
Maybe for point size only the upper range is editable as 0 is the natural minimum, or maybe it’s more appropriate to think of absolute bounds that you can’t edit beyond
Anyway, all of that would be for follow up PRs, but putting down here as it might influence our thinking about the design of the range slider pop up

I have a slight preference for labels-above-handles as well.  So I'll see what it takes to implement...

How do you feel about labels below vs above? I seem to recall photoshop does something similar for some sliders but under with little triangles connecting like ^
Probably don’t need the ^ but under might be more conventional

I think the labels ended up looking better on top.  I implemented it, you can try it out if you'd like, here's the gif:

This looks stunning @tlambert03! 😍! I'll try to have a look at the code a bit later today, but do merge if anything is being held back — things can always be fixed in later PRs.

Thanks for the thorough review @jni!  So useful... sorry it turned into such a big one.
Caught a couple outdated exceptions for me.  I made all the changes, renamed the mixin, enabled the full range button on all integer types (not just unsigned), and broke up the tests.
Will wait for tests to pass and then merge

the right-click to expand the clim slider is working now. Here's a gif... stylistic or other suggestions welcome:

Hi! thanks for making this gif.  I tried to follow this yet in my case nothing happened when I right click on the slider.
the small slider itself works fine, but I don't have this popup.
my environment is:
napari: 0.2.11
Platform: Windows-10-10.0.17134-SP0
Python: 3.7.4 (default, Aug 9 2019, 18:34:13) [MSC v.1915 64 bit (AMD64)]
Qt: 5.9.6
PyQt5: 5.9.2
VisPy: 0.6.4
NumPy: 1.16.5
SciPy: 1.3.1
scikit-image: 0.15.0
Dask: 2.5.2
GL version: 4.0.0 - Build <IP_ADDRESS>25
MAX_TEXTURE_SIZE: 16384

Thanks for reporting this @fenixnano can you try updating to napari 0.2.12, though I think this should have still worked with 0.2.11, and then updating your Qt / PyQt5 too. I'm now on 5.14.1. I suspect that is the source of the problem. Maybe @tlambert03 knows if this behavior is expected or not with 5.9.x

I actually had some issues with this as well. For me with a dual screen set up the pop up showed up on the other screen (and I didn't notice). I meant to create an issue but too scatter-brained at the moment.

I can confirm that the slider popup as currently implemented will not work on Qt < 5.10.  Technically, we don't support Qt < 5.12.3, but it probably shouldn't be too hard to make this one work for older Qt installations.  I'm going to create a separate issue for this


make vouch protocol configurable

should also add the vouch protocol to the rfcs repo, btw.

when Amundsen runs on testnets, where people want to easily run tutorials, it's desirable to disable its vouch check (as is the case currently in the code). When running on real main nets, that would be very unwise, so removing the code for it would effectively create a vulnerability in the software; it's therefore desirable to leave the vouch protocol code present, but to disable it through configuration


Request: make it so that nav-pills can be have different colors

Thanks for this awesome project.
What about adding css classes to give .nav-pills different colors?
For example something like:

.nav-pill-default
.nav-pill-primary
.nav-pill-danger
etc ...

I could use this too - at least nav-pill primary

We won't be adding it, sorry.

For anyone stumbling upon this, one may use the bg- classes to get the desired result. Ie bg-primary, bg-warning, etc.


CDAP-15775 allow writing to an empty BQ table using sink

BigQuery tables can be created without any schema. When data is
loaded, the schema is set. Fixed the sink to allow writing to
these types of tables instead of failing during validation.

cherry-pick of #205


WIP: RFC: Wasmtime 1.0

Rendered

For now the definition of what a bug is for being backported is also intentionally vague. It's expected that fixes such as performance improvements won't be backported, but panicking on valid input for example would be backported. It's intended that this concept of what is backported is refined over time.

I definitely understand the intention of leaving an "escape hatch" here so that we have room for judgment calls, but I wonder if it would make sense to give a slightly more precise statement of what guarantees an ESR user could expect. Concretely, skipping perf improvement backports makes total sense, but should we be more explicit about execution correctness bugs?
It seems to me that making a stronger statement about "ESR releases will always, to the best of our ability, conform to the Wasm spec's semantics" (for on-by-default features) has a lot of value -- Wasm gets a lot of mileage out of having a very careful and precise spec, and if it's not an undue burden, promising to provide that careful and precise foundation to the end-user is similarly valuable. The escape hatch adds a lot of uncertainty, IMHO.
The thing to figure out is whether the burden is really manageable or not. IMHO our core Wasm implementation is stable enough now that I'd be comfortable promising to backport any correctness fix; but it does have implications for how much we let a new feature bake before turning it on by default. Thoughts?

Nah that sounds like a good threshold to me and is what I was trying to get at which is that we won't backport everything but we will backport "important things". I think the spec behavior is clear enough that it's likely sufficient.


Adolescent Insomnia Study- AutoViz

Is your feature request related to a problem? Please describe.
Adolescent Insomnia Insights: Sleep Habits & Psychosocial Impact
Describe the solution you'd like
The project uses:
numpy
pandas
matplotlib
seaborn
AutoViz_Class
autoviz.AutoViz_Class
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This project is inspired by https://www.kaggle.com/code/utkarshx27/adolescent-insomnia-study-autoviz

Assign me


feat: using enumeration for event hooks instead of strings

Newcomers to the project may find it hard to figure out the processing cycle because there's no central listing of possible event hooks. This PR addresses that:

Add an Event enum to ivy/events.py listing known event hooks.
Add an EVENT_NAMES dict to support string-to-enum translations for backward compatibility.
Register all internal events using enum elements.
Alter all internal event registrations and firings to use enums.

If this PR is useful, I'd be happy to add similar enumerations elsewhere, and to try to add documentation on the enum classes to try to explain the purpose/lifecycle of each element.
This PR also adds a .gitignore file to ignore build artifacts.

That's a very clever implementation. I like how you've maintained backwards compatibility with string hook names.
I'm going to take a proper look at the weekend when I have more time but I like it.

:+1: I'd be happy to hop on a call next week to try to debug the "empty node" problem I'm seeing (and to figure out if there's a way to implement a couple of my extensions that doesn't involve double-processing files).


no user error

2016-09-05 08:34:18 [INFO] Config created: /app/config.js
2016-09-05 08:34:19 [WARN] No users found!
2016-09-05 08:34:19 [INFO] Create a new user with 'lounge add <name>'.
2016-09-05 08:34:52 [INFO] Config created: /app/config.js
2016-09-05 08:34:53 [WARN] No users found!
2016-09-05 08:34:53 [INFO] Create a new user with 'lounge add <name>'.
2016-09-05 08:35:26 [INFO] Config created: /app/config.js
2016-09-05 08:35:27 [WARN] No users found!
2016-09-05 08:35:27 [INFO] Create a new user with 'lounge add <name>'.
2016-09-05 08:36:00 [INFO] Config created: /app/config.js
2016-09-05 08:36:01 [WARN] No users found!
2016-09-05 08:36:01 [INFO] Create a new user with 'lounge add <name>'.
2016-09-05 08:36:35 [INFO] Config created: /app/config.js
2016-09-05 08:36:36 [WARN] No users found!
2016-09-05 08:36:36 [INFO] Create a new user with 'lounge add <name>'

I installed it according to Heroku guide.
 If start the server with --home, you need to create users with that too.

I don't remember how I fixed it but it works now.


Only show transfer stats when transferring files

Only commands which actually transfer files need to show the transfer stats, eg sync, copy.  Commands like ls, md5sum shouldn't.
Some thought as to exactly which commands should and shouldn't show transfer stats.  Eg delete.

Fixed in 2cbdb95ce5840ba17ba46538ab0168ed9030e3fd


C# patterns reference: relational patterns and pattern combinators

Contributes to #20584

@BillWagner thank you for review and suggestions. I think I've addressed all the feedback.

Thanks @pkulikov
I'll :shipit:


Crash at startup

Unspecified error (Exception from HRESULT: 0x80004005)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at CharacterMap.Services.UserCollectionsService.<CreateCollectionAsync>d__13.MoveNext() + 0x1ff
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at CharacterMap.Services.UserCollectionsService.<>c__DisplayClass10_0.<<LoadCollectionsAsync>b__0>d.MoveNext() + 0x715
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at CharacterMap.Services.UserCollectionsService.<LoadCollectionsAsync>d__10.MoveNext() + 0x166
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at CharacterMap.ViewModels.MainViewModel.<LoadAsync>d__68.MoveNext() + 0x103

OS Version: 10.0.18363.778
OS Architecture: X64
App Version: 2<IP_ADDRESS>
App Culture: en-US

@Arreba thanks for posting the details. Is this your first ever run of the app, or has it only started occurring after some time?

(For posterities sake, I've tested this on 1809 & 1903, on both clean installs and updates and can't reproduce yet. The code path doesn't suggest any reason for this to fail.)

Still having the same issue after several reinstallation.

#151


SyntaxError: Use of const in strict mode.

MacBook Pro (Retina, 13-inch, Late 2013)

You need NodeJS >= v4.
Nice work @vdemedes

Agreed, I solved this by upgrading from 0.12.x to 4.x.

I'll leave this as a request to make it compatible with older Node.js (v0.10, 0.12). Thanks for reporting!

@vdemedes Seems no more ES2015 features besides const/let. So it is okay to use var only.

Done and released on npm, thanks!


Add Vulkan QML backend

🎉 New feature
Order in which PRs must be merged

gazebosim/gz-rendering#706
gazebosim/gz-gui#357

or optionally, merge this one as part of the next one aka PR 467, which includes it

This PR.
gazebosim/gz-sim#1735

Summary

Note: This PR depends on gazebosim/gz-rendering#706

Note: This PR is polluted with changes that are supposed to be merged by PR #357

This PR adds native Vulkan backend using Qt's QML Vulkan RHI.
I couldn't believe it so I opened it up on RenderDoc and indeed it's using Vulkan:

This PR breaks ABI slightly, so it's best if it targets post-Garden.
With a few global variables we could workaround it and backport it to Garden though. Note that Garden supports Vulkan via a fallback that is very slow. This PR offers native, full speed integration.

Note: Qt 5.14 is the minimum requirement, which means it's not available on Ubuntu 20.04 but rather Ubuntu 22.04. I put macros to use at least 5.15.2 because that's what I tested against.

Note: Qt 5 considers Vulkan QML interface to be 'experimental' and I've submitted a patch to Qt to improve compliance with the Vulkan standard. Ideally Gazebo should eventually migrate to Qt 6.

Missing tasks:

[x] Ensure code compiles without Qt 5.15.2+
[x] Ensure code compiles when Vulkan isn't available
[x] Gazebo needs to tell OgreNext to make a layout transition / synchronization for Qt (via BarrierSolver).
[x] Run Vulkan validations to catch any potential issue

Done. Only validation errors show up on shutdown, but that's difficult to debug right now because gz-gui crashes on shutdown due to infamous crash at shutdown (can't find the ticket now) that could be the cause. May also be a side effect of #17

[ ] Add vulkan toggle via command line

Test it
This PR can be tested once gazebosim/gz-sim#1735 (which comes after this PR) is merged, which adds the capability to enable the features in this PR via CLI.
Testing it in Ubuntu 20.04
It is possible to build with Ubuntu 20.04 against Qt 5.15.2. You need the following:

Install Qt 5.15.2 using the online installer
Compile Gazebo with: colcon build --cmake-args -DCMAKE_PREFIX_PATH=/opt/Qt/5.15.2/gcc_64 -DQT_QMAKE_EXECUTABLE=/opt/Qt/5.15.2/gcc_64/bin/qmake --merge-install
To run gazebo go to the install folder and do:

export LD_LIBRARY_PATH=/opt/Qt/5.15.2/gcc_64/lib
. setup.bash
gz sim shapes.sdf

Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

This PR breaks ABI slightly, so it's best if it targets post-Garden.

I think there is no ABI breakage? Adding a new function to Helpers.hh should be ok. The minimal scene plugin headers are not installed.

we need to bump gz-rendering dep version to 8.0.0 and update CI configurations. I'll do that in a separate PRs after all changes are forward ported to main.

we need to bump gz-rendering dep version to 8.0.0 and update CI configurations. I'll do that in a separate PRs after all changes are forward ported to main.

I thought this could land in garden?

I thought this could land in garden?

https://github.com/gazebosim/gz-rendering/pull/706 may have some ABI breaking changes. We could try to work around it.

Originally yes. With a few hacks I think/thought it could still land on Garden.
However my original assessment was assuming #357 was already merged (I was surprised when I found out it was not), and AFAIK Garden will be released without it.
I'm not sure if we can avoid ABI breakage given that #357 wasn't included. I'd have to carefully look into it if we want to backport at least the fallback path.

I think https://github.com/gazebosim/gz-gui/pull/357 can go in gz-gui6 and it touches only files in the minimal scene GUI plugin. Those headers are not installed so we don't have to worry about API/ABI compatibility.

coming back to this, I think https://github.com/gazebosim/gz-rendering/pull/706 is going to be hard to backport to garden. @mjcarroll are you ok with these PRs landing in main?

Yes, lets land them on main for expedience.

needs version bumps

@azeey I'm trying to rebase this PR to main; but current main has a gazillion build errors.
gz-gui/main branch clearly needs to merge with gz-gui/gz-gui7 branch.
gz-sim/main is in the same state (merging has quite a number of merge conflicts).
gz-launch/main is in the same state.
On top of those build errors, they're also looking for the wrong project versions (e.g they look for gz-rendering7 instead of gz-rendering8).
Basically building Harmonic via collection-harmonic.yaml doesn't yet work out of the box.
Should I wait until Harmonic is buildable?

Should I wait until Harmonic is buildable?
Yes, there are a couple of PRs in flight bumping the major versions of gz-rendering and its dependees. These are tracked in https://github.com/gazebo-tooling/release-tools/issues/853. Let's wait till all of those are merged.

after https://github.com/gazebosim/gz-gui/pull/512 gets in, everything up to gz-gui should be buildable

Another rebased and retargeted.

I need to rebase this PR now that the previous one has been merged.

Are the tests flaky? Jammy always fails on these two:

   51 - INTEGRATION_minimal_scene (Timeout)

53 - INTEGRATION_transport_scene_manager (SEGFAULT)

And Focal always succeeded except this last time (I made no significant changes that would cause this, possibly flaky):

45 - INTEGRATION_camera_tracking (SEGFAULT)

As for Windows CI, I fixed the problems caused by my PR; the new warnings don't look like caused by me (?)
And macOS was failing build, I fixed that. Now it fails various tests. I don't know if those are my fault.

51 - INTEGRATION_minimal_scene (Timeout)
53 - INTEGRATION_transport_scene_manager (SEGFAULT)
45 - INTEGRATION_camera_tracking (SEGFAULT)

I've seen these tests fail from time to time. I think they are flaky.

And macOS was failing build, I fixed that. Now it fails various tests. I don't know if those are my fault.

I haven't seen those tests failed before. Not sure why. I restarted a new homebrew build and now it only has one expected test failure: https://build.osrfoundation.org/job/ignition_gui-ci-pr_any-homebrew-amd64/1893/. Will need to keep an eye on this.


Update normalized cache with results from a mutation

Looking at the apollo android documentation I don't see a reference to it supporting this functionality: https://www.apollographql.com/docs/android/essentials/mutations/

Sorry not sure I understand what functionality is not supported? Mutation operations do update normalized cache.

I thought I'd read on the apollo site that it isn't supported on android, but I can't seem to find that on the site anymore. It was just an issue on my end and it's working now. Sorry about the noise.