[FIXED JENKINS-25865] Provision machines with NORMAL mode

Fixes JENKINS-25865

This really should be configurable!
Since I'm already working on some major changes in the config GUI (using ssh-credentials resp. credentials plugin wherever possible), I can take care of that.

What is the usecase for explicit configuration?

It means: Do not use this slaves for anything else but the speciefied labels.
In other words, it disables matching jobs without a Label-Expression to this slave.

Right, I have just realized it is explicitly configured for DumbSlaves as well. That would work for me. I prefer NORMAL mode to be the default, same as for DumbSlave.

If that's the case whith a none-empty label, then this would be a bug of
the generic job/executor mather (Perhaps you left the label empty? -
this is not validated in this plugin yet - of course it will be if I
touch the code).
NORMAL:

Label is optional.
EXPLICIT:
Label is mandatory - not shure what happens if slave label is empty.

Cheers
-Fritz
On 02/09/2015 10:20 AM, Oliver Gondža wrote:

Right, I have just realized it is explicitly configured for |DumbSlave|s
as well. That would work for me. I prefer |NORMAL| mode to be the
default, same as for |DumbSlave|.
—
Reply to this email directly or view it on GitHub
https://github.com/jenkinsci/jclouds-plugin/pull/80#issuecomment-73478283.

Agree, I do not mind fixing this myself.


[TypeScript] insomnia-inso

(not 100% done, but absolutely ready to start looking at)

although making separate branches is much nicer for GitHub/review purposes, only those packages that have no other dependencies from the project will work since they consume each others' types.  For example, insomnia-inso consumes types from insomnia-testing.  If I pull those changes out, it will error because it's expecting types.  For that reason I've pushed a branch ts/first7 that contains all of these exact same commits, but stacked.  If you want to run something, your best bet will be to do so from there.  I'll then make sure that everything is always symmetrical between the two.


Items are not shown on listing when price facet is chosen

On listing when price facet is chosen, facets are showing correct values, but no products are served.
Go to https://catalyst-demo.site/mens/?minPrice=11, facets are shown indicating that products should be shown, but no products are shown.

Thanks for reporting! I will take a look 👀!

Hi, are there any updates for this?

Hi @mhuretski!
I looked into it and it's a known GraphQL API issue that we are currently investigating. Unfortunately I don't have any timeline, but will update this issue when it's been fixed.


feat(HACBS-2401): Remove label-check task

Description
As part of HACBS-2401, the label-check is no longer included in the build pipelines. This change updates the tests to no longer check for its presence.
Issue ticket number and link
https://issues.redhat.com/browse/HACBS-2401
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

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

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test redhat-appstudio-e2e

/retest

/test redhat-appstudio-e2e


force packaging versions

Signed-off-by: Ryan Cook<EMAIL_ADDRESS>Force set versions.
Output RHEL 8
Total                                                          79 MB/s |  36 MB     00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                      1/1
  Installing       : microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.noarch   1/2
  Running scriptlet: microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.noarch   1/2
  Installing       : microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.x86_64           2/2
  Running scriptlet: microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.x86_64           2/2
  Running scriptlet: microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.noarch   2/2
  Running scriptlet: microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.x86_64           2/2
  Verifying        : microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.x86_64           1/2
  Verifying        : microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.noarch   2/2
Installed products updated.

Installed:
  microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.x86_64
  microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.el8.noarch

Complete!

Output Fedora 35
Importing GPG key 0x26DF568C:
 Userid     : "cooktheryan_microshift (None<EMAIL_ADDRESS> Fingerprint: 6075 9B78 E731 4E58 7E4F E878 AA94 B3E7 26DF 568C
 From       : https://download.copr.fedorainfracloud.org/results/cooktheryan/microshift/pubkey.gpg
Is this ok [y/N]: y
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Installing       : microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.noarch                         1/2
  Running scriptlet: microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.noarch                         1/2
libsemanage.semanage_direct_install_info: A higher priority microshift module exists at priority 400 and will override the module currently being installed at priority 200.

  Installing       : microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.x86_64                                 2/2
  Running scriptlet: microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.x86_64                                 2/2
Removed /etc/systemd/system/multi-user.target.wants/microshift.service.

  Running scriptlet: microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.noarch                         2/2
  Running scriptlet: microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.x86_64                                 2/2
  Verifying        : microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.x86_64                                 1/2
  Verifying        : microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.noarch                         2/2

Installed:
  microshift-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.x86_64
  microshift-selinux-4.8.0-2022_01_04_175420_24_g8a3819ee.fc35.noarch

Complete!

Closes #473

Awesome ryan!!! :-) thanks for looking on this.

works for me, but still there is some scriptlet error, the selinux warning goes away
@cooktheryan is there a way to check if the module was installed?

@mangelajo do semodule --list | grep microshift

@mangelajo did you have crio installed when you ran the above? I am not getting the scriptlet error on RHEL 8

semodule --list | grep microshift
microshift

It's there.
I had crio installed. not sure what's going on but it's an improvement so let's merge IMHO.
I'll see if there's some way to debug the rpm install and figure that out.

/lgtm


[ION-1300] Getting this error a lot for my lambda: "it does not seem like sst dev is running"

https://github.com/sst/sst/issues/3885
ION-1300

I managed to fix this. In my case, I had to delete pyproject.toml from my parent directory. This was my setup:
root
- pyproject.toml     # this is what I had to delete
- lambdas folder
  - sst.config.ts
  - hello_lambda folder
    - pyproject.toml # for that lambda
    - index.py
  - other_lambda folder
    - pyproject.toml
    - index.py

After upgrading SST from version 3.3.2 to 3.3.5, I started encountering the following issue when invoking my Node.js Lambdas using npx sst dev:
{"body":"sst dev is not running"}

To troubleshoot, I tried deleting all production and development resources in AWS by running npx sst remove stage... and then redeployed everything in dev mode. Unfortunately, this didn’t resolve the issue.
I also deleted the .sst folder, cleared node_modules, and reinstalled dependencies using yarn. Despite these steps, my Lambdas still don’t seem to connect to the dev environment as expected.
For context, I’m running this setup on WSL in Windows. Any advice on further troubleshooting or fixes would be greatly appreciated.

@c4rloscg might be a different issue but we'll take a look.

I also get this issue following the hello-world example. My sst version is 3.3.10 using npx sst version
https://guide.sst.dev/chapters/create-a-hello-world-api.html

@aaronvg what OS?

macOS apple silicon (m1).
Can't seem to get it to connect when I open the browser or curl the endpoint still (unsure if this is an sstv3 issue)

So when do you get the sst dev is not running error?

this console url is also blank page:

What does your functions tab show?

@thdxr

can you share what region your app is in

us-east-1. I'm gonna try 3.2.73

alrighty, I manually changed all package.jsons on the hello-world to 3.2.73, ran it and it worked.
I changed it back once more to 3.3.10 and it didn't work again. will stay on 3.2.73.
Unsure how many this affects but I couldn't get past the first tutorial with this problem.

potential fix in v3.3.11

potential fix in v3.3.11

This fix worked for me, thanks! Using 3.3.13 now on WSL in Windows without issues.
Related comment.

Great. Closing this for now.


Investigate unexpected behavior of violations before & after use of TRADE

The in.txt file for release 0.5 contains multiple comments:
"Pay attention to violation on FORCE before and after TRADE".
These comments are positioned around use of the TRADE command in the hope of facilitating this investigation.
In theory, the use of the TRADE command in the operation of the 0.5 in.txt file should reset everything to the state that existed before TRADE was invoked.  If you look at violations on FORCE, that may not have happened properly.  The behavior is observed in both the PLI (expected_dos.txt) and JavaScript (expected_out.txt) code.  Is there a bug in here somewhere ?

I was able to reproduce the behavior under the Eclipse debugger.  It is possible to step through and watch the values of vmin by expanding sv.  As of this moment, I continue to believe that there is a problem with the reset of values when trade finishes without retaining the calculated result (i.e. something is not handled correctly in the case that trade attempts to set everything back to "oldvalue".  Again, note that the problem is also apparent in the PL/I code.
However, since this investigation is turning into an extended effort.  I will defer further activity on this issue in order to make progress on other issues.

Please include specifics of input and output so that I can reproduce this issue. For example an input file and screen shots before along with actual output and screen shots after. Since it appears on both, I’m only interested in the JS version to reduce the work to capture the issue.

Multiple places in trade, change and fix found where a constraint level was being manipulated without a corresponding call to sclden() to update the scaling denominator.  These problems originated in the PL/I code. In the process, a similar but more recent coding error was found in trade.js.  This issue will be closed after a more careful inspection of expected_out.txt and expected_dos.txt

Review of expected_out.txt and expected_dos.txt is now complete.  Closing.


Fix blend shape handling.

Should fix #13.
The core of the issue here is that geometry data in FBX is not indexed, so there is no way to map from the processed array mesh into blend shape offsets after mesh_surface_tool->index() is called. I assume that blend shapes are currently broken for non-indexed glTF meshes as well.
To fix this we need to retain vertex index information during this process, but as we have no extra geometry data channels to use currently I did a somewhat strange fix: Instead of storing vertex positions directly in Mesh::ARRAY_VERTEX, for meshes with blend shapes we store instead Vector3(index & 0xffff, index >> 16, 0). This prevents the index() call from merging vertices that are in the same position but have potentially different blend offsets, but still allows merging identical vertices by index.
Afterwards it's easy to retrieve the vertex indices for generating the blend shape data. The real vertex positions are later patched in after blend shapes are read.
Edited:
Fixes: https://github.com/V-Sekai/godot-ufbx/issues/10
Fixes: https://github.com/V-Sekai/godot-ufbx/issues/13

I also added a temporary local modification to ufbx to support normals in blend shapes, I'll add it to mainline ufbx with some tests soon.

The normals a broken. Maybe axis conversion?
https://github.com/V-Sekai/godot-ufbx/assets/32321/5a187b4c-6a48-4887-89a9-a02816a46d56

Shouldn't be it's local space, I'll take a look with that model!

Turns out the normals were offsets as well (which is not too surprising), they feel a bit too strong in this model so not 100% sure what's going on but they look roughly correct at least.

array[Mesh::ARRAY_NORMAL] = _decode_vertex_attrib_vec3(fbx_mesh->vertex_tangent, indices);
Noticed this bug.

Whelp how did that happen, awkward copy-paste mistake from me, I'll fix it in this PR and see if it helps.

Tangent is a vector4/plane/color

Oh it contains the bitangent sign as well?

See https://godotengine.org/article/fixing-tangents-accurate-normal-maps/

To save on space Godot uses the approach where only the tangents are store and bi-tangents are calculated by combining them with the normal vector. For this a direction flag is also included with each tangent.

Yeah that's what I expected, I'll fix it!

When we're ready, we can rebase to one commit and merge. The reasoning for one commit is we ran into a detour in the middle of the patch series.

Sure, do you mind if I add temporary animation support here as well while I'm at it?

Want me to merge this in first?
I can do it promptly.
Then you can start on temporary animation support.

Sure thing! I'm still sorting some unrelated stuff out for a while before I could start.


 Please consider improving the usability of filter sliders for touch enabled devices such as tablets.

Hi @brylie ,
Currently, keshif is not designed for the best experience with touch screens or small displays. It focuses on offering a smooth mouse-based interaction on desktop/laptop devices.
Thank you for your feedback and interest, and I hope you can continue finding use cases for Keshif!
Adil

@adilyalcin thanks for your quick response.
We are considering using Keshif as a dashboard for nurses and administrators in a healthcare facility. The healthcare workers have ready access to tablet devices, and may want to interact with our information dashboard via those, and other, touch-enabled devices. This is an emerging demographic, so might be of value to put touch support and usability testing on the Keshif roadmap.

This, and other touch related usability issues might be resolved by using jQuery Mobile. E.g.

touch enabled range slider

Closing this because there is no current plan to improve on the tablet / touch interaction.


AsEnumerable is not an extension method

Missing "this" keyword on the first parameter.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 17 Jan 2011 at 6:48

Original comment by azizatif on 17 Jan 2011 at 6:51

Changed state: Accepted
Added labels: Milestone-Release1.3

Fixed in r251.

Original comment by azizatif on 17 Jan 2011 at 7:34

Changed state: Fixed


How to persist the server between reboots in production?

We need to ensure that all servers (Python, Node.js, reverse proxy server) start on boot. I've been using systemd for this, and I think it's a common solution for this problem. Is there a better way to do this?
Docker daemon runs in its own systemd service so nothing for us to do there.

systemd seems like the choice most Linux distributions are opting for. There is also extensive documentation available, like in the Arch Wiki: https://wiki.archlinux.org/title/Systemd.

Fixed by #32.


Fix role parsing in golang 1.17+

In golang 1.17 a change was made to remove anything preceding a slash from the filename field of the Content-Disposition header. This causes a problem with notary since it's using the filename field for the role value. This fix changes the parsing of the header value so it grabs the raw filename value instead of using the method that removes the base part of the filename.
This is also outlined in this issue:
https://github.com/notaryproject/notary/issues/1630

Ping @thaJeztah @marcofranssen

ping @justincormack @HuKeping PTAL (also looks like CI is no longer running, including codecov, which was marked as "required"; probably need to rewrite CI to use GitHub actions, or re-enable CircleCI


Missing the last line

I am using foreman on an ubuntu vagrant machine with byebug.
I can't see the last line which is my input line.
Does anyone know how to solve this issue  - just print one more line?

I am also experiencing this issue for Foreman version 0.84


Face Alignment in Full Pose Range

Is your feature request related to a problem? Please describe.
Yes , this feature adds a implementation model of the paper Face Alignment in Full Pose Range: A 3D Total Solution to the /Face Reconstruction directory.
Describe the solution you'd like
In this paper, they have proposed to tackle the challenges in an new alignment framework termed 3D Dense Face Alignment (3DDFA), in which a dense 3D Morphable Model (3DMM) is fitted to the image via Cascaded Convolutional Neural Networks.
Applications

Face Reconstruction
Face Alignment
3D Pose Estimation
Image Dense Estimation

@akshitagupta15june The applications of this is diverse , will it be feasible to add in the /Face Reconstruction Directory or anything else you would suggest ?


Adds onFocus and onBlur to text fields

Implementation of onFocus and onBlur based on #45841, #40675 and #140538.
The intention is to add the onFocus and onBlur events, in order to avoid dealing with the events manually and also adds new possibilities.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

FocusNode already allows a callback to be registered for those events I think.

@LongCatIsLooong Are you referring to FocusOnKeyCallback and FocusOnKeyEventCallback?
The idea of the proposed implementation would be to use it for general purposes, as we use on the web, but it could be expanded to other platforms.

FocusNode itself is listenable, and it notifies the listeners when it gains/loses focus.

We currently use something like focusNode.addListener(_onFocusChange) ;  , but the idea would be to make this automatic.
I consider it a good approach, but I don't know if it will contradict the idea of what FocusNode currently is.

Could you elaborate a bit on what problem this is solving? The new API does not seem to provide new functionalities over the existing focus node API and IMO it doesn't make listening to focus change too much easier either (as compared to focusNode.addListener).

What I want is a less cumbersome way of managing all the listeners on the screen. For example, if I have 10 listeners on the screen, each with its own characteristics, I need to add each one manually. For problem #40675 I simply solve it with Focus. I really still need something, maybe I can simplify the change to just the TextFormField.

I will close this PR. Analyzing it further, it really doesn't make much sense in how my implementation was done and the result I want (to be more flexible like on the web). For now I think the best way is to create abstractions based on what we have.


bad result

Hello, could you provide a script for reproducing the FID? I am using the pytorch-fid library to calculate it with AiM-B, topk=600, topp=0.98, and cfg=5, and the FID score is 9.3, which is significantly different from the value in the paper.
Here is part of my code
`
all_classes = list(range(args.num_classes)) * (args.num_fid_samples // args.num_classes)
subset_len = len(all_classes) // dist.get_world_size()
all_classes = np.array(all_classes[rank * subset_len: (rank+1)*subset_len], dtype=np.int64)
cur_idx = 0

for _ in pbar:
    # Sample inputs:
    # c_indices = torch.randint(0, args.num_classes, (n,), device=device)
    y = torch.from_numpy(all_classes[cur_idx * n: (cur_idx+1)*n]).to(device)
    cur_idx += 1
    with torch.inference_mode():
        images = model.generate(c=y,batch=len(y), temperature=1, top_p=0.98, top_k=600, cfg_scale=5)
    images = images * 0.5 + 0.5
    images = torch.clamp(255 * images, 0, 255).permute(0, 2, 3, 1).to("cpu", dtype=torch.uint8).numpy()
    # Save samples to disk as individual .png files
    for i, sample in enumerate(images):
        index = i * dist.get_world_size() + rank + total
        Image.fromarray(sample).save(f"{sample_folder_dir}/{index:06d}.png")
    total += global_batch_size

`
By the way, I notice that the adaln_group for AiM_B is False in your code, but in paper, the Groups for AiM_B is 24.

Hi,
We used the same evaluation script as LLamaGen, with the following parameter settings: temperature=1, top_p=1.0, top_k=0, cfg_scale=1.75 or 2.0
The reason for the difference in parameter settings when evaluating FID compared to those provided in the README is that higher cfg-scale and certain top-k parameters can improve visual quality but are not conducive to accurate FID evaluation.
For more details, please refer to: https://github.com/FoundationVision/VAR?tab=readme-ov-file#sampling--zero-shot-inference

Apologies for the lack of a clear explanation in the README. It will be updated shortly with the appropriate parameter settings for evaluation.

Thank you for your timely reply, looking forward to the update of the code


Enable headstamp prediction on upload, image notes

Several changes to run headstamp detection in the background when an image is uploaded.
Annotations now relate to specific headstamp detections
Image view is tabbed to enable addition of key-value pairs as notes.

Rob, this seems like things are getting g really close to functional!
On Fri, Dec 30, 2022, 08:53 Robert Sim @.***> wrote:

Several changes to run headstamp detection in the background when an image
is uploaded.
Annotations now relate to specific headstamp detections
Image view is tabbed to enable addition of key-value pairs as notes.
You can view, comment on, or merge this pull request online at:
https://github.com/Tech4Tracing/CartridgeOCR/pull/108
Commit Summary

f4bf2e5
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/f4bf2e5b6c0fa77945f352b001a5da4b3715ed18
Import script and some API cleanup
82a626b
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/82a626bc35fbfff8d4e66825ae9aacfc4de80494
More import logic
6ef87a3
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/6ef87a3db363686ae1ea37a941739f974fc59417
extra_data upload
1feb8b4
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/1feb8b4fee2c3a24cdcb067e8471e415cd8f2b3e
expose sql port for debugging
7675c8b
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/7675c8b48d16b923d0de7216e8c58760bd2ae612
debugging notes
0cddb9b
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/0cddb9b8206e8fd2ac9519cc93b83896bb267afa
deprecate competing db interfaces which were causing deadlocks
8e24ce2
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/8e24ce252e4d27703ea7e5aee3186c74c014e6fc
annotations import scripts
a319edc
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/a319edc1ef2c4c14d9e8e5ba4735b672364fe71f
sketching out celery tasks
ff6a5d0
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/ff6a5d0bb6680af69735124cc9df7ac25a62516b
move module files
c58c72c
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/c58c72ccb767b5225601b39447acc7acaaf71616
predictions WIP
dad484f
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/dad484faedaa084d78c74ff1578d365a9abeb331
Added predictions table
b4e1b78
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/b4e1b78c7fc0f88a2840d3e6d3d94332e160987f
Debugging predictions
ac94fad
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/ac94fad064582258539b6e71e50c3a9b8f6b931d
adding notes and prediction-based annotation
c3184e3
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/c3184e3727db4c211e0552821f9c3010f4c095ef
per-prediction annotation
bf0ef8b
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/bf0ef8b71a416fca2d2bd64fd3ae522dd6ef7728
image PUT
cc6d800
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/cc6d800486f8c8c3d6208afa79e53cd3939ea9fe
update ui
fc8ac3a
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/fc8ac3ae0648689992f680661fac8bd5b13b991c
docke-staging for predict api
86d7d88
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/86d7d887391156bf66e3d04b793fbe5eb1c1c75f
migrate predict_api to runtime image
e11923a
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/e11923aefd86f0153fd5c9dc37370211776b90e8
clean up predict_api
486f237
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/commits/486f237dcabaf2ade53cfa38e9bf010fc3e4a041
rabbitmq deployment

File Changes
(56 files https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files)

M .gitignore
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-bc37d034bad564583790a46f19d807abfe519c5671395fd494d8cce506c42947
(1)
A debugging_notes.md
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-45e8aac90532e5918aa79ecb2d8003165f3f7492ae1c775f4226a374502f4367
(4)
M docker-compose.yml
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-e45e45baeda1c1e73482975a664062aa56f20c03dd9d64a827aba57775bed0d3
(17)
A src/annotation/alembic/versions/3da61e435f13_add_predictions.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-f13e2f60e82577dd7776cfd3f76d2ccab88aeb61188bdc13d1865315239f4c9d
(51)
M
src/annotation/alembic/versions/ccabf4d80f27_image_collections_relations.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-47f6f52064b08259e3cd389fd57c7029d4d6217ba32490ebb68fb3a38e25c31d
(12)
M src/annotation/annotations_app/config.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-5fe50fe8a3fac9bf977bf3b5080ddd2483f97e79c6db722702db876bcad6cc41
(1)
M src/annotation/annotations_app/flask_app.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-a0dc6523cdcee7a5ea762253bb3bb395b770e5ddfa6ecf54dd073f48961af54c
(11)
M src/annotation/annotations_app/models/base.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-a802b3baa979ba17fca0b0c1b15ce03b8a38718be86cd5d1ccbdeff1865ef381
(37)
M src/annotation/annotations_app/schemas.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-d3525b4e9aa2b64dd1519f594b41647ee5d1d8125cd524d799e25bf5ae23a0f4
(57)
M src/annotation/annotations_app/static/annotations.js
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-54ef47ac0ebc892a8cfd92154f29a90d018c03cd5464e6b33d4feb7ffa59bba1
(4)
A src/annotation/annotations_app/tasks/init.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-52777cebfc6c147b1b1a64b1ce4a3371985c81728d658e84fcb0898f50665197
(13)
A src/annotation/annotations_app/tasks/predict.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-8af3f7829c61ddb38d64eb07fa454ca572441d9c89251ac521d1749df7790d5f
(67)
M src/annotation/annotations_app/user.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-cc43b33c8f492a7d4a6c36d19fc6a1036c7b83385e13bbb2c0dbbde6a07a0501
(135)
M src/annotation/annotations_app/utils.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-b4a032045b0686ec01f16af7a74b668490d99c5c6baa1a4b38989fbaaa75f369
(5)
M src/annotation/annotations_app/views/annotations.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-4408b2a5b5d37d8455f981c5922476937debc52dc4fad02629df640baaf4863f
(43)
M src/annotation/annotations_app/views/api.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-b22d1276fbc0a0ccaf8f3e7baa4aa86482cb1d9149847a7c80039e937544c3d7
(11)
M src/annotation/annotations_app/views/collections.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-64721901dc24b5caece986e4947c99dc8ea72eff2f93627d78e0a7e7b744f5eb
(2)
M src/annotation/annotations_app/views/generic.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-6bda9080697e08ead775b0fa3379d9e14fb89f5434c408a6651b2cff16fd9bdc
(2)
M src/annotation/annotations_app/views/images.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-df01af816b8cdfb51d25ef9636df863213c94dd3ddb8f3c0a73881dda958f444
(154)
A src/annotation/annotations_app/views/predictions.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-64511cfd83e20befcab450cdb9362b8d36baa8808fdbb8ea0c9c1cb406a29fd1
(294)
M src/annotation/annotations_app/views/users.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-99d8141faf00215b128cf0fe5e14073b1c18fe5f8d9c93b5af1bab5fab45b1c2
(135)
M src/annotation/devops/run-annotation-api-local.sh
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-207a6a0dddef061fdbe28e57cef44f196e46db883700a94639537a38e661db1d
(3)
M src/annotation/requirements.txt
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-f67bef353c73a7858f3cc8f6f52a2fa096a706c5feda9000d1949032004438bd
(3)
A src/model/LICENSE
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-c70cc305dbabc175cecb3808415a099adbd50f3e354f434fa092f37785c74df3
(21)
A src/model/README.md
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-f7d54492b3fe945cb6b4f5271491b33089eb170ff73c50332f401e87bb5c1e39
(3)
A src/model/setup.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-012c9ee83c8e5dc1884a7853e9ced9df855568e9465c312291032204a57d950c
(24)
R src/model/src/t4t_headstamp/init.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-630a9bc04f278f575965a881301c5847f4aaf0fb7c399ac9335bff43010cad0e
(0)
R src/model/src/t4t_headstamp/dataProcessing/init.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-24b6a1ebaf811a50c0305119f561d51fddf04ca14fbe18a7985cf74ea099da5e
(0)
R src/model/src/t4t_headstamp/dataProcessing/coco_utils.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-e925dfc53b4f5d26897a0470d856f7887cc34ce5eab98797913bab8adbcc05cc
(2)
R src/model/src/t4t_headstamp/dataProcessing/convert_coco_urls.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-ff121a2342922354af120dd03b68c3275e7630b2d8216fefd02d7309282279b8
(0)
R src/model/src/t4t_headstamp/dataProcessing/merge_annotations.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-bdd2832a1a1a2f26d23ed18b55c452e7591dccd5c4e20b2ce1cd53391a02c139
(0)
R src/model/src/t4t_headstamp/dataProcessing/transforms.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-16da74dffd8e89006946c238cd7594c5c01fd9035f016c5a6582a8ef2e0cb303
(0)
R src/model/src/t4t_headstamp/dataProcessing/utils.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-000e32691fc9553f4b30513c44fed1ea6f3e3a6b58d49064a5b40a9ad1af30f8
(0)
R src/model/src/t4t_headstamp/predictions/README.md
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-814c2c7ff4fb57d52be554849b22577168b5c669b5c7a2bf5254bb42b54195a7
(0)
R src/model/src/t4t_headstamp/predictions/init.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-5dd759d0db2ccf3ec0f5644e2f2dc15d512a19d79bd72c8d13575ea0e6378804
(0)
R src/model/src/t4t_headstamp/predictions/inference.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-f10b30263467264b2464c95150227b746dcfbcaee390e796868504f8083f7620
(2)
R src/model/src/t4t_headstamp/predictions/predict.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-2d7b6686582aae9bf5ff3a483ec5b338c9a77c8ffda27f2efb93a17a1baa738e
(0)
R src/model/src/t4t_headstamp/predictions/score.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-bcddc58b4556a35d17dc0ecf937daf28aed365006c6b44745b6882d94859ce98
(0)
A src/model/src/t4t_headstamp/training/init.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-ecba6078516cb3688d1bb2222cbe79d230d64c41b7690c631629a7499ad010c3
(0)
R src/model/src/t4t_headstamp/training/coco_eval.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-361b781669210038cf1d6ef24246235cd60f950ca7f94cd75336ace5a9cc005b
(0)
R src/model/src/t4t_headstamp/training/engine.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-407f9d030b57735de0ae649eb4e79344110ee01cbc8975605e7affc8441c4e3b
(0)
R src/model/src/t4t_headstamp/training/model_utils.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-598e37805e1e4015bcf0b129f9fef054e9b1165fcbcfec332efb8b1139a0b3b4
(6)
R src/model/src/t4t_headstamp/training/train.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-b844716ed735ddb6f5645f0b4ee46a2676b4f4e2bf6548686e1622017f29c82a
(0)
R src/model/src/t4t_headstamp/training/training_predictions.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-367a576ee57b69906604732a927884fa9c5539f0c6a204f3f7830b4f02ec6b00
(0)
M src/predict_api/Dockerfile
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-66d86d3d1712cd1e9ef409895b14cb88a8ecd7405c09234864b7ceab9f430de8
(8)
A src/predict_api/docker-staging.sh
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-a682cacd6db30541de762633277975e31c20cb11c0110bccb745c3e1672d266e
(16)
M src/predict_api/dockerize.sh
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-a4b66092cf430310c546273adca1a66e3cb6b2faf8222573bd133d4a845f1ed5
(6)
M src/predict_api/flask_app.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-8c712554b81199224dac113d7b26a2d4c2da8634fae2c24abec0795f2c1c6a93
(167)
A src/predict_api/templates/swagger-ui.html
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-e8f7d37c4ceef28e47c6a433f207d232285af82ec854a5c6f2b7bb591a396b94
(55)
D src/predict_api/user.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-39acaa0b0594cbf183f95f9ea67ed275d1b1f39a24910e012995e49bbdf3ef19
(129)
M src/predict_api/views/predictions.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-3381193342be3e02dc046b20cb81df2dab395f176d2d87118503883fdce9515f
(2)
M src/requirements.txt
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-0a0827574cc2d3aac80f74096dd6d1e871b83efae03aa087c2c8e8f1e9187d26
(3)
A src/scratch/import_collection.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-ec3a064ece063eeb1df68e17a12f9784c8715b63cfab0eb3d3b09e31f4cbc1f7
(92)
A src/scratch/reconcile_annotations.py
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-1e279297fec368aaff440877f838a5a2c4630b3caa83ca3c348577b469e917b8
(20)
A src/scratch/upload_all.sh
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-46db7549d474406b8be65e0ee7e0a2d36f3b266c100538a6b46b813e23d0fbf6
(5)
M src/t4t-annotation-UI
https://github.com/Tech4Tracing/CartridgeOCR/pull/108/files#diff-54f83e3d8c254cc09dd6372042a5cc9f38ff6feb691c7d1f189efea479d57f44
(2)

Patch Links:

https://github.com/Tech4Tracing/CartridgeOCR/pull/108.patch
https://github.com/Tech4Tracing/CartridgeOCR/pull/108.diff

—
Reply to this email directly, view it on GitHub
https://github.com/Tech4Tracing/CartridgeOCR/pull/108, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATZR5LPCTKSBWJC4VCM776DWP2IHNANCNFSM6AAAAAATMWIJGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Reduction with functions

Made a separate function from groups.

@VictorAlex1 I don't see any tests for this

@jkanche
tests added

@VictorAlex1 fixed a numbe of things and this should be good to go


Revert "refactor: plugin platform code cleanup"

Reverts aws-amplify/amplify-cli#10384
Breaks pkg CLI build: https://app.circleci.com/pipelines/github/aws-amplify/amplify-cli/8459/workflows/4d90aab3-f292-4f60-9b0a-0deacbc40f4e/jobs/251296

Successful run w/ revert https://app.circleci.com/pipelines/github/aws-amplify/amplify-cli/8465/workflows/1937156b-a95f-4345-a26c-e2dc18bd029f/jobs/251332

Codecov Report

Merging #10403 (92292b5) into master (2612585) will decrease coverage by 0.00%.
The diff coverage is 59.52%.

@@            Coverage Diff             @@
##           master   #10403      +/-   ##
==========================================
- Coverage   46.57%   46.57%   -0.01%
==========================================
  Files         703      703
  Lines       35245    35254       +9
  Branches     7136     7137       +1
==========================================
+ Hits        16417    16418       +1
- Misses      17043    17049       +6
- Partials     1785     1787       +2

Impacted Files
Coverage Δ

...ify-cli/src/plugin-helpers/scan-plugin-platform.ts
17.85% <34.21%> (-3.25%)
:arrow_down:

packages/amplify-cli/src/plugin-manager.ts
17.39% <67.85%> (-0.26%)
:arrow_down:

...es/amplify-cli/src/plugin-helpers/verify-plugin.ts
100.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Issuing a loadbalancer delete on a loadbalacner in PENDING_CREATE should change the state of the loadbalacner to PENDING_DELETE

Agent Version
9.0.2
Operating System
RHEL 7.3 - OSPv9
OpenStack Release
Mitaka
Bug Severity
Severity: 5
Description
When a request to delete a loadbalancer is issued against a loadbalancer in the PENDING_CREATE state (which can happen and persist if the agent errors and does not update the loadbalancer properly), the plugin should alter the loadbalance status to PENDING_DELETE and try to delete the loadbalancer rather then simply raising an error that a loadbalancer in PENDING_CREATE can not be deleted.
Deployment
Simple to reproduce even without an error.. Just shut down your agent. Issue a loadbalancer create and then immediately issues a loadbalancer delete.
OpenStack Release
OSPv9 running community tempest test creates errors which leave loadbalancers in PENDING_CREATE which can not be cleaned up with out working with the database.

BIt more detail. A create loadbalancer request which passed validation and was put in the database via the community LBaaS code, but which cases issues with the service builder leaves the loadbalancer object in the wrong state.
Here are three community tempest tests which cause this problem:
'''
neutron_lbaas.tests.tempest.v2.api.test_load_balancers_admin.LoadBalancersTestJSON.test_create_load_balancer_for_another_tenant[smoke]
neutron_lbaas.tests.tempest.v2.api.test_load_balancers_admin.LoadBalancersTestJSON.test_create_load_balancer_missing_tenant_id_field_for_admin[smoke]
neutron_lbaas.tests.tempest.v2.api.test_load_balancers_admin.LoadBalancersTestJSON.test_create_load_balancer_missing_tenant_id_for_other_tenant[smoke]
'''
As these are smoke tests they make us fail BVT.
From the neutron server log:
2017-02-27 14:31:29.525 31813 ERROR f5lbaasdriver.v2.bigip.plugin_rpc [req-0470b770-2e5c-49c1-9c33-643cef01d70a - - - - -] Exception: get_service_by_loadbalancer_id: Tenant Id of network and loadbalancer mismatched
The current behavior:
create loadbalancer->neutron server->DB->plugin->agent
agent->plugin-rpc(get_service_by_loadbalancer_id) Exception Raise->agent.
The appropriate behavior
create loadbalancer->neutron server->DB->plugin->agent
agent->plugin-rpc(get_service_by_loadbalancer_id) Exception Raise->agent
agent->plugin-rpc(update_loadbalancer_status)->plugin->DB (provisioning_status=ERROR)

From the /var/log/neutron/server.log on the controller..   It looks like neutron RPC wants to see .msg attributes on exceptions by oslo middleware.

The mismatched tenant issue is fixed in the current 'unreleased' code.  We no longer throw an exception in the service_builder.  Instead, the service with mismatched loadbalancer tenant and subnet tenant id's is forwarded to the agent.  The agent tries to deploy the network in the admin tenant folder on the big ip and the virtual address in the loadbalancer tenant folder.  This fails and the agent will set the loadbalancer to ERROR state.
In the recent work on the HPB.  A running cache of services in PENDING state is kept on the agent.  After a configurable timeout period, default is 60 seconds, the agent stops trying to fix the pending service and puts it in 'ERROR' state.  Where the user can delete it.
commit 47d2da82c7a7bee323c511fb9fa2e007e35b6aa2
Author: Rich Browne<EMAIL_ADDRESS>Date:   Wed Feb 1 09:54:40 2017 -0700
Loadbalancer stuck in 'PENDING_UPDATE' when listener created after tenant mismatch.

Issues:
Fixes #402

Problem:
When a loadbalancer is created on a network that is not shared, nor
owned by the administrator, there is a configuration problem on the
BigIP because the network constructs will be in a different partition
from the LTM objects.  Network RBAC will solve this problem.

In the near term an exception was thrown that would be thrown from
service builder and handled in the driver.  While the loadbalancer would
be put in ERROR state, this does not prevent a user from creating a
listener/pool this loadbalancer.  The result is that the loadbalancer
get's put in a 'PENDING_UPDATE' state that cannot be cleared
because the MismatchedTenants exception prevents the agent from
clearing up this condition.

Analysis:
The change is to remove the mismatched tenants exception all
together and log the error in the server log.  The result will
be the attempt by the agent to deploy the service will fail
because the LTM objects are in the loadbalancer partition and the
network objects are in the network partition.  These cannot be
shared and will result in a loadbalancer in ERROR state.  However,
subsequent objects created on the loadbalancer will not cause
the lb to stick in PENDING_UPDATE.  The request will be sent to the
agent and it will properly put the lb in ERROR state.

Tests:
Create an admin network and a demo network (owned by demo user)
As admin create a loadbalancer on the demo-network -- verify lb in ERROR
As admin, create a listener on the previous lb. -- verify lb in ERROR
not in PENDING_UPDATE.
As admin, remove listener -- verify removed.
As admin, remove loadbalancer --verify removed.
api/test_load_balancer_create.py::test_create_load_balancer_without_tenant_id

Confirm that this issue is resolved after the feature.opflex branch collapses.


Create a new Optimizer: Train Mask-RCNN with SWA

Hi,
according to the issue #4698, #3086 is the tutor 5 not the right way to customize the optimizer.
Could someone help how can i train Mask rcnn with SWA from torch.optim?
Thx.

I have seen that the new version mmdetection has support the swa with mask rcnn. There's no need to create a new optimizer.

@ yc0619 Hi, Could you tell me where is the config for the swa with mask rcnn?

where is  it  ?  Friend ,I'm  looking  for  it .


Where are the executables using drake_cmake_external??

Hi
This may be a silly question, but I cannot find the executables after build in cmake.
In addition, where is the executable of the simple_continuouse_time_system.cc??
If using drake as external, do I just need to put everything under app/
Cheers

The README says to build it like this:

To build all apps using CMake and Make:
mkdir build
cd build
cmake ..
make

Assuming you've done that, the binary is at ./drake_external_examples/apps/simple_continuous_time_system (in other words, drake-external-examples/drake_cmake_external/build/drake_external_examples/apps/simple_continuous_time_system).

If using drake as external, do I just need to put everything under app/?

No.  You can use any directory names you want.

Great! Thanks.

Great, thanks!


Fix non-strict equality against boolean.

[ ] PR has tests / docs demo, and is linted.
[ ] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[ ] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

What's the motivation for that change? It's breaking our test suite.

I didn't realize I broke the test suite. My motivation was to fix the UglifyJs warning during Webpack:
WARNING in bundle.js from UglifyJs
Non-strict equality against boolean: == true [./~/material-ui/utils/helpers.js:41,0]

Sounds like a good motivation :+1:. Feel free to fix the CI, we can reopen the PR if needed :).


HtmlJobReportFormatter - Accept velocity params (log location)

Hi,
the public constructor is
 public HtmlJobReportFormatter() {
        Properties properties = new Properties();
        properties.put("resource.loader", "class");
        properties.put("class.resource.loader.class", "org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader");
        velocityEngine = new VelocityEngine(properties);
        velocityEngine.init();
    }

a velocity.log is written in the FS when run, however when running in environments that are readonly (ie AWS Lambda) we have to specify the location of the logs. Adding this
properties.put("runtime.log", "/tmp/velocity.log"); creates the log in the right location.
Can we have a constructor that accepts some options?
Thanks!

Hi @psoares-resilient,
Thank you for reporting this issue! I consider this as a bug in Easy Batch: As a user, I should not be aware that the HtmlJobReportFormatter is using apache velocity behind the scene and I should not be concerned with its configuration. The reporter should not generate any log so I disabled it.


[WIP] Update the changelog

BayesSearchCV was missing, as are others (I am sure).
Let's try and get the log updated. If you know something that should be mentioned help me out by posting here. Will wait a bit and then merge this PR.
(We should get better at keeping it up to date as part of merging PRs.)

There was this important piece too https://github.com/scikit-optimize/scikit-optimize/pull/343
Also the bug fix regarding the inference of the type of dimensions.

Codecov Report

Merging #422 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #422   +/-   ##
=======================================
  Coverage   86.37%   86.37%
=======================================
  Files          22       22
  Lines        1556     1556
=======================================
  Hits         1344     1344
  Misses        212      212

Continue to review full report at Codecov.

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

Merging this :)

📝 📝 📝 📝


feat: Show formatted date of purchased ticket

Fixes #289

Add formatted date in Attendee Check-In layout

@iamareebjamal what timezone is the date/time displayed in ?

@niranjan94 Yeah. I had some doubts about the same.

As app will be used by an organizer so event's timezone shall be used in the whole app for time display right?
When an attendee books a ticket for an event, in which timezone the date is stored for order completion?

Yes. Use event timezone throughout. But ensure the user (organizer)
knows what timezone are dates and times displayed in. Give an option for
the organizer to change display timezone.
The timezone information is part of the api date time response. Use
that.

On Tue, Jul 11, 2017, 12:16 PM Amol Mejari<EMAIL_ADDRESS>wrote:

@niranjan94 https://github.com/niranjan94 Yeah. I had some doubts about
the same.

As app will be used by an organizer so event's timezone shall be
used in the whole app for time display right?
When an attendee books a ticket for an event, in which timezone the
date is stored for order completion?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-orga-app/pull/291#issuecomment-314350943,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACSwFAIYKaJXwB0EzHKSemAc3bUyLzJnks5sMxo9gaJpZM4OTf7K
.

@niranjan94 The timezone is event timezone throughout the app. And the current code supports local date time conversion, just not the UI component to do so. Should we just add option to switch local and event timezone or should we add option to choose any timezone? I think we should let local timezone from Android decide this behaviour as user can change the timezone from there?
And the problem in showing the timezone part is that if we include the timezone format in Date Format in Java, it automatically converts it to local time. There is no clean way to do it using the API date response, perhaps if we add a different function just to extract timezone information from the date?

@mejariamol For 2nd point, it's handled by the server

@mejariamol @arp95 @Shailesh351 @shreyasnbhat @rohanagarwal94 Please review

If styling can be taken in the PR, I think texts would look better if non all caps lock. For examle
Completed, Jul etc.. What do you think?

I like to think it this way, that they are representing one of the constant states, paid, free, donation, completed, etc. So I think we should use caps, but if not, we can discuss on another issue as this is date related


Build JVM variant on new JDK APIs for FFI

Project Panama's initial set of APIs will go stable in JDK 22 (March '24). We should build a variant of Zipline to support this, and use multi-release jars to enable that functionality on JDK 22+.
This will be faster than the JNI version. This will allow moving all the C++ code into Kotlin without introducing significant overhead (similar to the use of cinterop on Kotlin/Native).
Eventually, once JDK 22 is our minimum, the JNI code can move to be Android-only. And then at an even later time when our Android minSdk has the necessary Panama bits, we can eliminate JNI altogether. But that's all really far off...

Can you take a look at this repo?
https://github.com/Endoqa/kotlin-quickjs
QuickJS binding based on Project Panama, c-style api.

We would be binding against our own C++ code that talks to QuickJS, not directly to the QuickJS API.


Fixes for metadata page

fixes #240

[x] - all the form fields work as expected (you can edit it doesn't crash etc)

[x] - all the form fields and section shows appropriate help message (we need to extend one-word help messages, fix the links etc)

[x] - handle edge-cases (for example, currently npm run components fails for Package because it doesn't have any resources)

Please make sure that all the checks pass. Please add here any additional information regarding this pull request. It's highly recommended that you link this PR to an issue (please create one if it doesn't exist for this PR)

@roll it is ready for review!.


Build task shows forever spinner

this task which has no problem matcher https://github.com/microsoft/vscode-anycode/blob/e887e1daf60cd345e42eca7ac1c7c827a05bde91/.vscode/tasks.json#L9
it spins forever, never stops

https://user-images.githubusercontent.com/1794099/126169623-51d37674-2b06-490f-9d45-e8116f6784dd.mov

/duplicate https://github.com/microsoft/vscode/issues/127684

Actually this is different, you need to set isBackground to true to get rid of the spinner right now:
https://github.com/Microsoft/vscode/blob/5b642616ef3cba37b07ff6946da0cd8bd2280045/src/vs/workbench/contrib/tasks/browser/taskTerminalStatus.ts#L94-L97
This is likely as designed
cc @meganrogge

Oh, thanks @tyriar!

Yes, this is by design. For tasks that "end" (non- background tasks) we show the spinner until the task exits. Since this is a watch task it should set isBackground to indicate that it is a task that will usually not exit on its own.


Remove MacOS module in macCreatorType

utils.macCreatorType uses either the xattr module or the MacOS module to do its thing. But the MacOS module has been removed from Python 3.x. If we only support 3.x, we should remove the MacOS-related code.

Agreed.

Additionally if the xattr module is not available then setMacCreatorAndType silently fails.

Additionally if the xattr module is not available then setMacCreatorAndType silently fails.

This is intentional. It's a legacy thing, that is nice to have still around, but nothing more than that.


How to prepare the dataset

Hi,
Thanks for the great implementation! I am wondering how should I download voxceleb dataset. What is the expected directory structure? And also could you give us an example of test_pairs file?
Best,
Xin

Solved! Ended up generating testing pairs manually, since I did not find official test_pairs for voxceleb2

Hi! how do you fix this issue? @xinli94


Instructions on first run (setting username & passwoed) appear in system locale language

I live in Israel, therfore my system locale is Hebrew, while trying to run bash for the first time, I was asked to set a username, then I entered a username (in english, all lower case letters withouth any other character). After that, gibberish appeared, I copied it and pasted it in notepdatd (could have done it in any other unicode text box I think), and it is hebrew ("הכנס ססמת יוניקס חדשה:" which means Enter a new Unix password:).
This shouldn't be like this I think, as the console doesn't support Hebrew characters (I think non-unicode generally but I'm not sure about that).
It all should be in English I think. Either way, right now it's just not readable and useless.
I am running Microsoft Windows [Version 10.0.14393]
My Windows display language is English (though either way it should print it in English since the console doesn't support Hebrew), my region is set to Israel,

This happens for Brazillian Portuguese as well. And it`s not only the instructions on first run, but also the output from some commands, as seen on the screenshot below?

However, as mentioned in this SO question, running the following command fixes it:
$ export LC_ALL=C

lxrun is deprecated.


Handle PXE boot devices order when VM is restarted.

requires https://github.com/kubevirt/web-ui-components/pull/95

added fail checks

I didnt notice that errors are already handled in PromiseComponent so I do not need to catch anything, just pass errorMessage to Footer. Added progress too.


How to properly extend Decimal.js-light?

I want to add some helper methods into the prototype, so I write my own class and extend Decimal.js.
It works perfectly except when calling .add() and some other operators. the super class (Decimal) is returned by default. Any ideas to properly extend Decimal?

I tried to extends Decimal.js-light, but the behavior is strange.
class MyDecimal extends Decimal {
    constructor(value) {
        super(value)
    }
}

let x = new MyDecimal(0)
console.log(x.constructor.name) //Tested with Chrome, it is not 'MyDecimal' but 'e'

Please help.

Apologies for not replying sooner. Unfortunately, I was not able to help with this.
It is the sort of question that would have been better to ask on stackoverflow.com.


cannot read property 'write' of null

im using m1 mac
this is my init.vim right now

and the error is
[coc.nvim] Error on activate extension coc-discord-rpc: Cannot read property 'write' of null

https://github.com/LeonardSSH/coc-discord-rpc/issues/21#issuecomment-910384599

#21 (comment)

i couldn't find that and its all encrypted

It's unreadable, but you can spot the beginning of the return statement in question before the second occurrence of "discord-ipc."

I'm getting the same issue in Ubuntu 20.04, I thought that it was a snap thing but after reinstalling discord the error persist

I have the same issue I believe with a kind of different message

I tried finding out looking at the link that you refer about the ipc with the mac and thought maybe my discord have a separate package for ipc since I'm on arch. And so far I don't think this is the case. Not really sure yet why this happens

I have the same issue I believe with a kind of different message  I tried finding out looking at the link that you refer about the ipc with the mac and thought maybe my discord have a separate package for ipc since I'm on arch. And so far I don't think this is the case. Not really sure yet why this happens

A follow up reply it now works again not really sure why since I didn't do anything

Not working :(. Works well on linux, but not on mac currently

@KarlWithK hey, on mac I know there are problems, there's nothing I can do about it, it's up to discord-rpc to fix it, there's also an open PR for this purpose.

@KarlWithK hey, on mac I know there are problems, there's nothing I can do about it, it's up to discord-rpc to fix it, there's also an open PR for this purpose.

Any updates ? I see there are no open PRs anymore

This seems to be nvim/coc issue NOT disord-rpc-issue.


feat(framework): Add initial support

Enable deep sleep
Use kernel that's 5.12 or latest
Enable fingerprint scanner
HiDPI

closes #323

convert to draft until https://github.com/NixOS/nixos-hardware/pull/372#discussion_r799441383 is fixed.


Fixes

Coverage remained the same at 92.278% when pulling f69b03c35ddfff57a4833adafd3baba6de24922f on fixes into 49692b0e03851cd3bfd8e5fe4666d42cf687a0fc on master.

Coverage remained the same at 92.278% when pulling f69b03c35ddfff57a4833adafd3baba6de24922f on fixes into 49692b0e03851cd3bfd8e5fe4666d42cf687a0fc on master.


[DS-124] CLI Error Printing

DS-124 Expound error printing is broken for profile all errors, throws when invalid.
This PR replaces expound with a function that generates simple error strings for printing in the CLI.

Are you not going to update the FromInput docstring now that that protocol's contract has been changed?

Are you not going to update the FromInput docstring now that that protocol's contract has been changed?

haha, literally doing that as you posted this


⚠ Bofrost.lu has degraded performance

In ae0929c, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1120 ms

Resolved: Bofrost.lu performance has improved in f14e4b4 after 9 minutes.


Add support for GitHub's Fetch API polyfill

Adding typedef for https://github.com/github/fetch

@ryan-codingintrigue thank you your contributions.
please check this document. http://definitelytyped.org/guides/contributing.html#naming-the-file
rename fetch/fetch.d.ts to whatwg-fetch/whatwg-fetch.d.ts.

@ryan-codingintrigue thanks mate :+1:


Update stable version in repo from 1.14.3 to 1.15.0

Think about update stable version to 1.15.0
Version: stable=1.14.3 (77 days old) => latest=1.15.0 (15 days old)
Installs: stable=9422 (53.79%), latest=1223 (6.98%), total=17517
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.15.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.15.0 but the current stable version is already 1.15.0.
So this issue should be closed.
@mcm1957 for evidence


aarch64: Refactor cpu.h and move reset routine to C

The AArch64 port in growing in complexity and before adding new more layers and code on top it's sometimes needed to revisit the basics.
This PR is doing the following:

The cpu.h header file was being used as a catch-all header file, a no-man land without a proper naming convention for registers and bit fields. It is still a bit of a mess but at least with this PR I'm trying to name things following a reasonable scheme: _BIT for bits, _SHIFT for shifts and _MASK for masks.

AArch64 is currently using a mix of C code and inline assembly pretty much everywhere. This is error prone, redundant and in general in 2021 we should write as little assembly code as possible IMO. So this PR is adding a lib_helper.h file factoring out all the inlined assembly to common operations. We are also adding a new MAKE_REG_HELPER macro to create helpers to read / write system registers. This is handy to have self-explanatory C code when accessing system registers.

Leveraging the two previous points the reset routine has been rewritten, moving most of the code from assembly to C without any change to the actual functionality. This was inspired by some changes requested by @jharris-intel (but not yet implemented) that you can find in #32205. The C code also allows us to put in place more complex boot paths and in general to better handle all the possible permutations in which you can boot an AArch64 system.

failure is unrelated to this PR

in general in 2021 we should write as little assembly code as possible IMO.

As an aside, this is one of the reasons why load-exclusive / store-exclusive gets nowhere near as much use as it could.
There are a lot of optimizations you can do with load-exclusive / store-exclusive that you can't do with the standard atomics (notably, you can do nearly-arbitrary calculations and conditions between the load and store, all atomically and without redundant loads. E.g.  if (val.bitfieldA == 3 && val.bitfieldB == 4) {val.bitfieldC = 3;} else {val.bitfieldA = 3;}, all atomically.)
(Great for things like atomic recursive spinlocks. You don't need to do a separate fallback check "am I the owner", just have e.g. the owner core and current depth in the spinlock value and do the entire "set the lock to my core if it's unowned, else if I own the lock increment the depth, else clrex and continue" in one go.)
(Yes, you can't do too many calculations between the load and store for various reasons - but even restricting to say ten instructions very rapidly hits a combinatorial explosion of possible atomics APIs.)
Trying to do this in anything other than assembly is a recipe for disaster even if the intrinsics are exposed - because the compiler can and occasionally will insert memory operations.
The best you can do with the standard atomics is load / do calculation / CAS, which has much worse behavior especially under load (load-exclusive store-exclusive has forward-progress guarantees that load/calculate/CAS doesn't) (and load-exclusive store-exclusive doesn't suffer from the ABA problem which makes many things simpler than standard atomics)
...And unfortunately as a result even ARM is moving away from this model (e.g. ARMv8.1 introducing "standard" atomics). It's a shame, although I fully understand why this is the case. The power of a load-exclusive store-exclusive is being able to do (semi)-arbitrary calculations in the atomic section, but if no-one actually takes advantage of this...
I really wish e.g. GCC had a pragma or something to indicate "no implicit memory operations in this section". Most of the assembly I write is due to this for one reason or another (stack pointer invalid, etc, etc).

The new revision is modifying a bit the boot path. We are now dropping from EL3 to EL2 if this this is allowed and EL2 actually exists otherwise we drop into EL1 as usual.

@jharris-intel can you ACK / NACK this?

(If you're wondering; I'm always a little hesitant about showing up and stepping on people's toes.)

I really appreciate your reviews and your insights, so your showing up and stepping on people's toes is really welcome here and especially on AArch64 PRs ;)


spec: Support for payload compression?

HTTP/2 only compresses the headers, so delivering webhooks with large payloads consumes a lot of bandwidth. It would be nice if a future version of the spec automatically compressed payloads above a certain threshold and required that recipients support the resulting content-encoding.

Yeah, that sounds like a good idea. So suggest that webhook consumers support compression in the operational section?
Btw, we also recommend keeping webhook payloads small, though even at 20-40kb compression can be a boon if you're sending many messages.

My personal (Saleor Commerce) use case is that we allow users to write custom GraphQL queries for webhooks so they don't have to hit the API back immediately in response to a webhook event. Those can result in up to 1MB of JSON, which is not ideal but still better than a 100kb webhook followed by ten 100kb fetches.

What comes to my mind is should we even let the lib handle the compression by itself? Because we can have several cases:

compression/decompression is handled at proxy level like nginx: https://docs.nginx.com/nginx/admin-guide/web-server/compression/
compression/decompression is handled via a middleware: https://github.com/fastify/fastify-compress
compression/decompression is handled in the http handler itself.

What i'm seeing in here is the case you're picturing is the third one. However i'm not sure the lib itself should take care of it; the lib / spec are targeting the real content of it and not what the carrier transports. I'm not sure we should introduce the compression handling directly in the lib.

Upon further reading the original message I think I misread it. The way I read it is to include a line somewhere that it's recommended that the receiving server (or the sending client? or both?) support HTTP compression. Just a recommendation somewhere in the spec to mention that this is useful. I very much agree that we should not be doing compression in the libs, this is a transport layer concern (just like @zekth said).


Added charts library

I've tried to add my charts library to jfxcentral, not sure if everything is correct.

Could you please also add the referenced videos to the videos.json file? Unfortunately this is not an automatic process ..... yet.

Which videos.json? Do I have to create one for the libraries/charts folder?

The one inside the “videos” folder.
Gerrit Grunwald @.***> schrieb am Fr. 20. Aug. 2021 um
07:54:

Which videos.json? Do I have to create one for the libraries/charts folder?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dlemmermann/jfxcentral-data/pull/43#issuecomment-902450471,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIXWXPZU236GWCL3TQCEJLT5XU2TANCNFSM5COUXOUA
.

--
Dirk Lemmermann
Software & Consulting
Zurich, Switzerland
+41-(0)79-800-23-20
http://www.dlsc.com
@.***

Done :)


feat(jellyfish-api-core): expose verbose info from getVault RPC

What this PR does / why we need it:
https://github.com/DeFiCh/ain/pull/1344
Which issue(s) does this PR fixes?:

Fixes #
Additional comments?:

Add the next fork flag also

wait for https://github.com/JellyfishSDK/jellyfish/pull/1580
it has flags set and fixed all failing tests


Rename functional tests dir and files

Description
Prep for some more yea cleanups and new features.
Changes:
This will allow us to:

remove explicit adding of "id" key in the yea spec file
import files as we no longer start files with a number or have a hyphen
The directory hierarchy will allow us to have composable tests,  for example there can be a top level 1_service that runs all the 0_main with service on
Introduce dual ids, numbers 0.0.0 and names main.core.blah and a hybrid `0_main.0_core.0_blah'
numbers are used so we can be sure to have consistent tracking of tests over time

Not done:

mp dir
imports dir
not all hyphen files were renamed with underscores they were only renamed if they already had test numbers.  If they didnt have test numbers they will be renamed in a subsequent pass when yea is updated

Coming soon:

new yea that has some new features and can get rid of the unneeded id tags in each test

Testing
I checked to make sure i got most files with:
find . -type f | egrep "/\d" | egrep -v "t\d" | grep -v /mp/ | grep -v /imports/

and that program entries were fixed:
find . -name \*.yea | xargs fgrep program | grep "/t"

Checklist

Include reference to internal ticket "Fixes WB-NNNN" (and github issue "Fixes #NNNN" if applicable)

Looks awesome! Could you please fix the assertions in these tests: https://app.circleci.com/pipelines/github/wandb/client/13803/workflows/2744e841-cefd-4090-8156-97072e68bb16/jobs/227522


update header footer based on mockups

Footer isn't sticky. Not blocking but would be nice.
Browser metadata
Path:      /about/
Browser:   Firefox 113.0 on Mac OS 10.15
Viewport:  1280 x 1330 @2x
Language:  en-US
Cookies:   Enabled

Open in BrowserStack

Open Deploy Preview · Mark as Resolved

@itzsaga for the footer, honestly, I would just put the page background to black and it will make it look like it is all the way down.

Yea, it is an easy fix. I would just body {background: "#000"} and then in main, we add a #FFF background and pay with the width. I tested this out in browser dev-tools.


[PDI-17179] - Bad truncation of month. Also checkstyle fixes

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/pentahoreporting/PentahoReportingOutput.java
  engine/src/main/java/org/pentaho/di/trans/steps/script/ScriptAddedFunctions.java
  engine/src/main/java/org/pentaho/di/trans/steps/scriptvalues_mod/ScriptValuesAddedFunctions.java
  engine/src/main/resources/org/pentaho/di/trans/steps/streamlookup/messages/messages_de_DE.properties
  engine/src/test/java/org/pentaho/di/trans/steps/script/ScriptAddedFunctionsTest.java
  engine/src/test/java/org/pentaho/di/trans/steps/scriptvalues_mod/ScriptValueAddedFunctionsTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.1% (click to expand)
org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.core.injection.bean.BeanInjector

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.tableoutput.TableOutputMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.gpload.GPLoadMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

License header violations

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/main/java/org/pentaho/di/trans/steps/pentahoreporting/PentahoReportingOutput.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/main/java/org/pentaho/di/trans/steps/scriptvalues_mod/ScriptValuesAddedFunctions.java. Found 2017. Was expecting 2018

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/engine/src/main/java/org/pentaho/di/trans/steps/pentahoreporting/PentahoReportingOutput.java

:heavy_exclamation_mark: Using the '.' form of import should be avoided - java.awt.. at Line: 76


Fixing Issue #4104 Create Docs Component Button

Hey, I just made a Pull Request for Issue #4104 !
It was just a url fix : /create -> /create/docs-template
@emkidwell @OrkoHunter
For :  "let a Backstage Integrator decide where the button should take the user"
Could you please Explain me what exactly we want to do

Tagged wrong Emma @emmaindal 😅


Determine python version support

Split off from #520. What versions of python do we support for running repo2docker? Note that this is different from what version of python repositories being built with repo2docker can request.

My personal instinct is to go with whatever the latest LTS of Ubuntu ships with - in this case, that's 3.6. But I don't have particularly strong opinions here, since we don't use the biggest improvement of 3.5 (async) here.

I would be conservative in what we require. A bit like a while back when projects were still supporting Python 2. You'd not try to break it "on purpose" by exploiting lots of new features in Python 3 and when you did introduce something that didn't work in Python 2 there was an attempt to change the code.
The conservatism is mostly motivated by the fact that we target scientific users who are often stuck with linux systems which are "quite old". As well as not under the users control. For example with f-strings: I like using them but the code will be run by many more people than those who type it -> I type out .format(...).

One thing to look forward to when we can pin repo2docker versions #490 is that r2d will run in a container so we can use whatever Python we want (yay!) as long as we have a very small "init" script that runs on most Pythons. I have hope that we make progress on this in the near future which also makes me think we should be conservative (so as to not lose users before we reach version nirvana).

I think part of the point of LTS versions is that they are supported for a long time even if there's a new one, so I don't think dropping support the moment a new LTS is released is quite appropriate if LTS is our reference. If we do go by Ubuntu LTS as a reference, it should probably be the oldest still-supported LTS, or something like "last two LTS versions" since there are always three supported, I think. 14.04 is still supported until April of next year, and it has 3.5. 16.04 is supported for another two years and also maxes out at 3.5.
On the other hand, since repo2docker is a docker tool and can itself be run in docker, I think we could also choose to be more aggressive and point documentation to running repo2docker itself in docker, since using r2d already requires everything you need to run r2d itself in docker. Then folks who are stuck with old Python (this means they don't have access to backports or conda), they can always run r2d itself via docker:

needs to mount docker.sock so the container can create the 'real' containers
needs to specify user id and name explicitly, since discovery doesn't work and --user at the docker level may not get the right permissions

docker run --rm -v/var/run/docker.sock:/var/run/docker.sock -it jupyter/repo2docker:0.7.0 \
    jupyter-repo2docker --user-id=$(id -u) --user-name=$(whoami) https://github.com/binder-examples/requirements


Typo fix GitHUb -> GitHub

EOM

Thanks! I only just discovered the spell-checker in R Studio this morning.. Lots to learn still! #noob :)


Python API pose GPU utilisation

I have diligently followed the instructions on a Jetson Xavier NX found here and managed to successfully use the python API (specifically .solutions) for pose estimation to query the keypoints in an image. I would like to ask - in such a scenario, is the GPU enabled and utilised? i.e. are there seperate bazel build procedure/ configurations to enable and utilise the GPU?
Thanks and best regards.

The prebuilt MediaPipe Python wheels only have the cpu graphs and running those solutions doesn't require GPU. It's possible to modify the config and build a local gpu version of the Python package. See https://github.com/google/mediapipe/issues/1042. Note that that post assumes the version is v0.7.9 not the current version.

The prebuilt MediaPipe Python wheels only have the cpu graphs and running those solutions doesn't require GPU. It's possible to modify the config and build a local gpu version of the Python package. See https://github.com/google/mediapipe/issues/1042. Note that that post assumes the version is v0.7.9 not the current version.

@jiuqiant thank you so much for your reply - will give the instructions found in #1042 a shot. I can't seem to find a v0.7.9, do the instructions still hold if I were to work on the master branch?
Also, would there still be a need to setup OpenCV (since OpenCV comes inbuilt with Jetsons) if I was solely using the Python API?

@jiuqiant thank you so much for your reply - will give the instructions found in #1042 a shot. I can't seem to find a v0.7.9, do the instructions still hold if I were to work on the master branch?
Also, would there still be a need to setup OpenCV (since OpenCV comes inbuilt with Jetsons) if I was solely using the Python API?

"undefined symbol: _ZN2cv3MatC1Ev" means opencv is not linked correctly. Do you install opencv locally and build mediapipe python by python3 setup.py gen_protos && python3 setup.py install --link-opencv. If you plan to compile opencv with mediapipe, try python3 setup.py gen_protos && python3 setup.py bdist_wheel.

We are closing this issue for now due to lack of activity.

I have got the cpu version mediapipe , but now I want to get the gpu version
then
I follow the #1042 ,
add the
--copt=-DMESA_EGL_NO_X11_HEADERS --copt=-DEGL_NO_X11
in two places,
but I get a error:
when I run the code:
python3 setup.py gen_protos && python3 setup.py bdist_wheel
the error like this :
`nx@nx-desktop: -/mediapipe
／usr/bin/gcc-U_FORTIFY_SOURCE-fstack-protector-Wall-Wunused-but-set-parameter -Wno-free-nonh
－object-fno-omit-frame-pointer -gθ -02 '-D_FORTIFY_SOURCE=1' -DNDEBUG-ffunction-sections. . . (r
ining 69 argument (s) skipped)
Use--sandbox_debug to see verbose messages from the sandbox gcc failed: error executing command
r/bin/gcc -U FORTIFY SOURCE -fstack-protector -Wall -Wunused-but-set-parameter-Wno-free-nonheap
ect-fno-omit-frame-pointer-g0-02 '-D_FORTIFY_SOURCE=1'-DNDEBUG -ffunction-sections. . . (remai
g 69 argument (s) skipped)
Use--sandbox_debug to see verbose messages fron the sandbox
mediapipe/calculators/tensor/image_to_tensor_converter_gl_buffer.cc: In function 'absl: :lts_2020
23: : StatusOr <std: :unique_ptr <mediapipe: : ImageToTensorConverter> > mediapipe: : CreateImageToGLBuff
nsorConverter (mediapipe: : CalculatorContext*,bool,mediapipe: : BorderMode) ':
mediapipe/calculators/tensor/image_to_tensor_converter_gl_buffer.ck: 342: 10:error:could not con
＇result' from 'std: :unique_ptr <nediapipe: : {anonymous}::GlProcessor,std::default_delete<mediapi
｛anonymous} : : GLProcessor> > 「to 'absl: :lts_2020_09_23: : Status0r <std: :unique_ptr <mediapipe: : Image
nsorConverter> >
return result;
Target//mediapipe/modules/face_detection:face_detection_short_range_cpu failed to build
ICes to see the command Lines of failed build steps.
`
How can I do next？
in jeton xavier ubuntu 18.04

I have got the cpu version mediapipe , but now I want to get the gpu version
then
I follow the #1042 ,
add the
--copt=-DMESA_EGL_NO_X11_HEADERS --copt=-DEGL_NO_X11
in two places,
but I get a error:
when I run the code:
python3 setup.py gen_protos && python3 setup.py bdist_wheel
the error like this :
`nx@nx-desktop: -/mediapipe
／usr/bin/gcc-U_FORTIFY_SOURCE-fstack-protector-Wall-Wunused-but-set-parameter -Wno-free-nonh
－object-fno-omit-frame-pointer -gθ -02 '-D_FORTIFY_SOURCE=1' -DNDEBUG-ffunction-sections. . . (r
ining 69 argument (s) skipped)
Use--sandbox_debug to see verbose messages from the sandbox gcc failed: error executing command
r/bin/gcc -U FORTIFY SOURCE -fstack-protector -Wall -Wunused-but-set-parameter-Wno-free-nonheap
ect-fno-omit-frame-pointer-g0-02 '-D_FORTIFY_SOURCE=1'-DNDEBUG -ffunction-sections. . . (remai
g 69 argument (s) skipped)
Use--sandbox_debug to see verbose messages fron the sandbox
mediapipe/calculators/tensor/image_to_tensor_converter_gl_buffer.cc: In function 'absl: :lts_2020
23: : StatusOr <std: :unique_ptr <mediapipe: : ImageToTensorConverter> > mediapipe: : CreateImageToGLBuff
nsorConverter (mediapipe: : CalculatorContext*,bool,mediapipe: : BorderMode) ':
mediapipe/calculators/tensor/image_to_tensor_converter_gl_buffer.ck: 342: 10:error:could not con
＇result' from 'std: :unique_ptr <nediapipe: : {anonymous}::GlProcessor,std::default_delete<mediapi
｛anonymous} : : GLProcessor> > 「to 'absl: :lts_2020_09_23: : Status0r <std: :unique_ptr <mediapipe: : Image
nsorConverter> >
return result;
Target//mediapipe/modules/face_detection:face_detection_short_range_cpu failed to build
ICes to see the command Lines of failed build steps.
`
How can I do next？
in jeton xavier ubuntu 18.04

Hello, have you solve this?
I'm facing same problem with "return result;" in image_to_tensor_converter_gl_buffer.cc


where

numpy.where takes three arguments (ignore the single-argument version: it's equivalent to nonzero and we can do that other ways):

condition, a boolean array
x, any array
y, any array

and returns a single array with x values if condition is true and y values if condition is false.
We can do this in Awkward even if x and y are not the same type; ak.where would return a UnionArray (my issue #54).
If x and y do have the same type, we can return something simpler. Actually, we can do well by implementing the general case with UnionArray first, then add special cases like "both are NumpyArrays of the same format" or "both have ListType with compatible content," one by one as needed.

This was a frequently requested feature (see old issue, also frequently requested in person).


refactor:convert type of serialize struc to global

Hi Ludwig,
I have changed the type of the structure for serialization to global type in ZIF_DBBR_TY_GLOBAL and replaced the places where it was used.
Best regards,
Renata

and I included also the fix for Issue #5

Thanks Renata, for fixing this 🎉
Regards,
Ludwig
Fixes #5


Azure SQL Data Warehouse adapter

Hi,
I'm working on an adapter for Azure SQL Data Warehouse. I've read through: https://docs.getdbt.com/docs/building-a-new-adapter
I think I'm all set, but opening the ticket to start convo. I plan on basing the implementation on the postgres/redshift adapters.
Let me know if you've got any other tips or things I should know.

Hey @ichavez! That's great! There may be minor differences between that doc and reality - I think we changed a couple of tiny things in the adapter contract between 0.13.x and 0.14.0.
If you're looking for inspiration, check out https://github.com/fishtown-analytics/dbt-spark -- this is an 0.14.0 compatible plugin for Spark. Definitely also check out the dbt-postgres, dbt-snowflake, and dbt-bigquery folders over here: https://github.com/fishtown-analytics/dbt/tree/dev/0.14.1/plugins
Let me know if there's anything I can help out with as you get underway :)

I would be down to help with this as well. was about to start in tonight :)

A couple things we may need to consider early:

ADW does not support updates from CTEs
ADW does not allow joins in CTAS (ie SELECT ... INTO)
Like most DWs ADW does not support correlated subqueries

@norton120 awesome! Do you know how compatible the sqlserver and ADW connection semantics / SQL dialects are? Check out this prior art! https://github.com/mikaelene/dbt-sqlserver

Hi all, sorry for the delay.
It's about 90% the same queries. However SQL Data Warehouse supports more "warehouse" features such as CTAS. See: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-table-as-select-azure-sql-data-warehouse?view=aps-pdw-2016-au7
And a few commands are slightly different: https://docs.microsoft.com/en-us/sql/t-sql/statements/rename-transact-sql?view=aps-pdw-2016-au7
In terms of DBT, one important feature of Data Warehouse is the "distribution", which determines whether your table is partitioned or replicated to all the nodes. See:  https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-tables-distribute
Unfortunately dbt-sqlserver uses the pymssql driver, AFAIK it does not support connecting to SQL Data Warehouse. Microsoft only endorses pyodbc, which supports DW connections. See: https://docs.microsoft.com/en-us/sql/connect/python/python-driver-for-sql-server?view=sql-server-2017
@jacobm001 started a dbt plugin using pyodbc at https://github.com/jacobm001/dbt-mssql .
And... generously added an Apache license to it.
I will be building our SQL Data Warehouse adapter on his, and expect to publish it by next week.

Thanks for the update @ichavez!
One thing is becoming clear: we (the core dbt maintainers) need to do a better job of collecting and sharing information about which community-contributed plugins exist. I wrote up a quick issue over here https://github.com/fishtown-analytics/dbt/issues/1655 - if you have any thoughts / opinions on the topic, I'd love to hear them!

Hi! I can change my license for dbt-SQLServer if that’s a problem? Regarding pymsql vs pyodbc, it was just so much easier to connect to sql server with pymsql from a Mac. You probably just need to change the connections.py to pyodbc. All other will work the same. If someone have a azure sql dw to share, I can chip in on the development 😀

One more thing. The CTAS feature of dw will probably make it much easier in the development of the adapter! Why isn’t that in standard SQLServer?

I never got the @ notification sorry. A couple other things worth noting, the Authentication option needs to be set for Azure AD or service discovery (I actually have never got it to work using pyodbc without the option set). There is also a weird hanging transaction that seems to cause the initial handshake to return an error with ADW; setting autocommit=true in the option avoids this behavior.
so this should probably have options for Authentication and Autocommit si?

@ichavez do you have a fork up I can contribute to? I would really like to help get this over the curb

I'm going to take a pass at this using pyodbc. I'll get a WIP up as soon as I can

Hi there, we're looking at the Azure SQL Data Warehouse platform and the dbt space but it doesn't have that functionality right now. We would be interested in contributing. Let me know! @ichavez

So the test environment is a little more complex than I expected - I'm wrapping together a docker container so dev easy and we can chip away.  ADW seems sad about execute('BEGIN') at this very moment ... I'll try to get that WIP up in the next hour or so

Hi all @norton120 @DVAlexHiggs .
This is the initial commit: https://github.com/1A-Auto/dbt-azuredw
I just created a few models with table, view, incremental materializations, and all seem to be working. But, as you can see, it's pretty basic for now.
I'm sure performance can be improved over the default "incremental" implementation, but it works for now.
Also, the table materialization supports a "distribution" setting. It does not work while setting it as default on your dbt_project though.

Hey @ichavez , sorry I missed this - I put up a WIP repo here https://github.com/norton120/dbt-azuredatawarehouse just now. The docker container loads up jaffle_shop and the integration test repo as well if that helps? I found I also need to specify 'Authentication', not sure if that's due to our ADW security settings or what.
I looked at the connections file quick, it looks like you are overriding add_begin_query() and add_commit_query() - is DBT running outside a transaction then? I'm finding ADW has some weird commit behavior.

I looked at the connections file quick, it looks like you are overriding add_begin_query() and add_commit_query() - is DBT running outside a transaction then? I'm finding ADW has some weird transaction behavior.

and now I'm realizing how limited ADW transaction support is :( so autocommit seems like it may be the best way to go here then.

About transactions... yes, we typically want to be able to completely recreate our models from source tables, so there's little use for transactions. Even with incremental or snapshot models, the best practice seems to implement them using CTAS, which is minimally logged operation.
As you probably know, DDL operations are not supported, so it would be hard to work around that in dbt. See: https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-develop-transactions#limitations

@ichavez do you want to make yours a stand-alone repo so I can fork it and PR against it - since mssql  server / ADW will end up being 2 different adapters? I'd like to move the docker env and the authentication stuff to yours

Hi thanks for the replies, apologies for the delay in my response!
How best can I contribute? Where is development needed most? Looking forward to working on this

@DVAlexHiggs I think the convention we are working with would be to log / work from issues here https://github.com/jacobm001/dbt-mssql, if it's an ADW-specific feature PR against https://github.com/1A-Auto/dbt-azuredw

closing this one - out of scope for core

We were also looking for this and ended up rolling our own with some help from the community re: macros. Most of the existing repos were abandoned ~ dbt 0.15 and we're now supported 0.18. We're committed to supported this since it is also required for our day-to-day business.
https://github.com/embold-health/dbt-azuresynapse
apologies in advance for the necropost!


No pictures in what-if

I noticed, there are no pictures displayed for the what-ifs, just some tiny * or something like that which shows the alt-text when touched. Switching to offline mode for what-if and being on W-LAN instead of mobile internet did not change that behaviour, so I assume it is not related to those settings.

Weird, got a screenshot?

http://imgur.com/RSG5K7a

Happens with every what-if article? Or just this specific one?

With every one. I am currently on v3.1 from F-Droid on a Cyanogenmod 12.1 device without gapps.

Could maybe be an issue with the missing gapps.. Clearing app data does not work either?

Clearing app data solved it, thanks. I'll just assume it was caused due to some changes from an update. If it happens again, I will try to debug it a little more.


Custom Wave Animation

Hi ! First I have to tell you that this is a great library.
I'm trying to update de color using a custom wave form instead of the "WaveForm" feature that comes with the API, but when I try to update the color ( i'm just changing the brightness), the fixture starts to flicker. I' m updating the brightness each 1ms.
If  increase the time between each update (each 500ms) it works,  but is not a smooth change. Any suggestions? I'm new working with node js, so i don't know if I'm updating properly the color on the Fixture, I use a "setInterval" function to update it.
Thank you.

 From LIFX LAN protocol documentation:

Limits

Maximum recommended message transmit rate to a device: 20 per second

The only way I know to achieve faster or smoother updates using regular color/brightness messages is to set a duration for the transition.


Enhance hpcrun_reify_metric_set to eagerly allocate metrics_kind

The existing hpctoolkit doesn't have the bug I mentioned in the meeting last week. Originally, I thought hpcrun incorrectly attributes metrics if there are multiple metrics kind because the allocation interface hpcrun_reify_metric_set does not consider the case when different metric_ids are passed for the same cct_id.
However, the bug actually was resolved by myself back to 2019 in this commit:
https://github.com/HPCToolkit/hpctoolkit/commit/0a4707c8be275fd5427269c2e89c4c1501921932
This commit guarantees the correctness of metrics attribution by lazy initialization of all the metric kinds. The following code change propose a solution to early initialize metric kinds directly in hpcrun_reify_metric_set. Hope this change could make the code clearer.
If needed, I can remove the previous code and test if early initialization is enough.

I read the code and approve of the change. This indeed makes the allocation of metrics clearer.