Improve build documentation and Error Handling

You might want to add into the instructions a step to copy the fmodL.dll, and the fmodstudioL.dll into the build bin folder. I kept getting crash errors when trying to run Godot until I went into the fmod api and found those dll's and put them in the bin folder (which was just a guess on my part from some past c++ usage). Hopefully that's the right thing to do. I haven't gotten a chance to test out the API you put together. By the way, thanks for porting to Godot 4! I'm always really surprised, and impressed to see how much work people put into this stuff.
Edit: 'Project Settings/Fmod' don't show up in the Project Settings menu. And I can't get sound to play from a bank file. I tried one I made, plus an example music file from the Fmod studio project. Are there any easy things i can check to troubleshoot this? None of the functions fail, but the create_event_instance returns Object#Null when I print it, so seems like something isn't set up right. It does print a statement that the initialize function was successful.

Project Settings/Fmod is only visible when 'Advanced Settings' is enabled in the settings viewer.

Thanks for your suggestion. I guess I should revisit this project and improve it for other's use. This initially started as an internal project for my own game! I'll add instructions for the dll's, improve documentation, and add some more QoL changes (such as adding Event pickers to the Inspector). I'll look into what may be causing your issue shortly!

e123447 improves error handling for this project. Can you recompile your project with the new changes and see if it tells you any better info? Hope this helps!

21e314f9d69edd0cf5a05f94a7c006abece779be closes this issue.

Finally got a chance to test the recompile, and it throws a few errors.

Admittedly, I don't know anything about FMOD. I'm doing this because the sound guy for my project wanted to use FMOD, and I am working with Godot 4 (You're project is the only one that was geared toward 4).
Here's a simple piece of code I put together to test the API.
extends FmodManager

var music_vca:FmodVCA;
var fmod_event

# Called when the node enters the scene tree for the first time.
func _ready():
	initialize(1024, FmodManager.NORMAL);
	load_bank("Sound/FMOD/Master.bank", FmodManager.NORMAL_LOAD);

	fmod_event = Fmod.create_event_instance("Sound/FMOD/Music.bank", true, true)
	print(fmod_event)
	load_bank("Master.strings.bank", FmodManager.NORMAL_LOAD);
	Fmod.play("Sound/FMOD/Music.bank")#, FmodManager.NORMAL_LOAD);
	print('This was entered')

Can you take a screenshot of your project directory? The error you're getting is because Fmod could not find the bank you wanted to load.
I'm also noticing that you're creating an Event Instance using a path to a sound bank instead of a path to an Fmod Event. A quick and easy way to get the path to an event you've created is by right clicking on it and clicking Copy Path

Kind of sounds like I'm just not using FMOD correctly, and it's got nothing to do with your code. I assumed a bank file was the sound file that I created.


[flashv2/BW] nan in some configurations

Hi, after upgrading Flashv2 to 2.0.4 (in https://github.com/facebookresearch/xformers/pull/816), we still have some test failures in xformers. Here is a simple repro code:
Repro code:
# Tested with
# flash-attn 2.0.4 (v2.0.4 - d30f2e1cd50185c98ed88c0684b4a603f15bee37)
# torch==2.0.0
# NVIDIA A100-SXM4-80GB
# cuda 11.8
import torch
import flash_attn

q_cuseqlen = torch.tensor([0, 76, 110, 256], device='cuda', dtype=torch.int32)
k_cuseqlen = torch.tensor([0, 1, 2, 3], device='cuda', dtype=torch.int32)
Mq = 256
Mk = 3
H = 1
K = 32

torch.manual_seed(0)
q = torch.randn([Mq, H, K], dtype=torch.float16, device="cuda") * 3
k, v = [torch.randn([Mk, H, K], dtype=torch.float16, device="cuda") * 3 for _ in range(2)]
q.requires_grad_(True)
k.requires_grad_(True)
v.requires_grad_(True)

grad = torch.full_like(q, 1.0)

out = flash_attn.flash_attn_varlen_func(q, k, v, q_cuseqlen, k_cuseqlen, Mq, Mk, causal=True)
out.backward(grad)

print("flash_attn", flash_attn.__version__)
print("Q gradient:", "NaNs!" if q.grad.isnan().any().item() else "OK")
print("K gradient:", "NaNs!" if k.grad.isnan().any().item() else "OK")
print("V gradient:", "NaNs!" if v.grad.isnan().any().item() else "OK")

Output
flash_attn 2.0.4
Q gradient: NaNs!
K gradient: OK
V gradient: OK

I replicated the results above on a 3090 as well. The result is also the same changing float16 to bfloat16.

Thanks for the bug report.
Something I don't quite understand: the cuseqlen says there are 2 sequences, one from indices 0 to 46 and one from indices 46 to 256. However, the K & V passed in only has length 2, so it doesn't agree with what cuseqlen is describing.
Do you mean to pass in a different cuseqlen for K & V?

Woops my bad indeed. Let me close this and reopen once I figure out my issue

Reopening - I fixed the repro script.
The issue only happens with causal=True, although in this case there is no causal masking needed in practice (because we have only 1 key/value)

I've (hopefully) fixed this in v2.0.8. CI is building all the CUDA wheels now. Thanks for the bug report again!

Confirming that all xformers tests pass now on A100 :)
Thanks a lot for the prompt fix!


some problems in data_process.md

When i follow data_process.md to setup environment and download models, i realize some problems about downloading models. The original text said "download our Pose model dw-ll_ucoco_384.onnx and Det model yolox_l.onnx, then put them into Champ/annotator/ckpts/", the "Champ" is the root directory of the project or "pretrained_models/champ",or should the models be placed in an unopened "annotator/ckpts"?
As shown in the red boxes in the screenshots below, "annotator" and "hmr2" don’t feel like third-party libraries, but there is no relevant directories in repo. Has it not been released yet?

Yes, "Champ" means the root directory of the project.
For hmr2 and DWPose dependencies, you can just follow "Install dependencies" section in data_process.md.

Yes, "Champ" means the root directory of the project.
For hmr2 and DWPose dependencies, you can just follow "Install dependencies" section in data_process.md.

Sorry, this is my problem. Because of the network environment, I could only install it offline, so I did not use "pip+git" in the working directory. The above problem occurred without detailed analysis of the project structure. Thanks for your quick reply!!!


transparent mov not created

using this command 'backgroundremover -i "/path/to/video.mp4" -tv -o "output.mov"
I get the following result, the entire video is like this.

Using the website https://www.backgroundremoverai.com with this video gives the same result.


typo in decaying the learning rate example

From example in docs:

learning_rate = tf.exponential_decay(starter_learning_rate, global_step,
100000, 0.96, staircase=True)

should match function definiton above tf.train.exponential_decay.

Thanks, fixed this in our internal repo -- will push out the fix some time this week.


Get linting and tests running

This build should fail.
This should now pass.
I have only fixed the linting errors that can be fixed with --fix so far and the existing tests are broken.
Todo:

[x] Fix linting
[x] Fix tests

This makes me happy :). I like the airbnb lint rules a lot.

I'm working on the broken tests on another branch. I found these while investigating a separate bug. https://github.com/unchained-capital/caravan/tree/input-address-bug

I'm working on the broken tests on another branch. I found these while investigating a separate bug. https://github.com/unchained-capital/caravan/tree/input-address-bug

Nice, I can cherry-pick those in when you get them fixed and meanwhile I'll work on the linting issues.

This is ready to be reviewed and travis be green at this point.

Is this still failing just because it's not running yet on wallet-dev?

Part of this work was to set some types of errors to warnings temporarily and then address them later.
Unfortunately there is this:
Treating warnings as errors because process.env.CI = true.
Most CI servers set it automatically.

There is a related issue for create-react-app but it's since been closed (and censored): https://github.com/facebook/create-react-app/issues/3657
As far as I can tell we could handle this by one of these options:

Disable linting for the warnings
Move away from create-react-app for our scripts
Fix the warnings

Ultimately, I think we should do all three but I don't have enough context to do option 3 and option 2 seems like a fair amount of work so I'm thinking we should just do option 1 for now.  Thoughts?
Additionally it seems like we'll at least need to disable the console.error eslint warnings.

Wow, what a horribly reasoned conclusion for them to come to (at least based on the information they are making available).
I think option (2) is too involved for us to try and do at this point in time, with too little payoff.
For option (1) would this just be adding an ignore comment before each line? This isn't ideal either since it makes lint errors we want to eventually fix hard to identify. Turning off those specific rules seems less than ideal for the same reason.
Two other choices I see are to make the linting job non-blocking for PRs (as a policy that we enforce manually) until all warnings are cleared. We'll just have to make sure to test locally or confirm in Travis to make sure everything that is causing the fail is a warning and there are no errors. I'm happy to take on option (3) at some point very soon, but would rather that not be a blocker to getting this in.
We could also just try once to see if setting process.env.CI = false has any major adverse effects. That issue thread was from a couple years ago and it's possible they made that work and not run in watch-mode (the problem identified in the thread with trying this).

We could also just try once to see if setting process.env.CI = false has any major adverse effects. That issue thread was from a couple years ago and it's possible they made that work and not run in watch-mode (the problem identified in the thread with trying this).

It seems to work fine from what I can tell.
From my search the main thing this flag seems to do is to treat warnings as errors.  I will file a bug to fix the issues in transactionReducer and hopefully we can get to that soon as having CI=false does make me a little weary.


Use the correct method in shape_owner_remove_shape

When I backport #48175 I found that I check for the wrong method in shape_owner_remove_shape.
Also make const the _shape_changed's p_shape parameter.
This PR is not relevant for 3.x as I fix the typo in #48588.

Thanks!


KAFKA-14538: Implement KRaft metadata transactions

Implement KRaft metadata transactions as specified in KIP-868.
This includes creating a new metadata version, IBP_3_6_IV1, which contains the three new records: AbortTransactionRecord, BeginTransactionRecord, EndTransactionRecord.
Maintaining the various offsets and in-memory snapshots in QuorumController was getting too complex. Therefore, this PR splits that logic out into the LogReplayTracker class. This makes it possible to unit test events like Raft leader changes, which is difficult to do when the code is directly in QuorumController.java.

Thanks @cmccabe! Since this PR is already pretty big without the MetadataLoader changes, what do you think about merging this as-is (after reviews) and add the remaining changes as follow-on PRs? Otherwise, I worry it will grow really large and become hard to review.

Fair point. Yeah, let's do that.

duplicate of #14200


Precision on control machine mixed Ansible installation

This PR adds a note about Ansible installation troubleshooting on control machines mixing Ansible system package with pypi packages.
It includes a workaround tip that has been reported working on Ubuntu xenial control machines with ansible <IP_ADDRESS> (installed via apt).
I put it in the main README.md that describes how to get started but maybe the right place is docs/ansible.md (with a reference in README.md), if so let me know

ci check this

/lgtm
/approve


fix: update rum api client

Please ensure your pull request adheres to the following guidelines:

[ ] make sure to link the related issues in this description
[ ] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues
Thanks for contributing!

:tada: This PR is included in version 1.10.8 :tada:
The release is available on:

v1.10.8
GitHub release

Your semantic-release bot :package::rocket:


Available Plugins Table should link to corresponding plugin pages

The table on the page 'Understanding Plugins' should link to the corresponding plugin pages:

Table links added in PR #726


DistanceTool Not Working

I'm trying to integrate the DistanceTool into my Vedo project and I found that it isn't working. I'm using the example given in the documentation
from vedo import *
mesh = ParametricShape("RandomHills").c("red5")
plt = Plotter(axes=1)
dtool = DistanceTool()
dtool.on()
plt.show(mesh, dtool)
dtool.off()

The trackback points to this as the error:
\vedo\assembly.py", line 139, in __iadd__
    self.AddPart(a)
TypeError: AddPart argument %Id: %V

I'm using the most current version of Vedo from pypi (2024.5.2) and Python 3.8.19.
Any suggestions?

Thanks for reporting the issue, I just pushed a fix for it in the dev version:
pip install -U git+https://github.com/marcomusy/vedo.git

This update has fixed the issue! Thank you for your help.


Update for Bootstrap 4 ?

Glyphicons is desupported in Bootstrap 4, and replaced by Font Awesome.
Would it be possible to update js-datatable ?
I can submit a PR, I can see the following update being required :

https://github.com/toni-heittola/js-datatable/blob/master/js/bootstrap-table-filter-control.js

Anything else ?

js-datatable is build on top of bootstrap-table v1.11.1 which supports only Bootstrap v3.  The current version (v1.19.1) of bootstrap-table is supporting Bootstrap v4. Updating the code to use a newer bootstrap-table should be a relatively straightforward process, but it might require major code updates to js-datatable.
I understand that js-datatable is a bit outdated as it is relying on Bootstrap v3, and I am happy to receive PRs to fix this.


make RenditionSettings.type strongly types

RenditionSettings.type can have only specific value so I suppose it must be strongly typed, like:
/**
  * File type: RenditionType.PNG, JPG, PDF, or SVG
  */
    type: "PNG" | "JPG" | "PDF" | "SVG";

Really documentation is unclear if RenditionType stands for specific type or just a way to describe values.

I used application.RenditionType.PNG so I guess it's hardcoded object/class with static properties.

Agreed. I'll fix this in the next release.


More Info hyperlink redirects to dashboard page

On 2.5-head commit id: 118f999

In a downstream cluster --> In the cluster dashboard --> Secrets /Role Template --> Create
Click on More Info for any of the options
redirected back to the dashboard page

On 2.5-head commit id: 93d921f

I see the more info links have been removed.
But they look empty.

Question:

Is this how we want it to be?

How it is on a Create Workload:

Closing this issue as the more info links are removed. And tracking the other request in this issue - https://github.com/rancher/dashboard/issues/2644


power menu doesn't get applied after first boot until it is triggered manually

I've been using classic power menu for around 2 years now, this is such an awesome project!
i rely on it so my phone cannot be turned off from the lock screen
but sadly when i try to access the power menu after a reboot or whatever, the default power menu shows up, then if i exit it and then try again, the classic power menu will stay until the next reboot
that's no big deal but the problem is that i forgot to manually trigger it sometimes
is it caused by my OS or is it a known limitation?
I'm running stock android 14 security patch of april 2024 on a pixel 6 (AP1A.240405.002)
but I've had that since forever, i don't think its related anyways
and thanks for developing such a great solution!

This is normal, it's how the hooking works.


Cataloging appears to fail for name changes

In GitLab by @jakebeal on Oct 30, 2019, 10:39
The experiment request "YeastSTATES CRISPR Growth Curves Request" appears to have been originally cataloged with a typo in its name:

Validation Failed! Schema Validation Error: 'YeastSTATES-CRISPR-growth-cruves' is not one of ['UNKNOWN']  Failed validating 'enum' in schema[0]:     {'enum': ['UNKNOWN'], 'type': 'string'}  On instance:     'YeastSTATES-CRISPR-growth-cruves'

If this is indeed the case, then when the typo was corrected, the catalog failed to update the name, which is causing the intent parser to be unable to look it up.  I believe this likely indicates that the catalog is in general ignoring name changes in Experiment Request documents.

In GitLab by @mweston on Oct 30, 2019, 14:05
Ah - this is a little different. I believe the updated experiment references are not making it into the schema for validation purposes:
https://schema.catalog.sd2e.org/schemas/experiment_reference.json
I've updated this for now, but will need to factor this into the Jenkins syncing process:

Regen schemas
Commit diffs
Push to gh-pages branch
Push to GitHub mirror

In GitLab by @mweston on Oct 30, 2019, 14:21
Looking into this, there is also likely an issue with the name submitted for validation - e.g. it's using the old name still.

In GitLab by @jakebeal on Oct 30, 2019, 14:21
Whatever you did has in fact let things move forward to the next validation failure, at least, which seems to be a different issue.

In GitLab by @mweston on Oct 30, 2019, 16:25
Yes - I updated the schema references to account for the latest submitted requests. The 1-4 listed is to automate this process so it's no longer manual.
Still looking into the "old name" submission issue.

In GitLab by @mweston on Nov 11, 2019, 11:15
https://gitlab.sd2e.org/sd2program/python-datacatalog/merge_requests/190 addresses an underlying issue with document renames creating duplicate experiment designs

In GitLab by @jakebeal on Nov 11, 2019, 11:53
Does this mean this issue is now resolved, or not yet?

In GitLab by @mweston on Nov 11, 2019, 13:09
@jakebeal once that MR is merged, this will prevent duplicate designs from being created, which will help.
We'll still need implement an automated process to sync the experiment request names. All of the current requests are accounted for; this will be to future-proof against future requests.

In GitLab by @mweston on Nov 12, 2019, 15:58
@jakebeal the above MR has been merged, preventing duplicate experiment designs, and I've added an automated sync for the experiment reference names to  the existing Jenkins job. This issue should be fully resolved at this point. You should not see any further issues here. If so, please re-open. Thanks!

In GitLab by @mweston on Nov 12, 2019, 15:58
closed


facebook/twitter meta in head

From @jhil on March 5, 2015 8:22
Copied from original issue: StartupShell/web-2015#29

From @jhil on September 25, 2016 20:48
https://developers.facebook.com/docs/sharing/webmasters
https://dev.twitter.com/cards/markup

Meta added


setup command fails

$ intheam setup
Traceback (most recent call last):
  File "/home/cemsbr/.pyenv/versions/3.6.2/bin/intheam", line 11, in <module>
    load_entry_point('taskwarrior-inthe.am==0.1.1', 'console_scripts', 'intheam')()
  File "/home/cemsbr/.pyenv/versions/3.6.2/lib/python3.6/site-packages/taskwarrior_inthe_am/cmdline.py", line 57, in main
    COMMANDS[args.command[0]]['function'](config, args, *extra)
  File "/home/cemsbr/.pyenv/versions/3.6.2/lib/python3.6/site-packages/taskwarrior_inthe_am/commands.py", line 74, in setup
    api = get_api_connection(config)
  File "/home/cemsbr/.pyenv/versions/3.6.2/lib/python3.6/site-packages/taskwarrior_inthe_am/api.py", line 19, in get_api_connection
    'api_key',
  File "/home/cemsbr/.pyenv/versions/3.6.2/lib/python3.6/site-packages/keyring/core.py", line 41, in get_password
    return _keyring_backend.get_password(service_name, username)
  File "/home/cemsbr/.pyenv/versions/3.6.2/lib/python3.6/site-packages/keyring/backends/fail.py", line 23, in get_password
    raise RuntimeError(msg)
RuntimeError: No recommended backend was available. Install the keyrings.alt package if you want to use the non-recommended backends. See README.rst for details.

What's the recommended backend? There's nothing about it in README.rst and I can't get certificate and key from the web site.

It seems to be missing this from the dependencies, but running pip install keyrings.alt seems to fix this.


Automated cherry pick of #8503

Cherry pick of #8503 on cloud.
/cc  @hmhealey

/release-note-none


2D augmentation using Compose

Hello,
I am using the MONAI API to build a 2D segmentation pipeline. However, when it comes to creating the Dataset, DataLoader and Transforms for augmentation, I run into a problem.
For the Test Dataset, the transformations are applied to the images and labels differently, hence, the label does not match the area of interest anymore. In a 3D setting, I do not have this problem.
Below you can find the code, the images and labels are stored in separate directories as .npy files.
import os
import numpy as np
import matplotlib.pyplot as plt
from glob import glob

from sklearn.model_selection import train_test_split

from monai.transforms import(
    Compose,
    AddChanneld,
    LoadImaged,
    RandAffined,
    RandFlipd,
    RandRotate90d,
    ToTensord,
    # ScaleIntensityRanged,
)
from monai.data import DataLoader, Dataset, CacheDataset, list_data_collate
from monai.utils import set_determinism

path_to_img = r"C:\Users\BKeoh\Data\preprocessed\2D\images"
path_to_label = r"C:\Users\BKeoh\Data\preprocessed\2D\labels"

def prepare(path_to_img, path_to_label):

    images = glob(os.path.join(path_to_img, "*.npy"))
    labels = glob(os.path.join(path_to_label, "*.npy"))

    train_images, valid_images, train_labels, valid_labels = train_test_split(images,
                                                                            labels,
                                                                            test_size=0.2,
                                                                            shuffle=False)

    # After the split, the image and label still fit, I checked this

    train_files = [{'image': image_name, 'label': label_name} for image_name, label_name in zip(train_images, train_labels)]
    valid_files = [{'image': image_name, 'label': label_name} for image_name, label_name in zip(valid_images, valid_labels)]

    # set deterministic training for reproducibility
    set_determinism(seed=0)

    # Define the data transforms and augmentations (random rotation and flips)
    # TODO: Check bone window using ScaleIntensityRanged()
    train_transforms = Compose(
        [
        LoadImaged(keys=['image', 'label']),
        AddChanneld(keys=['image', 'label']), # Add a channel as 1st element
        RandAffined(
            keys=['image', 'label'],
            mode=('bilinear', 'nearest'),
            prob=0.5,
            rotate_range=(0.174533, 0.174533) # +-10° in radians
            ),
        RandFlipd(keys=["image", "label"],
                    prob=0.5,
                    spatial_axis=(0, 1)
                    ),
        RandRotate90d(keys=["image", "label"],
                    prob=0.5,
                    max_k=1,
                    spatial_axes=(0, 1)
                    ),
        ToTensord(keys=['image', 'label'])
        ]
    )

    valid_transforms = Compose(
        [
        LoadImaged(keys=['image', 'label']),
        AddChanneld(keys=['image', 'label']),
        ToTensord(keys=['image', 'label'])
        ]
    )

    train_ds = Dataset(data=train_files, transform=train_transforms)
    valid_ds = Dataset(data=valid_files, transform=valid_transforms)

    return train_ds, valid_ds

train_ds, valid_ds = prepare(path_to_img, path_to_label)

# Check if augs were applied correctly
n = 1200

plt.imshow(train_ds[n]['image'].squeeze(), cmap='bone')
mask_ = np.ma.masked_where(train_ds[n]['label'].squeeze()==0, train_ds[n]['label'].squeeze())
plt.imshow(mask_, cmap="autumn")

plt.show()

I encountered the same issue as you did. Take RandRotate90d as example.
RandRotate90d(keys=["img","seg"], prob=0.5, spatial_axes=[0,1])

Sometimes the image (also on 2D in my case) has been rotated by 90 degrees, while the labels may have been rotated by 180 degrees.
I wonder if it is really a bug?

Hey,
thanks for your reply. I figured out as well, that its an issue with calling the dataset.
After loading everything into the Dataloader, I extracted a batch and checked again, everything was fine!
Cheers


Fixed Badge Spec URL in Tutorial

I found a broken link in the tutorial document where it mentions the additional documentation for the URL conventions. changed this to a relative link to the Markdown File in question.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @JoeIzzard!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS against d899910d8330775947764a01a4cf9d58b9d162c4


Updated Proguard set up; added dbuild-specific entry point

A methods needed by dbuild has been added, with the related
Proguard settings. The Proguard version has been updated,
and optimization level bumped up a little. Closes #22.

This should be good to merge, and to release as 1.0.2.

Closing this request, since controlling Proguard as needed for this application is just too messy. Dbuild now uses a slightly customized fork of the launcher in which Proguard optimization is disabled: https://github.com/typesafehub/dbuild-launcher


change XML launch files to python examples

Is your feature request related to a problem? Please describe.
Python launch files in ros2 allow more flexibility than XML, in particular they can be easily composed using launch.actions.IncludeLaunchDescription
For example, rai_state_logs integration implemented in https://github.com/RobotecAI/rai/pull/314 can't be easily integrated with demo projects in simulations. For every example from this list rai_state_logs configuration shall be copied.
It would be better to have launch file implemented once in rai_state_logs package (already done in https://github.com/RobotecAI/rai/pull/322), which is imported in demos launches.
Additionally, some launch files in rai are already written in Python (see rai_bringup), therefore it would be nice to have consistency.
Describe the solution you'd like
Refactor all rai launch files to python.
Describe alternatives you've considered
Additional context

This issue has been resolved when PR was merged


[CARBONDATA-1971][Blocklet Prunning] Measure Null value blocklet prunning optimization

Recognise Null values in blocklets so that it can help in filter prunning.
Exclude filter isScanRequired is modified in order to help driver for blocklet prunning.

[x] Any interfaces changed? Yes

[x] Any backward compatibility impacted? No

[x] Document update required? No

[x] Testing done Yes
Please provide details on
- Whether new unit test cases have been added or why no new tests are required? Yes
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.  NA

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3432/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3050/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4294/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5183/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3973/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4466/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7125/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5901/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/53/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8802/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/735/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/557/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9846/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2182/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10257/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3564/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/80/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/79/

Build Failed  with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/79/


NIFI-6597 Azure Event Hub Version Update

NIFI-6597 - Upgrade Azure Event Hub Version from current 0.14.4 (outdated) to the newest 2.3.2 and EPH 2.5.2.

@pvillard31 Can you take another look at the change? I believe you comments are addressed

@pvillard31 Could you review again please?

Whenever referencing/presenting NiFi for external things it should be Apache NiFi. I recommend this string be ApacheNiFi, azureeventhub/2.3.2"
It is also quite odd to be setting this value of this impl class this way. Are there no better options?

Thanks :)
Good call on the ApacheNifi name! I changed it accordingly.
As to the User_Agent setting,  double checked with @JamesBirdsall - this is currently the only way.

@joewitt Could you check again? I believe your concerns are addressed :)

@mysunnytime can you please describe what testing/verification has been done for this?

@mysunnytime can you please describe what testing/verification has been done for this?
Sure.

There are three unit test for the three processors (PutAzureEventHub, GetAzureEventHub, and ConsumeAzureEventHut). They all passes. For this pr, we just upgraded the Event Hub api version and did not change the functionality, so no new test added.
We also test the three components from the Nifi GUI to send/receive events to event hub. Before our updates, processors initialization will fail with ServiceBusException: TransportException (because it uses a really old version of Event Hubs Java client, which uses a really old version of Proton-J, which exhibits this problems when used with current versions of the Java runtime). After the api upgrade, the three components work as expected. Send/receive was successful. ApacheNiFi-eventhub version is also successfully send for us to better understand our customer and provide support.

ok thanks - glad to hear it regarding the testing.  I think my only remaining concern for the moment then is the thread pools being created

@mysunnytime Yes it would be great to get this incorporated.  We have 366 issues already addressed and haven't done a release since April.
Features/improvements/fixes get merged off of review traction.  We need someone who can test/vet the changes.  I gave feedback on initial findings/thoughts and I think those are addressed.
If someone can validate the results and merge that is great.  If for any reason 1.10.0 RC1 fails and this gets into master in the meantime I'll grab it then.  Else, we can grab it whenever it is in and the next release comes along.
That the current approach isn't working is unpleasant.  But we have 286+ components in the build by default.  We don't have the infrastructure in apache land to vet all those extension points at all times for regressions.  Doubly hard when such testing would hit public cloud services with billing implications or vendor tools with licenses/etc..

@mysunnytime thanks for the contribution and sticking with us as we worked through this! I was able to test it against Azure EventHubs. Given Joe's comments above, I went ahead and merged to master. Thanks again!


[SPARK-40508][SQL][3.3] Treat unknown partitioning as UnknownPartitioning

What changes were proposed in this pull request?
When running spark application against spark 3.3, I see the following :
java.lang.IllegalArgumentException: Unsupported data source V2 partitioning type: CustomPartitioning
    at org.apache.spark.sql.execution.datasources.v2.V2ScanPartitioning$$anonfun$apply$1.applyOrElse(V2ScanPartitioning.scala:46)
    at org.apache.spark.sql.execution.datasources.v2.V2ScanPartitioning$$anonfun$apply$1.applyOrElse(V2ScanPartitioning.scala:34)
    at org.apache.spark.sql.catalyst.trees.TreeNode.$anonfun$transformDownWithPruning$1(TreeNode.scala:584)

The CustomPartitioning works fine with Spark 3.2.1
This PR proposes to relax the code and treat all unknown partitioning the same way as that for UnknownPartitioning.
Why are the changes needed?
3.3.0 doesn't seem to warrant such behavioral change (from that of 3.2.1 release).
Does this PR introduce any user-facing change?
This would allow user's custom partitioning to continue to work with 3.3.x releases.
How was this patch tested?
Existing test suite.
I have run the test using Cassandra Spark connector and modified Spark (with this patch) which passes.

cc @sunchao

@sunchao
So far, the Cassandra connector is used for verification.
Let me see if I can add a test.

@sunchao @dongjoon-hyun
According to https://github.com/tedyu/spark/runs/8477556657, all tests have passed.

Merged to branch-3.3. Thanks!


Is there anybody who can merge the Pull requests??

It´s very bad to not really have an up to date Repo....

I'm also concerned about the fact that the owner of this project lives in the Ukraine and hope he is okay. But from his contribution activity graph I can also see in the last years that he had the tendency to be very active over the period of a few months and then "disappeared" for a long time again.
There are some substantial contributions by different people in their own forks, such as @markusg1234 @airy10 @Raph22 @carferrer and others.
Anyone interested in putting your efforts together, create an organisation and create a maintained fork there?

I've also contacted @PlusPlus-ua via email, let's see...

Any update to this?
@pathob, have you got any reply?

+1!!
I'm dealing with this issue over and over again since I started with HA/Tuya about a year ago and I really appreciate that somebody opened an issue on this, since I thought about doing the same some time ago.
With every other HA update something breaks completely and another manual workaround is necessary, burried in some comment or (also already abandoned) fork..., even if most of the topics are imo actually covered by the open pull requests contained in this repository.
(For sure the changes on the Tuya-side are also adding to the mix - sometimes I even have the feeling they gradually change things "on purpose".)
And in my case the problem is mainly limited to just keep a BLE Fingerbot working.
I don't want to imagine how others feel having a lot of components in place which are dependent on this integration :D
Don't get me wrong, I really appreciate the work everybody puts into this and I understand and I'm very sorry about the "circumstances" the actual maintainer @PlusPlus-ua is probably suffering at the moment, but this whole thing is just a mess and desperately needs some one taking care of it.
I would really like to somehow support this, I'm even an IT guy, but I'm such a bad developer and never got into git, so I'm not able to take care of this unfortunately...
Is there really nobody able to step into this??
Mabye someone maintaining the several forks?
Or is this some kind of "authorization issue" as well, so that technically nobody can actually do it??
 Convince HACS people to publish migh be another issue.
However, I believe no one have done this before in respect to the situation of this project owner who may be in a difficult situation and incapable of maintaining it.
One approach could be creating a new repo with a promise to transfer it to @PlusPlus-ua when he is back (hopefully soon). There's no guarantees that he will be happy with this approach, but I cannot think in anything more right now.
I can definitely help creating the new repo and trying to convince HACS to publish that (although it still can be used without they publishing it), but I'm definitely not available to invest time on developing or maintaining, other than approving PRs and giving permissions to others to manage it.


Make flag completion opt in

This PR makes flag completion opt-in, fix #19.

Codecov Report

Merging #21 (7382f62) into main (a342b5a) will decrease coverage by 0.41%.
The diff coverage is 89.62%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
- Coverage   86.64%   86.24%   -0.41%
==========================================
  Files          11       11
  Lines        1940     1948       +8
==========================================
- Hits         1681     1680       -1
- Misses        181      188       +7
- Partials       78       80       +2

Files Changed
Coverage Δ

flag.go
86.09% <0.00%> (ø)

default.go
88.23% <66.66%> (ø)

context.go
85.71% <80.00%> (-14.29%)
:arrow_down:

cli.go
79.22% <91.17%> (-1.28%)
:arrow_down:

completion.go
89.39% <91.66%> (-1.45%)
:arrow_down:

command.go
89.30% <92.85%> (+0.62%)
:arrow_up:

option.go
100.00% <100.00%> (ø)

usage.go
90.32% <100.00%> (+0.03%)
:arrow_up:


"click for limits"-options display faulty

Card is working good, but the "click for limits" Option is faulty:

The options are displayed vertically but should be horizontal. Also, not all options are visible.

Hi and thanks for reporting. Yes, I am aware. There's been a problem with the dropdown list since HA deprecated the paper version of dropdown. I tried to do some quick fixes, but it took some time and I wasn't able to complete it before being swallowed by other tasks. I will dig into it eventually, and if anyone sees a quickfix, please contribute.

Hi, first of all a B I G thank you for your work!!! (and you have a large coffee coming your way).
I'm also not able to update the limits list (6-8-10-12-etc.) using the config file.

Hi tmjo,
do you already have had time to look for a solution for this bug?
kind regards

Hi, it is close. I've rewritten everything to typescript instead of plain javascript, so it will hopefully fix all known issues (but probably introduce some new ones, so need a bit more time for testing).

Please test alpha-version v0.2.0-alpha released now. It should fix UI, but please test carefully.

Hi tmjo,
just tested v0.2.2-alpha. Drop-Down feature now works perfekt for me!
I've two different Limits and the menu appears on click right above the used key.

Thank you very much for the solution and your time!

Sounds great! I'll close the issue, please feel free to create a new one if you find any other bugs.


Stripe agent toolkit support

Add support for stripe agent toolkit similar to crewAI and other frameworks:
https://stripe.dev/blog/adding-payments-to-your-agentic-workflows

@the-praxs, this is awesome. @bboynton97 is on it right now

Marking as completed. Thanks @bboynton97.


[Incompatibility issues] Not compatible with Carry On mod

Currently, when using this mod Carry on (https://www.curseforge.com/minecraft/mc-mods/carry-on). After lifting an entity or block, the arm disappears and the object that carries cannot be seen.

Duplicate #160


Breaks when > is in a script or style tag

Below will break.
<script>
    console.log('Script > are not minified');
    console.log('This is inside a script tag');
</script>

I do not understand very well what is this for.

@EdixonAlberto When having an inline script, it breaks in some cases when > character is used because it's also used for open/closing html tags.

There is the same issue in inline style tag.
<style>
    .fa-ul > li{position:relative}
</style>

Is there any solution for this? It happens even if style is inside elements->skip.

I just found your script and wanted to use it in production.
Too bad it broke our inline javascript, so I had to take it down :(
<script>
  a > b ? 'YES' : 'NO';
</script>

becomes:
<script>
  a </script>

Related to this (?): Removes 'unneeded' self slash in function removeSelfSlash.

There is the same issue in inline style tag.

# echo ' /var/www/html/info.php

becomes

# echo '


update repo for feedback

Our repo started getting feedback for SharePoint SDK APIs. Updating the feedback repo of this content to come here instead.
Line 56 is also probably the wrong place for folks to give product feedback, but I can't tell which site they should go for this.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint-server/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[AIRFLOW-2307] Add uuid attribute to TaskInstance, return uuid in CeleryExecutor

…k id
Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2307
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Closes AIRFLOW-2307.  Adds uid to task instance, opportunistically set uid if an id is returned from execute_async.  Returns task id from CeleryExecutor.   This should be generally applicable to other executors with a little work.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Covered by existing tests.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

do you mean UUID?

@bolkedebruin I don't have any religion about uuid/guid, simplified as uid out of habit.  I'll change it to uuid to be consistent with convention.

Updated to uuid.  Thanks @bolkedebruin for the feedback.

I do think this needs to be more comprehensive, ie. support the other executors as well.

and it needs tests, as with the typos that were in it would have failed in any production env.

@bolkedebruin It should be pretty easy to support uuids in all the executors, but I made this in such a way that it's totally optional.  I don't use the other executors generally, but I can take a look at the unit tests and see if this is something I can make time to do.  Certainly LocalExecutor and SequentialExecutor should be easy.  Otherwise, I figured someone who uses the alternatives (dask, etc) would know the best way to do it.
It's my bad for changing uid -> uuid and not actually re-running the unit tests before committing :|   I was going to just confirm it worked in travic-ci.   What specific tests would you like to see?
I am running this in production.  I was running the code before uid -> uuid change. Now I'm running the latest commit.

Updated executors to return uuid (or Future.key for dask, which appears to be a prefixed uuid).  Working on tests.

Added a couple simple tests for the executors returning uuid.  Not sure how to test that the uuid gets set in the model.

Rebased (attempting to get CI builds to pass)

@johnarnold  are you still working on this PR?


It should be possible to select an image file for remove background

Repro steps

Attempt to remove background
Use a custom uploaded image for this

Expected Result
Possible to upload your own image like in previous version
Actual Result
Only this one is available

System Info

Memory leak issue at the moment

Backround keeps flikkering


What is a template?

Approvals that are created from a template still store data in CDS, such as their title, details, template ID, and more. Responses that are submitted on the approval request are stored in Forms. Learn more about  Data storage for Microsoft Forms.
What is a template? Like this ; https://techcommunity.microsoft.com/t5/microsoft-forms-blog/microsoft-forms-powers-approvals-templates-in-microsoft-teams/ba-p/2262158 ?
The cx wants to know more specific information, not concepts, so please describe in which case approvals stored in CDS and not.

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

ID: 055b01ff-ee6c-7d5a-74bd-0e8eed7ee6b5
Version Independent ID: 13c4174f-2a2a-2ef9-14c5-2f10817cc66a
Content: Approvals application availability in Teams - Microsoft Teams
Content Source: Teams/approval-admin.md
Service: msteams
GitHub Login: @cichur
Microsoft Alias: v-cichur

Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @MiyukiAmino, thank you for your feedback and help us to improve docs.microsoft.com.
A template is a pre-created approval that already has some formatting. Rather than starting from scratch to create an approval, you can use the formatting of a template.
The tech community article you shared includes information about how the approval templates work. It doesn't specify what a template is because I understand it's a standard concept.
The "Approvals application availability in Teams" includes some more information about where the approvals templates are store:
"The approval templates are stored in Substrate Data Storage (SDS), which is a compliant storage platform used internally only inside Microsoft. The organization-scoped templates are stored in “tenant shard” of SDS, and team-scoped templates are stored in “group shards” of SDS. This means that the org-scoped templates share the same lifetime of the tenant and team-scoped templates share the same lifetime of the team. So, permanently deleting the team deletes the related templates."

Thank you for taking time to this issue! I can understand what are templates and where are they stored.
But... my essential question is where is approval data stored. Because cx wants to delete approval data manually.
Docs says , "Approvals that are created from a template still store data in CDS".
Q1. so since the word "still" is used, is there any case where they are stored outside of Dataverse?If no, every approval data created by template is in Dataverse? Where are approval data that are not created by template stored?
Q2. What does it mean to be stored in Froms? How do we delete approval data in Forms?
Best Regards.

Thank you for your new comment @MiyukiAmino.
Q1: Approvals created from the Approvals app will be stored in the default CDS environment.
Q2: Responses that are submitted on the approval request are stored in Forms. Learn more about  Data storage for Microsoft Forms.
Unfortunately, I have no more information at this time.

Thanks. I understand. If I need more information, I create IcM.
Appreciate your kind response during your busy time.


Are output coordinates one or zero-based?

Hi!
Thank you for your work!!
I have a simple question: the epic2 output comes in BED-similar format, however, I'm not sure if the output is really 0-based. When I do peak calling, if I check the minimum peak size obtained (which should be equal to the --bin-size argument), by doing End - Start, I get 1 bp less than --bin-size.
E.g. when peak calling with default parameters, the minimum peak size I observe is 199 bp. Thus, to get 200 bp, I would have to do End - Start + 1, which is compatible with the output being 1-based instead of 0-based.
Could you confirm this?
thanks for your help!

I just followed what SICER did. 0-199, 200-499 etc. This means that the start is 0-based and the end is 1-based

:)

Thanks for the response!
But then (and sorry for the misguided/ignorant question), does that mean that the window sizes are actually 199 bp wide?
I was trying to compare them to the UCSC coordinate systems where 0-start + 1-end means the end coordinate is excluded from the intervals. But maybe the meaning here is different or I am (probably) confused.


Add User Profiles

Add user profiles with ratings for enhanced trust and transparency.

Picked up in #12

Closed with #12


flutter webview_flutter  Stack child widget touch Event Pierce through -- iOS

Stack(
              children: <Widget>[
                WebView(
                  javascriptChannels: <JavascriptChannel>[
                    Js_exc_Flutter_getCoordinate(),
                    Js_exc_Flutter_getFeatureUrls(),
                    Js_exc_Flutter_getArea(),
                    Js_exc_Flutter_getPerimeter(),
                    Js_exc_Flutter_getDrawBox()
                  ].toSet(),
                  initialUrl: Api.mapSever,
                  javascriptMode: JavascriptMode.unrestricted,
                  onWebViewCreated: (WebViewController controller) {
                    this.controller = controller;
                  },

                  onPageFinished: (String url) {
                    Flutter_exc_Js_switchBaseMap(1);
                    getCurrentLocal();
                  },
                ),
  ....

iOS

Hello @dkluhack !
Thank you for posting an issue.
Can you please also provide additional information such as an output of the flutter doctor -v command and more information on the issue (what is wrong exactly)?
Thank you.

flutter Stack child:InkWell(.. ,ontap(){ // meanwhile})，webview_flutter JavascriptChannel(.., onMessageReceived: (JavascriptMessage message) { //meanwhile})

Hello @dkluhack !
Thank you for posting an issue.
Can you please also provide additional information such as an output of the flutter doctor -v command and more information on the issue (what is wrong exactly)?
Thank you.

flutter Stack child: webview_flutter JavascriptChannel(.., onMessageReceived: (JavascriptMessage message) { //meanwhile}), InkWell(.. ,ontap(){ // meanwhile})

Hi @dkluhack
Are you still experiencing this issue?
If so, can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Hi @dkluhack
Without additional information, we are unfortunately not sure how to resolve this issue. We are
therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the
bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Twitcha doesn't load the riotgames channel

As the title says, it doesn't load the riotgames channel while it loads any other LoL worlds related channel. And no, they aren't hosting anyone.

This might be due to the riotgames channel using some of the new encoding options, e.g. https://github.com/chrippa/livestreamer/pull/1429
The fork called Streamlink(https://github.com/streamlink/streamlink) has solved this issue, so I'd recommend using that instead, unless you intend to manually merge PR https://github.com/chrippa/livestreamer/pull/1429 into your installation.


Guidance group options differ on Tuuli test and live

Different guidance group options are presented between test and live Tuuli. I created a plan for Tekes on live and got the following options. Finnish DMP guidance is their main generic DMP guidance, akin to DCC guidance.

When re-creating this on test, different options appear. Finnish DMP guidance is absent (along with others) but there is definitely guidance available on this template (see later screengrab) so it's not been filtered out for a reason. The label for 'other institutional guidance' is also missing

I've just realised that it might not be missing guidance group, just that the display names are different...
DCC (UK) guidance > Digital Curation Centre
Finnish DMP guidance > Tuuli
FSD... > Finnish Social Science Data Archive
Are we pulling a different field e.g. org name rather than guidance group name?
It would be best to draw the same so it's less change for users and more intuitive

Because of the very poor main guidance names ("Uni guidance", blank, etc) we had in dmponline, the guidance selection has been rewritten to show the institution name instead of the main guidance name. I believe we should keep it this way as the code should not diverge between Tuuli and DMPonline.

Ok, let's leave it as it stands and see what comes out of Finnish testing. Should we close out for now?

It's intended behaviour so I'd lean towards closing


Missing BaseNameSuppport documentation

There are two links to a BasenameSupport.md document that doesn't exist. One from API.md and another from Histories.md.

A PR is more helpful here. The v2.x branch has the doc: https://github.com/mjackson/history/blob/v2.x/docs/BasenameSupport.md


Parsing: abbreviation "Ver." not recognised

In the NIST source dataset, there are documents with identifiers like NIST SP 800-63 Ver. 1.0. The pubid-nist gem should this kind of version abbreviation.
> Pubid::Nist::Document.parse("NIST SP 800-63 Ver. 1.0")
Failed to match sequence (STAGE? (' ' / '.') REPORT_NUMBER parts:(PARTS{0, })) at line 1 char 8.
cause: Failed to match sequence (STAGE? (' ' / '.') REPORT_NUMBER parts:(PARTS{0, })) at line 1 char 8.
...

@andrew2net can you provide a few more of these identifiers? Where did you get them from? Thanks.
@mico this is only for parsing -- when we generate we must follow PubID.

@ronaldtse I get the identifiers from https://csrc.nist.gov/CSRC/media/feeds/metanorma/pubs-export.zip
SP 800-60 Ver. 2.0
SP 800-63 Ver. 1.0
SP 800-63 Ver. 1.0.1
SP 800-63 Ver. 1.0.2
SP 800-67 Ver. 1

Not so much but we need to handle then somehow.

@andrew2net yes we must handle these identifiers because they are directly from NIST CSRC. Thanks.


carla.Color() do not work correctly when I draw a point using world.debug.draw_point()

Could you provide any examples of what is wrong?

I used world.debug.draw_point(carla.Location(px, py, 0.3), size=0.025, color=carla.Color(128,0,255,0), life_time=0) to show a specified color for the point. But the output of this code is as same as world.debug.draw_point(carla.Location(px, py, 0.3), size=0.025, color=carla.Color(255,0,255,0), life_time=0) and even world.debug.draw_point(carla.Location(px, py, 0.3), size=0.025, color=carla.Color(1,0,1,0), life_time=0).
Thank you for your answer very much!

Could you provide any examples of what is wrong?

I used world.debug.draw_point(carla.Location(px, py, 0.3), size=0.025, color=carla.Color(128,0,255,0), life_time=0) to show a specified color for the point. But the output of this code is as same as world.debug.draw_point(carla.Location(px, py, 0.3), size=0.025, color=carla.Color(255,0,255,0), life_time=0) and even world.debug.draw_point(carla.Location(px, py, 0.3), size=0.025, color=carla.Color(1,0,1,0), life_time=0).
Thank you for your answer very much!


Markdown for Text component

Thanks for this lib, it's a great job.
In my project, i want to display markdow in a input and after as message.
Have you a lib to display markdow in a text and not only in a textinput ?

@SuperBesse Thank you for your kind words as well as submitting this feature request.
Rendering Markdown-formatted text is also an important and very commom use case, that's why we are also working on MarkdownText component, see the draft PR here:

https://github.com/Expensify/react-native-live-markdown/pull/125

Thanks for the answer, i need to update RN and i will test your component.


Hover tooltip not showing on data that's been loaded in via .flow

The data that's been loaded in via a .flow() call doesn't show the tooltip when hovered over until the axis has been updated.

Yeah, it's intended, so let me close at the moment.

Why would this be intended behaviour?
Surely you'd expect all data visible on the chart to behave in the same manner regardless of what method used t load it into the chart?

Because the position of the cursor is not the position where the tooltip is to be shown anymore while flowing. However, you can change this behavior as you want by modifying the code.

I'm running flows with a duration of 0, I think it'd make sense if the tooltip showed on hover after the data had settled?
Otherwise you end up with the chart having an arbitrary cut off point where the tooltip stops working.
It does make sense why the tooltip wouldn't show while the flow is happening though.
(I'm using flow for performance, although I'm not sure if .load would be just as performant?)

I have a flow of duration 1000ms. While flowing, it makes sense not to support tooltip on hover.
However, once the flow is complete, the new points should then be hoverable.


Fix LatexEmbeddedLexer

Closes gh-1516

Conflicts resolved, the changes in #1537 were irrelevant

I did look at this and it all seems fine, but I don't quite understand the original code. Please bear with me -- I just need to convince myself it works (I'm fairly certain it does no harm :) ).

I wouldn't spend too much time understanding the old code - it had both indentation mistakes and a bad design...

Fair enough -- it does have tests now so I doubt it can be any worse than the original one; sorry for taking that long to merge.


[Track2 migration] Placeholder for track 2 migration

This issue is a placeholder for all issues related to track 2 migration.
We can link all issues related to track 2 migration to this issue.
There is also migration guide here for update instructions
The new version of SDK offers a number of new features but also introduces some breaking changes. Detailed info and documentation can be found here

Related issues:

https://github.com/Azure/azure-sdk-for-python/issues/16923
https://github.com/Azure/azure-sdk-for-python/issues/14919
https://github.com/Azure/azure-sdk-for-python/issues/16908


Fixed #322 - Added documentation how to remotely debug Knot.x

Fixed #322- Added documentation how to remotely debug Knot.x

Please update wiki repo after this merge.

@marcinczeczko please merge to wiki


[CT-697] [Bug] Seeds are considerably slower with dbt >= 1.0

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
There appear to be some degraded performance when using dbt seed with dbt >= 1.0 (like 10x slower).
-!         CAVEAT FOR ISSUE READERS           !-

dbt doesn't recommend the seed functionality for large seed files in the first place.
Expected Behavior
dbt seed should perform as it did prior to 1.0.
Steps To Reproduce
Setup

Install docker + clone the dbt-core repo + follow the initial setup in the contributing docs - this is to setup the postgres db locally (skip if you already have a local postgres db setup).
Generate a csv file with 10_000 rows (I used this gist) and copy it to your seeds/data path in your dbt project.
Add the seeds to your dbt_project.yml file, mine was something like this:

name: "postgres"
version: "1.0.0"
config-version: 2
profile: "postgres"
data-paths: ["seeds"]

target-path: "target"
clean-targets:
  - "target"
  - "dbt_modules"
  - "dbt_packages"

models:
  postgres:
    +materialized: table

seeds:
  postgres:
    +enabled: true
    +quote_columns: false

Install dbt + seed your csv

All the following were installed into separate virtual envs.

Note that the seed my_seed_a already exists in the db so dbt always did a truncate in the steps below. The same degraded performance was experienced if the seed hadn't already exist in the db, which means dbt would do create instead of truncate.

dbt 0.18.1
pip install dbt==0.18.1
pip install markupsafe==2.0.1
dbt seed

2022-05-31 05:57:41.850908 (MainThread): 17:57:41 | Concurrency: 8 threads (target='dev')
2022-05-31 05:57:41.851093 (MainThread): 17:57:41 |
2022-05-31 05:57:41.857162 (Thread-1): Began running node seed.postgres.my_seed_a
2022-05-31 05:57:41.858582 (Thread-1): 17:57:41 | 1 of 1 START seed file public.my_seed_a.............................. [RUN]
2022-05-31 05:57:41.859322 (Thread-1): Acquiring new postgres connection "seed.postgres.my_seed_a".
2022-05-31 05:57:41.859650 (Thread-1): finished collecting timing info
2022-05-31 05:57:43.044005 (Thread-1): Using postgres connection "seed.postgres.my_seed_a".
2022-05-31 05:57:43.044181 (Thread-1): On seed.postgres.my_seed_a: BEGIN
2022-05-31 05:57:43.044270 (Thread-1): Opening a new connection, currently in state closed
2022-05-31 05:57:43.056447 (Thread-1): SQL status: BEGIN in 0.01 seconds
2022-05-31 05:57:43.056643 (Thread-1): Using postgres connection "seed.postgres.my_seed_a".
2022-05-31 05:57:43.056732 (Thread-1): On seed.postgres.my_seed_a: /* {"app": "dbt", "dbt_version": "0.18.1", "profile_name": "postgres", "target_name": "dev", "node_id": "seed.postgres.my_seed_a"} */
truncate table "postgres"."public"."my_seed_a"
2022-05-31 05:57:43.062752 (Thread-1): SQL status: TRUNCATE TABLE in 0.01 seconds
2022-05-31 05:57:43.444330 (Thread-1): Using postgres connection "seed.postgres.my_seed_a".
2022-05-31 05:57:43.444525 (Thread-1): On seed.postgres.my_seed_a:
            insert into "postgres"."public"."my_seed_a" (first_name, last_name, job, company, amount, balance, timestamp_at, updated_at, deleted_at, created_at) values
            (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%...
2022-05-31 05:57:43.787235 (Thread-1): SQL status: INSERT 0 10000 in 0.34 seconds
2022-05-31 05:57:43.792411 (Thread-1): Writing runtime SQL for node "seed.postgres.my_seed_a"
2022-05-31 05:57:43.800577 (Thread-1): On seed.postgres.my_seed_a: COMMIT
2022-05-31 05:57:43.800747 (Thread-1): Using postgres connection "seed.postgres.my_seed_a".
2022-05-31 05:57:43.800831 (Thread-1): On seed.postgres.my_seed_a: COMMIT
2022-05-31 05:57:43.810414 (Thread-1): SQL status: COMMIT in 0.01 seconds
2022-05-31 05:57:43.812294 (Thread-1): finished collecting timing info
2022-05-31 05:57:43.812579 (Thread-1): On seed.postgres.my_seed_a: Close
2022-05-31 05:57:43.814104 (Thread-1): Sending event: {'category': 'dbt', 'action': 'run_model', 'label': '56fff452-6d07-4d50-afd8-95b873e36e9d', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x10a89ee20>]}
2022-05-31 05:57:43.814415 (Thread-1): 17:57:43 | 1 of 1 OK loaded seed file public.my_seed_a.......................... [INSERT 10000 in 1.95s]
2022-05-31 05:57:43.814566 (Thread-1): Finished running node seed.postgres.my_seed_a
2022-05-31 05:57:43.816776 (MainThread): Acquiring new postgres connection "master".
2022-05-31 05:57:43.817080 (MainThread): Using postgres connection "master".
2022-05-31 05:57:43.817243 (MainThread): On master: BEGIN
2022-05-31 05:57:43.817379 (MainThread): Opening a new connection, currently in state closed
2022-05-31 05:57:43.835475 (MainThread): SQL status: BEGIN in 0.02 seconds
2022-05-31 05:57:43.835730 (MainThread): On master: COMMIT
2022-05-31 05:57:43.835850 (MainThread): Using postgres connection "master".
2022-05-31 05:57:43.835953 (MainThread): On master: COMMIT
2022-05-31 05:57:43.837042 (MainThread): SQL status: COMMIT in 0.00 seconds
2022-05-31 05:57:43.837297 (MainThread): On master: Close
2022-05-31 05:57:43.837763 (MainThread): 17:57:43 |
2022-05-31 05:57:43.837974 (MainThread): 17:57:43 | Finished running 1 seed in 2.14s.
2022-05-31 05:57:43.838150 (MainThread): Connection 'master' was properly closed.
2022-05-31 05:57:43.838276 (MainThread): Connection 'seed.postgres.my_seed_a' was properly closed.
2022-05-31 05:57:43.847005 (MainThread):
2022-05-31 05:57:43.847287 (MainThread): Completed successfully
2022-05-31 05:57:43.847494 (MainThread):
Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

dbt 1.0.7
pip install dbt-core==1.0.7 dbt-postgres==1.0.7
dbt seed

05:58:27.677062 [info ] [MainThread]: Concurrency: 8 threads (target='dev')
05:58:27.677869 [info ] [MainThread]:
05:58:27.684727 [debug] [Thread-1  ]: Began running node seed.postgres.my_seed_a
05:58:27.685266 [info ] [Thread-1  ]: 1 of 1 START seed file public.my_seed_a......................................... [RUN]
05:58:27.686616 [debug] [Thread-1  ]: Acquiring new postgres connection "seed.postgres.my_seed_a"
05:58:27.687048 [debug] [Thread-1  ]: Began compiling node seed.postgres.my_seed_a
05:58:27.687441 [debug] [Thread-1  ]: finished collecting timing info
05:58:27.687691 [debug] [Thread-1  ]: Began executing node seed.postgres.my_seed_a
05:58:28.955714 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
05:58:28.955965 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: BEGIN
05:58:28.956123 [debug] [Thread-1  ]: Opening a new connection, currently in state closed
05:58:28.967233 [debug] [Thread-1  ]: SQL status: BEGIN in 0.01 seconds
05:58:28.967527 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
05:58:28.967703 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: /* {"app": "dbt", "dbt_version": "1.0.7", "profile_name": "postgres", "target_name": "dev", "node_id": "seed.postgres.my_seed_a"} */
truncate table "postgres"."public"."my_seed_a"
05:58:28.971334 [debug] [Thread-1  ]: SQL status: TRUNCATE TABLE in 0.0 seconds
05:58:54.523752 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
05:58:54.524875 [debug] [Thread-1  ]: On seed.postgres.my_seed_a:
          insert into "postgres"."public"."my_seed_a" (first_name, last_name, job, company, amount, balance, timestamp_at, updated_at, deleted_at, created_at) values
          (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s...
05:58:54.874008 [debug] [Thread-1  ]: SQL status: INSERT 0 10000 in 0.35 seconds
05:58:54.879118 [debug] [Thread-1  ]: Writing runtime SQL for node "seed.postgres.my_seed_a"
05:58:54.886762 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: COMMIT
05:58:54.887028 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
05:58:54.887209 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: COMMIT
05:58:54.891714 [debug] [Thread-1  ]: SQL status: COMMIT in 0.0 seconds
05:58:54.892380 [debug] [Thread-1  ]: finished collecting timing info
05:58:54.892604 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: Close
05:58:54.894010 [debug] [Thread-1  ]: Sending event: {'category': 'dbt', 'action': 'run_model', 'label': 'd718dd74-94d7-4dd4-b596-8682f54f3943', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x109e07ee0>]}
05:58:54.894367 [info ] [Thread-1  ]: 1 of 1 OK loaded seed file public.my_seed_a..................................... [INSERT 10000 in 27.21s]
05:58:54.894741 [debug] [Thread-1  ]: Finished running node seed.postgres.my_seed_a
05:58:54.896836 [debug] [MainThread]: Acquiring new postgres connection "master"
05:58:54.897364 [debug] [MainThread]: Using postgres connection "master"
05:58:54.897733 [debug] [MainThread]: On master: BEGIN
05:58:54.898062 [debug] [MainThread]: Opening a new connection, currently in state closed
05:58:54.931927 [debug] [MainThread]: SQL status: BEGIN in 0.03 seconds
05:58:54.932395 [debug] [MainThread]: On master: COMMIT
05:58:54.932709 [debug] [MainThread]: Using postgres connection "master"
05:58:54.933003 [debug] [MainThread]: On master: COMMIT
05:58:54.934533 [debug] [MainThread]: SQL status: COMMIT in 0.0 seconds
05:58:54.934977 [debug] [MainThread]: On master: Close
05:58:54.935634 [info ] [MainThread]:
05:58:54.936256 [info ] [MainThread]: Finished running 1 seed in 27.42s.
05:58:54.936907 [debug] [MainThread]: Connection 'master' was properly closed.
05:58:54.937327 [debug] [MainThread]: Connection 'seed.postgres.my_seed_a' was properly closed.
05:58:54.943688 [info ] [MainThread]:
05:58:54.944539 [info ] [MainThread]: Completed successfully

dbt 1.1.0
pip install dbt-core==1.1.0 dbt-postgres==1.1.0
dbt seed

08:08:51.605497 [info ] [MainThread]: Concurrency: 8 threads (target='dev')
08:08:51.605966 [info ] [MainThread]:
08:08:51.611963 [debug] [Thread-1  ]: Began running node seed.postgres.my_seed_a
08:08:51.612711 [info ] [Thread-1  ]: 1 of 1 START seed file public.my_seed_a ........................................ [RUN]
08:08:51.614090 [debug] [Thread-1  ]: Acquiring new postgres connection "seed.postgres.my_seed_a"
08:08:51.615405 [debug] [Thread-1  ]: Began compiling node seed.postgres.my_seed_a
08:08:51.616236 [debug] [Thread-1  ]: finished collecting timing info
08:08:51.616654 [debug] [Thread-1  ]: Began executing node seed.postgres.my_seed_a
08:08:52.871344 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
08:08:52.871767 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: BEGIN
08:08:52.872066 [debug] [Thread-1  ]: Opening a new connection, currently in state closed
08:08:52.887434 [debug] [Thread-1  ]: SQL status: BEGIN in 0.02 seconds
08:08:52.887853 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
08:08:52.888124 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: /* {"app": "dbt", "dbt_version": "1.1.0", "profile_name": "postgres", "target_name": "dev", "node_id": "seed.postgres.my_seed_a"} */
truncate table "postgres"."public"."my_seed_a"
08:08:52.893625 [debug] [Thread-1  ]: SQL status: TRUNCATE TABLE in 0.01 seconds
08:09:18.845472 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
08:09:18.845913 [debug] [Thread-1  ]: On seed.postgres.my_seed_a:
          insert into "postgres"."public"."my_seed_a" (first_name, last_name, job, company, amount, balance, timestamp_at, updated_at, deleted_at, created_at) values
          (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s,%s,%s,%s,%s,%s),(%s,%s,%s,%s,%s...
08:09:19.226980 [debug] [Thread-1  ]: SQL status: INSERT 0 10000 in 0.38 seconds
08:09:19.232895 [debug] [Thread-1  ]: Writing runtime SQL for node "seed.postgres.my_seed_a"
08:09:19.242962 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: COMMIT
08:09:19.243377 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
08:09:19.243676 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: COMMIT
08:09:19.256668 [debug] [Thread-1  ]: SQL status: COMMIT in 0.01 seconds
08:09:19.258547 [debug] [Thread-1  ]: finished collecting timing info
08:09:19.259305 [debug] [Thread-1  ]: On seed.postgres.my_seed_a: Close
08:09:19.260948 [debug] [Thread-1  ]: Sending event: {'category': 'dbt', 'action': 'run_model', 'label': 'efdc63ee-7ed7-4aef-899c-b7004b5a3917', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x10705b1c0>]}
08:09:19.261629 [info ] [Thread-1  ]: 1 of 1 OK loaded seed file public.my_seed_a .................................... [INSERT 10000 in 27.65s]
08:09:19.262245 [debug] [Thread-1  ]: Finished running node seed.postgres.my_seed_a
08:09:19.265492 [debug] [MainThread]: Acquiring new postgres connection "master"
08:09:19.266367 [debug] [MainThread]: Using postgres connection "master"
08:09:19.266922 [debug] [MainThread]: On master: BEGIN
08:09:19.267332 [debug] [MainThread]: Opening a new connection, currently in state closed
08:09:19.298020 [debug] [MainThread]: SQL status: BEGIN in 0.03 seconds
08:09:19.298505 [debug] [MainThread]: On master: COMMIT
08:09:19.298843 [debug] [MainThread]: Using postgres connection "master"
08:09:19.299175 [debug] [MainThread]: On master: COMMIT
08:09:19.301994 [debug] [MainThread]: SQL status: COMMIT in 0.0 seconds
08:09:19.302421 [debug] [MainThread]: On master: Close
08:09:19.302960 [info ] [MainThread]:
08:09:19.303368 [info ] [MainThread]: Finished running 1 seed in 27.86s.
08:09:19.303783 [debug] [MainThread]: Connection 'master' was properly closed.
08:09:19.304134 [debug] [MainThread]: Connection 'seed.postgres.my_seed_a' was properly closed.
08:09:19.309596 [info ] [MainThread]:
08:09:19.309948 [info ] [MainThread]: Completed successfully
08:09:19.310287 [info ] [MainThread]:
08:09:19.310588 [info ] [MainThread]: Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

Notice we went from about 2 seconds to 20 seconds.
Relevant log output
See above.

Environment
- OS: macOS
- Python: 3.8.7
- dbt: 0.18.1, 1.0.7, 1.1.0

What database are you using dbt with?
postgres
Additional Context
Looks like this is due to the long wait time between the truncate and the insert:
# dbt 0.18.1
2022-05-31 05:57:43.062752 (Thread-1): SQL status: TRUNCATE TABLE in 0.01 seconds
2022-05-31 05:57:43.444330 (Thread-1): Using postgres connection "seed.postgres.my_seed_a".
2022-05-31 05:57:43.444525 (Thread-1): On seed.postgres.my_seed_a:
            insert into "postgres"."public"."my_seed_a" (first_name, last_name, job, company, amount, balance, timestamp_at, updated_at, deleted_at, created_at) values

# dbt 1.1
08:08:52.893625 [debug] [Thread-1  ]: SQL status: TRUNCATE TABLE in 0.01 seconds
08:09:18.845472 [debug] [Thread-1  ]: Using postgres connection "seed.postgres.my_seed_a"
08:09:18.845913 [debug] [Thread-1  ]: On seed.postgres.my_seed_a:
          insert into "postgres"."public"."my_seed_a" (first_name, last_name, job, company, amount, balance, timestamp_at, updated_at, deleted_at, created_at) values

For the record, this becomes really bad for a 100k line seed file (27 seconds > 270 seconds) because the inserts are 10k rows at a time and dbt >= 1.0 has a lot of seemingly idle time between each command (insert into ... ).

Profile from 0.18 v 1.0:

Looks like its the thread lock?
timing_0.18.txt
timing_1.0.txt
timing_1.1.txt

@jeremyyeo  Thanks for the detailed repro steps!! And all of the logs!
I did some digging by placing a bunch of {{log('$somenumber')}} all around the place and found the bottleneck(I think).
This PR made some change to load_csv_rows macro, maybe that worsened it or just the last changed to that file. Either way, the two loops here are not very efficient, len(chunk) is probably the # of lines for the seed file so as the file size grow this will become slower.
Let me know what you think!

Is this issue resolved I m facing something similar with seeds

Thanks for reaching out @supersum9 !
 And which database adapter are you using? Would also be interested in the version numbers reported by:
dbt --version

I will repeat @jeremyyeo's caveat that:

dbt doesn't recommend the seed functionality for large seed files in the first place.

So we probably don't have a large appetite to prioritize performance optimization for really large seed files. But still very interested to hear about your experience!

I'm loading 320KB (5826 lines, 10 columns). Providing a properties.yml as described here the total time for this seed has dropped from roughly 300 seconds to about 30 seconds.

Thanks for sharing your results @frankivo !
Some follow up questions:
Which database adapter are you using? And which version? You can find both via:
dbt --version

Can you share the contents of your properties.yml that made a difference?
What were the data types of the 10 columns that the seed produced when it took 300 seconds? And what were the data types when it took 30 seconds?

Thanks for this info @frankivo !
Based on the differences in the data types, I'm guessing the difference in execution time is due to 4-byte int's and strings being able to insert into Databricks faster than 8-byte bigints. If so, then being explicit about desired data types in properties.yml / _seeds.yml file could yield faster load times.
We are unlikely to change our automatic type inference anytime soon, so this is good info to know for folks with "large" seed files in dbt-databricks or dbt-spark!

If you reduced your 5826 line seed file to just the Year column and then took the timings of dbt seed both with and without your properties.yml file, that should isolate a portion of the performance differences of inserting 4-byte int versus 8-byte bigint in Databricks.

60 seconds versus 7 seconds. The latter using the config specified above.


I want to know the specifications of your machine.

Hello,
I'm very grateful for your research.
And I want to use your tool, ADFuzz.
So, I want to know the specifications of your machine.
May I know which CPU and GPU you used to execute the experiment?
If you use different machines in SVL and CARLA, I wonder the specifications of each.
Thank you.

I use i9-7940x for CPU and 2080Ti for GPU. They work for both SVL and CARLA.

Thank you for your reply!
Have a good day :)


[ADAM-1308] Fix stack overflow in join with custom iterator impl.

Resolves #1308. CC @akmorrow13 @devin-petersohn

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1679/
Test PASSed.

I was going to try running this on the problem before it's merged unless anyone deems that unnecessary.

I was going to try running this on the problem before it's merged unless anyone deems that unnecessary.

I would really like that so we can confirm that this is a fix before we merge.

I computed on the same code as before, and did not run into stack overflow errors. I think we can go forward with the merge.

I reran my pipeline and it looks good. Thanks @fnothaft !

Thank you for confirming, @devin-petersohn @akmorrow13

Thank you, @fnothaft


Incorrect Schedule

For today, Friday the 23 of march the schedule is wrong. We were confused, it says E period is 1 hour and 25 min. and the lunch and F period and messed up. Please fix it.

Unable to reproduce.


Develop a backend without depend on others

Yesterday I tried to test Memcached backend (after that PR was merged into crystal-memcached project) and I noticed I could not run the tests because I don't have leveldb installed.
Could we split the specs in order to not depend on too many backends installed on the machine? Just an idea.

Yea, I guess we can do it. I'll try my idea when I'll be at home)
Thanks!

Thanks for the feedback! Done in 9ade38a
Now you can run it like:
crystal spec ./spec/kiwi/memcached_store_spec.cr

Thanks! I was going to make it possible but you already did it! :D


Add support for VMware Workstation to Fusion driver

Signed-off-by: Christopher A. Baumbauer<EMAIL_ADDRESS>

This is to resolve issue #3868.

I think it would be better to have a vmwareworkstation driver instead of using the vmwarefusion driver for VMware Workstation. For Windows VMware Workstation there is an external driver plugin at https://github.com/pecigonzalo/docker-machine-vmwareworkstation/, maybe you should start something similar for Linux. An external plugin has the advantage that you don't have to wait until the driver plugin got merged into core codebase.

Perhaps, but this would result in a lot of duplicate code between the Fusion
and Linux workstation driver which is why I moved the files back away from the
arch specific naming convention.
The modification itself is mainly adding arch switches to tell the driver to
look in /etc instead of /Library for the vmware specific network configs, and
/usr/bin instead of /Applications/VMWare\ Fusion.app for vmrun.
Windows Workstation is a completely different beast, and is one I'm not too
familiar with overal.
On Mon, Nov 21, 2016 at 12:36:39PM -0800, Stefan Scherer wrote:

I think it would be better to have a vmwareworkstation driver instead of using the vmwarefusion driver for VMware Workstation. For Windows VMware Workstation there is an external driver plugin at https://github.com/pecigonzalo/docker-machine-vmwareworkstation/, maybe you should start something similar for Linux. An external plugin has the advantage that you don't have to wait until the driver plugin got merged into core codebase.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/docker/machine/pull/3885#issuecomment-262059614

@cab105

Perhaps, but this would result in a lot of duplicate code between the Fusion
and Linux workstation driver which is why I moved the files back away from the
arch specific naming convention.

Did you consider writing a driver plugin that embeds the existing workstation driver? e.g. (totally spitballing this code),
package vmwareworkstation

import "github.com/docker/machine/drivers/vmwarefusion"

type Driver struct {
    vmwareFusion.Driver
}

You could re-use a lot of the methods, and just "over-ride" the methods you want to change.

At any rate, we're unable to accept new plugins in the core right now.  Thanks for the contribution @cab105 , my suggestion would be to make and distribute a docker-machine-driver plugin


Enable docker build workflow

Summary
Build docker images on any PR or push to main.
New behavior
Adds CI workflow.
Code changes
See .github/workflows/docker.yml.
Testing guidance
Examine the Github Actions for this PR.

This one is ready for review and merge


Jamf recon on success

It can be useful for jamf users to update inventory after software is successfully installed. This adds an argument JAMF_RECON_ON_SUCCESS that when set to yes will run a jamf recon. It defaults to no.
2022-05-26 15:24:33 : WARN  : zoom : setting variable from argument DEBUG=1
2022-05-26 15:24:34 : WARN  : zoom : setting variable from argument JAMF_RECON_ON_SUCCESS=yes
2022-05-26 15:24:34 : REQ   : zoom : ################## Start Installomator v. 10.0beta, date 2022-05-26
2022-05-26 15:24:34 : INFO  : zoom : ################## Version: 10.0beta
2022-05-26 15:24:34 : INFO  : zoom : ################## Date: 2022-05-26
2022-05-26 15:24:34 : INFO  : zoom : ################## zoom
2022-05-26 15:24:34 : DEBUG : zoom : DEBUG mode 1 enabled.
2022-05-26 15:24:34 : INFO  : zoom : BLOCKING_PROCESS_ACTION=tell_user
2022-05-26 15:24:34 : INFO  : zoom : NOTIFY=success
2022-05-26 15:24:34 : INFO  : zoom : LOGGING=DEBUG
2022-05-26 15:24:34 : INFO  : zoom : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-05-26 15:24:34 : INFO  : zoom : Label type: pkg
2022-05-26 15:24:34 : INFO  : zoom : archiveName: zoom.us.pkg
2022-05-26 15:24:34 : INFO  : zoom : no blocking processes defined, using zoom.us as default
2022-05-26 15:24:34 : DEBUG : zoom : Changing directory to /Users/dnikles/Documents/GitHub/Installomator/build
2022-05-26 15:24:34 : INFO  : zoom : App(s) found: /Applications/zoom.us.app
2022-05-26 15:24:34 : INFO  : zoom : found app at /Applications/zoom.us.app, version <IP_ADDRESS>26, on versionKey CFBundleVersion
2022-05-26 15:24:34 : INFO  : zoom : appversion: <IP_ADDRESS>26
2022-05-26 15:24:34 : INFO  : zoom : Latest version of zoom.us is <IP_ADDRESS>26
2022-05-26 15:24:34 : WARN  : zoom : DEBUG mode 1 enabled, not exiting, but there is no new version of app.
2022-05-26 15:24:34 : REQ   : zoom : Downloading https://zoom.us/client/latest/ZoomInstallerIT.pkg to zoom.us.pkg
2022-05-26 15:24:36 : DEBUG : zoom : File list: -rw-r--r--  1 root  staff   112M May 26 15:24 zoom.us.pkg
2022-05-26 15:24:36 : DEBUG : zoom : File type: zoom.us.pkg: xar archive compressed TOC: 4814, SHA-1 checksum
2022-05-26 15:24:36 : DEBUG : zoom : curl output was:
*   Trying <IP_ADDRESS>:443...
* Connected to zoom.us (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
} [312 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [102 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3913 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=San Jose; O=Zoom Video Communications, Inc.; CN=*.zoom.us
*  start date: Apr 29 00:00:00 2022 GMT
*  expire date: May  2 23:59:59 2023 GMT
*  subjectAltName: host "zoom.us" matched cert's "zoom.us"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x13b811400)
> GET /client/latest/ZoomInstallerIT.pkg HTTP/2
> Host: zoom.us
> user-agent: curl/7.79.1
> accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 302
< date: Thu, 26 May 2022 19:24:35 GMT
< content-length: 0
< location: https://cdn.zoom.us/prod/<IP_ADDRESS>26/ZoomInstallerIT.pkg
< x-zm-trackingid: v=2.0;clid=aw1;rid=WEB_08ff13e7765a8a247fba7c2e70228414
< x-content-type-options: nosniff
< content-security-policy: upgrade-insecure-requests; default-src https://*.zoom.us https://zoom.us blob: 'self'; img-src https: about: blob: data: 'self'; style-src https: safari-extension: chrome-extension: 'unsafe-inline' data: 'self'; font-src https: safari-extension: chrome-extension: blob: data: 'self'; connect-src * about: blob: data: 'self'; media-src * rtmp: blob: data: 'self'; frame-src https: ms-appx-web: zoommtg: zoomus: wvjbscheme: data: 'self'; object-src 'none'; base-uri 'none';
< x-frame-options: SAMEORIGIN
< set-cookie: zm_aid=""; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly
< set-cookie: zm_haid=""; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly
< set-cookie: zm_tmaid=""; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly
< set-cookie: zm_htmaid=""; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly
< p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM"
< set-cookie: _zm_ssid=aw1_c_qu-wXzqHRHSAIBVz5WA7-w; Domain=.zoom.us; Path=/; Secure; HttpOnly
< set-cookie: cred=154AC5D777FC3071FB632C4E44811C74; Path=/; Secure; HttpOnly
< set-cookie: _zm_ctaid=eR84vuzVQ_eRg85bMPuUBg.1653593075446.b98a83d8aa9584456436d77f104b5cc5; Domain=.zoom.us; Expires=Thu, 26-May-2022 21:24:35 GMT; Path=/; Secure; HttpOnly
< set-cookie: _zm_chtaid=917; Domain=.zoom.us; Expires=Thu, 26-May-2022 21:24:35 GMT; Path=/; Secure; HttpOnly
< x-zm-zoneid: VA
< set-cookie: _zm_mtk_guid=c4e3c7c159a145f084a66d0740c7189c; Domain=.zoom.us; Expires=Sat, 25-May-2024 19:24:35 GMT; Path=/; Secure
< strict-transport-security: max-age=31536000; includeSubDomains
< x-xss-protection: 1; mode=block
< referrer-policy: strict-origin-when-cross-origin
<
{ [0 bytes data]
* Connection #0 to host zoom.us left intact
* Issue another request to this URL: 'https://cdn.zoom.us/prod/<IP_ADDRESS>26/ZoomInstallerIT.pkg'
*   Trying <IP_ADDRESS>:443...
* Connected to cdn.zoom.us (<IP_ADDRESS>) port 443 (#1)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
} [316 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [10 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [3920 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=California; L=San Jose; O=Zoom Video Communications, Inc.; CN=*.zoom.us
*  start date: Apr 29 00:00:00 2022 GMT
*  expire date: May  2 23:59:59 2023 GMT
*  subjectAltName: host "cdn.zoom.us" matched cert's "*.zoom.us"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.
> GET /prod/<IP_ADDRESS>26/ZoomInstallerIT.pkg HTTP/1.1
> Host: cdn.zoom.us
> User-Agent: curl/7.79.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/vnd.apple.installer+xml
< Content-Length: 117388549
< Connection: keep-alive
< Date: Thu, 26 May 2022 05:46:41 GMT
< Last-Modified: Mon, 23 May 2022 14:31:42 GMT
< Etag: "6d27a490a1ffce97f45e3fa07a532743-14"
< X-Amz-Server-Side-Encryption: AES256
< Accept-Ranges: bytes
< Server: AmazonS3
< Via: 1.1 3a9f76e15ac64134cc339fc4f9fb6a4c.cloudfront.net (CloudFront)
< Age: 49075
< Cross-Origin-Resource-Policy: cross-origin
< X-Cache: Hit from cloudfront
< X-Amz-Cf-Pop: PHL50-C1
< X-Amz-Cf-Id: ToHNfqiW8z5pidaXMNX8DEPhrmuGzQD3bBDq7ykjRq8IDFMaidwz0g==
<
{ [15805 bytes data]
* Connection #1 to host cdn.zoom.us left intact

2022-05-26 15:24:36 : DEBUG : zoom : DEBUG mode 1, not checking for blocking processes
2022-05-26 15:24:36 : REQ   : zoom : Installing zoom.us
2022-05-26 15:24:36 : INFO  : zoom : Verifying: zoom.us.pkg
2022-05-26 15:24:36 : DEBUG : zoom : File list: -rw-r--r--  1 root  staff   112M May 26 15:24 zoom.us.pkg
2022-05-26 15:24:37 : DEBUG : zoom : File type: zoom.us.pkg: xar archive compressed TOC: 4814, SHA-1 checksum
2022-05-26 15:24:37 : DEBUG : zoom : spctlOut is zoom.us.pkg: accepted
2022-05-26 15:24:37 : DEBUG : zoom : source=Notarized Developer ID
2022-05-26 15:24:37 : DEBUG : zoom : override=security disabled
2022-05-26 15:24:37 : DEBUG : zoom : origin=Developer ID Installer: Zoom Video Communications, Inc. (BJ4HAAB9B3)
2022-05-26 15:24:37 : INFO  : zoom : Team ID: BJ4HAAB9B3 (expected: BJ4HAAB9B3 )
2022-05-26 15:24:37 : DEBUG : zoom : DEBUG enabled, skipping installation
2022-05-26 15:24:37 : INFO  : zoom : Finishing...
2022-05-26 15:24:48 : INFO  : zoom : App(s) found: /Applications/zoom.us.app
2022-05-26 15:24:48 : INFO  : zoom : found app at /Applications/zoom.us.app, version <IP_ADDRESS>26, on versionKey CFBundleVersion
2022-05-26 15:24:48 : REQ   : zoom : Installed zoom.us, version <IP_ADDRESS>26
2022-05-26 15:24:48 : INFO  : zoom : notifying
2022-05-26 15:24:48 : INFO  : zoom : running jamf recon
Retrieving inventory preferences from https://JAMFURL:8443/...
Finding extension attributes...
Locating accounts...
Locating applications...
Locating hard drive information...
Searching path: /System/Applications
Locating package receipts...
Locating printers...
Searching path: /Applications
Locating hardware information (macOS 12.4.0)...
Submitting data to https://JAMFURL:8443/...
<computer_id>123456</computer_id>
2022-05-26 15:25:01 : DEBUG : zoom : DEBUG mode 1, not reopening anything
2022-05-26 15:25:01 : REQ   : zoom : All done!
2022-05-26 15:25:01 : REQ   : zoom : ################## End Installomator, exit code 0

If running Installomator via a Jamf policy you can configure it to run inventory (recon) after running Installomator. I'm not sure the usefulness of having this happen within Installomator.

This would run recon after every update from Installomator, potentially creating many redundant recons. I agree this should not part of Installomator, but setup in the policy in Jamf.

It would run after a successful update, which is not what running recon after running installomator in a jamf policy would do. How would a recon be redundant if it is running after software is successfully installed? The point of this is to avoid unnecessary recons.

Sorted out a more efficient way of doing this in jamf thanks to @scriptingosx

If I have multiple update policies, I put them all on a custom trigger. Then I have one policy that runs that custom trigger once per day with update inventory enabled. Then you can disable the normal “update inventory once per day” policy. And you won't get more than one recon per day, no matter how many updates run (or don't)


Auditing Support with Tests

@derjust
Here is the pull request for the annotation support

Hi! This is a large PR.. I'm still digesting it - but on it :)

No worries! :) Do let me know if you have questions or if you would like me to move the files to another packages to make the file structure tidier.

Hello all,
Any updates on this PR? Did you have a change to review it? :)
I am asking this, because I wanted to use this project and this would be helpful.
Also I am available to migrate some of the existing code to Java 8!


Feat(eos_cli_config_gen): add ACL "counters per-entry" support (#1232)

Change Summary
The counters per-entry (ACL configuration modes) command places the ACL in counting mode.
Related Issue(s)
Fixes #1242
Fixes #1232
Component(s) name
arista.avd.eos_cli_config_gen
Proposed changes

Add enable_counters: < true | false > per ACL type
IP Extended Access-Lists
access_lists:
  < access_list_name_1 >:
    enable_counters: < true | false >
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"
      < sequence_id_2 >:
        action: "< action as string >"
  < access_list_name_2 >:
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"

IPv6 Standard Access-Lists
ipv6_standard_access_lists:
  < ipv6_access_list_name_1 >:
    enable_counters: < true | false >
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"
      < sequence_id_2 >:
        action: "< action as string >"
  < ipv6_access_list_name_2 >:
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"

IP Standard Access-Lists
standard_access_lists:
  < access_list_name_1 >:
    enable_counters: < true | false >
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"
      < sequence_id_2 >:
        action: "< action as string >"
  < access_list_name_2 >:
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"

IPv6 Extended Access-Lists
ipv6_access_lists:
  < ipv6_access_list_name_1 >:
    enable_counters: < true | false >
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"
      < sequence_id_2 >:
        action: "< action as string >"
  < ipv6_access_list_name_2 >:
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"

How to test

Molecule Testcases
Checklist
User Checklist

N/A

Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

Need to change the PR title. It should start with one of the following.
Available types:

Feat
Fix
Cut
Doc
CI
Start
Stop
Bump
Test
Make
Refactor
Reformat
Optimize
License
Revert

If you are adding any new features to eos_designs then use Feat(eos_designs): .

Can you add logic for enable counters to templates/documentation/access-list.j2 and ipv6-standard-access-lists.j2. Enable counters logic added for every access-list on it's top of table. Or come up with your own suggestion.

Missing new line at the End of File, ipv6-access-list.yml

done

Can you add logic for enable counters to templates/documentation/access-list.j2 and ipv6-standard-access-lists.j2. Enable counters logic added for every access-list on it's top of table. Or come up with your own suggestion.

done

See #1251 - will remove the commit from this PR

Updated key name to counters_per_entry instead of enable_counters to match EOS CLI more closely. Also updated CI input variables so we produce valid EOS config for each ACL type.