jw-demo-873 to 0.0.2

Promote jw-demo-873 to version 0.0.2

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


How to configure secrets.json file present in CSETWebCore.Reports/Resources/

[
{
"key": "IronPdf",
"value": ""
},
{
"key": "CSET_DB",
"value": ""
}
]
Can you please provide us any example to setup above.

We have removed the separate reports api, so this is no longer applicable


Moving forward

Hi all,
I want to start out by saying thanks for this project. I'm wondering what the plan is moving forward. Do you think this should be merged back into noble or do you think it should be standalone? If standalone do you think we can have an official release on npm? As someone who needs to support newer macOS platforms I now rely on this library now instead of noble.
Thanks again!
Jordan

There are no one maintained noble now. so...

@floating noble-mac is now included in abandonware noble fork
Checkout @abandonware/noble


upgrade upload-artifact to version 4

Description
upgrade upload-artifact to version 4, as v1 and v2 are deprecated.
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] API changes companion pull request created.
[x] Commits are signed per the DCO using --signoff.
[ ] Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks good to me. Will approve when the CI passed.

Can u check the CI error?

failed ones are caused BWC, we can ignore.

close it due to #961


Merging in update_spend_tx.

As mentioned in #312, update_spend_tx has been modified.

Hey, I noticed that I am still passing spend_tx to db_update_spend, but it must be unwrapped_tx. I was unable to find a db_update_spend version that takes DbSpendTransaction. Should I make one?

You could use the psbt member of old_tx if that's a DbSpendTransaction:
https://github.com/revault/revaultd/blob/b310208a8b3b420f9b0cddcc03588e264a99538b/src/database/schema.rs#L180-L188

To test if the merge is happening I have planned the following steps:

Create the same transaction spend_tx as created in test_spendtx_management
Push it to the database the first time using man.rpc.updatespendtx(spend_tx)
Obtain the corresponding psbt by deserializing spend_tx
Remove a signature from the only input of spend_tx, i.e. psbt.tx.vin[0]
Serialize it and call updatespendtx on new_spend_tx
Fetch it from the backend and assert if the transaction still has all the signatures

I'm kind of stuck on step 4 since I'm not sure how I can access the signatures from a CTxIn object, is there a simple way to do so?

The signature isn't part of a CTxIn, it's in the PartiallySignedInput: https://github.com/revault/revaultd/blob/c928b14e79d9f2b7ff2cdea22ba2df9049890d02/tests/test_framework/serializations.py#L602.
But i think you can do something simpler. How about having 3 managers and:

Getting a Spend with getspendtx. Copying it in psbt_a and psbt_b.
Signing psbt_a with the first manager and calling updatespendtx with the signed transaction.
Signing psbt_b with the two other managers and calling updatespendtx with the signed transaction.
Querying the Spend using listspendtx and asserting that the transaction has 3 signatures (or is fully signed if you set a threshold of 3 for the managers).

Also, note you'll need to rebase on master as the latest merges surely will create some hidden conflicts.
------- Original Message -------
Le mardi 17 mai 2022 à 5:48 PM, Zeeshan Ahmed @.***> a écrit :

To test if the merge is happening I have planned the following steps:

Create the same transaction spend_tx as created in test_spendtx_management
Push it to the database the first time using man.rpc.updatespendtx(spend_tx)
Obtain the corresponding psbt by deserializing spend_tx
Remove a signature from the only input of spend_tx, i.e. psbt.tx.vin[0]
Serialize it and call updatespendtx on new_spend_tx
Fetch it from the backend and assert if the transaction still has all the signatures

I'm kind of stuck on step 4 since I'm not sure how I can access the signatures from a CTxIn object, is there a simple way to do so?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


change package name

android studio 3.6.3
android : 7,8,9,10,5
when i released the apk and test it with change  package name .. the app crash and out
when i released with same your package name the app work normal ~~!!
version of weather 2.1.0
please see the problem when you change package name and release the apk and test it write some country

I think you did not correctly change the package name and application id of the app.
https://stackoverflow.com/questions/16804093/rename-package-in-android-studio


Fix #16: nixosProfiles -> nixosHosts

nixosProfiles might conflict a little too much with downstream naming.

Merging this as an implementation of authorized https://github.com/gytis-ivaskevicius/flake-utils-plus/issues/16#issuecomment-814999215

I would have preferred discussing hosts vs nixosHosts first. That would help for #17 and doing a rename in one swoop would be better.

I think everything should be hosts. Its getting very confusing to juggle around two names that are extremely similar. I say just rename to hosts and use host/hosts everywhere in fup. Leave the name profiles reserved for the more standard nixpkgs definition, a system agnostic config set.

profile → config? — they are mostly the contents of a traditional /etc/nixos/configuration.nix?

fup definition of profiles is basically a "computer configuration". Word host` seems to work fine in this context


Introducing ColorStyle to avoid dealing LCDColor

I'm proposing the enum ColorStyle to use LCDSolidColor or LCDPattern in the Graphics methods. For example:
let bitmap = Graphics.newBitmap(width: 100, height: 100, colorStyle: .solid(.colorBlack))
let newSprite = Sprite(bitmap: bitmap)

Also, using patterns:
let squares: LCDPattern = (
    0xF0, 0xF0, 0xF0, 0xF0, 0x0F, 0x0F, 0x0F, 0x0F,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF
)
let bitmap = Graphics.newBitmap(width: 100, height: 100, colorStyle: .pattern(squares))
let newSprite = Sprite(bitmap: bitmap)

It also works on Graphics methods, like:
mySprite.withImage {
    Graphics.fillRect(x: x - 25, y: y - 25, width: 50, height: 50, colorStyle: .solid(.colorClear))
    Graphics.fillEllipse(
         x: x - 25, y: y - 25,
         width: 50, height: 50,
         startAngle: startAngle, endAngle: endAngle,
         colorStyle: .solid(.colorBlack))
}

First, thank you for trying out these examples and getting involved. These changes are definitely something I'd like to see in a full featured Playdate Swift overlay..
That said this repo isn't intended to be a full overlay, its purpose is to show what's possible. I think some other Playdate developers have forked this repo and are expanding on the overlay. I suggest retargeting this PR to one of those forks.

Oh, cool! I was just soo excited about this repo! Sorry about it, and thank you so much! I will keeping an eye on it!

No need to be sorry, I very much appreciate your interest and enjoyed trying out our example locally too! :D

@heltena Here is an active fork the community is working on, please submit a PR there:  https://github.com/jackson-57/playdate-swift-overlay.

Thanks for the repo. I'm having a look on it :-)


Update Gherkin README

Some content is out of date:

The AST diagram needs to reflect the new Rule keyword and general Protobuf structure. Maybe generate it? (Wouldn't be as nice).
The docs need to be updated to reflect the fact that it's using protobuf, and that --json will produce NDJSON.

@jenisys The Gherkin README should probably also be updated. That might be a better place to describe the grammar rules more explicitly if you want to give that a go?

Thanks for the info.
I will have a look at it tomorrow.
Sent from my iPhone

On 26. Dec 2018, at 11:13, Marit van Dijk<EMAIL_ADDRESS>wrote:
@jenisys The Gherkin README should probably also be updated. That might be a better place to describe the grammar rules more explicitly if you want to give that a go?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Research Personal Traits

Research and create a list of Positive Personal Traits
Personal Traits will link to one or more Values
A list of traits are needed to mind map the traits and values together

Personal traits positive
*

  Being honest and taking responsibility for your actions are admirable qualities.

  Adaptability and affability are great traits that can help a person get along well with others.

  Drive, determination and persistence can help keep a person going no matter what.

  Compassion, understanding and empathy help a person relate well to others.

  In addition to being a virtue, patience is a personality trait that's universally valued.

  Courage and confidence can help a person choose to do what is right in tough situations.

  Loyalty is a good quality to possess; it will help others decide that you are trustworthy.

  Being adventurous and fearless can empower you to be willing to take chances.

  Having an imaginative and creative nature can help you come up with innovative ideas and unique solutions.

  Being helpful to others is a personality trait that will cause others to see you as indispensable.

  Being meticulous and precise means that you're careful and conscientious.

  A person who is optimistic tends to look for the bright side of situations rather than forcing on the negative.

  Someone who is reliable and dependable is an individual that others know they can count on.

  People who are gregarious, charming or sociable tend to be friendly, outgoing and upbeat.

  Those who are independent develop a reputation for taking initiative and seeing things through on their own.

  People who are fair and impartial are viewed by others as being able to make objective decisions not influenced by bias.

  Those who take an encouraging approach are viewed as being caring and interested in seeing others succeed.

  If people view you as capable and competent, they tend to trust that you know what you are doing.

  Those who are exuberant come across as being filled with joy and enthusiasm.

  People who are discreet are viewed as trustworthy individuals who are respectful of the privacy and dignity of others.

Personality traits negative

  A propensity for lying in order to avoid responsibility for one's actions is a deplorable quality.

  A tendency to be untruthful or dishonest in your dealings with others is also a negative trait.

  Being rigid and consistently unyielding to the needs of others are not endearing qualities.

  An inability to empathize with others is a negative personality trait that can alienate others.

  Being quick to anger will damage relationships and turn people away.

  Being disloyal, such as talking about others behind their backs or betraying them for personal gain, is among the most negative personality traits.

  People who are bossy tend to come across as self-centered individuals who disregard the concerns of others.

  Those who are conceited, pompous or arrogant tend to think that they have all the answers or universally know better than everyone else.

  Those who are unfriendly are often viewed as disrespectful and/or uninterested in connecting with other people.

  People who are sullen or surly by nature can be very rude and unpleasant to deal with in a personal or professional capacity.

  Those who are cowardly exhibit an unwillingness to face adversity head-on or to stand up for what is right.

  People who tend to be slovenly habitually fail to take care of their appearance or surroundings, and so are viewed negatively by others.

  People who are quarrelsome or argumentative by nature are more concerned with winning arguments and being right than with finding a solution.

  Those who are too finicky or picky come across as extreme perfectionists who cannot be pleased no matter what one does.

  People who tend to be impulsive often act without thinking about the consequences to themselves or others, thus coming across as reckless.

  Those who are habitually stingy or greedy are viewed by others as selfish individuals who disregard the needs of others.

  People who are sneaky tend to be deliberately deceptive, factors that most definitely represent negative personality traits.

  Those who engage in malicious acts deliberately do things that they know will negatively impact other people.

  Those who are thoughtless act with a total disregard for how their actions might impact other people.

  Those who behave in an unruly manner are often disruptive and disrespectful and can cause harm to others by their irresponsible actions.

Personality Traits
source of list of traits above
https://examples.yourdictionary.com/examples-of-personality-traits.html

Similar to research value issue, having limited scope to focus on goals and habits I will close this issue for now.


Add Zipper.search_pattern/2

Expanding on #147 which introduced Zipper.move_to_cursor/2, this PR adds a more general Zipper.search_pattern/2, which can match an arbitrarily nested pattern.
Also included is a small fix that makes do_find private (it was accidentally exposed) and a refactor for move_to_cursor.
cc @zachdaniel, @NickNeck

I am not sure if I understand everything right, maybe I overlook something. But a pattern with __cursor__() returns the same result for move_to_cursor/2 and search_to_pattern/2 for the same zipper. So the generalisation of search_to_pattern/2 is that it doesn't needs a __cursor__(). If I am right with that assumption, I would suggest to rename search_to_pattern/2 in move_to_pattern/2 and ignore __cursor__() in this function. Then we have both functionalities with a clear name.

So the generalisation of search_to_pattern/2 is that it doesn't needs a cursor().

Not quite; the generalization is that search_to_pattern/2 is that the pattern doesn't have to match at the top level, while move_to_cursor/2 does:
iex(1)> code = """
...(1)> if :foo != :bar do
...(1)>   IO.puts("hello")
...(1)> end
...(1)> """ |> Sourceror.parse_string!() |> Sourceror.Zipper.zip()

iex(2)> pattern = "IO.puts(__cursor__())"
"IO.puts(__cursor__())"

iex(3)> Sourceror.Zipper.move_to_cursor(code, pattern)
nil

iex(4)> Sourceror.Zipper.search_to_pattern(code, pattern)
#Sourceror.Zipper<
  #...
  {:__block__, [trailing_comments: [], leading_comments: [], delimiter: "\"", line: 2, column: 11],
   ["hello"]}
>

Now that I'm thinking about it, though, maybe find_pattern/2 might be a better name?

@zachallaun thanks for your explanation. My assumption about how move_to_cursor works was wrong. Now everything is clear and looks great. I think find_pattern/2 would be a better name.

This looks great!
On the naming part, I think search_pattern is a good name, find_* suggest to me that it will find with a function(like find, find_value, find_index etc in Enum), on the flip side I haven't seen many functions in the wild using search_* which makes me less worried about naming inconsistencies

Renamed search_to_pattern -> search_pattern 🙂


[DNM] west: update mcuboot to mainline PR 828

Fixes: #28921

This tests https://github.com/JuulLabs-OSS/mcuboot/pull/828

Closing in favor of #28967


[Results] Results now conforms to CVarArgType.

Fixes #1995. List already conforms to CVarArgType because it inherits from NSObject. /cc @tgoyne @bdash @segiddins

:+1:


how to use find() correctly?

hi serengil,
thanks to your library i have been able to build an application to recognize faces from a surveillance camera stream (4MP, very sharp, a bit oblique from above, but almost frontal face shot).
The recognition should be a part of a 2 factor authentication that runs automatically in the background. The goal is that our front door will only open if the numeric code is entered correctly (part 1) and the face recognition (part 2) confirms that it is one of the people in the database.
My database consists of 5-6 images each of me, my wife and my son. All pictures are frontal, with slight variations in the angle.
Unfortunately the thresholds don't seem to be set optimally for me, because for example my (6 year old) son or my wife always appear in the results when I walk into the picture.
I have tested it with other people... which look more similar to me and which should actually look completely different.
I would have expected in this case that either there is no recognition in the results, or that the threshold is "significantly" higher than when I am in the picture. Unfortunately, even unknown persons were sometimes recognized clearly false positive.
I know it's hard to tell when you don't see the images what that might be.
i have tried various mechanisms (only the first face from the find() result, all faces from the result and the one that occurs most often, etc.). The model and detector that works best seem to be vgg-face/facenet512 and yunet.
What would be the correct procedure in such a case? Especially the false positives from unknown persons should not appear.

i recommend you to store 1 image per person and use verify function. instead of checking its verified key in the respnse, check distance value. tune this according to your experiment. picking a smaller threshold will decrease false positives but it may increase false negatives which is okay for security purposes.


Getting Expression Matrices from the Segmented Masks

Hello, I'm trying to get the normalized_data.csv after segmentation.  I used ImageJ to generate individual grayscale images of each channel then use single channel inputs for segmentation.  When running the post-processing script, I am able to get the segmented masked overlaid on the images.  However, when I try to run the script to generate the expression matrices I get the 'KeyError: "not all values found in index 'fovs'".  Thanks in advance for your help.
I've pasted the error below:
img_sub_folder = "TIFs"
if not points:
# load channel data
all_points = os.listdir(tiff_dir)
all_points = [point for point in all_points if os.path.isdir(os.path.join(tiff_dir, point))
and point.startswith("Point")]
points = all_points
points.sort()
single_cell_dir = base_dir + "single_cell_output"
if not os.path.exists(single_cell_dir):
os.makedirs(single_cell_dir)
batch_size = 5
cohort_len = len(points)
num_batch = int(np.floor(cohort_len / batch_size))
combined_normalized_data = pd.DataFrame()
combined_transformed_data = pd.DataFrame()
for i in range(num_batch):
current_points = points[i * batch_size:(i + 1) * batch_size]
image_data = data_utils.load_imgs_from_tree(data_dir=tiff_dir, img_sub_folder=img_sub_folder,
fovs=current_points)
current_labels = segmentation_labels.loc[current_points, :, :, :]
normalized_data, transformed_data = segmentation_utils.generate_expression_matrix(segmentation_labels=current_labels, image_data=image_data)

combined_normalized_data = combined_normalized_data.append(normalized_data)
combined_transformed_data = combined_transformed_data.append(transformed_data)

if cohort_len % batch_size != 0:
current_points = points[num_batch * batch_size:]
image_data = data_utils.load_imgs_from_tree(data_dir=tiff_dir, img_sub_folder=img_sub_folder, fovs=current_points)
current_labels = segmentation_labels.loc[current_points, :, :, :]
normalized_data, transformed_data = segmentation_utils.generate_expression_matrix(segmentation_labels=current_labels, image_data=image_data)

combined_normalized_data = combined_normalized_data.append(normalized_data)
combined_transformed_data = combined_transformed_data.append(transformed_data)

KeyError                                  Traceback (most recent call last)
 in
21     current_points = points[num_batch * batch_size:]
22     image_data = data_utils.load_imgs_from_tree(data_dir=tiff_dir, img_sub_folder=img_sub_folder, fovs=current_points)
---> 23     current_labels = segmentation_labels.loc[current_points, :, :, :]
24
25     # segment the imaging data
/usr/local/lib/python3.6/site-packages/xarray/core/dataarray.py in getitem(self, key)
124             labels = indexing.expanded_indexer(key, self.data_array.ndim)
125             key = dict(zip(self.data_array.dims, labels))
--> 126         return self.data_array.sel(**key)
127
128     def setitem(self, key, value) -> None:
/usr/local/lib/python3.6/site-packages/xarray/core/dataarray.py in sel(self, indexers, method, tolerance, drop, **indexers_kwargs)
962         ds = self._to_temp_dataset().sel(
963             indexers=indexers, drop=drop, method=method, tolerance=tolerance,
--> 964             **indexers_kwargs)
965         return self._from_temp_dataset(ds)
966
/usr/local/lib/python3.6/site-packages/xarray/core/dataset.py in sel(self, indexers, method, tolerance, drop, **indexers_kwargs)
1796         indexers = either_dict_or_kwargs(indexers, indexers_kwargs, 'sel')
1797         pos_indexers, new_indexes = remap_label_indexers(
-> 1798             self, indexers=indexers, method=method, tolerance=tolerance)
1799         result = self.isel(indexers=pos_indexers, drop=drop)
1800         return result._overwrite_indexes(new_indexes)
/usr/local/lib/python3.6/site-packages/xarray/core/coordinates.py in remap_label_indexers(obj, indexers, method, tolerance, **indexers_kwargs)
323
324     pos_indexers, new_indexes = indexing.remap_label_indexers(
--> 325         obj, v_indexers, method=method, tolerance=tolerance
326     )
327     # attach indexer's coordinate to pos_indexers
/usr/local/lib/python3.6/site-packages/xarray/core/indexing.py in remap_label_indexers(data_obj, indexers, method, tolerance)
250         else:
251             idxr, new_idx = convert_label_indexer(index, label,
--> 252                                                   dim, method, tolerance)
253             pos_indexers[dim] = idxr
254             if new_idx is not None:
/usr/local/lib/python3.6/site-packages/xarray/core/indexing.py in convert_label_indexer(index, label, index_name, method, tolerance)
189             if np.any(indexer < 0):
190                 raise KeyError('not all values found in index %r'
--> 191                                % index_name)
192     return indexer, new_index
193
KeyError: "not all values found in index 'fovs'"

It looks like the segmentation_labels array doesn't contain a segmentation mask that matches the current_points names. Hence not all values found. You can print out the names within the current_points by just print(current_points), and print out the names in the xarray with print(segmentation_labels.fovs.values). This should help to figure out where the name mismatch is coming from.

Thanks. I think  that helped, but now I get a different error...

TypeError                                 Traceback (most recent call last)
 in
31
32     # segment the imaging data
---> 33     normalized_data, transformed_data = segmentation_utils.generate_expression_matrix(segmentation_labels=current_labels, image_data=image_data)
34
35     combined_normalized_data = combined_normalized_data.append(normalized_data)
/usr/local/lib/python3.6/site-packages/segmentation/utils/segmentation_utils.py in generate_expression_matrix(segmentation_labels, image_data, nuclear_counts)
487         # extract the counts per cell for each marker
488         marker_counts = compute_marker_counts(image_data.loc[fov, :, :, :], segmentation_label,
--> 489                                               nuclear_counts=nuclear_counts)
490
491         # remove the cell corresponding to background
/usr/local/lib/python3.6/site-packages/segmentation/utils/segmentation_utils.py in compute_marker_counts(input_images, segmentation_masks, nuclear_counts)
390     # get regionprops for each cell
391     cell_props = pd.DataFrame(regionprops_table(segmentation_masks.loc[:, :, 'whole_cell'].values,
--> 392                                                 properties=object_properties))
393
394     if nuclear_counts:
/usr/local/lib/python3.6/site-packages/skimage/measure/_regionprops.py in regionprops_table(label_image, intensity_image, properties, cache, separator)
622     """
623     regions = regionprops(label_image, intensity_image=intensity_image,
--> 624                           cache=cache)
625     return _props_to_dict(regions, properties=properties, separator=separator)
626
/usr/local/lib/python3.6/site-packages/skimage/measure/_regionprops.py in regionprops(label_image, intensity_image, cache, coordinates)
839
840     if not np.issubdtype(label_image.dtype, np.integer):
--> 841         raise TypeError('Label image must be of integer type.')
842
843     if coordinates is not None:
TypeError: Label image must be of integer type.

Oh, hmm. That's a bug that we didn't catch when we switched over to using the deepcell.org website. It returns the labels as floats, not ints.
As a workaround for now, if you add this line right after current_labels gets created, it will convert it to an int
import xarray as xr
current_labels = xr.DataArray(current_labels.values.astype('int'), coords=current_labels.coords, dims=current_labels.dims)

Got it and it works! Thank you!

I'm trying to see if I could use segment a multi-channel tif.  The expression matrix script runs, but the csv files are empty.  Is that because the channel information in the metadata is not read?

Yes, right now it only works for folders of TIFs. We're updating that part of the code tomorrow, we can add that in.

There's a couple options to resolve this; the long-term fix is to modify deepcell.org to to generate ints instead of floats for labels. We could either cast to int inside of compute_expression_matrix, or we could modify segmentation_labels when the xarray is being created/when the TIFs are read in

I think casting to int when reading TIFs into segmentation_labels is the easiest, most maintainable solution; we can include a warning message for the casting to int as well.

Okay great, sounds good!
On Fri, Aug 7, 2020 at 4:15 PM vacuous_planet<EMAIL_ADDRESS>wrote:

I think casting to int when reading TIFs into segmentation_labels is the
easiest, most maintainable solution; we can include a warning message for
the casting to int as well.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angelolab/segmentation/issues/147#issuecomment-670779863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJB47JMHEFMAMXL5B2IERTR7SDJDANCNFSM4PVCH3DA
.


can bytenode work with Cordova for mobile application?

Hi there,
not sure where to post this.
I was wondering if this javascript code compiler can work with Cordova?
Great job by the way!
Thank you

Of course this is not possible. Cordova does not use or support Node.js.

ok thank you for your feedback

@onelsonic maybe with https://github.com/janeasystems/nodejs-mobile-cordova using nodejs as backend, you can load bytenode but not for the front-end (you can put a AES crypto like "protection") and send it to front-end using cordova bridge. I will make some tests and post


Network may not restart or become enabled

The handler which is meant to restart and ensure the tinc networks are enabled and running  does not work in all scenarios:
---
- name: Restart Tinc
  ansible.builtin.service:
    name: tinc
    enabled: yes
    state: restarted
  tags: ansible-role-tinc

This handler only restarts/enables Tinc networks that are already 'registered' which the template unit service -- for lack of better terminology.
Meaning, restarting the tinc service will only restart tinc services that have already been enabled via something like:
systemctl enable --now tinc@mynetwork

Resolved by: https://github.com/spatterIight/ansible-role-tinc/pull/3


bug? code

I think there is a bug in UpdateService.CS
`
// Try to read the current version from disk
        try
        {
            var content = File.ReadLines(versionFile).First();
            var version = Version.Parse(versionFile);`

that sould be :
`
        try
        {
            var content = File.ReadLines(versionFile).First();
            var version = Version.Parse(content);`

Hey, nice find, thanks. Do you want to make a PR so you can appear as a contributor or do you want me to push the fix directly?

please push the fix directly I'm still browsing the code ... I see some enhacemnts and implemntations to be done ... you will see me make a pull request after that.
keep up the good work.
best regards.

Done https://github.com/openbullet/OpenBullet2/commit/79ccbbeac775d345cc8b4adbe67d8d0fe998afdd thank you and I'm looking forward to the PRs!


Check for Jupyter Notebook before allocating other terminal sizes.

Currently, the number of columns and rows used by progressbar2 in Jupyter notebooks is inherited from the shell from which it was run... which leads to some pretty weird behaviour. Instead, I think we should check for Jupyter notebooks first.
Is there ever a case where this doesn't make sense?
@WoLpH

Is there ever a case where this doesn't make sense?

Yes, actually... the ipython commanline shell. Detecting the terminal size is very error prone and I haven't found a good way to detect if we are within a Jupyter notebook which is why the method is only used as fallback.
This fix unfortunately "breaks" behavior in ipython which is not ideal either.

Hmmm... That's odd. When I checked this before, ZMQ is not used for the command line shell.
In [1]: get_ipython()
Out[1]: <IPython.terminal.interactiveshell.TerminalInteractiveShell at 0x10bca3b00>`

Is it different on other non-UNIX platforms?

You're right, my mind was somehow stuck in the past before jupyter detection was fixed properly. This fix works just fine :)

No worries! No I can remove my downstream hacks! Thanks @WoLpH :).

I've pushed out a new release so you can now install progressbar2 3.16.1 :)

Thanks!

Hi @WoLpH. This PR seems to have gone missing despite being merged. Can you confirm?

I honestly have no clue what happened here... it's not in the develop or master branch and doesn't appear to be in the history either. Since I've merged it using the Github pull request interface I'm pretty sure I didn't muck up anything locally but it's still missing somehow.
Very odd... I'll reapply your changes and create a new release

Thanks @WoLpH!
That is very odd indeed :). Anyway... all looks good now! Thanks again.

@WoLpH This patch has gone missing again. 🤒

How... why :(
The commit is somehow actually disappearing from git every time.
I've manually downloaded the patch and re-applied it using git apply instead of cherry-picking it again

It's definitely in v3.20.1 now :)


GCE: ingress only shows the first backend's healthiness in backends annotation

From https://github.com/kubernetes/features/issues/27#issuecomment-330589051.
We attach backends annotation to ingress object after LB creation:
  ...
  backends:		{"k8s-be-30910--7b4223ab4c1af15d":"UNHEALTHY"}

And from the implementation:
https://github.com/kubernetes/ingress/blob/937cde666e533e4f70087207910d6135c672340a/controllers/gce/backends/backends.go#L437-L452
Using only the first backend's healthiness to represent the healthiness for all backends seems incorrect.
cc @freehan

@MrHohn - anyone working on this one ? if not I can send a PR

@yastij  Nope, though I'm not quite sure how should we present the backends healthiness in annotation --- for huge cluster, we might have too many backends (nodes). It also seems unwise to append all of them via annotation...
cc @nicksardo

Maybe state healthy when all the backends are (checking all backends) , and unhealthy when some are (specifying which ones aren't healthy)

Maybe state healthy when all the backends are (checking all backends) , and unhealthy when some are (specifying which ones aren't healthy)

Yeah that sort of makes sense, though for the externlTrafficPolicy=Local case, some of the backends (nodes) may intentionally fail LB healthcheck so that traffic will only go to nodes that contains backend pods. Showing this as unhealthy may scare users, and it isn't actually unhealthy :(

We can detect this case nope ? if it is set to Local we can ignore the unhealthy status ?

I do not know if people use externalTrafficPolicy=Local with ingress (I've never tried it) and it's not something we document with ingress. It may technically work, but I don't know how well it works in production with rolling updates and other edge cases. Although if we wanted to support that case, another option is to correlate the instance status with the pods location(node).
I agree that this annotation is not accurate. Even if it shows a correct status, the annotation is only refreshed on every sync (which may be 10 minutes or longer if there are a lot of ingress objects). My question is whether this annotation is worth keeping. Wouldn't users be better off looking at the GCP Console for backend status? Do users have daemons which poll this annotation and perform alerts? If the only case we're concerned about is bad healthcheck configuration breaking all backends, couldn't we create an alert saying "All backends are unhealthy - please investigate"?
cc @csbell @nikhiljindal

This issue was moved to kubernetes/ingress-gce#35


OID4VCI plugin - Fix delete  exchange-supported records

Quick fix on ./oid4vci/exchange-supported/records delete. There is a typo that duplicates the "credential supported identifier" as a parameter causing deletes to fail.
FYI @dbluhm

You'll need to sign your commits. Then we can merge this.

@jamshale DCO has been added.

@jamshale thanks for the feedback. It is fixed now. I am switching between two github accounts and did not realize my DCO remediation PR was with a different github config from the initial PR. Anyway, fixed now after signing off on all the authors.

Dang! there's just a linting issue now at oid4vci/public_routes.py:353:91: . You can just add #E501to the end of the line.
This ones a bit annoying but it's the same in aca-py.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/23689

Triggering TagBot for merged registry pull request

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24098

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24207

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28773

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28773

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/81096

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/81172

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120824

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/122026


[docs]: some SVGs double scaled in patterns folder

Some SVG files in the patterns folder are double scaled from what their rendered form should be.  When used in an example shortcode this then makes the image larger then it should be.. This is more likely a function of export settings.
Need to rescale these images to the appropriate rendered size.
We can replace these by PNGs if necessary, @coreyvickery has mentioned issues with exporting from SVGs from XD.
Images scaled up 2x at render:

[x] https://ux.redhat.com/patterns/disclosure/#mobile
[x] https://ux.redhat.com/patterns/sticky-card/#style
[x] https://ux.redhat.com/patterns/sticky-card/#content

@zeroedin Image locations below.
disclosure-responsive-3.png
https://www.dropbox.com/scl/fi/vcvf0kj08lyrj9mwfwq4l/disclosure-responsive-3.png?rlkey=wkepv7hvmyufovad4fg754c3h&dl=0
sticky-card-style.png
https://www.dropbox.com/scl/fi/zh1tl93qfiatsncgflmqf/sticky-card-style.png?rlkey=f984ds6zadsrax7xyezx51sir&dl=0
sticky-card-content.png
https://www.dropbox.com/scl/fi/79nffomaydey30b1vbf2x/sticky-card-content.png?rlkey=4zuj3a68fhmaeurwyg5wfckf9&dl=0

@zeroedin re-assigning to you.

This was fixed with #1221 , closing


Some examples do not work under the new renderer

Environment

Bevy version: commit #340957994 (main as of Dec 19 2021)
OS & graphic stack: ArchLinux kernel 5.15.4; mesa/vulkan-radeon lib: v21.3.1; GPU: AMD ATI Radeon RX 5600

Bug
The following examples do not render things on screen as expected:

shader_material: Shows a gray screen with 8 green points forming the vertexes of a cube
shader_def: Just show a default gray window
shadow_biases: Shows a very interesting Moiré pattern with very pixelated shadows on the plane
wireframe: I see the default 3d_scene but the vertexes are a green pixel

Note: Other examples seem to work as intended.
Screenshots
Wireframe

shader_material

shadow_biases

More precision. I moved the camera and the shadows look way better. I do not see the same artifacts, though there is still more subtle artifacts such as a black grind on top of the plane.
shader_def
just a gray square.

The issues with wireframe, shader_material and shader_defs seem to be introduced by #3349

Can confirm, those three examples work on my machine on commit #6eb8e15e3d34f1c4171

The issue is that we need to specialize the pipeline for each entity in the queue_* functions, I'm working on a fix.


absolutely not self explaining

🚨 The issue tracker is not for questions 🚨
Hello,
IMHO, from the very beginning of using this product we've got the issue without reading Doc. We;'re firmly beehive that any (Ieditor,IDE) should be self explained. In your case -  for instance, lets go to the "File"  menu and click "New Few" -- what type of file should be opened  - "Java", "Python" ,""JavaScript or etc."  or something else ? Even the first step it looks pretty confusing. IMHO, this approuch looks wrong,
Thanks,

VS Code is not language specific and can be used as an editor for many types of files. Please see our documentation https://code.visualstudio.com/docs for help with getting started.


Use stack-path instead of inferring --programs

Closes #60.

Seems to work:

/cc @deemp

@pbrisbin, nice that you've implemented this!


Add Breakdown and Ligero to README.md

I guess we also have to update README.

Right, but isn't the difference only in the encoding method? We may implement it quickly if we would like?


Remove integration tests

The integration tests requires js and go to be in sync which is not the
case for much longer. For now it fails the PR builder...

Codecov Report

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

Continue to review full report at Codecov.

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


Why is LayerNorm default to False?

Not an issue, but a question:  why is the default LayerNorm function set to False?  In particular, for the point cloud example, the LayerNorm is not used.
Can you comment on the importance of having the nested LayerNorm activated for the model?  That is, in the paper there was not exposition on having LayerNorm activated versus not.
Thanks!

For our experiments, we found LayerNorm not very effective so set False as our default option. But it depends on the problem you want to solve.

Okay Great.  So it sounds like False is a good default for your experiments.  Thanks for the clarification!


chore: Use suggested tool for running prettier

This commit replaces precise-commits with pretty-quick. Apart from
the obviously more clever name, pretty-quick has a few benefits to it:

It's the suggested tool of Prettier, making it more heavily used and
more maticiously maintained.
It has really nicely formatted output
It doesn't support patch-based running.

Now, this last part is the real reason why this change is warranted.
When you run prettier on a patch (and that patch alone), it doesn't
take into consideration the code around it. This led to mangled code
(that no longer even compiled), and post-commit unstaged changes. Nah.
Instead, pretty-quick formats any file that's been touched for a given
commit. Sure, it's going to format more code, leading to larger diffs,
but I'm confident the upsides outweight its downsides.
Fixes #26

So far the prettier-commit-hook has caused some pain. Therefor I suggest we remove it as a hook and make it a regular npm run script, e.g npm run make-staged-files-prettier. As soon we feel the prettier setup is stable and fits our needs, it can make its comeback as commit hook.

Sure that's possible, but it's a bit sketchy to only run the prettier formatter whenever you want to. You can always skip the commit hook with -n - wouldn't it be safer (and provide more feedback, quicker) to keep it as a commit hook, and iterate on the setup until it fits our needs instead?

I feel prettier should iterate as regular run script as I believe a commit-hook should be more reliable than the two prettier hooks we tried so far.

Very well, I'll amend the pull request


0.2

Supports PHP:

8.0

Supports Laravel:

7.x
8.x

How do we maintain 0.1.x patches after this merge to master? Will that remain back on its own 0.1 branch instead, with tags 0.1.1/2/3 etc as it progresses, leaving the latest 0.2 here to progress on master? Not sure what the best practices are around this.. I presume the latest and greatest progresses on master though as makes sense.

Yeah that was my idea. I looked at laravel-debug-bar and other packages and it seems to be like how they do things.
We would have 0.1.1, 0.1.2, 0.1.3, 0.1.4... for Laravel 5+6 until we reach a stable version and have 1.0.0, 1.0.1, 1.1.0, 1.1.1... for Laravel 5+6
Same thing for 0.2 and 2.x.x for Laravel 7+8.
Did you have something else in mind?


Update the readme a little bit.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add objection-dynamic-finder plugin

This adds objection-dynamic-finder to the list of plugins.

Coverage remained the same at 96.017% when pulling eb244ef0957675ef8fe11a9d82e7c20ee4da86d7 on snlamm:plugin-dynamic-finder into 48fbe7a459f84252b4acf94ecdf1c43515450d26 on Vincit:master.

Awesome idea and plugin! Thank you!


Add utilities for working with function expressions

I've written these kinds of manipulations too many times and it seems better to have them in a package. Since this package has the best name :smile:, I chose this one. Hope that's OK.

Oh, and apologies for the fact that the tests are an awkward hybrid of Base.Test and FactCheck. I didn't notice they were using FactCheck until I'd written quite a few tests.
I will be happy to fix this. I personally find FactCheck vaguely annoying and would volunteer to switch all the tests to Base.Test. (Note that on julia 0.5, Base.Test now has what I see as the main attractions of FactCheck, and for julia 0.4 these are available in BaseTestNext.jl.)

It is perfectly OK :) I will check it, merge and release new version soon (within next 24 hours). I like the idea of switching from FactCheck to BaseTestNext. As I haven't tried BaseTestNext yet, I would like to do the rewrite of the old tests and learn/try it in the process.

Version 0.1.0 of ExpressionUtils with your changes and rewritten tests was just published :)


Error after import the package

I just import the package and appeared this errors
Unity Version: 2023.2.19
Entities: 1.2.0
Burst: 1.8.13
Error 1)
Library\PackageCache\com.annulusgames.magic-tween@0a5b840044\Runtime\Core\Systems\PathTweenSystems.cs(60,92): error CS8377: The type 'TweenDelegates<float3>' must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter 'T' in the generic type or method 'InternalCompilerInterface.GetComponentTypeHandle<T>(ref ComponentTypeHandle<T>, ref SystemState)'
Error 2)
Library\PackageCache\com.annulusgames.magic-tween@0a5b840044\Runtime\Core\Systems\TweenDelegateTranslationSystemBase.cs(46,93): error CS8377: The type 'TweenDelegates<TValue>' must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter 'T' in the generic type or method 'InternalCompilerInterface.GetComponentTypeHandle<T>(ref ComponentTypeHandle<T>, ref SystemState)'
Error 3)
Library\PackageCache\com.annulusgames.magic-tween@0a5b840044\Runtime\Core\Systems\TweenDelegateTranslationSystemBase.cs(47,99): error CS8377: The type 'TweenDelegatesNoAlloc<TValue>' must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter 'T' in the generic type or method 'InternalCompilerInterface.GetComponentTypeHandle<T>(ref ComponentTypeHandle<T>, ref SystemState)'
Error 4)
Library\PackageCache\com.annulusgames.magic-tween@0a5b840044\Runtime\Core\Systems\StringTweenSystems.cs(89,92): error CS8377: The type 'TweenDelegates<string>' must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter 'T' in the generic type or method 'InternalCompilerInterface.GetComponentTypeHandle<T>(ref ComponentTypeHandle<T>, ref SystemState)'
Error 5)
Library\PackageCache\com.annulusgames.magic-tween@0a5b840044\Runtime\Core\Transforms\TransformTranslationSystemBase.cs(123,99): error CS8377: The type 'TweenTargetTransform' must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter 'T' in the generic type or method 'InternalCompilerInterface.GetComponentTypeHandle<T>(ref ComponentTypeHandle<T>, ref SystemState)'

This appears to be a bug in the unity.entities package. They seem to have overlooked SystemAPI.ManagedAPI.GetComponentTypeHandle however it works if you replace those calls with EntityManager.GetComponentTypeHandle

Opened a PR with the fix.

Same Error, thanks @coryleach


Doesn't work on the other machines?

I've tried this on my own computer and it does work fine, but I gave the file to 2 of my friends with their permissions of course, and neither both send anything to the email even they have typed the amount of how many characters I set.
Does it actually work on the outside? or only on my machine?

Hello, yes it works.
Ask to your friend if the folder %appdata%\(s)AINT exist and it has some files, if the folder exist so probably or some AV can be blocking the sending mail or the email or password can be wrong.


Allow override config values by ENV variable

I want to set config values from ENV instead of package.json.
That feature allow me to reuse same docker images with different envs.
I have tried to override npm_package_config values, but it seems that npm does not let user to override any config values under npm_package_config namespace.
I have added config.js as config loader class.
It uses existing package.json as default configuration, and use ENV variables to override config.
BTW
Project's contributing.md seems to be empty.
Let me know if there's any guideline for pull req.

I think overriding ENV variable may not be good idea. That makes requiring config.js to have side effect.
I agree that it minimizes changes from existing codebase, but there is a risk that somebody forget to include config.js.
I'd rather have dependency than side effect.
Having said that, it seems to be possible to override ENV values.
And I will be happy to rewrite my code if you prefer that way.

@tomohisaota Thanks for your pull request. Iam adding another url param for rasa-core server and merged this into core-integration branch. I willadd it to master along with my change.
Thanks again for your contribution.


How to run this locally

Right now we have to use the line - realise_en = Realiser(host = "nlg.kutlak.info" , port = 40000)
to create the realiser and make the code run . What does this line do?
moreover, if I wanted to run this locally without calling out to the port - how do I do that?
Working on a deadline - would really appreciate the help!!

Hi @stalwar5,
The library is using SimpleNLG for realisation. This is a Java library that comes with a web server. You can start your own version of SimpleNLG on your local machine and just connect to that.
In order to do that, you can either use the compiled jar in nlglib/res/simplenlg.jar or you can download your own version of SimpleNLG and start the server either from the source code or compile it into a jar and start that. I am not sure how far behind is my copy of SimpleNLG (should be okay though as SimpleNLG is not really developed much anymore). The only complication with running the SimpleNLG package is that you need to have a lexicon -- either an XML version or NIH lexicon (see the SimpleNLG repo for explanations). I recall doing some modifications to SimpleNLG to allow passing the path to the lexicon as a parameter but don't quite remember whether it is still necessary. I suggest you try to get it working yourself (do read any messages in console as you run the jar file -- it should let you know if it has problems finding the lexicon). If that fails, I have a clone of SimpleNLG repo too and you could try to use it instead of the original. That is the version running on nlg.kutlak.info. If you can't get it working, post another message here and I will have a look. It might take a few days to reply though as I am quite busy at the moment.
Good luck,
Roman

Hi Roman,
SimpleNLG jar is a jar without main method. So how have you run it. Please explain the steps. Have you deployed it on apache webserver ??
Thanks and Regards,
Priyanka

@stalwar5,
If you are able to run it locally, Please suggest. Your help will be appreciated ..
Thanks and Regards,
Priyanka


[ZEPPELIN-5190] flink-1.12-shims CollectStreamTableSink package name is not correct

What is this PR for?
fix bug: flink-1.12-shims CollectStreamTableSink package name is not correct
What type of PR is it?
[Bug Fix]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5190

Screenshots (if appropriate)
Questions:

Does the licenses files need update?No
Is there breaking changes for older versions?No
Does this needs documentation?No

LGTM

LGTM

Please rebase your branch with the current master.  I have added a hotfix to fix the CI.

Please rebase your branch with the current master.  I have added a hotfix to fix the CI.

LGTM

LGTM


[C++] Add support for uint64 in JSON when possible

Newtonsoft JSON.NET supports uint64 where BigInteger is supported. This pull request allows Bond's SimpleJsonProtocol to leverage that support.

Addressed Ted's comments and add entry in CHANGELOG.
Please squash commits when merging.

gRPC build on Travis failed for what should be an unrelated reason. Restarting Travis build.

LGTM. Will wait for CI builds before merging.


[1.13] Remove nogroup group creation

High-level description
ATT&T is blocked from upgrading DC/OS because their security team does not allow non-standard linux group creation. We currently create the nogroup group, but it appears that it may not actually be used any longer. It looks like it was originally used by nginx (admin router). Depending where the service was started from, it'd set the nginx configuration to use either the nobody group (for Redhat based systems), or the nogroup group (for Debian based systems). It looks like we started creating the nogroup group on all systems to keep things consistent.
Backports: https://github.com/dcos/dcos/pull/6166
Corresponding DC/OS tickets (required)

COPS-5220

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot request-review @drewvanstone @br-lewis @makkes @bamarni @rgo3

Can one of the @dcos/admins  @mesosphere/dcos-owners issue the following command?
@mesosphere-mergebot override-status
teamcity/dcos/test/terraform/aws/onprem/static/group1 https://jira.mesosphere.com/browse/DCOS-58518

@mesosphere-mergebot override-status teamcity/dcos/test/terraform/aws/onprem/static/group1 https://jira.mesosphere.com/browse/DCOS-58518

@mesosphere-mergebot sync

@mesosphere-mergebot sync


Ratatui version question

Originally posted by @dustinblackman in https://github.com/dustinblackman/oatmeal/issues/33#issuecomment-1872940856

Ratatui is a fast moving library and they've introduced breaking changes in the latest version that I haven't supported. It's one of the reasons I keep all my dependencies pinned.

I wonder if you can expand a bit on what broke in 0.25 for oatmeal?
I just bumped the version of Ratatui in Cargo.toml and it compiles and tests fine. I also bumped every package to latest without failure (except yansi, which has a small api change in the 1.0.0 gamma release)

Hey there!
Sure, my comment wasn't any sly against Ratatui, I love using it and am glad you guys move fast to make the API as clean as possible.
I haven't dug super deep, but looking at it now with fresh eyes it'stui-textarea pulling in 0.24.0, and Oatmeal trying to pull in 0.25.0, and they're not playing nice together. I'd actually probably blame cargo+myself with how I'm pinning dependencies.
   Compiling oatmeal v0.12.3 (/Users/user/git/oatmeal)
error[E0277]: the trait bound `impl ratatui::widgets::Widget + '_: Widget` is not satisfied
   --> src/application/ui.rs:117:37
    |
117 |                 frame.render_widget(textarea.widget(), layout[1]);
    |                       ------------- ^^^^^^^^^^^^^^^^^ the trait `Widget` is not implemented for `impl ratatui::widgets::Widget + '_`
    |                       |
    |                       required by a bound introduced by this call
    |
    = help: the following other types implement trait `Widget`:
              BarChart<'a>
              ratatui::widgets::Block<'a>
              Canvas<'a, F>
              Chart<'a>
              ratatui::widgets::Clear
              Gauge<'a>
              LineGauge<'a>
              List<'a>
            and 4 others
note: required by a bound in `Frame::<'_>::render_widget`
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ratatui-0.25.0/src/terminal.rs:614:12
    |
612 |     pub fn render_widget<W>(&mut self, widget: W, area: Rect)
    |            ------------- required by a bound in this associated function
613 |     where
614 |         W: Widget,
    |            ^^^^^^ required by this bound in `Frame::<'_>::render_widget`

error[E0308]: mismatched types
    --> src/domain/models/textarea.rs:12:13
     |
11   |           textarea.set_block(
     |                    --------- arguments to this method are incorrect
12   | /             Block::default()
13   | |                 .borders(Borders::ALL)
14   | |                 .border_type(BorderType::Double)
15   | |                 .title("Enter prompt")
16   | |                 .padding(Padding::new(1, 1, 0, 0)),
     | |__________________________________________________^ expected `ratatui::widgets::block::Block<'_>`, found `ratatui::widgets::Block<'_>`
     |
     = note: `ratatui::widgets::Block<'_>` and `ratatui::widgets::block::Block<'_>` have similar names, but are actually distinct types
note: `ratatui::widgets::Block<'_>` is defined in crate `ratatui`
    --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ratatui-0.25.0/src/widgets/block.rs:233:1
     |
233  | pub struct Block<'a> {
     | ^^^^^^^^^^^^^^^^^^^^
note: `ratatui::widgets::block::Block<'_>` is defined in crate `ratatui`
    --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ratatui-0.24.0/src/widgets/block.rs:230:1
     |
230  | pub struct Block<'a> {
     | ^^^^^^^^^^^^^^^^^^^^
     = note: perhaps two different versions of crate `ratatui` are being used?
note: method defined here
    --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tui-textarea-0.4.0/src/textarea.rs:1648:12
     |
1648 |     pub fn set_block(&mut self, block: Block<'a>) {
     |            ^^^^^^^^^

Some errors have detailed explanations: E0277, E0308.
For more information about an error, try `rustc --explain E0277`.
error: could not compile `oatmeal` (bin "oatmeal") due to 2 previous errors

Thanks for the extra info :)
I definitely didn't take it as a slight - I was more interested to check if we'd broken something without knowing. I've seen the similar textarea related problems pop up from time to time. I think they're usually fixed by running cargo update.
For an app I'd really suggest just letting your lock file do the dependency pinning and make sure your install instructions specify --locked. This says to the user "use the versions I've tested this with, it might work with updated versions, but you're on your own if it breaks". Particularly for something that hits a network API, I'd want that to generally stay updated. Also this gives you power to be explicit when pinning to address a breaking change rather than never really knowing whether your updates will break things.


Missing libffi dependency when installing yotta on Mac OS

Just installed yotta on Mac OS 10.10.5 and hit two issues:

Missing cython dependency (already reported in mbedmicro/pyOCD#163)
Missing libffi dependency

The former is trivially resolved running pip install cython.
The later is resolved running brew install libffi.
Terminal log follows for reference:
e107250-mac:~ samtay01$ pip install yotta
You are using pip version 7.1.0, however version 7.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting yotta
Requirement already satisfied (use --upgrade to upgrade): semantic-version<3,>=2.3.1 in /usr/local/lib/python2.7/site-packages (from yotta)
Requirement already satisfied (use --upgrade to upgrade): Jinja2<3,>=2.7.0 in /usr/local/lib/python2.7/site-packages (from yotta)
Collecting argcomplete<1.0,>=0.8.0 (from yotta)
  Using cached argcomplete-0.9.0-py2.py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): requests<3,>=2.4.3 in /usr/local/lib/python2.7/site-packages (from yotta)
Collecting jsonschema<3.0,>=2.4.0 (from yotta)
  Using cached jsonschema-2.5.1-py2.py3-none-any.whl
Collecting cryptography>=0.8 (from yotta)
  Using cached cryptography-1.0.tar.gz
Requirement already satisfied (use --upgrade to upgrade): colorama<0.4,>=0.3 in /usr/local/lib/python2.7/site-packages (from yotta)
Requirement already satisfied (use --upgrade to upgrade): PyGithub<2,>=1.25 in /usr/local/lib/python2.7/site-packages (from yotta)
Collecting PyJWT<2.0,>=1.0 (from yotta)
  Using cached PyJWT-1.4.0-py2.py3-none-any.whl
Collecting mbed-test-wrapper<0.1.0,>=0.0.2 (from yotta)
Collecting valinor<1.0,>=0.0.0 (from yotta)
Requirement already satisfied (use --upgrade to upgrade): hgapi<2,>=1.7 in /usr/local/lib/python2.7/site-packages (from yotta)
Collecting intelhex<3.0,>=2.0 (from yotta)
  Using cached intelhex-2.0-py2.py3-none-any.whl
Collecting pathlib<1.1,>=1.0.1 (from yotta)
Requirement already satisfied (use --upgrade to upgrade): MarkupSafe in /usr/local/lib/python2.7/site-packages (from Jinja2<3,>=2.7.0->yotta)
Collecting functools32 (from jsonschema<3.0,>=2.4.0->yotta)
Requirement already satisfied (use --upgrade to upgrade): idna>=2.0 in /usr/local/lib/python2.7/site-packages (from cryptography>=0.8->yotta)
Requirement already satisfied (use --upgrade to upgrade): pyasn1>=0.1.8 in /usr/local/lib/python2.7/site-packages (from cryptography>=0.8->yotta)
Requirement already satisfied (use --upgrade to upgrade): six>=1.4.1 in /usr/local/lib/python2.7/site-packages (from cryptography>=0.8->yotta)
Requirement already satisfied (use --upgrade to upgrade): setuptools in /usr/local/lib/python2.7/site-packages (from cryptography>=0.8->yotta)
Requirement already satisfied (use --upgrade to upgrade): enum34 in /usr/local/lib/python2.7/site-packages (from cryptography>=0.8->yotta)
Requirement already satisfied (use --upgrade to upgrade): ipaddress in /usr/local/lib/python2.7/site-packages (from cryptography>=0.8->yotta)
Collecting cffi>=1.1.0 (from cryptography>=0.8->yotta)
  Using cached cffi-1.2.1.tar.gz
Collecting pyyaml<4,>=3 (from valinor<1.0,>=0.0.0->yotta)
Collecting pyOCD<1.0,>=0.3 (from valinor<1.0,>=0.0.0->yotta)
Collecting project-generator<0.8.0,>=0.7.0 (from valinor<1.0,>=0.0.0->yotta)
Requirement already satisfied (use --upgrade to upgrade): pycparser in /usr/local/lib/python2.7/site-packages (from cffi>=1.1.0->cryptography>=0.8->yotta)
Collecting hidapi (from pyOCD<1.0,>=0.3->valinor<1.0,>=0.0.0->yotta)
Collecting argparse (from project-generator<0.8.0,>=0.7.0->valinor<1.0,>=0.0.0->yotta)
  Using cached argparse-1.3.0-py2.py3-none-any.whl
Collecting xmltodict (from project-generator<0.8.0,>=0.7.0->valinor<1.0,>=0.0.0->yotta)
Building wheels for collected packages: cryptography, cffi
  Running setup.py bdist_wheel for cryptography
  Complete output from command /usr/local/opt/python/bin/python2.7 -c "import setuptools;__file__='/private/var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/pip-build-gA_GRX/cryptography/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" bdist_wheel -d /var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/tmpIyakpapip-wheel-:
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  c/_cffi_backend.c:13:10: fatal error: 'ffi.h' file not found
  #include <ffi.h>
           ^
  1 error generated.
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/private/var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/pip-build-gA_GRX/cryptography/setup.py", line 307, in <module>
      **keywords_with_side_effects(sys.argv)
    File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/core.py", line 111, in setup
      _setup_distribution = dist = klass(attrs)
    File "/usr/local/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__
      self.fetch_build_eggs(attrs['setup_requires'])
    File "/usr/local/lib/python2.7/site-packages/setuptools/dist.py", line 313, in fetch_build_eggs
      replace_conflicting=True,
    File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 836, in resolve
      dist = best[req.key] = env.best_match(req, ws, installer)
    File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1081, in best_match
      return self.obtain(req, installer)
    File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1093, in obtain
      return installer(requirement)
    File "/usr/local/lib/python2.7/site-packages/setuptools/dist.py", line 380, in fetch_build_egg
      return cmd.easy_install(req)
    File "/usr/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 629, in easy_install
      return self.install_item(spec, dist.location, tmpdir, deps)
    File "/usr/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 659, in install_item
      dists = self.install_eggs(spec, download, tmpdir)
    File "/usr/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 842, in install_eggs
      return self.build_and_install(setup_script, setup_base)
    File "/usr/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1070, in build_and_install
      self.run_setup(setup_script, setup_base, args)
    File "/usr/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1058, in run_setup
      raise DistutilsError("Setup script exited with %s" % (v.args[0],))
  distutils.errors.DistutilsError: Setup script exited with error: command 'clang' failed with exit status 1

  ----------------------------------------
  Failed building wheel for cryptography
  Running setup.py bdist_wheel for cffi
  Complete output from command /usr/local/opt/python/bin/python2.7 -c "import setuptools;__file__='/private/var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/pip-build-gA_GRX/cffi/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" bdist_wheel -d /var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/tmpcWxi2Qpip-wheel-:
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  Package libffi was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libffi.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libffi' found
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.macosx-10.10-x86_64-2.7
  creating build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/__init__.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/api.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/backend_ctypes.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/cffi_opcode.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/commontypes.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/cparser.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/ffiplatform.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/gc_weakref.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/lock.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/model.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/recompiler.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/setuptools_ext.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/vengine_cpy.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/vengine_gen.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/verifier.py -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/_cffi_include.h -> build/lib.macosx-10.10-x86_64-2.7/cffi
  copying cffi/parse_c_type.h -> build/lib.macosx-10.10-x86_64-2.7/cffi
  running build_ext
  building '_cffi_backend' extension
  creating build/temp.macosx-10.10-x86_64-2.7
  creating build/temp.macosx-10.10-x86_64-2.7/c
  clang -fno-strict-aliasing -fno-common -dynamic -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/System/Library/Frameworks/Tk.framework/Versions/8.5/Headers -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DUSE__THREAD -I/usr/include/ffi -I/usr/include/libffi -I/usr/local/include -I/usr/local/opt/openssl/include -I/usr/local/opt/sqlite/include -I/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c c/_cffi_backend.c -o build/temp.macosx-10.10-x86_64-2.7/c/_cffi_backend.o
  c/_cffi_backend.c:13:10: fatal error: 'ffi.h' file not found
  #include <ffi.h>
           ^
  1 error generated.
  error: command 'clang' failed with exit status 1

  ----------------------------------------
  Failed building wheel for cffi
Failed to build cryptography cffi
Installing collected packages: argcomplete, functools32, jsonschema, cffi, cryptography, PyJWT, mbed-test-wrapper, pyyaml, hidapi, intelhex, pyOCD, argparse, xmltodict, project-generator, valinor, pathlib, yotta
  Running setup.py install for cffi
    Complete output from command /usr/local/opt/python/bin/python2.7 -c "import setuptools, tokenize;__file__='/private/var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/pip-build-gA_GRX/cffi/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/pip-dhvPAn-record/install-record.txt --single-version-externally-managed --compile:
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    running install
    running build
    running build_py
    running build_ext
    building '_cffi_backend' extension
    clang -fno-strict-aliasing -fno-common -dynamic -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/System/Library/Frameworks/Tk.framework/Versions/8.5/Headers -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DUSE__THREAD -I/usr/include/ffi -I/usr/include/libffi -I/usr/local/include -I/usr/local/opt/openssl/include -I/usr/local/opt/sqlite/include -I/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c c/_cffi_backend.c -o build/temp.macosx-10.10-x86_64-2.7/c/_cffi_backend.o
    c/_cffi_backend.c:13:10: fatal error: 'ffi.h' file not found
    #include <ffi.h>
             ^
    1 error generated.
    error: command 'clang' failed with exit status 1

    ----------------------------------------
Command "/usr/local/opt/python/bin/python2.7 -c "import setuptools, tokenize;__file__='/private/var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/pip-build-gA_GRX/cffi/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/pip-dhvPAn-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/var/folders/yv/gm0nzvqj4v176t_w2rp5yk1svdyh2q/T/pip-build-gA_GRX/cffi
e107250-mac:~ samtay01$ brew install libffi
==> Downloading https://homebrew.bintray.com/bottles/libffi-3.0.13.yosemite.bottle.tar.gz
######################################################################## 100.0%
==> Pouring libffi-3.0.13.yosemite.bottle.tar.gz
==> Caveats
This formula is keg-only, which means it was not symlinked into /usr/local.

Some formulae require a newer version of libffi.

Generally there are no consequences of this for you. If you build your
own software and it requires this formula, you'll need to add to your
build variables:

    LDFLAGS:  -L/usr/local/opt/libffi/lib

==> Summary
🍺  /usr/local/Cellar/libffi/3.0.13: 14 files, 412K

Related to pyOCD issue mentioned above - v0.5.1 which was released today should fix this

Closing this as it was a pyOCD issue, now fixed. Thanks for the detailed error report!


CCD-3853 run FTAs against next test definition release

JIRA link (if applicable)
CCD-3853 "Intermittent Data Store FT failures in nightly build pipelines"
Change description
Run FTAs against the next ccd-test-definitions release, see hmcts/ccd-test-definitions#58.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

This PR is now ready for release: after removing temporary pipeline configuration.


Do not spawn a pet with a broken image if you cancel spawning a pet.

Before if you are in the process of spawning a pet and you cancel the operation with escape or close the spawn pet tab. A broke image is shown like below.

However with this new change, if the process of creating a pet is cancelled, an image is not displayed and a vscode.window.showErrorMessage is displayed. Like so...

Do not spawn a pet with a broken image if you cancel spawning a pet.
Created a .prettierignore for Markdown files.
Bumped the LICENSE.
Fixed Typo in the README

@tonybaloney this PR should be ready for review

Thanks @Harry-Hopkinson


Use event color for the event line

Colors for lines are different than those forced for events. In this example I forced some events to green and the lines are blue (I guess because my obsidian has blue as main color).
I think it might improve readability to actually have the same color (or maybe an option to set line color ?)

Thanks for this report! You are correct: Chronos uses your Obsidian theme for the default accents, which is why the lines appear blue in your case.
I agree, it would be ascetically more pleasing for the line and dot to match the color of the item.
Unfortunately, due to the complicated architecture of the rendered timeline from the vis-js library, it is difficult to dynamically set the style of the lines from the event.
Since it's difficult to set the line color dynamically, I experimented with using the text color instead of Obsidian accent color for the lines. It's less of a color clash with items that have colors, but seems somehow too intense to me with high density of background and foreground lines. What do you think?
Use theme (current)

Default to text color (Dark mode)

Default to text color (Light mode)

Looks good on the white background. But it seems to fail in the black background. I live in a dark mode world, , so for me this isn't an improvement.
Or... Just had a thought before I click 'send'. What if there was an option to change the color/intensity of the background/frame lines? Then the text colour lines would pop a bit more. Just a thought.

@slartybartfastest thanks for the feedback!
Interesting thought. Will keep this issue open while prioritizing some other issues first


Mode-responsive icons

Currently, if I pick black color for an icon,  would expect it to be white in dark mode and so on, for other selections.
One way to do that would be to have separate section for per mode but that would be too much.  I'd prefer if the colors are already paired so selecting one for a mode to automatically select a corresponding one for the alternative mode.

I've already implemented this for all colors except black and white. Inverting black and white is implemented for the next release.

It still doesn't work correctly.  Only after disabling and enabling the extension, it turns white.


release: v1.4.1

[1.4.1] (April 22 2024)
Feat:

Implemented safe parsing of message.data to prevent errors in data handling.
Enhanced efficiency by reusing user and channel information stored in localStorage, reducing redundant data requests and improving user experience.
Established functionality to connect the ChatAiWidget upon component mounting, improving real-time interaction capabilities. This includes various improvements such as managing connections and handling UI behavior between mobile and desktop platforms.

Fix:

Corrected the position of the feedback dialog which used to be incorrectly placed after bumping up UIKit version.

Chore:

Updated key structures to include appId and boId, which allows better identification and tracking of business objects.

LocalStorage key format: @sendbird/chat-ai-widget/${appId}/${botId}

Cleanup of Unused Files and Dependencies: Removed unnecessary files and dependencies like dompurify to streamline the codebase.

/bot create ticket

[Creating Ticket] 🔖 Done https://sendbird.atlassian.net/browse/SDKRLSD-1243


Update readme

First draft for the readme.
Would it be good if I added some gifs to the readme for some of the features?
Signed-off-by: David Kwon<EMAIL_ADDRESS>

Very nice! Thanks @xorye