Entity Relation Processing

Fixes #2960
Partial implementation of entity relationships. It takes it to the point where relationships are part of the processing output, but doesn't actually attach them to entities or store them in any way. Figuring we can keep discussions around the issue on this PR.
What I can see we can either refactor to get a global view of all entities so that the relationships can be attached at the end of the processing, or we can add a new table that keeps track of entity fragments that should be attached to entities when reading from the catalog, along with the logic for stitching them together.
Also need to consider the entities_search table and how to construct it, and whether it should contain relations.

The way I was thinking about the resolution and storage of relations:
The relation in memory has a kind:namespace/name triple as a lowercased string for the source and target. The entities table has a similar column. The relations are stored in a separate table, with the columns id, originating_entity_uid, source_name, relation_type, target_name (and maybe some more aux stuff). The name columns are indexed and can be joined on in queries. Loosely coupled.

Regarding search:
Yeah I think they will be added to the search as well. If the output format were
apiVersion: backstage.io/v1alpha1
kind: API
metadata:
  name: spotify
[...]
relations:
  implements-api: api:default/webapi

then the filter query would be along the lines of /entities?filter=relations.implements-api:api:default/webapi

@freben what do you want to use the id and originating_entity_uid for in that relations table?
And yeah search could work something like that. We did conclude that we likely wanted to keep the possibility of annotated relations open though, even if we don't add it initially

id is pretty much just a bit of a habit - all things in all databases having their own primary key to reference them by because it usually turns out you want it - but not an important part of my current model idea
originating_entity_uid has two important functions: it's an FK with ON DELETE CASCADE to keep them alive only for as long as the entity exists that causes them to be relevant, and to be able to batch replace all relations that an entity causes after the refresh concludes.

This is now ready for review and actually adds e2e support for relations.
It does not yet make it possible to query by relations, i.e. it does not populate the entities_search table.

yeah I think this one is perfectly fine, i mostly have nits and ideas for future improvement and no blockers


Error when making another faction in city rp

At first, i thought it was the player models i was using but changed the models to the defult citizen ones and still had this error
[ERROR] gamemodes/cityrp/plugins/cityrphud.lua:101: attempt to index local 'classData' (a nil value)

unknown - gamemodes/cityrp/plugins/cityrphud.lua:101
unknown - gamemodes/nutscript/gamemode/core/libs/sh_plugin.lua:420

Well, I didn't made this CityRP gamemode for multiple factions.

Is there any way to get around it to add a faction?

Easy fix to multiple factions on CityRP is to make sure both new classes and factions have unique names.


Fix instantiation of resource as property value

This fixes the case where you instantiate an scripted resource type directly as a property value. (It's another side effect of the new behavior of Variant regarding Reference, which makes calling script on an unreferenced Reference illegal.)

Thanks!

Cherry-picked for 3.2.4.


Unable to create DB2 pureScale instance

Error while DB2 Instance creation step, while running this
/data2/db2bits/server_dec/db2setup -r /root/db2server.rsp -l /tmp/db2setup_000.log -t /tmp/db2setup_000.trc
I tried the solution in https://github.com/Azure/db2-on-azure/blob/master/doc/archive/KB_archive.md but it still gives the same error.
Installing DB2 file sets :.......Success
Installing or updating DB2 HA scripts for IBM Tivoli System Automation for Multiplatforms (Tivoli SA MP) :.......Success
Installing or updating DB2 Cluster Scripts for IBM Spectrum Scale (GPFS) :.......Success
Compiling GPL :.......Success
Executing control tasks :.......Success
Updating global registry :.......Success
Updating the db2ls and db2greg link :.......Success
Setting default global profile registry variables :.......Success
Register NTP :.......Success
Initializing instance list :.......Success
Initiating the remote host list :.......Success
ERROR: A reachable IP address could not be automatically determined that did
not belong to one of the hosts in the DB2 pureScale instance. There may be a
problem with the network adapters gateway IP address or with the hosts network
connection. Verify connectivity for the hosts and manually edit the
configuration file /var/ct/cfg/netmon.cf on each host to include an IP on the
network outside of the DB2 pureScale instance that can be reached by the ping
command so that DB2 may ensure network connectivity. Hosts: "d0  d1 cf0 cf1".
The format of /var/ct/cfg/netmon.cf lines is as follows:  !REQD eth1
<IP_ADDRESS>

Configuring DB2 instances :.......Failure
Registering DB2 Update Service :.......Success
Updating global profile registry :.......Success
WARNING: A minor error occurred while installing "DB2 Server Edition " on this
computer. Some features may not function correctly.

Thank you. We're working on a solution to improve our documentation. Ultimately, the witness should be on the admin network, it's recommended that you don't need/use the witness, and you can ignore this error message (if you do get it... which the goal is to avoid it). The updates in the documentation will add a lot more additional clarity and information. Thank you for your help, as we seek to make this a frictionless process!

Thanks @EdPrice-MSFT for comment. Witness node comes as part of the setup.
Due to this error, we are not able to create a DB2 instance. I am really stuck at this point from last few weeks.
Any help is appreciated here, on how to proceed.

I got confirmation from IBM support that this is not a supported procedure/environment, as the use of GlusterFS under GPFS is known to be susceptible to data corruption.
They also communicated to MS team that this document be taken down, or at minimum marked as experimental and unsupported by IBM.

IBM recommends using Storage Spaces Direct. This shouldn't have the witness issue. We'll update the documentation with more information about this topic, as well as with the SSD instructions. The existing scenario works fine, but we'll add clarity around this scenario. Thank you.


When training to the second epoch, encounter "AssertionError: scalar should be 0D"

Hi Yisheng,
   There are somethings wrong when I train the Linemod dataset. Specifically，When training to the second epoch，the program will stop training and encounter the following error code. I hope to get your help，thanks a lot. Best wish.

At the first epoch, everything looks normal.
#######################################################
train_dataset_size:  186
cls_id in lm_dataset.py 1
cls_id in lm_dataset.py 1
test_dataset_size:  1050
test_dataset_size:  1050
loading resnet34 pretrained mdl.
loading resnet34 pretrained mdl.
local_rank: 0
local_rank: 1
Selected optimization level O0:  Pure FP32 training.
Defaults for this optimization level are:
enabled                : True
opt_level              : O0
cast_model_type        : torch.float32
patch_torch_functions  : False
keep_batchnorm_fp32    : None
master_weights         : False
loss_scale             : 1.0
Processing user overrides (additional kwargs that are not None)...
After processing overrides, optimization options are:
enabled                : True
opt_level              : O0
cast_model_type        : torch.float32
patch_torch_functions  : False
keep_batchnorm_fp32    : None
master_weights         : False
loss_scale             : 1.0
/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/nn/_reduction.py:43: UserWarning: size_average and reduce args will be deprecated, please use reduction='mean' instead.
warnings.warn(warning.format(ret))
Totally train 775 iters per gpu.
ape_epochs:   0%|                                        | 0/25 [00:00<?, ?it/s]/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/nn/_reduction.py:43: UserWarning: size_average and reduce args will be deprecated, please use reduction='mean' instead.
warnings.warn(warning.format(ret))
Totally train 775 iters per gpu.
ape_epochs:   0%|                                        | 0/25 [00:00<?, ?it/s]kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt [00:00<?, ?it/s]
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/nn/functional.py:2416: UserWarning: nn.functional.upsample is deprecated. Use nn.functional.interpolate instead.
warnings.warn("nn.functional.upsample is deprecated. Use nn.functional.interpolate instead.")
/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/nn/functional.py:2506: UserWarning: Default upsampling behavior when mode=bilinear is changed to align_corners=False since 0.4.0. Please specify align_corners=True if the old behavior is desired. See the documentation of nn.Upsample for details.
"See the documentation of nn.Upsample for details.".format(mode))
/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/nn/functional.py:2416: UserWarning: nn.functional.upsample is deprecated. Use nn.functional.interpolate instead.
warnings.warn("nn.functional.upsample is deprecated. Use nn.functional.interpolate instead.")
/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/nn/functional.py:2506: UserWarning: Default upsampling behavior when mode=bilinear is changed to align_corners=False since 0.4.0. Please specify align_corners=True if the old behavior is desired. See the documentation of nn.Upsample for details.
"See the documentation of nn.Upsample for details.".format(mode))
/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/nn/modules/container.py:100: UserWarning: Implicit dimension choice for log_softmax has been deprecated. Change the call to include dim=X as an argument.
input = module(input)
/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/nn/modules/container.py:100: UserWarning: Implicit dimension choice for log_softmax has been deprecated. Change the call to include dim=X as an argument.
input = module(input)
/home/extend/gy/pyproject/FFB6D/ffb6d/models/loss.py:30: UserWarning: Implicit dimension choice for log_softmax has been deprecated. Change the call to include dim=X as an argument.
logpt = F.log_softmax(input)
/home/extend/gy/pyproject/FFB6D/ffb6d/models/loss.py:30: UserWarning: Implicit dimension choice for log_softmax has been deprecated. Change the call to include dim=X as an argument.
logpt = F.log_softmax(input)
ape_epochs:   4%|\u2588\u258e                              | 1/25 [00:52<20:48, 52.02s/it]kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt/it, total_it=31]
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt/it, total_it=31]
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
###########################################################
But complete the second training epoch, it will stop training. Like this,
###########################################################
ape_epochs:   8%|\u2588\u2588\u258c                             | 2/25 [01:30<16:57, 44.25s/it]kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt/it, total_it=62]
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt/it, total_it=61]
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
ape_epochs:   8%|\u2588\u2588\u258c   kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txtit [00:00, ?it/s]
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txtkps_pth in get_kps:
datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
kps_pth in get_kps: datasets/linemod/kps_orb9_fps/ape_8_kps.txt
loss_rgbd_seg 0.11550371497869491
loss_kp_of 11.04855725969587
loss_ctr_of 1.3788805430276054
loss_all 12.658445249285016
loss_target 12.658445249285016
acc_rgbd 84.9538414137704
ape_epochs:   8%|\u2588\u2588\u258c                             | 2/25 [02:42<31:09, 81.28s/it]
Traceback (most recent call last):
File "train_lm.py", line 697, in
train()
File "train_lm.py", line 688, in train
clr_div=clr_div
File "train_lm.py", line 518, in train
val_loss, res = self.eval_epoch(test_loader, it=it)
File "train_lm.py", line 420, in eval_epoch
writer.add_scalars('val_acc', acc_dict, it)
File "/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/tensorboardX/writer.py", line 490, in add_scalars
fw.add_summary(scalar(main_tag, scalar_value),
File "/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/tensorboardX/summary.py", line 153, in scalar
assert(scalar.squeeze().ndim == 0), 'scalar should be 0D'
AssertionError: scalar should be 0D
Traceback (most recent call last):
File "/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/distributed/launch.py", line 263, in
main()
File "/home/extend/gy/miniconda3/envs/FFB/lib/python3.7/site-packages/torch/distributed/launch.py", line 259, in main
cmd=cmd)
subprocess.CalledProcessError: Command '['/home/extend/gy/miniconda3/envs/FFB/bin/python3', '-u', 'train_lm.py', '--local_rank=1', '--gpus=2', '--cls=ape']' returned non-zero exit status 1.
########################################################################
#48
The error seems to be due to the version of tensorboardX? or something else. Please give me some advises.

Hi, I have meet the same question as you. If you solve this problem, please give me some advices.

I have tried to lower the version of python and tensorboard, but it doesn't work. Otherway, Since "write_scalar" only plays the role of saving data for display on the tensorboard. it does not affect training, so I commenting it. There is everything normal until the training stage，I hope it can help you.

Hi, I have meet the same question as you. If you solve this problem, please give me some advices.
I have tried to lower the version of python and tensorboard, but it doesn't work. Otherway, Since "write_scalar" only plays the role of saving data for display on the tensorboard. it does not affect training, so I commenting it. There is everything normal until the training stage，I hope it can help you.

Hi, I have meet the same question as you. If you solve this problem, please give me some advices.

I have tried to lower the version of python and tensorboard, but it doesn't work. On the other way, since "write_scalar" only plays the role of saving data for display on the tensorboard. It does not affect training, so I commenting that. There is everything normal until the training stage，I hope it can help you.

Hi,
Any updates on this issue, or alternative class/function I can use to save these results?

It seems this is because the value in acc_dict is a list of many values. This will not squeeze to a 0D. I do not know exactly how add_scalars differs from add_scalar, but it would be work if you iterate through the values in the list and add them instead.

Have you solved this problem? Requesting help, I have also encountered this issue

看之前的回答应该是不影响训练精度，可以不用管
At 2023-05-06 23:03:36, "lin-fangzhou" @.***> wrote:
Have you solved this problem? Requesting help, I have also encountered this issue
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

你把acc_dict输出，其中acc_rgbd不是零维，我不太确定是不是可以取平均，然后这样就是零维可以正常运行


CUDA illegal memory access for the Triton example

Can you reproduce the error by running the softmax example ?  Thank you for your instruction.
x = torch.randn(756480, 3152, device='cuda', dtype=torch.float16)
for i in range(100):
  y_triton = softmax(x)
torch.cuda.synchronize()

RuntimeError: CUDA error: an illegal memory access was encountered

想请教一下这个问题怎么解决？ @jinz2014

Thanks to @htyu for the updated softmax tutorial


Webhid is also available in Chromium based Edge behind a flag

Tested in 80; assume also available in 79 based on same engine:
navigator.hid
HID {onconnect: null, ondisconnect: null}
    onconnect: null
    ondisconnect: null
    __proto__: HID

Thanks!


WIP: V4.4.x lgpl ffnv

lgpl variant with nvidia codecs
Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

its interesting that ubuntu uses clang to generate the nvidia files:
clang --cuda-gpu-arch=sm_30 -O2 -m64 -S -nocudalib -nocudainc --cuda-device-only -Wno-c++11-narrowing -include src/compat/cuda/cuda_runtime.h    -o libavfilter/vf_overlay_cuda.ptx src/libavfilter/vf_overlay_cuda.cu


https://dc.weba.ru/

https://dc.weba.ru/

I am afraid, this website will not be added to 10 KB Club because it does not meet the requirement specified in the fifth point of the Club Rules.


[Enhancement]: Implemented endpoint for renaming an application

Description
This PR introduces an endpoint to update an existing app, including the necessary backend logic and test cases.
Related Issue
Closes AGE-539
Changes Included:

Added a new update_app router to handle app update requests.
Implemented the update_app DB function to update app details in the database.
Added test cases to validate the update functionality.

What to QA

App Update via API:

Test the new update endpoint by updating an app’s details (e.g., name) and verify that the changes are correctly reflected in the database.

Error Handling:

Test edge cases like updating non-existent apps or providing invalid data and verify that appropriate errors are returned.

Acceptance Tests

Create App:

Create an app from the UI or CLI

Update App via API:

Send a request to the update app endpoint and confirm that the app’s details are updated correctly in the database.

Test Case Validation:

Run the test suite to ensure that all test cases pass, including the new ones added for the update functionality.

Error Handling Scenarios:

Verify that proper error messages are returned when invalid or incomplete data is provided in the update request.

Also, let's update the fern client SDK (it might make sense to add a github action for this @aakrem )

Added to my QA todo list.

What to QA

[ ] Test the new update endpoint by updating an app’s details (e.g., name) and verify that the changes are correctly reflected in the database.
[ ] Test edge cases like updating non-existent apps or providing invalid data and verify that appropriate errors are returned.

Acceptance Tests

[ ] Create an app from the UI or CLI
[ ] Send a request to the update app API endpoint and confirm that the app’s details are updated correctly in the database.
[ ] Run the test suite to ensure that all test cases pass, including the new ones added for the update functionality.
[ ] Verify that proper error messages are returned when invalid or incomplete data is provided in the update request.

ongoing

☝  requires fixing ?

 ☝ requires fixing ?

Nope, it doesn't.


Examples don't seem to pick up non-character keyes

Describe the bug
I checked out the source and ran several of the examples. In all cases the prompt wouldn't respond to the enter or backspace key, or any other keys I tried other than typing letters or spaces.
To Reproduce
Steps to reproduce the behavior:
Check out source.
cargo run --example cursor_style
Try to enter a command
Expected behavior
Should be able to enter commands with enter and delete characters with backspace
GQL (please complete the following information):
0.2.0

Hello @sadmac7000,
In the key bindings and drop down auto complete examples you can find an examples for binding common non-character keyes and custom key bindings,
If you have suggestion to improve samples and add any case feel free to suggest
Thank you,
Amr Hesham

Not binding enter in the examples means it is impossible to quit them. I had to kill the application from another window.

Oh, you are right i think we should register at least quit binding for all examples,

Done, Thank you @sadmac7000


Include softDeletes in search results

Is there a way to include soft deleted models in the search results?
I tried several approached found around the net with no luck.
Maybe this is related to #17?

i modified this engine a little to do the trick
added these lines in src/Engines/MySQLEngine.php
// line 59
if ($builder->callback) {
    $query = call_user_func($builder->callback, $query);
}

and then i could do this in my controller
$products = Product::search($request->keyword, function($query) {
    return $query->active()->withTrashed(); // local scope and soft deletes
})->paginate(20);

@sembrex - will this package already respect global scopes as it's querying the relevant table?

This is what I've had to use to get soft deletes in my results:
MyModel::search($text, function ($query) {
    return $query->onlyTrashed();
})->get();

Weirdly, only works with the 'soft_delete' boolean set to 'false' in app/scout.php


Brainstorming on MyST docstrings via sphinx.ext.autodoc

When converting rST projects to use MyST, directives from sphinx.ext.autodoc's such as automodule can cause issues.
The sphinx extension sphinx.ext.autodoc provides directives (automodule, autoclass, ...) that emits rST like .. py:module:: kubespawner.utils and provides the directives with raw docstrings from the referenced Python code.
Background
Here is an example of how you would use sphinx.ext.autodoc from a MyST document correctly.
# Utilities

```{eval-rst}
.. automodule:: kubespawner.utils
```

The automodule directive will emit rST directives and raw docstrings that also ends up parsed as rST.
Two issues
Here is an example using the automodule directly as a MyST directive, and it leads to two issues:
# Utilities

```{automodule} kubespawner.utils

```

Issue 1 - sphinx.ext.autodoc emits rST formatted directives
sphinx.ext.autodoc will emit rST formatted directives even though invoked from a MyST document like:
# Utilities

```{automodule} kubespawner.utils

```

Issue 2 - sphinx.ext.autodoc has made us write docstrings with rST
A project who has used sphinx.ext.autodoc has needed to write the docstrings in rST rather than MyST historically due to always being parsed with rST.
If we are to support MyST docstrings, I think of one initial key goal, and a stretch goal:

Key goal: to support a project wide default declaring docstrings to be either rST or MyST (100% rST docstrings or 100% MyST docstrings).
Stretch goal: to support exceptions from the default in some way, using both rST and MyST docstrings.

I see the key goal as a very valuable goal resolving my its own, and the stretch goal as valuable but also likely more complicated to implement and use sustainably.
Ideas to address this
I'm not sure if and how to address these issues. I've opened this issue to brainstorm if we can find reasonable resolutions to these issues - especially if we can find a way to support 100% MyST based docstrings via sphinx.ext.autodoc. A solution that is too complicated and hard to maintain isn't worth developing in my mind.
Support directly in sphinx.ext.autodoc?
Maybe sphinx.ext.autodoc could add support for this directly?

sphix.ext.autodoc should somehow decide if it should emit rST or MyST directives, either by configuration or automatic detection.
sphinx.ext.autodoc could optionally also wrap the raw docstring in a directive like eval-rst based on configuraition

Support by wrapping or patching sphinx.ext.autodoc in another sphinx extension?
Maybe a sphinx extension could be created (myst-autodoc), which would patch or influence sphinx.ext.autodoc somehow. Maybe by wrapping/redefining the provided directives and running rst2myst on the old definition, or maybe patching some functions in sphinx.ext.autodoc?
Your ideas?
I opened this issue hoping to overview the situation and find actionable paths towards resolving this in a good way that is sutainable to maintain and use.

Heya, I'd say this is a duplicate of https://github.com/executablebooks/MyST-Parser/issues/228

Definitely like to see it happen though

@chrisjsewell thanks for helping link things together!
Applying rst2docker on myst isn't good
I considered if rst2myst could be applied to MyST without making changes if its actually ending up parsing myst content. If that would be the case, it could be called on anything autodoc emits. I don't think that is possible though, and would at best lead to only few inconsistencies.
Currently, running rst2myst on myst content would lead to something like this.
-1. Make sure you have successfully completed {ref}`contributing/setup`.
+1. Make sure you have successfully completed \{ref}\`contributing/setup\`.

So whatever resolution we come up with, we must avoid ending up with a mix of myst and rST I think. Well, unless the rST is really MYST, wrapped in an eval-rst directive, which makes it really 100% MyST still.
Due to that, I'm thinking you are correct to say that whats needed is a removal of the rST assumptions used in sphinx.ext.autodoc.

Current understanding of the challenge
sphinx.ext.autodoc doesn't do parsing itself, but constructs rST text involving raw docstrings. This will create a mix of rST and MyST if MyST docstrings are used. Whenever a mix of rST and MyST is created, we can't reasonably disentangle things, so the crux is to avoid that from happening.
To avoid creating a mix of MyST and rST, we can:

transform MyST docstrings into rST before sphinx.ext.autodoc embeds it into its rST output
add support for sphinx.ext.autodoc to construct MyST + raw docstrings
(?) add support for sphinx.ext.autodoc to not construct MyST or rST, but parser generic docutils output or similar

@consideRatio want to give this a go https://sphinx-autodoc2.readthedocs.io/en/latest/quickstart.html#using-markdown-myst-docstrings 😄


rkt: add command to list images in the store.

This adds a new command "rkt images" to display the images in the store.
The -fields option let the user provide a comma separated list of fields to display. Accepted values: "key", "appname", "importtime", "latest".
The -sort option permits to sort the output according to the provided comma separated list of fields. Accepted values: "appname", "importtime".
The ordering is ascending by default but can be configured with the -order=[asc|desc] option.
By default all the available fields ("key", "appname", "importtime", "latest") are displayed sorted by ascending "importtime".
If the image has a version label its written in the app name (with the ":$version" format).
In future additional options can be provided:

show all the labels
define displayed time format (for example human format like "3 days ago").
filter by field value.

Examples:
$ rkt images
KEY                                                                     APP NAME                               IMPORT TIME                             LATEST
sha512-fa1cb92dc276b0f9bedf87981e61ecde93cc16432d2441f23aa006a42bb873df coreos.com/etcd:v2.0.5                 2015-03-01 16:18:38.951 +0100 CET       false
sha512-683438b100a48aead6c37e4f581105713763bb41c3f995ad58a2cc49eb744d68 test                                   2015-03-01 16:53:47.45 +0100 CET        false
sha512-8cf2956f26035ac7d34b78722b8a738fae74acfe29b18db0a92ed44bbcfd2958 coreos.com/rocket/stage1:0.0.1         2015-03-01 17:02:34.636 +0100 CET       false
sha512-d6bb5eb2c30cd12d305192c395f783d7039136a7484f2e07761323a39a0915b6 coreos.com/rocket/stage1:0.0.1         2015-03-10 12:03:26.57 +0100 CET        false

$ rkt images -sort="appname,importtime" -order=desc -fields="importtime,appname,latest"
IMPORT TIME                             APP NAME                              LATEST
2015-03-01 16:53:47.45 +0100 CET        test                                  false
2015-03-10 12:03:26.57 +0100 CET        coreos.com/rocket/stage1:0.0.1        false
2015-03-01 17:02:34.636 +0100 CET       coreos.com/rocket/stage1:0.0.1        false
2015-03-01 16:18:38.951 +0100 CET       coreos.com/etcd:v2.0.5                false

I am a bit concerned that the headings don't match the name of the fields. For example the heading is "IMPORT TIME" but the user has to type "importtime". How do we make this more discoverable?

@philips we can use the same name for the headings and the fields (IMPORTTIME or something else without spaces) and additionally accept them with any case. What do you think?

@philips I updated the PR using the same name for headers and fields (IMPORTTIME and APPNAME) and accepting fields with any case.
Additionally, as it looks very useful, if the image has a version labels its written.

@sgotti @philips Any updates on this feature?

@kelseyhightower @philips I rebased the patch. By now the command is "images", should it become something like "image list" (#649) and wait for subcommands (#632) (as for #603).

@sgotti In the interest of not blocking further I'm going to land this now. We may come back to revisit the exact command framework and invocation (via #632 #649) but let's get it out there so we can kick the tyres. Thanks!!


Post input: textarea outline is out of screen

Phanpy Dev

Screenshot

Thanks for reporting this, this is in fact a UI experiment 😬, to see if the expanded field would be useful to make use of the available space especially for mobile. I know it's looks weird 😂
If it doesn't seem to make any difference, I'll undo this experiment soon 🙏

It's ok! Maybe just style that outline differently so it doesn't leave screen :D

I think it's fixed

@cheeaun
In the light theme the right side of the input still doesn't have outline

In the dark theme outline from the ride side is visible, but only 50% of it's width

@Alex0007 hmm… is that Chrome Android? Or other browser?

@cheeaun this is Phanpy Dev as web app on Android


Location fix

I receive the error ReferenceError: location is not defined when running Mocha tests via Gulp. I'm using jsdom to mock the document and window, which is resulting in the global location being undefined unless I explicitly do global.location = '{}; (or utilize this fix).
Fix of PR #1653
CC @dasilvacontin

Nice! It wasn't necessary to create a new Pull Request though, they get updated when you commit to the same branch. That way it's easier to keep up the conversation/discussion. :)

I foolishly hadn't created a separate branch for the other PR, which is why I've created this new one.

Oh, my bad then.

Doesn't this still give you a ReferenceError, since you are trying to access location first?
Also, commits should be squashed into a single one if they are part of the same change.

I mean, if you check for location first, you still have the same issue in your case.
And if we check by window.location first, window might not exist in scenarios like yours.

Squashed commits, and added better checking so it should work in both cases. In my case, window isn't undefined because I'm using jsdom to mock it. However, it just seems that using jsdom to mock the window doesn't automatically globalize location.

Cool, LGTM! Thanks for the PR :smile:

@jakemmarsh Sorry, something is odd--there are updates to package.json and HISTORY.md in here which shouldn't be.

LGTM and the build works now. If you squash we'll merge. :)

Any update on this fix?

@jakemmarsh able to make the changes requested by @a8m?

@boneskull made the updates and squashed to 1 commit!

LGTM!
Thanks @jakemmarsh

@boneskull Is this ready to merge now?

LGTM. Thanks for the PR, @jakemmarsh. :)

This issue is still present in some wired environments. I ran into it in atom editor's Task today. In the context of atom task, document object is present while location/window.location is not.
I know this might be a corner case here. But how about a more permanent fix, something like checking process and location directly and use whichever is available?

I ran into this issue when running make test in https://github.com/l0b0/insecure-links-highlighter/tree/2d737d25b1ec4b1d820e85a442a5cc731a27c696 after adding a reference to location in highlight.js: exports.protocol = location.protocol;
Relevant output:
docker run --rm insecure-links-highlighter-nodejs /build/node_modules/.bin/mocha test/unit
/project/highlight.js:16
    exports.protocol = location.protocol;
                       ^

ReferenceError: location is not defined
    at /project/highlight.js:16:24
    at Object.<anonymous> (/project/highlight.js:54:2)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/project/test/unit/test.js:4:17)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at /build/node_modules/mocha/lib/mocha.js:231:27
    at Array.forEach (<anonymous>)
    at Mocha.loadFiles (/build/node_modules/mocha/lib/mocha.js:228:14)
    at Mocha.run (/build/node_modules/mocha/lib/mocha.js:536:10)
    at Object.<anonymous> (/build/node_modules/mocha/bin/_mocha:582:18)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Function.Module.runMain (module.js:701:10)
    at startup (bootstrap_node.js:190:16)
    at bootstrap_node.js:662:3


1.1 Tooling Not Compatible with Net46?

I have an EF Core project which I recently upgraded to 1.1. Everything was working fine...until I tried to add a migration. Executing dotnet ef  on the command line now generates an error about not being able to find the ef module/program.
Digging into this a bit I discovered that there was a breaking change in the EF Core 1 -> 1.1 transition involving the tooling. In project.json you have to replace this dependency:
"Microsoft.EntityFrameworkCore.Tools": "1.1.0-preview4-final",
with
"Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview4-final",
Unfortunately...when I do that the package update fails with the error message that this version of the tooling does not support net46.
Which I have to run under because of certain libraries that I'm using.
Here is the entire project.json file:
      "version": "1.0.0-*",

      "dependencies": {
        "ConnellDataCore": "1.0.0-*",
        "Microsoft.AspNetCore.Identity.EntityFrameworkCore": "1.1.0",
        "Microsoft.EntityFrameworkCore": "1.1.0",
        "Microsoft.EntityFrameworkCore.SqlServer": "1.1.0",
        "Microsoft.EntityFrameworkCore.SqlServer.Design": "1.1.0",
        "Microsoft.EntityFrameworkCore.Tools": "1.1.0-preview4-final",
        "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview4-final",
        "Microsoft.Extensions.Configuration": "1.1.0",
        "Microsoft.Extensions.Configuration.Json": "1.1.0",
        "Serilog": "2.3.0"
      },

      "buildOptions": {
        "emitEntryPoint": true,
        "xmlDoc": false
      },

      "frameworks": {
        "net46": {
          "frameworkAssemblies": {
            "System.IO.Compression": "<IP_ADDRESS>"
          }
        }
      },

      "tools": {
      }

I should also point out that the database is defined in a standalone-assembly, so I've had to use the "create a dummy static Program::Main()" trick, along with the "create a temporary context factory" trick.
How do I go about getting back to where I was, being able to add migrations to my EF Core database?

After some further research I found another issue here which I >>think<< solved my problem.
The workaround involved downgrading to 1.0.0.-preview3-final tooling and then running dotnet restore. As well as moving the references to the tooling assemblies from under "dependencies" to under "tooling" (not sure why I had them under dependencies).
Is this still the best workaround at this point?

@markolbert yes, that is the correct setup. This will all get much cleaner when we land on an RTM of the MSBuild tooling for .NET Core.


new project added : Personal Portfolio

Description
This is a Personal Portfolio Project made with React.
Live Demo 👉 https://portfolio-iambijoykar.vercel.app
Features ✨

[x] Responsive Design
[x] Dark / light Mode
[x] Animations
[x] Contact Form

Dependencies 🧱

[x] React
[x] React Router
[x] React Icons
[x] Redux Toolkit
[x] tailwindcss
[x] framer-motion

View 💻

Hey please review this PR 👍

Hey @ianshulx I am participating in Hacktoberfest. Can you add a hacktoberfest-accepted label in this PR?


Automated cherry pick of #816: release: update manifest and helm charts for v1.1.0

Cherry pick of #816 on release-1.1.
#816: release: update manifest and helm charts for v1.1.0
For details on the cherry pick process, see the cherry pick requests page.

/azp run pr-e2e-azure


[doc] classmethod decorator log things while building the docs

Feed back from edna site
WARNING:silx.DEPRECATION:Function RAW_RECORD_MODE is deprecated since silx version 0.7. Use 'DataViews.RAW_RECORD_MODE' instead.
  File "/home/tester/silx/build/lib.linux-x86_64-2.7/silx/utils/property.py", line 52, in __get__
    return classmethod(self.fget).__get__(None, owner)()

Closed by #1662


It is OK to do in this way? (dispatch store)

Hi, i have a questions.
For example i have this:
//Actions
export function getNews () {
   return Api.getNews()
       .then((response) => {
	   if (typeof response !== 'undefined') {
		return MainStore.dispatch(NewsActionCreators.getNews(response));
	   }
     })
     .catch((error) => // some logic);
}

//ActionsCreator
import { NewsConstants } from 'front/constants/NewsConstants';

import { Action } from 'redux-actions';

export function getNews(payload): Action {
	return {
		type: NewsConstants.NEWS_RECEIVED,
		payload,
	};
}

//Component
import * as NewsActions from 'front/actions/NewsActions';

componentDidMount() {
    getNews();
}

const mapStateToProps = (state, ownProps) => {
   return {
       news: state.News.getIn(['news']),
   };
};

const mapDispatchToProps = (dispatch, ownProps) => {
	return {};
};

All works fine. I just want to know It is OK ? Or i need call all actions by mapDispatchToProps inside components?
Thanks :)

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!


I don't know how to earn money on this post, please teach me how to connect on earning coin

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks


Code for moving files from app/ into sub-directories

Code for moving files from app/ into sub-directories leaving few. #212

The conflict looks resolved, thanks! Can you commit the result of execution of the script as you did before?

@gimite Can you please let me know why tests are failing? Looks like some modules are not getting imported. It was working fine earlier though.

@gimite Can you please let me know why tests are failing? Looks like some modules are not getting imported. It was working fine earlier though.

It is because you moved files :) Can you update import lines as well as I mentioned earlier?
Other comments:

Do not move files under app/vendors/:

app/vendors/six.py → app/handlers/six.py

These files should be in app/handlers instead of app/utils:

amp_start.py, send_mail.py

@gimite Can you please let me know why tests are failing? Looks like some modules are not getting imported. It was working fine earlier though.

It is because you moved files :) Can you update import lines as well as I mentioned earlier?

I have updated the import lines to include the path for modules. 3 tests have failed due to special character. Can you please take a look again at Build No. 326 ?

Other comments:

Do not move files under app/vendors/:

app/vendors/six.py → app/handlers/six.py

Have fixed this in the code itself.

These files should be in app/handlers instead of app/utils:

amp_start.py, send_mail.py

Yes, they were present initially due to order of execution, after re-execution of code they are in place.

I agree with @nworden
@gimite I already have * app/chinese_family_name_dict.txt and * app/japanese_name_location_dict.txt moved to app/data directory when the code is executed. What other changes are you requesting for ?

I agree with @nworden
@gimite I already have app/chinese_family_name_dict.txt and app/japanese_name_location_dict.txt moved to app/data directory when the code is executed. What other changes are you requesting for ?

The request here is to create a pull request (maybe a new one) which only move app/chinese_family_name_dict.txt and app/japanese_name_location_dict.txt to app/data but not other files. Since we want to move other files later, not now.

Closing this one for now. Can you create a new pull request with the changes suggested above once ready?

@gimite sure, will create a new PR once the requested changes are ready.


QC checking for Noctua GPAD outputs for gene-centric models

This ticket is to itemize the things we want to check in the Noctua GPAD output of the gene-centric MOD import GO-CAMs.
Please note:
Some of the items listed below will, if necessary, be linked to additional tickets when specific actions are required to correct errors.
Likewise, the granularity of the checklist below should increase as we add even more specific checks.

[ ] Check annotated entity ids

[ ] Check negation

[ ] Check gp2term relations
- https://github.com/geneontology/minerva/issues/390

[ ] Check GO ids

[ ] Check references

[ ] Check evidence

[ ] Check with/from

[ ] Check interacting taxon

[ ] Check date

[ ] Check assigned by

[ ] Check annotation extensions

[ ] Check annotation properties

For reference:
https://github.com/geneontology/pipeline/issues/237
https://github.com/geneontology/pipeline/issues/238

QC checks for MGI mid-late June are here: https://drive.google.com/drive/folders/1-_UtaNNdXZcBGcSGNaWHo43LvNyGOKPk

@vanaukenk do you want to leave this ticket open? Should I move it to the new GPAD project?

Closing this one for now. We may revisit this as other MODS progress further.


Remove system.exit() call in Launcher to re-enable Launcher ITs

Vertx.close() does not have the same effect as System.exit which does not work on travis, ignored a single launcher IT. Closed as no alternative has been found and it is not critical.


Link underline and state colors a11y

Add underline to text link.
Check all colors for a11y against all BGs and update as necessary.

All links should be underlined.
Update colors as follows:
Light theme
Link - normal & hover use Blue (198) 800 --- HSL: (198, 100%, 27%)
• For Clarity NG use: Action-700
Link - clicked use Violet (282) 700 --- HSL: (282, 80%, 36%)
• For Clarity NG use: Secondary-Action-600
Link - visited use Lavender (238) 600 --- HSL: (238, 60%, 52%)
Dark theme
Link - normal & hover use Blue (198) 300 --- HSL:  (198, 100%, 70%)
Link - clicked use Violet (282) 200 --- HSL: (282, 73%, 83%)
Link - visited use Lavender (238) 100 --- HSL: (238, 58%, 90%)
(First value is color token e.g. Color / Hue / Value - second is HSL, NG variables provided where used)

@coryrylan
Do we want to wrap this up in the core theming work?

Closing as part of the color theme work.


Created a rate.Limiter with burst: 1 and limit: 0
Called Allow on the limiter
Set the limit to a non-zero value using SetLimit
Called Wait on the limiter

func main() {
	limiter := rate.NewLimiter(0, 1)

	if !limiter.Allow() {
		// Should be true because the burst is 1
		fmt.Printf("Expected first request to be allowed but wasn't")
	}

	// Set a non-zero limit to start refilling the token bucket
	limiter.SetLimit(100)

	err := limiter.Wait(context.Background())
	if err != nil {
		fmt.Printf("Unexpected error waiting: %v\n", err)
	}
}

https://go.dev/play/p/25EIPtjqvDs
What did you see happen?
Wait returns a non-nil error: rate: Wait(n=1) exceeds limiter's burst 0.
This happens because the burst is decremented when reserveN is called on a Limiter with Limit of 0 which seems strange/incorrect to me.
The code appeared here but the conversation doesn't really reflect the code: the comment says:

The opposite in fact needs to happen: lim.tokens must be reduced by the n consumed tokens?

Which makes sense to me, but I'm not sure how we ended up decrementing the burst. To me the solution to the reported problem (limiters not actually being full) would be to set lim.tokens = burst on the constructor. I don't think burst should be changed by anything except SetBurst
What did you expect to see?
I expected Wait to return a nil error after an appropriate delay!

Related Issues and Documentation

x/time/rate: NewLimiter with burst of 1 and rate of 0 always allows #39984 (closed)
x/time/rate: Limiter allows more configured with multiple goroutines #65508
x/time/rate:  function Limiter.AllowN  generates much more tokens than expected #56263 (closed)
x/time: "bursts" of the RateLimiter don't work as documented #52618 (closed)
x/time/rate: When limit higher burst, Allow() will return true higher burst #39970 (closed)
x/time/rate: token bucket is not initially full #23482
x/time/rate: Limiter allows more than configured #45245 (closed)
x/time/rate: Parallel reservations in Limiter.WaitN are served in parallel, violating rate limit #43858 (closed)
x/time/rate: SetLimit does not update burst #23575 (closed)
x/time/rate:  function Limiter.AllowN  does not work as expected #56145 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

soo

CC @Sajmani

To me the solution to the reported problem (limiters not actually being full) would be to set lim.tokens = burst in the constructor

Having skimmed the code a bit more, I think this would actually make sense. The overflow described in the original issue is specifically guarded against.
If we remove this case entirely, a NewLimiter(0, 1) will never allow (instead of always allowing as before). I think changing the constructor to 👇 should resolve that:
func NewLimiter(r Limit, b int) *Limiter {
	return &Limiter{
		limit:  r,
		burst:  b,
		tokens: float64(b),
	}
}

I can submit a PR with this change

@leesio initializing tokens to the burst size makes sense to me based on the "initially full" phrase in the Limiter doc comment:
// It implements a "token bucket" of size b, initially full and refilled
// at rate r tokens per second.
I also agree that burst should only be set in the constructor and SetBurst.
Honestly I've lost any familiarity I've had with this code, so I'd feel better with a second set of eyes to review any changes and help us make sure we're not making a backwards-incompatible behavioral change.

Cool, glad we're on the same page.
There's no particular rush on my side to get this resolved—we've implemented a workaround on our side. Here's my suggested patch. It's very possible I've done something very wrong, it's my first time using the tooling 😅

Is this fixed by https://cs.opensource.google/go/x/time/+/772484ea383fac83b7da05684a96ae628b251bcd ?

Yes, it should be.
I was under the impression it would be closed automagically but perhaps I messed some annotation up in my change!


Any interest in a Muc Subscription plugin?

I'm building the basics of a muc/subscribe plugin for Stanza, based on Ejabberd's requirements that are described here.
This is still a proposed specification, but would there be any interest in this here?

I'd prefer for there to be a XEP for it, but I'd be interested. I've had to make similar, custom, things to this in the past.

@MattFoley I'd be really interested, did you manage to implement it ?

@MattFoley, did you get the MUC to work? I am trying to implement MUC for few days now, with no luck. Do you have any working code to share?
Please help,
Natan

MUC or MUC/SUB? They're two different things really. Both work well for me.

hi @MattFoley ,
I have a desktop app that implements the XMPP protocol. When I create a multi user chat room the stanza that I am getting (inside the web browser DevTool) is

john1@mhcure/MatriX invites you to the room<EMAIL_ADDRESS>
when I am using either "client.invite" or "client.directInvite", the stanza looks different.
The first issue comes to mind is the "from" attribute on the "message" node. In this case it comes from the room.
When I use either "invite" or "directInvite" the from is coming for the "logged in" user, not from the room.
Do I need to use  a different function? (other than invite,directInvite)
please help,
Natan

I posted an XML but the message broke it, here is after encoding:
<message xmlns='jabber:client'
to='feizhi1@mhcure'
<EMAIL_ADDRESS><archived by='feizhi1@mhcure' id='1544646287076046' xmlns='urn:xmpp:mam:tmp'/>
<stanza-id by='feizhi1@mhcure' id='1544646287076046' xmlns='urn:xmpp:sid:0'/>
<x xmlns='http://jabber.org/protocol/muc#user'>
<invite from='john1@mhcure/MatriX'/></x>
<x<EMAIL_ADDRESS>xmlns='jabber:x:conference'/>
<body xml:lang='en'>john1@mhcure/MatriX invites you to the room<EMAIL_ADDRESS></message>


add support for mesh network info to ParticleDevice

This PR adds support for few properties required to render Control Panel properly.

Self reviewed before merge.


[Refactor] refactor LLVM lib

Why I'm doing:
What I'm doing:
refactor LLVM lib for different platform
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

rebase

@mergify rebase

already pass compiling on ARM machine


Fix Issue#158:  Buttons in payment component should be full width on mobile

This pull request addresses issue #158, where the buttons in the payment component were not displaying at full width on mobile devices. I have implemented a fix to ensure that the buttons now occupy the entire width of the screen when viewed on mobile.

@rolznz  I will remove the unnecessary changes

@sunilsimar Is this issue already solved?


TCP proxy: Get remote address?

I'm fairly new to working with raw TCP transmissions, but I've got a device that sends it what we need to parse. We do need the source ip to differentiate devices though. Is there a way to get the original address, not the one fabio is running on? Currently python's socketserver.BaseRequestHandler.client_address is set to the local address. Is perhaps the PROXY way that ELB uses available?

I think the PROXY protocol is the only way to do this since the TCP proxy just shuffles a bunch of bytes. In that case this is #191 I can have another look at this since the TCP proxy has been around for a while :)

That would be awesome! I'm up for working on a PR, but I've got no idea where to start atm ☺


Page Status infinite-scroll-last is showing on every load?

Can someone tell me if infinite-scroll-last is showing on every page load?
In my case, i am using the template loader-ellips infinite-scroll-request, but infinite-scroll-last is showing every time a page loads.

Thank you for reporting this issue. I'm sorry to see you're having trouble with Infinite Scroll. Could you provide a live URL, or even better a reduced test case? See Submitting Issues in the contributing guidelines.

Hello,
same issue.  the animation is not stopping after last page request.

@lethunder Could you provide a live URL, or even better a reduced test case? See Submitting Issues in the contributing guidelines.

http://<IP_ADDRESS>/  click on the search icon on the top left. After click on search button with selecting any option. Then scroll till the end.

Sorry, I'm not able to view this page.

you can try it now
2017-07-06 16:19 GMT+02:00 David DeSandro<EMAIL_ADDRESS>
Sorry, I'm not able to view this page.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/metafizzy/infinite-scroll/issues/670#issuecomment-313409879,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF7gVEXkODH3N_Bs9BeWROwo3hgTAtruks5sLOzogaJpZM4OFdFG
.

--
Cordialement,
Didier Banlock

Thanks for that. It looks like you're not using the status option, how are you showing & hiding the loader animation?

I'm using it
      var $infiniteScroll = $grid.infiniteScroll({
          path: function () {
              if ($("#events-container .pagination

a.next_page").hasClass("disabled") === false) {
return $("#events-container .pagination
a.next_page:not(disabled)").attr("href");
} else {
$("#loader-wrapper").hide();
return "";
}
},
append: '.grid-item',
outlayer: msnry,
status: '#loader-wrapper',
hideNav: '#events-container .pagination',
checkLastPage: '#events-container .pagination a.next_page',
prefill: true
});
The initial state of the #loader-wrapper container is hidden.
I even try to force the status to hide with
} else {
$("#loader-wrapper").hide();
return "";
}
But no way
2017-07-06 16:56 GMT+02:00 David DeSandro<EMAIL_ADDRESS>
Thanks for that. It looks like you're not using the status option
https://infinite-scroll.com/options.html#status, how are you showing &
hiding the loader animation?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/metafizzy/infinite-scroll/issues/670#issuecomment-313421137,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF7gVFwKCRTguy-88pQKs4uAKBPupWccks5sLPWNgaJpZM4OFdFG
.

--
Cordialement,
Didier Banlock

Sorry, but I'm able to debug this issue. There's too much going on in the page. If you can provide a reduced test case demonstrating this issue, I can better identify what the issue is. See Submitting Issues in the contributing guidelines.

OK. I'll do that. Thanks
Le jeu. 6 juil. 2017 à 17:12, David DeSandro<EMAIL_ADDRESS>a
écrit :

Sorry, but I'm able to debug this issue. There's too much going on in the
page. If you can provide a reduced test case demonstrating this issue,
I can better identify what the issue is. See Submitting Issues in the
contributing guidelines
https://github.com/metafizzy/infinite-scroll/blob/master/.github/contributing.md#submitting-issues
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/metafizzy/infinite-scroll/issues/670#issuecomment-313425957,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF7gVPwk5OoYVpqQV4h_KWYCTVrkwWXtks5sLPlWgaJpZM4OFdFG
.

Hey desandro
check this please
https://codepen.io/anon/pen/KqYKew

actually it no more working at all on my project. i'm not able to load the next page. I have tested every thing.
The path with the class of the next page, function returning next page.

Sorry desandro. it works ! i did a mistake.

Thanks for following up. If anyone runs into a similar issue, please open a new issue.


Allow for multiple filter values to be combined in a comma-separated list

When referring to the JSON API recommendations for filtering it suggests:

Multiple filter values can be combined in a comma-separated list: For example:
GET /comments?filter[post]=1,2 HTTP/1.1

I understand that a similar result is achieved leveraging the Node querystring library as such:
GET /comments?filter[post]=1&filter[post]=2 HTTP/1.1
But in project I am currently working on it is not unusual to query the api with a filter list 100 values long and the redundancy of the same filter[xyz] tag despite easily automated adds a lot of length to a 100 entry long list query.
I've been able bridge the gap between the two types of filter list queries with essentially one line of code in  lib/filter.js See here: https://github.com/st3xupery/jsonapi-server/blob/development/lib/filter.js#L72
The build still passes all tests so there is no interuption to the latter method to doing a list filter query. I'd be happy to write an additional few tests to check that the former method works in all cases of the latter method too.

This is a great suggestion. In all honesty I'm sure we used to have this feature, but it looks like there wasn't test coverage on it and we lost it over a refactor. If we can get a test to ensure we don't lose the feature again, then I'd love to merge it :+1:

Thanks for the help :+1: Great work


[Candidate 4v4 Mt Pinatubo ZH v1] Main Supply Docks offer unequal build space

Observed behavior
Main Supply Docks offer unequal build space.
Expected behavior
All main Supply Docks offer about equal build space for fair conditions.
Screenshots
Has no generous space to build (6)

Has generous space to build (2)

28.06.2024
The terrain has changed, but build spaces are still not equal.

30.06.2024
It still is possible to build GLA Supply at spot 3 shown above. The others are fixed.


onContextMenu problem

Hi,
please check after update from beta.22 to beta.24  does not work.
Thanks

Thanks for reporting, fixed in beta.25
see it working -
https://codesandbox.io/s/github/rrag/react-stockcharts-examples2/tree/master/examples/CandleStickChartWithBollingerBandOverlay


Feat/file upload instrumentation

Description
Adding instrumentation to track status of file upload issues
Fixes #22416
Type of change

Please delete options that are not relevant.

Chore (housekeeping or task changes that don't impact user perception)

How Has This Been Tested?

Manual
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

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

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=608bf61

/ok-to-test sha=c76fbde

/ok-to-test sha=51eb165

Added test plan approved label since this is an instrumentation PR

/ok-to-test sha=6ffb13d


20 tps compatibility for schematic

by alternating the notes played between the lines you could make songs that work with 20tps in survival

i think this would be good as you could make the 20tps tempo compatible with survival/schematica

The .schematic format doesn't support >1.13 blocks, as the format hasn't been updated in years. So sadly this is not possible.

The .schematic format doesn't support >1.13 blocks, as the format hasn't been updated in years. So sadly this is not possible.

you can do it without the >1.13 blocks using pistons

hopefully this makes it possible?

With the pistons it needs to be very specific for it to work. For example, it explains the circumstances required here: https://youtu.be/CejiPtUKeTE?t=609
Anyway, this change would have to heavily alter the current structure for schematic export. Might as well rehaul it entirely if we were to do that.

Using this schematic specification allows for 1.13+ blocks (I've used it up to 1.15.x). It's also the one used by the WorldEdit plugins.

this

both of these setups work


Proposal: Rename this repo

With the introduction of #2 (lister generation), this repo will house more than just client generation. I propose we change the repo name to something more generic -- e.g. controller-tools or codegen -- before it gets too much foot traffic.

cc @ncdc @fabianvf @varshaprasad96

Makes sense. code-generator?

Makes sense. code-generator?

That works for me. @ncdc could you perform the rename?

Will do

Rename done

Make sure you update your git remote settings for your clones


Rigidbodypackets

https://groups.google.com/group/realxtend-dev/browse_thread/thread/c0d4e6c7791e09fc?hl=fi

Interesting read all around, looks great. Not a math wiz so my abilities to comment on it further ends there :)

Sorry, what exactly is different between our and your registrations? I tried cross-checking against that, but it did not catch my eye.

WriteRegStr HKCR "tundra" "" "Tundra_URL_Handler" (NSIS)
vs
WriteRegStr HKCR "tundra" "" "URL:tundra Protocol" (MSI)
I cant really figure out from here http://msdn.microsoft.com/en-us/library/ie/aa767914(v=vs.85).aspx if that URL:{something} Protocol is needed for it to actually work. So I guess just an observation, should overwrite any existing values from the MSI anyways.
And quotes removed around %1 in the command. But those ofc wont hurt there as Tundra knows how to parse them away last time i checked. Also the URL part cant have spaces, but perhaps good to keep there.

I suspect that it its not a required format, but I can make the change to make it look like the demonstrated example, just in case.


Transaction is still a reserved word in 2.4.1

Only applies when previewFeatures = ["transactionApi"] is set:
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

datasource db {
  provider = "sqlite"
  url      = "file:dev.db"
}

generator client {
  provider = "prisma-client-js"
  previewFeatures = ["transactionApi"]
}

model Role {
  id   Int     @default(autoincrement()) @id
  name String
  users Transaction[]
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

model Transaction {
  id        Int      @default(autoincrement()) @id
  email     String
  password  String
  name      String?
  roleId    Int
  role      Role    @relation(fields: [roleId], references: [id])
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

I can confirm this. Prisma generate also fails:

Yep, that's the issue I described.

Thank you for the report! It seems we forgot to remove the reserved keyword from our code.

The fix will be shipped in next 2.5.0 release next week.


Universal Reader having issues with anything but image paths

Hi there, forewarning that I have very little experience with image processing and Torch. I have not touched the configuration files at the moment. Currently trying to pass URLs to the analyzer, but I keep running into the following error:
"File \"C:\\Users\\win1\\AppData\\Local\\Programs\\Python\\Python312\\Lib\\site-packages\\torchvision\\transforms\\_functional_tensor.py\", line 926, in normalize
if std.ndim == 1:
std = std.view(-1, 1, 1)
return tensor.sub_(mean).div_(std)
~~~~~~~~~~~ <--- HERE
RuntimeError: The size of tensor a (4) must match the size of tensor b (3) at non-singleton dimension 1"

Replacing the configuration variables with their values for bath_size, fix_img_size, return_img_data, and include_tensors, this is my current endpoint:
@app.post("/predict/")
async def predict(url: str):
    try:
        response = analyzer.run(
            image_source=url,
            batch_size=8,
            fix_img_size=True,
            return_img_data=False,
            include_tensors=True,
            path_output=None,
        )

Here's an example output:
{"asctime": "2024-08-16 14:57:30,765", "levelname": "INFO", "message": "Running FaceAnalyzer", "taskName": "Task-12"}
{"asctime": "2024-08-16 14:57:30,766", "levelname": "INFO", "message": "Reading image", "taskName": "Task-12", "input": "https://image-cdn.essentiallysports.com/wp-content/uploads/20200606234527/the-rock-dwayne-johnson-muscles-740x662.png"}
{"asctime": "2024-08-16 14:57:33,463", "levelname": "INFO", "message": "Detecting faces", "taskName": "Task-12"}
INFO:     <IP_ADDRESS>:63490 - "POST /predict/?url=https%3A%2F%2Fimage-cdn.essentiallysports.com%2Fwp-content%2Fuploads%2F20200606234527%2Fthe-rock-dwayne-johnson-muscles-740x662.png HTTP/1.1" 500 Internal Server Error

I also tried to pass a PIL Image.Image object directly (again, I need to first convert this into RGB form which makes sense, the same dimension-matching error pops up if I do not), but despite the type matching, it appears that the detector is not finding any faces, i.e.:
@app.post("/predict/")
async def predict(file: UploadFile = File(...)):
    try:
        image = Image.open(BytesIO(await file.read())).convert('RGB')

        response = analyzer.run(
            image_source=image,
            batch_size=8,
            fix_img_size=True,
            return_img_data=False,
            include_tensors=True,
            path_output=None,
        )

With output:
{"asctime": "2024-08-16 15:21:51,393", "levelname": "INFO", "message": "Running FaceAnalyzer", "taskName": "Task-7"}
{"asctime": "2024-08-16 15:21:51,393", "levelname": "INFO", "message": "Reading image", "taskName": "Task-7", "input": "<PIL.Image.Image image mode=RGB size=978x605 at 0x2446A6248C0>"}
{"asctime": "2024-08-16 15:21:51,678", "levelname": "INFO", "message": "Detecting faces", "taskName": "Task-7"}
{"asctime": "2024-08-16 15:22:00,407", "levelname": "INFO", "message": "Number of faces: 0", "taskName": "Task-7"}
Response(faces=[], version='0.5.0')

Would appreciate any help! The reader works perfectly fine if an image path is given.

Thank you for the detailed report! The runtime error seems to stem from mismatched image channels, likely due to an alpha channel (RGBA) in some inputs. While you correctly convert PIL images to RGB, this might not be happening for images loaded from URLs. I’ve updated the read_pil_image and read_numpy_array methods in version 0.5.1 to ensure all inputs are properly converted to RGB before processing, which should resolve this issue.
Regarding the detector not finding faces: This could be due to the current configuration of the RetinaFace detector postprocessor. I suggest trying different settings to better match your use case. Specifically, you might want to adjust the following parameters in your configuration file:

confidence_threshold: Increase it to filter out low-confidence detections.
score_threshold: Experiment with lowering it to allow detections with lower confidence scores.
expand_box_ratio: Increase it slightly if faces near the image edges are being missed.

These adjustments can help fine-tune detection results. Please update to version 0.5.1 and let me know if these changes help or if you need further guidance!


refactor(connlib): don't rely on DNS when reconnecting to portal

Currently, connlib uses the feature of "known hosts" to provide DNS functionality for some domains even without any network connectivity. This is primarily used to ensure that when we reconnect to the portal, we can resolve the domain name which allows us to then create network connections.
With recent changes to how our phoenix-channel implementation works, this is actually no longer necessary. Currently, we re-resolve the domain every time we connect, even though we already resolved them when connecting to it for the first time. This step is unnecessary and we can simply directly use the previously resolved IP addresses for the portal domain.

How did you solve the verification of the SSL CN?

That is up for the TLS library to do, we create a TCP socket to a certain IP and only layer TLS on top of that. In fact, the TLS library is entirely agnostic the underlying stream that it is reading from and writing to. As long as whoever sits on the other side of the stream can provide a valid certificate for the domain we are trying to establish a connection to, this will work.


RHOAIENG-13014 - Rewrite Verify RHODS Operator Logs test

JIRA: RHOAIENG-13014

@mattmahoneyrh Yes, it was tested, see job/rhoai/job/2.13/job/selfmanaged/job/cli/job/aws/job/rhoai-tier3/ for last few runs. All of them passed with this test.

Approved... but there are conflicts that will need to be resolved prior to merge.


UI should rely on CLI commands

Currently most of the UI stuff does not rely on CLI, as it was supposed to be.
See #151

Yeah.... I've not done such a good job with that...

Another thing, I'd like to consider ways to improve upon the CLI command setup.
For instance, you can search in the CLI and see things, but these serve no function when automating tasks. I wonder how we can remedy that?
Some ideas:

Caching most recent search and having commands that work off of that
Storing the return value of commands into variables that can be referenced by commands

Hi

Closing as 3.X will address this with its new design philosophy.
The core module will provide all common api-like features and the UI module will provide a both a UI and a CLI that tie back into the core. This way the UI is not limited by the CLI design.


#100 azure terraform with docker

A multi region solution for deploying the db1000n container on Azure Container Group

@Amet13 Done


[engsys] fix: Dont skip code formatting validation when pylint is disabled.

Description
This pull request

Updates the pipeline definition run_black.yml to prevent it from getting skipped when Skip.Pylint is set
Adds black = false to all pyproject.tomls that had pylint = false, to preserve the behavior that existed before this PR

Background
The pipeline definition for code formatting will skip format validation if a package doesn't run pylint.
https://github.com/Azure/azure-sdk-for-python/blob/c816234b5bb722cc8007b1405b4f76b99dd0a602/eng/pipelines/templates/steps/run_black.yml#L26
This skip seems be longstanding (~2 years), which meant that disabling pylint for a package also disabled formatting validation.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

cc: @l0lawrence , @kristapratico

API change check
API changes are not detected in this pull request.

@kdestin Thank you for the PR!
Given the amount of different service directories that this PR, please do not merge or add additional commits.
Can you please push this as a single commit to a branch in azure/azure-sdk-for-python?
I will have an admin merge it to avoid triggering the entire world worth of builds.

@kdestin Thank you for the PR!
Given the amount of different service directories that this PR, please do not merge or add additional commits.
Can you please push this as a single commit to a branch in azure/azure-sdk-for-python, then let me know the name?
I will have an admin merge it to avoid triggering the entire world worth of builds.

@scbedd
Made a new branch, and I'll squash merge into that if that works. And you can take it from there?

Given the amount of different service directories that this PR, please do not merge or add additional commits.
Can you please push this as a single commit to a branch in azure/azure-sdk-for-python, then let me know the name?
I will have an admin merge it to avoid triggering the entire world worth of builds.

@scbedd
Made a new branch, and I'll squash merge into that if that works. And you can take it from there?

yep exactly! Just tell me which branch in repo!

Given the amount of different service directories that this PR, please do not merge or add additional commits.
Can you please push this as a single commit to a branch in azure/azure-sdk-for-python, then let me know the name?
I will have an admin merge it to avoid triggering the entire world worth of builds.

Made a new branch, and I'll squash merge into that if that works. And you can take it from there?

yep exactly! Just tell me which branch in repo!

@scbedd : https://github.com/Azure/azure-sdk-for-python/tree/dont-skip-black-when-pylint-disabled


About Rigidity masks

Hi @anuragranj !
I am training the model using all the pre-trained models that you published online. However, I do not get proper rigidity masks. Do you know why this is happening?  As I understand, Rigidity masks are the subtraction of rigid flow with flow generated by the flownet with some threshold(I havent chaned the code at all). Below is the picture:

Also, Could you share the optimizer checkpoint at the time of your training, so that I could visualize all the results at once?

Can you share the hyperparameters you are using for training? Also, are the depth, camera and flow networks trained well?

Thankyou @anuragranj ! Unfortunately, I cannot share with you immediately as I am not at my desk. However, I will do it as soon. If possible, meanwhile, could you share your tensorboard events file wherein I can see the rigid masks, please.

Also, are the depth, camera and flow networks trained well?

I have plugged in your pretrained depth, camera, and flow models. So, Isnt it already trained?

I don't have access to tensorboard event files. Could  you try the following hyperparameters? This worked for me.
python3 train.py DATA_PATH --sequence-length 5 --dispnet DispResNet6 \
--posenet PoseNetB6 --masknet MaskNet6 --flownet Back2Future --pretrained-disp \
pretrained/dispnet_model_best.pth.tar --pretrained-pose pretrained/posenet_model_best.pth.tar \
--pretrained-mask pretrained/masknet_model_best.pth.tar --pretrained-flow \
pretrained/flownet_model_best.pth.tar -b4 -m0.02 -pf 0.5 -pc 1.0 -s0.2 -c0.3 \
--epoch-size 100 --log-output -f 0 --nlevels 6 --lr 1e-6 -wssim 0.5 --with-flow-gt \
--with-depth-gt --epochs 100 --fix-flownet --fix-dispnet --fix-posenet \
--smoothness-type edgeaware --THRESH 0.999

Hi @anuragranj !
I used the default THRESH value before.
However, I ran test_flow.py script with the same THRESH value of 0.999. I expect the rigidity mask to be as shown in the paper:

However, while running the command:
`python test_flow.py  --pretrained-disp /cdtemp/ezorfa/cc-master/checkpoints/dispnet_k.pth.tar  --pretrained-pose /cdtemp/ezorfa/cc-master/checkpoints/posenet.pth.tar --pretrained-flow /cdtemp/ezorfa/cc-master/checkpoints/back2future.pth.tar   --pretrained-mask /cdtemp/ezorfa/cc-master/checkpoints/masknet.pth.tar --THRESH 0.999 --kitti-dir kitti2015/dataset --output-dir kitti2015/output/'  I get outputs of the rigidity mask like:

How can I get the mask outputs like the one described in the paper?
Thankyou!

@anuragranj  Is such a mask expected when camera motion is present? Also, could you please check the parameter values used in the above command test_flow.py and tell how to reproduce rigidity_flow_census masks.  I am only interested to find the moving objects by making use of rigidity flow and optical flow obtained by flownet.
Thankyou!

To get the masks, you should be running test_mask.py with default  --THRESH values. The test_flow.py functions outputs the masks that are optimal for best flow, but not for best masks.

Okay, Could you please assert if such masks like the picture above are expected?

Masks like Figure 1. in the paper are expected if you use test_mask.py with default --THRESH, which is .94.

Hmm. I am testing now. Thankyou for the guidance.

The visualization corresponds to the following line:
https://github.com/anuragranj/cc/blob/master/test_mask.py#L173
It is saved as 'val Rigidity Mask Census' in tensorboard events.

yeah, I spotted that and made my own script to vizualize only moving objects but somehow dint see the file test_mask.py existing. Sorry about that and will come back to you.


Background wihout image

When i use this library without background image i can not set text in all direction i mean when i move text near top,bottom edges it is automatically scrolling that text to center how can i solve this issue.Please help me to get out from this.

This is the expected behaviour of the library. Whenever we drag the View outside the image boundary. It will move it to the centre.

@DroidMagician you could achieve what you want creating a empty bitmap like so:
val emptyBitmap = Bitmap.createBitmap(editor_main.width, editor_main.height, Bitmap.Config.ARGB_8888)
photoEditorView?.source?.setImageBitmap(emptyBitmap)
I'm using this on our app and it's working perfectly.

@DroidMagician Will this solve your problem? if so, try to close the issue.
Thanks


Events without payloads

Sometimes you just want to publish a event without any any payload. Currently it's possible to use the createEventDefinition without the type declaration. However, the event creator method still forces you to pass in some dummy payload.
const creator = createEventDefinition()("eventname");
const event = creator({});

This PR solves this problem by introducing the function createEmptyEventDefinition which sets the generic parameter to undefined. Not sure whether a generic parameter should be undefined but at least this way it's obvious that the payload is empty and also the IDE will highlight an error if you type myevent.payload.property.
const creator = createEmptyEventDefinition()("eventname");
const event = creator();

Another option would be to introduce another event type without the payload property. But that would be too much overhead to maintain...
@ryardley What's your view on this?

Thanks for the PR. Have you thought of doing this?
const event = createEventDefinition()("foo")(undefined);
event.payload; // undefined

I am just wondering if the overhead of having to maintain a second function is worth it.

What about if we try and merge it to a single function:
export function createEventDefinition
(
  options?: EventDefinitionOptions
 | TestPredicateFn

) {
  return <T extends string>(type: T) => {
    const eventCreator = (payload?: P):{type:T, payload:P} => {

      // Allow runtime payload checking for plain JavaScript usage
      if (options && payload) {
        const testFn = typeof options === "function" ? options : options.test;
        if (testFn && !testFn(payload)) {
          showWarning(
            `${JSON.stringify(payload)} does not match expected payload.`
          );
        }
      }

      return {
        type,
        payload:payload as P
      };
    };
    eventCreator.eventType = type;
    eventCreator.toString = () => type; // allow String coercion to deliver the eventType
    return eventCreator;
  };
}

const event = createEventDefinition()("foo")();
event.payload; // undefined

const event2 = createEventDefinition<{foo:string, bar:number}>()("foo")({foo:'asdas', bar:4});
event2.payload; // undefined

Ahh just realised the above wont work with this :( :
const event = createEventDefinition<{foo:string, bar:number}>()("foo")();

so there is this option still not perfect:
export function createEventDefinition
(
  options?: EventDefinitionOptions
 | TestPredicateFn

) {
  return <T extends string>(type: T) => {

    function eventCreator(payload:void): {type:T}
    function eventCreator(payload:P): {type:T, payload:P}

    function eventCreator (payload: P | void) {

      // Allow runtime payload checking for plain JavaScript usage
      if (options && payload) {
        const testFn = typeof options === "function" ? options : options.test;
        if (testFn && !testFn(payload)) {
          showWarning(
            `${JSON.stringify(payload)} does not match expected payload.`
          );
        }
      }

      if(payload === undefined){
        return {type}
      }

      return {
        type,
        payload
      };
    };
    eventCreator.eventType = type;
    eventCreator.toString = () => type; // allow String coercion to deliver the eventType
    return eventCreator;
  };
}

const event = createEventDefinition()("foo")();
event.payload; // Property 'payload' does not exist on type '{ type: "foo"; }'

const event2 = createEventDefinition<{foo:string, bar:number}>()("foo")();
event2.payload; // Property 'payload' does not exist on type '{ type: "foo"; }'

const event3 = createEventDefinition<{foo:string, bar:number}>()("foo")({foo:'asdasd', bar: 123});
event3.payload; // {foo:'asdasd', bar: 123}

So as this does look hard to achieve 100% without a separate function we could perhaps wrap the original one?
export function createEmptyEventDefinition(options?: EventDefinitionOptions<undefined> | TestPredicateFn<undefined>) {
  const innerTypeCreator = createEventDefinition<undefined>(options);
  return <T extends string>(type: T) => {
    const eventCreator = innerTypeCreator(type);
    return () => eventCreator(undefined);
  }
}

Actually if we use void it works:
export function createEventDefinition
(
  options?: EventDefinitionOptions
 | TestPredicateFn

) {
  return <T extends string>(type: T) => {

    function eventCreator (payload: P) {

      // Allow runtime payload checking for plain JavaScript usage
      if (options && payload) {
        const testFn = typeof options === "function" ? options : options.test;
        if (testFn && !testFn(payload)) {
          showWarning(
            `${JSON.stringify(payload)} does not match expected payload.`
          );
        }
      }

      return {
        type,
        payload
      };
    };
    eventCreator.eventType = type;
    eventCreator.toString = () => type; // allow String coercion to deliver the eventType
    return eventCreator;
  };
}

const event = createEventDefinition()("foo")();
event.payload; // Property 'payload' does not exist on type '{ type: "foo"; }'

const event2 = createEventDefinition<{foo:string, bar:number}>()("foo")();
event2.payload; // Property 'payload' does not exist on type '{ type: "foo"; }'

const event3 = createEventDefinition<{foo:string, bar:number}>()("foo")({foo:'asdasd', bar: 123});
event3.payload; // {foo:'asdasd', bar: 123}

Closing this in favour of https://github.com/ryardley/ts-bus/pull/25


Update cmd usage description

Closes #218

Is there a traditional Go CLI syntax for specifying optional arguments?

Wrong branch. :joy:


Need to provide defaultDate in yyyymmdd format

The minor issue I have now is that I would love to be able to automatically load my db dates into the date picker (unfortunately they are stored in yyyymmdd format, as strings). I see that while your control will allow for the alternate format to send to the server, it will load only default dates in the Date.parse() format indicated.
Am I missing some other way to do this (see ex below) or should I handle my yyyymmdd date via php beforehand to match your supported format?
Thanks!
`<input class=flatpickr
data-dateFormat="Ymd"
data-altFormat="d/m/y"
data-altinput=true
data-defaultDate="20140120"
placeholder="Ingrese fecha"

`

or should I handle my yyyymmdd date via php beforehand to match your supported format

Yes, that's how I do in my project. Default javascript date parser is not that flexible to initialize date in different formats. So, it's much more easy to just format it in php before writing it into the html, with the yyyy-mm-dd format.
:+1:

Correct, Rafael, I've seen that too (in other datepickers as well). I've come up with the php solution below. Still, it's good that on returning to the server I can send as Ymd.  Thanks!
$value   = date('Y/m/d',strtotime($value));


getConfidenceScore returns NaN

We are running caffe-android-lib on a wide variety of Android phones, and we are seeing getConfidenceScore periodically return NaN.  We've traced it back far enough to know that the float vector returned by Forward has NaN values.  After it returns NaN, it continues to return NaN regardless of the image we send to Caffe until the Android app is restarted.  It occurs much more often on certain phones.
I don't think it is an issue with our Caffe model, as we have tried several different ones all having the same behavior.  Images do not consistently score NaN.  If it scores NaN, we re-score it after restarting the app, and it scores correctly.

Did try to run your model on desktop?

Yes, we've done a lot of testing on desktop and haven't seen similar issues.  We've mainly used OpenBLAS on desktop and Eigen on Android, so that could be a factor.

I would recommend you to use OpenBLAS on both platforms. And I'm actually planning to remove the support of Eigen in my forked caffe.

I'll give it a try again.  The last time I tried it, OpenBLAS was much slower then Eigen.  With the model I was using, Eigen was taking less then half a second and OpenBLAS was taking around 10 seconds to predict a single image.  Any tips on how to speed that up?

Hmm... That's a little bit strange. According to https://github.com/sh1r0/caffe-android-lib/issues/27, there should not have a such big difference of performance between 2 libraries. Could you try to benchmark caffenet on your devices over 2 libraries?
Thanks.

Hi
I have had the same problem (inconsistent output from the NN) so was advised to switch from Eigen to OpenBLAS.
I evaluated on GoogLeNet with HTC One with 4 threads. I found that OpenBLAS is about 4 times slower than Eigen.
-----

HTC One with Eigen:
20 iterations:
Time taken: 197025.0
=> 9.8 sec to process 1 image

----

HTC One with OpenBLAS:
20 iterations:
Time taken: 821187.0
=> 41 sec to process 1 image

@woodthom2 With ANDROID_ABI="armeabi", OpenBLAS is built with single thread and it's actually for armv5.

Thank you.
When I switch to
export ANDROID_ABI="armeabi-v7a-hard-softfp with NEON"

I get this output:
sources/cxx-stl/gnu-libstdc++/4.9/include/cstddef:44:28: fatal error: bits/c++config.h: No such file or directory
 #include <bits/c++config.h>
                            ^
compilation terminated.

Which ANDROID_ABI value do you recommend to use?

I think armeabi-v7a-hard-softfp with NEON is the right one for your case. Sorry, I did not have that error before. Please check your building environment, i.e., ndk, cmake, etc.

I obtain the same error when I change from "arm64-v8a" to "armeabi-v7a-hard-softfp with NEON". On arm64-v8a setup compile, linking and execute, works fine.

CMakeFiles/boost_atomic.dir/build.make:54: recipe for target 'CMakeFiles/boost_atomic.dir/boost_1_56_0/libs/atomic/src/lockpool.cpp.o' failed
make[2]: *** [CMakeFiles/boost_atomic.dir/boost_1_56_0/libs/atomic/src/lockpool.cpp.o] Error 1

@hpsaturn As I commented before, I think your problem was caused by cmake, please upgrade your cmake to at least v3.5.2. Thanks.

Yes, when I changed NDK to r11c, "armeabi-v7a-hard-softfp with NEON" build works!
I have the same problem.

@sh1r0 getConfidenceScore periodically return NaN.


Minor doc fixes

The formatting for knnQueryBatch is messed up because of a missing
newline: https://searchivarius.github.io/nmslib/api.html#nmslib.dist.FloatIndex.knnQueryBatch . Also listed out values for the DistType/DataType enums

Thanks!


Update dev to sw_dev

Added support for DRAMSim3 memory system
Removing dramsim2/3 submodules
Moving VCS timeouts to testbench makefiles
Skip zero DRAM entries in NBF (quicker restore time for checkpoints)

Holding off until #596


cook shopping-list segfaults on Ubuntu 21.04

Running Pop_OS! 21.04 and invoking cook shopping-list <some cook file> segfaults every time.

Hi @cmdln thanks for reporting. I wan't able to reproduce it on my Ubuntu (20.04), but I'll try to install a newer one and check again. Would it be possible to share an example recipe file which reproduces that behaviour? Many thanks!

Add @agave{0.25%cup} to the hot @water{0.5%cup} in a #small bowl{} and allow to dissolve. Stir in the @yeast packet{1} and allow to sit until a layer of foam forms on top.

In a #large mixing bowl{}, combine the yeast starter with the @spent grain{3%cups}, @salt{1%tsp}, and @beer{1%cup}. I like to use my homebrew but any beer that you like will do.

Add the @rye flour{1%cup}, @whole wheat flour{1%cup}, and @aquafaba{0.25%cup}.

Add the @all purpose flour{3%cup} a half cup at a time, mixing thoroughly.

I've attached my aisle.conf, too, which I modified a little from the one cook seed generated. Do I need to make sure ingredients are all in aisle.conf before trying to generate a shopping list?
aisle.zip

Great, thanks for sharing

I have the same problem, also Pop_OS. I have made no changes to aisle.conf and the seg fault occurs with seed recipes (eg. Easy Pancackes.cook).
Thanks for a great tool!

Sorry, took me a while get back to it. I can confirm that I can reproduce the bug on the latest Pop_OS.
Essentially SIGSEGV happens here https://github.com/cooklang/CookCLI/blob/main/Sources/Catalog/ConfigLoader.swift#L43 while getting user's home directory.
Here's the debugger output:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7f14844 in __GI___nss_readline (poffset=<optimized out>, len=<optimized out>, buf=<optimized out>, fp=<optimized out>) at nss_readline.c:68
68	nss_readline.c: No such file or directory.
(gdb) bt
#0  0x00007ffff7f14844 in __GI___nss_readline (poffset=<optimized out>, len=<optimized out>,
    buf=<optimized out>, fp=<optimized out>) at nss_readline.c:68
#1  __GI___nss_readline (fp=fp@entry=0x7ffff7c862a0,
    buf=buf@entry=0x3709810 "root:x:0:0:root:/root:/bin/bash\n", len=len@entry=1024,
    poffset=poffset@entry=0x7fffffffd660) at nss_readline.c:26
#2  0x00007ffff7f1a4e2 in internal_getent (errnop=<optimized out>, buflen=<optimized out>,
    buffer=<optimized out>, result=<optimized out>, stream=<optimized out>) at nss_files/files-XXX.c:124
#3  __GI__nss_files_getpwuid_r (uid=<optimized out>, result=0x36f3220 <resbuf>,
    buffer=0x3709810 "root:x:0:0:root:/root:/bin/bash\n", buflen=1024, errnop=0x36f58f0)
    at nss_files/files-pwd.c:40
#4  0x00000000010245c5 in getpwuid_r ()
#5  0x0000000001023f98 in getpwuid ()
#6  0x0000000000c3a6e0 in CFCopyUserName ()
#7  0x0000000000777cea in $s10Foundation10NSUserNameSSyF ()
#8  0x00000000006b7179 in $s10Foundation11FileManagerC27homeDirectoryForCurrentUserAA3URLVvg ()
#9  0x000000000051ac7a in $s7Catalog12ConfigLoaderC04findB4File33_FBEF48852F8E4F39368408162129A1CDLL4type_SSSgSS_AGtF (type=..., provided=..., self=...) at /src/Sources/Catalog/ConfigLoader.swift:43
#10 0x000000000051a68d in $s7Catalog12ConfigLoaderC4load4type10referenced11CookInSwift0gB0CSgSS_SSSgtKF (
    type=..., referenced=..., self=...) at /src/Sources/Catalog/ConfigLoader.swift:22
#11 0x000000000053addf in $s7CookCLI0A0V12ShoppingListV3runyyKF (self=...)
    at /src/Sources/CookCLI/Commands/ShoppingList.swift:50
#12 0x000000000053eff3 in $s7CookCLI0A0V12ShoppingListV14ArgumentParser15ParsableCommandAafGP3runyyKFTW ()
    at /src/Sources/CookCLI/Commands/ShoppingList.swift:37
#13 0x000000000045c4e1 in $s14ArgumentParser15ParsableCommandPAAE4mainyySaySSGSgFZ (arguments=..., self=...)
    at /src/.build/checkouts/swift-argument-parser/Sources/ArgumentParser/Parsable Types/ParsableCommand.swift:95
#14 0x000000000045c627 in $s14ArgumentParser15ParsableCommandPAAE4mainyyFZ (self=...)
    at /src/.build/checkouts/swift-argument-parser/Sources/ArgumentParser/Parsable Types/ParsableCommand.swift:105
#15 0x000000000054bc2e in main () at /src/Sources/CookCLI/main.swift:9
(gdb) q

Also strace output:
getrandom("\x9a\x97\xcf\x66\x86\x35\x39\x91", 8, GRND_NONBLOCK) = 8
mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f67ed2c6000
openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=2694, ...}, AT_EMPTY_PATH) = 0
lseek(3, 0, SEEK_SET)                   = 0
read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 2694
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xe5} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)

glibc version:
 ldd --version ldd
ldd (Ubuntu GLIBC 2.34-0ubuntu3) 2.34

Similar issue reported for statically compiled binaries which use nss library after update to glibc version 2.32+ .
I'll try to update glibc in a Docker image I use and check if it can fix it and it still works for older systems too. If not probably need to find another way to get home directory.


♻  Removing dead code, cleaning Consumers context

Co-authored-by: Anthony Accomazzo<EMAIL_ADDRESS>

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#103  👈
#102
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RTLS and the rest of your teammates on  Graphite


Server 2022

Is there a reason Server 2022 is not listed? please add it if appropriate

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

ID: 2a149789-67c1-e126-129b-6e77e831086d
Version Independent ID: dd04d845-c098-46e5-fedf-92ba8fc64615
Content: Trusted Platform Module Technology Overview (Windows) - Windows security
Content Source: windows/security/information-protection/tpm/trusted-platform-module-overview.md
Product: windows-client
Technology: itpro-security
GitHub Login: @Dansimp
Microsoft Alias: dansimp

Thanks @DeanGross for the feedback. You can generally assume that if something applies to Server 2016/2019, it probably also applies to Server 2022. Thanks to @RAJU2529 for checking (reference) and making the edit! This issue will automatically close when I merge the pull request, and then the change should publish soon (could be this afternoon, but with the US holidays may not be until next week at this point!)

Thanks for the update, I have run into a lot of issues over the years when I have made assumptions like that, so I always like to get explicit confirmation