enhancement request: On Asset Details page, add ‘Asset Type’ and move ‘Source’ to far right.

Is there an existing issue for this?

[X] I have searched the existing issues

Enhancement description
On Asset Details page, add ‘Asset Type’ and move ‘Source’ to far right.

🧑💻 Implementation
No response
Anything else?
Use in the commit msg -> MVP2023-484

@astra1 Please look into this request.


Issue #16 - Improve the footer of the website

Description:
Design and develop a good looking footer page and align it properly at the bottom of the page.
Tasks:

[ ] Design and improve footer page with proper styling.
[ ] Ensure responsive design

Technical Requirements:

React components

Hi @divyesh-mali, can I please be assigned to this issue? As well, do you have anything in mind to implement for design, or am I free to create and update you with design choice?

@cduarte3 Thank you for taking up this issue. There are no hard and fast rules for designing. Just make sure it matches with the color theme of website and is responsive to mobile device as well.

@cduarte3 Hey, any update on this issue?

@Siddheshuncodes
Yes, I have drafted up a design and am currently working on implementation.
My mockup is as below:

The design looks great! Looking forward to your PR. 👍

PR opened at https://github.com/Swifty9/Maverick-AI/pull/96

Thanks for your contribution you did great work.
We will be sharing contributors of Maverick AI on our social media platforms can you please share your details regarding LinkedIn and X(Twitter)?

No problem, was happy to contribute to the project !
LinkedIn:
www.linkedin.com/in/christian-duarte-97593329b
Twitter (Not as Active):
https://x.com/c_duarte718?s=21
Dev.to Blog:
https://dev.to/cduarte3

Thanks for sharing we will mention you in the post for next week.


[Blueprint] Use experimental tag, update doc

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/fengzhou-msft/azure-cli-extensions.git@update_blueprint#subdirectory=src/$EXT&egg=$EXT"


typescript How to  importing components on demand?

--------------^ Click "Preview" for a nicer view!
We primarily use GitHub as an issue tracker; for usage and support questions, please check out these resources below. Thanks!

Read the documentation: https://material-ui.com/.
Ask questions on StackOverflow using the tag material-ui: https://stackoverflow.com/questions/tagged/material-ui.
Chat with the community on Gitter: https://gitter.im/mui-org/material-ui.
Ping us on Twitter: https://twitter.com/MaterialUI.

ant design use typescript use ts-import-plugin ! and material ui?
I try to use the babel-plugin-import, but didn't succeed

just now! I have solved the problem.Let me share
install ts-import-plugin and react-app-rewired
write a config-overrides.js in the root,
///////////////////////////////////////////
const tsImportPluginFactory = require("ts-import-plugin");
const { getLoader } = require("react-app-rewired");
module.exports = function override(config, env) {
const tsLoader = getLoader(
config.module.rules,
rule =>
rule.loader &&
typeof rule.loader === "string" &&
rule.loader.includes("ts-loader")
);
tsLoader.options = {
getCustomTransformers: () => ({
before: [
tsImportPluginFactory([
{
libraryDirectory: "es",
libraryName: "antd-mobile",
style: "css"
},
{
camel2DashComponentName: false,
libraryDirectory: "",
libraryName: "@material-ui/core"
},
{
camel2DashComponentName: false,
libraryDirectory: "",
libraryName: "@material-ui/core/styles"
},
{
camel2DashComponentName: false,
libraryDirectory: "",
libraryName: "@material-ui/core/colors"
},
{
camel2DashComponentName: false,
libraryDirectory: "",
libraryName: "@material-ui/icons"
}
])
]
})
};
return config;
};
ok！

@sunshixiong789 Thanks for sharing the solution.


Filter order by warehouse

What I'm trying to achieve
Obtain orders that have specific click and collect warehouses
Describe a proposed solution
add filter input with warehouse id
Other solutions I've tried
Retrieving all orders with isClickAndCollect and applying second level of filtering

hey @timuric  can i work on this issue

Hey @akshatakulkarni25 sorry I missed your message, please feel free to pick up if you are still interested

More context in thread.

Hey, is this issue still available? Cannot get more context, because I don't have @saleor.io email.


Depot: Deleting a trail during creation hangs delete operation

Kinda a minor bug.  If a user goes to create a new trail, has the template page up, then clicks on the "delete" button...they get the confirmation "Are you sure you want to delete", but if you say OK to delete it, nothing happens and the dialog confirmation stays active.  Maybe we should disable the delete button until working with an actually persisted trail...or at least remove the delete button from the template screen perhaps.

This is actually happening for a lot of the deletes.  Saw it on Trails and Teams too.

fixed for Teams, Trails, Trail Urls, Domains, Domain Items, Users, CrawlType, ServiceType, Extractor.
Since we are cancelling the create, there is no actual Delete to perform, hence the object does not exist.  Added test to see if the object exists before trying to delete it.

merged https://github.com/Sotera/DatawakeDepot/commit/c25217271190e82514e8c67190c83b84e50cac22

tested and closing as fixed


Exclude unsupported EFO branches from Open Targets term mapping

Open Targets uses the slim version of EFO, which excludes some branches such as material entity. We should ensure the automation fetches terms only from this subset when we are running Open Targets processing.

One way to do this is to just use the regex OT uses during validation to filter the terms we fetch.


FCS update?

Hi @baronfel just wondering what your thoughts are about the next FCS update?
thanks!
don

FCS is being published on a nightly cadence from MS feeds as of about a month ago, there are 38.x prereleases there currently. I've been blocked due to life stuff on incorporating them into FSAC to prove them out, but they seem to be working fine in initial testing!

Oh that's great to know.  Where are they published to?

If you'd like to give an overview at the next dugnad session that would be cool

I have lost the commit where I was working on that, @cartermp can you give the actual answer here? The address you gave me in slack is lost to the sands of time.
@dsyme we're still missing automated publishing of the nuget dependencymanager as well (see https://github.com/dotnet/fsharp/issues/10133 for that), but once that's done I think we'll be in a really nice place for encouraging more rapid uptake/beta testing of the library across the community, and perhaps even start trying things like integrating different 'channels' of FCS into tools like Sharplab.

The feed should be: https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json
And an example installation:
nuget install FSharp.Compiler.Service -Source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json -PreRelease

Not sure how to do that with the .NET CLI though

dotnet add package FSharp.Compiler.Service -s https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json -version <blah>

It's pretty simple from a paket perspective as well: add the new source, enable prerelease, and do an update: https://github.com/fsharp/FsAutoComplete/pull/656


feat(firestore-bigquery-export): update the import script to write path_params

fixes: #947

Taking the branch from #979 consider merging it first

@yamankatby Waiting on CI updates before approving.


Local query with KnnService

I want to replace the client queries to the remote server, like this one:
client = ClipClient(url="https://knn.laion.ai/knn-service",
                    num_images=20,
                    deduplicate=True,
                    indice_name="laion5B-L-14"
                   )

results = client.query(embedding_input=image_emb.tolist())

with a locally run index.
My impression was that a local KnnService could do this, as demonstrated here:
https://github.com/rom1504/clip-retrieval/blob/main/notebook/simple_filter.ipynb
but then, the instructions linked for the laion5B-index dataset on HF (https://github.com/rom1504/clip-retrieval/blob/main/docs/laion5B_back.md) do not mention the use of the index files directly in Python.
When I try to run:
columns = ["url", "caption"]
indices_loaded, indices, device, model, preprocess, mclip_model = load_clip_indices("indices_paths.json", True, True, columns, False)
knn_service = KnnService(indices_loaded=indices_loaded, device=device, model=model, preprocess=preprocess, columns_to_return=columns, metadata_is_ordered_by_ivf=False, mclip_model=mclip_model)

It appears that the interface has changed since then (load_clip_indices() takes 2 positional arguments but 5 were given).
What would be the recommended way to run local queries from my own scripts? Is there any documentation for this that works with the current version of clip-retrieval?
Use case: embedding-based query for about 4,000 embeddings, each query with up to 10k results if possible (1k per query would be fine too)

In case anyone is wondering, you can still use ClipClient with a locally run index:
client = ClipClient(url="<IP_ADDRESS>:1234/knn-service",
                    num_images=20,
                    deduplicate=True,
                    indice_name="laion5B-L-14"
                   )

results = client.query(embedding_input=image_emb.tolist())

if you serve your index at <IP_ADDRESS>:1234.
You can serve from the command line as instructed here: https://github.com/rom1504/clip-retrieval/blob/main/docs/laion5B_back.md.

Simple filter way should work as well, let's update and test this notebook

Had a gander at this; looks like previously the ClipOptions class did not exist, the addition of which caused the notebook's usage of ClipClient() to bork. Here's a quick example oh how it might be updated
import os
os.environ["CUDA_VISIBLE_DEVICES"]=""
from clip_retrieval.clip_back import load_clip_indices, KnnService, ClipOptions

# setup clip options
clip_options = ClipOptions(
    indice_folder = "/home/chris/Documents/clip_client/Laion5B_H14",
    clip_model = "open_clip:ViT-H-14",
    enable_hdf5 = False,
    enable_faiss_memory_mapping = True,
    columns_to_return = ["url", "caption"],
    reorder_metadata_by_ivf_index = False,
    enable_mclip_option = False,
    use_jit = False,
    use_arrow = True,
    provide_safety_model = False,
    provide_violence_detector =  False,
    provide_aesthetic_embeddings =  False,
)

# load indices
loaded_indices = load_clip_indices("/home/chris/Documents/clip_client/indices_paths.json", clip_options)

# erect the knn search object
knn_service = KnnService(clip_resources=loaded_indices)

# filter a subset
results = knn_service.query(text_input="watermark",
                            modality="image",
                            indice_name="laion5B-H-14",
                            num_images=100,
                            num_result_ids=100)
import pprint
pprint.pprint(results)

Simple filter way should work as well, let's update and test this notebook

Updated the simple_filter.ipynb notebook just to get it working again; make a PR. You might wanna have a look at the ClipOptions()  params that I supplied, as I'm not sure what is appropriate for the default /common case.


updated use case again

Coverage remained the same at 92.174% when pulling 2182fc8c2fc62d638965581bd121d35037635cf5 on ALim95:V1.0_UpdateUseCaseAgain into 7f6b7a418ffacc3d02c1bdffb2f154260c985cba on CS2103AUG2017-T15-B4:master.


[CI] add link to PR in commit message before merge

It is useful find a link to PR just by looking at the commit log. The PR may have review and other details that helps establish the context of the patch.
For example arcanist would add Differential Revision to each commit message:
https://github.com/apple/llvm-project/commit/332b8cf1f689c8df279d920c4571ad4d2fc30066 This helps related a PR to patch and vice versa.

I guess this one has been solved by #272


func.yaml and environment variable security

I'm opening this issue for discussion of best practices surrounding environment variables defined in the func.yaml.
I didn't think much about this initially, but noticed that my func.yaml is included in the built container image. This isn't a big deal unless you're defining things like API Keys and SASL username/password in the environment. I was defining a username/password in the func.yaml and uploaded it to a public registry 😅
Does it make sense to strip the env field from the func.yaml, or omit the func.yaml (if that's even possible) from built images? I'm thinking how it can be better on the "secure by default" front.

I think we should just not include func.yaml in the image. It should be easy to filter it out in the buildpack

Closing: fixed in https://github.com/boson-project/buildpacks/pull/105


Add new plate reader compatibility. Update REVCOMP_SEQUENCERS

@RodolfoSalido all looks good! Thanks so much. 🎆


Consider making the "python" lexer support python 3?

(Original issue 1415 created by njs on 2018-02-06T08:21:31.485282+00:00)
Python 3 is increasingly popular, and has new syntax that's used pretty frequently (like async/await, f-strings, ...). But many popular applications follow pygments's lead, and use the python lexer by default, which only supports python 2, so you get ugly rendering of code that uses these new constructs. (E.g.: pygmentize, sphinx, pypi's readme_renderer, ...)
Heck, AFAICT the python lexer doesn't even know about "{}".format(...) syntax, which is in python 2.
Generally the python3 lexer gives pretty decent results on python 2. Most of the things removed from python 3 are pretty rare (e.g. file), and some keywords turned into builtins (print, exec) and vice-versa (True, False, None), but most files look OK. Probably the biggest mis-rendering is that the python3 won't highlight unicode and xrange as builtins. Plus at this point I think it's clear that python 3 is where the long-term momentum is – e.g. django is now python 3 only. And the vast majority of projects are at the very least py2/py3 polyglots, and by definition the python3 lexer should work for such code. So I think there's a good case for renaming python → python2 and making python an alias for python3.
If that's considered too extreme, though, then maybe it would at least make sense to have a python lexer that takes the union of the two languages (so e.g. treating async and await as keywords, but also treating xrange as a builtin), and provide python2 and python3 lexers for those who want to be more specific.

(Original comment by pganssle on 2018-02-12T17:46:38.765437+00:00)
Another option here might be to make it easy to globally set python to either python2  or python3 - for backwards compatibility you can keep the default to python2.

@pganssle for 2.5, PythonLexer and alias "python" is now Python 3.


feat: adding python side retry mechanism

Description
Add a retry mechanism in Python. We are assuming, that because of network issues, one call didn't reach the MAPDL instance. Hence, we can try again safely.
My concern is to trigger twice long calls (SOLVE).
Issue linked
Related to #3342
Checklist

[x] I have visited and read Develop PyMAPDL.
[x] I have tested my changes locally
[x] I have added necessary documentation or updated existing documentation.
[x] I have followed the PyMAPDL coding style guidelines.
[x] I have added appropriate unit tests that also ensure the minimal coverage criteria.
[x] I have reviewed my changes before submitting this pull request.
[x] I have linked the issue or issues that are solved to the PR if any.
[x] I have assigned this PR to myself.
[x] I have marked this PR as draft if it is not ready to be reviewed yet.
[x] I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

I feel i should ask for some advicing here... @koubaa @greschd @clatapie @ansys/pyansys-core

@pyansys-ci-bot LGTM.

The exception messages are now very clear:

Traceback (most recent call last):
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/errors.py", line 318, in wrapper
    out = func(*args, **kwargs)
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/mapdl_grpc.py", line 2498, in upload
    response = self._stub.UploadFile(chunks_generator)
  File "/Users/german.ayuso/pymapdl/.venv/lib/python3.10/site-packages/grpc/_channel.py", line 1518, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/Users/german.ayuso/pymapdl/.venv/lib/python3.10/site-packages/grpc/_channel.py", line 1005, in _end_unary_response_blocking
    raise _InactiveRpcError(state)  # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50053: Failed to connect to remote host: Connection refused"
        debug_error_string = "UNKNOWN:Error received from peer  {grpc_message:"failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50053: Failed to connect to remote host: Connection refused", grpc_status:14, created_time:"2024-08-22T16:36:30.03004+02:00"}"
>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/german.ayuso/pymapdl/tmp/crash.py", line 18, in <module>
    with mapdl.non_interactive:
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/mapdl_core.py", line 1380, in __exit__
    self._parent()._flush_stored()
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/mapdl_grpc.py", line 2028, in _flush_stored
    out = self.input(
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/errors.py", line 318, in wrapper
    out = func(*args, **kwargs)
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/mapdl_grpc.py", line 1785, in input
    filename = self._get_file_path(fname, progress_bar)
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/mapdl_grpc.py", line 1939, in _get_file_path
    self.upload(ffullpath, progress_bar=progress_bar)
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/errors.py", line 373, in wrapper
    handle_generic_grpc_error(error, func, args, kwargs, reason, suggestion)
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/errors.py", line 452, in handle_generic_grpc_error
    raise MapdlExitedError(msg)
ansys.mapdl.core.errors.MapdlExitedError: Error:
MAPDL server connection terminated unexpectedly while running:
  /var/folders/m7/qsr6z1m57rx8z_8xj8f3nm9r0000gp/T/tmp_jmpiuddomp.inp
called by:
  upload

Suggestions:
  MAPDL *might* have died because it executed a not-allowed command or ran out of memory.
  Check the MAPDL command output for more details.
  Open an issue on GitHub if you need assistance: https://github.com/ansys/pymapdl/issues
Error:
  failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50053: Failed to connect to remote host: Connection refused
Full error:
<_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50053: Failed to connect to remote host: Connection refused"
        debug_error_string = "UNKNOWN:Error received from peer  {grpc_message:"failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50053: Failed to connect to remote host: Connection refused", grpc_status:14, created_time:"2024-08-22T16:36:30.03004+02:00"}"
>

@PipKat can you spot any issues here (surely there are!) ?
ansys.mapdl.core.errors.MapdlExitedError: Error:
MAPDL server connection terminated unexpectedly while running:
  /var/folders/m7/qsr6z1m57rx8z_8xj8f3nm9r0000gp/T/tmp_jmpiuddomp.inp
called by:
  upload

Suggestions:
  MAPDL *might* have died because it executed a not-allowed command or ran out of memory.
  Check the MAPDL command output for more details.
  Open an issue on GitHub if you need assistance: https://github.com/ansys/pymapdl/issues
Error:
  failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50053: Failed to connect to remote host: Connection refused
Full error:
<_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50053: Failed to connect to remote host: Connection refused"
        debug_error_string = "UNKNOWN:Error received from peer  {grpc_message:"failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50053: Failed to connect to remote host: Connection refused", grpc_status:14, created_time:"2024-08-22T16:36:30.03004+02:00"}"
>

There are issues with CICD, taking forever to finish ... 75 minutes. It seems it gets stuck after runing this test.


What's the plan for 2.0 and future development?

From what I gather, 2.0 includes breaking changes.  The 2.0 rc1 hasn't seen any commits in several months.  There are several big changes like importing and journals in multiple files that are planned but haven't had any updates in 1/2 year.
I was just wondering if @maebert could share his plans for 2.0 and the future development of jrnl.
I ask because I want to work on improving the storage layer to gain the option of storing journals across multiple files #170, but I'm not sure if I should develop against master or 2.0 branch.

Hi there!
First of all, I'm sorry for being a little unresponsive and not giving jrnl as much time as it deserves these days. I got busy starting a company and traversing the world.
Here is the master plan for 2.0:

Switch the encryption engine from PyCrypto to cryptograph. Why? PyCrypto is a pain to install on different platforms. Cryptography uses OpenSSL as a backend and is much easier to install. This step is done on the 2.0 branch.
Have a generalised back-end interface so that writing a back-end that has multiple files is nothing but writing a new class with a different load / save method. This is basically also done. I'd like to make it a little smarter so that it doesn't have to load all files when you're just saving one for example.
Make YAML the new config format. It's more robust and easier to understand. Done, too.
Writing upgrade methods for converting journals encrypted with 1.x to the new format. This is not done yet and is the reasons tests are failing right now. Help appreciated
Write more tests. Help always appreciated.

I know there are a lot of PRs and a lot of people who'd like to support jrnl, and I'm super grateful for that. I'm going to manage as many of the PRs as possible today and then follow up here again!

You sound busy indeed.  Thanks for finding the time to reply.
That clears a lot of things up for me.  I think the only ones I might possibly be able to help with are 4 and 5.  Other than that I'd like to write another journal format or two and fix a few outstanding issues if I can find the time.
I couldn't find mention of YAML in 2.0-rc1 (I assume that is what you mean by the 2.0 branch).  Maybe it's not pushed yet?

It's in util.load_config:
def load_config(config_path):
    with open(config_path) as f:
        config = yaml.load(f)
    return config

Easy as that ;)

So it sounds like writing code to upgrade encrypted journals is the last item left?  I would think upgrading date format, too.  If so, I'll see if I can find time this week to work on that.

@maebert It would be cool if the 2.0.0 milestone tag was up-to-date so I knew where to focus my energy. :)

Writing code for upgrading encrypted journals is now done, too! And upgrading the date format, too. All there. All done.
What's really left to do is TESTING. Lots and lots of testing. And then more testing! Closing this issue now though :)

@flight16 Closed some issues that were fixed in 2.0!

Thank you for the replies and closing some issues!
Sorry for being persistent about this, but...
I still see 6 issues in the milestone for 2.0.0 that span bug, feature, large and small.  I assume that is the "things to resolve before 2.0.0 can be released" list, so I want to verify that the list is up-to-date and you expect all of them to be implemented before a release can happen.
If the focus is on getting 2.0.0 wrapped up and priority is given to breaking changes, then I would think the current 2.0.0 issues should be split out as follows:
v2.0.0

#297 No default configuration for 2.0rc1 bug (show-stopping bug, although this seemed to be implemented when I tryed 2.0rc1 branch)
#282 Plugin Framework Integration (big changes.  I saw some plugin-like hooks and code in 2.0rc1 branch.  Not sure what else there is left to do here)

v2.1.0 and beyond

#257 Import? Integration
#171 -quiet option Ideas Integration
#37 entries containing data Integration
#170 Use several files instead of only one? (can be supported with a new journal type, ideally minimal changes to core code will be needed)

I've been using jrnl daily for the last two weeks and like it a lot (thanks!).  I have many more bug fixes and features I'd like to work on, but I'd first like to help 2.0.0 get released so there is a single branch to develop against. : )

Totally agree :) I'd like to get #257 into 2.0 though. It's not a difficult feature to implement and it proves that the current framework makes sense. The rest: I agree. I'll change the milestones.


Changed the whole UI!

Changed the whole UI!
Added the The most popular component library for Tailwind CSS, also added the VantaJS library for the animated hero section.
You can find the Resources here:

VantaJS

Daisey UI

SICK UI!!!


CRC Image Registry login Issue - dial tcp <IP_ADDRESS>:5000: connect: connection refused

General information

OS: Ubuntu 18.04.4 LTS (Bionic Beaver)" VM with 64 GB RAM, 24 vCPUs, 100 GB disk
Hypervisor: KVM
Did you run crc setup before starting it (Yes/No)? Yes

$ crc version
crc version: 1.7.0+fa7e558
OpenShift version: 4.3.1 (embedded in binary)
$ crc status
CRC VM:          Running
OpenShift:       Running (v4.3.1)
Disk Usage:      16.72GB of 32.72GB (Inside the CRC VM)
Cache Usage:     12.3GB
Cache Directory: /home/ubuntu/.crc/cache
CRC config
$ crc config view

skip-check-crc-dnsmasq-file           : true
skip-check-network-manager-config     : true
skip-check-network-manager-installed  : true
skip-check-network-manager-running    : true

Host Operating System
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Steps to reproduce

crc setup
crc start
oc login -u kubeadmin -p  https://api.crc.testing:6443
Followed the instructions mentioned at https://docs.openshift.com/container-platform/4.3/registry/accessing-the-registry.html
$ oc policy add-role-to-user registry-viewer developer
clusterrole.rbac.authorization.k8s.io/registry-viewer added: "developer"
$ oc policy add-role-to-user registry-viewer kubeadmin
clusterrole.rbac.authorization.k8s.io/registry-viewer added: "kubeadmin"
$ oc policy add-role-to-user registry-editor developer
clusterrole.rbac.authorization.k8s.io/registry-editor added: "developer"
$ oc policy add-role-to-user registry-editor kubeadmin
clusterrole.rbac.authorization.k8s.io/registry-editor added: "kubeadmin"
podman login -u kubeadmin -p $(oc whoami -t) image-registry.openshift-image-registry.svc:5000

Expected
Login Succeeded!
Actual
$ podman login -u kubeadmin -p $(oc whoami -t) image-registry.openshift-image-registry.svc:5000
WARNING! Using --password via the cli is insecure. Please consider using --password-stdin
Error: error authenticating creds for "image-registry.openshift-image-registry.svc:5000": error pinging docker registry image-registry.openshift-image-registry.svc:5000: Get https://image-registry.openshift-image-registry.svc:5000/v2/: dial tcp <IP_ADDRESS>:5000: connect: connection refused
Logs
$ curl -vk https://image-registry.openshift-image-registry.svc:5000/v2/

Trying <IP_ADDRESS>...
TCP_NODELAY set
connect to <IP_ADDRESS> port 5000 failed: Connection refused
Failed to connect to image-registry.openshift-image-registry.svc port 5000: Connection refused
Closing connection 0
curl: (7) Failed to connect to image-registry.openshift-image-registry.svc port 5000: Connection refused

$ oc project openshift-image-registry
Now using project "openshift-image-registry" on server "https://api.crc.testing:6443".
$ oc get pods
NAME                                              READY   STATUS    RESTARTS   AGE
cluster-image-registry-operator-79bfcb686-4g44v   2/2     Running   0          31d
image-registry-5f4d9dc667-dhmxz                   1/1     Running   0          31d
node-ca-9s7kb                                     1/1     Running   0          31d
$ og c get all
NAME                                                  READY   STATUS    RESTARTS   AGE
pod/cluster-image-registry-operator-79bfcb686-4g44v   2/2     Running   0          31d
pod/image-registry-5f4d9dc667-dhmxz                   1/1     Running   0          31d
pod/node-ca-9s7kb                                     1/1     Running   0          31d
NAME                              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)     AGE
service/image-registry            ClusterIP   <IP_ADDRESS>           5000/TCP    31d
service/image-registry-operator   ClusterIP   None                    60000/TCP   31d
NAME                     DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
daemonset.apps/node-ca   1         1         1       1            1           kubernetes.io/os=linux   31d
NAME                                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/cluster-image-registry-operator   1/1     1            1           31d
deployment.apps/image-registry                    1/1     1            1           31d
NAME                                                        DESIRED   CURRENT   READY   AGE
replicaset.apps/cluster-image-registry-operator-79bfcb686   1         1         1       31d
replicaset.apps/image-registry-5bd685c64                    0         0         0       31d
replicaset.apps/image-registry-5f4d9dc667                   1         1         1       31d
replicaset.apps/image-registry-66997968c6                   0         0         0       31d
replicaset.apps/image-registry-7dbbbf5479                   0         0         0       31d
NAME                                     HOST/PORT                                                 PATH   SERVICES         PORT    TERMINATION   WILDCARD
route.route.openshift.io/default-route   default-route-openshift-image-registry.apps-crc.testing          image-registry      reencrypt     None

podman login -u kubeadmin -p $(oc whoami -t) image-registry.openshift-image-registry.svc:5000

@hi2kiran this is wrong, looks like you added the svc route to your dns so it is resolving the <IP_ADDRESS> but you should use the route instead of service endpoints to access the registry.
$  podman login -u kubeadmin -p $(oc whoami -t) default-route-openshift-image-registry.apps-crc.testing --tls-verify=false

Thanks a lot Praveen. It woked.
$ podman login -u kubeadmin -p $(oc whoami -t) default-route-openshift-image-registry.apps-crc.testing --tls-verify=false
WARNING! Using --password via the cli is insecure. Please consider using --password-stdin
Login Succeeded!
I have another Generic issue. If i execute any oc/crc commands ( like oc get pods, oc login, crc status). It is taking almost 15 secs to respond. Is there anything to be configured?

This is a separate issue. Can we file it as such to look into this?
Closing this issue as it is resolved.


Updating Xamarin component details and mode (to a shell component)

Resolves #6

@lindydonna , could you review the Markdown files to make sure the verbiage and links are accurate?

LGTM


Unify Gradle setup for API and implementation

We're currently using a quite huge amount of shared code in the Gradle setup of our projects. Because of this, changes always need to be done in each of them. Because SpongeAPI is referenced in the implementations splitting SpongeAPI's Gradle setup into separate (reusable) files simplifies an unified Gradle setup for SpongeAPI, Sponge and Granite.
The license header changes is only to provide a shared license header across the projects, therefore the project name is included directly from Gradle now instead of having it hard-coded in the header configuration file.

@progwml6

coughs sends @Mumfrey $5 coughs

looks good to me @AbrarSyed please review

@progwml6 Why do we move this to 2.1? This does not depend on the PR in the implementation at all and delaying this will just extremely delay the other Sponge PRs because I always need to wait for the implementation to update for the API changes and then have to fix tons of conflicts which takes a lot of time


Inconsistent header field names problem in OS X Safari (datajs issue)

Hi UI5 Team,
There is a little issue in datajs that leads to inconsistent response header names passed to the SAPUI5 handlers. I opened an issue at https://datajs.codeplex.com/workitem/1355 and I also wrote a tutorial about the issue on http://www.nabisoft.com/tutorials/javascript/resolving-datajs-response-header-access-errors-for-safari-on-mac-os-x (including the possible solutions).
To make it short: in line 2581 of datajs.js 1.1.2 there is a missing call of normalizeHeaders(headers);
This leads to the fact that in OS X Safari you have to access the response header with response.headers['Content-Type'] while you have to use response.headers['content-type'] for other browsers. It seems that Safari changes standard HTTP headers, i.e. 'content-type' is changed to 'Content-Type' even though the server sends all lower-case headers (I guess this is for a better human readability).
-Nabi

Thanks.
I fixed the issue. It was only the case in error cases that the headers were not normalized.
Will be in next 1.26.4 patch.


Update to gym==0.26.x

This PR updates the requirements, wrappers and examples to the new API introduced by gym==0.26.0.
Depends on https://github.com/coax-dev/coax/pull/27

There seems to be a lot of overlap with #27. Do we need both PRs?

There seems to be a lot of overlap with #27. Do we need both PRs?

Yes, I basically wanted to show the changes separately. In the end, we can just merge https://github.com/coax-dev/coax/pull/29 as it contains all other changes as well.


fix: minimumSize parameter is not considering the correct side of the split

@targos can you check this PR, after that can you merge it and create a new release?
fixed #153

@hamed-musallam did you mean that it fixes #151 ?
Michael is gone for one week, but this LGTM, I will create a release.

@stropitek
yes, i mean it fixes #151, can you make a new release?


helmfile: Stop prefixing PATH with kubernetes-helm

So helmfile will work with helm plugins wrapped by pkgs.wrapHelm:
{
  inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
  inputs.flake-utils.url = "github:numtide/flake-utils";

  outputs = { self, nixpkgs, flake-utils }:
    flake-utils.lib.eachDefaultSystem (system: let
      pkgs = nixpkgs.legacyPackages.${system};
      helm = pkgs.wrapHelm pkgs.kubernetes-helm {
        plugins = with pkgs.kubernetes-helmPlugins; [
          helm-diff helm-secrets
        ];
      };
    in {
      devShell = pkgs.mkShell {
        nativeBuildInputs = [
          helm
          pkgs.helmfile
        ];
      };
    });
}

Motivation for this change
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

This doesn't feel right. There's nothing guaranteeing postInstall will contain something else in the future.
I think the right call here would be to simply stop prefixing PATH with kubernetes-helm - and helmfile would pick the correct helm from $PATH if present.

Agree. The current implementation feels wrong, helmfile should not wrap kubernetes-helm, this makes helm plugins useless.

Can you update the PR/file a new one?

Pull request updated.

Thanks!

this makes helm plugins useless.

How do you figure? We have been using this for some time as follows:
let
  my-helm =  pkgs.wrapHelm pkgs.kubernetes-helm {
    plugins = with pkgs.kubernetes-helmPlugins; [
      helm-diff helm-secrets
    ];
  };
  my-helmfile = pkgs.helmfile.override {
    kubernetes-helm = my-helm;
  };
in
my-helmfile

Prior to this change you could create a predictable, hermetic helmfile like that. In the end, I suppose I can achieve similar results by ensuring the desired version of helm is on the PATH at runtime, but I prefer the way it used to be.

AFAIK, overriding kubernetes-helm will cause recompilation.
If you want to wrap helmfile with helm in PATH, you can now use:
let
  my-helm = pkgs.wrapHelm pkgs.kubernetes-helm {
    plugins = with pkgs.kubernetes-helmPlugins; [
      helm-diff helm-secrets
    ];
  };
  my-helmfile = pkgs.runCommandNoCC "helmfile" { buildInputs = [ pkgs.makeWrapper ]; } ''
    makeWrapper ${pkgs.helmfile}/bin/helmfile $out/bin/helmfile \
      --prefix PATH : ${pkgs.lib.makeBinPath [ my-helm ]}
  '';
in
  my-helmfile

Then helm wouldn't be in  PATH, and no recompilation.


Possible to support custom domain like *.?

In our existing CF deployments, we are using powerDNS, we want to move to BOSH dns to mitigate the pain of SPoF of powerDNS. Currently, we added custom domains (point to haproxy or load balancer) in powerDNS, so that it can help route the requests, like api., uaa., . and etc, to haproxy or load balancer. This is a very important requirement to us. Possible to support it in BOSH dns? Thanks.
/cc @maximilien @cppforlife

can you provide concrete example of these aliasing rules? ie what goes into matching and destination parts. that should help us make sure we would build right aliasing functionality.
Sent from my iPhone

On Aug 15, 2017, at 6:38 AM, cf-gitbot<EMAIL_ADDRESS>wrote:
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@cppforlife thanks for quick response, for example, if it's using haproxy in the deployment, I hope to add an alias like below:
addons:
- name: dns
  jobs:
  - name: dns
    release: dns
    properties:
      aliases:
        *.bosh-dns-sl-cpi.bluemix.net: [q-s0.ha-proxy.default.bosh-dns-sl-cpi.bosh]

So that api.bosh-dns-sl-cpi.bluemix.net, uaa.bosh-dns-sl-cpi.bluemix.net and .bosh-dns-sl-cpi.bluemix.net all can be routed to haproxy.

story: https://www.pivotaltracker.com/story/show/150418615

Thanks, @cppforlife , I will give another try once this story is implemented.
/cc @maximilien

Please note that the specific domain should overwrite wildcard domain, for examples:
addons:
- name: dns
  jobs:
  - name: dns
    release: dns
    properties:
      aliases:
        *.bosh-dns-sl-cpi.bluemix.net: [q-s0.ha-proxy.default.bosh-dns-sl-cpi.bosh]
        special_app.bosh-dns-sl-cpi.bluemix.net: [<IP_ADDRESS>]

Thanks.

@mattcui I added your comment in the story... if you can comment on stories, please do so when one is open so that point is not lost.

@mattcui i've confirmed that it works currently with following configuration:
addons:
- name: dns
  jobs:
  - name: dns
    release: dns
    properties:
      aliases:
        _.bosh-dns-sl-cpi.bluemix.net:           [q-s0.ha-proxy.default.bosh-dns-sl-cpi.bosh]
        special_app.bosh-dns-sl-cpi.bluemix.net: [q-s0.ha-proxy222.default.bosh-dns-sl-cpi.bosh]


For more details, see

https://github.com/sksamuel/scapegoat
https://github.com/sksamuel/sbt-scapegoat

(Also, I brought in a minor readme change from @ppiotrow 's fork)

Closing while I fiddle with this. Will open a new request when I get scalariform working.


feat: Enable PIE support for ASLR and full RELRO

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-rfid-llrp-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

Run the following command to build binary
make build

Verify that Full RELRO and PIE enabled are displayed
checksec --file=./cmd/device-rfid-llrp
RELRO           STACK CANARY      NX            PIE             RPATH      RUNPATH	Symbols		FORTIFY	Fortified	Fortifiable	FILE
Full RELRO      No canary found   NX enabled    PIE enabled     No RPATH   No RUNPATH   53710) Symbols	  No	0		0		./cmd/device-rfid-llrp

New Dependency Instructions (If applicable)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 39.52%. Comparing base (6a5b74d) to head (d982f18).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #319      +/-   ##
==========================================
- Coverage   39.56%   39.52%   -0.04%
==========================================
  Files          22       22
  Lines        9335     9335
==========================================
- Hits         3693     3690       -3
- Misses       4470     4472       +2
- Partials     1172     1173       +1

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


[ENHANCEMENT] Ensure the destination directories exist before starting downloads in the image-preload phase of Harvester Upgrade

Is your enhancement related to a problem? Please describe.

We've seen people encountered the following situation when conducting the Harvester upgrade...
In the prepare job's log, the curl command is screaming when downloading some image list files:
...
 local url=http://upgrade-repo-hvst-upgrade-bjx6b.harvester-system/harvester-iso/bundle//rancherd/images/rancherd-bootstrap-images-v1.3.1.txt
+ local output=/host/var/lib/rancher/agent/images/rancherd-bootstrap-images-v1.3.1.txt
+ echo 'Downloading the file from "http://upgrade-repo-hvst-upgrade-bjx6b.harvester-system/harvester-iso/bundle//rancherd/images/rancherd-bootstrap-images-v1.3.1.txt" to "/host/var/lib/rancher/agent/images/rancherd-bootstrap-images-v1.3.1.txt"...'
+ local i=0
+ [[ 0 -lt 100 ]]
Downloading the file from "http://upgrade-repo-hvst-upgrade-bjx6b.harvester-system/harvester-iso/bundle//rancherd/images/rancherd-bootstrap-images-v1.3.1.txt" to "/host/var/lib/rancher/agent/images/rancherd-bootstrap-images-v1.3.1.txt"...
+ curl -sSfL http://upgrade-repo-hvst-upgrade-bjx6b.harvester-system/harvester-iso/bundle//rancherd/images/rancherd-bootstrap-images-v1.3.1.txt -o /host/var/lib/rancher/agent/images/rancherd-bootstrap-images-v1.3.1.txt
curl: (23) Failure writing output to destination
Failed to download the requested file from "http://upgrade-repo-hvst-upgrade-bjx6b.harvester-system/harvester-iso/bundle//rancherd/images/rancherd-bootstrap-images-v1.3.1.txt" to "/host/var/lib/rancher/agent/images/rancherd-bootstrap-images-v1.3.1.txt" with error code: 23, retrying (0)...
+ echo 'Failed to download the requested file from "http://upgrade-repo-hvst-upgrade-bjx6b.harvester-system/harvester-iso/bundle//rancherd/images/rancherd-bootstrap-images-v1.3.1.txt" to "/host/var/lib/rancher/agent/images/rancherd-bootstrap-images-v1.3.1.txt" with error code: 23, retrying (0)...'
+ sleep 10

The root cause is that the destination directory /host/var/lib/rancher/agent/images does not exist. Since the pod mounts the host path, the equivalent path on the node is /var/lib/rancher/agent/images. The user stated that they didn't remove the directory. Harvester does not have relevant code snippets removing the directory either. So, I think the better way to address this is to ensure the destination path exists before starting any downloads.
Describe the solution you'd like

Check the destination path exists before downloading any image lists or tarballs. If not, create it.
Describe alternatives you've considered

N/A
Additional context

N/A

@starbops I'm not able to reproduce the exact issue, but I think we can use the curl built-in --create-dirs option to ensure that any missing target directory will get auto-created. Can you take a look at https://github.com/harvester/harvester/pull/6990 to see if it's the right approach?
Another possibility is that curl will also return the same curl: (23) Failure writing output to destination error if the uid didn't have sufficient r/w permissions to the target folder. Did the user, by any chance, change the in-container uid either manually or via policy engine?

@ihcsim Thanks for the PR; I'll take a look. Regarding error code 23 of the curl command, the user reported that the node was missing the target directory /var/lib/rancher/agent/images. After creating the directory, the curl command was happy. Though the permission was not the root cause, I think you pointed out a potential way the script would fail. With that said, I'm unsure how we can prevent this from happening or make things right. Any suggestion?

@starbops I think it's unlikely that user will modify the uid of the cattle-system/prepare pod, which is already configured to run as a privileged pod. I did notice the cattle-system namespace doesn't have any pod security admission labels. If necessary, we can just mention in the upgrade docs that all upgrade-related pods are privileged and must be run as root. Exemptions are needed if they alter the pod security restrictions of the harvester-system and cattle-system namespaces. (Better thing to do is to not touch those namespaces.)

@ihcsim That's a good suggestion. We can have a following documentation PR to state that it's better not to alter the harvester-system and cattle-system namespace objects for the upgrade to work smoothly.

Documentation updated per https://github.com/harvester/docs/pull/674.


Cape Fear Community College

https://cfcc.edu

@justinpridgen Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Expose IP-per-container app definition in App Details page

The App Details page needs to expose the new ipAddress object in the Configuration tab.
A network attribute will be added to the application definition. This attribute will hold the specification of a network interface with following attributes:
{
  "id": "oinker",
  "instances": 3,
  "network": {
    "ipAddress": {
      "groups": ["dev"],
      "labels": {
        "pool": "<IP_ADDRESS>/24"
      },
      "discovery": {
        "ports": [
          { "number": 80, "name": "http", "protocol": "tcp" }
        ]
      }
    }
  }

groups (optional): array of network groups. One network interface can belong to zero or more network groups. The idea is that containers can only reach containers with which they share at least one network group.
labels (optional): arbitrary key/value pairs as meta data to the network definition. This data can be used in the IPAM service to further specify requirements for the network interface.
discovery (optional): array of discovery information objects with the following attributes:
ports (required): an array of objects describing the ports used by the app. Each object contains the following attributes:
number (required): integer field with the port number the app is bound to.
protocol (required): enumeration of ["tcp", "udp"] defining the protocol.
name (optional): name of the port.

@leemunroe would it be enough to expose this object as a "code" block like we do for the healthChecks or can you suggest a better approach?
Keep in mind that:

labels are not the same as the top-level labels, they are specific to the network object and have likely different meaning / use cases
groups is an array
there can be multiple ports

@pierlo-upitup I think that makes perfect sense.

There's something not covered by mesosphere/marathon-ui#447.
Tasks with their own IP address still have a host field, with the hostname of the slave they're running on.
That field should be shown in the task details page.


Contact object conflict on guest

@Sammak : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@msmimart

Note that publishing in this repository is suspended until Tuesday, May 25. Merging will resume Tuesday. Authors can still review and sign off on PRs in the interim. Thanks.


refactor: add all missing non-core files to vhd

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

note for myself: still need to move our custom (and dynamic) containerd config generation out of cloud init.

https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=67755306&view=logs&j=6e436a35-c994-55aa-033b-9a96e1fbff66&t=ec907502-60f1-57e3-57a3-5710d3eff3e1&l=985


Add configurable throw exception when request body is larger than request cache size

My intent for this PR is to add exception throwing when request body is larger than request cache.
This feature is disabled by default.
When enableRequestTooLongException() javalin will throw exception if request cache is too small.
to my mind to get exception make it more predictable then to get empty body.

I personally dislike the inconsistency in naming. You call it RequestTooLongException, exceptionOnRequestCacheIsSmall.

Thanks @serii833, I appreciate the effort you've put into this, but how useful is this feature when it's disabled by default?

@tipsy I can make it enabled by default if you agree with such behavior of framework. For me personally would be better to get an exception instead of empty body. It's more clear what is happening.

@serii833 I think your proposal makes sense as default behavior, but it would break backwards compatibility. I propose you rewrite the PR to throw exceptions by default (I don't think it needs to be possible to disable the behavior), but the merge will have to wait until Javalin 3.0.

We could add this feature now with the default being disabled and change the default to enabled with the release of Javalin 3.0. That way those who want this feature earlier could opt-in as soon as we release the change.

We could, but would you seek out and enable this feature without knowing about it? The current behavior is the default behavior for Servlets.
What if we just log that the request was too big for the cache?

Maybe log it and advertise this option in the log message?

I'm trying to figure out how this is supposed to work. What are you supposed to do with these exceptions?

But both of this two options require you to deploy a new version of the app, so are these really runtime exceptions? Wouldn't it be enough to log.warn of the

sorry, I'm a little bit lost. You're talking about ways to implement this in javalin2 or about having such exception in general?

I'm not talking about implementation, but usage: How do you handle these exceptions? What you describe (increase cache size or go stream mode) requires you to make code changes, so what's the point of throwing a runtime exception?

@serii833 body() is not good anyways, cause empty body is not what I expect to get.
therefore I'll get an exception somewhere down in my code or I can get some weird behavior of my code.

Okay, let's say the Javalin now throws CacheTooSmallException, can you show me how you would handle this exception?

in simplified case I'll handle it like this
app.exception(Exception::class.java) { e, ctx ->
        logger.error(e) { "" }
        ctx.status(500)
}

then checking log manually or with some fancy stuff like elasticsearch with alerting I will see that I've got CacheTooSmallException.
And this is the most important that I will see CacheTooSmallException.
not some other exception (jackson, my code...) that will not give a clue that I need to increase cache.
this exception should guide me to docs saying that I need to increase cache size or go with "stream" mode.
My real case was
everything was ok in development.
we didn't use large requests and could consume body several times (first for bodyAsClass, second to log entire body for debugging).
when we switched to preproduction we were hit with some large requests that we needed to debug from application logic perspective.  but it turns out that log did not contain any errors and logged body was empty.
When I changed code to first log body and than do bodyAsClass I began to get "could not parse" from jackson.
It was some hours of frustration before I opened javalin sources and figured it out. :)
I don't think that log.warn will be enough. log.warn is often not respected by developers and admins as much as exception.

Accidentally closed the PR

I agree with you that the current behavior is bad, but isn't throwing an exception is less helpful than logging a warning/error? In your exception handler you're just logging and setting status to 500, maybe that could be the default behavior? What else could you want to do for this exception?

@serii833 I still don't think the exception is a good idea. It's hard for users to know what to do with it. What if we do this:

Add a hasBeenConsumed boolean to the CachedRequestWrapper
Check size > maxCacheSize && hasBeenConsumed and then something like:

log.error("""
    Attempted to read request body, but body has already been consumed
    and is not cached. You can increase the request body cache size by calling
    app.maxBodySizeForRequestCache(newMaxSize)
""")
throw HttpResponseException(413, "Payload Too Large")

looks very nice
it will stop the execution and will give some info in log

Great! Could you update the PR?

sure.

I still think logging is better than throwing an exception, so I'm going to close this.

in my opinion it's better to get an exception than dealing with unexpectable behavior.
but it's up to you to decide.
thanks


Question: Is it possible to make the equations selectable?

It might be a silly question. Is it possible to make the equation selectable in a PDF viewer?
using CSharpMath.SkiaSharp;
using SkiaSharp;

class MainClass
{
    public static void Main(string[] args)
    {
        using (var stream = new SKFileWStream("document.pdf"))
        using (var document = SKDocument.CreatePdf(stream))
        using (var canvas = document.BeginPage(500, 500))
        {
            // create the paint for the circle border
            var circleBorder = new SKPaint
            {
                IsAntialias = true,
                Style = SKPaintStyle.Stroke,
                Color = SKColors.Red,
                StrokeWidth = 5
            };
            // draw the circle border
            canvas.DrawCircle(100, 100, 40, circleBorder);

            // create the paint for the path
            var pathStroke = new SKPaint
            {
                IsAntialias = true,
                Style = SKPaintStyle.Stroke,
                Color = SKColors.Green,
                StrokeWidth = 5
            };

            // create a path
            var path = new SKPath();
            path.MoveTo(160, 60);
            path.LineTo(240, 140);
            path.MoveTo(240, 60);
            path.LineTo(160, 140);

            // draw the path
            canvas.DrawPath(path, pathStroke);

            // create the paint for the text
            var textPaint = new SKPaint
            {
                IsAntialias = true,
                Style = SKPaintStyle.Fill,
                Color = SKColors.Orange,
                TextSize = 80
            };
            // draw the text (from the baseline)
            canvas.DrawText("SkiaSharp!", 60, 160 + 80, textPaint);

            var painter = new TextPainter
            {
                Text = @"$\displaystyle\int_a^b f(x)\,\mathrm{d}x=F(b)-F(a)$"
            };
            painter.Draw(canvas, 320, 60, 100);

            document.EndPage();
        }
    }
}

This question could be about SkiaSharp, how to create links in an SKDocument, or independent of SkiaSharp and about how to manipulate pdfs. It also could be about links, or it could be about focus within pdf documents. It seems very ambiguous. Regardless, its unlikely that CSharpMath can help you.
It is interesting that SkiaSharp can be used to create pdfs and that therefore CSharpMath can be used to create pdfs.

@charlesroddie : canvas.DrawText("SkiaSharp!", 60, 160 + 80, textPaint); can be selected and searched because it is not blended to be a graphic object. But  painter.Draw(canvas, 320, 60, 100); blend the equation into a graphic object  that cannot be selected or searched.

OK I get it select = select and highlight text for copying
PDF does that badly even with ordinary text. So with maths there is no chance. But anything not in maths mode would probably be selectable.

CSharpMath draws all text as graphics, not as text. This is a byproduct of using the Typography library to read the typeface info and glyph contours, not SKTypeface of SkiaSharp. To use the DrawText method to draw text, CSharpMath would need to read the font file twice, which sounds like a performance loss.

OK. Thank you for responding!

@Happypig375,
for Pdf, selectable math expression adds  values to this lib.
and this is possible. But it need more works.
Since now you know exact position of each glyph.
Lets draw it with a character at that position.


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Update the if conditions so that validates the user names


Add user friendly message hinting incorrect gui user credentials

If I specify a wrong password for the gui user the only message from the failed csi pods is:
Back-off restarting failed container

Can you add a more user friendly message with a hint to check the credentials for the gui user?

@przem123 : Please let us know if anything is needed here.

Closing long pending issue, @przem123 if required please open the the issue with required information.


netboot: Minor fixes to accommodate rebooting from buildroot, failures in u-boot

Hah. Probably not your domain, but it would be a useful tool for @eddiejames IMO; it takes the pain out of netbooting custom kernels. This just adds support for a few more corner cases.


feat: added react 17 as peer dependency in packages

Addresses #5111
Summary
This PR adds React ^17.0.0 as peer dependency in packages to support Gatsby v3 and "gatsby-plugin-netlify-cms": "^5.0.0".
Test plan
yarn format
yarn test
A picture of a cute animal (not mandatory but encouraged)

Should be working fine


magento 2.2 receipe autload error in remote server

Q
A

Issue Type
Bug

Deployer Version
N/A

Local Machine OS
N/A

Remote Machine OS
N/A

Description
================
Autoload error: Vendor autoload is not found. Please run 'composer install' under application root directory.
Exception trace:
Deployer\Ssh\Client->run() at phar:///usr/local/bin/dep/src/functions.php:304
Deployer\run() at phar:///usr/local/bin/dep/recipe/magento2.php:50
Deployer\Deployer::Deployer{closure}() at n/a:n/a
call_user_func() at phar:///usr/local/bin/dep/src/Task/Task.php:105
Deployer\Task\Task->run() at phar:///usr/local/bin/dep/src/Executor/SeriesExecutor.php:63
Deployer\Executor\SeriesExecutor->run() at phar:///usr/local/bin/dep/src/Console/TaskCommand.php:155
Deployer\Console\TaskCommand->execute() at phar:///usr/local/bin/dep/vendor/symfony/console/Command/Command.php:252
Symfony\Component\Console\Command\Command->run() at phar:///usr/local/bin/dep/vendor/symfony/console/Application.php:946
Symfony\Component\Console\Application->doRunCommand() at phar:///usr/local/bin/dep/src/Console/Application.php:133
Deployer\Console\Application->doRunCommand() at phar:///usr/local/bin/dep/vendor/symfony/console/Application.php:248
Symfony\Component\Console\Application->doRun() at phar:///usr/local/bin/dep/vendor/symfony/console/Application.php:148
Symfony\Component\Console\Application->run() at phar:///usr/local/bin/dep/src/Deployer.php:331
Deployer\Deployer::run() at phar:///usr/local/bin/dep/bin/dep:119
require() at /usr/local/bin/dep:4
deploy [-p|--parallel] [-l|--limit LIMIT] [--no-hooks] [--log LOG] [--roles ROLES] [--hosts HOSTS] [-o|--option OPTION] [--] []
Steps to reproduce
Content of deploy.php
<?php
namespace Deployer;

require 'recipe/magento2.php';
inventory('hosts.yml');
// Project name
set('application', 'nthrive');
set('default_stage', 'staging');
// Project repository
set('repository', 'git@gitlab.com:fff/ggg.git');

set('writable_mode','chmod');

task('magento:enable', function () {
    run("pwd");
});

 task('deploy:update_code', function () {
   run("cd /home/nthrive/public_html && git checkout test.php && git pull origin develop");
});

// Tasks

desc('Deploy your project');
task('deploy', [
    'deploy:info',
    'deploy:prepare',
    'deploy:lock',
    'deploy:release',
    'deploy:update_code',
    'deploy:shared',
    'deploy:writable',
    'deploy:vendors',
    'deploy:clear_paths',
    'deploy:magento',
    'deploy:symlink',
    'deploy:unlock',
    'cleanup',
    'success'
]);

// [Optional] If deploy fails automatically unlock.
after('deploy:failed', 'deploy:unlock');

Output log
With enabled option for verbose output -vvv.

Please run 'composer install' under application root directory.

how to tell in deploy.php to run from application root directory.
there are two things deploy_path,release_path.
its trying to run release_path .

Override deploy:vendor task.

Closing this issue as inactive. If you still have this problem, please open a new issue.


reset unicodePwd

Hi,
I did a function to changePassword on AD via two modifications (delete with oldPassword, add with newPassword) and it works.
Now, I have to do a reset function, as an admin account on DC, I read that I can use replace modifier and set directly the new unicodePwd. I tried and InvalidCredentialsError, somebody did a function like that? What did I forget?
Alex.

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


Gradle plugin: allow to build arbitrary images without java plugin

Description of the issue:
When running jib tasks on a project without java plugin, tasks are failing with error:
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':tmp'.
> Could not find any convention object of type JavaPluginConvention.

Sample build.gradle:
plugins {
    id 'base'
    id 'com.google.cloud.tools.jib'
}

jib {
    container.entrypoint = "/${project.name}"
    from.image = 'registry.hub.docker.com/library/alpine:3.16.2'
    extraDirectories {
        paths {
            path {
                from = 'build/dist'
                into '/'
            }
        }
        permissions = ["/${project.name}": '755']
    }
}

Additional Information:
Current workaround is to add java plugin, but that adds a lot of unnecessary garbage to a non-java project.

Well, JIB does stand for "Java Image Builder". It sounds like it might not be a suitable tool for your usecase.

@elefeint true, but there is no better alternative :)
also jib-cli doesn't have this limitation.
I think it can be a nice feature to offer because ppl are build go\node\etc applications via gradle and they need to containerize them :)

Unfortunately, containerizing non-Java applications is not part of our team's charter -- buildpacks are a better fit for non-Java usecases. I am going to close this request as not planned.


regular image and camera

Hi
I just wondering if the training process running on normal images such as we take from regular camera instead of velo or stereo camera?

It should, you would just need to calibrate the camera. If you notice, I only use the left images from stereo, so it is a "normal" camera


feat: Add sample of new_with_encoders and infer_encoder

Related issue: https://github.com/adriangb/pgpq/issues/31
Adds a sample to Python README showcasing new_with_encoders and infer_encoder. The sample is based on my current work on exporting Arrow data to PostgreSQL.
Tested the script locally with a PostgreSQL database running on localhost:5432, and the final table looks like:
postgres=# select * from id_properties;
 id |          properties
----+------------------------------
  1 | {"age": 33, "name": "alice"}
  2 | {"age": 24, "name": "bob"}
  3 | {}
  4 | null
psothog=# \d id_properties
             Table "public.id_properties"
   Column   |  Type  | Collation | Nullable | Default
------------+--------+-----------+----------+---------
 id         | bigint |           |          |
 properties | jsonb  |           |          |

Besides this sample, I'd be happy to contribute more documentation. Are there any plans to host documentation pages somewhere? E.g. GitHub pages or readthedocs? I'd be happy to contribute the Sphinx boilerplate to get that going (at least for the Python API docs, not sure how to mix Rust and Python docs).
Thank you!

Thanks so much for the contribution! I prefer mkdocs hosted on github pages, I can set it up at some point, but for now I'd say let's keep it in a README.md until that clearly is not enough.


Clean up temporary directory used for multi-part download from S3 on startup

Directory should be configurable and whether feature is enabled should be configurable

Released in 0.83


Show status of file (staged vs non-staged) in a different way

Currently I always need to hover with the mouse across all changed files to see their commit status:

Can we please get an option to stop status icons/buttons from auto-hiding?

Currently I always need to hover with the mouse across all changed files to see their commit status

Why is that? How do the icons express any commit status?

They either show a "+" or a "-" sign.

They are in the Aederungen section. If you stage them, they will appear in another section, right?

Well, who else was I addressing?

They are in the Aederungen section. If you stage them, they will appear in another section, right?

So... what's the answer?

Here's how it works:

In git, when you modify a file, it becomes modified, we show it in the Changes view.
You can then stage it. That's what the plus does. And when you do, we show it in another section: the Staged Changes view.

The + doesn't transform to a -, the file actually goes into another group. Can you confirm?

Yes, I can confirm.
Yet, it's utterly hard to quickly distinguish between this:

... and that:

I don't know which size of screen you're working with, so here's the same screenshots scaled down for UX tests, to simulate a quick grasp while still having all the time to examine here:

Hi @joaomoreno : The needs more info flag is still set. Do you want me to provide more info?

I don't understand why it is hard to distinguish. The section names are very different.

Let's not argue about users being required to read and interpret subsidiary texts, particularly when they are hidden due to, say 50 files about to be pushed. Let's not argue about usability and mens' inability to quickly grasp static texts compared to the simplicity of recognizing a simple iconic sign.
I gave a visual example by providing the thumbnails above. In these examples it's not easy at all to tell one text from the other. Yet even with the thumbnails above one could simply tell "-" from "+".
You argue from a standpoint of someone with nothing else in mind than these two texts. I'm talking about feasibility, usability in contrast to information hiding.
So, for a moment, let's not argue about usability. Let's just restrain to argue about why VS Code hides functional information at all.  Why has deliberate functionality been added to VS Code to hide/reveal information instead of just showing necessary information statically? Why is hiding information an advantage to the VS Code team, worth implementing an animation?


peddy failling again in bcbio dev version

2
018-10-26 20:31:39 lt16 peddy.pca[71745] INFO loaded and subsetted thousand-genomes genotypes (shape: (2504, 6)) in 0.5 seconds
2018-10-26 20:31:42 lt16 peddy.pca[71745] INFO ran randomized PCA on thousand-genomes samples at 6 sites in 2.8 seconds
/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/sklearn/decomposition/base.py:133: RuntimeWarning: divide by zero encountered in divide
X_transformed /= np.sqrt(self.explained_variance_)
Traceback (most recent call last):
File "/home/pastore/data/bcbio/anaconda/bin/peddy", line 11, in
load_entry_point('peddy==0.4.2', 'console_scripts', 'peddy')()
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/click/core.py", line 764, in call
return self.main(*args, **kwargs)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/peddy/cli.py", line 207, in peddy
in ("ped_check", "het_check", "sex_check")]):
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/peddy/cli.py", line 43, in run
prefix=prefix, **kwargs)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/peddy/peddy.py", line 878, in het_check
pca_df, background_pca_df = pca(pca_plot, sitesfile, gt_types, sites)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/peddy/pca.py", line 81, in pca
pred = clf.predict(genotype_matrix)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/sklearn/utils/metaestimators.py", line 115, in
out = lambda *args, **kwargs: self.fn(obj, *args, **kwargs)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/sklearn/pipeline.py", line 307, in predict
return self.steps[-1][-1].predict(Xt)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/sklearn/svm/base.py", line 548, in predict
y = super(BaseSVC, self).predict(X)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/sklearn/svm/base.py", line 308, in predict
X = self._validate_for_predict(X)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/sklearn/svm/base.py", line 439, in _validate_for_predict
X = check_array(X, accept_sparse='csr', dtype=np.float64, order="C")
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/sklearn/utils/validation.py", line 453, in check_array
_assert_all_finite(array)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/sklearn/utils/validation.py", line 44, in _assert_all_finite
" or a value too large for %r." % X.dtype)
ValueError: Input contains NaN, infinity or a value too large for dtype('float64').
[2018-10-27T00:31Z] lt16: Unexpected error
Traceback (most recent call last):
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 52, in _setup_logging
yield config
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 177, in run_peddy
return ipython.zip_args(apply(peddy.run_peddy, *args))
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/peddy.py", line 99, in run_peddy
do.run(cmd.format(**locals()), message.format(**locals()))
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 23, in run
_do_run(cmd, checks, log_stdout, env=env)
File "/home/pastore/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 103, in _do_run
raise subprocess.CalledProcessError(exitcode, error_msg)
CalledProcessError: Command 'set -o pipefail; /home/pastore/data/bcbio/anaconda/bin/peddy -p 4  --plot --prefix /scratch/pastore/tmpWN4MhP/batch_FL_51608-P5-B5 /lila/data/abdelwao-lab/pastorea/Project/GALIUM/GALIUM/work/qc/batch_FL_51608-P5-B5/peddy/batch_FL_51608-P5-B5-annotated-germline.vcf.gz /lila/data/abdelwao-lab/pastorea/Project/GALIUM/GALIUM/work/qc/batch_FL_51608-P5-B5/peddy/batch_FL_51608-P5-B5-annotated-germline.ped 2> /scratch/pastore/tmpWN4MhP/run-stderr.log
' returned non-zero exit status 1

Thanks a lot for your help ! Yes ! is a super small gene panel only 100 genes

On Oct 27, 2018, at 9:22 PM, Brent Pedersen<EMAIL_ADDRESS>wrote:
INFO ran randomized PCA on thousand-genomes samples at 6 sites in 2.8 seconds
is the most informative message for some reason, it's only finding 6 sites to check the ancestry. is the a small gene panel?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/bcbio/bcbio-nextgen/issues/2547#issuecomment-433668478, or mute the thread https://github.com/notifications/unsubscribe-auth/AGOdNg75T4uFY0euyz3F4YZygHJeDwnWks5upQa4gaJpZM4X9b6o.

Alessandro and Brent;
Thanks for confirming. It sounds like catching the error and skipping here is the right thing. It's hard to say what will and won't work with peddy beforehand since it depends on overlaps with the sites, but if we error our in this way we're better off just cleanly skipping. Hope the workaround in bcbio gets your analysis finished and thanks again for the help debugging


Solved King Rush #1

Input white, black and the desired point in order in same line separated by space.
Solved #1

Solved  king Rush #1

Issue #1  fixed in #5


Fix debug policies

Fixed & tested the debug policy settings in PFR.  I changed the way of specifying them in config so they can be either turned all off or all on with one line.  Custom policies can be specified close to how they were before.
e.g.
[factory-settings]
debug-settings = "AllDisabled"

[factory-settings]
debug-settings = "AllEnabled"

[factory-settings]
debug-settings = {Custom = {nonsecure-noninvasive = "Disabled", secure-invasive = "EnableWithDap", jtag-tap = "Enabled"}}

Unfortunately custom debug-settings needs to be inlined currently due to toml-rs bug, but I think it's a safer to configure secure builds this way.

We should discuss out of band how to properly conceptualize these concepts; EnabledWithDap and the fixed/enabled bits etc. aren't really understable in the way I'd like this library to be.


Time Series key prefix to group sorted keys

Currently all keys are prefixed with o. Time Series keys should be prefixed with a different prefix so that they are stored together on disk when sorted by leveldb. This will make key scans more efficient because they will not have to skip over normal object keys in the case where they may be stored on the same node.
riak_kv_eleveldb_backend does not know which keys are Time Series and which are not, This change created a new type for Key, {colocated, LocalKey::binary()} which is part of the write once messages to the vnodes but not part of the object.  If the key is tuple tagged with the colocated atom then it will use the prefix c.
Further considerations:

AAE is currently disabled for Time Series but will most likely need to differentiate between partition and local keys in a similar way.
There is no write once path for merges, the riak_kv_vnode will need to check riak_object:get_ts_locat_key in the object metadata to construct the colocated key.
Single key deletes will also need to use the colocated key.

It appears single-key deletes PR (#1223) has the chances to get merged first. Will you then take care to rebase this PR on the new e2e/ts and massage the LK accordingly around here: https://github.com/basho/riak_kv/pull/1223/files#diff-021a303d7b16715d543d2b7a6239d15fR113?

I am taking this PR over @hmmr so will do

+1 after git://github.com/basho/riak_ql.git is changed to git@github.com:basho/riak_ql.git in rebar.config, so that get deps doesn't fail

Two changes: fixed rebar.config, fixed merge conflict due to the bucket/table overlap fix (and which negates my {Bucket, Bucket} concern).

+1


LabVIEW 2020 SW startup problem on D455 model

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D455

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10

Kernel Version (Linux Only)
-

Platform
PC

SDK Version
<IP_ADDRESS>74

Language
labview 2020

Segment
VR/AR/others }

Issue Description
<LabVIEW 2020 SW startup problem on D455 model>
Hello there!

I
Opening the LabVIEW Example was successful.
Opening LabVIEW Example by changing the dll file was successful.
However, the LabVIEW program runs but no screen appears. I have both LabVIEW 64bit and 32bit. Even if I try to run both by changing the dll file, the screen does not appear.

RealSense_HelloWorld_Left_Right_IR.vi is excutable.

Any help on how to solve this problem would be appreciated.
Thanks!!

Hi @woodal  Although the Monochrome + Depth LabVIEW example is included in the LabVIEW package, it is not described in the wrapper documentation.  From the descriptive text on the window of the image of the example that you kindly provided though, it looks as though it is streaming monochrome color from the left infrared sensor, probably with the monochrome UYVY format.

D455 supports streaming color from the left infrared imager if firmware version <IP_ADDRESS> or newer is installed, so your <IP_ADDRESS> firmware should allow this.  I do not know if this specific LabVIEW example has been tested with D455 though, as it would have more likely been designed for the older D415 model (which also supports color from the left infrared sensor - the D435 / D435i models do not).
Does the RealSense Hello World: Color + Depth example function correctly with your D455?  That example also streams color from the left infrared sensor.  https://github.com/IntelRealSense/librealsense/issues/8886 also demonstrates a D455 being successfully used with the Hello World: Point Cloud Plus that makes use of color from left imager for its color image.

Thank you @MartyG-RealSense !!
All programs recognize the D455 and run without error.
However, not all programs except "HelloWorld_Left_Right_IR.vi" will play the screen.😭

Hi @woodal Although the Monochrome + Depth LabVIEW example is included in the LabVIEW package, it is not described in the wrapper documentation. From the descriptive text on the window of the image of the example that you kindly provided though, it looks as though it is streaming monochrome color from the left infrared sensor, probably with the monochrome UYVY format.

D455 supports streaming color from the left infrared imager if firmware version <IP_ADDRESS> or newer is installed, so your <IP_ADDRESS> firmware should allow this. I do not know if this specific LabVIEW example has been tested with D455 though, as it would have more likely been designed for the older D415 model (which also supports color from the left infrared sensor - the D435 / D435i models do not).
Does the RealSense Hello World: Color + Depth example function correctly with your D455? That example also streams color from the left infrared sensor. #8886 also demonstrates a D455 being successfully used with the Hello World: Point Cloud Plus that makes use of color from left imager for its color image.
I am not aware of a previous case of the LabVIEW wrapper being used with LabVIEW 2020, though your successful launch of the RealSense Hello World: Left-Right example suggests that it is compatible.

When I try again, some programs work.
The rest will be dll's problem, right?

At the time of writing this, the latest release of the LabVIEW package was for the old SDK version 2.33.0.  We know that the wrapper works with newer SDK versions than 2.33.0, but there is no way to know for certain which samples will work with modern SDK dll library files until they are tried.

Hi Woodal and MartyG
It works on my machine (64-bit) with RealSense API version 2.40.00 and firmware <IP_ADDRESS> (as shown in the pic below).  I don't believe that I made any changes to the LabVIEW code in this particular example (other than updating the API as described in my original post (#7920)).

HOWEVER - when I update my firmware to <IP_ADDRESS> I have the same issue described by Woodal (see pic before) with errors in the Capture1 and Capture2 blocks.

If I revert backwards and start going from known working firmware (<IP_ADDRESS>) to successively newer firmware I get the following results (keeping API 2.40.0):
Firmware -       Functions?
<IP_ADDRESS> -    Yes
<IP_ADDRESS> -    Yes
<IP_ADDRESS> -  Yes
<IP_ADDRESS> -    Yes
<IP_ADDRESS> -    Yes
<IP_ADDRESS> -    No
Updated API to 2.49 in Labview folder (at least I think, I replaced the realsense2.dll and realsense2.lib files in the labview folder, but it still shows 24000 on the VI panel).
Firmware        Functions?
<IP_ADDRESS>     Yes
<IP_ADDRESS>     No
So, basically there appears to be something within firmware version <IP_ADDRESS> that is incompatible with this LabView example. Digging a little deeper, it appears the software times out before the frame arrives as there are no earlier reported errors.  If you have it working in one of the demos, it might be worth looking through the configuration portions of code to see what is different between the example code and the working one.
Or the easiest thing to do might be to just revert the firmware back a version or two...

Thanks so much @johnras for your detailed advice to @woodal   :)

Thanks so much @johnras and @MartyG-RealSense !
After changing Firmware, everything works fine.
thank you!😂😂

That's great to hear, @woodal ... thanks again @johnras for your helpful advice!

Case closed due to solution achieved and no further comments received.


Unable to bind chart to a gridster tile

I am trying to evaluate dc.js and c3.js for our internal dashboards. I am binding a gauge chart to a specific div inside a list item. For some reason the chart does not show up in the tile. Instead it shows outside the tile. I have attached the html file.
example.txt

nvm, the chart dimension was too big for the size of the tile. Reducing the height and width of the chart fixed it.


Issues with bridge start up with a lot of connections

I've got 4 gateways connecting 4 irc channels, 3 telegrams channels, 2 discord channels, steam, and matrix.
The 4 irc channels are on the same network and rizon doesn't seem to like when multiple connections are made too quickly which causes the bridge to fail.
Steam just has all around connectivity issues, especially when restarting the bridge after a connection was recently active. I normally have to wait two or three minutes before trying to start the bridge again to get it to connect.
I suggest either adding a way to dictate the order in which the bridge connects or adding an optional throttle between connections.
If you go with the latter I also recommend forcing steam chat connections first so if those fail the bridge isn't spamming the other networks with needless connections.

and you used a seperate connection for each irc channel why ? because of different user names ?

Because it's 4 different bridged chats. I never did check if it can do multiple chats with the same user, though, just assumed it wouldn't work since that's the way it works with Telegram.

It's a solution of a sort, but the problems I listed still exist.


Wrong property description in dialog component

Bug type
Component
Component name
Dialog
What happened?
The DeafultFocus prop has a wrong description

Expected behavior
Probably should be something different.
Reproduction link
https://github.com/MudBlazor/MudBlazor/blob/dev/src/MudBlazor/Components/Dialog/MudDialog.razor.cs#L112
Reproduction steps
Check the code
Relevant log output
No response
Version (bug)
6.1.7
Version (working)
No response
What browsers are you seeing the problem on?
Firefox
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Hi @mikes-gh Can I Work on this issue?


[BUG] Error at Importing Aepp-Sdk when running aeproject test

Describe the bug
When I ran aeproject test on the default aeproject (exampleTests.js file), Then I got an error that looks like [1]
However, a little bit of tracking got me to realize that it is in the util script from aeproject module when importing aepp-sdk [2]. The whole script ae-sdk.js is getting printed on the console which makes it harder to locate the actual errors on less precise terminal windows.
To Reproduce
Steps to reproduce the behavior:

Initialize the AEproject project aeproject init
Start the node with aeproject env
Run the tests with aeproject test
See the error

Expected behavior
It should work fine.
Screenshots
[1]

[2]

Aeproject information (please complete the following information):

OS executed at: [Ubuntu 20.04.2 LTS]
AEproject Version [^4(alpha)]
AEsdk Version [^10]

Thanks to @omar-saadoun  message on discord, This is solved by me as well by upgrading node to older LTS (12) to newer LTS (16).

This is also being solved on the sdk side in:
https://github.com/aeternity/aepp-sdk-js/pull/1365
https://github.com/aeternity/aepp-sdk-js/pull/1371
https://github.com/aeternity/aepp-sdk-js/issues/1382


Owen/uld example

Feel free to just take this as an idea. It isn't quite what I wanted (I couldn't find any 1d/2d easy systems in which ESS/autocorrelation time was meaningfully distinct form just doing Euler lol), but maybe has a little more fluff to motivate parallel sampling.

Ooops, I think my branch was based off main, the notebook is all that matters

Hey Owen, believe it or not, I haven't even realised you made a PR until now 😅.
I don't remember github notifying me of this, I must have missed it.
I really like your example and genuinely think it's a significant improvement on mine, but I think Patrick will be the final judge. It seem Langevin PR might get merged today (or soon anyway), so after that it's probably best if you just make a PR directly into diffrax/dev.


MobileBERT (fake weights) fails to run on Vulkan

With #5264 Mobilebert was changed to run as well in CI (there was a missing iree.symbol.export that prevented it). With this, the CPU side runs fine, but the GPU/Vulkan-SPIRV side fails to run. With the old path I get this error
$ ../build-vulkan-tracy/iree/tools/iree-run-mlir -export-all -iree-hal-target-backends=vulkan-spirv ../iree/iree/test/e2e/models/bert_encoder_unrolled_fake_weights.mlir
I /home/ravishankarm/Development/iree/iree/iree/tools/iree-run-mlir-main.cc:205] Compiling for target backend 'vulkan-spirv*'...
I /home/ravishankarm/Development/iree/iree/iree/tools/iree-run-mlir-main.cc:318] Evaluating all functions in module for driver 'vulkan'...
I /home/ravishankarm/Development/iree/iree/iree/tools/utils/vm_util.cc:258] Creating driver and device for 'vulkan'...
EXEC @serving_default
E /home/ravishankarm/Development/iree/iree/iree/tools/iree-run-mlir-main.cc:469] Failure for split at line #1: /home/ravishankarm/Development/iree/iree/iree/hal/vulkan/status_util.c:53: RESOURCE_EXHAUSTED; VK_ERROR_OUT_OF_DEVICE_MEMORY; vmaCreateBuffer; while invoking native function hal.allocator.allocate; while calling import; Evaluating export function 2; Evaluating functions
ERROR running file (../iree/iree/test/e2e/models/bert_encoder_unrolled_fake_weights.mlir): /home/ravishankarm/Development/iree/iree/iree/hal/vulkan/status_util.c:53: RESOURCE_EXHAUSTED; VK_ERROR_OUT_OF_DEVICE_MEMORY; vmaCreateBuffer; while invoking native function hal.allocator.allocate; while calling import; Evaluating export function 2; Evaluating functions
pure virtual method called
terminate called without an active exception
Aborted

with the new path I get this error
 ../build-vulkan-tracy/iree/tools/iree-run-mlir -export-all -iree-hal-target-backends=vulkan-spirv -iree-flow-dispatch-linalg-on-tensors -iree-codegen-spirv-experimental-linalg-on-tensors ../iree/iree/test/e2e/models/bert_encoder_unrolled_fake_weights.mlir
I /home/ravishankarm/Development/iree/iree/iree/tools/iree-run-mlir-main.cc:205] Compiling for target backend 'vulkan-spirv*'...
I /home/ravishankarm/Development/iree/iree/iree/tools/iree-run-mlir-main.cc:318] Evaluating all functions in module for driver 'vulkan'...
I /home/ravishankarm/Development/iree/iree/iree/tools/utils/vm_util.cc:258] Creating driver and device for 'vulkan'...
EXEC @serving_default
E /home/ravishankarm/Development/iree/iree/iree/tools/iree-run-mlir-main.cc:469] Failure for split at line #1: /home/ravishankarm/Development/iree/iree/iree/hal/vulkan/status_util.c:53: RESOURCE_EXHAUSTED; VK_ERROR_OUT_OF_DEVICE_MEMORY; vmaCreateBuffer; while invoking native function hal.allocator.allocate; while calling import; Evaluating export function 2; Evaluating functions
ERROR running file (../iree/iree/test/e2e/models/bert_encoder_unrolled_fake_weights.mlir): /home/ravishankarm/Development/iree/iree/iree/hal/vulkan/status_util.c:53: RESOURCE_EXHAUSTED; VK_ERROR_OUT_OF_DEVICE_MEMORY; vmaCreateBuffer; while invoking native function hal.allocator.allocate; while calling import; Evaluating export function 2; Evaluating functions
free(): double free detected in tcache 2
pure virtual method called
terminate called without an active exception
Aborted

Seems to be different errors.

This seems to pass on Android after Mahesh enabled it to run:
https://buildkite.com/iree/iree-android-arm64-v8a/builds/3873#f314defd-3437-45cd-9c10-066fecd3ef51
So the failure is only seen on Nvida GPUs so far.

In any case. It is disabled for all GPUs (I am happy to turn it back on if there is a way to avoid running this just on NVIDIA hardware)

Probably related to #5162

Probably related to #5162

This is related to running several tests in parallel right? This happens locally for me just running this single test.

oh I see. I didn't notice that it's run manually with  iree-run-mlir, sorry.

Started to look into this.

Looks it's because we are always allocating memory with both DIVICE_LOCAL_BIT and HOST_VISIBLE_BIT. The HOST_VISIBLE_BIT means a special heap with limited total size and we are exceeding that. For example, on my local  RTX 2070 Super, where I can repro this issue, vulkaninfo gives the following:
VkPhysicalDeviceMemoryProperties:
=================================
memoryHeaps: count = 3
        memoryHeaps[0]:
                size   =<PHONE_NUMBER> (0x200000000) (8.00 GiB)
                budget =<PHONE_NUMBER> (0x1c96d0000) (7.15 GiB)
                usage  = 0 (0x00000000) (0.00 B)
                flags: count = 1
                        MEMORY_HEAP_DEVICE_LOCAL_BIT
        memoryHeaps[1]:
                size   =<PHONE_NUMBER>6 (0x5e021a400) (23.50 GiB)
                budget =<PHONE_NUMBER>6 (0x5e021a400) (23.50 GiB)
                usage  = 0 (0x00000000) (0.00 B)
                flags: count = 0
                        None
        memoryHeaps[2]:
                size   = 257949696 (0x0f600000) (246.00 MiB)
                budget = 226754560 (0x0d840000) (216.25 MiB)
                usage  = 31195136 (0x01dc0000) (29.75 MiB)
                flags: count = 1
                        MEMORY_HEAP_DEVICE_LOCAL_BIT
memoryTypes: count = 11
        memoryTypes[0]:
                heapIndex     = 1
                propertyFlags = 0x0000: count = 0
                        None
                usable for:
                        IMAGE_TILING_OPTIMAL:
                                None
                        IMAGE_TILING_LINEAR:
                                color images
                                (non-sparse, non-transient)
        ... ...
        memoryTypes[10]:
                heapIndex     = 2
                propertyFlags = 0x0007: count = 3
                        MEMORY_PROPERTY_DEVICE_LOCAL_BIT
                        MEMORY_PROPERTY_HOST_VISIBLE_BIT
                        MEMORY_PROPERTY_HOST_COHERENT_BIT
                usable for:
                        IMAGE_TILING_OPTIMAL:
                                None
                        IMAGE_TILING_LINEAR:
                                None

A simple export VK_INSTANCE_LAYERS=VK_LAYER_LUNARG_api_dump shows that we are always allocating memory with memoryTypeIndex = 10, which uses memoryHeaps[2]. We only have 246MB there.. I don't know the heap status for Tesla T4 used for our CI, but I think it might be something similar.
This is passing for Android because we have unified memory there. So DEVICE_LOCAL_BIT and HOST_VISIBLE_BIT is available for the whole memory, e.g., for Mali G77.
Looking into the HAL code, it seems we have a TODO here, which forces HOST_VISIBLE_BIT on:
https://github.com/google/iree/blob/1386d2cd284bf8babafdf90a0823afabd0e0c9f8/iree/hal/vulkan/vma_allocator.cc#L158-L169
@benvanik: looks like we can just delete the above?

Yeah, I can confirm that after deleting L166-L167 in the above, the test passes.

awesome - good find! we may be able to get rid of the host visible/mapping bit soon (if not already) - part of the reason for it was hal.buffer.fill and such, but now those are all command buffer operations and don't require host-visible memory. lots of GPUs have limits on that memory type because they are limited to the PCI-E aperture size.

Ah nevermind with BufferLoadOp we may still need this for now - both HAL_BufferFillOp and HAL_BufferCopyOp can be removed though. We need the analysis to know that a particular buffer is read back on the host to set the right bit (which is the same analysis I need for allocation). We could at least ensure we aren't setting it for constants and such.

(detensoring would also help - it's used now for those silly tensor loop iterators)

We're having the same issue with large_cifar10_tests__applications__iree_vulkan__model__ResNet50: https://source.cloud.google.com/results/invocations/ad178b26-b4a9-4ec4-9aa8-80e41e43a8f1/targets/iree%2Fgcp_ubuntu%2Fcmake-bazel%2Flinux%2Fx86-turing%2Fmain/log

I've my hands full with a few other bugs to fix. For now I'll disable the ResNet50 test to avoid hiding other potential failures. I'll come back to this after addressing the other issues, if Ben didn't solve it before I can. :)

After #5328 lands I can take a look at this. Doing the buffer tracking to know when a readback is required (and thus HOST_VISIBLE must be set) is a good next step for buffer allocation.